ran14.0 kpi reference(02)(pdf)-en

RAN14.0

KPI Reference

Issue 02

Date 2012-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 02 (2012-06-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

PurposeThis 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 networkoptimization. However, the KPI description is updated from time to time based on therequirements of customers.

Product VersionsThe following table lists the product versions included in this document.

Product Name Product Version

BSC6900 V900R014C00

NodeB V100R014

NodeB V200R014

Intended AudienceThis document is intended for:

l Network planning engineersl Field engineersl System engineers

Organization1 Changes in the RAN KPI Reference

This chapter describes the changes made in the RAN KPI Reference.

2 Accessibility

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

RAN14.0KPI Reference About This Document


ii

3 Availability

Availability KPIs mainly indicate the utilization for several kinds of network resources such asRadio, bandwidth or CPU Load.

4 Coverage

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

5 Mobility

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

6 Retainability

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

7 Service Integrity

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

8 Traffic

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

ConventionsSymbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or savetime.

Provides additional information to emphasize or supplementimportant points of the main text.



iii

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder.



iv

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enter and press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A meansthe two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

Action Description

Click Select and release the primary mouse button without movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move thepointer to a certain position.



v

Contents

About This Document.....................................................................................................................ii

1 Changes in the RAN KPI Reference..........................................................................................1

2 Accessibility....................................................................................................................................42.1 IU Paging Success Ratio.....................................................................................................................................62.2 RRC Setup Success Ratio...................................................................................................................................62.3 Radio Access Success Ratio...............................................................................................................................92.4 PS Radio Access Success Ratio........................................................................................................................112.5 CS Radio Access Success Ratio.......................................................................................................................122.6 AMR RAB Setup Success Ratio......................................................................................................................132.7 VP RAB Setup Success Ratio..........................................................................................................................142.8 CS RAB Setup Success Ratio...........................................................................................................................152.9 CS+PS Combined Service RAB Setup Success Rate.......................................................................................162.10 PS+PS Combined Service RAB Setup Success Rate.....................................................................................162.11 PS RAB Setup Success Ratio.........................................................................................................................172.12 HSDPA RAB Setup Success Ratio................................................................................................................182.13 HSUPA RAB Setup Success Ratio................................................................................................................192.14 PS E-FACH RAB Setup Success Ratio..........................................................................................................202.15 CS over HSPA RAB Setup Success Ratio.....................................................................................................202.16 HSDPA 64QAM RAB Setup Success Ratio..................................................................................................212.17 HSDPA MIMO RAB Setup Success Ratio....................................................................................................222.18 HSDPA DC RAB Setup Success Ratio..........................................................................................................222.19 HSDPA MIMO64QAM RAB Setup Success Ratio.......................................................................................232.20 PTM Channel Setup Success Ratio................................................................................................................242.21 PTP Channel Setup Success Ratio..................................................................................................................242.22 RRC Congestion Ratio...................................................................................................................................252.23 CS RAB Congestion Ratio.............................................................................................................................262.24 PS RAB Congestion Ratio..............................................................................................................................272.25 PS R99 RAB Setup Success Rate...................................................................................................................282.26 WB AMR RAB Setup Success Rate..............................................................................................................28

3 Availability...................................................................................................................................303.1 Worst Cell Ratio...............................................................................................................................................323.2 Paging Congestion Ratio..................................................................................................................................32

RAN14.0KPI Reference Contents


vi

3.3 Call Admission Refused Ratio.........................................................................................................................333.4 Congested Cell Ratio........................................................................................................................................343.5 Radio Network Unavailability Ratio................................................................................................................353.6 Average CPU Load...........................................................................................................................................353.7 IUB Port Available Bandwidth Utilizing Ratio (UL).......................................................................................363.8 IUB Port Available Bandwidth Utilizing Ratio (DL).......................................................................................373.9 Cell Unavailability duration.............................................................................................................................383.10 HSDPA Unavailability duration.....................................................................................................................393.11 HSUPA Unavailability duration.....................................................................................................................393.12 CE Consumption for a NodeB Cell................................................................................................................393.13 Hardware Configured CE for a NodeB..........................................................................................................403.14 Shared Group Configured License CE for a NodeB......................................................................................403.15 Shared Group License CE Consumption for a NodeB...................................................................................413.16 License Group Configured CE for a NodeB..................................................................................................413.17 License Group CE Consumption for a NodeB...............................................................................................423.18 RTWP (Received Total Wideband Power).....................................................................................................423.19 TCP (Transmitted Carrier Power)..................................................................................................................433.20 R99 Code Utilization......................................................................................................................................443.21 Number of Codes Used by HS-PDSCHs........................................................................................................443.22 HSDPA Efficiency.........................................................................................................................................45

4 Coverage........................................................................................................................................464.1 UL Interference Cell Ratio...............................................................................................................................474.2 Soft Handover Overhead..................................................................................................................................47

5 Mobility.........................................................................................................................................505.1 Soft Handover Success Ratio...........................................................................................................................525.2 Softer Handover Success Ratio........................................................................................................................525.3 AMR Soft Handover Success Ratio.................................................................................................................535.4 CS64 Soft Handover Success Ratio..................................................................................................................545.5 PS Soft Handover Success Ratio......................................................................................................................545.6 Intra-frequency Hard Handover Success Ratio................................................................................................555.7 Inter-frequency Hard Handover Success Ratio................................................................................................565.8 Service Cell Change Success Ratio with SHO (H2H).....................................................................................565.9 H2H Intra-Frequency Hard Handover Success Ratio.......................................................................................575.10 H2H Inter-Frequency Hard Handover Success Ratio.....................................................................................585.11 H2D Inter-frequency Hard Handover Success Ratio......................................................................................595.12 H2D Intra-Frequency Hard Handover Success Ratio.....................................................................................605.13 E2D Intra-Frequency Hard Handover Success Ratio.....................................................................................615.14 H2D Channel Switch Success Ratio...............................................................................................................625.15 D2H Channel Switch Success Ratio...............................................................................................................635.16 CS W2G Inter-RAT Handover Out Success Ratio.........................................................................................635.17 PS W2G Inter-RAT Handover Out Success Ratio.........................................................................................645.18 PS G2W Inter-RAT Handover In Success Ratio............................................................................................65



vii

5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio................................................................................665.20 SRNC Relocation Success Ratio....................................................................................................................665.21 TRNC Relocation Success Ratio....................................................................................................................675.22 E-DCH Soft Handover Success Ratio............................................................................................................685.23 E-DCH Cell Change Success Ratio with SHO...............................................................................................695.24 E-DCH Cell Change Success Ratio with Inter-HHO.....................................................................................705.25 E2D Channel Switch Success Ratio...............................................................................................................715.26 D2E Channel Switch Success Ratio...............................................................................................................725.27 E2D Handover Success Ratio with Inter HHO..............................................................................................735.28 HSUPA W2G Inter-RAT Handover Out Success Ratio................................................................................735.29 MBMS Service Mode Switch Success Ratio.................................................................................................745.30 CS Inter-Frequency Hard Handover Success Rate.........................................................................................755.31 PS Inter-Frequency Hard Handover Success Rate.........................................................................................76

6 Retainability.................................................................................................................................776.1 CS Service Drop Ratio.....................................................................................................................................786.2 CS Call Drop Rate in CS+PS Combined Services...........................................................................................786.3 PS Call Drop Rate in CS+PS Combined Services............................................................................................796.4 AMR Call Drop Ratio.......................................................................................................................................806.5 WB AMR Call Drop Rate................................................................................................................................806.6 VP Call Drop Ratio...........................................................................................................................................816.7 AMR Traffic Drop Ratio..................................................................................................................................826.8 VP Traffic Drop Ratio......................................................................................................................................846.9 PS Call Drop Ratio...........................................................................................................................................846.10 PS Call Drop Ratio (PCH)..............................................................................................................................856.11 PS R99 Call Drop Ratio..................................................................................................................................866.12 PS R99 Call Drop Ratio (PCH)......................................................................................................................886.13 PS BE Call Drop Ratio...................................................................................................................................886.14 HSDPA Call Drop Ratio.................................................................................................................................896.15 HSDPA Call Drop Ratio (PCH).....................................................................................................................906.16 HSUPA Call Drop Ratio.................................................................................................................................916.17 HSUPA Call Drop Ratio (PCH).....................................................................................................................936.18 MBMS Service PTP drop Ratio.....................................................................................................................94

7 Service Integrity...........................................................................................................................957.1 Average UL Throughput for PS R99 Service...................................................................................................967.2 Average DL Throughput for PS R99 Service...................................................................................................977.3 Average UL BLER for CS Service...................................................................................................................987.4 Average UL BLER for PS Service...................................................................................................................987.5 HSDPA Throughput.........................................................................................................................................997.6 HSUPA Throughput.......................................................................................................................................1007.7 PS UL Throughput of RNC............................................................................................................................1017.8 PS DL Throughput of RNC............................................................................................................................1027.9 MBMS Service Throughput...........................................................................................................................103



viii

8 Traffic...........................................................................................................................................1048.1 CS Equivalent Erlang of RNC........................................................................................................................1058.2 Number of CS Users.......................................................................................................................................1058.3 Number of PS R99 Users................................................................................................................................1068.4 Number of HSDPA Users...............................................................................................................................1118.5 Number of HSUPA Users...............................................................................................................................1118.6 Number of E-FACH Users.............................................................................................................................1128.7 Number of CS Over HSPA Users...................................................................................................................1128.8 Number of HSDPA 64QAM Users................................................................................................................1138.9 Number of HSDPA MIMO Users..................................................................................................................1138.10 Number of HSUPA 16QAM users...............................................................................................................1148.11 Number of HSDPA MIMO64QAM Users...................................................................................................1148.12 Number of MBMS Users..............................................................................................................................1148.13 HSDPA RLC Traffic Volume......................................................................................................................1158.14 HSUPA RLC Traffic Volume......................................................................................................................1168.15 R99 Service UL Traffic Volume..................................................................................................................1168.16 R99 Service DL Traffic Volume..................................................................................................................1178.17 E-FACH Traffic Volume..............................................................................................................................120



ix

1 Changes in the RAN KPI Reference

This chapter describes the changes made in the RAN KPI Reference.

02 (2012-06-30)

This is the second commercial release of RAN14.0.

Compared with issue 01 (2012-04-26), this issue does not include any new topics.

Compared with issue 01 (2012-04-26), this issue incorporates the following changes:

Content Description

3.8 IUB Port Available BandwidthUtilizing Ratio (DL)3.7 IUB Port Available BandwidthUtilizing Ratio (UL)

The name of the KPI is modified from IUBBandwidth Utilizing Ratio to IUB Port AvailableBandwidth Utilizing Ratio.

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

01 (2012-04-26)

This is the first commercial release of RAN14.0.

Compared with issue Draft A (2012-02-15), this issue does not include any new topics.

Compared with issue Draft A (2012-02-15), this issue does not incorporate any changes.

Compared with issue Draft A (2012-02-15), this issue does not exclude any topics.

Draft A (2012-02-15)

This is the Draft A release of RAN14.0.

Compared with issue 02 (2011-08-31) of RAN13.0, this issue includes the following new topics:l 5.30 CS Inter-Frequency Hard Handover Success Ratel 5.31 PS Inter-Frequency Hard Handover Success Rate

RAN14.0KPI Reference 1 Changes in the RAN KPI Reference


1

l 2.25 PS R99 RAB Setup Success Ratel 2.26 WB AMR RAB Setup Success Ratel 6.5 WB AMR Call Drop Ratel 5.12 H2D Intra-Frequency Hard Handover Success Ratiol 5.13 E2D Intra-Frequency Hard Handover Success Ratiol 3.21 Number of Codes Used by HS-PDSCHsl 3.22 HSDPA Efficiencyl 2.9 CS+PS Combined Service RAB Setup Success Ratel 2.10 PS+PS Combined Service RAB Setup Success Ratel 6.2 CS Call Drop Rate in CS+PS Combined Servicesl 6.3 PS Call Drop Rate in CS+PS Combined Services

Compared with issue 02 (2011-08-31) of RAN13.0, this issue incorporates the followingchanges:

Content Description

5.21 TRNC Relocation SuccessRatio

The Associated Counters of this KPI is modified.If the proportion of combined services is high in thetraffic module, the KPI value calculated by using theoriginal formula is smaller than the actual value. InRAN14.0, the following counters related to CS andPS TRNC relocation success rate are added and theformula is modified accordingly:l VS.TRELOC.SuccExecUEInvolCSl VS.TRELOC.SuccExecUEInvolPSl VS.TRELOC.SuccExecUENotInvolCSl VS.TRELOC.SuccExecUENotInvolPS

6.11 PS R99 Call Drop Ratio The Associated Counters of this KPI is modified.The RNC-level formula is added.

2.8 CS RAB Setup Success Ratio The content that the formula for calculating this KPImust be modified in inter-DRD scenarios is addedto Note.

2.6 AMR RAB Setup Success Ratio The content that the formula for calculating this KPImust be modified in inter-DRD scenarios is addedto Note.

2.2 RRC Setup Success Ratio The following content is added to Note:The number of RRC connection setup requests thatare resent after the first RRC connection setuprequest of the UE is rejected due to resourceinsufficiency can be subtracted from thedenominator of the formula to increase the value ofthis KPI.



2

Content Description

6.1 CS Service Drop Ratio The following content is added to Note:CS call drops due to authentication failure during PSsecurity mode in the cell can be subtracted from thenumerator of the formula to decrease the value ofthis KPI.

6.9 PS Call Drop Ratio The following content is added to Note:PS call drops due to authentication failure during CSsecurity mode in the cell can be subtracted from thenumerator of the formula to decrease the value ofthis KPI.

2.24 PS RAB Congestion Ratio Two counters related to the number of PS RAB setupfailures due to the reach of the maximum allowednumber of HSDPA/HSUPA users are added to theformula for calculating this KPI.l VS.RAB.FailEstabPS.HSDPAUser.Congl VS.RAB.FailEstabPS.HSUPAUser.Cong

3.8 IUB Port Available BandwidthUtilizing Ratio (DL)3.7 IUB Port Available BandwidthUtilizing Ratio (UL)

Added the scenario where the value of this KPI isincorrect to Note.

Compared with issue 02 (2011-08-31) of RAN13.0, this issue does not exclude any topics.



3

2 Accessibility

About This Chapter

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

2.1 IU Paging Success Ratio

2.2 RRC Setup Success Ratio

2.3 Radio Access Success Ratio

2.4 PS Radio Access Success Ratio

2.5 CS Radio Access Success Ratio

2.6 AMR RAB Setup Success Ratio

2.7 VP RAB Setup Success Ratio

2.8 CS RAB Setup Success Ratio

2.9 CS+PS Combined Service RAB Setup Success Rate

2.10 PS+PS Combined Service RAB Setup Success Rate

2.11 PS RAB Setup Success Ratio

2.12 HSDPA RAB Setup Success Ratio

2.13 HSUPA RAB Setup Success Ratio

2.14 PS E-FACH RAB Setup Success Ratio

2.15 CS over HSPA RAB Setup Success Ratio

2.16 HSDPA 64QAM RAB Setup Success Ratio

2.17 HSDPA MIMO RAB Setup Success Ratio

2.18 HSDPA DC RAB Setup Success Ratio

2.19 HSDPA MIMO64QAM RAB Setup Success Ratio

RAN14.0KPI Reference 2 Accessibility


4

2.20 PTM Channel Setup Success Ratio

2.21 PTP Channel Setup Success Ratio

2.22 RRC Congestion Ratio

2.23 CS RAB Congestion Ratio

2.24 PS RAB Congestion Ratio

2.25 PS R99 RAB Setup Success Rate

2.26 WB AMR RAB Setup Success Rate



5

2.1 IU Paging Success Ratio

Table 2-1 IU Paging Success Ratio

Name IU Paging Success Ratio

Formula

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

AssociatedCounters

IU Paging Success Ratio =(VS.RANAP.Paging.Succ.IdleUE/VS.RANAP.Paging.Att.IdleUE) x100%

Object RNC

Unit/Range %

Note None

2.2 RRC Setup Success Ratio

Table 2-2 RRC Setup Success Ratio

Name RRC Setup Success Ratio

Formula



6

Description Description of RRC Setup Success Ratio for service requests:l 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 servicetypes requested by the UE: Conversational Call, Streaming Call,Background Call, Interactive Call, Originating Subscribed Traffic Call,Emergency Call, High Priority Signaling, Low Priority Signaling, CauseUnknown, Call Re-Establishment. For details on the reason types, seesection 10.3.3.11 in 3GPP TS 25.331.

l The RRC Setup Success for Service Procedure is complete when the RNCreceives an RRC CONNECTION SETUP COMPLETE message from theUE.

Description of RRC Setup Success Ratio for other causes:l RRC Connection Attempt for Other reasons Procedure is complete when

the RNC receives an RRC CONNECTION REQUEST message from theUE. The message contains information about one of the following servicetypes requested by the UE: Inter-RAT cell re-selection, Inter-RAT cellchange order, Registration and Detach.

l The RRC Setup Success for Other reasons Procedure is complete whenthe RNC receives an RRC CONNECTION SETUP COMPLETE messagefrom the UE.



7

AssociatedCounters

l 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 +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 )] x 100%

