03 - Fo - Nast3101 - c01 - 1 Lte Handover Analysis (Ppt+Notes) 58-Final

LTE Handover Analysis
Objectives
 To learn about the handover concept, category, and
steps
 To learn about the signaling flows of intra-base
station handover, X2 handover, and S1 handover
 To learn about analysis of typical handover signaling
 To learn about common factors that affect handovers
 To learn about the general ideas of handover
optimization and analysis of common handover
problems
2
Contents
 Handover Principle
 Handover Signaling Flows
 Handover Optimization Ideas
 Handover-Related Wireless Parameters
 Analysis of Common Handover Problems
3
Overview of LTE Handover
Purpose of Handover
 Keeping continuous conversation while the terminal is in motion
 Improving network service quality
 Reducing call drop rate
 Reducing congestion rate
LTE Handover Mode
 LTE uses a mobile-assisted backward hard-handover technology
 Mobile Assisted Handoff (MAHO): Both the network and the mobile terminal measure the radio link
parameters (uplink and downlink). The mobile terminal periodically reports downlink measurement reports to
the network, and the network performs the handover decision according to the measurement results of the
uplink and the downlink.
The advantage of this mode is low signaling load and short handover delay.
 Backward handover: The information related to the handover and between the mobile terminal and the
network is exchanged through the old path. The source base station initiates the handover procedure and is
responsible for sending the terminal's context information to the target base station.
The advantage of this mode is that the link with the source cell can be restored after the handover failure.
© ZTE All rights reserved 4
LTE Handover Category
The LTE system handover may be categories in different ways
 By wireless standard: Whether Within TD-LTE system

the system
 Intra-LTE handover: Handover is changed TD-LTE <--> FDD LTE handover
inside the LTE TDD (or FDD) system,
handover between LTE FDD and Intra-base station handover
LTE TDD systems. Whether
cross-eNB
 Inter-LTE handover: Handover Inter-base station handover
between an LTE system and a Category of
UMTS, GSM, CDMA2000 or other intra-LTE Co-frequency handover
systems. Handover handovers Whether
frequency is
 By reasons that trigger a changed Inter-frequency handover
handover: Whether Intra-MME handover

 Coverage-based handover cross
MME Inter-MME handover
 Load-based handover
 Traffic-based handover
TD LTE<-->TDS
Inter-system handover TD LTE<-->GSM
TD LTE<-->UMTS
TD LTE<-->CDMA

Contents
 Handover Signaling Process
 Handover-related Wireless Parameters
6
LTE Handover Types
Intra-eNB handover
 Intra-eNB handover refers to a handover among
multiple different cells of an eNB. So the flow is
slightly different from the inter-eNB handover:
The preparation messages for intra-base station
handover are not transmitted through the S1 or
X2 interface, but rather the inter-board
information exchange
 When the UE reports the MR message and the

base station decides that it needs to perform an
intra-eNB handover, it then directly request for a
handover through inter-board message exchange
to the target cell If the target cell is ready, it will
inform the source cell of the resource information.
The source cell sends a reconfiguration message
to the UE instructing the terminal to perform a
handover.

LTE Handover Types
Intra-eNB handover
 Intra-eNB handover refers to a handover among
multiple different cells of an eNB. So the flow is
slightly different from the inter-eNB handover:
The preparation messages for intra-base station
handover are not transmitted through the S1 or
X2 interface, but rather the inter-board
information exchange
 When the UE reports the MR message and the

base station decides that it needs to perform an
intra-eNB handover, it then directly request for a
handover through inter-board message exchange
to the target cell If the target cell is ready, it will
inform the source cell of the resource information.
The source cell sends a reconfiguration message
to the UE instructing the terminal to perform a
handover.

LTE Handover Types
Inter-eNB X2 handover
 The whole process involves the cooperation of the UE eNB1 eNB2 MME
source eNB and all the subsystems in the target 1 Measurement Report
eNB, the MME/S-GW and the handover UE. Judge for X2 handover
2 handover Request
 If the source cell in which the UE is located Accept, allocate dedicated
resource
receives the triggered measurement report and 3 handover Request ACK
determines that a handover is required, it first 4 RRC connection Reconfiguration
determines whether the source cell and the target

5 SN Status transfer
cell are in the same eNB. And if not, the decision Detach from S-eNB
6 RA Preamble
about handover mode (based on X2 or S1 port) is
7 RA Response
required.
8 RRC connection Reconfiguration Complete
 If there is X2 connection available between the
