22.4.23 NB-IoT / Radio link failure / T310 expiry / Dedicated RLF timer (CP CIoT)

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

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives an RRCConnectionSetup-NB message containing an rlf-TimersAndConstants-r13 set to setup }

then { UE uses timer value received in the RRCConnectionSetup-NB message }

}

(2)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives an RRCConnectionSetup-NB message without IE rlf-TimersAndConstants-r13 }

then { UE uses timer value received in SystemInformationBlockType2-NB }

}

22.4.23.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.2.2.9, 5.3.10.0, 5.3.10.7 and 5.3.11.3.

[TS 36.331 clause 5.2.2.9]

Upon receiving SystemInformationBlockType2-NB, the UE shall:

1> apply the configuration included in the radioResourceConfigCommon;

1> apply the defaultPagingCycle included in the radioResourceConfigCommon;

1> apply the specified PCCH configuration defined in 9.1.1.3.

[TS 36.331 clause 5.3.10.0]

The UE shall:

1> if the received radioResourceConfigDedicated includes the rlf-TimersAndConstants:

2> reconfigure the values of timers and constants as specified in 5.3.10.7;

[TS 36.331 clause 5.3.10.7]

The UE shall:

1> if the received rlf-TimersAndConstants is set to release:

2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SystemInformationBlockType2 (or SystemInformationBlockType2-NB in NB-IoT);

1> else:

2> reconfigure the value of timers and constants in accordance with received rlf-TimersAndConstants;

[TS 36.331 clause 5.3.11.3]

The UE shall:

1> upon T310 expiry; or

2> consider radio link failure to be detected for the MCG i.e. RLF;

2> if AS security has not been activated:

3> if the UE is a NB-IoT UE:

4> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

[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, T322, T325, T330;

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

1> else:

2> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

2> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was triggered neither by reception of the MobilityFromEUTRACommand message nor by selecting an inter-RAT cell while T311 was running:

2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4, 5.2.7];

22.4.23.3 Test description

22.4.23.3.1 Pre-test conditions

System Simulator:

– Ncell 1.

UE:

None.

Preamble:

– The UE is in registered Idle Mode (State 3-NB) on Ncell 1 according to Table 8.1.5.3.3 [18]

22.4.23.3.2 Test procedure sequence

Table 22.4.23.3.2-1 illustrates the downlink power levels to be applied for the cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Ncell 1

Remark

T1

Cell-specific NRS EPRE

dBm/15kHz

”Off”

No Ncells are available.

(NOTE 1).

T2

Cell-specific NRS EPRE

dBm/15kHz

-85

Only Ncell 1 is available.

(NOTE 1).

NOTE 1: Power level “Off” is ≤ -150 dBm

Table 22.4.23.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The generic test procedure in TS 36.508 subclause 8.1.5A.2.3 is performed on Ncell 1.

1A

The SS changes Ncell 1 levels according to row "T1" in Table 22.4.23.3.2-1 in order that UE considers the radio link of Ncell 1 is out-of-sync.

1B

Wait for 5s.

1C

The SS changes Ncell 1 levels according to row "T2" in Table 22.4.23.3.2-1 in order that UE considers the radio link of Ncell 1 is in-sync.

1D

The SS transmits a UECapabilityEnquiry-NB message to request UE radio access capability information.

<–

UECapabilityEnquiry-NB

1E

Check: Does the UE transmit a UECapabilityInformation-NB message?

–>

UECapabilityInformation-NB

1

P

1F

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

1G

‘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

2

Void

3-7

Void

8

The SS changes Ncell1 power levels according to row "T1" in Table 22.4.23.3.2-1.

8A

Wait for 3s.

8B

The SS changes Ncell1 power levels according to row "T2" in Table 22.4.23.3.2-1.

8C

Wait for 30s to ensure UE enters RRC_IDLE.

9-13

‘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

2

P

14

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

22.4.23.3.3 Specific message contents

Table 22.4.23.3.3-1: SystemInformationBlockType2-NB for Ncell 1 (all steps, Table 22.4.23.3.2-2)

Derivation Path: 36.508, Table 8.1.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2-NB-r13 ::= SEQUENCE {

ue-TimersAndConstants-r13 SEQUENCE {

t310-r13

ms1000

n310-r13

n1

}

}

Table 22.4.23.3.3-2: RRCConnectionSetup-NB (step 1, Table 22.4.23.3.2-2)

Derivation Path: 36.508 Table 8.1.6.1-14

Information Element

Value/remark

Comment

Condition

RRCConnectionSetup-NB ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionSetup-r13 SEQUENCE {

radioResourceConfigDedicated-r13 SEQUENCE {

rlf-TimersAndConstants-r13 CHOICE {

setup SEQUENCE {

t301-r13

ms10000

t310-r13

ms8000

n310-r13

n1

t311-r13

ms1000

n311-r13

n1

}

}

}

}

}

}

}

Table 22.4.23.3.3-3: Void