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 Qrxlevm

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
Propagate delay counters from RRC measurement M1006C128-C148 reports call setup distance during RRC connection request or cell
This give hints that either cells has large coverage area (tall sites with over-shooting) or non-optimum cell coverage from neighbourin

RAB setup & Access Fail Root Cause Analysis

1. Check the problem cells and its neighbouring cells of 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 evaluat
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
ers in order to

RABOffset vs Qqualmin (or Qrxlevmin)

 not the cause)

d at distance area or close to cell edge area

ng RRC connection request or cell update
um cell coverage from neighbouring cells

de congestion

g BTS resources
5001) Counters in order to evaluate lack of Channel Elements
Identify CSSR 2nd

Berikut beberapa meas yang dibutuhkan untuk analisis CSSR

1. Check high call drop cells and its neighbouring cells of any faulty alarms

2. Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS, Iur, MS, RNC) – Services -> RSRAN079

3. Check SHO KPI if performance < 90% ( leads to radio failure)

Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)
Detect badly performing neighbours using HO success rate per adjacency counters (M1013)
High incoming HO failure rate in all adjs – check sync alarms
Assessing neighbor list plan and visualization check with map
Evaluate HO control parameters and trigger threshold

4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)

Check missing neighbour (M1015), GSM frequency plan neighbour RNC and MSC database consistency audit, check alarm of referen
Check RRC Drop ISHO RT / NRT

5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call
drop cause > 50%)

Check UL Lost Active KPI from Iub counters (active L1 synchronization failure) to check UL/DL path loss problem
Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC
Mapping radio failures with Tx power and CPICH related parameters -> CPICHToRefRABOffset, PTXDPCH MAX
Check Call reestablishment timer -> T315
Ecno distribution for bad coverage issue (M1007C38-M1007C47)
6. Check core network parameter setting if RAB_ACT_FAIL_XXX_IU

Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU

7. If high RAB_ACT_FAIL_XXX_BTS

Check if any BTS faulty alarm (7653 cell faulty alarm)

If no alarms, COCO detach/attach

8. If high RAB_ACT_FAIL_XXX_MS

Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)
 MS, RNC) – Services -> RSRAN079

ency audit, check alarm of reference clock in 3G or in 2G, check 2G TCH congestion

ath loss problem

TXDPCH MAX
HSDPA Retainability Analysis

1. Identify root cause failure distribution and main contributor of low retainability - RSRAN079

2. If high HSDPA Radio Link Failures (NRT) – dominant cause

Compare to Cell Update ATT due to Radio link Failure (M1006C39) and Cell Update ATT due to RLC Recoverable
Check Serving Cell Change failure rate (KPI RNC_733a) - high SCC failures lead to radio link failure -------> RSRA

Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue (M1007C38-M1007C47)

Check HSDPA FMCS Mobility Control Parameter (handover or SCC too late)
Check call re-establishment T315 timer due to radio link failure

3. If high HSDPA Non- Radio Link Failures (NRL)

UE responding with some failure message or not responding to some message but no RL failure (timer expiry) --

Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate

 Required ICSU log for further troubleshooting

HSDPA Retainability Failure Cause Analysis Flowchart

e ATT due to RLC Recoverable Error (M1006C40)
adio link failure -------> RSRAN079

issue (M1007C38-M1007C47) --> RSRAN039

no RL failure (timer expiry) --> RSRAN038

on failure rate
HSDPA Accessibility Analysis
1. Identify root cause of failure distribution and main failure contributor in Services –RSRAN073

2. If high HSDPA Access Failure _max user fails --> check RSRAN067

3. If high HSDPA Access Failure_UL DCH check

Rejected HS-DSCH return channel due to lack of radio power resource

Check M1002C521 or M1002C522 or M1000C144 (RAS06) – only when HSDPA static allocation
Check Cell resource PrxTotal, PtxTotal
Check scrambling code congestion

4. If high HSDPA Access Failure_UE

Check RB reconfiguration failure rate

ICSU log for UE types troubleshooting

5. If high HSDPA Access Failure_BTS

Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH)
Too high SHO overhead – all branches must have enough CE capacity if UE is in SHO when HS-DSCH allocation is started

6. HS-DSCH return channel setup fail due to Iub transport

Breakdown the failure distribution (64,128,384,MAC-d)

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 Iub Utilisation / max CID / avg CID
HS-DSCH allocation is started
Optimising Iub considering CID congestion

Following performance indicators are proposed :

M550: Average utilisation of AAL2 connections - includes R99, SRB, HSDPA and return channels

SUM_AAL2_CONNECTIONS / NBR_SAMPLES/ CID MAX = C4/C7/248

M550: Max utilisation of AAL2 connections during measurement period

MAX_AAL2_CONNECTIONS/CID MAX = C6/248

CID Utilisation Monitoring Process

The maximum CID utilisation is followed and forecasted to future so that there is enough time to introduce the
Average CID utilisation helps in interpreting if a peak in the maximum value is normal growth or just load varia
CID congestion is usually a problem of special events when there are a lot of voice calls and SMS
CID congestion is probable in DCH&HSDPA, DCH and RT_DCH VCCs
Unlikely in others

CID Optimisation Actions and RU10 Features

The CID congestion needs to be solved by adding a VCC

