8.2.4 Handover

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.2.4.1 RRC connection reconfiguration / Handover / Success / Dedicated preamble

8.2.4.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the intra frequency measurement}

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo with a rach-ConfigDedicated }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the intra frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a nextHopChainingCount which is different from the NCC associated with the currently active KeNB }

then { UE derives new KeNB key from the nextHopChainingCount }

}

(3)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the intra frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a nextHopChainingCount which is same as the NCC associated with the currently active KeNB }

then { UE derives new KeNB key from the currently active KeNB }

}

8.2.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target cell by acquiring system information from that cell before performing RACH access in the target cell.

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.1.3 Test description

8.2.4.1.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 4 and Cell 11.

UE:

None.

Preamble:

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

8.2.4.1.3.2 Test procedure sequence

Table 8.2.4.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", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 4

Cell 11

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

”Off”

The power level values are such that measurement results for Cell 1 (M1) and Cell 4 (M4) satisfy exit condition for event A3 (M4 < M1)(NOTE 1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

”Off”

The power level values are such that measurement results for Cell 1 (M1) and Cell 4 (M4) satisfy entry condition for event A3 (M4 > M1)(NOTE 1).

T2

Cell-specific RS EPRE

dBm/15kHz

-85

-91

"Off"

The power level values are such that measurement results for Cell 1 (M1) and Cell 4 (M4) satisfy entry condition for event A3 (M1 > M4)(NOTE 1).

T3

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

-79

The power level value are such that measurement results for Cell 1 (M1) and Cell 11 (M11) satisfy entry condition for event A3 (M11 > M1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T1" in table 8.2.4.1.3.2-1.

4

The UE transmits a MeasurementReport message to report event A3 on Cell 1 with the measured RSRP, RSRQ value for Cell 4.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 4.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 4 using dedicated preamble to confirm the successful completion of the intra frequency handover?

Check2: Does the UE transmit an RRCConnectionReconfigurationComplete using the security key derived from the currently active KeNB?

–>

RRCConnectionReconfigurationComplete

1,3

P

EXCEPTION: Steps 6a1 to 6a2 describe behaviour that depends on the UE capability; the “lower case letter” identifies a step sequence that takes place if a capability is supported.

6a1

IF pc_intraFreq-CE-NeedForGaps THEN the SS transmits an RRCConnectionReconfiguration message to activate the measurement gaps on Cell 4

<-

RRCConnectionReconfiguration

6a2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the activation of the measurement gaps on Cell 4

->

RRCConnectionReconfigurationComplete

7

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T2" in table 8.2.4.1.3.2-1.

8

The UE transmits a MeasurementReport message to report event A3 on Cell 4 with the measured RSRP, RSRQ value for Cell 1.

–>

MeasurementReport

9

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 1.

<–

RRCConnectionReconfiguration

10

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 using dedicated preamble to confirm the successful completion of the intra frequency handover?

Check2: Does the UE transmit an RRCConnectionReconfigurationComplete using the security key derived from the nextHopChainingCount?

–>

RRCConnectionReconfigurationComplete

1,2

P

EXCEPTION: Steps 10a1 to 10a2 describe behaviour that depends on the UE capability; the “lower case letter” identifies a step sequence that takes place if a capability is supported.

10a1

IF pc_intraFreq-CE-NeedForGaps THEN the SS transmits an RRCConnectionReconfiguration message to activate the measurement gaps on Cell 1

<-

RRCConnectionReconfiguration

10a2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the activation of the measurement gaps on Cell 1

->

RRCConnectionReconfigurationComplete

11

The SS changes Cell 1 and Cell 11 parameters and switches Cell 4 off according to the row "T3" in table 8.2.4.1.3.2-1.

12

The UE transmits a MeasurementReport message to report event A3 on Cell 1 with the measured RSRP,RSRQ value for Cell 11.

–>

MeasurementReport

13

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 11.

<–

RRCConnectionReconfiguration

14

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 11 using dedicated preamble to confirm the successful completion of the intra frequency handover?

Check2: Does the UE transmit an RRCConnectionReconfigurationComplete using the security key derived from the nextHopChainingCount?

–>

RRCConnectionReconfigurationComplete

1,2

P

14A

The UE transmit a TRACKING AREA UPDATE REQUEST message on Cell 11.

14B

  1. SS responds with a TRACKING AREA UPDATE ACCEPT message.

14C

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

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 11?

1

8.2.4.1.3.3 Specific message contents

Table 8.2.4.1.3.3-0: Conditions for specific message contents
in Table 8.2.4.1.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.1.3.3-2: MeasConfig (Table 8.2.4.1.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-NeedForGaps to TRUE.

Table 8.2.4.1.3.3-3: MeasurementReport (step 4, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 4

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.1.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

CEmodeA

CEmodeB

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 4

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.1.3.3-5: MobilityControlInfo (Table 8.2.4.1.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 4

carrierFreq

Not present

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.1.3.3-6: MeasurementReport (step 8, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.1.3.3-7: RRCConnectionReconfiguration (step 9, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

CEmodeA

CEmodeB

securityConfigHO

SecurityConfigHO

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 1

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.1.3.3-8: MobilityControlInfo (Table 8.2.4.1.3.3-7)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq

Not present

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.1.3.3-9: SecurityConfigHO (step 9, Table 8.2.4.1.3.3-7)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

intraLTE SEQUENCE {

nextHopChainingCount

2

}

}

}

Table 8.2.4.1.3.3-10: MeasurementReport (step 12, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measuredResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 11

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.1.3.3-11: RRCConnectionReconfiguration (step 13, Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

CEmodeA

CEmodeB

securityConfigHO

SecurityConfigHO

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 11

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.1.3.3-12: MobilityControlInfo (Table 8.2.4.1.3.3-11)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 11

carrierFreq

Not present

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

Table 8.2.4.1.3.3-13: SecurityConfigHO (Table 8.2.4.1.3.3-11)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

intraLTE SEQUENCE {

nextHopChainingCount

3

}

}

}

Table 8.2.4.1.3.3-14: RRCConnectionReconfiguration (step 6a1, step 10a1 Table 8.2.4.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.1.3.3-14: MeasConfig (Table 8.2.4.1.3.3-14)

Derivation Path: 36.331, clause 6.3.5

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToRemoveList

Not present

measObjectToAddModList

Not present

reportConfigToRemoveList

Not present

reportConfigToAddModList

Not present

measIdToRemoveList

Not present

measIdToAddModList

Not present

quantityConfig

Not present

measGapConfig

MeasGapConfig-CE

s-Measure

Not present

preRegistrationInfoHRPD

Not present

speedStatePars

Not present

}

Table 8.2.4.1.3.3-15: RadioResourceConfigDedicated-HO (Table 8.2.4.1.3.3-4), Table 8.2.4.1.3.3-7 , Table 8.2.4.1.3.3-11

Derivation Path: 36.508 Table 4.6.3-19

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-HO ::= SEQUENCE {

physicalConfigDedicated

PhysicalConfigDedicated-DEFAULT

}

Table 8.2.4.1.3.3-16: PhysicalConfigDedicated-DEFAULT(Table 8.2.4.1.3.3-15)

Derivation Path: 36.508 Table 4.6.3-2B

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated-DEFAULT ::= SEQUENCE {

epdcch-Config-r11

EPDCCH-Config-r11-DEFAULT with condition (CEmodeA OR CEmodeB)

}

8.2.4.2 RRC connection reconfiguration / Handover / Success / Common preamble

8.2.4.2.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the intra frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo without a rach-ConfigDedicated }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.2.3 Test description

8.2.4.2.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.2.4.2.3.2 Test procedure sequence

Table 8.2.4.2.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.2.4.2.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy exit condition for event A3 (M2 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1).

Table 8.2.4.2.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 setup intra frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.2.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 2.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 2 using common preamble to confirm the successful completion of the intra frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

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

8.2.4.2.3.3 Specific message contents

Table 8.2.4.2.3.3-0: Conditions for specific message contents
in Table 8.2.4.2.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.2.3.3-2: MeasConfig (Table 8.2.4.2.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-NeedForGaps to TRUE.

Table 8.2.4.2.3.3-3 MeasurementReport (step 4, Table 8.2.4.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.2.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.2.3.3-5: MobilityControlInfo (Table 8.2.4.2.3.3-4)

Derivation Path: 36.508 clause 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

8.2.4.3 RRC connection reconfiguration / Handover / Success / Intra-cell / Security reconfiguration

8.2.4.3.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a securityConfigHO }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.3.2 Conformance requirements

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

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the eutra-CarrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity; as the C-RNTI

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the configuration that do not require the UE to know the SFN of the target cell;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

2> the procedure ends;

8.2.4.3.3 Test description

8.2.4.3.3.1 Pre-test conditions

System Simulator:

– Cell 1.

UE:

None.

Preamble:

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

8.2.4.3.3.2 Test procedure sequence

Table 8.2.4.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an AUTHENTICATION REQUEST message to initiate the EPS authentication and AKA procedure.

<–

DLInformationTransfer

2

The UE transmits an AUTHENTICATION RESPONSE message and re-establishes mutual authentication.

–>

ULInformationTransfer

3

The SS transmits a NAS SECURITY MODE COMMAND message to reactivate NAS security.

<–

DLInformationTransfer

4

The UE transmits a NAS SECURITY MODE COMPLETE message and re-establishes the security configuration.

–>

ULInformationTransfer

5

The SS transmits an RRCConnectionReconfiguration message to perform intra cell handover and security reconfiguration.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message using the security key indicated by the keyChangeIndicator and nextHopChainingCount, as well as the indicated algorithms, to confirm the successful completion of the intra cell handover and security reconfiguration?

–>

RRCConnectionReconfigurationComplete

1

P

7

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?

1

8.2.4.3.3.3 Specific message contents

Table 8.2.4.3.3.3-1: RRCConnectionReconfiguration (step 5, Table 8.2.4.3.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

securityConfigHO

SecurityConfigHO

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 1

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.3.3.3-2: MobilityControlInfo (Table 8.2.4.3.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq

Not present

}

Table 8.2.4.3.3.3-3: SecurityConfigHO (Table 8.2.4.3.3.3-1)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

intraLTE SEQUENCE {

keyChangeIndicator

TRUE

nextHopChainingCount

0

}

}

}

8.2.4.4 RRC connection reconfiguration / Handover / Failure / Intra-cell / Security reconfiguration

8.2.4.4.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a SecurityConfigHO }

ensure that {
when { UE detects handover failure and the initial cell is selectable }

then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA RRC_CONNECTED state }

}

8.2.4.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.3, 5.3.5.4, 5.3.5.6, 5.3.7.4 and 5.3.7.5.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC Connection Re-establishment procedure:

2> re-establish PDCP for SRB2 and for all DRBs that are established, if any;

2> re-establish RLC for SRB2 and for all DRBs that are established, if any;

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

3> perform the radio resource configuration procedure as specified in 5.3.10;

2> resume SRB2 and all DRBs that are suspended, if any;

NOTE 1: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> if T304 expires (handover failure):

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

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

[TS 36.331, clause 5.3.7.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value ‘reconfigurationFailure’;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

2> else:

3> set the reestablishmentCause to the value ‘otherFailure’;

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

[TS 36.331, clause 5.3.7.5]

NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

8.2.4.4.3 Test description

8.2.4.4.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.2.4.4.3.2 Test procedure sequence

Table 8.2.4.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to perform intra cell handover and security reconfiguration.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 2 the steps specified in Table 8.2.4.4.3.2-2 should take place.

2

Wait for 1 s to ensure that T304 expires.

3

Check: Does the UE transmit an RRCConnectionReestablishmentRequest message?

–>

RRCConnectionReestablishmentRequest

1

P

4

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and reactivate security.

<–

RRCConnectionReestablishment

5

The UE transmits an RRCConnectionReestablishmentComplete message.

–>

RRCConnectionReestablishmentComplete

6

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

<–

RRCConnectionReconfiguration

7

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationComplete

8

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

1

Table 8.2.4.4.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the intra cell handover using MAC Random Access Preamble.

2

The SS does not respond.

8.2.4.4.3.3 Specific message contents

Table 8.2.4.4.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.4.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 1

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.4.3.3-2: MobilityControlInfo (Table 8.2.4.4.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq

Not present

}

Table 8.2.4.4.3.3-3: SecurityConfigHO (Table 8.2.4.4.3.3-1)

Derivation Path: 36.508, Table 4.6.4-1

Information Element

Value/remark

Comment

Condition

SecurityConfigHO ::= SEQUENCE {

handoverType CHOICE {

intraLTE SEQUENCE {

nextHopChainingCount

2

}

}

}

Table 8.2.4.4.3.3-4: RRCConnectionReestablishmentRequest (step 3, Table 8.2.4.4.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

handoverFailure

}

}

}

Table 8.2.4.4.3.3-5: RRCConnectionReconfiguration (step 6, Table 8.2.4.4.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

}

}

}

}

8.2.4.5 RRC connection reconfiguration / Handover / All parameters included

8.2.4.5.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the intra frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo is provided with all parameters included }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.5.3 Test description

8.2.4.5.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.2.4.5.3.2 Test procedure sequence

Table 8.2.4.5.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.2.4.5.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy exit condition for event A3 (M2 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1).

Table 8.2.4.5.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 setup intra frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the setup of intra frequency measurement.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.5.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ values for Cell 2.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 2 to confirm the successful completion of the intra frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

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

8.2.4.5.3.3 Specific message contents

Table 8.2.4.5.3.3-0: Conditions for specific message contents
in Tables 8.2.4.5.3.3-2 and 8.2.4.5.3.3-5

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.5.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.5.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.5.3.3-2: MeasConfig (Table 8.2.4.5.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-NeedForGaps to TRUE.

Table 8.2.4.5.3.3-3: MeasurementReport (step 4, Table 8.2.4.5.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.5.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.5.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.5.3.3-5: MobilityControlInfo (Table 8.2.4.5.3.3-4)

Derivation Path: 36.508 Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 2

ul-CarrierFreq

Same uplink EARFCN as used for Cell 2

FDD

ul-CarrierFreq

Not present

TDD

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 2

ul-CarrierFreq-v9e0

Same uplink EARFCN as used for Cell 2

FDD

ul-CarrierFreq-v9e0

Not present

TDD

}

carrierBandwidth SEQUENCE {

dl-Bandwidth

Same downlink system bandwidth as used for Cell 2

ul-Bandwidth

Same uplink system bandwidth as used for Cell 2

FDD

ul-Bandwidth

Not present

TDD

}

additionalSpectrumEmission

Same additionalSpectrumEmission as used for Cell 2

t304

ms1000

newUE-Identity

SS arbitrarily selects a value between ‘003C’H and ‘FFF2’H.

radioResourceConfigCommon SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

prach-Config

PRACH-Config-DEFAULT

pdsch-ConfigCommon

PDSCH-ConfigCommon-DEFAULT

pusch-ConfigCommon

PUSCH-ConfigCommon-DEFAULT

phich-Config

PHICH-Config-DEFAULT

pucch-ConfigCommon

PUCCH-ConfigCommon-DEFAULT

soundingRS-UL-ConfigCommon

SoundingRsUl-ConfigCommon-DEFAULT

uplinkPowerControlCommon

UplinkPowerControlCommon-DEFAULT

Prach-Config-v1310

PRACH-Config-v1310-DEFAULT

CEmodeA or CEmodeB

pdsch_ConfigCommon_v1310

PDSCH-ConfigCommon-v1310-DEFAULT

CEmodeA or CEmodeB

pucch_ConfigCommon_v1310

PUCCH-ConfigCommon-v1310-DEFAULT

CEmodeA or CEmodeB

pusch-ConfigCommon-v1310

PUSCH-ConfigCommon-v1310-DEFAULT

CEmodeA or CEmodeB

antennaInfoCommon SEQUENCE {

antennaPortsCount

an1

}

p-Max

Not present

tdd-Config

Not present

FDD

TDD-Config-DEFAULT

TDD

ul-CyclicPrefixLength

len1

}

rach-ConfigDedicated

Not present

}

Condition

Explanation

FDD

FDD cell environment

TDD

TDD cell environment

8.2.4.6 RRC connection reconfiguration / Handover / Success / Inter-frequency

8.2.4.6.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the inter frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA frequency}

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue’:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.6.3 Test description

8.2.4.6.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 3.

– 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.2.4.6.3.2 Test procedure sequence

Table 8.2.4.6.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.2.4.6.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

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 8.2.4.6.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 setup inter frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.6.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

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

1

8.2.4.6.3.3 Specific message contents

Table 8.2.4.6.3.3-0: Conditions for specific message contents
in Tables 8.2.4.6.3.3-2 and 8.2.4.6.3.3-5

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.6.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.6.3.3-2: MeasConfig (Table 8.2.4.6.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.6.3.3-3: MeasurementReport (step 4, Table 8.2.4.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.6.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.6.3.3-5: MobilityControlInfo (Table 8.2.4.6.3.3-5)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 3

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

ul-CarrierFreq-v9e0

Not present

}

}

8.2.4.7 RRC connection reconfiguration / Handover / Failure / Re-establishment successful

8.2.4.7.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA cell having attempted intra frequency handover }

ensure that {
when { UE detects handover failure and the initial cell is selectable }

then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA RRC_CONNECTED state }

}

(2)

with { UE having transmitted an RRCConnectionReestablishmentRequest message }

ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is different from the NCC associated with the currently active KeNB }

then { UE derives new KeNB from the nextHopChainingCount }

}

(3)

with { UE having transmitted an RRCConnectionReestablishmentRequest message }

ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is same as the NCC associated with the currently active KeNB }

then { UE derives new KeNB from the currently active KeNB }

}

8.2.4.7.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> if T304 expires (handover failure):

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

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

[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 handover failure, in accordance with 5.3.5.6; or

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.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value ‘reconfigurationFailure’;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

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

[TS 36.331, clause 5.3.7.5]

NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.7.3 Test description

8.2.4.7.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 4 and Cell 11.

UE:

None.

Preamble:

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

8.2.4.7.3.2 Test procedure sequence

Table 8.2.4.7.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", "T2", "T3", "T4", "T5" and "T6" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 4

Cell 11

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-91

The power level values are such that measurement results for Cell 1 (M1) Cell 4 (M4) and Cell 11(M11) satisfy exit condition for event A3 (M4 < M1 and M11 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 4 (M4) satisfy entry condition for event A3 (M4 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

"Off"

-79

"Off"

The power level values are assigned to satisfy SrxlevCell 1 < 0 and SrxlevCell 11 < 0 such that selecting Cell 4 is guaranteed

(NOTE 1).

T3

Cell-specific RS EPRE

dBm/15kHz

-73

-79

"Off"

The power level values are such that measurement results for Cell 1 (M1) and Cell 4 (M4) satisfy entry condition for event A3 (M1> M4).

(NOTE 1).

T4

Cell-specific RS EPRE

dBm/15kHz

-73

"Off"

"Off"

The power level values are assigned to satisfy SrxlevCell 4 < 0 and SrxlevCell 11 < 0 such that selecting Cell 1 is guaranteed.

(NOTE 1).

T5

Cell-specific RS EPRE

dBm/15kHz

-73

"Off"

-67

The power level values are such that measurement results for Cell 1 (M1) and Cell 11 (M11) satisfy entry condition for event A3 (M11> M1).

(NOTE 1).

T6

Cell-specific RS EPRE

dBm/15kHz

"Off"

"Off"

-67

The power level values are assigned to satisfy SrxlevCell 1 < 0 and SrxlevCell 4 < 0 such that selecting Cell 11 is guaranteed.

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.7.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T1" in table 8.2.4.7.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 4.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 4.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 6 the steps specified in Table 8.2.4.7.3.2-3 should take place.

6

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T2" in table 8.2.4.7.3.2-1.

7

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

–>

RRCConnectionReestablishmentRequest

1

P

8

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 4.

<–

RRCConnectionReestablishment

9

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the currently active KeNB on Cell 4?

–>

RRCConnectionReestablishmentComplete

3

P

10

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

<–

RRCConnectionReconfiguration

11

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 4.

–>

RRCConnectionReconfigurationtComplete

12

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T3" in table 8.2.4.7.3.2-1.

13

The UE transmits a MeasurementReport message on Cell 4 to report event A3 with the measured RSRP, RSRQ value for Cell 1.

–>

MeasurementReport

14

The SS transmits an RRCConnectionReconfiguration message on Cell 4 to order the UE to perform intra frequency handover to Cell 1.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 15 the steps specified in Table 8.2.4.7.3.2-4 should take place.

15

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T4" in table 8.2.4.7.3.2-1.

16

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

–>

RRCConnectionReestablishmentRequest

1

P

17

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 1.

<–

RRCConnectionReestablishment

18

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the nextHopChainingCount on Cell 1?

–>

RRCConnectionReestablishmentComplete

2

P

19

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

<–

RRCConnectionReconfiguration

20

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationtComplete

21

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T5" in table 8.2.4.7.3.2-1.

22

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 11.

–>

MeasurementReport

23

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 11.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 24 the steps specified in Table 8.2.4.7.3.2-5 should take place.

24

The SS changes Cell 1, Cell 4 and Cell 11 parameters according to the row "T6" in table 8.2.4.7.3.2-1.

25

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

–>

RRCConnectionReestablishmentRequest

1

P

26

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 11.

<–

RRCConnectionReestablishment

27

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the nextHopChainingCount on Cell 11?

–>

RRCConnectionReestablishmentComplete

2

P

28

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

<–

RRCConnectionReconfiguration

29

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 11.

–>

RRCConnectionReconfigurationtComplete

29A

The UE transmit a TRACKING AREA UPDATE REQUEST message on Cell 11.

29B

SS responds with TRACKING AREA UPDATE ACCEPT message.

29C

The UE transmits a TRACKING AREA UPDATE COMPLETE.

30

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 11?

1

Table 8.2.4.7.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 4.

2

The SS does not respond.

Table 8.2.4.7.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 1.

2

The SS does not respond.

Table 8.2.4.7.3.2-5: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 11.

2

The SS does not respond.

8.2.4.7.3.3 Specific message contents

Table 8.2.4.7.3.3-0: Conditions for specific message contents
in Table 8.2.4.7.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.7.3.3-0: SystemInformationBlockType2 for Cell 1, cell 4 and Cell 11 (preamble and all the steps in Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n50

}

Table 8.2.4.7.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.7.3.3-2: MeasConfig (Table 8.2.4.7.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-NeedForGaps to TRUE.

Table 8.2.4.7.3.3-3: MeasurementReport (step 4, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 4

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.7.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 4

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.7.3.3-5: MobilityControlInfo (Table 8.2.4.7.3.3-4)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 4

carrierFreq

Not present

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.7.3.3-6: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.7.3.2-2)

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

handoverFailure

}

}

}

Table 8.2.4.7.3.3-7: RRCConnectionReestablishment (step 8, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-10

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishment ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReestablishment-r8 SEQUENCE {

nextHopChainingCount

0

}

}

}

}

Table 8.2.4.7.3.3-8: RRCConnectionReconfiguration (step 28, Table 8.2.4.7.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

RadioResourceConfigDedicated-HO

}

}

}

}

Table 8.2.4.7.3.3-8A: RRCConnectionReconfiguration (step 10, step 19 Table 8.2.4.7.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 {

measConfig

MeasConfig-Gap

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

}

}

}

}

Table 8.2.4.7.3.3-8B: MeasConfig-Gap (Table 8.2.4.7.3.3-8A)

Derivation Path: 36.331, clause 6.3.5

Information Element

Value/remark

Comment

Condition

MeasConfig-Gap ::= SEQUENCE {

measObjectToRemoveList

Not present

measObjectToAddModList

Not present

reportConfigToRemoveList

Not present

reportConfigToAddModList

Not present

measIdToRemoveList

Not present

measIdToAddModList

Not present

quantityConfig

Not present

measGapConfig

MeasGapConfig-CE

s-Measure

Not present

preRegistrationInfoHRPD

Not present

speedStatePars

Not present

}

Table 8.2.4.7.3.3-9: MeasurementReport (step 13, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.7.3.3-10: RRCConnectionReconfiguration (step 14, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 1

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.7.3.3-11: MobilityControlInfo (Table 8.2.4.7.3.3-10)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq

Not present

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.7.3.3-12: RRCConnectionReestablishmentRequest (step 16, Table 8.2.4.7.3.2-2)

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 4

shortMAC-I

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

calculated by SS.

}

reestablishmentCause

handoverFailure

}

}

}

Table 8.2.4.7.3.3-13: RRCConnectionReestablishment (step 17, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-10

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishment ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReestablishment-r8 SEQUENCE {

nextHopChainingCount

2

}

}

}

}

Table 8.2.4.7.3.3-14: MeasurementReport (step 22, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 11

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.7.3.3-15: RRCConnectionReconfiguration (step 23, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 11

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.7.3.3-16: MobilityControlInfo (Table 8.2.4.7.3.3-15)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 11

carrierFreq

Not present

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.7.3.3-17: RRCConnectionReestablishmentRequest (step 25, Table 8.2.4.7.3.2-2)

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

handoverFailure

}

}

}

Table 8.2.4.7.3.3-18: RRCConnectionReestablishment (step 26, Table 8.2.4.7.3.2-2)

Derivation Path: 36.508, Table 4.6.1-10

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishment ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReestablishment-r8 SEQUENCE {

nextHopChainingCount

3

}

}

}

}

8.2.4.8 RRC connection reconfiguration / Handover / Failure / Re-establishment failure

8.2.4.8.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including an IE mobilityControlInformation indicating a different E-UTRA cell having attempted intra frequency handover }

ensure that {

when { UE detects handover failure and fails an RRC connection re-establishment procedure }

then { UE enters the E-UTRA RRC_IDLE state and trigger TAU procedure in order to recover RRC connection }

}

8.2.4.8.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInformation and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInformation;

1> request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in [8].

1> reset MAC and re-establish RLC for all RBs that are established;

1> If the RRCConnectionReconfiguration message includes the radioResourceConfiguration:

2> perform the Radio resource configuration procedure as specified in 5.3.10;

1> set the C-RNTI to the value of the newUE-Identity;

1> if the eutra-CarrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the eutra-CarrierFreq with a physical cell identity indicated by the targetCellIdentity;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetCellIdentity;

1> if the dl-Bandwidth is included:

2> for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;

1> else:

2> for the target cell, apply the same downlink bandwidth as for the current cell;

1> if the ul-Bandwidth is included:

2> for the target cell, apply the uplink bandwidth indicated by the ul-Bandwidth;

1> else:

2> for the target cell, apply the same uplink bandwidth as for the current cell;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> If the RRCConnectionReconfiguration message includes the securityConfiguration:

2> apply the AS-derived keys associated with the AS-base key indicated by the keyIndicator;

2> configure lower layers to apply the indicated integrity protection algorithm, i.e. the indicated integrity protection configuration shall be applied to all subsequent messages received and sent by the UE in the target cell, including the message used to indicate the successful completion of the procedure;

2> configure lower layers to apply the indicated ciphering algorithm, i.e. the indicated ciphering configuration shall be applied to all subsequent messages received and sent by the UE in the target cell, including the message used to indicate the successful completion of the procedure;

1> If the RRCConnectionReconfiguration message includes the measurementConfiguration:

2> perform the Measurement configuration procedure as specified in 5.5.2;

1> synchronise to the DL of the target cell;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration;

1> If MAC successfully completes the random access procedure:

2> stop timer T304;

2> If the physicalConfigDedicated is included in the RRCConnectionReconfiguration message:

3> If the UE needs the SFN of the target cell to apply the PUCCH and Sounding RS configuration:

4> apply the new PUCCH and Sounding RS configuration upon acquiring the SFN of the target cell;

3> else:

4> apply the new PUCCH and Sounding RS configuration;

2> indicate to PDCP to complete the PDCP Re-establishment procedure for all DRBs that are established, if any;

2> the procedure ends.

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> If T304 expires (handover failure):

NOTE 1: Following T304 expiry dedicated preambles, if provided within the rach-ConfigDedicated, are not available for use by the UE anymore.

2> revert back to the configuration used in the source cell, excluding the physical layer configuration;

NOTE 2: The UE reverts to the RRC configuration as well as the layer 2 configuration (PDCP/RLC/MAC) used in the source cell.

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends.

[TS 36.331, clause 5.3.7.2]

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

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

Upon initiation of the procedure, the UE shall:

1> start timer T311;

1> request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;

NOTE 1: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in [8].

1> reset MAC and re-establish RLC for all RBs that are established;

1> select a suitable cell in accordance with the cell selection process as specified in [4];

[TS 36.331, clause 5.3.7.3]

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

[TS 36.331, clause 5.3.7.4]

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

1> set the IE ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover failure case) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the cellIdentity to the Physical layer identity of the source cell (handover failure case) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the concatenation of the ASN.1 encoded CellIdentity of the current cell, PhysicalCellIdentity of the cell the UE was connected to prior to the failure and C-RNTI that the UE had in the cell it was connected to prior to the failure;

3> with the integrity protection key and integrity protection algorithm that was used in the cell the UE was connected to prior to the failure; and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones.

1> set the IE reestablishmentCause as follows:

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

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

[TS 36.331, clause 5.3.7.7]

Upon T311 expiry, the UE shall:

1> perform the actions upon moving from RRC_CONNECTED to RRC_IDLE as specified in 5.3.12.

[TS 36.331, clause 5.3.12]

Upon moving from RRC_CONNECTED to RRC_IDLE, the UE shall:

1> reset MAC and re-establish RLC for all RBs that are established;

1> stop all timers that are running except T320;

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

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

1> enter RRC_IDLE.

8.2.4.8.3 Test description

8.2.4.8.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.2.4.8.3.2 Test procedure sequence

Table 8.2.4.8.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, while columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M1 > M2)

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1)

T2

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

The power level values are such that SrxlevCell 1 > SrxlevCell 2 and SrxlevCell 2 <0.(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.8.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup intra frequency measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.8.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 2.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 6 the steps specified in Table 8.2.4.8.3.2-3 should take place.

6

The SS changes Cell 1 and Cell 2 parameters according to the row "T2" in table 8.2.4.8.3.2-1.

7

The UE transmits an RRCConnectionReestablishmentRequest message on Cell 1.

–>

RRCConnectionReestablishmentRequest

8

The SS does not respond to any RRCConnectionReestablishmentRequest message and waits for 1s to ensure that T301 expires and the UE goes to RRC_IDLE state on Cell 1.

9-13

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

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

14

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

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

Table 8.2.4.8.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304

1

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 2

2

The SS does not respond.

8.2.4.8.3.3 Specific message contents

Table 8.2.4.8.3.3-0: Conditions for specific message contents
in Table 8.2.4.8.3.3-1A

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.8.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.8.3.2-2)

Derivation path: 36.508 Table 4.6.1-8, condition MEAS

Table 8.2.4.8.3.3-1A: MeasConfig (Table 8.2.4.8.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-NeedForGaps to TRUE.

Table 8.2.4.8.3.3-2: MeasurementReport (step 4, Table 8.2.4.8.3.2-2)

Derivation path: 36.508 Table 4.6.1-5

Information Element

Value/Remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.8.3.3-3: RRCConnectionReconfiguration (step 5, Table 8.2.4.8.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension ::= SEQUENCE {

CEmodeA

CEmodeB

lateNonCriticalExtension

Not present

nonCriticalExtension ::= SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension ::= SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

Not present

nonCriticalExtension ::= SEQUENCE {

systemInformationBlockType1Dedicated-r11

SystemInformationBlockType1-BR-r13 of Cell 2

nonCriticalExtension

Not present

}

}

}

}

}

}

}

}

Table 8.2.4.8.3.3-3A: MobilityControlInfo (Table 8.2.4.8.3.3-3)

Derivation Path: 36.508 Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

Table 8.2.4.8.3.3-4: Void

Table 8.2.4.8.3.3-5: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.8.3.2-2)

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

handoverFailure

}

}

}

8.2.4.9 RRC connection reconfiguration / Handover / Inter-band blind handover / Success

8.2.4.9.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating an E-UTRA frequency on different frequency band }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.9.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.9.3 Test description

8.2.4.9.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 10.

– 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.2.4.9.3.2 Test procedure sequence

Table 8.2.4.9.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter band handover to Cell 10.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 10?

–>

RRCConnectionReconfigurationComplete

1

P

3

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 10?

1

8.2.4.9.3.3 Specific message contents

Table 8.2.4.9.3.3-0: Conditions for specific message contents
in Table 8.2.4.9.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.9.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.9.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.9.3.3-2: MobilityControlInfo (Table 8.2.4.9.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 10

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 10

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq-v9e0

Not present

}

}

8.2.4.10 RRC connection reconfiguration / Handover (between FDD and TDD)

8.2.4.10.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure in FDD mode}

ensure that {
when { UE receives an RRCConnectionReconfiguration message including an IE mobilityControlInformation with TDD configuration parameters included }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE having completed the radio bearer establishment and initial security activation procedure in TDD mode}

ensure that {
when { UE receives an RRCConnectionReconfiguration message including an IE mobilityControlInformation with FDD configuration parameters included }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.10.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target cell by acquiring system information from that cell before performing RACH access in the target cell.

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.10.3 Test description

8.2.4.10.3.1 Pre-test conditions

System Simulator:

– Cell 1 in FDD and Cell 10 in TDD

– 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.2.4.10.3.2 Test procedure sequence

Table 8.2.4.10.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including TDD-Config to order the UE to perform inter band handover to Cell 10.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 10?

–>

RRCConnectionReconfigurationComplete

1

P

3

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 10?

1

4

The SS transmits an RRCConnectionReconfiguration message without including TDD-Config to order the UE to perform inter band handover to Cell 1.

<–

RRCConnectionReconfiguration

5

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

–>

RRCConnectionReconfigurationComplete

2

P

6

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?

2

8.2.4.10.3.3 Specific message content

Table 8.2.4.10.3.3-0: Conditions for specific message contents
in Tables 8.2.4.10.3.3-2 and 8.2.4.10.3.3-4

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.10.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.10.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.10.3.3-2: MobilityControlInfo (Table 8.2.4.10.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo-HO ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 10

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 10

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq-v9e0

Not present

}

carrierBandwidth SEQUENCE {

dl-Bandwidth

Same downlink system bandwidth as used for Cell 10

ul-Bandwidth

Not present

}

additionalSpectrumEmission

Same additionalSpectrumEmission as used for Cell 10

radioResourceConfigCommon

RadioResourceConfigCommon-withTDDconfig

}

Table 8.2.4.10.3.3-2A: RadioResourceConfigCommon-withTDDconfig (Table 8.2.4.10.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

tdd-Config

TDD-Config-DEFAULT

}

Table 8.2.4.10.3.3-3: RRCConnectionReconfiguration (step 4, Table 8.2.4.10.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.10.3.3-4: MobilityControlInfo (Table 8.2.4.10.3.3-3)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo-HO ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq

Same uplink EARFCN as used for Cell 1

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq-v9e0

Same uplink EARFCN as used for Cell 1

}

carrierBandwidth SEQUENCE {

dl-Bandwidth

Same downlink system bandwidth as used for Cell 1

ul-Bandwidth

Same uplink system bandwidth as used for Cell 1

}

additionalSpectrumEmission

Same additionalSpectrumEmission as used for Cell 1

radioResourceConfigCommon

RadioResourceConfigCommon-withoutTDDconfig

}

Table 8.2.4.10.3.3-5: RadioResourceConfigCommon-withoutTDDconfig (Table 8.2.4.10.3.3-4)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

tdd-Config

Not present

}

8.2.4.11 Void

8.2.4.12 RRC connection reconfiguration / Handover / Setup and release of MIMO

8.2.4.12.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a cell with 2 antenna ports }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE having completed the radio bearer establishment and initial security activation procedure }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a cell with 1 antenna port }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.12.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323.

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target cell by acquiring system information from that cell before performing RACH access in the target cell.

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ or ‘tm8‘:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

2> if the configured transmissionMode is ‘tm8‘ and pmi-RI-Report is not present:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.12.3 Test description

8.2.4.12.3.1 Pre-test conditions

System Simulator:

  • Cell 1 and Cell 2 (2 antenna ports MIMO)

UE:

None.

Preamble:

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

8.2.4.12.3.2 Test procedure sequence

Table 8.2.4.12.3.2-0 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.2.4.12.3.2-0: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

T0

Cell-specific RS EPRE

dBm/15kHz

-91

-85

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-91

Table 8.2.4.12.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

2

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

–>

RRCConnectionReconfigurationComplete

1

P

3

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

3A

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.12.3.2-0.

4

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 1.

<–

RRCConnectionReconfiguration

5

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

–>

RRCConnectionReconfigurationComplete

2

P

6

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?

2

8.2.4.12.3.3 Specific message content

Table 8.2.4.12.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.4.2.12.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.12.3.3-2: MobilityControlInfo (Table 8.2.4.12.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo-HO ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

}

Table 8.2.4.12.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.12.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13, condition 2TX

Table 8.2.4.12.3.3-4: RRCConnectionReconfiguration (step 4, Table 8.4.2.12.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.12.3.3-5: MobilityControlInfo (Table 8.2.4.12.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq

Not present

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

}

Table 8.2.4.12.3.3-6: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.12.3.3-5)

Derivation Path: 36.508, Table 4.6.3-1

Information Element

Value/remark

Comment

Condition

antennaInfoCommon SEQUENCE {

antennaPortsCount

an1

}

8.2.4.13 RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band

8.2.4.13.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the inter-band measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating an E-UTRA frequency on different frequency band }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.13.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ or ‘tm8‘:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

2> if the configured transmissionMode is ‘tm8‘ and pmi-RI-Report is not present:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.13.3 Test description

8.2.4.13.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 10.

– 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.2.4.13.3.2 Test procedure sequence

Table 8.2.4.13.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.2.4.13.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 10

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy exit condition for event A3 (M10 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M10 > M1).

Table 8.2.4.13.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 setup inter-band measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

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

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 10.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 10.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 10 to confirm the successful completion of the inter-band handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

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

1

8.2.4.13.3.3 Specific message contents

Table 8.2.4.13.3.3-0: Conditions for specific message contents
in Tables 8.2.4.13.3.3-2 and 8.2.4.13.3.3-5

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.13.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.13.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.13.3.3-2: MeasConfig (Table 8.2.4.13.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f5

measObject[2]

MeasObjectEUTRA-GENERIC(f5)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f5

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f5

}

}

}

Table 8.2.4.13.3.3-3: MeasurementReport (step 4, Table 8.2.4.13.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 10

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

}

}

}

}

}

Table 8.2.4.13.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.13.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.13.3.3-5: MobilityControlInfo (Table 8.2.4.13.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 10

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 10

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq-v9e0

Not present

}

}

8.2.4.13a RRC connection reconfiguration / Handover / Success (with measurement) / Inter-band / Between FDD and TDD

8.2.4.13a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA FDD RRC_CONNECTED state and having completed the radio bearer establishment and initial security activation procedure and performed the inter band LTE TDD measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA TDD frequency }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA TDD RRC_CONNECTED state and having completed the radio bearer establishment and initial security activation procedure and performed the inter band LTE FDD measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA FDD frequency }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.13a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue’:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.13a.3 Test description

8.2.4.13a.3.1 Pre-test conditions

