UMTS Key Performance Indicator and Troubleshooting Counters

(For GP internal uses)

By

Shuvro Kumar Saha

Verified by

RP Regional Optimization Lead, NPO

Reference

HEDex / 3GPP TS 25.331 V11.4.0 (2012-12)

Revision Version: 1

Date: 25-03-2015
Objective & Background
Major rollout on UMTS has already been done in Grameenphone network to cover all districts of Bangladesh. Now the focus has
come to the performance management of UMTS service. As different user groups use different KPIs, formulas and thresholds to
maintain their regular activities, there comes a requirement of a consolidate documentation on some key performance indicators,
their associated counters, formulas and suitable thresholds for the synchronization and make the focus strong to be best in network
test.

This document aims to meet that requirement and also help radio planners and optimization engineers on 3G performance
management in Huawei network system.

Besides the important KPIs, this document also contains the list of troubleshooting counters associated to these KPIs.

Categorization of KPIs
KPIs have been categorized into 4 groups.

1. Accessibility
a. RRC setup success ratio
b. PS RAB setup success ratio
c. PS R99 setup SR
d. CS RAB setup success ratio
e. HSDPA RAB setup success ratio
f. HSUPA RAB setup success ratio
2. Retainability
a. CS Drop Rate
b. 3G MPD
c. PS Drop Rate
d. CS64 Drop Rate
e. CS AMR Drop Rate
f. HSDPA Drop Rate
g. HSUPA Drop Rate
3. Integrity
a. Traffic and Throughput Measurement
b. Utilization
4. Mobility
a. Soft Handover Success Ratio
b. Softer Handover Success Ratio
c. Inter-frequency Hard Handover Success Ratio
d. CS Inter-RAT Handover Out Success Ratio
e. PS Inter-RAT Handover Out Success Ratio
f. Soft Handover Overhead
RRC Setup Success Ratio

Name RRC Setup Success Ratio

Description Description of RRC Setup Success Ratio for service requests:

 The RRC Connection Attempt for service Procedure is complete when the RNC receives an RRC
CONNECTION REQUEST message from the UE. The message contains information about one of the
following service types requested by the UE: For details on the reason types, see section 10.3.3.11 in
3GPP TS 25.331.
 The RRC Setup Success for Service Procedure is complete when the RNC receives an RRC CONNECTION
SETUP COMPLETE message from the UE.

Formula  RRC Setup Success Ratio (Cell.Service) =

( RRC.SuccConnEstab.sum / VS.RRC.AttConnEstab.Sum ) x 100%

Object CELL

Unit/Range %

GPRP Thresholds 98%

Cause for an RRC connection establishment request (section 10.3.3.11 in 3GPP TS 25.331)
Counter Type Cause Detail Counter Type Cause Detail
RRC..OrgConvCall Originating Conversational Call RRC..IRATCCO Inter-RAT Cell Change Order
RRC..OrgStrCall Originating Streaming Call RRC..Reg Registration
RRC..OrgInterCall Originating Interactive Call RRC..Detach Detach
RRC..OrgBkgCall Originating Background Call RRC..OrgHhPrSig Originating High Priority Signaling
RRC..TmConvCall Terminating Conversational Call RRC..OrgLwPrSig Originating Low Priority Signaling
RRC..TmStrCall Terminating Streaming Call RRC..CallReEst Call Re-Establishment
RRC..TmInterCall Terminating Interactive Call RRC..TmHhPrSig Terminating High Priority Signaling
RRC..TmBkgCall Terminating Background Call RRC..TmLwPrSig Terminating Low Priority Signaling
RRC..OrgSubCall Originating Subscribed Traffic Call RRC..Unknown Terminating-Cause Unknown
RRC..EmgCall Emergency Call RRC..MBMSRep MBMS Reception
RRC..IRATCelRes Inter-RAT Cell Re-Selection RRC..MBMSPtp MBMS PTP RB Request
RRC connection rejects measurement
Description The number of failed RRC connection setups in a cell based on failure causes
Counters VS.RRC.FailConnEstab.Cell
Object CELL
Associated VS.RRC.Rej.ULPower.Cong
Counters VS.RRC.Rej.DLPower.Cong
VS.RRC.Rej.ULIUBBand.Cong
VS.RRC.FailConnEstab.Cell
VS.RRC.Rej.DLIUBBand.Cong
VS.RRC.Rej.ULCE.Cong
VS.RRC.Rej.DLCE.Cong
VS.RRC.Rej.Code.Cong
VS.RRC.Rej.NodeBResUnavail
VS.RRC.Rej.RL.Fail
VS.RRC.Rej.TNL.Fail
VS.RRC.FailConnEstab.NoReply
Number of RRC Connection Rejects for Cell (UL Power Congestion)
Number of RRC Connection Rejects for Cell (DL Power Congestion)
Number of RRC Connection Rejects for Cell (UL Iub Bandwidth Congestion)
Number of RRC Connection Rejects for Cell (DL Iub Bandwidth Congestion)
Number of RRC Connection Rejects for Cell (UL CE Resource Congestion)
Number of RRC Connection Rejects for Cell (DL CE Resource Congestion)
Number of RRC Connection Rejects for Cell (Code Resource Congestion)
Number of RRC Connection Rejects Due to NodeB Resource Unavailable
Number of RRC Connection Rejects Due to Radio Link Setup Failure for Cell
Number of RRC Connection Rejects for Cell (Transmission Setup Failure on Iub
Interface )
Number of RRC Connection Rejects Due to Timeout of RRC CONNECT SETUP
COMPLETE for Cell
PS RAB Setup Success Ratio

Name PS RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of all PS services in an RNC or a cluster.
The PS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST
message from the SGSN in the PS domain. The message contains information about one of the following
service types: Conversational services, Streaming services, Interactive Services, Background Services.
The PS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE
message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE
message to the SGSN in the PS domain.

Formula  PS RAB Setup Success Ratio (Cell) =

[(VS.RAB.SuccEstabPS.Conv + VS.RAB.SuccEstabPS.Str + VS.RAB.SuccEstabPS.Int +
VS.RAB.SuccEstabPS.Bkg)
/
(VS.RAB.AttEstabPS.Conv + VS.RAB.AttEstabPS.Str + VS.RAB.AttEstabPS.Int +
VS.RAB.AttEstabPS.Bkg)]
x 100%

Object CELL, RNC

Unit/Range %

GPRP Thresholds 97%

PS R99 RAB Setup Success Rate

Name PS R99 RAB Setup Success Rate

Description This KPI provides the PS R99 RAB setup success rate.
The number of PS R99 RAB setup attempts is measured in the best cell where the UE camps on when the RNC
receives from the PS CN an RAB ASSIGNMENT REQUEST message. After receiving this message, the RNC
attempts to set up an RAB for the service based on the network configuration.
The number of successfully set up PS R99 RABs is measured in the best cell where the UE camps on when the
RNC sends the CN an RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP
COMPLETE message from the UE if the RAB is for a PS R99 service.

Associated Counters PS RAB Setup Success Ratio (Cell)=

(VS.RAB.SuccEstab.PSR99/ VS.RAB.AttEstab.PSR99) * 100%

Object CELL, RNC

Unit/Range %

GP RP Threshold 97%
PS RAB Setup Failure measurement

Description The number of failed PS RAB setup request in a cell based on failure causes

Object CELL

Associated Counter Name Number of Failed PS RAB Establishments for Cell

Counters VS.RAB.FailEstabPS.DLIUBBand.Cong DL Iub Bandwidth Congestion
VS.RAB.FailEstabPS.ULIUBBand.Cong UL Iub Bandwidth Congestion
VS.RAB.FailEstabPS.ULCE.Cong UL CE Congestion
VS.RAB.FailEstabPS.DLCE.Cong DL CE Congestion
VS.RAB.FailEstabPS.Code.Cong Code Congestion
VS.RAB.FailEstabPS.ULPower.Cong UL Power Congestion
VS.RAB.FailEstabPS.DLPower.Cong DL Power Congestion
VS.RAB.FailEstabPS.HSUPAUser.Cong Failures When the Maximum Number of HSUPA UEs Is Reached
VS.RAB.FailEstabPS.HSDPAUser.Cong Failures When the Maximum Number of HSDPA UEs Is Reached
VS.RAB.FailEstabPS.SRBReset Signaling RLC Reset
VS.RAB.FailEstabPS.IubFail Radio Link Configuration Failure for Cell
VS.RAB.FailEstabPS.CellUpd Concurrent Procedures
VS.RAB.FailEstabPS.RBIncCfg UU interface invalid configuration
VS.RAB.FailEstabPS.UuNoReply No reply of UE during the RB setup procedure
VS.RAB.FailEstabPS.PhyChFail Physical channel failure of UE during the RB setup procedure
VS.RAB.FailEstabPS.RBCfgUnsupp Configuration unsupported of UE during the RB setup procedure
VS.RAB.FailEstabPS.TNL Transport Network Layer Cause
VS.RAB.FailEstabPS.RNL Radio Network Layer Cause
VS.RAB.FailEstabPS.UuFail Uu Interface Configuration Failure for Cell
VS.RAB.FailEstabPS.Unsp Unsupported Capabilities
VS.RAB.FailEstabPS.Cong All Congestion

Counter VS.RAB.FailEstabPS.TNL
Relationship VS.RAB.FailEstabPS.SRBReset
VS.RAB.FailEstabPS.IubFail
VS.RAB.FailEstabPS.CellUpd
VS.RAB.FailEstabPS.RBIncCfg
TOTAL NUMBER OF PS RAB FAIL

VS.RAB.FailEstabPS.UuNoReply
VS.RAB.FailEstabPS.UuFail
VS.RAB.FailEstabPS.RNL

VS.RAB.FailEstabPS.PhyChFail
VS.RAB.FailEstabPS.RBCfgUnsupp
VS.RAB.FailEstabPS.DLIUBBand.Cong
VS.RAB.FailEstabPS.ULIUBBand.Cong
VS.RAB.FailEstabPS.Cong/
VS.RAB.FailEstabPS.Unsp

VS.RAB.FailEstabPS.ULCE.Cong
VS.RAB.FailEstabPS.DLCE.Cong
VS.RAB.FailEstabPS.Code.Cong
VS.RAB.FailEstabPS.ULPower.Cong
VS.RAB.FailEstabPS.DLPower.Cong
VS.RAB.FailEstabPS.HSUPAUser.Cong
VS.RAB.FailEstabPS.HSDPAUser.Cong
CS RAB Setup Success Ratio

Name CS RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of all CS services in an RNC or a cluster.
The CS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST
message from the CN in the CS domain. The message contains information about one of the following service
types: Conversational Services, streaming Services.
The CS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE
message from UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message
to the CN in the CS domain.

Formula  CS RAB Setup Success Ratio (Cell) =

[(VS.RAB.SuccEstabCS.Conv + VS.RAB.SuccEstabCS.Str + VS.IRATHO.SuccOutCS.DR)/
(VS.RAB.AttEstabCS.Conv + VS.RAB.AttEstabCS.Str)] x 100%

Object CELL, RNC

Unit/Range %

GPRP Threshold 98%

Note As direct retry is off, VS.IRATHO.SuccOutCS.DR can be excluded from the equation.

CS64 RAB Setup Success Ratio

Name CS64 RAB Setup Success Ratio

Formula  CS64 RAB Setup Success Ratio =

(VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64)*100

Object CELL , RNC

Unit/Range %

GPRP Threshold 95%

CS RAB Setup Failure measurement

Description The number of failed CS RAB setup request in a cell based on failure causes

Object CELL

Associated Counter Name Number of Failed CS RAB Establishments for Cell

Counters VS.RAB.FailEstabCS.DLIUBBand.Cong DL Iub Bandwidth Congestion
VS.RAB.FailEstabCS.ULIUBBand.Cong UL Iub Bandwidth Congestion
VS.RAB.FailEstabCS.ULCE.Cong UL CE Congestion
VS.RAB.FailEstabCS.DLCE.Cong DL CE Congestion
VS.RAB.FailEstabCS.Code.Cong Code Congestion
VS.RAB.FailEstabCS.ULPower.Cong UL Power Congestion
VS.RAB.FailEstabCS.DLPower.Cong DL Power Congestion
VS.RAB.FailEstabCS.SRBReset Signaling RLC Reset
VS.RAB.FailEstabCS.IubFail Radio Link Configuration Failure for Cell
VS.RAB.FailEstabCS.CellUpd Concurrent Procedures
VS.RAB.FailEstabCS.RBIncCfg UU interface invalid configuration
VS.RAB.FailEstabCS.UuNoReply No reply of UE during the RB setup procedure
VS.RAB.FailEstabCS.PhyChFail Physical channel failure of UE during the RB setup procedure
VS.RAB.FailEstabCS.RBCfgUnsupp Configuration unsupported of UE during the RB setup procedure
VS.RAB.FailEstabCS.TNL Transport Network Layer Cause
VS.RAB.FailEstabCS.RNL Radio Network Layer Cause
VS.RAB.FailEstabCS.UuFail Uu Interface Configuration Failure for Cell
VS.RAB.FailEstabCS.Unsp Unsupported Capabilities
VS.RAB.FailEstabCS.Cong All Congestion

Counter VS.RAB.FailEstabCS.TNL
Relatonship VS.RAB.FailEstabCS.SRBReset
VS.RAB.FailEstabCS.IubFail
VS.RAB.FailEstabCS.CellUpd
VS.RAB.FailEstabCS.RBIncCfg
TOTAL NUMBER OF CS RAB FAIL

VS.RAB.FailEstabCS.UuNoReply
VS.RAB.FailEstabCS.UuFail
VS.RAB.FailEstabCS.RNL

VS.RAB.FailEstabCS.PhyChFail
VS.RAB.FailEstabCS.RBCfgUnsupp
VS.RAB.FailEstabCS.DLIUBBand.Cong
VS.RAB.FailEstabCS.Cong/
VS.RAB.FailEstabCS.Unsp

VS.RAB.FailEstabCS.ULIUBBand.Cong

VS.RAB.FailEstabCS.ULCE.Cong

VS.RAB.FailEstabCS.DLCE.Cong

VS.RAB.FailEstabCS.Code.Cong

VS.RAB.FailEstabCS.ULPower.Cong

VS.RAB.FailEstabCS.DLPower.Cong
HSDPA RAB Setup Success Ratio

Name HSDPA RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of PS services that are carried by HSDPA in a cluster.
The HSDPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST
message from the CN for setting up the HSDPA service.
The HSDPA RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE
message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE
message to the CN.

Formula HSDPA RAB Setup Success Ratio =

(VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%

Object CELL , RNC

Unit/Range %

GPRP Threshold 97%

HSDPA RAB Setup Failure measurement

Description The number of failed HSDPA RAB setup request in a cell based on failure causes

Counters VS.HSDPA.RAB.FailEstab

Object CELL

Associated Counter Name Number of Failed HSDPA RAB Establishments for Cell
Counters VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong DL Iub Bandwidth Congestion
VS.HSDPA.RAB.FailEstab.DLPower.Cong DL Power Congestion
VS.HSDPA.RAB.FailEstab.Other VS.HSDPA.RAB.FailEstab – (VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong +
VS.HSDPA.RAB.FailEstab.DLPower.Cong)
HSUPA RAB Setup Success Ratio

Name HSUPA RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of the HSUPA service in an RNC or a cluster.
The HSUPA RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE
message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE
message to the CN.
The HSUPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST
message from the CN for setting up the HSUPA service.

Associated Counters HSUPA RAB Setup Success Ratio =

(VS.HSUPA.RAB.SuccEstab/VS.HSUPA.RAB.AttEstab) x 100%

Object CELL , RNC

Unit/Range %

GPRP Threshold 95%

HSUPA RAB Setup Failure measurement

Description The number of failed HSUPA RAB setup request in a cell based on failure causes

Counters VS.HSUPA.RAB.FailEstab

Object CELL

Associated Counter Name
Counters VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong
VS.HSDPA.RAB.FailEstab.DLPower.Cong
VS.HSDPA.RAB.FailEstab.ULCE.Cong
VS.HSDPA.RAB.FailEstab.Other
Number of Failed HSUPA RAB Establishments for Cell
DL Iub Bandwidth Congestion
DL Power Congestion
UL CE Congestion
VS.HSUPA.RAB.FailEstab – (VS.HSDPA.RAB.FailEstab.DLIUBBand.Cong +
VS.HSDPA.RAB.FailEstab.DLPower.Cong +
VS.HSDPA.RAB.FailEstab.ULCE.Cong)
CS Drop Rate

Name CS Service Drop Ratio

Description This KPI provides the ratio of the CS RAB abnormal Releases to the total CS RAB Releases (Normal Release +
Abnormal Release). This KPI is used to check the retainabililty of CS Service within the UTRAN (RNC or
Cluster).
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exceptions.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with the causes other
than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RNC
measures the items according to the service types in the best cell that the UE camps on if the released RABs
belong to PS domain.

Associated Counters CS Service Drop Ratio (Cell) = [VS.RAB.AbnormRel.CS/(VS.RAB.AbnormRel.CS+ VS.RAB.NormRel.CS)] x

100%

Object CELL, RNC

Unit/Range %

GPRP Threshold 1%

Note This KPI involves CS call drops due to authentication failure during PS security mode in the cell. You can
subtract VS.RAB.AbnormRel.CS.Security from the numerator of the formula to decrease the value of this KPI.

3G MPD

Name 3G Voice MPD

Description This KPI provides minutes per drop of 3G voice service;

Associated Counters 3G Voice MPD = [60 * VS.AMR.Erlang.BestCell ] / [ 2 * VS.RAB.AbnormRel.AMR]

Object CELL, RNC

Unit/Range %

GPRP Threshold According to clutter

Note VS.AMR.Erlang.BestCell is equivalent Erlang for AMR Services for Best Cell. In M2000 this measurement item
provides the mean number of UEs for 30 min resolution. In PRS, for different resolution it accumulates the
counter value of 30 min resolution. Thus VS.AMR.Erlang.BestCell actually shows double erlang value in one
hour.
CS RAB Abnormal Release measurement

Description The number of CS abnormal release based on different causes

Object CELL

Counters Counters Description

VS.RAB.AbnormRel.CS.IuAAL2
VS.RAB.AbnormRel.CS.RF
VS.RAB.AbnormRel.CS.OM
VS.RAB.AbnormRel.CS.Preempt
VS.RAB.AbnormRel.CS.UTRANgen
VS.RAB.AbnormRel.CS.OLC
VS.RAB.AbnormRel.CS.Security
VS.RAB.AbnormRel.CS.RF.UuNoReply
VS.RAB.AbnormRel.CS.RF.ULSync
VS.RAB.AbnormRel.CS.RF.SRBReset
Number of CS RABs Abnormally Released Due to Iu Interface AAL2
Link Failure for Cell
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)
Number of CS RAB Release Requests Due to OM Intervention
Number of CS RAB Release Attempts Due to RAB Preemption
Number of CS RAB Abnormal Releases Triggered by RNC Due to
UTRAN Cause for Cell
Number of CS RAB Release Attempts Due to Congestion for Cell
Number of CS RABs Abnormally Released Due to Security Mode
Procedure Failure for Cell
Number of CS RABs Abnormally Released Due to RF for Cell
(Failure in the Radio Interface Procedure)
Number of CS RABs Abnormally Released Due to RF (Uplink
Synchronization Fail)
Number of CS RABs Abnormally Released (Signaling RLC Reset)

Counter VS.RAB.AbnormRel.CS.IuAAL2
Relationship VS.RAB.AbnormRel.CS.OM
VS.
RAB. VS.RAB.AbnormRel.CS.Preempt
AbnormRel. VS.RAB.AbnormRel.CS.UTRANgen
AMR VS. VS.RAB.AbnormRel.CS.OLC
RAB.
AbnormRel. VS.RAB.AbnormRel.CS.Security
CS VS.RAB.AbnormRel.CS.RF.UuNoReply
VS. VS.RAB.AbnormRel.CS.RF.SRBReset
RAB. VS.RAB.AbnormRel.CS.RF
AbnormRel. VS.RAB.AbnormRel.CS.RF.ULSync
CS64 RAB.AbnormRel.CS.RF.Other
RAB.AbnormRel.CS.Other
PS Drop Rate

Name PS Call Drop Ratio (PCH)

Description Normal PS Call Drop Ratio KPI provides the ratio of the PS RAB abnormal Releases to the total PSRAB Releases
(Normal Release + Abnormal Release) and is used to check the retainabililty of PS Service within the UTRAN
(RNC or Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exception.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the
following information: "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization",
the RNC measures the items according to the service types in the best cell that the UE camps on if the
released RABs belong to PS domain. Compared with PS Call Drop Ratio, these KPIs take the PCH state into
account.
Since more and more smart phones camp on and keep Always Online in the network, if the PCH transition is
switched on while no data transferring for a period, these UEs usually transfer from connected state into Cell
PCH state instead of Idle state, that is, the occasion of RAB normal release for transferring into IDLE state will
greatly decrease than that in the conditions without PCH transition.
From user's point of view, the occasion of a UE transferring into PCH state should be considered as a normal
RAB release for calculating the formula of PS Call Drop Ratio.

Associated Counters  PS Call Drop Ratio with PCH (Cell) =

[(VS.RAB.AbnormRel.PS - VS.RAB.AbnormRel.PS.PCH - VS.RAB.AbnormRel.PS.D2P -
VS.RAB.AbnormRel.PS.F2P )
/
(VS.RAB.AbnormRel.PS + VS.RAB.NormRel.PS - VS.RAB.AbnormRel.PS.PCH - VS.RAB.NormRel.PS.PCH
+ VS.DCCC.D2P.Succ + VS.DCCC.Succ.F2P )]
x 100%

Object CELL, RNC

Unit/Range % GPRP Threshold 3%

Note The occasion of a UE transferring into PCH state should be considered as a normal RAB release for calculating
the formula of PS Call Drop Ratio. Why VS.RAB.normRel.PS.PCH is subtracted in the denominator. Because If
a UE transfers into PCH state and then go to the IDLE state, it will be counted twice respectively in
VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P) and VS.RAB.NormRel.PS. The same reason as
VS.RAB.AbnormRel.PS.PCH. The measurement object of the counters in Sum{*} is the cell, the RNC level KPI
can be calculated approximately by aggregating all the cell level counters in the SRNC. Due to the counters
are counted in the best cell of active set, If the best cell for the PS RAB Establishment located in DRNC via Iur
interface, this scenario is not taken into account in the formula.
CS64 Drop Rate

Name CS64 Call Drop Ratio

Description This KPI provides the ratio of the video call Service Erlang to the video call RAB Abnormal Releases, which
indicates the video call average Erlang per video call drop within the UTRAN (RNC or Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exception.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the
following information: "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization",
the RNC measures the items according to the service types in the best cell that the UE camps on if the
released RABs belong to PS domain.

Associated Counters VP Traffic Drop Ratio (Cell) =

VS.RAB.AbnormRel.CS64/ (VS.RAB.AbnormRel.CS64 + VS.RAB.NormRel.CS64) *100

Object CELL, RNC

Unit/Range %

GP RP Threshold 5%

CS AMR Drop Rate

Name CS AMR Service Drop Ratio

Description This KPI provides the ratio of the CS voice service RAB abnormal Releases to the total CS voice RAB Releases
(Normal Release + Abnormal Release). This KPI is used to check the retainabililty of CS voice Service within
the UTRAN (RNC or Cluster).
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exceptions.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with the causes other
than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RNC
measures the items according to the service types in the best cell that the UE camps on if the released RABs
belong to PS domain.

Associated Counters CS AMR Service Drop Ratio (Cell) = [VS.RAB.AbnormRel.AMR/( VS.RAB.AbnormRel.AMR +

VS.RAB.NormRel.AMR)] x 100%

Object CELL, RNC

Unit/Range %

GPRP Threshold 1%
PS RAB Abnormal Release measurement

Description The number of PS abnormal release based on different causes

Object CELL

Counters Counters Description

VS.RAB.AbnormRel.PS.RF
VS.RAB.AbnormRel.PS.OM
VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC
VS.RAB.AbnormRel.PS.Security
VS.RAB.AbnormRel.PS.UTRANgen
VS.RAB.AbnormRel.PS.RF.ULSync
VS.RAB.AbnormRel.PS.RF.UuNoReply
VS.RAB.AbnormRel.PS.RF.SRBReset
VS.RAB.AbnormRel.PS.RF.TRBReset
Abnormally Released Due to RF for Cell
Abnormal Released Due to O&M Intervention for Cell
Abnormal Released Due to RAB Preemption for Cell
Abnormally Released Due to GTPU Failure for Cell
Number of PS Domain RABs Released Due to Congestion for Cell
Abnormally Released Due to Security Mode Procedure Failure for
Cell
Number of Abnormally Released PS RABs Triggered by RNC for Cell
Abnormally Released for Cell (Uplink Synchronization Failure)
Abnormally Released Due to RF for Cell (Failure in the Radio
Interface Procedure)
Abnormally Released Due to Signaling RLC Reset for Cell
Abnormally Released for Cell (Traffic RLC Reset)

Counter VS.RAB.AbnormRel.PS.OM
Relationship VS.RAB.AbnormRel.PS.Preempt
VS.RAB.AbnormRel.PS.GTPULoss
VS.RAB.AbnormRel.PS.OLC
VS.RAB.AbnormRel.PS.Security
VS.RAB.AbnormRel.PS
VS.RAB.AbnormRel.PS.UTRANgen
VS.RAB.AbnormRel.PS.RF.ULSync
VS.RAB.AbnormRel.PS.RF.UuNoReply
VS.RAB.AbnormRel.PS.RF
VS.RAB.AbnormRel.PS.RF.SRBReset
VS.RAB.AbnormRel.PS.RF.TRBReset
HSDPA Drop Ratio

Name HSDPA Call Drop Ratio (PCH)

Description HSDPA Call Drop Ratio KPI normally provides the ratio of the HSDPA RAB abnormal Releases to the total HSDPA
RAB Releases (Normal Release+ Abnormal Release) and is used to check the retainabililty of HSDPA Service
within the UTRAN (RNC or Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exception. If
the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the following
information: "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RNC
measures the items according to the service types in the best cell that the UE camps on if the released RABs
belong to PS domain.
Since more and more smart phones camp on and keep Always Online in the network, if the PCH transition is
switched on while no data transferring for a period, these UEs usually transfer from connected state into Cell
PCH state instead of Idle state, that is, the occasion of RAB normal release for transferring into IDLE state will
greatly decrease than that in the conditions without PCH transition.
From user's point of view, the occasion of a UE transferring into PCH state should be considered as a normal RAB
release for calculating the formula of PS Call Drop Ratio.

Associated HSDPA Service Drop Ratio with PCH (Cell) =

Counters [(VS.HSDPA.RAB.AbnormRel - VS.HSDPA.RAB.AbnormRel.H2P)
/
(VS.HSDPA.RAB.AbnormRel + VS.HSDPA.RAB.NormRel + VS.HSDPA.HHO.H2D.SuccOutIntraFreq +
VS.HSDPA.HHO.H2D.SuccOutInterFreq + VS.HSDPA.H2D.Succ + VS.HSDPA.H2F.Succ +
VS.HSDPA.H2P.Succ)
] x 100

Object CELL, RNC

Unit/Range % GPRP Threshold 3%

Note RNC level KPI is calculated approximately by aggregating all the Cell and Iur level counters in SRNC. The
successful channel transition is considered as normal HSDPA RAB release (Including the transitions due to
mobility).The occasion of a UE transferring out of PS HS-DSCH Channel state (H2D, H2F, H2P) should be
considered as a normal RAB release for calculating the formula of PS HSDPA Call Drop Ratio.
HSUPA Drop Ratio

Name HSUPA Call Drop Ratio (PCH)

Description This KPI provides the ratio of the HSUPA RAB abnormal Releases to the total HSUPARAB Releases (Normal
Release + Abnormal Release) and is used to check the retainabililty of HSUPA Service of the UTRAN (RNC or
Cluster).
Description of RAB Abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exception.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the
following information: "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization",
the RNC measures the items according to the service types in the best cell that the UE camps on if the
released RABs belong to PS domain.
Since more and more smart phones camp on and keep Always Online in the network, if the PCH transition is
switched on while no data transferring for a period, these UEs usually transfer from connected state into Cell
PCH state instead of Idle state, that is, the occasion of RAB normal release for transferring into IDLE state will
greatly decrease than that in the conditions without PCH transition.
From user's point of view, the occasion of a UE transferring into PCH state should be considered as a normal
RAB release for calculating the formula of PS Call Drop Ratio.

Associated Counters  HSUPA Call Drop Ratio with PCH (Cell) =

[(VS.HSUPA.RAB.AbnormRel - VS.HSUPA.RAB.AbnormRel.E2P )/
(VS.HSUPA.RAB.AbnormRel + VS.HSUPA.RAB.NormRel + VS.HSUPA.HHO.E2D.SuccOutIntraFreq +
VS.HSUPA.HHO.E2D.SuccOutInterFreq + VS.HSUPA.E2F.Succ + VS.HSUPA.E2D.Succ +
VS.HSUPA.E2P.Succ )]
x 100%

Object CELL, RNC

Unit/Range %

GPRP Threshold 5%

Note RNC level KPI is calculated approximately by aggregating all the Cell and Iur level counters in SRNC.
The successful channel transition is considered as normal E-DCH release (Including the transitions due to
mobility).
TRAFFIC & THROUGHPUT MEASUREMENT

KPI COUNTERS & EQUATIONS

HSDPA Data
HSDPA Data Volume (GB) = VS.HSDPA.MeanChThroughput.TotalBytes / (1024* 1024 * 1024)
Volume (GB)

HSUPA Data
HSDPA Data Volume (GB) = VS.HSUPA.MeanChThroughput.TotalBytes / (1024* 1024 * 1024)
Volume (GB)

CS Voice Traffic
CS Voice Traffic (Erlang) = [ VS.AMR.Erlang.BestCell / 2]
(Erlang)

R99 PS DL Data R99 PS DL Data (GB) =

(GB) (VS.PS.Bkg.DL.8.Traffic + VS.PS.Bkg.DL.16.Traffic + VS.PS.Bkg.DL.32.Traffic + VS.PS.Bkg.DL.64.Traffic +
VS.PS.Bkg.DL.128.Traffic + VS.PS.Bkg.DL.144.Traffic + VS.PS.Bkg.DL.256.Traffic + VS.PS.Bkg.DL.384.Traffic +
VS.PS.Int.DL.8.Traffic + VS.PS.Int.DL.16.Traffic + VS.PS.Int.DL.32.Traffic + VS.PS.Int.DL.64.Traffic +
VS.PS.Int.DL.128.Traffic + VS.PS.Int.DL.144.Traffic + VS.PS.Int.DL.256.Traffic + VS.PS.Int.DL.384.Traffic +
VS.PS.Str.DL.8.Traffic + VS.PS.Str.DL.16.Traffic + VS.PS.Str.DL.32.Traffic + VS.PS.Str.DL.64.Traffic +
VS.PS.Str.DL.128.Traffic + VS.PS.Str.DL.144.Traffic + VS.PS.Str.DL.256.Traffic + VS.PS.Str.DL.384.Traffic +
VS.PS.Conv.DL.Traffic)
/(8*1024*1024*1024)

R99 PS UL Data R99 PS UL Data (GB) =

(GB) (VS.PS.Bkg.UL.8.Traffic + VS.PS.Bkg.UL.16.Traffic + VS.PS.Bkg.UL.32.Traffic + VS.PS.Bkg.UL.64.Traffic +
VS.PS.Bkg.UL.128.Traffic + VS.PS.Bkg.UL.144.Traffic + VS.PS.Bkg.UL.256.Traffic + VS.PS.Bkg.UL.384.Traffic +
VS.PS.Int.UL.8.Traffic + VS.PS.Int.UL.16.Traffic + VS.PS.Int.UL.32.Traffic + VS.PS.Int.UL.64.Traffic +
VS.PS.Int.UL.128.Traffic + VS.PS.Int.UL.144.Traffic + VS.PS.Int.UL.256.Traffic + VS.PS.Int.UL.384.Traffic +
VS.PS.Str.UL.8.Traffic + VS.PS.Str.UL.16.Traffic + VS.PS.Str.UL.32.Traffic + VS.PS.Str.UL.64.Traffic +
VS.PS.Str.UL.128.Traffic + VS.PS.Conv.UL.Traffic)
/(8*1024*1024*1024)

CS64 VP Traffic CS64 VP Traffic = [ VS.VP.Erlang.BestCell / 2 ]

(Erlang)
UTILIZATION

KPI COUNTERS & EQUATIONS GPRP Value

Equation:
UL CE UTILIZATION UL Mean CE Used Number / Defined UL CE * 100 80%
Resolution : weekly 3BH data for UL Mean CE Used Number

Equation:
DL CE UTILIZATION DL Mean CE Used Number / Defined DL CE * 100 80%
Resolution : weekly 3BH data

VS.Mean.TCP (Watt) / 20 *100

TCP UTILIZATION 80%
Resolution : weekly 3BH data

VS.MeanRTWP
RTWP (dBm) -100 dBm
Resolution : weekly 3BH data

Equation:
VS.LGCPRT.PEAK.TXRATE / Defined Iub BW (kbit) *100
IuB UTILIZATION 90%
Resolution : weekly 3BH data
VS.LGCPRT.PEAK.TXRATE is IPPATH data

VS.OVSF.UsageRate =
(([VS.MultRAB.SF4]+[VS.SingleRAB.SF4])*{64}+([VS.MultRAB.SF8]
+[VS.SingleRAB.SF8])*{32}
OVSF CODE +([VS.MultRAB.SF16]+[VS.SingleRAB.SF16])*{16}
UTILIZATION +([VS.MultRAB.SF32]+[VS.SingleRAB.SF32])*{8}+([VS.MultRAB.SF64] 90%
+[VS.SingleRAB.SF64])*{4} +([VS.MultRAB.SF128]
+[VS.SingleRAB.SF128])*{2}
+([VS.MultRAB.SF256]+[VS.SingleRAB.SF256]))
/{256}

PDSCH CODE
UTILIZATION VS.PdschCodeUsed.Mean / VS.PdschCodeAvail.Mean * 100 90%
Soft Handover Success Ratio

Name Soft Handover Success Ratio

Description This KPI is used to check the soft handover success ratio in an RNC or in a Cluster, including softer handover.
 The Successful Soft Handover (including softer handovers) procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover (including
the softer handover) procedure.
 The attempt procedure is complete when the RNC sends an ACTIVE SET UPDATE message to the UE.

Formula Soft Handover Success Ratio (Cell) =

[(VS.SHO.SuccRLAdd+ VS.SHO.SuccRLDel)/(VS.SHO.AttRLAdd+VS.SHO.AttRLDel)] x 100%

Object RNC, CELL

Unit/Range %

GPRP Threshold 99%

Service wise Soft Handover Success Ratio

KPI COUNTERS & EQUATIONS GPRP Value

AMR Soft Handover AMR Soft Handover Success Ratio = 99%

Success Ratio [(VS.SHO.AMR.Succ)/(VS.SHO.AMR.Att)] x 100%

CS64 Soft Handover CS64 Soft Handover Success Ratio =

99%
Success Ratio [(VS.SHO.CS64.Succ)/(VS.SHO.CS64.Att)] x 100%

PS Soft Handover PS services Soft Handover Success Ratio =

99%
Success Ratio [(VS.SHO.PS.Succ)/(VS.SHO.PS.Att)] x 100%
Softer Handover Success Ratio

Name Softer Handover Success Ratio

Description This KPI is used to check the softer handover success ratio in an RNC or a Cluster, including softer handover.
 The Successful Softer Handover procedure is complete when the RNC receives an ACTIVE SET UPDATE
COMPLETE message from the UE during the softer handover procedure.
 The attempt procedure is complete when the RNC sends an ACTIVE SET UPDATE message to the UE.

Formula Softer Handover Success Ratio (Cell) =

[(VS.SoHO.SuccRLAdd+VS.SoHO.SuccRLDel)/(VS.SoHO.AttRLAdd+VS.SoHO.AttRLDel)] x 100%

Object RNC, CELL

Unit/Range %

GPRP Threshold 98.5%

Inter-frequency Hard Handover Success Ratio

Name Inter-frequency Hard Handover Success Ratio

Description This KPI is used to check the inter-frequency hard handover success ratio in an RNC or a Cluster.
The Inter-frequency Hard Handover Success procedure is complete when RNC received a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from the UE.
The Inter-frequency Hard Handover attempts procedure starts when RNC sends a PHYSICAL CHANNEL
RECONFIGURATION message to the UE. In this case the RNC measures the counter.

Associated Counters Inter-frequency Hard Handover Success Ratio (Cell) =

(VS.HHO.SuccInterFreqOut/VS.HHO.AttInterFreqOut) x 100%

Object RNC, CELL

Unit/Range %

GPRP Threshold 98%

CS Inter-RAT Handover Out Success Ratio

Name CS Inter-RAT Handover Out Success Ratio

Description This KPI is used to indicate the success ratio of CS Outgoing inter-RAT handovers in an RNC or a Cluster.
The CS inter-RAT Handover Success procedure is complete when the RNC receives an IU RELEASE COMMAND
message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" after
sending a HANDOVER FROM UTRAN COMMAND message during the CS outgoing inter-RAT handover. In this
case, the outgoing handover succeeds and this counter is measured.
Number of CS W2G inter-RAT handover attempts = Number of HANDOVER FROM UTRAN COMMAND
messages sent from the RNC during CS outgoing inter-RAT handovers - Number of CS inter-RAT handover
cancellations caused by UE's failures in receiving the message

Associated Counters CS Inter-RAT Handover Out Success Ratio (Cell) =

[IRATHO.SuccOutCS/IRATHO.AttOutCS] x 100%

Object RNC, CELL

Unit/Range %

GPRP Threshold 98%

PS Inter-RAT Handover Out Success Ratio

Name PS Inter-RAT Handover Out Success Ratio

Description This KPI is used to indicate the success ratio of PS outgoing inter-RAT handover initiated by the RNC or in the
best cell.
The PS W2G Inter-RAT Outgoing Handover successes procedure is complete when the RNC sends the RANAP
IU RELEASE COMPLETE message after receiving the IU RELEASE COMMAND message with the cause of
"Successful Relocation", "Normal Release" or "Network Optimization." In this case, the PS outgoing inter-RAT
handover succeeds and the counter is measured.
Number of PS W2G inter-RAT handover attempts = Number of CELL CHANGE ORDER FROM UTRAN messages
sent from the RNC during PS outgoing inter-RAT handovers - Number of PS inter-RAT handover cancellations
caused by UE's failures in receiving the message

Associated Counters PS Inter-RAT Handover Out Success Ratio (Cell) =

[IRATHO.SuccOutPSUTRAN/IRATHO.AttOutPSUTRAN] x 100%

Object RNC, CELL

Unit/Range %

GPRP Threshold 95%

Soft Handover Overhead

KPI Name Soft Handover Overhead

Concept

A1: Number of UEs with 1 RL

B1: Number of UEs with 2 RLs
C1: Number of UEs with 3 RLs
D1: Number of UEs with 4 RLs
E1: Number of UEs with 5 RLs
F1: Number of UEs with 6 RLs.

Description This KPI is used to check the consumption of network resources due to soft handover in a Cell. It considered
the radio link quantity during the soft handover.
The Cell level KPI is only available for cells in a cluster. From A1 to F1 count the mean number of UEs with
different quantity of Radio Links (1~6 radio links) in the Cell of the active set.

Formula Soft Handover Overhead (Cell) =

[(VS.SHO.AS.1RL+VS.SHO.AS.2RL + VS.SHO.AS.3RL + VS.SHO.AS.4RL + VS.SHO.AS.5RL +
VS.SHO.AS.6RL )
/
(VS.SHO.AS.1RL+
VS.SHO.AS.2RL /2 +
VS.SHO.AS.3RL /3 +
VS.SHO.AS.4RL /4 +
VS.SHO.AS.5RL /5 +
VS.SHO.AS.6RL /6) -1]
x 100%

Object CELL

Unit/Range %

GP RP Threshold 30%

Note VS.SHO.Factor.RL.Cell * 100% can also be used.

Conclusion
This short handbook contains the brief description of important UMTS KPIs and troubleshooting counters. For the detail description,
please check out the related reference. Other KPIs can be incorporated here according to the requirements of user groups. However,
these KPIs and counters are recommended to be incorporated in single PRS template for the efficient uses. Quarterly revision of this
document is recommended. A new focus can be initiated on the detail description of the improvement scope of these KPIs.