source cell and the eNB where the target cell is
9 Path Switch Rrquest
located and connected to the same MME, X2-
10 Path Switch Rrquest ACK
based handover between eNBs may be performed. 11 UE context release
Otherwise, the handover between the eNBs based
on S1 will be performed. Delete Ue
instance

LTE Handover Types
Inter-eNB X2 handover
 The whole process involves the cooperation of the UE eNB1 eNB2 MME
source eNB and all the subsystems in the target 1 Measurement Report
eNB, the MME/S-GW and the handover UE. Judge for X2 handover
2 handover Request
 If the source cell in which the UE is located Accept, allocate dedicated
resource
receives the triggered measurement report and 3 handover Request ACK
determines that a handover is required, it first 4 RRC connection Reconfiguration
determines whether the source cell and the target

5 SN Status transfer
cell are in the same eNB. And if not, the decision Detach from S-eNB
6 RA Preamble
about handover mode (based on X2 or S1 port) is
7 RA Response
required.
 If there is X2 connection available between the
source cell and the eNB where the target cell is
9 Path Switch Rrquest
located and connected to the same MME, X2-
10 Path Switch Rrquest ACK
based handover between eNBs may be performed. 11 UE context release
Otherwise, the handover between the eNBs based
on S1 will be performed. Delete Ue
instance

LTE Handover Types
Inter-base station S1 handover
UE eNB1 eNB2 MME
1 Measurement Report
2 handover Require
Judge for S1 3 handover Request
handover
Allocate dedicated resource
4 handover Request ACK
5 handover Command
6 RRC connection Reconfiguration

7.eNB Status transfer
8.MME Status transfer
Detach from S-eNB
9 RA Preamble
10 RA Response

12 handover notify
13 UE context release Cmd
14 UE context release Complete

Delete Ue
instance
 After comparing the X2 handover with the S1 handover, you can see that the largest difference between
them is the timing of information interaction between the radio side and the CN. In S1 handover, the
source eNB sets up a connection with the destination eNB and allocates resources through the CN; in X2
handover, the source eNB and the destination eNB directly communicate and negotiate with each other
and then inform the CN after the handover is completed.

LTE Handover Types
Inter-base station S1 handover
UE eNB1 eNB2 MME
1 Measurement Report
2 handover Require
Judge for S1 3 handover Request
handover
Allocate dedicated resource
4 handover Request ACK
5 handover Command
6 RRC connection Reconfiguration

7.eNB Status transfer
8.MME Status transfer
Detach from S-eNB
9 RA Preamble
10 RA Response

12 handover notify
13 UE context release Cmd
14 UE context release Complete

Delete Ue
instance

LTE Handover Process
Handover steps
 Measurement
 Measurement configuration: The eNB notifies the measurement configuration message to the UE,
that is, to deliver the measurement control message.
 Measurement implementation: The UE makes measurements on the current serving cell.
 Measurement report: When the measurement report conditions are met, the UE fills the
MeasurementReport with the measurement result and sends it to the eNB.
 Preparation
 The eNodeB makes a decision of the UE handover based on the measurement report and the radio
resource management information. When the eNodeB considers that a handover is necessary, it
determines an appropriate target cell, and requests access to the target cell.
 The target cell performs resource access and allocates air interface resource and service bearer
resource for UE access
 Implementation
 Upon receipt of the handover request response of the target eNodeB, the source eNodeB sends a
Handover Command message to the UE and instructs the UE to start a handover.

Analysis of the LTE Handover Process
 Measurement configuration: The eNB informs the UE of the measurement configuration
message through the measConfig cell carried by the RRCConnectionReconfigurtion message.
It contains the objects to be measured, cell list, report mode, measurement identifier, and
event parameters.
 When to start measuring?

After the RRC connection is established (after
receiving the reconfiguration message)
 Measurement quantity
RSRP,RSRQ
 Reporting mode
Event triggered reporting, periodic reporting

Measurement implementation
 A UE measurement can be one in either RRC_IDLE state and RRC_CONNECTED state.
 Measurement in RRC_IDLE state: For cell reselection
 Measurement in RRC_CONNECTED state: For handover.
 The UE can perform the following types of measurements:

 Co-frequency measurement: Measure RSRP, RSRQ, and Pthloss on the downlink carrier frequency
