Ran Kpi Reference(v900r013c00_03)(PDF)-En

7/30/2019 Ran Kpi Reference(v900r013c00_03)(PDF)-En

1/121

RAN

V900R013C00

KPI Reference

Issue 03

Date 2012-02-27

HUAWEI TECHNOLOGIES CO., LTD.


2/121

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

Email: [email protected]

Issue 03 (2012-02-27) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

i
http://www.huawei.com/


3/121

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 network

optimization. However, the KPI description is updated from time to time based on therequirements of customers.

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

Product Name Product Version

BSC6900 V900R013C00

NodeB V100R013

NodeB V200R013

Intended AudienceThis document is intended for:

l Network planning engineers

lField engineers

l System engineers

Organization1 Changes in the RAN KPI Reference

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

2 Accessibility

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

RAN

KPI Reference About This Document



ii


4/121

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

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

Symbol Description

Indicates a hazard with a high level of risk, which if not

avoided, 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 not

avoided, could result in equipment damage, data loss,

performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or save

time.

Provides additional information to emphasize or supplement

important points of the main text.

RAN




iii


5/121

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

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.


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

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

{ x | y | ... } Optional items are grouped in braces and separated 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.


Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, clickOK.

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

RAN




iv


6/121

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.

RAN




v


7/121

Contents

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

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

2 Accessibility....................................................................................................................................5

2.1 IU Paging Success Ratio.....................................................................................................................................7

2.2 RRC Setup Success Ratio...................................................................................................................................7

2.3 Radio Access Success Ratio.............................................................................................................................10

2.4 PS Radio Access Success Ratio........................................................................................................................11

2.5 CS Radio Access Success Ratio.......................................................................................................................12

2.6 AMR RAB Setup Success Ratio......................................................................................................................13

2.7 VP RAB Setup Success Ratio..........................................................................................................................14

2.8 CS RAB Setup Success Ratio...........................................................................................................................15

2.9 PS RAB Setup Success Ratio...........................................................................................................................15

2.10 HSDPA RAB Setup Success Ratio................................................................................................................162.11 HSUPA RAB Setup Success Ratio................................................................................................................17

2.12 PS E-FACH RAB Setup Success Ratio..........................................................................................................18

2.13 CS over HSPA RAB Setup Success Ratio.....................................................................................................18

2.14 HSDPA 64QAM RAB Setup Success Ratio..................................................................................................19

2.15 HSDPA MIMO RAB Setup Success Ratio....................................................................................................20

2.16 HSDPA DC RAB Setup Success Ratio..........................................................................................................20

2.17 HSDPA MIMO64QAM RAB Setup Success Ratio.......................................................................................21

2.18 PTM Channel Setup Success Ratio................................................................................................................22

2.19 PTP Channel Setup Success Ratio..................................................................................................................22

2.20 RRC Congestion Ratio...................................................................................................................................23

2.21 CS RAB Congestion Ratio.............................................................................................................................24

2.22 PS RAB Congestion Ratio..............................................................................................................................25

3 Availability...................................................................................................................................26

3.1 Worst Cell Ratio...............................................................................................................................................28

3.2 Paging Congestion Ratio..................................................................................................................................28

3.3 Call Admission Refused Ratio.........................................................................................................................29

3.4 Congested Cell Ratio........................................................................................................................................30

3.5 Radio Network Unavailability Ratio................................................................................................................31

3.6 Average CPU Load...........................................................................................................................................31

RAN

KPI Reference Contents



vi


8/121

3.7 IUB Bandwidth Utilizing Ratio (UL)...............................................................................................................32

3.8 IUB Bandwidth Utilizing Ratio (DL)...............................................................................................................33

3.9 Cell Unavailability duration.............................................................................................................................35

3.10 HSDPA Unavailability duration.....................................................................................................................35

3.11 HSUPA Unavailability duration.....................................................................................................................35

3.12 CE Consumption for a NodeB Cell................................................................................................................36

3.13 Hardware Configured CE for a NodeB..........................................................................................................36

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

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

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

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

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

3.19 TCP (Transmitted Carrier Power)..................................................................................................................40

3.20 R99 Code Utilization......................................................................................................................................40

4 Coverage........................................................................................................................................42

4.1 UL Interference Cell Ratio...............................................................................................................................43

4.2 Soft Handover Overhead..................................................................................................................................43

5 Mobility.........................................................................................................................................46

5.1 Soft Handover Success Ratio...........................................................................................................................48

5.2 Softer Handover Success Ratio........................................................................................................................48

5.3 AMR Soft Handover Success Ratio.................................................................................................................49

5.4 CS64 Soft Handover Success Ratio..................................................................................................................50

5.5 PS Soft Handover Success Ratio......................................................................................................................50

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

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

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

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

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

5.11 H2D Inter-frequency Hard Handover Success Ratio......................................................................................55

5.12 H2D Channel Switch Success Ratio...............................................................................................................56

5.13 D2H Channel Switch Success Ratio...............................................................................................................57

5.14 CS W2G Inter-RAT Handover Out Success Ratio.........................................................................................585.15 PS W2G Inter-RAT Handover Out Success Ratio.........................................................................................59

5.16 PS G2W Inter-RAT Handover In Success Ratio............................................................................................60

5.17 HSDPA W2G Inter-RAT Handover Out Success Ratio................................................................................60

5.18 SRNC Relocation Success Ratio....................................................................................................................61

5.19 TRNC Relocation Success Ratio....................................................................................................................62

5.20 E-DCH Soft Handover Success Ratio............................................................................................................63

5.21 E-DCH Cell Change Success Ratio with SHO...............................................................................................63

5.22 E-DCH Cell Change Success Ratio with Inter-HHO.....................................................................................65

5.23 E2D Channel Switch Success Ratio...............................................................................................................66

5.24 D2E Channel Switch Success Ratio...............................................................................................................66

RAN




vii


9/121

5.25 E2D Handover Success Ratio with Inter HHO..............................................................................................67

5.26 HSUPA W2G Inter-RAT Handover Out Success Ratio................................................................................68

5.27 MBMS Service Mode Switch Success Ratio.................................................................................................68

6 Retainability.................................................................................................................................706.1 CS Service Drop Ratio.....................................................................................................................................71

6.2 AMR Call Drop Ratio.......................................................................................................................................71

6.3 VP Call Drop Ratio...........................................................................................................................................72

6.4 AMR Traffic Drop Ratio..................................................................................................................................73

6.5 VP Traffic Drop Ratio......................................................................................................................................75

6.6 PS Call Drop Ratio...........................................................................................................................................75

6.7 PS Call Drop Ratio (PCH)................................................................................................................................76

6.8 PS R99 Call Drop Ratio....................................................................................................................................77

6.9 PS R99 Call Drop Ratio (PCH)........................................................................................................................78

6.10 PS BE Call Drop Ratio...................................................................................................................................79

6.11 HSDPA Call Drop Ratio.................................................................................................................................80

6.12 HSDPA Call Drop Ratio (PCH).....................................................................................................................81

6.13 HSUPA Call Drop Ratio.................................................................................................................................82

6.14 HSUPA Call Drop Ratio (PCH).....................................................................................................................84

6.15 MBMS Service PTP drop Ratio.....................................................................................................................85

7 Service Integrity...........................................................................................................................86

7.1 Average UL Throughput for PS R99 Service...................................................................................................87

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

7.3 Average UL BLER for CS Service...................................................................................................................89

7.4 Average UL BLER for PS Service...................................................................................................................89

7.5 HSDPA Throughput.........................................................................................................................................90

7.6 HSUPA Throughput.........................................................................................................................................91

7.7 PS UL Throughput of RNC..............................................................................................................................92

7.8 PS DL Throughput of RNC..............................................................................................................................93

7.9 MBMS Service Throughput.............................................................................................................................94

8 Traffic.............................................................................................................................................95

8.1 CS Equivalent Erlang of RNC..........................................................................................................................968.2 Number of CS Users.........................................................................................................................................96

8.3 Number of PS R99 Users..................................................................................................................................97

8.4 Number of HSDPA Users...............................................................................................................................102

8.5 Number of HSUPA Users...............................................................................................................................102

