22.4.1 NB-IoT / Notification of BCCH modification in idle mode / eDRX cycle longer than the modification period

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

(1)

with { UE in E-UTRA RRC_IDLE state using eDRX cycle longer than System Information Modification period}

ensure that {
when { UE receives a Paging-NB message including IE systemInfoModification-eDRX-r13}

then { UE re-acquires and applies the new system information from the next eDRX acquisition period defined by H-SFN mod 1024 = 0 }

}

(2)

with { UE in E-UTRA RRC_IDLE state using eDRX cycle longer than System Information Modification period}

ensure that {
when { UE receives a Direct Indication Information message with the bit corresponding to systemInfoModification-eDRX set to 1}

then { UE re-acquires and applies the new system information from the next eDRX acquisition period defined by H-SFN mod 1024 = 0 }

}

22.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.304, clause 7.3, TS 36.331, clauses 5.2.1.3, 5.2.2.4, 5.3.2.3 and 6.7.5. Unless and otherwise stated these are Rel-13 requirements.

[TS 36.304, clause 7.3]

The UE may be configured by upper layers with an extended DRX (eDRX) cycle TeDRX. The UE may operate in extended DRX only if the cell indicates support for eDRX in System Information.

If the UE is configured with a TeDRX cycle of 512 radio frames, it monitors POs as defined in 7.1 with parameter T = 512. Otherwise, a UE configured with eDRX monitors POs as defined in 7.1 (i.e., based on the upper layer configured DRX value and a default DRX value determined in 7.1), during a periodic Paging Time Window (PTW) configured for the UE or until a paging message including the UE’s NAS identity is received for the UE during the PTW, whichever is earlier. The PTW is UE-specific and is determined by a Paging Hyperframe (PH), a starting position within the PH (PTW_start) and an ending position (PTW_end). PH, PTW_start and PTW_end are given by the following formulae:

The PH is the H-SFN satisfying the following equation:

H-SFN mod TeDRX,H= (UE_ID_H mod TeDRX,H), where

– UE_ID_H:

– 10 most significant bits of the Hashed ID, if P-PRNTI is monitored on PDCCH or MPDCCH

– 12 most significant bits of the Hashed ID, if P-RNTI is monitored on NPDCCH

IMSI mod 1024

– T eDRX,H  : eDRX cycle of the UE in Hyper-frames, (TeDRX,H =1, 2, …, 256 Hyper-frames) (for NB-IoT, TeDRX,H =2, …, 1024 Hyper-frames) and configured by upper layers.

PTW_start denotes the first radio frame of the PH that is part the PTW and has SFN satisfying the following equation:

SFN = 256* ieDRX, where

– ieDRX = floor(UE_ID_H /TeDRX,H) mod 4

PTW_end is the last radio frame of the PTW and has SFN satisfying the following equation:

SFN = (PTW_start + L*100 – 1) mod 1024, where

– L = Paging Time Window length (in seconds) configured by upper layers

Hashed ID is defined as follows:

Hashed_ID is the Cyclic Redundancy Check value of b31, b30…, b0 of S-TMSI, computed according to CRC-32 algorithm in [34], and

S-TMSI = <b39, b38, …, b0> as defined in [35]

[TS 36.331, clause 5.2.1.3]

Change of system information (other than for ETWS, CMAS and EAB parameters and other than for AB parameters for NB-IoT) only occurs at specific radio frames, i.e. the concept of a modification period is used. System information may be transmitted a number of times with the same content within a modification period, as defined by its scheduling. The modification period boundaries are defined by SFN values for which SFN mod m= 0, where m is the number of radio frames comprising the modification period. The modification period is configured by system information. If H-SFN is provided in SystemInformationBlockType1-BR, modification period boundaries for BL UEs and UEs in CE are defined by SFN values for which (H-SFN * 1024 + SFN) mod m=0. For NB-IoT, H-SFN is always provided and the modification period boundaries are defined by SFN values for which (H-SFN * 1024 + SFN) mod m=0.

To enable system information update notification for RRC_IDLE UEs configured to use a DRX cycle longer than the modification period, an eDRX acquisition period is defined. The boundaries of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod 256 =0. For NB-IoT, the boundaries of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod 1024 =0.

