DCRCounter Level 1Sub Counter Level 2Sub Counter Level 3DescriptionVS.RAB.AbnormRel.CS(Number of CS RABs Abnormally Released for Cell)VS.RAB.AbnormRel.CS.RF(Number of CS RABs Abnormally Released Due to RF for Cell)VS.RAB.AbnormRel.CS.RF.ULSyncNumber of CS RABs Abnormally Released Due to RF for Cell (Uplink Synchronization Fail)CS call drop may be caused by abnormal release caused by the lost synchronization of links because of poor network coverage (including adjacent cell missing, small handover area. As a result, UE closes the transmitter abnormally or uplink demodulation is asynchronous. To solve the problem, network coverage must be improved. In the early network, call drops are mainly caused by this reason.VS.RAB.AbnormRel.CS.RF.UuNoReplyNumber of CS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure)VS.RAB.AbnormRel.CS.RF.SRBResetNumber of CS RABs Abnormally Released for Cell (Signaling RLC Reset)CS call drops may be caused by link releasing due to downlink SRB reset. This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.VS.RAB.AbnormRel.CS.OMNumber of CS RAB Release Requests for Cell (O&M Intervention)VS.RAB.AbnormRel.CS.PreemptNumber of CS RAB Release Attempts for Cell (RAB Preemption)VS.RAB.AbnormRel.CS.UTRANgenNumber of CS RAB Abnormal Releases Triggered by RNC for Cell (UTRAN Cause)VS.RAB.AbnormRel.CS.IuAAL2Number of CS RABs Abnormally Released for Cell (Iu Interface AAL2 Link Failure)If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment. In some versions of RNC, normal release is recorded as abnormal release during the RB setup process.VS.RAB.AbnormRel.CS.OLCNumber of CS Domain RABs Released Due to Congestion for CellVS.Call.Drop.CS.OtherNumber of CS RAB Abnormal Releases due to other causeCS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process interaction timeout and cell update failure are recorded in CS_RAB_DROP_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are recorded in CS_RAB_DROP_OTHER.Counter Level 1Sub Counter Level 2Sub Counter Level 3DescriptionVS.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.RF.ULSyncNumber of PS RABs Abnormally Released for Cell (Uplink Synchronization Failure)VS.RAB.AbnormRel.PS.RF.UuNoReplyNumber of PS RABs Abnormally Released Due to RF for Cell (Failure in the Radio Interface Procedure)VS.RAB.AbnormRel.PS.RF.SRBResetNumber of PS RABs Abnormally Released Due to Signaling RLC Reset for CellVS.RAB.AbnormRel.PS.RF.TRBResetNumber of PS RABs Abnormally Released for Cell (Traffic RLC Reset)PS call drops may be caused by link releasing due to downlink TRB reset. This reason is mainly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.VS.RAB.AbnormRel.PS.OMNumber of PS RAB Abnormal Released Due to O&M Intervention for CellVS.RAB.AbnormRel.PS.PreemptNumber of PS RAB Abnormal Released Due to RAB Preemption for CellVS.RAB.AbnormRel.PS.GTPULossNumber of PS RABs Abnormally Released Due to GTPU Failure for CellIf IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment.VS.RAB.AbnormRel.PS.OLCNumber of PS Domain RABs Released Due to Congestion for CellVS.Call.Drop.PS.OtherNumber of PS RAB Abnormal Releases due to other causePS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process interaction timeout and cell update failure are recorded in PS_RAB_DROP_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are recorded in PS_RAB_DROP_OTHER.

CSSRCounter Level 1Sub Counter Level 2Sub Counter Level 3DescriptionVS.RRC.Rej.Sum(Number of RRC Connection Rejects for Cell)VS.RRC.FailConnEstab.Cong(Number of RRC Connection Rejects Due to Network Congestion for Cell)VS.RRC.Rej.ULPower.CongNumber of RRC Connection Rejects for Cell (UL Power Congestion)Power Congestion. Check RTWP and the maximum TCP.check power threshold, interference,netwrok capacityVS.RRC.Rej.DLPower.CongNumber of RRC Connection Rejects for Cell (DL Power Congestion)VS.RRC.Rej.ULIUBBand.CongNumber of RRC Connection Rejects for Cell (UL Iub Bandwidth Congestion)VS.RRC.Rej.DLIUBBand.CongNumber of RRC Connection Rejects for Cell (DL Iub Bandwidth Congestion)VS.RRC.Rej.ULCE.CongNumber of RRC Connection Rejects for Cell (UL CE Resource Congestion)CE CongestionVS.RRC.Rej.DLCE.CongNumber of RRC Connection Rejects for Cell (DL CE Resource Congestion)VS.RRC.Rej.Code.CongNumber of RRC Connection Rejects for Cell (Code Resource Congestion)Code Congestion.To locate the problem, start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm major services.VS.RRC.Rej.Other.CongNumber of RRC Connection Rejects due to other reasonOther,analyze call detail logs.VS.RRC.Rej.RL.FailNumber of RRC Connection Rejects Due to Radio Link Setup Failure for CellRL Fail.NodeB fails or NodeB resource is insufficient.VS.RRC.Rej.TNL.FailNumber of RRC Connection Rejects for Cell (Transmission Setup Failure on Iub Interface )AAL2 Fail.transmission resource is insufficient or any transmission equipment is faulty,VS.RRC.FailConnEstab.NoReplyNumber of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP COMPLETE for CellVS.RRC.Rej.Redir.IntraRatNumber of RRC Connection Rejects during redirection between inter-frequency cells for cellVS.RRC.Rej.Redir.InterRatNumber of RRC Connection Rejects during redirection between inter-RAT cells for cellVS.RRC.Rej.Redir.ServiceNumber of RRC Connection Rejects Due to Service-based RRC Redirection for CellVS.RRC.Rej.Redir.DistNumber of Distance-Based RRC Redirections for CellCounter Level 1Sub Counter Level 2Sub Counter Level 3Sub Counter Level 4DescriptionVS.RAB.FailEstabCS.RNLNumber of Failed CS RAB Establishments for Cell (Radio Network Layer Cause)VS.RAB.FailEstabCS.Unsp Number of Failed CS RAB Establishments for Cell (Unsupported Capabilities)VS.RAB.FailEstabCS.CongNumber of Failed CS RAB Establishments for Cell (Congestion)VS.RAB.FailEstabCS.DLIUBBand.CongNumber of Failed CS RAB Establishments for Cell (DL Iub Bandwidth Congestion)VS.RAB.FailEstabCS.ULIUBBand.CongNumber of Failed CS RAB Establishments for Cell (UL Iub Bandwidth Congestion)VS.RAB.FailEstabCS.ULCE.CongNumber of Failed CS RAB Establishments for Cell (UL CE Congestion)VS.RAB.FailEstabCS.DLCE.CongNumber of Failed CS RAB Establishments for Cell (DL CE Congestion)VS.RAB.FailEstabCS.Code.CongNumber of Failed CS RAB Establishments for Cell (Code Congestion)VS.RAB.FailEstabCS.ULPower.CongNumber of Failed CS RAB Establishments for Cell (UL Power Congestion)VS.RAB.FailEstabCS.DLPower.CongNumber of Failed CS RAB Establishments for Cell (DL Power Congestion)VS.RAB.FailEstabCS.Unsp.OtherNumber of Failed CS RAB Establishments for Cell due to other cause of insufficient capability of UTRANUE acknowledges the RB setup failure because of configuration unsupported compatibility problem of UE in some unknown scenariosVS.RAB.FailEstabCS.UuFailNumber of Failed CS RAB Establishments for Cell (Radio Network Layer Cause)VS.RAB.FailEstabCS.RBIncCfgNumber of Failed CS RAB Establishments for Cell(Invalid configuration of UE during the RB setup procedure)UE regards the configured parameters are invalid onesVS.RAB.FailEstabCS.RBCfgUnsupNumber of Failed CS RAB Establishments for Cell(Configuration unsupported of UE during the RB setup procedure)UE regards that the RB setup process and other processes simultaneously occur and they are incompatible.It is mainly caused by UE defectsVS.RAB.FailEstabCS.UuNoReplyNumber of Failed CS RAB Establishments for Cell(No reply of UE during the RB setup procedure)UE does not acknowledge the RB setup request. This reason frequently occurs. It is mainly caused by poor coverage, so UE cannot receive the RB setup request messageVS.RAB.FailEstabCS.PhyChFailNumber of Failed CS RAB Establishments for Cell(Physical channel failure of UE during the RB setup procedure)The RB setup failure may occur if FACH is migrated to DCH but downlink physical layers are not synchronized during the RB setup process. The rooted reason is poor coverageVS.RAB.FailEstabCS.IubFailNumber of Failed CS RAB Establishments for cell (Radio Link Configuration Failure)the Cell Update process occurs. The RB setup failure is caused by process nestingVS.RAB.FailEstabCS.RNL.OtherNumber of Failed CS RAB Establishments for Cell due to other cause of Radio Network LayerVS.RAB.FailEstabCS.TNLNumber of Failed CS RAB Establishments for Cell (Transport Network Layer CauseVS.RAB.FailEstabCS.other.CELLNumber of Failed CS RAB Establishments for Cell due to other causeCounter Level 1Sub Counter Level 2Sub Counter Level 3Sub Counter Level 4DescriptionVS.RAB.FailEstabPS.RNLNumber of Failed PS RAB Establishments for Cell (Radio Network Layer Cause)VS.RAB.FailEstabPS.Unsp Number of Failed PS RAB Establishments for Cell (Unsupported Capabilities)VS.RAB.FailEstabPS.CongNumber of Failed PS RAB Establishments for Cell (Congestion)VS.RAB.FailEstabPS.DLIUBBand.CongNumber of Failed PS RAB Establishments for Cell (DL Iub Bandwidth Congestion)VS.RAB.FailEstabPS.ULIUBBand.CongNumber of Failed PS RAB Establishments for Cell (UL Iub Bandwidth Congestion)VS.RAB.FailEstabPS.ULCE.CongNumber of Failed PS RAB Establishments for Cell (UL CE Congestion)VS.RAB.FailEstabPS.DLCE.CongNumber of Failed PS RAB Establishments for Cell (DL CE Congestion)VS.RAB.FailEstabPS.Code.CongNumber of Failed PS RAB Establishments for Cell (Code Congestion)VS.RAB.FailEstabPS.ULPower.CongNumber of Failed PS RAB Establishments for Cell (UL Power Congestion)VS.RAB.FailEstabPS.DLPower.CongNumber of Failed PS RAB Establishments for Cell (DL Power Congestion)VS.RAB.FailEstabPS.Unsp.OtherNumber of Failed PS RAB Establishments for Cell due to other cause of insufficient capability of UTRANVS.RAB.FailEstabPS.UuFailNumber of Failed PS RAB Establishments for Cell (Radio Network Layer Cause)VS.RAB.FailEstabPS.RBIncCfgNumber of Failed PS RAB Establishments for Cell(Invalid configuration of UE during the RB setup procedure)VS.RAB.FailEstabPS.RBCfgUnsupNumber of Failed PS RAB Establishments for Cell(Configuration unsupported of UE during the RB setup procedure)VS.RAB.FailEstabPS.UuNoReplyNumber of Failed PS RAB Establishments for Cell(No reply of UE during the RB setup procedure)VS.RAB.FailEstabPS.PhyChFailNumber of Failed PS RAB Establishments for Cell(Physical channel failure of UE during the RB setup procedure)VS.RAB.FailEstabPS.IubFailNumber of Failed PS RAB Establishments for cell (Radio Link Configuration Failure)VS.RAB.FailEstabPS.RNL.OtherNumber of Failed PS RAB Establishments for Cell due to other cause of Radio Network LayerVS.RAB.FailEstabPS.TNLNumber of Failed PS RAB Establishments for Cell (Transport Network Layer CauseVS.RAB.FailEstabPS.other.CELLNumber of Failed PS RAB Establishments for Cell due to other cause

VS.RAB.FailEstabCS.TNLVS.RRC.FailConnEstab.NoReplyVS.RRC.Rej.Redir.IntraRatVS.RRC.Rej.Redir.InterRatVS.RRC.Rej.Redir.ServiceVS.RRC.Rej.Redir.DistVS.RAB.FailEstabPS.TNL

SHOCounterDescriptionVS.SHO.FailRLAdd.CfgUnsuppNumber of Failed Radio Link Additions in Soft Handover for Cell (Configuration Unsupported)VS.SHO.FailRLAdd.ISRNumber of Failed Radio Link Additions in Soft Handover for Cell (Incompatible Simultaneous Reconfiguration)VS.SHO.FailRLAdd.InvCfgNumber of Failed Radio Link Additions in Soft Handover for Cell (Invalid Configuration)VS.SHO.FailRLAdd.NoReplyNumber of Failed Radio Link Additions in Soft Handover due to UE No Response for Cell

VS.SHO.FailRLAdd.CfgUnsuppVS.SHO.FailRLAdd.ISRVS.SHO.FailRLAdd.InvCfgVS.SHO.FailRLAdd.NoReply

IRATIRATHO CS FailureCounterDescriptionIRATHO CS Failure during Relocation PreparationIRATHO.FailRelocPrepOutCS.TAlExpNumber of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (TRELOCalloc expiry)IRATHO.FailRelocPrepOutCS.TgtFailNumber of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Relocation Failure in Target CN/RNC or Target System)IRATHO.FailRelocPrepOutCS.ReloNoSupNumber of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Relocation not supported in Target RNC or Target system)IRATHO.FailRelocPrepOutCS.HigherTrafficLodNumber of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell)IRATHO.FailRelocPrepOutCS.NoResAvailNumber of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (No Resource Available)IRATHO.FailRelocPrepOutCS.UKnowRNCNumber of Failed Preparations for CS Outgoing Inter-RAT Handover for Cell (Unknown Target RNC)IRATHO CS Failure after Relocation PreparationIRATHO.FailOutCS.CfgUnsuppNumber of Failed CS Outgoing Inter-RAT Handovers for Cell (Configuration Unsupported)IRATHO.FailOutCS.PhyChFailNumber of Failed CS Outgoing Inter-RAT Handovers for Cell (Physical Channel Failure)IRATHO PS FailureCounterDescriptionIRATHO PS Failure during Relocation PreparationVS.IRATHO.FailRelocPrepOutPS.TAlExpNumber of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (TRELOCalloc expiry)VS.IRATHO.FailRelocPrepOutPS.TgtFailNumber of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Relocation Failure in Target CN/RNC or Target System)VS.IRATHO.FailRelocPrepOutPS.ReloUnSuppNumber of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Relocation not supported in Target RNC or Target system)VS.IRATHO.FailRelocPrepOutPS.TgtHighLoadNumber of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Traffic Load In The Target Cell Higher Than In The Source Cell)VS.IRATHO.FailRelocPrepOutPS.NoResAvailNumber of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (No Resource Available)VS.IRATHO.FailRelocPrepOutPS.UnKnowRNCNumber of Failed Preparations for Enhanced PS Outgoing Inter-RAT Handover for Cell (Unknown Target RNC)IRATHO PS Failure after Relocation PreparationIRATHO.FailOutPSUTRAN.CfgUnsuppNumber of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Configuration unsupported)IRATHO.FailOutPSUTRAN.PhyChFailNumber of Failed PS Outgoing Inter-RAT Handovers Initiated by RNC (Physical Channel Failure)