of the serving cell.
 Different frequency measurement: Measure RSRP, RSRQ, and Pthloss in downlink carrier frequency
different from the serving cell.
 Inter-RAT measurements: Measure PCCPCH RSCP, CPICH RSCP, CPICH Ec/No, GSM Carrier RSSI,
BSIC Identification, and BSIC Reconfirmation.
 RSRP and RSRQ by different UE measurement amount.

 Measurement report: When the UE completes the measurement, it will evaluate the report condition
according to the measurement report configuration. When the setting condition is met, the UE will input
the measurement result into the MeasurementReport message and send it to the base station..
Content of measurementReport:
 measID: measurement ID
 measResultServCell: Measurement result

of the serving cell
 measResultNeighCell: Measurement
result of the neighbor cell.

 Measurement judgment: The eNB makes a judgment for an inter-eNB handover according to the report. The
source eNB sends a handover request to the target eNB, requesting for the target eNB to make handover
preparations. The handover request contains the handover cause, target cell ID, and UE context.
Cause
ECGI
GUMMEI
UE Context

 Completion of handover preparations: After the preparation of the target cell resource is successful, a
handover request ACK message is sent to the source eNB indicating that the target eNB’s handover
preparatory work has been completed.
 Content of Handover Request Act:

 ENB_UE_X2AP_ID: X2AP ID of the UE
on the eNodeB side.
 E_RABs_Admitted_List: eRAB resource
list.
 TargeteNBtoSource_eNBTransparentCo New/Old UE-
ntainer: The transparent channel X2AP-ID
message from target eNodeB to source
eNodeB.
Bearer
Information
HO Command

 Handover implementation steps:
 Upon receipt of the handover request response of the target eNodeB, the source eNodeB sends a
Handover Command message to the UE and instructs the UE to start handover
 After the UE accesses the target cell, it sends a Handover Confirm message to the target cell.
Handover implementation (source base station) Handover implementation (target base station)

 SN Status Transfer:
 For each of the SAE bearers in which the PDCP SN and the HFN state are saved, the reception state of the uplink
PDCP-SN and the HFN, the transmission state of the downlink PDCP-SN and the HFN are transmitted from the
source eNB to the target eNB at the X2 interface handover
 Path Switch Request:

 The purpose of the path translation request is to request that a downlink GTP tunnel be converted to a new GTP
tunnel
Bearer
Information
TAI
UL/DL PDCP-SN
and HFN Status UE Security Capability

 Completion of handover: The target eNB sends a UE context release message to the
source eNB informing the source eNB that the handover has succeeded and triggering
the source eNB to release the resource. (S1 handover corresponds to two messages: UE
Context Release Command and UE Context Release Completed)
Handover completion (X2-based) Handover completion (S1-based)

Contents
22
Common Factors that Affect Handover
Handover parameters Timer setting
Handover parameters (handover type, threshold, Field

hysteresis parameter) will affect the MR reporting to the Name Optimized to Field Meaning
by Timer length for the UE to monitor wireless
MR. When the MR reporting is made at a bad timing, and
T310_Ue 2000 ms link failure
the signal of the serving cell jitters and attenuates too by Idle status duration after the UE detects the
fast, dropped calls occur. Reasonable handover T311_Ue 30000 ms wireless link failure
parameters should be set: A3_offset, TTT, Hysteresis. 。 Time length for the UE to wait for the RRC
by T300 2000 ms connection response
Time length for the UE to wait for the RRC
by T301 2000 ms reestablishment response
Duration of waiting for the RRC request for
retry after the UE receives the RRC
by T302 1s connection rejection
Timer length for the UE to wait for successful
Uplink/downlink interference by T304 1000 ms handover
by T320 5 min Timer length of the cell reselction priority
 Uplink interference includes the uplink interference Maximum number of the UE receiving the
between users, uplink interference due to the device by T310 6 downlink out-of-sync indications
itself, and interference between the bands. Usually Maximum number of the UE receiving the
the uplink interference leads to handover failure, by T311 1 downlink sync indications
failure to rebuild, and dropped calls. The
interference level is determined by checking the
uplink RSSI of the RRU Network load and coverage
 The downlink interference in the system is one
of the causes of dropped calls, usually showing
 Network load determines whether there is free
no coverage of the main cell, the serving cell resource, thereby affecting the preparation of
and the neighbor cell have good and close handover.
RSRP values, but SINR is poor, resulting in  Network topology and coverage determine whether
weakening demodulation signals and easy out- the implementation of handover is smooth and
of-syn, and dropped calls. whether the switch can be completed.

Ideas of Solving the Handover Problem
Failure of handover preparation
1. If the parameters of the neighbor cell are incorrectly configured, for example, the definition
of the external cell is not consistent with the definition of the adjacent base station, extract the
planning data periodically and check the data (correct them with automatic association with
the OMMB).
2. If in the current network, the neighbor cell of a different manufacturer is defined wrongly,
extract the engineering parameters of different manufacturers and make correction.
3. If in the current network, the base station ID of the neighbor cell is wrong, that is, the
neighbor cell relation exists in NMS of neither the other manufacturer or ZTE, such neighbor
cell data should deleted.
4. Regularly check super-far (farther than 2.5 KM in urban area) neighbor cell relationship in the
current network. No such limitation for suburban areas.
Failure of handover implementation
1. If the source cell fails the handover all the time, check whether the target cell has the same
frequency and PCI as the surrounding site, whether the neighbor cell configuration is
reasonable (whether a very far site is added as a neighbor cell and has the same PCI as the
surrounding site).
2. If the source cell tries many handovers and succeeds/fails at a rate, check whether there is
uplink interference at the target base station and troubleshoot the interference accordingly.
3. For a site with many failures in inter-frequency handover, check the inter-frequency initiation
of A2 and A3 event measurement is reasonable.

Handover Problems
Too late Too early
Before and during the UE handover, an RLF During and after the UE handover, RLF occurs
occurs in the source cell, and a in the source cell / target cell, and a
reconstruction process is initiated in the reestablishment process is initiated in the
target cell. source cell.
Handover to wrong cell Ping-pong handover
During and after the UE handover, RLF occurs When the UE performs A → B → A handover
in the source cell / target cell, and a and stays for a very short time at cell B
reestablishment process is initiated in a third before returning to cell A, it is easier to
cell. analyze by signaling flow. Ping-pong
handover means that there are many
handovers within a second.

Contents
26
Measurement Event Category of LTE Handover
 E-UTRAN measures events

 Event A1:The cell quality is above an absolute threshold for turning off inter-frequency
measurements and to deactivate Gap.
 Event A2: The cell quality is below an absolute threshold for enabling inter-frequency
measurements and activating Gap.
 Event: A3 The quality of neighbor cell is higher than serving cell by more than an
absolute threshold, for intra-frequency/inter-frequency coverage-based handover.
 Event A4: The neighbor quality is higher than an absolute threshold, mainly for load-
based handoff.
 Event A5: The quality of the serving cell is lower than an absolute threshold by 1, and the
neighbor cell quality is higher than an absolute threshold by 2, for intra-frequency/inter-
frequency coverage-based handover。
 Different system measurement events
 Event B1: The quality of the neighbor cell of a different system is higher than an absolute
threshold, for load-based handover.
 Event B2: The quality of the serving cell is lower than an absolute threshold by 1 and the
quality of the neighbor cell of a different system is higher than an absolute threshold by
2, for coverage-based handover

Co-frequency Handover in LTE System
Condition for starting Event A3: Mn  Ofn  Ocn  Hys  Ms  Ofs  Ocs  Off
Condition for ending Event A3: Mn  Ofn  Ocn  Hys  Ms  Ofs  Ocs  Off
Parameters:
Mn: Neighbor cell measurement results, not including any
offset.
Ofn: Frequency-specific deviation of neighbor cells.
Ocn: Cell-specific deviation of the neighbor cell.
Hys: Hysteresis between starting and ending the event;
Ms: The measurement result of the current cell, not including
any offset;
Ofs: The frequency-specific deviation of the service
frequency (the frequency of the current cell);
Ocs: The cell-specific deviation of the current cell;
Off: Deviation of Event A3, to be configured at high level.

Description of Parameters
A3Offset
 Parameter meaning:
The Event A3 is triggered when "The quality of neighbor cell is higher the
serving cell by a threshold", where the "threshold" is also marked as a3-Offset
 Value Description:
The formula of starting event A3 shows that, the larger the value of a3-Offset,
the greater the difference between the signal intensity of the neighbor cell
and the serving cell is required to trigger the A3 handover, and the time point
of reporting the measurement result (handover request) is later.

 TimeToTrigger (TTT)
 Parameter Meaning:
n order to avoid the ping-pong handover, it’s not that the UE will report
Event A3 immediately after the neighbor cell’s signal quality is higher than
the serving cell by a threshold. Instead, the UE will report the measurement
report only after it measures the neighbor cell signal to be meeting the
formula for starting Event A3 within a period (Time to Trigger) after the signal
meets the condition for starting Event A3.
Range: 0, 40, 64, 80, 100, 128, 160, 256, 320, 480, 512, 640, 1024, 1280, 2560,
5120. 320 ms by default.

Hysteresis
Used to adjust the threshold of starting and ending Event A3, and determine
the period of UE staying in Event A3.
Default value: 1.5dB.
Mn  Ofn  Ocn
Enter
Hysteresis
Ms  Ofs  Ocs  Off

Hysteresis
Leave
Mn  Ofn  Ocn

Cell Individual Offset (CIO)
Since a3-Offset is the measurement threshold common to all neighbor cells, in many
cases it is not easy to adjust. In order to increase the flexibility of the handover threshold
and adjust the handover threshold (“opportunity of handover”) from the serving cell to
a certain (or some) neighbor cell(s), it is necessary to set the CIO for the neighbor cell.
The CIO of the neighbor cell is the Ocn in the Event A3 formula.
-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,1,20,22,24
Recommended value: 0dB.

The advantage of this parameter is that the offset can be set for each cell to ontrol the c
ell radius of the UE in a connected state.

ReportInterval and reportAmount:
For a measurement configuration of the Event Trigger type, the reporting interval
(reportInterval) can be used in conjunction with the reporting number (reportAmount). If
the reporting interval is greater than 1, the reporting interval is valid. That is, if an event
continues to meet the reporting conditions, the UE will report the measurement report
for reportAmount times continuously with the reportInterval as the period.
For a measurement configuration of the Periodic Reporting type, the reporting interval is
the reporting period.
It is recommended to set reportInterval to “480 ms” and reportAmount to “infinite”,
to increase the handoff success rate and help judge the neighbor cell missing.

Layer 3 filtering filterCoefficent
In the LTE system, the measurement result reported by the UE is filtered through Layer 3, and Layer 3
filtering is used to avoid the contingency of single measurement. The UE uses the following formula to
filter the measurement results:
Where, Mn is the latest value measured by the physical layer;

Fn is a filtered value that is a measure of whether or not a report condition is met (the value reported in
a measurement report).
Fn-1 is the last measured value after filtering, where F0 = M1 (the first measurement results measured
by the physical layer).
A = 1/2 (k/4), where k is the "filter coefficient (filterCoefficent)"
filterCoefficent in the above formula:0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 11, 13, 15, 17, 19. k = 0, Layer 3 filtering
does not work, the system default is 4.

S-Measure
It defines the threshold at which the same-frequency neighbor cell measurement is
initiated. If this field is configured and the RSRP value of the serving cell (after layer 3
filtering) is lower than s-Measure, the UE performs the measurement of the neighbor cell
of the frequency or system mentioned in the measurement configuration.
 Integers ranging from 0 to 97. The corresponding RSRP values of are shown in the
following:
Reported value Measured quantity value Unit
RSRP_00 RSRP  -140 dBm
RSRP_01 -140  RSRP < -139 dBm
RSRP_02 -139  RSRP < -138 dBm
… … …
RSRP_95 -46  RSRP < -45 dBm
RSRP_96 -45  RSRP < -44 dBm
RSRP_97 -44  RSRP dBm

Parameter Analysis
T304
In the cases of "intra-E-UTRAN handover" and "inter-system handover to E-
UTRAN", the UE starts a timer upon receipt of an RRC connection
reconfiguration message with "mobilityControlInfo", and stops the timer upon
completion of random access to the new cell. After the timer expires, the UE
needs to restore the original cell configuration and initiate the RRC re-
establishment request.
 50, 100, 150, 200, 500, 1000, 2000, in milliseconds.

Contents
37
Abnormal Handover Caused by Missed
Neighbor Cell - Multiple Measurement Reports
 In a road test found in the case of the below figure, the target PCI of the first three measurement reports
are 28 (same PCI but slightly different RSRP). In the fourth measurement report, there are two cells:
PCI28, and PCI19. The measured value shows that PCI28 is 3 dB higher than PCI19 and then a handover
command is received. The target cell of the handover command (see Figure 4-4) is PCI19 instead of
PCI28, which may be a missed neighbor cell.
The 4th
First three measurement
measurement reports reports

