You are on page 1of 44

HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

BSC6900 GU Product Documentation


Product Version: V900R012C01
Library Version: 09
Date: 12/5/2011

For any question, please contact us.


Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.

UMTS Service KPI


Contents
1 UMTS Service KPI
1.1 RAN KPI Reference
1.1.1 Changes in the RAN KPI Reference
1.1.2 Accessibility
1.1.2.1 IU Paging Success Ratio
1.1.2.2 RRC Setup Success Ratio
1.1.2.3 Radio Access Success Ratio
1.1.2.4 PS Radio Access Success Ratio
1.1.2.5 CS Radio Access Success Ratio
1.1.2.6 AMR RAB Setup Success Ratio
1.1.2.7 VP RAB Setup Success Ratio
1.1.2.8 CS RAB Setup Success Ratio
1.1.2.9 PS RAB Setup Success Ratio
1.1.2.10 HSDPA RAB Setup Success Ratio
1.1.2.11 HSUPA RAB Setup Success Ratio
1.1.2.12 PS E-FACH RAB Setup Success Ratio
1.1.2.13 CS over HSPA RAB Setup Success Ratio
1.1.2.14 HSDPA 64QAM RAB Setup Success Ratio
1.1.2.15 HSDPA MIMO RAB Setup Success Ratio
1.1.2.16 HSDPA DC RAB Setup Success Ratio
1.1.2.17 HSDPA MIMO64QAM RAB Setup Success Ratio
1.1.2.18 PTM Channel Setup Success Ratio
1.1.2.19 PTP Channel Setup Success Ratio
1.1.2.20 RRC Congestion Ratio
1.1.2.21 CS RAB Congestion Ratio
1.1.2.22 PS RAB Congestion Ratio
1.1.3 Availability
1.1.3.1 Worst Cell Ratio
1.1.3.2 Paging Congestion Ratio
1.1.3.3 Call Admission Refused Ratio
1.1.3.4 Congested Cell Ratio
1.1.3.5 Radio Network Unavailability Ratio
1.1.3.6 Average CPU Load
1.1.3.7 IUB Bandwidth Utilizing Ratio (UL)
1.1.3.8 IUB Bandwidth Utilizing Ratio (DL)
1.1.3.9 Cell Unavailability duration
1.1.3.10 HSDPA Unavailability duration
1.1.3.11 HSUPA Unavailability duration
1.1.3.12 CE Consumption for a NodeB Cell
1.1.3.13 Hardware Configured CE for a NodeB
1.1.3.14 Shared Group Configured License CE for a NodeB
1.1.3.15 Shared Group License CE Consumption for a NodeB
1.1.3.16 License Group Configured CE for a NodeB
1.1.3.17 License Group CE Consumption for a NodeB
1.1.3.18 RTWP (Received Total Wideband Power)
1.1.3.19 TCP (Transmitted Carrier Power)
1.1.3.20 R99 Code Utilization
1.1.4 Coverage
1.1.4.1 UL Interference Cell Ratio
1.1.4.2 Soft Handover Overhead
1.1.5 Mobility
1.1.5.1 Soft Handover Success Ratio
1.1.5.2 Softer Handover Success Ratio
1.1.5.3 AMR Soft Handover Success Ratio
1.1.5.4 CS64 Soft Handover Success Ratio
1.1.5.5 PS Soft Handover Success Ratio
1.1.5.6 Intra-frequency Hard Handover Success Ratio
1.1.5.7 Inter-frequency Hard Handover Success Ratio
1.1.5.8 Service Cell Change Success Ratio with SHO (H2H)
1.1.5.9 H2H Intra-frequency Hard Handover Success Ratio
1.1.5.10 H2H Inter-frequency Hard Handover Success Ratio
1.1.5.11 H2D Inter-frequency Hard Handover Success Ratio
1.1.5.12 H2D Channel Switch Success Ratio
1.1.5.13 D2H Channel Switch Success Ratio
1.1.5.14 CS W2G Inter-RAT Handover Out Success Ratio
1.1.5.15 PS W2G Inter-RAT Handover Out Success Ratio
1.1.5.16 PS G2W Inter-RAT Handover In Success Ratio
1.1.5.17 HSDPA W2G Inter-RAT Handover Out Success Ratio
1.1.5.18 SRNC Relocation Success Ratio
1.1.5.19 TRNC Relocation Success Ratio

1 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

1.1.5.20 E-DCH Soft Handover Success Ratio


1.1.5.21 E-DCH Cell Change Success Ratio with SHO
1.1.5.22 E-DCH Cell Change Success Ratio with Inter-HHO
1.1.5.23 E2D Channel Switch Success Ratio
1.1.5.24 D2E Channel Switch Success Ratio
1.1.5.25 E2D Handover Success Ratio with Inter HHO
1.1.5.26 HSUPA W2G Inter-RAT Handover Out Success Ratio
1.1.5.27 MBMS Service Mode Switch Success Ratio
1.1.6 Retainability
1.1.6.1 CS Service Drop Ratio
1.1.6.2 AMR Call Drop Ratio
1.1.6.3 VP Call Drop Ratio
1.1.6.4 AMR Traffic Drop Ratio
1.1.6.5 VP Traffic Drop Ratio
1.1.6.6 PS Call Drop Ratio
1.1.6.7 PS Call Drop Ratio (PCH)
1.1.6.8 PS R99 Call Drop Ratio
1.1.6.9 PS R99 Call Drop Ratio (PCH)
1.1.6.10 PS BE Call Drop Ratio
1.1.6.11 HSDPA Call Drop Ratio
1.1.6.12 HSDPA Call Drop Ratio (PCH)
1.1.6.13 HSUPA Call Drop Ratio
1.1.6.14 HSUPA Call Drop Ratio (PCH)
1.1.6.15 MBMS Service PTP drop Ratio
1.1.7 Service Integrity
1.1.7.1 Average UL Throughput for PS R99 Service
1.1.7.2 Average DL Throughput for PS R99 Service
1.1.7.3 Average UL BLER for CS Service
1.1.7.4 Average UL BLER for PS Service
1.1.7.5 HSDPA Throughput
1.1.7.6 HSUPA Throughput
1.1.7.7 PS UL Throughput of RNC
1.1.7.8 PS DL Throughput of RNC
1.1.7.9 MBMS Service Throughput
1.1.8 Traffic
1.1.8.1 CS Equivalent Erlang of RNC
1.1.8.2 Number of CS Users
1.1.8.3 Number of PS R99 Users
1.1.8.4 Number of HSDPA Users
1.1.8.5 Number of HSUPA Users
1.1.8.6 Number of E-FACH Users
1.1.8.7 Number of CS Over HSPA Users
1.1.8.8 Number of HSDPA 64QAM Users
1.1.8.9 Number of HSDPA MIMO Users
1.1.8.10 Number of HSUPA 16QAM users
1.1.8.11 Number of HSDPA MIMO64QAM Users
1.1.8.12 Number of MBMS Users
1.1.8.13 HSDPA RLC Traffic Volume
1.1.8.14 HSUPA RLC Traffic Volume
1.1.8.15 R99 Service UL Traffic Volume
1.1.8.16 R99 Service DL Traffic Volume
1.1.8.17 E-FACH Traffic Volume

1 UMTS Service KPI


The following KPIs are UMTS Service KPIs.

SingleRAN KPI Reference

Parent topic: SingleRAN KPI Reference

1.1 SingleRAN KPI Reference


Purpose

This document describes the RAN KPI and the counters used to calculate the KPI. Originally, the KPI was described based on the commercial network management and radio network optimization.
However, the KPI description is updated from time to time based on the requirements of customers.

Product Versions

The following table lists the product versions included in this document.

Product Name Product Version

BSC6900 V900R012C01

NodeB V100R012

NodeB V200R012

BTS3900 BTS3900V100R002C00SPC011

BTS3000 BTS3000V100R009C00SPC011

BTS3012/BTS3012AE/BTS3012II/BTS3006C/BTS3002 BTS3000V100R008C11SP03 and later versions

DBS3900 BTS3000V100R008C11 and later versions

BTS3900/BTS3900A BTS3000V100R008C11 and later versions

BTS3900B/BTS3900E V100R008 and later versions

BTS30/BTS312/BTS3012A V302R007 and later versions

BTS30 and macro BTS312 (EDGE) G3BTS32V302R002C06SP05 and later versions

2 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Product Name Product Version

BTS30 and macro BTS312 (PCS1900) G3BTS32V302R002C06SP05 and later versions

Macro BTS3X (AMR) G3BTS32V302R002C06SP05 and later versions

Intended Audience

This document is intended for:

Network planning engineers

Field engineers
System engineers

Organization

1.1.1 Changes in the RAN KPI Reference


This chapter describes the changes in the RAN KPI Reference.

04 (2011-09-20)

This is the fourth commercial release of V900R012C01.


Compared with issue 03 (2010-11-30), this issue does not include any new topics.
Compared with issue 03 (2010-11-30), this issue incorporates the following changes:

Content Description
H2H Intra-frequency Hard Handover Success RatioH2H Inter-frequency Hard Handover
Success Ratio
The description part of the two KPIs is optimized.

Compared with issue 03 (2010-11-30), this issue does not exclude any topics.

03 (2010-11-30)

This is the third commercial release of V900R012C01.


Compared with issue 02 (2010-09-20), this issue does not include any new topics.
Compared with issue 02 (2010-09-20), this issue incorporates the following changes:

Content Description
RRC Setup Success Ratio
Correct the counter name from RRC.SuccConnEstab.OrgItrCall to
RRC.SuccConnEstab.OrgInterCall
AMR Call Drop Ratio
Correct the counter name from VS.RAB.NormRel.AMRWB.Iur to
VS.RAB.NormRel.AMR.Iur

Compared with issue 02 (2010-09-20), this issue does not exclude any topics.

02 (2010-09-20)

This is the second commercial release of V900R012C01.


Compared with issue 01 (2010-04-10), this issue include the following new topics:

RRC Congestion Ratio

CS RAB Congestion Ratio

PS RAB Congestion Ratio

Intra-frequency Hard Handover Success Ratio

AMR Soft Handover Success Ratio

CS64 Soft Handover Success Ratio

PS Soft Handover Success Ratio

CE Consumption for a NodeB Cell

Hardware Configured CE for a NodeB

Shared Group Configured License CE for a NodeB

Shared Group License CE Consumption for a NodeB

License Group Configured CE for a NodeB

License Group CE Consumption for a NodeB

Average UL BLER for PS Service

RTWP (Received Total Wideband Power)

TCP (Transmitted Carrier Power)

R99 Code Utilization

CS Service Drop Ratio (RNC)

PS BE Call Drop Ratio (RNC)

PS Call Drop Ratio (PCH)

PS R99 Call Drop Ratio (PCH)

HSDPA Call Drop Ratio (PCH)

HSUPA Call Drop Ratio (PCH)

HSDPA Throughput

HSUPA Throughput

Number of PS R99 Users

Compared with issue 01 (2010-04-10), this issue incorporates the following changes:

Content Description

3 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Content Description
HSDPA Unavailability duration
Correct the counter name from VS.Hsdpa.UnavailTime to VS.Cell.HSDPA.UnavailTime
Number of HSDPA Users
Modify the KPI name from Mean Number of HSDPA Users to Number of HSDPA Users
New counter VS.HSDPA.UE.Max.Cell was added in the section Associated Counters.
Number of HSUPA Users
Modify the KPI name from Mean Number of HSUPA Users to Number of HSUPA Users
New counter VS.HSUPA.UE.Max.Cell was added in the section Associated Counters.

Compared with issue 01 (2010-04-10), this issue does not exclude any topics.

01 (2010-04-10)

This is the first release of V900R012C01.


Compared with RAN11.0 and RAN10.0, a lot of changes for KPI definition are presented in the current version within the following categories:

KPI Addition
KPI Modification

KPI Deletion

For more details, please refer to:


KPI Difference Between RAN12.0 and RAN11.0

KPI Difference Between RAN12.0 and RAN10.0

1.1.2 Accessibility
Accessibility is the ability of a user to obtain the requested service from the system. RRC connection and RAB setup are the main procedures of accessibility.

1.1.2.1 IU Paging Success Ratio

Table 1 IU Paging Success Ratio


Name IU Paging Success Ratio

Formula

Description This KPI is used to check the successful paging responses to the pagings from the Core Network (CN) in one RNC.
The Attempt Paging Procedure starts when the CN sends a PAGING message to the RNC, and is complete when the UE in idle mode receives
the PAGING TYPE 1 message from the RNC.
The Successful Paging Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE in idle mode.

Associated IU Paging Success Ratio =


Counters (VS.RANAP.Paging.Succ.IdleUE/ VS.RANAP.Paging.Att.IdleUE)*100%

Object RNC

Unit/Range %

Note None

1.1.2.2 RRC Setup Success Ratio

Table 1 RRC Setup Success Ratio


Name RRC Setup Success Ratio

Formula

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:
Conversational Call, Streaming Call, Background Call, Interactive Call, Originating Subscribed Traffic Call, Emergency Call,
High Priority Signaling, Low Priority Signaling, Cause Unknown, Call Re-Establishment. 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.
Description of RRC Setup Success Ratio for other causes:
RRC Connection Attempt for Other reasons 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: Inter-RAT cell re-selection, Inter-RAT cell change order, Registration and Detach.
The RRC Setup Success for Other reasons Procedure is complete when the RNC receives an RRC CONNECTION SETUP
COMPLETE message from the UE.

Associated Counters RRC Setup Success Ratio (Cell.Service) =


[(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.OrgStrCall+
RRC.SuccConnEstab.OrgInterCall+
RRC.SuccConnEstab.OrgBkgCall+
RRC.SuccConnEstab.OrgSubCall+
RRC.SuccConnEstab.TmConvCall+
RRC.SuccConnEstab.TmStrCall+
RRC.SuccConnEstab.TmItrCall+
RRC.SuccConnEstab.TmBkgCall+
RRC.SuccConnEstab.EmgCall+

4 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

RRC.SuccConnEstab.Unkown+
RRC.SuccConnEstab.OrgHhPrSig+
RRC.SuccConnEstab.OrgLwPrSig+
RRC.SuccConnEstab.CallReEst+
RRC.SuccConnEstab.TmHhPrSig+
RRC.SuccConnEstab.TmLwPrSig)/
(RRC.AttConnEstab.OrgConvCall+
RRC.AttConnEstab.OrgStrCall+
RRC.AttConnEstab.OrgInterCall+
RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.OrgSubCall+
RRC.AttConnEstab.TmConvCall+
RRC.AttConnEstab.TmStrCall+
RRC.AttConnEstab.TmInterCall+
RRC.AttConnEstab.TmBkgCall+
RRC.AttConnEstab.EmgCall+
RRC.AttConnEstab.Unknown+
RRC.AttConnEstab.OrgHhPrSig+
RRC.AttConnEstab.OrgLwPrSig+
RRC.AttConnEstab.CallReEst+
RRC.AttConnEstab.TmHhPrSig+
RRC.AttConnEstab.TmLwPrSig )]*100%
RRC Setup Success Ratio (Cell.Other)=
[(RRC.SuccConnEstab.IRATCelRes+
RRC.SuccConnEstab.IRATCCO+
RRC.SuccConnEstab.Reg+
RRC.SuccConnEstab.Detach)/
(RRC.AttConnEstab.IRATCelRes+
RRC.AttConnEstab.IRATCCO+
RRC.AttConnEstab.Reg+
RRC.AttConnEstab.Detach)]*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.3 Radio Access Success Ratio

