22.4.9 NB-IoT / RRC connection establishment / Access Barring for UE with AC 11 to 15 / MO exception data / ab-Category a, b and c

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

22.4.9.1 Test Purpose (TP)

(1)

with { UE in RRC_IDLE state on VPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB and ab-BarringForExceptionData is set to TRUE in the ab-Common and ab-Category set to c }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE does not transmit RRCConnectionRequest-NB message }

}

(2)

with { UE in RRC_IDLE state on OPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB and ab-BarringForExceptionData is set to TRUE in the ab-Common and ab-Category set to c }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE transmits RRCConnectionRequest-NB message }

}

(3)

with { UE in RRC_IDLE state on OPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB and ab-BarringForExceptionData is set to TRUE in the ab-Common and ab-Category set to b }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE does not transmit RRCConnectionRequest-NB message }

}

(4)

with { UE in RRC_IDLE state on HPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB and ab-BarringForExceptionData is set to TRUE in the ab-Common and ab-Category set to b }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE transmits RRCConnectionRequest-NB message }

}

(5)

with { UE in RRC_IDLE state on HPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB and ab-BarringForExceptionData is set to TRUE in the ab-Common and ab-Category set to a }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE does not transmit RRCConnectionRequest-NB message }

}

(6)

with { UE in RRC_IDLE state on HPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB and ab-BarringForExceptionData is not present in the ab-Common and ab-Category set to a }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE transmits RRCConnectionRequest-NB message }

}

(7)

with { UE in RRC_IDLE state on HPLMN having an Access Class with a value in the range 11..15 and with Access barring enabled in MasterInformationBlock-NB/MasterInformationBlock-TDD-NB and broadcasts SystemInformationBlockType14-NB with a special access class bitmap different from the special access class bitmap set in USIM and ab-BarringForExceptionData is set to TRUE in the ab-Common and ab-Category set to a }

ensure that {

when { UE has user data pending related to an exceptional event }

then { UE transmits RRCConnectionRequest-NB message }

}

22.4.9.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.3.14. Unless otherwise stated these are Rel-13 requirements.

[TS 36.331, clause 5.3.3.14]

The UE shall:

1> if the UE is connected to EPC, ab-Enabled included in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB is set to TRUE and SystemInformationBlockType14-NB is broadcast:

2> if access to the cell is not barred due to ab-PerNRSRP and ab-Param is included:

3> if the ab-Common is included in ab-Param:

4> if the UE belongs to the category of UEs as indicated in the ab-Category contained in ab-Common; and

4> if for the Access Class of the UE, as stored on the USIM and with a value in the range 0..9, the corresponding bit in the ab-BarringBitmap contained in ab-Common is set to one:

5> if the establishmentCause received from higher layers is set to mo-ExceptionData and ab-BarringForExceptionData is set to FALSE in the ab-Common:

6> consider access to the cell as not barred;

5> else:

6> if the UE has one or more Access Classes, as stored on the USIM, with a value in the range 11..15, which is valid for the UE to use according to TS 22.011 [10] and TS 23.122 [11] and for at least one of these valid Access Classes for the UE, the corresponding bit in the ab-BarringForSpecialAC contained in ab-Common is set to zero:

NOTE 1: ACs 12, 13, 14 are only valid for use in the home country and ACs 11, 15 are only valid for use in the HPLMN/ EHPLMN.

7> consider access to the cell as not barred;

6> else:

7> consider access to the cell as barred;

4> else:

5> consider access to the cell as not barred;

22.4.9.3 Test description

22.4.9.3.1 Pre-test conditions

System Simulator:

– Three inter-frequency multi-PLMN cells as specified in TS 36.508 clause 8.1.4.1.2 are configured broadcasting PLMNs as indicated in Table 22.4.9.3.1–1.

– The PLMNs are identified in the test by the identifiers in Table 22.4.9.3.1–1.

Table 22.4.9.3.1-1: PLMN identifiers

Ncell

PLMN name

MCC

MNC

1

PLMN4

001

01

12

PLMN1

001

11

13

PLMN2

001

21

– System information combination 4 as defined in TS 36.508[18] clause 8.1.4.3.1.1 is used in NB-IoT cells;

UE:

– The UE is in Automatic PLMN selection mode.

– The UE is equipped with a USIM containing default values (as per TS 36.508) except for those listed in Table 22.4.9.3.1–2.

