Huawei RAN14 Kpi Reference-English

RAN14.0

KPI Reference

Issue 01Date 2012-04-26

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.comEmail: [email protected]

Issue 01 (2012-04-26) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

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 VersionBSC6900 V900R014C00NodeB V100R014NodeB V200R014

Intended AudienceThis document is intended for:l Network planning engineersl Field engineersl System engineers

Organization1 Changes in the RAN KPI ReferenceThis chapter describes the changes made in the RAN KPI Reference.2 AccessibilityAccessibility 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 AvailabilityAvailability KPIs mainly indicate the utilization for several kinds of network resources such asRadio, bandwidth or CPU Load.4 CoverageCoverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in anRNC or a cluster.5 MobilityMobility KPIs are used to monitor the successful ratio for several kinds of handover features orservice mode changing in difference scenarios.6 RetainabilityRetainability 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 IntegrityService 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 TrafficTraffic-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 ConventionsThe symbols that may be found in this document are defined as follows.

Symbol DescriptionIndicates 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 ConventionsThe general conventions that may be found in this document are defined as follows.

Convention DescriptionTimes New Roman Normal paragraphs are in Times New Roman.Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.Italic Book titles are in italics.Courier New Examples of information displayed on the screen are in

Courier New.

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

Convention DescriptionBoldface 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 by

