Anda di halaman 1dari 23

Ericsson Internal

PROCESS DOCUMENT 1 (23)


Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

Standard Process Document

WCDMA PS Accessibility Analysis


Ericsson Internal
PROCESS DOCUMENT 2 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

Contents
1 INTRODUCTION .......................................................................................................... 3
1.1 PURPOSE .......................................................................................................... 3
1.2 SCOPE .......................................................................................................... 3
1.3 TOOLS .......................................................................................................... 3
2 TECHNICAL OVERVIEW................................................................................................ 3
3 RRC CONNECTION SETUP - PS ...................................................................................... 4
3.1 RRC CONNECTION SETUP – PS FLOWCHART. ......................................................... 6
4 RAB ESTABLISHMENT .................................................................................................. 8
4.1 RAB CONNECTION SETUP – FLOWCHART .............................................................. 11
5 ADMISSION CONTROL ................................................................................................ 15
5.1 POWER CONGESTION: .............................................................................................. 18
5.2 CODE CONGESTION: ................................................................................................. 19
5.3 UL/DL CE CONGESTION: ............................................................................................ 20
5.4 UL/DL ASE CONGESTION:.......................................................................................... 20
6 TRANSPORT NW/NODE BLOCKINGS: ......................................................................... 21
7 UL RSSI (RTWP): ........................................................................................................ 22
Ericsson Internal
PROCESS DOCUMENT 3 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

1 INTRODUCTION

1.1 PURPOSE

The purpose of this document is to specify the process for WCDMA PS accessibility analysis and
troubleshooting.

WCDMA PS accessibility methodology covers the study of OSS counters and related WRAN
parameter definitions based on the issues/improvement plans.

1.2 SCOPE

The scope of this document includes following


 OSS counters based analysis.
 Accessibility related parameter settings.

1.3 TOOLS

The measurement counters for WRAN can be accessed from the following
 MOSHEL (OSS login)
 ENIQ/BO
 ITK
 ESPA
 or similar PM ROP processing tools.

2 TECHNICAL OVERVIEW
Accessibility means the ability to successfully establish a radio connection for a requested Quality of
Service (QoS). Accessibility include the setup of a Packet-Switched (PS) and Circuit-Switched (CS)
Radio Resource Control (RRC) connection, the establishment of a Radio Access Bearer (RAB) for each
of the different service types.
Ericsson Internal
PROCESS DOCUMENT 4 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

3 RRC CONNECTION SETUP - PS


This traffic scenario describes both successful and unsuccessful attempts to set up an RRC connection
for an originating or terminating circuit-switched call.

The main counters for this scenario are as follows:

• pmTotNoRrcReq
• pmTotNoRrcConnectReq
• pmTotNoRrcConnectReqSucc
• pmTotNoRrcConnectReqPs
• pmTotNoRrcConnectReqPsSucc
• pmTotNoTermRrcConnectReq
• pmTotNoTermRrcConnectReqSucc
• pmTotNoTermRrcConnectReqPs
• pmTotNoTermRrcConnectReqPsSucc
• pmTotNoRrcConnectReqSubTr
• pmTotNoUtranRejRrcConnReq
• pmNoReqDeniedAdm
• pmNoFailedAfterAdm
Ericsson Internal
PROCESS DOCUMENT 5 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

• pmNoRejRrcConnMpLoadC
• pmNoRejRrcConnRrcLc
• pmNoRejRrcConnSpFlowCtrl
• pmNoRrcReqDeniedAdm
• pmNoRrcPsReqDeniedAdm
• pmNoLoadSharingRrcConn
• pmNoLoadSharingRrcConnPs
• pmNoRrcReqDeniedAdmDlPwr
• pmNoRrcReqDeniedAdmDlChnlCode
• pmNoRrcReqDeniedAdmDlHw
• pmNoRrcReqDeniedAdmUlHw
• pmNoRrcConnReqBlockTnPs
• pmNoRrcConnReqBlockNodePs
• pmSrbAdmExemptRrc
• pmTotNoRrcConnectSetup
• pmTotNoRrcConnectUeCapability
• pmTotNoRrcConnReqHsFach
• pmTotNoRrcConnReqSuccHsFach
• pmTotNoRrcConnReqPsHsFach
• pmTotNoRrcConnReqPsSuccHsFach
• pmTotNoRrcConnectReqCsfbInd
• pmTotNoRrcConnectReqCsfbIndSucc
 Standard RRC PS Accessibility KPIs
