OMD - LTE TDD HandoverFault Diagnosis Guide-20130325-A-3.0

LTE TDD
Handover Fault Diagnosis Guide
Issue 3.0
Date 2013-03-25
INTERNAL
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: support@huawei.com
Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
LTE TDD
Handover Performance Fault Diagnosis Guide About This Document
About This Document
Author
Prepared By Tao Yichen (employee ID: Date 2013-03-25
00181483)
Reviewed By Date
Reviewed By Date
Approved By Date
Change History
Date Issue Description Author
2011-06-30 1.0 Completed the draft.
2012-02-06 1.1 Added the principles for Tao Yichen
inter-frequency and intra-frequency (employee ID:
handovers. 00181483)
2012-10-25 1.2  Changed the screen images in the Wu Liting
document in Chinese. (employee ID:
00134378)
 Added the note that the M2000
mentioned in this document is
equivalent to the DOMC920 in
China to this document.
2013-03-25 3.0 Updated some descriptions. Tao Yichen
(employee ID:
00181483)
Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential ii

LTE TDD
Handover Performance Fault Diagnosis Guide Contents
Contents
About This Document .................................................................................................................... ii
1 Disclaimer Statement ................................................................................................................... 1
2 Overview......................................................................................................................................... 2
3 Principles ........................................................................................................................................ 3
3.1 Handover-related Parameters ........................................................................................................................... 4
3.1.1 Handover Thresholds .............................................................................................................................. 4
3.2 Intra-Frequency Handover ............................................................................................................................... 5
3.2.1 Signaling Exchange for Intra-eNodeB Handovers .................................................................................. 7
3.2.2 Signaling Exchange for X2-based Inter-eNodeB Handovers .................................................................. 8
3.2.3 Signaling Exchange for S1-based Inter-eNodeB Handovers .................................................................. 9

3.3 Inter-Frequency and Inter-RAT Handovers .................................................................................................... 10
3.3.1 Inter-Frequency Handover .................................................................................................................... 10
3.3.2 Inter-RAT Handover.............................................................................................................................. 12
3.3.3 Parameter Settings ................................................................................................................................ 13
3.4 Signaling Exchange on the User Plane ........................................................................................................... 16
4 KPIs ................................................................................................................................................ 17
4.1 Handover Success Rate .................................................................................................................................. 17
4.2 Handover Delay on the Control Plane ............................................................................................................ 17
4.3 Handover Interruption Delay on the User Plane ............................................................................................ 18
4.3.1 Uplink Handover Interruption Delay at the Application Layer ............................................................. 19
4.3.2 Downlink Handover Interruption Delay at the Application Layer ........................................................ 19
4.3.3 Uplink Handover Interruption Delay at the RLC Layer on the eNodeB ............................................... 19
4.3.4 Downlink Handover Interruption Delay at the RLC Layer on the eNodeB .......................................... 19
4.3.5 Uplink Handover Interruption Delay at the RLC Layer on the UE....................................................... 20
Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential iii

LTE TDD
4.3.6 Downlink Handover Interruption Delay at the RLC Layer on the UE .................................................. 20
5 Methods for Locating Common Faults ................................................................................... 21

5.1 Locating Handover Failures ........................................................................................................................... 21
5.1.1 Locating Signaling Faults over the Uu Interface................................................................................... 21
5.1.2 Signaling Faults over the X2 Interface .................................................................................................. 24
5.1.3 Signaling Faults over the S1 Interface .................................................................................................. 25

5.2 Locating Handover Delay Faults .................................................................................................................... 29
5.2.1 Locating Handover Delay Faults on the Control Plane ......................................................................... 29
5.2.2 Locating Handover Delay Faults on the User Plane ............................................................................. 29
6 Fault Locating Procedure ........................................................................................................... 31

6.1 Signaling Tracing ........................................................................................................................................... 31
6.1.1 Signaling Tracing on the eNodeB ......................................................................................................... 31
6.1.2 Signaling Tracing on the UE ................................................................................................................. 32
6.1.3 Identification of Handover Messages .................................................................................................... 33

6.2 Measuring the Handover Delay on the User Plane ......................................................................................... 35
6.2.1 Measuring the Handover Delay at the IP Application Layer ................................................................. 35
6.2.2 Measuring the Handover Delay at the RLC Layer ................................................................................ 36
6.3 Recommended Solutions ................................................................................................................................ 38
7 Typical Cases ............................................................................................................................... 39

7.1 Handover Failures .......................................................................................................................................... 42
7.1.1 UEs Cannot Receive a Handover Command after Multiple Measurement Reports Is Sent. ................. 42
7.1.2 Random Access Fails. ........................................................................................................................... 43
7.1.3 Messages Cannot Be Parsed Due to Inappropriate Ciphering and Integrity Configurations. ............... 44
7.1.4 Handover Commands Are Lost. ............................................................................................................ 45
7.1.5 The Distance Between UE Position and the Target Cell Exceeds the Maximum Theoretical Access
Radius Mapped to the Ncs Index. .................................................................................................................. 46
7.1.6 A Smaller Time to Trigger Is Used When the RSRP of the Source and Target Cells Is High. .............. 47
7.1.7 The Number of Ping-pong Handovers Increases and the Handover Success Rate Improves after the
Handover Threshold Is Set to a Smaller Value. .............................................................................................. 52
7.2 Large Handover Delay on the User Plane ...................................................................................................... 52
7.2.1 The Handover Delay Increases Due to Inappropriate X2 IPPATH Settings. ......................................... 52
7.2.2 The Handover Delay Increases Due to Inappropriate X2 IPPATH Settings. ......................................... 53
7.2.3 The Handover Delay Increases Due to Consecutive Error CRC Packets in the Source Cell. ............... 53
Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential iv

LTE TDD
7.2.4 The Handover Delay Increases Due to Preamble Retransmissions During Random Access. ............... 54
7.2.5 The UE Does Not Send the PDCP Status Report Or Sends the PDCP Status Report with Delay. ........ 56
7.2.6 The System Information Update Conflicts with Handover Command Processing on the UE. ............. 57
A Acronyms and Abbreviations .................................................................................................. 58
Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential v

LTE TDD
Handover Performance Fault Diagnosis Guide 1 Disclaimer Statement
1 Disclaimer Statement
This document can be used to quickly locate and resolve problems. Normally there is no way
to avoid that some user data such as Internet Protocol (IP) addresses will be used during the
troubleshooting. You are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the
personal data of users is fully protected.
Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 1

LTE TDD
Handover Performance Fault Diagnosis Guide 2 Overview
2 Overview
Mobility management is crucial in wireless communications. The access network must

monitor user equipment (UE) mobility between cells and hands over a UE at a proper
occasion to maintain service connectivity. During a handover, the access network and a UE
exchange signaling with each other to ensure quick service recovery. Long Term Evolution
(LTE) systems support only hard handovers, during which services are temporarily interrupted.
Therefore, the handover success rate, handover delay, and handover throughput must be
ensured to maintain user service connectivity. Deterioration of these key performance
indicators (KPIs), especially the handover success rate, affects user experience.
Various faults may occur during a handover. This document provides the methods for locating
handover faults based on associated experience.

LTE TDD
Handover Performance Fault Diagnosis Guide 3 Principles
3 Principles
A handover is a process in which the connection between a UE and the network changes due
to UE mobility, as shown in Figure 3-1 and Figure 3-2.
Figure 3-1 UE connected to the eNodeB on the left before a handover is performed
Figure 3-2 UE connected to the eNodeB on the right after a handover is complete
In LTE systems, E-UTRAN NodeBs (eNodeBs) control the entire handover process and
monitor UE behaviors. UEs are handed over when they are located in handover areas and
there are cells whose propagation conditions are better than that of the serving cell.
E-UTRAN is short for evolved universal terrestrial radio access network.

LTE TDD
An eNodeB obtains information about UE positions and radio propagation conditions based
on UE reports. A UE can report the information in periodic reporting mode and event
triggering mode. Huawei eNodeB supports event measurement reporting mode. When an
eNodeB receives a measurement or handover report, it delivers a handover command to hand
over the associated UE.
3.1 Handover-related Parameters

To ensure that handovers can be implemented accurately and timely, the eNodeB controls
handover triggering conditions using parameters. In Huawei handover algorithms, handovers
are triggered by the following events:
 Intra-frequency handovers: event A3

 Inter-frequency handovers: events A1-A2 and A3-A4-A5
 Inter-RAT handovers: events A1-A2 and B1-B2
There are three common parameters related to handovers: handover threshold, delay
triggering time, and cell individual offset (CIO).
3.1.1 Handover Thresholds

In Huawei LTE systems, intra-frequency handovers are triggered by event A3, which is
reported in event-triggered periodical reporting mode. Event A3 is triggered when a
neighboring cell has better channel quality than the serving cell. 3GPP TS 36.331 defines the
entering and leaving conditions of event A3 as follows:
 Entering condition: Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off

 Leaving condition: Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off
For inter-frequency handovers, event A1 or A2 is used to trigger inter-frequency or inter-RAT

measurement, and event A3, A4, or A5 is used to trigger handover decision-making. The
event for triggering handovers can be configured on the eNodeB.
3GPP TS 36.331 defines the entering and leaving conditions of event A3 as follows:
 Entering condition: Mn + Ofn + Ocn – Hys > Thresh

 Leaving condition: Mn + Ofn + Ocn + Hys < Thresh
NOTE
For the entering and leaving conditions of event A5, see 3GPP TS 36.331.
Inter-RAT handovers are triggered by event B1 and B2.

LTE TDD
3GPP TS 36.331 defines the entering and leaving conditions of event B1 as follows:
 Entering condition: Mn + Ofn – Hys > Thresh

 Leaving condition: Mn + Ofn + Hys < Thresh
3GPP TS 36.331 defines the entering and leaving conditions of event B2 as follows:
 Entering condition: Ms + Hys < Thresh1 and Mn + Ofn + Ocn – Hys > Thresh2
 Leaving condition: Ms – Hys > Thresh1 or Mn + Ofn + Ocn + Hys < Thresh2
The variables in the previous formulas are defined as follows:
 Mn is the measurement result of the neighboring cell.

 Ofn is the frequency-specific offset of the neighboring frequency. Its default value is 0. It
can be ignored for intra-frequency handovers.
 Ocn is the cell-specific offset for the neighboring cell. It is specified by the
CellIndividualOffset parameter. In most cases, this parameter is used to advance or
postpone handovers. It is delivered in measurement control messages only when its value
is not 0.
 Ms is the measurement result of the serving cell.
 Ofn is the frequency-specific offset of the neighboring frequency. Its devalue value is 0.
It can be ignored for intra-frequency handovers.
 Ocs is the cell-specific offset for the serving cell. In most cases, its value is 0.
 Hys is an event hysteresis parameter. It is delivered in measurement control messages.
 Off is an event offset parameter. This parameter is used to adjust the probability for
triggering a handover. The value of this parameter plus the measurement result is used to
assess event entering and leaving conditions. This parameter is delivered in measurement
control messages. Its value can be negative or positive. A positive value of this parameter
results in a low probability for triggering event A3 and therefore a low probability for
triggering handovers. A negative value of this parameter leads to a high probability for
triggering event A3 and therefore a high probability of handovers.
3.2 Intra-Frequency Handover

During an intra-frequency handover, the UE and the eNodeB exchange signaling as follows:
1. The source eNodeB sends an RRC CONNECT RECONFIG message to the UE over the
Uu interface. After receiving this message, the UE sends a response indicating that this
message has been successfully received and processed.
2. The UE responds with an RRC CONNECT RECONFIG CMP message over the Uu
interface. Then, the UE performs measurements in a timely manner based on the
measurement control requirements.
3. The UE sends a MeasurementReport message to the source eNodeB over the Uu
interface.

LTE TDD
The source eNodeB determines whether to initiate a handover based on the received
MeasurementReport message.
4. The source and target eNodeBs prepare for a handover. Different handover messages are
exchanged for different handover scenarios:
− For intra-eNodeB handovers, no external signaling exchange is required.
− For X2-based handovers, HANDOVER REQUEST and HANDOVER REQUEST
ACK are exchanged over the X2 interface.
− For inter-eNodeB handovers over the S1 interface, HANDOVER REQUIRED and
HANDVER COMMAND messages are associated with the source eNodeB over the
S1 interface, and HANDOVER REQUEST and HANDOVER REQ ACK messages
are associated with the target eNodeB over the S1 interface.
5. The source eNodeB sends an RRC CONNECT RECONFIG message over the Uu
interface.
After receiving this message, the UE is disconnected from the source cell and attempts to
enter the target cell.
6. The UE sends an RRC CONNECT RECONFIG CMP message (MSG3) to the target
cell.
S1-based handovers do not involve the Uu interface and its success rate is high. Therefore,
fault locating is rarely required.
RRC CONNECT RECONFIG and RRC CONNECT RECONFIG messages are used both in
measurement control and in handovers. However, they have different contents in these
scenarios.
Figure 3-3 Handover command reconfiguration message

LTE TDD
Figure 3-4 Measurement control reconfiguration message
Measurement control information is configured after a UE enters the network, regardless of

its position and handover status. In most cases, handover faults occur after measurement
reporting is triggered. Therefore, fault locating must begin from the triggering of
measurement reporting.
Signaling exchange varies with handover types. Intra-LTE handovers are classified into
intra-eNodeB handovers and inter-eNodeB handovers. Inter-eNodeB handovers are
subcategorized into X2-based handovers and S1-based handovers.
3.2.1 Signaling Exchange for Intra-eNodeB Handovers

Figure 3-5 shows signaling exchange between a UE and an eNodeB during an intra-eNodeB
handover.

LTE TDD
Figure 3-5 Signaling exchange between a UE and an eNodeB during an intra-eNodeB handover
3.2.2 Signaling Exchange for X2-based Inter-eNodeB Handovers

Figure 3-6 shows signaling exchange during an X2-based inter-eNodeB handover.

LTE TDD
Figure 3-6 Signaling exchange during an X2-based inter-eNodeB handover
UE S_eNB T_eNB Core Network
Meas_RPRT
Handover_Request
Handover_Request ACK
RRC_CONN_RE
CFG SN_STATUS_TRANS
(HO_CMD) FER
RRC_CONN_RECFG_CMP
(HO_CMP) S1AP_PATH_SWITCH_REQ
S1AP_PATH_SWITCH_REQ_ACK
UE_CONTEXT_RELEASE
RRC_CONN_RECFG
RRC_CONN_RECFG_CMP
UU_interface X2_interface S1_interface
3.2.3 Signaling Exchange for S1-based Inter-eNodeB Handovers

Figure 3-7 shows signaling exchange during an S1-based inter-eNodeB handover.

LTE TDD
Figure 3-7 Signaling exchange during an S1-based inter-eNodeB handover

Meas_RPRT
S1AP_Handover_Required
S1AP_Handover_Request
S1AP_Handover_REQ_ACK
S1AP_Handover_CMD
RRC_CONN_RECFG
(HO_CMD) S1AP_eNB_Status_Transfer
S1AP_MME_Status_Transfer
RRC_CONN_RECFG_CMP
(HO_CMP) S1AP_Handover_Notify
S1AP_UE_CONTEXT_REL_CMD
S1AP_UE_CONTEXT_REL_CMP
RRC_CONN_RECFG
RRC_CONN_RECFG_CMP
3.3 Inter-Frequency and Inter-RAT Handovers
3.3.1 Inter-Frequency Handover

Inter-frequency handovers indicate that UEs are handed over between inter-frequency cells in
LTE networks. Different areas in a network can use different frequencies, and therefore an
eNodeB must support inter-frequency handovers.
The following principles apply when the serving cell is configured with an inter-frequency
neighboring cell:
 Coverage-based inter-frequency measurements are initiated by UEs. A coverage-based

inter-frequency measurement is triggered when a UE detects that the signal quality of the
serving cell is lower than the specified threshold.
 Load-based inter-frequency measurements are initiated by eNodeBs. When the load level
of the serving cell reaches the inter-frequency load balancing threshold, an eNodeB
selects a certain number of UEs for inter-frequency measurements based on UE
capabilities, Address Resolution Protocol (ARP) configurations, and resource situations.
For details about ARP, see 3GPP TS 23.401.
 Frequency priority-based inter-frequency handovers are supported only in concentric
networks where the high-priority cell and lower priority cell are configured with 2600
MHz and 900 MHz frequencies in the downlink and uplink, respectively. A frequency

LTE TDD
priority-based handover is initiated when a UE detects that the signal quality is higher
than a specified threshold in a concentric network.
 Before a distance-based handover is performed, an eNodeB estimates its distance to a
UE based on the timing advance (TA) reported by the UE. When the reported TA
exceeds the specified threshold, the eNodeB instructs the UE to perform a distance-based
inter-frequency measurement. Target measurement object types must be specified for
distance-based inter-frequency handovers. A distance-based inter-frequency handover
can be performed only when the DistBasedMeasObjType parameter is set to EUTRAN.
 Service-based inter-frequency measurements are initiated by eNodeBs. eNodeBs identify
the types of services run by UEs, and instruct the UEs to perform service-based
inter-frequency measurements based on service-specific frequencies.
 Uplink quality-based inter-frequency measurements are initiated by eNodeBs. An
eNodeB instructs a UE to perform an uplink quality-based inter-frequency measurement
when detecting the UE's limited uplink quality.
If a UE reports to an eNodeB that the signal quality of a neighboring cell is higher than the
specified handover threshold, the eNodeB initiates the associated inter-frequency handover.
The inter-frequency handover procedure is similar to the intra-frequency handover procedure,
except that the UE must stop data exchange with the source cell to start inter-frequency
measurements within a measurement gap in an inter-frequency handover procedure.
Figure 3-8 Intra-frequency handover procedure

LTE TDD
3.3.2 Inter-RAT Handover

Inter-RAT handovers allows eNodeBs to hand over UEs from E-UTRAN cells to the cells of
GSM, WCDMA, TD-SCDMA, and CDMA2000 systems to ensure service continuity when
the UEs move between different areas.
NOTE
 GSM: Global System for Mobile Communications
 WCDMA: Wideband Code Division Multiple Access
 TD-SCDMA: Time Division-Synchronous Code Division Multiple Access
The following principles apply when the serving cell is configured with an inter-RAT
neighboring cell:
 Coverage-based inter-RAT measurements are initiated by UEs. A coverage-based

inter-RAT measurement is triggered when a UE moves from the coverage area of the
serving cell to the coverage area of an inter-RAT neighboring cell and detects that the
signal quality of the serving cell is lower than the specified threshold.
 Load-based inter-RAT measurements are initiated by eNodeBs. When the load level of
the serving cell reaches the inter-RAT load balancing threshold, an eNodeB selects a
certain number of UEs for load-based inter-RAT measurements based on UE capabilities,
UE running services, and ARP configurations.
 Service-based inter-RAT measurements are initiated by eNodeBs. eNodeBs identify the
types of services run by UEs, and instruct the UEs to perform service-based inter-RAT
measurements.
 Uplink quality-based inter-RAT measurements are initiated by eNodeBs. An eNodeB
instructs a UE to perform an uplink quality-based inter-RAT measurement when
detecting the UE's limited uplink quality.
 Before a distance-based inter-RAT handover is performed, an eNodeB estimates its
distance to a UE based on the TA reported by the UE. When the reported TA exceeds the
specified threshold, the eNodeB instructs the UE to perform a distance-based inter-RAT
measurement.
If a UE detects that the signal quality of a neighboring cell is higher than the specified
handover threshold during an inter-RAT measurement, the eNodeB initiates the associated
inter-RAT handover.

LTE TDD
Figure 3-9 Inter-RAT handover procedure
3.3.3 Parameter Settings

Inter-frequency and inter-RAT handovers are rarely used in the existing commercial networks.
Therefore, this section only describes parameter settings for intra-frequency handovers.
Mn and Ms are specified by the IntraFreqHoA3TrigQuan parameter. This parameter can be

set to RSRP and RSRQ, and its value is contained in the measurement control report defined
in 3GPP TS 36.331. In Huawei LTE systems, the default value is RSRP.
A UE reports event A3 in event-triggered periodic reporting mode when the triggering

conditions for event A3 are always met within the time specified by TimeToTrigger, as
shown in Figure 3-10.

LTE TDD
Figure 3-10 Event A3 triggering mechanism
For intra-frequency handovers, the serving and neighboring cells use the same frequency.
Therefore, Ofn and Ofs are equal to 0. In most cases, the CIO is 0 (which can be set by using
the MOD EUTRANINTERFREQNCELL command). Therefore, the triggering condition
for event A3 can be simplified as follows:
Mn > Ms + Off + Hys
In this inequality, Off is specified by the IntraFreqHoA3Offset parameter and Hys by the
IntraFreqHoA3Hyst parameter related to the MOD INTRAFREQHOGROUP command.
The values of both parameters are in 0.5 dB.
In current configurations, Off and Hys are equal to 2 dB.
Therefore,
Mn > Ms + Off + Hys = Ms + 2 x 0.5 + 2 x 0.5 = Ms + 2 dB
Therefore, event A3 is triggered when the serving cell's reference signal received power
(RSRP) is 2 dB lower than that of a neighboring cell.
Handover Triggering Delay

In Figure 3-10, Time To Trigger indicates the handover triggering delay. A UE reports cell
measurement information to the serving eNodeB only when the triggering conditions for
event A3 are always met within the handover triggering delay.
The current configurations are added by running the following command:

LTE TDD
ADD INTRAFREQHOGROUP: LocalCellId=0, IntraFreqHoGroupId=0,

IntraFreqHoA3TimeToTrig=320ms;
In the current configurations, a UE reports event A3 measurement reports only when the
triggering conditions for event A3 are always met within 320 ms.
CIO
CIOs can be configured separately for the serving cell and target cell. When signal quality
fluctuates violently, the probability for incoming or outgoing handovers for a specific cell
must be adjusted. The following inequality specifies the entering conditions for event A3 in
3GPP TS 36.331:
Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off
In Huawei LTE systems, Ofn, Ofs, and Ocs are equal to 0. Therefore:
Mn + Ocn – Hys > Ms + Off
In this inequality, Ocn indicates the CIO. The CIO is used to adjust the cell edge during a
handover. A large CIO for the target cell increases the possibility for an incoming handover to
this cell, and a small CIO decreases the possibility for an incoming handover. Huawei
mobility robust optimization (MRO) algorithm enables automatic CIO adjustment.
The CIO is delivered in the neighboring cell list field in measurement control messages. The
CIO is delivered only when it is not equal to 0.
Event Triggered Periodic Reporting Interval

The event triggered periodic reporting interval is an interval between the time an event A3
measurement report is sent to the eNodeB and the time the next event A3 measurement report
is sent. A UE periodically sends event A3 measurement reports to the eNodeB if the entering
conditions for event A3 are met and no handover command is received.
This interval is specified by the IntraFreqHoRprtInterval parameter, and the default value
is 320 ms in eRAN3.0. A smaller value increases the transmission rate of event A3
measurement reports over the radio interface, and quickens the transmission of subsequent
event A3 measurement reports when an event A3 measurement report is discarded at layer 3.
Event A3 measurement reports are rarely discarded at layer 3. Therefore, this parameter has
limited impact on handover-associated KPIs.

LTE TDD
3.4 Signaling Exchange on the User Plane

LTE systems support only hard handovers. There is no signaling exchange at an interval
between the time a UE receives a handover command and disconnects signaling exchange
with the source cell and the time the UE starts signaling exchange with the target cell. This
interval lasts for dozens of milliseconds. Therefore, this interruption has limited service
impact.
Figure 3-11 shows the signaling exchange procedure on the user plane.
Figure 3-11 Signaling exchange procedure on the user plane
Huawei eNodeB supports the following operations:
1. After the eNodeB delivers a handover command, the transmission of downlink data stops
at Packet Data Convergence Protocol (PDCP) and Radio Link Control (RLC) layers in
the source cell and data in the hybrid automatic repeat request (HARQ) queue may be
retransmitted over the radio interface at the Media Access Control (MAC) layer.
2. UEs stop transmitting and receiving uplink data in the source cell after receiving a
handover command.
3. UEs can transmit uplink data and receive downlink data in target cells after receiving
handover completion messages from the target cells.
Time cannot be precisely synchronized between two eNodeBs. Therefore, the handover delay
applies only to intra-eNodeB handovers.

LTE TDD
Handover Performance Fault Diagnosis Guide 4 KPIs
4 KPIs
Handover-associated KPIs include the handover success rate, handover delay on the control
plane, and handover delay on the user plane.
4.1 Handover Success Rate

The handover success rate is defined as follows:
Handover success rate = Number of successful handovers/Number of handover attempts x

100%
The handover success rate may vary with statistic methods:
 The number of handover attempts can be calculated when a measurement report is

delivered or a handover command is delivered.
 The handover success rate can be obtained on the UE and E-UTRAN. On the UE, the
handover success rate is measured based on the UE data in the drive test result. On the
E-UTRAN, the handover success rate is measured based on message tracing or traffic
statistics.
4.2 Handover Delay on the Control Plane

The handover delay on the control plane is the interval between the time a handover command
is delivered and the time a handover completion message is transported.

LTE TDD
The handover delay on the control plane is measured on the E-UTRAN. It can also be
measured on the UE. The handover delay measured on the E-UTRAN is greater than that
measured on the UE.
4.3 Handover Interruption Delay on the User Plane

The handover delay on the user plane is crucial, because it may affect user experience. The
handover delay on the user plane can be measured in the uplink and downlink. The methods
of measuring the delay in the uplink and downlink vary with timing points. The handover
delay at the application layer is closely associated with user experience. Handover
interruption delays can also be measured at the PDCP, RLC, and MAC layers.
The preceding figure shows the protocol layers at which data is transmitted on the UE and
eNodeB. The black and red arrows indicate uplink and downlink data transmission directions,
respectively. The pink dashed line indicates that other transport nodes exist between the IP
layer and the PDCP layer. For example, when a data card is used on the personal computer
(PC), the MSN application may be installed on the PC, and the MSN server is connected on
the Web Internet server.
If data transmission is interrupted, the delays are caused at the protocol layers along the
transmission routes. In delay tests, packet injection must be performed in full rates at the
associated directions. This ensures accurate delay measurement results, even when data
transmission is interrupted at the application layer.

LTE TDD
The handover delay on the user plane indicates the interval between the time a protocol layer
entity transmits or receives the last packet before a handover is performed and the time it
transmits or receives the first packet after the handover is performed. It can be measured on
the UE and eNodeB. In actual tests, only uplink and downlink handover delays need to be
measured at the application layer and RLC layer.
4.3.1 Uplink Handover Interruption Delay at the Application

Layer
When uplink packets are captured using the IP packet capture software on the File Transfer
Protocol (FTP) server, the maximum interval between the time a handover command is
delivered and the time a handover completion message is received is the uplink handover
delay on the user plane at the application layer. In the test, small User Datagram Protocol
(UDP) packets can be used to decrease the handover delay.
4.3.2 Downlink Handover Interruption Delay at the Application

Layer
When uplink packets are captured using the IP packet capture software on the UE, the
maximum interval between the time a handover command is delivered and the time a
handover completion message is received is the downlink handover delay on the user plane at
the application layer. In the test, small UDP packets can be used to decrease the handover
delay.
4.3.3 Uplink Handover Interruption Delay at the RLC Layer on

