138198983 accessibility analysis walkthroughf

8/19/2019 138198983 Accessibility Analysis Walkthroughf

1/26

Accessibility AnalysisAccessibility AnalysisAccessibility AnalysisAccessibility Analysis

WalkthroughWalkthroughWalkthroughWalkthrough


2/26

Accessibility failures due

to lack of UL/DL HW


3/26

› Counters:› RRC blockings due to lack of HW:

› pmNoFailedConnectReqHw

› pmNoFailedConnectReqCsHw › pmNoFailedRrcConnectReqPsHw

› pmNoRrcReqDeniedAdmUlHw

› pmNoRrcReqDeniedAdmDlHw

› RAB blockings due to lack of HW:› pmNoFailedRabEstAttemptLackUlHw

› pmNoFailedRabEstAttemptLackDlHw

Blockings due to lack of HW


4/26

› Increasing the UL CE license› Increase the license UL CE if HW is available

› If HW is not available, Add RAXB and Upgrade the license

› In case there is no plan to upgrade the license or to performHW expansion, many parameters can be tuned

› Reduce the parameters Sf4AdmUl and Sf8AdmUl

› Reduce the eulServingCellUsersAdmTti2 since EUL TTI2msusers are very greedy in UL CE (8 CEs are reserved wih ladder)

› ulHwAdm can be increased from 95% to 99% to reduce

blockings

UL CE blockings


5/26

› Increase the license DL CE› Increase the license DL CE if HW is available

› If HW is not available

› Add TXB and Upgrade the license› In case TXB can not be added, Free one HS resource ID inorder to free 128 available CE and then Upgrade the license

› In case there is no plan to upgrade the license, manyparameters can be tuned

› Reduce the parameters Sf8Adm and Sf16Adm

› dlHwAdm can be increased from 95% to 99% to reduceblockings

DL CE blockings


6/26


to lack of DL power


7/26

› Counters:

› RRC blockings due to lack of DL Power:› pmNoRrcReqDeniedAdmDlPwr

› RAB blockings due to lack of DL Power:

› pmNoFailedRabEstAttemptLackDlPwr

Blockings due to lack of DL power


8/26

› Audit the parameters maxDlPowerCapability (MO:RbsLocalCell, Node: RBS) andmaximumTransmissionPower (MO: UtranCell, Node: RNC) to

check if there is any inconsistency

› CPICH power can be slightly reduced to free power for traffic(from 330 to 320)

› pwrAdm can be increased from 75 to 85

› Reduce sf8Adm in order to reduce the number of DL PS

RAB384 which are more power consuming than other RABs

Blockings due to lack of DL power


9/26


to lack of codes


10/26

› Counters:

› RRC blockings due to lack of DL Channelization Codes:› pmNoRrcReqDeniedAdmDlChnlCode

› RAB blockings due to lack of DL Channelization Codes:

› pmNoFailedRabEstAttemptLackDlChnlCode

Blockings due to lack of DL Codes


11/26

› Reduce the parameter numHsPdschCodes from 5 to (4 or3) in order to free codes from the tree

› dlCodeAdm can be increased from 70 to 85

› Reduce sf8Adm in order to free codes from the tree

› 2nd

carrier expansion

› New site

Blockings due to lack of DL codes


12/26


toUL/DL ASE


13/26

› Counters:› RAB blockings due to lack of ASE:

› pmNoFailedRabEstAttemptLackUlAse

› pmNoFailedRabEstAttemptLackDlAse

› Increase aseDlAdm. Other Radio resources (DL Power and Codes)should be closely monitored to detect any congestion

› Increase aseUlAdm. UL RSSI should be closely monitored

Blockings due to lack of ASE


14/26


to Exceed Connection Limit


15/26

› Counters:› RAB blockings due Exceed Conn limit:

› pmNoFailedRabEstAttemptExceedConnLimit

› The counter defines the number of failed PS RAB failed due to exceedingthe configured connection limit when allocating a specific SF code

› Counter is stepped when admission control fails with reject reason valueof SF4, SF8, SF16 or SF32

› Increase the parameters sf4Adm, sf8Adm, sf16Adm and sf32Adm (MO:UtranCell, Node: RNC) in order to reduce the blockings. This is not

