Ran15.0 Kpi Reference(02)(PDF)-En

KPI Reference

Issue 02

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

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent 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.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase 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 representations of any kind, either express or implied.

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

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129

People's Republic of China Website: http://www.huawei.com

About This Document

Purpose

This document describes the RAN KPI and the counters for KPI calculation. The definition of KPI is derived based on the commercial network requirement.

Product Versions

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

Product Name Product Version

BSC6910 V100R015C00 BSC6900 V900R015C00 BTS3900 V100R008C00

The mapping single-mode base station version is: NodeB: V200R015C00 BTS3900A BTS3900L BTS3900C BTS3900AL DBS3900 BTS3812AE NodeB: V100R015C00 BTS3812A BTS3812E DBS3800

Intended Audience

l Network planning engineers l Field engineers

l System engineers

Organization

1 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. RRC connection and RAB setup are the main procedures of accessibility.

3 Availability

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

4 Coverage

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

5 Mobility

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

6 Retainability

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

7 Service Integrity

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

8 Traffic

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

Conventions

Symbol Conventions

Symbol Description

Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury.

Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personal injury.

Calls attention to important information, best practices and tips.

NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

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 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 Conventions

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

Convention Description

Convention Description

[ ] 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 all items can be selected.

[ x | y | ... ]* _{Optional items are grouped in brackets and separated by}

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

Convention Description

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

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 means

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

Contents

About This Document...ii

1 Changes in the RAN KPI Reference...1

2 Accessibility...4

2.1 IU Paging Success Ratio...5

2.2 RRC Setup Success Ratio...5

2.3 Radio Access Success Ratio...8

2.4 PS Radio Access Success Ratio...10

2.5 CS Radio Access Success Ratio...11

2.6 AMR RAB Setup Success Ratio...12

2.7 VP RAB Setup Success Ratio...13

2.8 CS RAB Setup Success Ratio...14

2.9 CS+PS Combined Service RAB Setup Success Rate...15

2.10 PS+PS Combined Service RAB Setup Success Rate...16

2.11 PS RAB Setup Success Ratio...16

2.12 HSDPA RAB Setup Success Ratio...18

2.13 HSUPA RAB Setup Success Ratio...18

2.14 PS E-FACH RAB Setup Success Ratio...19

2.15 CS over HSPA RAB Setup Success Ratio...20

2.16 HSDPA 64QAM RAB Setup Success Ratio...20

2.17 HSDPA MIMO RAB Setup Success Ratio...21

2.18 HSDPA DC RAB Setup Success Ratio...22

2.19 HSDPA MIMO64QAM RAB Setup Success Ratio...22

2.20 PTM Channel Setup Success Ratio...23

2.21 PTP Channel Setup Success Ratio...24

2.22 RRC Congestion Ratio...24

2.23 CS RAB Congestion Ratio...25

2.24 PS RAB Congestion Ratio...26

2.25 PS R99 RAB Setup Success Rate...27

2.26 WB AMR RAB Setup Success Rate...28

3 Availability...29

3.2 Paging Congestion Ratio...30

3.3 Call Admission Refused Ratio...31

3.4 Congested Cell Ratio...32

3.5 Radio Network Unavailability Ratio...33

3.6 Average CPU Load...34

3.7 Iub Port Available Bandwidth Utilizing Ratio (UL)...34

3.8 Iub Port Available Bandwidth Utilizing Ratio (DL)...35

3.9 Cell Unavailability duration...36

3.10 HSDPA Unavailability duration...37

3.11 HSUPA Unavailability duration...37

3.12 CE Consumption for a NodeB Cell...37

3.13 Hardware Configured CE for a NodeB...38

3.14 Shared Group Configured License CE for a NodeB...38

3.15 Shared Group License CE Consumption for a NodeB...39

3.16 License Group Configured CE for a NodeB...39

3.17 License Group CE Consumption for a NodeB...40

3.18 RTWP (Received Total Wideband Power)...40

3.19 TCP (Transmitted Carrier Power)...41

3.20 R99 Code Utilization...42

3.21 Number of Codes Used by HS-PDSCHs...42

3.22 HSDPA Efficiency...43

4 Coverage...44

4.1 UL Interference Cell Ratio...45

4.2 Soft Handover Overhead...45

5 Mobility...48

5.1 Soft Handover Success Ratio...49

5.2 Softer Handover Success Ratio...49

5.3 AMR Soft Handover Success Ratio...50

5.4 CS64 Soft Handover Success Ratio...51

5.5 PS Soft Handover Success Ratio...51

5.6 Intra-frequency Hard Handover Success Ratio...52