Fault Caused by Missed Neighbor Cell – No
Response After the Measurement Report Is Sent
 In a road test it is found that no handover command is received after the terminal sends the
measurement report, resulting in the wireless link failure and the initiation of the
reconstruction process.
 Missed neighbor cell can be checked in the background or foreground. The neighbor cell
information can be seen in the measurement control of the source cell.

Troubleshooting Not-Timely Handovers
 Fault Description
 The SINR value on a road near the Jinhu Guoxiang building is very poor. The test log
obtained with the CXA software shows that the road has been using the PCI = 160 signal
of the Jinqiao Building, instead of handing over to the PCI = 179 signal of the Guoxiang
Building.
 Fault Analysis and Troubleshooting

Check the neighbor cell configuration between PCI160 and
PCI179 to see if there is missing neighbor cell.
Check the handover threshold. A3Offset is 1.5 dB, and the
decision delay is 1.5 dB, both of which are correct.
Analysis: The handover may fail to be completed to the PCI179
cell timely, instead, the PCI160 has been used all the time,
causing the SINR to deteriorate along with the RSRP
deterioration of PCI160.
The A3Offset and decision hysteresis can be changed to change
the handover threshold. But this change will affect the
handover of other neighbor cells covered by the same base
station. So modify CIO of PCI179 instead.
The Ocn value corresponding to CIO is 0 by default. To speed
up the handover from PCI160 to PCI179, increase the CIO value
from 0 to 2.

Handover Problems Caused by Complex
Environment
 The terminal moves with a trace shown in blue. It should hand over from the PCI = 45 cell to
the PCI = 8 one. But it hands over to the PCI = 4 cell instead as shown by the red cross, and
then the call drops when the terminal hands back from PCI = 4 cell to the PCI = 45 cell.

Handover Problems Caused by Complex
Environment
 Troubleshooting
 To avoid the terminal from handing over to the PCI = 4 cell at the red cross location,
lower the RS Power of the PCI = 4 cell first, and next adjust the CIO of both the PCI = 45
and PCI = 4 cells. But the RSRP of the PCI = 4 cell is 17 dB higher than that of the PCI =
45 cell, so the handover problem persists.
 Analyze the RSRP distribution near the junction area: the east-west road is covered by
the PCI = 45 cell, the northbound road is covered by the PCI = 4 cell, but near the
junction area, the RSRP values of PCI = 7 and PCI = 4 cells are close to each other.
 Delete the unidirectional neighbor cell of PCI=45-PCI=4, the terminal will not
handover to PCI = 4 cell again along this test route. When the terminal moves from the
junction area to the PCI = 4 cell, it will hand over first to the PCI = 7 cell and then to the
PCI = 4 cell.

Frequent Ping-Pong Handovers Caused by
Wrong OCS Parameter Setting
 A complaint staged to China Mobile from a countryside outlet: The download rate is
very low, web pages are hard to open, yet the terminal signal shows to be good.
Network environment: There are two sites: A and B. No problem is found in single-
site test.
 Fault Analysis
 Replace the terminal. The problem persists.
 Field tests show there are ping-pong handovers near site A (upstairs of the outlet),
which result in very low download rate or no rate, and the source cell of a handover
has obviously better signals (by more than 10 dB) than the target cell does. But
there are much less handovers near site B and the download rate is 30 Mbps or
higher. So the problem is located to site A.

 Fault analysis
 Network management statistics show that the handovers of the two sites have
increased by about 60 times recently, while site A has a large number of handover
failures. Check the consistency of the network management parameters. It is found
that the cell-level parameter OCS is set to -24db by mistake (the correct value is 0db,
which corresponds “15” as shown on the network management system. However,
the value shown on the network management system is “0”, meaning the actual
value is of the parameter is -24db).
 Troubleshooting
 Use another terminal to perform the test. The problem still exists, thus ruling out the
terminal problem.
 Because there are too many handovers involved, there can be an overlapping
coverage problem. Field tests show frequent handovers between the two sites, but
the handovers mainly happen under site A, and the signal strength of site B is greatly
weaker than site A when the handover occurs under site A. The radio frequency
coverage problem is ruled out.

 Troubleshooting
 The problem is located to site A. No fault is found in the background. Shut down site A.
The ping-pong problem still exists. Service of single cells is normal, with the download
rate of 30 Mbps or higher.
 Network management statistics show that since the 13th day of the month, the
