13.4.1 Intra-system mobility

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

13.4.1.1 Void

13.4.1.2 Inter-frequency mobility / E-UTRA to E-UTRA packet

13.4.1.2.1 Test Purpose (TP)

(1)

with { UE has a default EPS bearer context }

ensure that {

when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(2)

with { UE has a default EPS bearer context }

ensure that {

when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

(3)

with { UE has a default EPS bearer context and successful completion of the inter-frequency handover }

ensure that {

when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(4)

with { UE has a default EPS bearer context and successful completion of the inter-frequency handover }

ensure that {

when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

13.4.1.2.2 Conformance requirements

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

[TS 23.401, clause 5.5.1.1.1]

These procedures are used to hand over a UE from a source eNodeB to a target eNodeB using the X2 reference point. In these procedures the MME is unchanged. Two procedures are defined depending on whether the Serving GW is unchanged or is relocated. In addition to the X2 reference point between the source and target eNodeB, the procedures rely on the presence of S1-MME reference point between the MME and the source eNodeB as well as between the MME and the target eNodeB.

The handover preparation and execution phases are performed as specified in TS 36.300 [5].

If the serving PLMN changes during handover, the source eNB shall initiate an S1-based handover instead of an X2-based handover.

When the UE receives the handover command it will remove any EPS bearers for which it did not receive the corresponding EPS radio bearers in the target cell. As part of handover execution, downlink packets are forwarded from the source eNodeB to the target eNodeB. When the UE has arrived to the target eNodeB, downlink data forwarded from the source eNodeB can be sent to it. Uplink data from the UE can be delivered via the (source) Serving GW to the PDN GW. Only the handover completion phase is affected by a potential change of the Serving GW, the handover preparation and execution phases are identical.

If the MME receives a rejection to a NAS procedure (e.g. dedicated bearer establishment/modification/release; location reporting control; NAS message transfer; etc.) from the eNodeB with an indication that an X2 handover is in progress (see TS 36.300 [5]), the MME shall reattempt the same NAS procedure either when the handover is complete or the handover is deemed to have failed. The failure is known by expiry of the timer guarding the NAS procedure.

13.4.1.2.3 Test description

13.4.1.2.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 Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.4.1.2.3.2 Test procedure sequence

Table 13.4.1.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 13.4.1.2.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 13.4.1.2.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message	–	–
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 1?	–>	IP packet	1,2	P
3	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter frequency measurement and reporting for event A3.	<–	RRCConnectionReconfiguration	–	–
4	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
5	The SS changes Cell 3 parameters according to the row "T1" in table 13.4.1.2.3.2-1	–	–	–	–
6	The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 3.	–>	MeasurementReport	–	–
7	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 3.	<–	RRCConnectionReconfiguration	–	–
8	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 3 to confirm the successful completion of the inter frequency handover.	–>	RRCConnectionReconfigurationComplete	–	–
9	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 3.	<–	IP packet	–	–
10	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 3?	–>	IP packet	3,4	P

13.4.1.2.3.3 Specific message contents

Table 13.4.1.2.3.3-0: Conditions for specific message contents
in Tables 13.4.1.2.3.3-3 and 13.4.1.2.3.3-6

Condition	Explanation
Band > 64	If band > 64 is selected
Band 24 High range	If Band 24 high frequency range is selected for the target cell

Table 13.4.1.2.3.3-1: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 13.4.1.2.3.3-2: RRCConnectionReconfiguration (step 3, Table 13.4.1.2.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.1.2.3.3-3: MeasConfig (step 3, Table 13.4.1.2.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition INTER-FREQ
Information Element	Value/Remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModifyList 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
}
reportConfigToAddModifyList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfigEUTRA-A3
reportConfig[1]	ReportConfigEUTRA-A3
}
measIdToAddModifyList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f2
reportConfigId[1]	IdReportConfigEUTRA-A3
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {	2 entries		Band > 64
measObjectEUTRA-v9e0[2] ::= SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
measObjectEUTRA-v9e0[2] ::= SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f2
}
}
}

Table 13.4.1.2.3.3-4: MeasurementReport (step 6, Table 13.4.1.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId	1
measResultServCell SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {
measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {	1 entry
physCellId[1]	PhysicalCellIdentity of Cell 3
cgi-Info[1]	Not present
measResult[1] SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
}
}
}
}
}
}
}

Table 13.4.1.2.3.3-5: RRCConnectionReconfiguration (step 7, Table 13.4.1.2.3.2-2)

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

