LTE Handover Fault Diagnosis (KPI) ISSUE1.00

LTE Handover Fault Diagnosis (Traffic KPIs) P-0
Confidential Information of Huawei. No Spreading Without Permission




 Triggering for Measurement

 Measurement on inter-frequency or IRAT handover neighbor cells has to be
triggered by the related event parameters, including source cell quality, cell load
and etc.
 Measurement
 UE performs measurement on serving cell and neighbor cells following the
instruction from measurement control.
 Decision
 eNodeB decides the target cell based on the measurement result sent by UE.
 Execution
 eNodeB delivers handover command for UE execution
 UE executes connection release procedure with source cell upon receiving
handover command, and initiate access procedure with the target cell


 The inter-frequency and IRAT measurement control delivery from eNodeB to user is
triggered by the event A1/A2 reported by user
 Ms : Measurement result of the serving cell, not taking into account any offsets.
 Hys : Hysteresis of event A1/A2
 Thresh X: Threshold of event A1/A2

 UE perform measurement according to the measurement control sent by eNodeB, and send event-
triggered-periodical measurement report shall event criteria fulfilled.
Event Criteria Action

Measurement result of intra-frequency / inter-
frequency neighbor cell is greater than Serving cell initiates intra-frequency /
A3
measurement result of serving cell for a certain inter-frequency handover request
threshold
Measurement result of inter-frequency neighbor Serving cell initiates inter-frequency
A4
cell is greater than a threshold handover request
Serving cell initiates inter-frequency
A5 A2 + A4
handover request
Measurement result of IRAT neighbor cell is greater Serving cell initiates IRAT handover
B1
than a threshold request
 The variables in the formula are defined as follows: Serving cell initiates IRAT handover
B2 A2 + B1
 Ms is the measurement result of the serving cell, not takingrequest
into account any offsets.
 Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
 Ofn is the frequency specific offset of the frequency of the neighbour cell.
 Ocn is the cell specific offset of the neighbour, and set to zero if not configured for the
neighbour cell.
 Ofs is the frequency specific offset of the serving frequency.
 Ocs is the cell specific offset of the serving, and is set to zero if not configured for the serving
cell.
 Hys is the hysteresis parameter for the events.
 ThreshX is the threshold parameter for the events


 Handover Request
Forwarding of UE context
Forwarding of UE history
information

 Handover Command

 Upon receiving handover command, UE release the connection with source eNodeB
and perform random access procedure with target cell, and send RRC connection
reconfiguration complete message to the target cell indicating a handover completion.
 Path switch procedure taken place after UE complete the access procedure in target
cell, where source eNodeB sends Path Switch Request to MME, requesting a S1 path
switched to target eNodeB.
 Upon completion of path switch, downlink and uplink data transmission would be
switched to the target cell, at the same time after the data forwarding completed in
source eNodeB, target eNodeB send UE Context Release to the source eNodeB so that
radio resource and UE context could be released at the source eNodeB end.


1. UE measures source cell and target cells and send measurement reports including
neighbor cells fulfilling event criteria
2. From the report, source eNodeB selects target cell fulfilling handover criteria and then
send the “Handover Request” to the target eNodeB.
3. Upon receiving handover request, target eNodeB sends “Handover Request
Acknowledge” message to source eNodeB after a successful call admission control.
4. Source eNodeB sends “RRC Connection Reconfiguration” message to the UE
indicating a handover command.
5. Source eNodeB initiates data forwarding process by sending “SN Status Transfer” for
existing eRAB (DRB)

6. UE perform random access procedure following the handover command.

7. UE send “RRC Connection Reconfiguration Complete” message to target eNodeB after
a successful access procedure.
8. Then, target eNodeB send “Path Switch Request” message to MME requesting a user
plane switching to the target eNodeB.
9. MME respond to target eNodeB with “Path Switch Request Acknowledge” indicating
a permission on the user plane switch.
10. Upon receiving “Path Switch Acknowledge”, target eNodeB send “UE Context Release”
message to the source eNodeB indicating a successful handover and hence the UE
context could be released in source eNodeB. Nevertheless source eNodeB will only
release UE context after the completion of data forwarding.



 Successful RRC Connection Reestablishment (performed by UE after handover failure) is included in the
total handover success number. The number has to be excluded if reestablishment is not deemed to
be considered.
 Number of intra-eNodeB HO outgoing execution attempts is counted at point B, and the number of
successful intra-eNodeB outgoing HO executions is counted at point C.
 Number of inter-eNodeB HO outgoing execution attempts is counted at point B, and the number of
successful inter-eNodeB outgoing HO executions is counted at point C.

 If the source cell and the target cell work on the same frequency, the statistic below counted under
intra-frequency handover counters.
 Number of intra-eNodeB intra-frequency HO outgoing execution attempts is counted at point B, and
the number of successful intra-eNodeB intra-frequency outgoing HO executions is counted at point C.
 Number of inter-eNodeB intra-frequency HO outgoing execution attempts is counted at point B, and

the number of successful inter-eNodeB intra-frequency outgoing HO executions is counted at point C.

 If the source cell and the target cell work on the same frequency, the statistic below counted under
inter-frequency handover counters.
 Number of intra-eNodeB inter-frequency HO outgoing execution attempts is counted at point B, and
the number of successful intra-eNodeB inter-frequency outgoing HO executions is counted at point C.
 Number of inter-eNodeB inter-frequency HO outgoing execution attempts is counted at point B, and