8.6 Number of E-FACH Users.............................................................................................................................103

8.7 Number of CS Over HSPA Users...................................................................................................................103

8.8 Number of HSDPA 64QAM Users................................................................................................................104

8.9 Number of HSDPA MIMO Users..................................................................................................................104

8.10 Numberof HSUPA 16QAM users...............................................................................................................105

8.11 Numberof HSDPA MIMO64QAM Users...................................................................................................105

RAN




viii


10/121

8.12 Number of MBMS Users..............................................................................................................................105

8.13 HSDPA RLC Traffic Volume......................................................................................................................106

8.14 HSUPA RLC Traffic Volume......................................................................................................................107

8.15 R99 Service UL Traffic Volume..................................................................................................................107

8.16 R99 Service DL Traffic Volume..................................................................................................................108

8.17 E-FACH Traffic Volume..............................................................................................................................111

RAN




ix


11/121

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

03 (2012-02-27)

This is the third commercial release of V900R013C00.

Compared with issue 02 (2011-08-31), this issue does not include any new topics.

Compared with issue 02 (2011-08-31), this issue incorporates the following changes:

Content Description

3.8 IUB Bandwidth Utilizing Ratio

(DL)

3.7 IUB Bandwidth Utilizing Ratio

(UL)

Added the scenario where the value of this KPI is

incorrect to Note.

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

02 (2011-08-31)

This is the second commercial release of V900R013C00.

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

Compared with issue 01 (2011-04-25), this issue incorporates the following changes:

Content Description

5.10 H2H Inter-Frequency Hard

Handover Success Ratio

The description of the KPI is optimized.

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

RAN

KPI Reference 1 Changes in the RAN KPI Reference



1


12/121

01 (2011-04-25)

This is the first commercial release of V900R013C00.

Compared with issue Draft A (2011-01-31), this issue does not include any new topics.

Compared with issue Draft A (2011-01-31), this issue does not incorporate any changes.

Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.

Draft A (2011-01-31)

This is the Draft A release of V900R013C00.

Compared with issue 02 (2010-09-20) of V900R012C01, this issue does not include any new

topics.

Compared with issue 02 (2010-09-20) of V900R012C01, this issue incorporates the following

changes:

Content Description

2.2 RRC Setup Success Ratio Correct the counter name

fromRRC.SuccConnEstab.OrgItrCall to

RRC.SuccConnEstab.OrgInterCall

6.2 AMR Call Drop Ratio Correct the counter name

VS.RAB.NormRel.AMRWB.Iur to

VS.RAB.NormRel.AMR.Iur

8.16 R99 Service DL Traffic Volume Correct the counter name VS.PS.Int.DUL.

32.Traffic to VS.PS.Int.DL.32.Traffic

6.12 HSDPA Call Drop Ratio (PCH)

6.11 HSDPA Call Drop Ratio

Correct the counter name

VS.RAB.NormRel.HSUPA.Iur to

VS.RAB.NormRel.HSDPA.Iur

7.5 HSDPA Throughput Correct the counter name VS.DataOutput.User-

Data to VS.DataOutput.Mean/

(VS.DataTtiRatio.Mean-

VS.HSDPA.InactiveDataTtiRatio.Mean)

5.6 Intra-frequency Hard Handover

Success Ratio

Correct the counter name

VS.HHO.AttIntraFreqOut.InterRNC to

VS.HHO.AttIntraFreqOut.IntraNodeB

6.7 PS Call Drop Ratio (PCH) Correct the counter name VS.DCCC.Succ.F2P to

VS.DCCC.F2P.Succ

6.9 PS R99 Call Drop Ratio (PCH) Correct the counter name VS.PSR99.F2P.Succ to

VS.DCCC.Succ.F2P

2.4 PS Radio Access Success Ratio Correct the counter name

RRC.SuccConnEstab.OrgItrCall to

RRC.SuccConnEstab.OrgInterCall

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

RAN




2


13/121

Compared with issue 01 (2010-04-10) of V900R012C01, this issue includes the following new

topics:

l 2.20 RRC Congestion Ratio

l 2.21 CS RAB Congestion Ratio