DCH&HSDPA (former shared) UP VCC

Likely to cause performance degradation to HSDPA if transmission capacity is not increas

- HSDPA rates are limited to VCC PCR
- UBR+ is not recommended with DCH&HSDPA VCC

Path Selection – CID congestion in RT VCC

- Introduce a 2nd RT VCC

- If additional capacity is not available then each VCC will get PCR_RT_NEW =
PCR_RT_OLD/2
- Capacity fragmentation may cause increased probability for AAL2 CAC blocking, with
AMR the impact should not be big
enough time to introduce the new configuration before CID congestion occurs.
mal growth or just load variation.
calls and SMS
Performance Measurements for Transport

Counter
ISHO vs Failures

Beberapa penampakan Failure yang ada di KPI ISHO :

1. UTRAN_NOT_ABLE_EXEC_ISHHO_RT
2. UE_NOT_ABLE_EXEC_ISHHO_RT
3. UTRAN_NOT_ABLE_EXC_ISHHO_NRT
4. UE_NOT_ABLE_EXEC_ISHHO_NRT
5. UNSUCC_IS_HHO_UE_TRX_PWR_RT
6. UNSUCC_IS_HHO_CPICH_ECNO_RT
7. UNSUCC_IS_HHO_CPICH_RSCP_RT
8. UNSUC_IS_HHO_UE_TRX_PWR_NRT
9. UNSUCC_IS_HHO_CPICH_ECNO_NRT
10. UNSUCC_IS_HHO_CPICH_RSCP_NRT

1. UTRAN_NOT_ABLE_EXEC_ISHHO_RT

Description: Number of inter-system handover failures for RT due to UTRAN. --- The failure can occur, for example, due to the follow

Updated: When the hard handover attempt fails before the serving RNC sends the handover When the RNC receives an RANAP: RELOC

2. UE_NOT_ABLE_EXEC_ISHHO_RT

Description : The number of times when during inter-system handover for RT the source RNC has ordered the UE to use a configuratio

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is "con

3. UTRAN_NOT_ABLE_EXC_ISHHO_NRT

Description: The number of inter-system handover failures for NRT due to UTRAN.

Updated: This counter is never updated.

4. UE_NOT_ABLE_EXEC_ISHHO_NRT

Description: The number of times when during inter-system handover for NRT the source RNC has ordered the UE to use a configurati

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE, and the failure ca

5. UNSUCC_IS_HHO_UE_TRX_PWR_RT
Description: The number of unsuccessful inter-system handovers caused by UE transmission power for RT. --- If the UE fails to establi

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is not

6. UNSUCC_IS_HHO_CPICH_ECNO_RT

Description: The number of unsuccessful inter-system handovers caused by CPICH Ec/No for RT. --- If the UE fails to establish the phy

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is not

7. UNSUCC_IS_HHO_CPICH_RSCP_RT

Description: The number of unsuccessful inter-system handovers caused by CPICH RSCP for RT. --- If the UE fails to establish the phys

Updated: When the source RNC receives an RRC: HANDOVER FROM UTRAN FAILURE message from the UE, and the failure cause is not

8. UNSUC_IS_HHO_UE_TRX_PWR_NRT

Description: The number of unsuccessful inter-system handovers caused by UE transmission power for NRT. --- If the UE fails to estab

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE, and the failure ca

9. UNSUCC_IS_HHO_CPICH_ECNO_NRT

Description: The number of unsuccessful inter-system handovers caused by CPICH Ec/No for NRT. --- If the UE fails to establish the ph

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE message from the UE, and the failure ca

10. UNSUCC_IS_HHO_CPICH_RSCP_NRT

Description: The number of unsuccessful inter-system handovers caused by CPICH RSCP for NRT. --- If the UE fails to establish the phy

Updated: When the source RNC receives an RRC: CELL CHANGE ORDER FROM UTRAN FAILURE from the UE, and the failure cause is no
ur, for example, due to the following reasons: relocation preparation procedure failure in the CN, or relocation resource allocation procedure fail

he RNC receives an RANAP: RELOCATION PREPATION FAILURE message from the CN, or the RNC does not receive an RANAP: RELOCATION COMMAN

dered the UE to use a configuration which the UE does not support. --- If the source RNC instructs the UE to use a configuration that it does not su

e UE, and the failure cause is "configuration unacceptable".

rdered the UE to use a configuration which the UE does not support. --- If the source RNC instructs the UE to use a configuration that it does not s

ge from the UE, and the failure cause is "configuration unacceptable".

or RT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to th

e UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is UE transmission power.

If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the recepti

e UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH Ec/No.

f the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the receptio

e UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH RSCP.

or NRT. --- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to

ge from the UE, and the failure cause is not "configuration unacceptable".

- If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the recep

ge from the UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH Ec/No.

If the UE fails to establish the physical channel(s) indicated in the handover command, the UE will revert to the configuration prior to the recept

he UE, and the failure cause is not "configuration unacceptable". This counter is updated only when the trigger reason is CPICH RSCP.
 resource allocation procedure failure in the target BSC.

an RANAP: RELOCATION COMMAND message from the CN within a certain time period. This counter is updated only during inter-system handovers

a configuration that it does not support, the UE will send a failure message to the source RNC. The handover procedure ends and the UE resumes