the number of successful inter-eNodeB inter-frequency outgoing HO executions is counted at point C.

 If the source cell and the target cell work in different duplex modes, the statistic below counted under
inter-fddtdd handover counters.
 Number of intra-eNodeB inter-fddtdd HO outgoing execution attempts is counted at point B, and the
number of successful intra-eNodeB inter-frequency outgoing HO executions is counted at point C.
 Number of inter-eNodeB inter-fddtdd HO outgoing execution attempts is counted at point B, and the
number of successful inter-eNodeB inter-frequency outgoing HO executions is counted at point C.

 The counters measure the number of X2-based intra-frequency outgoing handover executions,
the number of X2-based inter-frequency outgoing handover executions, and the number of X2-
based inter-duplex-mode outgoing handover executions in a cell.
 Number of X2-based HO outgoing execution attempt is counted at point B, and the number of
successful X2-based outgoing HO executions is counted at point C.

 Number of S1-based HO outgoing execution attempts is counted at point B, and the number of
successful S1-based outgoing HO executions is counted at point C.

 In U2000, outgoing handover failures for different causes could be categorized into intra-frequency,
inter-frequency, inter-FDDTDD:
Counter Name Counter Description
Number of intra-frequency outgoing handover preparation failures because of
L.HHO.IntraFreq.Prep.FailOut.MME
the MME side causes
Number of intra-frequency outgoing handover preparation failures because the
L.HHO.IntraFreq.Prep.FailOut.NoReply
target cell does not respond
L.HHO.IntraFreq.Prep.FailOut.PrepFailure
target cell sends handover preparation failure messages
L.HHO.IntraFreq.Prep.FailOut.HOCancel
source cell sends handover cancellation messages

L.HHO.IntraFreq.Prep.FailOut.TargetIllegal
handover response messages sent by the target eNodeB fail the validity check
Number of inter-duplex-mode outgoing handover preparation failures because

L.HHO.InterFddTdd.Prep.FailOut.MME
of faults on the MME side
L.HHO.InterFddTdd.Prep.FailOut.NoReply
of no responses from the target cell

L.HHO.InterFddTdd.Prep.FailOut.PrepFailure
of the handover preparation failure messages sent from the target cell
Number of failed inter-duplex-mode outgoing handover preparations because

L.HHO.InterFddTdd.Prep.FailOut.HOCancel
of the handover cancellation messages sent from the source cell
L.HHO.InterFddTdd.FailOut.HOCancel Number of inter-eNodeB inter-duplex-mode outgoing handover cancellations
Number of inter-duplex-mode outgoing handover preparation failures due to

L.HHO.InterFddTdd.Prep.FailOut.Other
other causes
L.HHO.InterFddTdd.FailOut.HOCancel.Flow Number of times inter-eNodeB inter-duplex-mode outgoing handovers are
Conflict canceled due to flow conflicts

 Successful RRC Connection Reestablishment (performed by UE after handover failure) is included in

the total handover success number. The number has to be excluded if reestablishment is not
deemed to be considered.
 Number of intra-eNodeB HO incoming execution attempts is counted at point B, and the number of
successful intra-eNodeB incoming HO executions is counted at point C.
 Number of inter-eNodeB HO incoming execution attempts is counted at point B, and the number of
successful inter-eNodeB incoming HO executions is counted at point C.

 The counters measure the number of X2-based incoming handover executions in a cell.
 Number of X2-based HO incoming execution attempt is counted at point B, and the number of
successful X2-based outgoing HO executions is counted at point C (Figure 1) and point E (Figure
2).
Figure 1 Figure 2

 Number of S1-based HO outgoing execution attempts is counted at point B, and the number of
successful S1-based outgoing HO executions is counted at point C.

 In U2000, incoming handover failures for different causes could be categorized into intra-
frequency, inter-frequency, inter-FDDTDD:

Number of inter-duplex-mode incoming handover preparation
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.SR
failures because of admission failure caused by insufficient SRS
S
resources in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.PU
failures because of admission failure caused by insufficient PUCCH
CCH
resources in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.UL
failures because of admission failure caused by insufficient licensed
ThrpLic
uplink traffic volume in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.DL
ThrpLic
downlink traffic volume in a cell
umber of inter-duplex-mode incoming handover preparation
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.Us
erLic
number of RRC-connected UEs in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.Us
failures because of admission failure caused by limited
erSpec
specification on the number of RRC-connected UEs in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.TN
failures because of admission failure caused by insufficient
L.DLRes
downlink transport resources in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.TN
failures because of admission failure caused by insufficient uplink
L.ULRes
transport resources in a cell
L.HHO.InterFddTdd.Prep.FailIn.Other
failures due to other causes


Number of inter-duplex-mode incoming handover
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.Other preparation failures because of admission failure due to
other causes in a cell
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail
preparation failures because of admission failure in a cell
L.HHO.InterFddTdd.Prep.FailIn.FlowCtrl
preparation failures because of flow control in a cell
L.HHO.InterFddTdd.Prep.FailIn
preparation failures in a cell
L.HHO.InterFddTdd.Prep.FailIn.HOCancel preparation failures because the target cell receives
handover cancellation messages
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.Load preparation failures because of load-based admission
failure in a cell
Number of preparation failures of incoming inter-duplex-
L.HHO.InterFddTdd.Prep.FailIn.AdmitFail.VoIPPref mode handovers triggered by voice service preferential
access
Number of intra-duplex-mode incoming handover
L.HHO.Prep.FailIn.AdmitFail.Load preparation failures because of load-based admission
failure in a cell
L.HHO.Prep.FailIn.AdmitFail.SRS preparation failures because of admission failure caused by
insufficient SRS resources in a cell
L.HHO.Prep.FailIn.AdmitFail.PUCCH preparation failures because of admission failure caused by
insufficient PUCCH resources in a cell
L.HHO.Prep.FailIn.AdmitFail.ULThrpLic preparation failures because of admission failure caused by
insufficient licensed uplink traffic volume in a cell
L.HHO.Prep.FailIn.AdmitFail.DLThrpLic preparation failures because of admission failure caused by
insufficient licensed downlink traffic volume in a cell
L.HHO.Prep.FailIn.AdmitFail.UserLic preparation failures because of admission failure caused by
insufficient licensed number of RRC-connected UEs in a cell
preparation failures because of admission failure caused by
L.HHO.Prep.FailIn.AdmitFail.UserSpec
limited specification on the number of RRC-connected UEs
in a cell
L.HHO.Prep.FailIn.AdmitFail.TNL.DLRes preparation failures because of admission failure caused by
insufficient downlink transport resources in a cell
L.HHO.Prep.FailIn.AdmitFail.TNL.ULRes preparation failures because of admission failure caused by
insufficient uplink transport resources in a cell
L.HHO.Prep.FailIn.AdmitFail.Other preparation failures because of admission failure due to
other causes in a cell
Number of preparation failures of incoming intra-duplex-
L.HHO.Prep.FailIn.AdmitFail.VoIPPref mode handovers triggered by voice service preferential
access

 U2000 provides standard KPI related measurement items, U2000 user is able to define
specific KPI item according to specific network scenario in Performance -> User
Defined Counter Management

 User-defined KPI is inactive by default, it could be activated in Measurement ->

Measurement Management
 Only check or uncheck the counters which requires activation / deactivation, avoid
modifying the existing measurement counters which were activated / deactivated.

 U2000 UE can perform query from Performance -> Measurement Management ->
Query Result -> New Query

 Handover Fault Performance Counter

KPI Counter Name KPI Counter Name
L.HHO.IntraeNB.IntraFreq.PrepAttOut L.HHO.IntraeNB.IntraFreq.Succ.ReEst2Src
Handover where
L.HHO.IntraeNB.IntraFreq.ExecAttOut RRC Connections L.HHO.IntraeNB.InterFreq.Succ.ReEst2Src
L.HHO.IntraeNB.IntraFreq.ExecSuccOut Are L.HHO.IntereNB.IntraFreq.Succ.ReEst2Src
Reestablished to
L.HHO.IntraeNB.InterFreq.PrepAttOut L.HHO.IntereNB.InterFreq.Succ.ReEst2Src
the Source Cell
L.HHO.IntraeNB.InterFreq.ExecAttOut L.HHO.BlindHO.Succ.ReEst2Src
L.HHO.IntraeNB.InterFreq.ExecSuccOut Handover where L.HHO.IntraeNB.IntraFreq.Succ.ReEst2SrcOther
Handover RRC Connections
Out KPI L.HHO.IntereNB.IntraFreq.PrepAttOut Are L.HHO.IntraeNB.InterFreq.Succ.ReEst2SrcOther
Statistic L.HHO.IntereNB.IntraFreq.ExecAttOut Reestablished to L.HHO.IntereNB.IntraFreq.Succ.ReEst2SrcOther
the Intra-
L.HHO.IntereNB.IntraFreq.ExecSuccOut eNodeB Non- L.HHO.IntereNB.InterFreq.Succ.ReEst2SrcOther
Source Cells
L.HHO.IntereNB.InterFreq.PrepAttOut L.HHO.IntraeNB.ExecSuccIn.ReEst2Tgt
Handover where
L.HHO.InterFddTdd.IntraeNB.ExecSuccIn.ReEst
L.HHO.IntereNB.InterFreq.ExecAttOut RRC Connections
2Tgt
Are
L.HHO.IntereNB.InterFreq.ExecSuccOut Reestablished to L.HHO.IntereNB.ExecSuccIn.ReEst2Tgt
the Target Cell L.HHO.InterFddTdd.IntereNB.ExecSuccIn.ReEst
L.HHO.Prep.FailOut.MME
2Tgt
L.HHO.Prep.FailOut.NoReply L.HHO.FailOut.HOCancel.FlowConflict
Handover L.HHO.Prep.FailOut.PrepFailure L.HHO.Prep.FailOut.RNL

Failures for L.HHO.Prep.FailOut.HOCancel Handover L.HHO.Prep.FailOut.TNL
Different Failures for
L.HHO.FailOut.HOCancel Different Causes L.IntraFreqHO.NoNRT
Causes
L.HHO.Prep.FailOut.Other L.InterFreqHO.NoNRT
L.HHO.Prep.FailOut.TargetIllegal L.InterFddTddHO.NoNRT
L.HHO.IntraFreq.Prep.FailOut.TargetIllegal


 Check if handover success rate lower than baseline value (for instance 98.5%,
benchmarked value in accordance to the regional KPI requirement) during KPI
monitoring.

 Check if handover success rate degrades gradually and becomes lower than baseline
value (for instance 98.5%, benchmarked value in accordance to the regional KPI
requirement) during KPI monitoring.

 Check if handover success rate degrades drastically and becomes lower than baseline
value (for instance 98.5%, benchmarked value in accordance to the regional KPI
requirement) during KPI monitoring.

 Top region is the area with most top N cells distributed, the fault could be related to