5.7 Inter-frequency Hard Handover Success Ratio...53

5.8 Service Cell Change Success Ratio with SHO (H2H)...54

5.9 H2H Intra-Frequency Hard Handover Success Ratio...54

5.10 H2H Inter-Frequency Hard Handover Success Ratio...56

5.11 H2D Intra-Frequency Hard Handover Success Ratio...57

5.12 H2D Inter-Frequency Hard Handover Success Ratio...57

5.13 E2D Intra-Frequency Hard Handover Success Ratio...58

5.14 H2D Channel Switch Success Ratio...59

5.17 PS W2G Inter-RAT Handover Out Success Ratio...61

5.18 PS G2W Inter-RAT Handover In Success Ratio...62

5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio...63

5.20 SRNC Relocation Success Ratio...64

5.21 TRNC Relocation Success Ratio...65

5.22 E-DCH Soft Handover Success Ratio...66

5.23 E-DCH Cell Change Success Ratio with SHO...66

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

5.25 E2D Channel Switch Success Ratio...68

5.26 D2E Channel Switch Success Ratio...69

5.27 E2D Handover Success Ratio with Inter HHO...70

5.28 HSUPA W2G Inter-RAT Handover Out Success Ratio...71

5.29 MBMS Service Mode Switch Success Ratio...72

5.30 CS Inter-Frequency Hard Handover Success Rate...72

5.31 PS Inter-Frequency Hard Handover Success Rate...73

6 Retainability...74

6.1 CS Service Drop Ratio...75

6.2 CS Call Drop Rate in CS+PS Combined Services...75

6.3 PS Call Drop Rate in CS+PS Combined Services...76

6.4 AMR Call Drop Ratio...77

6.5 WB AMR Call Drop Rate...78

6.6 VP Call Drop Ratio...78

6.7 AMR Traffic Drop Ratio...79

6.8 VP Traffic Drop Ratio...81

6.9 PS Call Drop Ratio...81

6.10 PS Call Drop Ratio (PCH)...82

6.11 PS Call Drop Ratio (PCH & Combined Service)...85

6.12 PS R99 Call Drop Ratio...87

6.13 PS R99 Call Drop Ratio (PCH)...88

6.14 PS BE Call Drop Ratio...89

6.15 HSDPA Call Drop Ratio...90

6.16 HSDPA Call Drop Ratio (PCH)...92

6.17 HSUPA Call Drop Ratio...93

6.18 HSUPA Call Drop Ratio (PCH)...94

6.19 MBMS Service PTP drop Ratio...95

6.20 DC-HSDPA Call Drop Ratio...96

6.21 HSDPA 64QAM Call Drop Ratio...98

6.22 HSDPA MIMO Call Drop Ratio...99

6.23 HSDPA MIMO+64QAM Call Drop Ratio...100

7 Service Integrity...102

7.2 Average DL Throughput for PS R99 Service...104

7.3 Average UL BLER for CS Service...106

7.4 Average UL BLER for PS Service...106

7.5 HSDPA Throughput...107 7.6 HSUPA Throughput...109 7.7 PS UL Throughput of RNC...110 7.8 PS DL Throughput of RNC...111 7.9 MBMS Service Throughput...112

8 Traffic...113

8.4 Number of HSDPA Users...120

8.5 Number of HSUPA Users...120

8.6 Number of E-FACH Users...121

8.7 Number of E-RACH Users...121

8.8 Number of CS Over HSPA Users...122

8.9 Number of HSDPA 64QAM Users...122

8.10 Number of HSDPA MIMO Users...123

8.11 Number of HSUPA 16QAM users...123

8.12 Number of HSDPA MIMO64QAM Users...124

8.13 Number of MBMS Users...124

8.14 HSDPA RLC Traffic Volume...125

8.15 HSUPA RLC Traffic Volume...126

8.16 R99 Service UL Traffic Volume...126

8.17 R99 Service DL Traffic Volume...127

8.18 E-FACH Traffic Volume...130

8.19 E-RACH Traffic Volume...130

1

Changes in the RAN KPI Reference

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

02 (2014-03-28)

This is the Draft A release of RAN15.0.

Compared with Issue RAN15.0 01 (2013-05-04), this issue includes the new topic: l 8.7 Number of E-RACH Users

l 8.19 E-RACH Traffic Volume

l 6.20 DC-HSDPA Call Drop Ratio

l 6.21 HSDPA 64QAM Call Drop Ratio

l 6.22 HSDPA MIMO Call Drop Ratio

l 6.23 HSDPA MIMO+64QAM Call Drop Ratio

l 8.20 Average Number of DC-HSDPA Users