Table 13.4.1.2.3.3-6: MobilityControlInfo (step 7, Table 13.4.1.2.3.2-2)

Derivation Path: 36.508 clause 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	Not present		Band > 64
carrierFreq-v9e0 SEQUENCE {			Band > 64
dl-CarrierFreq-v9e0	Same downlink EARFCN as used for Cell 3
}
}

13.4.1.3 Intra-system mobility / E-UTRA FDD to E-UTRA TDD to E-UTRA FDD packet

13.4.1.3.1 Test Purpose (TP)

(1)

with { UE has a default EPS bearer context }

ensure that {

when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(2)

with { UE has a default EPS bearer context }

ensure that {

when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

(3)

with { UE has a default EPS bearer context and successful completion of the inter-frequency handover from E-UTRA FDD to E-UTRA TDD}

ensure that {

when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(4)

with { UE has a default EPS bearer context and successful completion of the inter-frequency handover from E-UTRA FDD to E-UTRA TDD }

ensure that {

when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

(5)

with { UE has a default EPS bearer context and successful completion of the inter-frequency handover from E-UTRA TDD to E-UTRA FDD}

ensure that {

when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(6)

with { UE has a default EPS bearer context and successful completion of the inter-frequency handover from E-UTRA TDD to E-UTRA FDD }

ensure that {

when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

13.4.1.3.2 Conformance requirements

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

[TS 23.401, clause 5.5.1.1.1]

The handover preparation and execution phases are performed as specified in TS 36.300 [5].

If the serving PLMN changes during handover, the source eNB shall initiate an S1-based handover instead of an X2-based handover.

13.4.1.3.3 Test description

13.4.1.3.3.1 Pre-test conditions

System Simulator:

– Cell 1 (E-UTRA FDD Cell)

– Cell 10 (E-UTRA TDD Cell)

– 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 Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.4.1.3.3.2 Test procedure sequence

Table 13.4.1.3.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" 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 13.4.1.3.3.2-1: Time instances of cell power level and parameter changes

	Parameter	Unit	Cell 1	Cell 10	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-97	The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy exit condition for event A3 (M10 < M1).
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-73	The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M10 > M1).
T2	Cell-specific RS EPRE	dBm/15kHz	-73	-85	The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M1 > M10).

Table 13.4.1.3.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message	–	–
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 1?	–>	IP packet	1,2	P
3	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter frequency measurement and reporting for event A3.	<–	RRCConnectionReconfiguration	–	–
4	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
5	The SS changes Cell 10 parameters according to the row "T1" in table 13.4.1.3.3.2-1	–	–	–	–
6	The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 10.	–>	MeasurementReport	–	–
7	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter frequency handover to Cell 10 and to activate the measurement gaps..	<–	RRCConnectionReconfiguration	–	–
8	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 10 to confirm the successful completion of the inter frequency handover.	–>	RRCConnectionReconfigurationComplete	–	–
9	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 10.	<–	IP packet	–	–
10	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 10?	–>	IP packet	3,4	P
11	The SS changes Cell 10 parameters according to the row "T2" in table 13.4.1.3.3.2-1	–	–	–	–
12	The UE transmits a MeasurementReport message on Cell 10 to report event A3 with the measured RSRP and RSRQ value for Cell 1.	–>	MeasurementReport	–	–
13	The SS transmits an RRCConnectionReconfiguration message on Cell 10 to order the UE to perform inter frequency handover to Cell 1.	<–	RRCConnectionReconfiguration	–	–
14	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1 to confirm the successful completion of the inter frequency handover.	–>	RRCConnectionReconfigurationComplete	–	–
15	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
16	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 1?	–>	IP packet	5,6	P

13.4.1.3.3.3 Specific message contents

Table 13.4.1.3.3.3-0: Conditions for specific message contents
in Tables 13.4.1.3.3.3-3, 13.4.1.3.3.3-7 and 13.4.1.2.3.3-10

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 13.4.1.3.3.3-1: ACTIVATE TEST MODE (preamble)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 13.4.1.3.3.3-2: RRCConnectionReconfiguration (step 3, Table 13.4.1.3.3.2-2)

Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 with condition MEAS

Table 13.4.1.3.3.3-3: MeasConfig (step 3, Table 13.4.1.3.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1 with condition INTER-FREQ
Information Element	Value/Remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	2 entries
measObjectId[1]	IdMeasObject-f5
measObject[1]	MeasObjectEUTRA-GENERIC(f5)
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
measObjectId[2]	IdMeasObject-f1
measObject[2]	MeasObjectEUTRA-GENERIC(f1)
measObject[2]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfigEUTRA-A3
reportConfig[1]	ReportConfigEUTRA-A3
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f5
reportConfigId[1]	IdReportConfigEUTRA-A3
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {			Band > 64
measObjectEUTRA-v9e0[1] ::= SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f5
}
measObjectEUTRA-v9e0[2] ::= SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
}
}

Table 13.4.1.3.3.3-4: MeasurementReport (step 6, Table 13.4.1.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-5
Information Element	Value/remark	Comment	Condition
MeasurementReport ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
measurementReport-r8 SEQUENCE {
measResults SEQUENCE {
measId	1
measResultServCell SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
measResultNeighCells CHOICE {
measResultListEUTRA SEQUENCE (SIZE (1..maxCellReport)) OF SEQUENCE {	1 entry
physCellId[1]	PhysicalCellIdentity of Cell 10
cgi-Info[1]	Not present
measResult[1] SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
}
}
}
}
}
}
}
}

