22.4.26 NB-IoT / RRC connection establishment / Extended and spare fields in SI

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

(1)

with { UE is powered on and receives system information }

ensure that {

when { UE receives an optional spare or extended field in system information that it does not comprehend }

then { UE treats system information as if the spare or extended field were absent and system information is not ignored, and UE establishes an RRC connection }

}

22.4.26.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.331, clauses 5.2.2.3, 5.7.1 and 5.7.3.

[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/ MasterInformationBlock-TDD-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 and SystemInformationBlockType24 (depending on support of the concerned RATs), SystemInformationBlockType17 (depending on support of RAN-assisted WLAN interworking when the UE is connected to EPC), SystemInformationBlockType25 (depending on support of E-UTRA/5GC);

2> if in RRC_INACTIVE:

3> the MasterInformationBlock and SystemInformationBlockType1 as well as SystemInformationBlockType2 through SystemInformationBlockType8 (depending on support of the concerned RATs), SystemInformationBlockType25;

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 when the UE is connected to EPC), SystemInformationBlockType25 (depending on support of E-UTRA/5GC);

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/ MasterInformationBlock-TDD-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/ MasterInformationBlock-TDD-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.331 clause 5.7.1]

The generic error handling defined in the subsequent sub-clauses applies unless explicitly specified otherwise e.g. within the procedure specific error handling.

The UE shall consider a value as not comprehended when it is set:

– to an extended value that is not defined in the version of the transfer syntax supported by the UE.

– to a spare or reserved value unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/ reserved value.

The UE shall consider a field as not comprehended when it is defined:

– as spare or reserved unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/ reserved field.

[TS 36.331 clause 5.7.3]

The UE shall, when receiving an RRC message on any logical channel:

1> if the message includes a field that has a value that the UE does not comprehend:

2> if a default value is defined for this field:

3> treat the message while using the default value defined for this field;

2> else if the concerned field is optional:

3> treat the message as if the field were absent and in accordance with the need code for absence of the concerned field;

2> else:

3> treat the message as if the field were absent and in accordance with sub-clause 5.7.4;

22.4.26.3 Test description

22.4.26.3.1 Pre-test conditions

System Simulator:

– Ncell 1

UE:

None.

Preamble:

– The UE is in state Switched OFF (state 1) according to TS 36.508 [18].

22.4.26.3.2 Test procedure sequence

Table 22.4.26.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

System information that includes extended and spare fields that the UE does not comprehend is broadcasted on BCCH.

<–

RRC: SYSTEM INFORMATION (BCCH)

–

–

2

The UE is switched on.

–

–

–

–

3

Does the UE transmit an RRCConnectionRequest-NB message on Ncell 1?

–>

RRCConnectionRequest-NB

1

P

4

The SS transmits an RRCConnectionSetup-NB message on Ncell 1.

<–

RRCConnectionSetup-NB

–

–

5

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message to confirm the successful completion of the connection establishment and to initiate the Attach procedure by including the ATTACH REQUEST message? The PDN CONNECTIVITY REQUEST message is piggybacked in ATTACH REQUEST.

–>

RRCConnectionSetupComplete-NB

NAS: ATTACH REQUEST

NAS: PDN CONNECTIVITY REQUEST

1

P

6-15

Steps 5 to 14b1 of the registration procedure described in TS 36.508 subclause 8.1.5.2 are performed on Ncell 1

–

–

–

–

NOTE: sib-TypeAndInfo-r13 in SystemInformation-NB and si-WindowLength-r13 in SystemInformationBlockType1-NB are set to values in Rel-16 to check spare and extended fields in UE up to Rel-15.

22.4.26.3.3 Specific message contents

Table 22.4.26.3.3-1: Message SystemInformation-NB (step 1, Table 22.4.26.3.2-1)

Derivation Path: 36.508 clause 8.1.4.3.2-2

Information Element

Value/remark

Comment

Condition

SystemInformation-NB::= SEQUENCE {

criticalExtensions CHOICE {

systemInformation-r13 SEQUENCE {

sib-TypeAndInfo-r13 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE {

2 entries

sib2-r13[1]

SystemInformationBlockType2-NB-r13

SIB2-NB

sib23-v1530[2] SEQUENCE {

In the ASN.1, sib23-v1530 is considered an extended field from Rel-13 to Rel-14.

If Rel-13, Rel-14

ul-ConfigList-v1530

Not present

ul-ConfigListMixed-v1530

Not present

lateNonCriticalExtension

Not present

}

sib23-v1530[2]

Not present

TDD

sib27-v1610 [2] SEQUENCE {

In the ASN.1, sib27-v1610 is considered an extended field in Rel-15

If Rel-15

carrierFreqListEUTRA-r16

Not present

carrierFreqsListGERAN-r16

Not present

}

}

}

}

}

Table 22.4.26.3.3-2: Void

Table 22.4.26.3.3-3: Message MasterInformationBlock-NB (step 1, Table 22.4.26.3.2-1)

Derivation Path: 36.508 clause 8.1.4.3.2-1

Information Element

Value/remark

Comment

Condition

MasterInformationBlock-NB ::= SEQUENCE {

systemFrameNumber-MSB-r13

A valid value as defined in TS 36.331 [17]

hyperSFN-LSB-r13

A valid value as defined in TS 36.331 [17]

schedulingInfoSIB1-r13

2

systemInfoValueTag-r13

0

ab-Enabled-r13

FALSE

spare

1111 1111 1’B

From Rel-13 to Rel-15, the lowest 9 bits are considered spares according to TS 36.331 [17].

If Rel-13 to Rel-15

}

Table 22.4.26.3.3-3A: Message MasterInformationBlock-TDD-NB (step 1, Table 22.4.26.3.2-1)

Derivation Path: 36.508 clause 8.1.4.3.2-1A

Information Element

Value/remark

Comment

Condition

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

systemFrameNumber-MSB-r15

A valid value as defined in TS 36.331 [17]

hyperSFN-LSB-r15

A valid value as defined in TS 36.331 [17]

schedulingInfoSIB1-r15

2

systemInfoValueTag-r15

0

ab-Enabled-r15

FALSE

spare

‘0000 0000 0’B

}