Compared with Issue RAN15.0 01 (2013-05-04), this issue incorporates the following changes:

Content Description

6.10 PS Call Drop Ratio (PCH) Modified the formula by adding counters

VS.DCCC.Succ.F2U and VS.DCCC.Succ.D2U to the denominator. The modified formula is more accurate according to the KPI description.

6.11 PS Call Drop Ratio (PCH & Combined Service)

Modified the formula by adding counters

VS.DCCC.Succ.F2U and VS.DCCC.Succ.D2U to the denominator. The modified formula is more accurate according to the KPI description.

7.1 Average UL Throughput for PS R99 Service

Added the KPI "Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)."

7.2 Average DL Throughput Added the KPI "Average DL Throughput for PS R99 BE KPI Reference 1 Changes in the RAN KPI Reference

Content Description

7.5 HSDPA Throughput Added the formula of calculating HSDPA throughput for 3900 series base stations in Note.

7.6 HSUPA Throughput Modified the formula of calculating "Mean Throughput for One HSUPA Cell" in Note. In earlier KPI references, this KPI is measured at the MAC-d layer. In this version, this KPI is measured at the MAC-e/i layer over the air interface and therefore more accurate for UEs.

Compared with Issue RAN15.0 01 (2013-05-04), this issue does not exclude any topics.

01 (2013-05-04)

This is the first commercial release of RAN15.0.

Compared with issue RAN15.0 Draft A (2013-01-30), this issue includes the new topic: l 6.11 PS Call Drop Ratio (PCH & Combined Service)

Compared with issue RAN15.0 Draft A (2013-01-30), this issue incorporates the following changes. Content Description 2.20 PTM Channel Setup Success Ratio 2.21 PTP Channel Setup Success Ratio 5.29 MBMS Service Mode Switch Success Ratio

6.19 MBMS Service PTP drop Ratio

7.9 MBMS Service Throughput 8.13 Number of MBMS Users

Removed the note that these KPIs apply only to the BSC6900 because they can apply to the BSC6910 now.

5.16 CS W2G Inter-RAT Handover Out Success Ratio 5.17 PS W2G Inter-RAT Handover Out Success Ratio

Deducted the number of inter-RAT handover

cancellations from the denominator of the formula for calculating the cell-level KPI.

Compared with issue RAN15.0 Draft A (2013-01-30), this issue does not exclude any topics.

Compared with issue RAN14.0 02 (2012-06-30)), this issue includes the new topic: l The BSC6910 is introduced in RAN15.0. This document applies to the BSC6900 and

BSC6910.

Compared with issue RAN14.0 02 (2012-06-30), this issue incorporates the following changes:

Content Description

3.6 Average CPU Load Added a formula for BSC6910 in the KPI.

2.20 PTM Channel Setup Success Ratio

2.21 PTP Channel Setup Success Ratio

5.29 MBMS Service Mode Switch Success Ratio

6.19 MBMS Service PTP drop Ratio

7.9 MBMS Service Throughput 8.13 Number of MBMS Users

Added a note that these KPI were only for BSC6900.

Compared with issue RAN14.0 02 (2012-06-30), this issue does not exclude any topics. KPI Reference 1 Changes in the RAN KPI Reference

2

Accessibility

About This Chapter

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

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 pagings from the Core Network (CN) in one RNC.

The Attempt Paging Procedure starts when the CN sends a PAGING message to the RNC, and is complete when the UE in idle mode receives the PAGING TYPE 1 message from the RNC.

The Successful Paging Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE in idle mode.

Associated Counters

IU Paging Success Ratio =

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

Object RNC

Unit/Range %

Note None

2.2 RRC Setup Success Ratio

Name RRC Setup Success Ratio

Formula

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 service types requested by the UE: Conversational Call, Streaming Call, Background Call, Interactive Call, Originating Subscribed Traffic Call, Emergency Call, High Priority Signaling, Low Priority Signaling, Cause Unknown, Call Re-Establishment. For details on the reason types, see section 10.3.3.11 in 3GPP TS 25.331.

l The RRC Setup Success for Service Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE.

Description of RRC Setup Success Ratio for other causes:

l RRC Connection Attempt for Other reasons Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE. The message contains information about one of the following service types requested by the UE: Inter-RAT cell re-selection, Inter-RAT cell change order, Registration and Detach.

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

Associated Counters

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.IRATCCO+ 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 requests that are resent after the first RRC connection setup request of the UE is rejected due to resource insufficiency. You can subtract these counters from the denominator of the formula to increase the value of this KPI:

l RRC.AttConnEstab.Rep.OrgConvCall l RRC.AttConnEstab.Rep.OrgStrCall l RRC.AttConnEstab.Rep.OrgInterCall l RRC.AttConnEstab.Rep.OrgBkgCall l RRC.AttConnEstab.Rep.TmConvCall l RRC.AttConnEstab.Rep.TmStrCall l RRC.AttConnEstab.Rep.TmInterCall l RRC.AttConnEstab.Rep.TmBkgCall l RRC.AttConnEstab.Rep.OrgSubCall l RRC.AttConnEstab.Rep.EmgCall l RRC.AttConnEstab.Rep.IRATCelRes l RRC.AttConnEstab.Rep.IRATCCO l RRC.AttConnEstab.Rep.Reg l RRC.AttConnEstab.Rep.Detach l RRC.AttConnEstab.Rep.OrgHhPrSig l RRC.AttConnEstab.Rep.OrgLwPrSig l RRC.AttConnEstab.Rep.CallReEst l RRC.AttConnEstab.Rep.TmHhPrSig l RRC.AttConnEstab.Rep.TmLwPrSig l RRC.AttConnEstab.Rep.Unknown

The formula of CS and PS radio access success ratio refer to the 2.4 PS Radio Access Success Ratio and 2.5 CS Radio Access Success Ratio directly.

2.3 Radio Access Success Ratio

Formula

Description This KPI is used to check the Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not provided in this call setup procedure.

Description of the RAB Setup Attempt Procedure and the RAB Setup Success Procedure:

The RAB Setup Attempt Procedure starts when the CN sends an RAB ASSIGNMENT REQUEST message to the RNC. The message contains information about one of the following service types: CS Conversational RAB Establishments, CS Streaming RAB Establishments, PS Conversational RAB Establishment, PS Background RAB Establishments, PS Interactive RAB Establishments, PS Streaming RAB Establishments. The RAB Setup Attempt Procedure is complete When the RNC receives an RAB

ASSIGNMENT REQUEST message from the CN.

The RAB Setup Success Procedure is complete when the RNC sends to the CN an RAB ASSIGNMENT RESPONSE message.

Associated Counters

l Radio Access Success Ratio (Cell) =

RRC Setup Success Ratio (Cell.Service) x {[(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)=

RRC Setup Success Ratio (Cell.Service) x {[(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

Formula

Description This KPI is used to check the PS Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not provided in this call setup procedure.

The PS RRC Setup Attempt Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE. The message contains information about one of the following service types: Originating Interactive Call, Terminating Interactive Call, Originating Background Call, Terminating Background Call.

The PS RRC Setup Success Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE.

Associated Counters

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 )] x PS RAB Setup Success Ratio (Cell) 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)] x PS RAB Setup Success Ratio (RNC) x 100%

Object CELL, RNC

Unit/Range %

Note None

2.5 CS Radio Access Success Ratio

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 the Access Failures caused by the SCCP congestion are not provided in this call setup procedure.

The CS RRC Setup Attempt Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE.The message contains information about one of the following service types: Originating Conversational Call, Terminating Conversational Call, Emergency Call. The CS RRC Setup Success Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE.

Associated Counters

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

CS RAB Setup Success Ratio (Cell) 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)] x

CS RAB Setup Success Ratio (RNC) x 100%

Object CELL,RNC

Unit/Range %

Note None

Table 2-6 AMR RAB Setup Success Ratio Name AMR RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the AMR Service. AMR RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for the CS narrow band AMR services.

The AMR RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE message to the RNC. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.

Associated Counters

AMR RAB Setup Success Ratio(Cell) =

(VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR) 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 is measured as an AMR RAB setup failure regardless of whether the DRD succeeds. As a result, the value of this KPI is smaller than actual value. Therefore, it is recommended that you add VS.IRATHO.SuccOutCS.DR to the numerator of the formula for calculating this KPI if inter-RAT DRD is enabled during RAB setup.

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/s conversational services in an RNC or a cluster.

VP (Video Phone) RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN (The RAB type is for the CS 64 Kbit/s conversational service).

VP RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE message to RNC. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.

Associated Counters

VP RAB Setup Success Ratio (Cell) =

(VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64) 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

Name CS RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of all CS services in an RNC or a cluster.

The CS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN in the CS domain.The message contains information about one of the following service types: Conversational Services, streaming Services.

The CS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.

Associated Counters

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 %

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

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 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 RNC receives from the CN an RAB ASSIGNMENT REQUEST message and one or more RABs of the UE already exists in the cell, the RNC checks the RAB type carried in the message and determines the combined service type based on the existing RAB type of the UE. The number of CS+PS combined service RAB setup attempts is measured in the best cell that the UE camps on if the combined service type is CS+PS, CS+2PS, or CS+3PS.

