LTE KPI Improvement Solution User Guide

i
 Contents

About This Document ...................................................................Error! Bookmark not defined.

1 Introduction.................................................................................................................................... 1
1.1 Purpose and Scope ........................................................................................................................................................ 1
1.1.1 Purpose ...................................................................................................................................................................... 1
1.1.2 Scope ......................................................................................................................................................................... 1
1.1.3 Organization .............................................................................................................................................................. 1
1.1.4 Relationship with Other Documents .......................................................................................................................... 2
1.1.5 Lifecycle .................................................................................................................................................................... 2
1.2 Open Issues ................................................................................................................................................................... 2
1.3 Assumptions.................................................................................................................................................................. 2

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 ...................................................................................................................................... 13
3.1.4 Application Guide .................................................................................................................................................... 13
3.2 Solution to Service-Drop-related KPIs Improvement ................................................................................................. 14
3.2.1 Description............................................................................................................................................................... 14
3.2.2 Service-related Parameter Optimization .................................................................................................................. 16
3.2.3 Effect Evaluation Methods ...................................................................................................................................... 18
3.2.4 Application Guide .................................................................................................................................................... 18
3.3 Solution to Handover-related KPIs Improvement ....................................................................................................... 18
3.3.1 Description............................................................................................................................................................... 18
3.3.2 Service-related Parameter Optimization .................................................................................................................. 22
3.3.3 Effect Evaluation Methods ...................................................................................................................................... 22
3.3.4 Application Guide .................................................................................................................................................... 23

4 Case Study .................................................................................................................................... 24

ii
4.1 Case 1: Improvement in the RACH Access Success Rate .......................................................................................... 24
4.1.1 Background .............................................................................................................................................................. 24
4.1.2 Solution and Configuration ...................................................................................................................................... 24
4.1.3 Effect ....................................................................................................................................................................... 25
4.2 Case 2: Improvement in the RRC Connection Setup Success Rate ............................................................................ 25
4.2.1 Background .............................................................................................................................................................. 25
4.2.2 Solution and Configuration ...................................................................................................................................... 25
4.2.3 Effect ....................................................................................................................................................................... 26
4.3 Case 3: Improvement in the E-RAB Setup Success Rate ........................................................................................... 26
4.3.1 Background .............................................................................................................................................................. 26
4.3.2 Solution and Configuration ...................................................................................................................................... 26
4.3.3 Effect ....................................................................................................................................................................... 26
4.4 Case 4: Improvement in the Service Drop Rate .......................................................................................................... 27
4.4.1 Background .............................................................................................................................................................. 27
4.4.2 Solution and Configuration ...................................................................................................................................... 28
4.4.3 Effect ....................................................................................................................................................................... 28
4.5 Case 5: Improvement in the Handover Success Rate.................................................................................................. 28
4.5.1 Background .............................................................................................................................................................. 28
4.5.2 Solution and Configuration ...................................................................................................................................... 28
4.5.3 Effect Evaluation ..................................................................................................................................................... 30

5 Reference Documents.................................................................Error! Bookmark not defined.

iii
 1 Introduction

1.1 Purpose and Scope

1.1.1 Purpose
This document serves as an application guide of the LTE KPI improvement solutions. It
describes feature portfolios and end-to-end (E2E) deliverable applications of the solutions and
provides guidelines for future solution-level application, maintenance and secondary
development of service solutions for existing LTE systems.

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.1.4 Relationship with Other Documents
LTE Uplink Capacity Solution Design is the source of this document.

1.1.5 Lifecycle
The draft of this document was completed at TR5.
This document was updated and finalized at TR6.

1.2 Open Issues

None

1.3 Assumptions
None

2
 2 Solution Overview

2.1 Scenarios Analysis

The solution helps increase the KPIs such as the access success rate and handover success rate,
and decrease the service drop rate.

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.

2.3 General Solution

The solution is as follows:
 Improvement of access-related KPIs
Provide measures for improving access-related KPIs based on the causes of RACH
access failures, RRC connection setup failures, and E-RAB setup failures.
 Improvement of service-drop-related KPIs
Provide measures for improving service-drop-related KPIs based on the causes of service
drops.
 Improvement of handover-related KPIs
Provide measures for improving handover-related KPIs based on the causes of handover
failures in the handover preparation and execution phases.

3
 3 Application Guide

3.1 Solution to Access-related KPI Improvement