l 2.22 PS RAB Congestion Ratio

l 5.6 Intra-frequency Hard Handover Success Ratio

l 5.3 AMR Soft Handover Success Ratio

l 5.4 CS64 Soft Handover Success Ratio

l 5.5 PS Soft Handover Success Ratio

l 3.12 CE Consumption for a NodeB Cell

l 3.13 Hardware Configured CE for a NodeB

l 3.14 Shared Group Configured License CE for a NodeB

l 3.15 Shared Group License CE Consumption for a NodeB

l 3.16 License Group Configured CE for a NodeB

l 3.17 License Group CE Consumption for a NodeB

l 7.4 Average UL BLER for PS Service

l 3.18 RTWP (Received Total Wideband Power)

l 3.19 TCP (Transmitted Carrier Power)

l 3.20 R99 Code Utilization

l 6.1 CS Service Drop Ratio

l 6.10 PS BE Call Drop Ratio

l 6.7 PS Call Drop Ratio (PCH)

l 6.9 PS R99 Call Drop Ratio (PCH)

l 6.12 HSDPA Call Drop Ratio (PCH)

l 6.14 HSUPA Call Drop Ratio (PCH)

l 7.5 HSDPA Throughput

l 7.6 HSUPA Throughput

l 8.3 Number of PS R99 Users

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

changes:

Content Description

3.10 HSDPA Unavailability

duration

Correct the counter name VS.Hsdpa.UnavailTime

to VS.Cell.HSDPA.UnavailTime

8.4 Number of HSDPA Users Modify the KPI name from Mean Number of

HSDPA Users to Number of HSDPA Users

New counterVS.HSDPA.UE.Max.Cell was added

in the section Associated Counters

RAN




3


14/121

Content Description

8.5 Number of HSUPA Users Modify the KPI name from Mean Number of

HSUPA Users to Number of HSUPA Users

New counterVS.HSUPA.UE.Max.Cell was addedin the section Associated Counters

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

RAN




4


15/121

2 AccessibilityAbout 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

2.2 RRC Setup Success Ratio

2.3 Radio Access Success Ratio

2.4 PS Radio Access Success Ratio

2.5 CS Radio Access Success Ratio

2.6 AMR RAB Setup Success Ratio

2.7 VP RAB Setup Success Ratio

2.8 CS RAB Setup Success Ratio

2.9 PS RAB Setup Success Ratio

2.10 HSDPA RAB Setup Success Ratio

2.11 HSUPA RAB Setup Success Ratio

2.12 PS E-FACH RAB Setup Success Ratio

2.13 CS over HSPA RAB Setup Success Ratio

2.14 HSDPA 64QAM RAB Setup Success Ratio

2.15 HSDPA MIMO RAB Setup Success Ratio

2.16 HSDPA DC RAB Setup Success Ratio

2.17 HSDPA MIMO64QAM RAB Setup Success Ratio

2.18 PTM Channel Setup Success Ratio

2.19 PTP Channel Setup Success Ratio

RAN

KPI Reference 2 Accessibility



5


16/121

2.20 RRC Congestion Ratio

2.21 CS RAB Congestion Ratio

2.22 PS RAB Congestion Ratio

RAN




6


17/121

2.1 IU Paging Success Ratio

Table 2-1 IU Paging Success Ratio

Name IU Paging Success Ratio

Formula

Description This KPI is used to check the successful paging responses to the 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 receivesthe 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

Table 2-2 RRC Setup Success Ratio

Name RRC Setup Success Ratio

Formula

RAN




7


18/121

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.

RAN




8


19/121

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.IRATCelRes+

RRC.AttConnEstab.IRATCCO +

RAN




9


20/121

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.

2.3 Radio Access Success Ratio

Table 2-3 Radio Access Success Ratio

Name Radio Access Success Ratio

Formula

Description This KPI is used to check the Radio Access Success Ratio. The details of the

Access Failures caused by the SCCP congestion are not provided in this call

setup procedure.

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

Procedure:

The RAB Setup Attempt Procedure starts when the CN sends an RAB

ASSIGNMENT REQUEST message to the RNC. The message containsinformation 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.

