8.5.1 Radio link failure

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification

8.5.1.1 Radio link failure / RRC connection re-establishment success

8.5.1.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detecting physical layer problems}

then { UE shall start timer T310 and UE does not initiate any RRC Connection re-establishment procedure before expiring of timer T310}

}

(2)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE detecting radio link failure on expiring of timer T310 }

then { UE starts timer T311 and UE initiates the RRC Connection re-establishment procedure }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE successfully completes the RRC Connection re-establishment procedure }

then { UE is in E-UTRA RRC_CONNECTED state }

}

(4)

with { UE in E-UTRA RRC_CONNECTED state and detecting radio link failure on expiring of timer T310 }

ensure that {

when { A blacklisted neighbour cell satisfies the re-establishment condition, i.e. it has the UE context }

then { UE starts timer T311 and initiates the RRC Connection re-establishment procedure to the blacklisted cell }

}

8.5.1.1.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.7.2, 5.3.10.1, 5.3.10.3 and 5.3.10.4 TS 36.304, clause 5.2.3.1.

[TS 36.331 clause 5.3.7.2]

The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one of the following conditions is met:

1> upon detecting radio link failure, in accordance with 5.3.11; or

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> upon integrity check failure indication from lower layers; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> start timer T311;

1> suspend all RBs except SRB0;

1> reset MAC;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];

[TS 36.331 clause 5.3.11.1]

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications from lower layers while neither T300, T301, T304 nor T311 is running:

2> start timer T310;

[TS 36.331 clause 5.3.11.3]

The UE shall:

1> upon T310 expiry; or

1> upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is running; or

1> upon indication from RLC that the maximum number of retransmissions has been reached:

2> consider radio link failure to be detected;

2> if AS security has not been activated:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

2> else:

3> initiate the connection re-establishment procedure as specified in 5.3.7;

[TS 36.304 clause 5.2.3.1]

The UE shall use one of the following two cell selection procedures:

…

b) Stored Information Cell Selection

This procedure requires stored information of carrier frequencies and optionally also information on cell parameters, from previously received measurement control information elements or from previously detected cells. Once the UE has found a suitable cell the UE shall select it. If no suitable cell is found the Initial Cell Selection procedure shall be started.

NOTE: Priorities between different frequencies or RATs provided to the UE by system information or dedicated signalling are not used in the cell selection process.

8.5.1.1.3 Test description

8.5.1.1.3.1 Pre-test conditions

System Simulator:

– 3 cells on same E-UTRA frequency:

– Cell 1 (default parameters) serving cell

– Cell 2 and Cell 4 are intra-frequency neighbour cells

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18] on cell 1.

8.5.1.1.3.2 Test procedure sequence

Table 8.5.1.1.3.2-0: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Cell 4

T1

Cell-specific RS EPRE

dBm/15kHz

“Off”

-85

-97

T2

Cell-specific RS EPRE

dBm/15kHz

“Off”

“Off”

-85

Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.

Table 8.5.1.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1, Cell 2 and Cell 4 parameters according to the row "T1" in table 8.5.1.1.3.2-0 in order that the radio link quality of Cell 1 is degraded and cell 2 is suitable for camping.

–

–

–

–

2

Check: Does the UE initiate an RRC connection re-establishment procedure on Cell 1 or Cell 2. This is checked during the time T=T310.

–

–

1

F

3

Check: Does the UE send RRCConnectionReestablishmentRequest message on Cell 2?

–>

RRCConnectionReestablishmentRequest

2

P

4

The SS transmits RRCConnectionReestablishment message.

<–

RRCConnectionReestablishment

–

–

5

The UE transmits RRCConnectionReestablishmentComplete message.

–>

RRCConnectionReestablishmentComplete

–

–

6

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer.

<–

RRCConnectionReconfiguration

–

–

7

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

–

–

8

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 2?

–

3

P

9

The SS changes Cell 2 and Cell 4 parameters according to the row "T2" in table 8.5.1.1.3.2-0 in order that the radio link quality of Cell 2 is degraded and cell 4 is suitable for camping.

–

–

–

–

10

Check: Does the UE send RRCConnectionReestablishmentRequest message on Cell 4?

–>

RRCConnectionReestablishmentRequest

4

P

11

The SS transmits RRCConnectionReestablishment message.

<–

RRCConnectionReestablishment

–

–

12

The UE transmits RRCConnectionReestablishmentComplete message.

–>

RRCConnectionReestablishmentComplete

–

–

13

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer.

<–

RRCConnectionReconfiguration

–

–

14

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

–

–

15

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 4?

–

3

–

8.5.1.1.3.3 Specific message contents

Table 8.5.1.1.3.3-0: SystemInformationBlockType4 for Cell 2 (Preamble and all steps, Table 8.5.1.1.3.2-1)

Derivation Path: 36.508 table 4.4.3.3-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType4 ::= SEQUENCE {

intraFreqBlackCellList SEQUENCE (SIZE (1..maxCellBlack)) OF SEQUENCE {

PhysCellIdRange[1] SEQUENCE {

start

physicalCellIdentity-Cell4

range

Not present

}

}

}

Table 8.5.1.1.3.3-1: RRCConnectionReestablishmentRequest (step 3, Table 8.5.1.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentRequest-r8 SEQUENCE {

ue-Identity SEQUENCE {

c-RNTI

the value of the C-RNTI of the UE

physCellId

PhysicalCellIdentity of Cell 1

shortMAC-I

The same value as the 16 least significant bits of the XMAC-I value calculated by SS

}

reestablishmentCause

otherFailure

}

}

}

Table 8.5.1.1.3.3-2: RRCConnectionReconfiguration (step 6 and step 13, Table 8.5.1.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

}

}

}

}

Table 8.5.1.1.3.3-3: RRCConnectionReestablishmentRequest (step 10, Table 8.5.1.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentRequest-r8 SEQUENCE {

ue-Identity SEQUENCE {

c-RNTI

the value of the C-RNTI of the UE

physCellId

PhysicalCellIdentity of Cell 2

shortMAC-I

The same value as the 16 least significant bits of the XMAC-I value calculated by SS

}

reestablishmentCause

otherFailure

}

}

}

8.5.1.2 Radio link failure / T301 expiry

8.5.1.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {

when { UE having sent an RRCConnectionReestablishmentRequest message on starting of timer T301 }

then { UE goes to RRC_IDLE state after timer T301 is expired and trigger TAU procedure in order to recover RRC connection}

}

8.5.1.2.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.7.2, 5.3.7.3, 5.3.7.7, 5.3.11.1 and 5.3.11.3. The following represent an extraction of the requirements relevant to the test purpose.

[TS 36.331 clause 5.3.7.2]

The UE shall only initiate the procedure when AS security has been activated. The UE initiates the procedure when one of the following conditions is met:

1> upon detecting radio link failure, in accordance with 5.3.11; or

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> upon integrity check failure indication from lower layers; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5;

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> start timer T311;

1> suspend all RBs except SRB0;

1> reset MAC;

1> apply the default physical channel configuration as specified in 9.2.4;

1> apply the default semi-persistent scheduling configuration as specified in 9.2.3;

1> apply the default MAC main configuration as specified in 9.2.2;

1> perform cell selection in accordance with the cell selection process as specified in TS 36.304 [4];

[TS 36.331 clause 5.3.7.3]

Upon selecting a suitable E-UTRA cell, the UE shall:

1> stop timer T311;

1> start timer T301;

1> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

1> initiate transmission of the RRCConnectionReestablishmentRequest message in accordance with 5.3.7.4;

NOTE: This procedure applies also if the UE returns to the source cell.

Upon selecting an inter-RAT cell, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

[TS 36.331 clause 5.3.7.7]

The UE shall:

1> if timer T301 expires; or

1> if the selected cell becomes no longer suitable according to the cell selection criteria as specified in TS 36.304 [4]:

2> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

[TS 36.331 clause 5.3.11.1]

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications from lower layers while neither T300, T301, T304 nor T311 is running:

2> start timer T310;

[TS 36.331 clause 5.3.11.3]

The UE shall:

1> upon T310 expiry; or

1> upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is running; or

1> upon indication from RLC that the maximum number of retransmissions has been reached:

2> consider radio link failure to be detected;

2> if AS security has not been activated:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

2> else:

3> initiate the connection re-establishment procedure as specified in 5.3.7;

8.5.1.2.3 Test description

8.5.1.2.3.1 Pre-test conditions

System Simulator:

  • 2 cells on same E-UTRA frequency:

– Cell 1 (default parameters) serving cell

– Cell 2 intra-frequency cell

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.5.1.2.3.2 Test procedure sequence

Table 8.5.1.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes the power level of Cell 1 to non-suitable “Off” and changes the power level of Cell 2 to suitable according to TS 36.508 subclause 6.2.2.1 in order that the radio link quality of Cell 1 is degraded.

–

–

–

–

2

The UE sends RRCConnectionReestablishmentRequest message on Cell 2.

–>

RRCConnectionReestablishmentRequest

–

–

3

The SS does not respond to any RRCConnectionReestablishmentRequest message for 2s (T301).

–

–

–

–

4-8

The UE will perform TAU procedure based on steps 1 to 5 of subclause 6.4.2.7 in TS 36.508 on Cell 2.

NOTE: The UE performs a TAU procedure due to NAS signalling connection recovery.

–

–

–

–

9

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 2?

–

–

1

–

–

At the end of this test procedure sequence, the UE is in end state E-UTRA connected (E2_T3440) according to TS 36.508.

–

–

–

–

8.5.1.2.3.3 Specific message contents

Table 8.5.1.2.3.3-1: SystemInformationBlockType2 for Cell 2 (all steps)

Derivation path: 36.508 table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ue-TimersAndConstants SEQUENCE {

t301

ms2000

}

}

Table 8.5.1.2.3.3-2: RRCConnectionReestablishmentRequest (step 2, Table 8.5.1.2.3.2-1)

Derivation Path: 36.508, Table 4.6.1-13

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentRequest ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentRequest-r8 SEQUENCE {

ue-Identity SEQUENCE {

c-RNTI

the value of the C-RNTI of the UE

physCellId

PhysicalCellIdentity of Cell 1

shortMAC-I

The same value as the 16 least significant bits of the XMAC-I value calculated by SS

}

reestablishmentCause

otherFailure

}

}

}

8.5.1.3 Radio link failure / T311 expiry

8.5.1.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with default bearer established and radio link failure was detected and UE attempts to select a suitable E-UTRA cell to re-establish the RRC connection }

ensure that {
when { UE can not find a suitable cell within T311 }

then { UE does not try to re-establish the RRC connection and goes to RRC_IDLE state after T311 expired }

}

8.5.1.3.2 Conformance requirements

The conformance requirements covered in the current test case are specified in TS 36.331 clause 5.3.7.2, 5.3.7.6 and 5.3.12.

[TS 36.331 clause 5.3.7.2]

…

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> start timer T311;

…

[TS 36.331 clause 5.3.7.6]

Upon T311 expiry, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’.

[TS 36.331 clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers with the release cause;

1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:

2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4].

8.5.1.3.3 Test description

8.5.1.3.3.1 Pre-test conditions

System simulator:

2 cells on same E-UTRA frequency:

– Cell 1 (default parameters) serving cell

– Cell 11 intra-frequency cell

UE:

None.

Preamble:

– The UE is in Generic RB Established (state 3) according to [18] on Cell 1.

– DRX is not configured

8.5.1.3.3.2 Test procedure sequence

Table 8.5.1.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes the power level of Cell 1 to non-suitable “Off” according to TS 36.508 subclause 6.2.2.1 in order that the radio link quality of Cell 1 is degraded.

–

–

–

–

2

Wait for 12s (T311 (10s) is transmitted in SIB2).

–

–

–

–

3

The SS changes the power level of Cell 11 to “Serving Cell” according to TS 36.508 subclause 6.2.2.1.

–

–

–

–

4

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.7 indicate that the UE is camped on E-UTRAN Cell 11?

NOTE: The UE performs a TAU procedure and the RRC connection is released.

–

–

1

–

8.5.1.3.3.3 Specific message contents

Table 8.5.1.3.3.3-1: RRCConnectionReconfiguration (preamble)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

drx-Config

Not present

}

}

}

}

}

}

8.5.1.4 Radio link failure / RRC connection re-establishment reject

8.5.1.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with default bearer established and radio link failure was detected and UE initiates the re-establishment procedure}

ensure that {
when { the UE receives a RRCConnectionReestablishmentReject message }

then { UE goes to RRC_IDLE and trigger TAU procedure in order to recover RRC connection }

}

8.5.1.4.2 Conformance requirements

The conformance requirements covered in the current test case are specified in TS 36.331 clause 5.3.7.8 and 5.3.12.

[TS 36.331 clause 5.3.7.8]

Upon receiving the RRCConnectionReestablishmentReject message, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’.

[TS 36.331 clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:

2> enter RRC_IDLE by performing cell selection in accordance with the cell selection process, defined for the case of leaving RRC_CONNECTED, as specified in TS 36.304 [4];

8.5.1.4.3 Test description

8.5.1.4.3.1 Pre-test conditions

System simulator:

– 2 cells on same E-UTRA frequency:

– Cell 1(default parameters) serving cell

– Cell 2 intra-frequency cell

UE:

None.

Preamble:

– The UE is in Generic RB Established (state 3) according to [18] on Cell 1.

8.5.1.4.3.2 Test procedure sequence

Table 8.5.1.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes the power level of Cell 1 to non-suitable “Off” cell according to TS 36.508 subclause 6.2.2.1 in order that the radio link quality of Cell 1 is degraded and set the power level of Cell 2 to suitable cell.

–

–

–

–

2

The UE transmits an RRCConnectionReestablishmentRequest message on Cell 2.

–>

RRCConnectionRestablishmentRequest

–

–

3

The SS transmits a RRCConnectionReestablishmentReject message

<–

RRCConnectionReestablishmentReject

–

–

4-8

Check: Does the UE perform TAU procedure based on steps 1 to 5 of subclause 6.4.2.7 in TS 36.508 on Cell 2.

NOTE: The UE performs a TAU procedure due to NAS signalling connection recovery.

–

–

1

–

8A

The SS transmits an RRCConnectionRelease message to release RRC connection and move to RRC_IDLE.

<–

RRC: RRCConnectionRelease

–

–

9

Void

–

–

–

–

8.5.1.4.3.3 Specific message contents

None.

8.5.1.5 Radio link failure / Radio link recovery while T310 is running

8.5.1.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE detecting physical layer recovery while T310 was running }