transmission fault (access leg), external interference and etc
 To troubleshoot handover KPI fault of top N cells / regions, troubleshooting on the
relevant top N cells / regions is prioritized:
 For top N cells / regions with handover success rate lower than benchmark
value, prioritize the audit of inappropriate handover parameter
 For top N cells / regions with handover success rate degradation, prioritize the
checking of performance alarm and resource overload
 For top N cells / regions with drastic degradation of handover success rate,
prioritize the checking of hardware fault, alarm, new feature activation,
parameter change, transmission cutover and equipment upgrade and etc.
 For other fault of top N cells / regions and global network, analyze the handover failure
based on different causes, identify the top root cause, and then perform relevant
counteraction based on the root cause.

 This course focuses on the fault diagnosis of common handover fault in live network, which includes
premature handover, delayed handover, ping-pong handover and handover failure.
 Pre-mature handover
 Inappropriate handover parameter causes UE handover to the target cell with unstable signal
quality, leading to admission failure in target cell hence UE perform reestablishment with
source cell. The number of reestablishment with source cell could be recorded at eNodeB.
 Delayed handover
 Delayed handover could be attributed to delayed neighboring cell measurement or
inappropriate handover threshold, after handover failure UE perform reestablishment with
target cell or other neighboring cell. The number of reestablishment with non-source cell could
be recorded at eNodeB.
 Ping-Pong handover
 Cell level ping pong handover: If UE perform handover out and back between a pair of source
cell and neighbor cell within ping-pong timer (default value is 2s), that is considered as one
cell-level ping-pong handover.
 UE-level ping pong handover: If UE perform handover out and back between a pair of source
cell and neighbor cell for more than N times (N is the UE PingPong Number Threshold, default
value of 5), and the average camping time in the target cell during the most recent N ping-
pong handovers is shorter than ping-pong timer (default value is 2s), this UE is considered as a
ping-pong UE, with UE-level ping pong handover counted 1.
 Handover failure
 eNodeB counts the statistic according to the different causes of handover failure, identifying
the fault is related to radio network layer, transmission layer, core network, flow control or
admission control failure.

 If there are numerous reestablishment with source cell during handover execution, an
initial conclusion could be made that the target cell signal quality is not stable, and the
handover threshold to the target cell is required to be optimized. This is to minimize
reestablishment and the call drop after reestablishment failure.
 Number of Premature Intra-RAT Handovers statistics between two specific cells within
LTE could be recorded:
Counter Name Description

Number of premature intra-RAT
L.HHO.NCell.HoTooearly
handovers between two specific cells

 If there are numerous reestablishment with non-source cell during handover execution,
an initial conclusion could be made that source cell signal quality degraded drastically
before UE receives handover command, therefore measurement trigger and handover
decision threshold of source cell is required to be optimized. This is to minimize
reestablishment and the call drop after reestablishment failure.

 Sub-counters of certain handover failure performance counter:

Counter Name Description
Number of inter-eNodeB intra-duplex-mode outgoing
L.HHO.FailOut.HOCancel
handover cancellations
Number of intra-frequency outgoing handover preparation
L.HHO.IntraFreq.Prep.FailOu
failures because the handover response messages sent by
t.TargetIllegal
the target eNodeB fail the validity check
L.HHO.FailOut.HOCancel.Flo Number of times inter-eNodeB intra-duplex-mode outgoing
wConflict handovers are canceled due to flow conflicts
Number of intra-frequency handover initiation failures
L.IntraFreqHO.NoNRT
because the adjacent cell is not on the NRT of the source cell
Number of inter-frequency handover initiation failures
L.InterFreqHO.NoNRT because the target cell is not configured as a neighboring cell
for the source cell
Number of inter-duplex-mode handover initiation failures
L.InterFddTddHO.NoNRT
because the adjacent cell is not on the NRT of the source cell



 Figure above shows the statistics of one top cell with handover fault (x state beer
factory 2LF_1). It is noticed that the average handover success rate of the week is at
around 95.5%, which is failed to meet the baseline value, at the same time the
number of reestablishment with the source cell is at around 10% of the handover
success rate. This is an indication of the high percentage of reestablishment, hence the
possibility of premature handover.

 The current handover decision is based on target cell RSRP, therefore admission failure
might occur in the target cell with interference although the RSRP of target cell met
the handover decision threshold.
 The fault diagnosis of premature handover should be done together with handover
failure, reestablishment and etc.

 During handover data analysis, Top N cells with the highest number of UE
reestablishment with source cell should be recorded. Statistic of handover out number
between specific cells could be diagnosed in U2000 to identify the distribution of the
top N cell (within neighbor list), to confirm if the premature handover is limited to top
N neighbor or it is common issue of all neighbors.
 If it is a top-N neighbor issue, it could be concluded that this issue is related to
improper neighbor-cell CIO setting.
 If the number of reestablishment to all neighbor cells of a specific frequency is
high, it could be concluded that this issue is related to improper frequency
offset.
 If it is a common issue of all neighbors, it could be concluded that this issue is
related to improper handover threshold or time-to-trigger.
 To diagnose target cell / frequency with numerous reestablishment or low handover
success rate, tracing and drive test could be performed to analyze if there is
interference in target cell / frequency. Strong interference causes low admission
success rate in target cell, leading to handover failure or reestablishment.

 Neighboring CIO Ocn: CellIndividualOffset

 Source Cell CIO Ocs: CellSpecificOffset
 Neighboring frequency offset Ofn：QoffsetFreqConn
 Serving frequency offset Ofs：QoffsetFreq
 Ocn audit & modification
 Intra-frequency neighbor: LST EUTRANINTRAFREQNCELL/MOD