Table 13.4.1.3.3.3-5: RRCConnectionReconfiguration (step 7, Table 13.4.1.3.3.2-2)

Derivation Path: 36.508 clause 4.6.1-8
Information Element	Value/remark	Comment	Condition
RRCConnectionReconfiguration ::= SEQUENCE {
criticalExtensions CHOICE {
c1 CHOICE{
rrcConnectionReconfiguration-r8 SEQUENCE {
measConfig	MeasConfig
mobilityControlInfo	MobilityControlInfo
}
}
}
}

Table 13.4.1.3.3.3-6: MeasConfig (step 7, Table 13.4.1.3.3.2-2)

Derivation path: 36.508 clause 4.6.6 table 4.6.6-1, condition INTER-FREQ

Table 13.4.1.3.3.3-7: MobilityControlInfo (step 7, Table 13.4.1.3.3.2-2)

Derivation Path: 36.508 clause 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
}
carrierFreq	Not present		Band > 64
carrierFreq-v9e0 SEQUENCE {			Band > 64
dl-CarrierFreq-v9e0	Same downlink EARFCN as used for Cell 10
}
}

Table 13.4.1.3.3.3-8: MeasurementReport (step 12, Table 13.4.1.3.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 13.4.1.3.3.3-9: RRCConnectionReconfiguration (step 13, Table 13.4.1.3.3.2-2)

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

Table 13.4.1.3.3.3-10: MobilityControlInfo (step 13, Table 13.4.1.3.3.2-2)

Derivation Path: 36.508 clause 4.6.5-1
Information Element	Value/remark	Comment	Condition
MobilityControlInfo ::= SEQUENCE {
targetPhysCellId	PhysicalCellIdentity of Cell 1
carrierFreq SEQUENCE {
dl-CarrierFreq	Same downlink EARFCN as used for Cell 1
ul-CarrierFreq	Not present
	Same uplink EARFCN as used for Cell 1		Band 24 High range
}
carrierFreq	Not present		Band > 64
carrierFreq-v9e0 SEQUENCE {			Band > 64
dl-CarrierFreq-v9e0	Same downlink EARFCN as used for Cell 1
}
}

13.4.1.4 Inter-band mobility / E-UTRA to E-UTRA packet

13.4.1.4.1 Test Purpose (TP)

(1)

with { UE has a default EPS bearer context }

ensure that {
when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(2)

with { UE has a default EPS bearer context }

ensure that {
when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

(3)

with { UE has a default EPS bearer context and successful completion of the inter-band handover }

ensure that {
when { UE receives downlink data on the radio bearer associated with the default EPS bearer context }

then { UE delivers the downlink data to upper layers }

}

(4)

with { UE has a default EPS bearer context and successful completion of the inter-band handover }

ensure that {
when { uplink data are submitted for transmission }

then { UE transmits the uplink data on the radio bearer associated with the default EPS bearer context }

}

13.4.1.4.2 Conformance requirements

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

[TS 23.401, clause 5.5.1.1.1]

The handover preparation and execution phases are performed as specified in TS 36.300 [5]. If emergency bearer services are ongoing for the UE handover to the target eNodeB is performed independent of the Handover Restriction List. The MME checks, as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3.

If the serving PLMN changes during X2-based handover, the source eNodeB shall indicate to the target eNodeB (in the Handover Restriction List) the PLMN selected to be the new Serving PLMN.

When the UE receives the handover command it will remove any EPS bearers for which it did not receive the corresponding EPS radio bearers in the target cell. As part of handover execution, downlink and optionally also uplink packets are forwarded from the source eNodeB to the target eNodeB. When the UE has arrived to the target eNodeB, downlink data forwarded from the source eNodeB can be sent to it. Uplink data from the UE can be delivered via the (source) Serving GW to the PDN GW or optionally forwarded from the source eNodeB to the target eNodeB. Only the handover completion phase is affected by a potential change of the Serving GW, the handover preparation and execution phases are identical.

If the MME receives a rejection to a NAS procedure (e.g. dedicated bearer establishment/modification/release; location reporting control; NAS message transfer; etc.) from the eNodeB with an indication that an X2 handover is in progress (see TS 36.300 [5]), the MME shall reattempt the same NAS procedure either when the handover is complete or the handover is deemed to have failed, except in the case of Serving GW relocation. The failure is known by expiry of the timer guarding the NAS procedure.

13.4.1.4.3 Test description

13.4.1.4.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 Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.4.1.4.3.2 Test procedure sequence

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

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

	Parameter	Unit	Cell 1	Cell 10	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-97	The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy exit condition for event A3 (M10 < M1).
T1	Cell-specific RS EPRE	dBm/15kHz	-85	-73	The power level values are such that measurement results for Cell 1 (M1) and Cell 10 (M10) satisfy entry condition for event A3 (M10 > M1).

Table 13.4.1.4.3.2-2: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 1?	–>	IP packet	1,2	P
3	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to setup inter-band measurement and reporting for event A3.	<–	RRCConnectionReconfiguration	–	–
4	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 1.	–>	RRCConnectionReconfigurationComplete	–	–
5	The SS changes Cell 10 parameter according to the row "T1" in table 13.4.1.4.3.2-1	–	–	–	–
6	The UE transmits a MeasurementReport message on Cell 1 to report event A3 with the measured RSRP and RSRQ value for Cell 10.	–>	MeasurementReport	–	–
7	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform inter-band handover to Cell 10.	<–	RRCConnectionReconfiguration	–	–
8	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 10 to confirm the successful completion of the inter-band handover.	–>	RRCConnectionReconfigurationComplete	–	–
9	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 10.	<–	IP packet	–	–
10	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 10?	–>	IP packet	3,4	P

13.4.1.4.3.3 Specific message contents

Table 13.4.1.4.3.3-0: Conditions for specific message contents
in Tables 13.4.1.4.3.3-2 and 13.4.1.4.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 13.4.1.4.3.3-1: RRCConnectionReconfiguration (step 3, Table 13.4.1.4.3.2-2)

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

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

Derivation Path: 36.508, Table 4.6.6-1, condition INTER-FREQ
Information Element	Value/remark	Comment	Condition
MeasConfig ::= SEQUENCE {
measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {	2 entries
measObjectId[1]	IdMeasObject-f1
measObject[1]	MeasObjectEUTRA-GENERIC(f1)
measObject[1]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
measObjectId[2]	IdMeasObject-f5
measObject[2]	MeasObjectEUTRA-GENERIC(f5)
measObject[2]	MeasObjectEUTRA-GENERIC(maxEARFCN)		Band > 64
}
reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {	1 entry
reportConfigId[1]	IdReportConfig-A3
reportConfig[1]	ReportConfigEUTRA-A3
}
measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {	1 entry
measId[1]	1
measObjectId[1]	IdMeasObject-f5
reportConfigId[1]	IdReportConfig-A3
}
measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {	2 entries		Band > 64
measObjectEUTRA-v9e0[1] ::= SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f1
}
measObjectEUTRA-v9e0[2] ::= SEQUENCE {
carrierFreq-v9e0	Same downlink EARFCN as used for f5
}
}
}

Table 13.4.1.4.3.3-3: MeasurementReport (step 6, Table 13.4.1.4.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	PhysicalCellIdentity of Cell 10
cgi-Info	Not present
measResult SEQUENCE {
rsrpResult	(0..97)
rsrqResult	(0..34)
additionalSI-Info-r9	Not present
}
}
}
measResultForECID-r9	Not present
}
}
}
}
}