recommended since this will be impacting other KPIs such as blockingsdue to DL codes and power

Blockings due to exceed conn limit


16/26

Accessibility failures

due to Node


17/26

› Counters:

› pmNoRrcConnReqBlockNodePs

› pmNoRrcConnReqBlockNodeCs

› pmNoRabEstBlockNodeSpeechBest

› pmNoRabEstBlockNodeCs57Best

› pmNoRabEstBlockNodeCs64Best

› pmNoRabEstBlkNodePsIntNonHsBest

› pmNoRabEstBlkTnPsStrNonHsBest

› pmNoRabEstBlkNodePsIntHsBest

› pmNoRabEstBlkNodePsStrHsBest

› Check if there any parameter misconfiguration

For example: hsdpaUsersAdm configured higher than maxNumHsdpaUsers

› Check if there is any faulty HW or hanging boards

Blockings due to Node

RRC

RAB


18/26

Accessibility failures

due to TN


19/26

› Counters:

› pmNoRrcConnReqBlockTnPs

› pmNoRrcConnReqBlockTnCs

› pmNoRabEstBlockTnSpeech

› pmNoRabEstBlockTnCs57

› pmNoRabEstBlockTnCs64

› pmNoRabEstBlockTnPsIntNonHs

› pmNoRabEstBlockTnPsIntNonHs

› pmNoRabEstBlockTnPsIntHs

› pmNoRabEstBlockTnPsStreamHs

› Check for Iub congestion

› Check for any misconfiguration on the Iub or Link Intermittent

Blockings due to TN

RRC

RAB


20/26

HS blockings due to

number of HSDPAusers


21/26

› Counter: pmNoOfNonHoReqDeniedHs

› Two parameters to be audited:

› hsdpaUsersAdm (MO: Utrancell, Node: RNC)

› maxNumHsdpaUsers (MO: RbsLocalCell, Node: RBS)

› Ideally speaking, hsdpaUsersAdm should be equal to 75% ofmaxNumHsdpaUsers. The 25% difference is used as mobility margin (HS cell

change) and reduces the risk for HS drops

› maxNumHsdpaUsers is directly related to licenseCapacityNumHsdpaUsers

› If maxNumHsdpaUsers = licenseCapacityNumHsdpaUsers› hsdpaUsersAdm can be increased to 90-95% of maxNumHsdpaUsers (1)

› If blockings are not solved using (1), IncreaselicenseCapacityNumHsdpaUsers, maxNumHsdpaUsers andhsdpaUsersAdm

HSDPA RAB blockings due to HS users limit


22/26

EUL blockings due to

number of EUL users


23/26

› Counter: pmNoOfNonHoReqDeniedEul

› Parameters to be audited:

› eulServingCellUsersAdm (MO: Utrancell, Node: RNC)

› eulNonServingCellUsersAdm (MO: Utrancell, Node: RNC)› eulServingCellUsersAdmTti2 (MO: Utrancell, Node: RNC)

› maxNumEulUsers (MO: RbsLocalCell, Node: RBS)

› maxNumEulUsers is directly related to licenseCapacityNumEulUsers

› Parameter eulNonServingCellUsersAdm can be set to limit a large number ofEUL users in soft/softer handover

› If maxNumEulUsers = licenseCapacityNumEulUsers

› eulServingCellUsersAdm can be increased to reach maxNumEulUsers (1)

› If blockings are not solved using (1), IncreaselicenseCapacityNumEulUsers, maxNumEulUsers and

eulServingCellUsersAdm

EUL RAB blockings due to EUL users limit


24/26

Failures After

Admission


25/26

› Counter: pmNoFailedAfterAdmBy definition, the counter defines the number of RRC or RAB failed after

being admitted by admission control

› The reasons of failures after admission are many:

› Iub congestion

› Wrong parameter settings (ex: parameters related to admission are higheron RNC than the RBS capability, ulHwAdm/dlHwAdm = 100, etc.)

› Coverage issues

› Pilot Pollution› Faulty HW

› Hanging Boards

› Transmission issues

› High UL RSSI› etc

› Failures after admission should be analyzed case by case to identify the

reason behind these failures and take the necessary actions accordingly

Failures After Admission


26/26

138198983 accessibility analysis walkthroughf

Documents