then { the UE resumes the RRC connection without explicit signalling }

}

8.5.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.11.1 and 5.3.11.2.

[TS 36.331, clause 5.3.11.1]

The UE shall:

1> upon receiving N310 consecutive "out of sync" indications from lower layers while neither T300, T301, T304 nor T311 is running:

2> start timer T310.

[TS 36.331, clause 5.3.11.2]

Upon receiving N311 consecutive "in-sync" indications from lower layers while T310 is running, the UE shall:1>

stop timer T310.

NOTE 1: In this case, the UE resumes the RRC connection without explicit signalling, i.e. the UE resumes the entire radio resource configuration.

NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications

8.5.1.5.3 Test description

8.5.1.5.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) according to [18].

8.5.1.5.3.2 Test procedure sequence

Table 8.5.1.5.3.2-1 illustrates the downlink power level to be applied for the cell at various time instants of the test execution. Row marked "T0" denotes the initial condition, while column marked "T1"is applied according the procedure.

Table 8.5.1.5.3.2-1: Time instances of cell power level

Parameter

Unit

Cell 1

Remark

T0

RS EPRE

dBm/15kHz

Pdefault

Power level from 36.508 clause 6.2.2.1. Pdefault as serving cell.

T1

RS EPRE

dBm/15kHz

Poff

Poff as non-suitable “Off” cell.

Table 8.5.1.5.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

SS wait for the 660ms to ensure that DL Timing Advance is sent at least once and UE apply the value of timeAlignmentTimerDedicated which is updated during the preamble.

–

–

–

–

1

The SS changes Cell 1 level according to the row "T1" in table 8.5.1.5.3.2-1.

–

–

–

–

2

SS waits for 1.5s. The T310 is 2s.

–

–

–

–

3

The SS changes Cell 1 level according to the row "T0" in table 8.5.1.5.3.2-1.

–

–

–

–

4

SS waits for 5s.

Check: Does the UE transmit any signalling message?

–

–

1

F

5

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

–

–

1

–

8.5.1.5.3.3 Specific message contents

Table 8.5.1.5.3.3-1: SystemInformationBlockType2 (preamble and all steps, Table 8.5.1.5.3.2-2)

Derivation path: 36.508 table 4.4.3.3-1

Information Element

Value/Remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ue-TimersAndConstants SEQUENCE {

t310

ms2000

}

}

Table 8.5.1.5.3.3-2: RRCConnectionReconfiguration (preamble: Table 4.5.3.3-1 [18], step 8)

Derivation path: 36.508 table 4.8.2.1.5-1

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated SEQUENCE {

mac-MainConfig CHOICE {

timeAlignmentTimerDedicated

Infinity

}

}

}

}

}

}

NOTE: As per test model SS is not configured to transmit PDCCH orders and it expects UE to be PUCCH synchronized throughout the test sequence.

8.5.1.6 Radio link failure / T311 expiry / Dedicated RLF timer

8.5.1.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state }

ensure that {
when { UE receives an RRCConnectionReconfiguration message containing an rlf-TimersAndConstants-r9 set to setup }

then { UE uses timer value received in the RRCConnectionReconfiguration message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state and having received an RRCConnectionReconfiguration message containing an rlf-TimersAndConstants-r9 set to setup }

ensure that {
when { UE receives SystemInformationBlockType2 containing different timer value from RRCConnectionReconfiguration message }

then { UE continues to use timer value received in the RRCConnectionReconfiguration message }

}

(3)

with { UE in E-UTRA RRC_CONNECTED state and having received an RRCConnectionReconfiguration message containing an rlf-TimersAndConstants-r9 set to setup }

ensure that {
when { UE receives an RRCConnectionReconfiguration message containing an rlf-TimersAndConstants-r9 set to release }

then { UE does not use timer value received in the RRCConnectionReconfiguration message }

}

8.5.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.2.2.9, 5.3.7.2, 5.3.7.6, 5.3.10.0, 5.3.10.7 and 5.3.12.

[TS 36.331 clause 5.2.2.9]

Upon receiving SystemInformationBlockType2, the UE shall:

…

1> if in RRC_CONNECTED and UE has previously received rlf-TimersAndConstants:

2> The UE shall not update its values of the timers and constants in UE-TimersAndConstants except for the value of timer T300.

[TS 36.331 clause 5.3.7.2]

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> start timer T311;

[TS 36.331 clause 5.3.7.6]

Upon T311 expiry, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘RRC connection failure’;

[TS 36.331 clause 5.3.10.0]

The UE shall:

…

1> if the received radioResourceConfigDedicated includes the rlf-TimersAndConstants:

2> reconfigure the values of timers and constants as specified in 5.3.10.7;

[TS 36.331 clause 5.3.10.7]

The UE shall:

1> if the received rlf-TimersAndConstants is set to ‘release’:

2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SystemInformationBlockType2;

1> else:

2> reconfigure the value of timers and constants in accordance with received rlf-TimersAndConstants;

[TS 36.331 clause 5.3.12]

Upon leaving RRC_CONNECTED, the UE shall:

1> reset MAC;

1> stop all timers that are running except T320;

1> release all radio resources, including release of the RLC entity, the MAC configuration and the associated PDCP entity for all established RBs;

1> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC_CONNECTED was not triggered by reception of the MobilityFromEUTRACommand message:

2> enter RRC_IDLE and perform procedures as specified in TS 36.304 [4, 5.2.7];

8.5.1.6.3 Test description

8.5.1.6.3.1 Pre-test conditions

System simulator:

– Cell 1 and Cell 2

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.5.1.6.3.2 Test procedure sequence

Table 8.5.1.6.3.2-1 illustrates the downlink power levels to be applied for the cells at various time instants of the test execution. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.5.1.6.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T1

Cell-specific RS EPRE

dBm/15kHz

”Off”

”Off”

No Cells are available.

(NOTE 1).

T2

Cell-specific RS EPRE

dBm/15kHz

”Off”

-85

Only Cell 2 is available.

(NOTE 1).

T3

Cell-specific RS EPRE

dBm/15kHz

-85

”Off”

Only Cell 1 is available.

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.

Table 8.5.1.6.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 levels according to row "T1" in Table 8.5.1.6.3.2-1.

–

–

–

–

2

Wait for 10s (see NOTE).

–

–

–

–

3

The SS changes Cell 2 levels according to row "T2" in Table 8.5.1.6.3.2-1.

–

–

–

–

4

Check: Does the UE transmit an RRCConnectionRequest message on Cell 2?

–>

RRCConnectionRequest

1

P

5-9

Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 6.4.2.7 are performed on Cell 2.

NOTE: The UE performs a TAU procedure and the RRC connection is released.

–

–

–

–

10

Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.

–

–

–

–

11-18

Steps 2 to 9 of the generic test procedure in TS 36.508 subclause 4.5.3.3 are performed on Cell 2.

NOTE: The UE performs the establishment of the data radio bearer associated with the default EPS bearer context.

–

–

–

–

19

The SS transmits a Paging message including systemInfoModification on Cell 2.

<–

Paging

–

–

20

Wait for 2.1* modification period for the UE to receive system information.

–

–

–

–

21

The SS changes Cell 2 levels according to row "T1" in Table 8.5.1.6.3.2-1.

–

–

–

–

22

Wait for 10s (see NOTE).

–

–

–

–

23

The SS changes Cell 1 levels according to row "T3" in Table 8.5.1.6.3.2-1.

–

–

–

–

24

Check: Does the UE transmit an RRCConnectionRequest message on Cell 1?

–>

RRCConnectionRequest

2

P

25-29

Steps 2 to 6 of the generic test procedure in TS 36.508 subclause 6.4.2.7 are performed on Cell 1.

NOTE: The UE performs a TAU procedure and the RRC connection is released.

–

–

–

–

30

Wait for 5 s for the UE to enter E-UTRA RRC_IDLE state.

–

–

–

–

31-38

Steps 2 to 9 of the generic test procedure in TS 36.508 subclause 4.5.3.3 are performed on Cell 1.

NOTE: The UE performs the establishment of the data radio bearer associated with the default EPS bearer context.

–

–

–

–

39

The SS transmits an RRCConnectionReconfiguration message on Cell 1.

<–

RRCConnectionReconfiguration

–

–

40

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

–

–

41

The SS changes Cell 1 levels according to row "T1" in Table 8.5.1.6.3.2-1.

–

–

–

–

42

Wait for 10s (see NOTE).

–

–

–

–

43

The SS changes Cell 2 levels according to row "T2" in Table 8.5.1.6.3.2-1.

–

–

–

–

44

Check: Does the UE transmit an RRCConnectionReestablishmentRequest message on Cell 2?

–>

RRCConnectionReestablishmentRequest

3

P

45

The SS transmits an RRCConnectionReestablishment message on Cell 2.

<–

RRCConnectionReestablishment

–

–

46

The UE transmits an RRCConnectionReestablishmentComplete message on Cell 2.

–>

RRCConnectionReestablishmentComplete

–

–

47

The SS transmits an RRCConnectionReconfiguration message on Cell 2.

<–

RRCConnectionReconfiguration

–

–

48

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2.

–>

RRCConnectionReconfigurationComplete

–

–

49

Check: Does the test result of generic test procedure in TS 36.508 subclause 6.4.2.3 indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 2?

–

–

3

–

NOTE: The delay of 10 sec is more than 8.4 sec (= time for evaluation of the out-of-sync situation + T310 + T311) plus one additional DRX cycle of 1.28 sec.

8.5.1.6.3.3 Specific message contents

Table 8.5.1.6.3.3-1: SystemInformationBlockType2 for Cell 1 (preamble and all steps, Table 8.5.1.6.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ue-TimersAndConstants SEQUENCE {

t311

ms30000

}

}

Table 8.5.1.6.3.3-2: RRCConnectionReconfiguration (preamble, step 17 and 37 Table 8.5.1.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition SRB2-DRB(1, 0)

Table 8.5.1.6.3.3-3: RadioResourceConfigDedicated (Table 8.5.1.6.3.3-2)

Derivation Path: 36.508, Table 4.6.3-16

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated ::= SEQUENCE {

rlf-TimersAndConstants-r9 CHOICE {

setup SEQUENCE {

t301-r9

ms1000

t310-r9

ms1000

n310-r9

n1

t311-r9

ms1000

n311-r9

n1

}

}

}

Table 8.5.1.6.3.3-4: Paging (step 19, Table 8.5.1.6.3.2-2)

Derivation Path: 36.508 Table 4.6.1-7

Information Element

Value/remark

Comment

Condition

Paging ::= SEQUENCE {

pagingRecordList

Not present

systemInfoModification

true

}

Table 8.5.1.6.3.3-5: SystemInformationBlockType2 for Cell 2 (step 20, Table 8.5.1.6.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

ue-TimersAndConstants SEQUENCE {

t311

ms30000

}

}

Table 8.5.1.6.3.3-6: RRCConnectionReconfiguration (step 39, Table 8.5.1.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated SEQUENCE {

RadioResourceConfigDedicated-NON-DEFAULT

}

}

}

}

}