RAN




10


21/121

Associated

Counters

l Radio Access Success Ratio (Cell) =

2.2 RRC Setup Success Ratio*

{[(VS.RAB.SuccEstabCS.Conv+

VS.RAB.SuccEstabCS.Str )+(VS.RAB.SuccEstabPS.Conv+

VS.RAB.SuccEstabPS.Str +

VS.RAB.SuccEstabPS.Int +

VS.RAB.SuccEstabPS.Bkg )]/

[(VS.RAB.AttEstabCS.Conv+

VS.RAB.AttEstabCS.Str )+

(VS.RAB.AttEstabPS.Conv+

VS.RAB.AttEstabPS.Str +

VS.RAB.AttEstabPS.Int+VS.RAB.AttEstabPS.Bkg )]} x 100%

l Radio Access Success Ratio (RNC) =

2.2 RRC Setup Success Ratio*

{[(VS.RAB.SuccEstabCS.Conv.RNC +

VS.RAB.SuccEstabCS.Str.RNC )+

(VS.RAB.SuccEstabPS.Conv.RNC+

VS.RAB.SuccEstabPS.Str.RNC +

VS.RAB.SuccEstabPS.Int.RNC +

VS.RAB.SuccEstabPS.Bkg.RNC )]/[(VS.RAB.AttEstabCS.Conv.RNC+

VS.RAB.AttEstabCS.Str.RNC )+

(VS.RAB.AttEstabPS.Conv.RNC+

VS.RAB.AttEstabPS.Str.RNC +

VS.RAB.AttEstabPS.Int.RNC+

VS.RAB.AttEstabPS.Bkg.RNC)]} x 100%

Object CELL, RNC

Unit/Range %

Note None

2.4 PS Radio Access Success Ratio

Table 2-4 PS Radio Access Success Ratio

Name PS Radio Access Success Ratio

RAN




11


22/121

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

(RRC.AttConnEstab.OrgBkgCall+



RRC.AttConnEstab.TmInterCall )]*

2.9 PS RAB Setup Success Ratio x 100%

l PS Radio Access Success Ratio (RNC) =

[(RRC.SuccConnEstab.OrgBkgCall +

RRC.SuccConnEstab.OrgInterCall +


RRC.SuccConnEstab.TmItrCall )/

(RRC.AttConnEstab.OrgBkgCall+



RRC.AttConnEstab.TmInterCall )]*

2.9 PS RAB Setup Success Ratio x 100%

Object CELL, RNC

Unit/Range %

Note None

2.5 CS Radio Access Success Ratio

RAN




12


23/121

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


RRC.AttConnEstab.TmConvCall+

RRC.AttConnEstab.EmgCall )]*

2.8 CS RAB Setup Success Ratio x 100%

l CS Radio Access Success Ratio (RNC) =



RRC.SuccConnEstab.EmgCall )/


RRC.AttConnEstab.TmConvCall+

RRC.AttConnEstab.EmgCall )]*

2.8 CS RAB Setup Success Ratio x 100%

Object CELL,RNC

Unit/Range %

Note None

2.6 AMR RAB Setup Success Ratio

Table 2-6 AMR RAB Setup Success Ratio

Name AMR RAB Setup Success Ratio

RAN




13


24/121

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 %


2.7 VP RAB Setup Success Ratio

Table 2-7 VP RAB Setup Success Ratio

Name VP RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB setup success ratio of CS 64 Kbit/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 %

RAN




14


25/121


2.8 CS RAB Setup Success Ratio

Table 2-8 CS RAB Setup Success Ratio

Name CS RAB Setup Success Ratio

Formula

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

AssociatedCounters

l CS RAB Setup Success Ratio (Cell) =

[(VS.RAB.SuccEstabCS.Conv+ VS.RAB.SuccEstabCS.Str )/

(VS.RAB.AttEstabCS.Conv+ VS.RAB.AttEstabCS.Str)] x 100%

l CS RAB Setup Success Ratio (RNC) =

[(VS.RAB.SuccEstabCS.Conv.RNC +

VS.RAB.SuccEstabCS.Str.RNC )/

(VS.RAB.AttEstabCS.Conv.RNC+ VS.RAB.AttEstabCS.Str.RNC)]