o UMTS_ERI_RRC_Att = pmTotNoRrcConnectReq
o UMTS_ERI_RRC_Succ = pmTotNoRrcConnectReqSuccess
o UMTS_ERI_RRC_Succ_Rate = 100 *
(pmTotNoRrcConnectReqSuccess/pmTotNoRrcConnectReq)
o UMTS_ERI_RRC_Fail_Rate = 100 * (1 -
(pmTotNoRrcConnectReqSuccess/(pmTotNoRrcConnectReq-pmNoLoadSharingRrcConn)))
o UMTS_ERI_RRC_Att_PS = pmTotNoRrcConnectReqPs-pmNoLoadSharingRrcConnPs
o UMTS_ERI_RRC_Succ_PS = pmTotNoRrcConnectReqPsSucc
o UMTS_ERI_RRC_Succ_PS_Rate = 100 *
pmTotNoRrcConnectReqPsSucc/(pmTotNoRrcConnectReqPs-
pmNoLoadSharingRrcConnPs)
o UMTS_ERI_RRC_Failures = (pmTotNoRrcConnectReq -pmNoLoadSharingRrcConn -
pmTotNoRrcConnectReqSuccess)
o UMTS_ERI_RRC_PS_Failures = (pmTotNoRrcConnectReqPs -
pmNoLoadSharingRrcConnPs - pmTotNoRrcConnectReqPsSucc)
 PS RRC failure causes can be identified by
1. MP load rejections (pmNoRejRrcConnMpLoadC) due to high MP load
2. Admission control (DeniedAdmDlPwr, DeniedAdmDlChnlCode, DeniedAdmDlHw,
DeniedAdmUlHw) due to resource unavailability
3. Transport NW/Node blockings (pmNoRrcConnReqBlockTnPs ,pmNoRrcConnReqBlockNodePs)
due to transport network congestion
Ericsson Internal
PROCESS DOCUMENT 6 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

3.1 RRC CONNECTION SETUP – PS FLOWCHART.

RRC Connection Setup - PS Scenario (Part A)


Ericsson Internal
PROCESS DOCUMENT 7 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

RRC Connection Setup - PS Scenario (Part B)


Ericsson Internal
PROCESS DOCUMENT 8 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

4 RAB ESTABLISHMENT
This traffic scenario describes both successful and unsuccessful attempts to set up a Radio Access
Bearer for a requested service

The main counters for this scenario are as follows:

• pmNoSuccRbReconfPsIntDch
• pmNoSuccRbReconfOrigPsIntDch
• pmNoSuccRbReconfPsIntHs
• pmNoSuccRbReconfOrigPsIntHs
• pmNoSuccRbReconfPsIntEul
• pmNoSuccRbReconfOrigPsIntEul
• pmNoRabEstablishAttempts
• pmNoRabEstablishSuccess
• pmNoRabEstablishAttemptPacketInteractive
• pmNoRabEstablishSuccessPacketInteractive
• pmNoRabEstablishAttemptPacketStream
• pmNoRabEstablishSuccessPacketStream
• pmNoRabEstAttemptPsStreamHs
• pmNoRabEstSuccessPsStreamHs
• pmNoRabEstablishAttemptPacketInteractiveHs
• pmNoRabEstablishSuccessPacketInteractiveHs
• pmNoRabEstablishAttemptPacketInteractiveEul
• pmNoRabEstablishSuccessPacketInteractiveEul
• pmNoRabEstablishAttemptPacketStream128
• pmNoRabEstablishSuccessPacketStream128
• pmRabEstablishEcAttempt
• pmRabEstablishEcSuccess
• pmNoInvalidRabEstablishAttempts
• pmNoRabEstablishFailureUeCapability
• pmNoRabEstAttemptPsIntNonHs
• pmNoRabEstSuccessPsIntNonHs
• pmNoFailedRabEstAttemptLackDlHwBest
• pmNoFailedRabEstAttemptLackUlHwBest
• pmNoFailedRabEstAttemptLackDlHw
• pmNoFailedRabEstAttemptLackUlHw
• pmNoFailedRabEstAttemptLackDlAse
• pmNoFailedRabEstAttemptLacKUlAse
• pmNoFailedRabEstAttemptExceedConnLimit
• pmNoFailedRabEstAttemptLackDlChnlCode
• pmNoFailedRabEstAttemptLackDlPwr
• pmNoFailedRabEstAttEulRateCong
• pmCmAttUlSf2
• pmCmSuccUlSf2
• pmCmAttDlSf2
• pmCmSuccDlSf2
Ericsson Internal
PROCESS DOCUMENT 9 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

• pmCmAttUlHls
• pmCmSuccUlHls
• pmCmAttDlHls
• pmCmSuccDlHls
• pmCmStop
• pmNoReqDeniedAdm
• pmNoFailedAfterAdm
• pmNoOfNonHoReqDeniedInteractive
• pmNoOfNonHoReqDeniedPsStreaming
• pmNoOfNonHoReqDeniedPsStr128
• pmNoOfNonHoReqDeniedHs
• pmNoOfNonHoReqDeniedEul
• pmNoRabEstBlockRnPsStreamHs
• pmNoRabEstBlockRnBestPsStreamHs
• pmNoRabEstBlockTnPsStrHs
• pmNoRabEstBlockTnPsStrHsBest
• pmNoRabEstBlockNodePsStrHsBest
• pmNoRabEstBlockTnPsStrNonHs
• pmNoRabEstBlockTnPsStrNonHsBest,
• pmNoRabEstBlkNodePsStrNonHsBest
• pmNoRabEstBlockTnPsIntNonHs
• pmNoRabEstBlockTnPsIntNonHsBest,
• pmNoRabEstBlkNodePsIntNonHsBest
• pmNoRabEstBlockTnPsIntHs
• pmNoRabEstBlockTnPsIntHsBest
• pmNoRabEstBlockNodePsIntHsBest
• pmSrbAdmExemptRab
• pmNoRabEstAttemptMultiPsInt
• pmNoRabEstSuccessMultiPsInt
• pmReconfAttSource,

 Standard RAB PS (R99)Accessibility KPIs


o UMTS_ERI_RAB_Att_PS = (<pmNoRabEstablishAttempt.PacketInteractive>
+<pmNoRabEstablishAttempt.PacketStream> +<pmNoRabEstablishAttempt.PacketStream128>)
o UMTS_ERI_RAB_Succ_PS = (<pmNoRabEstablishSuccess.PacketInteractive>
+<pmNoRabEstablishSuccess.PacketStream> +<pmNoRabEstablishSuccess.PacketStream128>)
o UMTS_ERI_RAB_Succ_PS_Rate = 100 * ((<pmNoRabEstablishSuccess.PacketInteractive>
+<pmNoRabEstablishSuccess.PacketStream> +<pmNoRabEstablishSuccess.PacketStream128>) /
(<pmNoRabEstablishAttempt.PacketInteractive> +<pmNoRabEstablishAttempt.PacketStream>
+<pmNoRabEstablishAttempt.PacketStream128>))
o UMTS_ERI_RAB_PS_Failures = (<pmNoRabEstablishAttempt.PacketInteractive>
+<pmNoRabEstablishAttempt.PacketStream> +<pmNoRabEstablishAttempt.PacketStream128>)-
(<pmNoRabEstablishSuccess.PacketInteractive> +<pmNoRabEstablishSuccess.PacketStream>
+<pmNoRabEstablishSuccess.PacketStream128>)
Ericsson Internal
PROCESS DOCUMENT 10 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

 Standard RAB PS (HS)Accessibility KPIs