EUTRANINTRAFREQNCELL
 Inter-frequency neighbor: LST EUTRANINTERFREQNCELL/MOD
EUTRANINTERFREQNCELL
 Frequency audit & modification
 If the percentage of reestablishment on specific frequency is high, the
frequency offset Ofn could be reduced by 1-3dB; If the percentage of
reestablishment on all neighboring frequencies is high, the serving frequency
offset Ofs could be increased by 1-3dB;
 Serving Frequency: LST CELL/MOD CELL
 Neighboring Frequency: LST EUTRANINTERNFREQ/MOD EUTRANINTERNFREQ
 Source cell CIO audit & modification
 Source cell: LST CELL/MOD CELL






 Measurement trigger threshold is set to be too low in source cell, causing UE trigger
for measurement too late, source cell signal degrades during measurement report
sending and handover command receiving, handover is not able to be triggered
promptly, therefore radio link failure occurs and leading to reestablishment with non-
source cell.
 Handover decision threshold is set to be too high, or handover time-to-trigger is set to
be too long, causing very strict handover decision of target cell. Candidate cells
fulfilling handover criteria could not be found promptly, therefore radio link failure
occurs or handover command sent to UE too late hence UE is not able to receive or
decode correctly. That leads to numerous reestablishment with non-source cell.

 During handover data analysis, Top N cells with the highest number of UE reestablishment with
non-source cell should be recorded. Statistic of handover out number between specific cells
could be diagnosed in U2000 to identify the distribution of the top N cell (within neighbor list),
to confirm if the premature handover is limited to top N neighbor or it is common issue of all
neighbors.
 If it is a top-N neighbor issue, it could be concluded that this issue is related to
improper neighbor-cell CIO setting.
 If the percentage of delayed handover to all neighbor cells of a specific frequency is
high, it could be concluded that this issue is related to improper frequency offset.
 If it is a common issue of all neighbors, it could be concluded that this issue is related
to improper handover threshold or time-to-trigger.
 The statistic of handover out between specific cells in U2000 is able to show the statistic of
delayed-handover related to inter-frequency measurement event A2, it could help identifying
improper configuration of A2 measurement start threshold of top N frequency:
Delayed HO Number between Specific Cells
600
400
200
0
1
Limyu_1
Linlli Center_1
ALA National
Edinberg_1
XX_Street_1
Northstreet_1
Baitang_1
International_
Delayed HO Number between Delayed-handover related to inter-frequency measurement

特定两小区间切换出过晚次数特定两小区间系统内异频A2测量相关的切换过晚次数
Specific Cells event A2

 Neighboring CIO Ocn: CellIndividualOffset

 Source Cell CIO Ocs: CellSpecificOffset
 Neighboring frequency offset Ofn：QoffsetFreqConn
 Serving frequency offset Ofs：QoffsetFreq
frequency offset Ofn could be reduced by 1-3dB; If the percentage of
offset Ofs could be increased by 1-3dB;


frequency offset Ofn could be increased by 1-3dB; If the percentage of
offset Ofs could be reduced by 1-3dB;




Avg RSRP Distribution

Percentage (%) RSRP (dBm)
Percentage (%)



 The value above is only for reference purpose, baseline value strictly follow different
regional requirement.


 During handover fault diagnosis, the first step is to identify the root cause:
 If the handover KPI failure is caused by top N cells, then identify the top N cells
and troubleshoot the cells, and compute statistic of handover performance
between two specific cells.
 If the top N cells are distributed in the same region, then troubleshoot the top
N region to identify if there is fault of equipment, transmission, core network
or interference.
 If the handover KPI failure is not caused by top N cells, then the failure causes
of overall network KPI failure are to be identified in order to confirm the
handover root causes.

 If the fault above is not found, then proceed in analyzing the statistics of handover
failure causes, referring to the troubleshooting step of TopN causes.
 eNodeB fault may causes handover failure, the related alarms listed below:
 Board Alarm
 ALM-26202 Board Overload
 RF Unit Alarm
 ALM-26529 RF Unit VSWR Threshold Crossed, ALM-26522 RF Unit RX
Channel RTWP/RSSI Unbalanced
 Cell Capability Degradation Alarm
 ALM-29243 Cell Capability Degraded
 Abnormal CPRI Link Alarm (only applicable for 3900 BTS)
 ALM-26235 RF Unit Maintenance Link Failure, ALM-26234 BBU CPRI
Interface Error, ALM-26233 BBU CPRI Optical Interface Performance
Degraded, ALM-26506 RF Unit Optical Interface Performance Degraded
 Abnormal Clock Alarm
 ALM-26263 IP Clock Link Failure, ALM-26264 System Clock Unlocked,
ALM-26538 RF Unit Clock Problem, ALM-26260 System Clock Failure,
ALM-26265 Base Station Frame Number Synchronization Error
 Transmission Fault Alarm
 ALM-25886 IP Path Fault ALM-25888 SCTP Link Fault, ALM-25952
User Plane Path Fault, ALM-29201 S1 Interface Fault

 Performance alarm helps investigating degradation of baseband unit, resource

congestion and etc.
 Missing neighbor or wrong neighbor configuration of Top N cells could be diagnosed
from checking the number of handover failure due to missing neighbor relationship:
 Check the number of intra-frequency handover initiation failures because the
