Counter

VS.RRC.Rej.Redir.Inter.Att
VS.RRC.Reject.Redir.Intrat
VS.RRC.Reject.Redir.Service

RRC Setup Fail

RRC Setup Reject.
RRC REQ CELL RESEL
RRC REQ REG

RRC setup reject

RRC setup reject

RRC setup reject

RRC setup reject
RRC setup reject
RRC setup reject
RRC setup reject
RRC setup reject
RRC setup reject
 Description
Number of RRC redirections in a cell with different frequencies.
Number of RRC redirections in a cell with different systems.
Number of RRC Connection Reject due to Service Based Redirection.

Downlink FACH and RACH are covered unevenly.

If network coverage is poor, inter-system reselection may occur.

no of attempts to register

Admission reject due to crowded subscribers

Access failure due to equipment faults

Power Congestion. Check RTWP and the maximum TCP.check power threshold, interference,netwrok capacity
CE Congestion
RL Fail.NodeB fails or NodeB resource is insufficient.
AAL2 Fail.transmission resource is insufficient or any transmission equipment is faulty,
FP Fail. If the transmission fails or an equipment is faulty, FP synchronization may fail. To locate the problem, check whether t
Code Congestion.To locate the problem, start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm m
Other,analyze call detail logs.
ce,netwrok capacity

ocate the problem, check whether there is any BTS alarm.

e the code allocation and confirm major services.
 Counter
RRC.AttConnEstab.OrgConvCall
RRC.AttConnEstab.OrgStrCall
RRC.AttConnEstab.OrgInterCall
RRC.AttConnEstab.OrgBkgCall
RRC.AttConnEstab.OgSubCall
RRC.AttConnEstab.TmConvCall
RRC.AttConnEstab.TmStrCall
RRC.AttConnEstab.TmInterCall
RRC.AttConnEstab.TmBkgCall
RRC.AttConnEstab.EmgCall
RRC.AttConnEstab.IRATCelRes
RRC.AttConnEstab.IRATCCO
RRC.AttConnEstab.Reg
RRC.AttConnEstab.Detach
RRC.AttConnEstab.OgHhPrSig
RRC.AttConnEstab.OgLwPrSig
RRC.AttConnEstab.CallReEst
RRC.AttConnEstab.TmHhPrSig
RRC.AttConnEstab.TmLwPrSig
RRC.AttConnEstab.Unknown
RRC.AttConnEstab.MBMSRep
RRC.AttConnEstab.MBMSPtp
Description
Originating Conversational Call
Originating Streaming Call
Originating Interactive Call
Originating Background Call
Originating Subscribed traffic Call
Terminating Conversational Call
Terminating Streaming Call
Terminating Interactive Call
Terminating Background Call
Emergency Call
Inter-RAT cell re-selection
Inter-RAT cell change order
Registration
Detach
Originating High Priority Signalling
Originating Low Priority Signalling
Call re-establishment
Terminating High Priority Signalling
Terminating Low Priority Signalling
Terminating - cause unknown
MBMS Reception
MBMS PTP RB Request
 Counter
RRC.AttConnRelDCCH.NormRel
RRC.AttConnRelDCCH.Congestion
RRC.AttConnRelDCCH.Preempt
RRC.AttConnRelDCCH.ReEstRej
RRC.AttConnRelDCCH.SigConReEst
RRC.AttConnRelDCCH.UsrInact
RRC.AttConnRelDCCH.Unspec
 Description
Number of RRC connection releases on the dedicated control channel for a normal event.
Number of RRC connection releases on the dedicated control channel for congestion.
Number of RRC connection releases on the dedicated control channel for pre-emptive release.
Number of RRC connection releases on the dedicated control channel for re-establishment reject.
Number of RRC connection releases on the dedicated control channel for directed signaling connection re-establishment.
Number of RRC connection releases on the dedicated control channel for user inactivity.
Number of RRC connection releases on the dedicated control channel for unspecified causes.
n re-establishment.
 qwa Description
VS.FailRBSetup.CfgUnsup Configuration unsupported
VS.FailRBSetup.PhyChFail Physical channel failure
VS.FailRBSetup.CellUpd Cell update occurred
VS.FailRBSetup.IncCfg Invalid configuration
VS.FailRBSetup.NoReply No reply

CS RAB setup failures PARAM_CELL. RNC regards the parameters transmitted by core network as invalid parameters.
CS RAB setup failures RELOC_CELL,relatedto migration
CS RAB setup failures TNL_CELL.IU transmission setup fails.
CS RAB setup failures CONG_CELL.RNC resource allocation failure.
CS RAB setup failures POWER_CONG_CELL
CS RAB setup failures CE_CONG_CELL
CS RAB setup failures CODE_CONG_CELL
CS RAB setup failures OTHER_CELL
CS RAB setup failures UNSUP_CELL.the QoS is not supported by RNC or RRM admission fails in RAB.

CFG_UNSUPP UE acknowledges the RB setup failure because of configuration unsupported compatibility prob
PHYCH_FAIL The RB setup failure may occur if FACH is migrated to DCH but downlink physical layers are not
SIMU_RECFG_INCOMP UE regards that the RB setup process and other processes simultaneously occur and they are in
CELL_UPDT the Cell Update process occurs. The RB setup failure is caused by process nesting
CFG_INVALID UE regards the configured parameters are invalid ones
NO_RESPONSE UE does not acknowledge the RB setup request. This reason frequently occurs. It is mainly caus
OTHER

lParameter violation
lNon supported UTRAN capabilities

lRelocation triggered

lTransport connection failed to establish

lUnavailable resources

lProtocol error
 twork as invalid parameters.

supported compatibility problem of UE in some unknown scenarios

wnlink physical layers are not synchronized during the RB setup process. The rooted reason is poor coverage
neously occur and they are incompatible.It is mainly caused by UE defects
process nesting

ently occurs. It is mainly caused by poor coverage, so UE cannot receive the RB setup request message
 Counter
VS.RAB.RelReqCS.OM
VS.RAB.RelReqCS.RABPreempt
VS.RAB.RelReqCS.UTRANgen
VS.RAB.RelReqPS.OM
VS.RAB.RelReqPS.RABPreempt

Call Drop Rate of Signaling Plane

lOM intervention
lUser inactivity
lRepeated integrity checking failure
lUE generated signaling connection release
lRL out-of-synchronization

Call Drop Rate of User Plane

lOM intervention
lUTRAN generated reason
lRAB preempted
 Description
Number of released CS RABs triggered by the RNC in the best cell with the cause of "O&M Intervention"
Number of released CS RABs triggered by the RNC in the best cell with the cause of "RAB pre-empted"
Number of released CS RABs triggered by the RNC in the best cell with the cause of "Release due to UTRAN Generated Reason
Number of released PS RABs triggered by the RNC in the best cell with the cause of "O&M Intervention"
Number of released PS RABs triggered by the RNC in the best cell with the cause of "RAB pre-empted"

gnaling Plane

ted integrity checking failure

nerated signaling connection release
-of-synchronization

N generated reason
TRAN Generated Reason"
 Counter
VS.RAB.AttRelCS.NetOpt
VS.RAB.AttRelCS.NormRel
VS.RAB.AttRelCS.OM
VS.RAB.AttRelCS.Preempt
VS.RAB.AttRelCS.UEInact
VS.RAB.AttRelCS.UTRANGen

VS.Norm.Rel.CS.AMR.UlSigRel
VS.Norm.Rel.CS.AMR.UlSigRel

RAB_CS_REL_RF_LOSS
RNC_CS_RAB_REL_TRIG_BY_RNC_SRB_RESET
RNC_CS_RAB_REL_TRIG_BY_RNC_AAL2_LOSS
CS_RAB_DROP_OTHER

RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESET
RNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSS
PS_RAB_DROP_OTHER
 Description
Number of CS RABs requested to release in the best cell for network optimization
Number of CS RABs requested to release in the best cell for normal release
Number of CS RABs requested to release in the best cell for O&M intervention
Number of CS RABs requested to release in the best cell for RAB preempted
Number of CS RABs requested to release in the best cell for user inactivity
Number of CS RABs requested to release in the best cell for release caused by the UTRAN

Number of released CS AMR RABs due to uplink signaling connection release in the best cell
Number of released CS RABs triggered by the RNC due to CELL congestion

CS call drop may be caused by abnormal release caused by the lost synchronization of links because of poor network coverag
CS call drops may be caused by link releasing due to downlink SRB reset. This reason is mainly caused by poor network covera
If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occ
CS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process

PS call drops may be caused by link releasing due to downlink TRB reset. This reason is mainly caused by poor network covera
If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occ
PS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process i
 because of poor network coverage (including adjacent cell missing, small handover area. As a result, UE closes the transmitter abnormall
nly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network covera
n seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment. In some versions of RNC, norma
sion 12). Such reasons as process interaction timeout and cell update failure are recorded in CS_RAB_DROP_OTHER. In practice, many ca

nly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network covera
n seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment.
sion 12). Such reasons as process interaction timeout and cell update failure are recorded in PS_RAB_DROP_OTHER. In practice, many cal
 closes the transmitter abnormally or uplink demodulation is asynchronous. To solve the problem, network coverage must be improved.
e the problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.
. In some versions of RNC, normal release is recorded as abnormal release during the RB setup process.
ROP_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are

e the problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.

ROP_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are
ork coverage must be improved. In the early network, call drops are mainly caused by this reason.
ed by this reason.

ure. Therefore, these call drops are recorded in CS_RAB_DROP_OTHER.

ed by this reason.

ure. Therefore, these call drops are recorded in PS_RAB_DROP_OTHER.

 Counter
VS.RAB.Loss.CS.RF
VS.RAB.Loss.CS.RF.RLCRst
VS.RAB.Loss.CS.RF.ULSync
VS.RAB.Loss.CS.RF.UuNoReply
VS.RAB.Loss.CS.RF.Oth
 Description
Number of CS domain RABs released due to RF failures in the best cell
Number of CS domain RABs released RF failures (RLC reset) in the best cell
Number of CS domain RABs released due to RF failures (Uplink Synchronization Fail) in the best cell
Number of the CS domain RABs released due to RF failures (Failure in the Radio Interface Procedure) in the best cell
Number of the CS domain RABs released due to RF failures (other cause) in the best cell
n the best cell
 Counter
VS.RAB.RelReqCS.OM
VS.RAB.RelReqCS.RABPreempt
VS.RAB.RelReqCS.UTRANgen
VS.RAB.RelReqPS.OM
VS.RAB.RelReqPS.RABPreempt
 Description
Number of released CS RABs triggered by the RNC in the best cell with the cause of "O&M Intervention"
Number of released CS RABs triggered by the RNC in the best cell with the cause of "RAB pre-empted"
Number of released CS RABs triggered by the RNC in the best cell with the cause of "Release due to UTRAN Generated Reason
Number of released PS RABs triggered by the RNC in the best cell with the cause of "O&M Intervention"
Number of released PS RABs triggered by the RNC in the best cell with the cause of "RAB pre-empted"
TRAN Generated Reason"
 Counter
VS.Norm.Rel.CS.AMR.UlSigRel
VS.Norm.Rel.CS.Conv.RB.64.UlSigRel
VS.Norm.Rel.PS.BE.RB.0.32.UlSigRel
VS.Norm.Rel.PS.BE.RB.32.64.UlSigRel
VS.Norm.Rel.PS.BE.RB.64.144.UlSigRel
VS.Norm.Rel.PS.BE.RB.144.384.UlSigRel
VS.Norm.Rel.PS.CCH.UlSigRel
VS.Norm.Rel.PS.HS.UlSigRel
VS.Norm.Rel.CS.Str.UlSigRel
VS.Norm.Rel.PS.Conv.UlSigRel
VS.Norm.Rel.PS.Str.UlSigRel
 Description
Number of released CS AMR RABs due to uplink signaling connection release in the best cell
Number of released CS conversational service RABs due to uplink signaling connection release in the best cell( max DL bit rate
Number of released PS BE service RABs due to uplink signaling connection release in the best cell (max DL bitrate in (0,32] kbi
Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (32,6
Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (64,1
Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (144
Number of released PS RABs with the cause of uplink signaling connection release in the best cell that belongs to the SRNC (R
Number of released PS RABs due to uplink signaling connection release in the best cell ( HS-DSCH user only)
Number of released CS streaming service RABs due to uplink signaling connection release in the best cell
Number of released PS conversational service RABs due to uplink signaling connection release in the best cell(R99 user only)
Number of released PS streaming service RABs due to uplink signaling connection release in the best cell(R99 user only)
 est cell( max DL bit rates is 64kbps)
x DL bitrate in (0,32] kbit/s, RRC state is CELL_DCH, R99 user only)
(max DL bit rate in (32,64] kbit/s, RRC state is CELL_DCH, R99 user only)
(max DL bit rate in (64,144] kbit/s, RRC state is CELL_DCH, R99 user only)
(max DL bit rate in (144,384] kbit/s, RRC state is CELL_DCH, R99 user only)
belongs to the SRNC (RRC state is CELL_FACH)

est cell(R99 user only)

ell(R99 user only)
SHO_PREP_RL_SETUP_FAIL
SHO_PREP_AAL2_SETUP_FAIL
SHO_PREP_FP_SYNC_FAIL
SHO_PREP_ FAIL_OTHER_CELL
SHO_RL_ADD_FAIL_CFG_UNSUPP
SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP
SHO_RL_ADD_FAIL_CFG_INVALID
SHO_RL_ADD_FAIL_NO_RSP
SHO_RL_DEL_FAIL_CFG_UNSUPP
SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP
SHO_RL_ADD_FAIL_CFG_INVALID
SHO_RL_ADD_FAIL_NO_RSP
SHO_FAIL_OTHER_CELL
NodeB CE resource is insufficient or NodeB is faulty.
AAL2 setup of lub interface fails because the transmission bandwidth is insuf
the synchronization of AAL2 and FP of lub interface fails
Soft handover prepare failure is caused by other reasons, such as insufficien
UE does not support to add radio links in RNC during the active set update. T
UE feeds back that the soft handover process is incompatible with other con
UE regards active set update of adding radio links in RNC as invalid configura
RNC does not receive the acknowledgement of active set update of adding r
UE does not support to delete radio links in RNC during the active set update
UE feeds back that the soft handover is incompatible with other concurrent
UE regards the active set update of deleting radio links in RNC as invalid con
RNC does not receive the acknowledgement of active set update of deleting
Soft handover failure is caused by other reasons;
nsmission bandwidth is insufficient.

reasons, such as insufficient RNC resource, radio resource admission reject, and RNC link state reject. To locate the problem, RNC logs mu

ring the active set update. This reason seldom exists in a commercial network.
ncompatible with other concurrent processes when radio links are added in RNC.The problem is mainly caused by some handsets.
s in RNC as invalid configuration.
ctive set update of adding radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover
during the active set update.
tible with other concurrent processes when radio links are deleted in RNC.The problem is mainly caused by some handsets.
o links in RNC as invalid configuration.
ctive set update of deleting radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handove
o locate the problem, RNC logs must be used for further analysis.

caused by some handsets.

overage is poor or soft handover area is small, soft handover failure easily occurs.

by some handsets.

coverage is poor or soft handover area is small, soft handover failure easily occurs.
CS_INTERRAT_HO_PREP_FAIL_TARGET_FAIL
CS_INTERRAT_HO_PREP_FAIL_TALLOC_EXPIR
CS_INTERRAT_HO_PREP_FAIL_TARGET_UNSUPP
CS_INTERRAT_HO_PREP_FAIL_RELOC_ABORT
CS_INTERRAT_HO_PREP_FAIL_NO_RSRC_AVAIL
CS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGET
CS_INTERRAT_HO_PREP_FAIL_ REQINFNOTAVAI
CS_INTERRAT_HO_PREP_FAIL_NO_RSP

CS_INTERRAT_HO_ FAIL_UNSPEC
CS_INTERRAT_HO_ FAIL_PHYCN_FAIL
CS_INTERRAT_HO_ FAIL_ CFG_UNSUPP
CS_INTERRAT_HO_ FAIL_ RELOC_ABORT
CS_INTERRAT_HO_ FAIL_NO_RSP
CS_INTERRAT_HO_ FAIL_OTHER
CS inter-RAT handover prepare failure is caused by Relocation Failure Target CN/RNC
CS inter-RAT handover prepare failure is caused by TRELOCalloc Expiry (cause value) because the data configuration or link co
CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) be
After sending the handover prepare request, RNC receives the release message from core network. This may be caused by tw
CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MS
CS inter-RAT handover prepare failure is caused by Unknown Target RNC (cause value) because the data configuration of MSC
CS inter-RAT handover prepare failure is caused by Requested Information Not Available because the data configuration is inc
CS inter-RAT handover prepare failure occurs because core network does not respond to the handover prepare request. This

CS inter-RAT handover failure is caused by Unspecified (cause value).

CS inter-RAT handover failure is caused by Physical Channel Failure (cause value). CS inter-RAT handover failure is mainly caus
CS inter-RAT handover failure is caused by Configuration Unsupported (cause value) because UE does not support the handov
After sending the handover request message to UE, RNC receives the release message from core network. However, the caus
After RNC sends the handover request message to UE, UE does not acknowledge the request because network coverage is po
CS inter-RAT handover failure is caused by other reasons. To locate the problem, analyze the RNC logs.
 data configuration or link connection of core network is incorrect. To locate the problem, track the signaling of core network and BSS for
rget System (cause value) because BSC does not support some parameters of handover requests. To locate the problem, track the signalin
k. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location update. Locati
he data configuration of MSC is incorrect or there is no available resource in BSC. To locate the problem, track the signaling of core netwo
he data configuration of MSC is incorrect or the LAC of target cell is not configured.
the data configuration is incorrect or target BSC does not support the handover.
dover prepare request. This may be caused by incorrect data configuration or link connection of core network.

ndover failure is mainly caused by:1) The signals of 2G network are weak or UE fails to access the network due to serious interference.2) S
does not support the handover request. This reason may be mainly caused by abnormal UE.
network. However, the cause is not Normal Release because the link is released abnormally due to other reasons.
ause network coverage is poor.
aling of core network and BSS for further analysis.
ate the problem, track the signaling of core network and BSS for further analysis.
es, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initia
, track the signaling of core network and BSS for further analysis.

rk due to serious interference.2) Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.
omplete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the call.

nsistent with that of BSC.

formed, an MS hangs up the call. Thus, core network initializes the release.
RTWP If the RTWP of a cell is greater than -100 dBm, the cell must be analyzed
TCP Transmitted carrier power.The cell that has the greatest TCP represents the cell that has the greatest downlink ra
DCH UE downlink admission rejects.The cell that has the greatest DCH UE is used to measure the subscriber number of a c
DL ADMSN DENY
The cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio loa
hat has the greatest downlink radio load. In practice, if the cell has the greatest downlink radio load, the cell also has the greatest downlin
ure the subscriber number of a cell. Combined with the utilization of OVSF codes, the average CE and transmission can be estimated to fur
s the greatest downlink radio load. In practice, downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and t
cell also has the greatest downlink admission rejects. For such cell, check whether the cross coverage is serious and check whether the in
nsmission can be estimated to further check whether the resources are sufficient.
asymmetric to the downlink and the downlink is of interference. If a cell has the greatest DL ADMSN DENY, check whether the cross cove
serious and check whether the indoor coverage of high traffic area must be improved to decrease large power consumption.

NY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be i
power consumption.

rage for high traffic area must be improved.

lConfiguration unsupported
lPhysical channel failure
lIncompatible simultaneous reconfiguration
lProtocol error
lCell update occurred
lInvalid configuration