Table 8.5.1.6.3.3-7: RadioResourceConfigDedicated-NON-DEFAULT (Table 8.5.1.6.3.3-6)

Derivation Path: 36.508, Table 4.6.3-18A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-NON-DEFAULT ::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList

Not present

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

Not present

rlf-TimersAndConstants-r9 CHOICE {

release

NULL

}

}

8.5.1.7 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell

8.5.1.7.1 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band Contiguous CA

8.5.1.7.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED, security activated and Scell configured }

ensure that {

when { UE drops out out service on Scell }

then { UE does not consider radio link failure to be detected and stay in RRC_CONNECTED state }

}

8.5.1.7.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.10.7, 5.3.11.1 and 5.3.11.3.

[TS 36.331, clause 5.3.10.7]

The UE shall:

1> if the received rlf-TimersAndConstants is set to release:

2> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SystemInformationBlockType2;

1> else:

2> reconfigure the value of timers and constants in accordance with received rlf-TimersAndConstants;

[TS 36.331, clause 5.3.11.1]

The UE shall:

1> upon receiving N310 consecutive "out-of-sync" indications for the PCell from lower layers while neither T300, T301, T304 nor T311 is running:

2> start timer T310;

NOTE: Physical layer monitoring and related autonomous actions do not apply to SCells.

[TS 36.331, clause 5.3.11.3]

The UE shall:

1> upon T310 expiry; or

1> upon random access problem indication from MAC while neither T300, T301, T304 nor T311 is running; or

1> upon indication from RLC that the maximum number of retransmissions has been reached:

2> consider radio link failure to be detected;

2> store the following radio link failure information in the VarRLF-Report by setting its fields as follows:

3> clear the information included in VarRLF-Report, if any;

3> set the plmn-Identity to the RPLMN;

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the PCell based on measurements collected up to the moment the UE detected radio link failure;

3> set the measResultNeighCells to include the best measured cells, other than the PCell, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected radio link failure, and set its fields as follows;

4> if the UE was configured to perform measurements for one or more EUTRA frequencies, include the measResultListEUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring UTRA frequencies, include the measResultListUTRA;

4> if the UE was configured to perform measurement reporting for one or more neighbouring GERAN frequencies, include the measResultListGERAN;

4> if the UE was configured to perform measurement reporting for one or more neighbouring CDMA2000 frequencies, include the measResultsCDMA2000;

NOTE: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Blacklisted cells are not required to be reported.

3> if detailed location information is available, set the content of the locationInfo as follows:

4> include the locationCoordinates;

4> include the horizontalVelocity, if available;

3> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

3> if an RRCConnectionReconfiguration message including the mobilityControlInfo was received before the connection failure:

4> include previousPCellId and set it to the global cell identity of the PCell where the last RRCConnectionReconfiguration including the mobilityControlInfo message was received;

4> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration message including the mobilityControlInfo;

3> set the connectionFailureType to rlf;

2> if AS security has not been activated:

3> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

2> else:

3> initiate the connection re-establishment procedure as specified in 5.3.7;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report 48, hours after the radio link failure is detected, upon power off or upon detach.

8.5.1.7.1.3 Test description

8.5.1.7.1.3.1 Pre-test conditions

System Simulator:

– Cell 1, and Cell 3

– Cell 1 is PCell

– Cell 3 is SCell

– Cell 3 is an Inactive SCell according to [18] cl. 6.3.4

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.5.1.7.1.3.2 Test procedure sequence

Table 8.5.1.7.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.5.1.7.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-85

Cell1 and Cell 3 are available

T1

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

Only Cell 1 is available.

.