x 100%

Object CELL, RNC

Unit/Range %

Note None

2.9 PS RAB Setup Success Ratio

Table 2-9 PS RAB Setup Success Ratio

Name PS RAB Setup Success Ratio

RAN




15


26/121

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.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.10 HSDPA RAB Setup Success Ratio

RAN




16


27/121

Table 2-10 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


procedure is complete when the RNC sends an RAB ASSIGNMENTRESPONSE 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 %


2.11 HSUPA RAB Setup Success Ratio

Table 2-11 HSUPA RAB Setup Success Ratio

Name HSUPA RAB Setup Success Ratio

Formula

Description This KPI is used to check the RAB Setup Success Ratio of the HSUPA service

in an RNC or a cluster.

The HSUPA RAB Setup Success Procedure starts when the RNC receives a



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.

RAN




17


28/121

Associated

Counters

HSUPA RAB Setup Success Ratio (Cell) =

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

Object CELL

Unit/Range %


2.12 PS E-FACH RAB Setup Success Ratio

Table 2-12 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%

CELL

Unit/Range %


2.13 CS over HSPA RAB Setup Success Ratio

Table 2-13 CS over HSPA RAB Setup Success Ratio

Name CS over HSPA RAB Setup Success Ratio

RAN




18


29/121

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.

AssociatedCounters

CS over HSPA RAB Setup Success Ratio (Cell) =

(VS.HSPA.RAB.SuccEstab.CS.Conv /

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

Object CELL

Unit/Range %


2.14 HSDPA 64QAM RAB Setup Success Ratio

Table 2-14 HSDPA 64QAM RAB Setup Success Ratio

Name HSDPA 64QAM RAB Setup Success Ratio

Formula

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

The HSDPA 64 QAM RAB Setup Success Procedure starts when the RNC

receives an RADIO BEARER SETUP COMPLETE message from the UE.



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.

RAN




19


30/121

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 %


2.15 HSDPA MIMO RAB Setup Success Ratio

Table 2-15 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.



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

Unit/Range %


2.16 HSDPA DC RAB Setup Success Ratio

Table 2-16 HSDPA DC RAB Setup Success Ratio

Name HSDPA DC RAB Setup Success Ratio

RAN




20


31/121

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



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 %


2.17 HSDPA MIMO64QAM RAB Setup Success Ratio

Table 2-17 HSDPA MIMO64QAM RAB Setup Success Ratio

Name HSDPA MIMO64QAM RAB Setup Success Ratio

Formula

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

64QAM service in an RNC or a cluster.

The HSDPA MIMO 64QAM RAB Setup Success procedure starts when the

RNC receives a RADIO BEARER SETUP COMPLETE message from the

UE. This procedure is complete when the RNC sends an RAB

ASSIGNMENT RESPONSE message to the CN.

The HSDPA MIMO 64QAM RAB Setup Attempt procedure is complete

when the RNC receives an RAB ASSIGNMENT REQUEST message from

the CN for setting up the HSDPA service using MIMO+64QAM.

Associated

Counters

HSDPA MIMO64QAM RAB Setup Success Ratio=

(VS.HSDPA.RAB.MIMO64QAM.SuccEstab /

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

RAN




21


32/121

Object CELL

Unit/Range %


2.18 PTM Channel Setup Success Ratio

Table 2-18 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 ) x

100%

Object CELL

Unit/Range %


2.19 PTP Channel Setup Success Ratio

Table 2-19 PTP Channel Setup Success Ratio

Name PTP Channel Setup Success Ratio

Formula

RAN




22


33/121

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

Object CELL

Unit/Range %


2.20 RRC Congestion Ratio

Table 2-20 RRC Congestion Ratio

Name RRC Congestion Ratio

Formula

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

After receiving an RRC CONNECTION REQUEST message from the UE,

the RNC initiates admission procedures for resources of code, power, CE,

and Iub bandwidth. If the resource admission fails, the RRC Setup Failure

due to Congestion procedure is complete when the RNC sends an RRC

CONNECTION REJECT message to the UE.

The RRC Connection Attempt for service Procedure is complete when the

RNC receives an RRC CONNECTION REQUEST message from the UE.

Associated

Counters

RRC Congestion Ratio=

[(VS.RRC.Rej.ULPower.Cong+

VS.RRC.Rej.DLPower.Cong+

VS.RRC.Rej.ULIUBBand.Cong+

VS.RRC.Rej.DLIUBBand.Cong+

VS.RRC.Rej.ULCE.Cong +

VS.RRC.Rej.DLCE.Cong +

VS.RRC.Rej.Code.Cong )/

VS.RRC.AttConnEstab.Sum] x 100%

RAN




23


34/121

Object CELL

Unit/Range %

Note None

2.21 CS RAB Congestion Ratio

Table 2-21 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

RAN




24


35/121

2.22 PS RAB Congestion Ratio

Table 2-22 PS RAB Congestion Ratio

Name PS RAB Congestion Ratio

Formula

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

The PS RAB Setup Fails due to Congestion procedure is complete when the

RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The

message contains information about one of the following RAB assignment

responses: "No Radio Resources Available in Target cell", "Requested

Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL

not Available", "Requested Guaranteed Bit Rate not Available", "Requested

Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate

for UL not Available".

The PS RAB Setup Attempt Procedure starts when the RNC receives an RAB

ASSIGNMENT REQUEST message from the SGSN in the PS domain. The

message contains information about one of the following RAB assignment

requests: Conversational services, Streaming services, Interactive Services,

Background Services.

Associated

Counters

PS RAB Congestion Ratio=

[(VS.RAB.FailEstabPS.DLIUBBand.Cong+

VS.RAB.FailEstabPS.ULIUBBand.Cong+

VS.RAB.FailEstabPS.ULCE.Cong+

VS.RAB.FailEstabPS.DLCE.Cong+

VS.RAB.FailEstabPS.Code.Cong+

VS.RAB.FailEstabPS.ULPower.Cong+

VS.RAB.FailEstabPS.DLPower.Cong)/


VS.RAB.AttEstabPS.Str+

VS.RAB.AttEstabPS.Int +

VS.RAB.AttEstabPS.Bkg )] x 100%

