Product name Confidentiality level

LTE RNO For internal use only

Product version
Total 19 pages
V1.0

India Airtel KTK 4G MS Team

Optimization Process
(For internal use only)

Prepared by Padmanava Date 2014-02-25

Reviewed by Date

Reviewed by Date

Approved by Date

Huawei Technologies Co., Ltd.

All rights reserved.
 For internal use only

1. India Airtel LTE MS Project RNO work flow ...................................................... 3

2. RRC Setup Success Rate KPI Analysis ............................................................... 4
1.1 RRC Reject ........................................................................................................................... 4
1.2 RRC no reply ........................................................................................................................ 5
3. E-RAB Setup Success Rate KPI Analysis ............................................................ 6
2.1 L.E-RAB.FailEst.MME ........................................................................................................... 6
2.2 L.E-RAB.FailEst.TNL .............................................................................................................. 6
2.3 L.E-RAB.FailEst.NoRadioRes ................................................................................................ 6
2.4 L.E-RAB.FailEst.SecurModeFail ............................................................................................ 7
2.5 L.E-RAB.FailEst.NoReply ...................................................................................................... 7
4. PS Drop .......................................................................................................... 7
3.1 RF Failure ............................................................................................................................. 7
5. HOSR.............................................................................................................. 8
4.1 HO summary ....................................................................................................................... 8
4.2 Ho troubleshooting e-Flow ................................................................................................. 9
4.3 Ho Failure .......................................................................................................................... 10
6. Throughput ...................................................................................................11
6.1 Throughput E-Flow ...................................................................................................... 11
6.2 Issue description ......................................................................................................... 12
6.3 Issue troubleshooting.................................................................................................. 12
7. IRAT Per call ..................................................................................................14
8. CSFB ..............................................................................................................14
9. Neighbor optimization ...................................................................................14
10. PCI conflict ....................................................................................................15
11. User complaint ..............................................................................................15
12. Resource monitoring .....................................................................................16
13. Alarm ............................................................................................................19

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 2 of 19

 For internal use only

1. India Airtel LTE MS Project RNO work flow

01. Monitoring KPIs

and Identify Issue

02. Identify Issue KPI

and TOP cells

 TOP Cells for RRC

 TOP Cells for ERAB

04. need check: 03. need check:

 Any activity:  Revert activity

05. the solution for each

If it’s not resolve, pls

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 3 of 19

 For internal use only

2. RRC Setup Success Rate KPI Analysis

TOP Cell condition: continuous 2 days NBH <99.5% & Failure number > 1 or 1 day BBH failure
number ≥ 20

1.1 RRC Reject

Counter: L.RRC.SetupFail.Rej / L.RRC.SetupFail.ResFail

The L.RRC.SetupFail.Rej counter is incremented by 1 each time the eNodeB sends an RRC

Connection Reject message to the UE after receiving an RRC Connection Request message

from the UE. If the reject reason is due to resource allocation failure then the

L.RRC.SetupFail.ResFail counter is incremented by 1 each time

a. If it increase/decrease suddenly from particular time, need correlated to any activity,

event or any faulty.

b. Check <L.Traffic.User.Max> if reach the product caps or the license limited <RRC

Connected User(per RRC Connected User)> ---normally it’s 400 per site.

 DSP License:

c. Check CPU load < VS.Board.CPUload.Mean>, normally it should be less than 70%.

d. Check planning data (PCI/TAC/PRACH)

 LST CELL: PCI / RootSequenceIdx.

 LST CNOPERATORTA : TAC

e. Check configuration parameter : Use FMA tool to compare with normal site.

f. Get board log and use FMA to check if any internal fault in the cfltlog.log. like <low-

layer link of S1 interface fault>, need push BSS & transmission team to check.

How to get board log

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 4 of 19

 For internal use only

1.2 RRC no reply

Counter: L.RRC.SetupFail.NoReply
RRC no-reply possible reason are: After UE send RRC request, eNodeB didn’t reply RRC

setup, or delay to reply/UE didn’t receive RRC setup MSG/eNodeB didn’t receive RRC setup

complete MSG. So need to check below points:

a. Check any alarm like ALM-26529 RF Unit VSWR Threshold Crossed/26532 RF Unit

Hardware Fault/26200 Board Hardware Fault. Other alarms which time is mapping with