adjacent cell is not on the NRT of the source cell (L.IntraFreqHO.NoNRT), and
verify if there is missing intra-frequency neighbor.
 Check the number of inter-frequency handover initiation failures because the
adjacent cell is not on the NRT of the source cell (L.InterFreqHO.NoNRT), and
verify if there is missing inter-frequency neighbor.
 Check the number of inter-duplex-mode handover initiation failures because
the adjacent cell is not on the NRT of the source cell (L.InterFddTddHO.NoNRT)
and verify if there is missing inter-duplex-mode neighbor.
 Inappropriate handover parameter of Top N cells could be diagnosed from checking
the percentage of UE reestablishment, target cell of reestablishment, as inappropriate
handover parameter usually causing numerous handover failure and reestablishment:
 Intra-frequency handover parameter: Ocs, Ocn
 Inter-frequency measurement trigger parameter: A2 threshold
 Inter-frequency A3 handover parameter: Ocs, Ocn, Ofs, Ofn, timetotrigger (A3)
 Inter-frequency A4 handover parameter: Ocn, Ofn, A4 threshold, timetotrigger
(A4)
 Coverage or interference issues of Top N cells could be diagnosed by checking the ratio
of 64QAM and QPSK, BLER of PDSCH (DL channel quality), UL SINR of sub PRB (UL
channel quality):
 MSC ratio: If the ratio of QPSK is much higher than 64QAM, it indicates the
possibility of downlink weak coverage
 iBLER: If initial BLER is higher than 20%, it indicates coverage / interference
issues
 Average RSSI: if the average RSSI of each PRB is higher than -110dBm, it
indicates existence of uplink interference
 Parameter modification and feature activation could be checked from operation log of
cell
 To verify if the degradation is related to upgrade or cutover operation, check if there is
such operation near the KPI degradation time stamp.

 If the fault above is not found, then proceed in analyzing the statistics of handover
failure causes, referring to the troubleshooting step of TopN causes.
 Transmission performance alarm helps investigating degradation of transmission
equipment, transmission network congestion and transmission network performance
degradation. Network congestion troubleshooting should involves transmission
department.
 Troubleshooting steps of other above mentioned issues is similar to the
troubleshooting steps of Top N cells.

 Core network fault

 Calculate the ratio of L.HHO.Prep.FailOut.MME, if it is the Top N cause,
signaling tracing has to be performed (associates with EPC engineer) to analyze
the failure cause returned by EPC.
 No response from target cell
 No response received from target cell during the end of the S1 or X2-based
handover preparation stage, timer expired and it is counted in target cell no
response.
 Calculate the ratio of L.HHO.Prep.FailOut.NoReply, if it is the Top N cause,
analyzes the Top N target cells flow control, overload and hardware fault
issues.
 This KPI is categorized into intra-frequency, inter-frequency and inter-duplex-
mode.
 Preparation failure in target cell
 Target cell responds with handover preparation failure due to admssion
control, resource congestion, resource distribution failure or target cell fails to
identify handover request.
 Analyze L.HHO.Prep.FailOut.PrepFailure, identify the problematic cells and
check their neighbor list configuration, target cell load and PRACH resource
configuration

 Handover cancellation by source cell

 Source eNodeB decided to cancel a handover request by sending HANDOVER
CANCEL to target during the end of the S1 or X2-based handover preparation
stage, this will be counted in L.HHO.Prep.FailOut.HOCancel.
 During X2-based handover preparation, source eNodeB starts timer RELOCprep
after sending Handover Request message, if there is no response from target
after the timer expired, source eNodeB sends Handover Cancel to target
eNodeB and that will be counted in L.HHO.Prep.FailOut.HOCancel.
 During S1-based handover preparation, source cell starts timer TS1RELOCprep
after sending Handover Required message, if there is no response from target
after the timer expired, source cell sends Handover Cancel to MME and that
will be counted in L.HHO.Prep.FailOut.HOCancel.
 Scenario 1: Source eNodeB sent handover command to UE, but UE performs
connection reestablishment with source eNodeB successfully before the
completion of the handover, therefore source eNodeB sends Handover Cancel
to target; scenario 2: during handover out procedure, there is no PDP context
setup of the UE with a third-party cell, source eNodeB triggers Handover
Cancel after receiving private message from UE. These two scenarios will be
counted in L.HHO.Prep.FailOut.HOCancel (they will be counted in
L.HHO.InterFddTdd.FailOut.HOCancel if it is inter-duplex-mode handover).
 Validity checking failure
 Source cell receives Handover Command from MME during S1-based handover
preparation, or source cell receives Handover Request Acknowledge message
from target cell during X2-based handover preparation, source cell decides to
cancel the handover due to the failure in validity checking of the messages.
 Procedure conflict
 During S1-based or X2-based handover preparation, if there is a a concurrent
CS fallback or flow control procedure, source cell prioritizes the execution of
these procedure, and cancelling the handover execution by sending Handover
Cancel message.

 Hardware / performance fault

 For hardware fault, refer to alarm processing guideline; for performance fault,
expand the troubleshooting area to any relevant feature license or hardware.

 After hardware upgrade, cutover or expansion of transmission or core network, the

wireless configuration has to be updated concurrently. For the problematic eNodeB
which failed to update configuration in batches, the parameter update has to be
executed promptly after the eNodeB is back to normal operation.

 Handover preparation failure in target cell

 Target cell fails to identify handover target, need to optimize neighbor relationship with source
 Flow control, overload, resource congestion in target cell may cause handover preparation failure,
