Counter Level 1 Sub Counter Level 2

VS.RAB.AbnormRel.CS.RF
(Number of CS RABs Abnormally
Released Due to RF for Cell)

VS.RAB.AbnormRel.CS
(Number of CS RABs VS.RAB.AbnormRel.CS.OM
Abnormally Released for Cell)
VS.RAB.AbnormRel.CS.Preempt

VS.RAB.AbnormRel.CS.UTRANgen

VS.RAB.AbnormRel.CS.IuAAL2

VS.RAB.AbnormRel.CS.OLC

VS.Call.Drop.CS.Other

Counter Level 1 Sub Counter Level 2

VS.RAB.AbnormRel.PS.RF
(Number of PS RABs Abnormally
Released Due to RF for Cell)
VS.RAB.AbnormRel.PS
(Number of PS RABs
Abnormally Released for Cell)
 VS.RAB.AbnormRel.PS.RF
(Number of PS RABs Abnormally
Released Due to RF for Cell)
VS.RAB.AbnormRel.PS
(Number of PS RABs
Abnormally Released for Cell)

VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt

VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC
VS.Call.Drop.PS.Other
Sub Counter Level 3

VS.RAB.AbnormRel.CS.RF.ULSync

VS.RAB.AbnormRel.CS.RF.UuNoReply

VS.RAB.AbnormRel.CS.RF.SRBReset

Sub Counter Level 3

VS.RAB.AbnormRel.PS.RF.ULSync

VS.RAB.AbnormRel.PS.RF.UuNoReply
VS.RAB.AbnormRel.PS.RF.SRBReset

VS.RAB.AbnormRel.PS.RF.TRBReset
Description

Number of CS RABs Abnormally Released Due to RF for Cell (Uplink Synchronization Fail)

Number of CS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure)

Number of CS RABs Abnormally Released for Cell (Signaling RLC Reset)

Number of CS RAB Release Requests for Cell (O&M Intervention)

Number of CS RAB Release Attempts for Cell (RAB Preemption)

Number of CS RAB Abnormal Releases Triggered by RNC for Cell (UTRAN Cause)

Number of CS RABs Abnormally Released for Cell (Iu Interface AAL2 Link Failure)

Number of CS Domain RABs Released Due to Congestion for Cell

Number of CS RAB Abnormal Releases due to other cause

Description

Number of PS RABs Abnormally Released for Cell (Uplink Synchronization Failure)

Number of PS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure)
Number of PS RABs Abnormally Released Due to Signaling RLC Reset for Cell

Number of PS RABs Abnormally Released for Cell (Traffic RLC Reset)

Number of PS RAB Abnormal Released Due to O&M Intervention for Cell

Number of PS RAB Abnormal Released Due to RAB Preemption for Cell

Number of PS RABs Abnormally Released Due to GTPU Failure for Cell

Number of PS Domain RABs Released Due to Congestion for Cell

Number of PS RAB Abnormal Releases due to other cause
Analysis
Uplink synchronization failure causes abnormal release of links. The coverage quality (including missing
neighbor cell and over small handover area) is bad, so the UE powers off the transmitter abnormally or
uplink demodulation is asynchronous.
RNC delivers a message and waits for the response from a mobile phone, but timeout occurs. For example,
waiting for RB reconfiguration completion message times out and waiting for active set update completion
times out. This case is generally caused by poor coverage.

Downlink SRB reset causes release of links, because the coverage quality (including missing neighbor cell
and over mall handover area) is bad. Uplink RLC reset causes release of links, because the coverage
quality (including missing neighbor cell and over mall handover area) is bad.
Downlink interference usually refers to pilot pollution. When over three cells meets the handover
requirements in the coverage area, the active set replaces the best cell or the best cell changes due to
fluctuation of signals. When the comprehensive quality of active set is bad (CPICH Ec/Io changes around –
10 dB), handover failure usually causes SRB reset or TRB reset.
Uplink interference increases the UE downlink transmit power in connection mode, so the over high BLER
causes SRB reset, TRB reset, or call drop due to asynchronization. Uplink interference might be internal or
external. Most of scenario uplink interference is external.

The O&M tasks cause call drop.

High-priority preemption causes release of CS links. This kind of call drop occurs when the load and
resources are limited. Performing expansion depends on the times of occurrence.
The causes due to UTRAN in the cell lead to abnormal release of link. This corresponds to abnormal
process, so you must further analyze it based on CHR.
The RNC detects that AAL2 Path at CS lu interface is abnormal, so the system originates an abnormal
release. The problem might be due to abnormal transport equipment. Immediate normal release during RB
establishment is counted by statistics as abnormal release as the cause.

Abnormal call drop can neither be located from coverage and interference nor be explained by TRB reset or
SRB reset. It is caused by abnormal equipment or UE. For example, it might be caused by the following
factors:
 Abrupt transmission failure
 Abnormal NodeB equipment
 Abrupt breakdown of UE
Analyze abnormal transmission by analyzing CHR or checking alarms. Confirm that the NodeB equipment
is abnormal by querying NodeB state. Locate abnormal UE problems by analyzing data recorded by UE.

Uplink synchronization failure causes abnormal release of links. The coverage quality (including missing
neighbor cell and over mall handover area) is bad, so the UE powers off the transmitter abnormally or uplink
demodulation is asynchronous.
RNC delivers a message and waits for the response from a mobile phone, but timeout occurs. For example,
waiting for RB reconfiguration completion message times out and waiting for active set update completion
times out. This case is generally caused by poor coverage.
The call drop due to SRB reset is that the UE or RNC fails to receive signaling transmitted in confirmation
mode, and consequently SRT reset occurs, so the connection is released. SRB reset occurs probably if the
UE fails to receive the following messages in downlink:
 Security mode process
 Authentication and encryption process
 Measurement control
 Active set update
 Physical channel reconfiguration
 Transport channel reconfiguration
 RB reset
 Handover command from 3G to 2G (HANDOVER FROM UTRAN COMMAND)
Confirm that the UE receives these messages by tracing messages at UE side.
SRB reset occurs probably if the UE fails to receive the following messages in uplink:
 Measurement report
 Active set update complete
 Physical channel reconfiguration complete
 Transport channel reconfiguration complete
 RB reconfiguration complete
Confirm that the UE receives these messages by tracing messaged at RNC side.

TRB reset usually occurs in PS services. It seldom occurs in voice and VP services. Confirm TRB reset by
the UE transmit power upon call drop and downlink code transmit power.
When only one link exists in active set, uplink asynchronization causes RL failure which consequently
causes lu release originated by RNC. Downlink asynchronization causes UE to power off transmitter, which
consequently causes uplink asynchronization. To judge whether uplink asynchronization or downlink
asynchronization causes release, you must analyze the UE transmit power before call drop and downlink
code transmit power monitored in realtime state.
Weak downlink coverage, strong downlink interference or uplink interference causes TRB reset. If the
retransmission times of data services are improperly configured, TRB reset occurs before SRB reset upon
delayed handover

The O&M tasks cause call drop.

High-priority preemption causes release of CS links. This kind of call drop occurs when the load and
resources are limited. Performing expansion depends on the times of occurrence.
The RNC detects the GTPU at PS lu interface is abnormal, so the system originates an abnormal release.
The problem is due to equipment failure.
Counter Level 1 Sub Counter Level 2

VS.RRC.FailConnEstab.Cong
VS.RRC.Rej.Sum (Number of RRC Connection Rejects Due to
(Number of RRC Connection Rejects for Network Congestion for Cell)
Cell)

VS.RRC.Rej.RL.Fail
VS.RRC.Rej.TNL.Fail
VS.RRC.FailConnEstab.NoReply
VS.RRC.Rej.Redir.IntraRat
VS.RRC.Rej.Redir.InterRat
VS.RRC.Rej.Redir.Service
VS.RRC.Rej.Redir.Dist

Counter Level 1 Sub Counter Level 2

VS.RAB.FailEstabCS.Unsp
Number of Failed CS RAB Establishments
for Cell (Unsupported Capabilities)
VS.RAB.FailEstabCS.RNL
Number of Failed CS RAB
Establishments for Cell (Radio Network
Layer Cause)
VS.RAB.FailEstabCS.UuFail
Number of Failed CS RAB Establishments
for Cell (Radio Network Layer Cause)

VS.RAB.FailEstabCS.IubFail
VS.RAB.FailEstabCS.RNL.Other
VS.RAB.FailEstabCS.TNL
VS.RAB.FailEstabCS.other.CELL

Counter Level 1 Sub Counter Level 2

VS.RAB.FailEstabPS.Unsp
Number of Failed PS RAB Establishments
for Cell (Unsupported Capabilities)
VS.RAB.FailEstabPS.RNL
Number of Failed PS RAB
Establishments for Cell (Radio Network
Layer Cause)
VS.RAB.FailEstabPS.UuFail
Number of Failed PS RAB Establishments
for Cell (Radio Network Layer Cause)

VS.RAB.FailEstabPS.IubFail
VS.RAB.FailEstabPS.RNL.Other
VS.RAB.FailEstabPS.TNL
VS.RAB.FailEstabPS.other.CELL
Sub Counter Level 3
VS.RRC.Rej.ULPower.Cong
VS.RRC.Rej.DLPower.Cong
VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.Rej.DLIUBBand.Cong
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong
VS.RRC.Rej.Other.Cong

Sub Counter Level 3 Sub Counter Level 4

VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabCS.Cong VS.RAB.FailEstabCS.ULCE.Cong
Number of Failed CS RAB VS.RAB.FailEstabCS.DLCE.Cong
Establishments for Cell (Congestion) VS.RAB.FailEstabCS.Code.Cong
VS.RAB.FailEstabCS.ULPower.Cong
VS.RAB.FailEstabCS.DLPower.Cong
VS.RAB.FailEstabCS.Unsp.Other
VS.RAB.FailEstabCS.RBIncCfg
VS.RAB.FailEstabCS.RBCfgUnsup
VS.RAB.FailEstabCS.UuNoReply
VS.RAB.FailEstabCS.PhyChFail

Sub Counter Level 3 Sub Counter Level 4

VS.RAB.FailEstabPS.DLIUBBand.Cong
VS.RAB.FailEstabPS.ULIUBBand.Cong
VS.RAB.FailEstabPS.Cong VS.RAB.FailEstabPS.ULCE.Cong
Number of Failed PS RAB VS.RAB.FailEstabPS.DLCE.Cong
Establishments for Cell (Congestion) VS.RAB.FailEstabPS.Code.Cong
VS.RAB.FailEstabPS.ULPower.Cong
VS.RAB.FailEstabPS.DLPower.Cong
VS.RAB.FailEstabPS.Unsp.Other
VS.RAB.FailEstabPS.RBIncCfg
VS.RAB.FailEstabPS.RBCfgUnsup
VS.RAB.FailEstabPS.UuNoReply
VS.RAB.FailEstabPS.PhyChFail
Description
Number of RRC Connection Rejects for Cell (UL Power Congestion)
Number of RRC Connection Rejects for Cell (DL Power Congestion)
Number of RRC Connection Rejects for Cell (UL Iub Bandwidth Congestion)
Number of RRC Connection Rejects for Cell (DL Iub Bandwidth Congestion)
Number of RRC Connection Rejects for Cell (UL CE Resource Congestion)
Number of RRC Connection Rejects for Cell (DL CE Resource Congestion)
Number of RRC Connection Rejects for Cell (Code Resource Congestion)
Number of RRC Connection Rejects due to other reason
Number of RRC Connection Rejects Due to Radio Link Setup Failure for Cell
Number of RRC Connection Rejects for Cell (Transmission Setup Failure on Iub Interface )
Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE for Cell
Number of RRC Connection Rejects during redirection between inter-frequency cells for cell
Number of RRC Connection Rejects during redirection between inter-RAT cells for cell
Number of RRC Connection Rejects Due to Service-based RRC Redirection for Cell
Number of Distance-Based RRC Redirections for Cell

Description
Number of Failed CS RAB Establishments for Cell (DL Iub Bandwidth Congestion)
Number of Failed CS RAB Establishments for Cell (UL Iub Bandwidth Congestion)
Number of Failed CS RAB Establishments for Cell (UL CE Congestion)
Number of Failed CS RAB Establishments for Cell (DL CE Congestion)
Number of Failed CS RAB Establishments for Cell (Code Congestion)
Number of Failed CS RAB Establishments for Cell (UL Power Congestion)
Number of Failed CS RAB Establishments for Cell (DL Power Congestion)
Number of Failed CS RAB Establishments for Cell due to other cause of insufficient capability of UTRAN
Number of Failed CS RAB Establishments for Cell(Invalid configuration of UE during the RB setup procedure)
Number of Failed CS RAB Establishments for Cell(Configuration unsupported of UE during the RB setup procedure)
Number of Failed CS RAB Establishments for Cell(No reply of UE during the RB setup procedure)
Number of Failed CS RAB Establishments for Cell(Physical channel failure of UE during the RB setup procedure)
Number of Failed CS RAB Establishments for cell (Radio Link Configuration Failure)
Number of Failed CS RAB Establishments for Cell due to other cause of Radio Network Layer
Number of Failed CS RAB Establishments for Cell (Transport Network Layer Cause
Number of Failed CS RAB Establishments for Cell due to other cause

Description
Number of Failed PS RAB Establishments for Cell (DL Iub Bandwidth Congestion)
Number of Failed PS RAB Establishments for Cell (UL Iub Bandwidth Congestion)
Number of Failed PS RAB Establishments for Cell (UL CE Congestion)
Number of Failed PS RAB Establishments for Cell (DL CE Congestion)
Number of Failed PS RAB Establishments for Cell (Code Congestion)
Number of Failed PS RAB Establishments for Cell (UL Power Congestion)
Number of Failed PS RAB Establishments for Cell (DL Power Congestion)
Number of Failed PS RAB Establishments for Cell due to other cause of insufficient capability of UTRAN
Number of Failed PS RAB Establishments for Cell(Invalid configuration of UE during the RB setup procedure)
Number of Failed PS RAB Establishments for Cell(Configuration unsupported of UE during the RB setup procedure)
Number of Failed PS RAB Establishments for Cell(No reply of UE during the RB setup procedure)
Number of Failed PS RAB Establishments for Cell(Physical channel failure of UE during the RB setup procedure)
Number of Failed PS RAB Establishments for cell (Radio Link Configuration Failure)
Number of Failed PS RAB Establishments for Cell due to other cause of Radio Network Layer
Number of Failed PS RAB Establishments for Cell (Transport Network Layer Cause
Number of Failed PS RAB Establishments for Cell due to other cause
Analysis
RRM admission decision cannot establish any new RRC connection due to too high radio load within a cell. In this case, you need to query the maximum RTWP

Transmission congestion is mainly caused by insufficient transmission resource. You may query the downlink cell throughput from associated traffic statistics ind

Uplink CE resource admission congestion within an RNC. You need to query the number of uplink CEs of a cell from relevant parameters and judge whether to
Downlink CE resource admission congestion within an RNC. You need to query the number of downlink CEs of a cell from relevant parameters and judge wheth
Code resource fails to be allocated during RRC connection establishment. Code congestion is generally caused by too many network users. It may be seen in h
RRC setup reject due to SPU overload and other reason.
It may be caused by NodeB fault or insufficient NodeB resource. You may query the maximum downlink CE of a cell from associated traffic statistics index. If the
Generally transmission equipment fault or insufficient transmission capacity. You need to query the transmission utilization of that time.
Generally poor coverage makes UE unable to receive any RB establishment command.
After the UE sends the RRC connection setup request message, the redirection algorithm is triggered if the cell is congestion or assigning resources (mainly the

Analysis
Transmission congestion is mainly caused by insufficient transmission resource. You may query the downlink cell thr

Uplink CE resource admission congestion within an RNC. You need to query the number of uplink CEs of a cell from relevant parameters and judge whether to
Downlink CE resource admission congestion within an RNC. You need to query the number of downlink CEs of a cell from relevant parameters and judge wheth
Code resource fails to be allocated during RRC connection establishment. Code congestion is generally caused by too many network users. It may be seen in h

RRM admission decision cannot establish any new RRC connection due to too high radio load within a cell. In
Because VS.RAB.FailEstPS.Unsp includes all kinds of insufficient capability of UTRAN, HSDPA User License congestion is one kind of insufficient capability.
If the sum of 6 sub counters much less than VS.RAB.FailEstPS.Unsp, maybe the HSDPA User License is not enough
UE considers parameter configuration illegal. Network and terminals have an inconsistent understanding of parameter processing. If RB establishment failure oc
The compatibility of a mobile phone itself becomes faulty in some unknown scenarios. For example, when a Huawei mobile phone droCS network abnormally, it
Generally poor coverage makes UE unable to receive any RB establishment command.
This generally occurs when FACH migrates to DCH and sets up RB. The downlink physical layer of a terminal is not synchronized, which leads to RB establishm
 RRC connection setup rejection due to RL setup failure
 RRC connection setup rejection due to AAL2 setup failure

Generally transmission equipment fault or insufficient transmission capacity. You need to query the transmission utilization of that time.

Analysis
Transmission congestion is mainly caused by insufficient transmission resource. You may query the downlink cell thr

Uplink CE resource admission congestion within an RNC. You need to query the number of uplink CEs of a cell from relevant parameters and judge whether to
Downlink CE resource admission congestion within an RNC. You need to query the number of downlink CEs of a cell from relevant parameters and judge wheth
Code resource fails to be allocated during RRC connection establishment. Code congestion is generally caused by too many network users. It may be seen in h

RRM admission decision cannot establish any new RRC connection due to too high radio load within a cell. In
Because VS.RAB.FailEstPS.Unsp includes all kinds of insufficient capability of UTRAN, HSDPA User License congestion is one kind of insufficient capability.
If the sum of 6 sub counters much less than VS.RAB.FailEstPS.Unsp, maybe the HSDPA User License is not enough
UE considers parameter configuration illegal. Network and terminals have an inconsistent understanding of parameter processing. If RB establishment failure oc
The compatibility of a mobile phone itself becomes faulty in some unknown scenarios. For example, when a Huawei mobile phone droPS network abnormally, it
Generally poor coverage makes UE unable to receive any RB establishment command.
This generally occurs when FACH migrates to DCH and sets up RB. The downlink physical layer of a terminal is not synchronized, which leads to RB establishm
 RRC connection setup rejection due to RL setup failure
 RRC connection setup rejection due to AAL2 setup failure
Generally transmission equipment fault or insufficient transmission capacity. You need to query the transmission utilization of that time.
 in a cell. In this case, you need to query the maximum RTWP and the maximum TCP of the cell to confirm uplink congestion or downlink congestion and judge whether any exp

e downlink cell throughput from associated traffic statistics indexes. If the downlink cell throughput is lower than 200 kbps, it is possible that there is abnormal equipment. The p

CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 20, then traffic is not high and the problem may lie in abnorma
wnlink CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 40, traffic is not high and the problem may lie in abnorm
erally caused by too many network users. It may be seen in high traffic scenarios with microcell coverage. You may query the effective utilization of codes from associated traffi

wnlink CE of a cell from associated traffic statistics index. If the maximum uplink CE is less than 20, then traffic is not high and the problem lies in abnormal NodeB equipment.
transmission utilization of that time.

ed if the cell is congestion or assigning resources (mainly the admission and code resource assignment) fails, and the entire RRC direct retrial algorithms fail. If the serving cell

CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 20, then traffic is not high and the problem may lie in abnorma
wnlink CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 40, traffic is not high and the problem may lie in abnorm
erally caused by too many network users. It may be seen in high traffic scenarios with microcell coverage. You may query the effective utilization of codes from associated traffi

ser License congestion is one kind of insufficient capability.

ense is not enough
anding of parameter processing. If RB establishment failure occurs in the domain of CS, it is possible that a user dials a wrong telephone number and at once goes onhook. RB
e, when a Huawei mobile phone droCS network abnormally, it may not release any RB. When CS RB is set up next time, this case may occur. This case also happens to the SE

f a terminal is not synchronized, which leads to RB establishment failure. This is mainly caused by poor coverage.

transmission utilization of that time.

CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 20, then traffic is not high and the problem may lie in abnorma
wnlink CEs of a cell from relevant parameters and judge whether to expand CE. If the number of uplink CEs is less than 40, traffic is not high and the problem may lie in abnorm
erally caused by too many network users. It may be seen in high traffic scenarios with microcell coverage. You may query the effective utilization of codes from associated traffi

ser License congestion is one kind of insufficient capability.

ense is not enough
anding of parameter processing. If RB establishment failure occurs in the domain of PS, it is possible that a user dials a wrong telephone number and at once goes onhook. RB
e, when a Huawei mobile phone droPS network abnormally, it may not release any RB. When PS RB is set up next time, this case may occur. This case also happens to the SE

f a terminal is not synchronized, which leads to RB establishment failure. This is mainly caused by poor coverage.

transmission utilization of that time.

congestion or downlink congestion and judge whether any expansion is necessary. Meanwhile, we should check whether related admission strategy settings, such as DCCC, a

00 kbps, it is possible that there is abnormal equipment. The power-down of a base station once led to transmission interruption, but the cause in traffic statistics is transmission

20, then traffic is not high and the problem may lie in abnormal NodeB equipment.
than 40, traffic is not high and the problem may lie in abnormal NodeB equipment.
y query the effective utilization of codes from associated traffic statistics indexes. If the effective utilization of codes is lower than 30%, it is possible that the code distribution alg

ot high and the problem lies in abnormal NodeB equipment.

d the entire RRC direct retrial algorithms fail. If the serving cell of originating UE has inter-frequency neighbor cell or GSM cell, the UE is indicated by the IE Redirection info of R

20, then traffic is not high and the problem may lie in abnormal NodeB equipment.
than 40, traffic is not high and the problem may lie in abnormal NodeB equipment.
y query the effective utilization of codes from associated traffic statistics indexes. If the effective utilization of codes is lower than 30%, it is possible that the code distribution alg

als a wrong telephone number and at once goes onhook. RB SETUP failure may also occur at this time. The cause is illegal configuration.
t time, this case may occur. This case also happens to the SE V800 mobile phone.

20, then traffic is not high and the problem may lie in abnormal NodeB equipment.
than 40, traffic is not high and the problem may lie in abnormal NodeB equipment.
y query the effective utilization of codes from associated traffic statistiPS indexes. If the effective utilization of codes is lower than 30%, it is possible that the code distribution al

als a wrong telephone number and at once goes onhook. RB SETUP failure may also occur at this time. The cause is illegal configuration.
t time, this case may occur. This case also happens to the SE V800 mobile phone.
whether related admission strategy settings, such as DCCC, are proper.

n interruption, but the cause in traffic statistics is transmission congestion.

s is lower than 30%, it is possible that the code distribution algorithm is abnormal.

r GSM cell, the UE is indicated by the IE Redirection info of RRC connection reject message to redirection to the frequency point of inter-frequency neighbor cell or GSM cell. If

s is lower than 30%, it is possible that the code distribution algorithm is abnormal.

e is illegal configuration.

es is lower than 30%, it is possible that the code distribution algorithm is abnormal.

e is illegal configuration.
requency point of inter-frequency neighbor cell or GSM cell. If there is no inter-frequency neighbor cell or GSM cell, the IE Redirection info of RRC connection reject message is
l, the IE Redirection info of RRC connection reject message is not configured
Counter Description
VS.SHO.FailRLAdd.CfgUnsupp Number of Failed Radio Link Additions in Soft Handover for Cell
(Configuration Unsupported)
VS.SHO.FailRLAdd.ISR Number of Failed Radio Link Additions in Soft Handover for Cell
(Incompatible Simultaneous Reconfiguration)
VS.SHO.FailRLAdd.InvCfg Number of Failed Radio Link Additions in Soft Handover for Cell
(Invalid Configuration)
VS.SHO.FailRLAdd.NoReply Number of Failed Radio Link Additions in Soft Handover due to UE
No Response for Cell
Analysis
UE considers that the content of the active set update of RNC adding/deleting a link is not supported. Generally, this scenario w

UE considers that the content of the active set update of RNC adding/deleting a link is illegal. Generally, this scenario will not a

RNC does not receive the active set update command response for adding/deleting a link. This is the main cause of softer/soft
t supported. Generally, this scenario will not appear in commercial use.

gal. Generally, this scenario will not appear in commercial use

. This is the main cause of softer/soft handover failure. This happens in the region with poor coverage or a small handover area. It needs R
e or a small handover area. It needs RF optimization.
IRATHO CS Failure Counter
IRATHO.FailRelocPrepOutCS.TAlExp

IRATHO.FailRelocPrepOutCS.TgtFail

IRATHO.FailRelocPrepOutCS.ReloNoSup
IRATHO CS Failure during
Relocation Preparation
IRATHO.FailRelocPrepOutCS.HigherTrafficLod

IRATHO.FailRelocPrepOutCS.NoResAvail

IRATHO.FailRelocPrepOutCS.UKnowRNC

IRATHO.FailOutCS.CfgUnsupp
IRATHO CS Failure after
Relocation Preparation IRATHO.FailOutCS.PhyChFail
VS.IRATHO.FailOutCS.Other

IRATHO PS Failure Counter

VS.IRATHO.FailRelocPrepOutPS.TAlExp

VS.IRATHO.FailRelocPrepOutPS.TgtFail

VS.IRATHO.FailRelocPrepOutPS.ReloUnSupp
IRATHO PS Failure during
Relocation Preparation
VS.IRATHO.FailRelocPrepOutPS.TgtHighLoad

VS.IRATHO.FailRelocPrepOutPS.NoResAvail

VS.IRATHO.FailRelocPrepOutPS.UnKnowRNC

IRATHO.FailOutPSUTRAN.CfgUnsupp
IRATHO PS Failure after
Relocation Preparation IRATHO.FailOutPSUTRAN.PhyChFail
VS.IRATHO.FailOutPS.Other
Description Analysis
Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell
The problem often lies in CN parameter configuration or a related link conne
(TRELOCalloc expiry)
Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell
It generally corresponds to core network configuration er
(Relocation Failure in Target CN/RNC or Target System)
Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell
Generally, RNC does not support some hard handover parameters. We nee
(Relocation not supported in Target RNC or Target system)
Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell
(Traffic Load In The Target Cell Higher Than In The Source Cell)
Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (No
The problem often lies in an MSC parameter configuratio
Resource Available)
Number of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell
The problem often lies in an MSC parameter configuration error. That is, the
(Unknown Target RNC)
Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Configuration
UE considers that the command for hard handover out of a cell is not suppo
Unsupported)
Number of Failed CS Outgoing Inter-RAT Handovers for Cell (Physical Channel
Possibly poor coverage or severe interference
Failure)
Number of Failed CS Outgoing Inter-RAT Handovers for Cell (other cause)

Description Analysis
Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for
The problem often lies in CN parameter configuration or a related link conne
Cell (TRELOCalloc expiry)
Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for
It generally corresponds to core network configuration error.
Cell (Relocation Failure in Target CN/RNC or Target System)

Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for

Generally, RNC does not support some hard handover parameters. We nee
Cell (Relocation not supported in Target RNC or Target system)

Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for

Cell (Traffic Load In The Target Cell Higher Than In The Source Cell)

Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for

The problem often lies in an MSC parameter configuration error, or BSC ha
Cell (No Resource Available)
Number of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for
The problem often lies in an MSC parameter configuration error. That is, the
Cell (Unknown Target RNC)
Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC
UE considers that the command for hard handover out of a cell is not suppo
(Configuration unsupported)
Number of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Physical
Possibly poor coverage or severe interference
Channel Failure)
Number of Failed PS Outgoing Inter-RAT Handovers for Cell (other cause)
 Solution
onfiguration or a related link connection. We need to make an analysis based on RNC logs.

Check AMR definition in 2G MSC, usually occurred in multi vendor network

ard handover parameters. We need to make an analysis based on RNC logs.

2G database inconsistence(LAC, CI)

2G Site High TCH Blocking
Beside that, we need do neighbor audit, remove some neighbor with high TCH congestion(or make it difficult handover to this site)
eter configuration error. That is, the LAC of the target cell fails to be configured. We need to check the parameter configuration of a core network. This case is often seen after th

handover out of a cell is not supported. The problem generally lies in the compatibility of a mobile phone.
2G database inconsistence(BCCH)
2G site has a TRX hardware alarm

onfiguration or a related link connection. We need to make an analysis based on RNC logs.

configuration error.

ard handover parameters. We need to make an analysis based on RNC logs.

eter configuration error, or BSC has no resource available. We need to analyze the cause according to the signaling tracing of a core network and a BSS.

eter configuration error. That is, the LAC of the target cell fails to be configured. We need to check the parameter configuration of a core network. This case is often seen after th

handover out of a cell is not supported. The problem generally lies in the compatibility of a mobile phone.
make it difficult handover to this site)
configuration of a core network. This case is often seen after the adjustment of 2 G network.

ng tracing of a core network and a BSS.

configuration of a core network. This case is often seen after the adjustment of 2 G network.