System Simulator:

– Cell 1 is FDD cell and Cell 28 is TDD cell.

– Each cell has only a single PLMN identity. The PLMNs are identified in the test by the identifiers in Table 8.2.4.13a.3.1-1.

Table 8.2.4.13a.3.1-1: PLMN identifiers

Cell

PLMN name

1

PLMN1

28

PLMN2

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

UE:

None.

Preamble:

– The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508[18] clause 4.5.2.3 except that the ATTACH ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described in Table 8.2.4.13a.3.3-9.

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

8.2.4.13a.3.2 Test procedure sequence

Table 8.2.4.13a.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.2.4.13a.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 28

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 28 (M28) satisfy exit condition for event A3 (M28 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 28 (M28) satisfy entry condition for event A3 (M28 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

-73

-85

The power level values are such that measurement results for Cell 1 (M1) and Cell 28 (M28) satisfy entry condition for event A3 (M1 > M28).

Table 8.2.4.13a.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 setup inter band measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 28 power level according to the row "T1" in table 8.2.4.13a.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ values for Cell 28.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter band handover to Cell 28.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 28 to confirm the successful completion of the inter band handover?

–>

RRCConnectionReconfigurationComplete

1

P

6A

The UE transmits a TRACKING AREA UPDATE REQUEST message on Cell 28.

6B

SS responds with a TRACKING AREA UPDATE ACCEPT message.

NOTE: The TAU is accepted with PLMN1 listed as an Equivalent PLMN.

6C

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

7

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 28?

1

8

The SS transmits an RRCConnectionReconfiguration message on Cell 28 to setup inter band measurement.

<–

RRCConnectionReconfiguration

9

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 28.

–>

RRCConnectionReconfigurationComplete

10

The SS changes Cell 1 and Cell 28 power levels according to the row "T2" in table 8.2.4.13a.3.2-1.

11

The UE transmits a MeasurementReport message on Cell 28 to report event A3 with the measured RSRP, RSRQ values for Cell 1.

–>

MeasurementReport

12

The SS transmits an RRCConnectionReconfiguration message on Cell 28 to order the UE to perform inter band handover to Cell 1.

<–

RRCConnectionReconfiguration

13

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the successful completion of the inter band handover?

–>

RRCConnectionReconfigurationComplete

2

P

13A

The UE transmits a TRACKING AREA UPDATE REQUEST message on Cell 1.

13B

SS responds with a TRACKING AREA UPDATE ACCEPT message.

NOTE: The TAU is accepted with PLMN2 listed as an Equivalent PLMN.

13C

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

14

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

2

8.2.4.13a.3.3 Specific message contents

Table 8.2.4.13a.3.3-0: Conditions for specific message contents
in Tables 8.2.4.13a.3.3-2, 8.2.4.13a.3.3-5, 8.2.4.13a.3.3-6 and 8.2.4.13a.3.3-8

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.13a.3.3-1: RRCConnectionReconfiguration (step 1 and step 8, Table 8.2.4.13a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.13a.3.3-2: MeasConfig (step 1, Table 8.2.4.13a.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f6

measObject[2]

MeasObjectEUTRA-GENERIC(f6)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f6

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f6

}

}

}

Table 8.2.4.13a.3.3-3: MeasurementReport (step 4, Table 8.2.4.13a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 28

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.13a.3.3-4: RRCConnectionReconfiguration (step 5 and step 12, Table 8.2.4.13a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.13a.3.3-5: MobilityControlInfo (step 5, Table 8.2.4.13a.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 28

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 28

ul-CarrierFreq

Not present

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 28

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.13a.3.3-6: MeasConfig (step 8, Table 8.2.4.13a.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entry

measObjectId[1]

IdMeasObject-f6

measObject[1]

MeasObjectEUTRA-GENERIC(f6)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f1

measObject[2]

MeasObjectEUTRA-GENERIC(f1)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f6

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 8.2.4.13a.3.3-7: MeasurementReport (step 11, Table 8.2.4.13a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 28

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.13a.3.3-8: MobilityControlInfo (step 12, Table 8.2.4.13a.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 1

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.13a.3.3-9: ATTACH ACCEPT for Cell 1 (preamble)

Derivation path: 36.508 Table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN2

Table 8.2.4.13a.3.3-10: TRACKING AREA UPDATE ACCEPT for Cell 28 (step 6B, Table 8.2.4.13a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN1

Table 8.2.4.13a.3.3-11: TRACKING AREA UPDATE ACCEPT for Cell 1 (step 13B, Table 8.2.4.13a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN2

8.2.4.14 RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Inter-band

8.2.4.14.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA cell having attempted inter-band handover }

ensure that {
when { UE detects handover failure and the target cell is selectable }

then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA RRC_CONNECTED state }

}

8.2.4.14.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> if T304 expires (handover failure):

NOTE 4: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not available for use by the UE anymore.

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

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

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

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes 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 handover failure;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

[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 handover failure, in accordance with 5.3.5.6; or

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> release reportProximityConfig and clear any associated proximity status reporting timer;

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.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value ‘reconfigurationFailure’;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

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

[TS 36.331, clause 5.3.7.5]

NOTE 5: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

NOTE 6: E-UTRAN should not transmit any message on SRB1 prior to receiving the RRCConnectionReestablishmentComplete message.

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> set the content of RRCConnectionReestablishmentComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3> include the rlf-InfoAvailable;

1> perform the measurement related actions as specified in 5.5.6.1;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ or ‘tm8‘:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

2> if the configured transmissionMode is ‘tm8‘ and pmi-RI-Report is not present:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.14.3 Test description

8.2.4.14.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 10.

– 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.2.4.14.3.2 Test procedure sequence

Table 8.2.4.14.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" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 10

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy exit condition for event A3 (M10 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M10 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

"Off"

-79

The power level values are assigned to satisfy SrxlevCell 1 < 0 such that selecting Cell 10 is guaranteed

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.14.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter-band measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

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

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 10.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 10.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 6 the steps specified in Table 8.2.4.14.3.2-3 should take place.

6

The SS changes Cell 1 and Cell 10 parameters according to the row "T2" in table 8.2.4.14.3.2-1.

7

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

–>

RRCConnectionReestablishmentRequest

1

P

8

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 10.

<–

RRCConnectionReestablishment

9

The UE transmits an RRCConnectionReestablishmentComplete message on Cell 10.

–>

RRCConnectionReestablishmentComplete

10

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

<–

RRCConnectionReconfiguration

11

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 10.

–>

RRCConnectionReconfigurationtComplete

12

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 10?

1

Table 8.2.4.14.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the inter-band handover using MAC Random Access Preamble on Cell 10.

2

The SS does not respond.

8.2.4.14.3.3 Specific message contents

Table 8.2.4.14.3.3-0: Conditions for specific message contents
in Tables 8.2.4.14.3.3-3 and 8.2.4.14.3.3-6

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.14.3.3-1: SystemInformationBlockType2 for Cell 10 (preamble and all the steps in Table 8.2.4.14.3.2-2)

Derivation Path: 36.508, Table 4.4.3.3-1

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType2 ::= SEQUENCE {

radioResourceConfigCommon SEQUENCE {

rach-ConfigCommon SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n50

}

}

}

lateNonCriticalExtension

Not present

ssac-BarringForMMTEL-Voice-r9

Not present

ssac-BarringForMMTEL-Video-r9

Not present

}

Table 8.2.4.14.3.3-2: RRCConnectionReconfiguration (step 1, Table 8.2.4.14.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.14.3.3-3: MeasConfig (Table 8.2.4.14.3.3-2)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f5

measObject[2]

MeasObjectEUTRA-GENERIC(f5)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f5

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f5

}

}

}

Table 8.2.4.14.3.3-4: MeasurementReport (step 4, Table 8.2.4.14.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 10

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

}

}

}

}

}

Table 8.2.4.14.3.3-5: RRCConnectionReconfiguration (step 5, Table 8.2.4.14.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.14.3.3-6: MobilityControlInfo (Table 8.2.4.14.3.3-5)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 10

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 10

Band 24 High range

}

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.14.3.3-7: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.14.3.2-2)

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

handoverFailure

}

}

}

Table 8.2.4.14.3.3-8: RRCConnectionReestablishmentComplete (step 9, Table 8.2.4.14.3.2-2)

Derivation Path: 36.508, Table 4.6.1-11

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentComplete ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentComplete-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {}

Not present

Rel-8

nonCriticalExtension SEQUENCE {}

Not checked

Rel-9

nonCriticalExtension SEQUENCE {

Rel-10 and above

rlf-InfoAvailable-r9

true

nonCriticalExtension

Not present

}

}

}

}

Table 8.2.4.14.3.3-9: RRCConnectionReconfiguration (step 10, Table 8.2.4.14.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

RadioResourceConfigDedicated-HO

}

}

}

}

8.2.4.14a RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Inter-band / Between FDD and TDD

8.2.4.14a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA FDD RRC_CONNECTED state and having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA TDD cell having attempted inter-mode handover }

ensure that {

when { UE detects handover failure and the initial E-UTRA TDD cell is selectable }

then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA RRC_CONNECTED state on the E-UTRA TDD cell }

}

(2)

with { UE in E-UTRA FDD RRC_CONNECTED state and having transmitted an RRCConnectionReestablishmentRequest message on E-UTRA TDD cell }

ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is same as the NCC associated with the currently active KeNB }

then { UE derives new KeNB from the currently active KeNB }

}

(3)

with { UE in E-UTRA TDD RRC_CONNECTED state and having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA FDD cell having attempted inter-mode handover }

ensure that {
when { UE detects handover failure and the initial E-UTRA FDD cell is selectable }

then { UE performs an RRC connection re-establishment procedure and remains in the E-UTRA RRC_CONNECTED state on the E-UTRA FDD cell }

}

(4)

with { UE in E-UTRA TDD RRC_CONNECTED state and having transmitted an RRCConnectionReestablishmentRequest message on E-UTRA FDD cell }

ensure that {
when { UE receives an RRCConnectionReestablishment message with a nextHopChainingCount which is different from the NCC associated with the currently active KeNB }

then { UE derives new KeNB from the nextHopChainingCount }

}

8.2.4.14a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> if T304 expires (handover failure):

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

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

[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 handover failure, in accordance with 5.3.5.6; or

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.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value ‘reconfigurationFailure’;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

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

[TS 36.331, clause 5.3.7.5]

NOTE 5: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

NOTE 6: E-UTRAN should not transmit any message on SRB1 prior to receiving the RRCConnectionReestablishmentComplete message.

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> set the content of RRCConnectionReestablishmentComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3> include the rlf-InfoAvailable;

1> perform the measurement related actions as specified in 5.5.6.1;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.14a.3 Test description

8.2.4.14a.3.1 Pre-test conditions

System Simulator:

– Cell 1 is FDD cell and Cell 28 is TDD cell.

– Cell 28 has a valid UE context

– Each cell has only a single PLMN identity. The PLMNs are identified in the test by the identifiers in Table 8.2.4.14a.3.1-1.

Table 8.2.4.14a.3.1-1: PLMN identifiers

Cell

PLMN name

1

PLMN1

28

PLMN2

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

UE:

None.

Preamble:

– The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508[18] clause 4.5.2.3 except that the ATTACH ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described in Table 8.2.4.14a.3.3-15.

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

8.2.4.14a.3.2 Test procedure sequence

Table 8.2.4.14a.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", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.4.14a.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 28

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 28 (M28) satisfy exit condition for event A3 (M28 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 28 (M28) satisfy entry condition for event A3 (M28 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

"Off"

-73

The power level values are assigned to satisfy SrxlevCell 1 < 0 such that selecting Cell 28 is guaranteed

(NOTE 1).

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 28 (M28) satisfy entry condition for event A3 (M1> M28).

T4

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

The power level values are assigned to satisfy SrxlevCell 28 < 0 such that selecting Cell 1 is guaranteed.

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.14a.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter-band measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 28 power level according to the row "T1" in table 8.2.4.14a.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 28.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 28.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 6 the steps specified in Table 8.2.4.14a.3.2-3 should take place.

6

The SS changes Cell 1 power level according to the row "T2" in table 8.2.4.14a.3.2-1.

7

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

–>

RRCConnectionReestablishmentRequest

1

P

8

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 28.

<–

RRCConnectionReestablishment

9

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the currently active KeNB on Cell 28?

–>

RRCConnectionReestablishmentComplete

2

P

10

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

<–

RRCConnectionReconfiguration

11

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 28.

–>

RRCConnectionReconfigurationtComplete

11A

The UE transmits a TRACKING AREA UPDATE REQUEST message on Cell 28.

11B

SS responds with a TRACKING AREA UPDATE ACCEPT message.

NOTE: The TAU is accepted with PLMN1 listed as an Equivalent PLMN

11C

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

12

The SS changes Cell 1 and Cell 28 power levels according to the row "T3" in table 8.2.4.14a.3.2-1.

13

The UE transmits a MeasurementReport message on Cell 28 to report event A3 with the measured RSRP, RSRQ value for Cell 1.

–>

MeasurementReport

14

The SS transmits an RRCConnectionReconfiguration message on Cell 28 to order the UE to perform inter-band handover to Cell 1.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 15 the steps specified in Table 8.2.4.14a.3.2-4 should take place.

15

The SS changes Cell 28 power level according to the row "T4" in table 8.2.4.14a.3.2-1.

16

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

–>

RRCConnectionReestablishmentRequest

3

P

17

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 1.

<–

RRCConnectionReestablishment

18

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the nextHopChainingCount on Cell 1?

–>

RRCConnectionReestablishmentComplete

4

P

19

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

<–

RRCConnectionReconfiguration

20

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationtComplete

20A

The UE transmits a TRACKING AREA UPDATE REQUEST message on Cell 1.

20B

SS responds with a TRACKING AREA UPDATE ACCEPT message.

NOTE: The TAU is accepted with PLMN2 listed as an Equivalent PLMN

20C

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

21

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?

3

Table 8.2.4.14a.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the inter-band handover using MAC Random Access Preamble on Cell 28.

2

The SS does not respond.

Table 8.2.4.14a.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the inter-band handover using MAC Random Access Preamble on Cell 1.

2

The SS does not respond.

8.2.4.14a.3.3 Specific message contents

Table 8.2.4.14a.3.3-00: Conditions for specific message contents
in Tables 8.2.4.14a.3.3-2, 8.2.4.14a.3.3-5 and 8.2.4.14a.3.3-12

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.14a.3.3-0: SystemInformationBlockType2 for Cell 1 and Cell 28 (preamble and all the steps in Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n50

}

Table 8.2.4.14a.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.14a.3.3-2: MeasConfig (Table 8.2.4.14a.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f6

measObject[2]

MeasObjectEUTRA-GENERIC(f6)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f6

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f6

}

}

}

Table 8.2.4.14a.3.3-3: MeasurementReport (step 4, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 28

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.14a.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.14a.3.3-5: MobilityControlInfo (Table 8.2.4.14a.3.3-4)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 28

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 28

ul-CarrierFreq

Not present

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 28

ul-CarrierFreq-v9e0

Not present

}

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.14a.3.3-6: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.14a.3.2-2)

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

handoverFailure

}

}

}

Table 8.2.4.14a.3.3-7: RRCConnectionReestablishment (step 8, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-10

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishment ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReestablishment-r8 SEQUENCE {

nextHopChainingCount

0

}

}

}

}

Table 8.2.4.14a.3.3-7A: RRCConnectionReestablishmentComplete (step 9 and step 18, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-11

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishmentComplete ::= SEQUENCE {

criticalExtensions CHOICE {

rrcConnectionReestablishmentComplete-r8 = SEQUENCE {

nonCriticalExtension SEQUENCE {}

Not present

Rel-8

nonCriticalExtension SEQUENCE {}

Not checked

Rel-9

nonCriticalExtension SEQUENCE {

Rel-10 and above

rlf-InfoAvailable-r9

true

nonCriticalExtension

Not present

}

}

}

}

Table 8.2.4.14a.3.3-8: RRCConnectionReconfiguration (step 10 and step 19, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-HO

}

}

}

}

Table 8.2.4.14a.3.3-9: MeasConfig (Table 8.2.4.14a.3.3-8)

Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ

Table 8.2.4.14a.3.3-10: MeasurementReport (step 13, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 28

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.14a.3.3-11: RRCConnectionReconfiguration (step 14, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.14a.3.3-12: MobilityControlInfo (Table 8.2.4.14a.3.3-11)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 1

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.14a.3.3-13: RRCConnectionReestablishmentRequest (step 16, Table 8.2.4.14a.3.2-2)

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 28

shortMAC-I

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

calculated by SS.

}

reestablishmentCause

handoverFailure

}

}

}

Table 8.2.4.14a.3.3-14: RRCConnectionReestablishment (step 17, Table 8.2.4.14a.3.2-2)

Derivation Path: 36.508, Table 4.6.1-10

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishment ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReestablishment-r8 SEQUENCE {

nextHopChainingCount

2

}

}

}

}

Table 8.2.4.14a.3.3-15: ATTACH ACCEPT for Cell 1 (preamble)

Derivation path: 36.508 Table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN2

Table 8.2.4.14a.3.3-16: TRACKING AREA UPDATE ACCEPT for Cell 28 (step 11B, Table 8.2.4.14a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN1

Table 8.2.4.14a.3.3-17: TRACKING AREA UPDATE ACCEPT for Cell 1 (step 20B, Table 8.2.4.14a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN2

8.2.4.15 RRC connection reconfiguration / Handover / Failure / Re-establishment failure / Inter-band

8.2.4.15.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including an IE mobilityControlInformation indicating a different E-UTRA cell having attempted inter-band handover }

ensure that {

when { UE detects handover failure and fails an RRC connection re-establishment procedure }

then { UE enters the E-UTRA RRC_IDLE state and trigger TAU procedure in order to recover RRC connection }

}

8.2.4.15.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clauses 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target cell by acquiring system information from that cell before performing RACH access in the target cell.

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> if T304 expires (handover failure):

NOTE 5: Following T304 expiry any dedicated preamble, if provided within the rach-ConfigDedicated, is not available for use by the UE anymore.

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

[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 handover failure, in accordance with 5.3.5.6; or

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> release reportProximityConfig and clear any associated proximity status reporting timer;

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 6: This procedure applies also if the UE returns to the source cell.

[TS 36.331, clause 5.3.7.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value ‘reconfigurationFailure’;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

2> else:

3> set the reestablishmentCause to the value ‘otherFailure’;

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

[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 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.2.4.15.3 Test description

8.2.4.15.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 10

– 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.2.4.15.3.2 Test procedure sequence

Table 8.2.4.15.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, while columns marked "T1" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 10

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy exit condition for event A3 (M1 > M10)

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M10 > M1)

T2

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

The power level values are such that SrxlevCell 1 > SrxlevCell 10 and SrxlevCell 10 <0.

(NOTE 1)

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.15.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter-band measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

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

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 10.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 10.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 6 the steps specified in Table 8.2.4.15.3.2-3 should take place.

6

The SS changes Cell 1 and Cell 10 parameters according to the row "T2" in table 8.2.4.15.3.2-1.

7

The UE transmits an RRCConnectionReestablishmentRequest message on Cell 1.

–>

RRCConnectionReestablishmentRequest

8

The SS does not respond to any RRCConnectionReestablishmentRequest message and waits for 1s to ensure that T301 expires and the UE goes to RRC_IDLE state on Cell 1.

9-13

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

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

14

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

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

Table 8.2.4.15.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304

1

The UE attempts to perform the inter-band handover using MAC Random Access Preamble on Cell 10

2

The SS does not respond.

8.2.4.15.3.3 Specific message contents

Table 8.2.4.15.3.3-0: Conditions for specific message contents
in Tables 8.2.4.15.3.3-2 and 8.2.4.15.3.3-5

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.15.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.15.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition MEAS

Table 8.2.4.15.3.3-2: MeasConfig (Table 8.2.4.15.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ

Information Element

Value/Remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f5

measObject[2]

MeasObjectEUTRA-GENERIC(f5)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfig-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f5

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

 

 

 

carrierFreq-v9e0

Same downlink EARFCN as used for f5

}

}

}

Table 8.2.4.15.3.3-3: MeasurementReport (step 4, Table 8.2.4.15.3.2-2)

Derivation Path: 36.508 Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 10

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

}

}

}

}

}

Table 8.2.4.15.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.15.3.2-2)

Derivation path: 36.508 Table 4.6.1-8, condition HO

Table 8.2.4.15.3.3-5: MobilityControlInfo (Table 8.2.4.15.3.3-4)

Derivation Path: 36.508 Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 10

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 10

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.15.3.3-6: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.15.3.2-2)

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

handoverFailure

}

}

}

8.2.4.15a RRC connection reconfiguration / Handover / Failure / Re-establishment failure / Inter-band / Between FDD and TDD

8.2.4.15a.1 Test Purpose (TP)

(1)

with { UE in E-UTRA FDD RRC_CONNECTED state and having completed the radio bearer establishment and initial security activation procedure on E-UTRA FDD cell and after receiving an RRCConnectionReconfiguration message including an IE mobilityControlInfo indicating a different E-UTRA TDD cell having attempted inter-mode handover }

ensure that {

when { UE detects handover failure and fails an RRC connection re-establishment procedure }

then { UE enters the E-UTRA FDD RRC_IDLE state and trigger TAU procedure in order to recover RRC connection on E-UTRA FDD cell }

}

(2)

with { UE in E-UTRA TDD RRC_CONNECTED state and having completed the radio bearer establishment and initial security activation procedure on E-UTRA TDD cell and after receiving an RRCConnectionReconfiguration message including an IE mobilityControlInfo indicating a different E-UTRA FDD cell having attempted inter-mode handover }

ensure that {

when { UE detects handover failure and fails an RRC connection re-establishment procedure }

then { UE enters the E-UTRA TDD RRC_IDLE state and trigger TAU procedure in order to recover RRC connection on E-UTRA TDD cell }

}

8.2.4.15a.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: 3GPP TS 36.331 clauses 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.3, 5.3.7.4, 5.3.7.7 and 5.3.12.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInformation and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInformation;

1> request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in [8].

1> reset MAC and re-establish RLC for all RBs that are established;

1> If the RRCConnectionReconfiguration message includes the radioResourceConfiguration:

2> perform the Radio resource configuration procedure as specified in 5.3.10;

1> set the C-RNTI to the value of the newUE-Identity;

1> if the eutra-CarrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the eutra-CarrierFreq with a physical cell identity indicated by the targetCellIdentity;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetCellIdentity;

1> if the dl-Bandwidth is included:

2> for the target cell, apply the downlink bandwidth indicated by the dl-Bandwidth;

1> else:

2> for the target cell, apply the same downlink bandwidth as for the current cell;

1> if the ul-Bandwidth is included:

2> for the target cell, apply the uplink bandwidth indicated by the ul-Bandwidth;

1> else:

2> for the target cell, apply the same uplink bandwidth as for the current cell;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> If the RRCConnectionReconfiguration message includes the securityConfiguration:

2> apply the AS-derived keys associated with the AS-base key indicated by the keyIndicator;

2> configure lower layers to apply the indicated integrity protection algorithm, i.e. the indicated integrity protection configuration shall be applied to all subsequent messages received and sent by the UE in the target cell, including the message used to indicate the successful completion of the procedure;

2> configure lower layers to apply the indicated ciphering algorithm, i.e. the indicated ciphering configuration shall be applied to all subsequent messages received and sent by the UE in the target cell, including the message used to indicate the successful completion of the procedure;

1> If the RRCConnectionReconfiguration message includes the measurementConfiguration:

2> perform the Measurement configuration procedure as specified in 5.5.2;

1> synchronise to the DL of the target cell;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration;

1> If MAC successfully completes the random access procedure:

2> stop timer T304;

2> If the physicalConfigDedicated is included in the RRCConnectionReconfiguration message:

3> If the UE needs the SFN of the target cell to apply the PUCCH and Sounding RS configuration:

4> apply the new PUCCH and Sounding RS configuration upon acquiring the SFN of the target cell;

3> else:

4> apply the new PUCCH and Sounding RS configuration;

2> indicate to PDCP to complete the PDCP Re-establishment procedure for all DRBs that are established, if any;

2> the procedure ends.

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> If T304 expires (handover failure):

NOTE 1: Following T304 expiry dedicated preambles, if provided within the rach-ConfigDedicated, are not available for use by the UE anymore.

2> revert back to the configuration used in the source cell, excluding the physical layer configuration;

NOTE 2: The UE reverts to the RRC configuration as well as the layer 2 configuration (PDCP/RLC/MAC) used in the source cell.

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends.

[TS 36.331, clause 5.3.7.2]

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

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

Upon initiation of the procedure, the UE shall:

1> start timer T311;

1> request PDCP to initiate the PDCP Re-establishment procedure for all RBs that are established;

NOTE 1: The handling of the radio bearers after the successful completion of the L2 re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in [8].

1> reset MAC and re-establish RLC for all RBs that are established;

1> select a suitable cell in accordance with the cell selection process as specified in [4];

[TS 36.331, clause 5.3.7.3]

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

[TS 36.331, clause 5.3.7.4]

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

1> set the IE ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover failure case) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the cellIdentity to the Physical layer identity of the source cell (handover failure case) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the concatenation of the ASN.1 encoded CellIdentity of the current cell, PhysicalCellIdentity of the cell the UE was connected to prior to the failure and C-RNTI that the UE had in the cell it was connected to prior to the failure;

3> with the integrity protection key and integrity protection algorithm that was used in the cell the UE was connected to prior to the failure; and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones.

1> set the IE reestablishmentCause as follows:

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

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

[TS 36.331, clause 5.3.7.7]

Upon T311 expiry, the UE shall:

1> perform the actions upon moving from RRC_CONNECTED to RRC_IDLE as specified in 5.3.12.

[TS 36.331, clause 5.3.12]

Upon moving from RRC_CONNECTED to RRC_IDLE, the UE shall:

1> reset MAC and re-establish RLC for all RBs that are established;

1> stop all timers that are running except T320;

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

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

1> enter RRC_IDLE.

8.2.4.15a.3 Test description

8.2.4.15a.3.1 Pre-test conditions

System Simulator:

– Cell 1 is an LTE FDD cell, Cell 10 and Cell 30 are LTE TDD cells.

– Each cell has only a single PLMN identity. The PLMNs are identified in the test by the identifiers in Table 8.2.4.15 a.3.1-1.

Table 8.2.4.15 a.3.1-1: PLMN identifiers

Cell

PLMN name

1

PLMN1

10

PLMN1

30

PLMN2

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

UE:

None.

Preamble:

– The UE is registered on PLMN1 (Cell 1) using the procedure described in TS 36.508[18] clause 4.5.2.3 except that the ATTACH ACCEPT message indicates PLMN2 in the Equivalent PLMN list as described in Table 8.2.4.15a.3.3-13.

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

8.2.4.15a.3.2 Test procedure sequence

Table 8.2.4.15a.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, while columns marked "T1", "T2", "T3", "T4" and "T5" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.4.15a.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 10

Cell 30

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-97

“Off”

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy exit condition for event A3 (M10 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

“Off”

The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M10 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

“Off”

The power level values are assigned to satisfy SrxlevCell 10 < 0 such that selecting Cell 1 is guaranteed

(NOTE 1).

T3

Cell-specific RS EPRE

dBm/15kHz

-85

"Off"

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 30 (M30) satisfy entry condition for event A3 (M30> M1).

(NOTE 1).

T4

Cell-specific RS EPRE

dBm/15kHz

-73

"Off"

-85

The power level values are such that measurement results for Cell 30 (M30) satisfy entry condition for event A3 (M1> M30).

(NOTE 1).

T5

Cell-specific RS EPRE

dBm/15kHz

"Off"

"Off"

-85

The power level values are assigned to satisfy SrxlevCell 1 < 0 such that selecting Cell 30 is guaranteed

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.15a.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter-band measurement on Cell 1 for Cell 10.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

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

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 10.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 10.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 6 the steps specified in Table 8.2.4.15a.3.2-3 should take place.

6

The SS changes Cell 10 parameters according to the row "T2" in table 8.2.4.15a.3.2-1.

7

The UE transmits an RRCConnectionReestablishmentRequest message on Cell 1.

–>

RRCConnectionReestablishmentRequest

8

The SS does not respond to any RRCConnectionReestablishmentRequest message and waits for 1s to ensure that T301 expires and the UE goes to RRC_IDLE state on Cell 1.

9

Generic test procedure described in TS 36.508 subclause 6.4.2.7 is performed on Cell 1.

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

NOTE: The TAU is accepted with PLMN2 listed as an Equivalent PLMN

10

Generic test procedure described in TS 36.508 subclause 4.5.3.3.is executed

1

11

The SS transmits an RRCConnectionReconfiguration message to setup inter-band measurement on Cell 1 for Cell 30.

<–

RRCConnectionReconfiguration

12

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

13

The SS changes Cell 30 parameters according to the row "T3" in table 8.2.4.15a.3.2-1.

14

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 30.

–>

MeasurementReport

15

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 30.

<–

RRCConnectionReconfiguration

16

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 30 to confirm the successful handover

–>

RRCConnectionReconfigurationComplete

17

The UE transmits a TRACKING AREA UPDATE REQUEST message on Cell 30.

18

SS responds with a TRACKING AREA UPDATE ACCEPT message.

NOTE: The TAU is accepted with PLMN1 listed as an Equivalent PLMN

19

The UE transmits a TRACKING AREA UPDATE COMPLETE message.

20

The SS changes Cell 1 and Cell 30 parameters according to the row "T4" in table 8.2.4.15a.3.2-1.

21

The UE transmits a MeasurementReport message on Cell 30 to report event A3 with the measured RSRP and RSRQ value for Cell 1.

–>

MeasurementReport

22

The SS transmits an RRCConnectionReconfiguration message on Cell 30 to order the UE to perform inter-band handover to Cell 1.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 26 the steps specified in Table 8.2.4.15a.3.2-4 should take place.

23

The SS changes Cell 1 parameters according to the row "T5" in table 8.2.4.15a.3.2-1.

24

The UE transmits an RRCConnectionReestablishmentRequest message on Cell 30.

–>

RRCConnectionReestablishmentRequest

25

The SS does not respond to any RRCConnectionReestablishmentRequest message and waits for 1s to ensure that T301 expires and the UE goes to RRC_IDLE state on Cell 30.

26-30

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

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

NOTE: The TAU is accepted with PLMN1 listed as an Equivalent PLMN

31

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 30?

2

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

Table 8.2.4.15a.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304

1

The UE attempts to perform the inter-band handover using MAC Random Access Preamble on Cell 10

2

The SS does not respond.

Table 8.2.4.15a.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304

1

The UE attempts to perform the inter-band handover using MAC Random Access Preamble on Cell 1

2

The SS does not respond.

8.2.4.15a.3.3 Specific message contents

Table 8.2.4.15a.3.3-0: Conditions for specific message contents
in Tables 8.2.4.15a.3.3-2, 8.2.4.15a.3.3-5, 8.2.4.15a.3.3-8 and 8.2.4.15a.3.3-10

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.15a.3.3-1: RRCConnectionReconfiguration (step 1 and step 11, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.6.1-8, condition MEAS

Table 8.2.4.15a.3.3-2: MeasConfig (step 1 and step 11, Table 8.2.4.15a.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f5

measObject[2]

MeasObjectEUTRA-GENERIC(f5)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f5

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f5

}

}

}

Table 8.2.4.15a.3.3-3: MeasurementReport (step 4, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.6.1-5

Information Element

Value/Remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 10

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.15a.3.3-4: RRCConnectionReconfiguration (step 5 and step 22, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.6.1-8, condition HO

Table 8.2.4.15a.3.3-4A: RRCConnectionReconfiguration (step 15, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.6.1-8, condition HO and condition MEAS

Table 8.2.4.15a.3.3-4B: MeasConfig (step 15 Table 8.2.4.15a.3.3-4A)

Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ

Table 8.2.4.15a.3.3-5: MobilityControlInfo (step 5, Table 8.2.4.15a.3.3-4)

Derivation Path: 36.508 Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 10

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq

Not present

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 10

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.15a.3.3-6: RRCConnectionReestablishmentRequest (step 7, Table 8.2.4.15a.3.2-2)

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

handoverFailure

}

}

}

Table 8.2.4.15a.3.3-7: MeasurementReport (step 14, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.6.1-5

Information Element

Value/Remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 30

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.15a.3.3-8: MobilityControlInfo (step 15, Table 8.2.4.15a.3.3-4A)

Derivation Path: 36.508 Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 30

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 30

ul-CarrierFreq

Not present

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 30

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.15a.3.3-9: MeasurementReport (step 21, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.6.1-5

Information Element

Value/Remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

Cell 30

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.15a.3.3-10: MobilityControlInfo (step 22, Table 8.2.4.15a.3.3-4)

Derivation Path: 36.508 Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq

Not present

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.15a.3.3-11: RRCConnectionReestablishmentRequest (step 24, Table 8.2.4.15a.3.2-2)

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 30

shortMAC-I

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

}

reestablishmentCause

handoverFailure

}

}

}

Table 8.2.4.15a.3.3-12: ATTACH ACCEPT for Cell 1 (preamble)

Derivation path: 36.508 Table 4.7.2-1

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN2

Table 8.2.4.15a.3.3-13: TRACKING AREA UPDATE ACCEPT for Cell 1 (steps 9, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN2

Table 8.2.4.15a.3.3-14: TRACKING AREA UPDATE ACCEPT for Cell 30 (step 18, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN1

Table 8.2.4.15a.3.3-15: TRACKING AREA UPDATE ACCEPT for Cell 30 (steps 26-30, Table 8.2.4.15a.3.2-2)

Derivation path: 36.508 Table 4.7.2-24

Information Element

Value/Remark

Comment

Condition

Equivalent PLMNs

PLMN1

8.2.4.16 CA / RRC connection reconfiguration / Setup and Change of MIMO

8.2.4.16.1 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band Contiguous CA

8.2.4.16.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and configured an Scell }

ensure that {
when { UE receives an RRCConnectionReconfiguration message indicating PCell and Scell TM modification}

then { UE sends an RRCConnectionReconfigurationComplete message and changes transmission mode of the Pcell and SCell}

}

8.2.4.16.1.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]

The UE shall:

1> if the antennaInfo-r10 is included in the received physicalConfigDedicated and the previous version of this field that was received by the UE was antennaInfo (without suffix i.e. the version defined in REL-8):

2> apply the default antenna configuration as specified in section 9.2.4;

1> if the cqi-ReportConfig-r10 is included in the received physicalConfigDedicated and the previous version of this field that was received by the UE was cqi-ReportConfig (without suffix i.e. the version defined in REL-8):

2> apply the default CQI reporting configuration as specified in 9.2.4;

NOTE: Application of the default configuration involves release of all extensions introduced in REL-9 and later.

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

1> if the antennaInfo is included and set to explicitValue:

2> if the configured transmissionMode is not tm3 or tm4 or tm8 or tm9; or

2> if the configured transmissionMode is tm8 and pmi-RI-Report is not present; or

2> if the configured transmissionMode is tm9 and pmi-RI-Report is not present; or

2> if the configured transmissionMode is tm9 and pmi-RI-Report is present and antennaPortsCount within csi-RS is set to an1:

3> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to defaultValue:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.16.1.3 Test description

8.2.4.16.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 3

– 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] , with TM2 configured.

8.2.4.16.1.3.2 Test procedure sequence

Table 8.2.4.16.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. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 3

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-107

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-91

Table 8.2.4.16.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.16.1.3.2-1.

2

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to reconfigure Cell 3 as a Scell and reconfiguring transmission mode for both PCell and SCell.

<–

RRCConnectionReconfiguration

3

Check: Does the UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

1

P

4

The SS transmits an RRCConnectionReconfiguration message to reconfigure transmission mode on both PCell and SCell.

<–

RRCConnectionReconfiguration

5

Check: Does the UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

1

P

8.2.4.16.1.3.3 Specific message contents

Table 8.2.4.16.1.3.3-0: Conditions for specific message contents
in Table 8.2.4.16.1.3.3-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.16.1.3.3-1: RRCConnectionReconfiguration (step 2, Table 8.2.4.16.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod and 2TX

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated-SCell_AddMod SEQUENCE {

PhysicalConfigDedicated SEQUENCE {

antennaInfo-r10

TM3

}

}

}

}

}

}

Table 8.2.4.16.1.3.3-2: SCellToAddMod-r10 (Table 8.2.4.16.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

}

Table 8.2.4.16.1.3.3-3: RadioResourceConfigDedicatedSCell-r10 (Table 8.2.4.16.1.3.3-1)

Derivation Path: 36.508, Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

PhysicalConfigDedicatedSCell-r10 SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

antennaInfo-r10 {

transmissionMode-r10

TM2

}

}

}

}

Table 8.2.4.16.1.3.3-4: RRCConnectionReconfiguration (step 4, Table 8.2.4.16.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition SCell_AddMod and 2TX

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

RadioResourceConfigDedicated-SCell_AddMod SEQUENCE {

PhysicalConfigDedicated SEQUENCE {

antennaInfo-r10 SEQUENCE {

transmissionMode-r10

TM2

codebookSubsetRestriction-r10

Not present

ue-TransmitAntennaSelection

release

}

}

}

}

}

}

}

Table 8.2.4.16.1.3.3-5: SCellToAddMod-r10 (Table 8.2.4.16.1.3.3-4)

Derivation Path: 36.508, Table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE {

sCellIndex-r10

1

cellIdentification-r10 SEQUENCE {}

Not present

radioResourceConfigCommonSCell-r10

Not present

}

Table 8.2.4.16.1.3.3-6: RadioResourceConfigDedicatedSCell-r10 (Table 8.2.4.16.1.3.3-4)

Derivation Path: 36.508, Table 4.6.3-19AA

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE {

PhysicalConfigDedicatedSCell-r10 SEQUENCE {

nonUL-Configuration-r10 SEQUENCE {

antennaInfo-r10 {

transmissionMode-r10

TM3

}

}

}

}

Table 8.2.4.16.1.3.3-7: RRCConnectionReconfiguration (preamble, step 8, TS 36.508 table 4.5.3.3-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-SRB2-DRB(n, m) SEQUENCE {

PhysicalConfigDedicated SEQUENCE {

antennaInfo-r10 SEQUENCE {

transmissionMode-r10

TM2

codebookSubsetRestriction-r10

Not present

ue-TransmitAntennaSelection

release

}

}

}

}

}

}

}

8.2.4.16.2 CA / RRC connection reconfiguration / Setup and Change of MIMO / Inter-band CA

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

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

– Cells configuration: Cell 10 replaces Cell 3.

8.2.4.16.3 CA / RRC connection reconfiguration / Setup and Change of MIMO / Intra-band non-contiguous CA

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

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

8.2.4.17 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell addition

8.2.4.17.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell addition / Intra-band Contiguous CA

8.2.4.17.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the inter frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA frequency to be handover to one of the SCell and sCellToAddModList with an SCell addition }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.17.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> configure lower layers to consider the SCell(s), if configured, to be in deactivated state;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if connected as an RN:

2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or subsequently established DRBs that are configured to apply integrity protection, if any;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and plmn-Identity stored in VarRLF-Report is equal to the RPLMN:

3> include rlf-InfoAvailable;