Table 13.4.1.4.3.3-4: RRCConnectionReconfiguration (step 7, Table 13.4.1.4.3.2-2)

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

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

Derivation Path: 36.508, Table 4.6.5-1
Information Element	Value/remark	Comment	Condition
MobilityControlInfo ::= SEQUENCE {
targetPhysCellId	PhysicalCellIdentity of Cell 10
carrierFreq SEQUENCE {
dl-CarrierFreq	Same downlink EARFCN as used for Cell 10
ul-CarrierFreq	Not present
	Same uplink EARFCN as used for Cell 10		Band 24 High range
}
carrierFreq	Not present		Band > 64
carrierFreq-v9e0 SEQUENCE {			Band > 64
dl-CarrierFreq-v9e0	Same downlink EARFCN as used for Cell 10
}
}

13.4.1.5 RRC connection reconfiguration / Handover/ Full configuration / DRB establishment

13.4.1.5.1 Test Purpose (TP)

(1)

with { UE in E-UTRA RRC_CONNECTED state and has data transmit }

ensure that {
when { UE receives an RRCConnectionReconfiguration message including mobilityControlInfo and fullConfig-r9 }

then { UE release and re-setup DRB and resume data transfer }

}

13.4.1.5.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.3.5.4 and 5.3.5.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> else:

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

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

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