o UMTS_ERI_RAB_Att_PS = (<pmNoRabEstablishAttempt.PacketInteractiveHs>
+<pmNoRabEstablishAttempt.PsStreamHs>)
o UMTS_ERI_RAB_Succ_PS = (<pmNoRabEstablishSuccess.PacketInteractiveHs>
+<pmNoRabEstablishSuccess.PsStreamHs>)
o UMTS_ERI_RAB_Succ_PS_Rate = 100* ((<pmNoRabEstablishSuccess.PacketInteractiveHs>
+<pmNoRabEstablishSuccess.PsStreamHs>)/(<pmNoRabEstablishAttempt.PacketInteractiveHs>
+<pmNoRabEstablishAttempt.PsStreamHs>))
o UMTS_ERI_RAB_PS_Failures = (<pmNoRabEstablishAttempt.PacketInteractiveHs>
+<pmNoRabEstablishAttempt.PsStreamHs>) - (<pmNoRabEstablishSuccess.PacketInteractiveHs>
+<pmNoRabEstablishSuccess.PsStreamHs>)

 PS RAB failure causes can be identified by


1. Admission control (LackDlPwr, LackDlChnlCode, LackDlHwBest, LackUlHwBest, LackDlHw,
LackUlHw, ExceedConnLimit, LackDlAse, LackUlAse) due to resource unavailability
2. Transport NW/Node blockings (pmNoRabEstBlockTnPsStrHs, pmNoRabEstBlockTnPsStrHsBest,
pmNoRabEstBlockNodePsStrHsBest,pmNoRabEstBlockTnPsStrNonHs,pmNoRabEstBlockTnPsStrN
onHsBest,pmNoRabEstBlkNodePsStrNonHsBest,pmNoRabEstBlockTnPsIntNonHs,pmNoRabEstBlo
ckTnPsIntNonHsBest,pmNoRabEstBlkNodePsIntNonHsBest,pmNoRabEstBlockTnPsIntHs,pmNoRa
bEstBlockTnPsIntHsBest,pmNoRabEstBlockNodePsIntHsBest) due to transport network congestion.
Ericsson Internal
PROCESS DOCUMENT 11 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

4.1 RAB CONNECTION SETUP – FLOWCHART

RAB Establishment Scenario (Part A)


Ericsson Internal
PROCESS DOCUMENT 12 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

RAB Establishment Scenario (Part B)


Ericsson Internal
PROCESS DOCUMENT 13 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

RAB Establishment Scenario (Part C)


Ericsson Internal
PROCESS DOCUMENT 14 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

RAB Establishment Scenario (Part D)


Ericsson Internal
PROCESS DOCUMENT 15 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

5 ADMISSION CONTROL

This traffic scenario describes the handling of Admission Control requests from various traffic
scenarios including Radio Link Addition, Radio Link Setup, Radio Link Deletion, Radio Link
Reconfiguration and Start Compressed Mode usage.

The main counters for this scenario are as follows:

 pmNoOfSwDownNgAdm
 pmNoFailedAfterAdm
 pmNoServingCellReqDeniedEul
 pmNoServingCellReqDeniedEulTti2
 pmNoNonServingCellReqDeniedEul
 pmNoOfDiscardedNbapCMessages
 pmLevelSampAseUl
 pmLevelSampAseDl
 pmLevelCompMode
 pmSoftCongGbrBwUl, pmSoftCongGbrBwDl
 pmSoftCongRbsUlHw
 pmSamplesDlCredits
 pmSumSqrDlCredits
 pmSamplesUlCredits
 pmSumSqrUlCredits
 pmSamplesDlCode
 pmSumSqrDlCode
 pmDlCredits
 pmUlCredits
 pmSumUlCredits
 pmSumUlCredits
 pmSumDlCode
 pmLevelDlCodeCnOp
