CounterVS.RRC.Rej.Redir.Inter.AttVS.RRC.Reject.Redir.IntratVS.RRC.Reject.Redir.Service

RRC Setup FailRRC Setup Reject.RRC REQ CELL RESELRRC REQ REG

RRC setup rejectRRC setup reject

RRC setup rejectRRC setup rejectRRC setup rejectRRC setup rejectRRC setup rejectRRC setup rejectRRC setup reject

DescriptionNumber 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 subscribersAccess failure due to equipment faults

Power Congestion. Check RTWP and the maximum TCP.check power threshold, interference,netwrok capacityCE CongestionRL 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 there is any BTS alarm.Code Congestion.To locate the problem, start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm major services.Other,analyze call detail logs.

Power Congestion. Check RTWP and the maximum TCP.check power threshold, interference,netwrok capacity

FP Fail. If the transmission fails or an equipment is faulty, FP synchronization may fail. To locate the problem, check whether there is any BTS alarm.Code Congestion.To locate the problem, start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm major services.

Counter DescriptionRRC.AttConnEstab.OrgConvCall Originating Conversational CallRRC.AttConnEstab.OrgStrCall Originating Streaming CallRRC.AttConnEstab.OrgInterCall Originating Interactive CallRRC.AttConnEstab.OrgBkgCall Originating Background CallRRC.AttConnEstab.OgSubCall Originating Subscribed traffic CallRRC.AttConnEstab.TmConvCall Terminating Conversational CallRRC.AttConnEstab.TmStrCall Terminating Streaming CallRRC.AttConnEstab.TmInterCall Terminating Interactive CallRRC.AttConnEstab.TmBkgCall Terminating Background CallRRC.AttConnEstab.EmgCall Emergency CallRRC.AttConnEstab.IRATCelRes Inter-RAT cell re-selectionRRC.AttConnEstab.IRATCCO Inter-RAT cell change orderRRC.AttConnEstab.Reg RegistrationRRC.AttConnEstab.Detach DetachRRC.AttConnEstab.OgHhPrSig Originating High Priority SignallingRRC.AttConnEstab.OgLwPrSig Originating Low Priority SignallingRRC.AttConnEstab.CallReEst Call re-establishmentRRC.AttConnEstab.TmHhPrSig Terminating High Priority SignallingRRC.AttConnEstab.TmLwPrSig Terminating Low Priority SignallingRRC.AttConnEstab.Unknown Terminating - cause unknownRRC.AttConnEstab.MBMSRep MBMS ReceptionRRC.AttConnEstab.MBMSPtp MBMS PTP RB Request

CounterRRC.AttConnRelDCCH.NormRelRRC.AttConnRelDCCH.CongestionRRC.AttConnRelDCCH.PreemptRRC.AttConnRelDCCH.ReEstRejRRC.AttConnRelDCCH.SigConReEstRRC.AttConnRelDCCH.UsrInactRRC.AttConnRelDCCH.Unspec

DescriptionNumber 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.

qwa DescriptionVS.FailRBSetup.CfgUnsup Configuration unsupportedVS.FailRBSetup.PhyChFail Physical channel failureVS.FailRBSetup.CellUpd Cell update occurredVS.FailRBSetup.IncCfg Invalid configurationVS.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 migrationCS 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_CELLCS RAB setup failures CE_CONG_CELLCS RAB setup failures CODE_CONG_CELLCS RAB setup failures OTHER_CELLCS 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 problem of UE in some unknown scenariosPHYCH_FAIL 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 coverageSIMU_RECFG_INCOMP UE regards that the RB setup process and other processes simultaneously occur and they are incompatible.It is mainly caused by UE defectsCELL_UPDT the Cell Update process occurs. The RB setup failure is caused by process nestingCFG_INVALID UE regards the configured parameters are invalid onesNO_RESPONSE 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 messageOTHER

lParameter violationlNon supported UTRAN capabilitieslRelocation triggeredlTransport connection failed to establishlUnavailable resources lProtocol error