1> reset MAC;

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

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

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

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

1> if the RRCConnectionReconfiguration message includes the fullConfig:

2> perform the radio configuration procedure as specified in section 5.3.5.8;

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

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

1> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated:

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

…

1> 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> 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> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

1> if MAC successfully completes the random access procedure:

2> stop timer T304;

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

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

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

2> the procedure ends;

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

[TS 36.331, clause 5.3.5.8]

The UE shall:

1> release/ clear all current dedicated radio configurations except the C-RNTI, the security configuration and the PDCP, RLC and logical channel configurations for the RBs;

NOTE 1: Radio configuration is not just the resource configuration but includes other configurations like MeasConfig and OtherConfig.

1> if the RRCConnectionReconfiguration message includes the mobilityControlInfo:

2> release/ clear all current common radio configurations;

2> use the default values specified in 9.2.5 for timer T310, T311 and constant N310, N311;

1> else:

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

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> for each srb-Identity value included in the srb-ToAddModList (SRB reconfiguration):

2> apply the specified configuration defined in 9.1.2 for the corresponding SRB;

2> apply the corresponding default RLC configuration for the SRB specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;

2> apply the corresponding default logical channel configuration for the SRB as specified in 9.2.1.1 for SRB1 or in 9.2.1.2 for SRB2;

NOTE 2: This is to get the SRBs (SRB1 and SRB2 for handover and SRB2 for reconfiguration after reestablishment) to a known state from which the reconfiguration message can do further configuration.

1> for each eps-BearerIdentity value included in the drb-ToAddModList that is part of the current UE configuration:

2> release the PDCP entity;

2> release the RLC entity or entities;

2> release the DTCH logical channel;

2> release the drb-identity;

NOTE 3: This will retain the eps-bearerIdentity but remove the DRBs including drb-identity of these bearers from the current UE configuration and trigger the setup of the DRBs within the AS in Section 5.3.10.3 using the new configuration. The eps-bearerIdentity acts as the anchor for associating the released and re-setup DRB.

1> for each eps-BearerIdentity value that is part of the current UE configuration but not part of the drb-ToAddModList:

2> perform DRB release as specified in 5.3.10.2;

13.4.1.5.3 Test description

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

– The condition SRB2-DRB(1, 0) is used for step 8 in 4.5.3A.3 on Cell 1 according to [18].

– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18] using the UE TEST LOOP MODE B.

13.4.1.5.3.2 Test procedure sequence

Table 13.4.1.5.3.2-0 illustrates the downlink power levels and other changing parameters to be applied for the cells during test execution as of time instant "T0", which denotes the initial conditions after preamble.

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

	Parameter	Unit	Cell 1	Cell 2	Remark
T0	Cell-specific RS EPRE	dBm/15kHz	-85	-73

Table 13.4.1.5.3.2-1: Main behaviour

St	Procedure	Message Sequence		TP	Verdict
		U – S	Message