2> if the UE has logged measurements available for E-UTRA and plmn-Identity stored in VarLogMeasReport is equal to the RPLMN:

3> include the logMeasAvailable;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell.

8.2.4.17.1.3 Test description

8.2.4.17.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell and Cell 3 SCell

– 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.2.4.17.1.3.2 Test procedure sequence

Table 8.2.4.17.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.2.4.17.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

Off

The power level values are such that camping on Cell 1 is guarantee.

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

Power levels are such that entry condition for event A3 (measId 1) is satisfied:

Table 8.2.4.17.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including sCellToAddModList with Cell 3 as SCell addition.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup event A3 reporting configuration.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

5

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

6

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

7

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform handover to Cell 3 with Cell 1 as SCell addition at the same time.

<–

RRCConnectionReconfiguration

8

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the handover and SCell addition of Cell 1?

–>

RRCConnectionReconfigurationComplete

1

P

9

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

1

8.2.4.17.1.3.3 Specific message contents

Table 8.2.4.17.1.3.3-0: Conditions for specific message contents
in Tables 8.2.4.17.1.3.3-2 and 8.2.4.17.1.3.3-6.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.17.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.17.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 {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sCellToReleaseList-r10

Not present

sCellToAddModList-r10

SCellToAddMod-r10-f2

SCell addition for Cell 3

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.4.17.1.3.3-2: SCellToAddMod-r10-f2 (Table 8.2.4.17.1.3.3-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

cellIdentification-r10[1] SEQUENCE {

physCellId-r10[1]

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10[1]

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10[1]

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10[1]

RadioResourceConfigCommonSCell-r10-f2

dl-CarrierFreq-v1090[1]

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.4.17.1.3.3-3: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.4.17.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 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

}

}

Table 8.2.4.17.1.3.3-4: Void

Table 8.2.4.17.1.3.3-5: RRCConnectionReconfiguration (step 3, Table 8.2.4.17.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.17.1.3.3-6: MeasConfig (Table 8.2.4.17.1.3.3-5)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

3 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

Cell 1

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.17.1.3.3-7: MeasurementReport (step 6, Table 8.2.4.17.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults ::= SEQUENCE {

measId

1

measResultPCell ::= SEQUENCE {

Report Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

physicalCellId of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

servFreqId-r10

1

measResultSCell-r10 SEQUENCE {

Cell 3

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

}

}

}

}

}

}

Table 8.2.4.17.1.3.3-8: RRCConnectionReconfiguration (step 7, Table 8.2.4.17.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8 condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

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

SCellIndex-r10[1]

1

}

sCellToAddModList-r10

SCellToAddMod-r10-f1

SCell addition for Cell 1

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

}

}

}

Table 8.2.4.17.1.3.3-9: MobilityControlInfo (Table 8.2.4.17.1.3.3-8)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.17.1.3.3-10: SCellToAddMod-r10-f1 (Table 8.2.4.17.1.3.3-8)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

cellIdentification-r10[1] SEQUENCE {

physCellId-r10[1]

Physical Cell Identity of Cell 1

dl-CarrierFreq-r10[1]

Same downlink EARFCN as used for Cell 1

dl-CarrierFreq-r10[1]

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10[1]

RadioResourceConfigCommonSCell-r10-f1

dl-CarrierFreq-v1090[1]

Same downlink EARFCN as used for Cell 1

Band > 64

}

Table 8.2.4.17.1.3.3-11: RadioResourceConfigCommonSCell-r10-f3 (Table 8.2.4.17.1.3.3-10)

Derivation Path: 36.508 clause 4.6.3 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 1

}

}

8.2.4.17.2 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell addition / Inter-band CA

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

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

– Cells configuration: Cell 10 replaces Cell 3

8.2.4.17.3 CA / RRC connection reconfiguration / Handover / Success / PCell Change and SCell addition / Intra-band non-contiguous CA

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

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

8.2.4.18 CA / RRC connection reconfiguration / Handover / Success / SCell release

8.2.4.18.1 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band Contiguous CA

8.2.4.18.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure, performed the intra-frequency measurement and configured an SCell }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and including sCellToReleaseList with an sCellIndex set to the configured SCell }

then { UE sends an RRCConnectionReconfigurationComplete message }

}

8.2.4.18.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4 and 5.3.10.3a.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> configure lower layers to consider the SCell(s), if configured, to be in deactivated state;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if connected as an RN:

2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or subsequently established DRBs that are configured to apply integrity protection, if any;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and plmn-Identity stored in VarRLF-Report is equal to the RPLMN:

3> include rlf-InfoAvailable;

2> if the UE has logged measurements available for E-UTRA and plmn-Identity stored in VarLogMeasReport is equal to the RPLMN:

3> include the logMeasAvailable;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell.

[TS 36.331, clause 5.3.10.3a]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell;

8.2.4.18.1.3 Test description

8.2.4.18.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is PCell, Cell 2 is intra-frequency cell of PCell, and Cell 3 is SCell to be added

– 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.2.4.18.1.3.2 Test procedure sequence

Table 8.2.4.18.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 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.2.4.18.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Cell 3

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) do not satisfy entry condition for event A3 (M2 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1).

Table 8.2.4.18.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 Cell 3 as a SCell.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message to setup intra-frequency measurement reporting for event A3 on Cell 1.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

5

The SS changes Cell 2 level according to row "T1" in Table 8.2.4.18.1.3.2-1.

6

The UE transmits a MeasurementReport message on Cell 1 to report event A3.

–>

MeasurementReport

7

The SS transmits an RRCConnectionReconfiguration message to perform intra-frequency handover and SCell release on Cell 1.

<–

RRCConnectionReconfiguration

8

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

–>

RRCConnectionReconfigurationComplete

1

P

9

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

1

8.2.4.18.1.3.3 Specific message contents

Table 8.2.4.18.1.3.3-0: Conditions for specific message contents
in Tables 8.2.4.18.1.3.3-2 and 8.2.4.18.1.3.3-5.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.18.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.18.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.4.18.1.3.3-2: SCellToAddMod-r10 (Table 8.2.4.18.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

}

Table 8.2.4.18.1.3.3-3: RadioResourceConfigCommonSCell-r10 (Table 8.2.4.18.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

}

}

Table 8.2.4.18.1.3.3-4: RRCConnectionReconfiguration (step 3, Table 8.2.4.18.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.18.1.3.3-5: MeasConfig (Table 8.2.4.18.1.3.3-4)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfig-A3

}

measIdToAddModListSEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.18.1.3.3-5A: ReportConfig-A3 (Table 8.2.4.18.1.3.3-5)

Derivation path: 36.508, Table 4.6.6-6

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA-A3 ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

timeToTrigger

ms2560

}

}

}

Table 8.2.4.18.1.3.3-6: MeasurementReport (step 6, Table 8.2.4.18.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

1 entry

servFreqId-r10[1]

1

Cell 3

measResultSCell-r10[1] SEQUENCE {

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

measResultBestNeighCell-r10[1]

Not present

}

}

}

}

}

}

Table 8.2.4.18.1.3.3-7: RRCConnectionReconfiguration (step 7, Table 8.2.4.18.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

Not present

nonCriticalExtension SEQUENCE {

otherConfig-r9

Not present

fullConfig-r9

Not present

nonCriticalExtension SEQUENCE {

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

1 entry

SCellIndex-r10[1]

1

}

sCellToAddModList-r10

Not present

nonCriticalExtension

Not present

}

}

}

}

}

}

}

Table 8.2.4.18.1.3.3-8: MobilityControlInfo (Table 8.2.4.18.1.3.3-7)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

8.2.4.18.2 CA / RRC connection reconfiguration / Handover / Success / SCell release / Inter-band CA

The scope and description of the present TC is the same as test case 8.2.4.18.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.2.4.18.2.1 Specific message contents

Same as test case 8.2.4.18.1 with the following differences.

Table 8.2.4.18.2.1-1: Conditions for specific message contents in Table 8.2.4.18.2.1-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.18.2.1-1: MeasConfig (Table 8.2.4.18.1.3.3-4)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

Apply conditions “DS_Meas and LAA SCell” to work out the value of this IE

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfig-A3

}

measIdToAddModListSEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

8.2.4.18.3 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band non-contiguous CA

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

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

8.2.4.19 CA / RRC connection reconfiguration / Handover / Success / PCell Change / SCell no Change

8.2.4.19.1 CA / RRC connection reconfiguration / Handover / Success / PCell Change / SCell no Change / Intra-band Contiguous CA

8.2.4.19.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure, performed the inter-frequency measurement and configured an SCell }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including mobilityControlInfo indicating change of the PCell and sCellToAddModList with an SCell same from configured SCell representing an intra-band contiguous CA }

then { UE sends an RRCConnectionReconfigurationComplete message and does not change SCell }

}

8.2.4.19.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in TS 36.331, clauses 5.3.5.4 and 5.3.10.3b.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> configure lower layers to consider the SCell(s), if configured, to be in deactivated state;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if connected as an RN:

2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or subsequently established DRBs that are configured to apply integrity protection, if any;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and plmn-Identity stored in VarRLF-Report is equal to the RPLMN:

3> include rlf-InfoAvailable;

2> if the UE has logged measurements available for E-UTRA and plmn-Identity stored in VarLogMeasReport is equal to the RPLMN:

3> include the logMeasAvailable;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell.

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the received radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell;

2> configure lower layers to consider the SCell to be in deactivated state;

1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the received radioResourceConfigDedicatedSCell;

8.2.4.19.1.3 Test description

8.2.4.19.1.3.1 Pre-test conditions

System Simulator:

– Cell 3 is the PCell, Cell 1 is the SCell to be added and Cell 6 is the inter-frequency neighbour cell.

– Cell 1 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 3 according to [18].

8.2.4.19.1.3.2 Test procedure sequence

Table 8.2.4.19.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.2.4.19.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Cell 6

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-91

-85

-97

The power level values are such that measurement results for Cell 3 (M1) and Cell 1 (M2) do not satisfy entry condition for event A3 (M2 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-85

-79

The power level values are such that measurement results for Cell 3 (M1) and Cell 6 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 8.2.4.19.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message on Cell 3 to configure Cell 1 as an SCell.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message to setup inter-frequency measurement reporting for event A3 on Cell 3.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3.

–>

RRCConnectionReconfigurationComplete

5

The SS changes Cell 6 level according to row "T1" in Table 8.2.4.19.1.3.2-1.

6

The UE transmits a MeasurementReport message on Cell 3 to report event A3.

–>

MeasurementReport

7

The SS transmits an RRCConnectionReconfiguration message to perform inter-frequency handover.

<–

RRCConnectionReconfiguration

8

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 6?

–>

RRCConnectionReconfigurationComplete

1

P

9

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

1

8.2.4.19.1.3.3 Specific message contents

Table 8.2.4.19.1.3.3-0: Conditions for specific message contents
in Tables 8.2.4.19.1.3.3-2, 8.2.4.19.1.3.3-8 and 8.2.4.19.1.3.3-6.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.19.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.19.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.4.19.1.3.3-2: SCellToAddMod-r10 (Table 8.2.4.19.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 1

dl-CarrierFreq-r10

Same downlink EARFCN as used for Cell 1

dl-CarrierFreq-r10

maxEARFCN

Band > 64

}

dl-CarrierFreq-v1090

Same downlink EARFCN as used for Cell 1

Band > 64

}

Table 8.2.4.19.1.3.3-3: RadioResourceConfigCommonSCell-r10 (Table 8.2.4.19.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 1

}

}

Table 8.2.4.19.1.3.3-4: Void

Table 8.2.4.19.1.3.3-5: RRCConnectionReconfiguration (step 3, Table 8.2.4.19.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.19.1.3.3-6: MeasConfig (Table 8.2.4.19.1.3.3-5)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

3 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[3]

IdMeasObject-f3

measObject[3]

MeasObjectEUTRA-GENERIC(f3)

measObject[3]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfig-A3

}

measIdToAddModListSEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

measId[1]

1

measObjectId[1]

IdMeasObject-f3

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

measObjectEUTRA-v9e0[3] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f3

}

}

}

Table 8.2.4.19.1.3.3-6A : ReportConfig-A3 (Table 8.2.4.19.1.3.3-6)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-6

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA-A3 ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

timeToTrigger

ms2560

}

}

}

Table 8.2.4.19.1.3.3-7: MeasurementReport (step 6, Table 8.2.4.19.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

Cell 3

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 6

Cell 6

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

1 entry

servFreqId-r10[1]

1

measResultSCell-r10[1] SEQUENCE {

Cell 1

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

measResultBestNeighCell-r10[1]

Not present

}

}

}

}

}

}

Table 8.2.4.19.1.3.3-7: RRCConnectionReconfiguration (step 7, Table 8.2.4.19.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.19.1.3.3-8: MobilityControlInfo (Table 8.2.4.19.1.3.3-7)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 6

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 6

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

8.2.4.19.2 CA / RRC connection reconfiguration / Handover / Success / PCell Change / SCell no Change / Inter-band CA

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

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

– Cells configuration: Cell 10 replaces Cell 1& Cell 1 replaces Cell 6.

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

8.2.4.19.2.1 Specific message contents

Same as test case 8.2.4.19.1 with the following differences

Table 8.2.4.19.2.1-1: Conditions for specific message contents in Table 8.2.4.19.2.1-2

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.19.2.1-2: MeasConfig (Table 8.2.4.19.1.3.3-5)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

3 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Apply conditions “DS_Meas and LAA SCell” to work out the value of this IE

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[3]

IdMeasObject-f3

measObject[3]

MeasObjectEUTRA-GENERIC(f3)

measObject[3]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfig-A3

}

measIdToAddModListSEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

measId[1]

1

measObjectId[1]

IdMeasObject-f3

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

measObjectEUTRA-v9e0[3] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f3

}

}

}

8.2.4.19.3 CA / RRC connection reconfiguration / Handover / Success / PCell Change / SCell no Change / Intra-band non-contiguous CA

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

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

8.2.4.20 CA / RRC connection reconfiguration / Handover / Success / SCell Change

8.2.4.20.1 CA / RRC connection reconfiguration / Handover / Success / SCell Change / Intra-band Contiguous CA

8.2.4.20.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and performed the inter frequency measurement }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and sCellToAddModList with an SCell different from configured SCell }

then { UE sends an RRCConnectionReconfigurationComplete message and changes SCell }

}

8.2.4.20.1.2 Conformance requirements

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

[TS 36.331, clause 5.3.10.3b]

The UE shall:

1> for each sCellIndex value included in the sCellToAddModList that is not part of the current UE configuration (SCell addition):

2> add the SCell, corresponding to the cellIdentification, in accordance with the received radioResourceConfigCommonSCell and radioResourceConfigDedicatedSCell;

2> configure lower layers to consider the SCell to be in deactivated state;

1> for each sCellIndex value included in the sCellToAddModList that is part of the current UE configuration (SCell modification):

2> modify the SCell configuration in accordance with the received radioResourceConfigDedicatedSCell;

8.2.4.20.1.3 Test description

8.2.4.20.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added and Cell 12 is the intra-frequency neighbour cell of Cell 3.

– Cell 3 is 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.

– 3 E-UTRA Cells with the same PLMN.

UE:

None.

Preamble:

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

8.2.4.20.1.3.2 Test procedure sequence

Table 8.2.4.20.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.2.4.20.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Cell 12

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-97

The power level values are such that measurement results for Cell 12 (M12) and Cell 3 (M2) do not satisfy entry condition for event A6.

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-85

-79

The power level values are such that measurement results for Cell 12 (M12) and Cell 3 (M3) satisfy entry condition for event A6.

Table 8.2.4.20.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Wait 1 s to allow for the switching of cells.

2

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to configure Cell 3 as an SCell.

<–

RRCConnectionReconfiguration

3

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

EXCEPTION: If UE does not support FGI bit 111, i.e. Event A6, the following step 4 to step 7 except step 6 should not be executed

4

The SS transmits an RRCConnectionReconfiguration message to setup intra-frequency measurement reporting for event A6 on Cell 1.

<–

RRCConnectionReconfiguration

5

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

6

The SS changes power level according to row "T1" in Table 8.2.4.20.1.3.2-1.

7

The UE transmits a MeasurementReport message on Cell 1 to report event A6.

–>

MeasurementReport

8

The SS transmits an RRCConnectionReconfiguration message to perform inter-frequency handover to Cell 12 with original SCell Cell 3 release and new SCell Cell1addition.

<–

RRCConnectionReconfiguration

9

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 12?

–>

RRCConnectionReconfigurationComplete

1

P

10

The UE transmits a TRACKING AREA UPDATE REQUEST message to update the registration of the actual tracking area.

11

The SS responds with TRACKING AREA UPDATE ACCEPT message.

12

The UE transmits a TRACKING AREA UPDATE COMPLETE.

13

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

1

8.2.4.20.1.3.3 Specific message contents

Table 8.2.4.20.1.3.3-0: Conditions for specific message contents
in Tables 8.2.4.20.1.3.3-2, 8.2.4.20.1.3.3-5, 8.2.4.18.1.3.3-5.8.2.4.19.1.3.3-8 and 8.2.4.20.1.3.3-9.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.20.1.3.3-1: RRCConnectionReconfiguration (step 2, Table 8.2.4.20.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.4.20.1.3.3-2: SCellToAddMod-r10 (Table 8.2.4.20.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

}

Table 8.2.4.20.1.3.3-3: RadioResourceConfigCommonSCell-r10 (Table 8.2.4.20.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

}

}

Table 8.2.4.20.1.3.3-4: RRCConnectionReconfiguration (step 4, Table 8.2.4.20.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.20.1.3.3-5: MeasConfig (Table 8.2.4.20.1.3.3-4)

Derivation Path: 36.508 clause 4.6.6 table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

{

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A6

reportConfig[1]

ReportConfigEUTRA-A6

}

measIdToAddModListSEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

measId[1]

1

measObjectId[2]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A6

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.20.1.3.3-6: MeasurementReport (step 7, Table 8.2.4.20.1.3.2-2)

Derivation Path: 36.508, clause 4.6.1 table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 12

Cell 12

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

1 entry

servFreqId-r10[1]

1

measResultSCell-r10[1] SEQUENCE {

Cell 3

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

measResultBestNeighCell-r10[1]

Not present

}

}

}

}

}

}

Table 8.2.4.20.1.3.3-7: RRCConnectionReconfiguration (step 8, Table 8.2.4.20.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated

RadioResourceConfigDedicated-CQIConfig-R10

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

SCellToReleaseList-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

SCellIndex-r10[1]

1

}

SCellToAddModList-r10

SCellToAddMod-r10-f1

}

}

}

}

}

}

}

Table 8.2.4.20.1.3.3-7A: RadioResourceConfigDedicated-CQIConfig-R10 (Table 8.2.4.20.1.3.3-7)

Derivation Path: 36.508 , condition HO

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated ::= SEQUENCE {

physicalConfigDedicated

PhysicalConfigDedicated-CQIConfig-R10

}

Table 8.2.4.20.1.3.3-7B: PhysicalConfigDedicated-CQIConfig-R10 (Table 8.2.4.20.1.3.3-7 A)

Derivation Path: 36.508, Table 4.8.2.1.6-1, condition HO

Information Element

Value/remark

Comment

Condition

PhysicalConfigDedicated ::= SEQUENCE {

cqi-ReportConfig-r10

CQI-ReportConfig-r10-DEFAULT

}

Table 8.2.4.20.1.3.3-8: MobilityControlInfo (Table 8.2.4.20.1.3.3-7)

Derivation Path: clause 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 12

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 12

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.20.1.3.3-9: SCellToAddMod-r10-f1 (Table 8.2.4.20.1.3.3-7)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

cellIdentification-r10[1] SEQUENCE {

physCellId-r10[1]

Physical Cell Identity of Cell 1

dl-CarrierFreq-r10[1]

Same downlink EARFCN as used for Cell 1

dl-CarrierFreq-r10[1]

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10[1]

RadioResourceConfigCommonSCell-r10-f1

dl-CarrierFreq-v1090[1]

Same downlink EARFCN as used for Cell 1

Band > 64

}

Table 8.2.4.20.1.3.3-10: RadioResourceConfigCommonSCell-r10-f1 (Table 8.2.4.20.1.3.3-9)

Derivation Path: 36.508 clause 4.6.3 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 1

}

8.2.4.20.2 CA / RRC connection reconfiguration / Handover / Success / SCell Change / Inter-band CA

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

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

– Cells configuration: Cell 10 replaces Cell 3& Cell 30 replaces Cell 12.

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

– Cell 1, Cell 10 and Cell 30 with the same PLMN.

8.2.4.20.3 CA / RRC connection reconfiguration / Handover / Success / SCell Change Intra-band non-contiguous CA

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

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

8.2.4.21 CA / RRC connection reconfiguration / Handover / Success / SCell release

8.2.4.21.1 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band Contiguous CA

8.2.4.21.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure, performed the inter-frequency measurement and configured an SCell }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo and including sCellToReleaseList with an sCellIndex set to the configured SCell }

then { UE sends an RRCConnectionReconfigurationComplete message }

}

8.2.4.21.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4 and 5.3.10.3a.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> configure lower layers to consider the SCell(s), if configured, to be in deactivated state;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if connected as an RN:

2> configure lower layers to apply the integrity protection algorithm and the KUPint key, for current or subsequently established DRBs that are configured to apply integrity protection, if any;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the reportProximityConfig:

2> perform the proximity indication in accordance with the received reportProximityConfig;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and plmn-Identity stored in VarRLF-Report is equal to the RPLMN:

3> include rlf-InfoAvailable;

2> if the UE has logged measurements available for E-UTRA and plmn-Identity stored in VarLogMeasReport is equal to the RPLMN:

3> include the logMeasAvailable;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell.

[TS 36.331, clause 5.3.10.3a]

The UE shall:

1> if the release is triggered by reception of the sCellToReleaseList:

2> for each sCellIndex value included in the sCellToReleaseList:

3> if the current UE configuration includes an SCell with value sCellIndex:

4> release the SCell;

1> if the release is triggered by RRC connection re-establishment:

2> release all SCells that are part of the current UE configuration;

8.2.4.21.1.3 Test description

8.2.4.21.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the SCell to be added and Cell 6 is the inter-frequency neighbour cell of PCell.

– 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.2.4.21.1.3.2 Test procedure sequence

Table 8.2.4.21.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.2.4.21.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Cell 6

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 6 (M6) do not satisfy entry condition for event A5.

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 6 (M6) satisfy entry condition for event A5.

Table 8.2.4.21.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 Cell 3 as an SCell.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message to setup inter-frequency measurement reporting for event A5 on Cell 1.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

5

The SS changes Cell 6 level according to row "T1" in Table 8.2.4.21.1.3.2-1.

6

The UE transmits a MeasurementReport message on Cell 1 to report event A5.

–>

MeasurementReport

7

The SS transmits an RRCConnectionReconfiguration message to perform inter-frequency handover to Cell 6 and release SCell Cell 3.

<–

RRCConnectionReconfiguration

8

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 6?

–>

RRCConnectionReconfigurationComplete

1

P

9

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

1

8.2.4.21.1.3.3 Specific message contents

Table 8.2.4.21.1.3.3-0: Conditions for specific message contents
in Tables 8.2.4.21.1.3.3-2, 8.2.4.21.1.3.3-5. and 8.2.4.21.1.3.3-9.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.21.1.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.21.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.4.21.1.3.3-2: SCellToAddMod-r10 (Table 8.2.4.21.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

}

Table 8.2.4.21.1.3.3-3: RadioResourceConfigCommonSCell-r10 (Table 8.2.4.21.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

}

}

Table 8.2.4.21.1.3.3-4: RRCConnectionReconfiguration (step 3, Table 8.2.4.21.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition MEAS

Table 8.2.4.21.1.3.3-5: MeasConfig (Table 8.2.4.21.1.3.3-4)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1

Information Element

Value/Remark

Comment

Condition

measConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

3 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

Cell 1

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[3]

IdMeasObject-f3

measObject[3]

MeasObjectEUTRA-GENERIC(f3)

Cell 6

measObject[3]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A5

reportConfig[1]

ReportConfig-A5

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f3

reportConfigId[1]

IdReportConfig-A5

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

measObjectEUTRA-v9e0[3] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f3

}

}

}

Table 8.2.4.21.1.3.3-6: ReportConfig-A5 (Table 8.2.4.21.1.3.3-5)

Derivation path: 36.508 clause 4.6.6 table ReportConfigEUTRA-A5(-76, -88)

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA ::= SEQUENCE {

reportAmount

infinity

triggerType CHOICE {

event SEQUENCE {

timeToTrigger

ms2560

}

}

}

}

Table 8.2.4.21.1.3.3-7: MeasurementReport (step 6, Table 8.2.4.21.1.3.2-2)

Derivation Path: 36.508, clause 4.6.1 table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultPCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 6

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

additionalSI-Info-r9

Not present

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

1 entry

servFreqId-r10[1]

1

measResultSCell-r10[1] SEQUENCE {

Cell 3

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

measResultBestNeighCell-r10[1]

Not present

}

}

}

}

}

}

Table 8.2.4.21.1.3.3-8: RRCConnectionReconfiguration (step 7, Table 8.2.4.21.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

MeasConfig ::= SEQUENCE {

measIdToRemoveList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

}

}

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

SCellToReleaseList-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

SCellIndex-r10[1]

1

}

SCellToAddModList-r10

Not present

}

}

}

}

}

}

}

Table 8.2.4.21.1.3.3-9: MobilityControlInfo (Table 8.2.4.21.1.3.3-8)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 6

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 6

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

8.2.4.21.2 CA / RRC connection reconfiguration / Handover / Success / SCell release / Inter-band CA

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

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

– Cells configuration:

– Cell 10 replaces Cell 3, and then

– If f6 is supported as per TS 36.508 Table 6.2.3.2-2 by the band combination in which the test case is executed, then Cell 28 replaces Cell 6; otherwise Cell 3 replaces Cell 6. When Cell 28 is used its PLMN shall be set to PLMN 1.

8.2.4.21.3 CA / RRC connection reconfiguration / Handover / Success / SCell release / Intra-band non-Contiguous CA

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

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

– Cells configuration:

8.2.4.22 Void

8.2.4.23 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful

8.2.4.23.1 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Intra-band Contiguous CA

8.2.4.23.1.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA cell and including sCellToReleaseList with an sCellIndex set to the configured SCell }

ensure that {
when { UE detects handover failure and the source PCell is selectable }

then { UE successfully performs an RRC connection re-establishment procedure on source PCell }

}

(2)

with { UE having completed the radio bearer establishment and initial security activation procedure and after receiving an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA cell and including sCellToReleaseList with an sCellIndex set to the configured SCell }

ensure that {
when { UE detects handover failure and the initial SCell is selectable }

then { UE successfully performs an RRC connection re-establishment procedure on original SCell and the original SCell becomes the PCell }

}

8.2.4.23.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.1.3, 5.3.5.4, 5.3.5.6, 5.3.7.2, 5.3.7.4, 5.3.7.5, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.1.3]

The source eNB should, for some time, maintain a context to enable the UE to return in case of handover failure. After having detected handover failure, the UE attempts to resume the RRC connection either in the source PCell or in another cell using the RRC re-establishment procedure. This connection resumption succeeds only if the accessed cell is prepared, i.e. concerns a cell of the source eNB or of another eNB towards which handover preparation has been performed. The cell in which the re-establishment procedure succeeds becomes the PCell while SCells and STAGs, if configured, are released..

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.5.6]

The UE shall:

1> if T304 expires (handover failure):

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

2> revert back to the configuration used in the source cell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

[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 handover failure, in accordance with 5.3.5.6; or

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.4]

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

1> set the ue-Identity as follows:

2> set the c-RNTI to the C-RNTI used in the source cell (handover and mobility from E-UTRA failure) or used in the cell in which the trigger for the re-establishment occurred (other cases);

2> set the physCellId to the physical cell identity of the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases);

2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated:

3> over the ASN.1 encoded as per section 8 (i.e., a multiple of 8 bits) VarShortMAC-Input;

3> with the KRRCint key and integrity protection algorithm that was used in the source cell (handover and mobility from E-UTRA failure) or of the cell in which the trigger for the re-establishment occurred (other cases); and

3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones;

1> set the reestablishmentCause as follows:

2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.5 (the UE is unable to comply with the reconfiguration):

3> set the reestablishmentCause to the value ‘reconfigurationFailure’;

2> else if the re-establishment procedure was initiated due to handover failure as specified in 5.3.5.6 (intra-LTE handover failure) or 5.4.3.5 (inter-RAT mobility from EUTRA failure):

3> set the reestablishmentCause to the value ‘handoverFailure’;

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

[TS 36.331, clause 5.3.7.5]

NOTE: Prior to this, lower layer signalling is used to allocate a C-RNTI. For further details see TS 36.321 [6];

The UE shall:

1> stop timer T301;

1> re-establish PDCP for SRB1;

1> re-establish RLC for SRB1;

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

1> resume SRB1;

1> update the KeNB key based on the KASME key to which the current KeNB is associated, using the nextHopChainingCount value indicated in the RRCConnectionReestablishment message, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> derive the KRRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the KRRCenc key and the KUPenc key associated with the previously configured ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to activate integrity protection using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply ciphering using the previously configured algorithm, the KRRCenc key and the KUPenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> submit the RRCConnectionReestablishmentComplete message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue‘:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.23.1.3 Test description

8.2.4.23.1.3.1.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell and Cell 3 is the SCell

– 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.2.4.23.1.3.2 Test procedure sequence

Table 8.2.4.23.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", "T2", "T3" and "T4" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.4.23.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

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

The power level values are assigned to satisfy SrxlevCell 3 < 0 such that selecting Cell 1 is guaranteed

(NOTE 1).

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3> M1).

(NOTE 1).

T4

Cell-specific RS EPRE

dBm/15kHz

"Off"

-79

The power level values are assigned to satisfy SrxlevCell 1 < 0 such that selecting Cell 3 is guaranteed.

(NOTE 1).

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.23.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 Cell 3 as an SCell.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup event A3 reporting configuration.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

5

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.23.1.3.2-1.

6

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

7

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3 and to release SCell Cell 3.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 8 the steps specified in Table 8.2.4.23.1.3.2-3 should take place.

8

The SS changes Cell 1 and Cell 3 parameters according to the row "T2" in table 8.2.4.23.1.3.2-1.

9

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

–>

RRCConnectionReestablishmentRequest

1

P

10

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 1.

<–

RRCConnectionReestablishment

11

The UE transmits an RRCConnectionReestablishmentComplete message

–>

RRCConnectionReestablishmentComplete

=

12

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer on Cell 1 and configure Cell 3 as an SCell

<–

RRCConnectionReconfiguration

13

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1

–>

RRCConnectionReconfigurationtComplete

14

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup event A3 reporting configuration.

<–

RRCConnectionReconfiguration

15

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

16

The SS changes Cell 1 and Cell 3 parameters according to the row "T3" in table 8.2.4.23.1.3.2-1.

17

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

18

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform handover to Cell 3 and to release SCell Cell3.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 19 the steps specified in Table 8.2.4.23.1.3.2-3 should take place.

19

The SS changes Cell 1 and Cell 3 parameters according to the row "T4" in table 8.2.4.23.1.3.2-1.

20

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

–>

RRCConnectionReestablishmentRequest

2

P

21

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 3.

<–

RRCConnectionReestablishment

22

The UE transmits an RRCConnectionReestablishmentComplete message

–>

RRCConnectionReestablishmentComplete

23

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

<–

RRCConnectionReconfiguration

24

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3.

–>

RRCConnectionReconfigurationtComplete

Table 8.2.4.23.1.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the inter frequency handover using MAC Random Access Preamble on Cell 3.

2

The SS does not respond.

8.2.4.23.1.3.3 Specific message contents

Table 8.2.4.23.1.3.3-00: Conditions for specific message contents
in Tables 8.2.4.23.1.3.3-2, 8.2.4.23.1.3.3-5 and 8.2.4.23.1.3.3-9.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.23.1.3.3-0: SystemInformationBlockType2 for Cell 1 and cell 3 (preamble and all the steps in Table 8.2.4.23.3.2-2)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n50

}

Table 8.2.4.23.1.3.3-1: RRCConnectionReconfiguration (steps 1 and 12, Table 8.2.4.23.1.3.2-2)

Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod

Table 8.2.4.23.1.3.3-2: SCellToAddMod-r10-f2 (Table 8.2.4.23.1.3.3-1)

Derivation Path: 36.508 clause 4.6.1 table 4.6.3-19D SCellToAddMod-r10-DEFAULT

Information Element

Value/remark

Comment

Condition

SCellToAddMod-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

1 entry

sCellIndex-r10[1]

1

cellIdentification-r10[1] SEQUENCE {

physCellId-r10[1]

Physical Cell Identity of Cell 3

dl-CarrierFreq-r10[1]

Same downlink EARFCN as used for Cell 3

dl-CarrierFreq-r10[1]

maxEARFCN

Band > 64

}

radioResourceConfigCommonSCell-r10[1]

RadioResourceConfigCommonSCell-r10-f2

dl-CarrierFreq-v1090[1]

Same downlink EARFCN as used for Cell 3

Band > 64

}

Table 8.2.4.23.1.3.3-3: RadioResourceConfigCommonSCell-r10-f2 (Table 8.2.4.23.1.3.3-2)

Derivation Path: 36.508 clause 4.6.3 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

}

}

Table 8.2.4.23.1.3.3-4: RRCConnectionReconfiguration (steps 3 and 14, Table 8.2.4.23.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.23.1.3.3-5: MeasConfig (Table 8.2.4.23.1.3.3-4)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

Cell 1

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

Cell 3

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfig-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.23.1.3.3-6: ReportConfig-A3 (Table 8.2.4.18.1.3.3-5)

Derivation path: 36.508, Table 4.6.6-6

Information Element

Value/Remark

Comment

Condition

ReportConfigEUTRA-A3 ::= SEQUENCE {

triggerType CHOICE {

event SEQUENCE {

timeToTrigger

ms2560

}

}

}

Table 8.2.4.23.1.3.3-7: MeasurementReport (steps 6 and 17, Table 8.2.4.23.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults ::= SEQUENCE {

measId

1

measResultPCell ::= SEQUENCE {

Report Cell 1

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

physicalCellId of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

measResultForECID-r9

Not present

locationInfo-r10

Not present

measResultServFreqList-r10 SEQUENCE (SIZE (1..maxServCell-r10)) OF SEQUENCE {

servFreqId-r10

1

measResultSCell-r10 SEQUENCE {

Cell 3

rsrpResultSCell-r10

(0..97)

rsrqResultSCell-r10

(0..34)

}

}

}

}

}

}

}

Table 8.2.4.23.1.3.3-8: RRCConnectionReconfiguration (steps 7 and 18, Table 8.2.4.23.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

SCellToReleaseList-r10 ::= SEQUENCE (SIZE (1..maxSCell-r10)) OF SEQUENCE {

SCellIndex-r10[1]

1

}

SCellToAddModList-r10

Not present

}

}

}

}

}

}

}

Table 8.2.4.23.1.3.3-9: MobilityControlInfo (Table 8.2.4.23.1.3.3-8)

Derivation Path: 36.308, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

rach-ConfigDedicated SEQUENCE {

ra-PreambleIndex

63

ra-PRACH-MaskIndex

0

}

}

Table 8.2.4.23.1.3.3-10: RRCConnectionReestablishmentRequest (steps 9 and 20, Table 8.2.4.23.1.3.2-2)

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

handoverFailure

}

}

}

Table 8.2.4.23.1.3.3-11: RRCConnectionReestablishment (steps 10 and 21, Table 8.2.4.23.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-10

Information Element

Value/remark

Comment

Condition

RRCConnectionReestablishment ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReestablishment-r8 SEQUENCE {

nextHopChainingCount

0

}

}

}

}

8.2.4.23.2 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Inter-band CA

The scope and description of the present TC is the same as test case 8.2.4.23.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 Inactive SCells according to [18] cl. 6.3.4

8.2.4.23.3 CA / RRC connection reconfiguration / Handover / Failure / Re-establishment successful / Intra-band non-Contiguous CA

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

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

8.2.4.24 Void

8.2.4.24.1 Void

8.2.4.25 Dual Connectivity / RRC connection reconfiguration / Handover

8.2.4.25.1 RRC connection reconfiguration / Intra-MeNB Handover / MCG DRB to MCG DRB and MCG DRB to/from SCG DRB

8.2.4.25.1.1 Test Purpose (TP)

(1)

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

ensure that {

when { the UE receives a RRCConnectionReconfiguration message including mobilityControlInfo indicating a different E-UTRA frequency }
then { the UE responds with a RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in connected mode with SCG activated has performed handover to another PCell keeping the UE context for the MCG DRB and SCG DRB }
ensure that {
when
{ uplink data are submitted for transmission on the MCG/SCG DRBs }
then { the UE transmits the uplink data on the radio bearer associated with the MCG/SCG DRBs respectively }
}

(3)

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

ensure that {

when { the UE receives a RRCConnectionReconfiguration message including mobilityControlInfo indicating a different E-UTRA frequency and to change of one of the MCG DRBs to a SCG DRB }
then { the UE responds with a RRCConnectionReconfigurationComplete message }

}

(4)

with { UE in connected mode with SCG activated has performed handover to another PCell and has re-configured a MCG DRB to a SCG DRB }
ensure that {
when
{ uplink data are submitted for transmission on the MCG/SCG DRBs }
then { the UE transmits the uplink data on the radio bearer associated with the MCG/SCG DRBs respectively }
}

(5)

with { UE in connected mode with SCG activated with a MCG DRB and two SCG DRBs established }

ensure that {

when { the UE receives a RRCConnectionReconfiguration message including mobilityControlInfo indicating a different E-UTRA frequency and to change of one of the SCG DRBs to a MCG DRB }
then { the UE responds with a RRCConnectionReconfigurationComplete message }

}

(6)

with { UE in connected mode with SCG activated has performed handover to another PCell and has re-configured a SCG DRB to a MCG DRB }
ensure that {
when
{ uplink data are submitted for transmission on the MCG/SCG DRBs }
then { the UE transmits the uplink data on the radio bearer associated with the MCG/SCG DRBs respectively }
}

8.2.4.25.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.3a1, 5.3.10.12. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if drb-ToAddModListSCG is received and includes the drb-Identity value; and drb-Identity value is not part of the current UE configuration (i.e. DC specific DRB establishment):

2> if drb-ToAddModList is received and includes the drb-Identity value (i.e. add split DRB):

3> establish a PDCP entity and configure it with the current MCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModList;

3> establish an MCG RLC entity and an MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig included in drb-ToAddModList;

3> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

2> else (i.e. add SCG DRB):

3> establish a PDCP entity and configure it with the current SCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModListSCG;

3> establish an SCG RLC entity or entities and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

2> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

1> else (i.e. DC specific DRB modification; drb-ToAddModList and/ or drb-ToAddModListSCG received):

2> if the DRB indicated by drb-Identity is a split DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. split to MCG):

4> release the SCG RLC entity and the SCG DTCH logical channel;

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

3> else (i.e. reconfigure split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

2> if the DRB indicated by drb-Identity is an SCG DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. SCG to MCG):