Table 1 Radio Access Success Ratio


Name Radio Access Success Ratio

Formula

Description This KPI is used to check the Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not
provided in this call setup procedure.
Description of the RAB Setup Attempt Procedure and the RAB Setup Success Procedure:
The RAB Setup Attempt Procedure starts when the CN sends an RAB ASSIGNMENT REQUEST message to the RNC. The message
contains information about one of the following service types: CS Conversational RAB Establishments, CS Streaming RAB
Establishments, PS Conversational RAB Establishment, PS Background RAB Establishments, PS Interactive RAB Establishments, PS
Streaming RAB Establishments. The RAB Setup Attempt Procedure is complete when the UE receives a RADIO BEARER SETUP
message from the RNC.
The RAB Setup Success Procedure is complete when the CN receives an RAB ASSIGNMENT RESPONSE message from the RNC.

Associated Counters Radio Access Success Ratio (Cell) =


RRC Setup Success Ratio (Cell.Service)*
{[(VS.RAB.SuccEstabCS.Conv+
VS.RAB.SuccEstabCS.Str)+
(VS.RAB.SuccEstabPS.Conv+
VS.RAB.SuccEstabPS.Str+
VS.RAB.SuccEstabPS.Int+
VS.RAB.SuccEstabPS.Bkg)]/
[(VS.RAB.AttEstabCS.Conv+
VS.RAB.AttEstabCS.Str)+
(VS.RAB.AttEstabPS.Conv+
VS.RAB.AttEstabPS.Str+
VS.RAB.AttEstabPS.Int+
VS.RAB.AttEstabPS.Bkg)]}*100%
Radio Access Success Ratio (RNC) =
RRC Setup Success Ratio (Cell.Service)*
{[(VS.RAB.SuccEstabCS.Conv.RNC+
VS.RAB.SuccEstabCS.Str.RNC)+
(VS.RAB.SuccEstabPS.Conv.RNC+
VS.RAB.SuccEstabPS.Str.RNC+
VS.RAB.SuccEstabPS.Int.RNC+
VS.RAB.SuccEstabPS.Bkg.RNC)]/
[(VS.RAB.AttEstabCS.Conv.RNC+
VS.RAB.AttEstabCS.Str.RNC)+

5 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

(VS.RAB.AttEstabPS.Conv.RNC+
VS.RAB.AttEstabPS.Str.RNC+
VS.RAB.AttEstabPS.Int.RNC+
VS.RAB.AttEstabPS.Bkg.RNC)]}*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.2.4 PS Radio Access Success Ratio

Table 1 PS Radio Access Success Ratio


Name PS Radio Access Success Ratio

Formula

Description This KPI is used to check the PS Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are
not provided in this call setup procedure.
The PS RRC Setup Attempt 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: Originating Interactive Call, Terminating Interactive Call,
Originating Background Call, Terminating Background Call.
The PS RRC Setup Success Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message
from the UE.

Associated Counters PS Radio Access Success Ratio (Cell) =


[(RRC.SuccConnEstab.OrgBkgCall+
RRC.SuccConnEstab.OrgInterCall+
RRC.SuccConnEstab.TmBkgCall+
RRC.SuccConnEstab.TmItrCall)/
(RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.OrgInterCall+
RRC.AttConnEstab.TmBkgCall+
RRC.AttConnEstab.TmInterCall)]*
PS RAB Setup Success Ratio (Cell) *100%

PS Radio Access Success Ratio (RNC) =


[(RRC.SuccConnEstab.OrgBkgCall+
RRC.SuccConnEstab.OrgInterCall+
RRC.SuccConnEstab.TmBkgCall+
RRC.SuccConnEstab.TmItrCall)/
(RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.OrgInterCall+
RRC.AttConnEstab.TmBkgCall+
RRC.AttConnEstab.TmInterCall)]*
PS RAB Setup Success Ratio (RNC)*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.2.5 CS Radio Access Success Ratio

Table 1 CS Radio Access Success Ratio


Name CS Radio Access Success Ratio

Formula

Description This KPI is used to check the Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not
provided in this call setup procedure.
The CS RRC Setup Attempt 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: Originating Conversational Call, Terminating
Conversational Call, Emergency Call.
The CS RRC Setup Success Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message
from the UE.

Associated Counters CS Radio Access Success Ratio (Cell) =


[(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.TmConvCall+
RRC.SuccConnEstab.EmgCall)/
(RRC.AttConnEstab.OrgConvCall+
RRC.AttConnEstab.TmConvCall+
RRC.AttConnEstab.EmgCall)]*
CS RAB Setup Success Ratio (Cell)*100%

CS Radio Access Success Ratio (RNC) =


[(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.TmConvCall+
RRC.SuccConnEstab.EmgCall)/
(RRC.AttConnEstab.OrgConvCall+

6 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

RRC.AttConnEstab.TmConvCall+
RRC.AttConnEstab.EmgCall)]*
CS RAB Setup Success Ratio (RNC)*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.2.6 AMR RAB Setup Success Ratio

Table 1 AMR RAB Setup Success Ratio


Name AMR RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the AMR Service.
AMR RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for
the CS narrow band AMR services.
The AMR RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE message to the RNC.
This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.

Associated Counters AMR RAB Setup Success Ratio (Cell) =


(VS.RAB.SuccEstabCS.AMR/ VS.RAB.AttEstab.AMR)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.7 VP RAB Setup Success Ratio

Table 1 VP RAB Setup Success Ratio


Name VP RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB setup success ratio of CS 64 Kbit/s conversational services in an RNC or a cluster.
VP (Video Phone) RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message
from the CN (The RAB type is for the CS 64 Kbit/s conversational service).
VP RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE message to RNC. This
procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.

Associated Counters VP RAB Setup Success Ratio (Cell) =


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

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.8 CS RAB Setup Success Ratio

Table 1 CS RAB Setup Success Ratio


Name CS RAB Setup Success Ratio

Formula

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.

Associated Counters CS RAB Setup Success Ratio (Cell) =


[(VS.RAB.SuccEstabCS.Conv+ VS.RAB.SuccEstabCS.Str)/
(VS.RAB.AttEstabCS.Conv+VS.RAB.AttEstabCS.Str)]*100%
CS RAB Setup Success Ratio (RNC) =
[(VS.RAB.SuccEstabCS.Conv.RNC+ VS.RAB.SuccEstabCS.Str.RNC)/
(VS.RAB.AttEstabCS.Conv.RNC+ VS.RAB.AttEstabCS.Str.RNC)]*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.2.9 PS RAB Setup Success Ratio

7 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Table 1 PS RAB Setup Success Ratio


Name PS RAB Setup Success Ratio

Formula

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.

Associated Counters 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)]*100%
PS RAB Setup Success Ratio (RNC) =
[(VS.RAB.SuccEstabPS.Bkg.RNC+
VS.RAB.SuccEstabPS.Str.RNC+
VS.RAB.SuccEstabPS.Conv.RNC+
VS.RAB.SuccEstabPS.Int.RNC)/
(VS.RAB.AttEstabPS.Conv.RNC+
VS.RAB.AttEstabPS.Bkg.RNC+
VS.RAB.AttEstabPS.Int.RNC+
VS.RAB.AttEstabPS.Str.RNC)]*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.2.10 HSDPA RAB Setup Success Ratio

Table 1 HSDPA RAB Setup Success Ratio


Name HSDPA RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the PS service 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.

Associated Counters HSDPA RAB Setup Success Ratio (Cell) =


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

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.11 HSUPA RAB Setup Success Ratio

Table 1 HSUPA RAB Setup Success Ratio


Name HSUPA RAB Setup Success Ratio

Formula

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 (Cell) =


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

Object CELL

Unit/Range %

8 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.12 PS E-FACH RAB Setup Success Ratio

Table 1 PS E-FACH RAB Setup Success Ratio


Name PS E-FACH RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB setup success ratio of the E-FACH service in an RNC or a cluster.
Successful PS RAB Setup on E-FACH 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.
Attempts of PS RAB Setup on E-FACH Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message
from the SGSN, and the PS service is established on the EFACH.

Associated Counters PS E-FACH RAB Setup Success Ratio (Cell) =


(VS.RAB.SuccEstPS.EFACH/ VS.RAB.AttEstPS.EFACH)*100%

CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.13 CS over HSPA RAB Setup Success Ratio

Table 1 CS over HSPA RAB Setup Success Ratio


Name CS over HSPA RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB setup success ratio of the CS over HSPA service.
When the RAB is set for the CS conversational service and is carried on an HSPA channel, the CS over HSPA RAB Setup Success
Procedure starts when the RNC receives an RADIO BEARER SETUP COMPLETE message from UE. This procedure is complete
when the RNC sends an RAB ASSIGNMENT RESPONSE message to CN.
The CS over HSPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message
from the CN, and the RAB is set up on an HSPA channel.

Associated Counters CS over HSPA RAB Setup Success Ratio (Cell) =


(VS.HSPA.RAB.SuccEstab.CS.Conv/ VS.HSPA.RAB.AttEstab.CS.Conv)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.14 HSDPA 64QAM RAB Setup Success Ratio

Table 1 HSDPA 64QAM RAB Setup Success Ratio


Name HSDPA 64QAM RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA 64QAM service in an RNC or a cluster.
The HSDPA 64 QAM RAB Setup Success Procedure starts when the RNC receives an 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 HSDPA 64QAM RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message
from the CN for setting up the HSDPA service using 64QAM.

Associated Counters HSDPA 64QAM RAB Setup Success Ratio (Cell) =


(VS.HSDPA.RAB.64QAM.SuccEstab/ VS.HSDPA.RAB.64QAM.AttEstab)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.15 HSDPA MIMO RAB Setup Success Ratio

Table 1 HSDPA MIMO RAB Setup Success Ratio


Name HSDPA MIMO RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO service in an RNC or a cluster.
The HSDPA MIMO RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message

9 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.
The HSDPA MIMO RAB Setup Attempt procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message
from the CN for setting up the HSDPA service using MIMO.

Associated Counters HSDPA MIMO RAB Setup Success Ratio=


(VS.HSDPA.RAB.MIMO.SuccEstab/ VS.HSDPA.RAB.MIMO.AttEstab)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.16 HSDPA DC RAB Setup Success Ratio

Table 1 HSDPA DC RAB Setup Success Ratio


Name HSDPA DC RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA DC RAB service in an RNC or a cluster.
The HSDPA DC 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 HSDPA DC RAB Setup Attempt procedure is complete when the RNC receives from the CN an RAB ASSIGNMENT REQUEST
message for setting up the HSDPA service using DC-HSDPA.

Associated Counters HSDPA DC RAB Setup Success Ratio=


(VS.HSDPA.RAB.DC.SuccEstab/ VS.HSDPA.RAB.DC.AttEstab)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.17 HSDPA MIMO64QAM RAB Setup Success Ratio

Table 1 HSDPA MIMO64QAM RAB Setup Success Ratio


Name HSDPA MIMO64QAM RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO 64QAM service in an RNC or a cluster.
The HSDPA MIMO 64QAM 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 HSDPA MIMO 64QAM RAB Setup Attempt procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST
message from the CN for setting up the HSDPA service using MIMO+64QAM.

Associated Counters HSDPA MIMO64QAM RAB Setup Success Ratio=


(VS.HSDPA.RAB.MIMO64QAM.SuccEstab/ VS.HSDPA.RAB.MIMO64QAM.AttEstab)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.18 PTM Channel Setup Success Ratio

Table 1 PTM Channel Setup Success Ratio


Name PTM Channel Setup Success Ratio

Formula

Description This KPI is used to check the Channel Setup Success Rate of MBMS service in PTM mode.
When the RB of PTM MBMS service is successfully set up, the PTM Channel RB is successfully set up.
When the RNC initiates the setup of PTM MBMS service, the PTM Channel RB Setup Attempt.

Associated Counters PTM Channel Setup Success Ratio=


(VS.MBMS.RB.PTM.SuccEstab/ VS.MBMS.RB.PTM.AttEstab)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.19 PTP Channel Setup Success Ratio

Table 1 PTP Channel Setup Success Ratio


Name PTP Channel Setup Success Ratio

10 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Formula

Description This KPI is used to check the Channel Setup Success Rate of MBMS service in PTP mode.
The PTP Channel RB Setup Success Procedure is as follows:
When the UE initiates a request to set up an MBMS, the RNC, in response to the UE's request, initiates PTP RB setup, and the PTP
RB is successfully set up.
The PTP Channel RB Setup Attempt Procedure:
The RNC initiates PTP RB setup after the UE initiates an MBMS setup request.

Associated Counters PTP Channel Setup Success Ratio=


(VS.MBMS.RB.PTP.SuccEstab/ VS.MBMS.RB.PTP.AttEstab)*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.2.20 RRC Congestion Ratio

Table 1 RRC Congestion Ratio


Name RRC Congestion Ratio

Formula

Description This KPI is used to check the RRC Congestion Ratio in a cluster.
After receiving an RRC CONNECTION REQUEST message from the UE, the RNC initiates admission procedures for resources of
code, power, CE, and Iub bandwidth. If the resource admission fails, the RRC Setup Failure due to Congestion procedure is complete
when the RNC sends an RRC CONNECTION REJECT message to the UE.
The RRC Connection Attempt for service Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message
from the UE.

Associated Counters RRC Congestion Ratio=


[(VS.RRC.Rej.ULPower.Cong+
VS.RRC.Rej.DLPower.Cong+
VS.RRC.Rej.ULIUBBand.Cong+
VS.RRC.Rej.DLIUBBand.Cong+
VS.RRC.Rej.ULCE.Cong+
VS.RRC.Rej.DLCE.Cong+
VS.RRC.Rej.Code.Cong)/
VS.RRC.AttConnEstab.Sum]*100%

Object CELL

Unit/Range %

Note None

1.1.2.21 CS RAB Congestion Ratio

Table 1 CS RAB Congestion Ratio


Name CS RAB Congestion Ratio

Formula

Description This KPI is used to check the CS RAB Congestion Ratio in a cluster.
The CS RAB Setup Fails due to Congestion procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message
to the CN. The message contains one of the following RAB assignment responses: "No Radio Resources Available in Target cell",
"Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate
not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available".
The CS RAB Setup Attempt Procedure starts when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN in the
CS domain. The message contains one of the following RAB assignment requests: Conversational Services, streaming Services.

Associated Counters CS RAB Congestion Ratio=