3.1.1 Description
Solution to Access-related KPIs Improvement includes:
 Improvement of RACH access success rate
 Improvement of RRC connection setup success rate
 Improvement of E-RAB setup success rate

Table 3-1 lists the causes of RACH access failures and the improvement measures.

Table 3-1 RACH failure category, symptom and improvement measure

RACH Failure Symptom Improvement Measure

Category

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
cell root sequence
conflict.

4
RACH Failure Symptom Improvement Measure
Category
PRACH The PRACH channel The failure can be gradually rectified as follows:
interference interference is extremely  Check the PRACH interference source to resolve the
higher than the PUSCH or PRACH channel interference.
PUCCH interference.
 Select the PrachIrcSwitch option to improve PRACH
You can compare the anti-interference capabilities. For details, see Receiver
L.UL.Interference.PRACH Technology Feature Parameter Description.
and
 Select the PrachFalseAlarmDetSwitch option. For
L.UL.Interference.PUSCH/
L.UL.Interference.PUCCH details, see Random Access Control and RACH
counters. Optimization Feature Parameter Description.

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.

5
 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

6
RRC Connection Cause for RRC Symptom Improvement Measure
Setup Failure Connection Setup
Category Failures
Air interface fault No RRC L.RRC.SetupFail. The failure can be gradually rectified as
CONNECTION NoReply > 0 follows:
SETUP The TMSIs of UEs  Optimize RF settings to reduce poorly
COMPLETE with access covered areas.
message from UEs failures are  Troubleshoot uplink interference.
irregular.
 Adjust the QRxLevMin parameter
value. The adjusted value must meet the
requirements for cell edge coverage on
live networks.
 Set the SmartPreAllocationSwitch
parameter on. For details, see
Scheduling Feature Parameter
Description.
 Select the SrbProbeSchSwitch option.
For details, see Scheduling Feature
Parameter Description.
Abnormal UEs A certain UE L.RRC.ConnReq. The failure can be gradually rectified as
repeatedly fails to Msg > follows:
access networks. L.RRC.ConnReq.  Deselect the RrcSetupOptSwitch
Att option to avoid UE compatibility issues.
The TMSIs of UEs  Increase the value of
with access FilterReptRrcConnReqTimer to filter
failures are repeated RRC Connection Request
densely messages of abnormal UEs.
distributed.
 Adjust the RrcConnPunishThd
parameter value to reduce the impact of
abnormal UEs.
 Set the FltrRptRrcConReqExtdSwitch
parameter to ON to filter repeated RRC
Connection Request messages of
abnormal UEs.

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

7
E-RAB Setup Cause for E-RAB Symptom Improvement Measure
Failure Category Setup Failures
Insufficient uplink L.E-RAB.FailEst.
transport resources TNL.ULRes > 0
Resource Insufficient SRS L.E-RAB.FailEst. The failure can be rectified using either of
deficiency resources NoRadioRes.SRS the following methods:
>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-RAB.FailEst. The PUCCH resource allocation failure
resources NoRadioRes.PUC refers to the SRI allocation failure. The
CH > 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.
Insufficient L.E-RAB.FailEst. Expand the capacity of sites whose
downlink licensed NoRadioRes.DLT resources are congested, or increase
traffic volume hrpLic > 0 licensed traffic volume.
Insufficient licensed L.E-RAB.FailEst.
uplink traffic volume NoRadioRes.ULT
hrpLic > 0
Low downlink L.E-RAB.FailEst. Change the downlink satisfaction rate
satisfaction rate NoRadioRes.DLS threshold or deselect the DlSwitch option.
atis > 0 For details, see Admission and Congestion
Control Feature Parameter Description.
Low uplink L.E-RAB.FailEst. Change the uplink satisfaction rate
satisfaction rate NoRadioRes.ULS threshold or deselect the UlSwitch option.
atis > 0 For details, see Admission and Congestion
Control Feature Parameter Description.
Insufficient UE L.E-RAB.FailEst. Expand the capacity of sites.
number specification NoRadioRes.User
Spec > 0

8
E-RAB Setup Cause for E-RAB Symptom Improvement Measure
Failure Category Setup Failures
Insufficient L.E-RAB.FailEst. Expand the capacity of sites or add
RRC_CONNECTE NoRadioRes.RrcU RRC_CONNECTED UE license.
D UE license serLic > 0
Air interface fault The retransmission L.E-RAB.FailEst. The failure can be gradually rectified as
number of downlink SRBReset > 0 follows:
SRB RLC reaches  Optimize RF settings to reduce poorly
the maximum. covered areas.
 Troubleshoot uplink interference.
 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
