ACCESSIBILITY for the E-UTRAN is a measure of the ability of a user to obtain an E-RAB from the system.

The Initial E-RAB Establishment process can be divided into the following phases:
 RRC CONNECTION ESTABLISHMENT
 S1 SIGNALING CONNECTION ESTABLISHMENT
 INITIAL E-RAB ESTABLISHMENT OR E-RAB ADDITION

Accessibility / SSSR Formula

ACCESSIBILITY for the E-UTRAN is a measure of the ability of a user to obtain an E-RAB from the system.
The Initial E-RAB Establishment process can be divided into the following phases:
 RRC CONNECTION ESTABLISHMENT
 S1 SIGNALING CONNECTION ESTABLISHMENT
 INITIAL E-RAB ESTABLISHMENT OR E-RAB ADDITION

Counters related :

Counter Remarks
pmRrcConnEstabAtt
RRC pmRrcConnEstabSucc
pmRrcConnEstabAttReatt
Primary pmS1SigConnEstabAtt
S1 Sig Conn
pmS1SigConnEstabSucc
pmErabEstabAttInit
Erab Init Establihsment
pmErabEstabSuccInit
pmRrcConnEstabFailLic CUL Congestion
RRC pmRrcConnEstabFailOverload
Secondary
pmRrcConnEstabFailHighLoad
Erab Init Establihsment pmErabEstabFailInitLic
1. Poor coverage
 Check inter site distance with neighbors site.
 Check value of pmBadCovEvalReport (if MCPC enabled, need to check pmCriticalBorderEvalReport). If this counter is pegging
high in respect to RRC attempts, then we can say that more number of UEs are falling in bad coverage.
 Check pmRadioTbsPwrRestricted to see if UE has reached maximum power of UE.
 Check if the cell is overshooting and the power of the cell is to high

2. Alarms
 Through OSS commands “alt” (Current / Active site alarms can be checked) & “lga <nd>” (n is an integer value) (Site alarms
present for n days can be checked) .
 Sometimes, due to MOs are not synchronized properly, pmRrcConnEstabFailOverload is pegged high. In this case, the
ServiceUnavailable (S1 Connection failure) alarm is observed in sites, even though RRC Conn Users remain to be same.
3. High Load (High Traffic)
 The command “ue print -admitted” is used to find the no. of UEs currently latched to the site sector-wise ROP-wise & the
counters “pmRrcConnMax (max)” & “pmRrcConnMax (sum)” are used to find out ‘max. active users/ day’ and ‘sum of all
active users/day’, respectively.
 Connected User License Congestion
Check counter “pmRrcConnEstabFailLic” . If this counter is pegging, which means there will be rrc connection request reject
due to Connected User License limitation.
4. H/W issue (Hard Reset on site)
 If RRUs are disabled, in that case “HW fault” alarm is observed in sites.
 Command “st . aux” shows that the operational state of the auxiliary unit/ RRUs is DISABLED.

CONTD.
5. High UL interference
 High UL N+I is impacting to all KPIs. UL NI values {-119 …….. -110 dBm} is considered to be good.
 The cause may be Internal Sources (Check Tx & Rx antenna ports, fiber cables and connectors. All connection should be
proper) and External Sources ( like repeaters, airport, power plant etc. sources resulting in high EMW in the neighborhood).
 pmRadiorecInterferencePwr is checked for UL N+I values.
6. PCI conflict
 Two types of PCI conflict:
 PCI confusion, i.e., UE is confused if it is getting two or more target cells having same PCI.
 PCI collision, i.e., UE is collision due to source and target having same PCI.
 Impacts all KPIs.
 Use “EUtranCellFDD . pciconflict” to find out PCI conflict of site.
7. RACH Root Sequence Index plan need to be reviewed
 Based on ‘Zero Correlation Zero Configuration‘ parameter RACH root Sequence index need to be planned. Difference of 10 is
recommended for RACH root Sequence index per cell.
8. VSWR over threshold
 The cabx command provides VSWR status for RL1 & RL2 (for 2T2R). Both, RL1 and RL2 should be difference of less than 5.
9. Cell availability
 Cell availability should be 100% , more when it is in cell busy hour.