[(VS.RAB.FailEstabCS.DLIUBBand.Cong+
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)/
(VS.RAB.AttEstabCS.Conv+
VS.RAB.AttEstabCS.Str)]* 100%

Object CELL

Unit/Range %

Note None

1.1.2.22 PS RAB Congestion Ratio

11 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Table 1 PS RAB Congestion Ratio


Name PS RAB Congestion Ratio

Formula

Description This KPI is used to check the PS RAB Congestion Ratio in a cluster.
The PS RAB Setup Fails due to Congestion procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message
to the CN. The message contains information about one of the following RAB assignment responses: "No Radio Resources Available in
Target cell", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available", "Requested
Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not
Available".
The PS RAB Setup Attempt Procedure starts 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 RAB assignment requests: Conversational services,
Streaming services, Interactive Services, Background Services.

Associated Counters PS RAB Congestion Ratio=


[(VS.RAB.FailEstabPS.DLIUBBand.Cong+
VS.RAB.FailEstabPS.ULIUBBand.Cong+
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.AttEstabPS.Conv+
VS.RAB.AttEstabPS.Str+
VS.RAB.AttEstabPS.Int+
VS.RAB.AttEstabPS.Bkg)]*100%

Object CELL

Unit/Range %

Note None

1.1.3 Availability
Accessibility is the ability of a user to obtain the requested service from the system. RRC connection and RAB setup are the main procedures of accessibility.

1.1.3.1 Worst Cell Ratio

Table 1 Worst Cell Ratio


Name Worst Cell Ratio

Formula

Description This KPI is used to check the Availability of the cells with poor call drop ratio or call setup success ratio in an RNC or a cluster.
Description of the numerator:
The number of Cells in which AMR RAB Setup Success Ratio <95% and VP RAB Setup Ratio<= 95%, or AMR Call Drop Ratio>3% and
VP Call Drop Ratio >3%.

Associated Counters Worst Cell Ratio =


{[The Number Of Cells, in which (AMR RAB Setup Success Ratio (Cell)< 95% and VP RAB Setup Success Ratio (Cell)=< 95%) or
(AMR Call Drop Ratio> 3% and VP Call Drop Ratio> 3%)]/ The Total Number Of Cells In RNC}*100%

Object CELL

Unit/Range %

Note 95% and 3% are the values obtained based on the references from the commercial network with the condition of that the traffic of AMR
voice and video call is greater than 0.1 Erlang.

1.1.3.2 Paging Congestion Ratio

Table 1 Paging Congestion Ratio


Name Paging Congestion Ratio

Formula

Description Paging Congestion Ratio (RNC):


This KPI is used to check the consumption of PCCH bandwidth during busy hours.
Description of the numerator:
The Failures to Respond to PAGING Message From CN counted if the RNC does not send a PAGING type 1 or PAGING type
2 message. The reason is that the RNC does not send a PAGING message due to congestion causes such as Iu flow control
or high CPU usage.

12 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Description of the denominator:


The Number of PAGING Message from CN is counted when RNC receives a PAGING message from the CN included CS and
PS PAGING.
Paging Congestion Ratio (Cell):
This KPI is used to check the consumption of PCCH bandwidth during the busy hour.
Description of the numerator:
This counter provides the number of losses of PAGING TYPE 1 message due to PCH congestion in a cell.
Description of the denominator:
This counter provides the number of paging messages of PAGING TYPE 1 sent by the RNC in a cell.

Associated Counters IU Paging Congestion Ratio (RNC) =


[(VS.RANAP.CsPaging.Loss+ VS.RANAP.PsPaging.Loss)/ (VS.RANAP.CsPaging.Att+ VS.RANAP.PsPaging.Att)]*100%
IU Paging Congestion Ratio (Cell) =
(VS.RRC.Paging1.Loss.PCHCong.Cell/ VS.UTRAN.AttPaging1)*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.3.3 Call Admission Refused Ratio

Table 1 Call Admission Refused Ratio


Name Call Admission Refused Ratio

Formula

Description This KPI is used to check the admission refused ratio of new calls during busy hours in an RNC or a cluster.
Description of the numerator:
The failed number of Cell Resource Requests for New Call setup is counted after RNC requesting cell resources for the UE
successfully.
Description of the denominator:
The number of Cell Resource Requests during RAB establishment for Cell. After RNC receiving the RAB ASSIGNMENT
REQUEST message from CN, the RNC requests cell resources for the UE and the counter is pegged in the cell where the
UE camps on.

Associated Counters Call admission Refused Ratio=


[1-VS.RAC.NewCallAcc/VS.RAC.NewCallReq]*100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.

1.1.3.4 Congested Cell Ratio

Table 1 Congested Cell Ratio


Name Congested Cell Ratio

Formula

Description This KPI is used to check the utility ratio of radio network resources during busy hours in an RNC or a cluster. It is the rate of congested
cell during the busy hour to total number of cells in RNC.
Description of the numerator:
The number of congested cell counted after RNC receiving the COMMON MESUREMENT REPORT message from NodeB. The RNC
measures when overload congestion occurs at UL or DL.

Associated Counters Congested Cell Ratio =


(The Number Of Cells, in which VS.LCC.OLC.UL.Num>0 or VS.LCC.OLC.DL.Num>0 On Busy Hour/ The Total Number Of Cells In
RNC)*100%

Object CELL

Unit/Range %

Note The number of congested cells is calculated by aggregating the cells which is congested in DL or UL directions during busy hours.

1.1.3.5 Radio Network Unavailability Ratio

Table 1 Radio Network Unavailability Ratio


Name Radio Network Unavailability Ratio

Formula

Description This KPI describes the ratio of cell unavailable duration to the number of cells in RNC during busy hours. It is used to check the impact
of the degrading of the network performance caused by the unavailable cells during busy hours in an RNC.
Description of the numerator:
The cell unavailable time is started to count when the cell is out of service, or the channel is barred through the LMT in a measurement

13 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

period, or problem of CCH such as failed synchronization, or equipment faults.

Associated Counters Radio Network Unavailability Ratio =


(VS.Cell.UnavailTime.Sys)/(The Total Number Of Cells in RNC*{SP}*60)*100%

Object CELL

Unit/Range %

Note The unit of {SP} (Statistic Period): Minute

1.1.3.6 Average CPU Load

Table 1 Average CPU Load


Name Average CPU Load

Formula Average CPU Load = XPU usage of the XPU in the measurement period

Description This KPI provides the CPU usage of the XPU in a measurement period. It also indicates the load and operating performance of CPU on
the XPU in the measurement period.
The CPU usage of the XPU is accumulated every second in the measurement period.

Associated Counters Average CPU Load= VS.XPU.CPULOAD.MEAN

Object XPU

Unit/Range %

Note Mean CPU Utility is the CPU average load showed in percentage.

1.1.3.7 IUB Bandwidth Utilizing Ratio (UL)

Table 1 IUB Bandwidth Utilizing Ratio (UL)


Name IUB Bandwidth Utilizing Ratio (UL)

Formula

Description This KPI is used to check the ratio of consumption of Iub bandwidth and configured Iub bandwidth in a NodeB for downlink during busy
hours. The consumption of interactive and background services cannot maintain the full rate all the time on the configured Iub
bandwidth.
The UL Bandwidth could be measured on ATM Physical Ports or IP physical Ports. The numerator is defined as the average used
bandwidth on an ATM or IP physical ports during a measurement period counted by NodeB. The NodeB measures the used UL
bandwidth on the physical port every five seconds for 15 minutes and then calculates the average value. The counter and the physical
port have one-to-one relation, and they are all used for traffic measurement at the physical layer.

Associated Counters IUB Bandwidth Utilizing Ratio (ATM_UL) =


[(VS.ATMUlAvgUsed.1+
VS.ATMUlAvgUsed.2+
VS.ATMUlAvgUsed.3+
VS.ATMUlAvgUsed.4)/
(VS.ATMUlTotal.1+
VS.ATMUlTotal.2+
VS.ATMUlTotal.3+
VS.ATMUlTotal.4)]*100%
IUB Bandwidth Utilizing Ratio (IP_UL) =
[(VS.IPUlAvgUsed.1+
VS.IPUlAvgUsed.2+
VS.IPUlAvgUsed.3+
VS.IPUlAvgUsed.4)/
(VS.IPUlTotal.1+
VS.IPUlTotal.2+
VS.IPUlTotal.3+
VS.IPUlTotal.4)]*100%

Object NodeB

Unit/Range %

Note The counters in the formula are measured on the NodeB side.

1.1.3.8 IUB Bandwidth Utilizing Ratio (DL)

Table 1 IUB Bandwidth Utilizing Ratio (DL)


Name IUB Bandwidth Utilizing Ratio (DL)

Formula

Description This KPI is used to check the ratio of consumption of Iub bandwidth and configured Iub bandwidth in a NodeB for downlink during busy
hours. The consumption of interactive and background services cannot maintain the full rate all the time on the configured Iub
bandwidth.
The DL Bandwidth could be measured on ATM Physical Ports or IP physical Ports. The numerator is defined as the average used
bandwidth on an ATM or IP physical ports during a measurement period counted by NodeB. The NodeB measures the used DL
bandwidth on the physical port every five seconds for 15 minutes and then calculates the average value. The counter and the physical

14 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

port have one-to-one relation, and they are all used for traffic measurement at the physical layer.

Associated Counters IUB Bandwidth Utilizing Ratio (ATM_DL) =


[(VS.ATMDIAvgUsed.1+
VS.ATMDLAvgUsed.2+
VS.ATMDLAvgUsed.3+
VS.ATMDLAvgUsed.4)/
(VS.ATMDLTotal.1+
VS.ATMDLTotal.2+
VS.ATMDLTotal.3+
VS.ATMDLTotal.4)]*100%
IUB Bandwidth Utilizing Ratio (IP_DL) =
[(VS.IPDLAvgUsed.1+
VS.IPDLAvgUsed.2+
VS.IPDLAvgUsed.3+
VS.IPDLAvgUsed.4)/
(VS.IPDLTotal.1+
VS.IPDLTotal.2+
VS.IPDLTotal.3+
VS.IPDLTotal.4)]*100%

Object NodeB

Unit/Range %

Note The counters in the formula are measured on the NodeB side.

1.1.3.9 Cell Unavailability duration

Table 1 Cell Unavailability duration


Name Cell Unavailability duration

Description This KPI is used to check the total duration of the unavailability of a cell caused by system fault in a measurement period.

Associated Counters VS.Cell.UnavailTime.Sys

Object CELL

Unit/Range s

Note None

1.1.3.10 HSDPA Unavailability duration

Table 1 HSDPA Unavailability duration


Name HSDPA Unavailability duration

Description This KPI is used to check the total duration of unavailability of the HSDPA service in a cell, caused by system fault in a measurement
period.

Associated Counters VS.Cell.HSDPA.UnavailTime

Object CELL

Unit/Range s

Note None

1.1.3.11 HSUPA Unavailability duration

Table 1 HSUPA Unavailability duration


Name HSUPA Unavailability duration

Description This KPI is used to check the total duration of unavailability of the HSUPA service in a cell, caused by system fault in a measurement
period.

Associated Counters VS.Cell.HSUPA.UnavailTime

Object CELL

Unit/Range s

Note None

1.1.3.12 CE Consumption for a NodeB Cell

Table 1 CE Consumption for a NodeB Cell


Name CE Consumption for a NodeB Cell

Description The resources for license groups are measured based on the usage of CEs in each license group. This measurement indicates the
consumption of baseband resources in the NodeB.
The corresponding counters listed below give the Average/ Maximum number of UL/DL and HSUPA CEs consumption for an operator.

Associated Counters VS.ULCE.Mean.Shared


VS.ULCE.Max.Shared
VS.DLCE.Mean.Shared

15 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.DLCE.Max.Shared
VS.ULCE.Mean.Dedicated
VS.ULCE.Max.Dedicated
VS.DLCE.Mean.Dedicated
VS.DLCE.Max.Dedicated

Object NodeB CELL

Unit/Range Numbers

Note If only one Operator is available on the NodeB, the Dedicated Counter value is always Zero and the Shared CE counters should be
used to check actual consumption of the Cell in NodeB.

1.1.3.13 Hardware Configured CE for a NodeB

Table 1 Hardware Configured CE for a NodeB


Name Hardware Configured CE for a NodeB

Description Number of UL/DL CEs configured for a NodeB.

Associated Counters VS.HW.ULCreditAvailable


VS.HW.DLCreditAvailable

Object NodeB

Unit/Range Numbers

Note None

1.1.3.14 Shared Group Configured License CE for a NodeB

Table 1 Shared Group Configured License CE for a NodeB


Name Shared Group Configured License CE for a NodeB

Description The Configured DL/UL CEs for the Shared Group.

Associated Counters VS.LC.ULCreditAvailable.Shared


VS.LC.DLCreditAvailable.Shared

Object NodeB

Unit/Range Numbers

Note If only one operator is available on the NodeB, the configured counters given above should be used to evaluate the total configured
License CE in the NodeB.

1.1.3.15 Shared Group License CE Consumption for a NodeB

Table 1 Shared Group License CE Consumption for a NodeB


Name Shared Group License CE Consumption for a NodeB

Description The Average/ Maximum/Minimum number of shared DL/UL CEs consumed by an operator, or by HSUPA service.

Associated Counters VS.LC.ULMean.LicenseGroup.Shared


VS.LC.ULMax.LicenseGroup.Shared
VS.LC.ULMin.LicenseGroup.Shared
VS.HSUPA.LC.ULMean.LicenseGroup.Shared
VS.HSUPA.LC.ULMax.LicenseGroup.Shared
VS.HSUPA.LC.ULMin.LicenseGroup.Shared
VS.LC.DLMean.LicenseGroup.Shared
VS.LC.DLMax.LicenseGroup.Shared
VS.LC.DLMin.LicenseGroup.Shared

Object NodeB

Unit/Range Numbers

Note If only one operator is available on the NodeB, the shared counters given above should be used to evaluate the total License CE
Consumption in the NodeB.

1.1.3.16 License Group Configured CE for a NodeB

Table 1 License Group Configured CE for a NodeB


Name License Group Configured CE for a NodeB

Description The Number of DL CEs configured for a license Group.

Associated Counters VS.LC.DLCreditAvailable.LicenseGroup.Dedicated


VS.LC.ULCreditAvailable.LicenseGroup.Dedicated

Object NodeB

Unit/Range Numbers

Note If only one operator is available on the NodeB, the configured counter value given above is Zero.

1.1.3.17 License Group CE Consumption for a NodeB

16 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Table 1 License Group CE Consumption for a NodeB


Name License Group CE Consumption for a NodeB

Description The Average/ Maximum/Minimum number of shared DL/UL CEs consumed by a licensed group, or by HSUPA services.

Associated Counters UL Statistics


VS.LC.ULMean.LicenseGroup
VS.LC.ULMax.LicenseGroup
VS.LC.ULMin.LicenseGroup
VS.HSUPA.LC.ULMin.LicenseGroup
VS.HSUPA.LC.ULMean.LicenseGroup
VS.HSUPA.LC.ULMax.LicenseGroup
DL Statistics
VS.LC.DLMean.LicenseGroup
VS.LC.DLMax.LicenseGroup
VS.LC.DLMin.LicenseGroup