1	The SS transmits one IP packet to the UE on the DRB associated with the default EPS bearer context on Cell 1.	<–	IP packet	–	–
2	The SS transmits an RRCConnectionReconfiguration message on Cell 1 to order the UE to perform handover with full configuration option to Cell 2.	<–	RRCConnectionReconfiguration	–	–
3	The UE transmits an RRCConnectionReconfigurationComplete message on Cell 2.	–>	RRCConnectionReconfigurationComplete	–	–
4	Check: Does the UE loop back the IP packet on the DRB associated with the default EPS bearer context on Cell 2?	–>	IP packet	1	P

13.4.1.5.3.3 Specific message contents

Table 13.4.1.5.3.3-1: ACTIVATE TEST MODE (preamble, Table 13.4.1.5.3.2-1)

Derivation Path: 36.508, Table 4.7A-1, condition UE TEST LOOP MODE B

Table 13.4.1.5.3.3-2: CLOSE UE TEST LOOP (preamble, Table 13.4.1.5.3.2-1)

Derivation Path: 36.508, Table 4.7A-3, condition UE TEST LOOP MODE B
Information Element	Value/remark	Comment	Condition
UE test loop mode B LB setup
IP PDU delay	00000101	5 seconds

Table 13.4.1.5.3.3-3: RRCConnectionReconfiguration (step 2, Table 13.4.1.5.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 {
radioResourceConfigDedicated	RadioResourceConfigDedicated-RECONFIG
nonCriticalExtension SEQUENCE {
lateNonCriticalExtension	Not present
nonCriticalExtension SEQUENCE {
otherConfig-r9	Not present
fullConfig-r9	true
nonCriticalExtension SEQUENCE {			CEmodeA CEmodeB
sCellToReleaseList-r10	Not present
sCellToAddModList-r10	NotPresent
nonCriticalExtension ::= SEQUENCE {
systemInformationBlockType1Dedicated-r11	SystemInformationBlockType1-BR-r13 of Cell 2
nonCriticalExtension	NotPresent
}
}
}
}
}
}
}
}

Table 13.4.1.5.3.3-4: MobilityControlInfo (Table 13.4.1.5.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 SEQUENCE {
dl-CarrierFreq	Same downlink EARFCN as used for Cell 2
ul-CarrierFreq	Not present
	Same uplink EARFCN as used for Cell 2		Band 24 High range
}
carrierFreq	Not present		Band > 64
radioResourceConfigCommon	RadioResourceConfigCommon-DEFAULT
carrierFreq-v9e0 SEQUENCE {			Band > 64
dl-CarrierFreq-v9e0	Same downlink EARFCN as used for Cell 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 13.4.1.5.3.3-5: RadioResourceConfigCommon-DEFAULT (Table 13.4.1.5.3.3-4)

Derivation Path: 36.508 table 4.6.3-13 with condition FullConfig

Table 13.4.1.5.3.3-6: SecurityConfigHO (Table 13.4.1.5.3.3-3)

Derivation Path: 36.508, Table 4.6.4-1
Information Element	Value/remark	Comment	Condition
SecurityConfigHO ::= SEQUENCE {
handoverType CHOICE {
intraLTE SEQUENCE {
securityAlgorithmConfig	SecurityConfigSMC-DEFAULT	TS 36.508, Table 4.6.4-2
}
}
}

Table 13.4.1.5.3.3-7: RadioResourceConfigDedicated-RECONFIG (Table 13.4.1.5.3.3-3)

Derivation Path: 36.331 clause 6.3.2
Information Element	Value/remark	Comment	Condition
RadioResourceConfigDedicated ::= SEQUENCE {
srb-ToAddModList	SRB-ToAddModList-DEFAULT	TS 36.508 Table 4.8.2.1.1-1
drb-ToAddModList	DRB-ToAddModList-DEFAULT (1) using condition AM	TS 36.508 Table 4.8.2.1.7-1
drb-ToReleaseList	Not present
mac-MainConfig CHOICE {
explicitValue	MAC-MainConfig-DEFAULT
}
sps-Config	Not present
physicalConfigDedicated	PhysicalConfigDedicated-DEFAULT		HO-TO-EUTRA
}

Table 13.4.1.5.3.3-8: MAC-MainConfig-DEFAULT (Table 13.4.1.5.3.3-6)

Derivation Path: 36.508 table 4.8.2.1.5-1
Information Element	Value/remark	Comment	Condition
MAC-MainConfig ::= SEQUENCE {
ul-SCH-Config SEQUENCE {
periodicBSR-Timer	infinity
retxBSR-Timer	sf2560
}
drx-Config	Not present
phr-Config CHOICE {
release	NULL
}
sr-ProhibitTimer-r9	0
}