RETAINABILITY is defined as the ability of a user to retain the E-RAB once connected, for the desired duration.

Retainability / SARR Formula

Retainability Related Counters :

Counter Remarks
pmErabRelAbnormalEnbAct
Ret at EnodeB pmErabRelNormalEnb
Primary pmErabRelAbnormalEnb
pmErabRelMmeAct
Ret at MME
pmErabRelMme
pmErabRelAbnormalEnbActTnFail
Retainability due to Transport (s1 or X2 down)
pmUeCtxtRelAbnormalEnbActTnFail
pmErabRelAbnormalEnbActHo
Retainability due to Handover Failure (Execution)
pmUeCtxtRelAbnormalEnbActHo
pmErabRelAbnormalEnbActUeLost
Retainability due to Coverage
pmUeCtxtRelAbnormalEnbActUeLost
Additonal counter for
Secondary pmErabRelAbnormalEnbActCdt
analysis Retainability due to Cell Downtime
pmUeCtxtRelAbnormalEnbActCdt
pmErabRelAbnormalEnbActHpr Retainability due to Handover Failure (Preparation)
pmBestCellEvalReport
Retainability due to Coverage (ue move to another RAT)
pmBadCovEvalReport

pmMeasMissingNeighRel Retainaibility due to missing Neighbour Relation

1. Poor coverage*
Check if the cell is not overshooting and power per sector is not configured too high.
Check the CRSgain parameter if needed set to zero (default value)
2. Alarms*
Need to check alarm for HW fault and Transport alarm and Mixed Mode Configuration issue.
3. High UL RSSI Issue
 High UL N+I is impacting to all KPIs. UL NI values {-119 …….. -110 dBm} is considered to be good.
 The cause may be Internal Sources (Check Tx & Rx antenna ports, fiber cables and connectors. All connection should be
proper) and External Sources ( like repeaters, airport, power plant etc. sources resulting in high EMW in the neighborhood).
 pmRadiorecInterferencePwr is checked for UL N+I values.

4. VSWR over threshold*

The cabx command provides VSWR status for RL1 & RL2 (for 2T2R). Both, RL1 and RL2 should be difference of less than 5.

5. HO failure : If a sector is having high HO Execution fail, it results in poor retainability.

Probable Solutions: -
The counter pmErabRelAbnormalEnbActHo is checked. If this counter is pegging high, it implies poor retainability and resolution of
sector HOSR is required.
6. Missing Neighbour
As we implement ANR in the network, just need to make sure that Eutranfreqlrelation to 1350 already created on the EnodeB (per
Eutrancell)

*Already Mentioned in Accessibility

NOTE: MME drops are also very high during Poor RET. Need to investigate at MME end.
There is a limitation in MME drops analysis, these cannot be analyzed with the help of ENIQ alone, we need
MME statistics for this.
If MME drop is high, we need to investigate through the following steps :
 If BH/Core issue  All sectors will be impacted
 If MME issue  Multiple sites in the NW will be impacted.
1. pmErabRelAbnormalEnbActCdt – The total number of abnormal ERAB releases by the eNB per cell due cell down time (manual
intervention) with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed and that
there was data in either the UL or DL buffer (i.e. active).
Probable Solutions : - Check Outage report or Fluctuation Report.
2. pmErabRelAbnormalEnbActHo – The total number of abnormal ERAB releases per cell by the eNB due to handover execution failure
and that there was data in either the UL or DL buffer (i.e. active).
Probable Solutions:-
 Check PCI Planning is correct or not, to avoid PCI collision issue. There should not be any PCI re-use in nearby cells (Tier 1, Tier 2 neighbours).
 Coverage issue(make Any PCI Dominant which should be based on Clutter as per Common sense). Make EDT, Change Azimuth
 High UL Interference issue on Target cell (PmRadiorecInterferencePwr). Check Connection b/w Antenna Connector & RRU Connector.
 Also Repeater is responsible sometimes for Hi-UL Interference. Might be due to Power Leakage.
