Professional Documents
Culture Documents
95 of cells (20%) are not meeting the CSV access in BBH. Average CSV access at NBH is 95%
1
Utility
LCV< 50
Category Inconsistent Transport RF BSS
Attempts BB Issue DG Issue Misc
95 cells (20%) are not meeting the CSV access in BBH. 35 cells having less than 20 Call
attempts in BBH.
4
RRC failures due to Radio Interface Synch, RI setup expiry, & time out of UU Interface
and CS RAB failures due to radio Interface procedure, timeout of UU rb setup & RI
Setup or reconfig timeout are caused by BW congestion.
RRC failures due to RI setup fail & RAB failures due to RI setup or reconfig fail are
caused by high CE utlization. Case study shown In further slides.
Average 14% of cells are not meeting the HSDPA+HSUPA+PS access success rate in BBH
6
Utility
LCV< 50
Category Inconsistent Transport RF BSS RCOM
Attempts
BB Issue DG Issue Misc
% of PS Access Failure
11.11 8.33 26.39 20.83 2.78 13.89 2.78 4.17 9.72
Reasons
PS RAB failures due to RI Setup or Reconfig timeout, Radio Interface Synch Procedure & timeout
of UU rb setup are caused by BW congestion.
PS RAB failures due to RI setup or reconfig fail & UE send rb setup failed are caused by high
CE utlization.Case study shown In further slides.
Average 91% of cells are not meeting IRAT in BBH. Average IRAT failure rate is 10% at NBH
93% of cells having at most 5 IRAT attemtps in NBH. The maximum IRAT attempt is in a cell in
NBH is 23 .
10
Description: The number of RRC access failures caused by radio interface synchronisation failure
When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the
UE within 6 seconds, and the RNC has not received the NBAP message which indicates that L1
synchronisation has been established between UE and BTS. This counter is updated also in case of
inter-system handovers and inter-RNC hard handovers.
Description: The number of RRC access failures caused by radio interface setup fail
The major reasons for RRC access failures caused by radio interface setup fail is Black of HW
resources at NodeB, eg BPC (CE) card.
Description: The number of RRC access failures caused by radio interface setup expiry
The major reasons for RRC access failures caused by radio interface setup expiry is BW congestion &
Packetloss
11
When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the
UE within 6 seconds, and the RNC has received the NBAP message which indicates that L1
synchronisation has been established between UE and BTS. This counter is updated also in case of
incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers
Description: The number of RRC access failures caused by RNC internal reason.
When an RNC internal failure occurs before receiving the RRC: RRC CONNECTION SETUP
COMPLETE message from the UE. This counter is updated also in case of incoming SRNS relocations,
inter-system handovers, and inter-RNC hard handovers
12
Case Study: To show the impact of BW congestion on RRC failures, due to Radio
Interface Synch & RI setup expiry
Case Study: To show the impact of high CE utlization on RRC failures due to RI setup fail
Bangalipara site of WB was added with one additional BPC (CE) card on 28th, after that
the number of failed RRC connection preparation,Due To Rl setup FAIL, has become
zero.
14
Case Study: To show the impact of BW congestion on RAB failures, due to Radio
Interface procedure & timeout of UU rb setup
Case Study: To show the impact of high CE utlization on RAB failure due to RL setup or reconfig
fail
16
17