Number of successfully set up CS+PS combined service RABs: When the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE and one or more RABs of a UE already exists in the cell, the RNC checks the RAB type and determines the combined service type based on the existing RAB type of the UE. The number of successfully set up CS+PS combined service RABs is measured in the best cell that the UE camps on if the

Associated Counters

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

Name PS+PS Combined Service RAB Setup Success Rate

Formula 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 RNC receives from the CN an RAB ASSIGNMENT REQUEST message and one or more RABs of the UE already exists in the cell, the RNC checks the RAB type carried in the message and determines the combined service type based on the existing RAB type of the UE. The number of PS+PS combined service RAB setup attempts is measured in the best cell that the UE camps on if the combined service type is 2PS, 3PS, or 4PS.

Number of successfully set up PS+PS combined service RABs: When the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE and one or more RABs of a UE already exists in the cell, the RNC checks the RAB type and determines the combined service type based on the existing RAB type of the UE. The number of successfully set up PS+PS combined service RABs is measured in the best cell that the UE camps on if the combined service type is 2PS, 3PS, or 4PS.

Associated Counters

PS+PS RAB Setup Success ratio=

(VS.MultiRAB.SuccEstab.PSPS/VS.MultiRAB.AttEstab.PSPS)*100%

Object CELL

Unit/Range %

Note None

Table 2-11 PS RAB Setup Success Ratio Name PS RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of all PS services in an RNC or a cluster.

The PS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN in the PS domain, the message contains information about one of the following service types: Conversational services, Streaming services, Interactive Services, Background Services.

The PS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the SGSN in the PS domain.

Associated Counters

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

Name HSDPA RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of PS services that are carried by HSDPA in a cluster.

The HSDPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service.

The HSDPA RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.

Associated Counters

HSDPA RAB Setup Success Ratio (Cell) =

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

Object CELL

Unit/Range %

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

2.13 HSUPA RAB Setup Success Ratio

Name HSUPA RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of the HSUPA service in an RNC or a cluster.

The HSUPA RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.

The HSUPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSUPA service.

Associated Counters

HSUPA RAB Setup Success Ratio (Cell) =

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

Object CELL

Unit/Range %

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

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 service in an RNC or a cluster.

Successful PS RAB Setup on E-FACH Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the SGSN in the PS domain.

The procedure of Attempts of PS RAB Setup on E-FACH is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN, and the PS service is established on the EFACH.

Associated Counters

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

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

Object CELL

Unit/Range %

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

2.15 CS over HSPA RAB Setup Success Ratio

Name CS over HSPA RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB setup success ratio of the CS over HSPA service.

When the RAB is set for the CS conversational service and is carried on an HSPA channel, the CS over HSPA RAB Setup Success Procedure starts when the RNC receives an RADIO BEARER SETUP COMPLETE message from UE. This procedure is complete when the RNC sends an RAB

ASSIGNMENT RESPONSE message to CN.

The CS over HSPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN, and the RAB is set up on an HSPA channel.

Associated Counters

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

VS.HSPA.RAB.AttEstab.CS.Conv) x 100%

Object CELL

Unit/Range %

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

2.16 HSDPA 64QAM RAB Setup Success Ratio

Name HSDPA 64QAM RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA 64QAM service in an RNC or a cluster.

The HSDPA 64 QAM RAB Setup Success Procedure starts when the RNC receives an RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.

The HSDPA 64QAM RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service using 64QAM.

Associated Counters

HSDPA 64QAM RAB Setup Success Ratio (Cell) = (VS.HSDPA.RAB.64QAM.SuccEstab/VS.HSDPA.RAB.

64QAM.AttEstab) x 100%

Object CELL

Unit/Range %

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

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 MIMO

service in an RNC or a cluster.

The HSDPA MIMO RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.

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

Associated Counters

HSDPA MIMO RAB Setup Success Ratio=

(VS.HSDPA.RAB.MIMO.SuccEstab/VS.HSDPA.RAB.MIMO.AttEs-tab) x 100%

Object CELL

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

2.18 HSDPA DC RAB Setup Success Ratio

Name HSDPA DC RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA DC

RAB service in an RNC or a cluster.

The HSDPA DC RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.

The HSDPA DC RAB Setup Attempt procedure is complete when the RNC receives from the CN an RAB ASSIGNMENT REQUEST message for setting up the HSDPA service using DC-HSDPA.

Associated Counters

HSDPA DC RAB Setup Success Ratio=

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

Object CELL

Unit/Range %

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

2.19 HSDPA MIMO64QAM RAB Setup Success Ratio