When the network changes (some of the) system information, it first notifies the UEs about this change, i.e. this may be done throughout a modification period. In the next modification period, the network transmits the updated system information. These general principles are illustrated in figure 5.2.1.3-1, in which different colours indicate different system information. Upon receiving a change notification, the UE not configured to use a DRX cycle that is longer than the modification period acquires the new system information immediately from the start of the next modification period. Upon receiving a change notification applicable to eDRX, a UE in RRC_IDLE configured to use a DRX cycle that is longer than the modification period acquires the updated system information immediately from the start of the next eDRX acquisition period. The UE applies the previously acquired system information until the UE acquires the new system information. The possible boundaries of modification for SystemInformationBlockType1-BR are defined by SFN values for which SFN mod 512 = 0 except for notification of ETWS/CMAS for which the eNB may change SystemInformationBlockType1-BR content at any time. For NB-IoT, the possible boundaries of modification for SystemInformationBlockType1-NB are defined by SFN values for which (H-SFN * 1024 + SFN) mod 4096 = 0.

Figure 5.2.1.3-1: Change of system Information

The Paging message is used to inform UEs in RRC_IDLE and UEs in RRC_CONNECTED about a system information change. If the UE is in RRC_CONNECTED or is not configured to use a DRX cycle longer than the modification period in RRC_IDLE, and receives a Paging message including the systemInfoModification, it knows that the system information will change at the next modification period boundary. If a UE in RRC_IDLE is configured to use a DRX cycle longer than the modification period, and the notification is received in a Paging message including the systemInfoModification-eDRX, it acquires the updated system information at the next eDRX acquisition period boundary. Although the UE may be informed about changes in system information, no further details are provided e.g. regarding which system information will change, except if systemInfoValueTagSI is received by BL UEs or UEs in CE.

In RRC_CONNECTED, BL UEs or UEs in CE or NB-IoT UEs are not required to acquire system information except when T311 is running or upon handover where the UE is only required to acquire the MasterInformationBlock in the target PCell. In RRC_IDLE, E-UTRAN may notify BL UEs or UEs in CE or NB-IoT UEs about SI update, and except for NB-IoT, ETWS and CMAS notification and EAB modification, using Direct Indication information, as specified in 6.6 (or 6.7.5 in NB-IoT) and TS 36.212 [22].

…

For BL UEs or UEs in CE or NB-IoT UEs, the change of specific SI message can additionally be indicated by a SI message specific value tag systemInfoValueTagSI. If systemInfoValueTag included in the SystemInformationBlockType1-BR (or MasterInformationBlock-NB/ MasterInformationBlock-TDD-NB in NB-IoT) is different from the one of the stored system information and if systemInfoValueTagSI is included in the SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in NB-IoT) for a specific SI message and is different from the stored one, the UE shall consider this specific SI message to be invalid. If only systemInfoValueTag is included and is different from the stored one, the BL UE or UE in CE should consider any stored system information except SystemInformationBlockType10, SystemInformationBlockType11, SystemInformationBlockType12 and SystemInformationBlockType14 to be invalid; the NB-IoT UE should consider any stored system information except SystemInformationBlockType14-NB to be invalid.