l RRC Setup Success Ratio (Cell.Other) =[(RRC.SuccConnEstab.IRATCelRes+RRC.SuccConnEstab.IRATCCO +RRC.SuccConnEstab.Reg +RRC.SuccConnEstab.Detach )/(RRC.AttConnEstab.IRATCelRes+RRC.AttConnEstab.IRATCCO +



8

RRC.AttConnEstab.Reg +RRC.AttConnEstab.Detach )] x 100%

Object CELL

Unit/Range %

Note The RNC level KPI is calculated by aggregating all the cell counters.The following counters provide the number of RRC connection setup requeststhat are resent after the first RRC connection setup request of the UE isrejected due to resource insufficiency. You can subtract these counters fromthe denominator of the formula to increase the value of this KPI:l RRC.AttConnEstab.Rep.OrgConvCalll RRC.AttConnEstab.Rep.OrgStrCalll RRC.AttConnEstab.Rep.OrgInterCalll RRC.AttConnEstab.Rep.OrgBkgCalll RRC.AttConnEstab.Rep.TmConvCalll RRC.AttConnEstab.Rep.TmStrCalll RRC.AttConnEstab.Rep.TmInterCalll RRC.AttConnEstab.Rep.TmBkgCalll RRC.AttConnEstab.Rep.OrgSubCalll RRC.AttConnEstab.Rep.EmgCalll RRC.AttConnEstab.Rep.IRATCelResl RRC.AttConnEstab.Rep.IRATCCOl RRC.AttConnEstab.Rep.Regl RRC.AttConnEstab.Rep.Detachl RRC.AttConnEstab.Rep.OrgHhPrSigl RRC.AttConnEstab.Rep.OrgLwPrSigl RRC.AttConnEstab.Rep.CallReEstl RRC.AttConnEstab.Rep.TmHhPrSigl RRC.AttConnEstab.Rep.TmLwPrSigl RRC.AttConnEstab.Rep.Unknown

2.3 Radio Access Success Ratio

Table 2-3 Radio Access Success Ratio

Name Radio Access Success Ratio

Formula



9

Description This KPI is used to check the Radio Access Success Ratio. The details of theAccess Failures caused by the SCCP congestion are not provided in this callsetup procedure.Description of the RAB Setup Attempt Procedure and the RAB Setup SuccessProcedure:The RAB Setup Attempt Procedure starts when the CN sends an RABASSIGNMENT REQUEST message to the RNC. The message containsinformation about one of the following service types: CS ConversationalRAB Establishments, CS Streaming RAB Establishments, PS ConversationalRAB Establishment, PS Background RAB Establishments, PS InteractiveRAB Establishments, PS Streaming RAB Establishments. The RAB SetupAttempt Procedure is complete When the RNC receives an RABASSIGNMENT REQUEST message from the CN.The RAB Setup Success Procedure is complete when the RNC sends to theCN an RAB ASSIGNMENT RESPONSE message.



10

AssociatedCounters

l Radio Access Success Ratio (Cell) =2.2 RRC Setup Success Ratio*{[(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 )]} x 100%

l Radio Access Success Ratio (RNC) =2.2 RRC Setup Success Ratio*{[(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 )+(VS.RAB.AttEstabPS.Conv.RNC+VS.RAB.AttEstabPS.Str.RNC +VS.RAB.AttEstabPS.Int.RNC +VS.RAB.AttEstabPS.Bkg.RNC )]} x 100%

Object CELL, RNC

Unit/Range %

Note None

2.4 PS Radio Access Success Ratio

Table 2-4 PS Radio Access Success Ratio

Name PS Radio Access Success Ratio



11

Formula

Description This KPI is used to check the PS Radio Access Success Ratio. The details ofthe Access Failures caused by the SCCP congestion are not provided in thiscall setup procedure.The PS RRC Setup Attempt Procedure is complete when the RNC receivesan RRC CONNECTION REQUEST message from the UE. The messagecontains information about one of the following service types: OriginatingInteractive Call, Terminating Interactive Call, Originating Background Call,Terminating Background Call.The PS RRC Setup Success Procedure is complete when the RNC receivesan RRC CONNECTION SETUP COMPLETE message from the UE.

AssociatedCounters

l 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 )]*2.11 PS RAB Setup Success Ratio x 100%

l 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 )]*2.11 PS RAB Setup Success Ratio x 100%

Object CELL, RNC

Unit/Range %

Note None

2.5 CS Radio Access Success Ratio



12

Table 2-5 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 theAccess Failures caused by the SCCP congestion are not provided in this callsetup procedure.The CS RRC Setup Attempt Procedure is complete when the RNC receivesan RRC CONNECTION REQUEST message from the UE.The messagecontains information about one of the following service types: OriginatingConversational Call, Terminating Conversational Call, Emergency Call.The CS RRC Setup Success Procedure is complete when the RNC receivesan RRC CONNECTION SETUP COMPLETE message from the UE.

AssociatedCounters

l CS Radio Access Success Ratio (Cell) =[(RRC.SuccConnEstab.OrgConvCall+RRC.SuccConnEstab.TmConvCall +RRC.SuccConnEstab.EmgCall )/(RRC.AttConnEstab.OrgConvCall+RRC.AttConnEstab.TmConvCall +RRC.AttConnEstab.EmgCall )]*2.8 CS RAB Setup Success Ratio x 100%

l CS Radio Access Success Ratio (RNC) =[(RRC.SuccConnEstab.OrgConvCall+RRC.SuccConnEstab.TmConvCall +RRC.SuccConnEstab.EmgCall )/(RRC.AttConnEstab.OrgConvCall+RRC.AttConnEstab.TmConvCall +RRC.AttConnEstab.EmgCall )]*2.8 CS RAB Setup Success Ratio x 100%

Object CELL,RNC

Unit/Range %

Note None

2.6 AMR RAB Setup Success Ratio

Table 2-6 AMR RAB Setup Success Ratio

Name AMR RAB Setup Success Ratio



13

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 anRAB ASSIGNMENT REQUEST message from the CN for the CS narrowband AMR services.The AMR RAB Setup Success Procedure starts when the UE sends a RADIOBEARER SETUP COMPLETE message to the RNC. This procedure iscomplete when the RNC sends an RAB ASSIGNMENT RESPONSEmessage to the CN in the CS domain.

AssociatedCounters

AMR RAB Setup Success Ratio(Cell) =(VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR) x 100%

Object CELL

Unit/Range %

Note RNC-level KPIs are obtained by accumulating values of cell-level counters.If inter-RAT DRD is enabled during RAB setup, an AMR RAB setup ismeasured as an AMR RAB setup failure regardless of whether the DRDsucceeds. As a result, the value of this KPI is smaller than actual value.Therefore, it is recommended that you add VS.IRATHO.SuccOutCS.DR tothe numerator of the formula for calculating this KPI if inter-RAT DRD isenabled during RAB setup.

2.7 VP RAB Setup Success Ratio

Table 2-7 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/sconversational services in an RNC or a cluster.VP (Video Phone) RAB Setup Attempt Procedure is complete when the RNCreceives an RAB ASSIGNMENT REQUEST message from the CN (TheRAB type is for the CS 64 Kbit/s conversational service).VP RAB Setup Success Procedure starts when the UE sends a RADIOBEARER SETUP COMPLETE message to RNC. This procedure is completewhen the RNC sends an RAB ASSIGNMENT RESPONSE message to theCN in the CS domain.



14

AssociatedCounters

VP RAB Setup Success Ratio (Cell) =(VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64) x 100%

Object CELL

Unit/Range %

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

2.8 CS RAB Setup Success Ratio

Table 2-8 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 inan RNC or a cluster.The CS RAB Setup Attempt Procedure is complete when the RNC receivesan RAB ASSIGNMENT REQUEST message from the CN in the CSdomain.The message contains information about one of the following servicetypes: Conversational Services, streaming Services.The CS RAB Setup Success Procedure starts when the RNC receives aRADIO BEARER SETUP COMPLETE message from UE. This procedureis complete when the RNC sends an RAB ASSIGNMENT RESPONSEmessage to the CN in the CS domain.

AssociatedCounters

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

l 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)]x 100%

Object CELL, RNC

Unit/Range %



15

Note If inter-RAT DRD is enabled during RAB setup, a CS RAB setup is measuredas a CS RAB setup failure regardless of whether the DRD succeeds. As aresult, the value of this KPI is smaller than actual value. Therefore, it isrecommended that you add VS.IRATHO.SuccOutCS.DR to the numeratorof the formula for calculating this KPI if inter-RAT DRD is enabled duringRAB setup.

2.9 CS+PS Combined Service RAB Setup Success Rate

Table 2-9 CS+PS Combined Service RAB Setup Success Rate

Name CS+PS Combined Service RAB Setup Success Rate

Formula CS+PS Combined Service RAB Setup Success Rate = Number ofsuccessfully set up CS+PS combined service RABs x 100%/Number of CS+PS combined service RAB setup attempts

Description This KPI provides the setup success rate of CS+PS combined services.Number of CS+PS combined service RAB setup attempts: When the RNCreceives from the CN an RAB ASSIGNMENT REQUEST message and oneor more RABs of the UE already exists in the cell, the RNC checks the RABtype carried in the message and determines the combined service type basedon the existing RAB type of the UE. The number of CS+PS combined serviceRAB setup attempts is measured in the best cell that the UE camps on if thecombined service type is CS+PS, CS+2PS, or CS+3PS.Number of successfully set up CS+PS combined service RABs: When theRNC sends an RAB ASSIGNMENT RESPONSE message to the CN afterreceiving an RADIO BEARER SETUP COMPLETE message from the UEand one or more RABs of a UE already exists in the cell, the RNC checks theRAB type and determines the combined service type based on the existingRAB type of the UE. The number of successfully set up CS+PS combinedservice RABs is measured in the best cell that the UE camps on if thecombined service type is CS+PS, CS+2PS, or CS+3PS.

AssociatedCounters

CS+PS RAB Setup Success ratio=(VS.MultiRAB.SuccEstab.CSPS/VS.MultiRAB.AttEstab.CSPS) * 100%

Object CELL

Unit/Range %

Note None

2.10 PS+PS Combined Service RAB Setup Success Rate



16

Table 2-10 PS+PS Combined Service RAB Setup Success Rate

Name PS+PS Combined Service RAB Setup Success Rate

Formula PS+PS Combined Service RAB Setup Success Rate = Number ofsuccessfully set up PS+PS combined service RABs x 100%/Number of PS+PS combined service RAB setup attempts

Description This KPI provides the setup success rate of PS+PS combined services.Number of PS+PS combined service RAB setup attempts: When the RNCreceives from the CN an RAB ASSIGNMENT REQUEST message and oneor more RABs of the UE already exists in the cell, the RNC checks the RABtype carried in the message and determines the combined service type basedon the existing RAB type of the UE. The number of PS+PS combined serviceRAB setup attempts is measured in the best cell that the UE camps on if thecombined service type is 2PS, 3PS, or 4PS.Number of successfully set up PS+PS combined service RABs: When theRNC sends an RAB ASSIGNMENT RESPONSE message to the CN afterreceiving an RADIO BEARER SETUP COMPLETE message from the UEand one or more RABs of a UE already exists in the cell, the RNC checks theRAB type and determines the combined service type based on the existingRAB type of the UE. The number of successfully set up PS+PS combinedservice RABs is measured in the best cell that the UE camps on if thecombined service type is 2PS, 3PS, or 4PS.

AssociatedCounters

PS+PS RAB Setup Success ratio=(VS.MultiRAB.SuccEstab.PSPS/VS.MultiRAB.AttEstab.PSPS)*100%

Object CELL

Unit/Range %

Note None

2.11 PS RAB Setup Success Ratio

Table 2-11 PS RAB Setup Success Ratio

Name PS RAB Setup Success Ratio

Formula



17

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

AssociatedCounters

l PS RAB Setup Success Ratio (Cell) =[(VS.RAB.SuccEstabPS.Conv+VS.RAB.SuccEstabPS.Str +VS.RAB.SuccEstabPS.Int +VS.RAB.SuccEstabPS.Bkg )/(VS.RAB.AttEstabPS.Conv+VS.RAB.AttEstabPS.Str +VS.RAB.AttEstabPS.Int +VS.RAB.AttEstabPS.Bkg )] x 100%

l 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 )] x 100%

Object CELL, RNC

Unit/Range %

Note None

2.12 HSDPA RAB Setup Success Ratio

Table 2-12 HSDPA RAB Setup Success Ratio

Name HSDPA RAB Setup Success Ratio



18

Formula

Description This KPI is used to check the RAB Setup Success Ratio of PS services thatare carried by HSDPA in a cluster.The HSDPA RAB Setup Attempt Procedure is complete when the RNCreceives an RAB ASSIGNMENT REQUEST message from the CN forsetting up the HSDPA service.The HSDPA RAB Setup Success Procedure starts when the RNC receives aRADIO BEARER SETUP COMPLETE message from the UE. Thisprocedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE message to the CN.

AssociatedCounters