handovers of sites A and B increased by 60 times. There are a lot of handover failures at
site A. It is found that the cell-level parameter OCS is set to -24db by mistake (the
correct value is 0db, which corresponds “15” as shown on the network management
system. However, the value shown on the network management system is “0”,
meaning the actual value is of the parameter is -24db).

 Troubleshooting
 The fault is now located. Because the condition for so-frequency A3 handover is: Mn
+ ocn-Hys > Ms + ocs + off, that is, Mn > MS + Hys + off + ocs-ocn. OCS and OCN
are normally set to 0, and the sum of Hys plus off is 3, that is, the target is 3 db
higher than the source. Now that the OCS of site A is set to -24dB by mistake, while
that of site B is correct, the terminal occupying the signal of site A will initiate a
handover when the signal of the target cell is weaker by -21dB than the source cell.
 Once the OCS of site A is set to 0, the problem of ping-pong handovers is solved,
the download rate restores to about 33 Mbps, handover performance indexes in the
NMS are normal again.

 Troubleshooting
 The fault is now located. Because the condition for so-frequency A3 handover is: Mn +
ocn-Hys > Ms + ocs + off, that is, Mn > MS + Hys + off + ocs-ocn. OCS and OCN are
normally set to 0, and the sum of Hys plus off is 3, that is, the target is 3 db higher than
the source. Now that the OCS of site A is set to -24dB by mistake, while that of site B is
correct, the terminal occupying the signal of site A will initiate a handover when the
signal of the target cell is weaker by -21dB than the source cell.

Handover Problem Caused by Inconsistent
Capability of the Terminal
 It is found in a FDD-TDD handover test that there is no rate for about 20 seconds
in the process of handover from an FDD site to a TDD site. The FTP server timeout,
and reconnection is tried automatically. The terminal signaling seems to be
normal. The background KPIs are normal for a handover. The handover is normal
from the TDD site to the FDD site.
 Fault Analysis
 First, verify that the terminal has the capability to make a TF handover and, when
the terminal is making the attachment, the uecapabilityinformation signaling is
reported (supported if bit30 = 1, not supported if bit30 = 0).

Failure of Handover Between Different
Manufacturers/Frequencies
 Fault Analysis
 Signaling of the terminal and network shows that the terminal has completed the
process of handover to the target cell. But after the target cell sends a Handover
Notify, it releases the UE Connext immediately, and service is started after the
target cell is attached again. This is why the service stops for 20 seconds in the
test. In a normal handover process, there should be downlink data after the target
cell sends the Handover Notify message and then the resource of the source cell
is released (rather than the target cell releases the UE Context).

 Troubleshooting
 The handovers are totally normal and successful in most of the time. But they can
burst in quantity during some periods and they can hardly succeed during those
periods.

 Fault Analysis
 Signaling at the CN side shows that the base station sends UE Context Release
Request to the MME because of “cell not available”. The CN engineer confirms
that the CN does not distinguish FDD from TDD.
 Signaling at the terminal side shows that the terminal performs attachment after it
switches to the target cell, before the downlink data occurs. A description is then
found in the protocol that if the wireless capability is not consistent between TDD
and FDD, the terminal will attach again after it completes a handover between TD
LTE And FDD LTE.
 Solution
 Install new version software in the terminal and do the test again. Now the
handover is normal and the terminal signaling shows no more exceptional
attachment.

 Fault Analysis
 The problem terminal receives the 2585 message of the outdoor macro base station.
According to the measurement configuration, the 40540 of BAND41 is delivered to
suit the terminal capability, but the actual configuration of the Ericsson macro base
station is 37900 of BAND38, so the message cannot get to its target (since the
frequency configured in our neighbor cell is 37900). Timeout occurs.
Reestablishment is performed at the source cell. The handover is cancelled.
Afterwards, because the terminal is not handed out yet, it still receives 2585 and
initiates and fails handovers over and over again, till it cannot occupy the indoor
distribution signal any longer and is dropped.
 Solution
 The Ericsson engineer confirms that the Ericsson macro base station does not
support multi-frequency indication for the moment. Push the customer to convince
Ericsson to upgrade the software and finally the multi-frequency indication is
supported.

Handover Failure Due to Uplink Out-of-Sync
 During a test, it is found that the terminal performs reestablishment when it moves to the