Table 22.4.9.3.1-2: USIM configuration

USIM field

Value

Access Technology Identifier

EFIMSI

The HPLMN (MCC+MNC) of the IMSI is set to PLMN4.

EFPLMNwAcT

PLMN2

Remaining mandatory entries use default values

All specified

E-UTRAN

EFOPLMNwACT

PLMN1

Remaining defined entries use default values

All specified

EFHPLMNwAcT

PLMN4

E-UTRAN

EFACC

Type “C” as defined in TS 34.108 clause 8.3.2.15

EFNASCONFIG

“Exception Data Reporting Allowed is set to 01”

– The UE belongs to access class 0 and special access class 11 and 15.

Preamble:

– The UE is in state Registered, Idle Mode (State 3-NB) on Ncell 13 according to [18].

22.4.9.3.2 Test procedure sequence

Table 22.4.9.3.2-1 shows the cell configurations used during the test. The configuration T0 indicates the initial conditions. Subsequent configurations marked “T1”, “T2” etc are applied at the points indicated in the Main behaviour description in Table 22.4.9.3.2-2. Cell powers are chosen for a serving cell and a non-suitable “Off” cell as defined in TS 36.508 Table 8.3.2.2.1-1.

Table 22.4.9.3.2-1: Cell configuration changes over time

 

Parameter

Unit

Ncell 1

Ncell 12

Ncell 13

Remarks

T0

NRS EPRE

dBm/15kHz

“Off”

“Off”

-85

Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1

T1

NRS EPRE

dBm/15kHz

“Off”

-85

-120

Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1

T2

NRS EPRE

dBm/15kHz

-85

-120

“Off”

Power level “Off” is defined in TS 36.508 Table 8.3.2.2.1-1

Table 22.4.9.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

SS adjusts MasterInformationBlock-NB/MasterInformationBlock-TDD-NB of Ncell 13 with ab-Enabled-r13/ab-Enabled-r15 set to TRUE and SystemInformationBlockType14-NB of Ncell 13

2

The SS notifies the UE of change of System Information

<–

Paging-NB

3

Wait for 2.1* modification period (Note 4) to allow the new system information to take effect.

4

Trigger the UE to initiate MO Exception Data

5

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 13 within 30s?

–>

RRCConnectionRequest-NB

1

F

6

SS adjusts cell levels according to row T1 of table 22.4.9.3.2-1

7

Step 1 to 5 of generic test procedure in TS 36.508 subclause 8.1.5A.5 to take place on Ncell 12.

NOTE: The UE performs a TAU procedure.

7A

The SS starts timer Timer_1 = 10 s

EXCEPTION: Steps 7Ba1 to 7Bb1 describe a transaction that depends on the UE behaviour; the “lower case letter” identifies a test sequence that takes place if a specific behaviour happens (Note 1)

7Ba1

The UE transmits one IP packet embedded in a ESM DATA TRANSPORT and ULInformationTransfer-NB

–>

NAS: ESM DATA TRANSPORT

7Bb1

The SS waits for Timer_1 expiry

7C

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

8

SS adjusts MasterInformationBlock-NB/MasterInformationBlock-TDD-NB of Ncell 12 with ab-Enabled-r13/ab-Enabled-r15 set to TRUE and SystemInformationBlockType14-NB of Ncell 12

9

The SS notifies the UE of change of System Information

<–

Paging-NB

10

Wait for 2.1* modification period (Note 4) to allow the new system information to take effect.

11

Trigger the UE to initiate MO Exception Data

12

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 12 with establishmentCause-r13 set to mo-ExceptionData?

–>

RRCConnectionRequest-NB

2

P

13-15

Steps 2 to 4 of the ‘Generic Test Procedure NB-IoT Control Plan CIoT MO user data transfer non-SMS transport’ as described in TS 36.508 [18], clause 8.1.5A.3.3 are performed

NOTE: The UE will transmit one ESM DATA TRANSPORT message containing user data generated in step 11.

16

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

17

SS adjusts SystemInformationBlockType14-NB of Ncell 12 with ab-Category set to ‘b’

18

Trigger the UE to initiate MO Exception Data

19

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 12 within 30s?

–>

RRCConnectionRequest-NB

3

F

20

SS adjusts cell levels according to row T2 of table 22.4.9.3.2-1

21

Step 1 to 5 of generic test procedure in TS 36.508 subclause 8.1.5A.5 to take place on Ncell 1.