4> reconfigure the PDCP entity with the current MCG security configuration and in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity or entities and the SCG DTCH logical channel to be an MCG RLC entity or entities and an MCG DTCH logical channel;

4> reconfigure the MCG RLC entity or entities and/ or the MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig, if included in drb-ToAddModList;

3> else (i.e. drb-ToAddModListSCG is received and includes the drb-Identity value i.e. reconfigure SCG):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the SCG RLC entity or entities and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

2> if the DRB indicated by drb-Identity is an MCG DRB:

3> if drb-ToAddModListSCG is received and includes the drb-Identity value, while for this entry drb-Type is included and set to split (i.e. MCG to split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG, included in drb-ToAddModListSCG;

3> else (i.e. drb-Type is included and set to scg i.e. MCG to SCG):

4> reconfigure the PDCP entity with the current SCG security configuration and in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the MCG RLC entity or entities and the MCG DTCH logical channel to be an SCG RLC entity or entities and an SCG DTCH logical channel;

4> reconfigure the SCG RLC entity or entities and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

[TS 36.331, clause 5.3.10.12]

The UE shall:

1> for each split or SCG DRBs that is part of the current configuration:

2> if the corresponding drb-Identity value is included in the received drb-ToAddModList; and:

2> if the corresponding drb-Identity value is not included in the received drb-ToAddModListSCG (i.e. reconfigure split, split to MCG or SCG to MCG):

3> perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1;

8.2.4.25.1.3 Test description

8.2.4.25.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the interfrequency neighbour cell and Cell 10 is the PSCell.

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

UE:

Preamble:

– The UE is in state DC MCG/SCG DRB Loopback Activated (state 6A) on Cell 1 and Cell 10 according to [18], UE has 3 DRBs configured. DRB 1(Default bearer) and DRB 2(dedicated bearer) as MCG DRB’s and DRB 3 (dedicated bearer) as SCG bearer.

8.2.4.25.1.3.2 Test procedure sequence

Table 8.2.4.6.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, T2" 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.2.4.25.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Cell 10

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-73

-97

-75

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

-75

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

-73

-85

-75

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 8.2.4.25.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 setup inter frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.6.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

The SS transmits one IP packet to the UE on each of DRB 1 and DRB 2 on Cell 3, DRB 3 on Cell 10 (PSCell).

<–

IP packets

8

Check: Does the UE loops back the IP packet on each of DRB 1 and DRB 2 on Cell 3, DRB 3 on Cell 10 (PSCell)?

–>

IP packets

2

P

8A

The SS transmits an RRCConnectionReconfiguration message on Cell 3 to setup inter frequency measurement.

<–

RRCConnectionReconfiguration

8B

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3.

–>

RRCConnectionReconfigurationComplete

9

The SS changes Cell 1 and Cell 3 parameters according to the row "T2" in table 8.2.4.6.3.2-1.

10

The UE transmits a MeasurementReport message on Cell 3 to report event A3 with the measured RSRP, RSRQ value for Cell 1.

–>

MeasurementReport

11

The SS transmits an RRCConnectionReconfiguration message on Cell 3 to order the UE to perform inter frequency handover to Cell 1 and to change of one of the MCG DRBs to a SCG DRB.

<–

RRCConnectionReconfiguration

12

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

3

P

13

The SS transmits one IP packet to the UE on each of DRB 1 on Cell 1, DRB 2 and DRB 3 on Cell 10 (PSCell).

<–

IP packets

14

Check: Does the UE loops back the IP packet on each of DRB 1 on Cell 1, DRB 2 and DRB 3 on Cell 10 (PSCell)?

–>

IP packets

4

P

14A

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter frequency measurement.

<–

RRCConnectionReconfiguration

14B

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

15

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.6.3.2-1.

16

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

17

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3 and to change of one of the SCG DRBs to a MCG DRB.

<–

RRCConnectionReconfiguration

18

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

5

P

19

The SS transmits one IP packet to the UE on each of DRB 1 and DRB 2 on Cell 3, DRB 3 on Cell 10 (PSCell).

<–

IP packets

20

Check: Does the UE loops back the IP packet on each of DRB 1 and DRB 2 on Cell 3, DRB 3 on Cell 10 (PSCell)?

–>

IP packets

6

P

8.2.4.25.1.3.3 Specific message contents

Table 8.2.4.25.1.3.3-0: Conditions for specific message contents
in Tables 8.2.4.25.1.3.3-2, 8.2.4.25.1.3.3-5, 8.2.4.25.1.3.3-7 and 8.2.4.25.1.3.3-10.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.25.1.3.3-1: RRCConnectionReconfiguration (step 1, 8A, 14A, Table 8.2.4.25.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.25.1.3.3-2: MeasConfig (step 1/14A, Table 8.2.4.25.1.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.25.1.3.3-2A: MeasConfig (step 8A, Table 8.2.4.25.1.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.25.1.3.3-3: MeasurementReport (step 4, 16, Table 8.2.4.25.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.25.1.3.3-3A: MeasurementReport (step 10, Table 8.2.4.25.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.25.1.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.25.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.25.1.3.3-5: MobilityControlInfo (Table 8.2.4.25.1.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.25.1.3.3-6: RRCConnectionReconfiguration (step 11, Table 8.2.4.25.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO and tbd

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

scg-Configuration-r12

SCG-Configuration-r12-MCGToSCG

}

}

}

}

}

}

}

Table 8.2.4.25.1.3.3-7: MobilityControlInfo (Table 8.2.4.25.1.3.3-6)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

}

}

Table 8.2.4.25.1.3.3-8: SCG-Configuration-r12-MCGToSCG(Table 8.2.4.25.1.3.3-6)

Derivation Path: 36.508 clause 4.6.3-19F conditon PSCell_Add_SCG_DRB

Information Element

Value/remark

Comment

Condition

scg-Configuration-r12 CHOICE {

setup SEQUENCE {

scg-ConfigPartMCG-r12 SEQUENCE {

scg-Counter-r12

Not Present

powerCoordinationInfo-r12

Not Present

}

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12 SEQUENCE {

drb-ToAddModListSCG-r12 SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

1 entry

DRB-ToAddModSCG-r12[1] SEQUENCE {

drb-Identity-r12

Same as DRB 2 established as MCG bearer in preamble

drb-Type-r12 CHOICE {

scg-r12 SEQUENCE {

eps-BearerIdentity-r12

Not Present

pdcp-Config-r12

Not Present

}

}

rlc-ConfigSCG-r12

Not Present

rlc-Config-v1250

Not present

logicalChannelIdentitySCG-r12

4

logicalChannelConfigSCG-r12

LogicalChannelConfig-DRB using condition LO

}

}

mac-MainConfigSCG-r12

Not present

rlf-TimersAndConstantsSCG-r12

Not present

}

sCellToReleaseListSCG-r12

Not Present

pSCellToAddMod-r12

Not Present

sCellToAddModListSCG-r12

Not Present

mobilityControlInfoSCG-r12

Not Present

}

}

}

Table 8.2.4.25.1.3.3-9: RRCConnectionReconfiguration (step 17, Table 8.2.4.25.1.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.25.1.3.3-10: MobilityControlInfo (Table 8.2.4.25.1.3.3-9)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.25.1.3.3-11: RadioResourceConfigDedicated (Table 8.2.4.25.1.3.3-9)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.25.1.3.3-12: DRB-ToAddMod-DEFAULT(Table 8.2.4.25.1.3.3-11)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

Same as DRB 2 established as MCG bearer in preamble

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Same as DRB 2 established as MCG bearer in preamble

logicalChannelConfig

Not Present

drb-TypeChange-r12

toMCG

}

8.2.4.25.2 RRC connection reconfiguration / Intra-MeNB Handover / MCG DRBs to/from Split DRB

8.2.4.25.2.1 Test Purpose (TP)

(1)

with { UE in connected mode }

ensure that {

when { the UE receives a RRCConnectionReconfiguration message including mobilityControlInfo indicating a different E-UTRA frequency and to change from the MCG DRB to a Split DRB }
then { the UE responds with a RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in connected mode with SCG activated has performed handover to another PCell and has re-configured a MCG DRB to a Split DRB }
ensure that {
when
{ uplink data are submitted for transmission on the MCG/Split DRBs }
then { the UE transmits the uplink data on the radio bearer associated with the MCG/Split DRBs respectively }
}

(3)

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

ensure that {

when { the UE receives a RRCConnectionReconfiguration message including mobilityControlInfo indicating a different E-UTRA frequency and to change from the Split DRB to a MCG DRB }
then { the UE responds with a RRCConnectionReconfigurationComplete message }

}

(4)

with { UE in connected mode with SCG activated has performed handover to another PCell and has re-configured a Split DRB to a MCG/SCG DRB }
ensure that {
when
{ uplink data are submitted for transmission on the MCG/Split DRBs }
then { the UE transmits the uplink data on the radio bearer associated with the MCG/Split DRBs respectively }
}

8.2.4.25.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.3a1, 5.3.10.12. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> if drb-ToAddModListSCG is received and includes the drb-Identity value; and drb-Identity value is not part of the current UE configuration (i.e. DC specific DRB establishment):

2> if drb-ToAddModList is received and includes the drb-Identity value (i.e. add split DRB):

3> establish a PDCP entity and configure it with the current MCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModList;

3> establish an MCG RLC entity and an MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig included in drb-ToAddModList;

3> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

2> else (i.e. add SCG DRB):

3> establish a PDCP entity and configure it with the current SCG security configuration and in accordance with the pdcp-Config included in drb-ToAddModListSCG;

3> establish an SCG RLC entity or entities and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG included in drb-ToAddModListSCG;

2> indicate the establishment of the DRB(s) and the eps-BearerIdentity of the established DRB(s) to upper layers;

1> else (i.e. DC specific DRB modification; drb-ToAddModList and/ or drb-ToAddModListSCG received):

2> if the DRB indicated by drb-Identity is a split DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. split to MCG):

4> release the SCG RLC entity and the SCG DTCH logical channel;

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

3> else (i.e. reconfigure split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

2> if the DRB indicated by drb-Identity is an SCG DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. SCG to MCG):

4> reconfigure the PDCP entity with the current MCG security configuration and in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity or entities and the SCG DTCH logical channel to be an MCG RLC entity or entities and an MCG DTCH logical channel;

4> reconfigure the MCG RLC entity or entities and/ or the MCG DTCH logical channel in accordance with the rlc-Config, logicalChannelIdentity and logicalChannelConfig, if included in drb-ToAddModList;

3> else (i.e. drb-ToAddModListSCG is received and includes the drb-Identity value i.e. reconfigure SCG):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the SCG RLC entity or entities and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

2> if the DRB indicated by drb-Identity is an MCG DRB:

3> if drb-ToAddModListSCG is received and includes the drb-Identity value, while for this entry drb-Type is included and set to split (i.e. MCG to split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> establish an SCG RLC entity and an SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG, included in drb-ToAddModListSCG;

3> else (i.e. drb-Type is included and set to scg i.e. MCG to SCG):

4> reconfigure the PDCP entity with the current SCG security configuration and in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the MCG RLC entity or entities and the MCG DTCH logical channel to be an SCG RLC entity or entities and an SCG DTCH logical channel;

4> reconfigure the SCG RLC entity or entities and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG, logicalChannelIdentitySCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

[TS 36.331, clause 5.3.10.12]

The UE shall:

1> for each split or SCG DRBs that is part of the current configuration:

2> if the corresponding drb-Identity value is included in the received drb-ToAddModList; and:

2> if the corresponding drb-Identity value is not included in the received drb-ToAddModListSCG (i.e. reconfigure split, split to MCG or SCG to MCG):

3> perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1;

8.2.4.25.2.3 Test description

8.2.4.25.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the interfrequency neighbour cell and Cell 10 is the PSCell.

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

UE:

Preamble:

– The UE is in state DC Loopback Activated (state 6) on Cell 1 according to [18], UE has 2 DRBs configured. DRB 1(Default bearer) and DRB 2(dedicated bearer) as MCG DRB.

8.2.4.25.2.3.2 Test procedure sequence

Table 8.2.4.6.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, T2" 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.2.4.25.2.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 3

Cell 10

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-73

-97

-75

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

-75

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

T2

Cell-specific RS EPRE

dBm/15kHz

-73

-85

-75

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 8.2.4.25.2.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 setup inter frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.25.2.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3 and to change from the MCG DRB to a Split DRB.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

The SS transmits one IP packet to the UE on Cell 3 on each 2 DRB’s.

<–

IP packets

8

Check: Does the UE loop back the IP packet on Cell 3 on each of 2 DRB’s?

(NOTE)–>

IP packets

2

P

8A

The SS transmits an RRCConnectionReconfiguration message on Cell 3 to setup inter frequency measurement.

<–

RRCConnectionReconfiguration

8B

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3.

–>

RRCConnectionReconfigurationComplete

9

The SS changes Cell 1 and Cell 3 parameters according to the row "T2" in table 8.2.4.25.2.3.2-1.

10

The UE transmits a MeasurementReport message on Cell 3 to report event A3 with the measured RSRP, RSRQ value for Cell 1.

–>

MeasurementReport

11

The SS transmits an RRCConnectionReconfiguration message on Cell 3 to order the UE to perform inter frequency handover to Cell 1 and to change from the Split DRB to a MCG DRB.

<–

RRCConnectionReconfiguration

12

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

3

P

13

The SS transmits one IP packet to the UE on Cell 1 on all each 2 DRB’s.

<–

IP packets

14

Check: Does the UE loop back the IP packet on Cell1 on each of 2 DRB’s?

–>

IP packets

4

P

NOTE: The UE loops back the IP packet via Cell 10 (PSCell) at PHY/MAC/RLC level, which is then routed within the SS to the PCell’s PDCP entity. UE’s lower layer transmission on Cell 10 (PSCell) is implicitly tested by assigning an UL Grant only on Cell 10.

8.2.4.25.2.3.3 Specific message contents

Table 8.2.4.25.2.3.3-0: Conditions for specific message contents
in Tables 8.2.4.25.2.3.3-2, 8.2.4.25.2.3.3-5 and 8.2.4.25.2.3.3-7.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.25.2.3.3-1: RRCConnectionReconfiguration (step 1, step 8A, Table 8.2.4.25.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.25.2.3.3-2: MeasConfig (step 1, Table 8.2.4.25.2.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.25.2.3.3-2A: MeasConfig (step 8A, Table 8.2.4.25.2.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.25.2.3.3-3: MeasurementReport (step 4, Table 8.2.4.25.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.25.2.3.3-3A: MeasurementReport (step 10, Table 8.2.4.25.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 1

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.25.2.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.25.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO and PSCell_Add_Split_DRB

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

scg-Configuration-r12

SCG-Configuration-r12

}

}

}

}

}

}

}

Table 8.2.4.25.2.3.3-5: MobilityControlInfo (Table 8.2.4.25.2.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.25.2.3.3-5a: SCG-Configuration-r12 (Table 8.2.4.25.2.3.3-4)

Derivation Path: 36.508 Table 4.6.3-19F conditon PSCell_Add_Split_DRB

Information Element

Value/remark

Comment

Condition

scg-Configuration-r12 CHOICE {

setup SEQUENCE {

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12 SEQUENCE {

drb-ToAddModListSCG-r12 SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

1 entry

DRB-ToAddModSCG-r12[1] SEQUENCE {

drb-Identity-r12

Same as DRB 2 established as MCG bearer in preamble

drb-Type-r12 CHOICE {

split-r12

NULL

}

rlc-ConfigSCG-r12

RLC-Config-DRB-AM

rlc-Config-v1250

Not present

logicalChannelIdentitySCG-r12

4

drb-Identity-r12+2

logicalChannelConfigSCG-r12

LogicalChannelConfig-DRB using condition LO

}

}

mac-MainConfigSCG-r12

Not present

rlf-TimersAndConstantsSCG-r12

Not present

}

}

Table 8.2.4.25.2.3.3-6: RRCConnectionReconfiguration (step 11, Table 8.2.4.25.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.25.2.3.3-7: MobilityControlInfo (Table 8.2.4.25.2.3.3-6)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 1

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 1

}

}

Table 8.2.4.25.2.3.3-8: RadioResourceConfigDedicated (Table 8.2.4.25.2.3.3-6)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.25.2.3.3-9: DRB-ToAddMod-DEFAULT(Table 8.2.4.25.2.3.3-8)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

Same as DRB 2 established as MCG bearer in preamble

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Same as DRB 2 established as MCG bearer in preamble

logicalChannelConfig

Not Present

drb-TypeChange-r12

toMCG

}

8.2.4.25.3 RRC connection reconfiguration / Intra-MeNB Handover / Split DRB to Split DRB

8.2.4.25.3.1 Test Purpose (TP)

(1)

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

ensure that {

when { the UE is receiving a RRCConnectionReconfiguration message including mobilityControlInfo indicating a different E-UTRA frequency for the PCell and keeping the current PSCell and the Split DRB }

then { the UE responds with a RRCConnectionReconfigurationComplete message }

}

(2)

With { UE in connected mode with SCG activated has performed handover to another PCell keeping the PSCell and the Split DRB }
ensure that {
when { uplink data are submitted for transmission on the Split DRB }
then { the UE transmits the uplink data on the radio bearer associated with the Split DRB }
}

8.2.4.25.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.10 and 5.3.10.12. Unless otherwise stated these are Rel-12 requirements.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> …;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MCG MAC and SCG MAC, if configured;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish MCG RLC and SCG RLC, if configured, for all RBs that are established;

1> configure lower layers to consider the SCell(s) other than the PSCell, if configured, to be in deactivated state;

1> apply the value of the newUE-Identity as the C-RNTI;

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> …;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> …;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the KASME key taken into use with the latest successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> if connected as an RN:

3> derive the KUPint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> if connected as an RN:

2> …;

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList:

2> …;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList:

2> …;

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

1> if the received RRCConnectionReconfiguration includes the systemInformationBlockType1Dedicated:

2> perfom the actions upon reception of the SystemInformationBlockType1 message as specified in 5.2.2.7;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> perform the measurement identity autonomous removal as specified in 5.5.2.2a;

1> release reportProximityConfig and clear any associated proximity status reporting timer;

1> if the RRCConnectionReconfiguration message includes the otherConfig:

2> perform the other configuration procedure as specified in 5.3.10.9;

1> if the RRCConnectionReconfiguration message includes the sl-DiscConfig or sl-CommConfig:

2> …;

1> if the RRCConnectionReconfiguration message includes wlan-OffloadInfo:

2> …;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report:

3> …;

2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and if T330 is not running:

3> …;

2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport:

3> include the logMeasAvailable;

2> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport:

3> …;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target PCell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target PCell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target PCell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> if the UE is configured to provide IDC indications:

3> …:

2> if the UE is configured to provide power preference indications:

3> …:

2> if SystemInformationBlockType15 is broadcast by the PCell:

3> …;

2> if SystemInformationBlockType18 is broadcast by the target PCell; and the UE transmitted a SidelinkUEInformation message including commRxInterestedFreq or commTxResourceReq during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo; or

2> if SystemInformationBlockType19 is broadcast by the target PCell; and the UE transmitted a SidelinkUEInformation message including discRxInterest or discTxResourceReq during the last 1 second preceding reception of the RRCConnectionReconfiguration message including mobilityControlInfo:

3> …;

2> the procedure ends;

NOTE 4: The UE is not required to determine the SFN of the target PCell by acquiring system information from that cell before performing RACH access in the target PCell.

[TS 36.331, clause 5.3.10.10]

The UE shall:

1> if the received scg-Configuration is set to release or includes the mobilityControlInfoSCG (i.e. SCG release/ change):

2> if mobilityControlInfo is not received (i.e. SCG release/ change without HO):

3> …;

1> if the received scg-Configuration is set to release:

2> …;

1> else:

2> if the received scg-ConfigPartMCG includes the scg-Counter:

3> update the S-KeNB key based on the KeNB key and using the received scg-Counter value, as specified in TS 33.401 [32];

3> derive the KUPenc key associated with the cipheringAlgorithmSCG included in mobilityControlInfoSCG within the received scg-ConfigPartSCG, as specified in TS 33.401 [32];

3> configure lower layers to apply the ciphering algorithm and the KUPenc key;

2> if the received scg-ConfigPartSCG includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> if the received scg-ConfigPartSCG includes the pSCellToAddMod:

3> perform PSCell addition or modification as specified in 5.3.10.3c;

2> if the received scg-ConfigPartSCG includes the sCellToReleaseListSCG:

3> …;

2> if the received scg-ConfigPartSCG includes the sCellToAddModListSCG:

3> perform SCell addition or modification as specified in 5.3.10.3b;

2> configure lower layers in accordance with mobilityControlInfoSCG, if received;

2> if the received scg-ConfigPartSCG includes the mobilityControlInfoSCG (i.e. SCG change):

3> …;

NOTE 2: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

[TS 36.331, clause 5.3.10.12]

The UE shall:

1> for each split or SCG DRBs that is part of the current configuration:

2> if the corresponding drb-Identity value is included in the received drb-ToAddModList; and:

2> if the corresponding drb-Identity value is not included in the received drb-ToAddModListSCG (i.e. reconfigure split, split to MCG or SCG to MCG):

3> perform the DC specific DRB addition or reconfiguration as specified in 5.3.10.3a1;

8.2.4.25.3.3 Test description

8.2.4.25.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the source PCell, Cell 3 is the target PCell and Cell 10 is the PSCell.

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

UE:

Preamble:

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

8.2.4.25.3.3.2 Test procedure sequence

Table 8.2.4.25.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo (handover).

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3?

–>

RRCConnectionReconfigurationComplete

1

P

3

The SS transmits one IP packet to the UE on Cell 3 on the DRB associated with the Split DRB.

<–

IP packet

4

Check: Does the UE loop back the IP packet on Cell 3 on the Split DRB

(NOTE)?

–>

IP packet

2

P

NOTE: The UE loops back the IP packet via Cell 10 (PSCell) at PHY/MAC/RLC level, which is then routed within the SS to the PCell’s PDCP entity. UE’s lower layer transmission on Cell 10 (PSCell) is implicitly tested by assigning an UL Grant only on Cell 10

8.2.4.25.3.3.3 Specific message contents

Table 8.2.4.25.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.25.3.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

8.2.4.25.4 RRC connection reconfiguration / Handover with SCG release / MCG/SCG DRBs to MCG DRB

8.2.4.25.4.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCG activated with a MCG DRB and a SCG DRB established }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with release }

then { UE sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { uplink data are submitted for transmission on the radio bearer of the target PCell UE }

then { UE transmits the uplink data on the radio bearer associated with the dedicated EPS bearer context }

}

8.2.4.25.4.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.4 and 5.3.10.10.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.10]

1> if the received scg-Configuration is set to release:

2> release the entire SCG configuration, except for the DRB configuration (i.e. as configured by drb-ToAddModListSCG);

2> stop timer T313, if running;

2> stop timer T307, if running;

8.2.4.25.4.3 Test Description

8.2.4.25.4.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the target PCell and Cell 10 is the PSCell.

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

UE:

None.

Preamble:

– The UE is in state DC MCG/SCG DRB Loopback Activation (to state 6A).

8.2.4.25.4.3.2 Test procedure sequence

Table 8.2.4.25.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with release. RRCConnectionReconfiguration message contains the DEACTIVATE EPS BEARER CONTEXT REQUEST message

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

The UE transmits an ULInformationTransfer message containing a DEACTIVATE EPS BEARER CONTEXT ACCEPT message.

–>

ULInformationTransfer

4

The SS transmits one IP packet to the UE on Cell 3.

<–

IP packet

5

Check: Does the UE loops back the IP packet on Cell 3?

–>

IP packet

2

P

8.2.4.25.4.3.3 Specific message contents

Table 8.2.4.25.4.3.3-0: Conditions for specific message contents
in Table 8.2.4.25.4.3.3-2.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.25.4.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.25.4.3.2-1)

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

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

radioResourceConfigDedicated SEQUENCE {

drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

drb-Identity

3

‘ }

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

scg-Configuration-r12 CHOICE {

release

NULL

}

}

}

}

}

}

}

Table 8.2.4.25.4.3.3-2: MobilityControlInfo (Table 8.2.4.25.4.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

8.2.4.25.5 RRC connection reconfiguration / Handover with SCG release / Split DRB to MCG DRB

8.2.4.25.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCG activated with a with a Split DRB established }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with release }

then { UE sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { uplink data are submitted for transmission on the radio bearer of the target PCell UE }

then { UE transmits the uplink data on the radio bearer associated with the dedicated EPS bearer context }

}

8.2.4.25.5.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.3a1 and 5.3.10.10.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> else (i.e. DC specific DRB modification; drb-ToAddModList and/ or drb-ToAddModListSCG received):

2> if the DRB indicated by drb-Identity is a split DRB:

3> if drb-ToAddModList is received and includes the drb-Identity value, while for this entry drb-TypeChange is included and set to toMCG (i.e. split to MCG):

4> release the SCG RLC entity and the SCG DTCH logical channel;

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

[TS 36.331, clause 5.3.10.10]

1> if the received scg-Configuration is set to release:

2> release the entire SCG configuration, except for the DRB configuration (i.e. as configured by drb-ToAddModListSCG);

2> stop timer T313, if running;

2> stop timer T307, if running;

8.2.4.25.5.3 Test Description

8.2.4.25.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the target PCell and Cell 10 is the PSCell.

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

UE:

None.

Preamble:

– The UE is in state DC Split DRB Loopback Activation (to state 6B).

8.2.4.25.5.3.2 Test procedure sequence

Table 8.2.4.25.5.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with release.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

Void

4

The SS transmits one IP packet to the UE on Cell 3.

<–

IP packet

5

Check: Does the UE loops back the IP packet on Cell 3?

–>

IP packet

2

P

8.2.4.25.5.3.3 Specific message contents

Table 8.2.4.25.5.3.3-0: Conditions for specific message contents
in Table 8.2.4.25.5.3.3-2.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.25.5.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.25.5.3.2-1)

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

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

scg-Configuration-r12 CHOICE {

release

NULL

}

}

}

}

}

}

}

Table 8.2.4.25.5.3.3-2: MobilityControlInfo (Table 8.2.4.25.5.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.25.5.3.3-3: RadioResourceConfigDedicated-HO (Table 8.2.4.25.5.3.3-1)

Derivation Path: 36.331 clause 4.6.3-19

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-HO ::= SEQUENCE {

srb-ToAddModList

Not present

DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

eps-BearerIdentity

Not present

drb-Identity

2

pdcp-Config

Not present

rlc-Config

Not present

logicalChannelIdentity

Not present

logicalChannelConfig

Not present

drb-TypeChange-r12

toMCG

}

}

8.2.4.25.6 RRC connection reconfiguration / Handover with SCG reconfiguration / SCG DRB to SCG DRB

8.2.4.25.6.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCG activated with a MCG DRB and a SCG DRB established }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with scg-r12 }

then { UE sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { uplink data are submitted for transmission on the radio bearer of the target PCell UE }

then { UE transmits the uplink data on the radio bearer associated with the dedicated EPS bearer context }

}

8.2.4.25.6.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.10 and 5.3.10.3a1.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.10]

1> else:

2> if the received scg-ConfigPartSCG includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> if the received scg-ConfigPartSCG includes the pSCellToAddMod:

3> perform PSCell addition or modification as specified in 5.3.10.3c;

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> else (i.e. DC specific DRB modification; drb-ToAddModList and/ or drb-ToAddModListSCG received):

2> if the DRB indicated by drb-Identity is an SCG DRB:

3> else (i.e. drb-ToAddModListSCG is received and includes the drb-Identity value i.e. reconfigure SCG):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModListSCG;

4> reconfigure the SCG RLC entity or entities and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

8.2.4.25.6.3 Test Description

8.2.4.25.6.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the target PCell and Cell 10 is the PSCell.

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

UE:

None.

Preamble:

– The UE is in state DC MCG/SCG DRB Loopback Activation (to state 6A).

8.2.4.25.6.3.2 Test procedure sequence

Table 8.2.4.25.6.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with scg-r12.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message?

–>

RRCConnectionReconfigurationComplete

1

P

3

Void

4

The SS transmits one IP packet to the UE on Cell 3.

<–

IP packet

5

Check: Does the UE loops back the IP packet on Cell 3?

–>

IP packet

2

P

8.2.4.25.6.3.3 Specific message contents

Table 8.2.4.25.6.3.3-0: Conditions for specific message contents
in Table 8.2.4.25.6.3.3-2.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.25.6.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.25.6.3.2-1)

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

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

scg-Configuration-r12 CHOICE {

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12 SEQUENCE {

drb-ToAddModListSCG-r12 SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

1 entry

drb-Identity-r12

3

drb-Type-r12 CHOICE {

scg-r12 SEQUENCE {

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.4.25.6.3.3-2: MobilityControlInfo (Table 8.2.4.25.6.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

8.2.4.25.7 RRC connection reconfiguration / Handover with SCG reconfiguration / Split DRB to Split DRB

8.2.4.25.7.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state with SCG activated with a with a Split DRB established }

ensure that {

when { UE receives an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with split-r12 }

then { UE sends an RRCConnectionReconfigurationComplete message }

}

(2)

with { UE in E-UTRA RRC_CONNECTED state}

ensure that {

when { uplink data are submitted for transmission on the radio bearer of the target PCell UE }

then { UE transmits the uplink data on the radio bearer associated with the dedicated EPS bearer context }

}

8.2.4.25.7.2 Conformance requirements

References: The conformance requirements covered in the current TC is specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.10 and 5.3.10.3a1.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the scg-Configuration; or

1> if the current UE configuration includes one or more split DRBs and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList:

2> perform SCG reconfiguration as specified in 5.3.10.10;

[TS 36.331, clause 5.3.10.10]

1> else:

2> if the received scg-ConfigPartSCG includes the radioResourceConfigDedicatedSCG:

3> reconfigure the dedicated radio resource configuration for the SCG as specified in 5.3.10.11;

2> if the current UE configuration includes one or more split or SCG DRBs and the received RRCConnectionReconfiguration message includes radioResourceConfigDedicated including drb-ToAddModList:

3> reconfigure the SCG or split DRB by drb-ToAddModList as specified in 5.3.10.12;

2> if the received scg-ConfigPartSCG includes the pSCellToAddMod:

3> perform PSCell addition or modification as specified in 5.3.10.3c;

[TS 36.331, clause 5.3.10.3a1]

For the drb-Identity value for which this procedure is initiated, the UE shall:

1> else (i.e. DC specific DRB modification; drb-ToAddModList and/ or drb-ToAddModListSCG received):

2> if the DRB indicated by drb-Identity is a split DRB:

3> else (i.e. reconfigure split):

4> reconfigure the PDCP entity in accordance with the pdcp-Config, if included in drb-ToAddModList;

4> reconfigure the MCG RLC entity and/ or the MCG DTCH logical channel in accordance with the rlc-Config and logicalChannelConfig, if included in drb-ToAddModList;

4> reconfigure the SCG RLC entity and/ or the SCG DTCH logical channel in accordance with the rlc-ConfigSCG and logicalChannelConfigSCG, if included in drb-ToAddModListSCG;

8.2.4.25.7.3 Test Description

8.2.4.25.7.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the PCell, Cell 3 is the target PCell and Cell 10 is the PSCell.

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

UE:

None.

Preamble:

– The UE is in state DC Split DRB Loopback Activation (to state 6B).

8.2.4.25.7.3.2 Test procedure sequence

Table 8.2.4.25.7.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message containing mobilityControlInfo and SCG-Configuration-r12 with split-r12.

<–

RRCConnectionReconfiguration

2

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3?

–>

RRCConnectionReconfigurationComplete

1

P

3

Void

4

The SS transmits one IP packet to the UE on Cell 3 on the DRB associated with the Split DRB.

<–

IP packet

5

Check: Does the UE loops back the IP packet on Cell 3?

(NOTE)

–>

IP packet

2

P

NOTE: The UE loops back the IP packet via Cell 10 (PSCell) at PHY/MAC/RLC level, which is then routed within the SS to the PCell’s PDCP entity. UE’s lower layer transmission on Cell 10 (PSCell) is implicitly tested by assigning an UL Grant only on Cell 10.

8.2.4.25.7.3.3: Specific message contents

Table 8.2.4.25.7.3.3-0: Conditions for specific message contents
in Table 8.2.4.25.7.3.3-2.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.25.7.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.25.7.3.2-1)

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

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

scg-Configuration-r12 CHOICE {

scg-ConfigPartSCG-r12 SEQUENCE {

radioResourceConfigDedicatedSCG-r12 SEQUENCE {

drb-ToAddModListSCG-r12 SEQUENCE (SIZE (1..maxDRB)) OF SEQUENCE {

1 entry

drb-Identity-r12

2

drb-Type-r12 CHOICE {

split-r12

NULL

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.4.25.7.3.3-2: MobilityControlInfo (Table 8.2.4.25.7.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

8.2.4.26 eIMTA / RRC connection reconfiguration / Handover / Success

8.2.4.26.1 Test Purpose (TP)

(1)

with { UE having completed the radio bearer establishment and initial security activation procedure }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA frequency}

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.26.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue’:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.26.3 Test description

8.2.4.26.3.1 Pre-test conditions

System Simulator:

– Cell 1(TDD) is not supported eIMTA and Cell 3(TDD) is supported eIMTA.

– 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.2.4.26.3.2 Test procedure sequence

Table 8.2.4.26.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.2.4.26.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

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 8.2.4.26.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 setup inter frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.26.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

7

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

1

8.2.4.26.3.3 Specific message contents

Table 8.2.4.26.3.3-0: Conditions for specific message contents
in Tables 8.2.4.26.3.3-2 and 8.2.4.26.3.3-5.

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.2.4.26.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.26.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.26.3.3-2: MeasConfig (Table 8.2.4.26.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.26.3.3-3: MeasurementReport (step 4, Table 8.2.4.26.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.26.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.26.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.26.3.3-5: MobilityControlInfo (Table 8.2.4.26.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

Table 8.2.4.26.3.3-6: RadioResourceConfigDedicated-HO (Table 8.2.4.26.3.3-4)

Derivation Path: 36.508, Table 4.6.3-19

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated-HO ::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList

Not present

drb-ToReleaseList

Not present

mac-MainConfig

Not present

sps-Config

Not present

physicalConfigDedicated

PhysicalConfigDedicated- eIMTA

}

Table 8.2.4.26.3.3-7: PhysicalConfigDedicated-eIMTA (Table 8.2.4.26.3.3-6)

Derivation Path: 36.508 table 4.8.2.1.6-1A ,condition eIMTA

8.2.4.27 RRC connection reconfiguration / Handover / Success / Intra-frequency in Enhanced Coverage

8.2.4.27.1 Test Purpose (TP)

(1)

Void

(2)

with { UE supporting CE Mode A in E-UTRA RRC_CONNECTED state supports eventA3 for intra-frequency neighbouring cells and measurement configured for event A3 with event based periodical reporting }

ensure that {

when { Neighbour becomes offset better than serving }

then { UE sends MeasurementReport with correct measId for event A3 }

}

(3)

with { UE supporting CE Mode A in E-UTRA RRC_CONNECTED state supports intra-frequency handover and UE having completed the radio bearer establishment and initial security activation procedure and performed the intra frequency measurement }

ensure that {

when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.27.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 36.306, clauses 4.3.29.1, 4.3.29.3, 4.3.29.5.

[TS 36.306, clause 4.3.29.1]

ce-ModeA-r13

This field defines whether the UE supports operation in coverage enhancement mode A, as specified in TS 36.211 [17], TS 36.213 [22] and TS 36.331 [5], and PRACH CE levels 0 and 1 at Random Access, as specified in TS 36.321 [4]. It is mandatory for UEs of DL category M1 and UL category M1.

[TS 36.306, clause 4.3.29.3]

intraFreqA3-CE-ModeA-r13

This field defines whether the UE when operating in CE Mode A supports eventA3 for intra-frequency neighbouring cells in normal coverage and CE Mode A, as specified in TS 36.331 [5] and TS 36.133 [16]. It is mandatory for UEs of this release if ce-ModeA-r13 is supported.

[TS 36.306, clause 4.3.29.5]

intraFreqHO-CE-ModeA-r13

This field defines whether the UE when operating in CE Mode A supports intra-frequency handover to target cell in normal coverage and CE Mode A, as specified in TS 36.331 [5] and TS 36.133 [16]. It is mandatory for UEs of this release if ce-ModeA-r13 is supported.

8.2.4.27.3 Test description

8.2.4.27.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

– System information combination 1 as defined in TS 36.508 [18] clause 4.4.3.1 is used in Cell 1 and Cell 2.

UE:

None.

Preamble:

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

8.2.4.27.3.2 Test procedure sequence

Table 8.2.4.27.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.2.4.27.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy exit condition for event A3 (M2 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1).

Table 8.2.4.27.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Void

2

Void

3

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup intra frequency measurement.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

5

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.2.3.2-1.

6

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 2.

–>

MeasurementReport

2

P

7

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

8

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 2 using common preamble to confirm the successful completion of the intra frequency handover?

–>

RRCConnectionReconfigurationComplete

3

P

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?

8.2.4.27.3.3 Specific message contents

Table 8.2.4.27.3.3-1: Void

Table 8.2.4.27.3.3-2: Void

Table 8.2.4.27.3.3-3: RRCConnectionReconfiguration (step 3, Table 8.2.4.27.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.27.3.3-4: MeasConfig (Table 8.2.4.27.3.3-3)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measGapConfig

MeasGapConfig-CE

intraFreq-CE-NeedForGaps

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0[1]

Same downlink EARFCN as used for f1

}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

intraFreq-CE-NeedForGaps

For UE having set pc_intraFreq-CE-NeedForGaps to TRUE.

Table 8.2.4.27.3.3-5 MeasurementReport (step 6, Table 8.2.4.27.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.27.3.3-6: RRCConnectionReconfiguration (step 7, Table 8.2.4.27.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

systemInfomationBlockType1Dedicated-r11

Octet string of SystemInformationBlockType1-BR of Cell2

CEModeA,CEModeB

nonCriticalExtension ::= SEQUENCE {}

}

}

}

}

}

}

}

}

Table 8.2.4.27.3.3-7: MobilityControlInfo (Table 8.2.4.27.3.3-6)

Derivation Path: 36.508 clause 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

8.2.4.28 eCall Only mode / RRC connection reconfiguration / Inter-frequency Handover / Success

8.2.4.28.1 Test Purpose (TP)

(1)

with { UE in eCall Only mode and an eCall over IMS is ongoing }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo indicating a different E-UTRA frequency }

then { UE transmits an RRCConnectionReconfigurationComplete message }

}

8.2.4.28.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4, 5.3.10.4 and 5.3.10.6. Unless otherwise stated these are Rel-14 requirements.

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> if the carrierFreq is included:

2> consider the target cell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target cell to be one on the current frequency with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target cell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> reset MAC;

1> re-establish PDCP for all RBs that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

1> re-establish RLC for all RBs that are established;

1> apply the value of the newUE-Identity as the C-RNTI;

1> configure lower layers in accordance with the received radioResourceConfigCommon;

1> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received mobilityControlInfo;

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

2> perform the radio resource configuration procedure as specified in 5.3.10;

1> if the keyChangeIndicator received in the securityConfigHO is set to TRUE:

2> update the KeNB key based on the fresh KASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the KeNB key based on the current KeNB or the NH, using the nextHopChainingCount value indicated in the securityConfigHO, as specified in TS 33.401 [32];

1> store the nextHopChainingCount value;

1> if the securityAlgorithmConfig is included in the securityConfigHO:

2> derive the KRRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm, as specified in TS 33.401 [32];

1> else:

2> derive the KRRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

2> derive the KRRCenc key and the KUPenc key associated with the current ciphering algorithm, as specified in TS 33.401 [32];

1> configure lower layers to apply the integrity protection algorithm and the KRRCint key, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> configure lower layers to apply the ciphering algorithm, the KRRCenc key and the KUPenc key, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure;

1> perform the measurement related actions as specified in 5.5.6.1;

1> if the RRCConnectionReconfiguration message includes the measConfig:

2> perform the measurement configuration procedure as specified in 5.5.2;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

2> apply the parts of the CQI reporting configuration, the scheduling request configuration and the sounding RS configuration that do not require the UE to know the SFN of the target cell, if any;

2> apply the parts of the measurement and the radio resource configuration that require the UE to know the SFN of the target cell (e.g. measurement gaps, periodic CQI reporting, scheduling request configuration, sounding RS configuration), if any, upon acquiring the SFN of the target cell;

NOTE 3: Whenever the UE shall setup or reconfigure a configuration in accordance with a field that is received it applies the new configuration, except for the cases addressed by the above statements.

2> the procedure ends;

[TS 36.331, clause 5.3.10.4]

The UE shall:

1> reconfigure the MAC main configuration in accordance with the received mac-MainConfig;

[TS 36.331, clause 5.3.10.6]

The UE shall:

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

1> if the antennaInfo is included and set to ‘explicitValue’:

2> if the configured transmissionMode is not ‘tm3‘ or ‘tm4‘ release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

1> else if the antennaInfo is included and set to ‘defaultValue‘:

2> release ri-ConfigIndex in cqi-ReportPeriodic, if previously configured;

8.2.4.28.3 Test description

8.2.4.28.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 3 both supports eCall over IMS.

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

UE:

– The eCall capable UE is equipped with ‘eCall only’ enabled USIM configured as per TS 36.508 [18] Table 4.9.3.5-2.

Preamble:

– The UE has established an eCall over IMS according to [18] subclause 4.5A.27 by executing steps 1 to 25.

8.2.4.28.3.2 Test procedure sequence

Table 8.2.4.28.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.2.4.28.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

-97

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy exit condition for event A3 (M3 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-73

The power level values are such that measurement results for Cell 1 (M1) and Cell 3 (M3) satisfy entry condition for event A3 (M3 > M1).

Table 8.2.4.28.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 setup inter frequency measurement.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.28.3.2-1.

4

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 3.

–>

MeasurementReport

5

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

6

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover?

–>

RRCConnectionReconfigurationComplete

1

P

8.2.4.28.3.3 Specific message contents

Table 8.2.4.28.3.3-0: Conditions for specific message contents
in Tables 8.2.4.28.3.3-2 and 8.2.4.28.3.3-5

Condition

Explanation

Band > 64

If band > 64 is selected

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.28.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.2.4.28.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.28.3.3-2: MeasConfig (Table 8.2.4.28.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1 condition INTER-FREQ

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f2

measObject[2]

MeasObjectEUTRA-GENERIC(f2)

measObject[2]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f2

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f2

}

}

}

Table 8.2.4.28.3.3-3: MeasurementReport (step 4, Table 8.2.4.28.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 3

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.28.3.3-4: RRCConnectionReconfiguration (step 5, Table 8.2.4.28.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.28.3.3-5: MobilityControlInfo (Table 8.2.4.28.3.3-4)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 3

Band 24 High range

}

carrierFreq SEQUENCE {}

Not present

Band > 64

carrierFreq-v9e0 SEQUENCE {

Band > 64

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

}

}

8.2.4.29 UDC/ RRC connection reconfiguration / Handover / Success

8.2.4.29.1 Test Purpose (TP)

(1)

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

ensure that {

when { UE receives an RRCConnectionReconfiguration message including a mobilityControlInfo }

then { UE release the configured uplinkDataCompression and re-establish PDCP for all RBs configured with pdcp-config that are established }

}

8.2.4.29.2 Conformance requirements

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

[TS 36.331 clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> stop timer T310, if running;

1> stop timer T312, if running;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlInfo;

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellId;

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellId;

1> start synchronising to the DL of the target PCell;

NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message.

1> if BL UE or UE in CE:

2> if sameSFN-Indication is not present in mobilityControlInfo:

3> acquire the MasterInformationBlock in the target PCell;

1> if makeBeforeBreak is configured:

2> perform the remainder of this procedure including and following resetting MAC after the UE has stopped the uplink transmission/downlink reception with the source cell(s);

NOTE 1a: It is up to UE implementation when to stop the uplink transmission/ downlink reception with the source cell(s) to initiate re-tuning for connection to the target cell [16], if makeBeforeBreak is configured.

1> reset MCG MAC and SCG MAC, if configured;

1> release uplinkDataCompression, if configured;

1> re-establish PDCP for all RBs configured with pdcp-config that are established;

NOTE 2: The handling of the radio bearers after the successful completion of the PDCP re-establishment, e.g. the re-transmission of unacknowledged PDCP SDUs (as well as the associated status reporting), the handling of the SN and the HFN, is specified in TS 36.323 [8].

8.2.4.29.3 Test description

8.2.4.29.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2

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.2.4.29.3.2 Test procedure sequence

Table 8.2.4.29.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.2.4.29.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy exit condition for event A3 (M2 < M1).

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

The power level values are such that measurement results for Cell 1 (M1) and Cell 2 (M2) satisfy entry condition for event A3 (M2 > M1).

Table 8.2.4.29.3.2-2: 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 transmits an RRCConnectionReconfiguration message on Cell 1 to setup intra frequency measurement.

<–

RRCConnectionReconfiguration

7

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

8

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.2.3.2-1.

9

The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP, RSRQ value for Cell 2.

–>

MeasurementReport

10

The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

11

The UE transmits an RRCConnectionReconfigurationComplete message.

–>

RRCConnectionReconfigurationtComplete

12

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

13

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.2.4.29.3.3 Specific message contents

Table 8.2.4.29.3.3-1: RRCConnectionReconfiguration (step 6, Table 8.2.4.29.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.2.4.29.3.3-2: MeasConfig (Table 8.2.4.29.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-A3

reportConfig[1]

ReportConfigEUTRA-A3

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

IdReportConfig-A3

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

Band > 64

measObjectEUTRA-v9e0[1] SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

}

}

Table 8.2.4.29.3.3-3 MeasurementReport (step 9, Table 8.2.4.29.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5

Information Element

Value/remark

Comment

Condition

MeasurementReport ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

measurementReport-r8 SEQUENCE {

measResults SEQUENCE {

measId

1

measResultServCell SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

measResultNeighCells CHOICE {

measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {

1 entry

physCellId[1]

PhysicalCellIdentity of Cell 2

cgi-Info[1]

Not present

measResult[1] SEQUENCE {

rsrpResult

(0..97)

rsrqResult

(0..34)

}

}

}

}

}

}

}

}

Table 8.2.4.29.3.3-4: RRCConnectionReconfiguration (step 10, Table 8.2.4.29.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.29.3.3-5: MobilityControlInfo (Table 8.2.4.29.3.3-4)

Derivation Path: 36.508 clause 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq

Not present

}

8.2.4.30 RRC connection reconfiguration / Handover / DAPS Handover

8.2.4.30.1 RRC connection reconfiguration / Handover / DAPS Handover / Success / Intra-Frequency

8.2.4.30.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover }

ensure that {

when { UE receives an RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

then { UE performs DAPS handover to the target cell. For the DRB configured daps-HO, the UE continues to receive downlink data from both source and target eNBs for the DL and the UE transmits UL data to the source eNB }

}

(2)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { UE has performed random access procedure to the target cell successfully }

then { UE transmits an RRCReconfigurationComplete message and the UE switches its UL data transmission to the target eNB }

}

(3)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { UE receives an RRCConnectionReconfiguration message does not include the mobilityControlInfo and includes daps-SourceRelease }

then { UE stops to receive downlink data from source eNB and releases the radio link with source cell }

}

8.2.4.30.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.2.1.0 and 10.1.2.1.1 and TS 36.331 clause 5.3.5.3 and 5.3.5.4. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.2.1.0]

The intra E-UTRAN HO of a UE in RRC_CONNECTED state is a UE-assisted network-controlled HO, with HO preparation signalling in E-UTRAN:

– If DAPS handover is configured, the UE continues the downlink user data reception from the source eNB until releasing the source cell and continues the uplink user data transmission to the source eNB until successful random access procedure to the target eNB. Upon reception of the handover command, the UE:

– Creates a MAC entity for target cell;

– Establishes the RLC entity and an associated DTCH logical channel for target cell for each DRB configured with DAPS;

– For the DRB(s) configured with DAPS, reconfigures the PDCP entity to configure DAPS with separate security and ROHC functions for source and target and associates them with the RLC entities configured for source and target respectively;

– Retains rest of the source link configurations until release of the source.

– UE maintains only PCell connection with both source and target cells and any other configured serving cells are released by the network before the handover command is sent to the UE.

NOTE: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.

– If the access towards the target cell (using RACH or RACH-less procedure) is not successful within a certain time, the UE initiates radio link failure recovery using a suitable cell except in DAPS handover or CHO scenarios:

– When DAPS handover fails, the UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment if the source link is still available; Otherwise, RRC re-establishment is performed;

– When initial CHO execution attempt fails or Handover fails, if network configured the UE to try CHO after HO/CHO failure and the UE performs cell selection to a CHO candidate cell, the UE attempts CHO execution to that cell; Otherwise, RRC re-establishment is performed.

[TS 36.300, clause 10.1.2.1.1]

The preparation and execution phase of the HO procedure is performed without EPC involvement, i.e. preparation messages are directly exchanged between the eNBs. The release of the resources at the source side during the HO completion phase is triggered by the eNB. In case an RN is involved, its DeNB relays the appropriate S1 messages between the RN and the MME (S1-based handover) and X2 messages between the RN and target eNB (X2-based handover); the DeNB is explicitly aware of a UE attached to the RN due to the S1 proxy and X2 proxy functionality (see clause 4.7.6.6). The figure below depicts the basic handover scenario where neither MME nor Serving Gateway changes:

Figure 10.1.2.1.1-1: Intra-MME/Serving Gateway HO

Below is a more detailed description of the intra-MME/Serving Gateway HO procedure:

0 The UE context within the source eNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update.

1 The source eNB configures the UE measurement procedures according to the roaming and access restriction information and e.g. the available multiple frequency band information. Measurements provided by the source eNB may assist the function controlling the UE’s connection mobility.

2 A MEASUREMENT REPORT is triggered and sent to the eNB.

3 The source eNB makes decision based on MEASUREMENT REPORT and RRM information to hand off the UE.

4 The source eNB issues a HANDOVER REQUEST message to the target eNB passing necessary information to prepare the HO at the target side (UE X2 signalling context reference at source eNB, UE S1 EPC signalling context reference, target cell ID, KeNB*, RRC context including the C-RNTI of the UE in the source eNB, AS-configuration, E-RAB context and physical layer ID of the source cell + short MAC-I for possible RLF recovery). The source eNB may also request a DAPS Handover for one or more E-RABs. UE X2 / UE S1 signalling references enable the target eNB to address the source eNB and the EPC. The E-RAB context includes necessary RNL and TNL addressing information, and QoS profiles of the E-RABs.

5 Admission Control may be performed by the target eNB dependent on the received E-RAB QoS information to increase the likelihood of a successful HO, if the resources can be granted by target eNB. The target eNB configures the required resources according to the received E-RAB QoS information and reserves a C-RNTI and optionally a RACH preamble. The AS-configuration to be used in the target cell can either be specified independently (i.e. an "establishment") or as a delta compared to the AS-configuration used in the source cell (i.e. a "reconfiguration").

6 The target eNB prepares HO with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB. The HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE as an RRC message to perform the handover. The container includes a new C-RNTI, target eNB security algorithm identifiers for the selected security algorithms, may include a dedicated RACH preamble, and possibly some other parameters i.e. access parameters, SIBs, etc. If RACH-less HO is configured, the container includes timing adjustment indication and optionally a preallocated uplink grant. The HANDOVER REQUEST ACKNOWLEDGE message may also include RNL/TNL information for the forwarding tunnels, if necessary. The target eNB also indicates if a DAPS Handover is accepted.

NOTE 1: As soon as the source eNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated.

NOTE 1a: For E-RABs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source eNB, until SN assignment is handed over to the target eNB in step 11b, for which the normal data forwarding follows as defined in 10.1.2.3.

Steps 7 to 16 provide means to avoid data loss during HO and are further detailed in 10.1.2.1.2 and 10.1.2.3.

7 The target eNB generates the RRC message to perform the handover, i.e. RRCConnectionReconfiguration message including the mobilityControlInfo, to be sent by the source eNB towards the UE. The source eNB performs the necessary integrity protection and ciphering of the message.

The UE receives the RRCConnectionReconfiguration message with necessary parameters (i.e. new C-RNTI, target eNB security algorithm identifiers, and optionally dedicated RACH preamble, target eNB SIBs, etc.) and is commanded by the source eNB to perform the HO. If RACH-less HO is configured, the RRCConnectionReconfiguration includes timing adjustment indication and optionally preallocated uplink grant for accessing the target eNB. If preallocated uplink grant is not included, the UE should monitor PDCCH of the target eNB to receive an uplink grant. The UE does not need to delay the handover execution for delivering the HARQ/ARQ responses to source eNB.

If Make-Before-Break HO is configured, the connection to the source cell is maintained after the reception of RRCConnectionReconfiguration message with mobilityControlInfo before the UE executes initial uplink transmission to the target cell.

NOTE 2: If Make-Before-Break HO is configured, the source eNB decides when to stop transmitting to the UE.

NOTE 3: The UE can be configured with Make-Before-Break HO and RACH-less HO simultaneously.

In case of DAPS Handover, the UE does not detach from the source cell upon receiving the RRCConnectionReconfiguration message. The UE releases the source SRB resources, security configuration of the source cell and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node.

NOTE 3a: The DAPS Handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released.

NOTE 4: DC, CHO or RACH-less HO cannot be configured simultaneously with DAPS Handover.

NOTE 5: For E-RABs configured with DAPS, the source eNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target eNB in step 11a.

8a For E-RABs configured with DAPS, the source eNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source eNB forwards to the target eNB. The source eNB does not stop assigning PDCP SNs to downlink packets until it sends the SN STATUS TRANSFER message to the target eNB in step 11b.

8 For E-RABs not configured with DAPS, the source eNB sends the SN STATUS TRANSFER message to the target eNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of E-RABs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL SDU and may include a bit map of the receive status of the out of sequence UL SDUs that the UE needs to retransmit in the target cell, if there are any such SDUs. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target eNB shall assign to new SDUs, not having a PDCP SN yet. The source eNB may omit sending this message if none of the E-RABs of the UE shall be treated with PDCP status preservation.

NOTE 6: In case of DAPS Handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for an E-RAB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 11b instead of step 8.

NOTE 7: For E-RABs configured with DAPS, the source eNB may additionally send the EARLY STATUS TRANSFER message(s) between step 8 and step 11b, to inform discarding of already forwarded PDCP SDUs. The target eNB does not transmit forwarded downlink PDCP SDUs to the UE whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already.

9 If RACH-less HO is not configured, after receiving the RRCConnectionReconfiguration message including the mobilityControlInfo, UE performs synchronisation to target eNB and accesses the target cell via RACH, following a contention-free procedure if a dedicated RACH preamble was indicated in the mobilityControlInfo, or following a contention-based procedure if no dedicated preamble was indicated. UE derives target eNB specific keys and configures the selected security algorithms to be used in the target cell.

If RACH-less HO is configured, UE performs synchronisation to target eNB. UE derives target eNB specific keys and configures the selected security algorithms to be used in the target cell.

10 If RACH-less HO is not configured, the target eNB responds with UL allocation and timing advance.

10a If RACH-less HO is configured and the UE did not get the periodic pre-allocated uplink grant in the RRCConnectionReconfiguration message including the mobilityControlInfo, the UE receives uplink grant via the PDCCH of the target cell. The UE uses the first available uplink grant after synchronization to the target cell.

11 When the RACH-less HO is not configured and the UE has successfully accessed the target cell, the UE sends the RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with an uplink Buffer Status Report, and/or UL data, whenever possible, to the target eNB, which indicates that the handover procedure is completed for the UE. The target eNB verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to the UE.

When the RACH-less HO is configured, after the UE has received uplink grant, the UE sends the RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with an uplink Buffer Status Report, and/or UL data, whenever possible, to the target eNB. The target eNB verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to the UE. The handover procedure is completed for the UE when the UE receives the UE contention resolution identity MAC control element from the target eNB.

11a/b In case of DAPS Handover, the target eNB sends the HANDOVER SUCCESS message to the source eNB to inform that the UE has successfully accessed the target cell. In return, the source eNB sends the SN STATUS TRANSFER message for E-RABs configured with DAPS for which the description in step 8 applies, and the normal data forwarding follows as defined in 10.1.2.3.

NOTE 8: For E-RABs configured with DAPS, the source eNB does not stop delivering uplink packets to the S-GW until it sends the SN STATUS TRANSFER message in step 11b. The target eNB does not forward the uplink PDCP SDUs successfully received in-sequence to the S-GW until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the S-GW. The target eNB does not deliver any uplink packet which has an UL COUNT lower than the provided.

NOTE 9: Void.

12 The target eNB sends a PATH SWITCH REQUEST message to MME to inform that the UE has changed cell.

13 The MME sends a MODIFY BEARER REQUEST message to the Serving Gateway.

14 The Serving Gateway switches the downlink data path to the target side. The Serving gateway sends one or more "end marker" packets on the old path to the source eNB and then can release any U-plane/TNL resources towards the source eNB.

15 The Serving Gateway sends a MODIFY BEARER RESPONSE message to MME.

16 The MME confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.

17 By sending the UE CONTEXT RELEASE message, the target eNB informs success of HO to source eNB and triggers the release of resources by the source eNB. The target eNB sends this message after the PATH SWITCH REQUEST ACKNOWLEDGE message is received from the MME.

18 Upon reception of the UE CONTEXT RELEASE message, the source eNB can release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.

When an X2 handover is used involving HeNBs and when the source HeNB is connected to a HeNB GW, a UE CONTEXT RELEASE REQUEST message including an explicit GW Context Release Indication is sent by the source HeNB, in order to indicate that the HeNB GW may release of all the resources related to the UE context.

For DAPS handover, upon receiving DAPS handover command message, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling towards the source cell and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available then the UE reverts back to the source cell configuration and activates source cell SRBs for control plane signalling. When DAPS handover is configured, PDCP duplication is not allowed.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the daps-SourceRelease:

2> reset source MCG MAC and release the source MCG MAC configuration;

2> for each DAPS bearer:

3> re-establish the RLC entity or entities for the source PCell;

3> release the RLC entity or entities and the associated DTCH logical channel for the source PCell;

3> reconfigure the PDCP entity to release DAPS, as specified in TS 36.323 [8];

2> for each SRB:

3> release the PDCP entity for the source PCell;

3> release the RLC entity and the associated DCCH logical channel for the source PCell;

2> release the physical channel configuration for the source PCell;

[TS 36.331, clause 5.3.5.4]

If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if daps-HO is configured for any DRB:

2> establish a MAC entity for the target PCell, with the same configuration as the MAC entity for the source PCell;

2> for each DRB configured with daps-HO:

3> establish the RLC entity or entities and the associated DTCH logical channel for the target PCell, with the same configurations as for the source PCell;

3> reconfigure the PDCP entity to configure DAPS as specified in TS36.323 [8].

2> for each DRB not configured with daps-HO:

3> re-establish PDCP;

3> re-establish the RLC entity and associate it, and the associated DTCH logical channel, to the target PCell;

2> for each SRB:

3> establish a PDCP entity for the target PCell, with the same configuration as the PDCP entity for the source PCell;

3> establish an RLC entity and an associated DCCH logical channel for the target PCell, with the same configuration as for the source PCell;

2> suspend the SRBs for the source PCell;

NOTE 1c: In order to understand if a daps-HO is configured, the UE needs to check the presence of the field daps-HO within the received RadioResourceConfigDedicated IE.

8.2.4.30.1.3 Test description

8.2.4.30.1.3.1 Pre-test conditions

System Simulator:

– Cell 1 is the serving cell, Cell 2 is the intra-ferquency neighbour cell of Cell 1.

UE:

– None.

Preamble:

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

8.2.4.30.1.3.2 Test procedure sequence

Table 8.2.4.30.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS ignores scheduling requests and does not allocate any uplink grant in Cell 1.

2

The SS sends one IP Packet to the UE on the DRB#1.

<–

3

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 2. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step4 to 6, parallel behaviour defined in Table 8.2.4.30.1.3.2-2 is executed repeatedly.

4

The SS allocates uplink grant in Cell 1, allowing the UE to return the IP packet received at step 2 and continues to respond to scheduling requests from UE.

<–

(UL Grant)

5

Check: Does the UE loop back the IP packet received at step 2 in the Cell 1?

1

P

6

The SS sends one IP Packet to the UE via DRB#1 in the Cell 1 and stops sending RLC acknowledgements for the waiting time period (Note 1)

7

The SS transmit Random Access Response to respond to the latest preamble on Cell 2.

<-

Random Access Response

8

The SS configures UL grant for the UE in Cell 2 and continues to respond to scheduling requests from UE.

🡨

(UL Grant)

EXCEPTION: Steps 9 and 10 can occur in any order.

9

Check: Does UE transmit an RRCConnectionReconfigurationComplete message in Cell 2?

🡪

RRCConnectionReconfigurationComplete

1,2

P

10

Check: Does the UE loop back the IP packet received at step 6 in the Cell 2?

2

P

11

The SS transmits an RRCConnectionReconfiguration message not including mobilityControlInfo and including daps-SourceRelease in Cell 2.

🡨

RRCConnectionReconfiguration

12

Check: Does UE transmit an RRCConnectionReconfigurationComplete message in Cell 2?

🡪

RRCConnectionReconfigurationComplete

3

P

13

the SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

14

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1?

3

F

15

the SS transmits one IP Packet to verify data path on DRB#1 on Cell 2.

16

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 2?

1

P

Note 1: The waiting timer starts after SS sending RRCConnectionReconfiguration message in step 3. The waiting time period should not exceed the value of T304. The default value of T304 is set to 1000ms currently as specified in table 4.6.5-1 in [18].

Table 8.2.4.30.1.3.2-2: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmit preamble to Cell2.

->

(PRACH Preamble)

8.2.4.30.1.3.3 Specific message contents

Table 8.2.4.30.1.3.3-1: RRCConnectionReconfiguration (step 3, Table 8.2.4.30.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.30.1.3.3-2: MobilityControlInfo (Table 8.2.4.30.1.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 2

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 2

Band 24 High range

}

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

rach-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

}

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.1.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.30.1.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 8.2.4.30.1.3.3-4: RACH-ConfigCommon-DEFAULT (Table 8.2.4.30.1.3.3-3)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n200

}

}

Table 8.2.4.30.1.3.3-5: RadioResourceConfigDedicated (Table 8.2.4.30.1.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.30.1.3.3-6: DRB-ToAddMod-DEFAULT (Table 8.2.4.30.1.3.3-5)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

Table 8.2.4.30.1.3.3-7: RRCConnectionReconfiguration (step 11, Table 8.2.4.30.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

Not present

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

daps-SourceRelease-r16

TRUE

}

}

}

}

}

}

}

}

}

}

}

}

8.2.4.30.2 DAPS handover / Success / Radio Link Failure in source / Intra-Frequency

8.2.4.30.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { Timer T310 configured by using the value for target’s timer T310 expires in source }

then { UE stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration and continue the handover procedure to target }

}

(2)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { random access problem indication from source MCG MAC }

then { UE stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration and continue the handover procedure to target }

}

(3)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { indication from source MCG RLC, which is allowed to be sent on source PCell, that the maximum number of retransmissions has been reached for an DRB }

then { UE stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration and continue the handover procedure to target }

}

8.2.4.30.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.6 and TS 36.331 clause 5.3.11.3. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.6]

Two phases govern the behaviour associated to radio link failure as shown on Figure 10.1.6-1:

– First phase:

– started upon radio problem detection;

– leads to radio link failure detection;

– no UE-based mobility;

– based on timer or other (e.g. counting) criteria (T1).

– Second Phase:

– started upon radio link failure detection or handover failure;

– leads to RRC_IDLE;

– UE-based mobility;

– Timer based (T2).

Figure 10.1.6-1: Radio Link Failure

Table 10.1.6-1 below describes how mobility is handled with respect to radio link failure:

Table 10.1.6-1: Mobility and Radio Link Failure

Cases

First Phase

Second Phase

T2 expired

UE returns to the same cell

Continue as if no radio problems occurred

Activity is resumed by means of explicit signalling between UE and eNB

Go via RRC_IDLE

UE selects a different cell from the same eNB

N/A

Activity is resumed by means of explicit signalling between UE and eNB

Go via RRC_IDLE

UE selects a cell of a prepared eNB (NOTE)

N/A

Activity is resumed by means of explicit signalling between UE and eNB

Go via RRC_IDLE

UE selects a cell of a different eNB that is not prepared (NOTE)

N/A

Go via RRC_IDLE

Go via RRC_IDLE

NOTE: a prepared eNB is an eNB which has admitted the UE during an earlier executed HO preparation phase, or obtains the UE context during the Second Phase.

For a NB-IoT UE that only uses Control Plane CIoT EPS/5GS optimisations, as defined in TS 24.301 [20] and does not support RRC Connection re-establishment for the control plane as defined in TS 36.331 [16], at the end of the first phase, the UE enters RRC_IDLE (there is no second phase).In the Second Phase, in order to resume activity and avoid going via RRC_IDLE when the UE returns to the same cell or when the UE selects a different cell from the same eNB, or when the UE selects a cell from a different eNB, the following procedure applies:

– The UE stays in RRC_CONNECTED;

– The UE accesses the cell through the random access procedure;

– Except for a NB-IoT UE using only Control Plane CIoT EPS/5GS optimisations, the UE identifier used in the random access procedure for contention resolution (i.e. C‑RNTI of the UE in the cell where the RLF occurred + physical layer identity of that cell + short MAC-I based on the keys of that cell) is used by the selected eNB to authenticate the UE and check whether it has a context stored for that UE:

– If the eNB finds a context that matches the identity of the UE, or obtains this context from the previously serving eNB, it indicates to the UE that its connection can be resumed;

– If the context is not found, RRC connection is released and UE initiates procedure to establish new RRC connection. In this case UE is required to go via RRC_IDLE.

– For a NB-IoT UE using only Control Plane CIoT EPS/5GS optimisations, the UE identifier used in the random access procedure for contention resolution (i.e. S-TMSI (for EPS) or truncated 5G-S-TMSI (for 5GS) of the UE at the time where the RLF occurred + UL NAS MAC + UL NAS COUNT) is used by the selected (ng-)eNB to request the MME/AMF to authenticate the UE’s re-establishment request and provide the UE context:

– If the authentication of the UE is successful and a context is provided, it indicates to the UE that its connection can be resumed;

– If no context is provided, the RRC connection is released and UE initiates procedure to establish new RRC connection. In this case UE is required to go via RRC_IDLE.

The radio link failure procedure applies also for RNs, with the exception that the RN is limited to select a cell from its DeNB cell list. Upon detecting radio link failure, the RN discards any current RN subframe configuration (for communication with its DeNB), enabling the RN to perform normal contention-based RACH as part of the re-establishment. Upon successful re-establishment, an RN subframe configuration can be configured again using the RN reconfiguration procedure.

For DC, PCell supports above phases. In addition, the first phase of the radio link failure procedure is supported for PSCell. However, upon detecting RLF on the PSCell, the re-establishment procedure is not triggered at the end of the first phase. Instead, UE shall inform the radio link failure of PSCell to the MeNB.

NOTE: If the recovery attempt in the second phase fails, the details of the RN behaviour in RRC_IDLE to recover an RRC connection are up to the RN implementation.

In case of DAPS handover, the UE continues the detection of radio link failure at the source cell until the successful completion of the random access procedure to the target cell. If RLF is declared in the source cell, the UE:

– stays in RRC_CONNECTED;

– stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration;

– if handover failure is declared at the target cell after source cell RLF was declared,

– selects a suitable cell and initiates RRC re-establishment;

– enters RRC_IDLE if a suitable cell was not found within a certain time after handover failure was declared.

In case of CHO, after RLF is declared in the source cell, the UE:

– stays in RRC_CONNECTED;

– selects a suitable cell and if the selected cell is a CHO candidate and if network configured the UE to try CHO at the selected CHO candidate cell after RLF, then the UE attempts CHO execution, otherwise re-establishment is performed;

– enters RRC_IDLE if a suitable cell was not found within a certain time after RLF was declared.

[TS 36.331, clause 5.3.11.3]

The UE shall:

1> in case any DAPS bearer is configured, only the target PCell is considered in the following;

1> upon T310 expiry; or

1> upon T312 expiry; or

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

1> upon indication from MCG RLC, which is allowed to be send on PCell, that the maximum number of retransmissions has been reached for an SRB or DRB:

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

2> discard any segments of segmented RRC messages received;

2> if the UE is configured with (NG)EN-DC; and

2> if T316 is configured; and

2> if SCG transmission is not suspended; and

2> if NR PSCell change is not ongoing (i.e. T304 for the NR PSCell is not running as specified in TS 38.331 [82], clause 5.3.5.5.2, in (NG)EN-DC):

3> initiate the MCG failure information procedure as specified in 5.6.26 to report MCG radio link failure;

2> else:

3> store the following radio link failure information in the VarRLF-Report (VarRLF-Report-NB in NB-IoT) by setting its fields as follows:

4> clear the information included in VarRLF-Report (VarRLF-Report-NB in NB-IoT), if any;

4> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

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

4> except for NB-IoT, 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;

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

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

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

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

5> if the UE was configured to perform measurement reporting, not related to NR sidelink communication, for one or more neighbouring NR frequencies, include the measResultListNR;

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

NOTE 1: 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.

4> except for NB-IoT, if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

4> except for NB-IoT, if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

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

5> include the locationCoordinates;

5> include the horizontalVelocity, if available;

4> set the failedPCellId to the global cell identity, if available, and otherwise , except for NB-IoT, to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

4> except for NB-IoT, set the tac-FailedPCell to the tracking area code, if available, of the PCell where radio link failure is detected;

4> except for NB-IoT, if an RRCConnectionReconfiguration message including the mobilityControlInfo was received before the connection failure:

5> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned an intra E-UTRA handover:

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

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

5> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a handover to E-UTRA from UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO:

6> include the previousUTRA-CellId and set it to the physical cell identity, the carrier frequency and the global cell identity, if available, of the UTRA Cell in which the last RRCConnectionReconfiguration message including mobilityControlInfo was received;

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

5> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a handover to E-UTRA from NR and if the UE supports Radio Link Failure Report for Inter-RAT MRO:

6> include the previousNR-PCellId and set it to the global cell identity of the PCell where the last RRCConnectionReconfiguration message including mobilityControlInfo was received embedded in NR RRC message MobilityFromNRCommand message as specified in TS 38.331 [82] clause 5.4.3.3;

6> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration message including the mobilityControlInfo embedded in NR RRC message MobilityFromNRCommand message as specified in TS 38.331 [82] clause 5.4.3.3.

4> except for NB-IoT, if the UE supports QCI1 indication in Radio Link Failure Report and has a DRB for which QCI is 1:

5> include the drb-EstablishedWithQCI-1;

4> except for NB-IoT, set the connectionFailureType to rlf;

4> except for NB-IoT, set the c-RNTI to the C-RNTI used in the PCell;

4> except for NB-IoT, set the rlf-Cause to the trigger for detecting radio link failure;

3> if AS security has not been activated:

4> if the UE is a NB-IoT UE:

5> if the UE is connected to EPC and the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation; or

5> if the UE is connected to 5GC, the UE supports RRC connection re-establishment for the Control Plane CIoT 5GS optimisation and the UE is configured with a truncated 5G-S-TMSI:

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

5> else:

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

4> else:

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

3> else:

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

In case of DC or NE-DC, the UE shall:

1> upon T313 expiry; or

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

1> upon indication from SCG RLC, which is allowed to be sent on PSCell, that the maximum number of retransmissions has been reached for an SCG, for a split DRB or for a split SRB:

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

2> if the UE is configured with DC; or

2> if the UE is configured with NE-DC and MCG transmission is not suspended:

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

2> else:

3> initiate the connection re-establishment procedure as specified in TS 38.331 [82], clause 5.3.7.

In case of CA PDCP duplication, the UE shall:

1> upon indication from an RLC entity, which is restricted to be sent on SCell only, that the maximum number of retransmissions has been reached:

2> initiate the failure information procedure as specified in 5.6.21 to report RLC failure of type duplication;

If any DAPS bearer is configured and T304 is running, the UE shall:

1> upon T310 expiry; or

1> upon T312 expiry; or

1> upon random access problem indication from source MCG MAC; or

1> upon indication from source MCG RLC, which is allowed to be sent on source PCell, that the maximum number of retransmissions has been reached for an DRB:

2> consider radio link failure to be detected for the source MCG;

2> suspend the transmission of all DRBs in the source MCG;

2> reset MAC for the source MCG;

2> release the source connection;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report (VarRLF-Report-NB in NB-IoT), 48 hours after the radio link failure is detected, upon power off or upon detach, and for NB-IoT, upon entering another RAT.

8.2.4.30.2.3 Test description

8.2.4.30.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 2.

UE:

– None.

Preamble:

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

8.2.4.30.2.3.2 Test procedure sequence

Table 8.2.4.30.2.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", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

T2

Cell-specific RS EPRE

dBm/15kHz

“Off”

-79

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-85

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.30.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.30.2.3.2-1.

2

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 2. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step 4 to 6, parallel behaviour defined in Table 8.2.4.30.2.3.2-3 is executed repeatedly on Cell 2

3

The SS changes Cell 1 and Cell 2 parameters according to the row "T2" in table 8.2.4.30.2.3.2-1.

4

Wait 1s to make t310 expired.

5

The SS changes Cell 1 and Cell 2 parameters according to the row "T3" in table 8.2.4.30.2.3.2-1.

6

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

–>

RRCConnectionReestablishmentRequest

1

F

7

The SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

8

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1 in 5 seconds?

1

F

9

The SS transmit Random Access Response to respond to the latest preamble on Cell 2.

<-

Random Access Response

10

Check: Does UE transmit an RRCConnectionReconfigurationComplete message on Cell 2?

–>

RRCConnectionReconfigurationComplete

1

P

11

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 1. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step12 to 15, parallel behaviour defined in Table 8.2.4.30.2.3.2-3 is executed repeatedly on Cell 1

12

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

<–

(PDCCH Order)

EXCEPTION: Step 13 is executed 3 times and the SS does not transmit Random Access Response to the UE.

13

The UE transmits a preamble on PRACH to the Cell 2 using the same preamble index as given in step 12

–>

(PRACH Preamble)

14

The SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

15

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1 in 5 seconds?

2

F

16

The SS transmit Random Access Response to respond to the latest preamble on Cell 1.

<-

Random Access Response

17

Check: Does UE transmit an RRCConnectionReconfigurationComplete message on Cell 1?

–>

RRCConnectionReconfigurationComplete

2

P

18

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 2. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step 19 to 25, parallel behaviour defined in Table 8.2.4.30.2.3.2-3 is executed repeatedly on Cell 2

19

The SS stops sending RLC acknowledgments on Cell 1

20

The SS transmits one AMD PDU containing SDU (100 bytes) in its data field.

<–

(AMD PDU)

21

The UE transmits an AMD PDU containing SDU in its data field.

–>

(AMD PDU)

22

EXCEPTION: Step 23 shall be repeated maxRetxThreshold times

23

The UE transmits an AMD PDU containing SDU in its data field.

–>

(AMD PDU)

24

The SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

25

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1 in 5 seconds?

3

F

26

The SS transmit Random Access Response to respond to the latest preamble on Cell 2.

<-

Random Access Response

27

Check: Does UE transmit an RRCConnectionReconfigurationComplete message on Cell 2?

–>

RRCConnectionReconfigurationComplete

3

P

Table 8.2.4.30.2.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmit preamble.

->

(PRACH Preamble)

8.2.4.30.2.3.3 Specific message contents

Table 8.2.4.30.2.3.3-1: SystemInformationBlockType2 (preamble and all steps, Table 8.2.4.30.2.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

ms1000

}

}

Table 8.2.4.30.2.3.3-2: RRCConnectionReconfiguration (step 2, 11 and 18, Table 8.2.4.30.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.30.2.3.3-3: MobilityControlInfo (Table 8.2.4.30.2.3.3-2)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

Step 2 and 18

PhysicalCellIdentity of Cell 1

Step 11

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 2

Step 2 and 18

Same downlink EARFCN as used for Cell 1

Step 11

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 2

Band 24 High range, Step 2 and 18

Same uplink EARFCN as used for Cell 1

Band 24 High range, Step 11

}

t304

ms2000

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

rach-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

}

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.2.3.3-4: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.30.2.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 8.2.4.30.2.3.3-5: RACH-ConfigCommon-DEFAULT (Table 8.2.4.30.2.3.3-3)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n200

}

}

Table 8.2.4.30.2.3.3-6: RadioResourceConfigDedicated (Table 8.2.4.30.2.3.3-2)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.30.2.3.3-7: DRB-ToAddMod-DEFAULT (Table 8.2.4.30.2.3.3-6)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

8.2.4.30.3 DAPS handover / Failure / source link available / Radio Link Failure in source / Intra-Frequency

8.2.4.30.3.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { T304 expires (handover failure) and radio link failure has not been detected for the source MCG }

then { The UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment }

}

(2)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB and T304 expires (handover failure) and radio link failure has been detected for the source MCG}

ensure that {

when { UE perform RRC re-establishment and selecting a suitable E-UTRA cell while T311 is running }

then { UE stays in RRC_CONNECTED and selects a suitable cell and then initiates RRC re-establishment }

}

(3)

with { UE in RRC_CONNECTED state and supporting Intra-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB and T304 expires (handover failure) and radio link failure has been detected for the source MCG }

ensure that {

when { UE can not find a suitable cell before T311 expires }

then { UE enters RRC_IDLE }

}

8.2.4.30.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.2.1.0 and 10.1.2.1.1 and TS 36.331 clause 5.3.5.6, 5.3.7.6 and 5.6.21.3. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.2.1.0]

The intra E-UTRAN HO of a UE in RRC_CONNECTED state is a UE-assisted network-controlled HO, with HO preparation signalling in E-UTRAN:

– If DAPS handover is configured, the UE continues the downlink user data reception from the source eNB until releasing the source cell and continues the uplink user data transmission to the source eNB until successful random access procedure to the target eNB. Upon reception of the handover command, the UE:

– Creates a MAC entity for target cell;

– Establishes the RLC entity and an associated DTCH logical channel for target cell for each DRB configured with DAPS;

– For the DRB(s) configured with DAPS, reconfigures the PDCP entity to configure DAPS with separate security and ROHC functions for source and target and associates them with the RLC entities configured for source and target respectively;

– Retains rest of the source link configurations until release of the source.

– UE maintains only PCell connection with both source and target cells and any other configured serving cells are released by the network before the handover command is sent to the UE.

NOTE: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.

– If the access towards the target cell (using RACH or RACH-less procedure) is not successful within a certain time, the UE initiates radio link failure recovery using a suitable cell except in DAPS handover or CHO scenarios:

– When DAPS handover fails, the UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment if the source link is still available; Otherwise, RRC re-establishment is performed;

– When initial CHO execution attempt fails or Handover fails, if network configured the UE to try CHO after HO/CHO failure and the UE performs cell selection to a CHO candidate cell, the UE attempts CHO execution to that cell; Otherwise, RRC re-establishment is performed.

[TS 36.300, clause 10.1.2.1.1]

The preparation and execution phase of the HO procedure is performed without EPC involvement, i.e. preparation messages are directly exchanged between the eNBs. The release of the resources at the source side during the HO completion phase is triggered by the eNB. In case an RN is involved, its DeNB relays the appropriate S1 messages between the RN and the MME (S1-based handover) and X2 messages between the RN and target eNB (X2-based handover); the DeNB is explicitly aware of a UE attached to the RN due to the S1 proxy and X2 proxy functionality (see clause 4.7.6.6). The figure below depicts the basic handover scenario where neither MME nor Serving Gateway changes:

Figure 10.1.2.1.1-1: Intra-MME/Serving Gateway HO

Below is a more detailed description of the intra-MME/Serving Gateway HO procedure:

0 The UE context within the source eNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update.

1 The source eNB configures the UE measurement procedures according to the roaming and access restriction information and e.g. the available multiple frequency band information. Measurements provided by the source eNB may assist the function controlling the UE’s connection mobility.

2 A MEASUREMENT REPORT is triggered and sent to the eNB.

3 The source eNB makes decision based on MEASUREMENT REPORT and RRM information to hand off the UE.

4 The source eNB issues a HANDOVER REQUEST message to the target eNB passing necessary information to prepare the HO at the target side (UE X2 signalling context reference at source eNB, UE S1 EPC signalling context reference, target cell ID, KeNB*, RRC context including the C-RNTI of the UE in the source eNB, AS-configuration, E-RAB context and physical layer ID of the source cell + short MAC-I for possible RLF recovery). The source eNB may also request a DAPS Handover for one or more E-RABs. UE X2 / UE S1 signalling references enable the target eNB to address the source eNB and the EPC. The E-RAB context includes necessary RNL and TNL addressing information, and QoS profiles of the E-RABs.

5 Admission Control may be performed by the target eNB dependent on the received E-RAB QoS information to increase the likelihood of a successful HO, if the resources can be granted by target eNB. The target eNB configures the required resources according to the received E-RAB QoS information and reserves a C-RNTI and optionally a RACH preamble. The AS-configuration to be used in the target cell can either be specified independently (i.e. an "establishment") or as a delta compared to the AS-configuration used in the source cell (i.e. a "reconfiguration").

6 The target eNB prepares HO with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB. The HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE as an RRC message to perform the handover. The container includes a new C-RNTI, target eNB security algorithm identifiers for the selected security algorithms, may include a dedicated RACH preamble, and possibly some other parameters i.e. access parameters, SIBs, etc. If RACH-less HO is configured, the container includes timing adjustment indication and optionally a preallocated uplink grant. The HANDOVER REQUEST ACKNOWLEDGE message may also include RNL/TNL information for the forwarding tunnels, if necessary. The target eNB also indicates if a DAPS Handover is accepted.

NOTE 1: As soon as the source eNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated.

NOTE 1a: For E-RABs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source eNB, until SN assignment is handed over to the target eNB in step 11b, for which the normal data forwarding follows as defined in 10.1.2.3.

Steps 7 to 16 provide means to avoid data loss during HO and are further detailed in 10.1.2.1.2 and 10.1.2.3.

7 The target eNB generates the RRC message to perform the handover, i.e. RRCConnectionReconfiguration message including the mobilityControlInfo, to be sent by the source eNB towards the UE. The source eNB performs the necessary integrity protection and ciphering of the message.

The UE receives the RRCConnectionReconfiguration message with necessary parameters (i.e. new C-RNTI, target eNB security algorithm identifiers, and optionally dedicated RACH preamble, target eNB SIBs, etc.) and is commanded by the source eNB to perform the HO. If RACH-less HO is configured, the RRCConnectionReconfiguration includes timing adjustment indication and optionally preallocated uplink grant for accessing the target eNB. If preallocated uplink grant is not included, the UE should monitor PDCCH of the target eNB to receive an uplink grant. The UE does not need to delay the handover execution for delivering the HARQ/ARQ responses to source eNB.

If Make-Before-Break HO is configured, the connection to the source cell is maintained after the reception of RRCConnectionReconfiguration message with mobilityControlInfo before the UE executes initial uplink transmission to the target cell.

NOTE 2: If Make-Before-Break HO is configured, the source eNB decides when to stop transmitting to the UE.

NOTE 3: The UE can be configured with Make-Before-Break HO and RACH-less HO simultaneously.

In case of DAPS Handover, the UE does not detach from the source cell upon receiving the RRCConnectionReconfiguration message. The UE releases the source SRB resources, security configuration of the source cell and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node.

NOTE 3a: The DAPS Handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released.

NOTE 4: DC, CHO or RACH-less HO cannot be configured simultaneously with DAPS Handover.

NOTE 5: For E-RABs configured with DAPS, the source eNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target eNB in step 11a.

8a For E-RABs configured with DAPS, the source eNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source eNB forwards to the target eNB. The source eNB does not stop assigning PDCP SNs to downlink packets until it sends the SN STATUS TRANSFER message to the target eNB in step 11b.

8 For E-RABs not configured with DAPS, the source eNB sends the SN STATUS TRANSFER message to the target eNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of E-RABs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL SDU and may include a bit map of the receive status of the out of sequence UL SDUs that the UE needs to retransmit in the target cell, if there are any such SDUs. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target eNB shall assign to new SDUs, not having a PDCP SN yet. The source eNB may omit sending this message if none of the E-RABs of the UE shall be treated with PDCP status preservation.

NOTE 6: In case of DAPS Handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for an E-RAB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 11b instead of step 8.

NOTE 7: For E-RABs configured with DAPS, the source eNB may additionally send the EARLY STATUS TRANSFER message(s) between step 8 and step 11b, to inform discarding of already forwarded PDCP SDUs. The target eNB does not transmit forwarded downlink PDCP SDUs to the UE whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already.

9 If RACH-less HO is not configured, after receiving the RRCConnectionReconfiguration message including the mobilityControlInfo, UE performs synchronisation to target eNB and accesses the target cell via RACH, following a contention-free procedure if a dedicated RACH preamble was indicated in the mobilityControlInfo, or following a contention-based procedure if no dedicated preamble was indicated. UE derives target eNB specific keys and configures the selected security algorithms to be used in the target cell.

If RACH-less HO is configured, UE performs synchronisation to target eNB. UE derives target eNB specific keys and configures the selected security algorithms to be used in the target cell.

10 If RACH-less HO is not configured, the target eNB responds with UL allocation and timing advance.

10a If RACH-less HO is configured and the UE did not get the periodic pre-allocated uplink grant in the RRCConnectionReconfiguration message including the mobilityControlInfo, the UE receives uplink grant via the PDCCH of the target cell. The UE uses the first available uplink grant after synchronization to the target cell.

11 When the RACH-less HO is not configured and the UE has successfully accessed the target cell, the UE sends the RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with an uplink Buffer Status Report, and/or UL data, whenever possible, to the target eNB, which indicates that the handover procedure is completed for the UE. The target eNB verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to the UE.

When the RACH-less HO is configured, after the UE has received uplink grant, the UE sends the RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with an uplink Buffer Status Report, and/or UL data, whenever possible, to the target eNB. The target eNB verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to the UE. The handover procedure is completed for the UE when the UE receives the UE contention resolution identity MAC control element from the target eNB.

11a/b In case of DAPS Handover, the target eNB sends the HANDOVER SUCCESS message to the source eNB to inform that the UE has successfully accessed the target cell. In return, the source eNB sends the SN STATUS TRANSFER message for E-RABs configured with DAPS for which the description in step 8 applies, and the normal data forwarding follows as defined in 10.1.2.3.

NOTE 8: For E-RABs configured with DAPS, the source eNB does not stop delivering uplink packets to the S-GW until it sends the SN STATUS TRANSFER message in step 11b. The target eNB does not forward the uplink PDCP SDUs successfully received in-sequence to the S-GW until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the S-GW. The target eNB does not deliver any uplink packet which has an UL COUNT lower than the provided.

NOTE 9: Void.

12 The target eNB sends a PATH SWITCH REQUEST message to MME to inform that the UE has changed cell.

13 The MME sends a MODIFY BEARER REQUEST message to the Serving Gateway.

14 The Serving Gateway switches the downlink data path to the target side. The Serving gateway sends one or more "end marker" packets on the old path to the source eNB and then can release any U-plane/TNL resources towards the source eNB.

15 The Serving Gateway sends a MODIFY BEARER RESPONSE message to MME.

16 The MME confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.

17 By sending the UE CONTEXT RELEASE message, the target eNB informs success of HO to source eNB and triggers the release of resources by the source eNB. The target eNB sends this message after the PATH SWITCH REQUEST ACKNOWLEDGE message is received from the MME.

18 Upon reception of the UE CONTEXT RELEASE message, the source eNB can release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.

When an X2 handover is used involving HeNBs and when the source HeNB is connected to a HeNB GW, a UE CONTEXT RELEASE REQUEST message including an explicit GW Context Release Indication is sent by the source HeNB, in order to indicate that the HeNB GW may release of all the resources related to the UE context.

For DAPS handover, upon receiving DAPS handover command message, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling towards the source cell and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available then the UE reverts back to the source cell configuration and activates source cell SRBs for control plane signalling. When DAPS handover is configured, PDCP duplication is not allowed.

[TS 36.331, clause 5.3.5.6]

If T304 expires (handover failure), the UE shall:

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

1> if no DAPS bearer is configured; or

1> if any DAPS bearer is configured and radio link failure has been detected for the source MCG in accordance with 5.3.11.3:

2> if attemptCondReconf is not configured:

3> revert back to the configuration used in the source PCell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> else:

3> revert back to the configuration used in the source PCell;

NOTE 1a: In the context above, "the configuration" includes state variables and parameters of each radio bearer. PDCP entities associtated with RLC UM and SRB bearers are reset after the successful RRC connection re-establishment procedure according to clause 5.2 in TS 36.323 [8]. In the above, "the configuration" includes the RB configuration using NR PDCP, if configured (i.e. by nr-RadioBearerConfig1 and nr-RadioBearerConfig2).

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

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

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the source PCell based on measurements collected up to the moment the UE detected handover failure and in accordance with the following;

4> if the UE includes rsrqResult, include the lastServCellRSRQ-Type;

3> set the measResultNeighCells to include the best measured cells, other than the source PCell, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected handover 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 includes rsrqResult, include the rsrq-Type;

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;

4> if the UE was configured to perform measurement reporting, not related to NR sidelink communication, for one or more neighbouring NR frequencies, include the measResultListNR;

4> 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.

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

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> if last RRCConnectionReconfiguration message including mobilityControlInfo concerned a failed intra-RAT handover (E-UTRA to E-UTRA):

4> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

3> else if last MobilityFromEUTRACommand concerned a failed inter-RAT handover from E-UTRA to NR and if the UE supports Radio Link Failure Report for Inter-RAT MRO (EUTRA to NR):

4> set the failedNR-PCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

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

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

3> set the connectionFailureType to ‘hof’;

3> set the c-RNTI to the C-RNTI used in the source PCell;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

1> else (any DAPS bearer is configured and radio link failure has not been detected for the source MCG):

2> release the MAC entity for the target PCell;

2> for each DAPS bearer:

3> re-establish the RLC entity for the target PCell;

3> release the RLC entity or entities and the associated DTCH logical channel for the target PCell;

3> reconfigure the PDCP entity to release DAPS as specified in TS 36.323 [8];

2> for each non-DAPS bearer:

3> revert back to the configuration used for the DRB in the source PCell, including PDCP and RLC states and the security configuration;

2> for each SRB:

3> discard any PDCP SDUs along with the PDCP data PDUs for the source PCell;

3> re-establish the RLC entity for the source PCell;

3> release the PDCP entity for the target PCell;

3> release the RLC entity and the associated DCCH logical channel for the target PCell;

2> release the physical channel configuration for the target PCell;

2> resume the SRBs for the source PCell;

2> initiate the failure information procedure as specified in 5.6.21 to report a DAPS HO failure.

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

NOTE 3: E-UTRAN may retrieve the handover failure information using the UE information procedure with rlf-ReportReq set to true, as specified in 5.6.5.3.

[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.6.21.3]

When initiating the procedure according to 5.6.21.2, the UE shall:

1> set the contents of the FailureInformation message as follows:

2> if the procedure is initiated to report RLC failure:

3> set logicalChannelIdentity to the logical channel identity of the RLC entity;

3> set cellGroupIndication to the cell group where the RLC entity is located;

3> set failureType to the type of failure that has been detected;

2> if the procedure is initiated to report a DAPS HO failure:

3> set failureType to dapsHO-failure;

1> submit the FailureInformation message to lower layers for transmission.8.2.4.30.3.3 Test description

8.2.4.30.3.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.2.4.30.3.3.2 Test procedure sequence

Table 8.2.4.30.3.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", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

T2

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-79

T4

Cell-specific RS EPRE

dBm/15kHz

“Off”

-85

T5

Cell-specific RS EPRE

dBm/15kHz

-79

-85

T6

Cell-specific RS EPRE

dBm/15kHz

“Off”

“Off”

T7

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.30.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 and Cell 2 parameters according to the row "T1" in table 8.2.4.30.3.3.2-1.

2

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events

described in step 3 the steps specified in Table

8.2.4.30.3.3.2-3 should take place on Cell 2.

3

The SS changes Cell 1 and Cell 2 parameters according to the row "T2" in table 8.2.4.30.3.3.2-1.

4

Check: Does the UE transmit an FailureInformation message on Cell 1

–>

FailureInformation

1

P

5

The SS changes Cell 1 and Cell 2 parameters according to the row "T3" in table 8.2.4.30.3.3.2-1.

6

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 2.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events

described in step 7 the steps specified in Table

8.2.4.30.3.3.2-3 should take place on Cell 2.

7

The SS changes Cell 1 and Cell 2 parameters according to the row "T4" in table 8.2.4.30.3.3.2-1.

8

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

–>

RRCConnectionReestablishmentRequest

2

P

9

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 2.

<–

RRCConnectionReestablishment

10

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the currently active KeNB on Cell 2?

–>

RRCConnectionReestablishmentComplete

11

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

<–

RRCConnectionReconfiguration

12

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2.

–>

RRCConnectionReconfigurationtComplete

13

The SS changes Cell 1 and Cell 2 parameters according to the row "T5" in table 8.2.4.30.3.3.2-1.

14

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform intra frequency handover to Cell 1.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events

described in step 15 the steps specified in Table

8.2.4.30.3.3.2-3 should take place on Cell 2.

15

The SS changes Cell 1 and Cell 2 parameters according to the row "T6" in table 8.2.4.30.3.3.2-1.

16

Wait for 12s to make T311 expired.

17

The SS changes Cell 1 and Cell 2 parameters according to the row "T7" in table 8.2.4.30.3.3.2-1.

18

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

3

P

Table 8.2.4.30.3.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the handover using MAC Random Access Preamble.

2

The SS does not respond.

8.2.4.30.3.3.3 Specific message contents

Table 8.2.4.30.3.3.3-1: RRCConnectionReconfiguration (steps 2, 6 and 14, Table 8.2.4.30.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.30.3.3.3-2: MobilityControlInfo (Table 8.2.4.30.3.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

Step 2 and 6

PhysicalCellIdentity of Cell 1

Step 14

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 2

Step 2 and 6

Same downlink EARFCN as used for Cell 1

Step 14

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 2

Band 24 High range, Step 2 and 6

Same uplink EARFCN as used for Cell 1

Band 24 High range, Step 14

}

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

rach-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

}

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.3.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.30.3.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 8.2.4.30.3.3.3-4: RACH-ConfigCommon-DEFAULT (Table 8.2.4.30.3.3.3-3)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n200

}

}

Table 8.2.4.30.3.3.3-5: RadioResourceConfigDedicated (Table 8.2.4.30.3.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.30.3.3.3-6: DRB-ToAddMod-DEFAULT (Table 8.2.4.30.3.3.3-5)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

Table 8.2.4.30.3.3.3-7: FailureInformation (Step 4, Table 8.2.4.30.3.3.2-2)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

FailureInformation-r16 ::= SEQUENCE {

criticalExtensions CHOICE {

failureInformation-r16 SEQUENCE {

failedLogicalChannelIdentity-r16 SEQUENCE {}

Not present

failureType-r16

dapsHO-failure

NonCriticalExtension SEQUENCE {}

Not present

}

criticalExtensionsFuture SEQUENCE {}

Not present

}

}

8.2.4.30.4 RRC connection reconfiguration / Handover / DAPS Handover / Success / Inter-Frequency

8.2.4.30.4.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover }

ensure that {

when { UE receives an RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

then { UE performs DAPS handover to the target cell. For the DRB configured daps-HO, the UE continues to receive downlink data from both source and target eNBs for the DL and the UE transmits UL data to the source eNB }

}

(2)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { UE has performed random access procedure to the target cell successfully }

then { UE tran

smits an RRCReconfigurationComplete message and the UE switches its UL data transmission to the target eNB }

}

(3)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { UE receives an RRCConnectionReconfiguration message does not include the mobilityControlInfo and includes daps-SourceRelease }

then { UE stops to receive downlink data from source eNB and releases the radio link with source cell }

}

8.2.4.30.4.2 Conformance requirements

Same as 8.2.4.30.1.2.

8.2.4.30.4.3 Test description

8.2.4.30.4.3.1 Pre-test conditions

Same as 8.2.4.30.1.3.1 with following changes:

System Simulator:

– Cell 1 is the serving cell and Cell 3 is the neighbour inter-frequency cell of Cell 1.

8.2.4.30.4.3.2 Test procedure sequence

Same as 8.2.4.30.1.3.2.

8.2.4.30.4.3.3 Specific message contents

Table 8.2.4.30.4.3.3-0: Conditions for specific message contents
in Table 8.2.4.30.4.3.3-2

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.4.3.3-1: RRCConnectionReconfiguration (step 3, Table 8.2.4.30.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.30.4.3.3-2: MobilityControlInfo (Table 8.2.4.30.4.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 3

Band 24 High range

}

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

rach-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

}

Table 8.2.4.30.4.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.30.4.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 8.2.4.30.4.3.3-4: RACH-ConfigCommon-DEFAULT (Table 8.2.4.30.4.3.3-3)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n200

}

}

Table 8.2.4.30.4.3.3-5: RadioResourceConfigDedicated (Table 8.2.4.30.4.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.30.4.3.3-6: DRB-ToAddMod-DEFAULT (Table 8.2.4.30.4.3.3-5)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

Table 8.2.4.30.4.3.3-7: RRCConnectionReconfiguration (step 11, Table 8.2.4.30.1.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

Not present

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

daps-SourceRelease-r16

TRUE

}

}

}

}

}

}

}

}

}

}

}

}

8.2.4.30.5 DAPS handover / Success / Radio Link Failure in source / Inter-Frequency

8.2.4.30.5.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { Timer T310 configured by using the value for target’s timer T310 expires in source }

then { UE stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration and continue the handover procedure to target }

}

(2)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { random access problem indication from source MCG MAC }

then { UE stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration and continue the handover procedure to target }

}

(3)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { indication from source MCG RLC, which is allowed to be sent on source PCell, that the maximum number of retransmissions has been reached for an DRB }

then { UE stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration and continue the handover procedure to target }

}

8.2.4.30.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.6 and TS 36.331 clause 5.3.11.3. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.6]

Two phases govern the behaviour associated to radio link failure as shown on Figure 10.1.6-1:

– First phase:

– started upon radio problem detection;

– leads to radio link failure detection;

– no UE-based mobility;

– based on timer or other (e.g. counting) criteria (T1).

– Second Phase:

– started upon radio link failure detection or handover failure;

– leads to RRC_IDLE;

– UE-based mobility;

– Timer based (T2).

Figure 10.1.6-1: Radio Link Failure

Table 10.1.6-1 below describes how mobility is handled with respect to radio link failure:

Table 10.1.6-1: Mobility and Radio Link Failure

Cases

First Phase

Second Phase

T2 expired

UE returns to the same cell

Continue as if no radio problems occurred

Activity is resumed by means of explicit signalling between UE and eNB

Go via RRC_IDLE

UE selects a different cell from the same eNB

N/A

Activity is resumed by means of explicit signalling between UE and eNB

Go via RRC_IDLE

UE selects a cell of a prepared eNB (NOTE)

N/A

Activity is resumed by means of explicit signalling between UE and eNB

Go via RRC_IDLE

UE selects a cell of a different eNB that is not prepared (NOTE)

N/A

Go via RRC_IDLE

Go via RRC_IDLE

NOTE: a prepared eNB is an eNB which has admitted the UE during an earlier executed HO preparation phase, or obtains the UE context during the Second Phase.

For a NB-IoT UE that only uses Control Plane CIoT EPS/5GS optimisations, as defined in TS 24.301 [20] and does not support RRC Connection re-establishment for the control plane as defined in TS 36.331 [16], at the end of the first phase, the UE enters RRC_IDLE (there is no second phase).In the Second Phase, in order to resume activity and avoid going via RRC_IDLE when the UE returns to the same cell or when the UE selects a different cell from the same eNB, or when the UE selects a cell from a different eNB, the following procedure applies:

– The UE stays in RRC_CONNECTED;

– The UE accesses the cell through the random access procedure;

– Except for a NB-IoT UE using only Control Plane CIoT EPS/5GS optimisations, the UE identifier used in the random access procedure for contention resolution (i.e. C‑RNTI of the UE in the cell where the RLF occurred + physical layer identity of that cell + short MAC-I based on the keys of that cell) is used by the selected eNB to authenticate the UE and check whether it has a context stored for that UE:

– If the eNB finds a context that matches the identity of the UE, or obtains this context from the previously serving eNB, it indicates to the UE that its connection can be resumed;

– If the context is not found, RRC connection is released and UE initiates procedure to establish new RRC connection. In this case UE is required to go via RRC_IDLE.

– For a NB-IoT UE using only Control Plane CIoT EPS/5GS optimisations, the UE identifier used in the random access procedure for contention resolution (i.e. S-TMSI (for EPS) or truncated 5G-S-TMSI (for 5GS) of the UE at the time where the RLF occurred + UL NAS MAC + UL NAS COUNT) is used by the selected (ng-)eNB to request the MME/AMF to authenticate the UE’s re-establishment request and provide the UE context:

– If the authentication of the UE is successful and a context is provided, it indicates to the UE that its connection can be resumed;

– If no context is provided, the RRC connection is released and UE initiates procedure to establish new RRC connection. In this case UE is required to go via RRC_IDLE.

The radio link failure procedure applies also for RNs, with the exception that the RN is limited to select a cell from its DeNB cell list. Upon detecting radio link failure, the RN discards any current RN subframe configuration (for communication with its DeNB), enabling the RN to perform normal contention-based RACH as part of the re-establishment. Upon successful re-establishment, an RN subframe configuration can be configured again using the RN reconfiguration procedure.

For DC, PCell supports above phases. In addition, the first phase of the radio link failure procedure is supported for PSCell. However, upon detecting RLF on the PSCell, the re-establishment procedure is not triggered at the end of the first phase. Instead, UE shall inform the radio link failure of PSCell to the MeNB.

NOTE: If the recovery attempt in the second phase fails, the details of the RN behaviour in RRC_IDLE to recover an RRC connection are up to the RN implementation.

In case of DAPS handover, the UE continues the detection of radio link failure at the source cell until the successful completion of the random access procedure to the target cell. If RLF is declared in the source cell, the UE:

– stays in RRC_CONNECTED;

– stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration;

– if handover failure is declared at the target cell after source cell RLF was declared,

– selects a suitable cell and initiates RRC re-establishment;

– enters RRC_IDLE if a suitable cell was not found within a certain time after handover failure was declared.

In case of CHO, after RLF is declared in the source cell, the UE:

– stays in RRC_CONNECTED;

– selects a suitable cell and if the selected cell is a CHO candidate and if network configured the UE to try CHO at the selected CHO candidate cell after RLF, then the UE attempts CHO execution, otherwise re-establishment is performed;

– enters RRC_IDLE if a suitable cell was not found within a certain time after RLF was declared.

[TS 36.331, clause 5.3.11.3]

The UE shall:

1> in case any DAPS bearer is configured, only the target PCell is considered in the following;

1> upon T310 expiry; or

1> upon T312 expiry; or

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

1> upon indication from MCG RLC, which is allowed to be send on PCell, that the maximum number of retransmissions has been reached for an SRB or DRB:

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

2> discard any segments of segmented RRC messages received;

2> if the UE is configured with (NG)EN-DC; and

2> if T316 is configured; and

2> if SCG transmission is not suspended; and

2> if NR PSCell change is not ongoing (i.e. T304 for the NR PSCell is not running as specified in TS 38.331 [82], clause 5.3.5.5.2, in (NG)EN-DC):

3> initiate the MCG failure information procedure as specified in 5.6.26 to report MCG radio link failure;

2> else:

3> store the following radio link failure information in the VarRLF-Report (VarRLF-Report-NB in NB-IoT) by setting its fields as follows:

4> clear the information included in VarRLF-Report (VarRLF-Report-NB in NB-IoT), if any;

4> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

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

4> except for NB-IoT, 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;

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

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

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

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

5> if the UE was configured to perform measurement reporting, not related to NR sidelink communication, for one or more neighbouring NR frequencies, include the measResultListNR;

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

NOTE 1: 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.

4> except for NB-IoT, if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

4> except for NB-IoT, if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

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

5> include the locationCoordinates;

5> include the horizontalVelocity, if available;

4> set the failedPCellId to the global cell identity, if available, and otherwise , except for NB-IoT, to the physical cell identity and carrier frequency of the PCell where radio link failure is detected;

4> except for NB-IoT, set the tac-FailedPCell to the tracking area code, if available, of the PCell where radio link failure is detected;

4> except for NB-IoT, if an RRCConnectionReconfiguration message including the mobilityControlInfo was received before the connection failure:

5> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned an intra E-UTRA handover:

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

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

5> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a handover to E-UTRA from UTRA and if the UE supports Radio Link Failure Report for Inter-RAT MRO:

6> include the previousUTRA-CellId and set it to the physical cell identity, the carrier frequency and the global cell identity, if available, of the UTRA Cell in which the last RRCConnectionReconfiguration message including mobilityControlInfo was received;

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

5> if the last RRCConnectionReconfiguration message including the mobilityControlInfo concerned a handover to E-UTRA from NR and if the UE supports Radio Link Failure Report for Inter-RAT MRO:

6> include the previousNR-PCellId and set it to the global cell identity of the PCell where the last RRCConnectionReconfiguration message including mobilityControlInfo was received embedded in NR RRC message MobilityFromNRCommand message as specified in TS 38.331 [82] clause 5.4.3.3;

6> set the timeConnFailure to the elapsed time since reception of the last RRCConnectionReconfiguration message including the mobilityControlInfo embedded in NR RRC message MobilityFromNRCommand message as specified in TS 38.331 [82] clause 5.4.3.3.

4> except for NB-IoT, if the UE supports QCI1 indication in Radio Link Failure Report and has a DRB for which QCI is 1:

5> include the drb-EstablishedWithQCI-1;

4> except for NB-IoT, set the connectionFailureType to rlf;

4> except for NB-IoT, set the c-RNTI to the C-RNTI used in the PCell;

4> except for NB-IoT, set the rlf-Cause to the trigger for detecting radio link failure;

3> if AS security has not been activated:

4> if the UE is a NB-IoT UE:

5> if the UE is connected to EPC and the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation; or

5> if the UE is connected to 5GC, the UE supports RRC connection re-establishment for the Control Plane CIoT 5GS optimisation and the UE is configured with a truncated 5G-S-TMSI:

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

5> else:

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

4> else:

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

3> else:

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

In case of DC or NE-DC, the UE shall:

1> upon T313 expiry; or

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

1> upon indication from SCG RLC, which is allowed to be sent on PSCell, that the maximum number of retransmissions has been reached for an SCG, for a split DRB or for a split SRB:

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

2> if the UE is configured with DC; or

2> if the UE is configured with NE-DC and MCG transmission is not suspended:

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

2> else:

3> initiate the connection re-establishment procedure as specified in TS 38.331 [82], clause 5.3.7.

In case of CA PDCP duplication, the UE shall:

1> upon indication from an RLC entity, which is restricted to be sent on SCell only, that the maximum number of retransmissions has been reached:

2> initiate the failure information procedure as specified in 5.6.21 to report RLC failure of type duplication;

If any DAPS bearer is configured and T304 is running, the UE shall:

1> upon T310 expiry; or

1> upon T312 expiry; or

1> upon random access problem indication from source MCG MAC; or

1> upon indication from source MCG RLC, which is allowed to be sent on source PCell, that the maximum number of retransmissions has been reached for an DRB:

2> consider radio link failure to be detected for the source MCG;

2> suspend the transmission of all DRBs in the source MCG;

2> reset MAC for the source MCG;

2> release the source connection;

The UE may discard the radio link failure information, i.e. release the UE variable VarRLF-Report (VarRLF-Report-NB in NB-IoT), 48 hours after the radio link failure is detected, upon power off or upon detach, and for NB-IoT, upon entering another RAT.

8.2.4.30.5.3 Test description

8.2.4.30.5.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 3.

UE:

– None.

Preamble:

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

8.2.4.30.5.3.2 Test procedure sequence

Table 8.2.4.30.5.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", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.2.4.30.5.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

-91

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

T2

Cell-specific RS EPRE

dBm/15kHz

“Off”

-79

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-85

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.30.5.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.30.5.3.2-1.

2

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 3. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step 4 to 6, parallel behaviour defined in Table 8.2.4.30.5.3.2-3 is executed repeatedly on Cell 3

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T2" in table 8.2.4.30.5.3.2-1.

4

Wait 1s to make t310 expired.

5

The SS changes Cell 1 and Cell 3 parameters according to the row "T3" in table 8.2.4.30.5.3.2-1.

6

Check: Does the UE send RRCConnectionReestablishmentRequest message on Cell 3 in 5 seconds?

–>

RRCConnectionReestablishmentRequest

1

F

7

The SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

8

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1 in 5 seconds?

1

F

9

The SS transmit Random Access Response to respond to the latest preamble on Cell 3.

<-

Random Access Response

10

Check: Does UE transmit an RRCConnectionReconfigurationComplete message on Cell 3?

–>

RRCConnectionReconfigurationComplete

1

P

11

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 1. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step 12 to 15, parallel behaviour defined in Table 8.2.4.30.5.3.2-3 is executed repeatedly on Cell 1

12

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

<–

(PDCCH Order)

EXCEPTION: Step 13 is executed 3 times and the SS does not transmit Random Access Response to the UE.

13

The UE transmits a preamble on PRACH to the Cell 3 using the same preamble index as given in step 12

–>

(PRACH Preamble)

14

The SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

15

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1 in 5 seconds?

2

F

16

The SS transmit Random Access Response to respond to the latest preamble on Cell 1.

<-

Random Access Response

17

Check: Does UE transmit an RRCConnectionReconfigurationComplete message on Cell 1?

–>

RRCConnectionReconfigurationComplete

2

P

18

The SS transmits an RRCConnectionReconfiguration message including mobilityControlInfo containing rach-ConfigDedicated to order UE to perform non-contention based DAPS handover to Cell 3. DRB #1 is configured as DAPS bearer.

<–

RRCConnectionReconfiguration

EXCEPTION: During the execution from Step 19 to 25, parallel behaviour defined in Table 8.2.4.30.5.3.2-3 is executed repeatedly on Cell 3

19

The SS stops sending RLC acknowledgments on Cell 1

20

The SS transmits one AMD PDU containing SDU (100 bytes) in its data field.

<–

(AMD PDU)

21

The UE transmits an AMD PDU containing SDU in its data field.

–>

(AMD PDU)

22

EXCEPTION: Step 23 shall be repeated maxRetxThreshold times

23

The UE transmits an AMD PDU containing SDU in its data field.

–>

(AMD PDU)

24

The SS transmits one IP Packet to verify data path on DRB#1 on Cell 1.

25

Check: Does UE send the IP Packet on DRB#1 in the uplink on Cell 1 in 5 seconds?

3

F

26

The SS transmit Random Access Response to respond to the latest preamble on Cell 3.

<-

Random Access Response

27

Check: Does UE transmit an RRCConnectionReconfigurationComplete message on Cell 3?

–>

RRCConnectionReconfigurationComplete

3

P

Table 8.2.4.30.5.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE transmit preamble.

->

(PRACH Preamble)

8.2.4.30.5.3.3 Specific message contents

Table 8.2.4.30.5.3.3-0: Conditions for specific message contents
in Table 8.2.4.30.5.3.3-3

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.5.3.3-1: SystemInformationBlockType2 (preamble and all steps, Table 8.2.4.30.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

ms1000

}

}

Table 8.2.4.30.5.3.3-2: RRCConnectionReconfiguration (step 2, 11 and 18, Table 8.2.4.30.5.3.2-1)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.30.5.3.3-3: MobilityControlInfo (Table 8.2.4.30.5.3.3-2)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

Step 2 and 18

PhysicalCellIdentity of Cell 1

Step 11

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

Step 2 and 18

Same downlink EARFCN as used for Cell 1

Step 11

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 3

Band 24 High range, Step 2 and 18

Same uplink EARFCN as used for Cell 1

Band 24 High range, Step 11

}

t304

ms2000

radioResourceConfigCommon

RadioResourceConfigCommon-DEFAULT

rach-ConfigDedicated

Rach-ConfigDedicated-DEFAULT

}

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.5.3.3-4: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.30.5.3.3-3)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 8.2.4.30.5.3.3-5: RACH-ConfigCommon-DEFAULT (Table 8.2.4.30.5.3.3-4)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n200

}

}

Table 8.2.4.30.5.3.3-6: RadioResourceConfigDedicated (Table 8.2.4.30.5.3.3-2)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.30.5.3.3-7: DRB-ToAddMod-DEFAULT (Table 8.2.4.30.5.3.3-6)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

8.2.4.30.6 DAPS handover / Failure / source link available / Radio Link Failure in source / Inter-Frequency

8.2.4.30.6.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB }

ensure that {

when { T304 expires (handover failure) and radio link failure has not been detected for the source MCG }

then { The UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment }

}

(2)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB and T304 expires (handover failure) and radio link failure has been detected for the source MCG}

ensure that {

when { UE perform RRC re-establishment and selecting a suitable E-UTRA cell while T311 is running }

then { UE stays in RRC_CONNECTED and selects a suitable cell and then initiates RRC re-establishment }

}

(3)

with { UE in RRC_CONNECTED state and supporting Inter-Frequency DAPS handover and having received RRCConnectionReconfiguration message includes the mobilityControlInfo for handover to the target cell and daps-HO is configured for any DRB and T304 expires (handover failure) and radio link failure has been detected for the source MCG }

ensure that {

when { UE can not find a suitable cell before T311 expires }

then { UE enters RRC_IDLE }

}

8.2.4.30.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.2.1.0 and 10.1.2.1.1 and TS 36.331 clause 5.3.5.6, 5.3.7.6 and 5.6.21.3. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.2.1.0]

The intra E-UTRAN HO of a UE in RRC_CONNECTED state is a UE-assisted network-controlled HO, with HO preparation signalling in E-UTRAN:

– If DAPS handover is configured, the UE continues the downlink user data reception from the source eNB until releasing the source cell and continues the uplink user data transmission to the source eNB until successful random access procedure to the target eNB. Upon reception of the handover command, the UE:

– Creates a MAC entity for target cell;

– Establishes the RLC entity and an associated DTCH logical channel for target cell for each DRB configured with DAPS;

– For the DRB(s) configured with DAPS, reconfigures the PDCP entity to configure DAPS with separate security and ROHC functions for source and target and associates them with the RLC entities configured for source and target respectively;

– Retains rest of the source link configurations until release of the source.

– UE maintains only PCell connection with both source and target cells and any other configured serving cells are released by the network before the handover command is sent to the UE.

NOTE: The handling on RLC and PDCP for DRBs not configured with DAPS is the same as in normal handover.

– If the access towards the target cell (using RACH or RACH-less procedure) is not successful within a certain time, the UE initiates radio link failure recovery using a suitable cell except in DAPS handover or CHO scenarios:

– When DAPS handover fails, the UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment if the source link is still available; Otherwise, RRC re-establishment is performed;

– When initial CHO execution attempt fails or Handover fails, if network configured the UE to try CHO after HO/CHO failure and the UE performs cell selection to a CHO candidate cell, the UE attempts CHO execution to that cell; Otherwise, RRC re-establishment is performed.

[TS 36.300, clause 10.1.2.1.1]

The preparation and execution phase of the HO procedure is performed without EPC involvement, i.e. preparation messages are directly exchanged between the eNBs. The release of the resources at the source side during the HO completion phase is triggered by the eNB. In case an RN is involved, its DeNB relays the appropriate S1 messages between the RN and the MME (S1-based handover) and X2 messages between the RN and target eNB (X2-based handover); the DeNB is explicitly aware of a UE attached to the RN due to the S1 proxy and X2 proxy functionality (see clause 4.7.6.6). The figure below depicts the basic handover scenario where neither MME nor Serving Gateway changes:

Figure 10.1.2.1.1-1: Intra-MME/Serving Gateway HO

Below is a more detailed description of the intra-MME/Serving Gateway HO procedure:

0 The UE context within the source eNB contains information regarding roaming and access restrictions which were provided either at connection establishment or at the last TA update.

1 The source eNB configures the UE measurement procedures according to the roaming and access restriction information and e.g. the available multiple frequency band information. Measurements provided by the source eNB may assist the function controlling the UE’s connection mobility.

2 A MEASUREMENT REPORT is triggered and sent to the eNB.

3 The source eNB makes decision based on MEASUREMENT REPORT and RRM information to hand off the UE.

4 The source eNB issues a HANDOVER REQUEST message to the target eNB passing necessary information to prepare the HO at the target side (UE X2 signalling context reference at source eNB, UE S1 EPC signalling context reference, target cell ID, KeNB*, RRC context including the C-RNTI of the UE in the source eNB, AS-configuration, E-RAB context and physical layer ID of the source cell + short MAC-I for possible RLF recovery). The source eNB may also request a DAPS Handover for one or more E-RABs. UE X2 / UE S1 signalling references enable the target eNB to address the source eNB and the EPC. The E-RAB context includes necessary RNL and TNL addressing information, and QoS profiles of the E-RABs.