need to check Top N neighbor cells user number, load status, control plane resource utilization rate
and capacity configuration, optimizes the RACH configuration, license and cell capacity
 Handover cancellation during handover preparation
 TRELOCprep is set to be too short, causing insufficient preparation time in target network. A short
value of TRELOCprep is not recommended.
 Handover cancellation during handover execution
 Troubleshoot premature handover, delayed handover, admission failure in target, referring to the
ratio of reestablishment after handover failure, target cell of reestablishment and signal quality of
the target
 Validity checking issues
 For equipment of same vendor, check the compatibility of terminal capability and equipment version
 For equipment of different vendors, check the consistency between vendor protocols, handover
between vendor equipment is related to signaling analysis, protocol version, processing algorithm
discrepancy which leading to interworking signaling failed to pass validity check.
 Failure in validity check usually related to signal decoding, protocol implementation capability and
etc, needs to feedback to vendors for cross-working
 Flow Conflict
 Minor handover cancellation due to flow conflict could be ignroed, eNodeB and core network are
with relevant flow control algorithm
 If there are numerous of flow conflict, feedback to vendor for flow analysis, and solution




 Target cell unknown is usually attributed to two causes below:

 Information in Target ID does not match with configuration in MME:
 Handover required message carry key ID information such as PLMN,
eNodeB ID, TAC; if these information do not match with the
configuration in MME, it leads to handover preparation failure with the
cause of “Unknown-targetid”.
 Missing configuration of SCTP causing incomplete eNodeB configuration in
MME:
 Only TAC and PLMN need to be configured in MME, other information
will be obtained by sending request to eNodeB via SCTP link. Therefore,
any missing or wrong configuration of SCTP link will cause incomplete
information in MME side, failed to acquire eNB ID of target eNodeB,
and then responds “Unknown-targetid” to source cell for handover
preparation failure

 After checking core network configuration, it is found that target cell Yulongxin_HLH
belongs to POOL3, and there are 5 MMEs under POOL3


Handover Success Rate

Xingang_HLH-1 Xingang_HLH-2 Xingang_HLH-3


 eNodeB records the statistic of number of ping-pong handover and number of

consecutive ping-pong handover between specific cells:
 Ping-Pong Handover: User handover out and in between specific cells (with
neighbor relationship defined) within ping-pong handover timer (default value
of 2s), it is counted in performance counter L.HHO.Ncell.PingPongHo.
 Consecutive Ping-Pong Handover: User handover out and in between specific
cells (with neighbor relationship defined) for N times (N is UePingPongNumThd,
with default value of 5), and the average camping time in the target cell during
the most recent N ping-pong handovers is less than PingpongTimeThd (default
value is set to 2s). Then it is counted under
L.HHO.NCell.PingPongHo.Consecutive.

 Overlapped coverage is a scenario where an area is covered by numerous cells with

equivalent RSRP, causing UE handover frequently between few cells
 Inappropriate handover parameter causes UE handover in and out between specific
cells or specific frequencies, that is a ping-pong handover
 Signal fluctuation such as discontinuous coverage blocked by street buildings, causing
best cell changed frequently, hence frequent handover occurs and poor user
experience.

 Overlapped coverage
 With the condition of serving cell RSRP > -110dBm, overlapped coverage is
identified if there are equals or more than 3 neighbor cells with RSRP difference
is around ±6dB.
 If default handover parameters used in network, usually neighbor cells which fulfill
event A3 criteria are with around 6dB RSRP difference with serving cell. Therefore in
this scenario, the number of neighbor cells with high number of ping-pong handover
could be used in identifying existence of ping-pong handover.
 If the number of neighbor cells with high number of ping-pong handover is
more than 3, this indicates possibility of overlapped coverage.
 To further verify the area with overlapped coverage, perform drive test in the
mid-point and far-point of the suspected cells.


 Overlapped coverage could be optimized by RF tuning (adjustment of downtilt,

antenna azimuth and transmit power), improving dominance of best serving cell, and
thus minimizing number of ping-pong handover
 To counteract ping-pong handover with most neighbors, increase Ocs about 1-3dB,
with time-to-trigger of intra-frequency and inter-frequency handover not shorter than
640ms. After adjustment, monitor the post-adjustment performance, further
adjustment of Ofs / Ofn could be performed to control the difficulties of handover to a
specific frequency.


Weixing-HLH_1,
PCI: 201,
RSRP = -116dBm




Intra-LTE Handover Parameter