Object NodeB

Unit/Range Numbers

Note If only one operator is available on the NodeB, the counter value given above is Zero.

1.1.3.18 RTWP (Received Total Wideband Power)

Table 1 RTWP (Received Total Wideband Power)


Name RTWP (Received Total Wideband Power)

Description The first 3 counters given below provide the RTWP measurement values of a cell in the RNC, Mean/Maximum/Minimum Power of
Totally Received Bandwidth for Cell. The last 3 counters provide average, maximum and minimum received scheduled E-DCH power
shared in the measurement period for cell.

Associated Counters VS.MaxRTWP


VS.MinRTWP
VS.MeanRTWP
VS.HSUPA.MeanRSEPS
VS.HSUPA.MaxRSEPS
VS.HSUPA.MinRSEPS

Object CELL

Unit/Range dBm; %

Note None

1.1.3.19 TCP (Transmitted Carrier Power)

Table 1 TCP (Transmitted Carrier Power)


Name TCP (Transmitted Carrier Power)

Description The first 3 counters provide the Maximum/Minimum/Mean Transmitted Power of Carrier for a cell.
The second 3 counters provide the Maximum/Minimum/Mean Transmitted Power of Carrier for Non-HSDPA Cell.
The third 3 counters provide Maximum/Minimum/Mean Required Power by HS-DSCH for Cell.
The last 3 counters provide Maximum/Minimum/Mean Received Scheduled E-DCH Power shared for Cell.

Associated Counters VS.MaxTCP


VS.MinTCP
VS.MeanTCP
VS.MaxTCP.NonHS
VS.MinTCP.NonHS
VS.MeanTCP.NonHS
VS.HSDPA.MaxRequiredPwr
VS.HSDPA.MinRequiredPwr
VS.HSDPA.MeanRequiredPwr

Object CELL

Unit/Range dBm

Note None

1.1.3.20 R99 Code Utilization

Table 1 R99 Code Utilization


Name R99 Code Utilization

Formula

Description The occupied codes are the codes occupied by the common channel and R99 user. The code number is normalized to SF = 256, that
is, converted to the code number when SF=256.
The counters given below provide the number of single-RAB and Multi-RAB UEs that occupy the DL R99 codes with Spreading Factor
(SF) of 4/8/16/32/64/128/256.

17 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Associated Counters R99 Code Utilization =


[(VS.SingleRAB.SF4+VS.MultRAB.SF4)*64+
(VS.SingleRAB.SF8+VS.MultRAB.SF8)*32+
(VS.SingleRAB.SF16+VS.MultRAB.SF16)*16+
(VS.SingleRAB.SF32+VS.MultRAB.SF32)*8+
(VS.SingleRAB.SF64+VS.MultRAB.SF64)*4+
(VS.SingleRAB.SF128+VS.MultRAB.SF128)*2+
(VS.SingleRAB.SF256+VS.MultRAB.SF256)]/256*100%

Object CELL

Unit/Range %

Note The occupied codes are normalized to SF=256.


Total Code utilization for a cell can be calculated approximately by using the following formula:
VS.RAB.SFOccupy/256
The value would be greater than the real usage as the code for HSDPA was reserved initially.

1.1.4 Coverage
Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an RNC or a cluster.

1.1.4.1 UL Interference Cell Ratio

Table 1 UL Interference Cell Ratio


Name UL Interference Cell Ratio

Formula

Description This KPI is used to check how the UL capacity is limited by the UL interference of all cells in an RNC.
The mean RTWP's measurement is started when the RNC receives a COMMON MEASUREMENT REPORT message from the NodeB
about the RTWP of a cell and obtains the RTWP of the cell.

Associated Counters UL Interference Cell Ratio =


[(The Number Of Cells In which VS.MeanRTWP >-98dBm)/The Total Number Of Cells In RNC]*100%

Object RNC

Unit/Range %

Note -98 dBm is the value obtained based on the references from the commercial network.

1.1.4.2 Soft Handover Overhead

Table 1 Soft Handover Overhead


KPI Name Soft Handover Overhead (RNC)

Formula

A1:Number of UEs with 1 RL in the RNC


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

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 an RNC or a Cell. It considered the radio link
quantity during the soft handover.
In the RNC Soft handover ratio, count the mean number of UEs with different quantity of radio links for RNC from A1 to F1. The RNC
periodically samples of the number of UEs with corresponding radio links in a measurement period. At the end of the measurement
period, the RNC divides the accumulated number by the sampling times to obtain the soft handover overhead.
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.

Associated Counters Soft Handover Overhead (RNC) =


{[VS.SHO.AS.1.RNC+
(VS.SHO.AS.2Softer.RNC+
VS.SHO.AS.2Soft.RNC)*2+
(VS.SHO.AS.3Soft2Softer.RNC+
VS.SHO.AS.3Soft.RNC+
VS.SHO.AS.3Softer.RNC)*3+
VS.SHO.AS.4.RNC*4+

18 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.SHO.AS.5.RNC*5+
VS.SHO.AS.6.RNC*6]/
(VS.SHO.AS.1.RNC+
VS.SHO.AS.2Softer.RNC+
VS.SHO.AS.2Soft.RNC+
VS.SHO.AS.3Soft2Softer.RNC+
VS.SHO.AS.3Soft.RNC+
VS.SHO.AS.3Softer.RNC+
VS.SHO.AS.4.RNC+
VS.SHO.AS.5.RNC+
VS.SHO.AS.6.RNC)-1}*100%
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]*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.5 Mobility
Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or service mode changing in difference scenarios.

1.1.5.1 Soft Handover Success Ratio

Table 1 Soft Handover Success Ratio


Name Soft Handover Success Ratio

Formula

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.

Associated Counters Soft Handover Success Ratio (RNC) =


(VS.SHO.Succ.RNC/ VS.SHO.Att.RNC)*100%
Soft Handover Success Ratio (Cell) =
[(VS.SHO.SuccRLAdd+ VS.SHO.SuccRLDel)/ (VS.SHO.AttRLAdd+VS.SHO.AttRLDel)]*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.5.2 Softer Handover Success Ratio

Table 1 Softer Handover Success Ratio


Name Softer Handover Success Ratio

Formula

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.

Associated Counters Softer Handover Success Ratio (RNC) =


(VS.SoHO.Succ.RNC/VS.SoHO.Att.RNC)*100%
Softer Handover Success Ratio (Cell) =
[(VS.SoHO.SuccRLAdd+VS.SoHO.SuccRLDel)/ (VS.SoHO.AttRLAdd+VS.SoHO.AttRLDel)]*100%

Object RNC, CELL

Unit/Range %

Note None

19 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

1.1.5.3 AMR Soft Handover Success Ratio

Table 1 AMR Soft Handover Success Ratio


Name AMR Soft Handover Success Ratio

Formula

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

Associated Counters AMR Soft Handover Success Ratio =


[(VS.SHO.AMR.Succ)/ (VS.SHO.AMR.Att)]*100%

Object CELL

Unit/Range %

Note The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.

1.1.5.4 CS64 Soft Handover Success Ratio

Table 1 CS64 Soft handover Success Ratio


Name CS64 Soft handover Success Ratio

Formula

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

Associated Counters CS64 Soft Handover Success Ratio =


[(VS.SHO.CS64.Succ)/ (VS.SHO.CS64.Att)]*100%

Object CELL

Unit/Range %

Note The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.

1.1.5.5 PS Soft Handover Success Ratio

Table 1 PS soft handover Success Ratio


Name PS soft handover Success Ratio

Formula

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

Associated Counters PS services Soft Handover Success Ratio =


[(VS.SHO.PS.Succ)/(VS.SHO.PS.Att)]*100%

Object CELL

Unit/Range %

Note The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.

1.1.5.6 Intra-frequency Hard Handover Success Ratio

Table 1 Intra-frequency Hard Handover Success Ratio


Name Intra-frequency Hard Handover Success Ratio

Formula

Description This KPI is used to check the intra-frequency hard handover success ratio in an RNC.
The Intra-frequency Hard Handover Success procedure is complete when the RNC receives the PHYSICAL CHANNEL
RECONFIGURATION COMPLETE (for example) message from the UE.
The Intra-frequency Hard Handover Attempt procedure is complete when RNC sends the PHYSICAL CHANNEL RECONFIGURATION
message to the UE.

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


[(VS.HHO.SuccIntraFreqOut.IntraNodeB+
VS.HHO.SuccIntraFreqOut.InterNodeBIntraRNC+

20 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.HHO.SuccIntraFreqOut.InterRNC)/
(VS.HHO.AttIntraFreqOut.InterNodeBIntraRNC+
VS.HHO.AttIntraFreqOut.InterRNC+
VS.HHO.AttIntraFreqOut.InterRNC)]*100%
Intra-frequency Hard Handover Success Ratio (RNC) =
[(VS.HHO.SuccIntraFreq.RNC)/(VS.HHO.AttIntraFreq.RNC)]*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.5.7 Inter-frequency Hard Handover Success Ratio

Table 1 Inter-frequency Hard Handover Success Ratio


Name Inter-frequency Hard Handover Success Ratio

Formula

Description This KPI is used to check the inter-frequency hard handover success ratio in an RNC.
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 (RNC) =


(VS.HHO.SuccInterFreq.RNC/ VS.HHO.AttInterFreq.RNC)*100%
Inter-frequency Hard Handover Success Ratio (Cell) =
(VS.HHO.SuccInterFreqOut/ VS.HHO.AttInterFreqOut)*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.5.8 Service Cell Change Success Ratio with SHO (H2H)

Table 1 Service Cell Change Success Ratio with SHO (H2H)


Name Service Cell Change Success Ratio with SHO (H2H)

Formula

Description The HS-DSCH service cell change success with SHO is triggered with the following messages:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
ACTIVE SET UPDATE
Accordingly, the UE will send the following messages to the RNC as a response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
ACTIVE SET UPDATE COMPLETE
ACTIVE SET UPDATE FAILURE Message
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example. When receiving a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from a UE, the RNC measures this item as numerator, and when sending a PHYSICAL
CHANNEL RECONFIGURATION message to a UE, the RNC measures this item as denominator.

Associated Counters Service Cell Change Success Ratio with SHO (H2H) =
(VS.HSDPA.SHO.ServCellChg.SuccOut/ VS.HSDPA.SHO.ServCellChg.AttOut)*100%

Object CELL

Unit/Range %

Note None

1.1.5.9 H2H Intra-frequency Hard Handover Success Ratio

Table 1 H2H Intra-frequency Hard Handover Success Ratio


Name H2H Intra-frequency Hard Handover Success Ratio

Formula

21 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Description This KPI is used to check the intra-frequency hard handover success ratio of HSDPA service in an RNC or a cluster.
The HS-DSCH service cell change success with SHO is triggered with the following message:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
Accordingly, the UE will send the following messages to the RNC as a response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when receiving a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from a UE , the RNC measures this item in the best cell from which the UE is handed over
if an intra-frequency HSDPA hard handover without channel change is performed.

Associated Counters H2H Intra-frequency Hard Handover Success Ratio =


(VS.HSDPA.HHO.H2H.SuccOutIntraFreq/ VS.HSDPA.HHO.H2H.AttOutIntraFreq)*100%

Object CELL

Unit/Range %

Note None

1.1.5.10 H2H Inter-frequency Hard Handover Success Ratio

Table 1 H2H Inter-frequency Hard Handover Success Ratio


Name H2H Inter-frequency Hard Handover Success Ratio

Formula

Description This KPI is used to indicate the success ratio of inter-frequency hard handovers from the HSDPA to the HSDPA in a cell.
The hard handover procedure can be triggered with the following message:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
Accordingly, the UE will send the following messages to the RNC as a response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when receiving a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from a UE , the RNC measures this item in the best cell from which the UE is handed over
if an inter-frequency HSDPA hard handover without channel change is performed.

Associated Counters H2H Inter-frequency Hard Handover Success Ratio =


(VS.HSDPA.HHO.H2H.SuccOutInterFreq/ VS.HSDPA.HHO.H2H.AttOutInterFreq)*100%

Object CELL

Unit/Range %

Note None

1.1.5.11 H2D Inter-frequency Hard Handover Success Ratio

Table 1 H2D Inter-frequency Hard Handover Success Ratio


Name H2D Inter-frequency Hard Handover Success Ratio

Formula

Description This KPI is used to indicate the success ratio of inter-frequency hard handovers from the HSDPA to the DCH in a cell.
The hard handover procedure can be triggered with the following messages:
RADIO BEARER RECONFIGURATION
RADIO BEARER SETUP
RADIO BEARER RELEASE message
Accordingly, the UE will send the following messages to the RNC as a response.
RADIO BEARER RECONFIGURATION COMPLETE

22 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

RADIO BEARER RECONFIGURATION FAILURE


RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
Take the RADIO BEARER RECONFIGURATION message as an example, when receiving a RADIO BEARER RECONFIGURATION
COMPLETE message from a UE , the RNC measures this item in the best cell from which the UE is handed over if an inter-frequency
hard handover from the HSDPA to the DCH is performed.

Associated Counters H2D Inter-frequency Hard Handover Success Ratio =


(VS.HSDPA.HHO.H2D.SuccOutInterFreq/ VS.HSDPA.HHO.H2D.AttOutInterFreq)*100%

Object CELL

Unit/Range %

Note None

1.1.5.12 H2D Channel Switch Success Ratio

Table 1 H2D Channel Switch Success Ratio


Name H2D Channel Switch Success Ratio

Formula

Description This KPI is used to check the channel switch success ratio when UE switches from HSDPA to DCH in an RNC or a cluster.
The number of successful HS-DSCH to DCH channel switch measures when RNC receives a RAIDO BEARER RECONFIGURATION
COMPLETE message from the UE indicating the channel reconfiguration for HSDPA service in the DCCC or RAB MODIFY procedure.
The RNC measures the item in the HSDPA serving cell.
The attempt number of H2D channel handover counts when RNC decides to perform a channel handover, which sends a RADIO
BEARER RECONFIGURATION message to a UE during the DCCC or RAB MODIFY procedure. In this case, the RNC measures the
item in the serving cell of the HSDPA service according to the transport channels of UEs before and after the reconfiguration.
The RNC performs the transport channel Switch in the same cell.

Associated Counters H2D Channel Switch Success Ratio=


(VS.HSDPA.H2D.Succ/ VS.HSDPA.H2D.Att)*100%

Object CELL

Unit/Range %

Note None

1.1.5.13 D2H Channel Switch Success Ratio

Table 1 D2H Channel Switch Success Ratio


Name D2H Channel Switch Success Ratio

Formula

Description This KPI is used to check the channel switch success ratio when the UE switches from DCH to HSDPA in an RNC or a cluster.
The number of successful DCH to HS-DSCH channel switch measures when RNC receives from the UE a RAIDO BEARER
RECONFIGURATION COMPLETE message indicating the channel reconfiguration for HSDPA service in the DCCC or RAB MODIFY
procedure. The RNC measures the item in the HSDPA serving cell.
The attempt number of D2H channel switch counts when RNC decides to perform a channel switch, which sends a RADIO BEARER
RECONFIGURATION message to a UE during the DCCC or RAB MODIFY procedure. In this case, the RNC measures the item in the
serving cell of the HSDPA service according to the transport channels of UEs before and after the reconfiguration.
The RNC performs the transport channel switch in the same cell.

Associated Counters D2H Channel Switch Success Ratio =


(VS.HSDPA.D2H.Succ/ VS.HSDPA.D2H.Att)*100%

Object CELL

Unit/Range %

Note None

1.1.5.14 CS W2G Inter-RAT Handover Out Success Ratio

Table 1 CS W2G Inter-RAT Handover Out Success Ratio


Name CS W2G Inter-RAT Handover Out Success Ratio

Formula

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 RNC receives an IU RELEASE COMMAND message. The message
contains one of the following information: "Successful Relocation", "Normal Release", "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.
The CS inter-RAT Handover attempts procedure starts when the RNC sends a HANDOVER FROM UTRAN COMMAND message to

23 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

the UE during the CS outgoing inter-RAT handover.

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


(VS.IRATHO.SuccOutCS.RNC/ VS.IRATHO.AttOutCS.RNC)*100%
CS W2G Inter-RAT Handover Out Success Ratio (Cell) =
(IRATHO.SuccOutCS/ IRATHO.AttOutCS)*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.5.15 PS W2G Inter-RAT Handover Out Success Ratio

Table 1 PS W2G Inter-RAT Handover Out Success Ratio


Name PS W2G Inter-RAT Handover Out Success Ratio

Formula

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 IU RELEASE COMPLETE
message after receiving the IU RELEASE COMMAND message. The message contains one of the following information: "Successful
Relocation", "Normal Release", "Network Optimization" during the PS outgoing inter-RAT handover. In this case, the PS outgoing
inter-RAT handover succeeds and the counter is measured.
The PS W2G Inter-RAT Outgoing Handover attempts procedure starts when the RNC sends the CELL CHANGE ORDER FROM
UTRAN message during the PS outgoing inter-RAT handover.

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


(VS.IRATHO.SuccOutPSUTRAN.RNC/ VS.IRATHO.AttOutPSUTRAN.RNC)*100%
PS W2G Inter-RAT Handover Out Success Ratio (Cell) =
(IRATHO.SuccOutPSUTRAN/ IRATHO.AttOutPSUTRAN)*100%

Object RNC, CELL

Unit/Range %

Note None

1.1.5.16 PS G2W Inter-RAT Handover In Success Ratio

Table 1 PS G2W Inter-RAT Handover In Success Ratio


Name PS G2W Inter-RAT Handover In Success Ratio

Formula

Description This KPI is used to check the PS inter-RAT handover in success ratio in an RNC or a cluster.
The PS G2W Inter-RAT Handover successes procedure is complete when the RNC receives an RRC CONNECTION SETUP
COMPLETE message from the UE. The reasons for RRC connection request is Inter-RAT Cell Change Order and Inter-RAT Cell
Reselection.
The PS G2W Inter-RAT Handover attempts procedure starts when the RNC receives an RRC CONNECTION REQUEST message from
the UE, the reasons for RRC CONNECTION REQUEST is Inter-RAT Cell Change Order and Inter-RAT Cell Reselection.

Associated Counters PS G2W Inter-RAT Handover In Success Ratio =


[(RRC.SuccConnEstab.IRATCCO+RRC.SuccConnEstab.IRATCelRes)/
(RRC.AttConnEstab.IRATCCO+RRC.AttConnEstab.IRATCelRes)]*100%

Object CELL

Unit/Range %

Note The KPI includes the IRAT cell reselection of UE in idle status.

1.1.5.17 HSDPA W2G Inter-RAT Handover Out Success Ratio

Table 1 HSDPA W2G Inter-RAT Handover Out Success Ratio


Name HSDPA W2G Inter-RAT Handover Out Success Ratio

Formula

Description This KPI is used to check the PS outgoing inter-RAT handover for HSDPA services initiated by the RNC in the best cell that the UE
camps on before the handover.
The HSDPA Inter-RAT HO successes procedure is complete when the RNC receives the IU RELEASE COMMAND message . The
message contains one of the following information: "Successful Relocation", "Normal Release", "Network Optimization" during the PS
outgoing inter-RAT handover for HSDPA services.
The HSDPA Inter-RAT HO attempts procedure starts when the RNC sends the CELL CHANGE ORDER FROM UTRAN message
during the PS outgoing inter-RAT handover for HSDPA services, the counter is measured in the best cell that the UE camps on.

Associated Counters HSDPA W2G Inter-RAT Handover Out Success Ratio=


(VS.IRATHO.HSDPA.SuccOutPSUTRAN/ VS.IRATHO.HSDPA.AttOutPSUTRAN)*100%

Object CELL

24 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Unit/Range %

Note The KPI includes the IRAT cell reselection of UE in idle status.

1.1.5.18 SRNC Relocation Success Ratio

Table 1 SRNC Relocation Success Ratio


Name SRNC Relocation Success Ratio

Formula

Description This KPI is used to check the relocation executions (UE involved and UE not involved) initiated by SRNC according to different CN
domains.
The SRNC Relocation Success procedure is complete when the SRNC receives an IU RELEASE COMMAND message. The message
contains one of the following information: "Successful Relocation", "Normal Release", "Network Optimization". In this case, the SRNC
measures the related counter according to the CN domain.
The SRNC Relocation Attempts procedure starts when the SRNC receives a RELOCATION COMMAND message from the CN in the
CS domain. In this case, the SRNC measures the related counter according to different relocation types (CS, PS, UE involved, UE not
involved).

Associated Counters SRNC Relocation Success Ratio =


[(VS.SRELOC.SuccExecUEInvolCS+
VS.SRELOC.SuccExecUEInvolPS+
VS.SRELOC.SuccExecUENonInvolCS+
VS.SRELOC.SuccExecUENonInvolPS)/
(RELOC.SuccPrepUEInvolCS+
RELOC.SuccPrepUENotInvolCS+
RELOC.SuccPrepUEInvolPS+
RELOC.SuccPrepUENotInvolPS)]*100%

Object RNC

Unit/Range %

Note None

1.1.5.19 TRNC Relocation Success Ratio

Table 1 TRNC Relocation Success Ratio


Name TRNC Relocation Success Ratio

Formula

Description This KPI is used to check the TRNC relocation executions (UE involved and UE not involved) initiated by SRNC according to different
CN domains.
The TRNC Relocation Success procedure is complete when the TRNC relocation is complete, and when the TRNC sends a
RELOCATION COMPLETE message to the CN. In this case, the TRNC measures the related counters according to different relocation
types. If the UE connects to both the CS domain and the PS domain at the same time, the related counters are increased by one each
time the TRNC sends a RELOCATION COMPLETE message to the CNs in the CS domain and PS domain.
When the resource allocation for TRNC relocation is complete, the TRNC sends a RELOCATION REQUEST ACKNOWLEDGE
message to the CN in the CS or the PS domain. In this case, the TRNC measures the related counter according to different relocation
types.

Associated Counters TRNC Relocation Success Ratio =


[(VS.TRELOC.SuccExecUEInvol+
VS.TRELOC.SuccExecUENotInvol)/
(RELOC.SuccResAllocUEInvolCS+
RELOC.SuccResAllocUENotInvolCS+
RELOC.SuccResAllocUEInvolPS+
RELOC.SuccResAllocUENotInvolPS)]*100%

Object RNC

Unit/Range %

Note None

1.1.5.20 E-DCH Soft Handover Success Ratio

Table 1 E-DCH Soft Handover Success Ratio


Name E-DCH Soft Handover Success Ratio

Formula

Description This KPI is used to check EDCH RL additions and deletions due to soft handover in a cell.
The E-DCH soft Handover Success procedure is complete when the RNC receives an ACTIVE SET UPDATE COMPLETE message
from the UE. An EDCH link is added or deleted during the soft handover.
The E-DCH soft Handover attempts procedure starts when the RNC sends an ACTIVE SET UPDATE message to the UE and there is
EDCH RL to be deleted or added during the soft handover.

25 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Associated Counters E-DCH Soft Handover Success Ratio=


(VS.HSUPA.SHO.SuccOut/ VS.HSUPA.SHO.AttOut)*100%

Object CELL

Unit/Range %

Note None

1.1.5.21 E-DCH Cell Change Success Ratio with SHO

Table 1 E-DCH Cell Change Success Ratio with SHO


Name E-DCH Cell Change Success Ratio with SHO

Formula

Description This KPI is used to check the success ratio of HSUPA serving cell changes in soft handover status for cell.
Description of the numerator:
The successful HSUPA serving cell changes in soft handover status for cell, this procedure can be triggered with the following
messages:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
Accordingly, the UE will send the following messaged to the RNC as a response:
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC receives a PHYSICAL
CHANNEL RECONFIGURATION COMPLETE message from the UE, the RNC measures this item in the original HSUPA
serving cell if the HSUPA serving cell is changed. The item is used to indicate the change of HSUPA serving cells in the soft
handover state instead of the hard handover state.
Description of the denominator:
Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC sends a PHY CHANNEL
RECONFIGURATION message to the UE. The RNC measures this item in the original HSUPA serving cell if the HSUPA
serving cell is changed. This item is used to indicate the change of HSUPA serving cells in the soft handover status instead of
the hard handover status.

Associated Counters E-DCH Service Cell Change Success Ratio with SHO =
(VS.HSUPA.SHO.ServCellChg.SuccOut/ VS.HSUPA.SHO.ServCellChg.AttOut)*100%

Object CELL

Unit/Range %

Note None

1.1.5.22 E-DCH Cell Change Success Ratio with Inter-HHO

Table 1 E-DCH Cell Change Success Ratio with Inter-HHO


Name E-DCH Cell Change Success Ratio with Inter-HHO

Formula

Description This KPI is used to check the E-DCH service cell change success ratio with the Inter-HHO procedure in an RNC or a cluster.
Description of the numerator:
When the RNC receives one of the following messages from the UE, the RNC measures this item in the HSUPA serving cell
before the hard handover if an EDCH-to-EDCH inter-frequency hard handover is performed.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER SETUP COMPLETE
RADIO BEARER RELEASE COMPLETE
Description of the denominator:
When the RNC sends the following messages to the UE , the RNC measures the item in the HSUPA serving cell before the
hard handover if an EDCH-to-EDCH inter-frequency hard handover is performed.
PHYSICAL CHANNEL RECONFIGRATION
TRANSPORT CHANNEL RECONFIGRATION
RADIO BEARER RECONFIGRATION
RADIO BEARER SETUP
RADIO BEARER RELEASE

Associated Counters E-DCH Service Cell Change Success Ratio with Inter-HHO=
(VS.HSUPA.HHO.E2E.SuccOutInterFreq/ VS.HSUPA.HHO.E2E.AttOutInterFreq)*100%

Object CELL

Unit/Range %

26 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Note None

1.1.5.23 E2D Channel Switch Success Ratio

Table 1 E2D Channel Switch Success Ratio


Name E2D Channel Switch Success Ratio

Formula

Description This KPI is used to check the channel switch success ratio when there is UE handover from E-DCH to DCH in the same cell.
The Switch Channel Type from EDCH to DCH successful attempts procedure is complete when the RNC receives an RB RECFG CMP
message from the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC
measures the items in the HSUPA serving cell by the channel switch type.
The Switch Channel Type from EDCH to DCH attempts procedure starts when the RNC sends a RADIO BEAR RECONFIGURE
message to the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC
measures the items in the HSUPA serving cell by the channel switch type.

Associated Counters E2D Channel Switch Success Ratio =


(VS.HSUPA.E2D.Succ/ VS.HSUPA.E2D.Att)*100%

Object CELL

Unit/Range %

Note None

1.1.5.24 D2E Channel Switch Success Ratio

Table 1 D2E Channel Switch Success Ratio


Name D2E Channel Switch Success Ratio

Formula

Description This KPI is used to check the channel switch success ratio when there is UE handover from E-DCH to DCH in the same cell.
The Switch Channel Type from DCH to EDCH successful attempts procedure is complete when the RNC receives a RB RECFG CMP
message from the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC
measures the items in the HSUPA serving cell by the channel switch type.
The Switch Channel Type from DCH to EDCH attempts procedure starts when the RNC sends a RADIO BEAR RECONFIGURE
message to the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC
measures the items in the HSUPA serving cell by the channel switch type.

Associated Counters D2E Channel Switch Success Ratio (Intra Cell) =


(VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att)*100%

Object CELL

Unit/Range %

Note None

1.1.5.25 E2D Handover Success Ratio with Inter HHO

Table 1 E2D Handover Success Ratio with Inter HHO


Name E2D Handover Success Ratio with Inter HHO

Formula

Description This KPI is used to check the success ratio of HSUPA Inter-Frequency Hard Handover from EDCH to DCH in a cell.
The Switch Channel Type from EDCH to DCH successful attempts procedure is complete when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE. The RNC measures this item in the HSUPA serving cell before the hard
handover if an EDCH-to-DCH inter-frequency hard handover is performed.
The Switch Channel Type from EDCH to DCH attempts procedure starts when the RNC sends a RADIO BEARER
RECONFIGURATION message to the UE. The RNC measures this item in the HSUPA serving cell before the hard handover if an
EDCH-to-DCH inter-frequency hard handover is performed.

Associated Counters E-DCH to DCH Handover Success Ratio (with Inter HHO) =
(VS.HSUPA.HHO.E2D.SuccOutInterFreq/ VS.HSUPA.HHO.E2D.AttOutInterFreq)*100%

Object CELL

Unit/Range %

Note None

1.1.5.26 HSUPA W2G Inter-RAT Handover Out Success Ratio

Table 1 HSUPA W2G Inter-RAT Handover Out Success Ratio


Name HSUPA W2G Inter-RAT Handover Out Success Ratio

27 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Formula

Description This KPI is used to check the HSUPA service Inter-RAT handover success ratio from WCDMA to GPRS in the best cell that the UE
camps on.
The HSUPA W2G Inter-RAT Handover Out success procedure is complete when the RNC receives an IU RELEASE COMMAND
message. The message contains one of the following information: "Successful Relocation", "Normal Release", "Network Optimization"
and sends an IU RELEASE COMPLETE message during the PS outgoing inter-RAT handover for HSUPA services. In this case, the PS
outgoing handover succeeds and this counter is measured in the best cell that the UE camps on before the handover.
The HSUPA W2G Inter-RAT Handover Out attempts procedure starts when the RNC sends a CELL CHANGE ORDER FROM UTRAN
message to the UE during the PS outgoing inter-RAT handover for HSUPA services. In this case, this counter is measured in the best
cell that the UE camps on.

Associated Counters HSUPA W2G Inter-RAT Handover Out Success Ratio =


(VS.IRATHO.HSUPA.SuccOutPSUTRAN/VS.IRATHO.HSUPA.AttOutPSUTRAN)*100%

Object CELL

Unit/Range %

Note None

1.1.5.27 MBMS Service Mode Switch Success Ratio

Table 1 MBMS Service Mode Switch Success Ratio


Name MBMS Service Mode Switch Success Ratio

Formula

Description This KPI is used to check the MBMS service mode switch success ratio from PTP to PTM.
The MBMS Service Mode Switch Success procedure is complete after a MBMS service is switched from PTP mode to PTM mode and
a PTM MBMS RB is successfully set up.
The MBMS Service Mode Switch attempts procedure starts after the initiation of transition from PTP mode to PTM mode.

Associated Counters MBMS Service Mode Switch Success Ratio from PTP to PTM=
(VS.MBMS.PTPtoPTM.Succ/VS.MBMS.PTPtoPTM.Att)*100%

Object CELL

Unit/Range %

Note None

1.1.6 Retainability
Retainability is defined as the ability of a user to retain its requested service for the required duration once connected. The RNC level KPIs can be calculated by aggregating all the cell counters and
Iur counters.

1.1.6.1 CS Service Drop Ratio

Table 1 CS Service Drop Ratio


Name CS Service Drop Ratio

Formula

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).
Description of RAB abnormal Release:
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)]*100%
CS Service Drop Ratio (RNC)=
[VS.RAB.AbnormRel.CS.RNC/(VS.RAB.AbnormRel.CS.RNC+VS.RAB.NormRel.CS.RNC)]*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.6.2 AMR Call Drop Ratio

Table 1 AMR Call Drop Ratio


Name AMR Call Drop Ratio

Formula

Description This KPI provides the ratio of AMR RAB abnormal Releases to the total AMR RAB Releases (Normal Release + Abnormal Release)
and is used to check the retainabililty of AMR Service within the UTRAN (RNC or Cluster).

28 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

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 messages: "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 AMR Call Drop Ratio(Cell)=


[VS.RAB.AbnormRel.AMR/(VS.RAB.AbnormRel.AMR+ VS.RAB.NormRel.AMR)]*100%
AMR Call Drop Ratio (RNC)=
[(Sum{VS.RAB.AbnormRel.AMR}+Sum{VS.RAB.AbnormRel.AMR.Iur})/
(Sum{VS.RAB.AbnormRel.AMR}+ Sum{VS.RAB.NormRel.AMR}+ Sum{VS.RAB.AbnormRel.AMR.Iur}+
Sum{VS.RAB.NormRel.AMR.Iur})]*100%

Object CELL, RNC

Unit/Range %

Note The RNC level KPIs are calculated by aggregating all the Cell and Iur counters in SRNC.

1.1.6.3 VP Call Drop Ratio

Table 1 VP Call Drop Ratio


Name VP Call Drop Ratio

Formula

Description This KPI provides the ratio of the VP (Video Phone) RAB abnormal Releases to the total VP RAB Releases (Normal Release + Abnormal Release) and
is used to check the retainabililty of VP 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.

Associated VP Call Drop Ratio (Cell) =


Counters [VS.RAB.AbnormRel.CS64/(VS.RAB.AbnormRel.CS64+VS.RAB.NormRel.CS64)]*100%
VP Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.CS64}+Sum{VS.RAB.AbnormRel.CS64.Iur})/
(Sum{VS.RAB.AbnormRel.CS64}+Sum{VS.RAB.NormRel.CS64}+Sum{VS.RAB.AbnormRel.CS64.Iur}+Sum{VS.RAB.NormRel.CS64.Iur})]*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.6.4 AMR Traffic Drop Ratio

Table 1 AMR Traffic Drop Ratio


Name AMR Traffic Drop Ratio

Formula

Description This KPI provides the ratio of the AMR Service Erlang to the AMR RAB Abnormal Releases, which indicates the AMR average Erlang
per AMR call drop within the UTRAN (RNC or Cluster).
Description of the AMR RB counters in the numerator:
Average number of AMR users with different DL rates during the measurement period.
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 AMR Traffic Drop Ratio (Cell) =


[(VS.RB.AMR.DL.12.2+
VS.RB.AMR.DL.10.2+
VS.RB.AMR.DL.7.95+
VS.RB.AMR.DL.7.4+
VS.RB.AMR.DL.6.7+
VS.RB.AMR.DL.5.9+
VS.RB.AMR.DL.5.15+
VS.RB.AMR.DL.4.75)*{SP}/60]/
VS.RAB.AbnormRel.AMR
AMR Traffic Drop Ratio (RNC) =
[(VS.RB.AMR.DL.4.75.RNC+
VS.RB.AMR.DL.5.15.RNC+
VS.RB.AMR.DL.5.9.RNC+
VS.RB.AMR.DL.6.7.RNC+
VS.RB.AMR.DL.7.4.RNC+
VS.RB.AMR.DL.7.95.RNC+
VS.RB.AMR.DL.10.2.RNC+
VS.RB.AMR.DL.12.2.RNC) *{SP}/60]/
(VS.RAB.AbnormRel.AMR.RNC)

29 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Object CELL, RNC

Unit/Range The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit of minute

Note None

1.1.6.5 VP Traffic Drop Ratio

Table 1 VP Traffic Drop Ratio


Name VP Traffic Drop Ratio

Formula

Description This KPI provides the ratio of the VP (Video Phone) Service Erlang to the VP RAB Abnormal Releases, which indicates the VP average
Erlang per VP call drop within the UTRAN (RNC or Cluster).
Description of the VS.RB.CS.Conv.DL.64/VS.RB.CS.Conv.DL.64.RNC:
Average number of VP users with different DL rates during the measurement period.
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.RB.CS.Conv.DL.64*{SP}/60)/VS.RAB.AbnormRel.CS64
VP Traffic Drop Ratio (RNC) =
(VS.RB.CS.Conv.DL.64.RNC*{SP}/60)/(VS.RAB.AbnormRel.CS64.RNC)

Object CELL, RNC

Unit/Range The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit of minute

Note None

1.1.6.6 PS Call Drop Ratio

Table 1 PS Call Drop Ratio


Name PS Call Drop Ratio

Formula

Description This 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.

Associated Counters PS Call Drop Ratio (Cell) =


[VS.RAB.AbnormRel.PS/ (VS.RAB.AbnormRel.PS+ VS.RAB.NormRel.PS)]*100%
PS Call Drop Ratio (RNC) =
[VS.RAB.AbnormRel.PS.RNC/ (VS.RAB.AbnormRel.PS.RNC+ VS.RAB.NormRel.PS.RNC)]*100%

Object CELL, RNC

Unit/Range %

Note None

1.1.6.7 PS Call Drop Ratio (PCH)

Table 1 PS Call Drop Ratio (PCH)


Name PS Call Drop Ratio (PCH)

Formula

Description 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+

30 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.DCCC.Succ.F2P)]*100%
PS Service Drop Ratio with PCH (RNC) =
[(VS.RAB.AbnormRel.PS.RNC-
Sum{VS.RAB.AbnormRel.PS.PCH}-
Sum{VS.RAB.AbnormRel.PS.D2P}-
Sum{VS.RAB.AbnormRel.PS.F2P})/
(VS.RAB.AbnormRel.PS.RNC+
VS.RAB.NormRel.PS.RNC-
Sum{VS.RAB.AbnormRel.PS.PCH}-
Sum{VS.RAB.NormRel.PS.PCH}+
Sum{VS.DCCC.D2P.Succ}+
Sum{VS.DCCC.Succ.F2P})]*100%

Object CELL, RNC

Unit/Range %

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?
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.

1.1.6.8 PS R99 Call Drop Ratio

Table 1 PS R99 Call Drop Ratio


Name PS R99 Call Drop Ratio

Formula

Description This KPI provides the ratio of the PS R99 RAB abnormal Releases to the total PS R99RAB Releases (Normal Release + Abnormal
Release) and is used to check the retainabililty of PS R99 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.

Associated Counters PS R99 Call Drop Ratio (Cell) =


(VS.RAB.AbnormRel.PSR99)/(VS.RAB.AbnormRel.PSR99+VS.RAB.NormRel.PSR99)*100%

Object CELL

Unit/Range %

Note RNC level KPI can be calculated approximately by aggregating all the cell level counters in SRNC, due to the counters are counted in
the best cell of active set.If the best cell for the PS R99 RAB Establishment is located in DRNC through Iur interface, no counters for the
scenario exists in SRNC.

1.1.6.9 PS R99 Call Drop Ratio (PCH)

Table 1 PS R99 Call Drop Ratio (PCH)


Name PS R99 Call Drop Ratio (PCH)

Formula

Description Compared with PS R99 Call Drop Ratio, This KPI takes the PCH state into account.

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


[(VS.RAB.AbnormRel.PSR99-
VS.RAB.AbnormRel.PS.PCH-
VS.RAB.AbnormRel.PS.R99D2P-
VS.RAB.AbnormRel.PS.F2P)/
(VS.RAB.AbnormRel.PSR99+
VS.RAB.NormRel.PSR99-
VS.RAB.AbnormRel.PS.PCH-
VS.RAB.NormRel.PS.PCH+
VS.HSDPA.F2H.Succ+
VS.HSDPA.D2H.Succ+
VS.PSR99.D2P.Succ+
VS.DCCC.Succ.F2P)]*100%

Object CELL

Unit/Range %

Note The occasion of a UE transferring out of PS R99 state (F2H,F2P,D2H) should be considered as a normal RAB release for calculating
the formula of PS R99 Call Drop Ratio.
RNC level KPI can be calculated approximately by aggregating all the cell level counters in SRNC. Due to the counters are counted in

31 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

the best cell of active set, If the best cell for the PS R99 RAB Establishment located in DRNC via Iur interface, this scenario is not taken
into account in the formula.
VS.RAB.AbnormRel.PSR99 and VS.RAB.NormRel.PSR99 have already taken PCH into account, the occasion of the RAB
Normal/Abnormal Release (VS.RAB.AbnormRel.PS.PCH and VS.RAB.NormRel.PS.PCH) should be excluded off the Denominator.

1.1.6.10 PS BE Call Drop Ratio

Table 1 PS BE Call Drop Ratio


Name PS BE Call Drop Ratio

Formula

Description This KPI provides the ratio of the PS BE RAB abnormal Releases to the total PS BE RAB Releases (Normal Release + Abnormal
Release) and is used to check the retainabililty of PS BE 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.

Associated Counters PS BE Call Drop Ratio (Cell) =


[VS.RAB.AbnormRel.PS.BE/(VS.RAB.AbnormRel.PS.BE+VS.RAB.NormRel.PS.BE)]*100%
PS BE Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.PS.BE}+Sum{VS.RAB.AbnormRel.PS.BE.Iur})/
(Sum{VS.RAB.AbnormRel.PS.BE}+Sum{VS.RAB.NormRel.PS.BE}+Sum{VS.RAB.AbnormRel.PS.BE.Iur}+
Sum{VS.RAB.NormRel.PS.BE.Iur})]*100%

Object CELL, RNC

Unit/Range %

Note RNC level KPI can is calculated approximately by aggregating all the Cell and Iur level counters in SRNC.

1.1.6.11 HSDPA Call Drop Ratio

Table 1 HSDPA Call Drop Ratio


Name HSDPA Call Drop Ratio

Formula

Description This KPI provides the ratio of the HSDPA RAB abnormal Releases to the total HSDPARAB 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.

Associated Counters HSDPA Call Drop Ratio (Cell) =


[(VS.HSDPA.RAB.AbnormRel)/
(VS.HSDPA.RAB.AbnormRel+
VS.HSDPA.RAB.NormRel+
VS.HSDPA.H2D.Succ+
VS.HSDPA.H2F.Succ+
VS.HSDPA.HHO.H2D.SuccOutIntraFreq+
VS.HSDPA.HHO.H2D.SuccOutInterFreq)]*100%
HSDPA Call Drop Ratio (RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur})/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}+
Sum{VS.RAB.NormRel.HSDPA.Iur}+
Sum{VS.HSDPA.RAB.NormRel}+
Sum{VS.HSDPA.H2D.Succ}+
Sum{VS.HSDPA.H2F.Succ}+
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq})]*100%

Object CELL, RNC

Unit/Range %

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 HS-DSCH release (Including the transitions due to mobility).

1.1.6.12 HSDPA Call Drop Ratio (PCH)

Table 1 HSDPA Call Drop Ratio (PCH)


Name HSDPA Call Drop Ratio (PCH)

Formula

32 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Description Compared with HSDPA Call Drop Ratio, This KPI takes the PCH state into account.

Associated Counters HSDPA Service Drop Ratio with PCH (Cell) =


[(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)]*100%
HSDPA Service Drop Ratio with PCH (RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}-
Sum{VS.HSDPA.RAB.AbnormRel.H2P})/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}+
Sum{VS.RAB.NormRel.HSDPA.Iur}+
Sum{VS.HSDPA.RAB.NormRel}+
Sum{VS.HSDPA.H2D.Succ}+
Sum{VS.HSDPA.H2F.Succ}+
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq}+
Sum{VS.HSDPA.H2P.Succ})]*100%

Object CELL, RNC

Unit/Range %

Note 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.

1.1.6.13 HSUPA Call Drop Ratio

Table 1 HSUPA Call Drop Ratio


Name HSUPA Call Drop Ratio

Formula

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.

Associated Counters HSUPA Call Drop Ratio (Cell) =


[VS.HSUPA.RAB.AbnormRel/
(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)]*100%
HSUPA Call Drop Ratio (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur})/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}+
Sum{VS.RAB.NormRel.HSUPA.Iur} +
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq}+
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq} +
Sum{VS.HSUPA.E2F.Succ}+Sum{VS.HSUPA.E2D.Succ})]*100%

Object CELL, RNC

Unit/Range %

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).

1.1.6.14 HSUPA Call Drop Ratio (PCH)

Table 1 HSUPA Call Drop Ratio (PCH)


Name HSUPA Call Drop Ratio (PCH)

33 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Formula

Description Compared with HSUPA Call Drop Ratio, This KPI takes the PCH state into account.

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)]*100%
HSUPA Call Drop Ratio with PCH (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}-
Sum{VS.HSUPA.RAB.AbnormRel.E2P})/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}+
Sum{VS.RAB.NormRel.HSUPA.Iur}+
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq}+
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq}+
Sum{VS.HSUPA.E2F.Succ}+
Sum{VS.HSUPA.E2D.Succ}+
Sum{VS.HSUPA.E2P.Succ})]*100%

Object CELL, RNC

Unit/Range %

Note The occasion of a UE transferring out of PS E-DCH Channel state (E2D,E2F,E2P) should be considered as a normal RAB release for
calculating the formula of PS HSUPA Call Drop Ratio.

1.1.6.15 MBMS Service PTP drop Ratio

Table 1 MBMS Service PTP drop Ratio


Name MBMS Service PTP drop Ratio

Formula

Associated Counters MBMS Service PTP Drop Ratio=


[VS.MBMS.RB.PTP.Loss.Abnorm/(VS.MBMS.RB.PTP.Loss.Abnorm+VS.MBMS.RB.PTP.Loss.norm)]*100%

Object CELL

Unit/Range %

Note The RNC level KPIs is calculated by aggregating all the cell counters.

1.1.7 Service Integrity


Service Integrity KPIs mainly indicate the service capabilities for PS/HSPA throughput during busy hours in each cell and the service UL Average BLER for evaluating the UL BLER value of services
in each cell.

1.1.7.1 Average UL Throughput for PS R99 Service

Table 1 Average UL Throughput for PS R99 Service


Name Average UL Throughput for PS R99 Service

Description These counters provide the average uplink rates of different PS R99 services in the cells of the active set.
The UL traffic (excluding the RLC header and the retransmitted data, unit: bit) and the Data transfer duration (unit: ms) of each kind of
PS R99 services are accumulated in the measurement period for the cells that are under the SRNC. At the end of the measurement
period, the RNC divides the total bytes by the total data transfer time to obtain the Average UL Throughput for each PS R99 Service.

Associated Counters VS.PS.Bkg.Kbps.UL8


VS.PS.Bkg.Kbps.UL16
VS.PS.Bkg.Kbps.UL32
VS.PS.Bkg.Kbps.UL64
VS.PS.Bkg.Kbps.UL128
VS.PS.Bkg.Kbps.UL144
VS.PS.Bkg.Kbps.UL256
VS.PS.Bkg.Kbps.UL384
VS.PS.Int.Kbps.UL8
VS.PS.Int.Kbps.UL16
VS.PS.Int.Kbps.UL32
VS.PS.Int.Kbps.UL64
VS.PS.Int.Kbps.UL128
VS.PS.Int.Kbps.UL144
VS.PS.Int.Kbps.UL256

34 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.PS.Int.Kbps.UL384
VS.PS.Str.Kbps.UL8
VS.PS.Str.Kbps.UL16
VS.PS.Str.Kbps.UL32
VS.PS.Str.Kbps.UL64
VS.PS.Str.Kbps.UL128
VS.PS.Conv.Kbps.UL

Object CELL

Unit/Range Kbit/s

Note None

1.1.7.2 Average DL Throughput for PS R99 Service

Table 1 Average DL Throughput for PS R99 Service


Name Average DL Throughput for PS R99 Service

Description These counters provide the average downlink rates of different PS R99 services in the cells of the active set.
The DL traffic (excluding the RLC header and the retransmitted data, unit: bit) and the Data transfer duration (unit: ms) of each kind of
PS R99 services are accumulated in the measurement period for the cells that are under the SRNC. At the end of the measurement
period, the RNC divides the total bytes by the total data transfer time to obtain the Average DL Throughput for each PS R99 Service.

Associated Counters VS.PS.Bkg.Kbps.DL8


VS.PS.Bkg.Kbps.DL16
VS.PS.Bkg.Kbps.DL32
VS.PS.Bkg.Kbps.DL64
VS.PS.Bkg.Kbps.DL128
VS.PS.Bkg.Kbps.DL144
VS.PS.Bkg.Kbps.DL256
VS.PS.Bkg.Kbps.DL384
VS.PS.Int.Kbps.DL8
VS.PS.Int.Kbps.DL16
VS.PS.Int.Kbps.DL32
VS.PS.Int.Kbps.DL64
VS.PS.Int.Kbps.DL128
VS.PS.Int.Kbps.DL144
VS.PS.Int.Kbps.DL256
VS.PS.Int.Kbps.DL384
VS.PS.Str.Kbps.DL8
VS.PS.Str.Kbps.DL16
VS.PS.Str.Kbps.DL32
VS.PS.Str.Kbps.DL64
VS.PS.Str.Kbps.DL128
VS.PS.Str.Kbps.DL144
VS.PS.Str.Kbps.DL256
VS.PS.Str.Kbps.DL384
VS.PS.Conv.Kbps.DL

Object CELL

Unit/Range Kbit/s

Note None

1.1.7.3 Average UL BLER for CS Service

Table 1 Average UL BLER for CS Service


Name Average UL BLER for CS Service

Description These counters provide the UL BLER of AMR and CS 64K Conv. services on the DCH in the best cell. The counters are triggered in the
best cell when the number of UL TBs carrying the CS services on the DCH reaches the defined sampling window (500 TBs).

Associated Counters VS.ULBler.AMR


VS.ULBler.CS64

Object CELL

Unit/Range %

Note None

1.1.7.4 Average UL BLER for PS Service

Table 1 Average UL BLER for PS Service


Name Average UL BLER for PS Service

Description This counter provides the UL BLER of PS services on the DCH in the best cell.
The counters are triggered in the best cell when the number of UL TBs carrying the PS services on the DCH reaches the defined
sampling window (500 TBs).

Associated Counters VS.ULBler.PS.BE.DCH.8


VS.ULBler.PS.BE.DCH.16
VS.ULBler.PS.BE.DCH.32

35 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.ULBler.PS.BE.DCH.64
VS.ULBler.PS.BE.DCH.128
VS.ULBler.PS.BE.DCH.144
VS.ULBler.PS.BE.DCH.256
VS.ULBler.PS.BE.DCH.384
VS.ULBler.PS.BE.RACH
VS.ULBler.PS.Conv
VS.ULBler.PS.Str

Object CELL

Unit/Range %

Note None

1.1.7.5 HSDPA Throughput

Table 1 Mean Throughput for One HSDPA User


Name Mean Throughput for One HSDPA User

Description This counter indicates the mean downlink throughput for ONE HSDPA UE in a cell.
When the data is transferred to an HSDPA serving cell, the RNC measures the data transfer time of all the UEs and the total bytes sent
in the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean
downlink throughput of MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.

Associated Counters VS.HSDPA.MeanChThroughput

Object CELL

Unit/Range Kbit/s

Note None

Table 2 Mean Throughput for One HSDPA Cell


Name Mean Throughput for One HSDPA Cell

Description This counter provides the MAC-hs throughput when at least one HSDPA user is transferring data at the physical layer during the entire
measurement period.

Associated Counters VS.DataOutput.Mean/(VS.DataTtiRatio.Mean-VS.HSDPA.InactiveDataTtiRatio.Mean)

Object NodeB

Unit/Range Kbit/s

Note We can apply the following formula to get the Mean HSDPA Cell Throughput within RNC approximately:
HSDPA Cell Throughput (RNC Cell) =
VS.HSDPA.MeanChThroughput.TotalBytes*8/[{SP}*60]/1000
Where:
{SP} is the Statistic Period with the unit of Minute.
The KPI may not be accurate under the following condition: there is no HSDPA User transferring data for a while during the
total measurement period. Therefore, the KPI should be evaluated during busy hour for accuracy.

1.1.7.6 HSUPA Throughput

Table 1 Mean Throughput for One HSUPA User


Name Mean Throughput for One HSUPA User

Description This counter indicates the mean downlink throughput for ONE HSUPA UE in a cell.
When the data is received in HSUPA active cells, the RNC measures the data transfer time of all the UEs and the total bytes received in
the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean uplink
throughput of MAC-d flow in the cell. The RLC header and the retransfer data are excluded.

Associated Counters VS.HSUPA.MeanChThroughput

Object CELL

Unit/Range Kbit/s

Note None

Table 2 Mean Throughput for One HSUPA Cell


Name Mean Throughput for One HSUPA Cell

Description This counter provides the Mean HSUPA Cell Throughput when at least one HSUPA user is transferring data during the entire
measurement period.
Average bit rate of MAC-d data flows that the NodeB receives successfully from all users over the time when data is transferred during
a measurement period. The time when there is data transfer during a measurement period is calculated as follows: Sampling times of
data transfer x length of the sampling period If the number of received MAC-d PDU bits is 0 in a certain sampling period, which is 10 ms
in length, the NodeB does not count this period.

Associated Counters VS.HSUPA.MeanBitRate.WithData

Object NodeB

Unit/Range Kbit/s

36 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Note We can apply the following formula to get the Mean HSUPA Cell Throughput within the RNC approximately:
HSUPA Cell Throughput (RNC Cell) =
VS.HSUPA.MeanChThroughput.TotalBytes*8/[{SP}*60]/1000
Where:
{SP} is the Statistic Period with the unit of Minute.
The KPI may not be accurate under the following condition: there is no HSUPA User transferring data for a while during the total
measurement period. Therefore, the KPI should be evaluated during busy hour for accuracy.

1.1.7.7 PS UL Throughput of RNC

Table 1 PS UL Throughput of RNC


Name PS UL Throughput of RNC

Description This measurement item provides the Average or Max uplink throughput for PS services within an RNC.
Measurement point for Average UL Throughput
The RNC periodically samples the uplink traffic values of the related PS services in the PS domain. At the end of the
measurement period, the RNC divides the accumulated values by the number of samples to obtain the mean uplink traffic of
all the PS services in the PS domain. The uplink traffic of all the PS services in the PS domain refers to the traffic obtained at
the RLC layer. The data does not include the RLC head data.
Measurement point for Max UL Throughput
The RNC periodically samples uplink traffic values of all the related PS services in the PS domain. At the end of the
measurement period, the RNC calculates the maximum uplink traffic of all the services in the PS domain within the RNC. The
uplink traffic of all the services in the PS domain refers to the traffic obtained at the RLC layer. The data does not include the
RLC head data.

Associated Counters VS.R99PSLoad.ULThruput.RNC


VS.R99PSLoad.MaxULThruput.RNC
VS.HSUPAPSLoad.ULThruput.RNC
VS.HSUPAPSLoad.MaxULThruput.RNC

Object RNC

Unit/Range kbps

Note None

1.1.7.8 PS DL Throughput of RNC

Table 1 PS DL Throughput of RNC


Name PS DL Throughput of RNC

Description These counters provide the Average or Max dowunlink throughput for PS services within an RNC.
Measurement point for Average DL Throughput
The RNC periodically samples the downlink traffic values of the related PS services in the PS domain. At the end of the
measurement period, the RNC divides the accumulated values by the number of samples to obtain the mean downlink traffic
of all the PS services in the PS domain. The downlink traffic of all the PS services in the PS domain refers to the traffic
obtained at the RLC layer. The data does not include the RLC head data.
Measurement point for Max DL Throughput
The RNC periodically samples the downlink traffic values of all the related PS services in the PS domain. At the end of the
measurement period, the RNC calculates the maximum downlink traffic of all the services in the PS domain within the RNC.
The downlink traffic of all the services in the PS domain refers to the traffic obtained at the RLC layer. The data does not
include the RLC head data.

Associated Counters VS.R99PSLoad.DLThruput.RNC


VS.HSDPAPSLoad.DLThruput.RNC
VS.R99PSLoad.MaxDLThruput.RNC
VS.HSDPAPSLoad.MaxDLThruput.RNC
VS.MBMSPSLoad.DLThruput.RNC
VS.MBMSPSLoad.MaxDLThruput.RNC

Object RNC

Unit/Range kbps

Note None

1.1.7.9 MBMS Service Throughput

Table 1 MBMS Service Throughput


Name MBMS Service Throughput

Description These KPIs are used to check the throughput of MBMS service in a cell.

Associated Counters VS.MBMS.PTM.MeanThroughput


VS.MBMS.PTP.MeanThroughput

Object CELL

Unit/Range kbps

Note None

1.1.8 Traffic
Traffic related KPIs are used to check the circulated traffic such as CS Equivalent Erlang,PS Traffic, and Mean UE number for various kinds of services in an RNC or a Cluster.

1.1.8.1 CS Equivalent Erlang of RNC

37 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Table 1 CS Equivalent Erlang of RNC


Name CS Equivalent Erlang of RNC

Description VS.CSLoad.Erlang.Equiv.RNC:
This KPI provides the equivalent Erlang values of all the services in the CS domain in the RNC.
The RNC periodically takes the samples from the equivalent Erlang values of all the services in the CS domain. At the end of the measurement
period, the RNC divides the accumulated equivalent Erlang values by the number of samples to obtain the mean equivalent Erlang values of all
the services in the CS domain.
Each time a CS domain service is established, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the
CS domain in the current RNC.
Each time a CS domain service is released, the RNC converts its rate to the equivalent Erlang and decreases the equivalent Erlang of the CS
domain in the current RNC.
VS.CSLoad.MaxErlang.Equiv.RNC:
This KPI provides the maximum equivalent Erlang values of all the services in the CS domain within the RNC.
The RNC periodically takes a sample from the equivalent Erlang values of all the services in the CS domain. At the end of the period, the RNC
calculates the maximum equivalent Erlang of all the services in the CS domain within the RNC.
Each time a CS domain service is established, the RNC converts its rate to the equivalent Erlang, and then increases the equivalent Erlang of the
CS domain in the current RNC.
Each time a CS domain service is released, the RNC decreases the equivalent Erlang of the CS domain in the current RNC.

Associated VS.CSLoad.Erlang.Equiv.RNC
Counters VS.CSLoad.MaxErlang.Equiv.RNC

Object RNC

Unit/Range Erl

Note None

1.1.8.2 Number of CS Users

Table 1 Number of CS Users


Name Number of CS Users

Description These counters provide the number of CS (AMR and VP) users with different UL and DL rates in cells of the active set.
The related RB number is sampled periodically in cells of the active set. At the end of the measurement period, the value of each
counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.

Associated Counters Cell Counters


(VS.RB.AMR.DL.12.2+
VS.RB.AMR.DL.10.2+
VS.RB.AMR.DL.7.95+
VS.RB.AMR.DL.7.4+
VS.RB.AMR.DL.6.7+
VS.RB.AMR.DL.5.9+
VS.RB.AMR.DL.5.15+
VS.RB.AMR.DL.4.75) ;
VS.RB.CS.Conv.DL.64
RNC Counters
(VS.RB.AMR.DL.4.75.RNC+
VS.RB.AMR.DL.5.15.RNC+
VS.RB.AMR.DL.5.9.RNC+
VS.RB.AMR.DL.6.7.RNC+
VS.RB.AMR.DL.7.4.RNC+
VS.RB.AMR.DL.7.95.RNC+
VS.RB.AMR.DL.10.2.RNC+
VS.RB.AMR.DL.12.2.RNC) ;
VS.RB.CS.Conv.DL.64.RNC

Object CELL, RNC

Unit/Range None

Note The Unit is average user number, to get Erlang, should be multiplied by {SP}/60;
For 1 VP service, 4 EquivalErlangs on V1 Platform, 2 EquivalErlangs on V2 Platform.

1.1.8.3 Number of PS R99 Users

Table 1 Number of PS R99 Users


Name Number of PS R99 Users

Description These counters provide the number of PS R99 users with different UL and DL rates in cells of the active set.
The related RB number is sampled periodically in cells of the active set. At the end of the measurement period, the value of each
counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.

Associated Counters Cell Level


UL Counters:
VS.RB.PS.Bkg.UL.8
VS.RB.PS.Bkg.UL.16
VS.RB.PS.Bkg.UL.32
VS.RB.PS.Bkg.UL.64
VS.RB.PS.Bkg.UL.128
VS.RB.PS.Bkg.UL.144

38 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.RB.PS.Bkg.UL.256
VS.RB.PS.Bkg.UL.384
VS.RB.PS.Int.UL.8
VS.RB.PS.Int.UL.16
VS.RB.PS.Int.UL.32
VS.RB.PS.Int.UL.64
VS.RB.PS.Int.UL.128
VS.RB.PS.Int.UL.144
VS.RB.PS.Int.UL.256
VS.RB.PS.Int.UL.384
VS.RB.PS.Conv.UL.42.8
VS.RB.PS.Conv.UL.40
VS.RB.PS.Conv.UL.39.2
VS.RB.PS.Conv.UL.38.8
VS.RB.PS.Str.UL.8
VS.RB.PS.Str.UL.16
VS.RB.PS.Str.UL.32
VS.RB.PS.Str.UL.64
VS.RB.PS.Str.UL.128
VS.RB.PS.Str.UL.144
VS.RB.PS.Str.UL.256.384
VS.RB.PS.Conv.UL.64
DL Counters:
VS.RB.PS.Bkg.DL.8
VS.RB.PS.Bkg.DL.16
VS.RB.PS.Bkg.DL.32
VS.RB.PS.Bkg.DL.64
VS.RB.PS.Bkg.DL.128
VS.RB.PS.Bkg.DL.144
VS.RB.PS.Bkg.DL.256
VS.RB.PS.Bkg.DL.384
VS.RB.PS.Int.DL.8
VS.RB.PS.Int.DL.16
VS.RB.PS.Int.DL.32
VS.RB.PS.Int.DL.64
VS.RB.PS.Int.DL.128
VS.RB.PS.Int.DL.144
VS.RB.PS.Int.DL.256
VS.RB.PS.Int.DL.384
VS.RB.PS.Conv.DL.42.8
VS.RB.PS.Conv.DL.40
VS.RB.PS.Conv.DL.39.2
VS.RB.PS.Conv.DL.38.8
VS.RB.PS.Str.DL.8
VS.RB.PS.Str.DL.16
VS.RB.PS.Str.DL.32
VS.RB.PS.Str.DL.64
VS.RB.PS.Str.DL.128
VS.RB.PS.Str.DL.144
VS.RB.PS.Str.DL.256.384
VS.RB.PS.Conv.DL.64
RNC Counters
UL Counters:
VS.RB.PS.Bkg.UL.8.RNC
VS.RB.PS.Bkg.UL.16.RNC
VS.RB.PS.Bkg.UL.32.RNC
VS.RB.PS.Bkg.UL.64.RNC
VS.RB.PS.Bkg.UL.128.RNC
VS.RB.PS.Bkg.UL.144.RNC
VS.RB.PS.Bkg.UL.256.RNC
VS.RB.PS.Bkg.UL.384.RNC
VS.RB.PS.Int.UL.8.RNC
VS.RB.PS.Int.UL.16.RNC
VS.RB.PS.Int.UL.32.RNC
VS.RB.PS.Int.UL.64.RNC
VS.RB.PS.Int.UL.128.RNC
VS.RB.PS.Int.UL.144.RNC
VS.RB.PS.Int.UL.256.RNC
VS.RB.PS.Int.UL.384.RNC
VS.RB.PS.Str.UL.8.RNC
VS.RB.PS.Str.UL.16.RNC
VS.RB.PS.Str.UL.32.RNC
VS.RB.PS.Str.UL.64.RNC
VS.RB.PS.Str.UL.128.RNC
VS.RB.PS.Str.UL.144.RNC
VS.RB.PS.Str.UL.256.384.RNC
VS.RB.PS.Conv.UL.8.RNC
VS.RB.PS.Conv.UL.16.RNC

39 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.RB.PS.Conv.UL.32.RNC
VS.RB.PS.Conv.UL.64.RNC
VS.RB.PS.Conv.UL.38.8.RNC
VS.RB.PS.Conv.UL.42.8.RNC
VS.RB.PS.Conv.UL.40.RNC
VS.RB.PS.Conv.UL.39.2.RNC
DL Counters:
VS.RB.PS.Bkg.DL.8.RNC
VS.RB.PS.Bkg.DL.16.RNC
VS.RB.PS.Bkg.DL.32.RNC
VS.RB.PS.Bkg.DL.64.RNC
VS.RB.PS.Bkg.DL.128.RNC
VS.RB.PS.Bkg.DL.144.RNC
VS.RB.PS.Bkg.DL.256.RNC
VS.RB.PS.Bkg.DL.384.RNC
VS.RB.PS.Int.DL.8.RNC
VS.RB.PS.Int.DL.16.RNC
VS.RB.PS.Int.DL.32.RNC
VS.RB.PS.Int.DL.64.RNC
VS.RB.PS.Int.DL.128.RNC
VS.RB.PS.Int.DL.144.RNC
VS.RB.PS.Int.DL.256.RNC
VS.RB.PS.Int.DL.384.RNC
VS.RB.PS.Str.DL.8.RNC
VS.RB.PS.Str.DL.16.RNC
VS.RB.PS.Str.DL.32.RNC
VS.RB.PS.Str.DL.64.RNC
VS.RB.PS.Str.DL.128.RNC
VS.RB.PS.Str.DL.144.RNC
VS.RB.PS.Str.DL.256.384.RNC
VS.RB.PS.Conv.DL.8.RNC
VS.RB.PS.Conv.DL.16.RNC
VS.RB.PS.Conv.DL.32.RNC
VS.RB.PS.Conv.DL.64.RNC
VS.RB.PS.Conv.DL.42.8.RNC
VS.RB.PS.Conv.DL.40.RNC
VS.RB.PS.Conv.DL.39.2.RNC
VS.RB.PS.Conv.DL.38.8.RNC

Object CELL, RNC

Unit/Range None

Note The Unit is average user number, to get Erlang, should be multiplied by {SP}/60;

1.1.8.4 Number of HSDPA Users

Table 1 Number of HSDPA Users


Name Number of HSDPA Users

Description This KPI provides the mean, maximum and minimum number of HSDPA UEs in an HSDPA serving cell.
The RNC periodically samples the number of HSDPA UEs in the HSDPA serving cell. At the end of the measurement period, the RNC
obtains the mean and maximum number of HSDPA UEs.

Associated Counters VS.HSDPA.UE.Mean.Cell


VS.HSDPA.UE.Max.Cell

Object CELL

Unit/Range None

Note None

1.1.8.5 Number of HSUPA Users

Table 1 Number of HSUPA Users


Name Number of HSUPA Users

Description These KPIs provide the mean and maximum number of HSUPA UEs in an HSUPA serving cell.
The RNC periodically samples the number of HSUPA UEs in the HSUPA serving cell. At the end of the measurement period, the RNC
obtains the mean and maximum number of HSUPA UEs.

Associated Counters VS.HSUPA.UE.Mean.Cell


VS.HSUPA.UE.Max.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.6 Number of E-FACH Users

40 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Table 1 Number of E-FACH Users


Name Mean Number of E-FACH Users

Description This KPI provides the average number of UEs carried on the E-FACH in the cell
The system periodically samples the UEs carried on the EFACH. At the end of the measurement period, the average number of UEs
carried on the E-FACH in the measurement period is obtained by dividing the accumulated value of sample data in the period by the
number of samples.

Associated Counters VS.EFACHUEs

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.7 Number of CS Over HSPA Users

Table 1 Number of CS Over HSPA Users


Name Mean Number of CS Over HSPA Users

Description This KPI provides the average number of CS over HSPA users in the cell.
The system periodically samples the number of CS Over HSPA. At the end of a statistical period, the system divides the sampling
number by the sum at each sampling point to obtain the average number of CS Over HSPA during the period.

Associated Counters VS.HSPA.UE.Mean.CS.Conv.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.8 Number of HSDPA 64QAM Users

Table 1 Number of HSDPA 64QAM Users


Name Mean Number of HSDPA 64QAM Users

Description This KPI provides the average number of HSDPA 64QAM UEs in an HSDPA cell.
The number of HSDPA 64QAM UEs is sampled periodically in the HSDPA cells. At the end of the measurement period, the RNC
divides the accumulated time weight value of each sampling point by the sampling period, thus obtaining the average number of
64QAM UEs in the HSDPA cell.

Associated Counters VS.HSDPA.64QAM.UE.Mean.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.9 Number of HSDPA MIMO Users

Table 1 Number of HSDPA MIMO Users


Name Mean Number of HSDPA MIMO Users

Description This KPI provides the average number of HSDPA MIMO UEs in an HSDPA cell.
The number of HSDPA MIMO UEs is sampled periodically in the HSDPA cells. At the end of the measurement period, the RNC divides
the accumulated time weight value of each sampling point by the sampling period, thus obtaining the average number of MIMO UEs in
the HSDPA cell.

Associated Counters VS.HSDPA.MIMO.UE.Mean.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.10 Number of HSUPA 16QAM users

Table 1 Number of HSUPA 16QAM users


Name Mean Number of HSUPA 16QAM users

Description This KPI provides the average number of HSDPA 16QAM UEs in an HSDPA cell.
The number of HSDPA 16QAM UEs is sampled periodically in the HSDPA cells. At the end of the measurement period, the RNC
divides the accumulated time weight value of each sampling point by the sampling period, thus obtaining the average number of
16QAM UEs in the HSDPA cell.

Associated Counters VS.HSUPA.16QAM.UE.Mean.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.11 Number of HSDPA MIMO64QAM Users

41 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Table 1 Number of HSDPA MIMO64QAM Users


Name Mean Number of HSDPA MIMO64QAM Users

Description This KPI provides the average number of HSDPA MIMO64QAM UEs in an HSDPA cell.
The system periodically samples the number of MIMO+64QAM UEs. At the end of the measurement period, by dividing the
accumulated value of sample data in the period by the number of samples, the average number of MIMO+64QAM UEs in the
measurement period is obtained.

Associated Counters VS.HSDPA.MIMO64QAM.UE.Mean.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.12 Number of MBMS Users

Table 1 Number of MBMS Users


Name Mean Number of MBMS Users

Description The previous measurement counter provides the mean number of UEs that subscribes to MBMS channel in PTP mode in a cell.
If the MBMS channel is in PTP mode, the number of cell_MBMS UEs is reported when a connected UE orders or releases the program
in the cell. When the MBMS channel switches from PTM to PTP, the number of UEs that have currently ordered the program in the cell
is reported. When the MBMS channel switches from PTP to PTM, the number of UEs that have ordered the program in PTP mode is
reported as 0.

Associated Counters VS.MBMS.PTP.UE.Channel0.Mean.Cell


VS.MBMS.PTM.UE.Channel0.Mean.Cell
VS.MBMS.PTP.UE.Channel1.Mean.Cell
VS.MBMS.PTM.UE.Channel1.Mean.Cell
VS.MBMS.PTP.UE.Channel2.Mean.Cell
VS.MBMS.PTM.UE.Channel2.Mean.Cell
VS.MBMS.PTP.UE.Channel3.Mean.Cell
VS.MBMS.PTM.UE.Channel3.Mean.Cell
VS.MBMS.PTP.UE.Channel4.Mean.Cell
VS.MBMS.PTM.UE.Channel4.Mean.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

1.1.8.13 HSDPA RLC Traffic Volume

Table 1 HSDPA RLC Traffic Volume


Name HSDPA RLC Traffic Volume

Description This KPI provides the total downlink bytes of all the HSDPA MAC-d flows in a cell.
When the data is transmitted to an HSDPA serving cell, the RNC measures the number of total bytes sent in the downlink (including
data of all types of services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.

Associated Counters VS.HSDPA.MeanChThroughput.TotalBytes

Object CELL

Unit/Range byte

Note None

1.1.8.14 HSUPA RLC Traffic Volume

Table 1 HSUPA RLC Traffic Volume


Name HSUPA RLC Traffic Volume

Description This counter provides the total uplink bytes of all the HSUPA MAC-d flows in a cell.
When data is received in HSUPA active cells, the RNC measures the number of total bytes received in the uplink (including data of
different services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.

Associated Counters VS.HSUPA.MeanChThroughput.TotalBytes

Object CELL

Unit/Range byte

Note None

1.1.8.15 R99 Service UL Traffic Volume

Table 1 R99 Service UL Traffic Volume


Name R99 Service UL Traffic Volume

Description These KPIs provide the uplink traffic volume of different R99 services in all cells of the active set.
The UL traffic volume (excluding the RLC header and the retransmitted data) of each kind of R99 services over the RLC layer are
accumulated for all cells of the active set within SRNC.

42 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

Associated Counters CS Domain:


(VS.RB.AMR.UL.12.2*12200+
VS.RB.AMR.UL.10.2*10200+
VS.RB.AMR.UL.7.95*7950+
VS.RB.AMR.UL.7.4*7400+
VS.RB.AMR.UL.5.9*5900+
VS.RB.AMR.UL.5.15*5150+
VS.RB.AMR.UL.4.75*4750)*{SP}*60
PS Domain:
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

Object CELL

Unit/Range bit

Note None

1.1.8.16 R99 Service DL Traffic Volume

Table 1 R99 Service DL Traffic Volume


Name R99 Service DL Traffic Volume

Description These KPIs provide the downlink traffic volume of different R99 services in all cells of the active set.
The DL traffic volume (excluding the RLC header and the retransmitted data) of each kind of R99 services over the RLC layer are
accumulated for all cells of the active set within SRNC.

Associated Counters CS Domain:


(VS.RB.AMR.DL.12.2*12200+
VS.RB.AMR.DL.10.2*10200+
VS.RB.AMR.DL.7.95*7950+
VS.RB.AMR.DL.7.4*7400+
VS.RB.AMR.DL.5.9*5900+
VS.RB.AMR.DL.5.15*5150+
VS.RB.AMR.DL.4.75*4750)*{SP}*60
VS.CS.Conv.DL.64.Traffic
VS.CS.Str.DL.57.6.Traffic
PS Domain:
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

43 of 44 31/07/2015 15:00
HEEX Startpage http://localhost:7890/printtopics.html?time=Fri Jul 31 2015 15:00:16...

VS.PS.Str.DL.144.Traffic
VS.PS.Str.DL.256.Traffic
VS.PS.Str.DL.384.Traffic
VS.PS.Conv.DL.Traffic

Object CELL

Unit/Range bit

Note None

1.1.8.17 E-FACH Traffic Volume

Table 1 E-FACH Traffic Volume


Name E-FACH Traffic Volume

Description This KPI provides the number of downlink MAC PDU bytes sent by the CRNC on the E-FACH over the Iub interface in a cell.
The measurement is triggered when the CRNC sends downlink data on the E-FACH over the Iub interface.

Associated Counters VS.CRNCIubBytesEFACH.Tx

Object CELL

Unit/Range byte

Note None

44 of 44 31/07/2015 15:00