Professional Documents
Culture Documents
LTE CONFIDENTIAL
Product Version Total 33 pages
eRAN
Reviewed By Date
Reviewed By Date
Approved By Date
Change History
Date Issue Change Description Author
2015-05-24 1.0 Completed the draft. Jian Bin
2015-07-10 1.1 Corrected some incorrect Jian Bin
descriptions.
2015-08-12 1.1 Corrected some incorrect Jian Bin
descriptions.
2015-11-06 1.3 Updated solutions Jian Bin
according to eRAN11.1.
2015-12-28 1.4 Updated the document Jian Bin
based on the review
comments.
2016-03-22 1.5 Updated solutions Jian Bin
according to eRAN12.0.
2016-11-22 1.6 Updated solutions Deng Youliang
according to eRAN12.1.
Distribution List
Copy No. Holder's Name & Role Issue Date
Contents
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
2 Describes the solution overview.
Introduces the application scenarios of the solution. LTE Uplink
Capacity Solution Design is the source of this document.
Provides values and objectives of the solution in the current
version, that is, the system effect after the solution is used.
Describes the general solution and provides conclusions based on
different scenarios without details.
3 Describes the solution application guide.
Provides detailed solutions for each scenario, involving parameter
configuration, effect evaluation, and troubleshooting.
4 Describes application cases of the solution on commercial networks.
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 3-1 lists the causes of RACH access failures and the improvement measures.
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 3-2 lists the causes of RRC connection setup failures and the improvement measures.
Table 3-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.
MME overload L.RRC.SetupFail. Check the cause of MME overload.
Rej.MMEOverloa
d>0
Table 3-3 lists the causes of E-RAB setup failures and the improvement measures.
Table 3-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-RAB.FailEst. Check for transmission alarms. For details,
downlink TNL.DLRes > 0 see the alarm part in 3900 Series Product
transmission Documentation.
resources
Table 3-4 lists the feature names and reference documents involved in the solution.
Table 3-5 lists the features and functions involved in the solution.
Table 3-6 Cause for service drop, symptom and improvement measure
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
>0 Handover-related KPIs Improvement."
Uplink The value of Troubleshoot uplink interference.
interference L.UL.Interference.Avg is
significantly greater than the
normal in idle mode.
Table 3-7 lists of features and reference documents involved in the solution.
Table 3-8 lists the features and functions involved in the solution.
Table 3-9 Handover failure category, handover failure cause, symptom, and improvement
measure
Handover Handover Failure Symptom Improvement Measure
Failure Category Cause
Handover PUCCH resource L.HHO.Prep.FailIn.A The PUCCH resource allocation failure
preparation failure allocation failure dmitFail.PUCCH > 0 refers to the SRI allocation failure. Main
Based on the handover failure cause, symptom, and improvement measure described in the
preceding table, Table 3-10 lists the feature ID, feature name, and reference document for
each solution.
Table 3-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.
4 Case Study
Figure 4-2 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 4-4.
After reviewing the operation log, it was found that the UeInactiveTimer parameter value
was changed from 10s to 1800s, as shown in Figure 4-6.
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 4-7.
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
Total 4076 4076 3492 8696 85.67%
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