3. pmErabRelAbnormalEnbActUeLost – The total number of abnormal ERAB releases by the eNB per cell due that the contact with
the UE is lost with the pre-condition that the Initial Context Establishment procedure must first have been successfully completed and that
there was data in either the UL or DL buffer (i.e. active).
Probable Solutions:-
 Solve the Poor Coverage issue by changing tilt / azimuth or appropriate parameter value setting, E.g. : - partOfSectorPower, ENB Power, P0NominalPucch
/ P0NominalPusch (for uplink Coverage).
 High UL NI Issue(As per earlier mentioned. Also make sure Nominal power Should not set very high otherwise it will create interference in neighbour cell).
4. pmErabRelAbnormalEnbLic – The total number of abnormal E-RAB Releases initiated by the RBS due to license reject (per cell).
5. pmErabRelAbnormalEnbActTnFail – The total number of abnormal ERAB releases per cell due to S1 interface down, "X2 interface
down" or "Transport Resource Unavailable", with the pre-condition that the Initial Context Establishment procedure must first have been
successfully completed and that there was data in either the UL or DL buffer (i.e. active).
Probable Solutions : - Issue can be resolved with the help of NOC / IM Team by raising the required tickets.
4. pmErabRelAbnormalEnbActHpr – The total number of abnormal ERAB releases by the eNB per cell due to handover preparation
and that there was data in either the UL or DL buffer (i.e. active).
Probable Solutions:-
 MME missing issue or MME might be disabled.
 Transport issue suspected.
 License issue suspected.
 Site Configuration issue.
SARR – Session abnormal release rate
Mobility Success Rate [%]:

The ability to provide the requested service to the user with mobility
 MOBILITY X2 BASED HO PREPARATION

MOBILITY X2 BASED HO EXECUTION

When Intra LTE Handover triggered by event A3 , then ue will have 2 phase before HO takes place :
Preparation – The Source eNodeB sends a request to the Target eNodeB, which performs admission control
Execution – After successful preparation, the Source eNodeB sends a handover command to the UE

Counters related :

Counter Remarks
pmHoPrepAttLteIntraF
Preparation
pmHoPrepSuccLteIntraF
Primary
pmHoExecAttLteIntraF
Execution
pmHoExecSuccLteIntraF
pmHoPrepRejInLicConnUsers HO failure to due to CUL Congestion in Target Cell
Preparation pmHoPrepRejInLicRlcUm
Secondary pmHoPrepRejInLicMultiErab
pmRaSuccCfra
Execution To check if there is issue during RACH to target cell
pmRaAttCfra
Typically, handover preparations fail if there is something wrong with the target cell.
POSSIBLE CAUSES OF HANDOVER PREPARATION FAILURES
 MME pool should be same.
 If HO-Preparation fail = 100%, it might be due to MME pool different at source and target end.
 The command get . termpointmme can be used to find out the MME pool IPs. If different, set as per Market MME pool
