22.4.7 NB-IoT / RRC connection release with extendedWait / extendedWait ignored / RRC connection establishment / Reject with extendedWait

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

(1)

with { UE in RRC_Connected state }

ensure that {

when { UE receives an RRCConnectionRelease-NB message including an IE extendedWaitTime set to non-zero value }

then { UE does not send RRCConnectionRequest-NB before the extended wait timer is expired }

}

(2)

with { UE in RRC_IDLE state and has sent an RRCConnectionRequest-NB message }

ensure that {

when { UE receives an RRCConnectionReject-NB message including an IE extendedWaitTime set to non-zero value }

then { UE ignores the extended wait timer and sends RRCConnectionRequest-NB with cause moData }

}

22.4.7.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.3.8 and 5.3.8.3. Unless and otherwise stated these are Rel-13 requirements.

[TS 36.331, clause 5.3.3.8]

The UE shall:

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

1> if the extendedWaitTime is present and the UE supports delay tolerant access:

2> forward the extendedWaitTime to upper layers;

2> else:

3> inform upper layers about the failure to resume the RRC connection with suspend indication and that access barring for mobile originating calls, mobile originating signalling, mobile terminating access and except for NB-IoT for mobile originating CS fallback is applicable, upon which the procedure ends;

1> else

2> inform upper layers about the failure to establish the RRC connection and that access barring for mobile originating calls, mobile originating signalling, mobile terminating access and except for NB-IoT, for mobile originating CS fallback is applicable, upon which the procedure ends.

[TS 24.301, clause 5.3.1.2]

If the UE receives the "Extended wait time" from the lower layers when no attach, tracking area updating or service request procedure is ongoing, the UE shall ignore the "Extended wait time".

[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> 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> else:

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

22.4.7.3 Test description

22.4.7.3.1 Pre-test conditions

System Simulator:

– Ncell 1

– Cell power levels are selected according to [18] so that camping on Ncell 1 is guaranteed.

UE:

None.

Preamble:

– The UE is in state NB-IoT UE Attach, Connected Mode, UE Test Mode Activated (State 2B -NB) on Ncell 1 (serving cell) according to [18].

22.4.7.3.2 Test procedure sequence

Table 22.4.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U-S

Message

0

The SS transmits an RRCConnectionRelease-NB message

<-

RRCConnectionRelease-NB

0A

‘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

0B

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

<–

NAS: ESM DATA TRANSPORT

0C

Wait for 1 s after the IP packet has been transmitted in step 0B. (Note 1)

0D

Void.

1

The SS transmits an RRCConnectionRelease-NB message on Ncell 1 with IE extendedwaitTime set to 60s.

<–

RRCConnectionRelease-NB

2

Void

2A

Check: Does the UE ignore extendedwaitTime and transmit an RRCConnectionRequest-NB message on Ncell 1 within 60s (extendedwaitTime)?

–>

RRCConnectionRequest-NB

1

P

3

Void

3A

Void

3A1-3A3

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

3A5

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

Void

3B

‘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

3BA

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

3BB

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

3C

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

<–

NAS: ESM DATA TRANSPORT

3D

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

3E

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

3F

Void.

4

Void

5

UE transmits an RRCConnectionRequest-NB message.

–>

RRCConnectionRequest-NB

6

The SS responds with RRCConnectionReject-NB message with IE extendedwaitTime set to 60s.

<–

RRCConnectionReject-NB

6A

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

–>

RRCConnectionRequest-NB

2

F

6B

The SS starts timer Timer_1 = 8 s

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

6Ba1-6Ba4

Steps 1 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 3C.

5Ba5

The SS transmits an RRCConnectionRelease-NB message

<–

RRCConnectionRelease-NB

6Bb1

The SS waits for Timer_1 expiry

7-11

Void

12b1

Void

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

Table 22.4.7.3.2-2: Void

22.4.7.3.3 Specific message contents

Table 22.4.7.3.3-0A: CLOSE UE TEST LOOP (Preamble and step 3BA, Table 22.4.7.3.2-1)

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.7.3.3-1: RRCConnectionRelease-NB message (step 1, Table 22.4.7.3.2-1)

Derivation Path: 36.508 clause 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

other

extendedWaitTime-r13

60

60 seconds

}

}

}

}

Table 22.4.7.3.3-2: RRCConnectionReject-NB message (step 6, table 22.4.7.3.2-1)

Derivation Path: 36.508 clause 8.1.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReject-NB ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReject-r13 SEQUENCE {

extendedWaitTime-r13

60

60 seconds

}

}

}

}