Scribd
Upload
888 views

RRC Access Failures

The document discusses three types of RRC access failures in 3G networks: 1) RRC access failures caused by radio interface synchronization failure between the UE and BTS. 2) RRC access failures caused by issues with the UE. 3) RRC access failures caused by internal reasons within the RNC. It provides descriptions of each failure type and recommends evaluating failure reasons at the cell level and looking at radio parameters like UL interference, DL power, coverage, and BTS resource usage to diagnose and address dominant failure factors.

Uploaded by

Pradeep Dhote
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
888 views

RRC Access Failures

The document discusses three types of RRC access failures in 3G networks: 1) RRC access failures caused by radio interface synchronization failure between the UE and BTS. 2) RRC access failures caused by issues with the UE. 3) RRC access failures caused by internal reasons within the RNC. It provides descriptions of each failure type and recommends evaluating failure reasons at the cell level and looking at radio parameters like UL interference, DL power, coverage, and BTS resource usage to diagnose and address dominant failure factors.

Uploaded by

Pradeep Dhote
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

http://taktiktek.blogspot.in/2011/11/rrc-access-failures.

html
RRC ACC FAIL DUE TO RADIO INT SYNCH
NetAct name: RRC_CONN_ACC_FAIL_RADIO
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

RRC ACC FAIL DUE TO UU INT


NetAct name: RRC_CONN_ACC_FAIL_MS
Description: The number of RRC access failures caused by UE.
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

RRC ACC FAIL DUE TO RNC INTER REASONS


NetAct name: RRC_CONN_ACC_FAIL_RNC
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

3G - Optimization - Failure analysis


Failure analysis :

1. RRC Setup Failures,


Evaluate RRC Setup Failure at cell level

Evaluate the distribution among failure reason

In case the dominant factor is:


RRC_CONN_STP_FAIL_RNC --> at the moment no optimisation action is needed (typically is a fault or
Incoming SRNC Relocation failures)
RRC_CONN_STP_FAIL_ AC --> look at UL interference & DL power (-> UL power spikes & need to upgrade
radio capacity
Solution : Disable UL Admission Control if the number of failures is critical

RRC_CONN_STP_FAIL_ BTS
evaluate NBAP counters (radio link reconf. failure) and KPIs for troubleshooting BTS resource
use Pool Capacity KPI in order to evaluate lack of channel elements

check BTS configuration in terms of WAM and WSP allocation

expand the capacity or decrease the traffic offered to the site

in case the BTS is not responding delete and re-create the COCO

RRC_CONN_STP_FAIL_ TRANS
evaluate the number of reconfiguration failure due to transmission

Check COCO configuration

Use AAL2 Mux in case of two WAM

expand the capacity or decrease the traffic offered to the site

2. RRC Access Failures


Evaluate RRC Access Failure at cell level

Evaluate the distribution among failure reasons

In case the dominant factor is:

RRC_CONN_ACC_FAIL_RADIO --> it should be detected through drive test if UL or DL coverage:


UL Coverage --> tune CPICH and cell dominance (if UL interference is not the cause)

DL Coverage:

If UE does not receive the RRC Setup message --> tune SCCPCH Power

If UE does not synchronised in DL --> reduce N312 from 4 to 1 (tuning depends on UE model) or
tune CPICHToRefRABOffset vs Qqualmin (or Qrxlevmin)
RRC_CONN_ACC_FAIL_ MS --> UL Coverage << DL Coverage tune CPICH and cell dominance in order to
balance UL and DL (if UL interference is not the cause)

You might also like

pFad - Phonifier reborn

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

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy