22.4.6 NB-IoT / RRC / Paging for notification of BCCH modification in idle mode / Direct indication for SI update

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

(1)

with { UE in RRC_IDLE state }

ensure that {
when { UE receives a Direct Indication Information message indicating a systemInfoModification }

then { UE re-acquires and applies the new system information and initiates the RRC connection procedure using the updated NPRACH-ConfigSIB-NB provided in the system information }

}

22.4.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 6.7.5, 5.2.2.3, and 5.2.2.4.

[TS 36.331, clause 6.7.5]

Direct Indication information is transmitted on NPDCCH using P-RNTI but without associated Paging-NB message. Table 6.7.5-1 defines the Direct Indication information, see TS 36.212 [22, 6.4.3.3].

When bit n is set to 1, the UE shall behave as if the corresponding field is set in the Paging-NB message, see 5.3.2.3. Bit 1 is the least significant bit.

Table 6.7.5-1: Direct Indication information

Bit

Field in Direct Indication information

1

systemInfoModification

2

systemInfoModification-eDRX

3, 4, 5, 6, 7, 8

Not used, and shall be ignored by UE if received

[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> / MasterInformationBlock-TDD-NB the MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB and SystemInformationBlockType1-NB as well as SystemInformationBlockType2-NB through SystemInformationBlockType5-NB, SystemInformationBlockType22-NB;

[TS 36.331, clause 5.2.2.4]

The UE shall:

1> apply the specified BCCH configuration defined in 9.1.1.1 or BR-BCCH configuration defined in 9.1.1.8;

1> if the procedure is triggered by a system information change notification:

2> if the UE uses an idle DRX cycle longer than the modification period:

3> start acquiring the required system information, as defined in 5.2.2.3, from the next eDRX acquisition period boundary;

2> else

3> start acquiring the required system information, as defined in 5.2.2.3, from the beginning of the modification period following the one in which the change notification was received;

The UE may apply the received SIBs immediately, i.e. the UE does not need to delay using a SIB until all SI messages have been received. The UE may delay applying the received SIBs until completing lower layer procedures associated with a received or a UE originated RRC message, e.g. an ongoing random access procedure.

NOTE 6: While attempting to acquire a particular SIB, if the UE detects from schedulingInfoList that it is no longer present, the UE should stop trying to acquire the particular SIB.

22.4.6.3 Test description

22.4.6.3.1 Pre-test conditions

System Simulator:

– Ncell 1.

UE:

None.

Preamble:

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

22.4.6.3.2 Test procedure sequence

Table 22.4.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Wait for 5 s for the UE to enter RRC_IDLE state.

2

The SS changes the NPRACHConfigSIB-NB in SystemInformationBlockType2-NB and both systemInfoValueTag-r13 in MasterInformationBlock-NB and systemInfoValueTagList-r13 / systemInfoValueTagList-r15 inSystemInformationBlockType1-NB (see NOTE 1) are increased.

3

The SS indicates a systemInfoModification using Direct In<–dication Information.

NPDCCH (DCI N2):

Direct Indication

4

Wait for 2.1* modification period (Note 2) to allow the new system information to take effect.

5

Check: Does the test result 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

6

The SS transmits an RRCConnectionRelease-NB message.

<–

RRC: RRCConnectionRelease-NB

NOTE 1: The present test case uses the IE type systemInfoValueTagList-r13 in SystemInformationBlockType1-NB on purpose, to provide increased test coverage.

NOTE 2: The wait time of 2.1* modification period is to allow for the network to page the system information change during the next modification period, and update the system information at the subsequent modification period. UE should acquire the updated system information within 90ms of the start of modification period.

22.4.6.3.3 Specific message contents

Table 22.4.6.3.3-0A: SystemInformationBlockType1-NB (preamble, table 22.4.6.3.2-1)

Derivation path: 36.508 Table 8.1.4.3.2-3

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType1-NB ::= SEQUENCE {

systemInfoValueTagList-r13 SEQUENCE (SIZE (1.. maxSI-Message-NB-r13)) OF

1 entry

{

SystemInfoValueTagSI-r13[1]

0

}

}

Table 22.4.6.3.3-0B: MasterInformationBlock-NB (step 2, table 22.4.6.3.2-1)

Derivation path: 36.508 Table 8.1.4.3.2-1

Information Element

Value/Remark

Comment

Condition

MasterInformationBlock-NB ::= SEQUENCE {

systemInfoValueTag-r13

The value is increased by 1

}

Table 22.4.6.3.3-0C: MasterInformationBlock-TDD-NB (step 2, table 22.4.6.3.2-1)

Derivation path: 36.508 Table 8.1.4.3.2-1A

Information Element

Value/Remark

Comment

Condition

MasterInformationBlock-TDD-NB-r15 ::= SEQUENCE {

systemInfoValueTag-r15

The value is increased by 1

}

Table 22.4.6.3.3-1: SystemInformationBlockType1-NB (step 2, table 22.4.6.3.2-1)

Derivation path: 36.508 Table 8.1.4.3.2-3

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType1-NB ::= SEQUENCE {

systemInfoValueTagList-r13 SEQUENCE (SIZE (1.. maxSI-Message-NB-r13)) OF

1 entry

{

SystemInfoValueTagSI-r13[1]

The value is increased by 1

}

}

Table 22.4.6.3.3-2: SystemInformationBlockType2-NB (step 2, Table 22.4.6.3.2-1)

Derivation Path: 36.508 Table 8.1.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2-NB-r13 ::= SEQUENCE {

radioResourceConfigCommon-r13 SEQUENCE {

nprach-Config-r13 SEQUENCE {

nprach-CP-Length-r13

us266dot7

}

}

}