Professional Documents
Culture Documents
All rights reserved. No distribution without prior permission of ZTE. © 2020 ZTE CORPORATION. I
Contents
1 HANDOVER OVERVIEW..................................................................................................1
1.1 NECESSITY FOR HANDOVER...............................................................................1
1.2 HANDOVER PROCEDURE.....................................................................................1
1.3 INTRA-LTE HANDOVER MEASUREMENT EVENTS.............................................1
1.4 HANDOVER CLASSIFICATION..............................................................................4
1.4.1 INTRA-SITE HANDOVER..............................................................................5
1.4.2 S1-BASED INTER-SITE HANDOVER...........................................................6
1.4.3 X2-BASED INTER-SITE HANDOVER.........................................................11
1.4.4 INTER-FREQUENCY HANDOVER.............................................................16
All rights reserved. No distribution without prior permission of ZTE. © 2020 ZTE CORPORATION. II
4.1.3 X2 INTERFACE SIGNALING ANALYSIS....................................................56
4.1.4 S1 INTERFACE SIGNALING ANALYSIS....................................................58
All rights reserved. No distribution without prior permission of ZTE. © 2020 ZTE CORPORATION. III
1 Handover Overview
Handover instructions are sent from the eNodeB side. UEs actively report their radio
conditions to the eNodeB, so that the eNodeB can determine that the UEs are
located on the cell edge. There are two types of reporting, event-triggered reporting
and periodic reporting. In most cases, event-triggered reporting is used, meaning
that the eNodeB sends predefined measurement control rules to UEs. If the
measurement result of a UE meets the threshold requirement in the rules, a
Measurement Report (MR) is triggered.
The LTE system sends measurement control rules to UEs. For the details of the
measurement control rules, refer to 2.2 Measurement Control. Measurement event
types are specified by these rules.
2. Event A2: The serving cell quality is lower than an absolute threshold (serving
< threshold). It can be used for starting an inter-frequency or inter-RAT
measurement and activating a gap.
3. Event A3: The quality of a neighbor cell is higher than the serving cell (neighbor
> serving + offset). It can be used for coverage-based inter-frequency or intra-
frequency handover.
4. Event A4: The neighbor cell quality is higher than an absolute threshold. It can
be used for inter-frequency handover and load-based handover.
5. Event A5: The serving cell quality is lower than threshold 1 (serving <
threshold1), and the neighbor cell quality is higher than threshold2 (neighbor >
threshold2). It can be used for coverage-based inter-frequency or intra-
frequency handover.
1. Event A1/A2 is often used for starting and stopping inter-frequency or inter-RAT
measurement. Inter-frequency and inter-RAT measurements have a large
effect on the current service rate, so the measurements should be started only
when necessary. Therefore, event A2 is defined. When a UE determines that
the serving cell quality is lower than a threshold, it reports an MR. When inter-
frequency or inter-RAT measurement is implemented for a UE, and the signal
quality of the UE is enhanced, no measurement is required. In this case, the UE
needs to notify the eNodeB of the signal quality, so event A1 is defined. When
the eNodeB receives the event A1 MR, it determines that the signal quality is
good, and inter-frequency or inter-RAT measurement can be stopped.
Mn+Ofn+Ocn−Hys>Thresh 2
Mn+Ofn+Ocn+Hys<Thresh 2
Intra-LTE handovers refer to handovers within the LTE system, including LTE FDD
(or TDD) intra-frequency and inter-frequency handovers, and handovers between
LTE FDD and LTE TDD.
Inter-LTE handovers refer to handovers between LTE and other radio system modes
(such as UMTS, GSM, and CDMA2000).
Depending on whether the UE is within the same MME, intra-LTE handovers can be
classified into intra-MME handovers and inter-MME handovers. In many cities, an
MME pool is used to establish the network, meaning that each eNodeB is connected
to multiple MMEs, so true inter-MME handovers rarely occur, and are not described
in this document.
Inter-RAT
UMTS<->LTE
handover
GSM<->LTE
eNodeB
Source Target S1 S11 S5
UE MME S-GW PDN-GW
CELL CELL
Handover
decision
Preparation Phase
Handover Request
Radio Resource
allocation
Handover Request ACK
RRC Reconfiguration
(Handover Command)
Handover Confirm(Synchronization,
Execution Phase
RRC Reconfiguration Complete)
Release Resource
Radio Resource
Release
As shown in the above figure, when the UE reports an MR, the eNodeB determines
that an intra-site handover is required, and sends a handover request to the target
cell. If the target cell is prepared, it notifies the source cell of its resource
information, and the source cell sends a reconfiguration message to the UE through
the Uu interface, notifying the UE to implement handover. After the handover is
completed, it is not required to notify the core network, because no S1/X2 link is
involved during the handover process.
S1-AP
SCTP
IP
Physical layer
GTP-U
UDP
IP
Physical layer
MME
S1 S1
X2
eNodeB2
eNodeB1
Uu
MME
S1 S1
X2
eNodeB2
eNodeB1
Uu
1. Interaction between the source eNodeB and the MME through the S1 interface
2. Interaction between the UE and the source eNodeB through the Uu interface
3. Interaction between the UE and the target eNodeB through the Uu interface
4. Interaction between the target eNodeB and the MME through the S1 interface
During S1 handover, a direct data forwarding path may exist between the source
eNodeB and the target eNodeB. Data forwarding in S1 handover can be classified
into direct forwarding and indirect forwarding. In S1 handover, the source eNodeB
may have data not sent to the UE. After the handover, the data can be directly or
indirectly forwarded to the target eNodeB. Direct forwarding means that the data is
forwarded through the X2 interface, which is the interface built on the user plane
(data transmission channel), and indirect forwarding means that the data is
forwarded through the S1 interface.
Upon receiving an MR and determining that handover is required, the source cell
where the UE is located determines whether the source cell and target cell are
within the same eNodeB. If they are not within the same eNodeB, the source cell
needs to determine the handover type. If the source cell determines that no X2
handover can be implemented, it initiates an S1 handover procedure.
2. The source eNodeB sends a Handover Required message to the MME through
the S1 interface. This message contains the eNB UE X2AP ID allocated by the
local eNodeB, MME UE S1AP ID allocated by the MME, and handover type,
handover cause, UE capability, and UE security information.
3. Upon receiving the Handover Required message, the MME sends a handover
request to the target eNodeB through the S1 interface. Upon receiving the
handover request, the target eNodeB creates a new DCI instance, allocates a
new GID and a new eNB UE S1AP ID, and stores UE parameters from the
source eNodeB.
5. The MME sends a handover command to the source eNodeB, and establishes
a forwarding tunnel.
7. The source eNodeB forwards data and sends the PDCP SNs of uplink and
downlink services to the MME through a UE status message.
8. The MME sends the PDCP SNs of uplink and downlink services to the target
eNodeB through an MME status message.
12. The target eNodeB sends a handover notify message to the MME through the
S1 interface, and sends uplink data to the core network.
13. The MME sends a UE Context Release Command message to the source
eNodeB, notifying the source eNodeB to release resources for the UE.
14. The MME responds with a UE Context Release Complete message, and the
source eNodeB releases memory resources and deletes the UE instance.
S1 S1
X2
eNodeB2
eNodeB1
Uu
MME
S1 S1
X2
eNodeB2
eNodeB1
Uu Uu
1. Interaction between the source eNodeB and the MME through the S1 interface
2. Interaction between the UE and the source eNodeB through the Uu interface
3. Interaction between the UE and the target eNodeB through the Uu interface
4. Interaction between the target eNodeB and the MME through the S1 interface
Upon receiving an MR and determining that handover is required, the source cell
where the UE is located determines whether the source cell and target cell are
within the same eNodeB. If they are not within the same eNodeB, the source cell
needs to determine the handover type (whether based on the X2 interface or S1
interface). If there is an X2 association between the source eNodeB and the target
eNodeB, and the two eNodeBs are connected to the same MME, then X2-based
inter-eNodeB handover is implemented. If there is no X2 association between them,
S1 handover is implemented.
1 Measurement Report
Determines X2 handover
2 handover Request
Admits the UE and allocates
dedicated resources
3 handover Request ACK
5 SN Status transfer
Detach from S-eNB
6 RA Preamble
7 RA Response
Deletes the
UE instance
Tips: X2-Based Handover Procedure
A normal X2-based handover procedure includes the following phases:
2. The source eNodeB sends a handover request message to the target eNodeB
through the X2 interface, which contains Old eNB UE X2AP ID allocated by the
source eNodeB, MME UE S1AP ID allocated by the MME, UE capability, UE
security, and UE history information, list of E-RABs to be established, and
destination address on the core network side for each E-RAB.
Upon receiving the handover request message over the X2 interface, the target
eNodeB creates a new DCI instance, allocates a new GID and a new eNB UE
X2AP ID, stores UE parameters from the source eNodeB, queries the database
to obtain admission parameters, admits the UE, and creates a service bearer
channel.
3. The target eNodeB sends a Handover Request Ack message to the source
eNodeB through the X2 interface, which contains the New eNB UE X2AP ID,
Old eNB UE X2AP ID, D-eNB admission success or failure information, and a
handover command to be sent by the source eNodeB to the UE. If non-
competitive handover is implemented, an RACH preamble is contained in the
handover command.
4. The source eNodeB receives the Handover Request Ack message over the X2
interface, retrieves the RRC connection reconfiguration data, and sends it to
the UE.
5. The source eNodeB stops downlink data transmission over the Uu interface
and uplink transmission data over the S1 interface, collects uplink and downlink
PDCP SNs, and prepares for data forwarding. The source eNodeB sends
uplink and downlink PDCP SNs to the target eNodeB through an SN Status
Transfer message.
9. The target eNodeB sends a Path Switch Request message to the MME, which
contains the MME UE S1AP ID on the source side, eNB UE S1AP ID allocated
by the target eNodeB, Switch-required E-RAB information, and UE security
information.
10. The MME sends a Path Switch Request Ack message to the target eNodeB,
which contains Path Switch success or failure information. Upon receiving the
message, the target eNodeB determines whether the destination address on
the uplink transport layer on the core network side is changed. If the destination
address is changed, a bearer channel needs to be established.
11. The target eNodeB sends a UE Context Release message to the source
eNodeB through the X2 interface, notifying the source eNodeB to release the
resources and delete the UE instance.
The largest difference between the X2 and S1 handover procedures lies in the
moment of interaction between the radio access network and the core network. In
S1 handover, the source eNodeB establishes a connection with the target eNodeB
through the core network. In X2 handover, the source eNodeB directly interacts with
the target eNodeB, and notifies the core network after handover.
Data configuration is the same for X2 and S1 handovers. The neighbor cell
parameter whether to support X2 handover is set to yes by default. Whether X2
handover or S1 handover is implemented depends on the existence of an X2
association. If there is an X2 association, the system preferably implements X2
handover.
(2) The UE state changes to RRC_IDLE (it is not required to notify the UE to
release measurement through a message. The eNodeB releases the
measurement).
For inter-frequency handover measurement, the eNodeB needs to deliver event A1-
based and event A2-based measurement configuration data to the UE. The event
A2-based configuration is used for the UE to start inter-frequency measurement, and
the event A1-based configuration is used for the UE to stop inter-frequency
measurement. When the UE meets the event A2 condition, the UE reports an MR
message to the eNodeB, and the eNodeB sends new inter-frequency measurement
configuration (based on event A3) to notify the UE to periodically search for other
eNodeBs. When the signal strength of another eNodeB and the local cell meet event
A3 condition, the UE reports an MR message, and the eNodeB makes a handover
decision and starts inter-frequency handover.
For example,
If the thresholds for event A2 and event A1 are -115 dBm and -105 dBm
respectively, when the UE detects the RSRP of the serving cell is lower than -115
dBm, event A2 is triggered. The UE reports an MR message to the eNodeB,
notifying the eNodeB that the signal quality is poor. The eNodeB sends new
measurement configuration (based on event A3) to the UE, which contains the
target frequency points to be searched for (maximum: 8), search gap, A3 offset (for
example, 3 dB), lag (for example, 0), and TTT (for example, 320 ms). The eNodeB
also sends event A1 measurement configuration, where the threshold is -105 dBm.
When the UE detects a PCI signal on a target frequency point and determines that
the signal strength is 3 dB higher than the PCI signal strength of the serving cell,
which lasts for 320 ms, the UE resends an MR message to the eNodeB. The
eNodeB makes an inter-frequency handover decision.
If the UE fails to detect any strong inter-frequency signal, and the signal quality of
the serving cell becomes good when the UE moves (-100 dBm) and is higher than
the event A1 threshold -105 dBm, then event A1 is triggered. The UE reports a new
MR message to the eNodeB, and the eNodeB sends new measurement
configuration to the UE to stop the inter-frequency measurement (based on event
A3), because the inter-frequency measurement affects the service rate on the UE.
2 Intra-LTE Handover Procedures and Analysis
UL allocation Legend
L3 signalling
2. Measurement Reports
L1/L2 signalling
3. HO decision
User Data
4. Handover Request
Handover Preparation
5. Admission Control
6. Handover Request Ack
DL allocation
RRC Conn. Reconf. incl.
7.
mobilityControlinformation
Detach from old cell
Deliver buffered and in transit
and
packets to target eNB
synchronize to new cell
Handover Execution
8. SN Status Transfer
Data Forwarding
packet data
packet data
12. Path Switch Request
13. User Plane update
request
End Marker
14. Switch DL path
Handover Completion
packet data
End Marker
15.User Plane update
response
16.Path Switch Request Ack
18. Release
Resources
When a UE enters RRC Connected state for the first time, the eNodeB sends the
first RRCConnectionReconfiguration message to the UE for configuring handover
measurement events. When the UE moves to the target cell, the UE detects that the
signal strength of the target cell is better than that of the source cell, and the
condition of measurement event reporting is met, so the UE sends an MR to the
source cell. The source cell requests handover resources from the neighbor cell with
the best signal quality. The neighbor cell with the best signal quality starts admission
control. If it admits the UE, a handover is implemented. If it rejects the UE, the
source cell requests handover resources from the neighbor cell with the second best
signal quality. The UE receives the RRCConnectionReconfiguration message
containing mobility control information from the source cell, and tries to access the
target cell (perform a handover). After the handover is completed, the UE sends an
RRCConnectionReconfigurationComplete message to the target cell.
It can be concluded that intra-LTE handover is led by the eNodeB and assisted by
the UE. The eNodeB sends measurement configuration information to determine
what and how the UE is to measure and report. Upon receiving the measurement
configuration information, the UE performs measurements and reports MRs when
necessary (event conditions are met). The eNodeB makes handover decisions or
other actions (for example, starting or stopping inter-frequency measurement) in
accordance with the measurement result that the UE reports.
Figure 2-18 S1 Handover Signaling (2): Handover Command Message Received by the eNodeB
The Handover Command message received over the S1 interface contains target
RRC resource information used for constructing an RRCConnectionReconfiguration
message.
Figure 2-19 S1 Handover Signaling (3): RRCConnectionReconfiguration Message Sent by the
eNodeB
Note: In some measurements, the measurement object may be only one cell,
for example, the measurement for reporting neighbor cell system information or
delay of transmission between the serving cell and the UE.
According to Section 8.1.2.1 of the 3GPP 36.133 protocol, in gap mode 0, the
measurement window is 6 ms and the measurement period is 40 ms, and in gap
mode 1, the measurement window is 6 ms and the measurement period is 80 ms.
The third parameter measurement identities (measurement IDs) are used as index
numbers and measurement object and configuration associations. For example, if
there are three measurement objects and two reporting configurations, then there
are a maximum of six measurement IDs.
As shown in the above figure, the measurement configuration includes the following:
measurement object, reporting configuration, measurement ID, quantity
configuration, and s-Measure. There is only one MeasID (measurement ID), which
links measurement object 1 with reporting configuration 1.
The above figure shows an intra-RAT measurement, and no inter-frequency or inter-
RAT neighbor cells are configured, so the system does not send the gap
configuration (measGapConfig). Instead, the system sends the s-Measure field.
The s-Measure field is described as follows:
… … …
Note: Suppose the RSRP reported value is X, and the actual value is about X – 140
dBm (between (X – 141) dBm and (X – 140) dBm).
In the above figure, the MeasID parameter (MeasId = 1) corresponds to the MeasId
in the MR that the UE reports.
If the neighbor cell configuration is missing, the handover decision may fail. In some
cases where faults occur, the system may consider it unsuitable to perform
handover. These cases need to be further analyzed.
In handover preparation, the eNodeB of the serving cell requests the eNodeB of the
target cell to prepare handover resources through the X2 or S1 interface. In intra-
eNodeB handover, the serving cell requests the target cell to prepare handover
resources.
A timer is started for handover preparation. If no message is received from the target
eNodeB or MME within the timer duration, the system times out, and it is defined as
a failure.
If a rejection message is received from the target eNodeB or MME within the timer
duration, it is also defined as a preparation failure.
Incorrect neighbor cell configuration, for example, incorrect PCI or TAC, resulting in
that the MME cannot match the correct cell
Note:
1. As shown in the above figure, the source cell sends the RRC resource
information of the target cell (PCI = 94), so that the UE can access the target
cell.
1. The frequency and PCI of the neighbor cell are the same as the source cell,
resulting in the source being unable to deliver the MobilityControl field to the
correct target cell, so the UE cannot access the correct target cell. An RRC
connection is reestablished on the source cell.
2. In a high-speed scenario (high-speed rail or free way), the target cell with good
signal quality has a small coverage. When the source cell delivers the
MobilityControl parameter, the signal quality changes abruptly (very good to
very poor), and the UE cannot access the target cell, and an RRC connection is
reestablished on the source cell.
Note: The RRC_TransactionIdentifier field is 1, which agrees with the same field in
the corresponding RRCConnectionReconfiguration message.
3 Handover Parameter Setting Instructions
Neighbor cell configuration requires two steps: neighbor cell configuration on the
eNodeB layer, and neighbor relationship configuration on the cell layer, where
neighbor relationship configuration is a subset of the neighbor cell configuration.
The following uses the E-UTRAN FDD neighbor cell list as an example. Click the
New button at the left upper corner. The dialog box for adding a neighbor cell is
displayed.
Figure 3-26 Adding a Neighbor Cell
Cell ID
Set the bandwidth and central frequency of the neighbor cell as required.
The parameters of an E-UTRAN TDD neighbor cell are the same as those of an E-
UTRAN FDD neighbor cell.
3.1.2 Neighbor Relationship
After neighbor cell configuration, select the eNodeB, and select Modify Area >
Wireless Parameter > E-UTRAN FDD Cell > Neighbor Relationship Config > E-
UTRAN Neighbor Relationship. See the following figure.
Note: The neighbor relationship is specific to each cell, and the neighbor
relationships of all the cells are contained in the list.
FDD LTE intra-frequency and inter-frequency neighbor cells and TD-LTE neighbor
cells are contained in the list.
In the above figure, three parameters are underlined, and correspond to the intra-
site neighbor cell, FDD LTE neighbor cell, and TD-LTE neighbor cell respectively.
Click next to each parameter to select a neighbor cell from the existing
Select a neighbor cell, and click OK. Set other parameters as required. In general,
Description
Setting
Description
In accordance with 3.3, event A3 is triggered when the quality of a neighbor cell
is offset higher than the serving cell, and the offset is indicated as Off in the
following formula (also indicated as a3-Offset):
Mn+Ofn+Ocn−Hys>Ms+Ofs+Ocs+Off
Setting
Based on the formula of entering condition for event A3, a larger a3-Offset
value requires a bigger difference of the signal strength between the neighbor
cell and the serving cell for triggering event A3–based handover, and means a
later reporting of the measurement result (handover request).
In general, a3-Offset is set to 3 or 4 dB, and it is not recommended that you set
it to any other value greater than 3 or 4 dB. To avoid frequent handovers, a3-
Offset cannot be too small. If you need to accelerate measurement reporting,
you can modify the neighbor cell individual offset parameter defined in Section
3.2.3.1.
3.2.1.3 TimeToTrigger
Description
Setting
3.2.1.4 Hysteresis
Description
In accordance with the formulas of entering and leaving conditions for event A3
in Section 1.3, the Hysteresis parameter is a threshold for controlling the
entering and leaving of event A3, and decides the time for which the UE
resides in event A3. See the following figure.
Mn Ofn Ocn
Enter
Hysteresis
Leave
Mn Ofn Ocn
Setting
This parameter determines the signal strength interval that makes the UE
reside in event A3. A greater value means a higher signal strength of the
neighbor cell required for entering of event A3 (meaning a later handover) and
a lower signal strength of the neighbor cell required for leaving of event A3
(meaning a long period for which the UE resides in event A3). It is
recommended that the default value be kept for this parameter.
3.2.1.5 ReportOnLeave
Description
This parameter specifies whether to send a measurement report when the UE
leaves event A3. Leaving condition for event A3:
Mn+Ofn+Ocn+Hys<Ms+Ofs+Ocs+Off .
Setting
Description
Setting
Description
In the LTE system, the measurement result reported by a UE is the value after
layer 3 filtering, and an L3 filter is used to avoid the contingency of a single
measurement. The UE uses the following formula to filter the measurement
result:
Fn is the filtered measured value, which is matched with the report criteria and
reported in the measurement report.
Fn-1 is the measured value obtained after the preceding filter is applied. It should
be noticed that F0 = M1, meaning that the first measurement result is the value
measured on the physical layer.
Setting
If the filter coefficient is 0, layer 3 filtering is not applied, meaning that each value
reported by the UE is the value measured on the physical layer.
k = 1:
Fn =(1−a )⋅F n−1 +a⋅M n
k = 2:
Fn =(1−a )⋅F n−1 +a⋅M n
k = 3:
Fn =(1−a )⋅F n−1 +a⋅M n
k = 4:
Fn =(1−a)⋅F n−1+a⋅M n
A larger filter coefficient means that the current measurement result on the physical
layer is less relevant to the filtered value (which is more relevant to historical
measurement results).
In a fast fading scenario (for example, at the corner or through a shadow area), it is
recommended that the layer 3 filter coefficient be reduced (set to 1 or 0), so that the
filtered value is more close to the current measurement result on the physical layer.
Setting
This parameter is an enumerated type, and its options include -24,-22,-20, -18,
-16, -14, -12, -10, -8, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 8, 10, 12, 14, 16, 18,
20, 22, and 24 (dB).
Description
The a3-Offset is a parameter common to all the neighbor cells. It is not proper
to modify a3-Offset to increase the handover threshold flexibility and adjust the
thresholds for handovers to some specific neighbor cells. In this case, you can
set the CIO of a specific neighbor cell.
Setting
This parameter is an enumerated type, and its options include -24,-22,-20, -18,
-16, -14, -12, -10, -8, -6, -5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5, 6, 8, 10, 12, 14, 16, 18,
20, 22, and 24 (dB).
To accelerate handovers from the serving cell to a neighbor cell (reduce the
handover threshold), you can increase the CIO of the neighbor cell (which is
normally in the range of 1 to 3 dB). At corners or in deep fading scenarios, the
signal quality of the target cell is also not good. To avoid fast fading of the
signal strength of the serving cell that results in handover failure, you can
modify the CIO of the neighbor cell, so that the UE is handed over to the target
cell earlier before the signal quality of the serving cell declines.
In case of
cell
change
order from
E-UTRA
or intra E-
UTRA
handover,
initiate the
RRC
Criterion for
Reception of connectio
successful
RRCConnectionRec n re-
completion of
onfiguration establishm
handover within E-
message including ent
Timer of waiting for UTRA, handover to
the MobilityControl procedure;
T304 handover success E-UTRA or cell
Info or reception of In case of
(ms) change order is met
MobilityFromEUTRA handover
(the criterion is
Command message to E-
specified in the
including UTRA,
target RAT in case
CellChangeOrder. perform
of inter-RAT).
the
actions
defined in
the
specificati
ons
applicable
for the
source
RAT.
Reception of an
Timer of waiting for RRCConnectionRec
The eNodeB sends
the onfiguration
an Perform
rrcReCfgTi RRCConnectionRec Complete message
RRCConnectionRec exception
mer onfiguration from the UE or as
onfiguration handling.
Complete message stopped by the
message to the UE.
(ms) RRCConnectionRec
onfiguration request.
Settings
Defaul
Timer Setting
t
pingPongTmr [0..30] 2
4 Handover Problem Analysis
Handover problems are analyzed through signaling procedures.
Start
Yes
Yes
Refe
Yes
Yes
End
There are many handover failure causes. This document describes only common
causes. The general analysis flow is the same: Based on the typical signaling
procedure, analyze detected signaling messages and signaling messages traced on
the network management system, find exceptions, and determine the failure cause.
4.1.1.1 Measurement Report Loss
Start
Measurement control?
No
Check measurement control
Yes
1. If the UE sends an MR message, but the eNodeB does not receive the
message, it may be caused by the following:
(3) Poor downlink quality, resulting in that the UE fails to demodulate the
downlink, and cannot obtain the uplink scheduling information
2. If the UE does not send any MR message, perform the following checks:
The UL grant in the measurement report that the UE sends is not received, and the
PDCCH is restricted.
The eNodeB does not receive the measurement report from the UE, or receives the
measurement report but the CRC is incorrect, and the PUSCH is restricted.
Data loss occurs between internal layers of the UE. For example, when the L3
requests the L2 to send a measurement report, the L2 fails.
The configuration is incorrect, resulting in that the measurement control rules fail to
be sent to the UE. The UE keeps initiating reestablishment requests and cannot
make a further step to send a measurement report.
Start
Handover No
Check whether the target
decision accepted
cell is configured or in
on the source
the blacklist?
side?
Yes
End
1. Check whether the source eNodeB sends a handover request to the target
eNodeB or MME. If it sends a handover request, it indicates that the handover
decision on the source eNodeB is accepted. Check whether the neighbor cell is
configured or is in the handover blacklist.
2. If the target eNodeB sends a rejection message to the source eNodeB or MME,
it indicates that the handover preparation on the target eNodeB fails. Check
resources and X2/S1 link status.
7. The TAC configuration of the neighbor cell is different from that on the MME, so
no handover command is sent.
Yes
Improve uplink
coverage
The eNodeB does not receive the PREAMBLE of the UE on the target cell, and the
uplink PRACH is restricted.
RSRP: downlink pilot received power. The pilot channel quality is different from the
data channel quality. However, the data channel quality can be roughly learnt about
by referring to the pilot channel RSRP and SINR. If RSRP > –85 dBm, the user is at
a nearby place. If RSRP = –95 dBm, the user is at a middle-distance place. If RSRP
< –105 dBm, the user is at a far place. The user location cannot completely
determine the channel quality. In the load scenario, it is possible that users at the
middle-distance and nearby places still have poor channel quality (when the
neighbor cell's RSRP is close to the serving cell's RSRP, there is large interference).
Other parameters are required to determine the channel quality.
SINR: downlink pilot SINR. You can roughly learn about the data channel condition
through the pilot SINR. If SINR < 0 dB, it indicates that the downlink channel quality
is not good. If SINR < -3 dB, it indicates that the downlink channel quality is very
bad, easily causing handover signaling loss and resulting in handover failure.
BLER: In normal cases, the BLER should converge toward the target value (10%. If
the channel quality is very good, the BLER is close to or equal to 0%). If there is a
large BLER value, it indicates that the channel quality is not good and there are
many data errors, easily causing connection release, handover failure, or a large
handover delay. The downlink BLER can be obtained from front-end test data.
In RF optimization, when the neighbor cells and resources are normal, the following
cases may occur based on the handover parameters and coverage condition:
4.1.2.1 Early Handover
When the signal quality of the neighbor cell is improper or unstable, the eNodeB
initiates a handover, and this is called an early handover. Early handovers include
the following:
1. After the source cell sends a handover command, the signal quality of the
target cell is not good, and the UE fails to be handed over to the target cell. The
UE initiates RRC connection reestablishment to go back to the source cell. In
this case, the handover fails because the UE fails to be handed over to the
target cell by random access or sending msg3, and the UE initiates an RRC
connection reestablishment request to the source cell.
2. The UE is successfully handed over to the target cell, but downlink out-of-sync
occurs immediately, so the UE initiates an RRC connection reestablishment
request in the source cell. This is also defined as an early handover.
3. The UE is successfully handed over to the target cell, but it is handed over to a
third-party cell within a very short time. This is also defined as an early
handover.
1. In the 100% downlink load scenario, the service quality of the source cell is not
good (if SINR < –3, it is probable that handover commands may fail to be
sent), and the UE fails to receive a handover command or fails to perform
random access upon receiving the handover command. In this case, the UE
initiates an RRC connection reestablishment request to the target cell. A
context is established in the target cell, so the reestablishment can succeed.
2. Before the UE sends a measurement report, the signal quality of the source cell
abruptly declines, resulting in downlink out-of-sync. In this case, the UE directly
initiates an RRC connection reestablishment request to the target cell. No UE
context exists in the target cell, so the reestablishment is rejected.
4.1.2.3 Ping-Pong Handover
1 Measurement Report
Determines X2 handover
2 handover Request
Admits the UE and allocates
dedicated resources
3 handover Request ACK
5 SN Status transfer
Detached from S-eNB
6 RA Preamble
7 RA Response
Deletes the
UE instance
(1) The eNodeB fails to process the measurement report, for example, the
neighbor cell configuration is missing or its internal module fails.
(2) The X2 interface does not operate properly, for example, packet loss
occurs.
(1) The source cell does not operate properly. Before the target cell
responds to the handover request, the source cell sends a HANDOVER
CANCEL command to the target cell through the X2 interface.
(2) The target cell fails to prepare for handover. In this case, a HANDOVER
PREPRATION FAILURE message is transmitted through the X2
interface.
(3) The X2 interface does not operate properly, for example, packet loss
occurs.
(1) The X2 interface does not operate properly, for example, packet loss
occurs.
4. The loss of the UE context release message may be caused by the following:
(1) The X2 interface does not operate properly, for example, packet loss
occurs.
(2) Upon receiving the handover complete message, the target cell fails to
process the message, resulting in failure in S1 PATH handover.
If the device rejects the handover request, find out why the device rejects the
request.
For signaling message rejection or loss on the S1 interface, you need to trace
signaling of multiple NEs to locate the causes.
5 Handover Problem Positioning
The network management system provides lots of handover timers and performance
indicators. If the handover success rate is low, analyze the performance statistics to
find out reasons. Performance statistics analysis for LTE handover problems is
similar to that for 2G/3G handover problems. Determine the sub-scenario that has
the largest effect on general indicators, and perform related tests, analysis,
adjustment, and checks.
The handover success rate can be analyzed from the following aspects:
Failure causes: Determine the major failure causes, so that you can further
determine the specific step that causes the failure. For example, a handover
includes handover preparation and handover execution. Determine whether it is a
handover preparation failure or handover execution failure. If it is a handover
preparation failure, the failure is not related to the radio network.
Neighbor cells: If the handover success rates of a few cells are low, locate the
involved target cells through cell pair statistics. For example, if a cell can
successfully hand over UEs to target cells, but UEs cannot be handed over to this
cell, then the cell pair statistics show that the handover success rates are low of this
cell serves as the target cell.
Users: Find out the users with a high handover success rate and those with a low
handover success rate. This requires the assistance of CDT data.
Other associated features: Handovers are associated with many other features,
including the following:
Uplink RSSI
(1) Use drive testing software to check whether the neighbor cell
configuration is missing or incorrect.
(5) Check the data consistency of external cells, and check far neighbor
cells, nearby neighbor cells with missing configuration data, and PCI
conflicts.
(6) Determine the missing neighbor cells through drive testing data.
Handover Problem
Analysis
Whether 100%
handover failure?
Handle
Checkneighb
Whether congestion congestion
Whether neighbor cell or
improper relationship
configuration
Check
Whether handover handover
parameters improper parameters
Handle
Whether coverage coverage
problem? problem
Handle the
Whether uplink/ uplink/
downlink interference downlink
interference
5.4 Handover Problem Checklist
This checklist is provided for reference only, and does not include all the conditions
that may cause handover failures. However, it includes common handover failure
causes.
No Sub- Exception
Category Item Description
. Category Handling
Check Check
whether the whether the
Cell target cell RRU power
2 Diagnosis test.
hardware has output of the
hardware target cell is
faults. proper.
3 Check Based on
whether performance
MSG1 and statistics, check
MSG3 of the whether MSG1
target cell are is proper. There
proper. are lots of MSG1
detection
success records.
The number of
times that the
No Sub- Exception
Category Item Description
. Category Handling
eNodeB sends
MSG2 is nearly
0, the maximum
throughput on
the
downlink/uplink
PDCP layer is
nearly 0, and the
number of
MSG1 detection
success records
is over 3000
times of the
number of times
that the eNodeB
sends MSG2.
Check whether
MSG3 is proper.
There are
thousands of
MSG1 detection
success records
and MSG2
transmissions,
the number of
MSG3 detection
success records
is nearly 0, the
maximum
throughput on
the
downlink/uplink
PDCP layer is
nearly 0, and the
number of
MSG2 detection
success records
is over 3000
No Sub- Exception
Category Item Description
. Category Handling
times of the
number of
MSG3 detection
success records.
Check the
Check
transmission
whether
quality of the IP channel
Transmissio packet loss or
source check in the
n quality a large delay
eNodeB and diagnosis test.
occurs during
target
transmission.
eNodeB.
Check the
performance
statistics. If there
is high usage,
check whether
Check
the CFI
whether
parameter is
PDCCH
5 dynamically
congestion
adjusted, and
occurs on the
check whether
target cell.
congestion
occurs on the
cell based on
other
parameters.
maximum
number of RRC
connections of connections
the target cell allowed for the
exceeds the cell in the AC,
threshold. which is
specified by the
license.
Check the
performance
statistics. If the
PRB usage is
high, and the
traffic is heavy, it
indicates
congestion
occurs on the
cell. Increase
Check the
the difficulty of
7 PRB usage of
handover to the
the target cell.
cell and reduce
the difficulty of
handover from
the cell by
adjusting
handover
parameters, and
adjust heavy
traffic prevention
parameters.
Check the
Check the
number of
9 performance
activated
statistics.
users.
Improper PLMN
setting may
cause access
Check PLMN
failure. The
settings
11 PLMN on the
involving the
core network
target cell.
side must be the
same as that on
the target cell.
If inter-frequency
Check
measurements
whether the
are started late,
threshold for
the signal quality
12 starting inter-
of the source
frequency
cell may be very
measurement
poor before
s is proper.
handover.
13 Check Inter-frequency
whether the measurement
No Sub- Exception
Category Item Description
. Category Handling
configuration is
used in intra-LTE
redirection and
ANR. If the
configuration is
inter-
improper, inter-
frequency
frequency
measurement
measurement
configuration
errors may
is proper.
occur. Check the
central
frequency,
bandwidth, and
frequency offset.
Handover
Check configuration is
whether intra- used for
frequency and handover
inter- decision. Check
frequency whether the
14 handover delay and offset
configurations parameters are
are proper proper, and
(configuration whether the
IDs 50 and handover event
70) and function are
correct.
relationship for
the cell under
OMMB A are not
changed and
need to be
manually
adjusted. In
addition, check
the TAC, PLMN,
and eNodeBID
parameters.
Check
Check the
whether a
neighbor cell
neighbor cell
17 relationship list,
with the same
and change the
frequency and
conflicting PCI.
PCI exists.
19 Check A PRACH
whether parameter
PRACH conflict
parameters increases the
are proper. probability of
Preamble
detection failure.
PRACH
parameters can
be bound with
PCI. Check
whether the
PRACH
No Sub- Exception
Category Item Description
. Category Handling
parameters of
the source and
target cells
conflict, and
whether the
logic root
sequence, NCS,
and prach
configuration
index
parameters of
the two cells are
the same.
Trace signaling
based on front-
end logs and
back-end
network
management
Check system data.
Check the whether the Check whether
control-plane control-plane timer timeout is
20
and UE and UE timers caused by the
timers. are properly S1 or X2 delay.
set. Check
rrcReCfgTimer
and T304
settings, and
adjust the
settings if
necessary.
handover failure
due to abrupt
signal
deterioration.
Improve
coverage by
Check
adjusting power
whether there
22 and the antenna
is poor
downtilt angle,
coverage.
and increasing
sites.
Improve the
coverage
condition by
adjusting the
power and
antenna downtilt
angle. For inter-
vendor super-far
coverage
Check (restricted by the
whether there time alignment
23
is super-far parameter of the
coverage. other vendor),
you can adjust
the CIO of the
source cell for
the neighbor cell
of the other
vendor, and
disable ANR
self-deletion for
the source cell.
frequent
handovers.
Optimize indoor
coverage,
indoor-to-
Check outdoor CIO,
Check whether there and inter-
indoor is indoor frequency
25
distribution distribution measurement
coverage. signal parameters.
leakage. Reduce or avoid
handover of an
outdoor UE to
an indoor cell.
satisfactory.