22.4.15 NB-IoT / RRC connection suspend-resume / Success / different cell

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.15.1 Test Purpose (TP)

(1)

with { NB-IoT UE in switched off state }

ensure that {

when { NB-IoT UE has established User Plane (UP) bearer and a RRCConnectionRelease-NB message is received with resumeIdentity and rrc-Suspend }

then { NB-IoT UE suspends RRC Connection and stores the resumeIdentity and AS security context }

}

(2)

with { NB-IoT UE in RRC_IDLE state }

ensure that {

when { NB-IoT UE receives a Paging-NB message }

then { NBIOT UE transmits RRCConnectionResumeRequest-NB message including the stored resumeIdentity and AS security context to resume RRC Connection }

}

(3)

with { NB-IoT UE in RRC_CONNECTED state }

ensure that {

when { NB-IoT UE has established User Plane (UP) bearer and a RRCConnectionRelease-NB message is received with a new resumeIdentity and rrc-Suspend }

then { NB-IoT UE suspends RRC Connection and stores the new resumeIdentity and AS security context }

}

(4)

with { NB-IoT UE in RRC_IDLE state }

ensure that {

when { NB-IoT UE detects the cell re-selection criteria are met for the new Ncell and reselects to the new Ncell }

then { NB-IoT UE transmits RRCConnectionResumeRequest-NB message including the stored new resumeIdentity and AS security context to resume RRC Connection on the new Ncell }

}

22.4.15.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.3.3a, 5.3.8.3, and 5.3.12.

[TS 36.331, clause 5.3.3.3a]

The UE shall set the contents of RRCConnectionResumeRequest message as follows:

1> if the UE is a NB-IoT UE; or

1> if field useFullResumeID is signalled in SystemInformationBlockType2:

2> set the resumeID to the stored resumeIdentity;

1> else

2> set the truncatedResumeID to include bits in bit position 9 to 20 and 29 to 40 from the left in the stored resumeIdentity.

  1. if the UE supports mo-VoiceCall establishment cause and UE is resuming the RRC connection for mobile originating MMTEL voice and SystemInformationBlockType2 includes voiceServiceCauseIndication:

2> set the resumeCause to mo-VoiceCall;

1> else

2> set the resumeCause in accordance with the information received from upper layers;

1> set the shortResumeMAC-I to the 16 least significant bits of the MAC-I calculated:

2> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortResumeMAC-Input (or VarShortResumeMAC-Input-NB in NB-IoT);

2> with the KRRCint key and the previously configured integrity protection algorithm; and

2> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

The UE shall submit the RRCConnectionResumeRequest message to lower layers for transmission.

The UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.5.

[TS 36.331, clause 5.3.8.3]

The UE shall:

1> delay the following actions defined in this sub-clause 60 ms from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;

1> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:

2> store the cell reselection priority information provided by the idleModeMobilityControlInfo;

2> if the t320 is included:

3> start timer T320, with the timer value set according to the value of t320;

1> else:

2> apply the cell reselection priority information broadcast in the system information;

1> if the releaseCause received in the RRCConnectionRelease message indicates loadBalancingTAURequired:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘load balancing TAU required’;

1> else if the releaseCause received in the RRCConnectionRelease message indicates cs-FallbackHighPriority:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘CS Fallback High Priority’;

1> else:

2> if the extendedWaitTime is present; and

2> if the UE supports delay tolerant access or the UE is a NB-IoT UE:

3> forward the extendedWaitTime to upper layers;

2> if the releaseCause received in the RRCConnectionRelease message indicates rrc-Suspend:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC suspension’;

2> else:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