Sheet1KPIStageFailure CauseLevelCall Setup Success RateRRC Setup Success Rate- Congestion- UnspecifiedRAB Setup Success Rate- Parameter violationCN domain:- Non supported UTRAN capabilities- CS- Relocation triggered- PS- Transport connection failed to establishQoS Classes:- Unavailable resources- Conversational- Protocol error- Streaming- Interactive- BackgroundCall Drop RateSignaling Plane- OM intervention-CS- User inactivity- PS- Repeated integrity checking failure- UE generated signaling connection release- RL out-of-synchronizationUser Plane- OM interventionCN domain:- UTRAN generated reason- CS- RAB preempted- PSQoS Classes:- Conversational- Streaming- Interactive- BackgroundCongestion RateSignaling Congestion RateRRC Connection Reject (Cause: congestion)Traffic Congestion RateRAB Assignment Setup Failure (cause: congestion).- CS- PSSoft & Softer Handover Success RateRadio Link Addition- Configuration unsupported- Incompatible simultaneous reconfiguration- Protocol error- Invalid configurationRadio Link Deletion- No response from UEHard Handover Success Rate- Configuration unsupported- Physical channel failure- Incompatible simultaneous reconfiguration- Protocol error- Cell update occurred- Invalid configuration- No response received from UEInterRAT Handover to GSM Success Rate- Configuration unacceptable- Physical channel failure- Protocol error- Inter-RAT protocol error- Unspecified- InterRAT handover to GSM no responseInterRAT Handover to GPRS Success Rate- Configuration unacceptable- initiated by UTRAN- Physical channel failure- Protocol error- Unspecified- InterRAT handover to GSM no responseCS TrafficErlangQoS Classes:- Conversational- StreamingBears- AMR Voice- CS 64KPS TrafficErlangQoS Classes:- Conversational- Streaming- Interactive- BackgroundPS ThroughputByteQoS Classes:- Conversational- Streaming- Interactive- Background