Documente Academic
Documente Profesional
Documente Cultură
VS.RRC.Rej.Redir.Inter.Att
VS.RRC.Reject.Redir.Intrat
VS.RRC.Reject.Redir.Service
Power Congestion. Check RTWP and the maximum TCP.check power threshold, interference,netwrok capacity
CE Congestion
RL Fail.NodeB fails or NodeB resource is insufficient.
AAL2 Fail.transmission resource is insufficient or any transmission equipment is faulty,
FP Fail. If the transmission fails or an equipment is faulty, FP synchronization may fail. To locate the problem, check whether t
Code Congestion.To locate the problem, start Cell OVSF Code Allocation Analysis to analyze the code allocation and confirm m
Other,analyze call detail logs.
ce,netwrok capacity
CS RAB setup failures PARAM_CELL. RNC regards the parameters transmitted by core network as invalid parameters.
CS RAB setup failures RELOC_CELL,relatedto migration
CS RAB setup failures TNL_CELL.IU transmission setup fails.
CS RAB setup failures CONG_CELL.RNC resource allocation failure.
CS RAB setup failures POWER_CONG_CELL
CS RAB setup failures CE_CONG_CELL
CS RAB setup failures CODE_CONG_CELL
CS RAB setup failures OTHER_CELL
CS RAB setup failures UNSUP_CELL.the QoS is not supported by RNC or RRM admission fails in RAB.
CFG_UNSUPP UE acknowledges the RB setup failure because of configuration unsupported compatibility prob
PHYCH_FAIL The RB setup failure may occur if FACH is migrated to DCH but downlink physical layers are not
SIMU_RECFG_INCOMP UE regards that the RB setup process and other processes simultaneously occur and they are in
CELL_UPDT the Cell Update process occurs. The RB setup failure is caused by process nesting
CFG_INVALID UE regards the configured parameters are invalid ones
NO_RESPONSE UE does not acknowledge the RB setup request. This reason frequently occurs. It is mainly caus
OTHER
lParameter violation
lNon supported UTRAN capabilities
lRelocation triggered
lUnavailable resources
lProtocol error
twork as invalid parameters.
ently occurs. It is mainly caused by poor coverage, so UE cannot receive the RB setup request message
Counter
VS.RAB.RelReqCS.OM
VS.RAB.RelReqCS.RABPreempt
VS.RAB.RelReqCS.UTRANgen
VS.RAB.RelReqPS.OM
VS.RAB.RelReqPS.RABPreempt
gnaling Plane
N generated reason
TRAN Generated Reason"
Counter
VS.RAB.AttRelCS.NetOpt
VS.RAB.AttRelCS.NormRel
VS.RAB.AttRelCS.OM
VS.RAB.AttRelCS.Preempt
VS.RAB.AttRelCS.UEInact
VS.RAB.AttRelCS.UTRANGen
VS.Norm.Rel.CS.AMR.UlSigRel
VS.Norm.Rel.CS.AMR.UlSigRel
RAB_CS_REL_RF_LOSS
RNC_CS_RAB_REL_TRIG_BY_RNC_SRB_RESET
RNC_CS_RAB_REL_TRIG_BY_RNC_AAL2_LOSS
CS_RAB_DROP_OTHER
RNC_PS_RAB_REL_TRIG_BY_RNC_TRB_RESET
RNC_PS_RAB_REL_TRIG_BY_RNC_GTPU_LOSS
PS_RAB_DROP_OTHER
Description
Number of CS RABs requested to release in the best cell for network optimization
Number of CS RABs requested to release in the best cell for normal release
Number of CS RABs requested to release in the best cell for O&M intervention
Number of CS RABs requested to release in the best cell for RAB preempted
Number of CS RABs requested to release in the best cell for user inactivity
Number of CS RABs requested to release in the best cell for release caused by the UTRAN
Number of released CS AMR RABs due to uplink signaling connection release in the best cell
Number of released CS RABs triggered by the RNC due to CELL congestion
CS call drop may be caused by abnormal release caused by the lost synchronization of links because of poor network coverag
CS call drops may be caused by link releasing due to downlink SRB reset. This reason is mainly caused by poor network covera
If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occ
CS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process
PS call drops may be caused by link releasing due to downlink TRB reset. This reason is mainly caused by poor network covera
If IU CS interface (AAL2 path) is abnormal, RNC initializes the release. In practice, this reason seldom occurs. If this reason occ
PS call drops may be caused by other reasons. There are few call drop statistics in RNC (Version 12). Such reasons as process i
because of poor network coverage (including adjacent cell missing, small handover area. As a result, UE closes the transmitter abnormall
nly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network covera
n seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment. In some versions of RNC, norma
sion 12). Such reasons as process interaction timeout and cell update failure are recorded in CS_RAB_DROP_OTHER. In practice, many ca
nly caused by poor network coverage (including adjacent cell missing and small handover area). To solve the problem, the network covera
n seldom occurs. If this reason occurs, the problem may be caused by any faulty or defective equipment.
sion 12). Such reasons as process interaction timeout and cell update failure are recorded in PS_RAB_DROP_OTHER. In practice, many cal
closes the transmitter abnormally or uplink demodulation is asynchronous. To solve the problem, network coverage must be improved.
e the problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.
. In some versions of RNC, normal release is recorded as abnormal release during the RB setup process.
ROP_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are
e the problem, the network coverage must be improved. In the early network, call drops are mainly caused by this reason.
ROP_OTHER. In practice, many call drops are caused by process interaction timeout and cell update failure. Therefore, these call drops are
ork coverage must be improved. In the early network, call drops are mainly caused by this reason.
ed by this reason.
ed by this reason.
SHO_RL_ADD_FAIL_CFG_UNSUPP UE does not support to add radio links in RNC during the active set update. T
SHO_RL_ADD_FAIL_SIMU_RECFG_INCOMP UE feeds back that the soft handover process is incompatible with other con
SHO_RL_ADD_FAIL_CFG_INVALID UE regards active set update of adding radio links in RNC as invalid configura
SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of adding r
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
SHO_RL_ADD_FAIL_CFG_INVALID UE regards the active set update of deleting radio links in RNC as invalid con
SHO_RL_ADD_FAIL_NO_RSP RNC does not receive the acknowledgement of active set update of deleting
SHO_FAIL_OTHER_CELL Soft handover failure is caused by other reasons;
nsmission bandwidth is insufficient.
reasons, such as insufficient RNC resource, radio resource admission reject, and RNC link state reject. To locate the problem, RNC logs mu
ring the active set update. This reason seldom exists in a commercial network.
ncompatible with other concurrent processes when radio links are added in RNC.The problem is mainly caused by some handsets.
s in RNC as invalid configuration.
ctive set update of adding radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handover
during the active set update.
tible with other concurrent processes when radio links are deleted in RNC.The problem is mainly caused by some handsets.
o links in RNC as invalid configuration.
ctive set update of deleting radio links. Soft handover failure is mainly caused by this reason. If network coverage is poor or soft handove
o locate the problem, RNC logs must be used for further analysis.
overage is poor or soft handover area is small, soft handover failure easily occurs.
by some handsets.
coverage is poor or soft handover area is small, soft handover failure easily occurs.
CS_INTERRAT_HO_PREP_FAIL_TARGET_FAIL
CS_INTERRAT_HO_PREP_FAIL_TALLOC_EXPIR
CS_INTERRAT_HO_PREP_FAIL_TARGET_UNSUPP
CS_INTERRAT_HO_PREP_FAIL_RELOC_ABORT
CS_INTERRAT_HO_PREP_FAIL_NO_RSRC_AVAIL
CS_INTERRAT_HO_PREP_FAIL_UNKNOWTARGET
CS_INTERRAT_HO_PREP_FAIL_ REQINFNOTAVAI
CS_INTERRAT_HO_PREP_FAIL_NO_RSP
CS_INTERRAT_HO_ FAIL_UNSPEC
CS_INTERRAT_HO_ FAIL_PHYCN_FAIL
CS_INTERRAT_HO_ FAIL_ CFG_UNSUPP
CS_INTERRAT_HO_ FAIL_ RELOC_ABORT
CS_INTERRAT_HO_ FAIL_NO_RSP
CS_INTERRAT_HO_ FAIL_OTHER
CS inter-RAT handover prepare failure is caused by Relocation Failure Target CN/RNC
CS inter-RAT handover prepare failure is caused by TRELOCalloc Expiry (cause value) because the data configuration or link co
CS inter-RAT handover prepare failure is caused by Relocation Not Supported in Target RNC or Target System (cause value) be
After sending the handover prepare request, RNC receives the release message from core network. This may be caused by tw
CS inter-RAT handover prepare failure is caused by No Resource Available (cause value) because the data configuration of MS
CS inter-RAT handover prepare failure is caused by Unknown Target RNC (cause value) because the data configuration of MSC
CS inter-RAT handover prepare failure is caused by Requested Information Not Available because the data configuration is inc
CS inter-RAT handover prepare failure occurs because core network does not respond to the handover prepare request. This
ndover failure is mainly caused by:1) The signals of 2G network are weak or UE fails to access the network due to serious interference.2) S
does not support the handover request. This reason may be mainly caused by abnormal UE.
network. However, the cause is not Normal Release because the link is released abnormally due to other reasons.
ause network coverage is poor.
aling of core network and BSS for further analysis.
ate the problem, track the signaling of core network and BSS for further analysis.
es, such as location update. Location update process is complete before inter-RAT handover process is complete. Thus, core network initia
, track the signaling of core network and BSS for further analysis.
rk due to serious interference.2) Some parameters (such as ciphering mode) transmitted to UE are inconsistent with that of BSC.
omplete. Thus, core network initializes the release. (2) When inter-RAT handover prepare process is performed, an MS hangs up the call.
NY, check whether the cross coverage is serious, the handover area is unreasonable, or the indoor coverage for high traffic area must be i
power consumption.