Professional Documents
Culture Documents
LTE CONFIDENTIAL
Product Version Total 34 pages
eRAN
Reviewed By Date
Reviewed By Date
Approved By Date
Change History
Date Issue Change Description Author
Distribution List
Copy No. Holder's Name & Role Issue Date
Contents
2 Solution Overview........................................................................................................................3
2.1 Scenarios Analysis..........................................................................................................................................................3
2.2 Benefits...........................................................................................................................................................................3
2.3 General Solution.............................................................................................................................................................3
3 Application Guide.........................................................................................................................4
3.1 Solution to Access-related KPI Improvement................................................................................................................4
3.1.1 Description..................................................................................................................................................................4
3.1.2 Service-related Parameter Optimization....................................................................................................................11
3.1.3 Effect Evaluation Methods........................................................................................................................................12
3.1.4 Application Guide......................................................................................................................................................12
3.2 Solution to Service-Drop-related KPIs Improvement..................................................................................................13
3.2.1 Description................................................................................................................................................................13
3.2.2 Service-related Parameter Optimization....................................................................................................................15
3.2.3 Effect Evaluation Methods........................................................................................................................................17
3.2.4 Application Guide......................................................................................................................................................17
3.3 Solution to Handover-related KPIs Improvement........................................................................................................17
3.3.1 Description................................................................................................................................................................17
3.3.2 Service-related Parameter Optimization....................................................................................................................20
3.3.3 Effect Evaluation Methods........................................................................................................................................21
3.3.4 Application Guide......................................................................................................................................................21
4 Case Study....................................................................................................................................22
Issue 01 (2017-01-25) Huawei Proprietary and Confidential iii
Copyright © Huawei Technologies Co.,
Ltd.
LTE KPI Improvement Solution User Guide CONFIDENTIAL
5 Reference Documents..................................................................................................................29
1 Introduction
1.1.2 Scope
This document serves as a guide to Huawei solutions of the network KPI improvement for
different scenarios.
This document helps customers choose appropriate feature or function portfolio for their
network scenarios. The working principles, deployment, and maintenance of each feature are
not described in this document and are included in the corresponding feature parameter
description.
1.1.3 Organization
Chapter Description
1.1.5 Lifecycle
The draft of this document was completed at TR5.
This document was updated and finalized at TR6.
1.3 Assumptions
None
2 Solution Overview
2.2 Benefits
The solution is designed for scenarios of low access success rate and high service drop rate. It
brings better user experience by improving access-, service-drop-, and handover-related KPIs.
The solution describes how to evaluate, analyze, and improve network KPIs.
3 Application Guide
Table 1.1 lists the causes of RACH access failures and the improvement measures.
Root sequence The following two methods Check and optimize the root sequence conflict.
conflict can detect root sequence
conflict:
Use the PRACH root
sequence conflict
detection function to
trigger the root
sequence conflict
exception alarm. For
details, see Random
Access Control and
RACH Optimization
Feature Parameter
Description.
Use the OMStar and
engineering parameters
to check neighboring
Air interface Periodic and repeated The failure can be gradually rectified as follows:
RACH access failures Optimize RF settings to reduce poorly covered areas.
occur.
Adjust the T300 timer. It is recommended that the T300
timer be set to 1000 ms.
Extend the cell radius or activate the extended cell range
feature in scenarios such as lakeside and riverside that
experience extended cell range. For details, see Extended
Cell Range Feature Parameter Description.
Select the NonContRaOptSwitch option of the
CellAlgoSwitch.RachAlgoSwitch parameter to enable
optimization for UEs that access the cell during
handovers at places of longer distances to the eNodeB
than the cell radius.
Enable the high-speed mobility feature in high-speed
scenarios. For details, see High Speed Mobility Feature
Parameter Description.
Table 1.2 lists the causes of RRC connection setup failures and the improvement measures.
Table 1.2 RRC connection setup failure category, cause for RRC connection setup failures,
symptom and improvement measure
RRC Connection Cause for RRC Symptom Improvement Measure
Setup Failure Connection Setup
Category Failures
Resource SRS resource L.RRC.SetupFail. The failure can be rectified using either of
insufficiency allocation failure ResFail.SRS > 0 the following methods:
If the number of UEs in a cell reaches the
maximum, you are advised to expand
the capacity of sites.
If the number of UEs in a cell does not
reach the maximum, it is recommended
that the SrsSubframeRecfSwitch
option of SrsAlgoSwitch be selected.
For details, see Physical Channel
Resource Management Feature
Parameter Description.
PUCCH resource L.RRC.SetupFail. The PUCCH resource allocation failure
allocation failure ResFail.PUCCH > refers to the SRI allocation failure. The
0 failure can be rectified using either of the
following methods:
If the number of UEs in a cell reaches the
maximum, you are advised to expand
the capacity of sites.
If the number of UEs in a cell does not
reach the maximum, it is recommended
that the SriPeriodAdaptive option of
PUCCHcfg be selected. For details, see
Admission and Congestion Control
Feature Parameter Description.
A limited number of L.RRC.SetupFail. Expand the capacity of sites whose
UEs ResFail.UserSpec resources are congested.
>0
Flow control or The RRC L.RRC.ConnReq. Measures are as follows:
overload Connection Request Msg.disc.FlowCtrl Expand the capacity of sites whose
message is discarded >0 resources are congested.
due to flow control.
If the expansion fails for the time being,
The RRC L.RRC.SetupFail. increase the value of the T302 timer to
Connection Reject Rej.FlowCtrl > 0 delay the repeated access time of UEs.
message is discarded
due to flow control.
Table 1.3 lists the causes of E-RAB setup failures and the improvement measures.
Table 1.3 E-RAB setup failure category, cause for E-RAB setup failures, symptom, and
improvement measure
E-RAB Setup Cause for E-RAB Symptom Improvement Measure
Failure Category Setup Failures
Transmission fault Insufficient L.E- Check for transmission alarms. For details,
downlink RAB.FailEst.TNL. see the alarm part in 3900 Series Product
transmission DLRes > 0 Documentation.
resources
Insufficient uplink L.E-
transport resources RAB.FailEst.TNL.
ULRes > 0
Resource Insufficient SRS L.E- The failure can be rectified using either of
deficiency resources RAB.FailEst.NoR the following methods:
adioRes.SRS > 0 If the number of UEs in a cell reaches the
maximum, you are advised to expand
the capacity of sites.
If the number of UEs in a cell does not
reach the maximum, it is recommended
that the SrsSubframeRecfSwitch
option of SrsAlgoSwitch be selected.
For details, see Physical Channel
Resource Management Feature
Parameter Description.
Insufficient PUCCH L.E- The PUCCH resource allocation failure
resources RAB.FailEst.NoR refers to the SRI allocation failure. The
adioRes.PUCCH > failure can be rectified using either of the
0 following methods:
If the number of UEs in a cell reaches the
maximum, you are advised to expand
the capacity of sites.
If the number of UEs in a cell does not
reach the maximum, it is recommended
that the SriPeriodAdaptive option of
PUCCHcfg be selected. For details, see
Admission and Congestion Control
Feature Parameter Description.
Insufficient L.E- Expand the capacity of sites whose
downlink licensed RAB.FailEst.NoR resources are congested, or increase
traffic volume adioRes.DLThrpLi licensed traffic volume.
c>0
Insufficient licensed L.E-
uplink traffic volume RAB.FailEst.NoR
adioRes.ULThrpLi
c>0
Core network fault The core network L.E- The failure can be gradually rectified as
fault RAB.FailEst.MM follows:
E>0 Work jointly with core network engineers
to check whether the value of the timer
on the core network side is too small.
Check based on the measures for air
interface faults.
Table 1.4 lists the feature names and reference documents involved in the solution.
Table 1.5 lists the features and functions involved in the solution.
LOFD-001094 Control Channel IRC Improves the anti-interference capability of the PRACH.
N/A PrachFalseAlarmDetSwitch Identifies the detection and discard of false alarms to reduce
Table 1.6 Cause for service drop, symptom and improvement measure
Cause for Symptom Improvement Measure
Service Drop
Transmission fault L.E-RAB.AbnormRel.TNL > 0 Check for transmission alarms. For details, see the
alarm part in 3900 Series Product Documentation.
Handover fault L.E-RAB.AbnormRel.HOFailure For details, see section 3.3 "Solution to Handover-
>0 related KPIs Improvement."
Uplink The value of Troubleshoot uplink interference.
interference L.UL.Interference.Avg is
significantly greater than the
normal in idle mode.
Air interface fault L.E-RAB.AbnormRel.Radio > 0 The failure can be gradually rectified as follows:
Optimize RF settings to enhance indoor coverage.
Adjust the QRxLevMin parameter value. The
adjusted value must meet the requirements for
cell edge coverage on live networks.
Increase the number of downlink RLC
retransmissions (indicated by
eNodeBMaxRetxThreshold) to enhance the
downlink transmission reliability.
Increase the value of TimeAlignmentTimer to
reduce uplink timing errors and achieve better
uplink time alignment performance.
Increase the value of the TrafficRelDelay
parameter for a higher probability of UE
reestablishments.
Increase the value of
WaitRrcConnSetupCmpTimer to increase
tolerance duration. For details, see Connection
Management Feature Parameter Description.
Select the SrbProbeSchSwitch option. For details,
see Scheduling Feature Parameter Description.
Enable the ANR feature to solve problems caused
by missing neighboring cells. For details, see
ANR Feature Parameter Description.
Enable the PCI conflict detection feature to solve
PCI conflicts. For details, see PCI Conflict
Detection and Self-Optimization Feature
Parameter Description.
Network L.E-RAB.AbnormRel.Cong > 0 Expand the capacity of sites whose resources are
congestion congested.
A small sum of The sum of the L.E- Decrease the value of the UeInactiveTimer
normal releases RAB.NormRel is significantly parameter to increase the number of normal UE
small. releases and avoid false high service drop rate
caused by small number of normal releases.
RRC connection L.RRC.ReEstFail.NoCntx > 0 The failure can be rectified as follows:
reestablishment Select the RrcReestOptSwitch option to increase
failure the reestablishment success rate and reduce service
drop rate.
Table 1.7 lists of features and reference documents involved in the solution.
Table 1.8 lists the features and functions involved in the solution.
LOFD-002002 ANR Management Enables the neighboring cell self-addition and self-
optimization functions to reduce the service drop rate caused
by missing or incorrect neighbor relationships.
LOFD-002007 PCI Conflict Detection & Checks PCI conflicts and solves these problems to prevent
Self-Optimization service drops caused by improper handover or PCI conflicts.
N/A SrbProbeSchSwitch Improves the signaling feedback success rate.
N/A Reestablishment in Controls the eNodeB to support reestablishment in enhanced
enhanced scenarios scenarios, increases the reestablishment success rate, and
decreases the service drop rate.
Table 1.9 Handover failure category, handover failure cause, symptom, and improvement measure
Handover Handover Failure Symptom Improvement Measure
Failure Category Cause
There are two The cell information Troubleshoot using either of the
different PCIs, but in MR is inconsistent following measures:
only one PCI is with that in handover Add missing neighbor relationships.
configured in the commands.
neighbor
Enable the ANR function. For details,
relationship. see ANR Management Feature
Parameter Description.
Overshoot coverage Engineering Optimize RF settings.
parameters indicate
that top neighboring
cells with handover
failures experience
overshoot coverage.
Poor coverage Engineering The failure can be gradually rectified as
parameters indicate follows:
that top neighboring Optimize RF settings.
cells with handover
failures experience
Set the HoRarPwrEnhancedSwitch
overshoot coverage. parameter on. For details, see Power
Control Feature Parameter
Description.
Change the RarAndPagingCR
parameter value from 117 to 54.
Change the T304ForEutran
parameter value from 500 ms to 1000
ms.
Handover failures of Inter-frequency Select the
top UEs handovers of INTER_FREQ_HO_SWITCH_OFF
abnormal UEs fail. option of the
UeCompat.BlkLstCtrlSwitch parameter
so that the eNodeB performs inter-
frequency redirection after receiving
inter-frequency measurement reports
from abnormal UEs.
Based on the handover failure cause, symptom, and improvement measure described in the
preceding table, Table 1.10 lists the feature ID, feature name, and reference document for each
solution.
Table 1.11 lists the features and the functions in the solution.
LOFD-002002 ANR Management Enables the neighboring cell self-addition and self-optimization
functions to reduce the service drop rate caused by missing or
incorrect neighbor relationships.
N/A Handover RAR Power Enables this function in downlink poor coverage or interference
Enhance scenarios to improve the preamble access success rate and
handover success rate dedicated to only one UE.
CELLDLSCHALGO RarAndPagingCR Code Rate for Allows higher Set the parameter to
Random Access reliability of random 54. If further
Response and access response adjustment is
Paging Message message reception. needed, you are
advised to decrease
its value at the step
of 3.
RRCCONNSTATETI T304ForEutran Timer304 for Increasing the value Set the timer to 1000
MER EUTRAN of this timer allows ms. If further
the UE to have more adjustment is
access chances. needed, you are
advised to set it to
2000 ms.
(L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntraeNB.InterFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut)/
(L.HHO.IntraeNB.IntraFreq.PrepAttOut + L.HHO.IntraeNB.InterFreq.PrepAttOut +
L.HHO.IntereNB.IntraFreq.PrepAttOut + L.HHO.IntereNB.InterFreq.PrepAttOut)
Preparation Success Rate of Incoming Handover
(L.HHO.IntraeNB.ExecAttIn + L.HHO.IntereNB.ExecAttIn)/
(L.HHO.IntraeNB.PrepAttIn + L.HHO.IntereNB.PrepAttIn)
Execution Success Rate of Outgoing Handover
(L.HHO.IntraeNB.InterFreq.ExecSuccOut + L.HHO.IntraeNB.IntraFreq.ExecSuccOut +
L.HHO.IntereNB.IntraFreq.ExecSuccOut + L.HHO.IntereNB.InterFreq.ExecSuccOut)/
(L.HHO.IntraeNB.IntraFreq.ExecAttOut + L.HHO.IntraeNB.InterFreq.ExecAttOut +
L.HHO.IntereNB.IntraFreq.ExecAttOut + L.HHO.IntereNB.InterFreq.ExecAttOut)
Success Rate of Incoming Handover
(L.HHO.IntraeNB.ExecSuccIn + L.HHO.IntereNB.ExecAttIn)/
(L.HHO.IntraeNB.ExecAttIn + L.HHO.IntereNB.ExecAttIn)
This solution can be helpful in improving handover-related KPIs.
4 Case Study
was. In addition, values of interference-related counters were normal. Therefore, the issue
might be caused by the access of non-false-alarm. Survey of the live network found that the
two cells were beside sea. UEs in them were possibly out of cell radius.
Figure 1.3 Cells on the network edge with low RACH access success rate
4.1.3 Effect
The cell radius is extended from 15 km to 29 km. The RACH access success rate increases to
91%.
4.2.3 Effect
The intermodulation interference was eliminated after the customer performed site
engineering rectification. The RRC Connection Setup Success Rate recovers to the normal
state.
4.3.3 Effect
After the SmartPreAllocationSwitch option was selected, the E-RAB setup success rate
became normal, as shown in Figure 1.5.
After reviewing the operation log, it was found that the UeInactiveTimer parameter value
was changed from 10s to 1800s, as shown in Figure 1.7.
The setting of the UeInactiveTimer parameter value has a direct impact on UE status. If the
UE is constantly in connected mode, normal releases will significantly reduce so that service
drop rate will increase.
4.4.3 Effect
The service drop rate recovers to the normal state, as shown in Figure 1.8.
After analyzing traffic measurement and CHR of cell pairs, the top problematic cells with
outgoing handover failures were found. The target cell for these failed outgoing handovers
was the same.
Kuozhibu_Cell1 157
Guohang_Cell3 123
Bingguan_Cell1 72
Jiudian_Cell1 56
Based on the measurement traffic of the RACH, the cells all sent RAR if receiving preambles
and the random access success rate was 85%.But the number of handover preambles received
by this cell was far less than the total number of attempts for incoming handovers. This
showed that a large number of handovers had not received preambles, causing outgoing
handover failures of source cells.
Line Sum: Number Sum: Number Sum: Number of Times Total Random
Label of Dedicated of Responses That the eNodeB Receives Number of Access
Preamble to the Message 3 from the UE for Attempts Success
Messages Preamble the Response It sends to for Rate After
Received Due Messages the UE After Receiving Incoming Receiving
to Handovers Received Due Dedicated Preamble Handovers Handover
to Handovers Messages from the Cell Preambles
UEs were likely to be handed over to an incorrect cell because a preamble was not received.
1. Troubleshoot basic network planning and optimization.
2. Analyze neighbor relationships of sites with failed outgoing handovers. The PCI of the
target cell Guangchang_Cell2 was unique. Therefore, PCI confusion was excluded. To
check whether there was PCI confusion in a measurement cell of the UE, a fake
neighboring cell with the same PCI was manually added to force the UE to report eCGI.
This aimed to check whether the neighbor relationship was correct.
3. Based on the reported eCGI information, it was found that the eNodeB configured to
Guangchang_Cell2 was inconsistent with its cell ID. This proved that there were PCI
confusion and missing neighboring cells.
Based on the eCGI information, the cell turned out to be the one 10 km away with the same
PCI of 223. The signal of the cell encountered overshoot coverage, which caused the incorrect
handover to Guangchang_Cell2 and the overall handover failures.
5 Reference Documents