5 Admission Control may be performed by the target eNB dependent on the received E-RAB QoS information to increase the likelihood of a successful HO, if the resources can be granted by target eNB. The target eNB configures the required resources according to the received E-RAB QoS information and reserves a C-RNTI and optionally a RACH preamble. The AS-configuration to be used in the target cell can either be specified independently (i.e. an "establishment") or as a delta compared to the AS-configuration used in the source cell (i.e. a "reconfiguration").

6 The target eNB prepares HO with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB. The HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE as an RRC message to perform the handover. The container includes a new C-RNTI, target eNB security algorithm identifiers for the selected security algorithms, may include a dedicated RACH preamble, and possibly some other parameters i.e. access parameters, SIBs, etc. If RACH-less HO is configured, the container includes timing adjustment indication and optionally a preallocated uplink grant. The HANDOVER REQUEST ACKNOWLEDGE message may also include RNL/TNL information for the forwarding tunnels, if necessary. The target eNB also indicates if a DAPS Handover is accepted.

NOTE 1: As soon as the source eNB receives the HANDOVER REQUEST ACKNOWLEDGE, or as soon as the transmission of the handover command is initiated in the downlink, data forwarding may be initiated.

NOTE 1a: For E-RABs configured with DAPS, downlink PDCP SDUs are forwarded with SN assigned by the source eNB, until SN assignment is handed over to the target eNB in step 11b, for which the normal data forwarding follows as defined in 10.1.2.3.

Steps 7 to 16 provide means to avoid data loss during HO and are further detailed in 10.1.2.1.2 and 10.1.2.3.

7 The target eNB generates the RRC message to perform the handover, i.e. RRCConnectionReconfiguration message including the mobilityControlInfo, to be sent by the source eNB towards the UE. The source eNB performs the necessary integrity protection and ciphering of the message.

The UE receives the RRCConnectionReconfiguration message with necessary parameters (i.e. new C-RNTI, target eNB security algorithm identifiers, and optionally dedicated RACH preamble, target eNB SIBs, etc.) and is commanded by the source eNB to perform the HO. If RACH-less HO is configured, the RRCConnectionReconfiguration includes timing adjustment indication and optionally preallocated uplink grant for accessing the target eNB. If preallocated uplink grant is not included, the UE should monitor PDCCH of the target eNB to receive an uplink grant. The UE does not need to delay the handover execution for delivering the HARQ/ARQ responses to source eNB.

If Make-Before-Break HO is configured, the connection to the source cell is maintained after the reception of RRCConnectionReconfiguration message with mobilityControlInfo before the UE executes initial uplink transmission to the target cell.

NOTE 2: If Make-Before-Break HO is configured, the source eNB decides when to stop transmitting to the UE.

NOTE 3: The UE can be configured with Make-Before-Break HO and RACH-less HO simultaneously.

In case of DAPS Handover, the UE does not detach from the source cell upon receiving the RRCConnectionReconfiguration message. The UE releases the source SRB resources, security configuration of the source cell and stops DL/UL reception/transmission with the source upon receiving an explicit release from the target node.

NOTE 3a: The DAPS Handover is considered to only be completed after the UE has released the source cell as explicitly requested from the target node. RRC suspend, a subsequent handover or inter-RAT handover cannot be initiated until the source cell has been released.

NOTE 4: DC, CHO or RACH-less HO cannot be configured simultaneously with DAPS Handover.

NOTE 5: For E-RABs configured with DAPS, the source eNB does not stop transmitting downlink packets until it receives the HANDOVER SUCCESS message from the target eNB in step 11a.

8a For E-RABs configured with DAPS, the source eNB sends the EARLY STATUS TRANSFER message. The DL COUNT value conveyed in the EARLY STATUS TRANSFER message indicates PDCP SN and HFN of the first PDCP SDU that the source eNB forwards to the target eNB. The source eNB does not stop assigning PDCP SNs to downlink packets until it sends the SN STATUS TRANSFER message to the target eNB in step 11b.

8 For E-RABs not configured with DAPS, the source eNB sends the SN STATUS TRANSFER message to the target eNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of E-RABs for which PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at least the PDCP SN of the first missing UL SDU and may include a bit map of the receive status of the out of sequence UL SDUs that the UE needs to retransmit in the target cell, if there are any such SDUs. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target eNB shall assign to new SDUs, not having a PDCP SN yet. The source eNB may omit sending this message if none of the E-RABs of the UE shall be treated with PDCP status preservation.

NOTE 6: In case of DAPS Handover, the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status for an E-RAB with RLC-AM and not configured with DAPS may be transferred by the SN STATUS TRANSFER message in step 11b instead of step 8.

NOTE 7: For E-RABs configured with DAPS, the source eNB may additionally send the EARLY STATUS TRANSFER message(s) between step 8 and step 11b, to inform discarding of already forwarded PDCP SDUs. The target eNB does not transmit forwarded downlink PDCP SDUs to the UE whose COUNT is less than the conveyed DL COUNT value and discards them if transmission has not been attempted already.

9 If RACH-less HO is not configured, after receiving the RRCConnectionReconfiguration message including the mobilityControlInfo, UE performs synchronisation to target eNB and accesses the target cell via RACH, following a contention-free procedure if a dedicated RACH preamble was indicated in the mobilityControlInfo, or following a contention-based procedure if no dedicated preamble was indicated. UE derives target eNB specific keys and configures the selected security algorithms to be used in the target cell.

If RACH-less HO is configured, UE performs synchronisation to target eNB. UE derives target eNB specific keys and configures the selected security algorithms to be used in the target cell.

10 If RACH-less HO is not configured, the target eNB responds with UL allocation and timing advance.

10a If RACH-less HO is configured and the UE did not get the periodic pre-allocated uplink grant in the RRCConnectionReconfiguration message including the mobilityControlInfo, the UE receives uplink grant via the PDCCH of the target cell. The UE uses the first available uplink grant after synchronization to the target cell.

11 When the RACH-less HO is not configured and the UE has successfully accessed the target cell, the UE sends the RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with an uplink Buffer Status Report, and/or UL data, whenever possible, to the target eNB, which indicates that the handover procedure is completed for the UE. The target eNB verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to the UE.

When the RACH-less HO is configured, after the UE has received uplink grant, the UE sends the RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with an uplink Buffer Status Report, and/or UL data, whenever possible, to the target eNB. The target eNB verifies the C-RNTI sent in the RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to the UE. The handover procedure is completed for the UE when the UE receives the UE contention resolution identity MAC control element from the target eNB.

11a/b In case of DAPS Handover, the target eNB sends the HANDOVER SUCCESS message to the source eNB to inform that the UE has successfully accessed the target cell. In return, the source eNB sends the SN STATUS TRANSFER message for E-RABs configured with DAPS for which the description in step 8 applies, and the normal data forwarding follows as defined in 10.1.2.3.

NOTE 8: For E-RABs configured with DAPS, the source eNB does not stop delivering uplink packets to the S-GW until it sends the SN STATUS TRANSFER message in step 11b. The target eNB does not forward the uplink PDCP SDUs successfully received in-sequence to the S-GW until it receives the SN STATUS TRANSFER message, in which UL HFN and the first missing SN in the uplink PDCP SN receiver status indicates the start of uplink PDCP SDUs to be delivered to the S-GW. The target eNB does not deliver any uplink packet which has an UL COUNT lower than the provided.

NOTE 9: Void.

12 The target eNB sends a PATH SWITCH REQUEST message to MME to inform that the UE has changed cell.

13 The MME sends a MODIFY BEARER REQUEST message to the Serving Gateway.

14 The Serving Gateway switches the downlink data path to the target side. The Serving gateway sends one or more "end marker" packets on the old path to the source eNB and then can release any U-plane/TNL resources towards the source eNB.

15 The Serving Gateway sends a MODIFY BEARER RESPONSE message to MME.

16 The MME confirms the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.

17 By sending the UE CONTEXT RELEASE message, the target eNB informs success of HO to source eNB and triggers the release of resources by the source eNB. The target eNB sends this message after the PATH SWITCH REQUEST ACKNOWLEDGE message is received from the MME.

18 Upon reception of the UE CONTEXT RELEASE message, the source eNB can release radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.

When an X2 handover is used involving HeNBs and when the source HeNB is connected to a HeNB GW, a UE CONTEXT RELEASE REQUEST message including an explicit GW Context Release Indication is sent by the source HeNB, in order to indicate that the HeNB GW may release of all the resources related to the UE context.

For DAPS handover, upon receiving DAPS handover command message, the UE suspends source cell SRBs, stops sending and receiving any RRC control plane signalling towards the source cell and establishes SRBs for the target cell. The UE releases the source cell SRBs configuration upon receiving source cell release indication from the target cell after successful DAPS handover execution. When DAPS handover to the target cell fails and if the source cell link is available then the UE reverts back to the source cell configuration and activates source cell SRBs for control plane signalling. When DAPS handover is configured, PDCP duplication is not allowed.

[TS 36.331, clause 5.3.5.6]

If T304 expires (handover failure), the UE shall:

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

1> if no DAPS bearer is configured; or

1> if any DAPS bearer is configured and radio link failure has been detected for the source MCG in accordance with 5.3.11.3:

2> if attemptCondReconf is not configured:

3> revert back to the configuration used in the source PCell, excluding the configuration configured by the physicalConfigDedicated, the mac-MainConfig and the sps-Config;

2> else:

3> revert back to the configuration used in the source PCell;

NOTE 1a: In the context above, "the configuration" includes state variables and parameters of each radio bearer. PDCP entities associated with RLC UM and SRB bearers are reset after the successful RRC connection re-establishment procedure according to clause 5.2 in TS 36.323 [8]. In the above, "the configuration" includes the RB configuration using NR PDCP, if configured (i.e. by nr-RadioBearerConfig1 and nr-RadioBearerConfig2).

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

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

3> set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

3> set the measResultLastServCell to include the RSRP and RSRQ, if available, of the source PCell based on measurements collected up to the moment the UE detected handover failure and in accordance with the following;

4> if the UE includes rsrqResult, include the lastServCellRSRQ-Type;

3> set the measResultNeighCells to include the best measured cells, other than the source PCell, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected handover 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 includes rsrqResult, include the rsrq-Type;

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;

4> if the UE was configured to perform measurement reporting, not related to NR sidelink communication, for one or more neighbouring NR frequencies, include the measResultListNR;

4> 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.

3> if available, set the logMeasResultListWLAN to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs;

3> if available, set the logMeasResultListBT to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons;

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> if last RRCConnectionReconfiguration message including mobilityControlInfo concerned a failed intra-RAT handover (E-UTRA to E-UTRA):

4> set the failedPCellId to the global cell identity, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

3> else if last MobilityFromEUTRACommand concerned a failed inter-RAT handover from E-UTRA to NR and if the UE supports Radio Link Failure Report for Inter-RAT MRO (EUTRA to NR):

4> set the failedNR-PCellId to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PCell of the failed handover;

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

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

3> set the connectionFailureType to ‘hof’;

3> set the c-RNTI to the C-RNTI used in the source PCell;

2> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the RRC connection reconfiguration procedure ends;

1> else (any DAPS bearer is configured and radio link failure has not been detected for the source MCG):

2> release the MAC entity for the target PCell;

2> for each DAPS bearer:

3> re-establish the RLC entity for the target PCell;

3> release the RLC entity or entities and the associated DTCH logical channel for the target PCell;

3> reconfigure the PDCP entity to release DAPS as specified in TS 36.323 [8];

2> for each non-DAPS bearer:

3> revert back to the configuration used for the DRB in the source PCell, including PDCP and RLC states and the security configuration;

2> for each SRB:

3> discard any PDCP SDUs along with the PDCP data PDUs for the source PCell;

3> re-establish the RLC entity for the source PCell;

3> release the PDCP entity for the target PCell;

3> release the RLC entity and the associated DCCH logical channel for the target PCell;

2> release the physical channel configuration for the target PCell;

2> resume the SRBs for the source PCell;

2> initiate the failure information procedure as specified in 5.6.21 to report a DAPS HO failure.

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

NOTE 3: E-UTRAN may retrieve the handover failure information using the UE information procedure with rlf-ReportReq set to true, as specified in 5.6.5.3.

[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.6.21.3]

When initiating the procedure according to 5.6.21.2, the UE shall:

1> set the contents of the FailureInformation message as follows:

2> if the procedure is initiated to report RLC failure:

3> set logicalChannelIdentity to the logical channel identity of the RLC entity;

3> set cellGroupIndication to the cell group where the RLC entity is located;

3> set failureType to the type of failure that has been detected;

2> if the procedure is initiated to report a DAPS HO failure:

3> set failureType to dapsHO-failure;

1> submit the FailureInformation message to lower layers for transmission.8.2.4.30.6.3 Test description

8.2.4.30.6.3.1 Pre-test conditions

System Simulator:

– Cell 1 and Cell 3.

UE:

None.

Preamble:

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

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

8.2.4.30.6.3.2 Test procedure sequence

Table 8.2.4.30.6.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", "T2", and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

T2

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

T3

Cell-specific RS EPRE

dBm/15kHz

-85

-79

T4

Cell-specific RS EPRE

dBm/15kHz

“Off”

-85

T5

Cell-specific RS EPRE

dBm/15kHz

-79

-85

T6

Cell-specific RS EPRE

dBm/15kHz

“Off”

“Off”

T7

Cell-specific RS EPRE

dBm/15kHz

-85

“Off”

NOTE 1: Power level “Off” is defined in TS36.508 Table 6.2.2.1-1.

Table 8.2.4.30.6.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS changes Cell 1 and Cell 3 parameters according to the row "T1" in table 8.2.4.30.6.3.2-1.

2

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform Inter frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 3, the steps specified in Table 8.2.4.30.6.3.2-3 should take place on Cell 3.

3

The SS changes Cell 1 and Cell 3 parameters according to the row "T2" in table 8.2.4.30.6.3.2-1.

4

Check: Does the UE transmit an FailureInformation message on Cell 1

–>

FailureInformation

1

P

5

The SS changes Cell 1 and Cell 3 parameters according to the row "T3" in table 8.2.4.30.6.3.2-1.

6

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform Inter frequency handover to Cell 3.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 7, the steps specified in Table 8.2.4.30.6.3.2-3 should take place on Cell 3.

7

The SS changes Cell 1 and Cell 3 parameters according to the row "T4" in table 8.2.4.30.6.3.2-1.

8

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

–>

RRCConnectionReestablishmentRequest

2

P

9

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 3.

<–

RRCConnectionReestablishment

10

Check: Does the UE transmit an RRCConnectionReestablishmentComplete message using the security key derived from the currently active KeNB on Cell 3?

–>

RRCConnectionReestablishmentComplete

11

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

<–

RRCConnectionReconfiguration

12

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3.

–>

RRCConnectionReconfigurationtComplete

13

The SS changes Cell 1 and Cell 3 parameters according to the row "T5" in table 8.2.4.30.6.3.2-1.

14

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform Inter frequency handover to Cell 1.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 15, the steps specified in Table 8.2.4.30.6.3.2-3 should take place on Cell 1.

15

The SS changes Cell 1 and Cell 3 parameters according to the row "T6" in table 8.2.4.30.6.3.2-1.

16

Wait for 12s to make T311 expired.

17

The SS changes Cell 1 and Cell 3 parameters according to the row "T7" in table 8.2.4.30.6.3.2-1.

18

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

3

P

Table 8.2.4.30.6.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the handover using MAC Random Access Preamble.

2

The SS does not respond.

8.2.4.30.6.3.3 Specific message contents

Table 8.2.4.30.6.3.3-0: Conditions for specific message contents
in Table 8.2.4.30.6.3.3-2

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.30.6.3.3-1: RRCConnectionReconfiguration (steps 2, 6 and 14, Table 8.2.4.30.6.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

mobilityControlInfo

MobilityControlInfo

radioResourceConfigDedicated

RadioResourceConfigDedicated

}

}

}

}

Table 8.2.4.30.6.3.3-2: MobilityControlInfo (Table 8.2.4.30.6.3.3-1)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 3

Step 2 and step 6

PhysicalCellIdentity of Cell 1

Step 14

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 3

Step 2 and step 6

Same downlink EARFCN as used for Cell 1

Step 14

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 3

Band 24 High range, Step 2 and 6

Same uplink EARFCN as used for Cell 1

Band 24 High range, Step 14

}

carrierFreq SEQUENCE {}

Not present

carrierFreq-v9e0 SEQUENCE {

dl-CarrierFreq-v9e0

Same downlink EARFCN as used for Cell 3

Step 2 and step 6

Same downlink EARFCN as used for Cell 1

Step 14

ul-CarrierFreq-v9e0

Not present

}

}

Table 8.2.4.30.6.3.3-3: RadioResourceConfigCommon-DEFAULT (Table 8.2.4.30.6.3.3-2)

Derivation Path: 36.508, Table 4.6.3-13

Information Element

Value/remark

Comment

Condition

RadioResourceConfigCommon-DEFAULT ::= SEQUENCE {

rach-ConfigCommon

RACH-ConfigCommon-DEFAULT

}

Table 8.2.4.30.6.3.3-4: RACH-ConfigCommon-DEFAULT (Table 8.2.4.30.6.3.3-3)

Derivation Path: 36.508, Table 4.6.3-12

Information Element

Value/remark

Comment

Condition

RACH-ConfigCommon-DEFAULT ::= SEQUENCE {

ra-SupervisionInfo SEQUENCE {

preambleTransMax

n200

}

}

Table 8.2.4.30.6.3.3-5: RadioResourceConfigDedicated (Table 8.2.4.30.6.3.3-1)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

RadioResourceConfigDedicated::= SEQUENCE {

srb-ToAddModList

Not present

drb-ToAddModList SEQUENCE {

1 entries

drb-ToAddMod

DRB-ToAddMod-DEFAULT

}

drb-ToReleaseList

Not present

mac-MainConfig

Not present

mac-MainConfig

Not Present

sps-Config

Not present

physicalConfigDedicated

Not present

}

}

Table 8.2.4.30.6.3.3-6: DRB-ToAddMod-DEFAULT (Table 8.2.4.30.6.3.3-5)

Derivation Path: 36.331 clause 6.3.2

Information Element

Value/remark

Comment

Condition

DRB-ToAddMod-DEFAULT(bid) ::= SEQUENCE {

bid is the bearer identity (1..8)

eps-BearerIdentity

Not Present

drb-Identity

1

pdcp-Config

Not Present

rlc-Config

Not Present

logicalChannelIdentity

Not Present

logicalChannelConfig

Not Present

daps-HO-r16

TRUE

}

Table 8.2.4.30.6.3.3-7: FailureInformation (Step 4, Table 8.2.4.30.6.3.2-2)

Derivation Path: 36.331 clause 6.2.2

Information Element

Value/remark

Comment

Condition

FailureInformation-r16 ::= SEQUENCE {

criticalExtensions CHOICE {

failureInformation-r16 SEQUENCE {

failedLogicalChannelIdentity-r16 SEQUENCE {}

Not present

failureType-r16

dapsHO-failure

NonCriticalExtension SEQUENCE {}

Not present

}

criticalExtensionsFuture SEQUENCE {}

Not present

}

}

8.2.4.31 RRC connection reconfiguration / Handover / Conditional Handover

8.2.4.31.1 Conditional handover / Success / A3 / A5 / A3+A5

8.2.4.31.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting conditional handover and receiving RRCConnectionReconfiguration message includes the conditionalReconfiguration }

ensure that {

when { any CHO execution condition is not satisfied } then { UE maintains connection with source eNB and starts evaluating the CHO execution conditions for the candidate cell(s) }

}

(2)

with { UE in RRC_CONNECTED state and supporting conditional handover }

ensure that {

when { UE receives RRCConnectionReconfiguration message includes the conditionalReconfiguration and only event A3 is configured as conditional handover trigger event } then { UE starts evaluating the CHO execution condition A3 and perform conditional handover to the neighbour cell triggered in conditional configuration execution }

}

(3)

with { UE in RRC_CONNECTED state and supporting conditional handover }

ensure that {

when { UE receives RRCConnectionReconfiguration message includes the conditionalReconfiguration and only event A5 is configured as conditional handover trigger event } then { UE starts evaluating the CHO execution condition A5 and perform conditional handover to the neighbour cell triggered in conditional configuration execution }

}

(4)

with { UE in RRC_CONNECTED state and supporting conditional handover }

ensure that {

when { UE receives RRCConnectionReconfiguration message includes the conditionalReconfiguration and both event A3 and event A5 are configured as conditional handover trigger events } then { UE starts evaluating the CHO execution condition A3 and A5 and perform conditional handover to the neighbour cell triggered in conditional configuration execution }

}

(5)

with { UE in RRC_CONNECTED state and supporting conditional handover }

ensure that {

when { UE perform conditional handover procedure successfully } then { UE releases the stored CHO configurations }

}

8.2.4.31.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clause 5.3.5.9.1, 5.3.5.9.4, 5.3.5.9.5 and 5.3.5.3. Unless otherwise stated these are Rel-16 requirements.

[TS 36.331, clause 5.3.5.9.1]

The network configures the UE with conditional reconfiguration (i.e. conditional handover) including per candidate target cell an RRCConnectionReconfiguration to be stored and to be applied upon the fulfilment of an associated execution condition.

The UE shall:

1> if the received conditionalReconfiguration includes the condReconfigurationToRemoveList:

2> perform the conditional reconfiguration removal procedure as specified in 5.3.5.9.2;

1> if the received conditionalReconfiguration includes the condReconfigurationToAddModList:

2> perform the conditional reconfiguration addition/modification procedure as specified in 5.3.5.9.3;

[TS 36.331, clause 5.3.5.9.4]

If AS security has been activated successfully, the UE shall:

1> if VarConditionalReconfiguration includes at least one condReconfigurationId:

2> perform conditional reconfiguration evaluation;

1> for each condReconfigurationId within the VarConditionalReconfiguration:

2> consider the cell which has a physical cell identity matching the value indicated in the ServingCellConfigCommon within condReconfigurationToApply to be an applicable cell;

2> for each measId included in the measIdList within VarMeasConfig indicated in the triggerCondition associated to condReconfigurationId:

3> if the entry condition(s) applicable for this event associated with the condReconfigurationId, i.e. the event corresponding with the condEventId of the corresponding condReconfigurationTriggerEUTRA within VarConditionalReconfiguration, is fulfilled for the applicable cell for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfiguration:

4> consider the entry condition for the associated measId within triggerCondition as fulfilled;

3> if the leaving condition(s) applicable for this event associated with the condReconfigurationId, i.e. the event corresponding with the condEventId(s) of the corresponding condReconfigurationTriggerEUTRA within VarConditionalReconfiguration, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event within the VarConditionalReconfiguration:

4> consider the event associated to that measId to be not fulfilled;

2> if trigger conditions for all associated measId(s) within triggerCondition are fulfilled:

3> consider the target cell candidate within the stored condReconfigurationToApply, associated to that condReconfigurationId, as a triggered cell;

3> initiate the conditional reconfiguration execution, as specified in 5.3.5.9.5;

[TS 36.331, clause 5.3.5.9.5]

The UE shall:

1> if more than one triggered cell exists:

2> select one of the triggered cells as the selected cell for conditional reconfiguration;

1> for the selected cell of conditional reconfiguration:

2> apply the stored condReconfigurationToApply associated to that condReconfigurationId and perform the actions as specified in 5.3.5.4;

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the RRCConnectionReconfiguration message includes the conditionalReconfiguration:

2> perform conditional reconfiguration as specified in 5.3.5.9;

NOTE 6: In case of conditional reconfiguration the text "if the received RRCConnectionReconfiguration. . ." corresponds to applying the stored RRCConnectionReconfiguration message (according to 5.3.5.9.5).

8.2.4.31.1.3 Test description

8.2.4.31.1.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 2 and Cell4.

UE:

– None.

Preamble:

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

8.2.4.31.1.3.2 Test procedure sequence

Table 8.2.4.31.1.3.2-1 illustrate the downlink power levels to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1", "T2" and "T3", are to be applied in the test procedure in Table 8.2.4.31.1.3.2-2.

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

Parameter

Unit

Cell 1

Cell 2

Cell 4

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-82

-91

-91

Power levels are such that UE registered on Cell 1 and entry condition for event A3 is not satisfied

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-79

-91

Power levels are such that entry condition for event A3 is satisfied for Cell 2

T2

Cell-specific RS EPRE

dBm/15kHz

-91

-91

-79

Power levels are such that entry condition for event A5 is satisfied for Cell 4

T3

Cell-specific RS EPRE

dBm/15kHz

-79

-91

-91

Power levels are such that entry condition for event A3 and event A5 are satisfied for Cell 1

Table 8.2.4.31.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration including measConfig and conditionalReconfiguration to set Cell 2 and Cell 4 as target candidate cells and configure event A3 as trigger event in Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message in Cell 1.

–>

RRCConnectionReconfigurationComplete

3

Check: Does the UE attempt to perform the handover using MAC Random Access Preamble on Cell 2 within the next 5s?

–>

(PRACH Preamble)

1

F

4

SS adjusts the cell-specific reference signal level according to row "T1".

5

Check: Does the UE transmits RRCConnectionReconfigurationComplete message in Cell 2?

–>

RRCConnectionReconfigurationComplete

2

P

6

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 in Cell 2?

2

P

7

The SS transmits an RRCConnectionReconfiguration including measConfig and conditionalReconfiguration to set Cell 1 and Cell 4 as target candidate cells and configure event A5 as trigger event in Cell 2.

<–

RRCConnectionReconfiguration

8

The UE transmits an RRCConnectionReconfigurationComplete message in Cell 2.

–>

RRCConnectionReconfigurationComplete

9

SS adjusts the cell-specific reference signal level according to row "T2".

10

Check: Does the UE ransmits RRCConnectionReconfigurationComplete in Cell 4.

–>

RRCConnectionReconfigurationComplete

3

P

11

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 in Cell 4?

3

P

12

The SS transmits an RRCConnectionReconfiguration including measConfig and conditionalReconfiguration for intra-frequency event A3 and A5 in Cell 4.

<–

RRCConnectionReconfiguration

13

The UE transmits an RRCConnectionReconfigurationComplete message in Cell 4.

–>

RRCConnectionReconfigurationComplete

14

SS adjusts the cell-specific reference signal level according to row "T3".

15

Check: Does the UE ransmits RRCConnectionReconfigurationComplete message in Cell 1.

–>

RRCConnectionReconfigurationComplete

4

P

16

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 in Cell 1?

4

P

17

SS adjusts the cell-specific reference signal level according to row "T1".

18

Check: Does the UE transmit RRCConnectionReconfigurationComplete message in Cell 2 within 10s?

–>

RRCConnectionReconfigurationComplete

5

F

8.2.4.31.1.3.3 Specific message contents

Table 8.2.4.31.1.3.3-1: RRCConnectionReconfiguration (Step 1, step 7 and step 12, Table 8.2.4.31.1.3.2-3)

Derivation Path: 36.508 Table 4.6.1-8

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 ::= SEQUENCE {

measConfig

MeasConfig-DEFAULT

Table 8.2.4.31.1.3.3-2

mobilityControlInfo

Not present

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

conditionalReconfiguration-r16

ConditionalReconfiguration

Table 8.2.4.31.1.3.3-5

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.4.31.1.3.3-2: MeasConfig-DEFAULT (Table 8.2.4.31.1.3.3-1)

Derivation Path: TS 36.508 Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig-DEFAULT ::= SEQUENCE {

MeasObjectToAddModList SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasObjectToAddMod {

1 entry

MeasObjectToAddMod[1] SEQUENCE {

entry 1

measObjectId

1

measObject CHOICE {

measObjectEUTRA

MeasObjectEUTRA-GENERIC

Table 8.2.4.31.1.3.3-3

}

}

}

ReportConfigToAddModList SEQUENCE(SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod {

2 entries

ReportConfigToAddMod[1] SEQUENCE {

entry 1

reportConfigId

1

reportConfig CHOICE {

reportConfigEUTRA

ReportConfigEUTRA-A3-CHO

Table 8.2.4.31.1.3.3-4

}

}

ReportConfigToAddMod[2] SEQUENCE {

entry 2

reportConfigId

2

reportConfig CHOICE {

reportConfigEUTRA

ReportConfigEUTRA-A5-CHO(-80,-86) with condition Not RSRQ

}

}

}

measIdToAddModList SEQUENCE (SIZE (1.. maxMeasId)) OF MeasIdToAddMod {

1 entry

Step 1, Step 7

MeasIdToAddMod[1] SEQUENCE {

entry 1

measId

1

measObjectId

1

reportConfigId

1

Step 1

2

Step 7

}

}

measIdToAddModList SEQUENCE (SIZE (1.. maxMeasId)) OF MeasIdToAddMod {

2 entries

Step 12

MeasIdToAddMod[1] SEQUENCE {

entry 1

measId

1

measObjectId

1

reportConfigId

1

}

MeasIdToAddMod[2] SEQUENCE {

entry 2

measId

2

measObjectId

1

reportConfigId

2

}

}

}

Table 8.2.4.31.1.3.3-3: MeasObjectEUTRA-GENERIC (Table 8.2.4.31.1.3.3-2)

Derivation Path: TS 36.508 Table 4.6.6-2

Information Element

Value/remark

Comment

Condition

MeasObjectEUTRA-GENERIC::= SEQUENCE {

carrierFreq

ARFCN-ValueEUTRA for Cell 1

}

Table 8.2.4.31.1.3.3-4: ReportConfigEUTRA-A3-CHO (Table 8.2.4.31.1.3.3-2)

Derivation Path: 36.508 clause 4.6.6-17

Information Element

Value/remark

Comment

Condition

ReportConfigEUTRA-A3 ::= SEQUENCE {

condReconfigurationTriggerEUTRA-r16 ::= SEQUENCE {

condEventId-r16 CHOICE {

condEventA3-r16 SEQUENCE {

a3-Offset-r16

2

1 dB

}

}

}

}

Table 8.2.4.31.1.3.3-5: ConditionalReconfiguration (Table 8.2.4.31.1.3.3-1)

Derivation Path: TS 36.331 clause 6.3.4

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16::= SEQUENCE {

condReconfigurationToAddModList-r16

CondReconfigurationToAddModList-r16 (Step 1 and step 9)

Table 8.2.4.31.1.3.3-6

Step 1, Step 7

CondReconfigurationToAddModList-r16 (Step 16)

Table 8.2.4.31.1.3.3-9

Step 12

condReconfigurationToRemoveList-r16

Not present

}

Table 8.2.4.31.1.3.3-6: CondReconfigToAddModList-r16 (Step 1 and step 7, Table 8.2.4.31.1.3.3-5)

Derivation Path: TS 36.331 clause 6.3.4

Information Element

Value/remark

Comment

Condition

CondReconfigurationToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxCondConfig-r16)) OF CondReconfigurationAddMod-r16 {

2 entries

CondReconfigurationAddMod-r16 [1] ::= SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16::= SEQUENCE {

MeasId [1]

1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO and HO Cell 2

Table 8.2.4.31.1.3.3-7

Step 1

RRCConnectionReconfiguration with condition HO and HO Cell 1

Table 8.2.4.31.1.3.3-7

Step 7

}

CondReconfigurationAddMod-r16 [2] ::= SEQUENCE {

entry 2

condReconfigurationId-r16

2

triggerCondition-r16::= SEQUENCE {

MeasId [1]

1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO and HO Cell 4

Table 8.2.4.31.1.3.3-7

}

}

Table 8.2.4.31.1.3.3-7: RRCConnectionReconfiguration (Table 8.2.4.31.1.3.3-7)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo

MobilityControlInfo

Table 8.2.4.31.1.3.3-8

}

}

}

}

Table 8.2.4.31.1.3.3-8: MobilityControlInfo (Table 8.2.4.31.1.3.3-7)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 2

HO Cell 2

PhysicalCellIdentity of Cell 1

HO Cell 1

PhysicalCellIdentity of Cell 4

HO Cell 4

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 2

HO Cell 2

Same downlink EARFCN as used for Cell 1

HO Cell 1

Same downlink EARFCN as used for Cell 4

HO Cell 4

ul-CarrierFreq

Not present

Same uplink EARFCN as used for Cell 2

Band 24 High range, HO Cell 2

Same uplink EARFCN as used for Cell 1

Band 24 High range, HO Cell 1

Same uplink EARFCN as used for Cell 4

Band 24 High range, HO Cell 4

}

}

Condition

Explanation

Band 24 High range

If Band 24 high frequency range is selected for the target cell

Table 8.2.4.31.1.3.3-9: CondReconfigurationToAddModList-r16 (Step 16, Table 8.2.4.31.1.3.3-6)

Derivation Path: TS 36.331 clause 6.3.4

Information Element

Value/remark

Comment

Condition

CondReconfigurationToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxCondConfig-r16)) OF CondReconfigurationAddMod-r16{

2 entries

CondReconfigurationAddMod-r16 [1] ::= SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16::= SEQUENCE {

MeasId [1]

1

MeasId [2]

2

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO and HO Cell 1

Table 8.2.4.31.1.3.3-7

}

CondReconfigurationAddMod-r16 [2] ::= SEQUENCE {

entry 2

condReconfigurationId-r16

2

triggerCondition-r16::= SEQUENCE {

MeasId [1]

1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO and HO Cell 2

Table 8.1.4.4.1.3.3-7

}

}

8.2.4.31.2 Conditional handover / modify conditional handover configuration

8.2.4.31.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting conditional handover and receiving RRCConnectionReconfiguration message including the conditionalReconfiguration }

ensure that {

when { UE received another conditionalReconfiguration including the condReconfigurationToRemoveList before any CHO execution condition is satisfied }

then { UE removes the entry with the matching condReconfigurationId from the condReconfigurationList within the VarConditionalReconfiguration }

}

(2)

with { UE in RRC_CONNECTED state and supporting conditional handover and receiving RRCConnectionReconfiguration message including the conditionalReconfiguration }

ensure that {

when { UE received another conditionalReconfiguration including the condReconfigurationToAddModList before any CHO execution condition is satisfied }

then { UE performs the conditional reconfiguration addition/modification procedure }

}

8.2.4.31.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.2.1a.1 and 10.1.2.1a.2 and TS 36.331 clause 5.3.5.3, 5.3.5.9.1, 5.3.5.9.2 and 5.3.5.9.3. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.2.1a.1]

A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) for CHO candidate cells upon receiving the CHO configuration, and executes CHO once the execution condition(s) are met for a CHO candidate cell. UE stops evaluating the execution condition(s) once the handover is executed (legacy handover or conditional handover execution).

The following principles apply to CHO:

– The CHO configuration contains the configuration of CHO candidate cell(s) generated by each CHO candidate cell and execution condition(s) generated by the source cell.

– An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.

– UE maintains connection with source eNB until UE determines a CHO execution condition is met for CHO candidate cell.

– Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 10.1.2.1, regardless of any previously received CHO configuration.