Ericsson Internal
PROCESS DOCUMENT 16 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

Admission Control Scenario (Part A)


Ericsson Internal
PROCESS DOCUMENT 17 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

Admission Control Scenario (Part B)


Ericsson Internal
PROCESS DOCUMENT 18 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

Admission control blockings represents the resource congestion.


1. Power congestion
2. Code congestion
3. UL/DL CE congestion
4. UL/DL ASE congestion

5.1 POWER CONGESTION:

o Counters related to power congestion:


 pmNoRrcReqDeniedAdmDlPwr or pmNoFailedRabEstAttemptlackDlPwr can be
used as indication if RRC / RAB failure due to lack of DL power.
o Possible causes for power congestion:
 Check primaryCpichPower discrepancy.
 Check for output power parameter discrepency, which are mainly –
maxDlPowerCapability, maxTotalOutputPower, and
maximumTransmissionPower, as these parameter define output power of the cell.
 pwrAdm and pwrOffset parameter values can be verified.
 Check the propagation delay.
 Check the cell fluctuations (auto downtime and manual downtime) within own
cell, or neighboring cell.
 Check for alarms. For details, please refer Page 22.
 Check for licenses. For details, please refer Page 22.
o Recommendations to reduce power congestion:
 pwrAdm can be increased from till 84, if powerOffset is set to 15.
 Higher SF admission can be restricted. Ex: sf8Adm, sf4AdmUl, sf16Adm,
sf8AdmUl.
 Physical optimization.
 Alarm clearance.
 Power parameter discrepancy clearance.
 primaryCpichPower can be reduced.
 New site can be recommended if power congestion still exists after the above all
steps implementation.
 Increase the power capability of a cell by adding/upgrading an MCPA. The
available RBS DL Tx Carrier Power is limited by the MCPA capability (20W,
30W, 40W).
 Neighbor tuning can be done (inter/intra/IRAT neighbors).
Ericsson Internal
PROCESS DOCUMENT 19 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

5.2 CODE CONGESTION:

o Counters related to code congestion:


 pmNoRrcReqDeniedAdmDlChnlCode or
pmNoFailedRabEstAttemptlackDlChnlCode can be used as indication if RRC /
RAB failure due to lack of DL codes.
o Possible causes for code congestion:
 Check the dlCodeAdm parameter discrepancy.
 Check primaryCpichPower discrepancy.
 Check the propagation delay.
 Check the cell fluctuations (auto downtime and manual downtime) within own
cell, or neighboring cell.
 Check numHsPdschCode settings. If too high, it will block codes for R99 traffic.
 Check for alarms. For details, please refer Page 22.
 Check for licenses. For details, please refer Page 22.
o Recommendations to reduce code congestion:
 dlCodeAdm can be increased till 90.
 Higher SF admission can be restricted. Ex: sf8Adm, sf16Adm.
 Physical optimization.
 Alarm clearance.
 dlCodeAdm parameter discrepancy clearance.
 primaryCpichPower can be reduced.
 New carrier can be recommended if Code congestion still exists after the above
all steps implementation.
 Neighbor tuning can be done (inter/intra/IRAT neighbors).

5.3 UL/DL CE CONGESTION:

o Counters related to CE congestion:


 The following counters can be used as indication if RRC / RAB failure due to
lack of DL codes.
 pmNoFailedRrcConnectReqHw
 pmNoFailedRrcConnectReqCsHw
 pmNoFailedRrcConnectReqPsHw
 pmNoRrcReqDeniedAdmDlHw
 pmNoRrcReqDeniedAdmUlHw
 pmNoFailedRabEstAttemptLackDlHwBest
 pmNoFailedRabEstAttemptLackUlHwBest
o
Ericsson Internal
PROCESS DOCUMENT 20 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

