Sie sind auf Seite 1von 5

INITIAL LTE KPI TROUBLESHOOTING METRICS - NOKIA

ACCESSIBILITY RETAINABILITY MOBILITY INTEGRITY PARAMETERS INFO


Measure of the ability of a user Measure of the ability of a user UE moves from one eNB to User data speed in Mbps aPucchMinNumRrc:
to obtain an E-RAB from the to retain the E-RAB once target eNB while keeping its Minimum allocated number of
system. connected, for the desired connected state. LTE Services Possible Causes of UEs in the cell which may
The Initial E-RAB duration.Call drops are also will be uninterrupted. degradation: establish a RRC connection.
Establishment process can be referred as Radio Link Preparation – The Source LTE Downlink Throughput-
divided into the following Failures (RLF). eNodeB sends a request to the Cell Load(Users and PRB) countdownPucchCompr
phases: Target eNodeB, which PDCCH Blocking & higher specifies the countdown timer
The mechanisms dealing with performs admission control Usage that defines how long it takes
1.RRC CONNECTION RLF are implemented at both Execution – After successful Grant Bottleneck before any new SIB
ESTABLISHMENT UE and eNB side. preparation, the Source Air Interface modification process may be
2.S1 SIGNALING 1.If UE detects radio link eNodeB sends a handover Condition(RSSI,SINR,BLER) triggered again by a PUCCH
CONNECTION problems it tries to recover command to the UE RTT/Retransmission region compression.
ESTABLISHMENT from RLF during specified Ul thp
3.INITIAL E-RAB interval of time by RRC Mobility Issues TM mode setting rrcGuardTimer:
ESTABLISHMENT OR E-RAB connection re-establishment 1-Preparation Phase RRC Connected Users This timer is started when an
ADDITION procedure. 1.1- Wrong Tac Definition CQI Reporting Parameter RRC message for setup,
2.If eNB detects a radio link 1.2-X2-Link Failure Scheduler Limitation modification or release of a
RRC -Possible Causes of problem it will wait until the 1.3-CAC Failure QOS Profile radio bearer is sent to the UE.
degradation recovery (cancellation of 1.4-Prep Timer Expiry Application server When the timer expires, the
User or Control Plane and RLF state), or release the 1.5-Missing Neighbor eNB Data build corresponding procedure is
MME Overload ,Timer Expiry, UE. 1.6-MME pool should be same RS Pwr boost aborted
protocol Error,Lack of PUCCH The call drops can also be 1.7-Target cell is overloaded Others (VSWR,Backhaul
Resources,Max no of RRC initiated by the eNB (or MME) 1.8-Target cell Unavailable Capacity) Power Parameters:
Connection Reached,RF in other scenarios such as 1.9-Site Configuration issue Possible Causes of pMax- maximum output power
Quality Issues,cell availability timing alignment timer expiry, 2.0-Target cell has a fault degradation: of the cell
S1 Signalling -Possible S1 reset etc. (alarm, disabled cell, etc.) LTE Uplink Throughput dlCellPwrRed - dlCellPwrRed
Causes of degradation Cell Load(Users and PRB) value 0dB only
Transport issue,Wrongly Retainability Issues 2-Execution Phase Air Interface supported,Improve cell edge
Configured TAC,Degraded due UE SIDE- 2.1-Failure due to delay HO Condition(RSSI,SINR,BLER) behaviour , reduce interference
to H/W Issue 1.T310 expiry 2.2-Timer Expiry RTT/Retransmission and power consumption
ERAB -Possible Causes of 2.Maximum number of RLC 2.3-RLF DL thp dlChBw-Downlink channel
degradation retransmissions 2.4-ANR PCI Conflict (Collision Scheduler Limitation bandwidth
Radio & Transport resources 3.Handover failure (T304 & Confusion)* QOS Profile dlRsBoost- Transmission
not available,Radio connection expiry) 2.5-Target exceeds cell range Application server power of the downlink
with UE lost,Failure radio 4.Non-HO related random 2.6-Target is a sleeping cell eNB Data build reference signals in a cell is
interface procedure,Mobility access problem 2.7-Target has high uplink Others (VSWR,Backhaul boosted (positive value)
interference Capacity) respectively deboosted
Other Factor Impacting eNodeB SIDE- 2.8-Poor RF conditions Power control Strategy (negative value) compared to
Accessibility 1.PUSCH RLF 2.9-Due to radio deaf radio Proactive Scheduling PDSCH
RF Quality - 2.CQI RLF PUCCH and PRACH
1.Poor Coverage in DL and UL 3.HARQ RLF 3-Other Causes Overheads tHalfRrcCon:
impact the accessibility KPI 4.PDCCH Order failure 3.1-Poor Coverage The minimal time period during
2.High UL RSSI can cause 5.Maximum RLC 3.2-Interference GOOD THROUGHPUT which the internal state and the
degradation Retransmissions Exceeded at 3.3-Wrong Parameters in 1.RSSI- (< -105 DBM) resources associated with an
3.Low SINR impact the KPI eNB eNodeB 2.SINR- Value >= 20 half-open RRC connection (i.e.
4.Check whether the block 6.GTP-U failure at eNB 3.PRB UTILIZATION- (<80%) one for which no RRC
error rate (BLER) is 7.S1 reset Failure Counters : 4.POWER RESTRICTED connection setup complete
excessively high on the radio FAIL_INTRA_ENB_HO_PREP TRANSPORT BLOCK-UL - (< message has yet been
interface. Poor coverage* _AC 50%) received) must not be deleted
Admission Control Alarms* FAIL_ENB_HO_PREP_OTH 5.CQI-(>10) in the eNB.
Cell Availability High Load (high traffic)* FAIL_ENB_HO_PREP_TIME 6.MIMO RANK 2 TM2(PDF
Baseband Pooling Admission H/W issue (Re-set first) if FAIL_ENB_HO_PREP_AC RANGE 1) & TM3(PDF p0NomPucch:
Failures required replace RRU* FAIL_ENB_HO_PREP_OTHE RANGE 2) This parameter defines the cell
VSWR over threshold* R 7.HIGH USAGE OF 64 QAM specific nominal power to be
Failure Counters for RRC: INTER_X2_HO_PREP_FAIL_ AND 16 QAM SCHEME IN DL used for PUCCH power
SIGN_CONN_ESTAB_FAIL_O Faliure Counters: QCI 8.Rank indicator (should be 2) calculation in UE uplink power
VLUP ERAB_REL_ENB_RNL_UEL INTER_S1_HO_PREP_FAIL_ control equation (P2), for
SIGN_CONN_ESTAB_FAIL_C ERAB_REL_ENB_RNL_EUG TIME Parameter to Improve PRB controlling mean received SNR
P_POOL R INTER_S1_HO_PREP_FAIL_ inactivityTimer - 30 for control data.
SIGN_CONN_ESTAB_FAIL_O ERAB_REL_ENB_TNL_TRU NORR
VLMME ERAB_REL_ENB_RNL_RRN INTER_S1_HO_PREP_FAIL_ Parameter to Improve p0NomPusch:
SIGN_CONN_ESTAB_FAIL_P A OTHER PDCCH: This parameter defines the cell
UCCH ERAB_REL_HO_FAIL_TIM INTER_S1_HO_PREP_FAIL_ actLdPdcch – 0 specific nominal power for the
SIGN_CONN_ESTAB_FAIL_M EPC_EPS_BEARER_REL_RE QCI actOlLaPdcch – 1 PUSCH. Used for P0_PUSCH
AXRRC Q_RNL enableAmcPdcch – 1 calculation in UE uplink power
LTE_5590c E-UTRAN RRC EPC_EPS_BEARER_REL_RE Parameter for HO enablePcPdcch – 1 control equation (P1) for
Connection Setup Rejection Q_OTH Improvement: pdcchAggMsg4 – 8 controlling the mean received
Ratio (%) EPS_BEARER_SETUP_COM cellindividualoffsetEutran pdcchAggPaging – 4 SNR for user data during
LTE_5229e RRC Connection PLETIONS hysteresisA3 pdcchAggPreamb – 4 (re)transmission corresponding
Setup Failure Ratio due to RRC_CON_RE_ESTAB_ATT_ timeToTriggerA3 pdcchAggRaresp – 4 to a received PDCCH with DCI
"RRC timer expiry" failure (%) HO_FAIL a5ReportIntervalInterFreq- pdcchAggSib – 4 format 0 associated with a new
LTE_5230e RRC Connection RRC_CON_RE_ESTAB_ATT_ 240ms pdcchAlpha – 0.8 packet transmission.
Setup Failure Ratio per Cause HO_OTHER a5TimeToTriggerInterFreq- pdcchCqiShift – (-5)
RRCCOMPL_ERROR 480ms pdcchHarqTargetBler – 1

