22.4.14a NB-IoT / RRC Connection Establishment / Multi-Carrier/ Mixed Operation Mode

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.14a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_IDLE state }

ensure that {
when { UE receives an RRCConnectionSetup-NB message including IE CarrierConfigDedicated }

then { UE transmits an RRCConnectionSetupComplete-NB message }

}

(2)

with { UE has received an RRCConnectionSetup-NB message including IE CarrierConfigDedicated }

ensure that {

when { UE continues with initial registration }

then { RRC signalling happens on non-anchor carrier }

}

22.4.14a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.3.10.6.

[TS 36.331, clause 5.3.10.6]

For NB-IoT, the UE shall:

1> if the carrierConfigDedicated is not included in the received physicalConfigDedicated:

2> if the UE is configured with a carrier configuration previously received in carrierConfigDedicated:

3> use the carrier configuration received in carrierConfigDedicated;

2> else:

3> use the carrier configuration received for the anchor carrier in the system information;

1> else:

2> use the carrier configuration received in carrierConfigDedicated;

2> start to use the new carrier immediately after the last transport block carrying the RRC message has been acknowledged by the MAC layer, and any subsequent RRC response message sent for the current RRC procedure is therefore sent on the new carrier;

1> reconfigure the physical channel configuration in accordance with the received physicalConfigDedicated.

22.4.14a.3 Test description

22.4.14a.3.1 Pre-test conditions

System Simulator:

– Ncell 1.

– NB-IoT Operation Mode set to standalone.

– 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.14a.3.3-1.

UE:

None.

Preamble:

– UE is in State 1-NB switched off.

22.4.14a.3.2 Test procedure sequence

Table 22.4.14a.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1-2

Steps 1-2 expected sequence defined in TS 36.508 Table 8.1.5.2.3-1 NB-IoT UE connected mode procedure (state 1-NB to state 2-NB).

3

The SS transmits an RRCConnectionSetup-NB message including IE CarrierConfigDedicated.

<–

RRCConnectionSetup-NB

4

Check: Does the UE transmit an RRCConnectionSetupComplete-NB message to confirm the successful completion of the connection establishment on non-anchor carrier?

–>

RRCConnectionSetupComplete-NB

1, 2

P

5-16

Check: Does the UE complete initial registration by performing steps 4-14 of TS 36.508 Table 8.1.5.2.3-1 NB-IoT UE connected mode procedure (state 1-NB to state 2-NB) on the non-anchor carrier.

2

P

22.4.14a.3.3 Specific message contents

Table 22.4.14a.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

Not Present

ul-ConfigList-r14

Not Present

mixedOperationModeConfig-r15 SEQUENCE {

dl-ConfigListMixed-r15 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

}

}

ul-ConfigListMixed-r15

Not Present

}

}

Table 22.4.14a.3.3-2: DL-CarrierConfigCommon-NB (Table 22.4.14a.3.3-1)

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 clauses 8.1.3.1. Use the guard-band test frequencies.

}

Table 22.4.14a.3.3-3: RRCConnectionSetup-NB (step 3, Table 22.4.14a.3.2-1)

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

RadioResourceConfigDedicated-NB-SRB

}

}

}

}

Table 22.4.14a.3.3-4: RadioResourceConfigDedicated-NB-SRB (Table 22.4.14a.3.3-3)

Derivation Path: 36.508 table 8.1.6.3-10

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-NB-SRB ::= SEQUENCE {

physicalConfigDedicated-r13

PhysicalConfigDedicated-NB-DEFAULT

}

Table 22.4.14a.3.3-5: PhysicalConfigDedicated-NB-DEFAULT (Table 22.4.14a.3.3-4)

Derivation Path: 36.508 table 8.1.8.2.1.6-1

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-NB-DEFAULT ::= SEQUENCE {

carrierConfigDedicated-r13

CarrierConfigDedicated-NB

Non-anchor carrier

}

Table 22.4.14a.3.3-6: CarrierConfigDedicated-NB (Table 22.4.14a.3.3-5)

Derivation Path: 36.331 clause 6.7.3.2

Information Element

Value/remark

Comment

Condition

CarrierConfigDedicated-NB-r13 ::= SEQUENCE {

dl-CarrierConfig-r13 SEQUENCE {

dl-CarrierFreq-r13 SEQUENCE {

carrierFreq-r13

Downlink EARFCN for non-anchor carrier under test.

For Signalling test cases, see 36.508 clauses 8.1.3.1. Use the guard-band test frequencies.

carrierFreqOffset-r13

v-0dot5

}

downlinkBitmapNonAnchor-r13 CHOICE {

useNoBitmap-r13

NULL

}

dl-GapNonAnchor-r13 CHOICE {

useNoGap-r13

NULL

}

inbandCarrierInfo-r13 SEQUENCE {}

Not present

}

ul-CarrierConfig-r13

Not present

}