o Possible causes for CE congestion:


 Check the dlHwAdm and ulHwAdm parameter discrepancy.
 Check primaryCpichPower discrepancy.
 In case the site has 2 DUWs, check for parameters dlLicFractBbPool2 and
ulLicFractBbPool2.
 Check the propagation delay.
 Check the cell fluctuations (auto downtime and manual downtime) within own
cell, or neighboring cell.
 Check for alarms. For details, please refer Page 22.
 Check for licenses. For details, please refer Page 22.
o Recommendations to reduce CE congestion:
 UL/DL CE license upgrade (128/256 to 256/384 on DUW20). If site has DUW10,
DUW to be upgraded to DUW20. If site is RBS3000, RAX/TX board addition.
 Reduce/disable EUL TTI 2msec users.
 Higher SF admission can be restricted. Ex: sf8Adm, sf4AdmUl, sf16Adm,
sf8AdmUl.
 Physical optimization.
 Alarm clearance.
 dlHwAdm/ulHwAdm parameter discrepancy clearance.
 primaryCpichPower can be reduced.
 Neighbor tuning can be done (inter/intra/IRAT neighbors).

5.4 UL/DL ASE CONGESTION:

o Counters related to CE congestion:


 pmNoFailedRabEstAttemptLackUlAse or pmNoFailedRabEstAttemptLackDlAse
can be used as indication for RAB failure due to lack of ASE.
o Possible causes for CE congestion:
 Check the aseDlAdm and aseUlAdm parameter discrepancy.
o Recommendations to reduce CE congestion:
 Increase aseDlAdm and aseUlAdm to 500.
Ericsson Internal
PROCESS DOCUMENT 21 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

6 TRANSPORT NW/NODE BLOCKINGS:

o Counters related to Transport NW/Node Blocking:


 AAL2 Setup Failures (Iub over ATM)
 pmUnSuccInConnsLocalQosClass<X>
 pmUnSuccInConnsRemoteQosClass<X>
 pmUnSuccOutConnsLocalQosClass<X>
 pmUnSuccOutConnsRemoteQosClass<X>
 RRC/RAB Failures due to TN Blocking (Iub over ATM/IP)
 pmNoRabEstBlockTns<Y>
 <X> can be A,B,C,D and <Y> can be varioud RAB types.
o Possible causes for Iub congestion:
 Transport NW/Node blocking counters pegging.
 High IubHsLimiting Ratio.
 Check for transport related alarms (e.g. SIU)
o Recommendations to reduce Iub congestion:
 ATM path/port discrepancy clearance (VLAN definitions).
 E1/Bandwidth expansion.
 Alarm clearance.
 Transport network - ATM to IP conversion.
Ericsson Internal
PROCESS DOCUMENT 22 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

7 UL RSSI (RTWP):

RTWP represents the UL interference. Both hot RTWP (>-98dBm) and cold RTWP (<-106dBm)
causes the service degradation. Hot RTWP majorly impacts Accessibility and Retainability KPIs.
Cold RTWP causes decreased traffic on the cell. For UL RSSI, following steps helps in
troubleshooting.
1. Give cold restart.
2. Check and clear VSWR alarm.
3. Check cell overshooting or NBR overshooting into the cell’s serving area.
4. Check and define missing neighbors.
5. Check Feeder/Jumper/HW connections.
6. Give hard reset.
7. Check configuration and recreate the site.
8. Check and clear obstructions in antenna main lobe or re-orient antenna.

License issue:

Licenses related to code, power etc. can be checked by ‘invh’ command after logging into site.

Alarms:

Alarms can be checked by using ‘ala’ command after logging into site. ‘lga x’ command can be used
to see history of alarms for ‘x’ number of days in the command.
Ericsson Internal
PROCESS DOCUMENT 23 (23)
Prepared (Subject resp) No.

Saptarshi Laskar/Saurabh Kaushik/Akash Srivastava


Approved (Document resp) Checked Date Rev Reference

2014-07-28 Ver 1

*For sudden degradation of any KPI, Cold Restart is preferred as preliminary action.

***