No. of Establishment RRC


Connections per cell offsetFreqInter-0dB Qrxlevmin:
(Connected Users) Parameters tuning for Call measQuantInterFreq-rsrp Parameter to Improve Specifies the minimum
RRC connected users,max Drop: interPresAntP-true Latency required RX RSRP level in the
Avg_RRC_UE_Per_Cell rrcGuardTimer - 3sec to hysThreshold3InterFreq-2 ilReacTimerUl – 0 cell.
12sec threshold3InterFreq-60 cellSrPeriod – 2ms
threshold3aInterFreq-11 Parameter to Improve MIMO
"RRC timer expiry" failure (%) HO_FAIL a5ReportIntervalInterFreq- pdcchAggSib – 4 format 0 associated with a new
LTE_5230e RRC Connection RRC_CON_RE_ESTAB_ATT_ 240ms pdcchAlpha – 0.8 packet transmission.
Setup Failure Ratio per Cause HO_OTHER a5TimeToTriggerInterFreq- pdcchCqiShift – (-5)
RRCCOMPL_ERROR 480ms pdcchHarqTargetBler – 1

No. of Establishment RRC


Connections per cell offsetFreqInter-0dB Qrxlevmin:
(Connected Users) Parameters tuning for Call measQuantInterFreq-rsrp Parameter to Improve Specifies the minimum
RRC connected users,max Drop: interPresAntP-true Latency required RX RSRP level in the
Avg_RRC_UE_Per_Cell rrcGuardTimer - 3sec to hysThreshold3InterFreq-2 ilReacTimerUl – 0 cell.
12sec threshold3InterFreq-60 cellSrPeriod – 2ms
No. of Active UE’s per Cell pdcchOrderConfig - 1 to 0 threshold3aInterFreq-11 Parameter to Improve MIMO T300:
ENB_LOAD_ACT_UE_AVG rlcProftPollRetr - 120ms to a3OffsetRsrpInterFreq-15 dlMimoMode - 10 Timer T300 supervises the
ENB_LOAD_ACT_UE_MA 200ms a3ReportIntervalRsrpInterFreq- mimoClCqiThD - 7 RRC connection establishment
nCqiDtx - 100 or 250 to 0 240ms mimoClCqiThU - 8 procedure.
Failure Counters for S1: rlcProfmaxRetxThresh - t16 to a3TimeToTriggerRsrpInterFreq-mimoClRiThD - 1.4
S1_SETUP_FAIL_IND_BY_M t32 320ms mimoClRiThU - 1.6 T301:
ME maxRetxThreshSrbUL - 16 to hysA3OffsetRsrpInterFreq-15 mimoOlCqiThD - 7 Timer T301 supervises the
S1_SETUP_FAIL_NO_RESP 32 threshold3InterFreqQci1-60 mimoOlCqiThU - 8 RRC connection re-
threshold3aInterFreqQci1-11 mimoOlRiThD - 1.4 establishment procedure.
Failure Counters for ERAB: Parameter to Improve ERAB: thresholdRsrpIFLBFilter--44 mimoOlRiThU - 1.6
ERAB_INI_SETUP_FAIL_RNL rrcGuardTimer - 3sec to thresholdRsrpIFSBFilter--100 Parameter to Improve T310:
_RRNA 12sec thresholdRsrqIFSBFilter--10 PUSCH: Timer T310 supervises the
ERAB_INI_SETUP_FAIL_TNL dFpucchF1b - 0 tS1RelPrepL - 2000 ms ulpcPuschConfig recovery from physical layer
_TRU dlSrbCqiOffset - -20 to -40 ulpcUpqualSch - 20 problems.
ERAB_INI_SETUP_FAIL_RNL Handover Preparation : ulpcPuschConfig
_UEL RLF Timer GUI Values: RRC Measurement Control ulpcLowqualSch - 0 T311:
ERAB_INI_SETUP_FAIL_RNL T300 - 1000ms (Source ENB ->UE) ulpcPuschConfig Timer T311 supervises the
_RIP T301 - 1500ms RRC Measurement Report (UE ulpcUplevSch - -88 RRC connection re-
T310 - 2000ms -> Source ENB) ulpcPuschConfig establishment.
LTE_5750a Cell Availability T311 - 5000ms X2AP Handover Request ulpcLowlevSch - -103
Ratio (%) t304IntraLte - 2000ms (Source ENB -> Target ENB) actUlpcMethod - 0 N310:
t304InterRAT - 500ms Uplink S1 Bearer deltaTfEnabled - 0 This is the maximum number
Parameters tuning for Call N310 - n20 Establishment (SGW <-> p0NomPusch - -80 of consecutive "out of sync"
Failures: N311 - n1 Target ENB) ulpcAlpha - 7 indications received from lower
aPucchMinNumRrc - 10 to 30 X2AP Handover Request Parameter to Improve layers.
countdownPucchCompr - Uplink PUSCH DTX detection Acknowledge (Target ENB -> PUCCH:
15min to 60min and recovery Source ENB) dFpucchF1 - 1 N311: Maximum number of
tHalfRrcCon - 3000ms to rlpDetEndNUl - 3(Mint) X2 Bearer Establishment dFpucchF1b - 0 consecutive "in-sync"
6000ms rlpDetMaxNUl - 1000(Mint) (Source ENB <-> Target ENB) dFpucchF2 - 1 indications received from lower
p0NomPucch: -120dBm to - dFpucchF2a - 1 layers.
117dBm CQI DTX detection and Handover Execution : dFpucchF2b - 1
p0NomPusch: -106dBm to - recovery 1. RRC Connection p0NomPucch - -116 nCqiDtx: The parameter
102dBm nCqiDtx - 0 Reconfiguration Request Parameter to Improve MCS: defines the number of
Qrxlevmin: -120dBm to - nCqiRec - 2 (Source ENB ->UE) actModulationSchemeUL - 0 consecutive CQI DTX
114dBm 2. X2AP SN Transfer Status actUlLnkAdp - 5 detections causing radio link
Uplink Ack/Nack DTX (Source ENB -> Target ENB) harqMaxTrDl - 5 failure indication.
Features: Detection 3. DL data flow during HO iniMcsDl - 4
actBbPooling - true ( rlpDetEndNoDl - 3(Mint) preparation (PGW -> UE) iniMcsUl - 5 dlSrbCqiOffset: Provides the
Baseband Pooling Feature ) rlpDetMaxNoDl - 1000(Mint) 4. UL data flow during HO ulsSchedMethod - 0 CQI link adaptation offset
RRC Connections, GBR, rlpDetMaxTimeDl - 0(Mint) preparation (UE -> PGW) Parameter to Improve RF applied to downlink
Scheduled UEs/TTI are 5. RACH Preamble (UE -> Quality: transmissions containing
dynamically distributed UE Detected Radio Link Target ENB) allowPbIndexZero - 0 SRB1 messages.
among cells depending on Failure initiates RRC 6. Random Access Response dlCellPwrRed - 0 The more negative the value,
Connection Re- (Target ENB -> UE) dlPcfichBoost - 0 the more conservative the
live traffic load.
establishment: 7. RRC Connection dlPhichBoost - 0 MCS and PDCCH aggregation
Improved individual cell
Possible Failure Reasons Reconfiguration Complete (UE -pMax - level will be for the downlink
capacity (up to 76% more RRC
resulting in Drop: > Target ENB) qrxlevmin - -130 SRB1 message transmissions.
connections possible in a
8. Transmit transmission of
single cell). When the signaling shown is
not completed, the RRC re- queued downlink data (Target Counters for troubleshoot: a3Offset: low values -
ENB -> UE) AVG UL PRBs handover earlier; high values -
Sleeping Cells Detection : establishment procedure fails
9. DL data flow during HO AVG DL PRBs delay the handover.
Early detection” which will The reasons for unsuccessful
execution (PGW -> UE) PRB_USED_UL_TOTAL
trigger after 30mins of below RRC re-establishment can be
10. UL data flow during HO PRB_USED_PUSCH hysA3Offset:low values - ping-
event : associated to, the transmission
execution (UE -> PGW) PRB_USED_PUCCH pong HO; High values - delay
1.RRC connection setup failure of RRC REESTABLISHMENT
11. S1AP path switch Request PRB_USED_DL_TOTAL the HO a& possible lead to lost
rate >= 1% REJECT message from the
(Target ENB -> MME) PRB_USED_PDSCH connection to the serving cell.
2.ERAB drop rate >=10% eNB .
12. Modify Bearer Request DL_SCH_Kbits_per_PRB_use
“Normal detection” which will Feature not activated
(MME -> PGW) d a3TimeToTrigger: low values -
trigger after 30mins of no Reception of another RRC
13. Modify Bearer Response ( UL_SCH_Kbits_per_PRB_use ping-pong HO; High values -
activity on the cell due to below CONNECTION
PGW -> MME) d delay the HO a& possible lead
procedure : REESTABLISHMENT
14. End Marker ( PGW -> Grant BottleNeck to lost connection to the
1.RRC attempts REQUEST
Target ENB) Average AGG level used for serving cell.
2.Throughput while the procedure is already
15. Downlink data flow after PDCCH
3.Successful RRC / bearer ongoing,
handover (PGW->UE) scheduling(LTE_1084a)(#) tS1RelPrepL : Timer is
setup attempts Unknown Reestab UE-Identity,
16. S1AP path switch Request Average Burst Initial Scheduler started when Source eNB
4.PRBs used for DL or UL Loss of S1 or cell service,
Ack (MME -> Target ENB) Delay sends S1AP:Handover
transmission CAC failure
17. . X2AP UE Context PDCP_PDU_Delay_PerLstTTI required message to MME and
Release (Target ENB -> _V1 (ms) it is stopped when S1AP
Source ENB) RSSI_PUSCH_AVG - Handover Command or S1AP
SINR_PUSCH_AVG Handover preparation failure.
RSSI_PUCCH_AVG -
SINR_PUCCH_AVG
INITIAL LTE KPI TROUBLESHOOTING METRICS - ERICSSON
ACCESSIBILITY RETAINABILITY MOBILITY INTEGRITY FORMULAS INFO
Measure of the ability of a Measure of the ability of a user UE moves from one eNB to User data speed in Mbps / Initial E-RAB Establishment
user to obtain an E-RAB to retain the E-RAB once target eNB while keeping its Throughtput in Bits per Success Rate:
from the system. connected, for the desired connected state. LTE Services second.
duration.Call drops are also will be uninterrupted. C=B.LOG(1+S/N) RRC Succ Rate =
The Initial E-RAB
referred as Radio Link Preparation – The Source (pmRrcConnEstabSucc/pmRrc
Establishment process
Failures (RLF). eNodeB sends a request to the GOOD THROUGHPUT ConnEstabAtt-
can be divided into the Target eNodeB, which CONDITION pmRrcConnEstabReAtt)*100
following phases: The E-RAB Retainability QCI performs admission control 1.RSSI- (< -105 DBM)
drops per second and Execution – After successful 2.SINR- Value >= 20 S1 Sign Succ Rate =
1.RRC CONNECTION percentage KPIs represent the preparation, the Source 3.PRB UTILIZATION- (<80%) (pmS1SigConnEstabSucc/pm
ESTABLISHMENT number of abnormal active eNodeB sends a handover 4.POWER RESTRICTED S1SigConnEstabAtt)*100
2.S1 SIGNALING releases initiated by the command to the UE TRANSPORT BLOCK-UL - (<
CONNECTION EnodeB and the MME. 50%) Erab Estab Succ Rate =
ESTABLISHMENT Mobility Issues 5.CQI-(>10) (pmErabEstabSuccInit/
3.INITIAL E-RAB Retainability Issues Preparation Phase 6.MIMO RANK 2 TM2(PDF pmErabEstabAttInit)*100
ESTABLISHMENT OR E-RAB 1.OSS Alarm MME pool should be same. RANGE 1) & TM3(PDF
ADDITION 2.UL Interference SpidHoWhiteList is active on RANGE 2) E-RAB Drop =
3.ERAB Abnormal release the target, which has 7.HIGH USAGE OF 64 QAM ((pmErabRelAbnormalEnbAct
Accessibility issues causes primaryplmnReserved set to AND 16 QAM SCHEME IN DL +
Poor coverage 4.UE Context Abnormal true. 8.Rank indicator (should be 2) pmErabRelAbnormalMmeAct)
Alarms release causes Target cell is overloaded (High / (pmErabRelAbnormalEnb +
High Load (High Traffic) 5.MME Abnormal release capacity) Total Performance - Check all pmErabRelnormalEnb +
H/W issue (Hard Reset on site 6.Mobility causes Target cell Unavailable : The important Accessibly, Mobility pmErabRelMme)) *100
/ RRU Replacement, if 7.CTR and UETR analysis target cell is down / disabled and Retainability KPI
required) 8.Poor coverage* TAC not defined on site, as per HO Preparation Succ Rate =
High UL interference 9.High Load (high traffic)* network design RRC Connected Users - Dl ((pmHoPrepSuccLteIntraF +
PCI conflict 10.H/W issue (Re-set first) if License issue/Software issue. Throughput would reduce with pmHoPrepSuccLteInterF) /
RACH Root Sequence Index required replace RRU* Target cell has a fault (alarm, increase in number of (pmHoPrepAttLteIntraF +
plan need to be reviewed 11.VSWR over threshold* disabled cell, etc.) connected users. pmHoPrepAttLteInterF)) *100
UE camping in the wrong cell. Failure Counters: Site Configuration issue.
Cell Reselection Parameters ENODEB INITIATED E-RAB CQI ,64/16QAM,TM Modes HO Execution Succ Rate =
need to be tuned RELEASE:- 2-Execution Phase Av CQI, % 64QAM samples ((pmHoExeSuccLteIntraF +
Wrong System constant pmErabRelNormalEnb ANR PCI Conflict (Collision & and RI indicates DL SINR pmHoExeSuccLteInterF) /
setting(SC-556) pmErabRelAbnormalEnbAct Confusion) status. Average CQI should be (pmHoExeAttLteIntraF +
VSWR over threshold MME INITIATED E-RAB Target exceeds cell range high (>10%), % of 64QAM pmHoExeAttLteInterF)) *100
Cell availability RELEASE:- Target is a sleeping cell sample should be high (>10%),
pmErabRelMme Target has high uplink DL Average UE
Failures Counters for RRC: pmErabRelMmeAct interference PRB(DL) And PDCCH Throughput(Mbps) =
pmRrcConnEstabFailLic Poor RF conditions Utilization - High PRB and (pmPdcpVolDlDrb –
pmRrcConnEstabFailHighLoad 1.pmErabRelAbnormalEnbA PDCCH utilization would pmPdcpVolDlDrbLastTTI +
pmRrcConnEstabFailOverload ctCdt – The total number of Parameters for improving impact the DL Throughput pmPdcpVolDlDrbTransUm) /
pmRrcConnEstabFailActiveUs abnormal ERAB releases by intra LTE HOSR: pmUeThpTimeDl
erLicenseExceeded the eNB per cell due cell down cellindividualoffsetEutran DL Latency And RLC
pmRrcConnEstabFailFailureIn time (manual intervention) hysteresisA3 Retransmission - High value UL Average UE
RadioProcedure Probable Solutions : - Check timeToTriggerA3 of DL latency(>9ms) and RLC Throughput(Mbps) =
pmRrcConnEstabFailBearerAd Outage report retransmission(> 1%) would pmPdcpVolUlDrb /
missionRej 2.pmErabRelAbnormalEnbA Parameter tuning for Inter impact DL throughput. pmUeThpTimeUl
pmRrcConnReestFailLicMtRee ctHo – The total number of LTE HOSR:
st abnormal ERAB releases per a5Threshold1RSRP/-107 Power Limited UE And No Throughput Calculation:
pmRrcConnEstabFailLackOfR cell by the eNB due to a5Threshold2RSRP/-115 Of A2 Events - High
esources handover execution failure hysteresisA5/10 occurrence of Lets’ assume we have 20 MHz
pmRrcConnEstabFailUnspecifi Probable Solutions:- Check timeToTriggerA5/480 channel bandwidth.
pmRadioTbsPwrRestricted and
ed PCI Planning,Coverage pmBadCovEvalReport we need to calculate the
issue.Make EDT, Change If MCPC enabled, then the resource elements in a
indicates poor DL coverage.
Counters for S1 fails: Azimuth following parameters are subframe for this band i.e.
pmS1SigConnEstabFail High UL Interference issue on used: Alarm & Parameter/ Feature 12subcarriers x 7 OFDMA
Target cell a1a2SearchThresholdRsrp/- Check symbols x 100 resource blocks
Counters for ERAB Setup (PmRadiorecInterferencePwr). 103 x 2 slots= 16800 REs per
fails: Check Connection b/w hysteresisA1A2SearchRsrp/20RSSI - High uplink RSSI would subframe.
pmErabEstabFailGbrDlEnb Antenna Connector & RRU impact the throughput. Assume we have 64 QAM
pmErabEstabFailGbrUlEnb Connector. Major reasons / causes behind modulation and no coding, one
pmErabEstabFailAddedLic Also Repeater is responsible poor IRAT handover success % of 16 QAM samples - Low modulation symbol will carry 6
pmErabEstabFailInitLic sometimes for Hi-UL rate are as follows : - usage of 16 QAM modulations bits.
Interference. Might be due to Coverage gap between LTE & scheme in UL would impact 16800 modulation symbols x 6
Troubleshooting for CFR: Power Leakage. 3G/Other Technology. the UL throughput bits / modulation symbol =
High load – offload the traffic 3.pmErabRelAbnormalEnbA Improper parameter setting: 100800 bits.
Implementation of Hi-Cap ctUeLost – The total number a1a2SearchThresholdRsrp PUCCH & PUSCH SINR - So, the data rate is 100800 bits
Parameter (if Max RRC Conn of abnormal ERAB releases by from -110 dBm to -112 dBm Poor UL SINR conditions / 1 ms = 100.8 Mbps.
Users is more than the eNB per cell due that the b2Threshold2RscpUtra from -would impact UL throughput. With 4×4 MIMO, the peak data
150/sector and contact with the UE is lost 115 dBm to -105 dBm rate goes up to 100.8 Mbps x 4
pdcchutil>70% ) Probable Solutions:- a2CriticalThresholdRsrp from -
Power limited UE - High = 403 Mbps.
If still traffic load is more, Solve the Poor Coverage issue 122 dBm to -124dBm number of power limited UE Estimate about 25% overhead
new site integration and by changing tilt / azimuth or indicates poor uplink coverage. e.g. PDCCH, reference signal,
deployment plan is sync signals, PBCH, and some
submitted We get 403 Mbps x 0.75 = 302
Mbps.
appropriate parameter value BLER (bad coverage)
setting Failure Counters: Downlink Interference (Bad
dlMaxRetxTh of SRB1 E.g. : - partOfSectorPower, License Counters CQI) THROUGHPUT
ULMaxRetxTh of SRB1 ENB Power, P0NominalPucch pmHoPrepRejInLicConnUsers MIMO Parameters TROUBLESHOOTING:
pZeroNominalPucch: From - / P0NominalPusch (for uplink pmHoPrepRejInLicMob Scheduling algorithm
120 to -117 Coverage). pmHoPrepRejInLicRlcUm Low Demand Check whether the block error
High UL NI Issue(As per earlier pmHoPrepRejInLicMultiErab rate (BLER) is excessively high
pdcchutil>70% ) Probable Solutions:- a2CriticalThresholdRsrp from - Power limited UE - High = 403 Mbps.
If still traffic load is more, Solve the Poor Coverage issue 122 dBm to -124dBm number of power limited UE Estimate about 25% overhead
new site integration and by changing tilt / azimuth or indicates poor uplink coverage. e.g. PDCCH, reference signal,
deployment plan is sync signals, PBCH, and some
submitted We get 403 Mbps x 0.75 = 302
Mbps.
appropriate parameter value BLER (bad coverage)
setting Failure Counters: Downlink Interference (Bad
dlMaxRetxTh of SRB1 E.g. : - partOfSectorPower, License Counters CQI) THROUGHPUT
ULMaxRetxTh of SRB1 ENB Power, P0NominalPucch pmHoPrepRejInLicConnUsers MIMO Parameters TROUBLESHOOTING:
pZeroNominalPucch: From - / P0NominalPusch (for uplink pmHoPrepRejInLicMob Scheduling algorithm
120 to -117 Coverage). pmHoPrepRejInLicRlcUm Low Demand Check whether the block error
pZeroNominalPusch: From - High UL NI Issue(As per earlier pmHoPrepRejInLicMultiErab CQI reporting frequency rate (BLER) is excessively high
106 to -102 mentioned. Also make sure Other (VSWR, Backhaul on the radio interface. If the
qRxLevMin : from -120 to - Nominal power Should not set Coverage Evaluation capacity) BLER is higher than 10%, the
114 very high otherwise it will Counters channel condition is poor and
MCPC feature need to enable create interference in pmBestCellEvalReport Counters for troubleshoot will result in low throughput.
for poor coverage neighbour cell). pmBadCovEvalReport pmRrcConnMax Check whether uplink
connected users license 4.pmErabRelAbnormalEnbLi pmHoOscIntraF pmPrbUtilDl / pmPrbUtilUl interference exists, in a normal
Change from 1000 to 2000 c – The total number of pmHoOscInterF pmBadCovEvalReport case, the UL RSSI on each
abnormal E-RAB Releases pmMeasMissingNeighRel pmRadioRecInterferencePwrP resource block (RB) is about (
The following KPIs need to initiated by the RBS due to UCCH/pmRadioRecInterferenc – {119 to 120} ) dBm when the
be closely monitored, once license reject (per cell). IRAT MCPC FEATURE: ePwr cell is unloaded. If the RSSI is
the required changes for HI 5.pmErabRelAbnormalEnbA featureStateStateMobCtrlAtP pmsinrpucchdistr & 3 dBm to 5 dBm higher than
CAP Settings are ctTnFail – The total number of oorCov - provides information pmsinrpuschdistr the normal value (when un-
implemented: abnormal ERAB releases per about the licensed feature – pmRlcArqUlack / loaded), uplink interference
RACH Success Rate. cell due to S1 interface down, Mobility Control At Poor pmRlcArqUlNack exists. Locate the interference
Accessibility and Retainability. "X2 interface down" or Coverage. The feature needs pmSchedActivityCellDl source, and mitigate the
Max and Average RRC "Transport Resource to be set to 1. /pmSchedActivityUeDl interference (Could be some
Connected UEs. Unavailable pmRadioTxRankDistr external interferer or values of
High/Over load. Probable Solutions : - Issue serviceStateStateMobCtrlAtP pmRadioTbsPwrRestricted/pm pZeroNominalPusch in
Handover performance. can be resolved with the help oorCov - Indicates the RadioTbsPwrunRestricted neighbour cells are too high)
UL/DL Throughput. of NOC / IM Team by raising licensed feature Mobility pmMacHarqDlAck16qam/64qa Check whether the eNodeB’s
CCE utilization. the required tickets. Control At Poor Coverage. The m/Qpsk parameter settings are correct.
6.pmErabRelAbnormalEnbA feature needs to be set to 1. pmMacHarqDlNack16qam/64q If the values are inconsistent,
HI-CAP Parameters: ctHpr – The total number of am/Qpsk confirm whether the settings
ulMaxRetxThreshold - set to abnormal ERAB releases by mobCtrlAtPoorCovActive - pmMacHarqUlFail16qam/Qpsk are customized for the operator
8 (reduces the number of the eNB per cell due to Specifies if the feature Mobility pmMacHarqUlSucc16qam/Qps or have been changed to
uplink RLC retransmissions for handover preparation Control at Poor Coverage is k incorrect values
signaling radio bearer and data Probable Solutions:- enabled or disabled in the cell. Check whether the number of
radio bearer) MME missing issue or MME The parameter needs to be set Parameters for throughput users in the cell is excessively
tPollRetransmitDl - set to 160 might be disabled. to TRUE. improvement: large. If an excessively large
ms (It extends the downlink Transport issue suspected. number of users have
time for new poll if no status License issue suspected. a1a2SearchThresholdRsrp - dlMaxRetxThreshold accessed the cell and ENodeB
report is received for both Site Configuration issue. The Reference Signal (DRB/SRB) - 8/8 – Reduce the are exhausted when a UE
signaling radio bearer and data Received Power (RSRP) no. of RLC retransmission for accesses the cell, the user
radio bearer ) DL/UL MAXRETXTHDRB: threshold value for events SRB/DRB in DL. throughput will be low.
tPollRetransmitUl - set to dl maxRetxthdrb from 8 to 32 A1Search and A2Search. For Check whether relative license
160ms (It extends the uplink ul maxRetxthdrb from 8 to 32 single-carrier sites, ulMaxRetxThreshold information is incorrect and if
time for new poll if no status a1a2SearchThresholdRsrp (DRB/SRB) - 8/8 - Reduce the the license has not expired
report is received for both tinactivity timer value is replaces a2ThresholdRsrpPrim no. of RLC retransmission for Check whether the traffic
Signaling Radio Bearer and changed from 61s to 20s parameter. It needs to be set to SRB/DRB in UL. volume to the eNodeB is
Data Radio Bearer. The -116 for intraLTE, -112 for insufficient. A common reason
changes will reduce SE/TTI a3offset : Change from 3 to 2 interRAT_10 and -110 tPollRetransmitDl for the insufficient input traffic
usage for retransmissions, and dB interRAT_5. (DRB/SRB) – volume is a bottleneck
allow more SE/TTI to serve a2TresholdRsrpPrim : 160msec/1600msec. transmission bandwidth at an
traffic) Change from -120 to -110 a2CriticalThresholdRsrp - intermediate node.
deltaPsdRs2Tx - (3dB) to dBm. The Reference Signal noOfPucchsrUsers – 590 -
(0dB) (RS power boost is Received Power (RSRP) Max no. of PUCCH users is RBS Parameter Settings
reduced for inter-site/cell a3Offset = 3 dB, hysteresis = threshold value for event used EUtranCellFDD
interference under low Inter A2Critical. The dlChannelBandwidth /
Site Distance (ISD) RF radio performed once Neighbor Cell a2CriticalThresholdRsrp noOfPucchCqiUsers – 320 - dlChannelBandwidth
environment) RSRP > 4dB of Serving Cell parameter replaces Max no. of PUCCH users is (nrOfSymbolsPdcch) (Control
numInitialAccessAndIncomi RSRP a2ThresholdRsrpSec. The used Region Size)
ngHo - is changed from a A3 setting, A3 event handover setting for
will be performed when a2CriticalThresholdRsrp is - deltaPsdRs2Tx – 0dB – controls whether OLSM MIMO
Global 10 to Local 10 or 20 (It
neighbor cell is greater than 122 for all sites. Change RS Power boost to is used (2) or not.
reduces the maximum number
of initial accesses and a3Offset + hysteresis (RSRP) reduce DL inference and
of the current serving cell. timeToTriggerA2Critical - shrink coverage. this is the % part of RU
incoming handovers that are
allowed during a time window The time-to-trigger value for capability independent of
without triggering the load If retransmission limit measurement in event PdcchLaGinrMargin – 3dB – SectorEquipmentFunction::con
control mechanism ) increases from 8 to 32, RL A2Critical. This parameter is Reduce PDCCH link adaption fOutputPower settings
pdcchLaGinrMargin - set to failure due to retransmission set to 1280ms for all sites. algorithm from 10db to 3 db.
limit reached: UEs need this to be increased
30 (3dB) (This reduces
PDCCH link adaption SRB: 360ms (8) to 1440ms timeToTriggerB2 - The time QciProfilePredefined.schedu or ACK/NACKs are not
(32) to trigger value for the eventB2 lingAlgorithm – Favor user received successfully on
algorithm from 10db to 3 db .
DRB: 400ms (8) to 1600ms measurement. Set to 1280ms with better CQI in order to PUCCH.
3dB is a reasonable
compromise between saving (32) for all sites. increase the utilization of less
robust MCS Values. UEs need this to be increased
CCE resources and ensuring
Retainability issue due to HO from default or lots of errors
reception of PDCCH by the
failure: UL THROUGHPUT seen on PUSCH
UE)
Need to tune pzeronominalpucch (-120dBm
cellindividualoffset to -117dBm)
pzeronominalpusch (-102dBm
to -98dBm)

Das könnte Ihnen auch gefallen