– After source eNB sends CHO command to UE, the network is allowed to change source eNB configuration and network can add, modify or release a configured CHO configuration using RRC message (i.e. until UE starts executing CHO.

– While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.

NOTE 1: CHO is not supported for S1 based handover in this release of the specification.

NOTE 2: In case LTE-DC is configured, CHO is only supported in MeNB to eNB change procedure in this release of the specification.

[TS 36.300, clause 10.1.2.1a.2]

The figure below depicts the CHO scenario where neither MME nor Serving Gateway changes:

Figure 10.1.2.1a-1: Intra-MME/Serving Gateway Conditional Handover

1. The source eNB configures the UE with measurement configuration, which may be used by the UE to trigger Measurement Reports for potential CHO candidate cell(s).

2. A MEASUREMENT REPORT is triggered and sent to the source eNB.

3. The source eNB makes decision on the usage of CHO to handoff the UE based on MEASUREMENT REPORT information.

4. The source eNB requests a CHO to the eNB(s) of candidate cell(s). A CHO request message is sent for each candidate cell.

5. Same as step 5 in Figure 10.1.2.1.1-1 of clause 10.1.2.1.1.

6. The eNB(s) of candidate cell(s) sends CHO response including configuration of CHO candidate cell(s) to the source eNB. The response message is also sent for each candidate cell.

7. The source eNB sends a RRCConnectionReconfiguration message to the UE, containing configuration of CHO candidate cell(s) and CHO execution condition(s). The source eNB decides on the condition for the execution of CHO and adds the condition(s) to the RRC message sent to the UE.

NOTE 1: The source eNB may reconfigure the UE’s source configuration after providing CHO configuration for candidate target cell(s).

NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover.

8. The UE sends an RRCConnectionReconfigurationComplete message to the source eNB.

8a. If early data forwarding is applied, the source eNB sends the EARLY STATUS TRANSFER message.

9. The UE maintains connection with the source eNB after receiving CHO configuration, and starts evaluating the CHO execution condition(s) for the CHO candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source eNB, applies the stored corresponding configuration for that candidate cell and synchronises to that candidate cell.

10-11. The UE accesses to the target eNB and completes the handover procedure by sending RRCConnectionReconfigurationComplete message to the target eNB. The UE releases the stored CHO configurations after successful completion of RRC handover procedure.

11a/b. The target eNB sends the HANDOVER SUCCESS message to the source eNB to inform that the UE has successfully accessed the target cell. In return, the source eNB sends the SN STATUS TRANSFER message.

NOTE 2: Late data forwarding may be initiated as soon as the source eNB receives the HANDOVER SUCCESS message.

11c. The source eNB sends the HANDOVER CANCEL message toward the other signalling connections or other potential target eNBs, if any, to cancel CHO for the UE.

12. Steps 12-18 as in Figure 10.1.2.1.1-1.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the RRCConnectionReconfiguration message includes the conditionalReconfiguration:

2> perform conditional reconfiguration as specified in 5.3.5.9;

NOTE 6: In case of conditional reconfiguration the text "if the received RRCConnectionReconfiguration. . ." corresponds to applying the stored RRCConnectionReconfiguration message (according to 5.3.5.9.5).

[TS 36.331, clause 5.3.5.9.1]

The network configures the UE with conditional reconfiguration (i.e. conditional handover) including per candidate target cell an RRCConnectionReconfiguration to be stored and to be applied upon the fulfilment of an associated execution condition.

The UE shall:

1> if the received conditionalReconfiguration includes the condReconfigurationToRemoveList:

2> perform the conditional reconfiguration removal procedure as specified in 5.3.5.9.2;

1> if the received conditionalReconfiguration includes the condReconfigurationToAddModList:

2> perform the conditional reconfiguration addition/modification procedure as specified in 5.3.5.9.3;

[TS 36.331, clause 5.3.5.9.2]

The UE shall:

1> for each CondReconfigurationId included in the condReconfigurationToRemoveList that is part of the current UE configuration in VarConditionalReconfiguration:

2> remove the entry with the matching condReconfigurationId from the condReconfigurationList within the VarConditionalReconfiguration.

NOTE: The UE does not consider the message as erroneous if the condReconfigurationToRemoveList includes any CondReconfigurationId value that is not part of the current UE configuration.

[TS 36.331, clause 5.3.5.9.3]

The UE shall:

1> for each condReconfigurationId included in the condReconfigurationToAddModList:

2> if an entry with the matching condReconfigurationId exists in the condReconfigurationList within the VarConditionalReconfiguration:

3> if the entry in condReconfigurationToAddModList includes a triggerCondition;

4> replace triggerCondition within the VarConditionalReconfiguration with the value received for this condReconfigurationId

3> if the entry in condReconfigurationToAddModList includes an condReconfigurationToApply;

4> replace condReconfigurationToApply within the VarConditionalReconfiguration with the value received for this condReconfigurationId;

2> else:

3> add a new entry for this condReconfigurationId within the VarConditionalReconfiguration;

3> store the associated RRCConnectionReconfiguration in VarConditionalReconfiguration.

8.2.4.31.2.3 Test description

8.2.4.31.2.3.1 Pre-test conditions

System Simulator:

– Cell 1 Cell 2 and Cell 4.

UE:

– None.

Preamble:

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

8.2.4.31.2.3.2 Test procedure sequence

Table 8.2.4.31.2.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", "T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Cell 4

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-91

-91

Power levels are such that UE attached on Cell 1 and entry condition for event A3 is not satisfied

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-79

-91

Power levels are such that entry condition for event A3 is satisfied for Cell 2

T2

Cell-specific RS EPRE

dBm/15kHz

-91

-79

-79

Power levels are such that entry condition for event A3 is satisfied for Cell 2 and Cell 4

T3

Cell-specific RS EPRE

dBm/15kHz

-91

-91

-79

Power levels are such that entry condition for event A3 is satisfied for Cell 4

Table 8.2.4.31.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration in Cell 1 to set Cell 2 and Cell 4 as target candidate cells.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message including condReconfigurationToRemoveList in Cell 1 to remove Cell 2 from the target candidate cell list.

<–

RRCConnectionReconfiguration

4

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 1.

–>

RRCConnectionReconfigurationComplete

5

SS adjusts the cell-specific reference signal level according to row "T1".

6

Check: Does the UE attempt to perform the handover using MAC Random Access Preamble on Cell 2 within the next 5s?

–>

(PRACH Preamble)

1

F

7

The SS transmits an RRCConnectionReconfiguration message including condReconfigurationToAddModList in Cell 1 to replace Cell 4 with Cell 2 as the target candidate cell.

<–

RRCConnectionReconfiguration

8

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 1.

–>

RRCConnectionReconfigurationComplete

9

SS adjusts the cell-specific reference signal level according to row "T2".

10

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

–>

RRCConnectionReconfigurationComplete

2

P

11

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration in Cell 2 to set Cell 1 as target candidate cell.

<–

RRCConnectionReconfiguration

12

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 2.

–>

RRCConnectionReconfigurationComplete

13

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration in Cell 2 to add Cell 4 as target candidate cell.

<–

RRCConnectionReconfiguration

14

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 2.

–>

RRCConnectionReconfigurationComplete

15

SS adjusts the cell-specific reference signal level according to row "T3".

16

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 4?

–>

RRCConnectionReconfigurationComplete

2

P

8.2.4.31.2.3.3 Specific message contents

Table 8.2.4.31.2.3.3-1: RRCConnectionReconfiguration (step 1, step 3, step 7, step 11 and step 13, Table 8.2.4.31.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8 with condition CHO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

Not present

Step 3, Step 7, Step 13

MeasConfig

Table 8.2.4.31.2.3.3-2

Step 1, Step 11

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

conditionalReconfiguration-r16

ConditionalReconfiguration-r16-HO(Step 1)

Table 8.2.4.31.2.3.3-3

Step 1

ConditionalReconfiguration-r16-HO(Step 3)

Table 8.2.4.31.2.3.3-5

Step 3

ConditionalReconfiguration-r16-HO(Step 7)

Table 8.2.4.31.2.3.3-6

Step 7

ConditionalReconfiguration-r16-HO(Step 13)

Table 8.2.4.31.2.3.3-7

Step 11

ConditionalReconfiguration-r16-HO(Step 15)

Table 8.2.4.31.2.3.3-8

Step 13

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.4.31.2.3.3-2: MeasConfig (Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig-DEFAULT ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

1

reportConfig[1]

ReportConfigEUTRA-A3-CHO

Table 4.6.6-17 specified in TS 36.508

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

1

}

}

Table 8.2.4.31.2.3.3-3: ConditionalReconfiguration-r16-HO (Step 1, Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

2 entries

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 2

Table 8.2.4.31.2.3.3-4

}

CondReconfigurationAddMod-r16[2] SEQUENCE {

entry 2

condReconfigurationId-r16

2

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 4

Table 8.2.4.31.2.3.3-4

}

}

}

Table 8.2.4.31.2.3.3-4: ConditionalReconfiguration-r16-HO (Step 1, Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

2 entries

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 2

Table 8.2.4.31.2.3.3-4

}

CondReconfigurationAddMod-r16[2] SEQUENCE {

entry 2

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 4

Table 8.2.4.31.2.3.3-4

}

}

}

Table 8.2.4.31.2.3.3-5: RRCConnectionReconfiguration (Table 8.2.4.31.2.3.3-3)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

HO_to_Cell 1

PhysicalCellIdentity of Cell 2

HO_to_Cell 1

PhysicalCellIdentity of Cell 4

HO_to_Cell 1

}

}

}

}

}

Table 8.2.4.31.2.3.3-6: ConditionalReconfiguration-r16-HO (Step 3, Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

CondReconfigurationToRemoveList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationId-r16[1]

1

}

}

Table 8.2.4.31.2.3.3-7: ConditionalReconfiguration-r16-HO (Step 7, Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

2

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 2

Table 8.2.4.31.2.3.3-4

}

}

}

Table 8.2.4.31.2.3.3-8: ConditionalReconfiguration-r16-HO (Step 11, Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 1

Table 8.2.4.31.2.3.3-4

}

}

}

Table 8.2.4.31.2.3.3-9: ConditionalReconfiguration-r16-HO (Step 13, Table 8.2.4.31.2.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

2

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 4

Table 8.2.4.31.2.3.3-4

}

}

}

8.2.4.31.3 Conditional handover / Failure

8.2.4.31.3.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting conditional handover and network configured the UE to try CHO after HO/CHO failure and UE receiving an RRCReconfiguration message including a ConditionalReconfiguration }

ensure that {

when { UE detects conditional handover failure and performs cell selection to a CHO candidate cell before T311 expires }

then { UE perform conditional handover to the selected cell }

}

(2)

with { UE in RRC_CONNECTED state and supporting conditional handover and network configured the UE to try CHO after HO/CHO failure and UE receiving an RRCReconfiguration message including a ConditionalReconfiguration }

ensure that {

when { UE detects conditional handover failure and only finds a selectable cell which is not the candidate cell included in ConditionalReconfiguration before T311 expires }

then { UE initiate the connection re-establishment procedure in the selected cell }

}

(3)

with { UE in RRC_CONNECTED state and supporting conditional handover and network configured the UE to try CHO after HO/CHO failure and UE receiving an RRCReconfiguration message including a ConditionalReconfiguration }

ensure that {

when { UE detects conditional handover failure and cannot find any selectable cell before T311 expires }

then { UE goes to RRC_IDLE and release the stored conditional handover configurations }

}

8.2.4.31.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.2.1.0 and TS 36.331 clause 5.3.5.3, 5.3.7.3and 5.3.7.6. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.2.1.0]

The intra E-UTRAN HO of a UE in RRC_CONNECTED state is a UE-assisted network-controlled HO, with HO preparation signalling in E-UTRAN:

– Part of the HO command comes from the target eNB and is transparently forwarded to the UE by the source eNB;

– To prepare the HO, the source eNB passes all necessary information to the target eNB (e.g. E-RAB attributes and RRC context):

– When CA is configured and to enable SCell selection in the target eNB, the source eNB can provide in decreasing order of radio quality a list of the best cells and optionally measurement result of the cells.

– When DC is configured, the source MeNB provides the SCG configuration (in addition to the MCG configuration) to the target MeNB.

– Both the source eNB and UE keep some context (e.g. C-RNTI) to enable the return of the UE in case of HO failure;

– If RACH-less HO is not configured, the UE accesses the target cell via RACH following a contention-free procedure using a dedicated RACH preamble or following a contention-based procedure if dedicated RACH preambles are not available:

– the UE uses the dedicated preamble until the handover procedure is finished (successfully or unsuccessfully);

– If RACH-less HO is configured, the UE accesses the target cell via the uplink grant preallocated to the UE in the RRC message. If the UE does not receive the preallocated uplink grant in the RRC message from the source eNB, the UE monitors the PDCCH of the target cell;

– If DAPS handover is configured, the UE continues the downlink user data reception from the source eNB until releasing the source cell and continues the uplink user data transmission to the source eNB until successful random access procedure to the target eNB. Upon reception of the handover command, the UE:

– Creates a MAC entity for target cell;

– Establishes the RLC entity and an associated DTCH logical channel for target cell for each DRB configured with DAPS;

– For the DRB(s) configured with DAPS, reconfigures the PDCP entity to configure DAPS with separate security and ROHC functions for source and target and associates them with the RLC entities configured for source and target respectively;

– Retains rest of the source link configurations until release of the source.

– UE maintains only PCell connection with both source and target eNBs. Any other configured serving cells, NR sidelink configurations and V2X sidelink configurations are released by the network before the handover command is sent to the UE.

NOTE: Void.

– If the access towards the target cell (using RACH or RACH-less procedure) is not successful within a certain time, the UE initiates radio link failure recovery using a suitable cell except in DAPS handover or CHO scenarios:

– When DAPS handover fails, the UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment if the source link is still available; Otherwise, RRC re-establishment is performed;

– When initial CHO execution attempt fails or Handover fails, if network configured the UE to try CHO after HO/CHO failure and the UE performs cell selection to a CHO candidate cell, the UE attempts CHO execution to that cell; Otherwise, RRC re-establishment is performed.

– No ROHC and EHC context is transferred at handover;

– No UDC context is transferred at handover;

– ROHC and EHC contexts can be kept at handover within the same eNB.

[TS 36.331, clause 5.3.5.3]

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the RRCConnectionReconfiguration message includes the conditionalReconfiguration:

2> perform conditional reconfiguration as specified in 5.3.5.9;

NOTE 6: In case of conditional reconfiguration the text "if the received RRCConnectionReconfiguration. . ." corresponds to applying the stored RRCConnectionReconfiguration message (according to 5.3.5.9.5).

[TS 36.331, clause 5.3.7.3]

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

1> if T309 is running:

1> else:

2> stop timer T311;

2> if the cell selection is triggered by detecting radio link failure of the MCG or handover failure (including intra-E-UTRA handover and mobility from E-UTRA); and

2> if attemptCondReconf is configured; and

2> if the selected cell is one of the target candidate cells in VarConditionalReconfiguration:

3> apply the stored condReconfigurationToApply of the selected cell and perform the actions as specified in 5.3.5.4;

2> else:

3> if the UE is configured with conditionalReconfiguration:

4> release uplinkDataCompression, if configured;

4> suspend all RBs, including RBs configured with NR PDCP, except SRB0;

4> reset MAC;

4> release the MCG SCell(s), if configured, in accordance with 5.3.10.3a;

4> release the SCell group(s), if configured, in accordance with 5.3.10.3d;

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

4> for the MCG, apply the default semi-persistent scheduling configuration as specified in 9.2.3;

4> for the MCG, apply the default MAC main configuration as specified in 9.2.2;

4> release powerPrefIndicationConfig, if configured and stop timer T340, if running;

4> release reportProximityConfig, if configured and clear any associated proximity status reporting timer;

4> release obtainLocationConfig, if configured;

4> release idc-Config, if configured;

4> release sps-AssistanceInfoReport, if configured;

4> release measSubframePatternPCell, if configured;

4> release the entire SCG configuration, if configured, except for the DRB configuration (as configured by drb-ToAddModListSCG);

4> if (NG)EN-DC is configured:

5> perform MR-DC release, as specified in TS 38.331[82], clause 5.3.5.10;

5> release p-MaxEUTRA, if configured;

5> release p-MaxUE-FR1, if configured;

5> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

4> release naics-Info for the PCell, if configured;

4> if connected as an RN and configured with an RN subframe configuration:

5> release the RN subframe configuration;

4> release the LWA configuration, if configured, as described in 5.6.14.3;

4> release the LWIP configuration, if configured, as described in 5.6.17.3;

4> release delayBudgetReportingConfig, if configured and stop timer T342, if running;

4> release bw-PreferenceIndicationTimer, if configured and stop timer T341, if running;

4> release overheatingAssistanceConfig and overheatingAssistanceConfigForSCG, if configured and stop timer T345, if running;

4> release ailc-BitConfig, if configured;

3> remove all the entries within VarConditionalReconfiguration, if any;

3> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA configured:

4> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

4> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA:

5> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

4> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

3> start timer T301;

3> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

3> if the UE is a NB-IoT UE connected to EPC, the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation and AS security has not been activated; and

3> if cp-reestablishment is not included in SystemInformationBlockType2-NB:

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

3> else:

4> 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 PCell.

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

1> if the selected cell is a UTRA cell, and if the UE supports Radio Link Failure Report for Inter-RAT MRO, include selectedUTRA-CellId in the VarRLF-Report and set it to the physical cell identity and carrier frequency of the selected UTRA cell;

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.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’;

8.2.4.31.3.3 Test description

8.2.4.31.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 Cell 2 and Cell 4.

UE:

– None.

Preamble:

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

8.2.4.31.3.3.2 Test procedure sequence

Table 8.2.4.31.3.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", "T2" and "T3" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Cell 4

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

off

off

Power levels are such that UE attached on Cell 1 and entry condition for event A3 is not satisfied

T1

Cell-specific RS EPRE

dBm/15kHz

-91

-79

-81

Power levels are such that entry condition for event A3 is satisfied for Cell 2 and Cell 4

T2

Cell-specific RS EPRE

dBm/15kHz

-113

-113

-79

The power level is such that only SrxlevNR Cell 4 > 0

T3

Cell-specific RS EPRE

dBm/15kHz

-79

-81

-91

Power levels are such that entry condition for event A3 is satisfied for Cell 2 and Cell 4

T4

Cell-specific RS EPRE

dBm/15kHz

-113

-79

-113

The power level is such that only SrxlevNR Cell 2 > 0

T5

Cell-specific RS EPRE

dBm/15kHz

off

-91

-79

Power levels are such that entry condition for event A3 is satisfied for Cell 4

T6

Cell-specific RS EPRE

dBm/15kHz

off

-113

-113

The power level is such that all SrxlevNR Cell < 0

T7

Cell-specific RS EPRE

dBm/15kHz

off

off

-85

The power level is such that only SrxlevNR Cell 4 > 0

Table 8.2.4.31.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration in Cell 1 to set Cell 2 and Cell 4 as target candidate cells.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 1.

–>

RRCConnectionReconfigurationComplete

3

SS adjusts the cell-specific reference signal level according to row "T1".

EXCEPTION: The step 4 below is repeated preambleTransMax times for the duration of T304. (Note 1)

4

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 2.

5

The SS does not respond on Cell 2.

6

SS adjusts the cell-specific reference signal level according to row "T2".

7

The SS starts timer T311 when the number of Random Access Preamble repetition from UE reaches preambleTransMax.

8

Check: Does the UE transmit RRCReconfigurationComplete message in NR Cell 4 before T311 expires?

–>

RRCReconfigurationComplete

1

P

9

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration in Cell 4 to set Cell 1 as target candidate cell.

<–

RRCConnectionReconfiguration

10

The UE transmits an RRCConnectionReconfigurationComplete message in Cell 4.

–>

RRCConnectionReconfigurationComplete

11

SS adjusts the cell-specific reference signal level according to row "T3".

EXCEPTION: The step 12 below is repeated preambleTransMax times for the duration of T304. (Note 1)

12

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 1.

13

The SS does not respond on Cell 1.

14

SS adjusts the cell-specific reference signal level according to row "T4".

15

The SS starts timer T311 when the number of Random Access Preamble repetition from UE reaches preambleTransMax.

16

Check: Does the UE transmit RRCConnectionReestablishmentRequest message in NR Cell 2 before T311 expires?

–>

RRCConnectionReestablishmentRequest

2

P

17

The SS transmits an RRCConnectionReestablishment message to resume SRB1 operation and re-activate security on Cell 2.

<–

RRCConnectionReestablishment

18

The UE transmits an RRCConnectionReestablishmentComplete message on Cell 2.

–>

RRCConnectionReestablishmentComplete

19

The SS transmits an RRCConnectionReconfiguration message to resume existing radio bearer and set Cell 4 as target candidate cell on Cell 2.

<–

RRCConnectionReconfiguration

20

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 2.

–>

RRCConnectionReconfigurationComplete

21

SS adjusts the cell-specific reference signal level according to row "T5".

EXCEPTION: The step 22 below is repeated preambleTransMax times for the duration of T304. (Note 1)

22

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 4.

23

The SS does not respond on Cell 4.

24

SS adjusts the cell-specific reference signal level according to row "T6".

25

The SS starts timer T311 when the number of Random Access Preamble repetition from UE reaches preambleTransMax and wait timer T311 expires.

26

The SS changes the TAC for Cell 4 to 2.

27

SS adjusts the cell-specific reference signal level according to row "T7".

28

Check: Does the generic test procedure in TS 36.508 subclause 6.4.2.7 is performed on Cell 4?

–>

RRCConnectionReconfigurationComplete

3

P

Note 1: The default value of preambleTransMax is set to n6.

8.2.4.31.3.3.3 Specific message contents

Table 8.2.4.31.3.3.3-1: RRCConnectionReconfiguration (step 1, step 9, step 19, Table 8.2.4.31.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8 with condition CHO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

MeasConfig

Table 8.2.4.31.3.3.3-2

Step 1, Step 9, Step 19

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

conditionalReconfiguration-r16

ConditionalReconfiguration-r16-HO(Step 1)

Table 8.2.4.31.3.3.3-3

Step 1

ConditionalReconfiguration-r16-HO(Step 9)

Table 8.2.4.31.3.3.3-5

Step 9

ConditionalReconfiguration-r16-HO(Step 19)

Table 8.2.4.31.3.3.3-6

Step 19

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.4.31.3.3.3-2: MeasConfig (Table 8.2.4.31.3.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig-DEFAULT ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

1

reportConfig[1]

ReportConfigEUTRA-A3-CHO

Table 4.6.6-17 specified in TS 36.508

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

1

}

}

Table 8.2.4.31.3.3.3-3: ConditionalReconfiguration-r16-HO (Step 1, Table 8.2.4.31.3.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

2 entries

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 2

Table 8.2.4.31.3.3.3-4

}

CondReconfigurationAddMod-r16[2] SEQUENCE {

entry 2

condReconfigurationId-r16

2

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 4

Table 8.2.4.31.3.3.3-4

}

}

}

Table 8.2.4.31.3.3.3-4: RRCConnectionReconfiguration (Table 8.2.4.31.3.3.3-3)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

HO_to_Cell 1

PhysicalCellIdentity of Cell 2

HO_to_Cell 2

PhysicalCellIdentity of Cell 4

HO_to_Cell 4

}

}

}

}

}

Table 8.2.4.31.3.3.3-5: ConditionalReconfiguration-r16-HO (Step 9, Table 8.2.4.31.3.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 1

Table 8.2.4.31.3.3.3-4

}

}

}

Table 8.2.4.31.3.3.3-6: ConditionalReconfiguration-r16-HO (Step 19, Table 8.2.4.31.3.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

RRCConnectionReconfiguration with condition HO_to_Cell 4

Table 8.2.4.31.3.3.3-4

}

}

}

Table 8.2.4.31.3.3.3-7: SystemInformationBlockType1 for Cell 4 (step 26, Table 8.2.4.31.3.3.2-2)

Derivation Path: 36.508 Table 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

cellAccessRelatedInformation SEQUENCE {

trackingAreaCode

2

}

systemInfoValueTag

1

}

8.2.4.31.4 Conditional handover / Handover / Handover Failure

8.2.4.31.4.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state and supporting conditional handover and receiving RRCConnectionReconfiguration message including the conditionalReconfiguration }

ensure that {

when { UE receives HO command (without CHO configuration) before any CHO execution condition is satisfied }

then { UE executes the HO procedure, regardless of any previously received CHO configuration }

}

(2)

with { UE having stored conditionalReconfiguration and receiving another RRCConnectionReconfiguration message including the mobilityControlInfo for handover to a neighbour cell }

ensure that {

when { UE detects handover failure and finds a selectable cell which is the candidate cell included in conditionalReconfiguration before T311 expires }

then { UE applies the stored conditionalReconfiguration associated to the selected cell and perform conditional handover to the selected cell }

}

(3)

with { UE having stored conditionalReconfiguration and receiving another RRCConnectionReconfiguration message including the mobilityControlInfo for handover to a neighbour cell }

ensure that {

when { UE detects handover failure and cannot find any selectable cell before T311 expires }

then { UE goes to RRC_IDLE and releases the stored conditional handover configurations }

}

8.2.4.31.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.300 clause 10.1.2.1.0, 10.1.2.1a.1 and 10.1.2.1a.2 and TS 36.331 clause 5.3.7.3 and 5.3.12. Unless otherwise stated these are Rel-16 requirements.

[TS 36.300, clause 10.1.2.1.0]

The intra E-UTRAN HO of a UE in RRC_CONNECTED state is a UE-assisted network-controlled HO, with HO preparation signalling in E-UTRAN:

– Part of the HO command comes from the target eNB and is transparently forwarded to the UE by the source eNB;

– To prepare the HO, the source eNB passes all necessary information to the target eNB (e.g. E-RAB attributes and RRC context):

– When CA is configured and to enable SCell selection in the target eNB, the source eNB can provide in decreasing order of radio quality a list of the best cells and optionally measurement result of the cells.

– When DC is configured, the source MeNB provides the SCG configuration (in addition to the MCG configuration) to the target MeNB.

– Both the source eNB and UE keep some context (e.g. C-RNTI) to enable the return of the UE in case of HO failure;

– If RACH-less HO is not configured, the UE accesses the target cell via RACH following a contention-free procedure using a dedicated RACH preamble or following a contention-based procedure if dedicated RACH preambles are not available:

– the UE uses the dedicated preamble until the handover procedure is finished (successfully or unsuccessfully);

– If RACH-less HO is configured, the UE accesses the target cell via the uplink grant preallocated to the UE in the RRC message. If the UE does not receive the preallocated uplink grant in the RRC message from the source eNB, the UE monitors the PDCCH of the target cell;

– If DAPS handover is configured, the UE continues the downlink user data reception from the source eNB until releasing the source cell and continues the uplink user data transmission to the source eNB until successful random access procedure to the target eNB. Upon reception of the handover command, the UE:

– Creates a MAC entity for target cell;

– Establishes the RLC entity and an associated DTCH logical channel for target cell for each DRB configured with DAPS;

– For the DRB(s) configured with DAPS, reconfigures the PDCP entity to configure DAPS with separate security and ROHC functions for source and target and associates them with the RLC entities configured for source and target respectively;

– Retains rest of the source link configurations until release of the source.

– UE maintains only PCell connection with both source and target eNBs. Any other configured serving cells, NR sidelink configurations and V2X sidelink configurations are released by the network before the handover command is sent to the UE.

NOTE: Void.

– If the access towards the target cell (using RACH or RACH-less procedure) is not successful within a certain time, the UE initiates radio link failure recovery using a suitable cell except in DAPS handover or CHO scenarios:

– When DAPS handover fails, the UE falls back to source cell configuration, resumes the connection with source cell, and reports the DAPS handover failure via the source without triggering RRC connection re-establishment if the source link is still available; Otherwise, RRC re-establishment is performed;

– When initial CHO execution attempt fails or Handover fails, if network configured the UE to try CHO after HO/CHO failure and the UE performs cell selection to a CHO candidate cell, the UE attempts CHO execution to that cell; Otherwise, RRC re-establishment is performed.

– No ROHC and EHC context is transferred at handover;

– No UDC context is transferred at handover;

– ROHC and EHC contexts can be kept at handover within the same eNB.

[TS 36.300, clause 10.1.2.1a.1]

A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) for CHO candidate cells upon receiving the CHO configuration, and executes CHO once the execution condition(s) are met for a CHO candidate cell. UE stops evaluating the execution condition(s) once the handover is executed (legacy handover or conditional handover execution).

The following principles apply to CHO:

– The CHO configuration contains the configuration of CHO candidate cell(s) generated by each CHO candidate cell and execution condition(s) generated by the source cell.

– An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evaluation of CHO execution condition of a single candidate cell.

– UE maintains connection with source eNB until UE determines a CHO execution condition is met for CHO candidate cell.

– Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 10.1.2.1, regardless of any previously received CHO configuration.

– After source eNB sends CHO command to UE, the network is allowed to change source eNB configuration and network can add, modify or release a configured CHO configuration using RRC message (i.e. until UE starts executing CHO.

– While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell.

NOTE 1: CHO is not supported for S1 based handover in this release of the specification.

NOTE 2: In case LTE-DC is configured, CHO is only supported in MeNB to eNB change procedure in this release of the specification.

[TS 36.300, clause 10.1.2.1a.2]

The figure below depicts the CHO scenario where neither MME nor Serving Gateway changes:

Figure 10.1.2.1a-1: Intra-MME/Serving Gateway Conditional Handover

1. The source eNB configures the UE with measurement configuration, which may be used by the UE to trigger Measurement Reports for potential CHO candidate cell(s).

2. A MEASUREMENT REPORT is triggered and sent to the source eNB.

3. The source eNB makes decision on the usage of CHO to handoff the UE based on MEASUREMENT REPORT information.

4. The source eNB requests a CHO to the eNB(s) of candidate cell(s). A CHO request message is sent for each candidate cell.

5. Same as step 5 in Figure 10.1.2.1.1-1 of clause 10.1.2.1.1.

6. The eNB(s) of candidate cell(s) sends CHO response including configuration of CHO candidate cell(s) to the source eNB. The response message is also sent for each candidate cell.

7. The source eNB sends a RRCConnectionReconfiguration message to the UE, containing configuration of CHO candidate cell(s) and CHO execution condition(s). The source eNB decides on the condition for the execution of CHO and adds the condition(s) to the RRC message sent to the UE.

NOTE 1: The source eNB may reconfigure the UE’s source configuration after providing CHO configuration for candidate target cell(s).

NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover.

8. The UE sends an RRCConnectionReconfigurationComplete message to the source eNB.

8a. If early data forwarding is applied, the source eNB sends the EARLY STATUS TRANSFER message.

9. The UE maintains connection with the source eNB after receiving CHO configuration, and starts evaluating the CHO execution condition(s) for the CHO candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source eNB, applies the stored corresponding configuration for that candidate cell and synchronises to that candidate cell.

10-11. The UE accesses to the target eNB and completes the handover procedure by sending RRCConnectionReconfigurationComplete message to the target eNB. The UE releases the stored CHO configurations after successful completion of RRC handover procedure.

11a/b. The target eNB sends the HANDOVER SUCCESS message to the source eNB to inform that the UE has successfully accessed the target cell. In return, the source eNB sends the SN STATUS TRANSFER message.

NOTE 2: Late data forwarding may be initiated as soon as the source eNB receives the HANDOVER SUCCESS message.

11c. The source eNB sends the HANDOVER CANCEL message toward the other signalling connections or other potential target eNBs, if any, to cancel CHO for the UE.

12. Steps 12-18 as in Figure 10.1.2.1.1-1.

[TS 36.331, clause 5.3.7.3]

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

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> if the UE is connected to 5GC and the selected cell is only connected to EPC; or

1> if the UE is connected to EPC and the selected cell is only connected to 5GC:

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

1> else:

2> stop timer T311;

2> if the cell selection is triggered by detecting radio link failure of the MCG or handover failure (including intra-E-UTRA handover and mobility from E-UTRA); and

2> if attemptCondReconf is configured; and

2> if the selected cell is one of the target candidate cells in VarConditionalReconfiguration:

3> apply the stored condReconfigurationToApply of the selected cell and perform the actions as specified in 5.3.5.4;

2> else:

3> if the UE is configured with conditionalReconfiguration:

4> release uplinkDataCompression, if configured;

4> suspend all RBs, including RBs configured with NR PDCP, except SRB0;

4> reset MAC;

4> release the MCG SCell(s), if configured, in accordance with 5.3.10.3a;

4> release the SCell group(s), if configured, in accordance with 5.3.10.3d;

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

4> for the MCG, apply the default semi-persistent scheduling configuration as specified in 9.2.3;

4> for the MCG, apply the default MAC main configuration as specified in 9.2.2;

4> release powerPrefIndicationConfig, if configured and stop timer T340, if running;

4> release reportProximityConfig, if configured and clear any associated proximity status reporting timer;

4> release obtainLocationConfig, if configured;

4> release idc-Config, if configured;

4> release sps-AssistanceInfoReport, if configured;

4> release measSubframePatternPCell, if configured;

4> release the entire SCG configuration, if configured, except for the DRB configuration (as configured by drb-ToAddModListSCG);

4> if (NG)EN-DC is configured:

5> perform MR-DC release, as specified in TS 38.331[82], clause 5.3.5.10;

5> release p-MaxEUTRA, if configured;

5> release p-MaxUE-FR1, if configured;

5> release tdm-PatternConfig or tdm-PatternConfig2, if configured;

4> release naics-Info for the PCell, if configured;

4> if connected as an RN and configured with an RN subframe configuration:

5> release the RN subframe configuration;

4> release the LWA configuration, if configured, as described in 5.6.14.3;

4> release the LWIP configuration, if configured, as described in 5.6.17.3;

4> release delayBudgetReportingConfig, if configured and stop timer T342, if running;

4> release bw-PreferenceIndicationTimer, if configured and stop timer T341, if running;

4> release overheatingAssistanceConfig and overheatingAssistanceConfigForSCG, if configured and stop timer T345, if running;

4> release ailc-BitConfig, if configured;

3> remove all the entries within VarConditionalReconfiguration, if any;

3> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA configured:

4> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

4> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA:

5> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

4> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

3> start timer T301;

3> apply the timeAlignmentTimerCommon included in SystemInformationBlockType2;

3> if the UE is a NB-IoT UE connected to EPC, the UE supports RRC connection re-establishment for the Control Plane CIoT EPS optimisation and AS security has not been activated; and

3> if cp-reestablishment is not included in SystemInformationBlockType2-NB:

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

3> else:

4> 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 PCell.

[TS 36.331, clause 5.3.12]

Upon leaving RRC_CONNECTED or RRC_INACTIVE, the UE shall:

1> reset MAC;

1> if leaving RRC_CONNECTED was triggered by suspension of the RRC:

2> re-establish RLC entities for all SRBs and DRBs, including RBs configured with NR PDCP;

2> remove all entries within VarConditionalReconfiguration, if any;

2> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA configured:

3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

3> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA:

4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

NOTE 1: Except when resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18, ciphering is not applied for the subsequent RRCConnectionResume message used to resume the connection and an integrity check is performed by lower layers, but merely upon request from RRC.

1> else:

2> upon leaving RRC_INACTIVE:

3> discard the UE Inactive AS context;

3> discard the KeNB, the KRRCenc key, the KRRCint and the KUPenc key;

2> release rrc-InactiveConfig, if configured;

2> remove all entries within VarConditionalReconfiguration, if any;

2> for each measId, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA configured:

3> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig;

3> if the associated measObjectId is only associated with condReconfigurationTriggerEUTRA:

4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig;

3> remove the entry with the matching measId from the measIdList within the VarMeasConfig;

2> release all radio resources, including release of the MAC configuration, the RLC entity and the associated PDCP entity and SDAP (if any) for all established RBs, except for the following:

pur-Config, if stored;

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

8.2.4.31.4.3 Test description

8.2.4.31.4.3.1 Pre-test conditions

System Simulator:

– Cell 1, Cell 2 and Cell 4.

UE:

– None.

Preamble:

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

8.2.4.31.4.3.2 Test procedure sequence

Table 8.2.4.31.4.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" and "T2" are to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

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

Parameter

Unit

Cell 1

Cell 2

Cell 4

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-85

-113

-88

Power levels are such that UE registered on Cell 1

T1

Cell-specific RS EPRE

dBm/15kHz

-85

-79

-113

Power levels are such that entry condition for event A3 is satisfied for Cell 2

T2

Cell-specific RS EPRE

dBm/15kHz

-113

-113

-113

Power levels are such that all Srxlev Cell < 0

T3

Cell-specific RS EPRE

dBm/15kHz

-113

-79

-113

Power levels are such that entry condition for event A3 is satisfied for Cell 2

Table 8.2.4.31.4.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration on Cell 1 to set Cell 2 and Cell 4 as target candidate cells.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform legacy handover to Cell 4.

<–

RRCConnectionReconfiguration

4

Check: Does the UE transmit an RRCConnectionReconfigurationComplete message on Cell 4?

–>

RRCConnectionReconfigurationComplete

1

P

5

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration on Cell 4 to set Cell 2 as target candidate cell.

<–

RRCConnectionReconfiguration

6

The UE transmits an RRCConnectionReconfigurationComplete message to Cell 4.

–>

RRCConnectionReconfigurationComplete

7

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform legacy handover to Cell 1.

<–

RRCConnectionReconfiguration

EXCEPTION: In parallel to the events described in step 8 the steps specified in Table 8.2.4.31.4.3.2-3 should take place.

8

SS adjusts the cell-specific reference signal level according to row "T1".

9

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

–>

RRCConnectionReconfigurationComplete

2

P

10

The SS transmits an RRCConnectionReconfiguration message including conditionalReconfiguration on Cell 2 to set Cell 4 as target candidate cell.

<–

RRCConnectionReconfiguration

11

The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2.

–>

RRCConnectionReconfigurationComplete

12

The SS transmits an RRCConnectionReconfiguration message to order the UE to perform legacy handover to Cell 1.

<–

RRCConnectionReconfiguration

12A

SS adjusts the cell-specific reference signal level according to row "T2".

EXCEPTION: In parallel to the events described in step 13 the steps specified in Table 8.2.4.31.4.3.2-3 should take place.

13

SS wait 10s to make sure T304+T311 expire.

13A

The SS changes the TAC of Cell 2 to 2.

14

SS adjusts the cell-specific reference signal level according to row "T3".

15

Check: Does the generic test procedure specified in TS 36.508 subclause 6.4.2.7 take place on Cell 2?

3

Table 8.2.4.31.4.3.2-3: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

EXCEPTION: The steps 1 and 2 below are repeated for the duration of T304.

1

The UE attempts to perform the intra frequency handover using MAC Random Access Preamble on Cell 1.

2

The SS does not respond.

8.2.4.31.4.3.3 Specific message contents

Table 8.2.4.31.4.3.3-1: RRCConnectionReconfiguration (step 1, step 5, step 10, Table 8.2.4.31.4.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8 with condition CHO

Information Element

Value/remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

rrcConnectionReconfiguration-r8 SEQUENCE {

measConfig

MeasConfig

Table 8.2.4.31.4.3.3-2

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

conditionalReconfiguration-r16

ConditionalReconfiguration-r16-HO

Table 8.2.4.31.4.3.3-3

Step 1

ConditionalReconfiguration-r16-HO

Table 8.2.4.31.4.3.3-5

Step 5

ConditionalReconfiguration-r16-HO

Table 8.2.4.31.4.3.3-6

Step 10

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.2.4.31.4.3.3-2: MeasConfig (Table 8.2.4.31.4.3.3-1)

Derivation Path: 36.508, Table 4.6.6-1

Information Element

Value/remark

Comment

Condition

MeasConfig-DEFAULT ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

1 entry

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

1

reportConfig[1]

ReportConfigEUTRA-A3-CHO

Table 4.6.6-17 specified in TS 36.508

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f1

reportConfigId[1]

1

}

}

Table 8.2.4.31.4.3.3-3: ConditionalReconfiguration-r16-HO (Step 1, Table 8.2.4.31.4.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

2 entries

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

OCTET STRING (CONTAINING RRCConnectionReconfiguration with condition HO_to_Cell 2)

Table 8.2.4.31.4.3.3-4

}

CondReconfigurationAddMod-r16[2] SEQUENCE {

entry 2

condReconfigurationId-r16

2

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

OCTET STRING (CONTAINING RRCConnectionReconfiguration with condition HO_to_Cell 4)

Table 8.2.4.31.4.3.3-4

}

}

}

Table 8.2.4.31.4.3.3-4: RRCConnectionReconfiguration (Table 8.2.4.31.4.3.3-3)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Information Element

Value/Remark

Comment

Condition

RRCConnectionReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

rrcConnectionReconfiguration-r8 SEQUENCE {

mobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 1

HO_to_Cell 1

PhysicalCellIdentity of Cell 2

HO_to_Cell 2

PhysicalCellIdentity of Cell 4

HO_to_Cell 4

}

}

}

}

}

Table 8.2.4.31.4.3.3-5: ConditionalReconfiguration-r16-HO (Step 5, Table 8.2.4.31.4.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

OCTET STRING (CONTAINING RRCConnectionReconfiguration with condition HO_to_Cell 2)

Table 8.2.4.31.4.3.3-4

}

}

}

Table 8.2.4.31.4.3.3-6: ConditionalReconfiguration-r16-HO (Step 10, Table 8.2.4.31.4.3.3-1)

Derivation Path: 36.508, Table 4.6.5-2

Information Element

Value/remark

Comment

Condition

ConditionalReconfiguration-r16-HO ::= SEQUENCE {

condReconfigurationToAddModList-r16 SEQUENCE (SIZE (1..maxCondConfig-r16)) OF SEQUENCE {

1 entry

CondReconfigurationAddMod-r16[1] SEQUENCE {

entry 1

condReconfigurationId-r16

1

triggerCondition-r16 SEQUENCE (SIZE (1..2)) OF SEQUENCE {

1 entry

MeasId[1]

1

entry 1

}

condReconfigurationToApply-r16

OCTET STRING (CONTAINING RRCConnectionReconfiguration with condition HO_to_Cell 4)

Table 8.2.4.31.4.3.3-4

}

}

}

Table 8.2.4.31.4.3.3-7: SystemInformationBlockType1 for Cell 2 (step 13A, Table 8.2.4.31.4.3.2-2)

Derivation Path: 36.508 Table 4.4.3.2-3

Information Element

Value/remark

Comment

Condition

SystemInformationBlockType1 ::= SEQUENCE {

cellAccessRelatedInformation SEQUENCE {

trackingAreaCode

2

}

systemInfoValueTag

1

}

Table 8.2.4.31.4.3.3-8: RRCConnectionReconfiguration (step 3, step 7 and step 12, Table 8.2.4.31.4.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition HO

Table 8.2.4.31.4.3.3-9: MobilityControlInfo (Table 8.2.4.31.4.3.3-8)

Derivation Path: 36.508, Table 4.6.5-1

Information Element

Value/remark

Comment

Condition

MobilityControlInfo ::= SEQUENCE {

targetPhysCellId

PhysicalCellIdentity of Cell 4

Step 3

PhysicalCellIdentity of Cell 1

Step 7, step 12

carrierFreq SEQUENCE {

dl-CarrierFreq

Same downlink EARFCN as used for Cell 4

Step 3

Same downlink EARFCN as used for Cell 1

Step 7, step 12

}

}