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

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

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 K_eNB }

then { UE derives new K_eNB 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 K_eNB }

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

}

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

2> derive the K_RRCenc key and the K_UPenc 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 K_RRCint 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 K_RRCenc key and the K_UPenc 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 K_eNB?	–>	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	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;

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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

1> reset MAC;

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

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 K_eNB key based on the K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the K_ASME key to which the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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> 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 K_RRCint 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 K_eNB key based on the K_ASME key to which the current K_eNB 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 K_RRCint key associated with the previously configured integrity algorithm, as specified in TS 33.401 [32];

1> derive the K_RRCenc key and the K_UPenc 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 K_RRCint 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 K_RRCenc key and the K_UPenc 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;

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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> 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 K_eNB }

then { UE derives new K_eNB 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 K_eNB }

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

}

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;

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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> 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 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 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> store the nextHopChainingCount value;

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

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

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 K_eNBon 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 Srxlev_{Cell 1} > Srxlev_{Cell 2} and Srxlev_{Cell 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;

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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

1> reset MAC;

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

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 K_eNB key based on the current K_eNB 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 K_RRCint key associated with the current integrity algorithm, as specified in TS 33.401 [32];

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

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

1> reset MAC;

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

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 K_eNB key based on the fresh K_ASME key taken into use with the previous successful NAS SMC procedure, as specified in TS 33.401 [32];

1> else:

2> update the K_eNB key based on the current K_eNB 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 K_RRCint key associated with the integrityProtAlgorithm, as specified in TS 33.401 [32];

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

1> else:

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

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

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;