UE response timeout L.E-RAB.FailEst. enhance the downlink transmission
NoReply > 0 reliability.
 Increase the value of
WaitRrcConnSetupCmpTimer to
increase tolerance duration. For details,
see Connection Management Feature
Parameter Description.
 Set the SmartPreAllocationSwitch
parameter on. For details, see
Scheduling Feature Parameter
Description.
 Select the SrbProbeSchSwitch option.
For details, see Scheduling Feature
Parameter Description.
 Set Inactvty Tmr Expiration
Processing Strategy to
ONLY_ERAB_SETUP_FLOW_FIRS
T(ONLY_ERAB_SETUP_FLOW_FI
RST) to resolve the conflict between the
E-RAB establishment procedure and the
UE inactivity timer expiration
procedure.
Core network fault The core network L.E-RAB.FailEst. The failure can be gradually rectified as
fault MME > 0 follows:
 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.

9
 Table 3-4 lists the feature names and reference documents involved in the solution.

Table 3-4 Feature ID, feature name, and reference document

Feature ID Feature/Function Name Introduced In… Reference Document

LOFD-001094 Control Channel IRC eRAN6.0 Receiver Technology Feature
Parameter Description
N/A PrachFalseAlarmDetSwitc eRAN7.0 Random Access Control and RACH
h Optimization Feature Parameter
Description
LOFD-001007 High Speed Mobility eRAN1.0 High Speed Mobility Feature
Parameter Description
LOFD-001008 Ultra High Speed Mobility eRAN1.0 High Speed Mobility Feature
Parameter Description
LOFD-001009 Ultra-remote Cells eRAN2.0 Extended Cell Range Feature
Parameter Description
N/A SmartPreAllocationSwitch eRAN6.0 Scheduling Feature Parameter
Description
N/A SrbProbeSchSwitch eRAN11.1 Scheduling Feature Parameter
Description
N/A FltrRptRrcConReqExtdSwi eRAN12.0 Connection Management Feature
tch Parameter Description

Table 3-5 lists the features and functions involved in the solution.

Table 3-5 Feature ID, feature name, and feature description

Feature ID Feature/Function Name Feature/Function Description

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
the impact of false alarms on the RACH access success rate.
LOFD-001007 High Speed Mobility Increases the UE access capability in high-speed frequency
offset scenarios.
LOFD-001008 Ultra High Speed Mobility
LOFD-001009 Ultra-remote Cells Increases the UE access capability in ultra-remote cells.
N/A SmartPreAllocationSwitch Ensures that there are available scheduling resources in the
uplink to avoid KPI deterioration caused by missing
detection of SRs.
N/A SrbProbeSchSwitch Improves the signaling feedback success rate.
N/A FltrRptRrcConReqExtdSwitch Identifies the repeated accesses of abnormal UEs for a longer
time, removes the statistics about abnormal RRC connection
setup attempts, and reduces the impact of abnormal UEs on

10
Feature ID Feature/Function Name Feature/Function Description
the RRC connection setup success rate.

3.1.2 Service-related Parameter Optimization

The optimization of parameter adjustment is a progressive process. You are advised to
progressively adjust the parameter values based on the KPIs of local networks.

MO Parameter Parameter Parameter Adjustment

ID Name Description

CellSel/CellResel QRxLevMin Minimum Reduces the The value of the downlink

Required RX number of UE RSRP below -122 dBm
Level accesses in poorly shows that an area is poorly
covered areas. covered. You are advised to
set the parameter to -122
dBm. If further adjustment is
needed, you are advised to
increase its value by 2 dB at
a time.
UeTimerConst T300 Timer 300 Prolongs the If the value of this parameter
processing is less than 1000 ms on the
duration of live network, you are advised
abnormal UEs to to set the parameter to 1000
prevent access ms. If further adjustment is
failures due to the needed, you are advised to
processing increase its value by 200 ms
interruption by the at a time.
timer.
RrcConnStateTimer T302 Timer 302 Delays the time of You are advised to set it to
UE re-access to the maximum value of 16s.
prevent eNodeB
against heavy
traffic.
SrbRlcPdcpCfg/Rlc eNodeBMax MaxRetxThresho Results in a larger You are advised to set it to
PdcpParaGroup RetxThreshol ld for eNodeB number of the maximum value of 32.
d retransmissions to
enhance the
downlink
transmission
reliability.
ENodeBConnStateT WaitRrcConn RRCConnSetup Prolongs the You are advised to set it to
imer SetupCmpTi Cmp Waiting waiting time to the maximum value of 15s.
mer Timer achieve higher
access success
rate.