KPIs decrease time also need to pay attention.

b. Check interference <L.UL.Interference.Avg> < -105dBm. If have high interference, need to

check PCI planning/GPS alarm for nearby sites/external interference.

 LST CLKMODE : to check GPS clock mode, if free will cause high interference.

c. Check from CHR log, if any top user’ issue;

d. Check parameter setting: T300/ UuMessageWaitingTimer /

WaitRrcConnSetupCmpTimer (Eran 6). Other parameter setting Use FMA tool to compare

with normal site.

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 5 of 19

 For internal use only

e. Check CPU load < VS.Board.CPUload.Mean>, normally it should be less than 70%.

f. Put the UU trace to check signal flow to find which MSG is missing and calculate each

MSG time.

g. Coverage issue: Check from CHR log, any UL weak coverage and the TA distributing (TA

counter will also be available in ERAN6.1), and try to do the physical optimization or Power

optimization;

3. E-RAB Setup Success Rate KPI Analysis

TOP Cell condition: continuous 2 days NBH <99% & Failure number > 1 or 1 day BBH failure
number ≥ 20
Below counters indicate the number of E-RAB setup failures due to different causes on the

network : L.E-RAB.FailEst.MME/ L.E-RAB.FailEst.TNL/ L.E-RAB.FailEst.RNL.

And L.E-RAB.FailEst.RNL include: L.E-RAB.FailEst.NoReply/ L.E-RAB.FailEst.NoRadioRes / L.E-

RAB.FailEst.SecurModeFail.

2.1 L.E-RAB.FailEst.MME

a. Check eNodeB parameter setting :S1MessageWaitingTimer;

b. Push Ericsson team help to check from EPC side (AMBR/ARP& etc.);

2.2 L.E-RAB.FailEst.TNL

a. Configuration check : IPPATH missing or wrong setting, As current setting, we need to

configure all 12 UGW IPs (10.210.0.25/26/27/28/29/30, 10.210.27.25/26/27/28/29/30)

 Command: LST IPPATH;

b. SCTP link alarm: ;

c. Push transmission team to check any transmission fluctuation;

2.3 L.E-RAB.FailEst.NoRadioRes

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 6 of 19

 For internal use only

a. Check license : <RRC Connected User(per RRC Connected User)>

 DSP LICENSE:;

b. Check parameter setting : InitPdcchSymNum/SrsSubframeCfg/S1interfaceisblock;

 LST CELLPDCCHALGO: InitPdcchSymNum=3

 LST SRSCFG : SrsSubframeCfg=SC0

 LST S1INTERFACE : S1InterfaceIsBlock=FALSE

c. Check board CPU load < VS.Board.CPUload.Mean>, normally it should be less than 70%

2.4 L.E-RAB.FailEst.SecurModeFail

a. Check license : < Security Mechanism >

 DSP LICENSE: LLT1SMECH01 Security Mechanism

b. Check eNodeB security parameter seeting :

 LST ENODEBCIPHERCAP: PrimaryCipherAlgo=AES, SecondCipherAlgo=Snow3G,

ThirdCipherAlgo=NULL;

 LST ENODEBINTEGRITYCAP: PrimaryIntegrityAlgo=AES, SecondIntegrityAlgo=Snow3G,

ThirdIntegrityAlgo=NULL;

c. Check any special UE which may have compatibility issue;

d. Check with EPC side for any authentication issue;

2.5 L.E-RAB.FailEst.NoReply

a. Check interference <L.UL.Interference.Avg> < -105dBm. If have high interference, need to

check PCI planning/GPS alarm for nearby sites/external interference.

b. Weak coverage : try to do the physical optimization or Power optimization ;

c. Top UE issue ;

4. PS Drop
TOP Cell condition: continuous 2 days NBH >1% & Failure number ≥ 5 or 1 day BBH PS drop
number ≥ 20

3.1 RF Failure

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 7 of 19

 For internal use only

 L.E-RAB.AbnormRel.Radio

a. If the issue happen suddenly, need to check any operation/event;

b. Check any related major alarm;

c. Parameter setting check :

 LST RRCCONNSTATETIMER: UeInactiveTimer=10s

 LST RLCPDCPPARAGROUP: UeMaxRetxThreshold=Maxretx_Threshold_t32,