NOTE: The UE performs a TAU procedure.

21A

The SS starts timer Timer_1 = 10s

EXCEPTION: Steps 21Ba1 to 21Bb1 describe a transaction that depends on the UE behaviour; the “lower case letter” identifies a test sequence that takes place if a specific behaviour happens (Note 2)

21Ba1

The UE transmits one IP packet embedded in a ESM DATA TRANSPORT and ULInformationTransfer-NB

–>

NAS: ESM DATA TRANSPORT

21Bb1

The SS waits for Timer_1 expiry

21C

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

22

SS adjusts MasterInformationBlock-NB/MasterInformationBlock-TDD-NB of Ncell 1 with ab-Enabled-r13/ab-Enabled-r15 set to TRUE and SystemInformationBlockType14-NB of Ncell 1

23

The SS notifies the UE of change of System Information

<–

Paging-NB

24

Wait for 2.1* modification period (Note 4) to allow the new system information to take effect.

25

Trigger the UE to initiate MO Exception Data

26

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 1 with establishmentCause-r13 set to mo-ExceptionData?

–>

RRCConnectionRequest-NB

4

P

27-29

Steps 2 to 4 of the ‘Generic Test Procedure NB-IoT Control Plan CIoT MO user data transfer non-SMS transport’ as described in TS 36.508 [18], clause 8.1.5A.3.3 are performed

NOTE: The UE will transmit one ESM DATA TRANSPORT message containing user data generated in step 25.

30

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

31

SS adjusts SystemInformationBlockType14-NB of Ncell 1 with ab-Category set to ‘a’

32

Trigger the UE to initiate MO Exception Data

33

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 1 within 30s?

–>

RRCConnectionRequest-NB

5

F

33A

‘Generic Test Procedure NB-IoT Control Plane CIoT MT user data transfer non-SMS transport’ as described in TS 36.508 [18], clause 8.1.5A.2.3 are performed (Note 3).

33AA

The SS starts timer Timer_1 = 10 s

EXCEPTION: Steps 33ABa1 to 33ABb1 describe a transaction that depends on the UE behaviour; the “lower case letter” identifies a test sequence that takes place if a specific behaviour happens (Note 3)

33ABa1

The UE transmits one IP packet embedded in a ESM DATA TRANSPORT and ULInformationTransfer-NB

–>

NAS: ESM DATA TRANSPORT

33ABb1

The SS waits for Timer_1 expiry

33B

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

34

SS adjusts SystemInformationBlockType14-NB of Ncell 1 with ab-BarringForExceptionData not present.

35

Trigger the UE to initiate MO Exception Data

36

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 1 with establishmentCause-r13 set to mo-ExceptionData?

–>

RRCConnectionRequest-NB

6

P

37-39

Steps 2 to 4 of the ‘Generic Test Procedure NB-IoT Control Plan CIoT MO user data transfer non-SMS transport’ as described in TS 36.508 [18], clause 8.1.5A.3.3 are performed

NOTE: The UE will transmit one ESM DATA TRANSPORT message containing user data generated in step 35.

40

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

41

SS adjusts SystemInformationBlockType14-NB of Ncell 1 with a special access class bitmap different from the special access class bitmap set in USIM and ab-BarringForExceptionData is set to true

42

Trigger the UE to initiate MO Exception Data

43

Check: Does the UE transmit an RRCConnectionRequest-NB message on Ncell 1 with establishmentCause-r13 set to mo-ExceptionData?

–>

RRCConnectionRequest-NB

7

P

44-46

Steps 2 to 4 of the ‘Generic Test Procedure NB-IoT Control Plan CIoT MO user data transfer non-SMS transport’ as described in TS 36.508 [18], clause 8.1.5A.3.3 are performed

NOTE: The UE will transmit one ESM DATA TRANSPORT message containing user data generated in step 42.

47

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

Note 1: A UE may send the pending data triggered at step 4.

Note 2: A UE may send the pending data triggered at step 18.

Note 3: A UE may send the pending data triggered at step 32.

Note 4: The wait time of 2.1* modification period is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 90ms of the start of modification period.

22.4.9.3.3 Specific message contents

Table 22.4.9.3.3-1: MasterInformationBlock-NB for Ncell 13 (Step 1, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.2-1

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-NB ::= SEQUENCE {

ab-Enabled-r13

TRUE

}

Table 22.4.9.3.3-1A: MasterInformationBlock-TDD-NB for Ncell 13 (Step 1, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.2-1A

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-TDD-NB-r15 ::= SEQUENCE {

ab-Enabled-r15

TRUE

}

Table 22.4.9.3.3-2: SystemInformationBlockType14-NB for Ncell 13 (Step 1, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

C

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

TRUE

ab-BarringForSpecialAC-r13

‘10001’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-3: Paging-NB for Ncell 13 (step 2, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.6.1-2

Information Element

Value/remark

Comment

Condition

Paging-NB ::= SEQUENCE {

pagingRecordList-r13

Not present

systemInfoModification-r13

True

Ncell 13

}

Table 22.4.9.3.3-4: RRCConnectionRequest-NB (Step 5, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}

Table 22.4.9.3.3-5: MasterInformationBlock-NB for Ncell 12 (Step 8, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.2-1

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-NB ::= SEQUENCE {

ab-Enabled-r13

TRUE

}

Table 22.4.9.3.3-5A: MasterInformationBlock-TDD-NB for Ncell 12 (Step 8, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.2-1A

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-TDD-NB-r15 ::= SEQUENCE {

ab-Enabled-r15

TRUE

}

Table 22.4.9.3.3-6: SystemInformationBlockType14-NB for Ncell 12 (Step 8, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

c

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

TRUE

ab-BarringForSpecialAC-r13

‘10001’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-7: Paging-NB for Ncell 12 (step 9, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.6.1-2

Information Element

Value/remark

Comment

Condition

Paging-NB ::= SEQUENCE {

pagingRecordList-r13

Not present

systemInfoModification-r13

True

Ncell 12

}

Table 22.4.9.3.3-8: RRCConnectionRequest-NB (Step 12, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}

Table 22.4.9.3.3-9: SystemInformationBlockType14-NB for Ncell 12 (Step 17, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

b

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

TRUE

ab-BarringForSpecialAC-r13

‘10001’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-10: RRCConnectionRequest-NB (Step 19, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}

Table 22.4.9.3.3-11: MasterInformationBlock-NB for Ncell 1 (Step 22, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.2-1

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-NB ::= SEQUENCE {

ab-Enabled-r13

TRUE

}

Table 22.4.9.3.3-11A: MasterInformationBlock-TDD-NB for Ncell 1 (Step 22, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.2-1A

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-TDD-NB-r15 ::= SEQUENCE {

ab-Enabled-r15

TRUE

}

Table 22.4.9.3.3-12: SystemInformationBlockType14-NB for Ncell 1 (Step 22, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

b

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

TRUE

ab-BarringForSpecialAC-r13

‘10001’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-13: Paging-NB for Ncell 1 (step 23, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.6.1-2

Information Element

Value/remark

Comment

Condition

Paging-NB ::= SEQUENCE {

pagingRecordList-r13

Not present

systemInfoModification-r13

True

Ncell 1

}

Table 22.4.9.3.3-14: RRCConnectionRequest-NB (Step 26, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}

Table 22.4.9.3.3-15: SystemInformationBlockType14-NB for Ncell 1 (Step 31, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

a

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

TRUE

ab-BarringForSpecialAC-r13

‘10001’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-16: RRCConnectionRequest-NB (Step 33, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}

Table 22.4.9.3.3-17: SystemInformationBlockType14-NB for Ncell 1 (Step 34, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

a

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

Not present

ab-BarringForSpecialAC-r13

‘10001’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-18: RRCConnectionRequest-NB (Step 36, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}

Table 22.4.9.3.3-19: SystemInformationBlockType14-NB for Ncell 1 (Step 41, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.4.3.3-5

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType14-NB-r13 ::= SEQUENCE {

ab-Param-r13 CHOICE {

ab-Common-r13 SEQUENCE {

ab-Category-r13

a

ab-BarringBitmap-r13

‘1000000000’

ab-BarringExceptionData-r13

TRUE

ab-BarringForSpecialAC-r13

‘10000’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.9.3.3-20: RRCConnectionRequest-NB (Step 43, Table 22.4.9.3.2-2)

Derivation Path: 36.508 Table 8.1.5A.3.4-1

Information Element

Value/remark

Comment

Condition

RRCConnectionRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionRequest-r13 SEQUENCE {

establishmentCause-r13

mo-ExceptionData

}

}

}