22.4.27 NB-IoT / RRC connection establishment / Access barring enhancement

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

22.4.27.1 Test Purpose (TP)

(1)

with { UE in RRC_IDLE state having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB and SystemInformationBlockType14-NB with ab-PerNRSRP-r15 set to thresh1 is broadcast }

ensure that {

when { UE has user data pending and measured RSRP is greater than the first entry in rsrp-ThresholdsPrachInfoList }

then { UE transmits RRC Connection Request-NB message }

}

(2)

with { UE in RRC_IDLE state having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB and SystemInformationBlockType14-NB with ab-PerNRSRP-r15 set to thresh1 is broadcast }

ensure that {

when { UE has user data pending and measured RSRP is less than the first entry in rsrp-ThresholdsPrachInfoList }

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

}

(3)

with { UE in RRC_IDLE state having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB and SystemInformationBlockType14-NB with ab-PerNRSRP-r15 set to thresh2 is broadcast }

ensure that {

when { UE has user data pending and measured RSRP is greater than the second entry in rsrp-ThresholdsPrachInfoList }

then { UE transmits RRC Connection Request-NB message }

}

(4)

with { UE in RRC_IDLE state having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB and SystemInformationBlockType14-NB with ab-PerNRSRP-r15 set to thresh2 is broadcast }

ensure that {

when { UE has user data pending and measured RSRP is less than the second entry in rsrp-ThresholdsPrachInfoList }

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

}

(5)

with { UE in RRC_IDLE state having an Access Class with a value in the range 0..9 and with Access barring enabled in MasterInformationBlock-NB / MasterInformationBlock-TDD-NB and SystemInformationBlockType14-NB with present ab-PerNRSRP-r15 and absent ab-Param is broadcast }

ensure that {

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

then { UE transmits RRC Connection Request-NB message }

}

22.4.27.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.3.14.

[TS 36.331, clause 5.3.3.14]

The UE shall:

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

2> if ab-PerNRSRP is included:

3> if the establishmentCause received from higher layers is set to a value other than mo-ExceptionData; and

3> if the UE has no Access Class, 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]:

4> if ab-PerNRSRP is set to thresh1:

5> if the measured RSRP is less than the first entry in rsrp-ThresholdsPrachInfoList;

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first NPRACH repetition level are configured;

4> if ab-PerNRSRP is set to thresh2:

5> if the measured RSRP is less than the second entry in rsrp-ThresholdsPrachInfoList;

6> consider access to the cell as barred;

5> else:

6> consider that only the resources indicated for the first and second NPRACH repetition levels are configured;

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

…

1> else:

2> consider access to the cell as not barred;

22.4.27.3 Test description

22.4.27.3.1 Pre-test conditions

System Simulator:

– Ncell 1

– System information combination 4 as defined in TS 36.508[18] clause 8.1.4.3.1.1.

UE:

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

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 1 according to [18].

22.4.27.3.2 Test procedure sequence

Table 22.4.27.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.27.3.2-2.

Table 22.4.27.3.2-1: Cell configuration changes over time

Parameter

Unit

Ncell 1

Remark

T0

NRS EPRE

dBm/15kHz

-85

T1

NRS EPRE

dBm/15kHz

-70

T2

NRS EPRE

dBm/15kHz

-90

T3

NRS EPRE

dBm/15kHz

-110

Table 22.4.27.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 cell levels according to row T1 of table 22.4.27.3.2-1.

–

–

–

–

3

SS adjusts MasterInformationBlock-NB / MasterInformationBlock-TDD-NB of Ncell 1 with ab-Enabled set to TRUE.

–

–

–

–

4

The SS notifies the UE of change of System Information.

<–

Paging-NB

–

–

5

Wait for 2.1* modification period (Note 1) for UE to read updated MasterInformationBlock-NB / MasterInformationBlock-TDD-NB.

–

–

–

–

6

‘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

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

<–