ENodeBMaxRetxThreshold=Maxretx_Threshold_t32

 LST UETIMERCONST : T300=MS200_T300, T301=MS200_T301, T310=MS1000_T310,

T311=MS10000_T311, N311=n1, N310=n10

 For other parameter check, Pls use FMA tool to compare with normal sites;

d. Check interference <L.UL.Interference.Avg> < -105dBm. If have high interference, need

to check PCI planning/GPS alarm for nearby sites/external interference.

e. Check ANR switch enable or not and check any missing neighbor;

 LST ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1;

f. Weak coverage: need to check from CHR log, if have many ul weak coverage & UL signal

instant deterioration . if these two reason percent is high, need to improve the coverage;

g. Check if any top UE issue;

5. HOSR
TOP Cell condition: continuous 2 days NBH <99% & Failure number ≥ 10 or 1 day BBH PS drop
number ≥ 20

4.1 HO summary

In the current Huawei LTE system, the intra-frequency handover algorithm is triggered by

event A3 and the event reporting mode is event-triggered periodic reporting. When the

quality of a neighboring cell is higher than that of the serving cell by a preset value, event

A3 is triggered. According to 3GPP TS36.331, the conditions for event A3 are as follows:

Entering condition: Mn + Ofn + Ocn – Hys > Ms + Ofs + Ocs + Off

Leaving condition: Mn + Ofn + Ocn + Hys < Ms + Ofs + Ocs + Off

where the variables in the formulas are defined as follows:

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 8 of 19
 For internal use only

 Mn is the measurement result of the neighboring cell.

 Ofn is the frequency-specific offset (QoffsetFreq) of the neighboring cell and

the default value is 0. It is not considered in the evaluation for intra-frequency
handover.

 Ocn is the cell-specific offset of the neighboring cell and is determined by the
CellIndividualOffset parameter. When the value is not zero, this parameter is
delivered in the measurement control message; when the value is zero, this
parameter is not delivered. The parameter value determines the occasion
when an intra-frequency handover is triggered.

 Ms is the measurement result of the serving cell.

 Ofs is the frequency-specific offset (QoffsetFreq) of the serving cell and the
default value is 0. It is not considered in the evaluation for intra-frequency
handovers.

 Ocs is the cell-specific offset (CellSpecificOffset) of the serving cell; the default
value is zero.

 Hys is the hysteresis of event A3 and is determined by the IntraFreqHoA3Hyst

parameter. This parameter is delivered in the measurement control message.

 Off is the offset of event A3 and is determined by the IntraFreqHoA3Offset

parameter. This parameter is used by event A3 to adjust the degree of
difficulty of a handover. The sum of this value and the measurement value is
used to evaluate event entering or leaving. This parameter is delivered in the
measurement object of the measurement control message; its value can be
positive or negative. In case of a positive value, the difficulty in event
triggering is increased to postpone handovers; in case of a negative value, the
difficulty is decreased to advance handovers.

4.2 Ho troubleshooting e-Flow

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 9 of 19

 For internal use only

4.3 Ho Failure

As in our HO formula, we are using handover executions success divide handover

executions attempt, and there is no related failure counters. So we use below formula to

get the failure : (L.HHO.IntraeNB.IntraFreq.ExecAttOut)+

(L.HHO.IntereNB.IntraFreq.ExecAttOut) - (L.HHO.IntraeNB.IntraFreq.ExecSuccOut) -

(L.HHO.IntereNB.IntraFreq.ExecSuccOut)

a. Check the HO failure happen to which target cells:

Counters: L.HHO.NCell.ExecAttOut /L.HHO.NCell.ExecSuccOut/L.HHO.Ncell.PingPongHo

b. Check any related alarm and clear the alarm, especially PCI conflict alarm;

c. Check ANR switch enable or not and check any missing neighbor;

 LST ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-1;

d. Check neighbor PCI & TAC definition:

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 10 of 19

 For internal use only

 LST CELL to check target cell PCI (PhyCellId)

 LST CNOPERATORTA to check target cell TAC

 LST EUTRANEXTERNALCELL to check if the cell PCI&TAC definition is mapping or not.

e. Check X2 link, if not configuration, then request BSS team for help; and then do the ping

