22.4.4 NB-IoT / RRC connection establishment / Paging / Access Barring for UE with AC 0 to 9 / 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.4.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE has user data pending }

then { UE does not transmit RRC Connection Request-NB message }

}

(2)

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

ensure that {

when { UE has user data pending }

then { UE transmits RRC Connection Request-NB message }

}

(3)

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

ensure that {

when { UE has user data pending }

then { UE does not transmit RRC Connection Request-NB message }

}

(4)

with { UE in RRC_IDLE state on HPLMN having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB and broadcasts SystemInformationBlockType14-NB and ab-Category set to b }

ensure that {

when { UE has user data pending }

then { UE transmits RRC Connection Request-NB message }

}

(5)

with { UE in RRC_IDLE state on HPLMN having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB and broadcasts SystemInformationBlockType14-NB and ab-Category set to a }

ensure that {

when { UE has user data pending }

then { UE does not transmit RRC Connection Request-NB message }

}

(6)

with { Access to the cell barred for mo-data because UE belongs to ab-Category ‘c’ and having an Access Class with a value in the range 0..9 }

ensure that {

when { UE receives paging }

then { UE transmits RRC Connection Request-NB message }

}

(7)

with { Access to the cell barred for mo-data because UE belongs to ab-Category ‘b’ and having an Access Class with a value in the range 0..9 }

ensure that {

when { UE receives paging }

then { UE transmits RRC Connection Request-NB message }

}

(8)

with { Access to the cell barred for mo-data because UE belongs to ab-Category ‘a’ and having an Access Class with a value in the range 0..9 }

ensure that {

when { UE receives paging }

then { UE transmits RRC Connection Request-NB message }

}

22.4.4.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clause 5.3.3.14, 5.2.2.4.

[TS 36.331, clause 5.2.2.4]

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

2> not initiate the RRC connection establishment/resume procedure for all access causes except mobile terminating calls until the UE has acquired the SystemInformationBlockType14NB;

[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.4.3 Test description

22.4.4.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.4.3.1–1.

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

Table 22.4.4.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.4.3.1–2.

Table 22.4.4.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 “A” as defined in TS 34.108 clause 8.3.2.15

– The UE belong to access class 0

Preamble:

– The UE is in state NB-IoT UE Attach, Connected Mode, UE Test Loopback Activated (State 2B-NB) with test loop mode G on Ncell 13 according to [18]

22.4.4.3.2 Test procedure sequence

Table 22.4.4.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.4.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.4.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.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

2

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 with ab-Category set to ‘c’

3

The SS notifies the UE of change of System Information

<–

Paging-NB

4

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

5

‘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

6

P

6

The SS transmits one IP packet to the UE embedded in a ESM DATA TRANSPORT and DLInformationTransfer-NB

<–

NAS: ESM DATA TRANSPORT

7

Wait for 1 s after the IP packet has been transmitted. (Note 1)

8

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

9

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

–>

RRCConnectionRequest-NB

1

F

10

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

11

Steps 1 to 5 of Generic test procedure in TS 36.508 subclause 8.1.5A.5 takes place on Ncell 12.

NOTE: The UE performs a TAU procedure

12

The SS starts timer Timer_1 = 8 s

EXCEPTION: Steps 13a1 to 13b1 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)

13a1

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

–>

NAS: ESM DATA TRANSPORT

13b1

The SS waits for Timer_1 expiry

14

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

15

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 with ab-Category set to ‘c’

16

The SS notifies the UE of change of System Information

<–

Paging-NB

17

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

18

‘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

18A

The SS transmits a CLOSE UE TEST LOOP message to close the UE test loop mode for user data transfer (15 sec delay).

<–

RRC: DLInformationTransfer-NB

TC: CLOSE UE TEST LOOP

18B

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback is activated.

–>

RRC: ULInformationTransfer-NB

TC: CLOSE UE TEST LOOP COMPLETE

19

The SS transmits one IP packet to the UE embedded in a ESM DATA TRANSPORT and DLInformationTransfer-NB

<–

NAS: ESM DATA TRANSPORT

20

Wait for 1 s after the IP packet has been transmitted. (Note 1)

21

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

22

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

–>

RRCConnectionRequest-NB

2

P

23-25

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 loopback data received in step 19.

26

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

27

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

27A

Wait for 1.28 seconds (Note 5) to allow the new system information to take effect.

28

‘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

7

P

28A

The SS transmits a CLOSE UE TEST LOOP message to close the UE test loop mode for user data transfer (15 sec delay).

<–

RRC: DLInformationTransfer-NB

TC: CLOSE UE TEST LOOP

28B

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback is activated.

–>

RRC: ULInformationTransfer-NB

TC: CLOSE UE TEST LOOP COMPLETE

29

The SS transmits one IP packet to the UE embedded in a ESM DATA TRANSPORT and DLInformationTransfer-NB

<–

NAS: ESM DATA TRANSPORT

30

Wait for 1 s after the IP packet has been transmitted. (Note 1)

31

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

32

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

–>

RRCConnectionRequest-NB

3

F

33

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

34

Steps 1 to 5 of Generic test procedure in TS 36.508 subclause 8.1.5A.5 to takes place on Ncell 1.

NOTE: The UE performs a TAU procedure.

35

The SS starts timer Timer_1 = 8 s

EXCEPTION: Steps 36a1 to 36b1 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)

36a1

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

–>

NAS: ESM DATA TRANSPORT

36b1

The SS waits for Timer_1 expiry

37

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

38

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 with ab-Category set to ‘b’

39

The SS notifies the UE of change of System Information