NAS: ESM DATA TRANSPORT

–

–

8

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

–

–

–

–

9

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

10

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

–>

RRCConnectionRequest-NB

1

P

11-13

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 7.

–

–

–

14

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

–

–

15

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

–

–

16

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

<–

NAS: ESM DATA TRANSPORT

–

–

17

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

–

–

–

–

18

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

19

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

–

–

–

–

20

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

–>

RRCConnectionRequest-NB

2

F

21

SS adjusts SystemInformationBlockType14-NB with ab-PerNRSRP-r15 set to ‘thresh2’.

–

–

–

–

22

Wait for 1.28 seconds for UE to read updated SystemInformation (Note 3)

23

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

–

–

–

–

24

The SS starts timer Timer_1 = 8 s.

–

–

–

–

–

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

–

–

–

–

25a1

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

–>

NAS: ESM DATA TRANSPORT

–

–

25b1

The SS waits for Timer_1 expiry.

–

–

–

–

26

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

–

–

27

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

–

–

28

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

<–

NAS: ESM DATA TRANSPORT

–

–

29

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

–

–

–

–

30

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

31

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

–>

RRCConnectionRequest-NB

3

P

32-34

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 28.

–

–

–

35

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

–

–

36

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

–

–

37

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

<–

NAS: ESM DATA TRANSPORT

–

–

38

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

–

–

–

–

39

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

40

SS adjusts cell levels according to row T3 of table 22.4.27.3.2-1.

–

–

–

–

41

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

–>

RRCConnectionRequest-NB

4

F

42

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

–

–

–

–

43

The SS starts timer Timer_1 = 8 s.

–

–

–

–

–

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

–

–

–

–

44a1

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

–>

NAS: ESM DATA TRANSPORT

–

–

44b1

The SS waits for Timer_1 expiry.

–

–

–

–

45

The SS transmits an OPEN UE TEST LOOP message to exit the UE test loop mode.

<–

RRC: DLInformationTransfer-NB

TC: OPEN UE TEST LOOP

–

–

46

The UE transmits an OPEN UE TEST LOOP COMPLETE message.

–>

RRC: ULInformationTransfer-NB

TC: OPEN UE TEST LOOP COMPLETE

–

–

47

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

48

Trigger the UE to initiate MO Exception Data.

–

–

–

–

49

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

–>

RRCConnectionRequest-NB

5

P

50-52

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 48.

–

–

–

–

Note 1: The wait time of 2.1* modification period is to allow for the network to paging the system information change during the next modification period, and update the system information at the subsequent modification period.

Note 2: 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 3 The 1.28 second (twice SIB14-NB periodicity) delay is used to ensure that updated SIBs are transmitted.

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

Note 5: A UE may send the pending data sent at step 37.

22.4.27.3.3 Specific message contents

Table 22.4.27.3.3-1: RadioResourceConfigCommonSIB-NB-DEFAULT in SystemInformationBlockType2-NB (Preamble, Table 22.4.27.3.2-2)

Derivation Path: 36.508 Table 8.1.6.3-9

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSIB-NB-DEFAULT ::= SEQUENCE {

rach-ConfigCommon-r13

RACH-ConfigCommon-NB-DEFAULT

nprach-Config-r13

NPRACH-ConfigSIB-NB-DEFAULT

npusch-ConfigCommon-r13

NPUSCH-ConfigCommon-NB-DEFAULT

nprach-Config-v1530

NPRACH-ConfigSIB-NB-v1530-DEFAULT

TDD

nprach-Config-v1550

NPRACH-ConfigSIB-NB-v1550-DEFAULT

TDD

}

Table 22.4.27.3.3-2: NPRACH-ConfigSIB-NB-DEFAULT (Table 22.4.27.3.3-1)

Derivation Path: 36.508 Table 8.1.6.3-5

Information Element

Value/remark

Comment

Condition