[TS 36.331, clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320, T325 and T330;

1> if leaving RRC_CONNECTED was triggered by suspension of the RRC:

2> re-establish RLC entities for all SRBs and DRBs;

2> store the UE AS Context including the current RRC configuration, the current security context, the PDCP state including ROHC state, C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell;

2> store the following information provided by E-UTRAN:

3> the resumeIdentity;

2> suspend all SRB(s) and DRB(s);

2> indicate the suspension of the RRC connection to upper layers;

22.4.15.3 Test description

22.4.15.3.1 Pre-test conditions

System Simulator:

– Ncell 1 and Ncell 11.

– The Network and test case requires Attach with User Plane CIoT EPS optimisation.

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

UE:

User Plane CIoT Optimisation is supported by UE (UE capability), pc_User_Plane_CIoT_Optimisation.

Preamble:

– The UE is in state Switched OFF (State 1-NB) according to TS 36.508 Table 8.1.5.1-1.

22.4.15.3.2 Test procedure sequence

Table 22.4.15.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. The configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 22.4.15.3.2-2.

Table 22.4.15.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Ncell 1

Ncell 11

Remark

T0

Cell-specific NRS EPRE

dBm/15kHz

-85

"Off"

T1

Cell-specific NRS EPRE

dBm/15kHz

-85

-73

Ncell 11 becomes stronger than Threshx, high.

Table 22.4.15.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Steps 1-14b1 of the generic procedure for UE registration specified in TS 36.508 subclause 8.1.5.2.3 are performed on Ncell1.

–

–

–

–

2

The SS transmits an RRCConnectionRelease-NB message including resumeIdentity and rrc-Suspend as releaseCause.

<–

RRC: RRCConnectionRelease-NB

–

–

3

The SS transmits a Paging-NB message including a matched identity.

<–

RRC: Paging-NB

–

–

4

Check: Does the UE transmit an RRCConnectionResumeRequest-NB message including the resumeIdentity and AS security context stored at Step 2?

–>

RRC: RRCConnectionResumeRequest-NB

1, 2

P

5

The SS transmits an RRCConnectionResume-NB message.

<–

RRC: RRCConnectionResume-NB

–

–

6

The UE transmits an RRCConnectionResumeComplete-NB message.

–>

RRC: RRCConnectionResumeComplete-NB

–

–

7

The SS transmits an RRCConnectionRelease-NB message including a new resumeIdentity and rrc-Suspend as releaseCause.

<–

RRCConnectionRelease-NB

–

–

8

The SS changes Ncell 11 power level according to the row "T1" in table 22.4.15.3.2-1.

–

–

–

–

9

Check: Does the test result of generic test procedure in TS 36.508 subclause 8.1.5A.6 indicate that the UE successfully resumes RRC connection on Ncell 11 using the new resumeIdentity and AS security context stored at Step 7?

–

–

3, 4

P

22.4.15.3.3 Specific message contents

Table 22.4.15.3.3-1: RRCConnectionRelease-NB (step 2, table 22.4.15.3.2-2)

Derivation Path: 36.508 table 8.1.6.1-9

Information Element

Value/remark

Comment

Condition

RRCConnectionRelease-NB ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionRelease-r13 SEQUENCE {

releaseCause-r13

rrc-Suspend

resumeIdentity-r13

BIT STRING (SIZE(40))

Any value

extendedWaitTime-r13

Not present

redirectedCarrierInfo

Not present

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 22.4.15.3.3-2: RRCConnectionResumeRequest-NB (step 4, Table 22.4.15.3.2-2)

Derivation Path: 36.508 table 8.1.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionResumeRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionResumeRequest-r13 SEQUENCE {

resumeID-r13

BIT STRING (SIZE(40))

Same value as Step 2

resumeMAC-I-r13

The same value as the 16 least significant bits of the MAC-I value

calculated by SS.

resumeCause-r13

mt-Access

spare

Present but contents not checked

}

}

}

Table 22.4.15.3.3-3: RRCConnectionResumeComplete-NB (step 6, Table 22.4.15.3.2-2)

Derivation Path: 36.508 table 8.1.6.1-12

Information Element

Value/remark

Comment

Condition

RRCConnectionResumeComplete-NB ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-UL

criticalExtensions CHOICE {

rrcConnectionResumeComplete-r13 SEQUENCE {

selectedPLMN-Identity-r13

Not checked

dedicatedInfoNAS-r13

Not Present

lateNonCriticalExtension

Not checked

nonCriticalExtension SEQUENCE {}

Not checked

}

}

}

Table 22.4.15.3.3-4: RRCConnectionRelease-NB (step 7, table 22.4.15.3.2-2)

Derivation Path: 36.508 table 8.1.6.1-9

Information Element

Value/remark

Comment

Condition

RRCConnectionRelease-NB ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionRelease-r13 SEQUENCE {

releaseCause-r13

rrc-Suspend

resumeIdentity-r13

BIT STRING (SIZE(40))

New value (other than the value used in Step 2)

extendedWaitTime-r13

Not present

redirectedCarrierInfo

Not present

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 22.4.15.3.3-5: RRCConnectionResumeRequest-NB (step 9, Table 22.4.15.3.2-2)

Derivation Path: 36.508 table 8.1.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionResumeRequest-NB ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionResumeRequest-r13 SEQUENCE {

resumeID-r13

BIT STRING (SIZE(40))

Same value as Step 7

resumeMAC-I-r13

The same value as the 16 least significant bits of the MAC-I value

calculated by SS.

resumeCause-r13

mo-Signalling

spare

Present but contents not checked

}

}

}