Table 8.5.1.7.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to configure Scell.

<–

RRCConnectionReconfiguration

–

–

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

–

–

2A

Wait for 1s.

–

–

–

–

3

The SS changes power levels according to row "T1" in Table 8.5.1.7.1.3.2-1.

–

–

–

–

4

Wait for 1s.

–

–

–

–

5

Check: Does the UE transmit an RRCConnectionReestablishmentRequest message on Cell 1?

–>

RRCConnectionReestablishmentRequest

1

F

6

Check: Does the test result of CALL generic test procedure in 36.508 subclause 6.4.2.3  indicate that the UE is in E-UTRA RRC_CONNECTED state on Cell 1?

–

–

1

–

8.5.1.7.1.3.3 Specific message contents

Table 8.5.1.7.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.5.1.7.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 8.5.1.7.1.3.3-2: SCellToAddMod-r10 (Table 8.5.1.7.1.3.3-1)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {

physCellId-r10

PhysicalCellIdentity of Cell 3

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 3

Band > 64

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.5.1.7.1.3.3-3: RadioResourceConfigCommonSCell-r10 (Table 8.5.1.7.1.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13A

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommonSCell-r10 ::= SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

dl-Bandwidth-r10

Same downlink system bandwidth as used for Cell 3

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment
8.5.1.7.2 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Inter-band CA

The scope and description of the present TC is the same as test case 8.5.1.7.1 with the following differences:

– CA configuration: Inter-band CA replaces Intra-band Contiguous CA

– Cells configuration: Cell 10 replaces Cell 3

– Cell 10 is an Inactive SCell according to [18] cl. 6.3.4

8.5.1.7.3 CA / No Radio Link Failure on SCell / RRC Connection Continues on PCell / Intra-band non-Contiguous CA

The scope and description of the present TC is the same as test case 8.5.1.7.1 with the following differences:

– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA

8.5.1.8 Dual Connectivity / Radio link failure

8.5.1.8.1 Radio link failure on PSCell / UE supports SCG DRB

8.5.1.8.1.1 Test Purpose (TP)

(1)

With { UE in connected mode with SCG activated with a SCG DRB established }

ensure that {

when { T313 expires }
then { the UE transmits a SCGFailureInformation message with failureType set to ‘t313-Expiry’ }

}

(2)

With { UE in connected mode with SCG activated with a SCG DRB established }
ensure that {
when { random access problem indication from SCG MAC }
then { the UE transmits a SCGFailureInformation message with failureType set to ‘randomAccessProblem’ }
}

(3)

With { UE in connected mode with SCG activated with a MCG DRB and a SCG DRB established }
ensure that {
when { indication from SCG RLC that the maximum number of retransmissions has been reached for a SCG DRB }
then { the UE shall transmit a SCGFailureInformation message with failureType set to ‘rlc-MaxNumRetx’ }
}

(4)

With { UE in connected mode with SCG activated with a SCG DRB established }
ensure that {
when { T307 expires }
then { the UE shall transmit a SCGFailureInformation message with failureType set to ‘scg-ChangeFailure’ }
}

(5)

With { UE in connected mode with SCG activated }
ensure that {
when { UE detects radio link failure of the PSCell and has PDCP SDUs available for transmission on the MCG DRB }
then { the UE transmits the uplink data on the MCG DRB }
}

8.5.1.8.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.7a, 5.3.11.3, 5.6.13.2, and 5.6.13.3. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.5.7a]

The UE shall:

1> if T307 expires:

NOTE 1: Following T307 expiry any dedicated preamble, if provided within the rach-ConfigDedicatedSCG, is not available for use by the UE anymore.

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG change failure;

[TS 36.331, clause 5.3.11.3]

…

The UE shall:

1> upon T313 expiry; or

1> upon random access problem indication from SCG MAC; or

1> upon indication from SCG RLC that the maximum number of retransmissions has been reached for an SCG or split DRB:

2> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG radio link failure;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure is detected, upon power off or upon detach.

[TS 36.331, clause 5.6.13.2]

A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with 5.3.11; or

1> upon SCG change failure, in accordance with 5.3.5.7a;

Upon initiating the procedure, the UE shall:

1> suspend all SCG DRBs and suspend SCG transmission for split DRBs;

1> reset SCG-MAC;

1> stop T307;

1> initiate transmission of the SCGFailureInformation message in accordance with 5.6.13.3;

[TS 36.331, clause 5.6.13.3]

The UE shall set the contents of the SCGFailureInformation message as follows:

1> if the UE initiates transmission of the SCGFailureInformation message to provide SCG radio link failure information:

2> include failureType and set it to the trigger for detecting SCG radio link failure;

1> else if the UE initiates transmission of the SCGFailureInformation message to provide SCG change failure information:

2> include failureType and set it to scg-ChangeFailure;

1> set the measResultServFreqList to include for each SCG cell that is configured, if any, within measResultSCell the quantities of the concerned SCell, if available according to performance requirements in [16];

1> for each SCG serving frequency included in measResultServFreqList, include within measResultBestNeighCell the physCellId and the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> set the measResultNeighCells to include the best measured cells on non-serving E-UTRA frequencies, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows;

2> if the UE was configured to perform measurements for one or more non-serving EUTRA frequencies and measurement results are available, include the measResultListEUTRA;

2> for each neighbour cell included, include the optional fields that are available;

NOTE 2: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Blacklisted cells are not required to be reported.

The UE shall submit the SCGFailureInformation message to lower layers for transmission.

8.5.1.8.1.3 Test description

8.5.1.8.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 10 is the PSCell1 and Cell 28 is the PSCell2.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1, Cell 10 and Cell 28.

UE:

Preamble:

– The UE is in state DC MCG/SCG DRB Loopback Activated (state 6A with Test loop Mode B) on Cell 1 and Cell 10 according to [18].

8.5.1.8.1.3.2 Test procedure sequence

Table 8.5.1.8.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while column marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.5.1.8.1.3.2-1: Time instances of cell power level and parameter changes

Unit

Cell 1

Cell 10

Cell 28

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-85

-85

Power level values are such that PCell and PSCell1 are used.

T1

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

-85

The power level value of the PSCell1 is changed to create detection of physical layer problems for the PSCell1 i.e. N313 consecutive out-of-sync indications from UE lower layers.

Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.

Table 8.5.1.8.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS stops sending SCG RLC acknowledgments

–

–

–

–

2

The SS transmits one IP packet to the UE on Cell 10 on SCG DRB.

<–

IP packet

–

–

3

UE loops back the IP packet on Cell 10 on SCG DRB

–>

IP packet

–

–

4

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘rlc-MaxNumRetx’?

–>

SCGFailureInformation

3

P

5

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfoSCG-r12

<–

RRCConnectionReconfiguration

–

–

6

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

–

–

7

The SS transmits a PDCCH order from the PSCell1 providing Random Access Preamble.

<–

(PDCCH Order)

–

–

8

The UE transmits a preamble on PRACH to the PSCell1 using the same preamble index as given in step 7

–>

(PRACH Preamble)

–

–

9

The SS waits for 10 seconds

NOTE: The SS does not transmit Random Access Response to the UE.

–

–

–

–

10

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘randomAccessProblem’?

–>

SCGFailureInformation

2

P

11

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfoSCG-r12

<–

RRCConnectionReconfiguration

–

–

12

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

–

–

13

The SS transmits an RRCConnectionReconfiguration message including the IE scg-Configuration that includes the IEs sCellToReleaseListSCG, pSCellToAddMod and mobilityControlInfoSCG modifying the SCG.

The SS does not respond to the UE transmitted RACH preambles on Cell 28.

<–

RRCConnectionReconfiguration

–

–

14

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘scg-ChangeFailure’?

–>

SCGFailureInformation

4

P

14A

The SS transmits an RRCConnectionReconfiguration message containing the IE scg-Configuration that includes the IEs sCellToReleaseListSCG mobilityControlInfoSCG-r12

<–

RRCConnectionReconfiguration

–

–

15

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

–

–

15A

The SS transmits a CLOSE UE TEST LOOP message with Test loop Mode B and IP PDU delay =10 seconds.

<–

RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

15B

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated

–>

RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

16

The SS transmits one IP packet to the UE on the DRB associated with the MCG DRB.

NOTE: The SS does not provide uplink grants to the UE until cell power levels have been set according to the row “T1” in step 17, to ensure UE does not loop back IP packet before RLF has happened.

<–

IP packet

–

–

17

The SS changes Cell 10 parameters according to the row "T1" in table 8.5.1.8.1.3.2-1.

–

–

–

–

18

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘t313-Expiry’?

–>

SCGFailureInformation

1

P

19

The SS changes Cell 10 parameters according to the row "T0" in table 8.5.1.8.1.3.2-1.

–

–

–

–

20

Check: Does the UE loops back the IP packet on Cell 1 (PCell) on the MCG DRB?

–>

IP packet

5

P

8.5.1.8.1.3.3 Specific message contents

Table 8.5.1.8.1.3.3-1: RRCConnectionReconfiguration (step 5& 11Table 8.5.1.8.1.3.2-2)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {}

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

v890

nonCriticalExtension SEQUENCE {

v920

nonCriticalExtension SEQUENCE {

v1020

nonCriticalExtension SEQUENCE {

v1130

nonCriticalExtension SEQUENCE {

v1250

scg-Configuration-r12 CHOICE {

SCG-Configuration-r12- MobSCG

}

}

}

}

}

}

}

}

}