vertical bars. One item is selected.[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.{ x | y | ... }* Optional items are grouped in braces and separated by

vertical 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 ConventionsThe GUI conventions that may be found in this document are defined as follows.

Convention DescriptionBoldface Buttons, menus, parameters, tabs, window, and dialog titles

are 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 OperationsThe keyboard operations that may be found in this document are defined as follows.

Format DescriptionKey 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 means

the two keys should be pressed in turn.

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

Action DescriptionClick Select and release the primary mouse button without moving

the pointer.Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.Drag Press and hold the primary mouse button and move the

pointer to a certain position.



v

Contents

About This Document.....................................................................................................................ii1 Changes in the RAN KPI Reference..........................................................................................12 Accessibility....................................................................................................................................4

2.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 Bandwidth Utilizing Ratio (UL)...............................................................................................................363.8 IUB Bandwidth Utilizing Ratio (DL)...............................................................................................................373.9 Cell Unavailability duration.............................................................................................................................393.10 HSDPA Unavailability duration.....................................................................................................................393.11 HSUPA Unavailability duration.....................................................................................................................393.12 CE Consumption for a NodeB Cell................................................................................................................403.13 Hardware Configured CE for a NodeB..........................................................................................................403.14 Shared Group Configured License CE for a NodeB......................................................................................413.15 Shared Group License CE Consumption for a NodeB...................................................................................413.16 License Group Configured CE for a NodeB..................................................................................................423.17 License Group CE Consumption for a NodeB...............................................................................................423.18 RTWP (Received Total Wideband Power).....................................................................................................433.19 TCP (Transmitted Carrier Power)..................................................................................................................443.20 R99 Code Utilization......................................................................................................................................443.21 Number of Codes Used by HS-PDSCHs........................................................................................................453.22 HSDPA Efficiency.........................................................................................................................................45

4 Coverage........................................................................................................................................474.1 UL Interference Cell Ratio...............................................................................................................................484.2 Soft Handover Overhead..................................................................................................................................48

5 Mobility.........................................................................................................................................515.1 Soft Handover Success Ratio...........................................................................................................................535.2 Softer Handover Success Ratio........................................................................................................................535.3 AMR Soft Handover Success Ratio.................................................................................................................545.4 CS64 Soft Handover Success Ratio..................................................................................................................555.5 PS Soft Handover Success Ratio......................................................................................................................555.6 Intra-frequency Hard Handover Success Ratio................................................................................................565.7 Inter-frequency Hard Handover Success Ratio................................................................................................575.8 Service Cell Change Success Ratio with SHO (H2H).....................................................................................575.9 H2H Intra-Frequency Hard Handover Success Ratio.......................................................................................585.10 H2H Inter-Frequency Hard Handover Success Ratio.....................................................................................595.11 H2D Inter-frequency Hard Handover Success Ratio......................................................................................605.12 H2D Intra-Frequency Hard Handover Success Ratio.....................................................................................615.13 E2D Intra-Frequency Hard Handover Success Ratio.....................................................................................625.14 H2D Channel Switch Success Ratio...............................................................................................................635.15 D2H Channel Switch Success Ratio...............................................................................................................645.16 CS W2G Inter-RAT Handover Out Success Ratio.........................................................................................645.17 PS W2G Inter-RAT Handover Out Success Ratio.........................................................................................655.18 PS G2W Inter-RAT Handover In Success Ratio............................................................................................66



vii

5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio................................................................................675.20 SRNC Relocation Success Ratio....................................................................................................................675.21 TRNC Relocation Success Ratio....................................................................................................................685.22 E-DCH Soft Handover Success Ratio............................................................................................................695.23 E-DCH Cell Change Success Ratio with SHO...............................................................................................705.24 E-DCH Cell Change Success Ratio with Inter-HHO.....................................................................................715.25 E2D Channel Switch Success Ratio...............................................................................................................725.26 D2E Channel Switch Success Ratio...............................................................................................................735.27 E2D Handover Success Ratio with Inter HHO..............................................................................................745.28 HSUPA W2G Inter-RAT Handover Out Success Ratio................................................................................745.29 MBMS Service Mode Switch Success Ratio.................................................................................................755.30 CS Inter-Frequency Hard Handover Success Rate.........................................................................................765.31 PS Inter-Frequency Hard Handover Success Rate.........................................................................................77

6 Retainability.................................................................................................................................786.1 CS Service Drop Ratio.....................................................................................................................................796.2 CS Call Drop Rate in CS+PS Combined Services...........................................................................................796.3 PS Call Drop Rate in CS+PS Combined Services............................................................................................806.4 AMR Call Drop Ratio.......................................................................................................................................816.5 WB AMR Call Drop Rate................................................................................................................................816.6 VP Call Drop Ratio...........................................................................................................................................826.7 AMR Traffic Drop Ratio..................................................................................................................................836.8 VP Traffic Drop Ratio......................................................................................................................................856.9 PS Call Drop Ratio...........................................................................................................................................856.10 PS Call Drop Ratio (PCH)..............................................................................................................................866.11 PS R99 Call Drop Ratio..................................................................................................................................876.12 PS R99 Call Drop Ratio (PCH)......................................................................................................................896.13 PS BE Call Drop Ratio...................................................................................................................................896.14 HSDPA Call Drop Ratio.................................................................................................................................906.15 HSDPA Call Drop Ratio (PCH).....................................................................................................................916.16 HSUPA Call Drop Ratio.................................................................................................................................926.17 HSUPA Call Drop Ratio (PCH).....................................................................................................................946.18 MBMS Service PTP drop Ratio.....................................................................................................................95

7 Service Integrity...........................................................................................................................967.1 Average UL Throughput for PS R99 Service...................................................................................................977.2 Average DL Throughput for PS R99 Service...................................................................................................987.3 Average UL BLER for CS Service...................................................................................................................997.4 Average UL BLER for PS Service...................................................................................................................997.5 HSDPA Throughput.......................................................................................................................................1007.6 HSUPA Throughput.......................................................................................................................................1017.7 PS UL Throughput of RNC............................................................................................................................1027.8 PS DL Throughput of RNC............................................................................................................................1037.9 MBMS Service Throughput...........................................................................................................................104



viii

8 Traffic...........................................................................................................................................1058.1 CS Equivalent Erlang of RNC........................................................................................................................1068.2 Number of CS Users.......................................................................................................................................1068.3 Number of PS R99 Users................................................................................................................................1078.4 Number of HSDPA Users...............................................................................................................................1128.5 Number of HSUPA Users...............................................................................................................................1128.6 Number of E-FACH Users.............................................................................................................................1138.7 Number of CS Over HSPA Users...................................................................................................................1138.8 Number of HSDPA 64QAM Users................................................................................................................1148.9 Number of HSDPA MIMO Users..................................................................................................................1148.10 Number of HSUPA 16QAM users...............................................................................................................1158.11 Number of HSDPA MIMO64QAM Users...................................................................................................1158.12 Number of MBMS Users..............................................................................................................................1158.13 HSDPA RLC Traffic Volume......................................................................................................................1168.14 HSUPA RLC Traffic Volume......................................................................................................................1178.15 R99 Service UL Traffic Volume..................................................................................................................1178.16 R99 Service DL Traffic Volume..................................................................................................................1188.17 E-FACH Traffic Volume..............................................................................................................................121



ix

1 Changes in the RAN KPI ReferenceThis chapter describes the changes made in the RAN KPI Reference.

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 Ratel 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 ServicesCompared with issue 02 (2011-08-31) of RAN13.0, this issue incorporates the followingchanges:

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


1

Content Description5.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.

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



2

Content Description3.8 IUB Bandwidth Utilizing Ratio(DL)3.7 IUB Bandwidth Utilizing 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 AccessibilityAbout 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 Ratio2.2 RRC Setup Success Ratio2.3 Radio Access Success Ratio2.4 PS Radio Access Success Ratio2.5 CS Radio Access Success Ratio2.6 AMR RAB Setup Success Ratio2.7 VP RAB Setup Success Ratio2.8 CS RAB Setup Success Ratio2.9 CS+PS Combined Service RAB Setup Success Rate2.10 PS+PS Combined Service RAB Setup Success Rate2.11 PS RAB Setup Success Ratio2.12 HSDPA RAB Setup Success Ratio2.13 HSUPA RAB Setup Success Ratio2.14 PS E-FACH RAB Setup Success Ratio2.15 CS over HSPA RAB Setup Success Ratio2.16 HSDPA 64QAM RAB Setup Success Ratio2.17 HSDPA MIMO RAB Setup Success Ratio2.18 HSDPA DC RAB Setup Success Ratio2.19 HSDPA MIMO64QAM RAB Setup Success Ratio

RAN14.0KPI Reference 2 Accessibility


4

2.20 PTM Channel Setup Success Ratio2.21 PTP Channel Setup Success Ratio2.22 RRC Congestion Ratio2.23 CS RAB Congestion Ratio2.24 PS RAB Congestion Ratio2.25 PS R99 RAB Setup Success Rate2.26 WB AMR RAB Setup Success Rate



5

2.1 IU Paging Success RatioTable 2-1 IU Paging Success Ratio

Name IU Paging Success RatioFormula

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 RNCUnit/Range %Note None

2.2 RRC Setup Success RatioTable 2-2 RRC Setup Success Ratio

Name RRC Setup Success RatioFormula



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 CELLUnit/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 RatioTable 2-3 Radio Access Success Ratio

Name Radio Access Success RatioFormula



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, RNCUnit/Range %Note None

2.4 PS Radio Access Success RatioTable 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%


2.5 CS Radio Access Success Ratio



12

Table 2-5 CS Radio Access Success RatioName CS Radio Access Success RatioFormula

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,RNCUnit/Range %Note None

2.6 AMR RAB Setup Success Ratio

Table 2-6 AMR RAB Setup Success RatioName 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 CELLUnit/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 RatioName VP RAB Setup Success RatioFormula

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%


2.8 CS RAB Setup Success RatioTable 2-8 CS RAB Setup Success Ratio

Name CS RAB Setup Success RatioFormula

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, RNCUnit/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 RateTable 2-9 CS+PS Combined Service RAB Setup Success Rate

Name CS+PS Combined Service RAB Setup Success RateFormula CS+PS Combined Service RAB Setup Success Rate = Number of

successfully 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 CELLUnit/Range %Note None

2.10 PS+PS Combined Service RAB Setup Success Rate



16

Table 2-10 PS+PS Combined Service RAB Setup Success RateName PS+PS Combined Service RAB Setup Success RateFormula PS+PS Combined Service RAB Setup Success Rate = Number of

successfully 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%


2.11 PS RAB Setup Success RatioTable 2-11 PS RAB Setup Success Ratio

Name PS RAB Setup Success RatioFormula



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%


2.12 HSDPA RAB Setup Success RatioTable 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%


2.13 HSUPA RAB Setup Success Ratio

Table 2-13 HSUPA RAB Setup Success RatioName HSUPA RAB Setup Success RatioFormula

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 %Note The RNC level KPI is calculated by aggregating all the cell counters.

2.14 PS E-FACH RAB Setup Success RatioTable 2-14 PS E-FACH RAB Setup Success Ratio

Name PS E-FACH RAB Setup Success RatioFormula

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 %Note The RNC level KPI is calculated by aggregating all the cell counters.

2.15 CS over HSPA RAB Setup Success RatioTable 2-15 CS over HSPA RAB Setup Success Ratio

Name CS over HSPA RAB Setup Success RatioFormula



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%


2.16 HSDPA 64QAM RAB Setup Success Ratio

Table 2-16 HSDPA 64QAM RAB Setup Success RatioName HSDPA 64QAM RAB Setup Success RatioFormula

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 CELLUnit/Range %



21

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

2.17 HSDPA MIMO RAB Setup Success RatioTable 2-17 HSDPA MIMO RAB Setup Success Ratio

Name HSDPA MIMO RAB Setup Success RatioFormula

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%


2.18 HSDPA DC RAB Setup Success RatioTable 2-18 HSDPA DC RAB Setup Success Ratio

Name HSDPA DC RAB Setup Success RatioFormula



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%


2.19 HSDPA MIMO64QAM RAB Setup Success RatioTable 2-19 HSDPA MIMO64QAM RAB Setup Success Ratio

Name HSDPA MIMO64QAM RAB Setup Success RatioFormula

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 CELLUnit/Range %



23

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

2.20 PTM Channel Setup Success RatioTable 2-20 PTM Channel Setup Success Ratio

Name PTM Channel Setup Success RatioFormula

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%


2.21 PTP Channel Setup Success RatioTable 2-21 PTP Channel Setup Success Ratio

Name PTP Channel Setup Success RatioFormula



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%


2.22 RRC Congestion RatioTable 2-22 RRC Congestion Ratio

Name RRC Congestion RatioFormula

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


2.23 CS RAB Congestion RatioTable 2-23 CS RAB Congestion Ratio

Name CS RAB Congestion RatioFormula

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%




26

2.24 PS RAB Congestion Ratio

Table 2-24 PS RAB Congestion RatioName PS RAB Congestion RatioFormula

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%




27

2.25 PS R99 RAB Setup Success Rate

Table 2-25 PS R99 RAB Setup Success RateName PS R99 RAB Setup Success RateFormula PS R99 RAB Setup Success Rate = Number of successfully set up PS R99

RABs x 100%/Number of PS R99 RAB setup attemptsDescription 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%


2.26 WB AMR RAB Setup Success Rate

Table 2-26 WB AMR RAB Setup Success RateName WB AMR RAB Setup Success RateFormula WB AMR RAB Setup Success Rate = Number of successfully set up WB

AMR RABs x 100%/Number of WB AMR RAB setup attemptsDescription 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%




29

3 AvailabilityAbout This Chapter

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

3.1 Worst Cell Ratio3.2 Paging Congestion Ratio3.3 Call Admission Refused Ratio3.4 Congested Cell Ratio3.5 Radio Network Unavailability Ratio3.6 Average CPU Load3.7 IUB Bandwidth Utilizing Ratio (UL)3.8 IUB Bandwidth Utilizing Ratio (DL)3.9 Cell Unavailability duration3.10 HSDPA Unavailability duration3.11 HSUPA Unavailability duration3.12 CE Consumption for a NodeB Cell3.13 Hardware Configured CE for a NodeB3.14 Shared Group Configured License CE for a NodeB3.15 Shared Group License CE Consumption for a NodeB3.16 License Group Configured CE for a NodeB3.17 License Group CE Consumption for a NodeB3.18 RTWP (Received Total Wideband Power)3.19 TCP (Transmitted Carrier Power)

RAN14.0KPI Reference 3 Availability


30

3.20 R99 Code Utilization3.21 Number of Codes Used by HS-PDSCHs3.22 HSDPA Efficiency



31

3.1 Worst Cell RatioTable 3-1 Worst Cell Ratio

Name Worst Cell RatioFormula

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 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 CELLUnit/Range %Note 95% and 3% are the values obtained based on the references from the

commercial network with the condition of that the traffic of AMR voice andvideo call is greater than 0.1 Erlang.

3.2 Paging Congestion RatioTable 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, CELLUnit/Range %Note None

3.3 Call Admission Refused Ratio



33

Table 3-3 Call Admission Refused RatioName Call Admission Refused RatioFormula

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%


3.4 Congested Cell RatioTable 3-4 Congested Cell Ratio

Name Congested Cell RatioFormula

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 CELLUnit/Range %Note The number of congested cells is calculated by aggregating the cells that are

congested in DL or UL directions during busy hours.

3.5 Radio Network Unavailability RatioTable 3-5 Radio Network Unavailability Ratio

Name Radio Network Unavailability RatioFormula

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 CELLUnit/Range %Note The unit of {SP}(Statistic Period): Minute

3.6 Average CPU LoadTable 3-6 Average CPU Load

Name Average CPU Load



35

Formula Average CPU Load = XPU usage of the XPU in the measurement periodDescription This KPI provides the CPU usage of the XPU in a measurement period. It

also indicates the load and operating performance of CPU on the XPU in themeasurement period.The CPU usage of the XPU is accumulated every second in the measurementperiod.

AssociatedCounters

Average CPU Load= VS.XPU.CPULOAD.MEAN

Object XPUUnit/Range %Note Mean CPU Utility is the CPU average load showed in percentage.

3.7 IUB Bandwidth Utilizing Ratio (UL)Table 3-7 IUB Bandwidth Utilizing Ratio (UL)

Name IUB Bandwidth Utilizing Ratio (UL)Formula

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



36

AssociatedCounters

l IUB Bandwidth Utilizing Ratio (ATM_UL) =[(VS.ATMUlAvgUsed.1+VS.ATMUlAvgUsed.2+VS.ATMUlAvgUsed.3+VS.ATMUlAvgUsed.4)/(VS.ATMUlTotal.1+VS.ATMUlTotal.2+VS.ATMUlTotal.3+VS.ATMUlTotal.4)] x 100%

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

Object NodeBUnit/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 the physicalbandwidths of ports rather than the actual available bandwidths of ports.Therefore, if the actual available bandwidth of a port is different from thephysical bandwidth of the port, the value of this KPI calculated by using thisformula is incorrect, and you are advised to use the actual availablebandwidths as the denominator to calculate this KPI.

3.8 IUB Bandwidth Utilizing Ratio (DL)Table 3-8 IUB Bandwidth Utilizing Ratio (DL)

Name IUB Bandwidth Utilizing Ratio (DL)Formula



37

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

AssociatedCounters

l IUB Bandwidth Utilizing Ratio (ATM_DL) =[(VS.ATMDIAvgUsed.1+VS.ATMDLAvgUsed.2+VS.ATMDLAvgUsed.3+VS.ATMDLAvgUsed.4)/(VS.ATMDLTotal.1+VS.ATMDLTotal.2+VS.ATMDLTotal.3+VS.ATMDLTotal.4)] x 100%

l IUB Bandwidth Utilizing Ratio (IP_DL) =[(VS.IPDLAvgUsed.1+VS.IPDLAvgUsed.2+VS.IPDLAvgUsed.3+VS.IPDLAvgUsed.4)/(VS.IPDLTotal.1+VS.IPDLTotal.2+VS.IPDLTotal.3+VS.IPDLTotal.4)] x 100%

Object NodeBUnit/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 thephysical bandwidths of ports rather than the actual available bandwidths ofports. Therefore, if the actual available bandwidth of a port is different fromthe physical bandwidth of the port, the value of this KPI calculated by usingthis formula is incorrect, and you are advised to use the actual availablebandwidths as the denominator to calculate this KPI.



38

3.9 Cell Unavailability duration

Table 3-9 Cell Unavailability durationName Cell Unavailability durationDescription This KPI is used to check the total duration of the unavailability of a cell

caused by system fault in a measurement period.AssociatedCounters

VS.Cell.UnavailTime.Sys

Object CELLUnit/Range sNote None

3.10 HSDPA Unavailability duration

Table 3-10 HSDPA Unavailability durationName HSDPA Unavailability durationDescription This KPI is used to check the total duration of unavailability of the HSDPA

service in a cell,caused by system fault in a measurement period.AssociatedCounters

VS.Cell.HSDPA.UnavailTime


3.11 HSUPA Unavailability duration

Table 3-11 HSUPA Unavailability durationName HSUPA Unavailability durationDescription This KPI is used to check the total duration of unavailability of the HSUPA

service in a cell,caused by system fault in a measurement period.



39

AssociatedCounters

VS.Cell.HSUPA.UnavailTime


3.12 CE Consumption for a NodeB Cell

Table 3-12 CE Consumption for a NodeB CellName CE Consumption for a NodeB CellDescription The resources for license groups are measured based on the usage of CEs in

each 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 CELLUnit/Range NumbersNote If only one Operator is available on the NodeB, the Dedicated Counter value

is always Zero and the Shared CE counters should be used to check actualconsumption of the Cell in NodeB.

3.13 Hardware Configured CE for a NodeB

Table 3-13 Hardware Configured CE for a NodeBName Hardware Configured CE for a NodeBDescription Number of UL/DL CEs configured for a NodeB.



40

AssociatedCounters

VS.HW.ULCreditAvailableVS.HW.DLCreditAvailable

Object NodeBUnit/Range NumbersNote None

3.14 Shared Group Configured License CE for a NodeBTable 3-14 Shared Group Configured License CE for a NodeB

Name Shared Group Configured License CE for a NodeBDescription The Configured DL/UL CEs for the Shared Group.AssociatedCounters

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

Object NodeBUnit/Range NumbersNote If only one operator is available on the NodeB, the configured counters given

above should be used to evaluate the total configured License CE in theNodeB.

3.15 Shared Group License CE Consumption for a NodeBTable 3-15 Shared Group License CE Consumption for a NodeB

Name Shared Group License CE Consumption for a NodeBDescription The Average/Maximum/Minimum number of shared DL/UL CEs consumed

by an operator, or by HSUPA service.



41

AssociatedCounters

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

Object NodeBUnit/Range NumbersNote If only one operator is available on the NodeB, the shared counters given

above should be used to evaluate the total License CE Consumption in theNodeB.

3.16 License Group Configured CE for a NodeB

Table 3-16 License Group Configured CE for a NodeBName License Group Configured CE for a NodeBDescription The Number of DL CEs configured for a license Group.AssociatedCounters

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

Object NodeBUnit/Range NumbersNote If only one operator is available on the NodeB, the configured counter value

given above is Zero.

3.17 License Group CE Consumption for a NodeB

Table 3-17 License Group CE Consumption for a NodeBName License Group CE Consumption for a NodeBDescription The Average/Maximum/Minimum number of shared DL/UL CEs consumed

by a licensed group, or by HSUPA services.



42

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 NodeBUnit/Range NumbersNote If only one operator is available on the NodeB, the counter value given above

is Zero.

3.18 RTWP (Received Total Wideband Power)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 of

a 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 CELLUnit/Range dBm; %Note None



43

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 Transmitted

Power of Carrier for a cell.l The second 3 counters provide the Maximum/Minimum/Mean

Transmitted Power of Carrier for Non-HSDPA Cell.l The third 3 counters provide Maximum/Minimum/Mean Required Power

by HS-DSCH for Cell.AssociatedCounters

VS.MaxTCPVS.MinTCPVS.MeanTCPVS.MaxTCP.NonHSVS.MinTCP.NonHSVS.MeanTCP.NonHSVS.HSDPA.MaxRequiredPwrVS.HSDPA.MinRequiredPwrVS.HSDPA.MeanRequiredPwr

Object CELLUnit/Range dBmNote None

3.20 R99 Code UtilizationTable 3-20 R99 Code Utilization

Name R99 Code UtilizationFormula

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.



44

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 CELLUnit/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-PDSCHsTable 3-21 Number of Codes Used by HS-PDSCHs

Name Number of Codes Used by HS-PDSCHsFormula HSDPA Efficiency = Duration when there is HSDPA data transmission/

Duration when there is HSDPA data in the bufferDescription The counters VS.PdschCodeUsed.Mean, VS.PdschCodeUsed.Max, and

VS.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 NodeBUnit/Range NoneNote None

3.22 HSDPA Efficiency



45

Table 3-22 HSDPA EfficiencyName HSDPA EfficiencyFormula HSDPA Efficiency = Duration when there is HSDPA data transmission/

Duration when there is HSDPA data in the bufferDescription This KPI provides the proportion of the duration when there is HSDPA data

transmission to the duration when there is HSDPA data in the buffer.AssociatedCounters

HSDPA efficiency =(VS.DataTtiRatio.Mean - VS.H

Documents

Huawei RAN14 Kpi Reference-English