NPRACH-ConfigSIB-NB-DEFAULT ::= SEQUENCE {

rsrp-ThresholdsPrachInfoList-r13 SEQUENCE (SIZE(1..2)) OF RSRP-Range {

2 entries

RSRP-Range[1]

60

-80 dBm

RSRP-Range[2]

40

-100 dBm

}

nprach-ParametersList-r13 SEQUENCE (SIZE (1.. maxNPRACH-Resources-NB-r13)) OF SEQUENCE {

3 entries

{

nprach-Periodicity-r13

ms640

nprach-StartTime-r13

ms8

nprach-SubcarrierOffset-r13

n12

nprach-NumSubcarriers-r13

n12

nprach-SubcarrierMSG3-RangeStart-r13

oneThird

maxNumPreambleAttemptCE-r13

n3

numRepetitionsPerPreambleAttempt-r13

n1

npdcch-NumRepetitions-RA-r13

r16

npdcch-StartSF-CSS-RA-r13

v4

npdcch-Offset-RA-r13

zero

}

{

nprach-Periodicity-r13

ms640

nprach-StartTime-r13

ms32

nprach-SubcarrierOffset-r13

n12

nprach-NumSubcarriers-r13

n12

nprach-SubcarrierMSG3-RangeStart-r13

oneThird

maxNumPreambleAttemptCE-r13

n3

numRepetitionsPerPreambleAttempt-r13

n2

npdcch-NumRepetitions-RA-r13

r16

npdcch-StartSF-CSS-RA-r13

v4

npdcch-Offset-RA-r13

zero

}

{

nprach-Periodicity-r13

ms640

nprach-StartTime-r13

ms128

nprach-SubcarrierOffset-r13

n12

nprach-NumSubcarriers-r13

n12

nprach-SubcarrierMSG3-RangeStart-r13

oneThird

maxNumPreambleAttemptCE-r13

n3

numRepetitionsPerPreambleAttempt-r13

n4

npdcch-NumRepetitions-RA-r13

r16

npdcch-StartSF-CSS-RA-r13

v4

npdcch-Offset-RA-r13

zero

}

}

}

Table 22.4.27.3.3-3: NPRACH-ConfigSIB-NB-v1530-DEFAULT (Table 22.4.27.3.3-1)

Derivation Path: 36.508 Table 8.1.6.3-17

Information Element

Value/remark

Comment

Condition

NPRACH-ConfigSIB-NB-v1530-DEFAULT ::= SEQUENCE {

TDD

tdd-Parameters-r15 SEQUENCE {

nprach-ParametersListTDD-r15 SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF SEQUENCE {

3 entries

{

nprach-Parameters-r15 SEQUENCE {

nprach-Periodicity-r15

ms640

nprach-StartTime-r15

ms10

nprach-SubcarrierOffset-r15

n12

nprach-NumSubcarriers-r15

n12

nprach-SubcarrierMSG3-RangeStart-r15

oneThird

npdcch-NumRepetitions-RA-r15

r16

npdcch-StartSF-CSS-RA-r15

v4

npdcch-Offset-RA-r15

zero

nprach-NumCBRA-StartSubcarriers-r15

n8

}

}

{

nprach-Parameters-r15 SEQUENCE {

nprach-Periodicity-r15

ms640

nprach-StartTime-r15

ms40

nprach-SubcarrierOffset-r15

n12

nprach-NumSubcarriers-r15

n12

nprach-SubcarrierMSG3-RangeStart-r15

oneThird

npdcch-NumRepetitions-RA-r15

r16

npdcch-StartSF-CSS-RA-r15

v4

npdcch-Offset-RA-r15

zero

nprach-NumCBRA-StartSubcarriers-r15

n8

}

}

{

nprach-Parameters-r15 SEQUENCE {

nprach-Periodicity-r15

ms640

nprach-StartTime-r15

ms160

nprach-SubcarrierOffset-r15

n12

nprach-NumSubcarriers-r15

n12

nprach-SubcarrierMSG3-RangeStart-r15

oneThird

npdcch-NumRepetitions-RA-r15

r16

npdcch-StartSF-CSS-RA-r15

v4

npdcch-Offset-RA-r15

zero

nprach-NumCBRA-StartSubcarriers-r15

n8

}

}

}

}

}

