Professional Documents
Culture Documents
Guide To Optimizing LTE Service Drops PDF
Guide To Optimizing LTE Service Drops PDF
Guide to Optimizing
LTE Service Drops
www.huawei.com
Huawei Confidential
Change History
Date
Version
Description
2012.1.10
1.0
Completed
the draft.
Huawei Confidential
Reviewer
Page 2
Author
Abstract
This document
Defines the call drop rate.
Describes how to use the related counters to diagnose a call drop
Huawei Confidential
Page 3
Content
Definition of the Service Drop Rate
Symptoms of a Service Drop
Cause Analysis and Data Processing
Huawei Confidential
Huawei Confidential
Page 5
I.
Does not receive the DEACTIVATE EPS BEARER CONTEXT REQUEST message and,
Does not receive the DETACH REQUEST message from the MME and,
In this case, if the ERAB num minus the eps-BearerIdentity contained in the ReleaseList is 0, the UE
transits to RRC_Idle mode.
II.
Does not receive the DEACTIVATE EPS BEARER CONTEXT REQUEST message and,
Does not receive the DETACH REQUEST message from the MME and,
Receives the RRCConnectionRelease message and the RLC layer performs data transmission in the
last 4s in any direction.
Huawei Confidential
Page 6
Huawei Confidential
Page 7
Huawei Confidential
Page 8
As shown in point A of Fig1, if the eNodeB sends the E-RAB RELEASE INDICATION message
containing a cause value that is not "Normal Release", "User Inactivity", "cs fallback triggered",
or "Inter-RAT redirection", L.E-RAB.AbnormRel increments by 1. If the E-RAB RELEASE
INDICATION message requests release of multiple e-RABs, L.E-RAB.AbnormRel increments
by 1 for each e-RAB.
As shown in point A of Fig2, when the eNodeB sends the UE CONTEXT RELEASE REQUEST
message to the MME, the eNodeB releases all e-RABs of the UE. If the release cause is not
"Normal Release", "User Inactivity", "cs fallback triggered", or "Inter-RAT redirection", L.ERAB.AbnormRel increments by 1 for each release.
Note:
The eRAB Release procedure releases one or multiple e-RABs. After the procedure, at least the default bearer is maintained.
The UE Context Release procedure releases all connections. No bearer is maintained after this procedure.
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
Page 9
Currently, there are five counters that count e-RAB abnormal releases by the
network:
Huawei Confidential
Page 10
Note: L.E-RAB.AbnormRel.MME does not include L.ERAB.AbnormRel. A release initiated by the EPC is not
counted as a call drop in eRAN2.1SPC400 and later
versions.
Huawei Confidential
Page 11
As shown in point A of Fig3, if the eNodeB sends the ERAB RELEASE INDICATION message to the MME with a
cause value indicating a radio error, L.ERAB.AbnormRel.Radio increments by 1. If the cause value
indicates a transmission network error, L.ERAB.AbnormRel.TNL increments by 1. If the cause value
indicates network congestion, L.E-RAB.AbnormRel.Cong
Huawei Confidential
Page 12
Huawei Confidential
Page 13
Content
Definition of the Service Drop Rate
Symptoms of a Service Drop
Cause Analysis and Data Processing
Huawei Confidential
UE receives
system
information.
Huawei Confidential
Time
segment of
call drops
Huawei Confidential
Content
Definition of the Service Drop Rate
Symptoms of a Service Drop
Cause Analysis and Data Processing
Huawei Confidential
Huawei Confidential
Page 18
Huawei Confidential
Page 19
cells of degraded call drop rate and top cells of number of e-RAB
abnormal releases.
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
Page 20
Huawei Confidential
Page 21
Entire-network problem
After one-fifth of the top cells of high call drop rate and large number of e-RAB
abnormal releases are removed from calculation of the entire-network call drop
performance, if the performance is not significantly improved, the call drop
problem is defined as an entire-network problem.
Huawei Confidential
Page 22
Top-UE problem
After one-fifth of the top UEs are removed from calculation of the entire-network
call drop performance, if the performance is significantly improved to the
expected value, the problem is defined as a top-UE problem.
Note
Currently, the CHR of the LTE system provides no information about the terminal type. The terminal type is
provided by complaining users or inferred from the symptoms.
Due to security concerns, the eNodeB does not provide IMSI information. Therefore, top UEs can be
inferred only from the TMSI, not from the IMSI.
Huawei Confidential
Page 23
Traffic statistics can be obtained from the M2000/PRS. For details, see
section 2.3.3 of LTE Service Drop Troubleshooting and Optimization
Guide.doc.
Signaling trace can be performed on the M2000. For details, see section 2.2.2
of LTE Service Drop Troubleshooting and Optimization Guide.doc.
The drive test data can be obtained by performing a drive test. For details, see
section 2.1.3 of LTE Service Drop Troubleshooting and Optimization
Guide.doc.
Huawei Confidential
Page 24
Probe
Acquisition Method
Usage
LMT.
http://support.huawei.com/support/pages/editionctrl/catalog/Sh
owVersionDetail.do?actionFlag=clickNode&node=000001099
409&colID=ROOTENWEB|CO0000000174
NIC
PRS
OMstar
http://support.huawei.com/support/pages/editionctrl/catalog/Sh
owVersionDetail.do?actionFlag=clickNode&node=000001099
information.
389&colID=ROOTENWEB|CO0000000174
http://support.huawei.com/support/pages/editionctrl/catalog/Sh
owVersionDetail.do?actionFlag=clickNode&node=000001468
Batch data collection tool
041&colID=ROOTENWEB|CO0000000174
http://support.huawei.com/support/pages/editionctrl/catalog/Sh
Parses and analyzes traffic statistics of the
owVersionDetail.do?actionFlag=clickNode&node=000001430
eNodeB.
110&colID=ROOTWEB|CO0000000065
http://support.huawei.com/support/pages/editionctrl/catalog/Sh
Parses and analyzes original traffic statistics
owVersionDetail.do?actionFlag=clickNode&node=000001470
and CHR. Compares parameters.
066&colID=ROOTENWEB|CO0000000174
signaling, scheduling, and signal quality
Huawei Confidential
Signaling Trace
Management
interface of the
M2000
Huawei UE
Probe
Huawei Confidential
Huawei
UE
Probe
eNodeB TrafficReview
Huawei Confidential
If the message
contains the IE
targetPhysCellId, the
message is a
handover command.
Huawei Confidential
Trend analysis
Obtain the call drop KPI of the global network for at least one to two
weeks, or two weeks before and one week after the upgrade in case
an upgrade has been performed. An example is shown in the upper
right figure.
Cause analysis
Top analysis
Analysis of the traffic statistics can show the top cells and top
time segments that have the highest RRC connection setup
failure and e-RAB setup failure, as shown in the lower right
figure.
Huawei Confidential
Page 29
Standard interface trace (a major means): Obtain top cells and top time segments by
analyzing the traffic statistics, start the standard interface trace on the top cells and at top
time segments, check which signaling procedure causes the call drop.
Single-UE global-network trace (a minor means): Query the IMSI of a TMSI from the
EPC, start the global-network trace of this IMSI. This method is effective for ensuring VIP
service.
Huawei Confidential
Page 30
The drive test can show whether the UE or eNodeB fails to receive the signaling
message; the downlink RSRP/SINR obtained from the drive test indicates the
downlink channel quality; the uplink transmit power indicates whether the uplink is
insufficient.
The UE log shows whether the UE correctly processes the received signaling
messages and whether the UE suddenly does not send any data.
Huawei Confidential
Page 31
Content
Definition of the Service Drop Rate
Symptoms of a Service Drop
Cause Analysis and Data Processing
Huawei Confidential
Analysis Action
1. Global parameter
configuration check
2. Inspection of EPC
parameter change
Deliverables
Closing Action
1. Distribution of the
causes and top causes
2. Actions that affect
the call drop rate
Huawei Confidential
Page 33
Neighbor
relationship
check
Major event
check
Analysis Action
Check whether batch
operations affecting the
global network are
recorded and whether
neighboring cells and PCI
are re-planned.
Check for missed
configuration of neighbor
relationship. Deployment
of scattered sites causes
incorrect neighbor
relationship.
Check for allocation of a
large quantity of phone
numbers and major
activity (such as
ceremony, holidays, and
games)
Deliverables
Closing Action
Note
The standard actions of a comprehensive problem (entire-network plus top-cell problem) are a
combination of the checklist for the entire-network problem and the checklist for the top-cell
problem.
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
Page 34
Analysis Action
Preliminary
analysis of
traffic statistics
of top sites
Deliverables
Closing Action
Huawei Confidential
Page 35
Analysis Action
Deliverables
Closing Action
Operation
Check whether batch
Records of batch operations
Analyze the impact of batch
record check operations affecting the global affecting the global network
operations on the call drop
of top sites network are recorded and
rate. Determine whether the
whether neighboring cells and
batch operations can be rolled
PCI are re-planned.
back.
Neighbor
Check for missed
Missed configuration of
Add neighboring cells that are
relationship configuration of neighbor
neighbor relationship
not configured in the neighbor
check of top relationship. Scattered site
relationship. Check whether
cells
deployment or network
the call drop KPI is restored.
optimization leads to incorrect
neighbor relationship.
Coverage
Analyze the MCS and CQI
Coverage evaluation report of Perform network optimization
check of top contained in the traffic
top cells
to optimize the coverage.
cells
statistics, CHR, and drive test
data to check for coverage
overlap or weak coverage of
the top cells.
Interference Analyze the real-time trace
Interference evaluation report Find out and remove the
check of top data of the top cells to check of top cells
interference.
cells
for inter-modulation
interference and external
interference.
Check whether the major
Major event Check for allocation of a large 1. Check the terminal type
quantity
of
phone
numbers
and
involved
in
the
number
event is coupled to the
check
major activity (such as
allocation, quantity of number deterioration of the call drop
ceremony, holidays, and games)allocation, and subscription
rate in the time dimension.
in the vicinity of top cells.
policy.
2. Determine the range and time
segment of the major event.
HUAWEI TECHNOLOGIES CO., LTD.
Huawei Confidential
Page 36
Fault Description
If the abnormal release is recorded in the counter L.E-RAB.AbnormRel.Radio, the abnormal release is
caused by Uu interface and occurs in a non-handover scenario.
Possible Cause
The abnormal release is caused by weak coverage, uplink interference, or abnormal UE that lead to
maximum number of RLC retransmissions, out-of-sync, or failure of signaling interactions. For details about
diagnosing the interference problem, see LTE RF Channel Check and Troubleshooting Guide.
Analyze the CHR to check whether some top UEs have the highest count.
If the call drop is caused by a factor other than the signaling procedures, analyze the DRB scheduling at layer 2 to
determine whether the call drop is caused by weak coverage or interference.
If the call drop is caused by signaling procedures, observe the last ten signaling messages to determine the faulty
signaling procedure. Determine whether the fault of the signaling procedure is due to failure to receive or process the
signaling messages by either the UE or eNodeB.
UEM_UECNT_REL_RB_RECFG_FAIL_RRC_CONN_RECFG_CMP_FAIL.
Huawei Confidential
Page 37
Fault Description
Obtain the top cells that have the highest counter L.E-RAB.AbnormRel.HOFailure,
analyze the pairs of source and target cells to obtain the top target cells that have the
Analyze the CHR of the source and target cells to determine whether the handover
failure is caused by failure to receive the handover command or random access failure.
Examples of the cause values are UEM_UECNT_REL_HO_OUT_X2_REL_BACK_FAIL
and UEM_UECNT_REL_HO_OUT_S1_REL_BACK_FAIL.
Optimize the handover parameters and neighbor relationship and check whether the call
drop KPI is improved.
Huawei Confidential
Page 38
Fault Description
Possible Cause
This call drop is caused by the abnormal transmission between the eNodeB and MME,
Check for alarms about the transmission network. Clear the alarms and check whether
the problem of abnormal release is solved.
Observe the M2000 and check whether alarms about the transmission network are
recorded in the M2000.
the logs and submit them to R&D engineers for further analysis.
Huawei Confidential
Page 39
Fault Description
Possible Cause
This call drop is caused by radio resource congestion, such as exceeding the
If the long-term congestion of a top cell leads to call drops, a short-term solution is
to enable the MLB algorithm or inter-operation to alleviate the load of the local cell.
Enable the MLB algorithm and check whether the congestion problem is alleviated.
Huawei Confidential
Page 40
Fault Description
Analyze the S1 interface trace of the top cells to obtain the distribution of the cause value.
Discuss with the EPC engineers about the analysis result and signaling messages.
Huawei Confidential
Page 41
Deliverables
If the front-line engineers fail to solve a difficult problem, collect the following
information and submit them to R&D engineers for further analysis:
Topology information, engineering parameters, and configuration files of the top sites
IFTS trace and cell trace. These traces generate large amount of data. Only the data of the top cells and
The single-UE trace is used for in-depth diagnosis of top UEs. The entire-network single-UE trace can be
performed by using the IMSI queried from the EPC using the TMSI.
Huawei Confidential
Page 42
Content
Definition of the Service Drop Rate
Symptoms of a Service Drop
Cause Analysis and Data Processing
Huawei Confidential
As shown in the upper right figure, the cause value of the abnormal
release is RRC_REEST_SRB1_FAIL.
As shown in the middle right figure, this problem occurs repeatedly
from 11:51 o'clock to 18:49 o'clock in cell 0.
As shown in the lower right figure, the TMSI column shows that this
problem is contributed by a single UE whose TMSI is C2 B0 B0 40
and the cause value is "Reconfiguration Failure".
As shown in the lower left figure, the message type indicates that
this reconfiguration message is not a handover command or
measurement control. This message is probably for reconfiguration
of the CQI, SRS, or transmission mode (TM). Upon reception of the
RRC CONN REESTAB message, the UE does not respond.
Therefore, the eNodeB releases the UE in 5s.
Huawei Confidential
Page 44
Case 2: UE Exception
Analysis of the CHR shows that the cause value of the abnormal release is
The TMSI column indicates that this problem is contributed by a single UE whose
TMSI is C2 7F 20 56.
The last 16 DRB scheduling procedures at a period of 64ms indicate that the
symptoms are similar. The symptoms are that the UE encounters suddenly
terminated data transmission shortly after the access. The duration from access
to release is tens of seconds to 2 minutes, indicating that the problem is not
caused by script test. The access type is MO-DATA, indicating that the user is
performing a service.
Huawei Confidential
Page 45
Huawei Confidential
Page 46
Release cause
TGT_ENB_RB_RECFG_FAIL is the cause value contained in the RB
reconfiguration failure message during a handover.
The symptom is that after the UE is successfully handed over to the target
cell, the target eNodeB sends the PATH SWITCH REQ ACK message to
the MME and, in 100 ms, sends the UE CONTEXT REL REQ message
containing the cause value "unspecified". The lower left figure shows the
last ten signaling messages.
Fault diagnosis
During the handover procedure, the EPC delivers the PATH_SWITCH_ACK message
containing the downlink AMBR value that is inconsistent with the downlink AMBR
contained in the S1/X2 handover request. Analysis shows that this is a defect of the
RR module. The upper-layer control module of the RR module sends the AMBR
Update message to the RB module who thinks that there is no need to deliver a
reconfiguration message to the UE. Therefore, the RB module returns a null value to
the upper-layer control module. However, the upper-layer control module regards this
return value as an exception and releases the UE. This problem is solved in
eRAN2.1SPC430.
Huawei Confidential
Page 47
IRHO_REDIRECTION_TRIGER is the
release caused by inter-RAT redirection. In
eRAN2.1SPC400/SPH401, this cause value
is counted as a call drop, as shown in the
following figure.
Huawei Confidential
Page 48
On December 11, the service drop rate of the entire network deteriorates for the Tele2 900M,
Telenor 900M, and Tele2 2.6G bands, as shown in the following figure.
Huawei field engineers discussed with the customer and suspected the EPC. However, they got
no positive answer.
Huawei Confidential
Page 49
Release cause
UE_RESYNC_TIMEROUT_REL_CAUSE indicates that the abnormal release is caused by resynchronization upon timeout of the
resynchronization timer. The same problem is recorded by the standard interface trace as "Radio Connection With UE Lost".
UE_RLC_UNRESTORE_IND indicates that the abnormal release is caused by restoration failure after exceeding the maximum number of RLC
retransmissions. The same problem is recorded by the standard interface as "Radio resources not available".
UE_RESYNC_DATA_IND_REL_CAUSE indicates that the abnormal release is caused by resynchronization triggered L2 report data. The same
Cause analysis
The DRB scheduling information at the last 4 512ms and 16 64ms periods shows that most abnormal releases are caused by suddenly
terminated data transmission, possibly caused by unplugging the data card or UE fault. The following figure shows the CHR information.
Huawei Confidential
Page 50
Release cause (Radio Connection With UE Lost recorded in the standard interface trace)
The last 10 signaling messages as shown in the following figure indicates that after sending the
RRC_CONN_REESTAB message, the eNodeB fails to receive the RRC_CONN_REESTAB_CMP
message from the UE before the 5s timer on the Uu interface expires.
The L2 scheduling information shows that the UE sends the ACK message upon reception of the
RRC_CONN_REESTAB message.
We suspect that the problem is caused by failure of some UEs to send the
RRC_CONN_REESTAB_CMP message. Some Samsung UEs have such a problem.
Huawei Confidential
Page 51
Thank you
www.huawei.com