Object CELL

Unit/Range %

Note None

RAN




25


36/121

3 AvailabilityAbout 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

3.2 Paging Congestion Ratio

3.3 Call Admission Refused Ratio

3.4 Congested Cell Ratio

3.5 Radio Network Unavailability Ratio

3.6 Average CPU Load

3.7 IUB Bandwidth Utilizing Ratio (UL)

3.8 IUB Bandwidth Utilizing Ratio (DL)

3.9 Cell Unavailability duration

3.10 HSDPA Unavailability duration

3.11 HSUPA Unavailability duration

3.12 CE Consumption for a NodeB Cell

3.13 Hardware Configured CE for a NodeB

3.14 Shared Group Configured License CE for a NodeB

3.15 Shared Group License CE Consumption for a NodeB

3.16 License Group Configured CE for a NodeB

3.17 License Group CE Consumption for a NodeB

3.18 RTWP (Received Total Wideband Power)

3.19 TCP (Transmitted Carrier Power)

RAN

KPI Reference 3 Availability



26


37/121

3.20 R99 Code Utilization

RAN




27


38/121

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

Table 3-2 Paging Congestion Ratio

Name Paging Congestion Ratio

RAN




28


39/121

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.


This counter provides the number of losses of PAGING TYPE 1 message

due to PCH congestion in a cell.


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

RAN




29


40/121

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.


The failed number of Cell Resource Requests for New Call setup is

counted after RNC requesting cell resources for the UE successfully.


The number of Cell Resource Requests during RAB establishment for

Cell. After RNC receiving the RAB ASSIGNMENT REQUEST messagefrom 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 %


3.4 Congested Cell Ratio

Table 3-4 Congested Cell Ratio

Name Congested Cell Ratio

Formula

Description This KPI is used to check the utility ratio of radio network resources 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.


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.

RAN




30


41/121

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

Table 3-5 Radio Network Unavailability Ratio

Name Radio Network Unavailability Ratio