PARAM_CELL. RNC regards the parameters transmitted by core network as invalid parameters.

UNSUP_CELL.the QoS is not supported by RNC or RRM admission fails in RAB.

UE acknowledges the RB setup failure because of configuration unsupported compatibility problem of UE in some unknown scenariosThe 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 coverageUE regards that the RB setup process and other processes simultaneously occur and they are incompatible.It is mainly caused by UE defectsthe Cell Update process occurs. The RB setup failure is caused by process nesting

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 message

CounterVS.RAB.RelReqCS.OMVS.RAB.RelReqCS.RABPreemptVS.RAB.RelReqCS.UTRANgenVS.RAB.RelReqPS.OMVS.RAB.RelReqPS.RABPreempt

Call Drop Rate of Signaling Plane

Call Drop Rate of User Plane

lOM interventionlUser inactivitylRepeated integrity checking failurelUE generated signaling connection releaselRL out-of-synchronization

lOM interventionlUTRAN generated reasonlRAB preempted

DescriptionNumber 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"

Call Drop Rate of Signaling Plane

Repeated integrity checking failureUE generated signaling connection releaseRL out-of-synchronization

UTRAN generated reason

CounterVS.RAB.AttRelCS.NetOptVS.RAB.AttRelCS.NormRelVS.RAB.AttRelCS.OMVS.RAB.AttRelCS.PreemptVS.RAB.AttRelCS.UEInactVS.RAB.AttRelCS.UTRANGen

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

RAB_CS_REL_RF_LOSSRNC_CS_RAB_REL_TRIG_BY_RNC_SRB_RESETRNC_CS_RAB_REL_TRIG_BY_RNC_AAL2_LOSSCS_RAB_DROP_OTHER

RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESETRNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSSPS_RAB_DROP_OTHER

DescriptionNumber of CS RABs requested to release in the best cell for network optimizationNumber of CS RABs requested to release in the best cell for normal releaseNumber of CS RABs requested to release in the best cell for O&M interventionNumber of CS RABs requested to release in the best cell for RAB preemptedNumber of CS RABs requested to release in the best cell for user inactivityNumber 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 cellNumber 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 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.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.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.CS 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.

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.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.PS 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.

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.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.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.CS 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.

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.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.PS 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.

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.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.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.CS 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.

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.

PS 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.

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.

CS 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.

PS 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.

CounterVS.RAB.Loss.CS.RFVS.RAB.Loss.CS.RF.RLCRstVS.RAB.Loss.CS.RF.ULSyncVS.RAB.Loss.CS.RF.UuNoReplyVS.RAB.Loss.CS.RF.Oth

DescriptionNumber of CS domain RABs released due to RF failures in the best cellNumber of CS domain RABs released RF failures (RLC reset) in the best cellNumber of CS domain RABs released due to RF failures (Uplink Synchronization Fail) in the best cellNumber of the CS domain RABs released due to RF failures (Failure in the Radio Interface Procedure) in the best cellNumber of the CS domain RABs released due to RF failures (other cause) in the best cell

CounterVS.RAB.RelReqCS.OMVS.RAB.RelReqCS.RABPreemptVS.RAB.RelReqCS.UTRANgenVS.RAB.RelReqPS.OMVS.RAB.RelReqPS.RABPreempt

DescriptionNumber 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"

CounterVS.Norm.Rel.CS.AMR.UlSigRelVS.Norm.Rel.CS.Conv.RB.64.UlSigRelVS.Norm.Rel.PS.BE.RB.0.32.UlSigRelVS.Norm.Rel.PS.BE.RB.32.64.UlSigRelVS.Norm.Rel.PS.BE.RB.64.144.UlSigRelVS.Norm.Rel.PS.BE.RB.144.384.UlSigRelVS.Norm.Rel.PS.CCH.UlSigRelVS.Norm.Rel.PS.HS.UlSigRelVS.Norm.Rel.CS.Str.UlSigRelVS.Norm.Rel.PS.Conv.UlSigRelVS.Norm.Rel.PS.Str.UlSigRel

