Call Drop Rate KPI’s and Relative Counter’s

•CS Service Drop Ratio = [VS.RAB.AbnormRel.CS/(VS.RAB.Abno rmRel.CS+VS.RAB.NormRel.CS)]*100%

•AMR Call Drop Ratio =[VS.RAB.AbnormRel.AMR/(VS.RAB.A bnormRel.AMR+VS.RAB.NormRel.AM
R)]*100%
•VP Call Drop Ratio =[VS.RAB.AbnormRel.CS64/(VS.RAB.A bnormRel.CS64+VS.RAB.NormRel.CS64 )]*100%

This KPI provides the ratio of the CS/AMR/VP RAB abnormal Releases to the total CS/AMR/VP RAB Releases
(Normal Release + Abnormal Release). This KPI is used to check the retainabililty of CS/AMR/VP Service within
a cell
When an RNC detects an exception 1) failure of radio link synchronization, timeout of the air-interface process 2(a signaling
radio bearer [SRB] reset, a traffic radio bearer [TRB] reset, 3) preemption of AAL2 links at the Iu interface), the RNC sends an
RAB RELEASE REQUEST message to the core network (CN) to request RAB release, or sends an IU RELEASE REQUEST
message to request connection release at the Iu interface. When the RNC initiates such abnormal release, it counts the
number of call drops based on specific causes.
UE NodeB RNC MSC
.
Case 1: RL failure
Case 3: Iu error
Case 2: RLC reset, Uu no reply

……
Rab/IU Release Req

Rab/IU Release Command

Rab/IU Release Complete

Measurement point
 Call Drop Rate KPI’s and Relative Counter’s
Counter Sub Counter Sub Counter
VS.RAB.AbnormRel.CS.OM
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.CS.UTRANgen
VS.RAB.AbnormRel.CS.IuAAL2

VS.RAB.Abnorm VS.RAB.AbnormRel.CS.OLC
Rel.CS VS.RAB.Abnorm
Rel.CS.RF.ULSync
VS.RAB.Abnorm VS.RAB.Abnorm
Rel.CS.RF Rel.CS.RF.UuNoReply
VS.RAB.Abnorm
Rel.CS.RF.SRBReset

Counter Sub Counter Sub Counter

VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC
VS.RAB.AbnormRel.PS.RF.UL
Sync
VS.RAB.AbnormRel.PS
VS.RAB.AbnormRel.PS.RF.Uu
NoReply
VS.RAB.AbnormRel.PS.RF
VS.RAB.AbnormRel.PS.RF.SR
BReset

VS.RAB.AbnormRel.PS.RF.TR
BReset
 Call Drop Rate KPI’s and Relative Counter’s
Counter’s description
Counter Name Description
VS.RAB.AbnormRel.CS.IuAAL2 Number of CS RABs Abnormally Released Due to Iu Interface AAL2
Link Failure for Cell(Fault over Iu:Signalling Transport Resource
Failure)
VS.RAB.AbnormRel.CS.RF.ULSync Number of CS RABs abnormally released due to Uplink
Synchronization Fail(Fault over Iu:Radio Connection With UE Lost)
VS.RAB.AbnormRel.CS.RF.UuNoReply Number of CS RABs abnormally released due to UU interface
Fail(Fault over Iu:Failure in the Radio Interface Procedure), Air
interface process timers, such as SHO, HHO, and RB RECFG, time
out.