Table 8.5.1.8.1.3.3-2: SCG-Configuration-r12-MobSCG (Table 8.5.1.8.1.3.3-1)

Derivation Path: 36.508, Clause 4.6.3 Table 4.6.3-19F

Information Element

Value/remark

Comment

Condition

scg-Configuration-r12 CHOICE {

setup SEQUENCE {

scg-ConfigPartMCG-r12

Not Present

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12

Not Present

sCellToReleaseListSCG-r12

Not Present

pSCellToAddMod-r12

Not Present

sCellToAddModListSCG-r12

Not present

mobilityControlInfoSCG-r12

mobilityControlInfoSCG-r12 (Table 8.5.1.8.1.3.5)

}

}

}

Table 8.5.1.8.1.3.3-3: RRCConnectionReconfiguration (step 13, Table 8.5.1.8.1.3.2-2)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {}

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-DRBRECONFIG

nonCriticalExtension SEQUENCE {

v890

nonCriticalExtension SEQUENCE {

v920

nonCriticalExtension SEQUENCE {

v1020

nonCriticalExtension SEQUENCE {

v1130

nonCriticalExtension SEQUENCE {

v1250

scg-Configuration-r12 CHOICE {

SCG-Configuration-r12- sCellRelease-pSCellAdd-ModSCG

}

}

}

}

}

}

}

}

}

Table 8.5.1.8.1.3.3-4: SCG-Configuration-r12-sCellRelease-pSCellAdd-ModSCG (Table 8.5.1.8.1.3.3-3)

Derivation Path: 36.508, Clause 4.6.3 Table 4.6.3-19F

Information Element

Value/remark

Comment

Condition

scg-Configuration-r12 CHOICE {

setup SEQUENCE {

scg-ConfigPartMCG-r12

Not present

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12

Not present

sCellToReleaseListSCG-r12

sCellToReleaseListSCG-r12

pSCellToAddMod-r12

pSCellToAddMod-r12

sCellToAddModListSCG-r12

Not present

mobilityControlInfoSCG-r12

mobilityControlInfoSCG-r12

}

}

}

Table 8.5.1.8.1.3.3-5: sCellToReleaseListSCG-r12 (Table 8.5.1.8.1.3.3-4)

Information Element

Value/remark

Comment

Condition

sCellToReleaseListSCG-r12

{ sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

PSCell release for Cell 10

}

}

Table 8.5.1.8.1.3.3-6: pSCellToAddMod-r12 (Table 8.5.1.8.1.3.3-4)

Information Element

Value/remark

Comment

Condition

PSCellToAddMod-r12 SEQUENCE {

1 entry

sCellIndex-r10

1

PSCellToAddMod-r12 SEQUENCE {

cellIdentification-r12 SEQUENCE {

physCellId-r12

Physical Cell Identity of cell 28

dl-CarrierFreq-r12

Same downlink EARFCN as used for Cell 28

Step 13

Same downlink EARFCN as used for Cell 28

Step 14A

}

RadioResourceConfigCommonPSCell-r12

Same value as 36.508 Clause 4.6.3 Table 4.6.3-19F

RadioResourceConfigDedicatedPSCell-r12

Same value as 36.508 Clause 4.6.3 Table 4.6.3-19F

AntennaInfoDedicated-v10i0

Not present

}

Table 8.5.1.8.1.3.3-7: mobilityControlInfoSCG-r12 (Table 8.5.1.8.1.3.3-4)

Information Element

Value/remark

Comment

Condition

mobilityControlInfoSCG-r12 SEQUENCE {

Modifies the SCG

T307-r12

ms2000

C-RNTI

Any allowed value different than previously assigned

RACH-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

CipheringAlgorithm-r12

Set according to PIXIT parameter for default ciphering algorithm

}
8.5.1.8.2 Radio link failure on PSCell / UE supports Split DRB

8.5.1.8.2.1 Test Purpose (TP)

(1)

With { UE in connected mode with SCG activated with a Split DRB established }

ensure that {

when { T313 expires }

then { the UE transmits a SCGFailureInformation message with failureType set to ‘t313-Expiry’ }

}

(2)

With { UE in connected mode with SCG activated with a Split DRB established }

ensure that {

when { random access problem indication from SCG MAC }

then { the UE transmits a SCGFailureInformation message with failureType set to ‘randomAccessProblem’ }

}

(3)

With { UE in connected mode with SCG activated with a Split DRB established }

ensure that {

when { indication from SCG RLC that the maximum number of retransmissions has been reached for a Split DRB }

then { the UE shall transmit a SCGFailureInformation message with failureType set to ‘rlc-MaxNumRetx’ }

}

(4)

With { UE in connected mode with SCG activated with a Split DRB established }

ensure that {

when { T307 expires }

then { the UE shall transmit a SCGFailureInformation message with failureType set to ‘scg-ChangeFailure’ }

}

(5)

With { UE in connected mode with SCG activated with a Split DRB established and with ul-DataSplitDRB-ViaSCG set to FALSE }

ensure that {

when { UE detects radio link failure of the PSCell and has PDCP SDUs available for transmission }

then { the UE transmits the uplink data on the MAC entity configured for MCG }

}

8.5.1.8.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.7a, 5.3.11.3, 5.6.13.2, and 5.6.13.3. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.5.7a]