e a configuration that it does not support, the UE will send a failure message to the source RNC. The handover procedure ends and the UE resumes
 ert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. Th

eason is UE transmission power.

configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard ha

eason is CPICH Ec/No.

configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard han

eason is CPICH RSCP.

evert to the configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. T

e configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard h

e trigger reason is CPICH Ec/No.

e configuration prior to the reception of the handover command (old configuration) and transmit a failure message to the source RNC. The hard ha

reason is CPICH RSCP.

nly during inter-system handovers.

ocedure ends and the UE resumes normal operation as if no handover attempt had occurred.

rocedure ends and the UE resumes normal operation as if no handover attempt had occurred.
ure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had o

ge to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred.

e to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred.

lure message to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had

age to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred

ge to the source RNC. The hard handover procedure ends and the UE resumes the normal operation as if no hard handover attempt had occurred.
if no hard handover attempt had occurred.

handover attempt had occurred.

handover attempt had occurred.

s if no hard handover attempt had occurred.

d handover attempt had occurred.

handover attempt had occurred.

ISHO Analysis

Breakdown ISHO analysis into three phases:

Compressed mode performance (RNC_294c/RNC_295c)

Inter-system measurement success (RNC_573c/RNC_574c)
Inter-system handover success (RNC_300e / RNC_301d)

If high ISHO compressed mode start not possible

Check busy hour data of PrxTotal , PtxTotal and M1000C22 AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_

If Low ISHO Measurement Success Rate (RNC_573c/RNC_574c)

Check ADJG neighbour list for missing neighbours or existing neighbour performance (RNC_905a/RNC_902a)
Check parameter discrepancy (BSIC) or BSIC collision due to too tight reuse
Check Compressed mode parameter set
Check ISHO triggering Threshold – too slow triggering
Check EcNo Distribution (M1007C38-M1007C47) or propagation delay counters (M1006) to indicate low coverage

If Low ISHO Success Rate (RNC_300e <95% / RNC_301d < 80%)

Check missing or wrong 2G parameter in MSC/SGSN (LAC, CellId, BCCH)

Check discrepancy of Cell information in RNC
Check 2G cell GPRS/EGPRS data congestion

May require further troubleshooting with ICSU logging to determine root cause of failure
and M1000C20 AVE_PTXTOT_CLASS_3 for AC rejection

ce (RNC_905a/RNC_902a)

006) to indicate low coverage / interference problem

3G HO Basic reporting events

Intra frequency events

1A: Primary CPICH enters the reporting range (Ncell addition), If active set of UE is full, UE stops reporting 1A eve
1B: P-CPICH leaves the reporting range (Ncell deletion)
1C: Non-active P-CPICH becomes better than an active PCPICH
1D: Change of current best cell with new P-CPICH

1E : The measurement value of a primary pilot channel exceeds the absolute threshold

1F : The measurement value of a primary pilot channel is lower than the absolute threshold

Inter frequency events

2A : The best frequency changes
2B : The quality of the current cell frequency is lower than a certain threshold, but that of the non-used frequenc
2C : The estimated quality of the non-used frequency is higher than a certain threshold
2D : The estimated quality of the used frequency is lower than a certain threshold
2E : The estimated quality of the non-used frequency is lower than a certain threshold
2F : The estimated quality of the used frequency is higher than a certain threshold

Inter system events

3A : The estimated quality value of the used UTRAN frequency is lower than a certain threshold, and that of the o
3B : The estimated quality value of the other system is lower than a certain threshold
3C : The estimated quality value of the other system is higher than a certain threshold
3D : The best cell in the other system changes
ull, UE stops reporting 1A event

hat of the non-used frequency is higher than a certain threshold

n threshold, and that of the other system is higher than a certain threshold
2G -> 3G Cell Re / Selection

QsearchI (A_BTS)

With this parameter you define the threshold for dual mode mobiles in idle state to search for and to measure UT

If the parameter value is 7, dual mode mobiles in idle state measure always neighbour UTRAN cell(s). If the param

GPRS-capable mobiles do not use this parameter if NCCR is active in the serving cell

QsearchP (A_BTS)

With this parameter you define the threshold for GPRS capable dual mode mobiles to search for and to measure UTRAN neigh

This parameter is broadcast on BCCH.

In case this parameter is broadcast on BCCH it shall be used only if GPRS cell re-selection parameters for one or more cells are

If the parameter value is 7, GPRS-capable multi-RAT MSs measure always neighbour UTRAN cell(s). If the parameter value is 15

GPRS-capable mobiles use this parameter only if NCCR is active in the serving cell

fddQOffset (A_BTS)

With this parameter you define a UTRAN cell reselection offset for non-GPRS capable dual mode mobiles which are in the idle

The mobiles add the offset to the running average (RLA_C) of the received signal level of the serving GSM cell and non-serving

-32 db = minus infinity dB

range: -28..28 dB, step 4 dB

FDD_GPRS_Offset

FDDQmin (A_BTS)

This parameter defines a minimum Ec/Io threshold which must be exceeded before a non-GPRS capable dual mod

FDD_REP_QUANT
defines the reporting quantity for UTRAN cell

3G_Search_PRIO