the eNodeB
The uplink handover delay at the RLC layer on the eNodeB is the interval between the time
the source cell receives the last packet data unit (PDU) at the RLC layer and the time the
target cell receives the first PDU at the RLC layer. This delay is available only for
intra-eNodeB handovers.
4.3.4 Downlink Handover Interruption Delay at the RLC Layer on

the eNodeB
The downlink handover delay at the RLC layer on the eNodeB is the interval between the
time the source cell transmits the last PDU at the RLC layer and the time the target cell
transmits the first PDU at the RLC layer. This delay is available only for intra-eNodeB
handovers.

LTE TDD
4.3.5 Uplink Handover Interruption Delay at the RLC Layer on

the UE
The uplink handover delay at the RLC layer on the UE is the interval between the time a UE
transmits the last PDU at the RLC layer in the source cell and the time the UE transmits the
first PDU at the RLC layer in the target cell.
4.3.6 Downlink Handover Interruption Delay at the RLC Layer on

the UE
The downlink handover delay at the RLC layer on the UE is the interval between the time a
UE receives the last PDU at the RLC layer in the source cell and the time the UE receives the
first PDU at the RLC layer in the target cell.

LTE TDD
Handover Performance Fault Diagnosis Guide 5 Methods for Locating Common Faults
5 Methods for Locating Common Faults
5.1 Locating Handover Failures

In most cases, handovers fail due to the following reasons:
 Signaling loss: Signaling is faulty in the transport process or cannot reach the peer end.
 Signaling processing failure: UEs or eNodeBs cannot process signaling properly due to,
for example, insufficient resources.
Signaling transmission is classified into wired and wireless signaling transmission.

Transmission over S1 and X2 interfaces belongs to wired transmission, and transmission over
the Uu interface belongs to wired transmission. Compared with wired transmission, wireless
transmission is more vulnerable, especially when signal quality is poor.
5.1.1 Locating Signaling Faults over the Uu Interface

In a handover process, only the following messages are transported over the Uu interface:
 MEASUREMENT REPORT
 RRC CONN RECFG
 RRC RECFG CMP
In some cases, service drop and reestablishment is required after a handover is complete due
to the first RRC CONN RECFG message exchanged over the Uu interface.

LTE TDD
Figure 5-1 Handover signaling exchange over the Uu interface
The following faults may occur in signaling over the Uu interface:
1. Loss of measurement reports, due to the following reasons:

− Measurement reports are lost between network layers in UEs. For example, layer 2
cannot process the measurement report transmitted from layer 3.
− Due to insufficient PDCCHs, eNodeBs cannot receive the uplink grants sent by UEs
in the measurement report.
− Due to insufficient PUSCHs, eNodeBs do not receive measurement reports or receive
measurement reports with incorrect cyclic redundancy codes (CRCs).
2. Loss of handover commands, due to the following reasons:
− eNodeBs do not deliver handover commands due to reasons such as missing
configuration of neighboring cells and insufficient resources.
− UEs cannot parse handover commands due to insufficient PDCCHs.
− UEs cannot parse handover commands due to insufficient PDSCHs.
3. Loss of handover completion messages, due to the following reasons:
− Due to insufficient PRACHs, eNodeBs do not receive the preambles sent by UEs in
the target cells.

LTE TDD
− UEs cannot receive random access response (RAR) messages due to insufficient
PDSCHs.
− Due to insufficient PUSCHs, eNodeBs cannot receive the handover completion
messages sent by UEs.
Transmission over the Uu interface belongs to wireless transmission, and the channel quality
can be analyzed separately in the uplink and downlink. Uplink and downlink faults can be
located based on eNodeB signaling tracing results if UEs can obtain information such as the
RSRP, signal to interference plus noise ratio (SINR), initial block error rate (IBLER),
downlink grant, and uplink grants.
Channel quality is estimated based on the following items:
 RSRP: The RSRP is the receive power of downlink pilots. Based on the RSRP of
downlink pilots, the channel quality can be roughly estimated. If the RSRP is greater
than –85 dBm, a UE is located near the eNodeB. If the RSRP equals to –95 dBm, the UE
is located at middle points. If the RSRP is less than –105 dBm, the UE is located
remotely from the eNodeB. Channel quality cannot be accurately estimated based on
RSRP, especially when the serving cell and neighboring cells provide similar RSRP.
 SINR: The SINR of downlink pilots is measured. If the SINR is less than 0 dB, downlink
channel quality is poor. If the SINR is less than –3 dB, the downlink channel quality is
reaching the demodulation threshold, which may cause the handover signaling loss and
handover failures. The SINR of uplink channels can be obtained using user performance
tracing on the local maintenance terminal (LMT).
 IBLER: The IBLER must decrease to the target value of 10%. When channel quality is
optimal, the IBLER must be close to or equal to 0%. A large IBLER indicates poor
channel quality. If the IBLER is large, service drop and handover failures may occur or
the handover delay may increase. The downlink IBLER can be obtained from the
GENEX Probe, and the uplink IBLER can be obtained from the user performance tracing
result on the LMT. The IBLER obtained from the LTE is more accurate than that
obtained from the probe.
 Physical downlink control channel (PDCCH) downlink: The downlink grant indicates
the number of the PDCCHs correctly parsed by UEs. If uplink and downlink UDP
packets are injected based on the maximum system capability, 800 PDCCHs are
allocated per transmission time interval (TTI) on the eNodeB when the subframe
configuration is 3:1. If the downlink grants equal to 800, PDCCHs are successfully
demodulated with proper channel quality. If the downlink grants are lower, PDCCHs
cannot be demodulated due to poor channel quality.
In some cases, the uplink and downlink channel quality cannot be determined based on only
the integrity of uplink and downlink signaling at layer 3. For example, downlink signaling
cannot be demodulated when the downlink channel quality is poor. When downlink PDCCHs
cannot be demodulated, uplink scheduling is affected, causing the loss of uplink signaling. In
most cases, channel quality problems are caused by weak coverage or interference.
Faults related to the air interface must be categorized into, for example, coverage faults,
interference, missing configuration of neighboring cells, and handovers not performed in a
timely manner. Based on these fault categories, appropriate solution can be taken.

LTE TDD
5.1.2 Signaling Faults over the X2 Interface

For X2-based inter-eNodeB handovers, only the following messages are transported over the
X2 interface:
 HANDOVER REQUEST
 HANDOVER REQUEST ACK
 SN STATUS TRANSFER
 UE CONTEST RELEASE
Figure 5-2 shows the handover signaling exchange over the X2 interface.
Figure 5-2 Handover signaling exchange over the X2 interface
The following faults may occur in signaling over the X2 interface:
1. Loss of handover requests, due to the following reasons:

− Measurement report processing faults in the eNodeB due to missing configuration of
neighboring cells and internal module faults.
− Abnormal transport over the X2 interface, such as packet loss

LTE TDD
2. Loss of handover responses, due to the following reasons:

− Internal faults of the source cell: The source cell sends a HANDOVER CANCEL
message to the target cell over the X2 interface before the target cell feeds back a
handover response.
− Handover preparation faults in the target cell: If these faults occur, a HANDOVER
PREPARATION FAILURE message is transported over the X2 interface.
3. Loss of status transfer messages, due to the following reasons:
− Internal faults in the source cell
4. Loss of UE context release messages, due to the following reasons:
− The target cell does not perform the S1 path switch after receiving a handover
completion message.
− The S1 path status cannot be switched.
Signaling exchange faults over the X2 interface may occur due to message transport failures
or internal signaling processing faults inside the eNodeB. In most cases, these faults are
caused due to message transport failures, which must be located using packet capture at both
ends.
5.1.3 Signaling Faults over the S1 Interface

The S1 interface is involved in inter-eNodeB handovers. For X2-based inter-eNodeB
handovers, only S1AP PATH SWITCH REQ and S1AP PATH SWITCH REQ ACK messages
are transported over the S1 interface. For S1-based inter-eNodeB handovers, more messages
are transported between the mobility management entity (MME) and the source and target
eNodeBs. In Figure 5-3 and Figure 5-4, the green lines indicate the messages transported over
the S1 interface.

LTE TDD
Figure 5-3 Handover signaling exchange over the S1 interface

LTE TDD
Figure 5-4 Handover signaling exchange over the S1 interface

Meas_RPRT
S1AP_Handover_Required
S1AP_Handover_Request
S1AP_Handover_REQ_ACK
S1AP_Handover_CMD
RRC_CONN_RECFG
(HO_CMD) S1AP_eNB_Status_Transfer
S1AP_MME_Status_Transfer
RRC_CONN_RECFG_CMP
(HO_CMP) S1AP_Handover_Notify
S1AP_UE_CONTEXT_REL_CMD
S1AP_UE_CONTEXT_REL_CMP
RRC_CONN_RECFG
RRC_CONN_RECFG_CMP
The following faults may occur in signaling over the S1 interface during X2-based handovers:
1. Loss of the S1AP PATH SWITCH REQ message for X2-based inter-eNodeB handovers,
due to the following reasons:
− Target eNodeB's failure in processing handover completion messages
− Abnormal transport over the S1 interface, such as packet loss
2. Loss of the S1AP PATH SWITCH REQ ACK message for X2-based inter-eNodeB
handovers, due to the following reasons:
The failure of the evolved packet core (EPC) in processing S1AP PATH SWITCH REQ
messages
3. Loss of the S1AP HANDOVER REQUIRTED message for S1-based inter-eNodeB
− The source cell does not S1AP HANDOVER REQUIRTED message due to reasons
such as missing configuration of neighboring cells and insufficient resources.
− The S1AP HANDOVER REQUIRTED message is lost over the S1 interface.
4. Loss of the S1AP HANDOVER REQUEST messages for S1-based inter-eNodeB

LTE TDD
− The EPC processes the received S1AP HANDOVER REQUIRED message

abnormally.
− The S1AP HANDOVER REQUEST message is lost over the S1 interface.
5. Loss of the S1AP HANDOVER REQUEST ACK message for S1-based inter-eNodeB
− The target cell processes the received S1AP HANDOVER REQUEST abnormally
due to reasons such as insufficient resources.
− The S1AP HANDOVER REQUEST ACK message is lost over the S1 interface.
6. Loss of the S1 HANDOVER CMD message for S1-based inter-eNodeB handovers, due
to the following reasons:
− The EPC processes the S1AP HANDOVER REQUEST ACK message abnormally.
− The S1AP HANDOVER REQUEST ACK message is lost over the S1 interface.
7. Loss of the S1AP ENB STATUS TRANSFER messages for S1-based inter-eNodeB
− The source cell processes the received S1 HANDOVER CMD message abnormally.
− The S1AP ENB STATUS TRANSFER message is lost over the S1 interface.
8. Loss of the S1AP MME STATUS TRANSFER messages for S1-based inter-eNodeB
− The EPC processes the S1AP ENB STATUS TRANSFER message abnormally.
− The S1AP MME STATUS TRANSFER message is lost over the S1 interface.
9. Loss of the S1AP HANDOVER NOTIFY messages for S1-based inter-eNodeB
− The target cell processes the handover completion message abnormally.
− The S1AP HANDOVER NOTIFY message is lost over the S1 interface.
10. Loss of the S1AP UE CONTEST REL CMD message for S1-based inter-eNodeB
− The EPC processes the S1AP HANDOVER NOTIFY message abnormally.
− The S1AP UE CONTEST REL CMD message is lost over the S1 interface.
11. Loss of the S1AP UE CONTEST REL CMP message for S1-based inter-eNodeB
− The source cell processes the received S1AP UE CONTEST REL CMD message
abnormally.
− The S1AP UE CONTEST REL CMP message is lost over the S1 interface.
Signaling exchange faults over the S1 interface may occur due to message transport failures
or internal signaling processing faults inside the associated NEs. In most cases, these faults
are caused due to message transport failures, which must be located using packet capture at
both ends.

LTE TDD
5.2 Locating Handover Delay Faults

Handover delays are divided into the delay on the control plane and the delay on the user
plane.
5.2.1 Locating Handover Delay Faults on the Control Plane

The handover delay on the control plane is the interval between the time a handover command
is delivered and the time a handover completion message is transported. It can be measured
on the eNodeB and UE. When observed on the eNodeB, the handover delay on the control
plane includes two radio interface delays. Therefore, the handover delay measured on the
eNodeB is greater than that measured on the UE. Only the delay on the control plane for
intra-eNodeB handovers can be observed on the eNodeB, because clocks cannot be
synchronized between two eNodeBs accurately. For a UE supplied by Samsung, the handover
delay on the control plane is about 31 ms when measured on the UE and is 38 ms when
measured on the eNodeB.
From UEs' perspective, the handover delay on the control plane consist of the handover
signaling processing delay, delay for synchronization with the target cell, and delay for
accessing the target cell. Among these three delays, the delay for accessing the target cell is
the longest.
From eNodeBs' perspective, the handover delay on the control plane consists of the handover
delay on the control plane measured on the UE and the delay for transporting two handover
messages over the radio interface.
If the delay on the control plane is greater than the upper limit, the common causes are as
follows:
 The delay consists of the delay for retransmitting handover commands over the radio
interface if the retransmissions are performed.
 The delay for a UE's attempts to access the target cell is repeatedly measured on the UE
and eNodeB.
 The delay increases with the packet random access channel (PRACH) scheduling period.
The TTI tracing results on the eNodeB and UE can be analyzed to locate faults related to the
handover delay on the control plane.
5.2.2 Locating Handover Delay Faults on the User Plane

There are different handover delays on the user plane based on the measurement points.
Among these handover delays, the handover delay at the application layer is closely related to
user experience. The handover delay at the application layer is measured at the IP layer on the
FTP server or UE. The handover delay may affect the E-UTRAN, EPC, and public network.
Therefore, it cannot be identified only on the E-UTRAN. On the E-UTRAN, the handover
delay on the user plane at the RLC is measured. The handover delay is measured separately in
the uplink and downlink.

LTE TDD
For Huawei UEs, the downlink handover delay on the user plane at the RLC layer is about 34
ms, and the handover delay on the user plane at the IP application layer is about 120 ms in the
uplink and about 60 ms in the downlink.
The handover delay on the user plane may be affected due to the following reasons on the
E-UTRAN:
 The eNodeB retransmits handover commands, increasing the delay in the downlink.
 Data is retransmitted on the user plane in the uplink or downlink due to poor radio
interface quality.
 The delay for accessing the target cell is large and data transport on the user plane
recovers slowly.
 The transport delay is large over the X2 or S1 interface.
 The PRACH scheduling period is large.
The TTI tracing results on the eNodeB and UE can be analyzed to locate faults related to the
handover delay on the user plane.

LTE TDD
Handover Performance Fault Diagnosis Guide 6 Fault Locating Procedure
6 Fault Locating Procedure
Before locating a handover fault, you need to verify that this fault occurs on the control plane
or user plane. Handover failures and handover delay faults on the control plane must be
analyzed based on signaling exchange on the control plane, and the handover delay faults on
the user plane must be analyzed based on data scheduling and exchange on the user plane.
6.1 Signaling Tracing

Signaling exchange can be traced on the eNodeB or UE. Signaling tracing can be used to
locate handover failures and the handover delay faults on the control plane.
6.1.1 Signaling Tracing on the eNodeB

On the eNodeB, the LMT can be used to trace signaling over the Uu, X2, and S1 interfaces,
and the M2000 can be used to trace signaling for a single user. Then, you can locate a
handover fault on the control plane based on the signaling tracing results and the signaling
exchange procedures described in chapter 5 "Methods for Locating Common Faults." The
delay on the control plane cannot be traced for inter-eNodeB handovers, because the clocks
cannot align with each other between two eNodeBs. For intra-eNodeB handovers, the
handover delay can be calculated based on the Uu interface signaling tracing on the
LMT. Figure 6-1 shows the handover signaling exchange over the Uu interface traced on the
eNodeB.

LTE TDD
Figure 6-1 Handover signaling exchange over the Uu interface traced on the eNodeB
In the previous figure, the handover delay on the control plane is 37.843 ms.
6.1.2 Signaling Tracing on the UE

Signaling can be traced on the UE using dedicated UE software. For example, the X-CAL and
GENEX Probe can be used to trace signaling exchange on Samsung UEs and Huawei UEs,
respectively. Then, you can locate a handover fault on the control plane based on the signaling
tracing results and the signaling exchange procedures described in chapter 5 "Methods for
Locating Common Faults." The signaling delay can be calculated based on the tracing results
over the Uu interface. Figure 6-2 shows the signaling tracing results of Huawei UE by using
the GENEX Probe.
Figure 6-2 Handover signaling exchange on Huawei UE using the GENEX Probe
In the previous figure, the handover delay on the control plane is 7.316 ms (597054419 –
597047103 = 7316 μs).

LTE TDD
6.1.3 Identification of Handover Messages

In a handover, the RRC CONNECT RECONFIG message is used both as a handover
measurement control message and the handover command. In addition, it also carries other
measurement and signaling control information. The MeasurementReport message is not only
a handover measurement report, but also carries other measurement information, such as
inter-cell interference coordination (ICIC), other frequencies, and other RATs. Therefore,
during fault locating, check for whether these messages are associated with handovers.
The RRCConnectionReconfiguration message is used for measurement control if it contains

the measConfig information element (IE), and is used for handover measurement control if it
contains the eventA3 IE and the values of the a3-offset and hysteresis IEs are not negative. If
this message is used for measurement control, the measId IE to which the reportConfigIdg IE
belongs indicates the handover measurement ID, as shown in Figure 6-3.
Figure 6-3 Identification of a handover measurement control message

LTE TDD
If the value of the measId IE in the measurementReport message is the same as measId in the
handover measurement control message, this measurementReport message is an event A3
measurement report, as shown in Figure 6-4.
Figure 6-4 Identification of a handover measurement report message
The RRCConnectionReconfiguration message with a targetPhysCellId IE is a handover

command, as shown in Figure 6-5.
Figure 6-5 Identification of a handover command

LTE TDD
6.2 Measuring the Handover Delay on the User Plane

The handover delay on the user plane at the IP application layer can be measured by using the
IP packet capture tool on the UE or FTP server. For the handover delay on the eNodeB, the
delay at the RLC layer is measured.
6.2.1 Measuring the Handover Delay at the IP Application Layer

The handover delay at the application layer is measured based on the time IP packets are
captured. IP packets are captured on the UE in the downlink and on the server in the uplink
using the same method. The Ethereal and Wireshark are used for packet capturing.
Figure 6-6 IP packet capturing
There is a slight deviation between the actual handover time and the time recorded by the
packet capturing software. Therefore, subjective judgment is required to determine the
handover delay at the IP application layer. Consequently, subjective deviations are introduced
in the test results.
The downlink handover delay at the application layer can be measured using the X-CAL
dedicated for Samsung UEs. On the X-CAL, click Message. On the displayed Packet
Capture Viewer page, click File Menu. Then, select a packet to be traced, and click Manual
Capture.

LTE TDD
Figure 6-7 IP packet capturing using the X-CAL
6.2.2 Measuring the Handover Delay at the RLC Layer

The uplink and downlink handover delays at the RLC layer can be measured on the UE and
eNodeB.
Measuring the Handover Delay on the UE

This part uses Huawei UE and the GENEX Probe as an example. For Huawei UEs, the OMT
is used as the control software.
On the OMT, enable the reporting of the handover delay.
NOTE
The reporting of the handover delay may affect the test for peak rates. Therefore, it is disabled by
default.
After the reporting of the handover delay is enabled, the GENEX Probe starts measuring the
handover delay, and displays the uplink and downlink handover delays on the user plane at
the RLC layer. As shown in Figure 6-8, the downlink and uplink handover delays are 29197
μs and 17181μs, respectively.

LTE TDD
Figure 6-8 Handover delays displayed on the GENEX Probe
Measuring the Handover Delay on the eNodeB

For inter-eNodeB handovers, the handover delay on the user plane cannot be measured,
because the clock cannot be aligned between eNodeBs. For intra-eNodeB handovers, the
handover delay on the user plane can be measured on the LMT.
Figure 6-9 Settings on the LMT for measuring the handover delay on the user plane

LTE TDD
Set the parameters on the User Plane Trace dialog box before using the LMT to obtain the
handover delay on the user plane.
After the handover delay is obtained, send the data to the R&D department for analysis.
6.3 Recommended Solutions

Based on the descriptions in previous sections, handover problems are classified as follows:
 Transmission problems
 Network element (NE) processing faults
 Coverage problems, such as weak coverage and cross-cell coverage
 Interference
 Missing configuration of neighboring cells
 Handover delay
There is a high probability that transmission problems occur, especially cross-town

transmission problems. These problems can be identified by using data capture at the
transmitter and receiver of the radio network equipment. NE processing problems can be
identified based on NE logs. Coverage problems, interference, missing configuration of
neighboring cells, and handover delay are related to air interface quality, which causes
signaling loss and handover failures. These problems can be resolved as follows:
 Weak coverage: Adjust antenna settings or transmit power, or increase site coverage.
 Cross-cell coverage: Adjust antenna settings.
 Interference: Enable interference coordination functions such as frequency selective
scheduling.
 Missing configurations of neighboring cells: Reconfigure neighboring cells on the LMT
or M2000.
 Handover delay: Adjust handover parameters, such as handover thresholds, hysteresis,
handover delay triggering time, and CIO.

LTE TDD
Handover Performance Fault Diagnosis Guide 7 Typical Cases
7 Typical Cases
Figure 7-1 and Figure 7-2 show the procedures for locating handover failures on the control
plane and the handover delay on the user plane, respectively.
Figure 7-1 Procedure for locating handover failures on the control plane
Figure 7-2 Procedures for locating the handover delay on the user plane

LTE TDD
These procedures are analyzed in the following tables.
Handover Failure Locating Method

Channel quality Use the GENEX Probe to trace the RSRP, SINR, IBLER, and uplink
problems and downlink grants.
Implement user performance tracing on the LMT to analyze uplink
and downlink channel quality.
Network Check for cross-cell coverage based on the network plan. If
optimization cross-cell coverage exists, adjust the electrical tilts of the antenna
problems system.
Configure neighboring relationships for the cluster edge.
Configuration Check for missing configurations of neighboring cells by running
problems man-machine language (MML) commands.
Adjust X2 settings.
Adjust configurations related to random access (Ncs_Index).
Adjust authentication configurations.
Transmission Check for alarms related to intermittent link disconnections.
problems
Verify transmission stability.
Product problems Check for product and function defects on the E-UTRAN and EPC.
Locate the product problems with the cooperation of R&D
personnel.
Handover Delay Problem Solution

Packet CRC error in the Since eRAN1.0 B060SPC350, the source cell
retransmission source cell instructs the target cell to use a low
modulation and coding scheme (MCS) at layer
2 when receiving the handover measurement
report at layer 3. The MCS scheme can be
configured. Increase the PDCCH power and
set the control channel element (CCE)
aggregation level to 8.
CRC error in the Since eRAN1.0 B060SPC350, the target cell
target cell starts the timer after a handover is complete.
During the time specified by the timer, low
MCS schemes are used. The MCS scheme can
be configured. Increase the PDCCH power and
set the CCE aggregation level to 8.
SET HOMCSPARAM: MCSHOSTATIC=0,
HOCQIRPTTIMER=60ms;

LTE TDD
Handover Delay Problem Solution

Re-delivery of Frequency Since eRAN1.0 B060SPC340, frequency
handover selection in case of selection is not performed when HARQ
commands HARQ retransmission is enabled in the handover
retransmission command.
PDCCH and The following optimizations were introduced
physical downlink in eRAN1.0 B060SPC350:
shared channel
 The PDCCH power is increased and the
(PDSCH)
limitations in the CCE aggregation level 8 is used fixedly in
handover the handover command.
command  The PDSCH power is increased and MCS
scheme 1 is used fixed in the handover
command.
 HARQ and automatic repeat request (ARQ)
retransmissions are enabled.
NOTE
Considering the commercial UE capabilities, HARQ
and ARQ retransmissions are disabled by default.
 Discontinuous transmission (DTX) is

introduced.
Preamble retransmission during random Optimize the coverage quality and adjust
access handover parameters to improve the channel
quality at the handover point and decreases the
number of retransmissions.
X2 configurations Check X2 configurations, such as the X2
interface, and IP path.
UE processing procedure Since eRAN1.0 B060SPC360, if the UE
receives an RRC reconfiguration message
during its system information update, the
system information update is terminated and
the UE processes the RRC reconfiguration
message immediately.

LTE TDD
7.1 Handover Failures
7.1.1 UEs Cannot Receive a Handover Command after Multiple

Measurement Reports Is Sent.
Handovers cannot be performed if automatic neighbor relation (ANR) is disabled and
neighboring relationships are not configured.
Check whether neighboring cells are configured on the eNodeB. If a UE sends a handover
measurement report to cell A for a handover to cell B and cell B is not a neighboring cell of
cell A, cell B does not deliver the handover command, even when it receives the handover
measurement report. Consequently, the handover fails. In this case, if the UE continues
moving away from cell A, service drop may occur due to poor signal quality.
To check for missing configurations of neighboring cells, perform the following operations:
 Run the LST EUTRANEXTERNALCELL command to query external E-UTRAN

cells.
 Run the LST EUTRANINTRAFREQNCELL command to query intra-frequency
neighboring cells.
In eRAN1.0, intra-eNodeB handovers can be performed only after intra-frequency

neighboring cells are configured, and inter-eNodeB handovers can be performed only after
external E-UTRAN cells and intra-frequency neighboring cells are configured. UEs can be
handed over in both directions if two cells are configured as external cells and intra-frequency
neighboring cells with each other.
In eRAN1.1, intra-eNodeB handovers can be performed even when no intra-frequency

neighboring cells are configured, and inter-eNodeB handovers can be performed after only
external E-UTRAN cells are configured.
NOTE
Measurement control and measurement control completion follows the handover procedure.
If neighboring relationships remains unchanged between eNodeBs during intra-eNodeB handovers, no
measurement control is performed.
When the CIO equals to 0, measurement control is performed only if neighboring relationships change.
When the CIO is not equal to 0, measurement control is required.
If neighboring relationships are configured properly, check the signaling tracing results on the
eNodeB to verify whether the eNodeB receives measurement reports or whether UEs do not
receive handover commands sent from the eNodeB. These problems may occur due to poor
channel quality in the uplink and downlink.

LTE TDD
7.1.2 Random Access Fails.

This section concerns only random access failures caused by incorrect parameter settings.
Random access performance is associated with Ncs values, and an Ncs value corresponding to
a maximum theoretical access radius. If a UE initiates random access beyond the maximum
theoretical access radius, a preamble sent by the UE reaches the eNodeB after a long
transmission delay, and the preamble is allocated an ID of the previous preamble when the
eNodeB parses the preamble in the normal receive window. In this case, the RAR sent by the
eNodeB does not match the preamble. Consequently, random access fails.
The following figure shows the log information when the RAR does not match the preamble.
The following table illustrates the mapping between Ncs indexes and maximum theoretical
access radii.
Ncs Index Ncs Value Max Access Radius(km)

1.00 13.00 1.86
2.00 15.00 2.15
3.00 18.00 2.57
4.00 22.00 3.15
5.00 26.00 3.72
6.00 32.00 4.58
7.00 38.00 5.44

LTE TDD
Ncs Index Ncs Value Max Access Radius(km)

8.00 46.00 6.58
9.00 59.00 8.44
10.00 76.00 10.87
11.00 93.00 13.3
12.00 119.00 17.02
13.00 167.00 23.89
14.00 279.00 39.9
15.00 419.00 59.93
Random access fails when a cell covers a long distance and the distance between the UE
position and eNodeB exceeds the maximum theoretical access radius. In this case, you can
increase the Ncs index to improve the random access success rate.
 In eRAN1.0, run the following command to set the Ncs value:

SET PRACHCFG: ZEROCORRZONECONFIG=xx;
The ZEROCORRZONECONFIG parameter specifies the Ncs index.
 In eRAN1.1, run the MOD PRACHCFG command to set the Ncs value.
7.1.3 Messages Cannot Be Parsed Due to Inappropriate Ciphering

and Integrity Configurations.
In LTE systems, each tracking area code (TAC) in the tracking area list (TAL) corresponds to
multiple cells. When a UE is handed over to a cell with a different TAC, tracking area update
(TAU) is performed.
As shown in drive test results, the target eNodeB cannot receive the handover completion
message from a UE, after TAU is performed, causing a handover failure. In this case, run the
LST S1SECPARA to check EPC parameter settings.

LTE TDD
Deselect INTER TAU and INTRA TAU from the Authentication selection check box. The
USN1.1 does not support inter-TAU and intra-TAU authentication.
If forcible TAU authentication is enabled, the EPC instructs the eNodeB to update the
authentication key, and the UE also needs to update the authentication key. However, the EPC,
eNodeB, and UE do not support TAU authentication. Consequently, the UE uses original keys
to encipher the handover completion message, and the target eNodeB uses the updated keys to
decipher the handover completion message. Consequently, integrity authentication fails,
resulting in a handover failure.
If ciphering algorithms are set consistently between the source cell and target cell, the target
cell cannot authenticate the integrity of a handover completion message at layer 2, and then
instructs layer 3 to release the UE. According to the signaling tracing result, the eNodeB does
not receive the handover completion message sent by the UE. In this case, run the DSP
ENODEBSECCAP command to verify that the ciphering algorithms are set consistently
between the source and target cells.
7.1.4 Handover Commands Are Lost.

In this section, the drive test data is obtained when the load ratio is 50% and ICIC is used.
At 23:45:59.062, a UE does not receive any command for triggering a handover from a cell
with the physical cell identifier (PCI) equal to 48 to a cell with the PCI equal to 50.
At the handover point, the RSRP of the neighboring cell increases by 6 dB, which causes
severe interference with the serving cell. In the downlink the SINR is only –5 dB.
Consequently, the UE cannot parse the handover command.

LTE TDD
This problem can be resolved by adjust the antenna radio frequency (RF) parameters and
CIOs of these two cells.
7.1.5 The Distance Between UE Position and the Target Cell

Exceeds the Maximum Theoretical Access Radius Mapped to the
Ncs Index.
In eRAN1.0, the default Ncs index is 2, which is mapped to the maximum theoretical access
radius of 2.15 km. However, coverage situations vary in different areas. For example, a cell
covers a larger area in dense urban areas where a large number of eNodeBs are deployed than
that in suburban areas where few eNodeBs are deployed. In this case, if the same Ncs Index
applies to the dense urban areas and suburban areas, network access and handovers are
performed in the dense urban areas, while they may fail in suburban areas when the distance
between the UE position and the target eNodeB exceeds the maximum theoretical access
radius. The following figure shows a commercial LTE network deployed in Norway. In this
network, random accesses fail when the Ncs index equals to 2, causing handover failures.

LTE TDD
7.1.6 A Smaller Time to Trigger Is Used When the RSRP of the

Source and Target Cells Is High.
Test 1: The UE does not receives a command for triggering a handover from a cell with the
PCI equal to 48 to another cell with the PCI equal to 50 at 2010-05-04 22:55:40.218.

LTE TDD

LTE TDD
This problem is analyzed as follows:
In this intra-eNodeB handover, both the S-RSRP and N_RSRP are high at the handover point.
In downlink loading scenarios, the target cell causes severe interference with the source cell.
Consequently, the SINR is lower than 0 dB and the downlink IBLER is greater than 20%,
causing the loss of handover commands.
The RSRP threshold is 2 dB, and the difference between the RSRP of the neighboring cell
and the RSRP of the source cell is 3 dB in the handover measurement report. If the RSRP of
the source and target cells is high and the downlink channel quality is poor at the handover
point in downlink virtual loading scenarios, intra-eNodeB handovers must be triggered before
the channel quality deteriorates sharply.
To ensure that a handover is performed in a timely manner, change the time to trigger from
128 ms to 64 ms. After the setting, intra-eNodeB handovers are performed successfully.
Test 2: The UE is handed over from a cell with the PCI equal to 48 to another cell with the
PCI equal to 50 at 2010-05-05 23:52:33.140 when the time to trigger is 64 ms.

LTE TDD
Test 3: The UE is handed over from a cell with the PCI equal to 48 to another cell with the
PCI equal to 50 at 2010-05-05 01:06:09.937 when the time to trigger is 64 ms.

LTE TDD
Conclusion
When the RSRP of both the source cell and target cell is high, the channel quality deteriorates
sharply at the handover point. Therefore, intra-eNodeB handovers must be performed in a
timely manner. You are advised to decrease the RSRP handover threshold from 3 dB to 2 dB
and the handover triggering time from 128 ms to 64 ms.

LTE TDD
7.1.7 The Number of Ping-pong Handovers Increases and the

Handover Success Rate Improves after the Handover Threshold Is
Set to a Smaller Value.
Assume that the handover thresholds are set to 2 dB and 3 dB in a test when the UE moves
along the same route. The test results are as follows:
When the handover threshold is set to 3 dB, 103 handovers are performed. When the
handover threshold is set to 2 dB, 130 handovers are performed.
When the threshold is changed from 3 dB to 2 dB, there are more probabilities for ping-pong
handovers. Therefore, more handovers are performed. In this case, handovers are performed
in a timely manner, so that the UE can be handed over before the downlink channel quality
deteriorates sharply, increasing the handover success rate.
7.2 Large Handover Delay on the User Plane
7.2.1 The Handover Delay Increases Due to Inappropriate X2

IPPATH Settings.
In a cluster acceptance project in Norway, the handover delay on the user plane at the RLC
layer is greater than 60 ms and even reaches 1s.
According to the timestamps obtained at associated NEs using temporary UE versions, the
target cell sends the first packet more than 100 ms after random access is complete. The
possible causes are as follows:
 A large delay occurs when the source eNodeB forwards data to the target eNodeB.
 The target eNodeB does not immediately send the UE the data received from the source
eNodeB.
Based on the test results in Huawei headquarters, an eNodeB receives the forwarded packet
over the X2 interface about 20 ms before receiving the handover completion message from a
UE. However, according to the site data, there is no data forwarded over the X2 interface.
When the delay is normal, there is data forwarded over the X2 interface. Therefore, the X2
link may be faulty.
The results of comparison between the IP address of the IP path over the X2 interface show
that the IP address of the IP address of the IP path over the X2 interface is set to the operation
and maintenance (OM) IP address. After the IP address of the IP path is changed, the
handover delay becomes normal (about 30 ms).
Conclusion
If the handover delay reaches 1s or more, verify that the port number, local IP address, and
peer IP address of the X2 link are correctly configured.

LTE TDD
7.2.2 The Handover Delay Increases Due to Inappropriate X2

IPPATH Settings.
In a cluster acceptance project in Norway, the handover delay on the user plane at the RLC
layer is greater than 60 ms and even reaches 1s.
According to the timestamps obtained at associated NEs using temporary UE versions, the
target cell sends the first packet more than 100 ms after random access is complete. The
possible causes are as follows:
A large delay occurs when the source eNodeB forwards data to the target eNodeB.
The target eNodeB does not immediately send the UE the data received from the source
eNodeB.
Based on the test results in Huawei headquarters, an eNodeB receives the forwarded packet
over the X2 interface about 20 ms before receiving the handover completion message from a
UE. However, according to the site data, there is no data forwarded over the X2 interface.
When the delay is normal, there is data forwarded over the X2 interface. Therefore, the X2
link may be faulty.
The results of comparison between the IP address of the IP path over the X2 interface show
that the IP address of the IP address of the IP path over the X2 interface is set to the operation
and maintenance (OM) IP address. After the IP address of the IP path is changed, the
handover delay becomes normal (about 30 ms).
Conclusion
If the handover delay reaches 1s or more, verify that the port number, local IP address, and
peer IP address of the X2 link are correctly configured.
7.2.3 The Handover Delay Increases Due to Consecutive Error

CRC Packets in the Source Cell.
Channel quality indicators (CQIs) are not adjusted in a timely manner when the signal quality
fluctuates sharply. Consequently, error CRC packets occur consecutively in the source cell,
increasing the handover delay. Based on the signaling tracing results in the GENEX Probe,
the source cell receives the last packets on the data radio bearer (DRB) earlier than required.