The UE shall:

1> if T307 expires:

NOTE 1: Following T307 expiry any dedicated preamble, if provided within the rach-ConfigDedicatedSCG, is not available for use by the UE anymore.

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG change failure;

[TS 36.331, clause 5.3.11.3]

…

The UE shall:

1> upon T313 expiry; or

1> upon random access problem indication from SCG MAC; or

1> upon indication from SCG RLC that the maximum number of retransmissions has been reached for an SCG or split DRB:

2> consider radio link failure to be detected for the SCG i.e. SCG-RLF;

2> initiate the SCG failure information procedure as specified in 5.6.13 to report SCG radio link failure;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report, 48 hours after the radio link failure is detected, upon power off or upon detach.

[TS 36.331, clause 5.6.13.2]

A UE initiates the procedure to report SCG failures when SCG transmission is not suspended and when one of the following conditions is met:

1> upon detecting radio link failure for the SCG, in accordance with 5.3.11; or

1> upon SCG change failure, in accordance with 5.3.5.7a;

Upon initiating the procedure, the UE shall:

1> suspend all SCG DRBs and suspend SCG transmission for split DRBs;

1> reset SCG-MAC;

1> stop T307;

1> initiate transmission of the SCGFailureInformation message in accordance with 5.6.13.3;

[TS 36.331, clause 5.6.13.3]

The UE shall set the contents of the SCGFailureInformation message as follows:

1> if the UE initiates transmission of the SCGFailureInformation message to provide SCG radio link failure information:

2> include failureType and set it to the trigger for detecting SCG radio link failure;

1> else if the UE initiates transmission of the SCGFailureInformation message to provide SCG change failure information:

2> include failureType and set it to scg-ChangeFailure;

1> set the measResultServFreqList to include for each SCG cell that is configured, if any, within measResultSCell the quantities of the concerned SCell, if available according to performance requirements in [16];

1> for each SCG serving frequency included in measResultServFreqList, include within measResultBestNeighCell the physCellId and the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency;

1> set the measResultNeighCells to include the best measured cells on non-serving E-UTRA frequencies, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows;

2> if the UE was configured to perform measurements for one or more non-serving EUTRA frequencies and measurement results are available, include the measResultListEUTRA;

2> for each neighbour cell included, include the optional fields that are available;

NOTE 2: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Blacklisted cells are not required to be reported.

The UE shall submit the SCGFailureInformation message to lower layers for transmission.

8.5.1.8.2.3 Test description

8.5.1.8.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 10 is the PSCell1 and Cell 28 is the PSCell2.

– System information combination 3 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA Cell 1, Cell 10 and Cell 28.

UE:

Preamble:

– The UE is in state DC Split DRB Loopback Activated (state 6B with Test loop Mode B) on Cell 1 and Cell 10 according to [18].

8.5.1.8.2.3.2 Test procedure sequence

Table 8.5.1.8.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while column marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.5.1.8.2.3.2-1: Time instances of cell power level and parameter changes

Unit

Cell 1

Cell 10

Cell 28

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-85

-85

Power level values are such that PCell and PSCell1 are used.

T1

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

-85

The power level value of the PSCell1 is changed to create detection of physical layer problems for the PSCell1 i.e. N313 consecutive out-of-sync indications from UE lower layers.

Power level “Off” is defined in TS 36.508 Table 6.2.2.1-1.

Table 8.5.1.8.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS stops sending SCG RLC acknowledgments

–

–

–

–

2

The SS transmits one IP packet to the UE on Cell 10 on split DRB.

<–

IP packet

–

–

3

UE loops back the IP packet on Cell 10 on SCG DRB

–>

IP packet

–

–

4

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘rlc-MaxNumRetx’?

–>

SCGFailureInformation

3

P

5

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfoSCG-r12

<–

RRCConnectionReconfiguration

–

–

6

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

–

–

7

The SS transmits a PDCCH order from the PSCell1 providing Random Access Preamble.

<–

(PDCCH Order)

–

–

8

The UE transmits a preamble on PRACH to the PSCell1 using the same preamble index as given in step 7

–>

(PRACH Preamble)

–

–

9

The SS waits for 10 seconds

NOTE: The SS does not transmit Random Access Response to the UE.

–

–

–

–

10

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘randomAccessProblem’ ?

–>

SCGFailureInformation

2

P

11

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfoSCG-r12

<–

RRCConnectionReconfiguration

–

–

12

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

–

–

13

The SS transmits an RRCConnectionReconfiguration message including the IE scg-Configuration that includes the IEs sCellToReleaseListSCG, pSCellToAddMod and mobilityControlInfoSCG modifying the SCG.

The SS does not respond to the UE transmitted RACH preambles. on Cell 28

<–

RRCConnectionReconfiguration

–

–

14

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘scg-ChangeFailure’?

–>

SCGFailureInformation

4

P

14A

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfoSCG-r12

<–

RRCConnectionReconfiguration

–

–

15

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

–

–

15A

The SS transmits a CLOSE UE TEST LOOP message with Test loop Mode B and IP PDU delay =10 seconds.

<–

RRC: DLInformationTransfer

TC: CLOSE UE TEST LOOP

–

–

15B

The UE transmits a CLOSE UE TEST LOOP COMPLETE message to confirm that loopback entities for the radio bearer(s) have been created and loop back is activated

–>

RRC: ULInformationTransfer

TC: CLOSE UE TEST LOOP COMPLETE

–

–

16

The SS transmits one IP packet to the UE on the DRB associated with the MCG DRB.

NOTE: The SS does not provide uplink grants to the UE until cell power levels have been set according to the row “T1” in step 17, to ensure UE does not loop back IP packet before RLF has happened.

<–

IP packet

–

–

17

The SS changes Cell 10 parameters according to the row "T1" in table 8.5.1.8.1.3.2-1.

–

–

–

–

18

Check: Does the UE transmit an SCGFailureInformation message with failureType set to ‘t313-Expiry’ ?

–>

SCGFailureInformation

1

P

19

The SS changes Cell 10 parameters according to the row "T0" in table 8.5.1.8.1.3.2-1.

–

–

–

–

20

Check: Does the UE loops back the IP packet on Cell 1 (PCell) on the MCG DRB?

–>

IP packet

5

P

8.5.1.8.2.3.3 Specific message contents

Table 8.5.1.8.2.3.3-1: RRCConnectionReconfiguration (step 5 & 11 Table 8.5.1.8.2.3.2-2)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {}

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-DRBRECONFIG

nonCriticalExtension SEQUENCE {

v890

nonCriticalExtension SEQUENCE {

v920

nonCriticalExtension SEQUENCE {

v1020

nonCriticalExtension SEQUENCE {

v1130

nonCriticalExtension SEQUENCE {

v1250

scg-Configuration-r12 CHOICE {

SCG-Configuration-r12- MobSCG

}

}

}

}

}

}

}

}

}

Table 8.5.1.8.2.3.3-2: SCG-Configuration-r12-MobSCG (Table 8.5.1.8.2.3.3-1)

Derivation Path: 36.508, Clause 4.6.3 Table 4.6.3-19F

Information Element

Value/remark

Comment

Condition

scg-Configuration-r12 CHOICE {

setup SEQUENCE {

scg-ConfigPartMCG-r12

Not Present

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12

Not Present

sCellToReleaseListSCG-r12

Not Present

pSCellToAddMod-r12

Not Present

sCellToAddModListSCG-r12

Not present

mobilityControlInfoSCG-r12

mobilityControlInfoSCG-r12 (Table 8.5.1.8.1.3.7)

}

}

}