11
MO Parameter Parameter Parameter Adjustment
ID Name Description
ENodeBConnStateT SecCmpWaiti SecurityModeCo Prolongs the If further adjustment is
imer ngTimer mplete Waiting waiting time to needed, you are advised to
Timer achieve higher increase its value by 2s at a
access success time. It is recommended that
rate. the value of the timer be less
than or equal to 35s.
ENodeBConnStateT UpUeCapInfo Unprotected Prolongs the If further adjustment is
imer WaitingTimer UeCapInfo waiting time to needed, you are advised to
Waiting Timer achieve higher increase its value by 2s at a
access success time. It is recommended that
rate. the value of the timer be less
than or equal to 35s.
ENodeBConnStateT UuMessageW UU Message Prolongs the If further adjustment is
imer aitingTimer Waiting Timer waiting time to needed, you are advised to
achieve higher increase its value by 2s at a
access success time. It is recommended that
rate. the value of the timer be less
than or equal to 35s.
ENodeBConnStateT S1MessageW S1 Message Prolongs the If further adjustment is
imer aitingTimer Waiting Timer waiting time to needed, you are advised to
achieve higher increase its value by 2s at a
access success time. It is recommended that
rate. the value of the timer be less
than or equal to 20s.
RrcConnStateTimer FilterReptRrc Filter Repeated Increases the value You are advised to set it to
ConnReqTim RRCConnReq of this parameter the maximum value of 15s.
er Timer to filter more
repeated access of
abnormal UEs to
traffic
measurement.

12
MO Parameter Parameter Parameter Adjustment
ID Name Description

GlobalProcSwitch InactvtyTmrE Inactvty Tmr Resolves the You are advised to set it to
xpnProcStrat Expiration conflict between ONLY_ERAB_SETUP_FL
Processing the E-RAB OW_FIRST(ONLY_ERAB
Strategy establishment _SETUP_FLOW_FIRST).
procedure and the
inactivity timer
expiration
procedure if the
parameter is set to
ONLY_ERAB_S
ETUP_FLOW_FI
RST(ONLY_ER
AB_SETUP_FLO
W_FIRST).

3.1.3 Effect Evaluation Methods

Definition of access-related KPIs:
 RACH Access Success Rate = (L.RA.GrpA.ContResolution +
L.RA.GrpB.ContResolution + L.RA.Dedicate.Msg3Rcv)/(L.RA.GrpA.Att +
L.RA.GrpB.Att + L.RA.Dedicate.Att)
 RRC Connection Setup Success Rate = L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att
 E-RAB Setup Success Rate = L.E-RAB.SuccEst/(L.E-RAB.AttEst–
L.E-RAB.FailEst.MME.X2AP)
This solution helps improve access-related KPIs.

3.1.4 Application Guide

The solution serves to improve RACH access success rate, RRC connection setup success rate
and E-RAB setup success rate. All of the three features can be activated at the same time. The
deployment and activation of each feature are not described in this document. For details, see
the corresponding feature parameter descriptions.

13
3.2 Solution to Service-Drop-related KPIs Improvement
3.2.1 Description
Table 3-6 lists the causes of service drops and the improvement measures.

Table 3-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
>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.

14
Cause for Symptom Improvement Measure
Service Drop

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 Decrease the value of the UeInactiveTimer
normal releases L.E-RAB.NormRel is parameter to increase the number of normal UE
significantly 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.

15
 Table 3-7 lists of features and reference documents involved in the solution.

Table 3-7 Feature ID, feature name, and reference document

Feature ID Feature/Function Name Introduced In… Reference Document

LOFD-002001 ANR Management eRAN1.x ANR Management Feature Parameter
Description
LOFD-002007 PCI Conflict Detection & eRAN1.x PCI Conflict Detection and
Self-Optimization Self-Optimization Feature Parameter
Description
N/A SrbProbeSchSwitch eRAN11.1 Scheduling Feature Parameter
Description
N/A Reestablishment in eRAN11.x For details, see the parameter
enhanced scenarios description.

Table 3-8 lists the features and functions involved in the solution.

Table 3-8 Feature ID, feature name, and feature description

Feature ID Feature/Function Feature/Function Description

Name

LOFD-002002 ANR Management Enables the neighboring cell self-addition and

LOFD-002007 PCI Conflict Detection &
Self-Optimization
N/A SrbProbeSchSwitch
N/A Reestablishment in
enhanced scenarios
self-optimization functions to reduce the service drop rate
caused by missing or incorrect neighbor relationships.
Checks PCI conflicts and solves these problems to prevent
service drops caused by improper handover or PCI conflicts.
Improves the signaling feedback success rate.
Controls the eNodeB to support reestablishment in enhanced
scenarios, increases the reestablishment success rate, and
decreases the service drop rate.

3.2.2 Service-related Parameter Optimization

The optimization of parameter adjustment is a progressive process. You are advised to
progressively adjust the parameter values based on the KPIs of local networks.

16
MO Parameter ID Parameter Parameter Adjustment
Name Description

CellSel/CellResel QRxLevMin Minimum Reduces the The value of the downlink

Required RX number of UE RSRP below -122 dBm
Level accesses in poorly shows that an area is poorly
covered areas. covered. You are advised to
set the parameter to -122
dBm. If further adjustment
is needed, you are advised to
increase its value by 2 dB at
a time.
SrbRlcPdcpCfg/Rlc eNodeBMaxRetx MaxRetxThres Results in a larger You are advised to set it to
PdcpParaGroup Threshold hold for number of the maximum value of 32.
eNodeB retransmissions to
enhance the
downlink
transmission
reliability.
TimeAlignmentTim TimeAlignmentT Uplink time Enhances the You are advised to set this
er imer alignment timer uplink timing timer to INFINITY. At the
reliability and same time, select the
reduces the TimingAdvCmdOptSwitc
out-of-synchroniz h option, and set the
ation TACmdSendPeriod
probabilities. parameter to SF928.
CellStandardQci TrafficRelDelay Traffic Release A longer waiting You are advised to set this
Delay duration leads to parameter to 30s, or at least
higher rate of not less than 15s.
RRC connection
reestablishment
and lower service
drop rate.
ENodeBConnStateT UuMessageWaiti UU Message A longer waiting If further adjustment is
imer ngTimer Waiting Timer duration leads to needed, you are advised to
lower service increase its value by 2s at a
drop rate. time. It is recommended that
the value of the timer be less
than or equal to 35s.
ENodeBConnStateT S1MessageWaiti S1 Message A longer waiting If further adjustment is
imer ngTimer Waiting Timer duration leads to needed, you are advised to
lower service increase its value by 2s at a
drop rate. time. It is recommended that
the value of the timer be less
than or equal to 20s.

17
MO Parameter ID Parameter Parameter Adjustment
Name Description
ENodeBConnStateT X2MessageWaiti X2 Message A longer waiting If further adjustment is
imer ngTimer Waiting Timer duration leads to needed, you are advised to
lower service increase its value by 2s at a
drop rate. time. It is recommended that
the value of the timer be less
than or equal to 20s.
RrcConnStateTimer UeInactiveTimer UE Inactivity A smaller value You are advised to set this
Timer of this parameter parameter to 10s, not more
results in more than 20s and less than 5s.
RRC connection
releases for UEs
to prevent worse
service drop rate
due to fewer
normal RRC
connection
releases.

3.2.3 Effect Evaluation Methods

The KPI of the service drop rate is defined as follows:
L.E-RAB.AbnormRel/(L.E-RAB.AbnormRel + L.E-RAB.NormRel +
L.E-RAB.NormRel.IRatHOOut)
This solution helps improve handover-related KPIs.

3.2.4 Application Guide

This solution improves service-drop-related KPIs, and the preceding features or functions can
be enabled at the same time. The deployment and activation of each feature are not described
in this document. For details, see the corresponding feature parameter descriptions.

3.3 Solution to Handover-related KPIs Improvement

3.3.1 Description
Table 3-9 lists the causes of handover failures and the improvement measures.

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