Is used to inidicate to the MS if 3G cells can be looked for when BSIC decoding is required. (0=no, 1=yes, default:
search for and to measure UTRAN neighbour cells introduced in 3G Cell Reselection list when a running average of the receiv

ur UTRAN cell(s). If the parameter value is 15, dual mode mobiles in idle state do not measure any of the neighbour UTRAN c

or and to measure UTRAN neighbour cells introduced in 3G Cell Reselection list when a running average of the received downlink signal lev

meters for one or more cells are sent to the MS in a Packet Cell Change Order or Packet Measurement Order message

ll(s). If the parameter value is 15, GPRS-capable multi-RAT MSs do not measure any of neighbour UTRAN cells.

de mobiles which are in the idle state.

erving GSM cell and non-serving GSM cells. After that the mobiles compare the measured RSCP values of UTRAN cells with signal levels of t

non-GPRS capable dual mode mobile is allowed to make a reselection from the serving GSM cell to an adjacent WCDMA RAN
uired. (0=no, 1=yes, default: 1)
 unning average of the received downlink signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold.

any of the neighbour UTRAN cells.

the received downlink signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold.

TRAN cells with signal levels of the GSM cells.

ll to an adjacent WCDMA RAN cell that is using frequency division duplex (FDD) type access technology/mode
or above (8-15) the threshold. This parameter is broadcast only on BCCH.

nology/mode
3G --> 2G Cell Re / selection

Cell Re / selection Criteria S di define sbb :

Squal = Qqualmeas – Qqualmin

Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation

Dimana :

Squal : Cell Selection quality (dB)

Qqualmeas : Measured cell quality value
Qqualmin : Minimum required quality level in the cell (dB)

Srxlev : Cell Selection RX level value (dB)

Qrxlevmeas : Measured cell RX level value
Qrxlevmin : Minimum required RX level in the cell (dBm)

Pcompensation : max(UE_TXPWR_MAX_RACH – P_MAX, 0) in dB

"UE_TXPWR_MAX_RACH" : Maximum TX power level an UE may use when accessing the cell on RACH (dBm)
P_MAX : Maximum RF output power of the UE (dBm)

Cell Re / selection Criteria S akan terpenuhi jika :

Squal > 0
Srxlev > 0

Asumsi tidak menggunakan HCS maka :

If Squal > Sintrasearch, UE need not perform intra-frequency measurements

If Squal <= Sintrasearch, perform intra-frequency measurements

If Squal > Sintersearch, UE need not perform inter-frequency measurement

If Squal <= Sintersearch, perform inter-frequency measurements

If Squal > SsearchRAT m, UE need not perform measurements on cells of RAT "m"
If Squal <= SsearchRAT m, perform measurements on cells of RAT "m"

ex :
Sintrasearch = 4 dB: Equate to –16dB Ec/No
Sintersearch = 2 dB: Equate to –18dB Ec/No
SsearchRAT m, = 0dB: Equate to –20dB Ec/No

Parameter untuk Cell Re/Selection 3G --> 2G adalah :

HCS_PRIO : Defines the HCS priority level for a cell (def:0) (A_WCEL)

NCr : Defines the maximum number of cell reselections (def:8) (A_WCEL)

QHCS : Quality threshold level for applying prioritised hierarchical cell re-selection for a cell (def:WCDMA : -24) (A

Qhyst1 : Qhyst1 is used for TDD and GSM cells, and for FDD cells when cell selection and re-selection quality meas

Qhyst2 : Qhyst2 is used for FDD cells when cell selection and re-selection quality measure is set to CPICH Ec/No (d

QqualMin : The minimum required quality level in the cell (Ec/No) (def:-20) (A_WCEL)

QrxlevMin : The minimum required RX level in the cell (def: WCDMA -115, GSM -105) (A_WCEL)

SHCS_RAT : The RAT specific threshold for inter-RAT measurement rules (def:1) (A_WCEL)

Sintersearch : The threshold for inter-frequency measurements, and for the HCS measurement rules (def:2) (A_W

Sintrasearch : The threshold for intra-frequency measurements, and for the HCS measurement rules (def:4) (A_W

Slimit_SearchRAT : Threshold for skipping inter-RAT measurement rules in HCS (def:2) (A_WCEL)

Ssearch_RAT : The RAT-specific threshold for inter-RAT measurement rules (def:0) (A_WCEL)

SsearchHCS : Threshold for intra- and interfrequency measurement rules in HCS (def:1) (A_WCEL)

TCrmax : The duration for evaluating the allowed amount of cell reselections (def:60sec) (A_WCEL)

TCrmaxHyst : Cell reselection hysteresis for reverting from UE high-mobility measurements (def:0sec) (A_WCEL)

Treselection : The UE triggers the reselection of a new cell if the cell reselection criteria are fulfilled during the t

UseOfHCS : Indicates whether the serving cell belongs to a Hierarchical Cell Structure (HCS), or not (def:0) (A_WC
e cell on RACH (dBm)
or a cell (def:WCDMA : -24) (A_WCEL)

and re-selection quality measure is set to CPICH RSCP (def:4) (A_WCEL)

asure is set to CPICH Ec/No (def:4) (A_WCEL)

asurement rules (def:2) (A_WCEL)

asurement rules (def:4) (A_WCEL)

2) (A_WCEL)

:1) (A_WCEL)

0sec) (A_WCEL)

ments (def:0sec) (A_WCEL)

teria are fulfilled during the time interval Treselection (def:0) (A_WCEL)

e (HCS), or not (def:0) (A_WCEL)

RAB setup failures for CS voice calls

RAB SETUP FAILURES DUE TO AC FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_AC

Description: The number of RAB setup failures caused by admission control for CS voice.

When the RNC decides to reject the CS voice RAB request because the admission control entity reports a failure (excluding f

RAB SETUP FAILURES DUE TO BTS FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_BTS

Description: The number of RAB setup failures caused by BTS for CS voice.

When the RAB assignment fails due to radio link setup or reconfiguration failure. The failure can happen either in the Iub or in the Iur inter

RAB SETUP FAILURES DUE TO TRANSPORT FOR CS VOICE

RAB_STP_FAIL_CS_VOICE_TRANS
Description: The number of RAB setup failures caused by transport for CS voice.

When the RNC decides to reject the CS voice RAB request due to transport failure. This happens before the RRC: RADIO BEARER SETUP me

RAB SETUP FAILURES DUE TO RNC FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_RNC

Description: The number of RAB setup failures caused by RNC for CS voice.

When the RNC decides to reject the CS voice RAB request due to RNC internal failure. This happens before the RRC: RADIO BEARER SETUP

RAB SETUP FAILURES DUE TO FROZEN BTS FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for CS voice.

When the RNC decides to reject the CS voice RAB request because the admission control entity blocks the radio link establishment to ensu

RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_V_IUB_AAL2
Description: The number of RAB setup failures caused by Iub AAL2 transport resource shortage for CS voice.

When the RNC decides to reject the CS voice RAB request due to Iub transport resource shortage between RNC and WBTS. This happens be

RAB SETUP FAILURE CS VOICE WPS

NetAct name: RAB_STP_FAIL_CS_VOICE_WPS

Description: The number of RAB setup failures for CS voice calls using Wireless Priority Service. Also some other RAB SETUP FAILURE counte

When allocating resources for Wireless Priority Service CS Voice RAB fails and blind Inter-System handover to GSM is not possible for exam

RAB SETUP FAILURES DUE TO LICENCE FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_LIC

Description: The number of RAB setup failures caused by AMR capacity license exceeded for CS voice.

When the RNC rejects a CS Voice RAB request due to AMR capacity license exceeded.

RAB SETUP FAILURES DUE TO IUR TRANSPORT FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_IUR_TR

Description: The number of failed CS voice RAB setups due to Iur transport resources. Also counter M1001C82 is updated with this counter

When a CS voice traffic class RAB setup fails due to Iur transport resources.

RAB SETUP FAILURES DUE TO IU-CS TRANSPORT FOR CS VOICE

NetAct name: RAB_STP_FAIL_CS_VOICE_IU_CS

Description: The number of failed CS voice RAB setups due to Iu-CS transport resources. Also counter M1001C82 is updated with this coun

Updated: When a CS voice traffic class RAB setup fails due to Iu-CS transport resources.
orts a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

in the Iub or in the Iur interface.

C: RADIO BEARER SETUP message would be sent to the UE

RRC: RADIO BEARER SETUP message would be sent to the UE

o link establishment to ensure the setup of high priority calls. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.
 and WBTS. This happens before the RRC: RADIO BEARER SETUP message is sent to the UE

r RAB SETUP FAILURE counter is updated along with this counter.

SM is not possible for example due to no neighbour cell available. In this case RNC responds to CN with RANAP: RAB ASSIGNMENT RESPONSE("No Resou

is updated with this counter

82 is updated with this counter

 be sent to the UE

would be sent to the UE.

MENT RESPONSE("No Resource Available").
RAB setup failures for PS calls

RAB SETUP FAILURES DUE TO AC FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_AC

Description: The number of RAB setup failures caused by admission control for PS data conversational.

When the RNC decides to reject the PS data conversational RAB request because the admission control entity repo

RAB SETUP FAILURES DUE TO BTS FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_BTS

Description: The number of RAB setup failures caused by BTS for PS data conversational.

When the RAB assignment fails due to radio link setup or reconfiguration failure. The failure can happen either in

RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_TRANS

Description: The number of RAB setup failures caused by transport for PS data conversational.

When the RNC decides to reject the PS data conversational RAB request due to transport failure. This happens be

RAB SETUP FAILURES DUE TO RNC FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_RNC

Description: The number of RAB setup failures caused by RNC for PS data conversational.

When the RNC decides to reject the PS data conversational RAB request due to RNC internal failure. This happens

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA CONV

NetAct name: RAB_STP_FAIL_PS_CONV_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for PS data conversational.

When the RNC decides to reject the PS data conversational RAB request because the admission control entity bloc

RAB SETUP FAILURES DUE TO AC FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_AC
Description: The number of RAB setup failures caused by admission control for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request because the admission control entity reports a

RAB SETUP FAILURES DUE TO BTS FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_BTS

Description: The number of RAB setup failures caused by BTS for PS data streaming.

When the RAB assignment fails due to radio link setup or reconfiguration failure. The failure can happen either in

RAB SETUP FAILURES DUE TO TRANSPORT FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_TRANS

Description: The number of RAB setup failures caused by transport for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request due to transport failure. This happens before

RAB SETUP FAILURES DUE TO RNC FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_RNC

Description: The number of RAB setup failures caused by RNC for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request due to RNC internal failure. This happens befo

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_STREA_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for PS data streaming.

When the RNC decides to reject the PS data streaming RAB request because the admission control entity blocks th

RAB SETUP FAILURES DUE TO AC FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_AC

Description: The number of RAB setup failures caused by admission control for PS data interactive.

When the RNC decides to reject the PS data interactive RAB request because the admission control entity reports

RAB SETUP FAILURES DUE TO RNC FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_RNC

Description: The number of RAB setup failures caused by RNC for PS data interactive.

When the RNC decides to reject the PS data interactive RAB request due to RNC internal failure. This happens bef

RAB SETUP FAILURES DUE TO ANCHORING FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_ANCH

Description: The number of RAB setup failures caused by ongoing relocation or hard handover for PS data interact

When the RNC rejects the PS data interactive RAB assignment request due to ongoing relocation or hard handover

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA INTERA

NetAct name: RAB_STP_FAIL_PS_INTER_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for PS data interactive.

When the RNC decides to reject the PS data interactive RAB request because the admission control entity blocks t

RAB SETUP FAILURES DUE TO AC FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_AC

Description: The number of RAB setup failures caused by admission control for PS data background.

When the RNC decides to reject the PS data background RAB request because the admission control entity reports

RAB SETUP FAILURES DUE TO RNC FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_RNC

Description: The number of RAB setup failures caused by RNC for PS data background.

When the RNC decides to reject the PS data background RAB request due to RNC internal failure. This happens be
RAB SETUP FAILURES DUE TO ANCHORING FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_ANCH

Description: The number of RAB setup failures caused by ongoing relocation or hard handover for PS data backgro

When the RNC rejects the PS data background RAB assignment request due to ongoing relocation or hard handove

RAB SETUP FAILURES DUE TO FROZEN BTS FOR PS DATA BACKG

NetAct name: RAB_STP_FAIL_PS_BACKG_FROZBS

Description: The number of RAB setup failures caused by frozen BTS for PS data background.

When the RNC decides to reject the PS data background RAB request because the admission control entity blocks

RAB SETUP NOT STARTED DUE TO NOT SUPPORTED PARAMETERS FOR PS

NetAct name: RAB_STP_FAIL_PS_NOT_SUPP_PAR

Description: The number of occasions when the PS RAB setup attempt is not started due to requested parameters

The counter is updated when RANAP: RAB ASSIGNMENT RESPONSE with error information is sent to the CN as a res

RAB SETUP NOT STARTED DUE TO UE CAPABILITY FOR PS

NetAct name: RAB_STP_FAIL_PS_UE_CAPA

Description: The number of occasions when the PS RAB setup attempt is not started due to requested parameters

The counter is updated when RANAP: RAB ASSIGNMENT RESPONSE with error information is sent to the CN as a res

RAB SETUP FAILURES DUE TO IUB AAL2 TRANS FOR PS DATA STREAM

NetAct name: RAB_STP_FAIL_PS_ST_IUB_AAL2

Description: The number of RAB setup failures caused by Iub AAL2 transport resource shortage for PS data stream

When the RNC decides to reject the PS data streaming RAB request due to Iub transport resource shortage betwee

RAB SETUP FAILURES DUE TO IUR TRANSPORT FOR PS STREAMING

NetAct name: RAB_STP_FAIL_PS_STRE_IUR_TR
Description: The number of failed PS Streaming traffic class RAB setups due to Iur transport resources. Also count

When a PS streaming traffic class RAB setup fails due to Iur transport resources.
ta conversational.

admission control entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER SETUP

failure can happen either in the Iub or in the Iur interface

port failure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.

nternal failure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.

ersational.

admission control entity blocks the radio link establishment to ensure the setup of high priority calls. This happens before th
ta streaming.

ission control entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER SETUP mes

failure can happen either in the Iub or in the Iur interface.

failure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

nal failure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

ission control entity blocks the radio link establishment to ensure the setup of high priority calls. This happens before the RR
ta interactive.

mission control entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER SETUP me

rnal failure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

handover for PS data interactive.

g relocation or hard handover.

mission control entity blocks the radio link establishment to ensure the setup of emergency calls. This happens before the RR

ta background.

mission control entity reports a failure (excluding frozen BTS reason). This happens before the RRC: RADIO BEARER SETUP me

ernal failure. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.
handover for PS data background.

g relocation or hard handover

mission control entity blocks the radio link establishment to ensure the setup of emergency calls. This happens before the RR

due to requested parameters are not supported by the RNC. The RAB setup attempt counter is not updated in this case.

tion is sent to the CN as a result of that the requested parameters are not supported.

due to requested parameters are not supported by the UE. The RAB setup attempt counter is not updated in this case.

tion is sent to the CN as a result of that the requested parameters are not supported.

shortage for PS data streaming.

ort resource shortage between RNC and WBTS. This happens before the RRC: RADIO BEARER SETUP message is sent to the UE
ansport resources. Also counter M1001C102 is updated with this counter.
he RRC: RADIO BEARER SETUP message would be sent to the UE

calls. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE
RC: RADIO BEARER SETUP message would be sent to the UE

s. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE
RC: RADIO BEARER SETUP message would be sent to the UE.

s. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE.

RRC: RADIO BEARER SETUP message would be sent to the UE

s. This happens before the RRC: RADIO BEARER SETUP message would be sent to the UE

not updated in this case.

t updated in this case.

TUP message is sent to the UE

RRC active failures

RRC ACTIVE FAIL DUE TO IU INT

NetAct name: RRC_CONN_ACT_FAIL_IU

Description: The number of RRC active failures caused by Iu-interface related problem.

When an Iu interface failure occurs, and the failure causes the release of the RRC connection. After this, the RNC

RRC ACTIVE FAIL DUE TO RADIO INTERFACE

NetAct name: RRC_CONN_ACT_FAIL_RADIO

Description: The number of RRC active failures due to radio interface.

When a radio interface failure occurs, and the failure causes the release of the RRC connection. After this, the RN

RRC ACTIVE FAIL DUE TO BTS REASONS

NetAct name: RRC_CONN_ACT_FAIL_BTS

Description: The number of RRC active failures due to BTS.

When a BTS failure occurs, and the failure causes the release of the RRC connection. After this, the RNC sends an

RRC ACTIVE FAIL DUE TO THE IUR INT

NetAct name: RRC_CONN_ACT_FAIL_IUR

Description: The number of RRC active failures due to drift RNC.

When a procedure failure in drift RNC occurs, and the failure causes the release of the RRC connection. After this

RRC ACTIVE FAIL DUE TO CIPH FAIL

NetAct name: RRC_CONN_ACT_FAIL_CIPH

Description: The number of RRC connection releases after a failed Security Mode Control procedure.

When the RNC releases the RRC connection after receiving RANAP: IU RELEASE COMMAND with cause "Requested C

RRC ACTIVE FAIL DUE TO RNC INTER REASONS

NetAct name: RRC_CONN_ACT_FAIL_RNC
Description: The number of RRC active failures due to reasons not covered by the other failure counters.

When an RNC internal failure occurs, and the failure causes the release of the RRC connection. After this, the RNC

RRC ACTIVE FAIL DUE TO UE

NetAct name: RRC_CONN_ACT_FAIL_UE

Description: Number of RRC active failures due to UE.

When the RRC connection is released due to the UE not responding to an RRC message or responding with such fai

SRB ACTIVE FAILURE CONVERSATIONAL

NetAct name: SRB_ACT_FAIL_CONV

Description: The number of abnormally released RRC connections with standalone signalling radio bearer before R

When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old Se

SRB ACTIVE FAILURE STREAMING

NetAct name: SRB_ACT_FAIL_STREA

Description: The number of abnormally released RRC connections with standalone signalling radio bearer before R

When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old Se

SRB ACTIVE FAILURE INTERACTIVE

NetAct name: SRB_ACT_FAIL_INTERA

Description: The number of abnormally released RRC connections with standalone signalling radio bearer before R

When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old Se

SRB ACTIVE FAILURE BACKGROUND

NetAct name: SRB_ACT_FAIL_BACKG

Description: The number of abnormally released RRC connections with standalone signalling radio bearer before R
When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old Se

SRB ACTIVE FAILURE OTHER

NetAct name: SRB_ACT_FAIL_OTHER

Description: The number of abnormally released RRC connections with standalone signalling radio bearer before R

When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in the old Se
nnection. After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs

connection. After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs.

After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs

he RRC connection. After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs

ntrol procedure.

AND with cause "Requested Ciphering and/or Integrity Protection Algorithms not Supported" from the core network.
her failure counters.

onnection. After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs. The possible failure reasons updatin

e or responding with such failure message that the connection must be released. After this, the RNC sends a RANAP: IU RELE

gnalling radio bearer before RAB assignment. Both originating and terminating conversational calls are included.

C Active Failure in the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNE

gnalling radio bearer before RAB assignment. Both originating and terminating streaming calls are included.

C Active Failure in the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNE

gnalling radio bearer before RAB assignment. Both originating and terminating interactive calls are included.

C Active Failure in the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNE

gnalling radio bearer before RAB assignment. Both originating and terminating background calls are included.
C Active Failure in the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNE

gnalling radio bearer before RAB assignment.

C Active Failure in the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC CONNE
m the core network.
ossible failure reasons updating this counter are for example RNC internal failure, transmission failure or loss of Frame Proto

e RNC sends a RANAP: IU RELEASE REQUEST to all involved CNs

lls are included.

ent cause in RRC: RRC CONNECTION REQUEST is either Originating Conversational Call or Terminating Conversational Call.

e included.

ent cause in RRC: RRC CONNECTION REQUEST is either Originating Streaming Call or Terminating Streaming Call.

are included.

ent cause in RRC: RRC CONNECTION REQUEST is either Originating Interactive Call or Terminating Interactive Call.

are included.
ent cause in RRC: RRC CONNECTION REQUEST is either Originating Background Call or Terminating Background Call.

ent cause in RRC: RRC CONNECTION REQUEST is some other cause not covered by counters M1001C635-M1001C638.
ailure or loss of Frame Protocol synchronization.

ating Conversational Call.

Streaming Call.

g Interactive Call.
ng Background Call.

1C635-M1001C638.
RRC access failures

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 secon

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 secon

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
ation failure

e from the UE within 6 seconds, and the RNC has not received the NBAP message which indicates that L1 synchronisation has

e from the UE within 6 seconds, and the RNC has received the NBAP message which indicates that L1 synchronisation has bee

UP COMPLETE message from the UE. This counter is updated also in case of incoming SRNS relocations, inter-system handove
es that L1 synchronisation has been established between UE and BTS. This counter is updated also in case of inter-system han

at L1 synchronisation has been established between UE and BTS. This counter is updated also in case of incoming SRNS reloc

cations, inter-system handovers, and inter-RNC hard handovers

so in case of inter-system handovers and inter-RNC hard handovers

n case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers
RRC setup failures

RRC SETUP FAIL DUE TO HC

NetAct name: RRC_CONN_STP_FAIL_HC

Description: The number of RRC setup failures caused by Handover Control.

When the RNC decides to reject the RRC connection request because the handover control entity reports a failure

This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard ha

RRC SETUP FAIL DUE TO AC

NetAct name: RRC_CONN_STP_FAIL_AC

Description: The number of RRC setup failures caused by Admission Control.

When the RNC decides to reject the RRC connection request because the admission control entity reports a failur

After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated also in ca

RRC SETUP FAIL DUE TO BTS REASONS

NetAct name: RRC_CONN_STP_FAIL_BTS

Description: The number of RRC setup failures caused by BTS.

When the RNC decides to reject the RRC connection request due to unsuccessful radio link setup. After this, the R

This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard ha

RRC SETUP FAIL DUE TO TRANS

NetAct name: RRC_CONN_STP_FAIL_TRANS

Description: The number of RRC setup failures caused by Transport.

When the RNC decides to reject the RRC connection request due to transport failure. After this, the RNC sends an

This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard ha

RRC SETUP FAIL DUE TO RNC INTER REASONS

NetAct name: RRC_CONN_STP_FAIL_RNC
Description: The number of RRC setup failures caused by RNC internal reason.

When the RNC decides to reject the RRC connection request due to RNC internal failure. After this, the RNC send

This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard ha

RRC SETUP FAIL DUE TO FROZEN BTS

NetAct name: RRC_CONN_STP_FAIL_FROZBS

Description: The number of RRC setup failures caused by frozen BTS.

When the RNC decides to reject the RRC connection request, because the admission control entity blocks the radi

This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard ha

RRC CONN SETUP FAIL DUE TO RNTI ALLO FAIL

NetAct name: RRC_CONN_STP_FAIL_RNTI_ALLO

Description: Number of RRC setup failures caused by RNTI allocation failure

When the RNC decides to reject the RRC connection request due to RNTI allocation failure caused by RRMU overlo

RRC SETUP FAIL DUE TO IUB AAL2 TRANS

NetAct name: RRC_CONN_STP_FAIL_IUB_AAL2

Description: The number of RRC setup failures caused by Iub AAL2 transport resource shortage.

When the RNC decides to reject the RRC connection request due to Iub transport resource shortage between RNC
This counter is updated also in case of inter-system handovers, and inter-RNC hard handover

RRC SETUP REJECT DUE TO EMERGENCY CALL REDIRECTION

NetAct name: RRC_CONN_STP_REJ_EMERG_CALL

Description: The number of RRC connections rejected due to emergency call redirection.

When the RNC redirects an emergency call to the GSM network by sending an RRC CONNECTION REJECT with redir
RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD

NetAct name: RRC_CONN_STP_FAIL_ICSU_OVERL

Description: The number of RRC setup failures caused by ICSU overload.

When the RNC decides to reject the RRC connection request due to ICSU overload. After this, the RNC sends an RR
ontrol entity reports a failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

overs, and inter-RNC hard handovers

control entity reports a failure (excluding frozen BTS reason).

counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers

o link setup. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

overs, and inter-RNC hard handovers

. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

overs, and inter-RNC hard handovers

ure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE

overs, and inter-RNC hard handovers

control entity blocks the radio link establishment, to ensure the setup of high priority calls. After this, the RNC sends an RRC

overs, and inter-RNC hard handovers

ailure caused by RRMU overload. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE

e shortage.

ource shortage between RNC and WBTS. After this the RNC sends an RRC: RRC CONNECTION REJECT message to the UE

ONNECTION REJECT with redirection information to the UE

fter this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.
sage to the UE.

r-RNC hard handovers

er this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.

essage to the UE

ECT message to the UE

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 SRN

RRC_CONN_STP_FAIL_ AC --> look at UL interference & DL power (-> UL power spikes & need to upgrade radio cap
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 CPICHToRe

RRC_CONN_ACC_FAIL_ MS --> UL Coverage << DL Coverage tune CPICH and cell dominance in order to balance UL
ally is a fault or Incoming SRNC Relocation failures)

s & need to upgrade radio capacity

TS resource
UE model) or tune CPICHToRefRABOffset vs Qqualmin (or Qrxlevmin)

nance in order to balance UL and DL (if UL interference is not the cause)