22.4.24 NB-IoT / RRC / Paging for connection in idle mode / Non-anchor carrier

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

(1)

with { UE in RRC_IDLE state in a cell which has broadcasted SystemInformationBlockType22-NB message including radio resource configuration for paging on non-anchor carrier and pagingWeightAnchor-r14 is not present}

ensure that {
when { SS sends a Paging-NB message on UE’s paging non-anchor carrier}

then { UE successfully establishes the RRC connection }

}

(2)

with { UE in RRC_IDLE state in a cell which has broadcasted SystemInformationBlockType22-NB message including radio resource configuration for paging on non-anchor carrier and pagingWeightAnchor-r14 is not present }

ensure that {
when { SS sends a Paging-NB message on anchor carrier }

then { UE does not establish any RRC connection }

}

22.4.24.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.2.2.3, TS 36.304, clauses 7.1

[TS 36.331, clause 5.2.2.3]

The UE shall:

1> ensure having a valid version, as defined below, of (at least) the following system information, also referred to as the ‘required’ system information:

2> if in RRC_IDLE:

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

4> the MasterInformationBlock-NB and SystemInformationBlockType1-NB as well as SystemInformationBlockType2-NB through SystemInformationBlockType5-NB, SystemInformationBlockType22-NB;

3> else:

4> the MasterInformationBlock and SystemInformationBlockType1 (or SystemInformationBlockType1-BR depending on whether the UE is a BL UE or the UE in CE) as well as SystemInformationBlockType2 through SystemInformationBlockType8 (depending on support of the concerned RATs), SystemInformationBlockType17 (depending on support of RAN-assisted WLAN interworking);

2> if in RRC_CONNECTED; and

2> the UE is not a BL UE; and

2> the UE is not in CE; and

2> the UE is not a NB-IoT UE:

3> the MasterInformationBlock, SystemInformationBlockType1 and SystemInformationBlockType2 as well as SystemInformationBlockType8 (depending on support of CDMA2000), SystemInformationBlockType17 (depending on support of RAN-assisted WLAN interworking);

2> if in RRC_CONNECTED and T311 is running; and

2> the UE is a BL UE or the UE is in CE or the UE is a NB-IoT UE;

3> the MasterInformationBlock (or MasterInformationBlock-NB in NB-IoT), SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) and SystemInformationBlockType2 (or SystemInformationBlockType2-NB in NB-IoT), and for NB-IoT SystemInformationBlockType22-NB;

1> delete any stored system information after 3 hours or 24 hours from the moment it was confirmed to be valid as defined in 5.2.1.3, unless specified otherwise;

1> consider any stored system information except SystemInformationBlockType10, SystemInformationBlockType11, systemInformationBlockType12 and systemInformationBlockType14 (systemInformationBlockType14-NB in NB-IoT) to be invalid if systemInfoValueTag included in the SystemInformationBlockType1 (MasterInformationBlock-NB in NB-IoT) is different from the one of the stored system information and in case of NB-IoT UEs, BL UEs and UEs in CE, systemInfoValueTagSI is not broadcasted. Otherwise consider system information validity as defined in 5.2.1.3;

[TS 36.304, clause 7.1]

One Paging Narrowband (PNB) is one narrowband, on which the UE performs the paging message reception.

PF, PO, and PNB are determined by following formulae using the DRX parameters provided in System Information:

PF is given by following equation:

SFN mod T= (T div N)*(UE_ID mod N)

Index i_s pointing to PO from subframe pattern defined in 7.2 will be derived from following calculation:

i_s = floor(UE_ID/N) mod Ns

If P-RNTI is monitored on MPDCCH, the PNB is determined by the following equation:

PNB = floor(UE_ID/(N*Ns)) mod Nn

If P-RNTI is monitored on NPDCCH and the UE supports paging on a non-anchor carrier, and if paging configuration for non-anchor carrier is provided in system information, then the paging carrier is determined by the paging carrier with smallest index n (0 ≤ n ≤ Nn-1) fulfilling the following equation:

floor(UE_ID/(N*Ns)) mod W < W(0) + W(1) + … + W(n)

System Information DRX parameters stored in the UE shall be updated locally in the UE whenever the DRX parameter values are changed in SI. If the UE has no IMSI, for instance when making an emergency call without USIM, the UE shall use as default identity UE_ID = 0 in the PF, i_s, and PNB formulas above.

The following Parameters are used for the calculation of the PF, i_s, PNB, and the NB-IoT paging carrier:

– T: DRX cycle of the UE. Except for NB-IoT, if a UE specific extended DRX value of 512 radio frames is configured by upper layers according to 7.3, T =512. Otherwise, T is determined by the shortest of the UE specific DRX value, if allocated by upper layers, and a default DRX value broadcast in system information. If UE specific DRX is not configured by upper layers, the default value is applied. UE specific DRX is not applicable for NB-IoT.

– nB: 4T, 2T, T, T/2, T/4, T/8, T/16, T/32, T/64, T/128, and T/256, and for NB-IoT also T/512, and T/1024.

– N: min(T,nB)

– Ns: max(1,nB/T)

– Nn : number of paging narrowbands (for P-RNTI monitored on MPDCCH) or paging carriers (for P-RNTI monitored on NPDCCH) provided in system information

– UE_ID:

IMSI mod 1024, if P-RNTI is monitored on PDCCH.

IMSI mod 4096, if P-RNTI is monitored on NPDCCH.

IMSI mod 16384, if P-RNTI is monitored on MPDCCH or if P-RNTI is monitored on NPDCCH and the UE supports paging on a non-anchor carrier, and if paging configuration for non-anchor carrier is provided in system information.

– W(i): Weight for NB-IoT paging carrier i.

– W: Total weight of all NB-IoT paging carriers, i.e. W = W(0) + W(1) + … + W(Nn-1).

22.4.24.3 Test description

22.4.24.3.1 Pre-test conditions

System Simulator:

– Ncell 1

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

SystemInformationBlockType22-NB as specified in Table 22.4.24.3.3-1.

UE:

None.

Preamble:

– The UE is in state Registered, Idle mode (State 3-NB) according to [18].

22.4.24.3.2 Test procedure sequence

Table 22.4.24.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a Paging-NB message including a matched identity on non-anchor carrier

<–

Paging-NB

2-5

Check: Does the test result of steps 2 to 5 of generic test procedure in TS 36.508 subclause 8.1.5A.2 indicate that the UE successfully responds to Paging for control plane CIoT MT access?

1

P

6

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

7

The SS transmits a Paging-NB message including a matched identity on the anchor carrier

<–

Paging-NB

8

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

–>

RRCConnectionRequest-NB

2

F

22.4.24.3.3 Specific message contents

Table 22.4.24.3.3-1: SystemInformationBlockType22-NB (preamble)

Derivation Path: 36.508 Table 8.1.4.3.3-8

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType22-NB-r14 ::= SEQUENCE {

dl-ConfigList-r14 SEQUENCE (SIZE (1.. maxNonAnchorCarriers-NB-r14)) OF DL-ConfigCommon-NB-r14 SEQUENCE {

1 entry

DL-ConfigCommon-NB-r14[1] SEQUENCE {

dl-CarrierConfig-r14

DL-CarrierConfigCommon-NB-DEFAULT1

pcch-Config-r14 SEQUENCE {

npdcch-NumRepetitionPaging-r14

Not present

pagingWeight-r14

w1

}

}

}

ul-ConfigList-r14

Not Present

}

Table 22.4.24.3.3-2: DL-CarrierConfigCommon-NB-DEFAULT1

Derivation Path: 36.508 clause 8.1.6.3-1A

Information Element

Value/remark

Comment

Condition

DL-CarrierConfigCommon-NB -DEFAULT::= SEQUENCE {

dl-CarrierFreq-r14

Downlink EARFCN for non-anchor carrier under test.

For Signalling test cases, see 36.508 clause 8.3.2.3. Use the anchor carrier EARFCN + 2.

}