<–

Paging-NB

40

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

41

‘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

41A

The SS transmits a CLOSE UE TEST LOOP message to close the UE test loop mode for user data transfer (15 sec delay).

<–

RRC: DLInformationTransfer-NB

TC: CLOSE UE TEST LOOP

41B

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback is activated.

–>

RRC: ULInformationTransfer-NB

TC: CLOSE UE TEST LOOP COMPLETE

42

The SS transmits one IP packet to the UE embedded in a ESM DATA TRANSPORT and DLInformationTransfer-NB

<–

NAS: ESM DATA TRANSPORT

43

Wait for 1 s after the IP packet has been transmitted. (Note 1)

44

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

45

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

–>

RRCConnectionRequest-NB

4

P

46-48

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 loopback data received in step 43.

49

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

50

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

50A

Wait for 1.28 seconds (Note 5) to allow the new system information to take effect.

51

‘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

8

P

51A

The SS transmits a CLOSE UE TEST LOOP message to close the UE test loop mode for user data transfer (15 sec delay).

<–

RRC: DLInformationTransfer-NB

TC: CLOSE UE TEST LOOP

51B

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback is activated.

–>

RRC: ULInformationTransfer-NB

TC: CLOSE UE TEST LOOP COMPLETE

52

The SS transmits one IP packet to the UE embedded in a ESM DATA TRANSPORT and DLInformationTransfer-NB

<–

NAS: ESM DATA TRANSPORT

53

Wait for 1 s after the IP packet has been transmitted. (Note 1)

54

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

55

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

–>

RRCConnectionRequest-NB

5

F

56

‘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 4)

56A

The SS starts timer Timer_1 = 8 s

EXCEPTION: Steps 56Ba1 to 56Bb1 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 4)

56Ba1

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

–>

NAS: ESM DATA TRANSPORT

56Bb1

The SS waits for Timer_1 expiry

57

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

Note 1: The 1 second delay is used to secure that the UE have received and forwarded the IP Packet transmitted by the SS to the UE test loop function before the RRCConnectionRelease-NB message is sent by the SS.

Note 2: A UE may send the pending data sent at step 6

Note 3: A UE may send the pending data sent at step 29

Note 4: A UE may send the pending data sent at step 52

Note 5: The 1.28 seconds (2* SIB14 schedule periodicity) delay is used to ensure that updated SIB 14 is transmitted.

Note 6: 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.4.3.3 Specific message contents

Table 22.4.4.3.3-1: CLOSE UE TEST LOOP (Preamble and steps 18A/28A/41A/51A, Table 22.4.4.3.2-2)

Derivation path: 36.508 Table 8.1.5.2B

Information Element

Value/Remark

Comment

Condition

UE test loop mode

‘00000110’B

UE test loop mode G setup

TL_MODE_G

Operation mode and repetitions

M0

0

return_via_EMM_SMC

R6..R0

‘0000001’B

1

The received DL message in uplink shall be looped back 1 time (once)

Uplink data delay

‘00001111’B

T_delay_modeGH timer = 15 sec

Table 22.4.4.3.3-2: MasterInformationBlock-NB for Ncell 13 (Step 2, Table 22.4.4.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.4.3.3-2A: MasterInformationBlock-TDD-NB for Ncell 13 (Step 2, Table 22.4.4.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.4.3.3-3: SystemInformationBlockType14-NB for Ncell 13 (Step 2, Table 22.4.4.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

FALSE

ab-BarringForSpecialAC-r13

‘00000’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.4.3.3-4: Paging-NB for Ncell 13 (step 3, Table 22.4.4.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.4.3.3-5: RRCConnectionRequest-NB (Step 9, Table 22.4.4.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-data

}

}

}

Table 22.4.4.3.3-6: MasterInformationBlock-NB for Ncell 12 (Step 12, Table 22.4.4.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.4.3.3-6A: MasterInformationBlock-TDD-NB for Ncell 12 (Step 12, Table 22.4.4.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.4.3.3-7: SystemInformationBlockType14-NB for Ncell 12 (Step 15, Table 22.4.4.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

FALSE

ab-BarringForSpecialAC-r13

‘00000’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.4.3.3-8: Paging-NB for Ncell 12 (step 16, Table 22.4.4.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.4.3.3-9: RRCConnectionRequest-NB (Step 22, Table 22.4.4.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-data

}

}

}

Table 22.4.4.3.3-10: SystemInformationBlockType14-NB for Ncell 12 (Step 27, Table 22.4.4.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

FALSE

ab-BarringForSpecialAC-r13

‘00000’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.4.3.3-11: MasterInformationBlock-NB for Ncell 1 (Step 38, Table 22.4.4.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.4.3.3-11A: MasterInformationBlock-TDD-NB for Ncell 1 (Step 38, Table 22.4.4.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.4.3.3-12: SystemInformationBlockType14-NB for Ncell 1 (Step 38, Table 22.4.4.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

FALSE

ab-BarringForSpecialAC-r13

‘00000’

}

}

lateNonCriticalExtension

Not present

}

Table 22.4.4.3.3-13: Paging-NB for Ncell 1 (step 39, Table 22.4.4.3.2-2)

Derivation Path: 36.508 clause 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.4.3.3-14: RRCConnectionRequest-NB (Step 45, Table 22.4.4.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-data

}

}

}

Table 22.4.4.3.3-15: SystemInformationBlockType14-NB for Ncell 1 (Step 50, Table 22.4.4.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

FALSE

ab-BarringForSpecialAC-r13

‘00000’

}

}

lateNonCriticalExtension

Not present

}