. (In Jabo area all Enode B should only connect to one MME Pool (CISCO) after last migration Sept 7, 2016.
 Target cell is overloaded (High capacity): Target cell is suffered from CUL Congestion
 Target cell Unavailable or has active alarm : The target cell is down / disabled, X2 or S1 alarm or fault HW alarm.
 Feature / License related to IntraFrequency Handover is not active / disabled
 EnodeB id Conflict, between 2 enodeB that connect to same MME Pool.

POSSIBLE CAUSES OF HANDOVER EXECUTION FAILURES

 ANR PCI Conflict (Collision & Confusion)*

 Target exceeds cell range: The target cell is more than 15km from the UE (or the current cell range setting). In that case
Ho-Exec fail occur.
 Target is a sleeping cell – The target cell is sleeping, need fixed sleeping on daily basis.
 Target has high uplink interference* ,
If UL N+I is less than -110 dBm, in that case Ho-Exec fail occur.
 Poor RF conditions*
 RACH Failure to target cell
Based on ‘Zero Correlation Zero Configuration‘ parameter RACH root Sequence index need to be planned. Difference of 10 is
recommended for RACH root Sequence index per cell.
IRAT PSHO :

Ability to provide UE to be transfer another Radio Access Technology.

IRAT PSHO SR (%) = 100*(pmHoPrepSucc/pmHoPrepSucc)/(pmHoExeAtt/pmHoExeSucc)

Counter Remarks
pmHoPrepAtt
Preparation
pmHoPrepSucc
Primary
pmHoExeAtt
Execution
pmHoExeSucc
 MO Class Name Node Parameter Current Value
EnodeB qRxLevMin -120 dBm
EnodeB systemInformationBlock3_qHyst 3 dB
EnodeB tReselectionEutra 2s
EutrancellFDD
systemInformationBlock3_sNonIntraS
EnodeB 10 dB
earch
EnodeB threshServingLow 2 dB
Eutranfreqrelation EnodeB threshXLow 6 dB
Eutranfreqrelation EnodeB threshXhigh 24 dB
Utranfreqrelation EnodeB qRxLevMin -115 dBm
Utranfreqrelation EnodeB threshXLow 14 dB
UeMeasControl EnodeB a5B2MobilityTimer 20000
EnodeB a1a2SearchThresholdRsrp -116
EnodeB a2CriticalThresholdRsrp -120
ReportConfigSearch EnodeB hysteresisA1A2SearchRsrp 20
EnodeB timeToTriggerA2Search 640
EnodeB timeToTriggerA2Critical 640
EnodeB b2Threshold1Rsrp -44
ReportConfigB2Utra
EnodeB b2Threshold2RscpUtra -84
RNC qRxlevmin -120
Eutranfreqrelation
RNC threshigh 6
Typically, handover preparations fail if there is something wrong with the target cell.
POSSIBLE CAUSES OF HANDOVER PREPARATION FAILURES

 Check feature related PSHO in both side Enode B (source) and Target (RNC)
For 3G , PSHO feature is per RN C level.
 Target cell is overloaded (High capacity): 3G Cell is having congestion (Power, Code, CE , SF and HS and EUL user
admission.
 Target cell Unavailable or has active alarm : The target cell has active alarm.
 Check if RNCid, RAC, LAC and SC of target is correctly defined in Source Cell.
Check if 3G RNCid , RAC , LAC and SC is correctly defined in Enode B (as Source Cell) under MO : ExternalutrancellFDD . Miss
match of RNCid , RAC , LAC frequently happen after BTS Rehoming Activity. For SC , it might happen when there is SC retune in
corresponding 3G Cell target. When miss match detected , utrancellrelation deletion can be done to mitigate this issue.

POSSIBLE CAUSES OF HANDOVER EXECUTION FAILURES

 ANR PCI Conflict (Collision)

 Check if the cell (Source) is overshooting that cause PCI Collision.
 Check parameter “RelocOverallValue” is set to 10s
tRelocOverallValue recommended value for EnodeB that connect to CISCO MME.
RNC Features LTE related features :
FORMULA FOR DL/UL THROUGHPUT
LTE END USER QUALITY OF SERVICE IS IMPACTED BY THE CUMULATIVE EFFECT OF VARIOUS NODES & INTERFACES.
THE PICTURE BELOW SHOWS THE CONTRIBUTING FACTORS TO END USER THROUGHPUT.

Mobility
Radio Environment • HO E2E Dimensioning Core network /
ENodeB • C/I, SINR • Nbr of active
features Ping pong PDN performance
• Link Adaptation • Packet users/cell • IP delays
• MIMO 2x2 4x4 • MCS allocated • RB allocated End server /
• HARQ forwarding • Router / #of hops
• Backhaul • Packet losses UE laptop
• Session • TCP/IP
ENodeB setup Performance settings
Params • MTU size
Audit
• Rec. values

Peak
performance Delay of cell
BLER at Air I/F: End to End
Retransmission transition
Available Performance,
Session rate Core ntwrk delays
bandwidth
Establishment per user TCP/IP issues
Times

End user throughput

THROUGHPUT CHECK : USEFUL COUNTERS
ANALYSIS FLOW FOR DL THROUGHPUT INVESTIGATION
Check all important Accessibly, Mobility and Retainability KPI. Holistic overview of
Total Performance performance makes analysis simpler

Dl Throughput would reduce with increase in number of connected users

RRC Connected Users (pmRrcConnMax).

CQI ,64/16QAM,TM Av CQI, % 64QAM samples and RI indicates DL SINR status. Average CQI should be high
Modes (>10%), % of 64QAM sample should be high (>10%),

PRB(DL) And PDCCH High PRB and PDCCH utilization would impact the DL Throughput. (pmPrbUtilDl /
Utilization pmPrbUtilUl).

DL Latency And RLC High value of DL latency(>9ms) and RLC retransmission(> 1%) would impact DL
Retransmission throughput.

Power Limited UE High occurrence of pmRadioTbsPwrRestricted and pmBadCovEvalReport indicates poor

And No Of A2 Events DL coverage.

BASIC HEALTH CHECK UP AND BASELINE PARAMETER/FEATURE AUDIT ALONG WITH ALL CHECKS
ANALYSIS FLOW FOR UL THROUGHPUT INVESTIGATION
Check all important Accessibly, Mobility and Retainability KPI. Holistic overview of performance
Total performance makes analysis simpler

Alarm & Parameter/

Make Baseline Audit for Parameter and feature.
Feature Check

High uplink RSSI would impact the throughput (pmRadioRecInterferencePwrPUCCH /

RSSI pmRadioRecInterferencePwr)

% of 16 QAM samples Low usage of 16 QAM modulations scheme in UL would impact the UL throughput

PUCCH & PUSCH SINR Poor UL SINR conditions would impact UL throughput. (pmsinrpucchdistr & pmsinrpuschdistr)

High number of power limited UE indicates poor uplink coverage. (pmRadioTbsPwrRestricted

Power limited UE ,pmRadioTbsPwrUNRestricted)
 ESSENTIAL FEATURES

 IRC (interference rejection combining) should be enabled.

 Ul FSS (Ul frequency selective scheduling) should be enabled.
 Channel Bandwidth (5, 10, 15 and 20) MHz should be equal to licensed bandwidth.
 64-QAM DL should be enabled, since L15 this feature became basic feature.
 16-QAM UL should be enabled. since L15 this feature became basic feature.
 Dual Antenna DL Performance Package or MIMO should be enabled (for Site MIMO 2 x 2 )
ALL THESE FEATURES SHOULD BE ENABLED AT ENODEB FOR GOOD UL AND DL THROUGHPUT
ESSENTIAL PARAMETERS
Radio Network MO parameters:
 EUtranCellFDD
 transmission Mode default is 3, TxDiv and Open Loop Spatial Multiplexing (2x2 MIMO)
 pdcchCfiMode (number of OFDM symbols used for PDCCH, 1->3)
 maximumTransmissionPower = 460 (for 40 watt site, for MIMO 2 x 2)
 partOfSectorPower (for a sector)= 100
 pZeroNominalPucch  some UEs need this to be increased or ACK/NACKs are not received successfully on PUCCH.
 pZeroNominalPusch  some UEs need this to be increased from default or lots of errors seen on PUSCH.
 SectorEquipmentFunction
 confOutputPower = license power (20/40/60 Watt.
IRAT PSHO :

Ability to provide UE to be transfer another Radio Access Technology.

IRAT PSHO SR (%) = 100*((pmPdcpPktDiscDlPelr+pmPdcpPktDiscDlPelrUu+pmPdcpPktDiscDlH)/pmPdcpPktTransDl)

+

Counter Remarks
pmPdcpPktDiscDlPelr
pmPdcpPktDiscDlPelrUu DL Packet Loss at Uu intefarce
Primary
pmPdcpPktDiscDlHo DL Packet Loss due to Handover
pmPdcpPktTransDl

POSSIBLE CAUSES OF HIGH DL PACKET LOSS

 If counter pmPdcpPktDiscDlHo is pegging to high , check HO Intra LTE performance , good or bad.
 If counter pmPdcpPktDiscDlHo is peeging to high , check also if feature IntraLteHoDataFwd is active.
to minimize packet discard in EnodeB that is sent from EPC during Handover.
 High failure “pmPdcpPktDiscDlPelr”
It happens due to UDP Traffic that reach radio capacity and transport bandwith as well.
 Check if the cell has alarm (HW Fault, alarm , etc)