Table 22.4.27.3.3-4: NPRACH-ConfigSIB-NB-v1550-DEFAULT (Table 22.4.27.3.3-1)

Derivation Path: 36.508 Table 8.1.6.3-18

Information Element

Value/remark

Comment

Condition

NPRACH-ConfigSIB-NB-v1550-DEFAULT ::= SEQUENCE {

TDD

tdd-Parameters-v1550 SEQUENCE {

nprach-ParametersListTDD-v1550 SEQUENCE (SIZE (1..maxNPRACH-Resources-NB-r13)) OF SEQUENCE {

3 entries

{

maxNumPreambleAttemptCE-v1550

n3

numRepetitionsPerPreambleAttempt-v1550

n1

}

{

maxNumPreambleAttemptCE-v1550

n3

numRepetitionsPerPreambleAttempt-v1550

n2

}

{

maxNumPreambleAttemptCE-v1550

n3

numRepetitionsPerPreambleAttempt-v1550

n4

}

}

}

}

Table 22.4.27.3.3-5: RACH-ConfigCommon-NB-DEFAULT (Table 22.4.27.3.3-1)

Derivation Path: 36.508 Table 8.1.6.3-8

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-NB-DEFAULT ::= SEQUENCE {

preambleTransMax-CE-r13

n7

rach-InfoList-r13 (SIZE (1.. maxNPRACH-Resources-NB-r13)) OF SEQUENCE {

3 entries

{

ra-ResponseWindowSize-r13

pp10

mac-ContentionResolutionTimer-r13

pp8

}

{

ra-ResponseWindowSize-r13

pp10

mac-ContentionResolutionTimer-r13

pp8

}

{

ra-ResponseWindowSize-r13

pp10

mac-ContentionResolutionTimer-r13

pp8

}

}

}

Table 22.4.27.3.3-6: NPUSCH-ConfigCommon-NB-DEFAULT (Table 22.4.27.3.3-1)

Derivation Path: 36.508 Table 8.1.6.3-6

Information Element

Value/remark

Comment

Condition

NPUSCH-ConfigCommon-NB-DEFAULT ::= SEQUENCE {

ack-NACK-NumRepetitions-Msg4-r13 (SIZE (1.. maxNPRACH-Resources-NB-r13)) OF SEQUENCE {

3 entries

ACK-NACK-NumRepetitions-NB-r13

r8

ACK-NACK-NumRepetitions-NB-r13

r8

ACK-NACK-NumRepetitions-NB-r13

r8

}

Table 22.4.27.3.3-7: SystemInformationBlockType14-NB (Preamble, Table 22.4.27.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

Not present

lateNonCriticalExtension

Not present

ab-PerNRSRP-r15

thresh1

}

Table 22.4.27.3.3-8: CLOSE UE TEST LOOP (Preamble, steps 14/26/35 Table 22.4.27.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.27.3.3-9: MasterInformationBlock-NB (Step 3, Table 22.4.27.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.27.3.3-10: MasterInformationBlock-TDD-NB (Step 3, Table 22.4.27.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.27.3.3-11: Paging-NB (step 4, Table 22.4.27.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

}

Table 22.4.27.3.3-12: RRCConnectionRequest-NB (Steps 10/20/31/41, Table 22.4.27.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.27.3.3-13: SystemInformationBlockType14-NB (Step 21, Table 22.4.27.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

Not present

lateNonCriticalExtension

Not present

ab-PerNRSRP-r15

thresh2

}

Table 22.4.27.3.3-14: RRCConnectionRequest-NB (Step 49, Table 22.4.27.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

}

}

}