Formula

Description This KPI describes the ratio of cell unavailable duration to the number of 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.


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

Table 3-6 Average CPU Load

Name Average CPU Load

RAN




31


42/121

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

Description This KPI provides the CPU usage of the XPU in a measurement period. It

also indicates the load and operating performance of CPU on the XPU in the

measurement period.

The CPU usage of the XPU is accumulated every second in the measurement

period.

Associated

Counters

Average CPU Load= VS.XPU.CPULOAD.MEAN

Object XPU

Unit/Range %

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

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 and

configured Iub bandwidth in a NodeB for downlink during busy hours. The

consumption of interactive and background services cannot maintain the full

rate all the time on the configured Iub bandwidth.

The UL Bandwidth could be measured on ATM Physical Ports or IP physical

Ports. The numerator is defined as the average used bandwidth on an ATM

or IP physical ports during a measurement period counted by NodeB. The

NodeB measures the used UL bandwidth on the physical port every five

seconds for 15 minutes and then calculates the average value. The counter

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

measurement at the physical layer.

RAN




32


43/121

Associated

Counters

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 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.4provide the physical

bandwidths of ports rather than the actual available bandwidths of ports.

Therefore, if the actual available bandwidth of a port is different from the

physical bandwidth of the port, the value of this KPI calculated by using this

formula is incorrect, and you are advised to use the actual available

bandwidths 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

RAN




33


44/121

Description This KPI is used to check the ratio of consumption of Iub bandwidth and

configured Iub bandwidth in a NodeB for downlink during busy hours. The

consumption of interactive and background services cannot maintain the full

rate all the time on the configured Iub bandwidth.

The DL Bandwidth could be measured on ATM Physical Ports or IP physicalPorts. The numerator is defined as the average used bandwidth on an ATM

or IP physical ports during a measurement period counted by NodeB. The

NodeB measures the used DL bandwidth on the physical port every five

seconds for 15 minutes and then calculates the average value. The counter

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

measurement at the physical layer.

Associated

Counters

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

physical bandwidths of ports rather than the actual available bandwidths of

ports. Therefore, if the actual available bandwidth of a port is different from

the physical bandwidth of the port, the value of this KPI calculated by using

this formula is incorrect, and you are advised to use the actual available

bandwidths as the denominator to calculate this KPI.

RAN




34


45/121

3.9 Cell Unavailability duration

Table 3-9 Cell Unavailability duration

Name Cell Unavailability duration

Description This KPI is used to check the total duration of the unavailability of a cell

caused by system fault in a measurement period.

Associated

Counters

VS.Cell.UnavailTime.Sys

Object CELL

Unit/Range s

Note None

3.10 HSDPA Unavailability duration

Table 3-10 HSDPA Unavailability duration

Name HSDPA Unavailability duration

Description This KPI is used to check the total duration of unavailability of the 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

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

RAN




35


46/121

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

Table 3-13 Hardware Configured CE for a NodeB

Name Hardware Configured CE for a NodeB

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

RAN




36


47/121

Associated

Counters

VS.HW.ULCreditAvailable

VS.HW.DLCreditAvailable

Object NodeB

Unit/Range Numbers

Note None

3.14 Shared Group Configured License CE for a NodeB

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

Name Shared Group Configured License CE for a NodeB

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

Table 3-15 Shared Group License CE Consumption for a NodeB

Name Shared Group License CE Consumption for a NodeB

Description The Average/Maximum/Minimum number of shared DL/UL CEs consumed

by an operator, or by HSUPA service.

RAN




37


48/121

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

Table 3-17 License Group CE Consumption for a NodeB

Name License Group CE Consumption for a NodeB

Description The Average/Maximum/Minimum number of shared DL/UL CEs consumed

by a licensed group, or by HSUPA services.

RAN




38


49/121

Associated

Counters

l UL Statistics

VS.LC.ULMean.LicenseGroup

VS.LC.ULMax.LicenseGroup

VS.LC.ULMin.LicenseGroupVS.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.

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

RAN




39


50/121

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/Min

Ran Kpi Reference(v900r013c00_03)(PDF)-En

Documents