Name HSDPA MIMO64QAM RAB Setup Success Ratio

Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO 64QAM service in an RNC or a cluster.

The HSDPA MIMO 64QAM RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB

ASSIGNMENT RESPONSE message to the CN.

The HSDPA MIMO 64QAM RAB Setup Attempt procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service using MIMO+64QAM.

Associated Counters

HSDPA MIMO64QAM RAB Setup Success Ratio= (VS.HSDPA.RAB.MIMO64QAM.SuccEstab/

VS.HSDPA.RAB.MIMO64QAM.AttEstab) x 100%

Object CELL

Unit/Range %

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

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 service in PTM mode.

When the RB of PTM MBMS service is successfully set up, the PTM Channel RB is successfully set up.

When the RNC initiates the setup of PTM MBMS service, the PTM Channel RB Setup Attempt.

Associated Counters

PTM Channel Setup Success Ratio=

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

Object CELL

Unit/Range %

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

2.21 PTP Channel Setup Success Ratio

Name PTP Channel Setup Success Ratio

Formula

Description This KPI is used to check the Channel Setup Success Rate of MBMS service in PTP mode.

The PTP Channel RB Setup Success Procedure is as follows:

When the UE initiates a request to set up an MBMS, the RNC, in response to the UE's request, initiates PTP RB setup, and the PTP RB is successfully set up.

The PTP Channel RB Setup Attempt Procedure:

The RNC initiates PTP RB setup after the UE initiates an MBMS setup request.

Associated Counters

PTP Channel Setup Success Ratio=

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

Object CELL

Unit/Range %

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

2.22 RRC Congestion Ratio

Name RRC Congestion Ratio

Description This KPI is used to check the RRC Congestion Ratio in a cluster.

After receiving an RRC CONNECTION REQUEST message from the UE, the RNC initiates admission procedures for resources of code, power, CE, and Iub bandwidth. If the resource admission fails, the RRC Setup Failure due to Congestion procedure is complete when the RNC sends an RRC CONNECTION REJECT message to the UE.

The RRC Connection Attempt for service Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE.

Associated Counters RRC Congestion Ratio= [(VS.RRC.Rej.ULPower.Cong+ VS.RRC.Rej.DLPower.Cong + VS.RRC.Rej.ULIUBBand.Cong + VS.RRC.Rej.DLIUBBand.Cong + VS.RRC.Rej.ULCE.Cong + VS.RRC.Rej.DLCE.Cong + VS.RRC.Rej.Code.Cong )/ VS.RRC.AttConnEstab.Sum ] x 100% Object CELL Unit/Range % Note None

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 the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message contains one of the following RAB assignment responses: "No Radio Resources Available in Target cell", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available".

The CS RAB Setup Attempt Procedure starts when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN in the CS domain. The message contains one of the following RAB assignment requests: Conversational Services, streaming Services.

Associated Counters

CS RAB Congestion Ratio=

[(VS.RAB.FailEstabCS.DLIUBBand.Cong+ VS.RAB.FailEstabCS.ULIUBBand.Cong+ VS.RAB.FailEstabCS.ULCE.Cong + VS.RAB.FailEstabCS.DLCE.Cong + VS.RAB.FailEstabCS.Code.Cong + VS.RAB.FailEstabCS.ULPower.Cong+ VS.RAB.FailEstabCS.DLPower.Cong)/ (VS.RAB.AttEstabCS.Conv+ VS.RAB.AttEstabCS.Str)] x100% Object CELL Unit/Range % Note None

2.24 PS RAB Congestion Ratio

Name PS RAB Congestion Ratio

Description This KPI is used to check the PS RAB Congestion Ratio in a cluster. The PS RAB Setup Fails due to Congestion procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message contains information about one of the following RAB assignment responses: "No Radio Resources Available in Target cell", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available".

The PS RAB Setup Attempt Procedure starts when the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN in the PS domain. The message contains information about one of the following RAB assignment requests: Conversational services, Streaming services, Interactive Services, Background Services.

Associated Counters

PS RAB Congestion Ratio=