HSDPA RAB Setup Success Ratio (Cell) =(VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%

Object CELL

Unit/Range %


2.13 HSUPA RAB Setup Success Ratio

Table 2-13 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 servicein an RNC or a cluster.The HSUPA RAB Setup Success Procedure starts when the RNC receives aRADIO BEARER SETUP COMPLETE message from the UE. Thisprocedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE message to the CN.The HSUPA RAB Setup Attempt Procedure is complete when the RNCreceives an RAB ASSIGNMENT REQUEST message from the CN forsetting up the HSUPA service.

AssociatedCounters

HSUPA RAB Setup Success Ratio (Cell) =(VS.HSUPA.RAB.SuccEstab/VS.HSUPA.RAB.AttEstab) x 100%

Object CELL



19

Unit/Range %


2.14 PS E-FACH RAB Setup Success Ratio

Table 2-14 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 servicein an RNC or a cluster.Successful PS RAB Setup on E-FACH Procedure starts when the RNCreceives a RADIO BEARER SETUP COMPLETE message from the UE.This procedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE message to the SGSN in the PS domain.The procedure of Attempts of PS RAB Setup on E-FACH is complete whenthe RNC receives an RAB ASSIGNMENT REQUEST message from theSGSN, and the PS service is established on the EFACH.

AssociatedCounters

PS E-FACH RAB Setup Success Ratio (Cell) =(VS.RAB.SuccEstPS.EFACH/VS.RAB.AttEstPS.EFACH) x 100%

CELL

Unit/Range %


2.15 CS over HSPA RAB Setup Success Ratio

Table 2-15 CS over HSPA RAB Setup Success Ratio

Name CS over HSPA RAB Setup Success Ratio

Formula



20

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

AssociatedCounters

CS over HSPA RAB Setup Success Ratio (Cell) =(VS.HSPA.RAB.SuccEstab.CS.Conv/VS.HSPA.RAB.AttEstab.CS.Conv) x 100%

Object CELL

Unit/Range %


2.16 HSDPA 64QAM RAB Setup Success Ratio

Table 2-16 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 HSDPA64QAM service in an RNC or a cluster.The HSDPA 64 QAM RAB Setup Success Procedure starts when the RNCreceives an RADIO BEARER SETUP COMPLETE message from the UE.This procedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE message to the CN.The HSDPA 64QAM RAB Setup Attempt Procedure is complete when theRNC receives an RAB ASSIGNMENT REQUEST message from the CN forsetting up the HSDPA service using 64QAM.

AssociatedCounters

HSDPA 64QAM RAB Setup Success Ratio (Cell) =(VS.HSDPA.RAB.64QAM.SuccEstab/VS.HSDPA.RAB.64QAM.AttEstab) x 100%

Object CELL

Unit/Range %



21


2.17 HSDPA MIMO RAB Setup Success Ratio

Table 2-17 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 MIMOservice in an RNC or a cluster.The HSDPA MIMO RAB Setup Success procedure starts when the RNCreceives a RADIO BEARER SETUP COMPLETE message from the UE.This procedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE message to the CN.The HSDPA MIMO RAB Setup Attempt procedure is complete when theRNC receives an RAB ASSIGNMENT REQUEST message from the CN forsetting up the HSDPA service using MIMO.

AssociatedCounters

HSDPA MIMO RAB Setup Success Ratio=(VS.HSDPA.RAB.MIMO.SuccEstab/VS.HSDPA.RAB.MIMO.AttEs-tab) x 100%

Object CELL

Unit/Range %


2.18 HSDPA DC RAB Setup Success Ratio

Table 2-18 HSDPA DC RAB Setup Success Ratio

Name HSDPA DC RAB Setup Success Ratio

Formula



22

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA DCRAB service in an RNC or a cluster.The HSDPA DC RAB Setup Success procedure starts when the RNC receivesa RADIO BEARER SETUP COMPLETE message from the UE. Thisprocedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE message to the CN.The HSDPA DC RAB Setup Attempt procedure is complete when the RNCreceives from the CN an RAB ASSIGNMENT REQUEST message forsetting up the HSDPA service using DC-HSDPA.

AssociatedCounters

HSDPA DC RAB Setup Success Ratio=(VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x100%

Object CELL

Unit/Range %


2.19 HSDPA MIMO64QAM RAB Setup Success Ratio

Table 2-19 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 MIMO64QAM service in an RNC or a cluster.The HSDPA MIMO 64QAM RAB Setup Success procedure starts when theRNC receives a RADIO BEARER SETUP COMPLETE message from theUE. This procedure is complete when the RNC sends an RABASSIGNMENT RESPONSE message to the CN.The HSDPA MIMO 64QAM RAB Setup Attempt procedure is completewhen the RNC receives an RAB ASSIGNMENT REQUEST message fromthe CN for setting up the HSDPA service using MIMO+64QAM.

AssociatedCounters

HSDPA MIMO64QAM RAB Setup Success Ratio=(VS.HSDPA.RAB.MIMO64QAM.SuccEstab/VS.HSDPA.RAB.MIMO64QAM.AttEstab) x 100%

Object CELL

Unit/Range %



23


2.20 PTM Channel Setup Success Ratio

Table 2-20 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 servicein PTM mode.When the RB of PTM MBMS service is successfully set up, the PTM ChannelRB is successfully set up.When the RNC initiates the setup of PTM MBMS service, the PTM ChannelRB Setup Attempt.

AssociatedCounters

PTM Channel Setup Success Ratio=(VS.MBMS.RB.PTM.SuccEstab/VS.MBMS.RB.PTM.AttEstab) x100%

Object CELL

Unit/Range %


2.21 PTP Channel Setup Success Ratio

Table 2-21 PTP Channel Setup Success Ratio

Name PTP Channel Setup Success Ratio

Formula



24

Description This KPI is used to check the Channel Setup Success Rate of MBMS servicein 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 tothe UE's request, initiates PTP RB setup, and the PTP RB is successfully setup.The PTP Channel RB Setup Attempt Procedure:The RNC initiates PTP RB setup after the UE initiates an MBMS setuprequest.

AssociatedCounters

PTP Channel Setup Success Ratio=(VS.MBMS.RB.PTP.SuccEstab/VS.MBMS.RB.PTP.AttEstab) x 100%

Object CELL

Unit/Range %


2.22 RRC Congestion Ratio

Table 2-22 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 Failuredue to Congestion procedure is complete when the RNC sends an RRCCONNECTION REJECT message to the UE.The RRC Connection Attempt for service Procedure is complete when theRNC receives an RRC CONNECTION REQUEST message from the UE.

AssociatedCounters

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 ] x 100%



25

Object CELL

Unit/Range %

Note None

2.23 CS RAB Congestion Ratio

Table 2-23 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 theRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. Themessage contains one of the following RAB assignment responses: "NoRadio Resources Available in Target cell", "Requested Maximum Bit Ratenot Available", "Requested Maximum Bit Rate for UL not Available","Requested Guaranteed Bit Rate not Available", "Requested Guaranteed BitRate for DL not Available", "Requested Guaranteed Bit Rate for UL notAvailable".The CS RAB Setup Attempt Procedure starts when the RNC receives an RABASSIGNMENT REQUEST message from the CN in the CS domain. Themessage contains one of the following RAB assignment requests:Conversational Services, streaming Services.

AssociatedCounters

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 )] x100%

Object CELL

Unit/Range %

Note None



26

2.24 PS RAB Congestion Ratio

Table 2-24 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 theRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. Themessage contains information about one of the following RAB assignmentresponses: "No Radio Resources Available in Target cell", "RequestedMaximum Bit Rate not Available", "Requested Maximum Bit Rate for ULnot Available", "Requested Guaranteed Bit Rate not Available", "RequestedGuaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Ratefor UL not Available".The PS RAB Setup Attempt Procedure starts when the RNC receives an RABASSIGNMENT REQUEST message from the SGSN in the PS domain. Themessage contains information about one of the following RAB assignmentrequests: Conversational services, Streaming services, Interactive Services,Background Services.

AssociatedCounters

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.FailEstabPS.HSDPAUser.Cong +VS.RAB.FailEstabPS.HSUPAUser.Cong /VS.RAB.AttEstabPS.Str +VS.RAB.AttEstabPS.Int +VS.RAB.AttEstabPS.Bkg ] x 100%

Object CELL

Unit/Range %

Note None



27

2.25 PS R99 RAB Setup Success Rate

Table 2-25 PS R99 RAB Setup Success Rate

Name PS R99 RAB Setup Success Rate

Formula PS R99 RAB Setup Success Rate = Number of successfully set up PS R99RABs x 100%/Number of PS R99 RAB setup attempts

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

AssociatedCounters

PS RAB Setup Success Ratio (Cell)=(VS.RAB.SuccEstab.PSR99/ VS.RAB.AttEstab.PSR99) * 100%

Object CELL

Unit/Range %

Note RNC-level KPIs are obtained by accumulating values of cell-level counters.

2.26 WB AMR RAB Setup Success Rate

Table 2-26 WB AMR RAB Setup Success Rate

Name WB AMR RAB Setup Success Rate

Formula WB AMR RAB Setup Success Rate = Number of successfully set up WBAMR RABs x 100%/Number of WB AMR RAB setup attempts

Description This KPI provides the WB AMR RAB setup success rate.The number of WB AMR RAB setup attempts is measured in the best cellwhere the UE camps on when the RNC receives from the CS CN an RABASSIGNMENT REQUEST message for a WB AMR voice service.The number of successfully set up WB AMR RABs is measured in the bestcell where the UE camps on when the RNC sends the CN an RABASSIGNMENT RESPONSE message after receiving a RADIO BEARERSETUP COMPLETE message from the UE if the RAB is for a WB AMRvoice service.



28

AssociatedCounters

AMR WB RAB Setup Success Ratio(Cell)=(VS.RAB.SuccEstabCS.AMRWB / VS.RAB.AttEstabCS.AMRWB)*100%

Object CELL

Unit/Range %




29

3 Availability

About This Chapter

Availability KPIs mainly indicate the utilization for several kinds of network resources such asRadio, bandwidth or CPU Load.

3.1 Worst Cell Ratio

3.2 Paging Congestion Ratio

3.3 Call Admission Refused Ratio

3.4 Congested Cell Ratio

3.5 Radio Network Unavailability Ratio

3.6 Average CPU Load

3.7 IUB Port Available Bandwidth Utilizing Ratio (UL)

3.8 IUB Port Available Bandwidth Utilizing Ratio (DL)

3.9 Cell Unavailability duration

3.10 HSDPA Unavailability duration

3.11 HSUPA Unavailability duration

3.12 CE Consumption for a NodeB Cell

3.13 Hardware Configured CE for a NodeB

3.14 Shared Group Configured License CE for a NodeB

3.15 Shared Group License CE Consumption for a NodeB

3.16 License Group Configured CE for a NodeB

3.17 License Group CE Consumption for a NodeB

3.18 RTWP (Received Total Wideband Power)

3.19 TCP (Transmitted Carrier Power)

RAN14.0KPI Reference 3 Availability


30

3.20 R99 Code Utilization

3.21 Number of Codes Used by HS-PDSCHs

3.22 HSDPA Efficiency



31

3.1 Worst Cell Ratio

Table 3-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 ratioor 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 VPRAB Setup Ratio <= 95%, or AMR Call Drop Ratio >3% and VP Call DropRatio >3%.

AssociatedCounters

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 CallDrop Ratio > 3% and VP Call Drop Ratio > 3%)]/The Total Number OfCells In RNC} x 100%

Object CELL

Unit/Range %

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

3.2 Paging Congestion Ratio

Table 3-2 Paging Congestion Ratio

Name Paging Congestion Ratio



32

Formula

Description Paging Congestion Ratio (RNC):This KPI is used to check the consumption of PCCH bandwidth during busyhours.l Description of the numerator:

The Failures to Respond to PAGING Message From CN counted if theRNC does not send a PAGING type 1 or PAGING type 2 message. Thereason is that the RNC does not send a PAGING message due tocongestion causes such as Iu flow control or high CPU usage.

l Description of the denominator:The Number of PAGING Message from CN is counted when RNCreceives 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 thebusy hour.l Description of the numerator:

This counter provides the number of losses of PAGING TYPE 1 messagedue to PCH congestion in a cell.

l Description of the denominator:This counter provides the number of paging messages of PAGING TYPE1 sent by the RNC in a cell.

AssociatedCounters

l IU Paging Congestion Ratio (RNC)=[(VS.RANAP.CsPaging.Loss+ VS.RANAP.PsPaging.Loss)/(VS.RANAP.CsPaging.Att+ VS.RANAP.PsPaging.Att)] x 100%

l IU Paging Congestion Ratio (Cell) =(VS.RRC.Paging1.Loss.PCHCong.Cell/VS.UTRAN.AttPaging1) x100%

Object RNC, CELL

Unit/Range %

Note None

3.3 Call Admission Refused Ratio



33

Table 3-3 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 busyhours in an RNC or a cluster.l Description of the numerator:

The failed number of Cell Resource Requests for New Call setup iscounted after RNC requesting cell resources for the UE successfully.

l Description of the denominator:The number of Cell Resource Requests during RAB establishment forCell. After RNC receiving the RAB ASSIGNMENT REQUEST messagefrom CN, the RNC requests cell resources for the UE and the counter ispegged in the cell where the UE camps on.

AssociatedCounters

Call admission Refused Ratio=[1-VS.RAC.NewCallAcc/VS.RAC.NewCallReq] x 100%

Object CELL

Unit/Range %


3.4 Congested Cell Ratio

Table 3-4 Congested Cell Ratio

Name Congested Cell Ratio

Formula

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



34

AssociatedCounters

Congested Cell Ratio =(The Number Of Cells, in which VS.LCC.OLC.UL.Num>0 orVS.LCC.OLC.DL.Num>0 On Busy Hour/The Total Number Of Cells InRNC) x 100%

Object CELL

Unit/Range %

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

3.5 Radio Network Unavailability Ratio

Table 3-5 Radio Network Unavailability Ratio

Name Radio Network Unavailability Ratio

Formula

Description This KPI describes the ratio of cell unavailable duration to the number of cellsin RNC during busy hours. It is used to check the impact of the degrading ofthe network performance caused by the unavailable cells during busy hoursin 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 period, or problemof CCH such as failed synchronization, or equipment faults.

AssociatedCounters

Radio Network Unavailability Ratio=(VS.Cell.UnavailTime.Sys)/(The Total Number Of Cells in RNC x {SP} x60) x 100%

Object CELL

Unit/Range %

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

3.6 Average CPU Load

Table 3-6 Average CPU Load

Name Average CPU Load



35

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. Italso indicates the load and operating performance of CPU on the XPU in themeasurement period.The CPU usage of the XPU is accumulated every second in the measurementperiod.

AssociatedCounters

Average CPU Load= VS.XPU.CPULOAD.MEAN

Object XPU

Unit/Range %

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

3.7 IUB Port Available Bandwidth Utilizing Ratio (UL)

Table 3-7 IUB Port Available Bandwidth Utilizing Ratio (UL)

Name IUB Port Available Bandwidth Utilizing Ratio (UL)

Formula

Description This KPI is used to check consumption of NodeB Iub port availablebandwidth utilizing ratio. The Bandwidth could be measured on ATMPhysical Ports or IP physical Ports.



36

AssociatedCounters

l IUB Port Available 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)] x 100%

l IUB Port Available 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)] x 100%

Object NodeB

Unit/Range %

Note The counters in the formula are measured on the NodeB side.In Iub over IP mode, the NodeB-level counters VS.IPUlTotal.1,VS.IPUlTotal.2, VS.IPUlTotal.3, and VS.IPUlTotal.4 provide theavailable physical bandwidths of ports rather than the actual availablebandwidths of ports. Therefore, this KPI can not be used to check the Iubactual bandwidth utilizing ratio.

3.8 IUB Port Available Bandwidth Utilizing Ratio (DL)

Table 3-8 IUB Port Available Bandwidth Utilizing Ratio (DL)

Name IUB Port Available Bandwidth Utilizing Ratio (DL)

Formula

Description This KPI is used to check consumption of NodeB Iub port availablebandwidth utilizing ratio. The Bandwidth could be measured on ATMPhysical Ports or IP physical Ports.



37

AssociatedCounters

l IUB Port Available 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)] x 100%

l IUB Port Available 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)] x 100%

Object NodeB

Unit/Range %

Note The counters in the formula are measured on the NodeB side.In Iub over IP mode, the NodeB-level counters VS.IPDLTotal.1,VS.IPDLTotal.2, VS.IPDLTotal.3, and VS.IPDLTotal.4 provide theavailable physical bandwidths of ports rather than the actual availablebandwidths of ports. Therefore, this KPI can not be used to check the Iubactual bandwidth utilizing ratio.

3.9 Cell Unavailability duration

Table 3-9 Cell Unavailability duration

Name Cell Unavailability duration

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

AssociatedCounters

VS.Cell.UnavailTime.Sys

Object CELL

Unit/Range s



38

Note None

3.10 HSDPA Unavailability duration

Table 3-10 HSDPA Unavailability duration

Name HSDPA Unavailability duration

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

AssociatedCounters

VS.Cell.HSDPA.UnavailTime

Object CELL

Unit/Range s

Note None

3.11 HSUPA Unavailability duration

Table 3-11 HSUPA Unavailability duration

Name HSUPA Unavailability duration

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

AssociatedCounters

VS.Cell.HSUPA.UnavailTime

Object CELL

Unit/Range s

Note None

3.12 CE Consumption for a NodeB Cell

Table 3-12 CE Consumption for a NodeB Cell

Name CE Consumption for a NodeB Cell



39

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

AssociatedCounters

VS.ULCE.Mean.SharedVS.ULCE.Max.SharedVS.DLCE.Mean.SharedVS.DLCE.Max.SharedVS.ULCE.Mean.DedicatedVS.ULCE.Max.DedicatedVS.DLCE.Mean.DedicatedVS.DLCE.Max.Dedicated

Object NodeB CELL

Unit/Range Numbers

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

3.13 Hardware Configured CE for a NodeB

Table 3-13 Hardware Configured CE for a NodeB

Name Hardware Configured CE for a NodeB

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

AssociatedCounters

VS.HW.ULCreditAvailableVS.HW.DLCreditAvailable

Object NodeB

Unit/Range Numbers

Note None

3.14 Shared Group Configured License CE for a NodeB

Table 3-14 Shared Group Configured License CE for a NodeB

Name Shared Group Configured License CE for a NodeB



40

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

AssociatedCounters

VS.LC.ULCreditAvailable.SharedVS.LC.DLCreditAvailable.Shared

Object NodeB

Unit/Range Numbers

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

3.15 Shared Group License CE Consumption for a NodeB

Table 3-15 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 consumedby an operator, or by HSUPA service.

AssociatedCounters

VS.LC.ULMean.LicenseGroup.SharedVS.LC.ULMax.LicenseGroup.SharedVS.LC.ULMin.LicenseGroup.Shared

VS.HSUPA.LC.ULMean.LicenseGroup.SharedVS.HSUPA.LC.ULMax.LicenseGroup.SharedVS.HSUPA.LC.ULMin.LicenseGroup.Shared

VS.LC.DLMean.LicenseGroup.SharedVS.LC.DLMax.LicenseGroup.SharedVS.LC.DLMin.LicenseGroup.Shared

Object NodeB

Unit/Range Numbers

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

3.16 License Group Configured CE for a NodeB



41

Table 3-16 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.

AssociatedCounters

VS.LC.DLCreditAvailable.LicenseGroup.DedicatedVS.LC.ULCreditAvailable.LicenseGroup.Dedicated

Object NodeB

Unit/Range Numbers

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

3.17 License Group CE Consumption for a NodeB

Table 3-17 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 consumedby a licensed group, or by HSUPA services.

AssociatedCounters

l UL StatisticsVS.LC.ULMean.LicenseGroupVS.LC.ULMax.LicenseGroupVS.LC.ULMin.LicenseGroupVS.HSUPA.LC.ULMin.LicenseGroupVS.HSUPA.LC.ULMean.LicenseGroupVS.HSUPA.LC.ULMax.LicenseGroup

l DL StatisticsVS.LC.DLMean.LicenseGroupVS.LC.DLMax.LicenseGroupVS.LC.DLMin.LicenseGroup

Object NodeB

Unit/Range Numbers

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

3.18 RTWP (Received Total Wideband Power)



42

Table 3-18 RTWP (Received Total Wideband Power)

Name RTWP (Received Total Wideband Power)

Description The first 3 counters given below provide the RTWP measurement values ofa cell in the RNC, Mean/Maximum/Minimum Power of Totally ReceivedBandwidth for Cell. The last 3 counters provide average, maximum andminimum received scheduled E-DCH power shared in the measurementperiod for cell.

AssociatedCounters

VS.MaxRTWPVS.MinRTWPVS.MeanRTWPVS.HSUPA.MeanRSEPSVS.HSUPA.MaxRSEPSVS.HSUPA.MinRSEPS

Object CELL

Unit/Range dBm; %

Note None

3.19 TCP (Transmitted Carrier Power)

Table 3-19 TCP (Transmitted Carrier Power)

Name TCP (Transmitted Carrier Power)

Description l The first 3 counters provide the Maximum/Minimum/Mean TransmittedPower of Carrier for a cell.

l The second 3 counters provide the Maximum/Minimum/MeanTransmitted Power of Carrier for Non-HSDPA Cell.

l The third 3 counters provide Maximum/Minimum/Mean Required Powerby HS-DSCH for Cell.

AssociatedCounters

VS.MaxTCPVS.MinTCPVS.MeanTCP

VS.MaxTCP.NonHSVS.MinTCP.NonHSVS.MeanTCP.NonHS

VS.HSDPA.MaxRequiredPwrVS.HSDPA.MinRequiredPwrVS.HSDPA.MeanRequiredPwr



43

Object CELL

Unit/Range dBm

Note None

3.20 R99 Code Utilization

Table 3-20 R99 Code Utilization

Name R99 Code Utilization

Formula

Description The occupied codes are the codes occupied by R99 user. The code number isnormalized 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-RABUEs that occupy the DL R99 codes with Spreading Factor (SF) of4/8/16/32/64/128/256.

AssociatedCounters

R99 Code Utilization =[(VS.SingleRAB.SF4+VS.MultRAB.SF4) x 64+(VS.SingleRAB.SF8+VS.MultRAB.SF8) x 32+(VS.SingleRAB.SF16+VS.MultRAB.SF16) x 16+(VS.SingleRAB.SF32+VS.MultRAB.SF32) x 8+(VS.SingleRAB.SF64+VS.MultRAB.SF64) x 4+(VS.SingleRAB.SF128+VS.MultRAB.SF128) x 2 +(VS.SingleRAB.SF256+VS.MultRAB.SF256)]/256 x 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 thefollowing formula:VS.RAB.SFOccupy /256The value would be greater than the real usage as the code for HSDPA wasreserved initially.

3.21 Number of Codes Used by HS-PDSCHs



44

Table 3-21 Number of Codes Used by HS-PDSCHs

Name Number of Codes Used by HS-PDSCHs

Formula HSDPA Efficiency = Duration when there is HSDPA data transmission/Duration when there is HSDPA data in the buffer

Description The counters VS.PdschCodeUsed.Mean, VS.PdschCodeUsed.Max, andVS.PdschCodeUsed.Min provide the mean, maximum, and minimumnumber of codes used by HS-PDSCHs in a cell during a measurement periodrespectively.

AssociatedCounters

VS.PdschCodeUsed.MeanVS.PdschCodeUsed.MaxVS.PdschCodeUsed.Min

Object NodeB

Unit/Range None

Note None

3.22 HSDPA Efficiency

Table 3-22 HSDPA Efficiency

Name HSDPA Efficiency

Formula HSDPA Efficiency = Duration when there is HSDPA data transmission/Duration when there is HSDPA data in the buffer

Description This KPI provides the proportion of the duration when there is HSDPA datatransmission to the duration when there is HSDPA data in the buffer.

AssociatedCounters

HSDPA efficiency =(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)/(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean +VS.HSDPA.ScheInactiveDataTtiRatio.Mean)

Object NodeB

Unit/Range %

Note (VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)indicates the proportion of TTIs with data transmission.VS.HSDPA.ScheInactiveDataTtiRatio.Mean indicates the proportion ofTTIs when there is no data transmission but the scheduling candidate setcontains data from the buffer.



45

4 Coverage

About This Chapter

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

4.1 UL Interference Cell Ratio

4.2 Soft Handover Overhead

RAN14.0KPI Reference 4 Coverage


46

4.1 UL Interference Cell Ratio

Table 4-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 ULinterference of all cells in an RNC.The mean RTWP's measurement is started when the RNC receives aCOMMON MEASUREMENT REPORT message from the NodeB about theRTWP of a cell and obtains the RTWP of the cell.

AssociatedCounters

UL Interference Cell Ratio =[(The Number Of Cells In which VS.MeanRTWP >-98dBm)/The TotalNumber Of Cells In RNC] x 100%

Object RNC

Unit/Range %

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

4.2 Soft Handover Overhead

Table 4-2 Soft Handover Overhead

KPI Name Soft Handover Overhead (RNC)



47

Formula

A1: Number of UEs with 1 RL in the RNCB1: Number of UEs with 2 RLs in the RNCC1: Number of UEs with 3 RLs in the RNCD1: Number of UEs with 4 RLs in the RNCE1: Number of UEs with 5 RLs in the RNCF1: Number of UEs with 6 RLs in the RNC.

A1: Number of UEs with 1 RLB1: Number of UEs with 2 RLsC1: Number of UEs with 3 RLsD1: Number of UEs with 4 RLsE1: Number of UEs with 5 RLsF1: Number of UEs with 6 RLs.

Description This KPI is used to check the consumption of network resources due to softhandover in an RNC or a Cell. It considered the radio link quantity during thesoft handover.In the RNC Soft handover ratio, count the mean number of UEs with differentquantity of radio links for RNC from A1 to F1. The RNC periodically samplesof the number of UEs with corresponding radio links in a measurement period.At the end of the measurement period, the RNC divides the accumulatednumber 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 countthe mean number of UEs with different quantity of Radio Links(1~6 radiolinks) in the Cell of the active set.



48

AssociatedCounters

l Soft Handover Overhead (RNC) ={[VS.SHO.AS.1.RNC +(VS.SHO.AS.2Softer.RNC +VS.SHO.AS.2Soft.RNC ) x 2 +(VS.SHO.AS.3Soft2Softer.RNC +VS.SHO.AS.3Soft.RNC +VS.SHO.AS.3Softer.RNC ) x 3 +VS.SHO.AS.4.RNC x 4 +VS.SHO.AS.5.RNC x 5 +VS.SHO.AS.6.RNC x 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} x 100%

l Soft Handover Overhead (Cell) =[(VS.SHO.AS.1RL+VS.SHO.AS.2RL +VS.SHO.AS.3RL +VS.SHO.AS.4RL +VS.SHO.AS.5RL +VS.SHO.AS.6RL )/(VS.SHO.AS.1RL+VS.SHO.AS.2RL /2 +VS.SHO.AS.3RL /3 +VS.SHO.AS.4RL /4 +VS.SHO.AS.5RL /5 +VS.SHO.AS.6RL /6)-1] x 100%

Object RNC, CELL

Unit/Range %

Note None



49

5 Mobility

About This Chapter

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

5.1 Soft Handover Success Ratio

5.2 Softer Handover Success Ratio

5.3 AMR Soft Handover Success Ratio

5.4 CS64 Soft Handover Success Ratio

5.5 PS Soft Handover Success Ratio

5.6 Intra-frequency Hard Handover Success Ratio

5.7 Inter-frequency Hard Handover Success Ratio

5.8 Service Cell Change Success Ratio with SHO (H2H)

5.9 H2H Intra-Frequency Hard Handover Success Ratio

5.10 H2H Inter-Frequency Hard Handover Success Ratio

5.11 H2D Inter-frequency Hard Handover Success Ratio

5.12 H2D Intra-Frequency Hard Handover Success Ratio

5.13 E2D Intra-Frequency Hard Handover Success Ratio

5.14 H2D Channel Switch Success Ratio

5.15 D2H Channel Switch Success Ratio

5.16 CS W2G Inter-RAT Handover Out Success Ratio

5.17 PS W2G Inter-RAT Handover Out Success Ratio

5.18 PS G2W Inter-RAT Handover In Success Ratio

5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio

RAN14.0KPI Reference 5 Mobility


50

5.20 SRNC Relocation Success Ratio

5.21 TRNC Relocation Success Ratio

5.22 E-DCH Soft Handover Success Ratio

5.23 E-DCH Cell Change Success Ratio with SHO

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

5.25 E2D Channel Switch Success Ratio

5.26 D2E Channel Switch Success Ratio

5.27 E2D Handover Success Ratio with Inter HHO

5.28 HSUPA W2G Inter-RAT Handover Out Success Ratio

5.29 MBMS Service Mode Switch Success Ratio

5.30 CS Inter-Frequency Hard Handover Success Rate

5.31 PS Inter-Frequency Hard Handover Success Rate



51

5.1 Soft Handover Success Ratio

Table 5-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 aCluster, including softer handover.l The Successful Soft Handover (including softer handovers) procedure is

complete when the RNC receives an ACTIVE SET UPDATECOMPLETE message from the UE during the soft handover (includingthe softer handover) procedure.

l The attempt procedure is complete when the RNC sends an ACTIVE SETUPDATE message to the UE.

AssociatedCounters

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

Object RNC, CELL

Unit/Range %

Note None

5.2 Softer Handover Success Ratio

Table 5-2 Softer Handover Success Ratio

Name Softer Handover Success Ratio

Formula



52

Description This KPI is used to check the softer handover success ratio in an RNC or aCluster, including softer handover.l The Successful Softer Handover procedure is complete when the RNC

receives an ACTIVE SET UPDATE COMPLETE message from the UEduring the softer handover procedure.

l The attempt procedure is complete when the RNC sends an ACTIVE SETUPDATE message to the UE.

AssociatedCounters

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

Object RNC, CELL

Unit/Range %

Note None

5.3 AMR Soft Handover Success Ratio

Table 5-3 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 RNCor a Cluster, including softer handover.The Successful AMR Soft Handover procedure is complete when the RNCreceives an ACTIVE SET UPDATE COMPLETE message from the UEduring the soft handover procedure.The attempt procedure is complete when the RNC sends an ACTIVE SETUPDATE message to the UE.

AssociatedCounters

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

Object CELL

Unit/Range %

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



53

5.4 CS64 Soft Handover Success Ratio

Table 5-4 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 RNCor a Cluster, including softer handover.The Successful CS64 Soft Handover procedure is complete when the RNCreceives an ACTIVE SET UPDATE COMPLETE message from the UEduring the soft handover procedure.The attempt procedure is complete when the RNC sends an ACTIVE SETUPDATE message to the UE.

AssociatedCounters

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

Object CELL

Unit/Range %


5.5 PS Soft Handover Success Ratio

Table 5-5 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 ora Cluster, including softer handover.The Successful PS Soft Handover procedure is complete when the RNCreceives an ACTIVE SET UPDATE COMPLETE message from the UEduring the soft handover procedure.The attempt procedure is complete when the RNC sends an ACTIVE SETUPDATE message to the UE.



54

AssociatedCounters

PS services Soft Handover Success Ratio =[(VS.SHO.PS.Succ)/(VS.SHO.PS.Att)] x 100%

Object CELL

Unit/Range %


5.6 Intra-frequency Hard Handover Success Ratio

Table 5-6 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 inan RNC.The Intra-frequency Hard Handover Success procedure is complete when theRNC receives the PHYSICAL CHANNEL RECONFIGURATIONCOMPLETE (for example) message from the UE.The Intra-frequency Hard Handover Attempt procedure is complete whenRNC sends the PHYSICAL CHANNEL RECONFIGURATION message tothe UE.

AssociatedCounters

l Intra-frequency Hard Handover Success Ratio (Cell) =[(VS.HHO.SuccIntraFreqOut.IntraNodeB+VS.HHO.SuccIntraFreqOut.InterNodeBIntraRNC +VS.HHO.SuccIntraFreqOut.InterRNC )/(VS.HHO.AttIntraFreqOut.InterNodeBIntraRNC+VS.HHO.AttIntraFreqOut.InterRNC +VS.HHO.AttIntraFreqOut.IntraNodeB )] x 100%

l Intra-frequency Hard Handover Success Ratio (RNC) =[(VS.HHO.SuccIntraFreq.RNC)/(VS.HHO.AttIntraFreq.RNC)] x100%

Object RNC, CELL

Unit/Range %

Note None



55

5.7 Inter-frequency Hard Handover Success Ratio

Table 5-7 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 inan RNC.The Inter-frequency Hard Handover Success procedure is complete whenRNC received a PHYSICAL CHANNEL RECONFIGURATIONCOMPLETE message from the UE.The Inter-frequency Hard Handover attempts procedure starts when RNCsends a PHYSICAL CHANNEL RECONFIGURATION message to the UE.In this case the RNC measures the counter.

AssociatedCounters

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

Object RNC, CELL

Unit/Range %

Note None

5.8 Service Cell Change Success Ratio with SHO (H2H)

Table 5-8 Service Cell Change Success Ratio with SHO (H2H)

Name Service Cell Change Success Ratio with SHO (H2H)

Formula



56

Description l The HS-DSCH service cell change success with SHO is triggered withthe following messages:PHYSICAL CHANNEL RECONFIGURATIONTRANSPORT CHANNEL RECONFIGURATIONRADIO BEARER RECONFIGURATIONACTIVE SET UPDATE

l Accordingly, the UE sends the following messages to the RNC as aresponse.PHYSICAL CHANNEL RECONFIGURATION COMPLETEPHYSICAL CHANNEL RECONFIGURATION FAILURETRANSPORT CHANNEL RECONFIGURATION COMPLETETRANSPORT CHANNEL RECONFIGURATION FAILURERADIO BEARER RECONFIGURATION COMPLETERADIO BEARER RECONFIGURATION FAILUREACTIVE SET UPDATE COMPLETEACTIVE SET UPDATE FAILURE Message

Take the PHYSICAL CHANNEL RECONFIGURATION message as anexample. When receiving a PHYSICAL CHANNEL RECONFIGURATIONCOMPLETE message from a UE, the RNC measures this item as numerator,and when sending a PHYSICAL CHANNEL RECONFIGURATIONmessage to a UE, the RNC measures this item as denominator.

AssociatedCounters

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

Object CELL

Unit/Range %

Note None

5.9 H2H Intra-Frequency Hard Handover Success Ratio

Table 5-9 H2H Intra-Frequency Hard Handover Success Ratio

Name H2H Intra-Frequency Hard Handover Success Ratio

Formula



57

Description This KPI is used to check the intra-frequency hard handover success ratio ofHSDPA service in an RNC or a cluster.l The HS-DSCH service cell change success with SHO is triggered with

the following message:PHYSICAL CHANNEL RECONFIGURATIONTRANSPORT CHANNEL RECONFIGURATIONRADIO BEARER RECONFIGURATION

l Accordingly, the UE sends the following messages to the RNC as aresponse.PHYSICAL CHANNEL RECONFIGURATION COMPLETEPHYSICAL CHANNEL RECONFIGURATION FAILURETRANSPORT CHANNEL RECONFIGURATION COMPLETETRANSPORT CHANNEL RECONFIGURATION FAILURERADIO BEARER RECONFIGURATION COMPLETERADIO BEARER RECONFIGURATION FAILURERADIO BEARER SETUP COMPLETERADIO BEARER SETUP FAILURERADIO BEARER RELEASE COMPLETERADIO BEARER RELEASE FAILURE

Take the PHYSICAL CHANNEL RECONFIGURATION message as anexample, when receiving a PHYSICAL CHANNEL RECONFIGURATIONCOMPLETE message from a UE , the RNC measures this item in the bestcell from which the UE is handed over if an intra-frequency HSDPA hardhandover without channel change is performed.

AssociatedCounters

H2H Intra-Frequency Hard Handover Success Ratio =(VS.HSDPA.HHO.H2H.SuccOutIntraFreq/VS.HSDPA.HHO.H2H.At-tOutIntraFreq) x 100%

Object CELL

Unit/Range %

Note None

5.10 H2H Inter-Frequency Hard Handover Success Ratio

Table 5-10 H2H Inter-Frequency Hard Handover Success Ratio

Name H2H Inter-Frequency Hard Handover Success Ratio

Formula



58

Description This KPI is used to indicate the success ratio of inter-frequency hardhandovers from the HSDPA to the HSDPA in a cell.l The hard handover procedure can be triggered with the following

message:PHYSICAL CHANNEL RECONFIGURATIONTRANSPORT CHANNEL RECONFIGURATIONRADIO BEARER RECONFIGURATION

l Accordingly, the UE sends the following messages to the RNC as aresponse.PHYSICAL CHANNEL RECONFIGURATION COMPLETEPHYSICAL CHANNEL RECONFIGURATION FAILURETRANSPORT CHANNEL RECONFIGURATION COMPLETETRANSPORT CHANNEL RECONFIGURATION FAILURERADIO BEARER RECONFIGURATION COMPLETERADIO BEARER RECONFIGURATION FAILURERADIO BEARER SETUP COMPLETERADIO BEARER SETUP FAILURERADIO BEARER RELEASE COMPLETERADIO BEARER RELEASE FAILURE

Take the PHYSICAL CHANNEL RECONFIGURATION message as anexample, when receiving a PHYSICAL CHANNEL RECONFIGURATIONCOMPLETE message from a UE , the RNC measures this item in the bestcell from which the UE is handed over if an inter-frequency HSDPA hardhandover without channel change is performed.

AssociatedCounters

H2H Inter-Frequency Hard Handover Success Ratio=(VS.HSDPA.HHO.H2H.SuccOutInterFreq/VS.HSDPA.HHO.H2H.At-tOutInterFreq) x 100%

Object CELL

Unit/Range %

Note None

5.11 H2D Inter-frequency Hard Handover Success Ratio

Table 5-11 H2D Inter-frequency Hard Handover Success Ratio

Name H2D Inter-frequency Hard Handover Success Ratio

Formula



59

Description This KPI is used to indicate the success ratio of inter-frequency hardhandovers from the HSDPA to the DCH in a cell.l The hard handover procedure can be triggered with the following

messages:RADIO BEARER RECONFIGURATIONRADIO BEARER SETUPRADIO BEARER RELEASE message

l Accordingly, the UE sends the following messages to the RNC as aresponse.RADIO BEARER RECONFIGURATION COMPLETERADIO BEARER RECONFIGURATION FAILURERADIO BEARER SETUP COMPLETERADIO BEARER SETUP FAILURERADIO BEARER RELEASE COMPLETERADIO BEARER RELEASE FAILURE

Take the RADIO BEARER RECONFIGURATION message as an example,when receiving a RADIO BEARER RECONFIGURATION COMPLETEmessage from a UE , the RNC measures this item in the best cell from whichthe UE is handed over if an inter-frequency hard handover from the HSDPAto the DCH is performed.

AssociatedCounters

H2D Inter-frequency Hard Handover Success Ratio =(VS.HSDPA.HHO.H2D.SuccOutInterFreq/VS.HSDPA.HHO.H2D.At-tOutInterFreq) x 100%

Object CELL

Unit/Range %

Note None

5.12 H2D Intra-Frequency Hard Handover Success Ratio

Table 5-12 H2D Intra-Frequency Hard Handover Success Ratio

Name H2D Intra-Frequency Hard Handover Success Ratio

Formula H2D Intra-Frequency Hard Handover Success Ratio = Number of successfulH2D intra-frequency hard handovers x 100%/Number of H2D intra-frequency hard handover attempts



60

Description This KPI provides the success rate of HSDPA-to-DCH intra-frequency hardhandovers in a cell.A hard handover is triggered by any of the following messages:l RADIO BEARER RECONFIGURATIONl RADIO BEARER SETUPl RADIO BEARER RELEASEAccordingly, a UE may respond with one of the following messages:l RADIO BEARER RECONFIGURATION COMPLETEl RADIO BEARER RECONFIGURATION FAILUREl RADIO BEARER SETUP COMPLETEl RADIO BEARER SETUP FAILUREl RADIO BEARER RELEASE COMPLETEl RADIO BEARER RELEASE FAILUREAssume that a hard handover is triggered by the RADIO BEARERRECONFIGURATION message. The number of successful H2D intra-frequency hard handovers is measured in the best cell where the UE campson before the hard handover when the RNC receives from the UE a RADIOBEARER RECONFIGURATION COMPLETE message during an intra-frequency hard handover.

AssociatedCounters

H2D Intra-frequency Hard Handover Success Ratio =(VS.HSDPA.HHO.H2D.SuccOutIntraFreq/ VS.HSDPA.HHO.H2D.At-tOutIntraFreq)*100%

Object CELL

Unit/Range %


5.13 E2D Intra-Frequency Hard Handover Success Ratio

Table 5-13 E2D Intra-Frequency Hard Handover Success Ratio

Name E2D Intra-Frequency Hard Handover Success Ratio

Formula E2D Intra-Frequency Hard Handover Success Ratio = Number of successfulE2D intra-frequency hard handovers x 100%/Number of E2D intra-frequencyhard handover attempts



61

Description This KPI provides the success rate of EDCH-to-DCH intra-frequency hardhandovers in a cell.The number of E2D intra-frequency hard handover attempts is measured inthe HSUPA serving cell where the UE camps on before the handover whenthe RNC sends the UE a RADIO BEARER RECONFIGURATION messageduring an EDCH-to-DCH intra-frequency hard handover.The number of successful E2D intra-frequency hard handovers is measuredin the HSUPA serving cell where the UE camps on before the handover whenthe RNC receives from the UE a RADIO BEARER RECONFIGURATIONCOMPLETE message during an EDCH-to-DCH intra-frequency hardhandover.

AssociatedCounters

E2D Intra-frequency Hard Handover Success Ratio =(VS.HSUPA.HHO.E2D.SuccOutIntraFreq/VS.HSUPA.HHO.E2D.At-tOutIntraFreq)*100%

Object CELL

Unit/Range %


5.14 H2D Channel Switch Success Ratio

Table 5-14 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 switchesfrom HSDPA to DCH in an RNC or a cluster.The number of successful HS-DSCH to DCH channel switch measures whenRNC receives a RAIDO BEARER RECONFIGURATION COMPLETEmessage from the UE indicating the channel reconfiguration for HSDPAservice in the DCCC or RAB MODIFY procedure. The RNC measures theitem in the HSDPA serving cell.The attempt number of H2D channel handover counts when RNC decides toperform a channel handover, which sends a RADIO BEARERRECONFIGURATION message to a UE during the DCCC or RAB MODIFYprocedure. In this case, the RNC measures the item in the serving cell of theHSDPA service according to the transport channels of UEs before and afterthe reconfiguration.The RNC performs the transport channel Switch in the same cell.



62

AssociatedCounters

H2D Channel Switch Success Ratio=(VS.HSDPA.H2D.Succ/VS.HSDPA.H2D.Att) x 100%

Object CELL

Unit/Range %

Note None

5.15 D2H Channel Switch Success Ratio

Table 5-15 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 UEswitches from DCH to HSDPA in an RNC or a cluster.The number of successful DCH to HS-DSCH channel switch measures whenRNC receives from the UE a RAIDO BEARER RECONFIGURATIONCOMPLETE message indicating the channel reconfiguration for HSDPAservice in the DCCC or RAB MODIFY procedure. The RNC measures theitem in the HSDPA serving cell.The attempt number of D2H channel switch counts when RNC decides toperform a channel switch, which sends a RADIO BEARERRECONFIGURATION message to a UE during the DCCC or RAB MODIFYprocedure. In this case, the RNC measures the item in the serving cell of theHSDPA service according to the transport channels of UEs before and afterthe reconfiguration.The RNC performs the transport channel switch in the same cell.

AssociatedCounters

D2H Channel Switch Success Ratio =(VS.HSDPA.D2H.Succ/VS.HSDPA.D2H.Att) x 100%

Object CELL

Unit/Range %

Note None

5.16 CS W2G Inter-RAT Handover Out Success Ratio



63

Table 5-16 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-RAThandovers in an RNC or a Cluster.The CS inter-RAT Handover Success procedure is complete when RNCreceives an IU RELEASE COMMAND message. The message contains oneof the following information: "Successful Relocation", "Normal Release","Network Optimization" after sending a HANDOVER FROM UTRANCOMMAND message during the CS outgoing inter-RAT handover. In thiscase, the outgoing handover succeeds and this counter is measured.The CS inter-RAT Handover attempts procedure starts when the RNC sendsa HANDOVER FROM UTRAN COMMAND message to the UE during theCS outgoing inter-RAT handover.

AssociatedCounters

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

Object RNC, CELL

Unit/Range %

Note None

5.17 PS W2G Inter-RAT Handover Out Success Ratio

Table 5-17 PS W2G Inter-RAT Handover Out Success Ratio

Name PS W2G Inter-RAT Handover Out Success Ratio

Formula



64

Description This KPI is used to indicate the success ratio of PS outgoing inter-RAThandover initiated by the RNC or in the best cell.The PS W2G Inter-RAT Outgoing Handover successes procedure is completewhen the RNC sends the IU RELEASE COMPLETE message after receivingthe IU RELEASE COMMAND message. The message contains one of thefollowing information: "Successful Relocation", "Normal Release","Network Optimization" during the PS outgoing inter-RAT handover. In thiscase, the PS outgoing inter-RAT handover succeeds and the counter ismeasured.The PS W2G Inter-RAT Outgoing Handover attempts procedure starts whenthe RNC sends the CELL CHANGE ORDER FROM UTRAN messageduring the PS outgoing inter-RAT handover.

AssociatedCounters

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

Object RNC, CELL

Unit/Range %

Note None

5.18 PS G2W Inter-RAT Handover In Success Ratio

Table 5-18 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 anRNC or a cluster.The PS G2W Inter-RAT Handover successes procedure is complete when theRNC receives an RRC CONNECTION SETUP COMPLETE message fromthe UE. The reasons for RRC connection request is Inter-RAT Cell ChangeOrder and Inter-RAT Cell Reselection.The PS G2W Inter-RAT Handover attempts procedure starts when the RNCreceives an RRC CONNECTION REQUEST message from the UE, thereasons for RRC connection request are Inter-RAT Cell Change Order andInter-RAT Cell Reselection.



65

AssociatedCounters

PS G2W Inter-RAT Handover In Success Ratio=[(RRC.SuccConnEstab.IRATCCO+RRC.SuccConnEstab.IRAT-CelRes)/(RRC.AttConnEstab.IRATCCO+RRC.AttConnEstab.IRATCelRes)] x100%

Object CELL

Unit/Range %

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

5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio

Table 5-19 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 HSDPAservices initiated by the RNC in the best cell that the UE camps on before thehandover.The HSDPA Inter-RAT HO successes procedure is complete when the RNCreceives the IU RELEASE COMMAND message. The message contains oneof the following information: "Successful Relocation", "Normal Release","Network Optimization" during the PS outgoing inter-RAT handover forHSDPA services.The HSDPA Inter-RAT HO attempts procedure starts when the RNC sendsthe CELL CHANGE ORDER FROM UTRAN message during the PSoutgoing inter-RAT handover for HSDPA services, the counter is measuredin the best cell that the UE camps on.

AssociatedCounters

HSDPA W2G Inter-RAT Handover Out Success Ratio=(VS.IRATHO.HSDPA.SuccOutPSUTRAN/VS.IRATHO.HSDPA.At-tOutPSUTRAN) x 100%

Object CELL

Unit/Range %

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

5.20 SRNC Relocation Success Ratio



66

Table 5-20 SRNC Relocation Success Ratio

Name SRNC Relocation Success Ratio

Formula

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

AssociatedCounters

SRNC Relocation Success Ratio =[(VS.SRELOC.SuccExecUEInvolCS+VS.SRELOC.SuccExecUEInvolPS +VS.SRELOC.SuccExecUENonInvolCS +VS.SRELOC.SuccExecUENonInvolPS )/(RELOC.SuccPrepUEInvolCS+RELOC.SuccPrepUENotInvolCS +RELOC.SuccPrepUEInvolPS +RELOC.SuccPrepUENotInvolPS )] x 100%

Object RNC

Unit/Range %

Note None

5.21 TRNC Relocation Success Ratio

Table 5-21 TRNC Relocation Success Ratio

Name TRNC Relocation Success Ratio

Formula



67

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

AssociatedCounters

TRNC Relocation Success Ratio =[(VS.TRELOC.SuccExecUEInvolCS+VS.TRELOC.SuccExecUEInvolPS+VS.TRELOC.SuccExecUENotInvolCS+VS.TRELOC.SuccExecUENotInvolPS )/(RELOC.SuccResAllocUEInvolCS+RELOC.SuccResAllocUENotInvolCS +RELOC.SuccResAllocUEInvolPS +RELOC.SuccResAllocUENotInvolPS )] x 100%

Object RNC

Unit/Range %

Note None

5.22 E-DCH Soft Handover Success Ratio

Table 5-22 E-DCH Soft Handover Success Ratio

Name E-DCH Soft Handover Success Ratio

Formula



68

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

AssociatedCounters

E-DCH Soft Handover Success Ratio=(VS.HSUPA.SHO.SuccOut/VS.HSUPA.SHO.AttOut) x 100%

Object CELL

Unit/Range %

Note None

5.23 E-DCH Cell Change Success Ratio with SHO

Table 5-23 E-DCH Cell Change Success Ratio with SHO

Name E-DCH Cell Change Success Ratio with SHO

Formula



69

Description This KPI is used to check the success ratio of HSUPA serving cell changesin soft handover status for cell.Description of the numerator:l The successful HSUPA serving cell changes in soft handover status for

cell, this procedure can be triggered with the following messages:PHYSICAL CHANNEL RECONFIGURATIONTRANSPORT CHANNEL RECONFIGURATIONRADIO BEARER RECONFIGURATION

l Accordingly, the UE sends the following messaged to the RNC as aresponse:PHYSICAL CHANNEL RECONFIGURATION COMPLETEPHYSICAL CHANNEL RECONFIGURATION FAILURETRANSPORT CHANNEL RECONFIGURATION COMPLETETRANSPORT CHANNEL RECONFIGURATION FAILURERADIO BEARER RECONFIGURATION COMPLETERADIO BEARER RECONFIGURATION FAILURE

l Take the PHYSICAL CHANNEL RECONFIGURATION message as anexample, when the RNC receives a PHYSICAL CHANNELRECONFIGURATION COMPLETE message from the UE, the RNCmeasures this item in the original HSUPA serving cell if the HSUPAserving cell is changed. The item is used to indicate the change of HSUPAserving cells in the soft handover state instead of the hard handover state.

Description of the denominator:l Take the PHYSICAL CHANNEL RECONFIGURATION message as an

example, when the RNC sends a PHY CHANNELRECONFIGURATION message to the UE. The RNC measures this itemin 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 thesoft handover status instead of the hard handover status.

AssociatedCounters

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

Object CELL

Unit/Range %

Note None

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



70

Table 5-24 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 withthe Inter-HHO procedure in an RNC or a cluster.Description of the numerator:l When the RNC receives one of the following messages from the UE, the

RNC measures this item in the HSUPA serving cell before the hardhandover if an EDCH-to-EDCH inter-frequency hard handover isperformed.PHYSICAL CHANNEL RECONFIGURATION COMPLETETRANSPORT CHANNEL RECONFIGURATION COMPLETERADIO BEARER RECONFIGURATION COMPLETERADIO BEARER SETUP COMPLETERADIO BEARER RELEASE COMPLETE

Description of the denominator:l When the RNC sends the following messages to the UE, the RNC

measures the item in the HSUPA serving cell before the hard handover ifan EDCH-to-EDCH inter-frequency hard handover is performed.PHYSICAL CHANNEL RECONFIGRATIONTRANSPORT CHANNEL RECONFIGRATIONRADIO BEARER RECONFIGRATIONRADIO BEARER SETUPRADIO BEARER RELEASE

AssociatedCounters

E-DCH Service Cell Change Success Ratio with Inter-HHO=(VS.HSUPA.HHO.E2E.SuccOutInterFreq/VS.HSUPA.HHO.E2E.At-tOutInterFreq) x 100%

Object CELL

Unit/Range %

Note None

5.25 E2D Channel Switch Success Ratio

Table 5-25 E2D Channel Switch Success Ratio

Name E2D Channel Switch Success Ratio



71

Formula

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

AssociatedCounters

E2D Channel Switch Success Ratio =(VS.HSUPA.E2D.Succ/VS.HSUPA.E2D.Att) x 100%

Object CELL

Unit/Range %

Note None

5.26 D2E Channel Switch Success Ratio

Table 5-26 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 UEhandover from E-DCH to DCH in the same cell.The Switch Channel Type from DCH to EDCH successful attempts procedureis complete when the RNC receives an RB RECFG CMP message from theUE during the DCCC or RAB ASSIGN procedure. If the UE camps on thesame cell after reconfigurations, the RNC measures the items in the HSUPAserving cell by the channel switch type.The Switch Channel Type from DCH to EDCH attempts procedure startswhen the RNC sends a RADIO BEAR RECONFIGURE message to the UEduring the DCCC or RAB ASSIGN procedure. If the UE camps on the samecell after reconfigurations, the RNC measures the items in the HSUPA servingcell by the channel switch type.



72

AssociatedCounters

D2E Channel Switch Success Ratio (Intra Cell) =(VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att) x 100%

Object CELL

Unit/Range %

Note None

5.27 E2D Handover Success Ratio with Inter HHO

Table 5-27 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 HardHandover from EDCH to DCH in a cell.The Switch Channel Type from EDCH to DCH successful attempts procedureis complete when the RNC receives a RADIO BEARERRECONFIGURATION COMPLETE message from the UE. The RNCmeasures this item in the HSUPA serving cell before the hard handover if anEDCH-to-DCH inter-frequency hard handover is performed.The Switch Channel Type from EDCH to DCH attempts procedure startswhen the RNC sends a RADIO BEARER RECONFIGURATION messageto the UE. The RNC measures this item in the HSUPA serving cell before thehard handover if an EDCH-to-DCH inter-frequency hard handover isperformed.

AssociatedCounters

E-DCH to DCH Handover Success Ratio (with Inter HHO) =(VS.HSUPA.HHO.E2D.SuccOutInterFreq/VS.HSUPA.HHO.E2D.At-tOutInterFreq) x 100%

Object CELL

Unit/Range %

Note None

5.28 HSUPA W2G Inter-RAT Handover Out Success Ratio



73

Table 5-28 HSUPA W2G Inter-RAT Handover Out Success Ratio

Name HSUPA W2G Inter-RAT Handover Out Success Ratio

Formula

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

AssociatedCounters

HSUPA W2G Inter-RAT Handover Out Success Ratio =(VS.IRATHO.HSUPA.SuccOutPSUTRAN/VS.IRATHO.HSUPA.At-tOutPSUTRAN) x 100%

Object CELL

Unit/Range %

Note None

5.29 MBMS Service Mode Switch Success Ratio

Table 5-29 MBMS Service Mode Switch Success Ratio

Name MBMS Service Mode Switch Success Ratio

Formula



74

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

AssociatedCounters

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

Object CELL

Unit/Range %

Note None

5.30 CS Inter-Frequency Hard Handover Success Rate

Table 5-30 CS Inter-Frequency Hard Handover Success Rate

Name CS Inter-Frequency Hard Handover Success Rate

Formula CS Inter-Frequency Hard Handover Success Rate = Number of successfulCS inter-frequency hard handovers x 100%/Number of CS inter-frequencyhard handover attempts

Description This KPI provides the success rate of CS inter-frequency hard handovers ofan RNC.The number of CS inter-frequency hard handover attempts is measured whenthe RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATIONmessage during a CS inter-frequency hard handover.The number of successful CS inter-frequency hard handovers is measuredwhen the RNC receives from the UE a PHYSICAL CHANNELRECONFIGURATION COMPLETE message during a CS inter-frequencyhard handover.

AssociatedCounters

CS Inter-frequency Hard Handover Success Ratio =(VS.HHO.SuccInterFreqOut.CS/ VS.HHO.AttInterFreqOut.CS) *100%

Object CELL

Unit/Range %

Note RNC-level KPIs are obtained by accumulating values of cell-level counter.



75

5.31 PS Inter-Frequency Hard Handover Success Rate

Table 5-31 PS Inter-Frequency Hard Handover Success Rate

Name PS Inter-Frequency Hard Handover Success Rate

Formula PS Inter-Frequency Hard Handover Success Rate = Number of successful PSinter-frequency hard handovers x 100%/Number of PS inter-frequency hardhandover attempts

Description This KPI provides the success rate of PS inter-frequency hard handovers ofan RNC.The number of PS inter-frequency hard handover attempts is measured whenthe RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATIONmessage during a PS inter-frequency hard handover.The number of successful PS inter-frequency hard handovers is measuredwhen the RNC receives from the UE a PHYSICAL CHANNELRECONFIGURATION COMPLETE message during a PS inter-frequencyhard handover.

AssociatedCounters

PS Inter-frequency Hard Handover Success Ratio=(VS.HHO.SuccInterFreqOut.PS/ VS.HHO.AttInterFreqOut.PS)*100%

Object CELL

Unit/Range %

Note RNC-level KPIs are obtained by accumulating values of cell-level counter.



76

6 Retainability

About This Chapter

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

6.1 CS Service Drop Ratio

6.2 CS Call Drop Rate in CS+PS Combined Services

6.3 PS Call Drop Rate in CS+PS Combined Services

6.4 AMR Call Drop Ratio

6.5 WB AMR Call Drop Rate

6.6 VP Call Drop Ratio

6.7 AMR Traffic Drop Ratio

6.8 VP Traffic Drop Ratio

6.9 PS Call Drop Ratio

6.10 PS Call Drop Ratio (PCH)

6.11 PS R99 Call Drop Ratio

6.12 PS R99 Call Drop Ratio (PCH)

6.13 PS BE Call Drop Ratio

6.14 HSDPA Call Drop Ratio

6.15 HSDPA Call Drop Ratio (PCH)

6.16 HSUPA Call Drop Ratio

6.17 HSUPA Call Drop Ratio (PCH)

6.18 MBMS Service PTP drop Ratio

RAN14.0KPI Reference 6 Retainability


77

6.1 CS Service Drop Ratio

Table 6-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 CSRAB Releases (Normal Release + Abnormal Release). This KPI is used tocheck 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 RELEASEREQUEST message to the CN due to exceptions. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message with thecauses other than "User Inactivity", "Normal Release", "SuccessfulRelocation", "Network Optimization", the RNC measures the itemsaccording to the service types in the best cell that the UE camps on if thereleased RABs belong to PS domain.

AssociatedCounters

CS Service Drop Ratio (Cell) =[VS.RAB.AbnormRel.CS/(VS.RAB.AbnormRel.CS+VS.RAB.NormRel.CS)] x 100%CS Service Drop Ratio (RNC) =[VS.RAB.AbnormRel.CS.RNC/(VS.RAB.AbnormRel.CS.RNC+VS.RAB.NormRel.CS.RNC)] x 100%

Object CELL, RNC

Unit/Range %

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

6.2 CS Call Drop Rate in CS+PS Combined Services

Table 6-2 CS Call Drop Rate in CS+PS Combined Services

Name CS Call Drop Rate in CS+PS Combined Services

Formula CS Call Drop Rate in CS+PS Combined Services = Number of times that aCS call in a CS+PS combined service drops/Number of CS+PS combinedservice release times



78

Description This KPI provides the drop rate of CS calls in CS+PS combined services.It reflects the retainability of CS+PS combined services in an RNC or cluster.When a failure occurs, the RNC sends the CN an IU RELEASE REQUESTmessage. After receiving the message, the CN sends an IU RELEASECOMMAND message to the RNC. If the IU RELEASE COMMANDmessage contains a cause value of abnormal release (causes except "UserInactivity", "Normal Release", "Successful Relocation", or "NetworkOptimization"), then the number of times that a CS call in a CS+PS combinedservice drops is measured in the best cell that the UE camps on if the messageis for a CS call in a CS+PS combined service.

AssociatedCounters

CS Call Drop Rate in CS+PS Combined Services (Cell) =(VS.MultiRAB.CSAbnormRel.CSPS/(VS.MultiRAB.CSNormRel.CSPS +VS.MultiRAB.CSAbnormRel.CSPS +VS.MultiRAB.PSNormRel.CSPS))*100%

Object CELL

Unit/Range %

Note None

6.3 PS Call Drop Rate in CS+PS Combined Services

Table 6-3 PS Call Drop Rate in CS+PS Combined Services

Name PS Call Drop Rate in CS+PS Combined Services

Formula PS Call Drop Rate in CS+PS Combined Services = Number of times that aPS connection in a CS+PS combined service fails/Number of CS+PScombined service release times

Description This KPI provides the PS connection failure rate in CS+PS combinedservices.It reflects the retainability of CS+PS combined services in an RNC or cluster.When a failure occurs, the RNC sends the CN an IU RELEASE REQUESTmessage. After receiving the message, the CN sends an IU RELEASECOMMAND message to the RNC. If the IU RELEASE COMMANDmessage contains a cause value of abnormal release (causes except "UserInactivity", "Normal Release", "Successful Relocation", or "NetworkOptimization"), then the number of times that a PS connection in a CS+PScombined service fails is measured in the best cell that the UE camps on ifthe message is for a PS service in a CS+PS combined service.

AssociatedCounters

PS Call Drop Rate in CS+PS Combined Services (Cell)=(VS.MultiRAB.PSAbnormRel.CSPS/(VS.MultiRAB.CSNormRel.CSPS + VS.MultiRAB.PSNormRel.CSPS +VS.MultiRAB.PSAbnormRel.CSPS))*100%



79

Object CELL

Unit/Range %

Note None

6.4 AMR Call Drop Ratio

Table 6-4 AMR Call Drop Ratio

Name AMR Call Drop Ratio

Formula

Description This KPI provides the ratio of AMR RAB abnormal Releases to the totalAMR RAB Releases (Normal Release + Abnormal Release) and is used tocheck the retainabililty of AMR Service within the UTRAN (RNC or Cluster).Description of RAB abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CNdue to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following messages: "User Inactivity","Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

AMR Call Drop Ratio (Cell) =[VS.RAB.AbnormRel.AMR/(VS.RAB.AbnormRel.AMR+VS.RAB.NormRel.AMR)] x 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} )] x 100%

Object CELL, RNC

Unit/Range %

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

6.5 WB AMR Call Drop Rate



80

Table 6-5 WB AMR Call Drop Rate

Name WB AMR Call Drop Rate

Formula WB AMR Call Drop Rate = Number of abnormally released WB AMR callsx 100%/Total number of released WB AMR calls

Description This KPI provides the proportion of abnormally released WB AMR calls tothe total number of released WB AMR calls. It reflects the retainability ofWB AMR calls in an RNC or a cluster.When a fault occurs, the RNC sends the CN an IU RELEASE REQUEST orRAB RELEASE REQUEST message. The number of abnormally releasedWB AMR calls is measured in the best cell where the UE camps on when theRNC receives an IU RELEASE COMMAND or RAB ASSIGNMENTREQUEST message whose cause value is not "User Inactivity", "NormalRelease", "Successful Relocation", or "Network Optimization".

AssociatedCounters

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

Object CELL, RNC

Unit/Range %

Note None

6.6 VP Call Drop Ratio

Table 6-6 VP Call Drop Ratio

Name VP Call Drop Ratio

Formula



81

Description This KPI provides the ratio of the VP (Video Phone) RAB abnormal Releasesto the total VP RAB Releases (Normal Release + Abnormal Release) and isused to check the retainabililty of VP Service of the UTRAN (RNC orCluster).Description of RAB abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity","Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

VP Call Drop Ratio (Cell) =[VS.RAB.AbnormRel.CS64/(VS.RAB.AbnormRel.CS64+VS.RAB.NormRel.CS64)] x 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})] x 100%

Object CELL, RNC

Unit/Range %

Note None

6.7 AMR Traffic Drop Ratio

Table 6-7 AMR Traffic Drop Ratio

Name AMR Traffic Drop Ratio

Formula



82

Description This KPI provides the ratio of the AMR Service Erlang to the AMR RABAbnormal Releases, which indicates the AMR average Erlang per AMR calldrop 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 themeasurement period.Description of RAB abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity", "Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

l 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 ) x {SP}/60]/VS.RAB.AbnormRel.AMR

l 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 ) x {SP}/60]/(VS.RAB.AbnormRel.AMR.RNC)

Object CELL, RNC

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

Note None



83

6.8 VP Traffic Drop Ratio

Table 6-8 VP Traffic Drop Ratio

Name VP Traffic Drop Ratio

Formula

Description This KPI provides the ratio of the VP (Video Phone) Service Erlang to theVP RAB Abnormal Releases, which indicates the VP average Erlang per VPcall 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 measurementperiod.Description of RAB Abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception.If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENTREQUEST message with any one of the following information: "UserInactivity", "Normal Release", "Successful Relocation", "NetworkOptimization", the RNC measures the items according to the service types inthe best cell that the UE camps on if the released RABs belong to PS domain.

AssociatedCounters

VP Traffic Drop Ratio (Cell) =(VS.RB.CS.Conv.DL.64 x {SP}/60)/VS.RAB.AbnormRel.CS64VP Traffic Drop Ratio (RNC) =(VS.RB.CS.Conv.DL.64.RNC x {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 unitof minute

Note None

6.9 PS Call Drop Ratio

Table 6-9 PS Call Drop Ratio

Name PS Call Drop Ratio

Formula



84

Description This KPI provides the ratio of the PS RAB abnormal Releases to the totalPSRAB Releases (Normal Release + Abnormal Release) and is used to checkthe retainabililty of PS Service within the UTRAN (RNC or Cluster).Description of RAB Abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity", "Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

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

Object CELL, RNC

Unit/Range %

Note This KPI involves PS connection failures due to authentication failure duringCS security mode in the cell. You can subtract VS.RAB.AbnormRel.PS.Se-curity from the numerator of the formula to decrease the value of this KPI.

6.10 PS Call Drop Ratio (PCH)

Table 6-10 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 intoaccount.Since more and more smart phones camp on and keep Always Online in thenetwork, if the PCH transition is switched on while no data transferring fora period, these UEs usually transfer from connected state into Cell PCH stateinstead of Idle state, that is, the occasion of RAB normal release fortransferring into IDLE state will greatly decrease than that in the conditionswithout PCH transition.From user's point of view, the occasion of a UE transferring into PCH stateshould be considered as a normal RAB release for calculating the formula ofPS Call Drop Ratio.



85

AssociatedCounters

l PS Call Drop Ratio with PCH (Cell) =[(VS.RAB.AbnormRel.PS-VS.RAB.AbnormRel.PS.PCH -VS.RAB.AbnormRel.PS.D2P -VS.RAB.AbnormRel.PS.F2P ) /(VS.RAB.AbnormRel.PS+VS.RAB.NormRel.PS -VS.RAB.AbnormRel.PS.PCH -VS.RAB.NormRel.PS.PCH +VS.DCCC.D2P.Succ +VS.DCCC.Succ.F2P )] x 100%

l 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})] x 100%

Object CELL, RNC

Unit/Range %

Note The occasion of a UE transferring into PCH state should be considered as anormal RAB release for calculating the formula of PS Call Drop Ratio.Why VS.RAB.normRel.PS.PCH is subtracted in the denominator?l 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(orVS.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 levelKPI can be calculated approximately by aggregating all the cell level countersin the SRNC. Due to the counters are counted in the best cell of active set, Ifthe best cell for the PS RAB Establishment located in DRNC via Iur interface,this scenario is not taken into account in the formula.

6.11 PS R99 Call Drop Ratio



86

Table 6-11 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 totalPS R99RAB Releases (Normal Release + Abnormal Release) and is used tocheck the retainabililty of PS R99 Service within the UTRAN (RNC orCluster).Description of RAB Abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity", "Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

PS R99 Call Drop Ratio (Cell) =(VS.RAB.AbnormRel.PSR99)/(VS.RAB.AbnormRel.PSR99+VS.RAB.NormRel.PSR99) x 100%PS R99 Call Drop Ratio (RNC)=[VS.RAB.AbnormRel.PSR99+(VS.RAB.AbnormRel.PS.Conv.Iur+VS.RAB.AbnormRel.PS.Str.Iur+VS.RAB.AbnormRel.PS.BE.Iur-VS.RAB.AbnormRel.HSDPA.Iur)]/[VS.RAB.AbnormRel.PSR99+VS.RAB.NormRel.PSR99+(VS.RAB.NormRel.PS.Conv.Iur+VS.RAB.NormRel.PS.Str.Iur+VS.RAB.NormRel.PS.BE.Iur-VS.RAB.NormRel.HSDPA.Iur)+(VS.RAB.AbnormRel.PS.Conv.Iur+VS.RAB.AbnormRel.PS.Str.Iur+VS.RAB.AbnormRel.PS.BE.Iur-VS.RAB.AbnormRel.HSDPA.Iur)]*100%

Object CELL

Unit/Range %

Note This KPI involves the call drops of UEs in CELL_PCH, URA_PCH, orCELL_FACH state.



87

6.12 PS R99 Call Drop Ratio (PCH)

Table 6-12 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 intoaccount.

AssociatedCounters

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 )] x 100%

Object CELL

Unit/Range %

Note The occasion of a UE transferring out of PS R99 state (F2H, F2P, D2H) shouldbe considered as a normal RAB release for calculating the formula of PS R99Call Drop Ratio.RNC level KPI can be calculated approximately by aggregating all the celllevel counters in SRNC. Due to the counters are counted in the best cell ofactive set, If the best cell for the PS R99 RAB Establishment located in DRNCvia Iur interface, this scenario is not taken into account in the formula.VS.RAB.AbnormRel.PSR99 and VS.RAB.NormRel.PSR99 have alreadytaken PCH into account, the occasion of the RAB Normal/Abnormal Release(VS.RAB.AbnormRel.PS.PCH and VS.RAB.NormRel.PS.PCH) shouldbe excluded off the Denominator.

6.13 PS BE Call Drop Ratio



88

Table 6-13 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 totalPS BE RAB Releases (Normal Release + Abnormal Release) and is used tocheck 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 RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity", "Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

PS BE Call Drop Ratio (Cell) =[VS.RAB.AbnormRel.PS.BE/(VS.RAB.AbnormRel.PS.BE +VS.RAB.NormRel.PS.BE)] x 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} )] x 100%

Object CELL, RNC

Unit/Range %

Note RNC level KPI can be calculated approximately by aggregating all the Celland Iur level counters in SRNC.

6.14 HSDPA Call Drop Ratio

Table 6-14 HSDPA Call Drop Ratio

Name HSDPA Call Drop Ratio

Formula



89

Description This KPI provides the ratio of the HSDPA RAB abnormal Releases to thetotal HSDPARAB Releases (Normal Release+ Abnormal Release) and isused to check the retainabililty of HSDPA Service within the UTRAN (RNCor Cluster).Description of RAB Abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity", "Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

l 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 )] x 100%

l 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} )] x 100%

Object CELL, RNC

Unit/Range %

Note RNC level KPI is calculated approximately by aggregating all the Cell andIur level counters in SRNC.The successful channel transition is considered as normal HS-DSCH release(Including the transitions due to mobility).

6.15 HSDPA Call Drop Ratio (PCH)



90

Table 6-15 HSDPA Call Drop Ratio (PCH)

Name HSDPA Call Drop Ratio (PCH)

Formula

Description Compared with HSDPA Call Drop Ratio, this KPI takes the PCH state intoaccount.

AssociatedCounters

l 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 )] x 100%

l 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} )] x 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 theformula of PS HSDPA Call Drop Ratio.

6.16 HSUPA Call Drop Ratio



91

Table 6-16 HSUPA Call Drop Ratio

Name HSUPA Call Drop Ratio

Formula

Description This KPI provides the ratio of the HSUPA RAB abnormal Releases to thetotal HSUPARAB Releases (Normal Release + Abnormal Release) and isused to check the retainabililty of HSUPA Service of the UTRAN (RNC orCluster).Description of RAB Abnormal Release:The RNC initially sends an IU RELEASE REQUEST/RAB RELEASEREQUEST message to the CN due to exception. If the RNC receives an IURELEASE COMMAND/RAB ASSIGNMENT REQUEST message withany one of the following information: "User Inactivity", "Normal Release","Successful Relocation", "Network Optimization", the RNC measures theitems according to the service types in the best cell that the UE camps on ifthe released RABs belong to PS domain.

AssociatedCounters

l 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 )] x 100%

l 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})] x 100%

Object CELL, RNC

Unit/Range %

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



92

6.17 HSUPA Call Drop Ratio (PCH)

Table 6-17 HSUPA Call Drop Ratio (PCH)

Name HSUPA Call Drop Ratio (PCH)

Formula

Description Compared with HSUPA Call Drop Ratio, this KPI takes the PCH state intoaccount.

AssociatedCounters

l HSUPA Call Drop Ratio with PCH (Cell) =[(VS.HSUPA.RAB.AbnormRel-VS.HSUPA.RAB.AbnormRel.E2P )/(VS.HSUPA.RAB.AbnormRel+VS.HSUPA.RAB.NormRel +VS.HSUPA.HHO.E2D.SuccOutIntraFreq +VS.HSUPA.HHO.E2D.SuccOutInterFreq +VS.HSUPA.E2F.Succ +VS.HSUPA.E2D.Succ +VS.HSUPA.E2P.Succ )] x 100%

l 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} )] x 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 theformula of PS HSUPA Call Drop Ratio.



93

6.18 MBMS Service PTP drop Ratio

Table 6-18 MBMS Service PTP drop Ratio

Name MBMS Service PTP drop Ratio

Formula

AssociatedCounters

MBMS Service PTP Drop Ratio =[VS.MBMS.RB.PTP.Loss.Abnorm/(VS.MBMS.RB.PTP.Loss.Abnorm+ VS.MBMS.RB.PTP.Loss.norm)] x 100%

Object CELL

Unit/Range %

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



94

7 Service Integrity

About This Chapter

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

7.1 Average UL Throughput for PS R99 Service

7.2 Average DL Throughput for PS R99 Service

7.3 Average UL BLER for CS Service

7.4 Average UL BLER for PS Service

7.5 HSDPA Throughput

7.6 HSUPA Throughput

7.7 PS UL Throughput of RNC

7.8 PS DL Throughput of RNC

7.9 MBMS Service Throughput

RAN14.0KPI Reference 7 Service Integrity


95

7.1 Average UL Throughput for PS R99 Service

Table 7-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 servicesin 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 servicesare accumulated in the measurement period for the cells that are under theSRNC. At the end of the measurement period, the RNC divides the total bytesby the total data transfer time to obtain the Average UL Throughput for eachPS R99 Service.

AssociatedCounters

VS.PS.Bkg.Kbps.UL8VS.PS.Bkg.Kbps.UL16VS.PS.Bkg.Kbps.UL32VS.PS.Bkg.Kbps.UL64VS.PS.Bkg.Kbps.UL128VS.PS.Bkg.Kbps.UL144VS.PS.Bkg.Kbps.UL256VS.PS.Bkg.Kbps.UL384VS.PS.Int.Kbps.UL8VS.PS.Int.Kbps.UL16VS.PS.Int.Kbps.UL32VS.PS.Int.Kbps.UL64VS.PS.Int.Kbps.UL128VS.PS.Int.Kbps.UL144VS.PS.Int.Kbps.UL256VS.PS.Int.Kbps.UL384VS.PS.Str.Kbps.UL8VS.PS.Str.Kbps.UL16VS.PS.Str.Kbps.UL32VS.PS.Str.Kbps.UL64VS.PS.Str.Kbps.UL128VS.PS.Conv.Kbps.UL

Object CELL

Unit/Range Kbit/s

Note None



96

7.2 Average DL Throughput for PS R99 Service

Table 7-2 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 R99services 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 servicesare accumulated in the measurement period for the cells that are under theSRNC. At the end of the measurement period, the RNC divides the total bytesby the total data transfer time to obtain the Average DL Throughput for eachPS R99 Service.

AssociatedCounters

VS.PS.Bkg.Kbps.DL8VS.PS.Bkg.Kbps.DL16VS.PS.Bkg.Kbps.DL32VS.PS.Bkg.Kbps.DL64VS.PS.Bkg.Kbps.DL128VS.PS.Bkg.Kbps.DL144VS.PS.Bkg.Kbps.DL256VS.PS.Bkg.Kbps.DL384VS.PS.Int.Kbps.DL8VS.PS.Int.Kbps.DL16VS.PS.Int.Kbps.DL32VS.PS.Int.Kbps.DL64VS.PS.Int.Kbps.DL128VS.PS.Int.Kbps.DL144VS.PS.Int.Kbps.DL256VS.PS.Int.Kbps.DL384VS.PS.Str.Kbps.DL8VS.PS.Str.Kbps.DL16VS.PS.Str.Kbps.DL32VS.PS.Str.Kbps.DL64VS.PS.Str.Kbps.DL128VS.PS.Str.Kbps.DL144VS.PS.Str.Kbps.DL256VS.PS.Str.Kbps.DL384VS.PS.Conv.Kbps.DL



97

Object CELL

Unit/Range Kbit/s

Note None

7.3 Average UL BLER for CS Service

Table 7-3 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. serviceson the DCH in the best cell. The counters are triggered in the best cell whenthe number of UL TBs carrying the CS services on the DCH reaches thedefined sampling window (500 TBs).

AssociatedCounters

VS.ULBler.AMRVS.ULBler.CS64

Object CELL

Unit/Range %

Note None

7.4 Average UL BLER for PS Service

Table 7-4 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 bestcell.The counters are triggered in the best cell when the number of UL TBscarrying the PS services on the DCH reaches the defined sampling window(500 TBs).



98

AssociatedCounters

VS.ULBler.PS.BE.DCH.8VS.ULBler.PS.BE.DCH.16VS.ULBler.PS.BE.DCH.32VS.ULBler.PS.BE.DCH.64VS.ULBler.PS.BE.DCH.128VS.ULBler.PS.BE.DCH.144VS.ULBler.PS.BE.DCH.256VS.ULBler.PS.BE.DCH.384VS.ULBler.PS.BE.RACHVS.ULBler.PS.ConvVS.ULBler.PS.Str

Object CELL

Unit/Range %

Note None

7.5 HSDPA Throughput

Table 7-5 Mean Throughput for One HSDPA User

Name Mean Throughput for One HSDPA User

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

AssociatedCounters

VS.HSDPA.MeanChThroughput

Object CELL

Unit/Range Kbit/s

Note None

Table 7-6 Mean Throughput for One HSDPA Cell

Name Mean Throughput for One HSDPA Cell



99

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

AssociatedCounters

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 Throughputwithin RNC approximately:HSDPA Cell Throughput (RNC Cell) =VS.HSDPA.MeanChThroughput.TotalBytes x 8/[{SP} x 60]/1000Where:l {SP} is the Statistic Period with the unit of Minute.l The KPI may not be accurate under the following condition: there is no

HSDPA User transferring data for a while during the total measurementperiod. Therefore, the KPI should be evaluated during busy hour foraccuracy.

7.6 HSUPA Throughput

Table 7-7 Mean Throughput for One HSUPA User

Name Mean Throughput for One HSUPA User

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

AssociatedCounters

VS.HSUPA.MeanChThroughput

Object CELL

Unit/Range Kbit/s

Note None

Table 7-8 Mean Throughput for One HSUPA Cell

Name Mean Throughput for One HSUPA Cell



100

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

AssociatedCounters

VS.HSUPA.MeanBitRate.WithData

Object NodeB

Unit/Range Kbit/s

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

7.7 PS UL Throughput of RNC

Table 7-9 PS UL Throughput of RNC

Name PS UL Throughput of RNC



101

Description This measurement item provides the Average or Max uplink throughput forPS services within an RNC.l Measurement point for Average UL Throughput

The RNC periodically samples the uplink traffic values of the related PSservices in the PS domain. At the end of the measurement period, the RNCdivides the accumulated values by the number of samples to obtain themean uplink traffic of all the PS services in the PS domain. The uplinktraffic of all the PS services in the PS domain refers to the traffic obtainedat the RLC layer. The data does not include the RLC head data.

l Measurement point for Max UL ThroughputThe RNC periodically samples uplink traffic values of all the related PSservices in the PS domain. At the end of the measurement period, the RNCcalculates the maximum uplink traffic of all the services in the PS domainwithin the RNC. The uplink traffic of all the services in the PS domainrefers to the traffic obtained at the RLC layer. The data does not includethe RLC head data.

AssociatedCounters

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

Object RNC