test to check if the link is ok or not, if have issue ,take transmission team for help.

f. Check HO parameter setting (see above description), and try to optimize;

g. Check interference <L.UL.Interference.Avg> < -105dBm. If have high interference, need

to check PCI planning/GPS alarm for nearby sites/external interference.

h. Weak coverage: need to check from CHR log, if have many ul weak coverage & UL signal

instant deterioration . if these two reason percent is high, need to improve the coverage;

6. Throughput

6.1 Throughput E-Flow

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 11 of 19

 For internal use only

6.2 Issue description

If we face a throughput issue, we first need to very clear about the issue description:

When: from when face the issue ?

Where: where face this issue ? special cell/site/area/whole network?

Who : who face the issue ? Single user or all users?

Which: which kind of device ?

What: what kind of issue ? no speed or low speed? For special Server or all the server?

How: how about the RF condition?

6.3 Issue troubleshooting

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 12 of 19

 For internal use only

After collect above information, it will be easy to begin analysis throughput issue:

a. If issue only happen from a special time, then pay more attention to check any

activity/fault from RF/BSS/Transmission/EPC side;

b. If issue is only happen on a special user, then pay more attention to the user

SIM/device/laptop issue. We can switch SIM/device to verify. For single SIM issue, also

need take EPC help to check the profile setting;

c. If issue happen on special site, then first need to check the configuration.

 LST IPPATH & LST IPRT to check IP configuration (need to configure all the12 UGW

IPs)

 LST VLANCLASS to check VLAN setting , VLAN ID need to map with transmission

planning. And need to define all the VLANCLASS SRVPRIO (0,10,18,26,34,46,63)

d. DSP license to check below license:

 Support of UE Category2/3/4 ; Throughput Capacity(per Mbps) ; DL 2x2

MIMO(per Cell)(TDD)

e. Check CPU load < VS.Board.CPUload.Mean>, normally it should be less than 70%. And

during drive test, also need to check if have frequent HO;

f. Check RF condition:

 If RSRP & SINR is poor, need to improve the coverage;

 If RSRP is good, but SINR is poor, need to check the PCI planning, and the neighbor RSRP,

if both 2 cells RSRP’s gap is below 3dB, then try to do optimization and give the a main

service cell;

 If Both RSRP & SINR is good, then need to check the RB count, if RB utilization is high

(>70%), and average user number is high(>20), but throughput is low, then can consider

traffic shift with nearby sites; or else go to next step.

g. Do the UDP/Ping test, if UDP is also low or have packet loss or big delay, then need to

take transmission team’ help;

h. Check interference <L.UL.Interference.Avg> < -105dBm. If have high interference, need

to check PCI planning/GPS alarm for nearby sites/external interference.

i. If still have issue, then raise the TT to GTAC/CNAC for help.

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 13 of 19
 For internal use only

7. IRAT Per call

For IRAT Per Call we need to exclude the CSFB. As in eRAN3.0 we don’t have such counter,

so we can use below formula to calculate it:

L.RRCRedirection.E2W - L.CSFB.E2W

Based on coverage, we can check below points:

a. Check any major alarm and any nearby sites down cause the coverage poor;

b. Check the IRAT parameter setting & Power setting:

 LST INTERRATHOCOMMGROUP : InterRatHoA2ThdRsrp=-115, InterRatHoA1A2Hyst=2

 LST PDSCHCFG: ReferenceSignalPwr=152(2T2R)/122(4T4R), Pb=1;

 LST CELLDLPCPDSCHPA: PaPcOff=DB_3_P_A

c. Check coverage, and try to do physical optimization.

8. CSFB
As current setting, our CS call is fall back to 3G by redirection;

a. Make sure the SIM card enable CS call (confirm with core network side)

b. Make sure TAC/LAC mapping & DNS etc. are definition well in MME side;

c. Check configuration in eNodeB side:

 LST CNOPERATORTA : TAC

 LST ENODEBALGOSWITCH : UtranCsfbSwitch-1; UtranRedirectSwitch-1;

 LST INTERRATPOLICYCFGGROUP : REDIRECTION-1

 LST UTRANNFREQ: Check 3G frequency;

 LTS UTRANNCELL: Check 3G neighbor;

d. Check 3G side: coverage/congestion/fault (or take 3G help)

9. Neighbor optimization
As our current setting, we enable the ANR automatically adding neighbor.

So for neighbor optimization, we pay more attention to Remove the useless neighbor:

Data source: Neighbor relation from CME or OMSTAR; 1 Week Neighbor HO from PRS;

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 14 of 19

 For internal use only

Optimization principle :

a. Source Cell have more than 40 Neighbores;

b. Between the Neighbors, there are no Ho attempt in total 7*24 hrs & double-direction

both have no HO;

c. The distance between the Neighbors are over 1KM ;

d. Above principle, if the remain neighbor is still more than 50, then put the distance to

over 500M;

e. When make script , also make the double-direction Neighbor & also remove the

external Ncell which are useless;

10. PCI conflict

PCI conflict will also cause many issue, like HO, Ps drop etc. Get the PCI conflict list from

M2000.

a. Check the conflict neighbor distance & azimuth, if distance is more than 3KM/over 4

layer sites, and also coverage different area, then we can remove the neighbor;

b. If distance is near or coverage towards same area, then need to re-plan the PCI;

c. If after remove neighbor, it’s continuous repeat, then need to check the coverage and

control the overshooting;

11. User complaint

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 15 of 19

 For internal use only

12. Resource monitoring

Alarm

KPI

Resource Formula Thres Action

Object hold

(Red)

License
L.Traffic.eNodeB.User.Max
usage of eNode >=80
/Maximum number of UEs add license
activated B %
specified by the license
Usage

UL PRB Used Rate Consider with PDCCH

>=80
PRB Usage =L.ChMeas.PRB.UL.Used.Avg/10 Cell resource & User
%
0 throughput
2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 16 of 19
 For internal use only

DL PRB Used Rate

=L.ChMeas.PRB.DL.Used.Avg/100

MOD
PRACH
CELLALGOSWITCH:
Resource （L.RA.GrpA.Att + >=75
Cell LocalCellId=x,
Usage(co L.RA.GrpB.Att）/3600/100 %
RachAlgoSwitch=Bac
mpete)
kOffSwitch-1

PRACH MOD

Resource CELLALGOSWITCH:
>=75
Usage(no L.RA.Dedicate.Att/3600/100 Cell LocalCellId=x，
%
n- RachAlgoSwitch=Ma

compete) ksIdxSwitch-1

1、MOD

CELLALGOSWITCH:

LocalCellId=xxx,

PucchAlgoSwitch=Pu
（L.ChMeas.CCE.CommUsed +
PDCCH cchSwitch-1;
L.ChMeas.CCE.ULUsed + >=80
Resource Cell 2、Physical
L.ChMeas.CCE.DLUsed） %
Usage optimization
/3600/1000/84
3、Divide the

coverage of the

eNodeB into more

cells

>=60 1.Divide TAC to

L.Paging.S1.Rx/3600/500 Cell
Paging % small;

Resource 2.MME side

>=150
Usage L.Paging.Dis.Num Cell parameter
0
optimization to

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 17 of 19

 For internal use only

reduce the Re-

Paging time after

first paging failure

LBBP/L 1.Changing LBBPC

VS.Board.CPULoad.CumulativeHi
MPT >=5% board to LBBPD
ghloadCount/3600
board boar;

CPU Load 2.Add LBBP board;

LBBP/L
>=60 3.Physical
VS.Board.CPUload.Mean MPT
% optimization;
board
4.Add new site

PRB Usage >70% & User

throughput < expectation

User throughput & Frequency 1.Physical

experienc efficiency > threshold optimization;

e User throughput = 2.Add new site;

L.Thrp.bits.DL/ L.Thrp.Time.DL

/1000;

1.Check alarm or
RRC
L.RRC.SetupFail.ResFail / board fault;
Congestio Cell
L.RRC.ConnReq.Att 2.Physical
n Ratio
optimization;

1.Check alarm or
E-RAB
L.E-RAB.FailEst.NoRadioRes / L.E- board fault;
Congestio Cell
RAB.AttEst 2.Physical
n Ratio
optimization;

13. Alarm
Important alarm related to Access/HOSR/PS Drop/Throughput:

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 18 of 19

 For internal use only

Alarm.xlsx

2016-09-09 Huawei Confidential. No Spreading Without Permission. Page 19 of 19