Identify CSSR: CSSR Affected If Any of The Followings Take Place

Senin, 16 Januari 2012
Identify CSSR
CSSR affected if any of the followings take place :
 RRC Conn. Setup Fail
 RRC Conn. Access Fail
 RAB Setup Fail
 RAB Setup Access Fail
RRC/RAB Setup & Access Analysis Process Flow Chart
1. Check the problem cells and its neighbouring cells of any faulty alarms
2. Identify root cause failure distribution using Service Report -> RSRAN073
3. RRC_CONN_STP_FAIL_AC
 Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
 UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical
M1002C1 CH_REQ_LINK_REJ_UL_SRNC ----> Evaluate Prx Resource Problem
M1002C2 CH_REQ_LINK_REJ_DL_SRNC ----->Evaluate Ptx Resource Problem
4. RRC_CONN_STP_FAIL_BTS
 Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resources
 Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to
 evaluate lack of Channel Elements
 Expand the Capacity or decrease the traffic offered to the site
 In case BTS is not responding delete and re-create COCO
5. RRC_CONN_STP_FAIL_TRANS
 Evaluate Number of reconfiguration failure due the transmission

 Check COCO Configuration
 Use AAL2 Mux in case of two WAM
 Expand the capacity or decrease the traffic offered to the site
6. RRC_CONN_STP_FAIL_RNC
 Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)

 Required ICSU log tracing if no RNC fault or SRNC relocation problem
7. RRC_CONN_STP_FAIL_RNTI ALLO FAIL

RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU overload
8. RRC_CONN_STP_FAIL_IUB_AAL2_TRANS
Updated when there is shortage or blocking of AAL2 resource

A subset of RRC_CONN_FAIL_TRANS which include ERQ/ECF fail due to some reason such as DMPG
problem in RNC + ERQ/ECF fail due to transport resource needed in RNC between RNC/MGW
9. RRC_CONN_ACC_FAIL_RADIO
Dominant failure causes
Perform drive test to detect if UL or DL coverage
UL Coverage -> Tune Cell Dominance if the cause is UL interference
DL Coverage -> Tune SCCPCH Power if UE does not receive the RRC Setup Message
-> If UE does not synchronize, reduce N312 from 2 to 1 (depends on UE model) or tune CPICHToRefRABOffset vs Qqualmin
(or Qrxlevmin)
10. RRC_CONN_ACC_FAIL_MS
UL Coverage -> Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL interference if not the cause)
11. If RRC setup/access failure due to Radio/MS, it is also possible to check whether UEs are located at distance area or
close to cell edge area
Propagate delay counters from RRC measurement M1006C128-C148 reports call setup distance during RRC connection
request or cell update
This give hints that either cells has large coverage area (tall sites with over-shooting) or non-optimum cell coverage from
neighbouring cells
RAB setup & Access Fail Root Cause Analysis
1. Check the problem cells and its neighbouring cellsof any faulty alarms
2. Identify root cause failure distribution and main failure contributor using
Services -> RSRAN073
3. RAB_STP_FAIL_XXX_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
REQ_CS_VOICE_REJ_UL_SRNC -> Evaluate Prx cell resource
REQ_CS_VOICE_REJ_DL_SRNC -> Evaluate Ptx cell resource
NO_CODES_AVAILABLE_SF128/SF32 -> Evaluate AMR voice / PS64 code congestion
4. RAB_STP_FAIL_XXX_BTS
Evaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshooting BTS resources
Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to
evaluate lack of Channel Elements
Expand the Capacity or decrease the traffic offered to the site
In case BTS is not responding delete and re-create COCO
5. RAB_STP_FAIL_XXX_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533
Check COCO Configuration
6. RAB_ACC_FAIL_XXX_UE
Evaluate Cell resource Prx and Ptx(for example high uplink interference)
Check RB reconfiguration failure ration ( If ATO setting is insufficient – recommmended is 500ms )
7. RAB_ACC_FAIL_XXX_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
Required ICSU log tracing if no RNC fault or SRNC relocation problem
Identify CSSR 2nd
Berikut beberapa meas yang dibutuhkan untuk analisis CSSR

Identify CSSR: CSSR Affected If Any of The Followings Take Place

Uploaded by

Copyright:

Available Formats

Identify CSSR: CSSR Affected If Any of The Followings Take Place

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Identify CSSR: CSSR Affected If Any of The Followings Take Place

Uploaded by

Copyright:

Available Formats

Senin, 16 Januari 2012

 RAB Setup Fail

 RAB Setup Access Fail

RRC/RAB Setup & Access Analysis Process Flow Chart

 evaluate lack of Channel Elements

 Expand the Capacity or decrease the traffic offered to the site

 In case BTS is not responding delete and re-create COCO

 Evaluate Number of reconfiguration failure due the transmission

 Use AAL2 Mux in case of two WAM

 Expand the capacity or decrease the traffic offered to the site

 Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)

7. RRC_CONN_STP_FAIL_RNTI ALLO FAIL

Updated when there is shortage or blocking of AAL2 resource

RAB setup & Access Fail Root Cause Analysis

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.