DescriptionNumber of released CS AMR RABs due to uplink signaling connection release in the best cellNumber of released CS conversational service RABs due to uplink signaling connection release in the best cell( max DL bit rates is 64kbps)Number of released PS BE service RABs due to uplink signaling connection release in the best cell (max DL bitrate in (0,32] kbit/s, RRC state is CELL_DCH, R99 user only)Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (32,64] kbit/s, RRC state is CELL_DCH, R99 user only)Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (64,144] kbit/s, RRC state is CELL_DCH, R99 user only)Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (144,384] kbit/s, RRC state is CELL_DCH, R99 user only)Number of released PS RABs with the cause of uplink signaling connection release in the best cell that belongs to the SRNC (RRC state is CELL_FACH)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 cellNumber 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)

SHO_PREP_RL_SETUP_FAIL NodeB CE resource is insufficient or NodeB is faulty.SHO_PREP_AAL2_SETUP_FAIL AAL2 setup of lub interface fails because the transmission bandwidth is insufficient.SHO_PREP_FP_SYNC_FAIL the synchronization of AAL2 and FP of lub interface failsSHO_PREP_ FAIL_OTHER_CELL Soft handover prepare failure is caused by other reasons, such as insufficient RNC resource, radio resource admission reject, and RNC link state reject. To locate the problem, RNC logs must be used for further analysis.

SHO_RL_ADD_FAIL_CFG_UNSUPP UE does not support to add radio links in RNC during the active set update. This reason seldom exists in a commercial network.SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP UE feeds back that the soft handover process is incompatible with other concurrent processes when radio links are added in RNC.The problem is mainly caused by some handsets.SHO_RL_ADD_FAIL_CFG_INVALID UE regards active set update of adding radio links in RNC as invalid configuration.SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of adding radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover area is small, soft handover failure easily occurs.SHO_RL_DEL_FAIL_CFG_UNSUPP UE does not support to delete radio links in RNC during the active set update.SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP UE feeds back that the soft handover is incompatible with other concurrent processes when radio links are deleted in RNC.The problem is mainly caused by some handsets.SHO_RL_ADD_FAIL_CFG_INVALID UE regards the active set update of deleting radio links in RNC as invalid configuration.SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of deleting radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover area is small, soft handover failure easily occurs.SHO_FAIL_OTHER_CELL Soft handover failure is caused by other reasons;

AAL2 setup of lub interface fails because the transmission bandwidth is insufficient.

Soft handover prepare failure is caused by other reasons, such as insufficient RNC resource, radio resource admission reject, and RNC link state reject. To locate the problem, RNC logs must be used for further analysis.

UE does not support to add radio links in RNC during the active set update. This reason seldom exists in a commercial network.UE feeds back that the soft handover process is incompatible with other concurrent processes when radio links are added in RNC.The problem is mainly caused by some handsets.UE regards active set update of adding radio links in RNC as invalid configuration.RNC does not receive the acknowledgement of active set update of adding radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover area is small, soft handover failure easily occurs.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 processes when radio links are deleted in RNC.The problem is mainly caused by some handsets.UE regards the active set update of deleting radio links in RNC as invalid configuration.RNC does not receive the acknowledgement of active set update of deleting radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover area is small, soft handover failure easily occurs.

Soft handover prepare failure is caused by other reasons, such as insufficient RNC resource, radio resource admission reject, and RNC link state reject. To locate the problem, RNC logs must be used for further analysis.

UE feeds back that the soft handover process is incompatible with other concurrent processes when radio links are added in RNC.The problem is mainly caused by some handsets.

RNC does not receive the acknowledgement of active set update of adding radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover area is small, soft handover failure easily occurs.

UE feeds back that the soft handover is incompatible with other concurrent processes when radio links are deleted in RNC.The problem is mainly caused by some handsets.

RNC does not receive the acknowledgement of active set update of deleting radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover area is small, soft handover failure easily occurs.

CS_INTERRAT_HO_PREP_FAIL_TARGET_FAILCS_INTERRAT_HO_PREP_FAIL_TALLOC_EXPIRCS_INTERRAT_HO_PREP_FAIL_TARGET_UNSUPPCS_INTERRAT_HO_PREP_FAIL_RELOC_ABORTCS_INTERRAT_HO_PREP_FAIL_NO_RSRC_AVAILCS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGETCS_INTERRAT_HO_PREP_FAIL_ REQINFNOTAVAICS_INTERRAT_HO_PREP_FAIL_NO_RSP

CS_INTERRAT_HO_ FAIL_UNSPECCS_INTERRAT_HO_ FAIL_PHYCN_FAILCS_INTERRAT_HO_ FAIL_ CFG_UNSUPPCS_INTERRAT_HO_ FAIL_ RELOC_ABORTCS_INTERRAT_HO_ FAIL_NO_RSPCS_INTERRAT_HO_ FAIL_OTHER

CS inter-RAT handover prepare failure is caused by Relocation Failure Target CN/RNCCS inter-RAT handover prepare failure is caused by TRELOCalloc Expiry (cause value) because the data configuration or link connection of core network is incorrect. To locate the problem, track the signaling of core network and BSS for further analysis.CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) because BSC does not support some parameters of handover requests. To locate the problem, track the signaling of core network and BSS for further analysis.After sending the handover prepare request, RNC receives the release message from core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the call. Thus, core network initializes the release.CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MSC is incorrect or there is no available resource in BSC. To locate the problem, track the signaling of core network and BSS for further analysis.CS inter-RAT handover prepare failure is caused by Unknown Target RNC (cause value) because the data configuration of MSC is incorrect or the LAC of target cell is not configured.CS inter-RAT handover prepare failure is caused by Requested Information Not Available because the data configuration is incorrect or target BSC does not support the handover.CS inter-RAT handover prepare failure occurs because core network does not respond to the handover prepare request. This may be caused by incorrect data configuration or link connection of core network.

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 caused by:1) The signals of 2G network are weak or UE fails to access the network due to serious interference.2) Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.CS inter-RAT handover failure is caused by Configuration Unsupported (cause value) because UE does not support the handover request. This reason may be mainly caused by abnormal UE.After sending the handover request message to UE, RNC receives the release message from core network. However, the cause is not Normal Release because the link is released abnormally due to other reasons.After RNC sends the handover request message to UE, UE does not acknowledge the request because network coverage is poor.CS inter-RAT handover failure is caused by other reasons. To locate the problem, analyze the RNC logs.

CS inter-RAT handover prepare failure is caused by TRELOCalloc Expiry (cause value) because the data configuration or link connection of core network is incorrect. To locate the problem, track the signaling of core network and BSS for further analysis.CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) because BSC does not support some parameters of handover requests. To locate the problem, track the signaling of core network and BSS for further analysis.After sending the handover prepare request, RNC receives the release message from core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the call. Thus, core network initializes the release.CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MSC is incorrect or there is no available resource in BSC. To locate the problem, track the signaling of core network and BSS for further analysis.CS inter-RAT handover prepare failure is caused by Unknown Target RNC (cause value) because the data configuration of MSC is incorrect or the LAC of target cell is not configured.CS inter-RAT handover prepare failure is caused by Requested Information Not Available because the data configuration is incorrect or target BSC does not support the handover.CS inter-RAT handover prepare failure occurs because core network does not respond to the handover prepare request. This may be caused by incorrect data configuration or link connection of core network.

CS inter-RAT handover failure is caused by Physical Channel Failure (cause value). CS inter-RAT handover 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) Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.CS inter-RAT handover failure is caused by Configuration Unsupported (cause value) because UE does not support the handover request. This reason may be mainly caused by abnormal UE.After sending the handover request message to UE, RNC receives the release message from core network. However, the cause is not Normal Release because the link is released abnormally due to other reasons.After RNC sends the handover request message to UE, UE does not acknowledge the request because network coverage is poor.

CS inter-RAT handover prepare failure is caused by TRELOCalloc Expiry (cause value) because the data configuration or link connection of core network is incorrect. To locate the problem, track the signaling of core network and BSS for further analysis.CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) because BSC does not support some parameters of handover requests. To locate the problem, track the signaling of core network and BSS for further analysis.After sending the handover prepare request, RNC receives the release message from core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the call. Thus, core network initializes the release.CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MSC is incorrect or there is no available resource in BSC. To locate the problem, track the signaling of core network and BSS for further analysis.

CS inter-RAT handover failure is caused by Physical Channel Failure (cause value). CS inter-RAT handover 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) Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.

After sending the handover prepare request, RNC receives the release message from core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the call. Thus, core network initializes the release.

CS inter-RAT handover failure is caused by Physical Channel Failure (cause value). CS inter-RAT handover 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) Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.

After sending the handover prepare request, RNC receives the release message from core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, 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 analyzedTCP Transmitted carrier power.The cell that has the greatest TCP represents the cell that has the greatest downlink radio load. In practice, if the cell has the greatest downlink radio load, the cell also has the greatest downlink admission rejects. For such cell, check whether the cross coverage is serious and check whether the indoor coverage of high traffic area must be improved to decrease large power consumption.DCH UE downlink admission rejects.The cell that has the greatest DCH UE is used to measure the subscriber number of a cell. Combined with the utilization of OVSF codes, the average CE and transmission can be estimated to further check whether the resources are sufficient.DL ADMSNThe cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. In practice, downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. If a cell has the greatest DL ADMSN DENY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be improved.

Transmitted carrier power.The cell that has the greatest TCP represents the cell that has the greatest downlink radio load. In practice, if the cell has the greatest downlink radio load, the cell also has the greatest downlink admission rejects. For such cell, check whether the cross coverage is serious and check whether the indoor coverage of high traffic area must be improved to decrease large power consumption.downlink admission rejects.The cell that has the greatest DCH UE is used to measure the subscriber number of a cell. Combined with the utilization of OVSF codes, the average CE and transmission can be estimated to further check whether the resources are sufficient.The cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. In practice, downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. If a cell has the greatest DL ADMSN DENY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be improved.

Transmitted carrier power.The cell that has the greatest TCP represents the cell that has the greatest downlink radio load. In practice, if the cell has the greatest downlink radio load, the cell also has the greatest downlink admission rejects. For such cell, check whether the cross coverage is serious and check whether the indoor coverage of high traffic area must be improved to decrease large power consumption.downlink admission rejects.The cell that has the greatest DCH UE is used to measure the subscriber number of a cell. Combined with the utilization of OVSF codes, the average CE and transmission can be estimated to further check whether the resources are sufficient.The cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. In practice, downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. If a cell has the greatest DL ADMSN DENY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be improved.

Transmitted carrier power.The cell that has the greatest TCP represents the cell that has the greatest downlink radio load. In practice, if the cell has the greatest downlink radio load, the cell also has the greatest downlink admission rejects. For such cell, check whether the cross coverage is serious and check whether the indoor coverage of high traffic area must be improved to decrease large power consumption.

The cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. In practice, downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. If a cell has the greatest DL ADMSN DENY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be improved.

The cell that has the greatest DL ADMSN DENY is used to measure the cell that has the greatest downlink radio load. In practice, downlink radio load is a bottleneck because the uplink is asymmetric to the downlink and the downlink is of interference. If a cell has the greatest DL ADMSN DENY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be improved.

lConfiguration unsupportedlPhysical channel failurelIncompatible simultaneous reconfigurationlProtocol errorlCell update occurredlInvalid configuration