[VS.RAB.FailEstabPS.DLIUBBand.Cong+ VS.RAB.FailEstabPS.ULIUBBand.Cong+ VS.RAB.FailEstabPS.ULCE.Cong+ VS.RAB.FailEstabPS.DLCE.Cong+ VS.RAB.FailEstabPS.Code.Cong+ VS.RAB.FailEstabPS.ULPower.Cong+ VS.RAB.FailEstabPS.DLPower.Cong+ VS.RAB.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

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 R99

RABs 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 where the UE camps on when the RNC receives from the PS CN an RAB

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

COMPLETE message from the UE if the RAB is for a PS R99 service.

Associated Counters

PS RAB Setup Success Ratio (Cell)=

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

Object CELL

Unit/Range %

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

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 WB

AMR 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 cell where the UE camps on when the RNC receives from the CS CN an RAB ASSIGNMENT REQUEST message for a WB AMR voice service. The number of successfully set up WB AMR RABs is measured in the best cell where the UE camps on when the RNC sends the CN an RAB

ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE if the RAB is for a WB AMR voice service.

Associated Counters

AMR WB RAB Setup Success Ratio(Cell)=

(VS.RAB.SuccEstabCS.AMRWB / VS.RAB.AttEstabCS.AMRWB) *100%

Object CELL

Unit/Range %

3

Availability

About This Chapter

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

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 ratio or call setup success ratio in an RNC or a cluster.

Description of the numerator:

The number of Cells in which AMR RAB Setup Success Ratio <95% and VP RAB Setup Ratio <= 95%, or AMR Call Drop Ratio >3% and VP Call Drop Ratio >3%.

Associated Counters

Worst Cell Ratio =

{[The Number Of Cells, In which (AMR RAB Setup Success Ratio (Cell)

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

Object CELL

Unit/Range %

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

3.2 Paging Congestion Ratio

Formula

Description Paging Congestion Ratio (RNC):

This KPI is used to check the consumption of PCCH bandwidth during busy hours.

l Description of the numerator:

The Failures to Respond to PAGING Message From CN counted if the RNC does not send a PAGING type 1 or PAGING type 2 message. The reason is that the RNC does not send a PAGING message due to congestion causes such as Iu flow control or high CPU usage. l Description of the denominator:

The Number of PAGING Message from CN is counted when RNC receives a PAGING message from the CN included CS and PS PAGING. Paging Congestion Ratio (Cell):

This KPI is used to check the consumption of PCCH bandwidth during the busy hour.

l Description of the numerator:

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

l Description of the denominator:

This counter provides the number of paging messages of PAGING TYPE 1 sent by the RNC in a cell.

Associated Counters

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

Object RNC, CELL

Unit/Range %

Note None

3.3 Call Admission Refused Ratio

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 busy hours in an RNC or a cluster.

l Description of the numerator:

The failed number of Cell Resource Requests for New Call setup is counted after RNC requesting cell resources for the UE successfully. l Description of the denominator:

The number of Cell Resource Requests during RAB establishment for Cell. After RNC receiving the RAB ASSIGNMENT REQUEST message from CN, the RNC requests cell resources for the UE and the counter is pegged in the cell where the UE camps on.

Associated Counters

Call admission Refused Ratio=

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

Object CELL

Unit/Range %

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

3.4 Congested Cell Ratio

Name Congested Cell Ratio

Formula

Description This KPI is used to check the utility ratio of radio network resources during busy hours in an RNC or a cluster. It is the rate of congested cell during the busy hour to total number of cells in RNC.

Description of the numerator:

The number of congested cells counted after RNC receiving the COMMON MESUREMENT REPORT message from NodeB. The RNC measures when overload congestion occurs at UL or DL.

Associated Counters

Congested Cell Ratio =

(The Number Of Cells, in which VS.LCC.OLC.UL.Num>0 or

VS.LCC.OLC.DL.Num>0 On Busy Hour/The Total Number Of Cells In

RNC) x 100%

Object CELL

Unit/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 Ratio

Name Radio Network Unavailability Ratio

Formula

Description This KPI describes the ratio of cell unavailable duration to the number of cells in RNC during busy hours. It is used to check the impact of the degrading of the network performance caused by the unavailable cells during busy hours in an RNC.

Description of the numerator:

The cell unavailable time is started to count when the cell is out of service, or the channel is barred through the LMT in a measurement period, or problem of CCH such as failed synchronization, or equipment faults.

Associated Counters

Radio Network Unavailability Ratio=

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

Object CELL

Unit/Range %

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

3.6 Average CPU Load

Name Average CPU Load

Formula For BSC6900: Average CPU Load = CPU usage of the XPU subsystem in

the measurement period

For BSC6910: Average CPU Load = CPU usage of the subsystem in the measurement period

Description This KPI provides the mean CPU usage of a subsystem in the measurement

period. It indicates the load and operating performance of the CPU on the subsystem in the measurement period.

The CPU usage of the subsystem is sampled every second in the measurement period. Then, average CPU usage of the subsystem is the accumulated value divided by the number of sampling times.

Associated Counters

For BSC6900: Average CPU Load= VS.XPU.CPULOAD.MEAN For BSC6910: Average CPU Load= VS.SUBSYS.CPULOAD.MEAN

Object For BSC6900: XPU

For BSC6910: SUBSYS

Unit/Range %

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

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 available bandwidth utilizing ratio. The Bandwidth could be measured on ATM Physical Ports or IP physical Ports.

Associated Counters

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 the

available physical bandwidths of ports rather than the actual available bandwidths of ports. Therefore, this KPI can not be used to check the Iub actual bandwidth utilizing ratio.

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 available bandwidth utilizing ratio. The Bandwidth could be measured on ATM

Associated Counters

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 the

available physical bandwidths of ports rather than the actual available bandwidths of ports. Therefore, this KPI can not be used to check the Iub actual bandwidth utilizing ratio.

3.9 Cell Unavailability duration

Name Cell Unavailability duration

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

Associated Counters

Unit/Range s

Note None

3.10 HSDPA Unavailability duration

Name HSDPA Unavailability duration

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

Associated Counters VS.Cell.HSDPA.UnavailTime Object CELL Unit/Range s Note None

3.11 HSUPA Unavailability duration

Name HSUPA Unavailability duration

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

Associated Counters VS.Cell.HSUPA.UnavailTime Object CELL Unit/Range s Note None

3.12 CE Consumption for a NodeB Cell

Table 3-12 CE Consumption for a NodeB Cell Name CE Consumption for a NodeB Cell

Description The resources for license groups are measured based on the usage of CEs in each license group. This measurement indicates the consumption of baseband resources in the NodeB.

The corresponding counters listed below give the Average/Maximum number of UL/DL and HSUPA CEs consumption for an operator.

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

Object NodeB CELL

Unit/Range Numbers

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

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.

Associated Counters VS.HW.ULCreditAvailable VS.HW.DLCreditAvailable Object NodeB Unit/Range Numbers Note None

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

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

Associated Counters VS.LC.ULCreditAvailable.Shared VS.LC.DLCreditAvailable.Shared Object NodeB Unit/Range Numbers

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

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 consumed

by an operator, or by HSUPA service.

Associated Counters VS.LC.ULMean.LicenseGroup.Shared VS.LC.ULMax.LicenseGroup.Shared VS.LC.ULMin.LicenseGroup.Shared VS.HSUPA.LC.ULMean.LicenseGroup.Shared VS.HSUPA.LC.ULMax.LicenseGroup.Shared VS.HSUPA.LC.ULMin.LicenseGroup.Shared VS.LC.DLMean.LicenseGroup.Shared VS.LC.DLMax.LicenseGroup.Shared VS.LC.DLMin.LicenseGroup.Shared Object NodeB Unit/Range Numbers

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

3.16 License Group Configured CE for a NodeB

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.

Associated Counters VS.LC.DLCreditAvailable.LicenseGroup.Dedicated VS.LC.ULCreditAvailable.LicenseGroup.Dedicated Object NodeB Unit/Range Numbers

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

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 consumed

by a licensed group, or by HSUPA services.

Associated Counters l UL Statistics VS.LC.ULMean.LicenseGroup VS.LC.ULMax.LicenseGroup VS.LC.ULMin.LicenseGroup VS.HSUPA.LC.ULMin.LicenseGroup VS.HSUPA.LC.ULMean.LicenseGroup VS.HSUPA.LC.ULMax.LicenseGroup l DL Statistics VS.LC.DLMean.LicenseGroup VS.LC.DLMax.LicenseGroup VS.LC.DLMin.LicenseGroup Object NodeB Unit/Range Numbers

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

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 Received Bandwidth for Cell. The last 3 counters provide average, maximum and minimum received scheduled E-DCH power shared in the measurement period for cell.

Associated Counters VS.MaxRTWP VS.MinRTWP VS.MeanRTWP VS.HSUPA.MeanRSEPS VS.HSUPA.MaxRSEPS VS.HSUPA.MinRSEPS Object CELL Unit/Range dBm; % Note None

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 Non-HSDPA Transmitted Carrier Power for a Cell.

l The third 3 counters provide Maximum/Minimum/Mean Power Required by HS-DSCH for a Cell. Associated Counters VS.MaxTCP VS.MinTCP VS.MeanTCP VS.MaxTCP.NonHS VS.MinTCP.NonHS VS.MeanTCP.NonHS VS.HSDPA.MaxRequiredPwr VS.HSDPA.MinRequiredPwr

Object CELL

Unit/Range dBm

Note None

3.20 R99 Code Utilization

Name R99 Code Utilization

Formula

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

4/8/16/32/64/128/256. Associated Counters 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 the following formula:

VS.RAB.SFOccupy /256

The value would be greater than the real usage as the code for HSDPA was reserved initially.