18
Handover Handover Failure Symptom Improvement Measure
Failure Category Cause
(observing leads to incoming scenarios are as follows:
handover target handover  If the number of UEs in a cell reaches
cells) preparation failure. 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.
The uplink and L.HHO.Prep.FailIn.A Increase licensed traffic in the uplink
downlink licensed dmitFail.ULThrpLic > and downlink.
traffic leads to 0
incoming L.HHO.Prep.FailIn.A
preparation dmitFail.DLThrpLic >
handover failure. 0
The limited number L.HHO.Prep.FailIn.A Expand the capacity of sites whose
of UEs in RRC dmitFail.UserLic > 0 resources are congested, or increase
connected mode licensed number of UEs in RRC
leads to incoming connection mode.
handover
preparation failure.
The limited number L.HHO.Prep.FailIn.A Expand the capacity of sites whose
of UEs in RRC dmitFail.UserSpec > 0 resources are congested.
connected mode
leads to incoming
preparation
handover failure.
Faults at the L.HHO.Prep.FailIn.T The failure can be gradually rectified as
transport network NL > 0 follows:
layer lead to  Check whether there are missing
incoming handover S-GW addresses in the target site.
preparation failures.
 Turn on the GTPU static detection
switch to check whether there is a
GTPU fault alarm. If so, troubleshoot
any GTPU faults.
Insufficient uplink L.HHO.Prep.FailIn.A Troubleshoot using any of the following
transport resources dmitFail.TNL.ULRes measures:
lead to incoming >0  Expand the target site capacity.
handover
 Increase the transport resource group
preparation failures.
bandwidth of the target site.
 Increase the value of the
TRMULHOCACTH parameter.
 Set the RSCGRPULCACSWITCH

19
Handover Handover Failure Symptom Improvement Measure
Failure Category Cause
parameter off in order not to apply
UL admission control to a resource
group. For details, see Transport
Resource Management Feature
Parameter Description.
Insufficient L.HHO.Prep.FailIn.A Troubleshoot using any of the following
downlink transport dmitFail.TNL.DLRes measures:
resources lead to >0  Expand the target site capacity.
incoming handover
 Increase the transport resource group
preparation failures.
bandwidth of the target site.
 Increase the value of the
TRMULHOCACTH parameter.
 Set the RSCGRPULCACSWITCH
parameter off in order not to apply
UL admission control to a resource
group. For details, see Transport
Resource Management Feature
Parameter Description.
Handover Handover failure The air interface Check and modify the configuration of
execution failure caused by incorrect message shows that in neighboring cells.
(observing configuration of handover commands
handover target neighboring cells the delivered PCI is
cells) not the PCI in the
measurement report
(MR) sent by the UE.
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.
 Enable the ANR function. For
neighbor
relationship. details, see ANR Management
Feature Parameter Description.
Overshoot coverage Engineering Troubleshoot using either of the
parameters indicate following measures:
that top neighboring  Optimize RF settings.
cells with handover
 Select the NonContRaOptSwitch
failures experience
overshoot coverage. option of the
CellAlgoSwitch.RachAlgoSwitch
parameter.
Poor coverage Engineering The failure can be gradually rectified as
parameters indicate follows:
that top neighboring  Optimize RF settings.
cells with handover
 Set the HoRarPwrEnhancedSwitch
failures experience
overshoot coverage. parameter on. For details, see Power
Control Feature Parameter
Description.

20
Handover Handover Failure Symptom Improvement Measure
Failure Category Cause
 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 3-10 lists the feature ID, feature name, and reference document for
each solution.

Table 3-10 Feature ID, feature name, and reference document

Feature ID Feature/Function Name Introduced In… Reference Document

LOFD-002002 ANR Management eRAN1.0 ANR Management Feature
Parameter Description
N/A Handover RAR Power eRAN11.0 Power Control Feature
Enhance Parameter Description

Table 3-11 lists the features and the functions in the solution.

Table 3-11 Feature ID, feature name, and functions

Feature ID Feature/Function Feature/Function Description

Name
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.

21
3.3.2 Service-related Parameter Optimization
The optimization of parameter adjustment is a progressive process. You are advised to
progressively adjust the parameter values based on the KPIs of local networks.

MO Parameter ID Parameter Parameter Adjustment

Name Description
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.
RrcConnStateTimer T304ForEutran Timer304 for Increasing the value Set the timer to 1000
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.

3.3.3 Effect Evaluation Methods

The handover-related KPIs are defined as follows:
 Preparation Success Rate of Outgoing Handover
(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.

22
3.3.4 Application Guide
This solution improves handover-related KPIs, and the preceding features or functions can be
enabled at the same time. The deployment and activation of each feature are not described in
this document. For details, see the corresponding feature parameter descriptions.

23
 4 Case Study

4.1 Case 1: Improvement in the RACH Access Success Rate

4.1.1 Background
Operator A in country R had two top cells with low RACH access success rate. In severe
conditions, the RACH access success rate was lower than 10%, as shown in Figure 4-1.

Figure 4-1 RACH access success rate

4.1.2 Solution and Configuration

The statistics about the RACH success rate and the L.RA.GrpA.Att counter on the live
network indicate that the more times of the RACH access had, the poorer the success rate 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.

24
 Figure 4-2 Cells on the network edge with low RACH access success rate

Enable Extended Cell Range. Set its parameters as follows:

MOD CELL: PreambleFmt = 1, CellRadius = 29000

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 Case 2: Improvement in the RRC Connection Setup

Success Rate
4.2.1 Background
Cell 1 on a site of project XX suffered a continual low setup success rate of approximately
40% on average, failing to meet demands.

4.2.2 Solution and Configuration

Check results showed that the value of the L.UL.Interference.Avg counter was greater than
-105 dBm, which meant that the fault was caused by uplink interference.
By means of cell trace, the fault was that the RRC CONN CMP message from UEs could not
be received due to uplink intermodulation interference.

25
 Figure 4-3 Uplink intermodulation interference of a cell

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 Case 3: Improvement in the E-RAB Setup Success Rate

4.3.1 Background
After DRX (with both entry and exit thresholds being 1000) was enabled in a certain network
in country A, the E-RAB setup success rate of top problematic cells decreased by 0.08%.
It was detected that UEs in these cells occasionally did not send SR, and eNodeBs did not
send uplink scheduling indications to the UEs.

4.3.2 Solution and Configuration

Select the SmartPreAllocationSwitch option. The MML command is as follows: MOD
CELLALGOSWITCH: LocalCellId = x, UlSchSwitch = SmartPreAllocationSwitch-1;

4.3.3 Effect
After the SmartPreAllocationSwitch option was selected, the E-RAB setup success rate
became normal, as shown in Figure 4-4.

26
 Figure 4-4 E-RAB setup success rate on site B

4.4 Case 4: Improvement in the Service Drop Rate

4.4.1 Background
Network K in country L was found to suffer a high service drop rate. Since June 9, 2012, the
average service drop rate of the live network had deteriorated to 20% as field engineers
checked traffic statistics, as shown in Figure 4-5.

Figure 4-5 Service drop rate from May to June in network K

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.

27
 Figure 4-6 UeInactiveTimer value changed from 10s to 1800s

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.2 Solution and Configuration

Set the UeInactiveTimer parameter to 10s. The MML command is as follows: MOD
RRCCONNSTATETIMER: UeInactiveTimer = 10;

4.4.3 Effect
The service drop rate recovers to the normal state, as shown in Figure 4-7.

Figure 4-7 Service drops by hour

4.5 Case 5: Improvement in the Handover Success Rate

4.5.1 Background
The handover success rate in the network of operator C in country C was only 99.35%. After
analysis, top outgoing cells and top incoming cells were found. Overshoot coverage occurred
in the top cells, in some of which the PCIs in measurement cells and target cells were
inconsistent, causing handover failures.

4.5.2 Solution and Configuration

First, locate the fault scope.
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.

28
Source Cell Number of Handover Failures in Target Cell of Guangchang_Cell2

Kuozhibu_Cell1 157
Guohang_Cell3 123
Bingguan_Cell1 72
Jiudian_Cell1 56

Then, analyze counter correlations.

Analyze the counters of the target cell (from 10 September to 24 September). The
inter-eNodeB incoming handover was the main problem, with a very low success rate.

Line Label Times of Incoming Inter-eNodeB Intra-eNodeB

Incoming Handover Incoming Incoming
Handover Failure Success Rate Handover Handover
Success Rate Success Rate
Guangchang_Cell2 5060 41.81% 25.09% 95.00%

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.

29
 Figure 4-8 Target PCI of 223

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.

4.5.3 Effect Evaluation

After overshoot coverage is resolved, the counters of the handover success rate recover to the
normal state.

30