VS.RAB.AbnormRel.CS.RF Number of CS RABs Abnormally Released Due to RF for Cell(The RF

failure includes Radio Connection With UE Lost and Failure in the
Radio Interface Procedure)
VS.RAB.AbnormRel.CS.OM Number of CS RAB Abnormal Released Due to OM Intervention for
Cell(Fault over Iu:O&M Intervention)
VS.RAB.AbnormRel.CS.Preempt Number of CS RAB Abnormal Released Due to RAB Preemption for
Cell(Fault over Iu:RAB pre-empted)
VS.RAB.AbnormRel.CS.UTRANgen Number of CS RABs Abnormally Released Due to causes on the
UTRAN side for Cell(Fault over Iu:Release due to UTRAN Generated
Reason)
VS.RAB.AbnormRel.CS.RF.SRBReset Number of CS RABs abnormally released due to signaling RLC
reset(Fault over Iu:Radio Connection With UE Lost)
VS.RAB.AbnormRel.CS.OLC Number of CS RAB Release Attempts Due to Congestion for
Cel(Currently, the OLC switch is not turned on by default. Therefore,
this call drop does not exist.)
VS.RAB.AbnormRel.AMR.RF Number of wideband and narrowband AMR services Abnormally
Released Due to RF for Cell(The RF failure includes Radio
Connection With UE Lost and Failure in the Radio Interface
Procedure).
Counter’s description
●VS.RAB.AbnormRel.CS/PS.OM: Number of CS RAB Release Requests for Cell Due to O&M Intervention
“O&M intervention”
● VS.RAB.AbnormRel.CS/PS.Preempt: Number of CS RAB Release Attempts for Cell Due to RAB Preemption
“user with higher priority can preempt a user with lower priority”
● VS.RAB.AbnormRel.CS/PS.OLC: Number of CS Domain RABs Released Due to Congestion for Cell “RNC
can release some RAB to reduce the load bec of OLC algorithm”
● VS.RAB.AbnormRel.CS/PS.RF: Number of CS RABs Abnormally Released Due to RF for Cell “RF problems:
bad coverage, handover failure, interference and etc.”
● VS.RAB.AbnormRel.CS/PS.RF.ULSync: Number of CS RABs Abnormally Released Due to Uplink
Synchronization Failure for Cell “NodeB loses the UL synchronization of the UE during service, result from bad
coverage, missing neighbor, UE TX shutdown abnormally”
● VS.RAB.AbnormRel.CS/PS.RF.UuNoReply: Number of CS RABs Abnormally Released Due to Failure in the
Radio Interface Procedure for Cell “If UE can not respond to the signaling from RNC during service & Air interface
process timers, such as SHO, HHO, and RB RECFG, time out.
● VS.RAB.AbnormRel.CS/PS.RF.SRBReset: Number of CS RABs Abnormally Released Due to Signaling RLC
Reset for Cell “If RNC sends signaling to UE in DL repeat but UE can not send a ACK response, RNC will reset
RLC layer”,Poor coverage.UU interface issue.
● VS.RAB.AbnormRel.CS.UTRANgen: Number of CS RAB Abnormal Releases Triggered by RNC for Cell Due
to UTRAN Cause “UTRAN problem & Cell unavailability caused by digital signal processing (DSP) faults or
packet loss due to high CPU load
● VS.RAB.AbnormRel.CS.IuAAL2: Number of CS RABs Abnormally Released for Cell Due to Iu Interface AAL2
Link Failure “AAL2 path is abnormal. Maybe it is Iu-CS transmission & AAL2 setup failure due to transmission on
the Iu interface
● VS.RAB.AbnormRel.PS.GTPULoss: Number of PS RABs Abnormally Released for Cell Due to GTPU Failure
“GTPU in Iu-PS user plane is abnormal”
● VS.RAB.AbnormRel.PS.RF.TRBReset: Number of PS RABs Abnormally Released Due to Traffic RLC Reset
for Cell “If RNC sends PS data to UE repeat but UE cannot send a ACK response, RNC will reset RLC layer”
RRC counter
Counter Sub Counter Sub Counter

VS.RRC.Rej.RL.Fail

VS.RRC.Rej.TNL.Fail

VS.RRC.Rej.ULPower.Cong

VS.RRC.Rej.DLPower.Cong

VS.RRC.Rej.Sum VS.RRC.Rej.Code.Cong

VS.RRC.FailConnEstab.cong VS.RRC.Rej.ULCE.Cong

VS.RRC.Rej.DLCE.Cong

VS.RRC.Rej.ULIUBBand.Cong

VS.RRC.Rej.DLIUBBand.Cong

VS.RRC.FailConnEstab.NoReply

VS.RRC.Rej.Redir.IntraRat x

VS.RRC.Rej.Redir.InterRat

VS.RRC.Rej.Redir.Service
RRC counter
●VS.RRC.Rej.Redir.IntraRat : Number of RRC Connection Rejects during redirection between inter-frequency
cells (whenever DRD Fails and Admission Fails then Redirection Happens “by sending in RRC Reject Message
redirection info.”, this don’t count if redirection is due to service-based redirection)
●VS.RRC.Rej.Redir.InterRat : Number of RRC Connection Rejects during redirection between inter-RAT cells
(whenever DRD Fails and Admission Fails then Redirection Happens “by sending in RRC Reject Message
redirection info.”, this don’t count if redirection is due to service-based redirection)
●VS.RRC.Rej.Redir.Service : Number of RRC Connection Rejects Due to Service-based RRC Redirection (by
sending in RRC Reject Message redirection info.)
●VS.RRC.Rej.RL.Fail : Number of RRC Connection Rejects Due to Radio Link Setup Failure (maybe from Iub or
Node-B hardware as power amplifier overheating “check alarms”)
●VS.RRC.Rej.TNL.Fail : Number of RRC Connection Rejects Due to Transmission Setup Failure on Iub Interface
(its problem with AAL2 transmission, happens in ATM connections)
●VS.RRC.FailConnEstab.NoReply : Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP
COMPLETE (it deppend on timer)
●VS.RRC.FailConnEstab.Cong : Number of RRC Connection Rejects Due to Congestion
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
VS.RRC.Rej.Redir.IntraRat /VS.RRC.Rej.Redir.InterRat

VS.RRC.Rej.Redir.Service
VS.RRC.Rej.RL.Fail

VS.RRC.Rej.TNL.Fail
VS.RRC.FailConnEstab.NoReply

VS.RRC.Rej.TNL.Fail
RAB counter detail
Counter Sub counter Sub counter
VS.RAB.FailEstabCS/
PS.DLIUBBand.Cong
VS.RAB.FailEstabCS/
PS.ULIUBBand.Cong

VS.RAB.FailEstabCS/PS.ULCE.Cong

VS.RAB.FailEstabCS/PS.Cong VS.RAB.FailEstabCS/PS.DLCE.Cong

VS.RAB.FailEstabCS/PS.Code.Cong

VS.RAB.FailEstabCS/
VS.RAB.FailEstabCS/PS.RNL PS.ULPower.Cong
VS.RAB.FailEstabCS/
PS.DLPower.Cong

VS.RAB.FailEstabCS/PS.RBIncCfg

VS.RAB.FailEstabCS/PS.RBCfgUnsup
VS.RAB.FailEstabCS.UuFail
VS.RAB.FailEstabCS/PS.PhyChFail

VS.RAB.FailEstabCS/PS.UuNoReply
VS.RAB.FailEstabCS/PS.IubFail
VS.RAB.FailEstabCS/PS.TNL
CS & PS RAB counter
CS & PS RAB counter
●VS.RAB.FailEstabCS/PS.UuFail/ VS.RAB.FailEstabCS.UuFail.CSFB: Number of Failed CS RAB
Establishments Due to Uu Interface Configuration Failure “count at best cell”
VS.RAB.FailEstabCS/PS.RBIncCfg “Invalid Configuration of UE”
VS.RAB.FailEstabCS/PS.RBCfgUnsup “Configuration unsupported by UE as UE don’t have VP”
VS.RAB.FailEstabCS/PS.PhyChFail “physical channel failure from UE side, not related to RF”
VS.RAB.FailEstabCS/PS.UuNoReply “RF problem”
●VS.RAB.FailEstabCS/PS.Cong : Number of Failed CS RAB Establishments due to Congestion “count at best
cell”
VS.RAB.FailEstabCS/PS.ULPower.Cong
VS.RAB.FailEstabCS/PS.DLPower.Cong
VS.RAB.FailEstabCS/PS.ULIUBBand.Cong
VS.RAB.FailEstabCS/PS.DLIUBBand.Cong
VS.RAB.FailEstabCS/PS.ULCE.Cong
VS.RAB.FailEstabCS.DLCE.Cong
VS.RAB.FailEstabCS/PS.Code.Cong
●VS.RAB.FailEstabCS/PS.IubFail : Number of Failed CS RAB Establishments Due to Radio Link Configuration
Failure “Iub or hardware problem + count at best cell”
●VS.RAB.FailEstabCS/PS.TNL : Number of Failed CS RABs Establishments Due to Transport Network Layer
Cause “Iu problem + count at best cell”
VS.RAB.FailEstabCS/PS.CellUpd/ VS.RAB.FailEstabCS.CellUpd.CSFBbe UU interface failure.
And the flow is that RNC wait for CELL update from UE time out.
VS.RAB.FailEstabCS/PS.SRBReset/ VS.RAB.FailEstabCS.SRBReset.CSFB-
VS.RAB.FailEstabCS/PS.UuFail /VS.RAB.FailEstabCS.UuFail.CSFB

If RNC receive “RADIOLINK If RNC can not receive “RADIOLINK

RECONFIGURATION FAILUER” form UE the RECONFIGURATION FAILUER” form UE
counter VS.RAB.FailEstabCS/PS.IubFail is response timeout the counter
triggered VS.RAB.FailEstabCS/PS.IubFail is triggered
VS.RAB.FailEstabCS/PS.CellUpd/ VS.RAB.FailEstabCS.CellUpd.CSFB

CS RAB establishment fails due to RB Setup and Cell Update Overlap

When the RAB setup fails due to the overlap of RB setup and cell update procedures,
the RNC sends the CN a RAB ASSIGNMENT RESPONSE message with a cause value of
"Failure in the Radio Interface Procedure". In this case, this counter is measured in
the best cell that the UE camps on.
VS.RAB.FailEstabCS/PS.IubFail

If RNC receive “RADIOLINK If RNC can not receive “RADIOLINK

RECONFIGURATION FAILUER” form NodeB RECONFIGURATION FAILUER” form NodeB
the counter VS.RAB.FailEstabCS/PS.IubFail response timeout the counter
is triggered VS.RAB.FailEstabCS/PS.IubFail is triggered
VS.RAB.FailEstabCS/PS.TNL

If IU bear setup fail the counter

VS.RAB.FailEstabCS/PS.TNL is triggered
Throughput Counter
Throughput formula

17A.M - Mean Throughput per UE,HSDPA(Kbps)-- VS.HSDPA.DataOutput.Traffic/(VS.HSDPA.All.ScheduledNum * 2)

17.M - Mean Throughput per UE,HSDPA(Kbps)--
[VS.HSDPA.MeanChThroughput.TotalBytes]*8/[VS.HSDPA.MeanChThroughput.Times]

HSDPAUser average throughput (kbps)

The old: VS.HSDPA.MeanChThroughput

The new1: VS.HSDPA.DataOutput.Traffic/(VS.HSDPA.DataTtiNum.User x 2)

<VS.HSDPA.DataOutput.Traffic>
This counter measuresthe traffic data at the MAC-hs layer in the TTIs which the HSDPA user feedback the ACK.
<VS.HSDPA.DataTtiNum.User>
This counter measuresthe number of TTIs when the HSDPA user has data to transmit in the queuebuffer.

There are 3 main differences betweenold formula and new formula as below.
Measurement layer
The old formula – measures at RLC layer, The new formula –measure at MAC-hslayer.
Sampling period
The old formula – fixed sampling period (10ms), The newformula – HSDPA scheduling period ( 2ms).
Data transmission time
The old formula– the TTI which the buffer has data totransfer, The new formula– the TTI which the air interface has
data totransfer.
Throughput

17A.M - Mean Throughput per UE,HSDPA(Kbps)-- VS.HSDPA.DataOutput.Traffic/(VS.HSDPA.All.ScheduledNum * 2)

17.M - Mean Throughput per UE,HSDPA(Kbps)--
[VS.HSDPA.MeanChThroughput.TotalBytes]*8/[VS.HSDPA.MeanChThroughput.Times]
HW

VS.HSDPA.DataOutput.Traffic/
VS.HSDPA.MeanChThr
(VS.HSDPA.DataTtiNum.User x 2)
oughput
MAC-hs layer HSDPA traffic
Numerator - Traffic RLC layer traffic result (traffic) is about 5% greater than RLC
layer
sample period is 2ms, same with TTI
Denominator - Data Transfer Time sample period is 10ms
result is more accurate than 10ms
 The following is an example to show the difference between 10ms and 2ms sample period.
Sample period is the minimum statistics unit. For the following example, total time duration is 10ms, user only is scheduled
in 2 TTI (4ms).
If sample period is 2ms, data transfer time will be counted as 4ms, user throughput = traffic/4ms
If sample period is 10ms, data transfer time will be counted as 10ms, user throughput = traffic/10ms
10ms
Scheduled Not Scheduled Not Scheduled Scheduled Not Scheduled
2ms 2ms 2ms 2ms 2ms
 So 2ms sample period can reflect user throughput more accurately.
Capacity/Congestion
Capacity/Congestion
Capacity/Congestion
Capacity/Congestion
Capacity/Congestion
Capacity/Congestion
LTE counter
Accessibility – RRC Setup Success Rate

 RRC Setup Success Rate (Service)

The RRC setup procedure is triggered by different reasons as identified by the

establishmentCause field in the RRCConnctionRequest message: emergency,
highPriorityAccess, mt-Access, mo-Signalling, mo-Data, and delayTolerantAccess-v1020.
The UE sets the establishmentCause received by eNodeB. Causes except mo-Signalling are
categorized as service related ones, and the cause of mo-Signalling is categorized as signal
related ones.
This KPI evaluates the RRC setup success rate with service related causes in a cell or cluster.

RRC _ ConnectionSuccessservice
RRC _ SSRService   100%
RRC _ ConnectionAttempt service

 RRC Setup Success Rate (Signaling)

This KPI evaluates the RRC setup success rate with signal
related causes (mo-Signalling) in a cell or cluster.

RRC _ ConnectionSuccessSignal
RRC _ SSRSignal  100%
RRC _ ConnectionAttempt Signal
Accessibility – RRC Setup Success Rate

L.RRC.ConnReq.Att…

L.RRC.ConnReq.Succ …
Accessibility – ERAB Setup Success Rate

ERAB Setup Success Rate (VoIP)

This KPI can be used to evaluate the E-RAB setup

success rate for VoIP services (QCI 1 services) in a
cell or cluster.

VoIP _ ERAB _ SetupSuccess

VoIP _ ERAB _ SSR  100%
VoIP _ ERAB _ SetupAttempt

 ERAB Setup Success Rate (All)

This KPI can be used to evaluate the E-RAB setup

success rate for all services including the VoIP
service in a cell or a cluster.

ERAB _ SetupSuccess
ERAB _ SSR ( ALL)  100%
ERAB _ SetupAttempt
Accessibility – ERAB Setup Success Rate

ERAB Setup Attempt Counters

ERAB Setup Success Counters

ERAB Setup Attempt Counters

ERAB Setup Success Counters

Accessibility– Call Setup Success Rate

Call Setup Success Rate (VoIP)

This KPI evaluates the success rate of the whole setup procedure for VoIP services
(QCI 1 service) in a cell or cluster, which mainly includes three phases: RRC setup
phase, S1 Signaling connection establishment phase, and VoIP E-RAB setup phase:

RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess VoIP _ ERAB _ SetupSuccess

VoIP _ CSSR  * * 100%
RRC _ ConnectionAttempt Service S1SIGConnectionEstablishAttempt VoIP _ ERAB _ SetupAttempt

Call Setup Success Rate (All)

This KPI can be used to evaluate the call setup success rate for all services including
the VoIP service in a cell or a cluster. This KPI mainly includes three phases: RRC setup
phase, S1 Signaling connection establishment phase and service E-RAB setup phase:

RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess ERAB _ SetupSuccess

CSSR ( ALL)  * * 100%
RRC _ ConnectionAttempt Service S1SIGConnectionEstablishAttempt ERAB _ SetupAttempt
Accessibility– Call Setup Success Rate
Accessibility – RRC & ERAB Fail counter

POSSIBLE Reasons Counters TO BE MONITORED

RRC rejection due to users license L.RRC.setupfail.rej

Rrc rejection due to high or overload L.RRC.setupfail.resfail

Number erabs per user license, rlc um license L.erab.fail.est Noradiores

Ul/dl gbr resource overload L.erab.fail.est Noradiores

UL RSSI (RTWP) L.erab.fail.est RNL

Cell fluctuation L.erab.fail.est NOreply

Overshooting L.erab.fail.est NOreply

Traffic surges L.erab.fail.est RNL

Alarms/TRANSMISSION/HW ISSUES L.erab.fail.est TNL

Retainability – Call Drop Rate
Call Drop Rate (VoIP)

This KPI can be used to evaluate the call drop rate of VoIP services (QCI 1 services) in a cell or cluster. The call drops
happen when eNodeB actively initiates an E-RAB (with data in buffer) release process by E-RAB Release Indication
or UE Context Release Request message with abnormal causes (the cause other than: Normal Release, Detach, User
Inactivity, cs fallback triggered, UE Not Available For PS Service, Successful Handover or Inter-RAT redirection), and
all of the other E-RAB releases are considered as normal E-RAB release.
VoIP _ ERAB _ Abnormal Re lease
VoIP _ CDR   100%
VoIP _ ERAB _ Re lease
Call Drop Rate (All)

This KPI can be used to evaluate the call drop rate of all services in
a cell or a cluster, including VoIP service.
ERAB _ Abnormal Re lease
CDR ( ALL)  100%
ERAB _ Re lease
Call Drop Rate (Always Online)

This KPI can be used to evaluate the call drop rate of all the services, including the VoIP service, when the always
online state is active. In always online state, the E-RAB number of a UE entering the asynchronous state from
synchronous state will be considered for the KPI calculating.
ERABAbnormalReleaseOfAlwaysOnline
AlwaysOnline _ CDR  100%
ERAB Re leaseOfAlwaysOnline
Retainability – Call Drop Rate

Normal and Abnormal release

Normal and Abnormal release
Counters based on the cause
Counters based on the cause
Retainability – Call Drop Rate

Call Setup Complete Rate (VoIP)

This KPI evaluates the call setup complete rate for VoIP services (QCI 1 services) in a cell or cluster,
which means the rate of the VoIP service can be normally terminated once the UE attempt to set up
the service. And it can include 4 phases: RRC setup phase, S1 Signaling connection establishment
phase, VoIP E-RAB setup phase and VoIP service E-RAB release phase;

RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess VoIP _ ERAB _ SetupSuccess VoIP _ ERAB _ Normal Re lease
VoIP _ CSTR  * * *  100%
RRC _ ConnectionAttempt Service S1SIGConnectionEstablishAttempt VoIP _ ERAB _ SetupAttempt Vo IP _ ERAB _ Re lease

Call Setup Complete Rate (All)

Similar as the preceding KPI, this KPI will evaluate the success rate in totally for 4 phases: RRC setup
phase, S1 Signaling connection establishment phase, service E-RAB setup phase and service E-RAB
release phase;
RRC _ ConnectionSuccessService S1SIGConnectionEstablishSuccess ERAB _ SetupSuccess ERAB _ Normal Re lease
CSTR ( ALL)  * * * 100%
RRC _ ConnectionAttempt Service S1SIGConnectionEstablishAttempt ERAB _ SetupAttempt ERAB _ Re lease

Call Setup Complete Rate (Always Online)

Similar as the preceding KPI, this KPI will evaluate the success rate in totally for 4 phases: RRC setup
phase, S1 Signaling connection establishment phase, service E-RAB setup phase and service E-RAB
release phase (when the always online state is active);
Retainability – Call Drop Rate

By abnormal-release cause, the counters can be classified into five types:

L.E-RAB.AbnormRel.Radio: number of abnormal E-RAB releases caused by radio-layer
problems
L.E-RAB.AbnormRel.TNL: number of abnormal E-RAB releases caused by transport-layer
problems
L.E-RAB.AbnormRel.Cong: number of abnormal E-RAB releases caused by network
congestion
L.E-RAB.AbnormRel.HOFailure: number of abnormal E-RAB releases caused by handover
failures
L.E-RAB.AbnormRel.MME: number of abnormal E-RAB releases caused by EPC problems
Retainability – Call Drop Rate

• By abnormal-release cause, the counters can be classified into five types:

– L.E-RAB.AbnormRel.Radio: number of abnormal E-RAB releases caused by radio-
layer problems
– L.E-RAB.AbnormRel.TNL: number of abnormal E-RAB releases caused by
transport-layer problems
– L.E-RAB.AbnormRel.Cong: number of abnormal E-RAB releases caused by
network congestion
– L.E-RAB.AbnormRel.HOFailure: number of abnormal E-RAB releases caused by
handover failures
– L.E-RAB.AbnormRel.MME: number of abnormal E-RAB releases caused by EPC
problems

• Abnormal E-RAB releases caused by EPC problems

– As shown by points A in figures 1 and 2 on the right, the MME initiates an E-RAB
or UE context release procedure. If the cause value of the E-RAB Release
Command or the UE Context Release Command message received by the
eNodeB from the MME is not Normal Release, Detach, User Inactivity, cs fallback
triggered, or inter-RAT redirection, the cause is counted into the L.E-
RAB.AbnormRel.MME counter.
Retainability – Call Drop Rate

• Abnormal E-RAB releases caused by non-EPC problems

– As shown by point A in figure 3, when the eNodeB sends an E-RAB Release Indication to the
MME, carrying a cause value being radio error, the L.E-RAB.AbnormRel.Radio counter is
incremented; if the cause value indicates a transport-layer problem, the L.E-
RAB.AbnormRel.TNL counter is incremented; if the cause value indicates congestion, the L.E-
RAB.AbnormRel.Cong counter is incremented. If the E-RAB Release Indication requires the
release of multiple E-RABs, related counters are incremented based on the number of
releases of corresponding causes.

– As shown by point A in figure 4, after the eNodeB sends a UE Context Release Request to the
MME, all E-RABs of the UE are released. If the cause value indicates a radio error, the L.E-
RAB.AbnormRel.Radio counter is incremented; if the cause value indicates a transport-layer
problem, the L.E-RAB.AbnormRel.TNL counter is incremented; if the cause value indicates
congestion, the L.E-RAB.AbnormRel.Cong counter is incremented and records abnormal
releases caused by preemption and resource congestion; If the cause value indicates a
handover failure, the L.E-RAB.AbnormRel.HOFailure counter is incremented. Related counters
are incremented based on the number of releases of corresponding causes. Releases are not
counted again when the MME responds with a UE Context Release Command message.
Utilization – DL/UL RB Utility Rate

Downlink Resource Block Utility Rate

This KPI evaluates the downlink RB (Resource Block) utility rate of a cell or cluster.

DLRB _ Used
DLRB _ UtilityRat e  100%
DLRB _ Available

Uplink Resource Block Utility Rate

This KPI evaluates the uplink RB (Resource Block) utility rate of a cell or cluster.

ULRB _ Used
ULRB _ UtilityRate  100%
ULRB _ Available
Utilization – Counter Mapping for RB Utility Rate
Utilization – Counter Mapping for RB Utility Rate

Average CPU Load

This KPI is used to evaluate the CPU usage in busy hours. It indicates the system load. The CPU load is
calculated by averaging the CPU usage ratio in the measurement period.
MeanCPUUtility

Counter Mapping for Average CPU Load

DL/UL Baseband Capacity Licenses
Cell Resources Monitoring
ENodeB Resources Monitoring
ENodeB Resources Monitoring