Professional Documents
Culture Documents
VS.RRC.Rej.Redir.Inter.At
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
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
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.
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 th
Code Congestion.To locate the problem, start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm ma
Other,analyze call detail logs.
Counter
VS.RRC.FailConnEstab
VS.RRC.Rej.Redir.Inter.At
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
d, interference,netwrok capacity
may fail. To locate the problem, check whether there is any BTS alarm.
sis to analyze the code allocation and confirm major services.
Description
Number of RRC Connection Rejects <Cell>
Count of RRC Connection Reject due to Redirection
between interfrequency cell <Cell>
Count of RRC Connection Reject due to Redirection
between interfRAT cell <Cell>
Number of RRC Connection Rejects due to Network
Congestion <Cell>
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 <Cell>
Count of RRC Connection Reject because of
Congestion<Congestion because of POWER><Cell>
Number of RRC Connection Rejects due to Uplink CE
Resource Request Fail <Cell>
Number of RRC Connection Rejects due to Downlink CE
Resource Request Fail <Cell>
Count of RRC Connection Reject because of
Congestion<Congestion because of CODE><Cell>
Count of RRC Connection Reject <Radio Link Setup
Failure><Cell>
Count of RRC Connection Reject <TNL establishment
Failure><Cell>
Count of RRC Connection Reject due to Service Based
Redirection <Cell>
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 Description
RRC.AtConnEstab.OrgConvCall Originating Conversational Call
RRC.AtConnEstab.OrgStrCall Originating Streaming Call
RRC.AtConnEstab.OrgInterCall Originating Interactive Call
RRC.AtConnEstab.OrgBkgCall Originating Background Call
RRC.AtConnEstab.OgSubCall Originating Subscribed traffic Call
RRC.AtConnEstab.TmConvCall Terminating Conversational Call
RRC.AtConnEstab.TmStrCall Terminating Streaming Call
RRC.AtConnEstab.TmInterCall Terminating Interactive Call
RRC.AtConnEstab.TmBkgCall Terminating Background Call
RRC.AtConnEstab.EmgCall Emergency Call
RRC.AtConnEstab.IRATCelRes Inter-RAT cell re-selection
RRC.AtConnEstab.IRATCCO Inter-RAT cell change order
RRC.AtConnEstab.Reg Registration
RRC.AtConnEstab.Detach Detach
RRC.AtConnEstab.OgHhPrSig Originating High Priority Signalling
RRC.AtConnEstab.OgLwPrSig Originating Low Priority Signalling
RRC.AtConnEstab.CallReEst Call re-establishment
RRC.AtConnEstab.TmHhPrSig Terminating High Priority Signalling
RRC.AtConnEstab.TmLwPrSig Terminating Low Priority Signalling
RRC.AtConnEstab.Unknown Terminating - cause unknown
RRC.AtConnEstab.MBMSRep MBMS Reception
RRC.AtConnEstab.MBMSPtp MBMS PTP RB Request
Counter Feature ID
VS.RRC.FailConnEstab WRFD-010510
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.
aling Plane
M intervention
ser inactivity
epeated integrity checking failure
E generated signaling connection release
L out-of-synchronization
on re-establishment
that the RRC must be
n RRC Connected UE
ed under another RNC
Update. If the SRNS
the RRC connection
the current SRNC and redirected
Counter
RRC.AtConnRelDCCH.Congestion
RRC.AtConnRelDCCH.Preempt
RRC.AtConnRelDCCH.ReEstRej
RRC.AtConnRelDCCH.SigConReEst
RRC.AtConnRelDCCH.UsrInact
RRC.AtConnRelDCCH.Unspec
RRC.AtConnRelCCCH.Congestion
RRC.AtConnRelCCCH.Preempt
RRC.AtConnRelCCCH.ReEstRej
RRC.AtConnRelCCCH.SigConReEst
RRC.AtConnRelDCCH.NormRel
RRC.AtConnRelCCCH.NormRel
RRC.AtConnRelCCCH.UsrInact
RRC.AtConnRelCCCH.Unspec
RRC.FailConnReEstab.Cong
VS.RRC.ConnRel.CellUpd
Counter
VS.CellUpdt.RLFAIL.Max.Time
VS.CellUpdt.RLFAIL.Mean.Time
RRC.AtConnReEstab.RFLoss
RRC.SuccConnReEstab
RRC.FailConnReEstab.NoReply
VS.CellUpdt.AtConf
VS.CellUpdt.AtUpd.Msg
VS.CellUpdt.AtErrSRLC
VS.CellUpdt.AtErrTRLC
VS.CellUpdt.SuccErrTRLC
VS.CellUpdt.AtMbmsRecv
VS.CellUpdt.SuccMbmsRecv
VS.CellUpdt.AtPtpRbReq
VS.CellUpdt.SuccMbmsPtpRbReq
VS.CellUpdt.AtPrd
VS.CellUpdt.AtResel
VS.CellUpdt.AtRsa
VS.CellUpdt.AtPage
VS.CellUpdt.AtULDatTrsf
VS.CellUpdt.SuccPrd
VS.CellUpdt.SuccResel
VS.CellUpdt.SuccRsa
VS.CellUpdt.SuccPage
VS.CellUpdt.SuccULDatTrsf
VS.CellUpdt.SuccUpd
VS.CellUpdt.SuccRRCRel
Description
Number of RRC Connection Release on DCH because of Congestion
Number of RRC Connection Release on DCH because of Pre-emptive release
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 <Cell>
Number of Cell Updates Success due to Radio Link Failure <Cell>
Number of Cell Updates Fail due to Radio Link Failure <no Reply><Cell>
Number of CELL UPDATE CONFIRM Messages from SRNC <Cell>
Number of Cell Updates due to Prd and Resel <Cell>
Number of Cell Updates Due to SRB FAILURE <Cell>
Number of Cell Updates Due to TRB FAILURE <Cell>
Number of Successful Cell Updates due to TRB FAILURE <Cell>
Number of Cell Updates Due to Mbms Reception <Cell>
Number of Succ Cell Updates Due to Mbms Reception <Cell>
Number of Cell Updates Due to Mbms PtP RB Request <Cell>
Number of Succ Cell Updates Due to Mbms PtP RB Request <Cell>
Number of Cell Updates due to Periodical Cell Update <Cell>
Number of Cell Updates due to Cell Reselection <Cell>
Number of Cell Updates due to Re-Entering Service Area <Cell>
Number of Cell Updates due to Paging Response <Cell>
Number of Cell Updates due to Uplink Data Transmission <Cell>
Number of Successful Cell Updates due to Periodical Cell Update <Cell>
Number of Successful Cell Updates due to Cell Reselection <Cell>
Number of Successful Cell Updates due to Re-Entering Service Area <Cell>
CS RAB setup failures PARAM_CELL. RNC regards the parameters transmited by core network as invalid parameters.
CS RAB setup failures RELOC_CELL,relatedto migration
CS RAB setup failures TNL_CELL.IU transmission setup fails.
CS RAB setup failures CONG_CELL.RNC resource allocation failure.
CS RAB setup failures POWER_CONG_CELL
CS RAB setup failures CE_CONG_CELL
CS RAB setup failures CODE_CONG_CELL
CS RAB setup failures OTHER_CELL
CS RAB setup failures UNSUP_CELL.the QoS is not supported by RNC or RRM admission fails in RAB.
CFG_UNSUPP UE acknowledges the RB setup failure because of configuration unsupported compatibility proble
PHYCH_FAIL The RB setup failure may occur if FACH is migrated to DCH but downlink physical layers are not sy
SIMU_RECFG_INCOMP UE regards that the RB setup process and other processes simultaneously occur and they are inco
CELL_UPDT the Cell Update process occurs. The RB setup failure is caused by process nesting
CFG_INVALID UE regards the configured parameters are invalid ones
NO_RESPONSE UE does not acknowledge the RB setup request. This reason frequently occurs. It is mainly caused
OTHER
lParameter violation
lNon supported UTRAN capabilities
lRelocation triggered
lTransport connection failed to establish
lUnavailable resources
lProtocol error
Counter Description
VS.FailRBSetup.CfgUnsup Configuration unsupported
VS.FailRBSetup.PhyChFail Physical channel failure
VS.FailRBSetup.CellUpd Cell update occurred
VS.FailRBSetup.IncCfg Invalid configuration
VS.FailRBSetup.NoReply No reply
Counter Description
VS.FailRBRecfg.CfgUnsup Configuration unsupported
VS.FailRBRecfg.PhyChFail Physical channel failure
VS.FailRBRecfg.CellUpd Cell update occurred
VS.FailRBRecfg.IncCfg Invalid configuration
VS.FailRBRecfg.NoReply 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
Band.Cong of 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
Band.Cong of rejection by admission control due to uplink Iub bandwidth congestion
Counter Description
VS.RAB.FailEstPS.Par 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)
67189401 VS.DRD.RRC.Out.Succ
67192607 VS.RRC.Estab.DRDIn
67199662 VS.CellDCHUEs
67199661 VS.CellFACHUEs
67204156 VS.CellEFACHUEs
67199660 VS.CellPCHUEs
67179302 VS.RRC.ConnEstabTimeMax.DCH
67199510 VS.RRC.ConnEstabTimeMean.DCH
67179329 RRC.AtConnEstab.OrgConvCall
67179330 RRC.AtConnEstab.OrgStrCall
67179331 RRC.AtConnEstab.OrgInterCall
67179332 RRC.AtConnEstab.OrgBkgCall
67179334 RRC.AtConnEstab.TmConvCall
67179335 RRC.AtConnEstab.TmStrCall
67179336 RRC.AtConnEstab.TmInterCall
67179337 RRC.AtConnEstab.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.AtConnEstab.OgSubCall
67179338 RRC.AtConnEstab.EmgCall
67179339 RRC.AtConnEstab.IRATCelRes
67179340 RRC.AtConnEstab.IRATCCO
67179341 RRC.AtConnEstab.Reg
67179342 RRC.AtConnEstab.Detach
67179343 RRC.AtConnEstab.OgHhPrSig
67179344 RRC.AtConnEstab.OgLwPrSig
67179345 RRC.AtConnEstab.CallReEst
67179346 RRC.AtConnEstab.TmHhPrSig
67179347 RRC.AtConnEstab.TmLwPrSig
67179348 RRC.AtConnEstab.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 VS.RRC.AtConEst.DCH
67179634 VS.RRC.SuccConEst.DCH
67179649 VS.RRC.AtConEst.CCH
67179650 VS.RRC.SuccConEst.CCH
67179466 RRC.SuccConnEstab.EmgCall
67190586 VS.RRC.AtConnEstab.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.AtConnEstab.MBMSRep
67195965 RRC.AtConnEstab.MBMSPtp
67195966 RRC.SuccConnEstab.MBMSRep
67195967 RRC.SuccConnEstab.MBMSPtp
67196198 VS.RRC.AtConnEstab.EDCH
67196199 VS.RRC.AtConnEstab.HSDSCH
67196200 VS.RRC.SuccConnEstab.EDCH
67196201 VS.RRC.SuccConnEstab.HSDSCH
work as invalid parameters.
ntly 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<Congestion ><Cell>
Count of CS Domain RAB Assignment Failed in setting up<Radio
Network ><Cell>
Count of CS Domain RAB Assignment Failed in setting
up<Transmission Network ><Cell>
Number of CS RABs Unsuccessfully Established due to Relocation
<Cell>
Count of CS Domain RAB Assignment RAB Failed in setting
up<Non Supported Capabilities><Cell>
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<Failure in the Radio Interface Procedure><Cell>
Count of CS Domain RAB Assignment RAB Failed in setting
up<Congestion because of power><Cell>
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<Congestion because of code><Cell>
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 <Cell>
Average Number of UEs in CELL_FACH State <Cell>
Average Number of UEs in EFACH State <Cell>
Average Number of UEs in CELL_PCH State <Cell>
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<Originating Conversational
Call><Cell>
Count of RRC Connection Request<Originating Streaming
Call><Cell>
Count of RRC Connection Request<Originating Interactive
Call><Cell>
Count of RRC Connection Request<Originating Background
Call><Cell>
Count of RRC Connection Request<Terminating Conversational
Call><Cell>
Count of RRC Connection Request<Terminating Streaming
Call><Cell>
Count of RRC Connection Request<Terminating Interactive
Call><Cell>
Count of RRC Connection Request<Terminating Background
Call><Cell>
Count of RRC Connection Establishment Success<Originating
Conversational Call><Cell>
Count of RRC Connection Establishment Success<Originating
Streaming Call><Cell>
Count of RRC Connection Establishment Success<Originating
Interactive Call><Cell>
Count of RRC Connection Establishment Success<Originating
Background Call><Cell>
Count of RRC Connection Establishment Success<Originating
Subscribed traffic Call><Cell>
Count of RRC Connection Establishment Success<Terminating
Conversational Call><Cell>
Count of RRC Connection Establishment Success<Terminating
Streaming Call><Cell>
Count of RRC Connection Establishment Success<Terminating
Interactive Call><Cell>
Count of RRC Connection Establishment Success<Terminating
Background Call><Cell>
Number of Initiated RRC Connection Setups <Cell>
Number of RRC Connection Setup Successes <Cell>
Count of RRC Connection Request<Originating Subscribed traffic
Call><Cell>
Count of RRC Connection Request<Emergency Call><Cell>
Count of RRC Connection Request<inter-RAT Cell Reselect><Cell>
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
lOM intervention
lUser inactivity
lRepeated integrity checking failure
lUE generated signaling connection release
lRL out-of-synchronization
lOM intervention
lUTRAN generated reason
lRAB preempted
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
Counter
VS.RAB.AtRelCS.NetOpt
VS.RAB.AtRelCS.NormRel
VS.RAB.AtRelCS.OM
VS.RAB.AtRelCS.Preempt
VS.RAB.AtRelCS.UEInact
VS.RAB.AtRelCS.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
OM interference
No response of UU port
Other RF causes
Abnormal GTPU
Other causes
l Measurement control
l RB reset
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 coverage
CS call drops may be caused by link releasing due to downlink SRB reset. This reason is mainly caused by poor network coverag
If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occu
CS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process in
PS call drops may be caused by link releasing due to downlink TRB reset. This reason is mainly caused by poor network coverag
If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occu
PS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process in
Cause
RF
Hardware failure
Transport layer failure
Subscribers are released by force by MML
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.
l RB reset
l Measurement report
l Active set update complete
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)
ks because of poor network coverage (including adjacent cell missing, small handover area. As a result, UE closes the transmiter abnormal
ainly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network covera
son seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment. In some versions of RNC, norma
ersion 12). Such reasons as process interaction timeout and cell update failure are recorded in CS_RAB_DROP_OTHER. In practice, many cal
ainly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network covera
son seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment.
ersion 12). Such reasons as process interaction timeout and cell update failure are recorded in PS_RAB_DROP_OTHER. In practice, many cal
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
the transmiter abnormally or uplink demodulation is asynchronous. To solve the problem, network coverage must be improved. In the ear
oblem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.
me versions of RNC, normal release is recorded as abnormal release during the RB setup process.
HER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are recorded
oblem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.
HER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are recorded
ge must be improved. In the early network, call drops are mainly caused by this reason.
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
transmission failure
mal NodeB equipment
breakdown of UE
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
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
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)
Counter
VS.Norm.Rel.PS.0kbps.Timeout
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
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 rates
Number of released PS BE service RABs due to uplink signaling connection release in the best cell (max DL bitrate in (0,32] kbit
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
Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (64,14
Number of released PS R99 BE service RABs due to uplink signaling connection release in the best cell (max DL bit rate in (144,3
Number of released PS RABs with the cause of uplink signaling connection release in the best cell that belongs to the SRNC (RR
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)
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 insuffic
SHO_PREP_FP_SYNC_FAIL the synchronization of AAL2 and FP of lub interface fails
SHO_PREP_ FAIL_OTHER_CELL Soft handover prepare failure is caused by other reasons, such as insufficient R
The UE thinks the content of active set update for RNC to
add/delete links does not support SHO. This scenario seldom
Configuration nonsupport exists in commercial networks.
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.
Synchronization reconfiguration nonsupport This cause is due to the problematic UE.
The UE thinks the content of active set update for RNC to
add/delete links is invalid. This scenario seldom exists in
Invalid configuration commercial networks.
SHO_RL_ADD_FAIL_CFG_UNSUPP UE does not support to add radio links in RNC during the active set update. Thi
SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP UE feeds back that the soft handover process is incompatible with other concu
SHO_RL_ADD_FAIL_CFG_INVALID UE regards active set update of adding radio links in RNC as invalid configuratio
SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of adding rad
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 pro
SHO_RL_ADD_FAIL_CFG_INVALID UE regards the active set update of deleting radio links in RNC as invalid configu
SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of deleting ra
SHO_FAIL_OTHER_CELL Soft handover failure is caused by other reasons;
ID Counter
67180483 VS.SoHO.ASU.AtRLAdd
67180484 VS.SoHO.ASU.SuccRLAdd
67180485 VS.SoHO.ASU.FailRLAdd.CfgUns
67180486 VS.SoHO.ASU.FailRLAdd.Isr
67180488 VS.SoHO.ASU.FailRLAdd.InvCfg
67180489 VS.SoHO.ASU.FailRLAdd.NoRepl
67180490 VS.SoHO.ASU.AtRlDel
67180491 VS.SoHO.ASU.SuccRlDel
67180498 SHO.AtRLAddUESide
67180499 SHO.SuccRLAddUESide
67180500 SHO.FailRLAddUESide.CfgUnsup
67180501 SHO.FailRLAddUESide.Isr
67180503 SHO.FailRLAddUESide.InvCfg
67180504 SHO.FailRLAddUESide.NoReply
67180508 SHO.AtRLDelUESide
67180509 SHO.SuccRLDelUESide
67192562 VS.SHO.SigOnly.AtOut
67193563 VS.SHO.SigOnly.SuccOut
67193564 VS.SHO.AtRLAdd.Prep
67180519 VS.SHO.AMR.AtOut
67180520 VS.SHO.AMR.SuccOut
67180521 VS.SHO.CS64.AtOut
67180522 VS.SHO.CS64.SuccOut
67180523 VS.SHO.PS64.AtOut
67180524 VS.SHO.PS64.SuccOut
67180525 VS.SHO.PS128.AtOut
67180526 VS.SHO.PS128.SuccOut
67190758 VS.SHO.PS144.AtOut
67190759 VS.SHO.PS144.SuccOut
67180527 VS.SHO.PS384.AtOut
67180528 VS.SHO.PS384.SuccOut
67203936 VS.SHO.AS.1RL
67203937 VS.SHO.AS.2RL
67203938 VS.SHO.AS.3RL
67203939 VS.SHO.AS.4RL
67203940 VS.SHO.AS.5RL
67203941 VS.SHO.AS.6RL
ID Counter
67189909 VS.SHO.SuccASU.N
67189910 VS.SHO.AtASU.N
67189911 VS.SHO.FailASU.NRply.N
67183489 VS.HHO.AtOutInterCell.N
67183490 VS.HHO.SuccOutInterCell.N
67189912 VS.HHO.FailOutInterCellNRlyN
67183491 VS.SHO.AddRLAt.NCell
67183492 VS.SHO.AddRLSucc.NCell
67183493 VS.SHO.DelRLAt.NCell
67183494 VS.SHO.DelRLSucc.NCell
67183499 VS.SHO.ReplaceRLAt.NCell
67183500 VS.SHO.ReplaceRLSucc.NCell
67190708 VS.HSDPA.HHO.NoChR.At.N
67190709 VS.HSDPA.HHO.NoChR.Succ.N
67190710 VS.HSDPA.ServCellChg.At.N
67190711 VS.HSDPA.ServCellChg.Succ.N
nsmission bandwidth is insufficient.
r reasons, such as insufficient RNC resource, radio resource admission reject, and RNC link state reject. To locate the problem, RNC logs mu
uring the active set update. This reason seldom exists in a commercial network.
incompatible with other concurrent processes when radio links are added in RNC.The problem is mainly caused by some handsets.
ks in RNC as invalid configuration.
active set update of adding radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover a
C during the active set update.
atible with other concurrent processes when radio links are deleted in RNC.The problem is mainly caused by some handsets.
io links in RNC as invalid configuration.
active set update of deleting radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover
Description
Number of RL Additions Attempt in Softer Handover <Cell>
Number of Successful RL Additions in Softer Handover <Cell>
Count of Softer Handover Radio Link Addition Failure<Configuration Unsupported>
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
overage is poor or soft handover area is small, soft handover failure easily occurs.
by some handsets.
coverage is poor or soft handover area is small, soft handover failure easily occurs.
CS_INTERRAT_HO_PREP_FAIL_TARGET_FAIL
CS_INTERRAT_HO_PREP_FAIL_TALLOC_EXPIR
CS_INTERRAT_HO_PREP_FAIL_TARGET_UNSUPP
CS_INTERRAT_HO_PREP_FAIL_RELOC_ABORT
CS_INTERRAT_HO_PREP_FAIL_NO_RSRC_AVAIL
CS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGET
CS_INTERRAT_HO_PREP_FAIL_ REQINFNOTAVAI
CS_INTERRAT_HO_PREP_FAIL_NO_RSP
CS_INTERRAT_HO_ FAIL_UNSPEC
CS_INTERRAT_HO_ FAIL_PHYCN_FAIL
CS_INTERRAT_HO_ FAIL_ CFG_UNSUPP
CS_INTERRAT_HO_ FAIL_ RELOC_ABORT
CS_INTERRAT_HO_ FAIL_NO_RSP
CS_INTERRAT_HO_ FAIL_OTHER
Unavailable resource
Other causes
Cell-level inter-RAT outgoing handover preparation failure
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
Configuration nonsupport
PCH failure
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 con
CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) beca
After sending the handover prepare request, RNC receives the release message from core network. This may be caused by two
CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MSC
CS inter-RAT handover prepare failure is caused by Unknown Target RNC (cause value) because the data configuration of MSC i
CS inter-RAT handover prepare failure is caused by Requested Information Not Available because the data configuration is inco
CS inter-RAT handover prepare failure occurs because core network does not respond to the handover prepare request. This m
er 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 Thesubscribers 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.
r 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.
oing 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
Description
Configuration Unsupported
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.AtOutCS.N
VS.IRATHO.SuccOutCS.N
VS.IRATHO.FailOutCS.UEF.N
VS.IRATHO.AtOutPSUTRAN.N
VS.IRATHO.SuccOutPSUTRAN.N
VS.IRATHO.FaiOutPSUTRAN.UEFN
Counter
VS.IRATHO.SuccOutCs.DR
VS.IRATHO.ReqRelocOutCS.DR
VS.IRATHO.SucRelocOutCS.DR
VS.IRATHO.Load.AtRelocPrepOutCS
VS.IRATHO.Load.SuccRelocPrepOutCS
VS.IRATHO.Load.SuccOutCS
VS.IRATHO.Load.AtOutPSUTRAN
VS.IRATHO.Load.SuccOutPSUTRAN
VS.IRATHO.RF.AtRelocPrepOutCS
VS.IRATHO.RF.SuccRelocPrepOutCS
VS.IRATHO.RF.SuccOutCS
VS.IRATHO.RF.AtOutPSUTRAN
VS.IRATHO.RF.SuccOutPSUTRAN
IRATHO.AtRelocPrepOutCS
IRATHO.SuccRelocPrepOutCS
IRATHO.FailRelocPrepOutCS.TAlExp
IRATHO.FailRelocPrepOutCS.TgtFail
IRATHO.FailRelocPrepOutCS.ReloNoSup
IRATHO.AtOutCS
IRATHO.SuccOutCS
IRATHO.FailOutCS.CfgUnsupp
IRATHO.FailOutCS.PhyChFail
IRATHO.AtIncCS
IRATHO.SuccIncCS
IRATHO.FailIncCS.TRNCSysFailReloc
IRATHO.FailIncCS.TRNCSysRelocUnsupp
IRATHO.FailIncCS.ResUnavail
IRATHO.SuccOutPSUE
VS.IRATHO.FailIncCS.NRply
IRATHO.AtOutPSUTRAN
IRATHO.SuccOutPSUTRAN
IRATHO.FailOutPSUTRAN.CfgUnsupp
IRATHO.FailOutPSUTRAN.PhyChFail
VS.IRATHO.AtOutPSUE
VS.IRATHO.PrepSuccCSIn
VS.IRATHO.Service.AtRelocPrepOutCS
VS.IRATHO.Service.SuccRelocPrepOutCS
VS.IRATHO.Service.SuccOutCS
VS.IRATHO.Service.AtOutPSUTRAN
VS.IRATHO.Service.SuccOutPSUTRAN
VS.IRATHO.HSDPA.AtOutPSUTRAN
VS.IRATHO.HSDPA.SuccOutPSUTRAN
VS.HSUPA.IRATHO.SuccOutPSUTRAN
VS.HSUPA.IRATHO.AtOutPSUTRAN
IRATHO.FailRelocPrepOutCS.HigherTrafficLod
IRATHO.FailIncCS.HigherTrafficLod
VS.IRATHO.Out.RelocPrep.SigOnly.At
VS.IRATHO.Out.RelocPrep.SigOnly.Succ
VS.IRATHO.Out.SigOnly.At
VS.IRATHO.Out.SigOnly.Succ
IRATHO.FailRelocPrepOutCS.NoResAvail
IRATHO.FailRelocPrepOutCS.UKnowRNC
VS.IRATHO.FailOutCS.Nrply
VS.IRATHO.CCO.FailOutPSUTRAN.Nrply
VS.IRATHO.Reloc.AtPrepOutPS
VS.IRATHO.Reloc.SuccPrepOutPS
VS.IRATHO.Reloc.AtOutPSUTRAN
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.AtPrepInPS
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.RelocAtOut
VS.IRATHO.CS.MBDR.RelocSuccOut
because the data configuration or link connection of core network is incorrect. To locate the problem, track the signaling of core network a
et RNC or Target System (cause value) because BSC does not support some parameters of handover requests. To locate the problem, track
m core network. This may be caused by two reasons: (1) Inter-RAT handover is requested during the signaling processes, such as location up
ue) because the data configuration of MSC is incorrect or there is no available resource in BSC. To locate the problem, track the signaling of
e) because the data configuration of MSC is incorrect or the LAC of target cell is not configured.
able because the data configuration is incorrect or target BSC does not support the handover.
d to the handover prepare request. This may be caused by incorrect data configuration or link connection of core network.
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 inter
because UE does not support the handover request. This reason may be mainly caused by abnormal UE.
ge from core network. However, the cause is not Normal Release because the link is released abnormally due to other reasons.
e request because network coverage is poor.
lyze 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<Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
request due to Directed retry<Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
Success due to Directed retry<Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
request due to Resource optimisation relocation or Reduce load in serving
cell <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
Success due to Resource optimisation relocation or Reduce load in
serving cell <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success
due to Resource optimisation relocation or Reduce load in serving cell
<Cell>
Count of PS Domain Inter-RAT Outgoing Handover From UTRAN Attempt
due to Resource optimisation relocation or Reduce load in serving cell
<Cell>
Count of PS Domain Inter-RAT Outgoing Handover From UTRAN Success
due to Resource optimisation relocation or Reduce load in serving cell
<Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
request <Relocation desirable for radio reasons> <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
Success <Relocation desirable for radio reasons> <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success
<Relocation desirable for radio reasons> <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Prepare
request <Relocation desirable for radio reasons> <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Success
<Relocation desirable for radio reasons> <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
request <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Prepare
Success <Cell>
Count of CS Domain Inter-RAT Handover In Prepare
Failure<TRELOCalloc expiry>
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
<Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN
success.<Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN
Fail<Configuration Unsupported> <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN
Fail<Physical Channel Failure> <Cell>
Count of CS Domain inter-RAT incoming handover To UTRAN Prepare
request <Cell>
Count of CS Domain inter-RAT incoming handover To UTRAN
Success<Cell>
Count of CS Domain inter-RAT incoming handover To UTRAN Prepare
Fail<Relocation failure in target CN/RNC or target system><Cell>
Count of CS Domain inter-RAT incoming handover To UTRAN Prepare
Fail<Relocation not supported in target RNC or target system><Cell>
Count of CS Domain inter-RAT incoming handover To UTRAN Prepare
Fail<No resource available><Cell>
Count of PS Domain RAB Cell Change Order To UTRAN Success by UE
Initiation<Cell>
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<Cell>
Number of successful PS domain inter-RAT outgoing handovers initiated
by RNC.
Count of PS Domain Inter-RAT Handover Failure<Configuration
Unsupported>
Count of PS Domain Inter-RAT Handover Failure<Physical Channel
Failure>
Count of Successful PS Domain Inter-RAT Handover Initiated by UE
Count of CS Domain inter-RAT incoming handover To UTRAN Success
<Cell>
Count of CS Domain Inter-RAT Outgoing Handover Attempts to Services in
serving cell <Cell>
Count of CS Domain Inter-RAT Outgoing Handover Prepare Success due
to Services in serving cell <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Success
due to Services in serving cell <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Prepare
request <Services> <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Success
<Services> <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Prepare
request of HSDPAservice <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Success of
HSDPAservice <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Success of
HSUPAservice <Cell>
Count of PS Domain RAB Cell Change Order From UTRAN Prepare
request of HSUPAservice <Cell>
Count of CS Domain Inter-RAT Outgoing Handover From UTRAN Failure
<receive RELOCATION PREPARATION FAILURE with cause "Traffic Load
In The Target Cell Higher Than In The Source Cell"> <Cell>
f core network.
he network due to serious interference.2) Some parameters (such as ciphering mode) transmited to UE are inconsistent with that of BSC.
e to other reasons.
ss is complete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the
TCP
DCH UE
DL ADMSN DENY
ID
67189782
67202807
67202808
67202422
67202423
67199640
67199641
67199651
67199652
67199653
67199655
67199656
67199657
67199642
67199643
67199646
67199647
67199639
67199638
67199637
67199739
67199740
67199741
67204155
67204753
67204754
ID
67202812
67183986
67202816
67183990
67202819
67183993
67202820
67183994
67202821
67183995
67202822
67183996
67202823
67183997
67202824
67183998
67202825
67183999
67202826
67184000
67202827
67184001
67202828
67184002
67202829
67184003
67202830
67184004
67202831
67184005
67202832
67184006
67202833
67184007
67202834
67184008
67202835
67184009
67202836
67184010
67202837
67184011
67202838
67184012
67202839
67184013
67202840
67184014
67202841
67184015
67202842
67184016
67202843
67184017
67202844
67184018
67202845
67184019
67202846
67184020
67202847
67184021
67202848
67184022
67202849
67184023
67202850
67184024
67202851
67184025
67202852
67184026
67202853
67184027
67202854
67184028
67202855
67184029
67202856
67184030
67202857
67184031
67202858
67184032
67202859
67189903
67202860
67189905
67203449
67203450
67203451
67203452
67203453
67203454
67203455
67203456
67203457
67203458
67203459
67203460
67192689
67192690
67204482
67204483
Counter
VS.SingleRAB.SF4
VS.SingleRAB.SF8
VS.SingleRAB.SF16
VS.SingleRAB.SF32
VS.SingleRAB.SF64
VS.SingleRAB.SF128
VS.SingleRAB.SF256
If the RTWP of a cell is greater than -100 dBm, the cell must be analyzed
Transmited 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
botleneck 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.
Counter
VS.BcchSrbKbps.Dl
VS.CcchSrbKbps.Dl
VS.CcchSrbKbps.Ul
VS.MAC.DRNCIubBytesDCH.Rx
VS.MAC.DRNCIubBytesDCH.Tx
VS.MAC.SRNCIubBytesDCH.Rx
VS.MAC.SRNCIubBytesDCH.Tx
VS.MAC.SRNCIubBytesPSStr.Rx
VS.MAC.SRNCIubBytesPSInt.Rx
VS.MAC.SRNCIubBytesPSBkg.Rx
VS.MAC.SRNCIubBytesPSStr.Tx
VS.MAC.SRNCIubBytesPSInt.Tx
VS.MAC.SRNCIubBytesPSBkg.Tx
VS.MAC.SRNCIubBytesCSConv.Rx
VS.MAC.SRNCIubBytesCSStr.Rx
VS.MAC.SRNCIubBytesCSConv.Tx
VS.MAC.SRNCIubBytesCSStr.Tx
VS.MAC.CRNCIubBytesRACH.Rx
VS.MAC.CRNCIubBytesFACH.Tx
VS.MAC.CRNCIubBytesPCH.Tx
VS.CRNC.IUB.RACH.Bandwidth
VS.CRNC.IUB.FACH.Bandwidth
VS.CRNC.IUB.PCH.Bandwidth
VS.MBMS.IUB.BANDWIDTH
VS.MAC.CRNCIubBytes.PS.CCH.RX
VS.MAC.CRNCIubBytes.PS.CCH.TX
Counter
VS.CS.Conv.Kbps.DL64
VS.CS.Conv.DL.64.Thruput
VS.CS.Str.Kbps.DL57.6
VS.CS.Str.DL.57.6.Thruput
VS.PS.Bkg.Kbps.DL8
VS.PS.Bkg.DL.8.Thruput
VS.PS.Bkg.Kbps.DL16
VS.PS.Bkg.DL.16.Thruput
VS.PS.Bkg.Kbps.DL32
VS.PS.Bkg.DL.32.Thruput
VS.PS.Bkg.Kbps.DL64
VS.PS.Bkg.DL.64.Thruput
VS.PS.Bkg.Kbps.DL128
VS.PS.Bkg.DL.128.Thruput
VS.PS.Bkg.Kbps.DL144
VS.PS.Bkg.DL.144.Thruput
VS.PS.Bkg.Kbps.DL256
VS.PS.Bkg.DL.256.Thruput
VS.PS.Bkg.Kbps.DL384
VS.PS.Bkg.DL.384.Thruput
VS.PS.Int.Kbps.DL8
VS.PS.Int.DL.8.Thruput
VS.PS.Int.Kbps.DL16
VS.PS.Int.DL.16.Thruput
VS.PS.Int.Kbps.DL32
VS.PS.Int.DL.32.Thruput
VS.PS.Int.Kbps.DL64
VS.PS.Int.DL.64.Thruput
VS.PS.Int.Kbps.DL128
VS.PS.Int.DL.128.Thruput
VS.PS.Int.Kbps.DL144
VS.PS.Int.DL.144.Thruput
VS.PS.Int.Kbps.DL256
VS.PS.Int.DL.256.Thruput
VS.PS.Int.Kbps.DL384
VS.PS.Int.DL.384.Thruput
VS.PS.Str.Kbps.DL32
VS.PS.Str.DL.32.Thruput
VS.PS.Str.Kbps.DL64
VS.PS.Str.DL.64.Thruput
VS.PS.Str.Kbps.DL128
VS.PS.Str.DL.128.Thruput
VS.PS.Str.Kbps.DL144
VS.PS.Str.DL.144.Thruput
VS.CS.Str.Kbps.UL64
VS.CS.Str.UL.64.Thruput
VS.PS.Bkg.Kbps.UL8
VS.PS.Bkg.UL.8.Thruput
VS.PS.Bkg.Kbps.UL16
VS.PS.Bkg.UL.16.Thruput
VS.PS.Bkg.Kbps.UL32
VS.PS.Bkg.UL.32.Thruput
VS.PS.Bkg.Kbps.UL64
VS.PS.Bkg.UL.64.Thruput
VS.PS.Bkg.Kbps.UL128
VS.PS.Bkg.UL.128.Thruput
VS.PS.Bkg.Kbps.UL144
VS.PS.Bkg.UL.144.Thruput
VS.PS.Bkg.Kbps.UL256
VS.PS.Bkg.UL.256.Thruput
VS.PS.Bkg.Kbps.UL384
VS.PS.Bkg.UL.384.Thruput
VS.PS.Int.Kbps.UL8
VS.PS.Int.UL.8.Thruput
VS.PS.Int.Kbps.UL16
VS.PS.Int.UL.16.Thruput
VS.PS.Int.Kbps.UL32
VS.PS.Int.UL.32.Thruput
VS.PS.Int.Kbps.UL64
VS.PS.Int.UL.64.Thruput
VS.PS.Int.Kbps.UL128
VS.PS.Int.UL.128.Thruput
VS.PS.Int.Kbps.UL144
VS.PS.Int.UL.144.Thruput
VS.PS.Int.Kbps.UL256
VS.PS.Int.UL.256.Thruput
VS.PS.Int.Kbps.UL384
VS.PS.Int.UL.384.Thruput
VS.PS.Str.Kbps.UL16
VS.PS.Str.UL.16.Thruput
VS.PS.Str.Kbps.UL32
VS.PS.Str.UL.32.Thruput
VS.PS.Str.Kbps.UL64
VS.PS.Str.UL.64.Thruput
VS.DcchSrbKbps.Ul
VS.DcchSrbKbps.Ul.Thruput
VS.DcchSrbKbps.Dl
VS.DcchSrbKbps.Dl.Thruput
VS.AMRLoad.kbits.UL
VS.AMRLoad.kbits.DL
VS.VPLoad.kbits.UL
VS.VPLoad.kbits.DL
VS.PSLoad.kbits.UL.0.32
VS.PSLoad.kbits.DL.0.32
VS.PSLoad.kbits.UL.32.64
VS.PSLoad.kbits.DL.32.64
VS.PSLoad.kbits.UL.64.144
VS.PSLoad.kbits.DL.64.144
VS.PSLoad.kbits.UL.144.384
VS.PSLoad.kbits.DL.144.384
VS.AMR.Erlang.BestCell
VS.VP.Erlang.BestCell
VS.MBMS.PTM.MeanThroughput.Cell
VS.MBMS.PTP.MeanThroughput.Cell
Description
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 4 in a cell
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 8 in a cell
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 16 in a cell
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 32 in a cell
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 64 in a cell
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 128 in a cell
The mean number of single-RAB UEs that occupy the codes with spreading
factor (SF) of 256in a cell
Description
BCCH throughput<cell>
CCCH DL throughput<cell>
CCCH UL throughput<cell>
Number of UL Bytes on DRNC Iub Interface<cell>
Number of DL Bytes on DRNC Iub Interface<cell>
Number of UL Signaling Bytes on Iub Interface<Cell>
Number of DL Signalling Bytes on Iub Interface<Cell>
Number of UL Bytes of PS Streaming Service on Iub
Interface, stat. on DCH only<Cell>
Number of UL Bytes of PS Interactive Service on Iub
Interface , stat. on DCH only<Cell>
Number of UL Bytes of PS Background Service on Iub
Interface , stat. on DCH only<Cell>
Number of DL Bytes of PS Streaming Service on Iub
Interface, stat. on DCH only<Cell>
Number of DL Bytes of PS Interactive Service on Iub
Interface, stat. on DCH only<Cell>
Number of DL Bytes of PS Background Service on Iub
Interface, stat. on DCH only<Cell>
Number of UL Bytes of CS Conversational Service on Iub
Interface, stat. on DCH only<Cell>
Number of UL Bytes of CS Streaming Service on Iub
Interface, stat. on DCH only<Cell>
Number of DL Bytes of CS Conversational Service on Iub
Interface, stat. on DCH only<Cell>
Number of DL Bytes of CS Streaming Service on Iub
Interface, stat. on DCH only<Cell>
Number of Bytes on Iub RACH<Cell>
Number of Bytes on IUB FACH<Cell>
Number of Bytes on PCH of Iub Interface<Cell>
Bandwidth of CRNC RACH in byte rate<cell>
Bandwidth of CRNC FACH in byte rate<cell>
Bandwidth of CRNC PCH in byte rate<cell>
Bandwidth of CRNC PCH in byte rate<cell>
Number of Bytes of PS Service on Iub RACH<Cell>
Number of Bytes of PS Service on IUB FACH<Cell>
Description
Average rate of the Traffic CS DownLink 64k
Conversational per Cell<cell>
The Bit Size of Transport Blocks of Traffic
CS_CONV_DL_64<Cell>
Average rate of the Traffic CS DownLink 57.6k Streaming
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
CS_STR_DL_57_6<Cell>
Average rate of the Traffic PS DownLink 8k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_8<Cell>
Average rate of the Traffic PS DownLink 16k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_16<Cell>
Average rate of the Traffic PS DownLink 32k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_32<Cell>
Average rate of the Traffic PS DownLink 64k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_64<Cell>
Average rate of the Traffic PS DownLink 128k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_128<Cell>
Average rate of the Traffic PS DownLink 144k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_144<Cell>
Average rate of the Traffic PS DownLink 256k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_256<Cell>
Average rate of the Traffic PS DownLink 384k Background
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_DL_384<Cell>
Average rate of the Traffic PS DownLink 8k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_8<Cell>
Average rate of the Traffic PS DownLink 16k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_16<Cell>
Average rate of the Traffic PS DownLink 32k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_32<Cell>
Average rate of the Traffic PS DownLink 64k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_64<Cell>
Average rate of the Traffic PS DownLink 128k Interactive
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_128<Cell>
Average rate of the Traffic PS DownLink 144k Interactive
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_144<Cell>
Average rate of the Traffic PS DownLink 256k Interactive
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_256<Cell>
Average rate of the Traffic PS DownLink 384k Interactive
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_DL_384<Cell>
Average rate of the Traffic PS DownLink 32k Streaming per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_DL_32<Cell>
Average rate of the Traffic PS DownLink 64k Streaming per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_DL_64<Cell>
Average rate of the Traffic PS DownLink 128k Streaming
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_DL_128<Cell>
Average rate of the Traffic PS DownLink 144k Streaming
per Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_DL_144<Cell>
Average rate of the Traffic CS UpLink 64k Streaming per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
CS_STR_UL_64<Cell>
Average rate of the Traffic PS UpLink 8k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_8<Cell>
Average rate of the Traffic PS UpLink 16k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_16<Cell>
Average rate of the Traffic PS UpLink 32k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_32<Cell>
Average rate of the Traffic PS UpLink 64k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_64<Cell>
Average rate of the Traffic PS UpLink 128k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_128<Cell>
Average rate of the Traffic PS UpLink 144k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_144<Cell>
Average rate of the Traffic PS UpLink 256k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_256<Cell>
Average rate of the Traffic PS UpLink 384k Background per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_BKG_UL_384<Cell>
Average rate of the Traffic PS UpLink 8k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_8<Cell>
Average rate of the Traffic PS UpLink 16k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_16<Cell>
Average rate of the Traffic PS UpLink 32k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_32<Cell>
Average rate of the Traffic PS UpLink 64k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_64<Cell>
Average rate of the Traffic PS UpLink 128k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_128<Cell>
Average rate of the Traffic PS UpLink 144k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_144<Cell>
Average rate of the Traffic PS UpLink 256k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_256<Cell>
Average rate of the Traffic PS UpLink 384k Interactive per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_INTER_UL_384<Cell>
Average rate of the Traffic PS UpLink 16k Streaming per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_UL_16<Cell>
Average rate of the Traffic PS UpLink 32k Streaming per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_UL_32<Cell>
Average rate of the Traffic PS UpLink 64k Streaming per
Cell<cell>
The Bit Size of Transport Blocks of Traffic
PS_STR_UL_64<Cell>
Rate of UL Signaling on DCCH<cell>
The Bit Size of UL Signaling on DCCH<cell>
Rate of DL Signaling on DCCH<cell>
The Bit Size of DL Signaling on DCCH<cell>
The Bit Size of Transport Blocks of Traffic
CS_AMR_UL<Cell>
The Bit Size of Transport Blocks of Traffic
CS_AMR_DL<Cell>
The Bit Size of Transport Blocks of Traffic CS_VP_UL<Cell>
lProtocol error
lInvalid configuration
ID
67180565
67180566
67189685
67193708
67192770
67192551
67192552
67192553
67192554
67192555
67192556
67192557
67192614
67192558
67192559
67192560
67192561
67193565
67193566
67192567
67192568
67189688
67189689
67180584
67180562
67180563
67180585
67180586
67180587
67180588
67180589
67180590
67189701
67192168
67189702
67192169
67189703
67192170
67189704
67192171
67189705
67192172
67189708
67189709
67189710
67189711
67189712
67189713
67189714
67189715
67189716
67189717
67189722
67189723
67180551
67180570
67180549
67180550
67193709
67193710
67190402
67183900
67183901
67183902
67183903
67183904
67183906
67183907
67183908
67183909
67183910
67183911
67183912
67183913
67183924
67183926
67190877
67190878
67190884
67190885
67190891
67190892
67190898
67190899
67191694
67191695
67193397
67193398
67193401
67193402
67193403
67193404
Radio link setup failure
Other causes
Internal NodeB/Between NodeBs/Between RNCs HHO failure
Configuration nonsupport
PCH failure
Cell update
Invalid configuration
Other causes
reconfiguration
Counter
VS.HHO.At.In
VS.HHO.Succ.In
VS.HHO.ReqRelocPrep.RF
VS.HHO.IntraFreqRelocPrep.At
VS.HHO.IntraFreqRelocPrep.Succ
VS.HHO.InterFreqRelocPrep.At
VS.HHO.InterFreqRelocPrep.Succ
VS.HHO.IntraFreqOut.NoReply
VS.HHO.IntraFreqOut.FailPrep
VS.HHO.InterFreqOut.FailPrep
VS.HHO.IntraFreqOut.RLAddFail
VS.HHO.InterFreqOut.RLAddFail
VS.HHO.IntraFreqOut.CfgInvalid
VS.HHO.IntraFreqOut.CfgUnsupp
VS.HHO.IntraFreqOut.PyhChFail
VS.HHO.IntraFreqOut.FailUSR
VS.HHO.IntraFreqOut.CellUpdt
VS.MBand.HO.AtOutCS
VS.MBand.HO.SuccOutCS
VS.MBand.HO.AtOutPS
VS.MBand.HO.SuccOutPS
VS.HHO.AtIFrqCM.DLQoS.Out
VS.HHO.SuccIFrqCM.DLQoS.Out
VS.HHO.Fail.RLAddFail.Out
VS.HHO.Fail.RACDenyUL.Out
VS.HHO.Fail.RACDenyDL.Out
VS.HHO.AtOutIntraNodeBIntraFreq
VS.HHO.SuccOutIntraNodeBIntraFreq
VS.HHO.AtOutInterNodeBIntraRNCIntraFreq
VS.HHO.SuccOutInterNodeBIntraRNCIntraFreq
VS.HHO.AtOutInterRNCIntraFreqIur
VS.HHO.SuccOutInterRNCIntraFreqIur
VS.HHO.FailOutInterRNCIntraFreqIur.CfgUnsup
VS.HHO.FailOutInterRNCIur.CfgUnsup
VS.HHO.FailOutInterRNCIntraFreqIur.PhyChFail
VS.HHO.FailOutInterRNCIur.PhyChFail
VS.HHO.FailOutInterRNCIntraFreqIur.ISR
VS.HHO.FailOutInterRNCIur.ISR
VS.HHO.FailOutInterRNCIntraFreqIur.InvCfg
VS.HHO.FailOutInterRNCIur.InvCfg
VS.HHO.FailOutInterRNCIntraFreqIur.IncompCfg
VS.HHO.FailOutInterRNCIur.IncompCfg
HHO.FailRelocPrepOutInterRNCCN.NoResAvail
HHO.FailRelocPrepOutInterRNCCN.TExp
HHO.FailRelocPrepOutInterRNCCN.TgtF
HHO.FailRelocPrepOutInterRNCCN.RNSp
HHO.FailRelocPrepOutInterRNCCN.RelocTgtNotAllo
HHO.FailRelocPrepOutInterRNCCN.OM
HHO.FailRelocPrepOutInterRNCCN.ResUnavail
HHO.FailRelocPrepOutInterRNCCN.UnspFail
VS.HHO.AtOutInterRNCIntraFreqCN
VS.HHO.SuccOutInterRNCIntraFreqCN
VS.HHO.EvalOut
VS.HHO.EvalIn
VS.HHO.EvalIFrq.Out.CM
VS.HHO.EvalIFrq.In.CM
VS.HHO.AtInterCell.LB
VS.HHO.SuccInterCell.LB
VS.HHO.AtInterCell.LB.MultiRL
VS.HHO.SuccInterCell.LB.MultiRL
VS.HHO.FailInterCell.NRly.LB
VS.HHO.InterFreq.AtOut
VS.HHO.InterFreq.SuccOut
VS.HHO.InterFreqOut.CfgUnsupp
VS.HHO.InterFreqOut.PyhChFail
VS.HHO.InterFreqOut.FailUSR
VS.HHO.InterFreqOut.CellUpdt
VS.HHO.InterFreqOut.CfgInvalid
VS.HHO.InterFreqOut.NoReply
VS.HHO.InterFreqOut.DLCodeRej
VS.HHO.InterFreqOut.ULAdmsnDeny
VS.HHO.InterFreqOut.DLAdmsnDeny
VS.HHO.InterFreqIn.At
VS.HHO.InterFreqIn.Succ
VS.HHO.InterFreq.Out.Drop
VS.HHO.IntraFreq.Out.Drop
VS.HHO.AtOutIntraNodeBInterFreq
VS.HHO.SuccOutIntraNodeBInterFreq
VS.HHO.AtOutInterNodeBIntraRNCInterFreq
VS.HHO.SuccOutInterNodeBIntraRNCInterFreq
VS.HHO.AtOutInterRNCInterFreqIur
VS.HHO.SuccOutInterRNCInterFreqIur
VS.HHO.AtOutInterRNCInterFreqCN
VS.HHO.SuccOutInterRNCInterFreqCN
VS.HHO.AtBlindHO
VS.HHO.SuccBlindHO
VS.HHO.InterFreqOutCS.MeasTimeOut
VS.HHO.InterFreqOutPS.MeasTimeOut
VS.HHO.InterFreq.CS.Out.TrigRscp
VS.HHO.InterFreq.CS.Out.TrigEcIo
VS.HHO.InterFreq.PS.Out.TrigRscp
VS.HHO.InterFreq.PS.Out.TrigEcIo
Analyze RL setup failure.
Analyze the problem further based on CHR logs.
e
The UE thinks it cannot support the command for outgoing
HHO, because it is incompatible with HHO.
The cause is probably weak coverage and strong interference.
The UE feeds back HHO is incompatible with other consequent
processes due to compatibility problems of UE.
Cell update occurs upon outgoing HHO. These two processes lead to
outgoing HHO failure.
The UE thinks the command for outgoing HHO as invalid. This is a
compatibility problem of UE.
Analyze the problem further based on CHR logs.
Description
Number of Requested Hard Handovers to Cell <Cell>
Number of Successful Hard Handovers to Cell <Cell>
Count of Hard Handover Out Cell Prepare with
Relocation<Radio Link Signal Quality>
IntraFreq Hho With Reloc Att
IntraFreq Hho With Reloc Succ
InterFreq Hho With Reloc Att
InterFreq Hho With Reloc Succ
IntraFreq Hho Ue NoRsp
IntraFreq Hho Prep Fail
InterFreq Hho Prep Fail
IntraFreq Hho Prep Fail With Rl Add Fail
InterFreq Hho Prep Fail With Rl Add Fail
Count of failures of intra-frequency handover out due to invalid
configuration within the cell
IntraFreq Hho Prep Fail With Cfg UnSupport
IntraFreq Hho Prep Fail With Phy Channel Recfg Fail
IntraFreq Hho Prep Fail With Sync Recfg Fail
IntraFreq Hho Prep Fail With Cell Update
Hho Req With Multi Freq
Hho Succ With Multi Freq
Hho Req With Multi Freq
Hho Succ With Multi Freq
Count of Inter-Frequency Hard Handover Out Cell Judgement
with compressed mode<DL Quality>
Count of Inter-Frequency Hard Handover Out Cell Success with
compressed mode<DL Quality>
Count of Hard Handover Out Cell Failure<Radio Link Setup
Failure>
Count of Hard Handover Out Cell Failure<Uplink Admission
Rejection>
Count of Hard Handover Out Cell Failure<Downlink Admission
Rejection>
Count of Intra-NodeB Intra-Frequency Intra-Frequecy Hard
Handover Out Cell
Number of Intra-NodeB Intra-Frequency Hard Handover Out
Cell Success
Number of Inter-NodeB Intra-Frequency Hard Handover Out
Cell
Number of Inter-NodeB Intra-Frequency Hard Handover Out
Cell Success
Number of Inter-RNC Intra-Frequency Hard Handover Out Cell
resources not available Cell not available DL radio resources not available UL radio resources not available RL Already A
e object SIB Origination in Node B not Supported Requested Tx Diversity Mode not supported Number of DL codes not supported S-CPICH
ources not available RL Already Activated/allocated, Node B Resources Unavailable Combining Resources not available Measurement Temp
DL codes not supported S-CPICH not supported Combining not supported UL SF not supported DL SF not supported Common Transport Cha
ot available Measurement Temporarily not Available Transport resource unavailable Control processing overload Not enough user plane pr
upported Common Transport Channel Type not supported Dedicated Transport Channel Type not supported Downlink Shared Channel Type
67199681
67199617
67199682
67199683
67199618
67202900
67202901
67202902
67202982
67202983
67202984
Counter
VS.MaxRTWP
VS.MinRTWP
VS.MeanRTWP
VS.MaxTCP
VS.MinTCP
VS.MeanTCP
VS.MaxTCP.NonHS
VS.MinTCP.NonHS
VS.MeanTCP.NonHS
VS.HSDPA.MaxRequiredPwr
VS.HSDPA.MinRequiredPwr
VS.HSDPA.MeanRequiredPwr
Description
Count of the maximum Received Total Wideband Power
on a per cell
Count of the minimum Received Total Wideband Power on
a per cell
Received Total Wideband Power of cell
Count of the maximum Transmitted Carrier Power on a per
cell
Count of the minimum Transmitted Carrier Power on a per
cell
Transmitted Carrier Power of cell
Count of the maximum Transmitted Carrier Power on a per
Non-HSDPA cell
Count of the minimum Transmitted Carrier Power on a per
cell
Transmitted Carrier Power of Non-HSDPA cell
Observed maximum value of the HS-DSCH Required
Power in dBm per cell basis
Observed minimum value of the HS-DSCH Required
Power in dBm per cell basis
Observed average value of the HS-DSCH Required Power
in dBm per cell basis
Counter
VS.IUB.RLFail.CfgUnsup
VS.IUB.RLFail.HW
VS.IUB.RLFail.OM
VS.IUB.RLFail.SyncFail
ID
67180830
RLM.FailRLAddIub.CfgUnsup
RLM.FailRLAddIub.Cong
VS.SHO.FailRLAddIub.HW
VS.IUB.FailRLAdd.OM
VS.IUB.FailRLRecfg.CfgUnsup
VS.IUB.FailRLRecfg.Cong
VS.IUB.FailRLRecfg.HW
VS.IUB.FailRLRecfg.OM
67180824
ID
67180838
ID
67194417
67194418
67194419
67194420
67194421
67194422
67194423
67194424
67194425
67194426
67194427
67194428
67194429
67194430
67194431
67204198
67204199
67193245
67193246
67193247
67193248
67193249
67193250
Description
Number of RL failures on Iub interface due to configuration
unsupported (cause value: Power level not supported, Measurement
not supported for the object, SIB Origination in Node B not
Supported, Requested Tx Diversity Mode not supported, Number of
DL codes not supported, S-CPICH not supported, Combining not
supported, UL SF not supported, DL SF not supported, Common
Transport Channel Type not supported, Dedicated Transport
Channel Type not supported, Downlink Shared Channel Type not
supported, Uplink Shared Channel Type not supported, CM not
supported, Tx diversity no longer supported, or Number of UL codes
not supported)
Counter
VS.PPP.TXPACKETS
VS.PPP.TXBYTES
VS.PPP.TXDROPS
VS.PPP.RXPACKETS
VS.PPP.RXBYTES
VS.PPP.RXDROPS
VS.PPP.FAULTEMIT
VS.PPP.FAULTCLEAR
VS.PPP.FAULTTIME
VS.PPP.TXMAXSPEED
VS.PPP.TXMINSPEED
VS.PPP.TXMEANSPEED
VS.PPP.RXMAXSPEED
VS.PPP.RXMINSPEED
VS.PPP.RXMEANSPEED
VS.PPP.Alloced.Ave.Fwd
VS.PPP.Alloced.Ave.Bwd
VS.PPP.Alloced.Max.Fwd
VS.PPP.Alloced.Max.Bwd
VS.PPP.Fwd.Cong
VS.PPP.Fwd.Cong.Dur
VS.PPP.Bwd.Cong
VS.PPP.Bwd.Cong.Dur
Description
the number of packets , which were sent successed in PPP
total bytes of send packets, PPP's head is containd in PPP
total dropped packets, in PPP
total received packets, in PPP
total bytes of receieved packets, PPP's head is containd in PPP
67176546
67176552
67176529
67176531
67176547
67176549
67176550
67176551
67176553
67176554
67176555
67176556
67176557
67176571
67176573
67190182
67192538
67192539
67192540
67193095
67196234
Counter
VS.IU.ResetCS.Tx
VS.IU.ResetCS.Rx
VS.IU.SIG.AtConnEstabCS
IU.AtConnRelReqUTRANCS.sum
IU.AtConnRelCNCS.sum
VS.IU.ErrInd.CS.Tx
VS.IU.ErrInd.CS.Rx
VS.IU.RelReqCS.OM
VS.IU.RelReqCS.IngChkFail
VS.IU.RelReqCS.SigConnRel
VS.IU.RelReqCS.RadConnUELost
VS.IU.RelCmdCS.RelocSucc
VS.IU.RelCmdCS.NormRel
VS.IU.RelCmdCS.UTRANGen
VS.IU.RelCmdCS.RelocCan
VS.IU.RelCmdCS.NoRAB
VS.Iu.RelReqCS.SRBReset
VS.Iu.RelReqCS.RIPFail
VS.IU.RelCSPreempt
VS.IU.LdBalRtCS.IMSI
VS.IU.LdBalRtCS.InValidNRI
VS.IU.LdBalRtCS.IMEI
VS.IU.SCCP.FlowCtrl.Disc.InitDTCS
VS.IU.RelReqCS.NetworkOpt
Description
Number of RESET Messages Initiated from RNC
Number of RESET Messages Received by RNC
Number of IU CONNECTION REQUEST Messages Sent from RNC to CS
Domain
Number of IU RELEASE REQUEST Messages Sent from RNC to CS
Domain
Number of IU RELEASE COMMAND Messages Sent from CS Domain to
RNC
Number of ERROR INDICATION Messages Initiated from RNC to CS
Domain
Number of ERROR INDICATION Messages Sent from CS Domain to RNC
67192577 VS.SHO.FailRLSetupIur.TransCongRx
67192578 VS.SHO.FailRLAddIur.TransCong.Rx
67179035 VS.SHO.AtRLAddIur.Tx
67179036 VS.SHO.SuccRLAddIur.Rx
67179037 VS.SHO.FailRLAddIur.OM.Rx
67179038 VS.SHO.FailRLAddIur.HW.Rx
67179039 VS.SHO.FailRLAddIur.Cong.Rx
67179040 VS.SHO.FailRLAddIur.CfgUnsRx
67179042 VS.SHO.AtRLRecfgIur.Tx
67179043 VS.SHO.SuccRLRecfgIur.Rx
67179044 VS.SHO.FailRLRecfgIur.OM.Rx
67179045 VS.SHO.FailRLRecfgIur.HW.Rx
67179046 VS.SHO.FailRLRecfgIur.CongRx
67179047 VS.SHO.FailRLRecfgIur.CfgURx
67179048 VS.SHO.FailRLRecfgIur.NRplyR
67179051 VS.SHO.RLFailIur.Rx
67179052 VS.SHO.RLFailIur.OM.Rx
67179053 VS.SHO.RLFailIur.HW.Rx
67179054 VS.SHO.RLFailIur.SyncFail.Rx
67179055 VS.SHO.RLFailIur.CfgUnsup.Rx
67179056 VS.SHO.RLRestoreIur.Rx
67179061 VS.Iur.SHO.At
67179062 VS.Iur.SHO.Succ
67179057 VS.IUR.AtComTraChResSRNC
67179058 VS.IUR.SuccComTraChResSRNC
67179059 VS.IUR.FailCTCRSRNC.NotSupp
67179060 VS.IUR.AtRelCoTrChResSRNC
67191845 VS.Norm.Rel.CS.Conv.RB.64.IurLink
67191846 VS.Norm.Rel.PS.BE.RB.0.32.IurLink
67191847 VS.Norm.Rel.PS.BE.RB.32.64.IurLink
67191848 VS.Norm.Rel.PS.BE.RB.64.144.IurLink
67191849 VS.Norm.Rel.PS.BE.RB.144.384.IurLink
67191850 VS.Norm.Rel.PS.CCH.IurLink
67191851 VS.Norm.Rel.CS.AMR.UlSigRel.IurLink
67191852 VS.Norm.Rel.CS.Conv.RB.64.UlSigRel.IurLink
67191853 VS.Norm.Rel.PS.BE.RB.0.32.UlSigRel.IurLink
67191854 VS.Norm.Rel.PS.BE.RB.32.64.UlSigRel.IurLink
67191855 VS.Norm.Rel.PS.BE.RB.64.144.UlSigRel.IurLink
67191856 VS.Norm.Rel.PS.BE.RB.144.384.UlSigRel.IurLink
67191857 VS.Norm.Rel.PS.CCH.UlSigRel.IurLink
67191858 VS.Norm.Rel.CS.AMR.IurLink
67191859 VS.Abnorm.Rel.CS.AMR.IurLink
67191860 VS.Abnorm.Rel.CS.Conv.RB.64.IurLink
67191861 VS.Abnorm.Rel.PS.BE.RB.0.32.IurLink
67191862 VS.Abnorm.Rel.PS.BE.RB.32.64.IurLink
67191863 VS.Abnorm.Rel.PS.BE.RB.64.144.IurLink
67191864 VS.Abnorm.Rel.PS.BE.RB.144.384.IurLink
67191865 VS.Abnorm.Rel.PS.CCH.IurLink
67194987 VS.NORM.REL.CS.STR.IURLINK
67194988 VS.NORM.REL.PS.CONV.IURLINK
67194989 VS.NORM.REL.PS.STR.IURLINK
67194990 VS.NORM.REL.PS.HS.IURLINK
67194991 VS.NORM.REL.PS.EDCH.IURLINK
67194992 VS.NORM.REL.CS.STR.ULSIGREL.IURLINK
67194993 VS.NORM.REL.PS.CONV.ULSIGREL.IURLINK
67194994 VS.NORM.REL.PS.STR.ULSIGREL.IURLINK
67194995 VS.NORM.REL.PS.HS.ULSIGREL.IURLINK
67194996 VS.NORM.REL.PS.EDCH.ULSIGREL.IURLINK
67194997 VS.ABNORM.REL.CS.STR.IURLINK
67194998 VS.ABNORM.REL.PS.CONV.IURLINK
67194999 VS.ABNORM.REL.PS.STR.IURLINK
67195000 VS.ABNORM.REL.PS.HS.IURLINK
67195001 VS.ABNORM.REL.PS.EDCH.IURLINK
67179050 VS.SHO.CancelRLRecfgIur.Tx
67196206 VS.Norm.Rel.HSPA.CS.Conv.Iurlink
67196207 VS.Abnorm.Rel.HSPA.CS.Conv.Iurlink
Description
Number of RLs Requested to Establish by SRNC on Iur Interface
Number of RLs Successfully Established by SRNC on Iur Interface
Count of SRNC Iur Interface Radio Link Setup Failure<OM Intervention>
Count of SRNC Iur Interface Radio Link Setup Failure<Device Fault>
Count of SRNC Iur Interface Radio Link Setup Failure<Congestion>
Count of SRNC Iur Interface Radio Link Setup Failure<Configuration Unsupported>