Handover Event
Parameter ID Huawei Parameter
Event Formula
Ofn QoffsetFreq（Ofn）
Ocn CellIndividualOffset
Intra- A3： Hys IntraFreqHoA3Hyst
frequency Mn+Ofn+Ocn-Hys > Ofs QoffsetFreq（Ofs）
Ms+Ofs+Ocs+Off
A3 Ocs CellSpecificOffset
Off IntraFreqHoA3Offset
timeToTrigger(A3) IntraFreqHoA3TimeToTrig
Hys InterFreqHoA1A2Hyst
A1：Ms-Hys>Thresh timeToTrigger(A1/A2) InterFreqHoA1A2TimeToTrig
A2：Ms+Hys<Thresh A1_Thresh A3InterFreqHoA1ThdRsrp
A2_Thresh A3InterFreqHoA2ThdRsrp
Inter- Ofn QoffsetFreqConn（Ofn）
frequency Ocn CellIndividualOffset
A2+A3 A3：Mn+Ofn+Ocn-Hys
Hys IntraFreqHoA3Hyst
Ofs QoffsetFreq（Ofs）
> Ms+Ofs+Ocs+Off
Ocs CellSpecificOffset
Off InterFreqHoA3Offset
timeToTrigger(A3) IntraFreqHoA3TimeToTrig
A2：Ms+Hys<Thresh A1_Thresh InterFreqHoA1ThdRsrp
Inter- A2_Thresh InterFreqHoA2ThdRsrp
frequency Ofn QoffsetFreqConn（Ofn）
A2+A4 A4：Mn+Ofn+Ocn-Hys
Ocn CellIndividualOffset
Hys InterFreqHoA4Hyst
> Thresh
A4_Thresh InterFreqHoA4ThdRsrp
timeToTrigger(A4) InterFreqHoA4TimeToTrig
A2：Ms+Hys<Thresh A1_Thresh InterFreqHoA1ThdRsrp
A2_Thresh InterFreqHoA2ThdRsrp
Hys（A5_1） InterFreqHoA1A2Hyst
Inter-
Thresh1 InterFreqHoA2ThdRsrp
frequency timeToTrigger(A5_1) InterFreqHoA1A2TimeToTrig
A2+A5 A5：Ms+Hys<Thresh1 Ofn QoffsetFreqConn（Ofn）
且Mn+Ofn+Ocn-Hys >
Thresh2 Ocn CellIndividualOffset
Hys InterFreqHoA4Hyst
Thresh2 InterFreqHoA4ThdRsrp
timeToTrigger(A5_2) InterFreqHoA4TimeToTrig

 For intra-eNodeB neighbor, the basic configuration of the cell existed in the source cell
hence there is no need of the step of adding external cell, only the neighboring cell
defining step is required in the source cell.
 For inter-eNodeB neighbor, basic configuration of the neighbor cell does not exist in
the source eNodeB, hence add external cell step is required before defining the
neighboring cell.
 Modify external cell: MOD EUTRANEXTERNALCELL
 Remove external cell: RMV EUTRANEXTERNALCELL
 Modify intra-frequency neighbor cell: MOD EUTRANINTRAFREQNCELL
 Remove intra-frequency neighbor cell: RMV EUTRANINTRAFREQNCELL

 Modify neighboring frequency: MOD EUTRANINTERNFREQ

 Remove neighboring frequency: RMV EUTRANINTERNFREQ
 Modify external cell: MOD EUTRANEXTERNALCELL
 Remove external cell: RMV EUTRANEXTERNALCELL
 Modify inter-frequency neighbor cell: MOD EUTRANINTERFREQNCELL
 Remove inter-frequency neighbor cell: RMV EUTRANINTERFREQNCELL

 Modify inter-RAT neighboring frequency band: MOD CDMA2000BANDCLASS

 Remove inter-RAT neighboring frequency band: RMV CDMA2000BANDCLASS
 Modify neighboring frequency: MOD CDMA2000NFREQ
 Remove neighboring frequency: RMV CDMA2000NFREQ
 Modify external cell: MOD CDMA2000HRPDEXTCELL
 Remove external cell: RMV CDMA2000HRPDEXTCELL
 Modify neighbor cell: MOD CDMA2000HRPDNCELL
 Remove neighbor cell: RMV CDMA2000HRPDNCELL

 Modify inter-RAT neighboring frequency band: MOD CDMA2000BANDCLASS

 Remove inter-RAT neighboring frequency band: RMV CDMA2000BANDCLASS
 Modify neighboring frequency: MOD CDMA2000NFREQ
 Remove neighboring frequency: RMV CDMA2000NFREQ
 Modify external cell: MOD CDMA20001XRTTEXTCELL
 Remove external cell: RMV CDMA20001XRTTEXTCELL
 Modify neighbor cell: MOD CDMA20001XRTTNCELL
 Remove neighbor cell: RMV CDMA20001XRTTNCELL


LTE Handover Fault Diagnosis (KPI) ISSUE1.00

Uploaded by

Document Information

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

LTE Handover Fault Diagnosis (KPI) ISSUE1.00

Uploaded by

Copyright:

Available Formats

LTE Handover Fault Diagnosis (Traffic KPIs) P-0

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Triggering for Measurement

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Event Criteria Action

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

6. UE perform random access procedure following the handover command.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Number of inter-eNodeB intra-frequency HO outgoing execution attempts is counted at point B, and

Confidential Information of Huawei. No Spreading Without Permission

 Number of inter-eNodeB inter-frequency HO outgoing execution attempts is counted at point B, and

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Number of intra-frequency outgoing handover preparation failures because the

Number of inter-duplex-mode outgoing handover preparation failures because

Number of inter-duplex-mode outgoing handover preparation failures because

Number of failed inter-duplex-mode outgoing handover preparations because

L.HHO.InterFddTdd.FailOut.HOCancel Number of inter-eNodeB inter-duplex-mode outgoing handover cancellations

Number of inter-duplex-mode outgoing handover preparation failures due to

Confidential Information of Huawei. No Spreading Without Permission

 Successful RRC Connection Reestablishment (performed by UE after handover failure) is included in

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Counter Name Counter Description

Confidential Information of Huawei. No Spreading Without Permission

Counter Name Counter Description

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 User-defined KPI is inactive by default, it could be activated in Measurement ->

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Handover Fault Performance Counter

Handover L.HHO.Prep.FailOut.PrepFailure L.HHO.Prep.FailOut.RNL

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Counter Name Description

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 Sub-counters of certain handover failure performance counter:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission