Counter

SubCounter
VS.RAB.AbnormRel.CS.IuAAL2

VS.RAB.AbnormRel.CS.OM

VS.RAB.AbnormRel.CS.UTRANgen

VS.RAB.AbnormRel.CS.OLC
VS.RAB.AbnormRel.CS.RF

VS.RAB.AbnormalRel.CS

VS.RAB.AbnormRel.CS.Preempt

SubCounter

.CS.IuAAL2

.CS.OM

.CS.Preempt

.CS.UTRANgen

.CS.OLC

VS.RAB.AbnormRel.CS.RF.UuNoReply

VS.RAB.AbnormRel.CS.RF.ULSync

VS.RAB.AbnormRel.CS.RF.SRBReset

Remark
Number of CS RABs Abnormally Released for Cell Due to Iu
Interface AAL2 Link Failure
Number of CS RAB Release Requests for Cell Due to O&M
Intervention

Number of CS RAB Release Attempts for Cell Due to RAB

Preemption
Number of CS RAB Abnormal Releases Triggered by RNC for Cell
Due to UTRAN Cause
Number of CS Domain RABs Released Due to Congestion for
Cell

If UE can not respond to the signaling from RNC during service,

the RAB will be release and this counter will be triggered.
If NodeB loses the UL synchronization of the UE during service,
the RAB will be released and this counter will be triggered.

If RNC sends signaling to UE repeat but UE can not send a ACK

response, RNC will reset RLC layer. Then call drop will happen
and this counter will be triggered.

Counter's Trigger Reason

This counter is triggered when RNC finds the AAL2 path is abnormal.
Maybe it is the problem of Iu-CS transmission.
If RAB is release by O&M intervention (For example RAB is
released by MML command), this counter will be triggered.
Normally this is not the main reason of call drop in real
network.
During access control procedure if system resource is limited and
preemption function is enabled, a user with higher priority can
preempt a user with lower priority. Then this counter will be
triggered.
If RAB is released because of UTRAN problem, this counter will
be triggered. If this counter has high value, more detailed information
need to be collected and analyzed.
If the system load is very high and over load control function is
enabled, RNC can release some RAB to reduce the load. Then
this counter will be triggered.
Bad coverage can trigger this counter.

Bad coverage or missing neighboring cell configuration can

triggered this counter.

Bad coverage or interference can trigger this counter.

Counter

SubCounter
VS.RAB.AbnormRel.PS.GTPULoss

VS.RAB.AbnormRel.PS.Preempt

VS.RAB.AbnormRel.PS.OLC

VS.RAB.AbnormRel.PS.RF

VS.RAB.AbnormalRel.PS

VS.RAB.AbnormRel.PS.OM

SubCounter

PULoss

eempt

VS.RAB.AbnormRel.PS.RF.UuNoReply

VS.RAB.AbnormRel.PS.RF.ULSync

VS.RAB.AbnormRel.PS.RF.SRBReset

VS.RAB.AbnormRel.PS.RF.TRBReset

Remark
Number of PS RABs Abnormally Released for Cell
Due to GTPU Failure
Number of PS RAB Release Requests for Cell Due to
O&M Intervention

Number of PS RAB Release Attempts for Cell Due to

RAB Preemption

Number of PS Domain RABs Released Due to

Congestion for Cell
If UE can not respond to the signaling from RNC
during service, the RAB will be release and this
counter will be triggered.
If NodeB loses the UL synchronization of the UE
during service, the RAB will be released and this
counter will be triggered.
If RNC sends signaling to UE repeat but UE can not
send a ACK response, RNC will reset RLC layer.
Then call drop will happen and this counter will be
triggered.
If RNC sends PS data to UE repeat but UE can not
send a ACK response, RNC will reset RLC layer.
Then call drop will happen and this counter will be
triggered.

Counter's Trigger Reason

This counter is triggered when RNC finds the GTPU in Iu-PS
user plane is abnormal. Maybe it is the problem of Iu-PS
transmission.
If RAB is release by O&M intervention (For example
RAB is released by MML command), this counter will
be triggered. Normally this is not the main reason of
call drop in real network.
During access control procedure if system resource is
limited and preemption function is enabled, a user
with higher priority can preempt a user with lower
priority. Then this counter will be triggered.
If the system load is very high and over load control
function is enabled, RNC can release some RAB to
reduce the load. Then this counter will be triggered.
Bad coverage can trigger this counter

Bad coverage or missing neighboring cell

configuration can triggered this counter.
Bad coverage or interference can trigger this counter.

Bad coverage or interference can trigger this counter.

Normally for access performance management and analysis, RRC setup and RAB assignment are t
important procedures.

Counter

Subconter

VS.RRC.Rej.RL.Fail

VS.RRC.Rej.Sum

VS.RRC.Rej.TNL.Fail

VS.RRC.FailConnEstab.Cong

VS.RRC.FailConnEstab.NoReply

VS.RRC.Rej.Redir.IntraRat

VS.RRC.Rej.Redir.InterRat
VS.RRC.Rej.Redir.Service

Subconter

VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.Rej.DLIUBBand.Cong
VS.RRC.Rej.ULPower.Cong
VS.RRC.Rej.DLPower.Cong
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong

Remark

This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC to the UE d
to RL setup failure on the Iub interface after the RNC receives a RRC CONNECTION REQUEST messa
from the UE.. If the value of this counter is very high, it is possible that the NodeB has hardware probl
such as the power amplifier is overheating. To confirm this problem, the device alarm and the
power amplifier should be checked. Normally thie problem is not popular in real network.

This counter provides the number of RRC CONNECTION REJECT messages sent by the RNC to the UE d
to transmission setup failure on the Iub interface after the RNC receives a RRC CONNECTION REQU
message from the UE. This counter indicates the AAL2 setup failure in Iub interface. Normally it doe
not happen if the transmission has no problem.

If the value of these counters is high. The most possible reason is that there are too many users in
cell. We should find which resource causes the congestion based on these counters.

If the value of this counter is high, it is very possible that the coverage of the cell is not good o
the cell reselection has problems. Drive test should be performed to get more information.

This counter provides the number of RRC connection reject messages with redirection information
triggered by RRC admission failure in the cell. This counter only measures the case of reso
admission failure. The case of service-based redirection is not measured.

This counter provides the number of RRC connection reject messages with redirection information
triggered by RRC admission failure in the cell. This counter only measures the case of reso
admission failure. The case of service-based redirection is not measured.

This counter provides the number of RRC connection rejects due to service-based redirection in the ce

Counter

Subconter

VS.RAB.FailEstabCS.RNL

VS.RAB.FailEstabCS.Cong

VS.RAB.FailEstabCS.UuFail

VS.RAB.FailEstabCS.IubFail

VS.RAB.FailEstabCS.TNL

Subconter
VS.RAB.FailEstabCS.ULIUBBand.Cong
VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.ULPower.Cong
VS.RAB.FailEstabCS.DLPower.Cong
VS.RAB.FailEstabCS.ULCE.Cong
VS.RAB.FailEstabCS.DLCE.Cong
VS.RAB.FailEstabCS.Code.Cong
VS.RAB.FailEstabCS.RBIncCfg

VS.RAB.FailEstabCS.RBCfgUnsup

VS.RAB.FailEstabCS.PhyChFail

VS.RAB.FailEstabCS.UuNoReply

Remark

If the value of these counters is high. The most possible reason is that there are too many
users in the cell. We should find which resource causes the congestion based on these
counters.

Number of failed CS RAB establishments for cell due

to invalid configuration of UE during RB setup
procedure
Number of failed CS RAB establishments for cell due
to configuration unsupported of UE during the RB
setup procedure
Number of failed CS RAB establishments for cell due
to physical channel failure of UE during the RB setup
procedure
This counter corresponds to the RF problem of radio network. For example, if the
radio coverage is not good, UE or RNC can not receive the signaling from each
other, then this counter can be triggered.
This counter provides the number of times that a CS RAB establishment fails due to radio link
configuration failure (such as no response from NodeB, or NodeB returns a failure message). If
the value of this counter is very high, it is possible that the NodeB has hardware
problem. It is not popular in real network.
This counter provides the number of CS RABs unsuccessfully established due to the failures of
transport network layer in the best cell. If the value of this counter is very high, maybe
the Iu transmission is in congestion. Normally this problem is not popular in real
network.

emark

st possible reason is that there are too many

esource causes the congestion based on these
unters.

This scenario is not related to the

RF problem of radio network.
Normally it is not popular.

oblem of radio network. For example, if the

C can not receive the signaling from each
unter can be triggered.

hat a CS RAB establishment fails due to radio link

m NodeB, or NodeB returns a failure message). If
it is possible that the NodeB has hardware
opular in real network.

s unsuccessfully established due to the failures of

he value of this counter is very high, maybe
ormally this problem is not popular in real
twork.

Counter

Subconter

VS.RAB.FailEstabPS.RNL

VS.RAB.FailEstabPS.Cong

VS.RAB.FailEstabPS.UuFail

VS.RAB.FailEstabPS.IubFail

VS.RAB.FailEstabPS.TNL

Subconter
VS.RAB.FailEstabPS.ULIUBBand.Cong
VS.RAB.FailEstabPS.DLIUBBand.Cong
VS.RAB.FailEstabPS.ULPower.Cong
VS.RAB.FailEstabPS.DLPower.Cong
VS.RAB.FailEstabPS.ULCE.Cong
VS.RAB.FailEstabPS.DLCE.Cong
VS.RAB.FailEstabPS.Code.Cong
VS.RAB.FailEstabPS.RBIncCfg

VS.RAB.FailEstabPS.RBCfgUnsup

VS.RAB.FailEstabPS.PhyChFail

VS.RAB.FailEstabPS.UuNoReply

Remark

If the value of these counters is high. The most possible reason is that there are too many users
We should find which resource causes the congestion based on these counters.

Number of failed PS RAB establishments for cell

due to invalid configuration of UE during RB setup
procedure
Number of failed PS RAB establishments for cell
due to configuration unsupported of UE during the
RB setup procedure
Number of failed PS RAB establishments for cell
due to physical channel failure of UE during the RB
setup procedure

This counter corresponds to the RF problem of radio network. For example, if the radio co
not good, UE or RNC can not receive the signaling from each other, then this counter c
triggered.

This counter provides the number of times that a PS RAB establishment fails due to radio link confi
failure (such as no response from NodeB, or NodeB returns a failure message). If the value of this cou
high, it is possible that the NodeB has hardware problem. It is not popular in real network.

This counter provides the number of PS RABs unsuccessfully established due to the failures of transpo
layer in the best cell. If the value of this counter is very high, maybe the Iu transmission is in cong
Normally this problem is not popular in real network.

Remark

most possible reason is that there are too many users in the cell.
ource causes the congestion based on these counters.

This scenario is not related to the RF problem of

radio network. Normally it is not popular.

roblem of radio network. For example, if the radio coverage is

ive the signaling from each other, then this counter can be
triggered.

mes that a PS RAB establishment fails due to radio link configuration

or NodeB returns a failure message). If the value of this counter is very
eB has hardware problem. It is not popular in real network.

ABs unsuccessfully established due to the failures of transport network

s counter is very high, maybe the Iu transmission is in congestion.
s problem is not popular in real network.