LTE TDD
Solution
Since eRAN1.0 B060SPC350, the source cell instructs the target cell to use a low MCS
scheme at layer 2 when receiving the handover measurement report at layer 3. This ensures
the reliable data delivery in the source cell. The MCS scheme can be configured. Increase the
PDCCH power and set the CCE aggregation level to 8.
7.2.4 The Handover Delay Increases Due to Preamble

Retransmissions During Random Access.
The handover delay increases when preambles are retransmitted for multiple times during
random access.
Preambles are retransmitted per 20 ms, and can be retransmitted for a maximum of four times.
The handover delay increases by 20 ms per preamble retransmission.
Case 1: Preambles are transmitted for four times during random access. Due to preamble
retransmissions, the following intervals increase:
Interval between the time specified by MacRxLastSrbTime and the time specified by
MacSendMsg3Time
Interval between the time the last packet is transmitted and the time the handover command is
delivered (15.786 ms)

LTE TDD
Interval between the time the handover completion message is sent and the time the first
packet is received
Consequently, the handover delay exceeds 100 ms.
Case 2: Preambles are transmitted for twice, and the handover delay reaches 51.739 ms.

LTE TDD
Solution
Preambles are retransmitted due to the following possible causes:
 The channel quality is poor in the uplink.

 The channel quality is poor in the downlink so that no RAR is received.
Adjust coverage or handover configurations to ensure optimal channel quality at the moment
the UE is handed over.
7.2.5 The UE Does Not Send the PDCP Status Report Or Sends
the PDCP Status Report with Delay.
The UE does not send the PDCP status report or sends the PDCP status report with delay.
Consequently, after the timer expires in the target eNodeB, the target eNodeB sends the UE
the packets that the source eNodeB has sent to the UE, increasing the handover delay.
Run the LST TYPDRBRLCPDCP command to check whether the

PDCPSTATUSREPORTREQUIRE parameter is set to FALSE.
If the PDCPSTATUSREPORTREQUIRE parameter is set to FALSE, the UE does not send

the PDCP status report after being handed over, and the target eNodeB forwards to the UE the
data sent by the source eNodeB after receiving the handover completion message. Some of
these data have been received by the UE. Consequently, the PDCP delay increases.
Therefore, it is recommended that the PDCPSTATUSREPORTREQUIRE parameter be set

to TRUE.
When this parameter is set to TRUE, the UE sends the handover completion message
containing the PDCP status report to the target eNodeB. The target eNodeB starts the timer for
waiting the PDCP status report after receiving the packet endmarker forwarded by the source
eNodeB. Due to the retransmissions of handover completion messages caused by poor
channel quality, the target eNodeB receives the PDCP status report later than required.
Consequently, the target eNodeB transmits data to the UE later than required, increasing the
handover delay at the RLC and PDCP layer.
Solution
 Run the LST TYPDRBRLCPDCP command to verify that the

PDCPSTATUSREPORTREQUIRE parameter is set to TRUE.
 Decrease the number of the signaling retransmissions during random access and the
number of the retransmissions of handover completion messages.

LTE TDD
7.2.6 The System Information Update Conflicts with Handover

Command Processing on the UE.
The UE receives the handover command when it is updating system information, increasing
the handover delay.
Due to product architecture limitations, the UE supports only serial processing. If a handover
command is received during a system information update, the UE buffers the handover
command at layer 3, and processes it after the system information update is complete.
Consequently, the handover delay increases.
Solution
Since eRAN1.0 B060SPC360, if the UE receives an RRC reconfiguration message during its
system information update, the system information update is terminated and the UE processes
the RRC reconfiguration message immediately.

LTE TDD
Handover Performance Fault Diagnosis Guide A Acronyms and Abbreviations
A Acronyms and Abbreviations
3
3GPP 3rd Generation Partnership Project
A
ACK acknowledgement
ANR automatic neighbor relation
ARP Address Resolution Protocol
ARQ automatic repeat request
C
CCE control channel element
CIO cell individual offset
CQI channel quality indicator
CRC cyclic redundancy check
D
DL downlink
DRB data radio bearer
DTX discontinuous transmission
E-UTRAN evolved universal terrestrial radio access network

LTE TDD
eNodeB E-UTRAN NodeB
EPC evolved packet core
F
FTP File Transfer Protocol
G
GSM Global System for Mobile Communications
H
HARQ hybrid automatic repeat request
I
IBLER initial block error rate
ICIC inter-cell interference coordination
ID identity
IE information element
IP Internet Protocol
KPI key performance indicator
LMT local maintenance terminal
LTE Long Term Evolution
M
MAC Media Access Control
MCS modulation and coding scheme
MHz megahertz
MME mobility management entity

LTE TDD
MML man-machine language
MRO mobility robust optimization
MCS mobile switching center
N
NE network element
O
OM operation and maintenance
PC personal computer
PCI physical cell identifier
PDCCH physical downlink control channel
PDCP Packet Data Convergence Protocol
PDSCH physical downlink shared channel
PDU packet data unit
PRACH packet random access channel
PUSCH physical uplink shared channel
R
RAR random access response
RF radio frequency
RLC Radio Link Control
RRC radio resource control
RSRP reference signal received power
RSRQ reference signal received quality
S1AP S1 Application Protocol
SINR signal to interference plus noise ratio

LTE TDD
T
TA tracking area
TAC tracking area code
TAL tracking area list
TAU tracking area update
TD-SCDMA Time Division-Synchronous Code Division Multiple Access
TDD time division duplex
TS technical specifications
TTI transmission time interval
U
UDP User Datagram Protocol
UE user equipment
UL uplink
WCDMA Wideband Code Division Multiple Access


OMD - LTE TDD HandoverFault Diagnosis Guide-20130325-A-3.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMD - LTE TDD HandoverFault Diagnosis Guide-20130325-A-3.0

Uploaded by

Copyright:

Available Formats

LTE TDD

Handover Fault Diagnosis Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

People's Republic of China

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential i

About This Document

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential ii

About This Document .................................................................................................................... ii

1 Disclaimer Statement ................................................................................................................... 1

3.1.1 Handover Thresholds .............................................................................................................................. 4

3.2 Intra-Frequency Handover ............................................................................................................................... 5

3.2.1 Signaling Exchange for Intra-eNodeB Handovers .................................................................................. 7

3.2.2 Signaling Exchange for X2-based Inter-eNodeB Handovers .................................................................. 8

3.2.3 Signaling Exchange for S1-based Inter-eNodeB Handovers .................................................................. 9

3.3.1 Inter-Frequency Handover .................................................................................................................... 10

3.3.2 Inter-RAT Handover.............................................................................................................................. 12

3.3.3 Parameter Settings ................................................................................................................................ 13

3.4 Signaling Exchange on the User Plane ........................................................................................................... 16

4.2 Handover Delay on the Control Plane ............................................................................................................ 17

4.3 Handover Interruption Delay on the User Plane ............................................................................................ 18

4.3.1 Uplink Handover Interruption Delay at the Application Layer ............................................................. 19

4.3.2 Downlink Handover Interruption Delay at the Application Layer ........................................................ 19

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential iii

5 Methods for Locating Common Faults ................................................................................... 21

5.1.2 Signaling Faults over the X2 Interface .................................................................................................. 24

5.1.3 Signaling Faults over the S1 Interface .................................................................................................. 25

5.2.1 Locating Handover Delay Faults on the Control Plane ......................................................................... 29

5.2.2 Locating Handover Delay Faults on the User Plane ............................................................................. 29

6 Fault Locating Procedure ........................................................................................................... 31

6.1.2 Signaling Tracing on the UE ................................................................................................................. 32

6.1.3 Identification of Handover Messages .................................................................................................... 33

6.2.1 Measuring the Handover Delay at the IP Application Layer ................................................................. 35

6.2.2 Measuring the Handover Delay at the RLC Layer ................................................................................ 36

6.3 Recommended Solutions ................................................................................................................................ 38

7 Typical Cases ............................................................................................................................... 39

7.1.2 Random Access Fails. ........................................................................................................................... 43

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential iv

A Acronyms and Abbreviations .................................................................................................. 58

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential v

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 1

Mobility management is crucial in wireless communications. The access network must

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 2

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 3

3.1 Handover-related Parameters

 Intra-frequency handovers: event A3

3.1.1 Handover Thresholds

 Entering condition: Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off

For inter-frequency handovers, event A1 or A2 is used to trigger inter-frequency or inter-RAT

 Entering condition: Mn + Ofn + Ocn – Hys > Thresh

Inter-RAT handovers are triggered by event B1 and B2.

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 4

 Entering condition: Mn + Ofn – Hys > Thresh

The variables in the previous formulas are defined as follows:

 Mn is the measurement result of the neighboring cell.

3.2 Intra-Frequency Handover

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 5

Figure 3-3 Handover command reconfiguration message

Issue 3.0 (2013-04-28) Huawei Proprietary and Confidential 6

Figure 3-4 Measurement control reconfiguration message

Measurement control information is configured after a UE enters the network, regardless of

3.2.1 Signaling Exchange for Intra-eNodeB Handovers