Counter VS.RRC.Rej.Redir.Inter.Att VS.RRC.Reject.Redir.Intrat VS.RRC.Reject.Redir.Service Counter VS.RRC.Rej.Power.Cong VS.RRC.Rej.UL.CE.Cong VS.RRC.Rej.DL.CE.Cong VS.RRC.Rej.Code.Cong VS.RRC.Rej.ULIUBBandCong VS.RRC.Rej.DLIUBBandCong
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
ID 67179300 67189473 67189474 67179521 67192608
67192609
67190401 67179522
67190404 67190405 67179524 67179525 67179527 67196031
Counter VS.RRC.Rej.Redir.Inter.Att VS.RRC.Reject.Redir.Intrat VS.RRC.Reject.Redir.Service Counter RRC.FailConnEstab.Cong
Counter RRC.FailConnEstab.NoReply
Bad Quality during RRC Request Failed RAB Admission Reject RAB Establishment Blocked Other RAB Establishment Blocked Other RAB Establishment Blocked Other Radio Link Fail Release Radio Link Fail Release RRC Request Denied due to Admission Reject for CS RRC Request Denied due to Admission Reject for CS RRC Request Denied due to Admission Reject for PS System Initiated Unspecified Release UE Lost at Unspecified RF UE Lost due to Downlink Bad Quality UE Lost due to Low Coverage UE Lost due to UL Interference UE Lost due to UL Interference
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. Description Failure of requesting for power resources. Failure of requesting for uplink CE resources in a cell. Failure of requesting for downlink CE resources in a cell. Failure of requesting for code resources. RNC admission algorithm rejection due to congestion of the uplink Iub interface bandwidth. RNC admission algorithm rejection due to congestion of the downlink Iub interface bandwidth.
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.
Counter
VS.RRC.FailConnEstab VS.RRC.Rej.Redir.Inter.Att VS.RRC.Reject.Redir.Intrat RRC.FailConnEstab.Cong VS.RRC.Rej.ULIUBBandCong VS.RRC.Rej.DLIUBBandCong RRC.FailConnEstab.NoReply VS.RRC.Rej.Power.Cong
VS.RRC.Rej.UL.CE.Cong VS.RRC.Rej.DL.CE.Cong VS.RRC.Rej.Code.Cong VS.RRC.Rej.RL.Fail VS.RRC.Rej.TNL.Fail VS.RRC.Reject.Redir.Service
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. Feature ID WRFD-010510
Feature ID WRFD-010510
Radio FailureInTheRadioInterfaceProcedure Too Many Serving Cell Users Eul RAB Mapping Failure Procedure Timeout Node Internal Failure 7 RL Release Non Transport RLC Unrecoverable Error Load Sharing Load Sharing Load Sharing System Release - Unspecified RLC Max Retranmission Reached RLC Max Retranmission Reached Radio FailureInTheRadioInterfaceProcedure RLC Max Retranmission Reached RCS Timer Expired
interference,netwrok capacity
ay fail. To locate the problem, check whether there is any BTS alarm. is to analyze the code allocation and confirm major services.
Description Number of RRC Connection Rejects
Count of RRC Connection Reject due to Redirection between interfrequency cell Count of RRC Connection Reject due to Redirection between interfRAT cell Number of RRC Connection Rejects due to Network Congestion Count of establishment failures of RRC connection due to RNC admission algorithem rejection which is caused by UL Iub bandwidth congestion Count of establishment failures of RRC connection due to RNC admission algorithem rejection which is caused by DL Iub bandwidth congestion Number of RRC Connection Fail due to no Reply Count of RRC Connection Reject because of Congestion
Number of RRC Connection Rejects due to Uplink CE Resource Request Fail Number of RRC Connection Rejects due to Downlink CE Resource Request Fail Count of RRC Connection Reject because of Congestion Count of RRC Connection Reject Count of RRC Connection Reject Count of RRC Connection Reject due to Service Based Redirection
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
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 VS.RRC.FailConnEstab
Feature ID WRFD-010510
Conflicting cell parameters prevent setup . No radio capacity . No spreading codes . No Channel Elements . No AAL type 2 capacity . Failure in creating L2 RLC entity . Failure in creating L2 MAC dedicated entity . Failure in creating L2 Outer Loop Power Control entity . No AAL type 2 termination points . No RNTI . Not supported service . UE not capable to support requested service . Iu tunnel endpoint reservation failure . Failure in reconfiguring L2 RLC entity for data PDU transportation . Failure in reconfiguring L2 MAC dedicated entity for data transportation . Failure in reconfiguring L2 OLPC dedicated entity for data transportation
. Initial synchronisation failure RRC Resource Shortage No resources for RRC in network RAB Resource Short.age No resources for RT RAB in network . No resources for NRT RAB in network RRC Setup Errors . RRC setup failure because of network error . RRC setup failure because of UE error RAB Setup errors . Requested RAB not supported by RAN . Requested RAB not supported by UE . RAB RT setup failure because of network error . RAB RT setup failure because of UE error . RAB NRT setup failure because of network error . RAB NRT setup failure because of UE
. UE does not respond to RRC SETUP . UE responds with wrong parameters . RL synchronisation failure . UE responds RB RECONFIGURATION FAILURE . Relocation failed . Relocation cancelled . UE does not confirm that it has received needed mobility information . No resources to execute Relocation in Target RNC . Relocation failed . UE does not confirm that it has received needed mobility information . Inter-RNC HHO failed . Inter-RNC HHO cancelled . UE does not confirm that it has reconfigured physical or transport channel . No resources to execute Inter-RNC HHO in Target RNC . Inter-RNC HHO failed . UE does not confirm that it has reconfigured physical or transport channel . Inter-System HHO failed . Inter-System HHO cancelled . UE Returns from GSM . Inter-System HHO failed . Inter-System HHO cancelled
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Counter VS.RAC.SHO.Fail.ULCE.Cong VS.RAC.SHO.Fail.DLCE.Cong VS.RAC.SHO.Fail.ULLD.Cong VS.RAC.SHO.Fail.DLLD.Cong VS.RAC.SHO.Fail.OVSF.Cong VS.RAC.SHO.Fail.ULIub.Cong VS.RAC.SHO.Fail.DLIub.Cong VS.RAC.SHO.Fail.HSUPANum.Cong VS.RAC.TrChSwitch.Fail.ULCE.Cong VS.RAC.TrChSwitch.Fail.DLCE.Cong VS.RAC.TrChSwitch.Fail.ULLD.Cong VS.RAC.TrChSwitch.Fail.DLLD.Cong VS.RAC.TrChSwitch.Fail.OVSF.Cong VS.RAC.TrChSwitch.Fail.ULIub.Cong VS.RAC.TrChSwitch.Fail.DLIub.Cong VS.RAC.TrChSwitch.Fail.HSDPANum.Cong VS.RAC.TrChSwitch.Fail.HSUPANum.Cong VS.RAC.HHO.Fail.ULCE.Cong VS.RAC.HHO.Fail.DLCE.Cong VS.RAC.HHO.Fail.ULLD.Cong VS.RAC.HHO.Fail.DLLD.Cong VS.RAC.HHO.Fail.ULIub.Cong VS.RAC.HHO.Fail.DLIub.Cong VS.RAC.HHO.Fail.HSDPANum.Cong VS.RAC.HHO.Fail.HSUPANum.Cong VS.RAC.HHO.Preempt.Cong VS.RAC.NewCallRequest.Fail.ULCE.Cong VS.RAC.NewCallRequest.Fail.DLCE.Cong VS.RAC.NewCallRequest.Fail.HSDPANum.Cong VS.RAC.NewCallRequest.Fail.HSUPANum.Cong VS.RAC.NewCallRequest.DownSZ.Cong VS.RAC.NewCallRequest.Preempt.Cong VS.RAC.R99.Power.Cong VS.RAC.HSDPA.Power.Cong VS.RAC.Total.Power.Cong VS.RAC.HSUPA.Power.Cong
Description Number of failures in each cell to request UL CE resources in the SHO procedure Number of failures in each cell to request DL CE resources in the SHO procedure Number of failures in each cell to request UL power resources in the SHO procedure Number of failures in each cell to request DL power resources in the SHO procedure Number of failures in each cell to request DL OVSF code resources in the SHO procedure Number of failures in each cell to request UL Iub resources in the SHO procedure Number of failures in each cell to request DL Iub resources in the SHO procedure Number of failures in each cell to request HSUPA user resources in the SHO procedure Number of failures in each cell to request UL CE resources in the channel switch procedure Number of failures in each cell to request DL CE resources in the channel switch procedure Number of failures in each cell to request UL power resources in the channel switch procedure Number of failures in each cell to request DL power resources in the channel switch procedure Number of failures in each cell to request DL OVSF code resources in the channel switch procedure Number of failures in each cell to request UL Iub resources in the channel switch procedure Number of failures in each cell to request DL Iub resources in the channel switch procedure Number of failures in each cell to request HSDPA user resources in the channel switch procedure Number of failures in each cell to request HSUPA user resources in the channel switch procedure Number of unsuccessfully applying for UL CE resources in each failed cell in HHO Procedure Number of unsuccessfully applying for DL CE resources in each failed cell in HHO Procedure Number of unsuccessfully applying for UL power resources in each failed cell in HHO Procedure Number of unsuccessfully applying for DL power resources in each failed cell in HHO Procedure Number of unsuccessfully applying for UL Iub resources in each failed cell in HHO Procedure Number of unsuccessfully applying for DL Iub resources in each failed cell in HHO Procedure Number of unsuccessfully applying for HSDPA user resources in each failed cell in HHO Procedure Number of unsuccessfully applying for HSUPA user resources in each failed cell in HHO Procedure Number of preemption by high priority user when unsuccessfully applying for resources in each failed cell in HHO Procedure Number of failures in each cell to request UL CE resources in the RRC/RAB SETUP procedure Number of failures in each cell to request DL CE resources in the RRC/RAB SETUP procedure Number of failures in each cell to request HSDPA user resources in the RRC/RAB SETUP procedure Number of failures in each cell to request HSUPA user resources in the RRC/RAB SETUP procedure Number of failures in each cell to request diffetent resources in the RRC/RAB SETUP procedure Number of preemption by high priority user when unsuccessfully applying for resources in each failed cell in the RRC/RAB SET Number of failures in each cell to request R99 power resources Number of failures in each cell to request HSDPA power resources Number of failures in each cell to request total power resources Number of failures in each cell to request HSUPA power resources
cell in HHO Procedure
cell in the RRC/RAB SETUP procedure
Counter RRC.AttConnRelDCCH.NormRel RRC.AttConnRelDCCH.Congestion RRC.AttConnRelDCCH.Preempt RRC.AttConnRelDCCH.ReEstRej RRC.AttConnRelDCCH.SigConReEst RRC.AttConnRelDCCH.UsrInact RRC.AttConnRelDCCH.Unspec
Call Drop Rate of Signaling Plane lOM intervention lUser inactivity lRepeated integrity checking failure lUE generated signaling connection release lRL out-of-synchronization
normal event The RNC indicates to the UE that the RRC must be released. user inactivity The RNC indicates to the UE that the RRC must be released. pre-emptive release The RNC indicates to the UE that the RRC must be released. directed signalling connection re-establishment The RNC indicates to the UE that the RRC must be released. This means that an RRC Connected UE (not in CELL_DCH) has moved under another RNC than SRNC and makes a Cell Update. If the SRNS Relocation is not possible needs to be released under the current SRNC and redirected to the additional SRNC. ID 67189459 67189460 67189461 67189462 67189463 67189464 67189465
67189466 67189467 67189468 67189469 67189470 67189471 67189472 67179571 67180387
ID 67189764 67202419 67180378 67189767 67189768 67180370 67192569 67192570 67192571 67192572 67192573 67192574 67192575 67192576 67180372 67180373 67180374 67180375 67180376 67180379 67180380 67180381 67180382 67180383 67180371 67180386
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.
ling Plane
integrity checking failure ated signaling connection release synchronization
ates to the UE that the RRC must be
ates to the UE that the RRC must be
that the RRC must be
n re-establishment that the RRC must be RRC Connected UE d under another RNC Update. If the SRNS the RRC connection the current SRNC and redirected
Counter
RRC.AttConnRelDCCH.Congestion RRC.AttConnRelDCCH.Preempt RRC.AttConnRelDCCH.ReEstRej RRC.AttConnRelDCCH.SigConReEst RRC.AttConnRelDCCH.UsrInact RRC.AttConnRelDCCH.Unspec RRC.AttConnRelCCCH.Congestion
RRC.AttConnRelCCCH.Preempt RRC.AttConnRelCCCH.ReEstRej RRC.AttConnRelCCCH.SigConReEst RRC.AttConnRelDCCH.NormRel RRC.AttConnRelCCCH.NormRel RRC.AttConnRelCCCH.UsrInact RRC.AttConnRelCCCH.Unspec RRC.FailConnReEstab.Cong VS.RRC.ConnRel.CellUpd
Counter
VS.CellUpdt.RLFAIL.Max.Time VS.CellUpdt.RLFAIL.Mean.Time RRC.AttConnReEstab.RFLoss RRC.SuccConnReEstab RRC.FailConnReEstab.NoReply VS.CellUpdt.AttConf VS.CellUpdt.AttUpd.Msg VS.CellUpdt.AttErrSRLC VS.CellUpdt.AttErrTRLC VS.CellUpdt.SuccErrTRLC VS.CellUpdt.AttMbmsRecv VS.CellUpdt.SuccMbmsRecv VS.CellUpdt.AttPtpRbReq VS.CellUpdt.SuccMbmsPtpRbReq VS.CellUpdt.AttPrd VS.CellUpdt.AttResel VS.CellUpdt.AttRsa VS.CellUpdt.AttPage VS.CellUpdt.AttULDatTrsf VS.CellUpdt.SuccPrd VS.CellUpdt.SuccResel VS.CellUpdt.SuccRsa VS.CellUpdt.SuccPage VS.CellUpdt.SuccULDatTrsf VS.CellUpdt.SuccUpd VS.CellUpdt.SuccRRCRel
n re-establishment.
Description Number of RRC Connection Release on DCH because of Congestion Number of RRC Connection Release on DCH because of Pre-emptive release Number of RRC Connection Release on DCH because of Re-establishment Reject Number of RRC Connection Release on DCH because of Directed signaling connection re-establishment Number of RRC Connection Release on DCH because of User inactivity Number of RRC Connection Release on DCH because of Unkown reason Number of RRC Connection Release on CCH because of Congestion
Number of RRC Connection Release on CCH because of Pre-emptive release Number of RRC Connection Release on CCH because of Re-establishment Reject Number of RRC Connection Release on CCH because of Directed signaling connection re-establishment Number of RRC Connection Release on CCH because of Normal Release Number of RRC Connection Release on CCH because of Normal Release Number of RRC Connection Release on CCH because of User inactivity Number of RRC Connection Release on CCH because of Unkown reason Count of RRC Connection Abnormal Release Number of RRC Connection Releases due to Cell Update Failure because of RL Failure Description The Maxim Time delay of Cell Update Procedure due to RL failure The Average Time delay of Cell Update Procedure due to RL failure Number of Cell Updates due to Radio Link Failure Number of Cell Updates Success due to Radio Link Failure Number of Cell Updates Fail due to Radio Link Failure Number of CELL UPDATE CONFIRM Messages from SRNC Number of Cell Updates due to Prd and Resel Number of Cell Updates Due to SRB FAILURE Number of Cell Updates Due to TRB FAILURE Number of Successful Cell Updates due to TRB FAILURE Number of Cell Updates Due to Mbms Reception Number of Succ Cell Updates Due to Mbms Reception Number of Cell Updates Due to Mbms PtP RB Request Number of Succ Cell Updates Due to Mbms PtP RB Request Number of Cell Updates due to Periodical Cell Update Number of Cell Updates due to Cell Reselection Number of Cell Updates due to Re-Entering Service Area Number of Cell Updates due to Paging Response Number of Cell Updates due to Uplink Data Transmission Number of Successful Cell Updates due to Periodical Cell Update Number of Successful Cell Updates due to Cell Reselection Number of Successful Cell Updates due to Re-Entering Service Area Number of Successful Cell Updates due to Paging Response Number of Successful Cell Updates due to Uplink Data Transmission Number of Successful Cell Updates Number of RRC Connection Releases due to Cell Update Failure
qwa VS.FailRBSetup.CfgUnsup VS.FailRBSetup.PhyChFail VS.FailRBSetup.CellUpd VS.FailRBSetup.IncCfg VS.FailRBSetup.NoReply
Description Configuration unsupported Physical channel failure Cell update occurred Invalid configuration No reply
CS RAB setup failures CS RAB setup failures CS RAB setup failures CS RAB setup failures CS RAB setup failures CS RAB setup failures CS RAB setup failures CS RAB setup failures CS RAB setup failures
PARAM_CELL. RNC regards the parameters transmitted by core network as invalid parameters. RELOC_CELL,relatedto migration TNL_CELL.IU transmission setup fails. CONG_CELL.RNC resource allocation failure. POWER_CONG_CELL CE_CONG_CELL CODE_CONG_CELL OTHER_CELL UNSUP_CELL.the QoS is not supported by RNC or RRM admission fails in RAB.
CFG_UNSUPP PHYCH_FAIL SIMU_RECFG_INCOMP CELL_UPDT CFG_INVALID NO_RESPONSE OTHER
UE acknowledges the RB setup failure because of configuration unsupported compatibility prob The RB setup failure may occur if FACH is migrated to DCH but downlink physical layers are not UE regards that the RB setup process and other processes simultaneously occur and they are in the Cell Update process occurs. The RB setup failure is caused by process nesting UE regards the configured parameters are invalid ones UE does not acknowledge the RB setup request. This reason frequently occurs. It is mainly caus
lParameter violation lNon supported UTRAN capabilities lRelocation triggered lTransport connection failed to establish lUnavailable resources lProtocol error Bad Quality during RRC Request Radio FailureInTheRadioInterfaceProcedure Failed RAB Admission Reject Too Many Serving Cell Users Eul RAB Establishment Blocked Other RAB Mapping Failure RAB Establishment Blocked Other Procedure Timeout Counter VS.FailRBSetup.CfgUnsup VS.FailRBSetup.PhyChFail VS.FailRBSetup.CellUpd VS.FailRBSetup.IncCfg VS.FailRBSetup.NoReply Counter
Description Configuration unsupported Physical channel failure Cell update occurred Invalid configuration No reply Description
VS.FailRBRecfg.CfgUnsup VS.FailRBRecfg.PhyChFail VS.FailRBRecfg.CellUpd VS.FailRBRecfg.IncCfg VS.FailRBRecfg.NoReply
Configuration unsupported Physical channel failure Cell update occurred Invalid configuration No reply
ID
Counter 67189494 VS.RAB.FailEstabCS.Cong 67189495 VS.RAB.FailEstabCS.RNL 67189496 VS.RAB.FailEstabCS.TNL 67179831 VS.RAB.FailEstCS.Relo 67179830 VS.RAB.FailEstCS.Unsp 67192610 VS.RAB.FailEstab.CS.DLIUBBand.Cong
67192611 VS.RAB.FailEstab.CS.ULIUBBand.Cong
67179865 VS.RAB.FailEstCS.RIPFail 67179862 VS.RAB.FailEstCs.Power.Cong 67190406 VS.RAB.FailEstCs.ULCE.Cong
67190407 VS.RAB.FailEstCs.DLCE.Cong
67179864 VS.RAB.FailEstCs.Code.Cong Counter Description VS.RAB.FailEstab.PS.DLIUB Number of RABs that fail to be set up in the PS domain with the failure cause of Band.Cong rejection by admission control due to downlink Iub bandwidth congestion VS.RAB.FailEstab.PS.ULIUB Number of RABs that fail to be set up in the PS domain with the failure cause of Band.Cong rejection by admission control due to uplink Iub bandwidth congestion Counter VS.RAB.FailEstPS.Par
Description Number of PS RABs unsuccessfully established because of parameter failures (cause value: Invalid RAB Parameters Value, Invalid RAB Parameters Combination, Condition Violation for SDU Parameters, Condition Violation for Traffic Handling Priority, or Condition Violation for Guaranteed Bit Rate)
VS.RAB.FailEstPS.Relo
Number of PS RABs unsuccessfully established due to relocation (cause value: Relocation Triggered) Number of PS RABs unsuccessfully established because of radio interface failure (cause value: Failure in the Radio Interface Procedure)
VS.RAB.FailEstPS.RIPFail
VS.RAB.FailEstPS.Unsp
VS.RAB.FailEstPS.NResAvail
VS.RAB.FailEstPS.RNL VS.RAB.FailEstPS.TNL Counter VS.RAB.FailEstPs.Power.Co ng VS.RAB.FailEstPs.ULCE.Con g VS.RAB.FailEstPs.DLCE.Con g VS.RAB.FailEstPs.Code.Con g
Number of PS RABs unsuccessfully established because of insufficient capability of UTRAN (cause value: Requested Traffic Class not Available, Requested Maximum Bit Rate not Available, Requested Maximum Bit Rate for DL not Available, Requested Maximum Bit Rate for UL not Available, Requested Guaranteed Bit Rate not Available, Requested Guaranteed Bit Rate for DL not Available, Requested Guaranteed Bit Rate for UL not Available, or Requested Transfer Delay not Achievable) Number of PS RABs unsuccessfully established because of lack of system resources, for instance, a shortage of memory (cause value: No Resource Available) Number of PS RABs unsuccessfully established because of radio network layer failures Number of PS RABs unsuccessfully established because of transmission network layer failures Description Number of the PS RABs unsuccessfully established with the cause of "No Resource Available" due to power resource congestion Number of the PS RABs unsuccessfully established with the cause of "No Resource Available" due to uplink CE congestion Number of the PS RABs unsuccessfully established with the cause of "No Resource Available" due to downlink CE congestion Number of the PS RABs unsuccessfully established with the cause of "No Resource Available" due to code congestion
ID
Counter 67189400 VS.DRD.RRC.Out.Att 67189401 67192607 67199662 67199661 67204156 67199660 67179302
VS.DRD.RRC.Out.Succ VS.RRC.Estab.DRDIn VS.CellDCHUEs VS.CellFACHUEs VS.CellEFACHUEs VS.CellPCHUEs VS.RRC.ConnEstabTimeMax.DCH
67199510 VS.RRC.ConnEstabTimeMean.DCH 67179329 RRC.AttConnEstab.OrgConvCall 67179330 RRC.AttConnEstab.OrgStrCall 67179331 RRC.AttConnEstab.OrgInterCall 67179332 RRC.AttConnEstab.OrgBkgCall 67179334 RRC.AttConnEstab.TmConvCall
67179335 RRC.AttConnEstab.TmStrCall 67179336 RRC.AttConnEstab.TmInterCall 67179337 RRC.AttConnEstab.TmBkgCall 67179457 RRC.SuccConnEstab.OgConvCall 67179458 RRC.SuccConnEstab.OrgStrCall 67179459 RRC.SuccConnEstab.OrgItrCall 67179460 RRC.SuccConnEstab.OrgBkgCall 67179461 RRC.SuccConnEstab.OrgSubCall 67179462 RRC.SuccConnEstab.TmConvCall 67179463 RRC.SuccConnEstab.TmStrCall 67179464 RRC.SuccConnEstab.TmItrCall 67179465 RRC.SuccConnEstab.TmBkgCall 67179298 VS.RRC.SetupConnEstab.Cell 67179299 RRC.SuccConnEstab.sum 67179333 RRC.AttConnEstab.OgSubCall 67179338 RRC.AttConnEstab.EmgCall 67179339 RRC.AttConnEstab.IRATCelRes 67179340 RRC.AttConnEstab.IRATCCO 67179341 RRC.AttConnEstab.Reg 67179342 RRC.AttConnEstab.Detach 67179343 RRC.AttConnEstab.OgHhPrSig 67179344 RRC.AttConnEstab.OgLwPrSig 67179345 RRC.AttConnEstab.CallReEst 67179346 RRC.AttConnEstab.TmHhPrSig 67179347 RRC.AttConnEstab.TmLwPrSig 67179348 RRC.AttConnEstab.Unknown 67179467 RRC.SuccConnEstab.IRATCelRes 67179468 RRC.SuccConnEstab.IRATCCO 67179469 RRC.SuccConnEstab.Reg 67179470 RRC.SuccConnEstab.Detach
67179471 RRC.SuccConnEstab.OgHhPrSig 67179472 RRC.SuccConnEstab.OgLwPrSig 67179473 RRC.SuccConnEstab.CallReEst 67179474 RRC.SuccConnEstab.TmHhPrSig 67179475 RRC.SuccConnEstab.TmLwPrSig 67179476 RRC.SuccConnEstab.Unkown 67179633 67179634 67179649 67179650 67179466
VS.RRC.AttConEst.DCH VS.RRC.SuccConEst.DCH VS.RRC.AttConEst.CCH VS.RRC.SuccConEst.CCH RRC.SuccConnEstab.EmgCall
67190586 VS.RRC.AttConnEstab.Cell 67190587 VS.RRC.SuccConnEstab.First 67190588 VS.RRC.SuccConnEstab.Second 67190589 VS.RRC.SuccConnEstab.Third 67195587 VS.RRC.ManualDsac.Num 67195590 VS.RRC.AutoDsac.Num 67195964 RRC.AttConnEstab.MBMSRep 67195965 RRC.AttConnEstab.MBMSPtp 67195966 RRC.SuccConnEstab.MBMSRep 67195967 RRC.SuccConnEstab.MBMSPtp 67196198 67196199 67196200 67196201
VS.RRC.AttConnEstab.EDCH VS.RRC.AttConnEstab.HSDSCH VS.RRC.SuccConnEstab.EDCH VS.RRC.SuccConnEstab.HSDSCH
ork as invalid parameters.
pported compatibility problem of UE in some unknown scenarios ink physical layers are not synchronized during the RB setup process. The rooted reason is poor coverage ously occur and they are incompatible.It is mainly caused by UE defects cess nesting
ly occurs. It is mainly caused by poor coverage, so UE cannot receive the RB setup request message
Description Count of CS Domain RAB Assignment Failed in setting up Count of CS Domain RAB Assignment Failed in setting up Count of CS Domain RAB Assignment Failed in setting up Number of CS RABs Unsuccessfully Established due to Relocation Count of CS Domain RAB Assignment RAB Failed in setting up Count of RAB which fails to establish RAB assignment request in CS domain due to RNC admission algorithem rejection which is caused by DL Iub bandwidth congestion Count of RAB which fails to establish RAB assignment request in CS domain due to RNC admission algorithem rejection which is caused by UL Iub bandwidth congestion Count of CS Domain RAB Assignment RAB Failed in setting up Count of CS Domain RAB Assignment RAB Failed in setting up Number of CS RABs unsuccessfully setup by RAB assignment request in each cell caused by unavailable resources because of UL CE. Number of CS RABs unsuccessfully setup by RAB assignment request in each cell caused by unavailable resources because of DL CE. Count of CS Domain RAB Assignment RAB Failed in setting up
Description Number of requesting to redirect a RRC connection request message received in an original cell to a target cell Number of RRC Connection Try Again and Succeed Count of RRC Connection Request message in DRD process Average Number of UEs in CELL_DCH State Average Number of UEs in CELL_FACH State Average Number of UEs in EFACH State Average Number of UEs in CELL_PCH State Count of the maximum delay time of RRC Connection Setup mapped on DCH RRC Connection Setup Delay Time on DCH Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request
Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Number of Initiated RRC Connection Setups Number of RRC Connection Setup Successes Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request< Detach> Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Request Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success< Detach>
Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Count of RRC Connection Establishment Success Number of RRC Connection Requests Number of RRC Connection Setup Successes Number of RRC Connection Requests Number of RRC Connection Setup Successes Count of RRC Connection Establishment Success Number of RRC Connection Request Number of RRC Connection Setup Successes on first Connection req Number of RRC Connection Setup Successes on second Connection req Number of RRC Connection Setup Successes on third Connection req Number of manual DSAC Number of auto DSAC Number of RRC Connection Request because of MBMS Reception Number of RRC Connection Request because of PTP RB Request Number of RRC Connection Setup Successes because of MBMS Reception Number of RRC Connection Setup Successes because of PTP RB Request Number of UL over E-DCH Connection Requests Number of DL over HS-DSCH Connection Requests Number of UL over E-DCH Connection Setup Successes Number of DL over HS-DSCH Connection Setup Successes
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 Channel Switch Failure Channel Switch Failure Abnormal RANAP Release Abnormal RANAP Release IFHO Failure IRAT Cell Change Failure IRAT HO Failure Radio Link Fail Release Soft Handover Failure UE Lost at Unspecified RF UE Lost at Unspecified RF UE Lost due to Downlink Bad Quality UE Lost due to Low Coverage UE Lost due to UL Interference UE Lost due to UL Interference
Counter VS.FailRBRel.CellUpd VS.FailRBRel.InvCfg VS.FailRBRel.NoReply
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
Radio ReleaseDueToUtranGeneratedReason Procedure Timeout MISC NoResourceAvailable Radio ReleaseDueToUtranGeneratedReason IFHO Timer Expired IRAT Cell Change Timer Expired IRAT HO Outgoing Timer Expired RLC Unrecoverable Error ASU Complete for Addition Not Received RLC Max Retranmission Reached RCS Timer Expired Radio RadioConnectionWithUELost Radio RadioConnectionWithUELost RLC Max Retranmission Reached RCS Timer Expired
Description Cell update occurred Invalid configuration No reply
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
CDR type
Due to air interface
Not due to air interface OM interference Causes due to RAB preemption Causes due to UTRAN Uplink RLC reset Downlink RLC reset
Uplink synchronization failure
Downlink synchronization failure
No response of UU port Other RF causes
Abnormal AAL2 link Abnormal GTPU Other causes
SRB reset occurs probably if the UE fails to receive the following messages in downlink: l Security mode process l Authentication and encryption process l Measurement control l Active set update l Physical channel reconfiguration l Transport channel reconfiguration l RB reset l Handover command from 3G to 2G (HANDOVER FROM UTRAN COMMAND) SRB reset occurs probably if the UE fails to receive the following messages in uplink: l Measurement report l Active set update complete l Physical channel reconfiguration complete l Transport channel reconfiguration complete l RB reconfiguration complete VS.RAB.Loss.CS.Norm VS.RAB.Loss.CS.Norm.AMR VS.Norm.Rel.CS.Str VS.HSPA.RAB.Loss.Norm.CS.Conv VS.RAB.Loss.VP.LIMIT VS.RAB.Loss.PS.Norm VS.Norm.Rel.PS.Conv VS.Norm.Rel.PS.Str Counter VS.RAB.RelReqCS.OM VS.RAB.RelReqCS.RABPreempt VS.RAB.RelReqCS.UTRANgen VS.RAB.RelReqPS.OM VS.RAB.RelReqPS.RABPreempt
Counter VS.RAB.Loss.CS.SRBReset VS.RAB.Loss.PS.SRBReset Counter VS.RAB.Loss.CS.Aal2Loss
Counter VS.RAB.Loss.CS.Congstion.CELL VS.RAB.Loss.PS.Congstion.CELL Counter VS.RAB.RelReqPS.BE.HSDPA.Cong.Golden VS.RAB.RelReqPS.BE.HSDPA.Cong.Silver VS.RAB.RelReqPS.BE.HSDPA.Cong.Copper VS.RAB.RelReqPS.BE.HSUPA.Cong.Golden VS.RAB.RelReqPS.BE.HSUPA.Cong.Silver VS.RAB.RelReqPS.BE.HSUPA.Cong.Copper
ID 67191786 67191787 67191788 67191789 67191790 67191791 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
Counter VS.RAB.AttRelCS.Conv VS.RAB.AttRelCS.Str 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 Counter VS.CN.RAB.Loss.CS
Counter VS.RAB.AttRelPS.Conv VS.RAB.AttRelPS.Str VS.RAB.AttRelPS.Inter VS.RAB.AttRelPS.Bkg Counter VS.RAB.AttRelPS.NetOptm VS.RAB.AttRelPS.NormRel VS.RAB.AttRelPS.OM VS.RAB.AttRelPS.RABPreempt VS.RAB.AttRelPS.UeInact VS.RAB.AttRelPS.Unsp VS.RAB.AttRelPS.UtranGen
Counter VS.CN.RAB.Loss.PS
Counter VS.HSDPA.OLC.UserRel
VS.LCC.OLC.UL.UserRel VS.LCC.OLC.DL.UserRel VS.LCC.OLC.HSUPA.UserRel
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
Cause RF
Expiration of process timer
Hardware failure Transport layer failure Subscribers are released by force by MML 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. Uplink RLC reset causes release of links, because the coverage quality (including missing neighbor cell and over mall handover area) is bad. Downlink SRB reset causes release of links, because the coverage quality (including missing neighbor cell and over mall handover area) is bad. 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. Downlink 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.
The UE air interface fails to respond the command transmitted by system, because the coverage is bad. It is due to RF causes and the coverage quality is bad. 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. 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. You need to analyze the abnormal call drop based on RNC logs.
and encryption process
el reconfiguration nel reconfiguration
mand from 3G to 2G (HANDOVER FROM UTRAN COMMAND)
te complete el reconfiguration complete nel reconfiguration complete tion complete Number of normally released CS RABs in the best cell Number of normally released CS RABs in the best cell (AMR) Number of normally released CS streaming RABs in the best cell Number of CS over HSPA RAB Release due to normal Loss in the best cell Number of normally released CS VP RABs triggered by RNC because VP is forbidden in target cell of SHO/HHO/Cell Update Number of normally released PS RABs in the best cell Number of normally released PS R99 conversational RABs in the best cell Number of normally released PS R99 streaming RABs in the best cell 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"
Description Number of released CS RABs due to signaling RLC reset in the best cell Number of released PS RABs due to signaling RLC reset in the best cell Feature ID WRFD-010510
Description Number of released CS RABs triggered by the RNC due to CELL congestion Number of released PS RABs triggered by the RNC due to CELL congestion Description Number of released golden user's PS BE RABs beared on HSDPA triggered by the RNC due to CELL congestion Number of released silver user's PS BE RABs beared on HSDPA triggered by the RNC due to CELL congestion Number of released copper user's PS BE RABs beared on HSDPA triggered by the RNC due to CELL congestion Number of released golden user's PS BE RABs beared on HSUPA triggered by the RNC due to CELL congestion Number of released silver user's PS BE RABs beared on HSUPA triggered by the RNC due to CELL congestion Number of released copper user's PS BE RABs beared on HSUPA triggered by the RNC due to CELL congestion Counter VS.Norm.Rel.CS.Conv.RB.64 VS.Norm.Rel.PS.BE.RB.0.32 VS.Norm.Rel.PS.BE.RB.32.64 VS.Norm.Rel.PS.BE.RB.64.144 VS.Norm.Rel.PS.BE.RB.144.384 VS.Norm.Rel.PS.CCH 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 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 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) Description Number of CS conversational service RABs requested to release in the best cell Number of CS streaming service RABs requested to release in the best cell 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 Feature ID WRFD-010510
Description Number of PS conversational service RABs requested to release in the best cell Number of PS streaming service RABs requested to release in the best cell Number of PS interactive service RABs requested to release in the best cell Number of PS background service RABs requested to release in the best cell Description Number of PS RABs requested to release in the best cell with the cause of "Network Optimization" Number of PS RABs requested to release in the best cell with the cause of "Normal Release" Number of PS RABs requested to release in the best cell with the cause of "O&M Intervention" Number of PS RABs requested to release in the best cell with the cause of "RAB Preempted" Number of PS conversational service RABs requested to release in the best cell with the cause of "User Inactivity" Number of PS RABs requested to release in the best cell with the cause of "Unspecified Failure" Number of PS RABs requested to release in the best cell with the cause of "Release due to UTRAN Generated Cause" Feature ID WRFD-010510
Description Number of HSDPA UEs Released due to Overload Congestion (Cell)
Number of UEs Released due to UL Overload Congestion (Cell) Number of UEs Released due to DL Overload Congestion (Cell) Number of HSUPA UEs Released due to Overload Congestion (Cell)
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
Corresponding signaling process RLC reset and RL Failure RB RECFG Expiration of PHY/TRCH/SHO/ASU HHO failure The transport failure between RNC and NodeB. NCP reports failure. FP synchronization failure. ALCAP report failure O&M intervention
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
oses the transmitter abnormally or uplink demodulation is asynchronous. To solve the problem, network coverage must be improved. In t he problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason. n some versions of RNC, normal release is recorded as abnormal release during the RB setup process. P_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are re
he problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.
P_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are re
k coverage must be improved. In the early network, call drops are mainly caused by this reason. by this reason.
. Therefore, these call drops are recorded in CS_RAB_DROP_OTHER. by this reason.
. Therefore, these call drops are recorded in PS_RAB_DROP_OTHER.
l l l
Abrupt transmission failure Abnormal NodeB equipment Abrupt breakdown of UE
RRC setup failure . RAB setup failure . RRC access failure . RAB access failure . RRC active failure . RAB active failure 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 VS.RAB.Loss.PS.RF VS.RAB.Loss.PS.RF.RLCRst VS.RAB.Loss.PS.RF.ULSync
VS.RAB.Loss.PS.RF.UuNoReply
VS.RAB.Loss.PS.RF.Oth
Counter VS.Abnorm.Rel.CS.Str VS.HSPA.RAB.Loss.Abnorm.CS.Conv
VS.Abnorm.Rel.PS.Conv VS.Abnorm.Rel.PS.Str
Counter VS.RAB.Loss.CS.AMR VS.RAB.Loss.CS.AMR.12.2 VS.RAB.Loss.CS.AMR.4.75 VS.RAB.Loss.CS.AMR.5.9 VS.RAB.Loss.CS.AMR.7.95 VS.RAB.Loss.CS.Conv64K VS.RAB.Loss.CS.AMRWB.12.65 VS.RAB.Loss.CS.AMRWB.8.85
Counter VS.RAB.Loss.PS.TRBReset
Counter VS.RAB.Loss.CS.AMR VS.RAB.Loss.CS.AMR.12.2 VS.RAB.Loss.CS.AMR.4.75 VS.RAB.Loss.CS.AMR.5.9 VS.RAB.Loss.CS.AMR.7.95 VS.RAB.Loss.CS.Conv64K VS.RAB.Loss.CS.AMRWB.12.65 VS.RAB.Loss.CS.AMRWB.8.85
Counter VS.RAB.Loss.PS.TRBReset
Counter VS.RAB.Loss.PS.GTPULoss
Counter VS.Abnorm.Rel.PS.BE.RB.0.32
VS.Abnorm.Rel.PS.BE.RB.32.64
VS.Abnorm.Rel.PS.BE.RB.64.144
VS.Abnorm.Rel.PS.BE.RB.144.384
VS.Abnorm.Rel.PS.CCH
Counter VS.RAB.Loss.PS.UEGen
ID 67196302
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 Number of the PS domain RABs released due to RF failures in the best cell Number of PS domain RABs released due to RF failures (RLC Reset) in the best cell Number of PS domain RABs released due to RF failures (Uplink Synchronization Fail) in the best cell Number of PS domain RABs released due to RF failure (Failure in the Radio Interface Procedure) in the best cell Number of PS domain RABs released due to RF failures (other causes) in the best cell Description Number of abnormally released CS streaming RABs in the best cell Number of abnormally released CS RAB which bears on HSPA in the best cell
Number of abnormally released PS R99 conversational RABs in the best cell Number of abnormally released PS R99 streaming RABs in the best cell Description Number of CS AMR RABs abormally released Number of released CS AMR 12.2 kbit/s RABs abormally released Number of released CS AMR 4.75 kbit/s RABs abormally released Number of released CS AMR 5.9 kbit/s RABs abormally released Number of released CS AMR 7.95 kbit/s RABs abormally released Number of released CS Conversation 64 kbit/s RABs abormally released Number of released CS AMRWB 12.65kbit/s abormally released Number of released CS AMRWB 8.85 kbit/s RABs abormally released Feature ID WRFD-010510
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Description Number of CS AMR RABs abormally released Number of released CS AMR 12.2 kbit/s RABs abormally released Number of released CS AMR 4.75 kbit/s RABs abormally released Number of released CS AMR 5.9 kbit/s RABs abormally released Number of released CS AMR 7.95 kbit/s RABs abormally released Number of released CS Conversation 64 kbit/s RABs abormally released Number of released CS AMRWB 12.65kbit/s abormally released Number of released CS AMRWB 8.85 kbit/s RABs abormally released Feature ID
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Feature ID
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
WRFD-010510
WRFD-010510
Description Number of abnormally released PS BE service RABs in the best cell(DL bit rate in (0,32] kbit/s, RRC state is CELL_DCH, R99 user only) Number of abnormally released PS BE service RABs in the best cell(DL bit rate in (32,64] kbit/s, RRC state is CELL_DCH, R99 user only) Number of abnormally released PS BE service RABs in the best cell(DL bit rate in (64,144] kbit/s, RRC state is CELL_DCH, R99 user only) Number of abnormally released PS BE service RABs in the best cell(DL bit rate in (144,384] kbit/s, RRC state is CELL_DCH, R99 user only) Number of abnormally released PS RABs in the best cell(the UE status is CELL_FACH) Feature ID WRFD-010510
Counter VS.Norm.Rel.PS.0kbps.Timeout
Feature Name 3.4/6.8/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release
Counter VS.RAB.RelReqCS.OM VS.RAB.RelReqCS.RABPreempt VS.RAB.RelReqCS.UTRANgen VS.RAB.RelReqPS.OM VS.RAB.RelReqPS.RABPreempt VS.RAB.Loss.CS.RF
VS.RAB.Loss.PS.RF
VS.RAB.Loss.CS.Abnorm
VS.RAB.Loss.PS.Abnorm
VS.RAB.Loss.PS.RF.RLCRst
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" VS.RAB.Loss.CS.RF.RLCRst VS.RAB.Loss.CS.RF.Oth VS.RAB.Loss.CS.RF.ULSync VS.RAB.Loss.CS.RF.UuNoReply VS.RAB.Loss.PS.RF.RLCRst VS.RAB.Loss.PS.RF.Oth VS.RAB.Loss.PS.RF.ULSync VS.RAB.Loss.PS.RF.UuNoReply VS.RAB.RelReqCS.OM VS.RAB.RelReqCS.RABPreempt VS.RAB.RelReqCS.UTRANgen VS.RAB.Loss.CS.Aal2Loss VS.RAB.Loss.CS.Congstion.CELL VS.RAB.RelReqPS.OM VS.RAB.RelReqPS.RABPreempt VS.RAB.Loss.PS.GTPULoss VS.RAB.Loss.PS.Congstion.CELL VS.RAB.Loss.PS.SRBReset VS.RAB.Loss.PS.TRBReset
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
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
Configuration nonsupport
The UE thinks the content of active set update for RNC to add/delete links does not support SHO. This scenario seldom exists in commercial networks.
Synchronization reconfiguration nonsupport
The UE feeds back that the SHO (or softer handover) for RNC to add/delete links is incompatible with other subsequent processes. The RNC guarantees serial processing upon flow processing. This cause is due to the problematic UE.
Invalid configuration
The UE thinks the content of active set update for RNC to add/delete links is invalid. This scenario seldom exists in commercial networks.
No response from UE
The RNC fails to receive response to active set update command for adding/deleting links. This is a major cause to SHO (or softer handover) failure. It occurs in areas with weak coverage and small handover area. RF optimization must be performed in the areas.
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
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;
ID
Counter 67180483 VS.SoHO.ASU.AttRLAdd 67180484 VS.SoHO.ASU.SuccRLAdd 67180485 VS.SoHO.ASU.FailRLAdd.CfgUns 67180486 VS.SoHO.ASU.FailRLAdd.Isr 67180488 67180489 67180490 67180491 67180498 67180499 67180500
VS.SoHO.ASU.FailRLAdd.InvCfg VS.SoHO.ASU.FailRLAdd.NoRepl VS.SoHO.ASU.AttRlDel VS.SoHO.ASU.SuccRlDel SHO.AttRLAddUESide SHO.SuccRLAddUESide SHO.FailRLAddUESide.CfgUnsup
67180501 SHO.FailRLAddUESide.Isr 67180503 SHO.FailRLAddUESide.InvCfg
67180504 67180508 67180509 67192562 67193563 67193564 67180519 67180520 67180521
SHO.FailRLAddUESide.NoReply SHO.AttRLDelUESide SHO.SuccRLDelUESide VS.SHO.SigOnly.AttOut VS.SHO.SigOnly.SuccOut VS.SHO.AttRLAdd.Prep VS.SHO.AMR.AttOut VS.SHO.AMR.SuccOut VS.SHO.CS64.AttOut
67180522 VS.SHO.CS64.SuccOut 67180523 VS.SHO.PS64.AttOut 67180524 VS.SHO.PS64.SuccOut 67180525 VS.SHO.PS128.AttOut 67180526 VS.SHO.PS128.SuccOut 67190758 VS.SHO.PS144.AttOut 67190759 VS.SHO.PS144.SuccOut 67180527 VS.SHO.PS384.AttOut 67180528 VS.SHO.PS384.SuccOut 67203936 67203937 67203938 67203939 67203940 67203941
VS.SHO.AS.1RL VS.SHO.AS.2RL VS.SHO.AS.3RL VS.SHO.AS.4RL VS.SHO.AS.5RL VS.SHO.AS.6RL
ID
Counter 67189909 VS.SHO.SuccASU.N 67189910 VS.SHO.AttASU.N 67189911 VS.SHO.FailASU.NRply.N 67183489 67183490 67189912 67183491
VS.HHO.AttOutInterCell.N VS.HHO.SuccOutInterCell.N VS.HHO.FailOutInterCellNRlyN VS.SHO.AddRLAtt.NCell
67183492 VS.SHO.AddRLSucc.NCell 67183493 VS.SHO.DelRLAtt.NCell 67183494 VS.SHO.DelRLSucc.NCell 67183499 VS.SHO.ReplaceRLAtt.NCell 67183500 VS.SHO.ReplaceRLSucc.NCell
67190708 VS.HSDPA.HHO.NoChR.Att.N 67190709 VS.HSDPA.HHO.NoChR.Succ.N 67190710 VS.HSDPA.ServCellChg.Att.N 67190711 VS.HSDPA.ServCellChg.Succ.N
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
Description Number of RL Additions Attempt in Softer Handover Number of Successful RL Additions in Softer Handover Count of Softer Handover Radio Link Addition Failure Count of Softer Handover Radio Link Addition Failure Count of Softer Handover Radio Link Addition Failure Number of RL Addition Failures in Softer Handover due to No Response Number of Attempted RL Deletions in Softer Handover Number of RL Successful Deletions in Softer Handover Number of RL Additions Attempt for Soft Handover Number of Successful RL Additions in Soft Handover Count of Soft Handover Radio Link Addition Failure Count of Soft Handover Radio Link Addition Failure Count of Soft Handover Radio Link Addition Failure
Number of RL Addition Failures in Soft Handover due to No Response Number of Attempted RL Deletions in Soft Handover Number of Successful RL Deletions in Soft Handover Sho With Sig Only Att Sho With Sig Only Succ Prep of Sho With Rl Add Count of CS Domain Soft Handover Count of CS Domain Soft Handover Success Count of CS Domain Soft Handover Count of CS Domain Soft Handover Success Count of PS Domain Soft Handover Count of PS Domain Soft Handover Success Count of PS Domain Soft Handover Count of PS Domain Soft Handover Success Count of PS Domain Soft Handover Count of PS Domain Soft Handover Success Count of PS Domain Soft Handover Count of PS Domain Soft Handover Success Average Number of UEs with One RL Average Number of UEs with Two RLs Average Number of UEs with Three RLs Average Number of UEs with Four RLs Average Number of UEs with Five RLs Average Number of UEs with Six RLs Description Number of Successful Soft Handovers between Neighboring Cells Number of Attempted Soft Handovers between Neighboring Cells Number of Soft Handovers Fail between Neighboring Cells due to Waiting Active Set Update Response Timeout Number of Attempted Hard Handovers between Neighboring Cells Number of Successful Hard Handovers between Neighboring Cells Number of Hard Handovers Fail between Neighboring Cells due to Timeout Number of Attempted RL Additions in Soft Handover between Neighboring Cells Number of Successful RL Additions in Soft Handover between Neighboring Cells Number of Attempted RL Deletions in Soft Handover between Neighboring Cells Number of Successful RL Deletions in Soft Handover between Neighboring Cells Number of Attempted RL Replacements in Soft Handover between Neighboring Cells Number of Successful RL Replacements in Soft Handover between Neighboring Cells
Number of HSDSCH Service HHO Request without channel change between Neighboring Cells Number of HSDSCH Service HHO Success without channel change between Neighboring Cells Number of HSDSCH Service Cell Change Request between Neighboring Cells Number of HSDSCH Service Cell Change success between Neighboring Cells
ate the problem, RNC logs must be used for further analysis.
ed by some handsets.
age is poor or soft handover area is small, soft handover failure easily occurs.
ome handsets.
erage 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 RNC-level inter-RAT outgoing handover preparation failure
Expiration of waiting for SRNS relocation command
SRNS relocation cancellation SRNS relocation expiration SRNS relocation failure in target CN/RNC/system
Unknown target RNC Unavailable resource Other causes
Cell-level inter-RAT outgoing handover preparation failure SRNS relocation expiration SRNS relocation failure in target CN/RNC/system SRNS relocation nonsupport in target CN/RNC/system Other causes
RNC-level/CELL-level inter-RAT outgoing handover failure Configuration nonsupport PCH failure
Other causes
IRATHO.FailRelocPrepOutCS.TAlExp IRATHO.FailRelocPrepOutCS.TgtFail IRATHO.FailRelocPrepOutCS.ReloNoSup IRATHO.FailRelocPrepOutCS.HigherTrafficLod IRATHO.FailRelocPrepOutCS.NoResAvail IRATHO.FailRelocPrepOutCS.UKnowRNC Counter IRATHO.FailOutCS.CfgUnsupp IRATHO.FailOutCS.PhyChFail Counter IRATHO.FailIncCS.TRNCSysFailReloc IRATHO.FailIncCS.TRNCSysRelocUnsupp IRATHO.FailIncCS.ResUnavail IRATHO.FailIncCS.HigherTrafficLod Counter IRATHO.FailOutPSUTRAN.CfgUnsupp IRATHO.FailOutPSUTRAN.PhyChFail Counter VS.IRATHO.Reloc.FailPrepOutPS.TAlExp VS.IRATHO.Reloc.FailPrepOutPS.TgtFail VS.IRATHO.Reloc.FailPrepOutPS.ReloNoSup VS.IRATHO.Reloc.FailPrepOutPS.TLoadHigher VS.IRATHO.Reloc.FailPrepOutPS.NoResAvail VS.IRATHO.Reloc.FailPrepOutPS.UKnowRNC Counter VS.IRATHO.Reloc.FailOutPSUTRAN.CfgUnsupp VS.IRATHO.Reloc.FailOutPSUTRAN.PhyChFail Counter VS.IRATHO.Reloc.FailPrepInPS.TgtFail VS.IRATHO.Reloc.FailPrepInPS.ReloNoSup VS.IRATHO.Reloc.FailPrepInPS.ResUnavail VS.IRATHO.Reloc.FailPrepInPS.TLoadHigher Counter VS.IRATHO.Reloc.FailInPS.NRply ID 67183495 67183496 67189907
67183497 67183498 67189908
RNC-level/CELL-level PS inter-RAT outgoing handover preparation failure Configuration nonsupport PCH failure Radio network layer cause Transport layer cause Other causes
ID 67189729 67189730 67189732 67189739
67189740
67189741
67189742
67189743
67189744 67189745 67189746 67189747 67189748 67189749 67189750 67189751 67189752 67189753 67189754 67189755 67189756 67189757 67189758 67189759 67189760 67189761 67189762 67189763 67190410 67190411 67190412 67190476 67190477 67190413 67190414 67190593
67190856 67190857 67190858 67190859 67191155 67191156 67192506 67192507 67192186
67192187
67192654 67192655 67192656 67192657 67192658
67192659
67192660 67192661 67192662 67192663 67192664 67192665 67192666 67192667
67192668
67192669
67192670 67192671 67192672 67192673 67192674 67192675 67192676 67192677 67192678 67192679 67192680 67192681
67192682 67193399 67193400 67193405 67193406 67193407 67193408 67196299 67196300
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.
r preparation failure The CN does not respond the corresponding command for handover preparation request, because the CN parameter configuration or the corresponding link connection is problematic. To solve this problem, analyze the causes according to CN and BSS signaling tracing. After the RNC requests handover preparation, it receives the release command from CN. This includes the following two cases: l The
inter-RAT handover request occurs during signaling process like location update, so the flow is not complete before location update is complete. Finally the CN sends a release message. l The subscribers that are calling hang UE before handover preparation, so the CN sends a release message. The previous two cases, despite incomplete handover, are normal nesting flows. It corresponds to incorrect configuration of CN, so you must analyze the causes according to CN and BSS signaling tracing. It corresponds to incorrect configuration of CN or BSS nonsupport, so you must analyze the causes according to CN and BSS signaling tracing. It corresponds to incorrect configuration of MSC parameters without information like LAC of target cell, so you must check the parameter configuration. It occurs easily after adjustment of 2G networks. It corresponds to incorrect configuration of MSC parameters or unavailable BSC resources, so you must analyze the causes according to CN and BSS signaling tracing. Analyze the causes according to CN and BSS signaling tracing.
preparation failure The CN parameter configuration or the corresponding link connection is problematic, so you must analyze the causes according to CN and BSS signaling tracing. It corresponds to incorrect configuration of CN or BSS nonsupport, so you must analyze the causes according to CN and BSS signaling tracing. The BSC fails to support some parameters of inter-RAT handover request, so you must analyze the causes according to CN and BSS signaling tracing. Analyze the causes according to CN and BSS signaling tracing.
ng handover failure The UE fails to support the handover command in the network, so the UE is incompatible with the handover command. The 2G signals are weak or the interference is strong so the UE fails to connect to the network.
Analyze the problem further according to CHR logs and CN/BSS signaling tracing.
TRELOCalloc expiry Relocation Failure in Target CN/RNC or Target System Relocation not supported in Target RNC or Target system Traffic Load In The Target Cell Higher Than In The Source Cell No Resource Available Unknown Target RNC Description Configuration Unsupported Physical Channel Failure Description Relocation failure in target CN/RNC or target system Relocation not supported in target RNC or target system No resource available Traffic Load In The Target Cell Higher Than In The Source Cell Description Configuration unacceptable Physical channel failure Description TRELOCalloc expiry Relocation Failure in Target CN/RNC or Target System Relocation not supported in Target RNC or Target system Traffic Load In The Target Cell Higher Than In The Source Cell No Resource Available Unknown Target RNC Description Configuration Unsupported Physical Channel Failure Description Relocation failure in target CN/RNC or target system Relocation not supported in target RNC or target system No resource available Traffic Load In The Target Cell Higher Than In The Source Cell Feature ID WRFD-02030802 Counter
VS.IRATHO.AttOutCS.N VS.IRATHO.SuccOutCS.N VS.IRATHO.FailOutCS.UEF.N
VS.IRATHO.AttOutPSUTRAN.N VS.IRATHO.SuccOutPSUTRAN.N VS.IRATHO.FaiOutPSUTRAN.UEFN
tgoing handover preparation failure The UE fails to support the handover command of the network, because the UE is incompatible with the command. The 2G signals are weak or the interference is strong, so the UE fails to access the network. The UE is probably incompatible. The UE detects that the sequence number of SNQ in the AUTN message is correct, so the handover fails. The value is synchronization failure. The corresponding transport link is abnormal. You must analyze the causes according to CN and BSS signaling tracing.
Counter
VS.IRATHO.SuccOutCs.DR VS.IRATHO.ReqRelocOutCS.DR VS.IRATHO.SucRelocOutCS.DR VS.IRATHO.Load.AttRelocPrepOutCS VS.IRATHO.Load.SuccRelocPrepOutCS VS.IRATHO.Load.SuccOutCS VS.IRATHO.Load.AttOutPSUTRAN VS.IRATHO.Load.SuccOutPSUTRAN
VS.IRATHO.RF.AttRelocPrepOutCS VS.IRATHO.RF.SuccRelocPrepOutCS VS.IRATHO.RF.SuccOutCS VS.IRATHO.RF.AttOutPSUTRAN VS.IRATHO.RF.SuccOutPSUTRAN IRATHO.AttRelocPrepOutCS IRATHO.SuccRelocPrepOutCS IRATHO.FailRelocPrepOutCS.TAlExp IRATHO.FailRelocPrepOutCS.TgtFail IRATHO.FailRelocPrepOutCS.ReloNoSup IRATHO.AttOutCS IRATHO.SuccOutCS IRATHO.FailOutCS.CfgUnsupp IRATHO.FailOutCS.PhyChFail IRATHO.AttIncCS IRATHO.SuccIncCS IRATHO.FailIncCS.TRNCSysFailReloc IRATHO.FailIncCS.TRNCSysRelocUnsupp IRATHO.FailIncCS.ResUnavail IRATHO.SuccOutPSUE VS.IRATHO.FailIncCS.NRply IRATHO.AttOutPSUTRAN IRATHO.SuccOutPSUTRAN IRATHO.FailOutPSUTRAN.CfgUnsupp IRATHO.FailOutPSUTRAN.PhyChFail VS.IRATHO.AttOutPSUE VS.IRATHO.PrepSuccCSIn VS.IRATHO.Service.AttRelocPrepOutCS
VS.IRATHO.Service.SuccRelocPrepOutCS VS.IRATHO.Service.SuccOutCS VS.IRATHO.Service.AttOutPSUTRAN VS.IRATHO.Service.SuccOutPSUTRAN VS.IRATHO.HSDPA.AttOutPSUTRAN VS.IRATHO.HSDPA.SuccOutPSUTRAN VS.HSUPA.IRATHO.SuccOutPSUTRAN VS.HSUPA.IRATHO.AttOutPSUTRAN IRATHO.FailRelocPrepOutCS.HigherTrafficLod
IRATHO.FailIncCS.HigherTrafficLod VS.IRATHO.Out.RelocPrep.SigOnly.Att VS.IRATHO.Out.RelocPrep.SigOnly.Succ VS.IRATHO.Out.SigOnly.Att VS.IRATHO.Out.SigOnly.Succ IRATHO.FailRelocPrepOutCS.NoResAvail IRATHO.FailRelocPrepOutCS.UKnowRNC VS.IRATHO.FailOutCS.Nrply VS.IRATHO.CCO.FailOutPSUTRAN.Nrply VS.IRATHO.Reloc.AttPrepOutPS VS.IRATHO.Reloc.SuccPrepOutPS VS.IRATHO.Reloc.AttOutPSUTRAN VS.IRATHO.Reloc.SuccOutPSUTRAN VS.IRATHO.Reloc.FailPrepOutPS.TAlExp VS.IRATHO.Reloc.FailPrepOutPS.TgtFail
VS.IRATHO.Reloc.FailPrepOutPS.ReloNoSup VS.IRATHO.Reloc.FailPrepOutPS.TLoadHigher VS.IRATHO.Reloc.FailPrepOutPS.NoResAvail VS.IRATHO.Reloc.FailPrepOutPS.UKnowRNC VS.IRATHO.Reloc.FailOutPSUTRAN.CfgUnsupp VS.IRATHO.Reloc.FailOutPSUTRAN.PhyChFail VS.IRATHO.Reloc.FailOutPSUTRAN.NRply VS.IRATHO.Reloc.AttPrepInPS VS.IRATHO.Reloc.SuccPrepInPS VS.IRATHO.Reloc.SuccInPS VS.IRATHO.Reloc.FailPrepInPS.TgtFail VS.IRATHO.Reloc.FailPrepInPS.ReloNoSup VS.IRATHO.Reloc.FailPrepInPS.ResUnavail VS.IRATHO.Reloc.FailPrepInPS.TLoadHigher VS.IRATHO.Reloc.FailInPS.NRply VS.IRATHO.OutCS.MeasTimeOut VS.IRATHO.OutPS.MeasTimeOut VS.IRATHO.CS.Out.TrigRscp VS.IRATHO.CS.Out.TrigEcIo VS.IRATHO.PS.Out.TrigRscp VS.IRATHO.PS.Out.TrigEcIo VS.IRATHO.CS.MBDR.RelocAttOut VS.IRATHO.CS.MBDR.RelocSuccOut
ecause the data configuration or link connection of core network is incorrect. To locate the problem, track the signaling of core network a t RNC or Target System (cause value) because BSC does not support some parameters of handover requests. To locate the problem, track core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location up e) because the data configuration of MSC is incorrect or there is no available resource in BSC. To locate the problem, track the signaling of ) because the data configuration of MSC is incorrect or the LAC of target cell is not configured. ble because the data configuration is incorrect or target BSC does not support the handover. to the handover prepare request. This may be caused by incorrect data configuration or link connection of core network.
nter-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 inter ecause UE does not support the handover request. This reason may be mainly caused by abnormal UE. from core network. However, the cause is not Normal Release because the link is released abnormally due to other reasons. equest because network coverage is poor. yze the RNC logs.
Feature Name PS Handover Between UMTS and GPRS Description Number of Attempted CS Inter-RAT Outgoing Handovers between Neighboring Cells Number of Successful CS Inter-RAT Outgoing Handovers between Neighboring Cells Number of CS Domain Inter-RAT Handover from UTRAN Fail between Neighboring Cells
Number of Attempted PS Inter-RAT Outgoing Handovers between Neighboring Cells Number of Successful PS Inter-RAT Outgoing Handovers between Neighboring Cells Number of PS Domain Inter-RAT Handover from UTRAN Fail between Neighboring Cells
Description Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success due to Directed retry Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare request due to Directed retry Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare Success due to Directed retry Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare request due to Resource optimisation relocation or Reduce load in serving cell Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare Success due to Resource optimisation relocation or Reduce load in serving cell Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success due to Resource optimisation relocation or Reduce load in serving cell Count of PS Domain Inter-RAT Outgoing Handover From UTRAN Attempt due to Resource optimisation relocation or Reduce load in serving cell Count of PS Domain Inter-RAT Outgoing Handover From UTRAN Success due to Resource optimisation relocation or Reduce load in serving cell
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare request Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare Success Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success Count of PS Domain RAB Cell Change Order From UTRAN Prepare request Count of PS Domain RAB Cell Change Order From UTRAN Success Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare request Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare Success Count of CS Domain Inter-RAT Handover In Prepare Failure Count of CS Domain Inter-RAT Handover In Prepare Failure(Relocation Failure in Target CN/RNC or Target System) Count of CS Domain Inter-RAT Handover In Prepare Failure(Relocation not supported in Target RNC or Target system) Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Attempt Count of CS Domain Inter-RAT Outgoing Handover From UTRAN success. Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Fail Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Fail Count of CS Domain inter-RAT incoming handover To UTRAN Prepare request Count of CS Domain inter-RAT incoming handover To UTRAN Success Count of CS Domain inter-RAT incoming handover To UTRAN Prepare Fail Count of CS Domain inter-RAT incoming handover To UTRAN Prepare Fail Count of CS Domain inter-RAT incoming handover To UTRAN Prepare Fail Count of PS Domain RAB Cell Change Order To UTRAN Success by UE Initiation Number of CS domain inter-RAT incoming handover commit failures due to no response from the UE. Count of PS Domain RAB Cell Change Order From UTRAN Attempt by RNC Initiation Number of successful PS domain inter-RAT outgoing handovers initiated by RNC. Count of PS Domain Inter-RAT Handover Failure Count of PS Domain Inter-RAT Handover Failure Count of Successful PS Domain Inter-RAT Handover Initiated by UE Count of CS Domain inter-RAT incoming handover To UTRAN Success Count of CS Domain Inter-RAT Outgoing Handover Attempts to Services in serving cell
Count of CS Domain Inter-RAT Outgoing Handover Prepare Success due to Services in serving cell Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success due to Services in serving cell Count of PS Domain RAB Cell Change Order From UTRAN Prepare request Count of PS Domain RAB Cell Change Order From UTRAN Success Count of PS Domain RAB Cell Change Order From UTRAN Prepare request of HSDPAservice Count of PS Domain RAB Cell Change Order From UTRAN Success of HSDPAservice Count of PS Domain RAB Cell Change Order From UTRAN Success of HSUPAservice Count of PS Domain RAB Cell Change Order From UTRAN Prepare request of HSUPAservice Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Failure Count of CS Domain Inter-RAT Incoming Handover From GSM Failure Count of CS Domain Inter-RAT Outgoing Handover Prepare Attempts with Only Signal Connection Count of CS Domain Inter-RAT Outgoing Handover Prepare Success with Only Signal Connection Count of CS Domain Inter-RAT Outgoing Handover Attempts with Only Signal Connection Count of CS Domain Inter-RAT Outgoing Handover Success with Only Signal Connection Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Failure | Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Failure | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 