[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;

[TS 36.331, clause 5.3.2.3]

Upon receiving the Paging message, the UE shall:

1> if in RRC_IDLE, for each of the PagingRecord, if any, included in the Paging message:

2> if the ue-Identity included in the PagingRecord matches one of the UE identities allocated by upper layers:

3> forward the ue-Identity and, except for NB-IoT, the cn-Domain to the upper layers;

1> if the systemInfoModification is included; or

  1. if the UE is configured with a DRX cycle longer than the modification period and the systemInfoModification-eDRX is included:

2> re-acquire the required system information using the system information acquisition procedure as specified in 5.2.2

[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

22.4.1.3 Test description

22.4.1.3.1 Pre-test conditions

System Simulator:

– Ncell 1.

UE:

None.

Preamble:

– The UE is configured to request the use of eDRX (in the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages).

– The UE sends “extended DRX parameters IE” in ATTACH REQUEST message and receives “extended DRX parameters IE” in ATTACH ACCEPT message.- The eDRX value in ATTACH ACCEPT is set to a value such that the eDRX cycle is longer than the System Information Modification period.

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

22.4.1.3.2 Test procedure sequence

Table 22.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes nprach-SubcarrierOffset-r13/nprach-SubcarrierOffset-r15 in SystemInformationBlockType2-NB.

–

–

–

–

2

The SS transmits a Paging message including IE systemInfoModification-eDRX-r13 in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX.

=

Paging-NB

–

–

3

Wait till the beginning of next eDRX acquisition time (next H-SFN for which H-SFN mod 1024 =0).

–

–

–

–

4

After Step 3, wait for 10s for the UE to acquire the new system information

–

–

–

–

5

The SS transmits a Paging-NB message including a matched identity in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX.

<–

Paging-NB

–

–

6

Check: Does the UE transmit a random access using nprach-SubcarrierOffset-r13/nprach-SubcarrierOffset-r15 given in step 1?

–

–

1

P

7-10

Steps 2-5 of the generic procedure 8.1.5A.2 specified in TS 36.508 are performed

–

–

–

–

11

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–

12

Wait for 5 seconds

–

–

–

–

13

The SS changes nprach-SubcarrierOffset-r13/nprach-SubcarrierOffset-r15 in SystemInformationBlockType2-NB

–

–

–

–

14

The SS indicates a systemInfoModification using Direct Indication Information with bit 2 set as 1

–

–

–

–

15

Wait till the beginning of next eDRX acquisition time (next H-SFN for which H-SFN mod 1024 =0).

–

–

–

–

16

After Step 15, wait for 10s for the UE to acquire the new system information

–

–

–

–

17

The SS transmits a Paging-NB message including a matched identity in a valid PO within the PTW of the next upcoming UE’s PH as per Idle eDRX.

<–

Paging-NB

–

–

18

Check: Does the UE transmit a random access using nprach-SubcarrierOffset-r13/nprach-SubcarrierOffset-r15 given in step 13?

–

–

2

P

19-22

Steps 2-5 of the generic procedure 8.1.5A.2 specified in TS 36.508 are performed

–

–

–

–

23

The SS transmits an RRCConnectionRelease-NB message.

<–

RRCConnectionRelease-NB

–

–
22.4.1.3.3 Specific message contents

Table 22.4.1.3.3-1: SystemInformationBlockType2-NB (Preamble)

Derivation Path: 36.508 Table 8.1.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2-NB-r13 ::= SEQUENCE {

radioResourceConfigCommon-r13

RadioResourceConfigCommonSIB-NB

}

Table 22.4.1.3.3-2: RadioResourceConfigCommonSIB-NB (Preamble)

Derivation Path: 36.508 Table 8.1.6.3-9

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSIB-NB-DEFAULT ::= SEQUENCE {

bcch-Config-r13 SEQUENCE {

modificationPeriodCoeff-r13

n16

}

pcch-Config-r13 SEQUENCE {

defaultPagingCycle-r13

rf256

}

}

Table 22.4.1.3.3-3: ATTACH ACCEPT (Preamble)

Derivation Path: 36.508 Table 4.7.2-1

Information Element

Value/remark

Comment

Condition

Extended DRX parameters

Paging Time Window

‘0001’B

5,12 seconds

eDRX value

‘0101’B

81,92 seconds

Table 22.4.1.3.3-4: Paging-NB (step 2, Table 22.4.1.3.2-1)

Derivation Path: 36.508 Table 8.1.6.1-2

Information Element

Value/remark

Comment

Condition

Paging-NB ::= SEQUENCE {

systemInfoModification-eDRX-r13

True

}

Table 22.4.1.3.3-5: MasterInformationBlock-NB (step 3, table 22.4.1.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

1

Default value is 0

}

Table 22.4.1.3.3-5A: MasterInformationBlock-TDD-NB (step 3, table 22.4.1.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

1

Default value is 0

}

Table 22.4.1.3.3-6: Void

Table 22.4.1.3.3-7: SystemInformationBlockType2-NB (step 1, Table 22.4.1.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 {

FDD

nprach-ParametersList-r13 SEQUENCE {

nprach-SubcarrierOffset-r13

n24

Default value is n12

}

}

nprach-Config-v1530 SEQUENCE {

TDD

tdd-Parameters-r15 SEQUENCE {

nprach-ParametersListTDD-r15 SEQUENCE{

nprach-Parameters-r15 SEQUENCE {

nprach-SubcarrierOffset-r15

n24

Default value is n12

}

}

}

}

}

}

Table 22.4.1.3.3-8: MasterInformationBlock-NB (step 15, table 22.4.1.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

2

}

Table 22.4.1.3.3-8A: MasterInformationBlock-TDD-NB (step 15, table 22.4.1.3.2-1)

Derivation path: 36.508 Table 8.1.4.3.2-1

Information Element

Value/Remark

Comment

Condition

MasterInformationBlock-NB-r15 ::= SEQUENCE {

systemInfoValueTag-r15

2

}

Table 22.4.1.3.3-9: SystemInformationBlockType2-NB (step 13, Table 22.4.1.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 {

FDD

nprach-Config-r13 SEQUENCE {

nprach-ParametersList-r13 SEQUENCE {

nprach-SubcarrierOffset-r13

n12

}

}

nprach-Config-v1530 SEQUENCE {

TDD

tdd-Parameters-r15 SEQUENCE {

nprach-ParametersListTDD-r15 SEQUENCE{

nprach-Parameters-r15 SEQUENCE {

nprach-SubcarrierOffset-r15

n12

}

}

}

}

}

}