Table 8.5.1.8.2.3.3-3: RRCConnectionReconfiguration (step 13 & 14A, Table 8.5.1.8.2.3.2-2)

Derivation Path: 36.508, Clause 4.6.1, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {}

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-DRBRECONFIG

nonCriticalExtension SEQUENCE {

v890

nonCriticalExtension SEQUENCE {

v920

nonCriticalExtension SEQUENCE {

v1020

nonCriticalExtension SEQUENCE {

v1130

nonCriticalExtension SEQUENCE {

v1250

scg-Configuration-r12 CHOICE {

SCG-Configuration-r12- sCellRelease-pSCellAdd-ModSCG

}

}

}

}

}

}

}

}

}

Table 8.5.1.8.2.3.3-4: SCG-Configuration-r12-sCellRelease-pSCellAdd-ModSCG (Table 8.5.1.8.2.3.3-3)

Derivation Path: 36.508, Clause 4.6.3 Table 4.6.3-19F

Information Element

Value/remark

Comment

Condition

scg-Configuration-r12 CHOICE {

setup SEQUENCE {

scg-ConfigPartMCG-r12

Not present

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12

Not present

sCellToReleaseListSCG-r12

sCellToReleaseListSCG-r12

pSCellToAddMod-r12

pSCellToAddMod-r12

sCellToAddModListSCG-r12

Not present

mobilityControlInfoSCG-r12

mobilityControlInfoSCG-r12

}

}

}

Table 8.5.1.8.2.3.3-5: sCellToReleaseListSCG-r12 (Table 8.5.1.8.2.3.3-4)

Information Element

Value/remark

Comment

Condition

sCellToReleaseListSCG-r12

{ sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

PSCell release for Cell 10

}

}

Table 8.5.1.8.2.3.3-6: pSCellToAddMod-r12 (Table 8.5.1.8.2.3.3-4)

Information Element

Value/remark

Comment

Condition

PSCellToAddMod-r12 SEQUENCE {

1 entry

sCellIndex-r10

1

PSCellToAddMod-r12 SEQUENCE {

cellIdentification-r12 SEQUENCE {

physCellId-r12

Physical Cell Identity of cell 28

dl-CarrierFreq-r12

Same downlink EARFCN as used for Cell 28

Step 13

dl-CarrierFreq-r12

Same downlink EARFCN as used for Cell 10

Step 14A

}

RadioResourceConfigCommonPSCell-r12

Same value as 36.508 Clause 4.6.3 Table 4.6.3-19F

RadioResourceConfigDedicatedPSCell-r12

Same value as 36.508 Clause 4.6.3 Table 4.6.3-19F

AntennaInfoDedicated-v10i0

Not present

}

Table 8.5.1.8.2.3.3-7: mobilityControlInfoSCG-r12 (Table 8.5.1.8.2.3.3-4)

Information Element

Value/remark

Comment

Condition

mobilityControlInfoSCG-r12 SEQUENCE {

Modifies the SCG

T307-r12

ms2000

C-RNTI

Any allowed value different than previously assigned

RACH-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

CipheringAlgorithm-r12

Set according to PIXIT parameter for default ciphering algorithm

}

8.5.1.9 Radio link failure / RRC connection re-establishment success/ Release configured UDC

8.5.1.9.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with UDC configuration}

ensure that {

when { UE successfully completes the RRC Connection re-establishment procedure }

then { UE release the configured UDC }

}

8.5.1.9.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in TS 36.331, clauses 5.3.7.2.

[TS 36.331 clause 5.3.7.2]

The UE shall only initiate the procedure either when AS security has been activated or for a NB-IoT UE supporting RRC connection re-establishment for the Control Plane CIoT EPS optimisation. The UE initiates the procedure when one of the following conditions is met:

1> upon detecting radio link failure, in accordance with 5.3.11; or

1> upon handover failure, in accordance with 5.3.5.6; or

1> upon mobility from E-UTRA failure, in accordance with 5.4.3.5; or

1> upon integrity check failure indication from lower layers concerning SRB1 or SRB2; or

1> upon an RRC connection reconfiguration failure, in accordance with 5.3.5.5; or

1> upon an RRC connection reconfiguration failure, in accordance with TS38.331 [82, 5.3.5.5].

Upon initiation of the procedure, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> stop timer T313, if running;

1> stop timer T307, if running;

1> start timer T311;

1> stop timer T370, if running;

1> release uplinkDataCompression, if configured;

8.5.1.9.3 Test description

8.5.1.9.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Loopback Activated (state 4) according to [18].

– The condition UDC is used for PDCP-Config in step 8 in 4.5.3.3 according to [18].

8.5.1.9.3.2 Test procedure sequence

Table 8.5.1.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS creates 3 PDCP Data PDUs and the Next_PDCP_TX_SN is set to "0".

–

–

–

–

2

The SS sends the PDCP Data PDU#0 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 0.

After having sent a PDU, the SS set Next_PDCP_TX_SN= 1.

<–

PDCP PDU DATA #0

–

–

3

The UE sends the PDCP Data PDU#0 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) , PDCP SN = 0, FU = 1, FR = 0, Checksum = 1111.

Data is previously received data from PDU #0 after decompression.

–>

PDCP PDU DATA #0

–

–

4

The SS sends the PDCP Data PDU#1 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 1.

After having sent a PDU, the SS set Next_PDCP_TX_SN= 2.

<–

PDCP PDU DATA #1

–

–

5

The UE sends the PDCP Data PDU#1 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) , PDCP SN = 1, FU = 1, FR = 0, the value of Checksum is checked (Note 1).

Data is previously received data from PDU #1 after decompression.

–>

PDCP PDU DATA #1

–

–

6

The SS changes the power level of Cell 1 to non-suitable “Off” according to TS 36.508 subclause 6.2.2.1 in order that the radio link quality of Cell 1 is degraded.

–

–

–

–

7

Wait for 12s (T311 (10s) is transmitted in SIB2).

–

–

–

–

8

The SS changes the power level of Cell 1 to “Serving Cell” according to TS 36.508 subclause 6.2.2.1.

–

–

–

–

9

The UE send RRCConnectionReestablishmentRequest message on Cell 1?

–>

RRCConnectionReestablishmentRequest

–

–

10

The SS transmits RRCConnectionReestablishment message.

<–

RRCConnectionReestablishment

–

–

11

The UE transmits RRCConnectionReestablishmentComplete message.

–>

RRCConnectionReestablishmentComplete

–

–

12

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer.

<–

RRCConnectionReconfiguration

–

–

13

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

–

–

14

The SS sends the PDCP Data PDU#0 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) and PDCP SN = 0.

<–

PDCP PDU DATA #0

–

–

15

Check: Does the UE sends the PDCP Data PDU#0 via RLC-AM RB with the following content to the UE:

D/C field = 1 (PDCP Data PDU) , PDCP SN = 0, FU = 1, FR = 1, Checksum = 1111.

Data is previously received data from PDU #0 after decompression.

–>

PDCP PDU DATA #0

1

P

Note 1: The SS compares the received value of Checksum and calculated value of Checksum based on the compression buffer.

8.5.1.9.3.3 Specific message contents

None.