place shown as a blue frame in the below figure, and the reestablishment is rejected.
 Fault analysis
 The signaling shows that two measurement reports are sent before the reestablishment,
but no handover command is received, resulting in the out-of-sync of the terminal and
then the reestablishment is rejected.

 Fault Analysis
 Open the diagnostic signaling and find that the terminal has sent the SR request before
sending the measurement report, but has not received the PDCCH feedback of
scheduling information, that is, the SR application failed.
 After SR is sent for the maximum number of times, random access is initiated at the
source cell to query the MAC RACH Trigger signaling. The cause value of sending the
random access is UL data arrival, which means the SR application failure and the MR
sending failure, thus the random access to restore the uplink.

 Fault Analysis
 During the entire random access process, the source cell sends MSG1 but does not
receive RAR.
 When the MSG1 is sent for the maximum number of times, that is, the source cell fails to
restore the uplink and enters into the reestablishment process, with the reestablishment
cause of Radio link failure.

 Fault Analysis
 Reestablishment requires cell selection. The selected cell does not have the terminal
context information and the reestablishment is rejected, resulting in dropped calls
(If there is no UE context information in the eNB, the UE refuses to reestablish the
RRC connection for the UE, and then replies an RRC connection reestablishment
rejection message on the SRB0 through the DL_CCCH).

 Solution:
 The problem of UL data arrival usually occurs in the weak field of the source cell. If it
is the handover belt, the problem can be solved by handing over beforehand to
another cell with better signal quality. Check the RSRP status of the problem spot and
find that the RSFP strength of the source cell dropped in a very short time, while that
of the neighbor cell rises sharply in a short time. Adjust CIO, but no obvious change
happens. Reduce “time to trigger” from 320 ms to 256 ms. Perform tests and the
problem is solved.

Thank you

03 - Fo - Nast3101 - c01 - 1 Lte Handover Analysis (Ppt+Notes) 58-Final

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

03 - Fo - Nast3101 - c01 - 1 Lte Handover Analysis (Ppt+Notes) 58-Final

Uploaded by

Copyright:

Available Formats

LTE Handover Analysis

 Keeping continuous conversation while the terminal is in motion

 Improving network service quality

 Reducing call drop rate

 Reducing congestion rate

LTE Handover Mode

 LTE uses a mobile-assisted backward hard-handover technology

 By wireless standard: Whether Within TD-LTE system

handover: Whether Intra-MME handover

Inter-system handover TD LTE<-->GSM

© ZTE All rights reserved 5

 When the UE reports the MR message and the

© ZTE All rights reserved 7

 When the UE reports the MR message and the

© ZTE All rights reserved 8

determines that a handover is required, it first 4 RRC connection Reconfiguration

determines whether the source cell and the target

© ZTE All rights reserved 9

determines that a handover is required, it first 4 RRC connection Reconfiguration

determines whether the source cell and the target

© ZTE All rights reserved 10

6 RRC connection Reconfiguration

11 RRC connection Reconfiguration Complete

13 UE context release Cmd

14 UE context release Complete

© ZTE All rights reserved 11

6 RRC connection Reconfiguration

11 RRC connection Reconfiguration Complete

13 UE context release Cmd

14 UE context release Complete

© ZTE All rights reserved 12

 Measurement implementation: The UE makes measurements on the current serving cell.

© ZTE All rights reserved 13

 When to start measuring?

© ZTE All rights reserved 14

 The UE can perform the following types of measurements:

 RSRP and RSRQ by different UE measurement amount.

© ZTE All rights reserved 15

 measResultServCell: Measurement result

© ZTE All rights reserved 16

© ZTE All rights reserved 17

 Content of Handover Request Act:

© ZTE All rights reserved 18

© ZTE All rights reserved 19

 Path Switch Request:

© ZTE All rights reserved 20

Handover completion (X2-based) Handover completion (S1-based)

© ZTE All rights reserved 21

Handover parameters (handover type, threshold, Field

© ZTE All rights reserved 23

Failure of handover implementation

© ZTE All rights reserved 24

Handover to wrong cell Ping-pong handover

© ZTE All rights reserved 25

 E-UTRAN measures events

© ZTE All rights reserved 27

© ZTE All rights reserved 28

© ZTE All rights reserved 29

© ZTE All rights reserved 30

Ms  Ofs  Ocs  Off

© ZTE All rights reserved 31

Cell Individual Offset (CIO)

Recommended value: 0dB.