Unit/Range kbit/s

Note None

7.8 PS DL Throughput of RNC

Table 7-10 PS DL Throughput of RNC

Name PS DL Throughput of RNC



102

Description These counters provide the Average or Max downlink throughput for PSservices within an RNC.l Measurement point for Average DL Throughput

The RNC periodically samples the downlink traffic values of the relatedPS services in the PS domain. At the end of the measurement period, theRNC divides the accumulated values by the number of samples to obtainthe mean downlink traffic of all the PS services in the PS domain. Thedownlink traffic of all the PS services in the PS domain refers to the trafficobtained at the RLC layer. The data does not include the RLC head data.

l Measurement point for Max DL ThroughputThe RNC periodically samples the downlink traffic values of all therelated PS services in the PS domain. At the end of the measurementperiod, the RNC calculates the maximum downlink traffic of all theservices in the PS domain within the RNC. The downlink traffic of all theservices in the PS domain refers to the traffic obtained at the RLC layer.The data does not include the RLC head data.

AssociatedCounters

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

Object RNC

Unit/Range kbit/s

Note None

7.9 MBMS Service Throughput

Table 7-11 MBMS Service Throughput

Name MBMS Service Throughput

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

AssociatedCounters

VS.MBMS.PTM.MeanThroughputVS.MBMS.PTP.MeanThroughput

Object CELL

Unit/Range kbit/s

Note None



103

8 Traffic

About This Chapter

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

8.1 CS Equivalent Erlang of RNC

8.2 Number of CS Users

8.3 Number of PS R99 Users

8.4 Number of HSDPA Users

8.5 Number of HSUPA Users

8.6 Number of E-FACH Users

8.7 Number of CS Over HSPA Users

8.8 Number of HSDPA 64QAM Users

8.9 Number of HSDPA MIMO Users

8.10 Number of HSUPA 16QAM users

8.11 Number of HSDPA MIMO64QAM Users

8.12 Number of MBMS Users

8.13 HSDPA RLC Traffic Volume

8.14 HSUPA RLC Traffic Volume

8.15 R99 Service UL Traffic Volume

8.16 R99 Service DL Traffic Volume

8.17 E-FACH Traffic Volume

RAN14.0KPI Reference 8 Traffic


104

8.1 CS Equivalent Erlang of RNC

Table 8-1 CS Equivalent Erlang of RNC

Name CS Equivalent Erlang of RNC

Description VS.CSLoad.Erlang.Equiv.RNCThis KPI provides the equivalent Erlang values of all the services in the CSdomain in the RNC.The RNC periodically takes the samples from the equivalent Erlang valuesof all the services in the CS domain. At the end of the measurement period,the RNC divides the accumulated equivalent Erlang values by the numberof samples to obtain the mean equivalent Erlang values of all the servicesin the CS domain.Each time a CS domain service is established, the RNC converts its rate tothe equivalent Erlang, and then increases the equivalent Erlang of the CSdomain in the current RNC.Each time a CS domain service is released, the RNC converts its rate to theequivalent Erlang and decreases the equivalent Erlang of the CS domain inthe current RNC.VS.CSLoad.MaxErlang.Equiv.RNCThis KPI provides the maximum equivalent Erlang values of all the servicesin the CS domain within the RNC.The RNC periodically takes a sample from the equivalent Erlang values ofall the services in the CS domain. At the end of the period, the RNCcalculates the maximum equivalent Erlang of all the services in the CSdomain within the RNC.Each time a CS domain service is established, the RNC converts its rate tothe equivalent Erlang, and then increases the equivalent Erlang of the CSdomain in the current RNC.Each time a CS domain service is released, the RNC decreases theequivalent Erlang of the CS domain in the current RNC.

AssociatedCounters

VS.CSLoad.Erlang.Equiv.RNCVS.CSLoad.MaxErlang.Equiv.RNC

Object RNC

Unit/Range Erl

Note None

8.2 Number of CS Users



105

Table 8-2 Number of CS Users

Name Number of CS Users

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

AssociatedCounters

l 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.64l 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, the counter value should bemultiplied by {SP}/60, where {SP} is the measurement period (unit: minute).For a VP service, V1 platform equals to four Erlangs and V2 platform equalsto two Erlangs.

8.3 Number of PS R99 Users



106

Table 8-3 Number of PS R99 Users

Name Number of PS R99 Users

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



107

AssociatedCounters

Cell Levell UL Counters:

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

l DL Counters:VS.RB.PS.Bkg.DL.8VS.RB.PS.Bkg.DL.16VS.RB.PS.Bkg.DL.32VS.RB.PS.Bkg.DL.64VS.RB.PS.Bkg.DL.128VS.RB.PS.Bkg.DL.144VS.RB.PS.Bkg.DL.256VS.RB.PS.Bkg.DL.384VS.RB.PS.Int.DL.8



108

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

RNC Countersl UL Counters:

VS.RB.PS.Bkg.UL.8.RNCVS.RB.PS.Bkg.UL.16.RNCVS.RB.PS.Bkg.UL.32.RNCVS.RB.PS.Bkg.UL.64.RNCVS.RB.PS.Bkg.UL.128.RNCVS.RB.PS.Bkg.UL.144.RNCVS.RB.PS.Bkg.UL.256.RNCVS.RB.PS.Bkg.UL.384.RNCVS.RB.PS.Int.UL.8.RNCVS.RB.PS.Int.UL.16.RNCVS.RB.PS.Int.UL.32.RNCVS.RB.PS.Int.UL.64.RNCVS.RB.PS.Int.UL.128.RNCVS.RB.PS.Int.UL.144.RNCVS.RB.PS.Int.UL.256.RNCVS.RB.PS.Int.UL.384.RNCVS.RB.PS.Str.UL.8.RNCVS.RB.PS.Str.UL.16.RNCVS.RB.PS.Str.UL.32.RNC



109

VS.RB.PS.Str.UL.64.RNCVS.RB.PS.Str.UL.128.RNCVS.RB.PS.Str.UL.144.RNCVS.RB.PS.Str.UL.256.384.RNCVS.RB.PS.Conv.UL.8.RNCVS.RB.PS.Conv.UL.16.RNCVS.RB.PS.Conv.UL.32.RNCVS.RB.PS.Conv.UL.64.RNCVS.RB.PS.Conv.UL.38.8.RNCVS.RB.PS.Conv.UL.42.8.RNCVS.RB.PS.Conv.UL.40.RNCVS.RB.PS.Conv.UL.39.2.RNC

l DL Counters:VS.RB.PS.Bkg.DL.8.RNCVS.RB.PS.Bkg.DL.16.RNCVS.RB.PS.Bkg.DL.32.RNCVS.RB.PS.Bkg.DL.64.RNCVS.RB.PS.Bkg.DL.128.RNCVS.RB.PS.Bkg.DL.144.RNCVS.RB.PS.Bkg.DL.256.RNCVS.RB.PS.Bkg.DL.384.RNCVS.RB.PS.Int.DL.8.RNCVS.RB.PS.Int.DL.16.RNCVS.RB.PS.Int.DL.32.RNCVS.RB.PS.Int.DL.64.RNCVS.RB.PS.Int.DL.128.RNCVS.RB.PS.Int.DL.144.RNCVS.RB.PS.Int.DL.256.RNCVS.RB.PS.Int.DL.384.RNCVS.RB.PS.Str.DL.8.RNCVS.RB.PS.Str.DL.16.RNCVS.RB.PS.Str.DL.32.RNCVS.RB.PS.Str.DL.64.RNCVS.RB.PS.Str.DL.128.RNCVS.RB.PS.Str.DL.144.RNCVS.RB.PS.Str.DL.256.384.RNCVS.RB.PS.Conv.DL.8.RNCVS.RB.PS.Conv.DL.16.RNCVS.RB.PS.Conv.DL.32.RNCVS.RB.PS.Conv.DL.64.RNC



110

VS.RB.PS.Conv.DL.42.8.RNCVS.RB.PS.Conv.DL.40.RNCVS.RB.PS.Conv.DL.39.2.RNCVS.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;

8.4 Number of HSDPA Users

Table 8-4 Number of HSDPA Users

Name Number of HSDPA Users

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

AssociatedCounters

VS.HSDPA.UE.Mean.CellVS.HSDPA.UE.Max.Cell

Object CELL

Unit/Range None

Note None

8.5 Number of HSUPA Users

Table 8-5 Number of HSUPA Users

Name Number of HSUPA Users

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



111

AssociatedCounters

VS.HSUPA.UE.Mean.CellVS.HSUPA.UE.Max.Cell

Object CELL

Unit/Range None

Note The KPI should be collected during busy hour.

8.6 Number of E-FACH Users

Table 8-6 Number of E-FACH Users

Name Mean Number of E-FACH Users

Description This KPI provides the average number of UEs that are carried on the E-FACHin the cellThe system periodically samples the UEs that are carried on the EFACH. Atthe end of the measurement period, the average number of UEs that are carriedon the E-FACH in the measurement period is obtained by dividing theaccumulated value of sample data in the period by the number of samples.

AssociatedCounters

VS.EFACHUEs

Object CELL

Unit/Range None


8.7 Number of CS Over HSPA Users

Table 8-7 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 endof a statistical period, the system divides the sampling number by the sum ateach sampling point to obtain the average number of CS Over HSPA duringthe period.

AssociatedCounters

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

Object CELL



112

Unit/Range None


8.8 Number of HSDPA 64QAM Users

Table 8-8 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 HSDPAcell.The number of HSDPA 64QAM UEs is sampled periodically in the HSDPAcells. At the end of the measurement period, the RNC divides the accumulatedtime weight value of each sampling point by the sampling period, thusobtaining the average number of 64QAM UEs in the HSDPA cell.

AssociatedCounters

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

Object CELL

Unit/Range None


8.9 Number of HSDPA MIMO Users

Table 8-9 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 HSDPAcell.The number of HSDPA MIMO UEs is sampled periodically in the HSDPAcells. At the end of the measurement period, the RNC divides the accumulatedtime weight value of each sampling point by the sampling period, thusobtaining the average number of MIMO UEs in the HSDPA cell.

AssociatedCounters

VS.HSDPA.MIMO.UE.Mean.Cell

Object CELL

Unit/Range None




113

8.10 Number of HSUPA 16QAM users

Table 8-10 Number of HSUPA 16QAM users

Name Mean Number of HSUPA 16QAM users

Description This KPI provides the average number of HSUPA 16QAM UEs in an HSUPAcell.The number of HSUPA 16QAM UEs is sampled periodically in the HSUPAcells. At the end of the measurement period, the RNC divides the accumulatedtime weight value of each sampling point by the sampling period, thusobtaining the average number of 16QAM UEs in the HSUPA cell.

AssociatedCounters

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

Object CELL

Unit/Range None


8.11 Number of HSDPA MIMO64QAM Users

Table 8-11 Number of HSDPA MIMO64QAM Users

Name Mean Number of HSDPA MIMO64QAM Users

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

AssociatedCounters

VS.HSDPA.MIMO64QAM.UE.Mean.Cell

Object CELL

Unit/Range None


8.12 Number of MBMS Users



114

Table 8-12 Number of MBMS Users

Name Mean Number of MBMS Users

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

AssociatedCounters

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

Object CELL

Unit/Range None


8.13 HSDPA RLC Traffic Volume

Table 8-13 HSDPA RLC Traffic Volume

Name HSDPA RLC Traffic Volume

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

AssociatedCounters

VS.HSDPA.MeanChThroughput.TotalBytes

Object CELL

Unit/Range byte



115

Note None

8.14 HSUPA RLC Traffic Volume

Table 8-14 HSUPA RLC Traffic Volume

Name HSUPA RLC Traffic Volume

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

AssociatedCounters

VS.HSUPA.MeanChThroughput.TotalBytes

Object CELL

Unit/Range byte

Note None

8.15 R99 Service UL Traffic Volume

Table 8-15 R99 Service UL Traffic Volume

Name R99 Service UL Traffic Volume

Description These KPIs provide the uplink traffic volume of different R99 services in allcells 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 cellsof the active set within SRNC.



116

AssociatedCounters

l CS Domain:(VS.RB.AMR.UL.12.2 x 12200 +VS.RB.AMR.UL.10.2 x 10200 +VS.RB.AMR.UL.7.95 x 7950 +VS.RB.AMR.UL.7.4 x 7400 +VS.RB.AMR.UL.5.9 x 5900 +VS.RB.AMR.UL.5.15 x 5150 +VS.RB.AMR.UL.4.75 x 4750) x {SP} x 60

l PS Domain:VS.PS.Bkg.UL.8.TrafficVS.PS.Bkg.UL.16.TrafficVS.PS.Bkg.UL.32.TrafficVS.PS.Bkg.UL.64.TrafficVS.PS.Bkg.UL.128.TrafficVS.PS.Bkg.UL.144.TrafficVS.PS.Bkg.UL.256.TrafficVS.PS.Bkg.UL.384.TrafficVS.PS.Int.UL.8.TrafficVS.PS.Int.UL.16.TrafficVS.PS.Int.UL.32.TrafficVS.PS.Int.UL.64.TrafficVS.PS.Int.UL.128.TrafficVS.PS.Int.UL.144.TrafficVS.PS.Int.UL.256.TrafficVS.PS.Int.UL.384.TrafficVS.PS.Str.UL.8.TrafficVS.PS.Str.UL.16.TrafficVS.PS.Str.UL.32.TrafficVS.PS.Str.UL.64.TrafficVS.PS.Str.UL.128.TrafficVS.PS.Conv.UL.Traffic

Object CELL

Unit/Range bit

Note None

8.16 R99 Service DL Traffic Volume



117

Table 8-16 R99 Service DL Traffic Volume

Name R99 Service DL Traffic Volume

Description These KPIs provide the downlink traffic volume of different R99 services inall 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 cellsof the active set within SRNC.



118

AssociatedCounters

l CS Domain:(VS.RB.AMR.DL.12.2 x 12200 +VS.RB.AMR.DL.10.2 x 10200 +VS.RB.AMR.DL.7.95 x 7950 +VS.RB.AMR.DL.7.4 x 7400 +VS.RB.AMR.DL.5.9 x 5900 +VS.RB.AMR.DL.5.15 x 5150 +VS.RB.AMR.DL.4.75 x 4750) x {SP} x 60VS.CS.Conv.DL.64.TrafficVS.CS.Str.DL.57.6.Traffic

l PS Domain:VS.PS.Bkg.DL.8.TrafficVS.PS.Bkg.DL.16.TrafficVS.PS.Bkg.DL.32.TrafficVS.PS.Bkg.DL.64.TrafficVS.PS.Bkg.DL.128.TrafficVS.PS.Bkg.DL.144.TrafficVS.PS.Bkg.DL.256.TrafficVS.PS.Bkg.DL.384.TrafficVS.PS.Int.DL.8.TrafficVS.PS.Int.DL.16.TrafficVS.PS.Int.DL.32.TrafficVS.PS.Int.DL.64.TrafficVS.PS.Int.DL.128.TrafficVS.PS.Int.DL.144.TrafficVS.PS.Int.DL.256.TrafficVS.PS.Int.DL.384.TrafficVS.PS.Str.DL.8.TrafficVS.PS.Str.DL.16.TrafficVS.PS.Str.DL.32.TrafficVS.PS.Str.DL.64.TrafficVS.PS.Str.DL.128.TrafficVS.PS.Str.DL.144.TrafficVS.PS.Str.DL.256.TrafficVS.PS.Str.DL.384.TrafficVS.PS.Conv.DL.Traffic

Object CELL

Unit/Range bit

Note None



119

8.17 E-FACH Traffic Volume

Table 8-17 E-FACH Traffic Volume

Name E-FACH Traffic Volume

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

AssociatedCounters

VS.CRNCIubBytesEFACH.Tx

Object CELL

Unit/Range byte

Note None



120

ran14.0 kpi reference(02)(pdf)-en

Documents

frequency

primary mouse

object unitrange

channel switch

switch channel

released rabs

frequency

transport