Gbss16.0&Ran16.0 Kpi Reference (01) (PDF) - en

GBSS16.0&RAN16.
KPI Reference
Issue
01
Date
2014-04-29
HUAWEI TECHNOLOGIES CO., LTD.
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
Email:
support@huawei.com
Issue 01 (2014-04-29)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
GBSS16.0&RAN16.0
KPI Reference
About This Document
About This Document

Purpose
The purpose of this document is to specify the GBSS&RAN KPI definition as well as counters
used to calculate the KPI. The original KPI definition comes from the experiences of commercial
network management and radio network optimization. The KPI definition shall be updated
according to the requirement from customers.
Version
The following table lists the product versions involved in this document.
Product Name
Product Version
BSC6910
V100R016C00
BSC6900
V900R016C00
BTS3900
V100R009C00
BTS3900A
The mapping single-mode base station

versions are:
BTS3900L
l GBTS: V100R016C00
BTS3900AL
l eGBTS: V100R016C00
DBS3900
l NodeB: V200R016C00
BTS3900C
V100R009C00
The mapping single-mode base station
version is:
NodeB: V200R016C00
BTS3812AE
NodeB: V100R016C00
BTS3812A
BTS3812E
DBS3800
Issue 01 (2014-04-29)

ii
GBSS16.0&RAN16.0
KPI Reference
About This Document
Intended Audience
This document is intended for:
l
Network planners
Field engineers
System engineers
Organization
1 Changes in the GBSS&RAN KPI Reference
This chapter describes the changes made in the GBSS&RAN KPI Reference.
2 GSM Service KPI
The following KPIs are GSM Service KPIs.
3 UMTS Service KPI
The following KPIs are UMTS Service KPIs.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
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.
avoided, may result in minor or moderate injury.
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.
Issue 01 (2014-04-29)

iii
GBSS16.0&RAN16.0
KPI Reference
About This Document
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
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.
Issue 01 (2014-04-29)
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.

iv
GBSS16.0&RAN16.0
KPI Reference
About This Document
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.
Issue 01 (2014-04-29)
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.

GBSS16.0&RAN16.0
KPI Reference
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes in the GBSS&RAN KPI Reference............................................................................1
2 GSM Service KPI...........................................................................................................................3
2.1 CS Accessibility KPIs....................................................................................................................................................5
2.1.1 Immediate Assignment Success Rate..........................................................................................................................5
2.1.2 Congestion Rate on SDCCH per Cell (Due to Busy)..................................................................................................5
2.1.3 Call Drop Rate on SDCCH..........................................................................................................................................6
2.1.4 Assignment Success Rate............................................................................................................................................6
2.1.5 TCH Congestion Rate (Overflow)...............................................................................................................................7
2.1.6 TCH Seizure Success Rate..........................................................................................................................................7
2.1.7 Call Establishment Success Rate.................................................................................................................................8
2.1.8 BSS Call Establishment Success Rate.........................................................................................................................9
2.1.9 Paging Overload Rate..................................................................................................................................................9
2.2 CS CPU Usage KPI......................................................................................................................................................10
2.2.1 Average CPU Usage of the XPU(Only for BSC6900)..............................................................................................10
2.2.2 Average CPU Usage of the CPU(Only for BSC6910)..............................................................................................10
2.3 CS Mobility KPIs.........................................................................................................................................................11
2.3.1 Handover Success Rate.............................................................................................................................................11
2.3.2 Um-Interface Handover Success Rate.......................................................................................................................11
2.3.3 Intra-BSC Handover Success Rate............................................................................................................................12
2.3.4 Um-Interface Intra-BSC Handover Success Rate......................................................................................................12
2.3.5 Incoming Inter-BSC Handover Success Rate............................................................................................................13
2.3.6 Um-Interface Incoming Inter-BSC Handover Success Rate.....................................................................................13
2.3.7 Outgoing Inter-BSC Handover Success Rate............................................................................................................14
2.3.8 Um-Interface Outgoing Inter-BSC Handover Success Rate.....................................................................................14
2.3.9 Success Rate of Dual-Band Handovers (900/850/810-1800/1900)...........................................................................15
2.3.10 Success Rate of Dual-Band Handovers (1800/1900-900/850/810).........................................................................16
2.4 CS Receive Quality KPIs.............................................................................................................................................16
2.4.1 Rx_QUALITY(UPLINK).........................................................................................................................................17
2.4.2 Rx_QUALITY(DOWNLINK)..................................................................................................................................19
2.5 CS Resource Usage KPIs.............................................................................................................................................21
2.5.1 Traffic Volume on SDCCH.......................................................................................................................................21
Issue 01 (2014-04-29)

vi
GBSS16.0&RAN16.0
KPI Reference
Contents
2.5.2 Traffic Volume on TCH............................................................................................................................................22

2.5.3 TCHH Traffic Volume..............................................................................................................................................22
2.5.4 TCH Availability.......................................................................................................................................................22
2.5.5 TCH Resource Usage................................................................................................................................................23
2.5.6 TRX Usage................................................................................................................................................................24
2.5.7 SDCCH Availability..................................................................................................................................................24
2.6 CS Retainability KPIs...................................................................................................................................................25
2.6.1 Call Drop Rate on TCH per Cell (Including Handover)............................................................................................25
2.6.2 Call Drop Rate on TCH per Cell (Excluding Handover)..........................................................................................26
2.6.3 Traffic Call Drop Rate per Cell.................................................................................................................................29
2.6.4 Radio Drop Rate of TCH...........................................................................................................................................29
2.6.5 Handover Drop Rate of TCH.....................................................................................................................................30
2.6.6 Call Complete Establishment Success Rate..............................................................................................................30
2.7 PS Accessibility KPIs...................................................................................................................................................31
2.7.1 Uplink Assignment Success Rate..............................................................................................................................31
2.7.2 Downlink Assignment Success Rate.........................................................................................................................31
2.7.3 Uplink TBF Establishment Success Rate..................................................................................................................32
2.7.4 Downlink TBF Establishment Success Rate.............................................................................................................32
2.7.5 Uplink EGPRS TBF Establishment Success Rate.....................................................................................................33
2.7.6 Downlink EGPRS TBF Establishment Success Rate................................................................................................34
2.7.7 Uplink TBF Congestion Rate....................................................................................................................................34
2.7.8 Downlink TBF Congestion Rate...............................................................................................................................35
2.7.9 Uplink EGPRS TBF Congestion Rate.......................................................................................................................35
2.7.10 Downlink EGPRS TBF Congestion Rate................................................................................................................36
2.8 PS Data Throughput KPIs............................................................................................................................................36
2.8.1 Upload Data Throughput (kbit/s)..............................................................................................................................36
2.8.2 Download Data Throughput (kbit/s)..........................................................................................................................37
2.9 PS Delay KPIs..............................................................................................................................................................37
2.9.1 Ping Delay (ms).........................................................................................................................................................37
2.9.2 Mean Delay of PDP Activation (ms).........................................................................................................................38
2.9.3 Mean Delay of Attach (ms).......................................................................................................................................38
2.9.4 Service Interruption Delay for Cell Reselection (ms)...............................................................................................39
2.10 PS Resource Usage KPIs............................................................................................................................................39
2.10.1 Uplink PDTCH/PACCH Usage...............................................................................................................................40
2.10.2 Downlink PDTCH/PACCH Usage..........................................................................................................................40
2.10.3 PDCH Occupation Rate...........................................................................................................................................40
2.10.4 Proportion of Dynamic PDCHs Reclaimed by BSC...............................................................................................41
2.11 PS Retainability KPIs.................................................................................................................................................41
2.11.1 Uplink TBF Drop Rate............................................................................................................................................41
2.11.2 Downlink TBF Drop Rate.......................................................................................................................................42
2.11.3 Uplink EGPRS TBF Drop Rate...............................................................................................................................43
Issue 01 (2014-04-29)

vii
GBSS16.0&RAN16.0
KPI Reference
Contents
2.11.4 Downlink EGPRS TBF Drop Rate..........................................................................................................................43

2.12 PS Transmission Performance KPIs...........................................................................................................................44
2.12.1 Retransmission Rate of Uplink GPRS RLC Data Blocks.......................................................................................44
2.12.2 Retransmission Rate of Downlink GPRS RLC Data Blocks..................................................................................44
2.12.3 Retransmission Rate of Uplink EGPRS RLC Data Blocks.....................................................................................45
2.12.4 Retransmission Rate of Downlink EGPRS RLC Data Blocks................................................................................46
2.12.5 Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4...................................................................................47
2.12.6 Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4..............................................................................47
2.12.7 Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9..............................................................48
2.12.8 Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9.........................................................49
2.12.9 Average Throughput of Uplink GPRS RLC per PDCH (kbit/s).............................................................................50
2.12.10 Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)......................................................................50
2.12.11 Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s).........................................................................51
2.12.12 Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)....................................................................52
2.12.13 Average Throughput of Uplink GPRS RLC per Cell (kbit/s)...............................................................................54
2.12.14 Average Throughput of Downlink GPRS RLC per Cell (kbit/s)..........................................................................54
2.12.15 Average Throughput of Uplink EGPRS RLC per Cell (kbit/s).............................................................................55
2.12.16 Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)........................................................................56
2.12.17 Average Throughput of Uplink GPRS LLC per User (kbit/s)...............................................................................57
2.12.18 Average Throughput of Downlink GPRS LLC per User (kbit/s)..........................................................................58
2.12.19 Average Throughput of Uplink EGPRS LLC per User (kbit/s)............................................................................58
2.12.20 Average Throughput of Downlink EGPRS LLC per User (kbit/s).......................................................................59
3 UMTS Service KPI......................................................................................................................60

3.1 Accessibility.................................................................................................................................................................61
3.1.1 IU Paging Success Ratio............................................................................................................................................61
3.1.2 RRC Setup Success Ratio..........................................................................................................................................61
3.1.3 Radio Access Success Ratio......................................................................................................................................65
3.1.4 PS Radio Access Success Ratio.................................................................................................................................66
3.1.5 CS Radio Access Success Ratio................................................................................................................................67
3.1.6 AMR RAB Setup Success Ratio...............................................................................................................................68
3.1.7 VP RAB Setup Success Ratio...................................................................................................................................69
3.1.8 CS RAB Setup Success Ratio....................................................................................................................................70
3.1.9 CS+PS Combined Service RAB Setup Success Rate................................................................................................71
3.1.10 PS+PS Combined Service RAB Setup Success Rate..............................................................................................72
3.1.11 PS RAB Setup Success Ratio..................................................................................................................................72
3.1.12 HSDPA RAB Setup Success Ratio.........................................................................................................................74
3.1.13 HSUPA RAB Setup Success Ratio.........................................................................................................................74
3.1.14 PS E-FACH RAB Setup Success Ratio...................................................................................................................75
3.1.15 CS over HSPA RAB Setup Success Ratio..............................................................................................................76
3.1.16 HSDPA 64QAM RAB Setup Success Ratio...........................................................................................................76
3.1.17 HSDPA MIMO RAB Setup Success Ratio.............................................................................................................77
Issue 01 (2014-04-29)

viii
GBSS16.0&RAN16.0
KPI Reference
Contents
3.1.18 HSDPA DC RAB Setup Success Ratio...................................................................................................................78

3.1.19 HSDPA MIMO64QAM RAB Setup Success Ratio................................................................................................78
3.1.20 PTM Channel Setup Success Ratio.........................................................................................................................79
3.1.21 PTP Channel Setup Success Ratio...........................................................................................................................80
3.1.22 RRC Congestion Ratio............................................................................................................................................80
3.1.23 CS RAB Congestion Ratio......................................................................................................................................81
3.1.24 PS RAB Congestion Ratio.......................................................................................................................................82
3.1.25 PS R99 RAB Setup Success Rate............................................................................................................................83
3.1.26 WB AMR RAB Setup Success Rate.......................................................................................................................84
3.1.27 Success Ratio of Cell Updates Initiated by CS Service of PCH UEs......................................................................84
3.1.28 Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs.............................................................85
3.1.29 CS RAB Setup Success Ratio of PCH UEs.............................................................................................................87
3.1.30 New PS RAB Setup Success Ratio of PCH UEs.....................................................................................................88
3.2 Availability...................................................................................................................................................................88
3.2.1 Worst Cell Ratio........................................................................................................................................................89
3.2.2 Paging Congestion Ratio...........................................................................................................................................89
3.2.3 Call Admission Refused Ratio..................................................................................................................................90
3.2.4 Congested Cell Ratio.................................................................................................................................................91
3.2.5 Radio Network Unavailability Ratio.........................................................................................................................92
3.2.6 Average CPU Load....................................................................................................................................................92
3.2.7 Iub Port Available Bandwidth Utilizing Ratio (UL).................................................................................................93
3.2.8 Iub Port Available Bandwidth Utilizing Ratio (DL).................................................................................................94
3.2.9 Cell Unavailability duration......................................................................................................................................95
3.2.10 HSDPA Unavailability duration..............................................................................................................................96
3.2.11 HSUPA Unavailability duration..............................................................................................................................96
3.2.12 CE Consumption for a NodeB Cell.........................................................................................................................96
3.2.13 Hardware Configured CE for a NodeB...................................................................................................................97
3.2.14 Shared Group Configured License CE for a NodeB...............................................................................................97
3.2.15 Shared Group License CE Consumption for a NodeB............................................................................................98
3.2.16 License Group Configured CE for a NodeB...........................................................................................................98
3.2.17 License Group CE Consumption for a NodeB........................................................................................................99
3.2.18 RTWP (Received Total Wideband Power)..............................................................................................................99
3.2.19 TCP (Transmitted Carrier Power).........................................................................................................................100
3.2.20 R99 Code Utilization.............................................................................................................................................101
3.2.21 Number of Codes Used by HS-PDSCHs...............................................................................................................101
3.2.22 HSDPA Efficiency................................................................................................................................................102
3.3 Coverage.....................................................................................................................................................................103
3.3.1 UL Interference Cell Ratio......................................................................................................................................103
3.3.2 Soft Handover Overhead.........................................................................................................................................103
3.4 Mobility......................................................................................................................................................................106
3.4.1 Soft Handover Success Ratio..................................................................................................................................106
Issue 01 (2014-04-29)

ix
GBSS16.0&RAN16.0
KPI Reference
Contents
3.4.2 Softer Handover Success Ratio...............................................................................................................................106

3.4.3 AMR Soft Handover Success Ratio........................................................................................................................107
3.4.4 CS64 Soft Handover Success Ratio.........................................................................................................................108
3.4.5 PS Soft Handover Success Ratio.............................................................................................................................108
3.4.6 Intra-frequency Hard Handover Success Ratio.......................................................................................................109
3.4.7 Inter-frequency Hard Handover Success Ratio.......................................................................................................110
3.4.8 Service Cell Change Success Ratio with SHO (H2H)............................................................................................111
3.4.9 H2H Intra-Frequency Hard Handover Success Ratio..............................................................................................111
3.4.10 H2H Inter-Frequency Hard Handover Success Ratio............................................................................................113
3.4.11 H2D Intra-Frequency Hard Handover Success Ratio............................................................................................114
3.4.12 H2D Inter-Frequency Hard Handover Success Ratio............................................................................................114
3.4.13 E2D Intra-Frequency Hard Handover Success Ratio............................................................................................115
3.4.14 H2D Channel Switch Success Ratio......................................................................................................................116
3.4.15 D2H Channel Switch Success Ratio......................................................................................................................117
3.4.16 CS W2G Inter-RAT Handover Out Success Ratio................................................................................................118
3.4.17 PS W2G Inter-RAT Handover Out Success Ratio................................................................................................118
3.4.18 PS G2W Inter-RAT Handover In Success Ratio...................................................................................................119
3.4.19 HSDPA W2G Inter-RAT Handover Out Success Ratio.......................................................................................120
3.4.20 SRNC Relocation Success Ratio...........................................................................................................................121
3.4.21 TRNC Relocation Success Ratio...........................................................................................................................122
3.4.22 E-DCH Soft Handover Success Ratio...................................................................................................................122
3.4.23 E-DCH Cell Change Success Ratio with SHO......................................................................................................123
3.4.24 E-DCH Cell Change Success Ratio with Inter-HHO............................................................................................124
3.4.25 E2D Channel Switch Success Ratio......................................................................................................................125
3.4.26 D2E Channel Switch Success Ratio......................................................................................................................126
3.4.27 E2D Handover Success Ratio with Inter HHO.....................................................................................................127
3.4.28 HSUPA W2G Inter-RAT Handover Out Success Ratio.......................................................................................128
3.4.29 MBMS Service Mode Switch Success Ratio........................................................................................................129
3.4.30 CS Inter-Frequency Hard Handover Success Rate................................................................................................129
3.4.31 PS Inter-Frequency Hard Handover Success Rate................................................................................................130
3.5 Retainability................................................................................................................................................................130
3.5.1 CS Service Drop Ratio............................................................................................................................................130
3.5.2 CS Call Drop Rate in CS+PS Combined Services..................................................................................................131
3.5.3 PS Call Drop Rate in CS+PS Combined Services...................................................................................................132
3.5.4 AMR Call Drop Ratio..............................................................................................................................................133
3.5.5 WB AMR Call Drop Rate.......................................................................................................................................134
3.5.6 VP Call Drop Ratio..................................................................................................................................................134
3.5.7 AMR Traffic Drop Ratio.........................................................................................................................................135
3.5.8 VP Traffic Drop Ratio.............................................................................................................................................137
3.5.9 PS Call Drop Ratio..................................................................................................................................................137
3.5.10 PS Call Drop Ratio (PCH).....................................................................................................................................138
Issue 01 (2014-04-29)

GBSS16.0&RAN16.0
KPI Reference
Contents
3.5.11 PS Call Drop Ratio (PCH & Combined Service)..................................................................................................141

3.5.12 PS R99 Call Drop Ratio.........................................................................................................................................143
3.5.13 PS R99 Call Drop Ratio (PCH).............................................................................................................................144
3.5.14 PS BE Call Drop Ratio..........................................................................................................................................145
3.5.15 HSDPA Call Drop Ratio........................................................................................................................................146
3.5.16 HSDPA Call Drop Ratio (PCH)............................................................................................................................147
3.5.17 HSUPA Call Drop Ratio........................................................................................................................................149
3.5.18 HSUPA Call Drop Ratio (PCH)............................................................................................................................150
3.5.19 MBMS Service PTP drop Ratio............................................................................................................................151
3.5.20 DC-HSDPA Call Drop Ratio.................................................................................................................................151
3.5.21 HSDPA 64QAM Call Drop Ratio.........................................................................................................................153
3.5.22 HSDPA MIMO Call Drop Ratio...........................................................................................................................154
3.5.23 HSDPA MIMO+64QAM Call Drop Ratio............................................................................................................155
3.6 Service Integrity.........................................................................................................................................................156
3.6.1 Average UL Throughput for PS R99 Service..........................................................................................................156
3.6.2 Average DL Throughput for PS R99 Service..........................................................................................................158
3.6.3 Average UL BLER for CS Service..........................................................................................................................160
3.6.4 Average UL BLER for PS Service..........................................................................................................................160
3.6.5 HSDPA Throughput................................................................................................................................................161
3.6.6 HSUPA Throughput................................................................................................................................................163
3.6.7 PS UL Throughput of RNC.....................................................................................................................................164
3.6.8 PS DL Throughput of RNC.....................................................................................................................................164
3.6.9 MBMS Service Throughput....................................................................................................................................165
3.7 Traffic.........................................................................................................................................................................166
3.7.1 CS Equivalent Erlang of RNC.................................................................................................................................166
3.7.2 Number of CS Users................................................................................................................................................167
3.7.3 Number of PS R99 Users.........................................................................................................................................168
3.7.4 Number of HSDPA Users........................................................................................................................................172
3.7.5 Number of HSUPA Users........................................................................................................................................172
3.7.6 Number of E-FACH Users......................................................................................................................................173
3.7.7 Number of E-RACH Users......................................................................................................................................173
3.7.8 Number of CS Over HSPA Users............................................................................................................................174
3.7.9 Number of HSDPA 64QAM Users.........................................................................................................................174
3.7.10 Number of HSDPA MIMO Users.........................................................................................................................175
3.7.11 Number of HSUPA 16QAM users........................................................................................................................175
3.7.12 Number of HSDPA MIMO64QAM Users............................................................................................................176
3.7.13 Number of MBMS Users.......................................................................................................................................176
3.7.14 HSDPA RLC Traffic Volume...............................................................................................................................177
3.7.15 HSUPA RLC Traffic Volume...............................................................................................................................178
3.7.16 R99 Service UL Traffic Volume...........................................................................................................................178
3.7.17 R99 Service DL Traffic Volume...........................................................................................................................179
Issue 01 (2014-04-29)

xi
GBSS16.0&RAN16.0
KPI Reference
Contents
3.7.18 E-FACH Traffic Volume.......................................................................................................................................182

3.7.19 E-RACH Traffic Volume......................................................................................................................................182
3.7.20 Average Number of DC-HSDPA Users................................................................................................................183
Issue 01 (2014-04-29)

xii
GBSS16.0&RAN16.0
KPI Reference
Changes in the GBSS&RAN KPI Reference

This chapter describes the changes made in the GBSS&RAN KPI Reference.
01 (2014-04-29)
This issue has no changes.
Draft A (2014-01-27)
Compared with Issue GBSS&RAN15.0 01 (2013-05-04), this issue includes the following
changes.
Change
Type
Function
change
Change Description
Added
l 3.7.7 Number of E-RACH Users

l 3.7.19 E-RACH Traffic Volume
l 3.1.27 Success Ratio of Cell Updates Initiated by CS
Service of PCH UEs
l 3.1.28 Success Ratio of Cell Updates Initiated by New PS
Service of PCH UEs
l 3.1.29 CS RAB Setup Success Ratio of PCH UEs
l 3.1.30 New PS RAB Setup Success Ratio of PCH UEs
l 3.5.20 DC-HSDPA Call Drop Ratio
l 3.5.21 HSDPA 64QAM Call Drop Ratio
l 3.5.22 HSDPA MIMO Call Drop Ratio
l 3.5.23 HSDPA MIMO+64QAM Call Drop Ratio
l 3.7.20 Average Number of DC-HSDPA Users
Issue 01 (2014-04-29)

GBSS16.0&RAN16.0
KPI Reference
Change
Type
Change Description
Modified
l 3.5.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.
l 3.5.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.
l 3.6.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)."
l 3.6.2 Average DL Throughput for PS R99 Service
Added the KPI "Average DL Throughput for PS R99 BE
Service of a Single User (Best Cell)."
l 3.6.5 HSDPA Throughput
Added the formula of calculating HSDPA throughput for 3900
series base stations in Note.
l 3.6.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.
Deleted
Editorial
change
Issue 01 (2014-04-29)
None.
None.

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
GSM Service KPI
About This Chapter

The following KPIs are GSM Service KPIs.
2.1 CS Accessibility KPIs
This chapter describes the CS accessibility KPIs that mainly indicate the call success rate when
an MS accesses the network. Low accessibility KPIs directly lead to low user satisfaction.
2.2 CS CPU Usage KPI
This chapter describes the CS CPU usage KPI that indicates the mean ratio of the busy time of
the CPU in a granularity period.
2.3 CS Mobility KPIs
This chapter describes the CS mobility KPIs that indicate the handover success rate on the move.
In addition, these KPIs indicate the capability of providing continuous services. A low handover
success rate leads to a high call drop rate.
2.4 CS Receive Quality KPIs
This chapter describes the CS receive quality KPIs that indicate the mean receive quality rank
on the TCH.
2.5 CS Resource Usage KPIs
This chapter describes the CS resource Uusage KPIs that are used to monitor the load of hot
spots and the network. These KPIs can serve as references for capacity expansion. The traffic
volume KPIs help operators obtain the ratio of traffic during peak hours to traffic during offpeak hours, to evaluate the system resource usage, and to adjust charges. The equipment
availability KPIs help operators learn about the running status of equipment, such as the running
status of channels. If these KPIs are low, equipment and transmission are faulty.
2.6 CS Retainability KPIs
This chapter describes the CS retainability KPIs that indicate the ratio of moving MSs to all MSs
as well as the moving frequency. In addition, these KPIs indicate the capability of providing
continuous services. A low success rate leads to low user satisfaction.
2.7 PS Accessibility KPIs
This chapter describes the PS accessibility KPIs that indicate whether MSs can easily access
cells. Poor PS accessibility KPIs decrease user satisfaction.
Issue 01 (2014-04-29)

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.8 PS Data Throughput KPIs

This chapter describes the PS data throughput rate KPIs. They involve the performance factors
associated with the MSs, the radio access network, and the core network. Now, the main
performance problem is concerned with the radio access network. Therefore, these KPIs indicate
the end-to-end service data link bearing capability of the GPRS network, which is directly related
to user satisfaction.
2.9 PS Delay KPIs
This chapter describes the PS delay KPIs that indicate the service response speed of the network.
Long delay decreases user satisfaction.
2.10 PS Resource Usage KPIs
This chapter describes the PS resource usage rate KPIs that indicate the network resource usage
and the busy states of services. Therefore, these KPIs can be used to guide network expansion.
2.11 PS Retainability KPIs
This chapter describes the PS retainability KPIs that mainly involve the uplink and downlink
TBF call drop rates. These KPIs indicate the capability of providing continuous services by the
network and are directly related to user satisfaction. Therefore, a high call drop rate decreases
user satisfaction.
2.12 PS Transmission Performance KPIs
This chapter describes the PS transmission performance KPIs that indicate the quality of radio
transmission links in a cell. If the RLC data block retransmission rate in a cell is high, the quality
of the radio transmission links in the cell is poor. Therefore, take corresponding measures, such
as RF optimization.
Issue 01 (2014-04-29)

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.1 CS Accessibility KPIs

This chapter describes the CS accessibility KPIs that mainly indicate the call success rate when
an MS accesses the network. Low accessibility KPIs directly lead to low user satisfaction.
2.1.1 Immediate Assignment Success Rate

This counter provides the rate of successful service accesses (except PS service accesses) to a
signaling channel. It indicates the procedure from the initiation of the channel request message
(including the retransmitted channel request message) by the MS to the reception of the establish
indication message.
Table 2-1 Immediate Assignment Success Rate
KPI Name
Immediate Assignment Success Rate
Measurement
Scope
CELL
Formula
RA303G:Immediate Assignment Success Rate = [CA303J:Call Setup

Indications (Circuit Service)] x {100}/
[CA300J:Channel Requests (Circuit Service)]
Associated
Counters
None
Notes
1. Unit: %
2. This KPI is essential.
2.1.2 Congestion Rate on SDCCH per Cell (Due to Busy)

This counter provides the rate of the number of times that all SDCCHs are busy to the total
number of requests for the SDCCH. It indicates the SDCCH collisions due to insufficient
resources.
Table 2-2 Congestion Rate on SDCCH per Cell (Due to Busy)
KPI Name
Congestion Rate on SDCCH per Cell (Due to Busy)
Measurement
Scope
CELL
Formula
RR370:Congestion Rate on SDCCH per Cell (Due to Busy) =

[K3001:Failed SDCCH Seizures due to Busy SDCCH] x{100}/
[K3000:SDCCH Seizure Requests]
Associated
Counters
Issue 01 (2014-04-29)
None

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Notes
1. Unit: %
2.1.3 Call Drop Rate on SDCCH

This counter provides the rate of call drops that occur when an SDCCH is occupied.
Table 2-3 Call Drop Rate on SDCCH
KPI Name
Call Drop Rate on SDCCH
Measurement
Scope
CELL
Formula
ZTR104C:Call Drop Rate on SDCCH = [CM30:Call Drops on SDCCH]

x {100}/
[K3003:Successful SDCCH Seizures]
Associated
Counters
None
Notes
1. Unit: %
2.1.4 Assignment Success Rate

This counter provides the rate that the requested TCHs are seized successfully in the assignment
procedure. It involves the procedure from the BSC's receiving the assignment request sent by
the MSC to the assignment completion.
Table 2-4 Assignment Success Rate
KPI Name
Assignment Success Rate
Measurement
Scope
CELL
Formula
RCA313:Assignment Success Rate = [CA313:Successful Assignments] x

{100}/
[CA310:Assignment Requests]
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.1.5 TCH Congestion Rate (Overflow)

This counter provides the rate of the number of failed immediate assignments, assignments, or
handovers due to no idle TCHs to the number of TCH seizure requests.
Table 2-5 TCH Congestion Rate (Overflow)
KPI Name
TCH Congestion Rate (Overflow)
Measurement
Scope
CELL
Formula
K3041:TCH Congestion Rate (Overflow) = {[K3021:Failed TCH Seizures

due to Busy TCH (Signaling Channel)]
+ [K3011A:Failed TCH Seizures due to Busy TCH (Traffic Channel)]
+ [K3011B:Failed TCH Seizures in TCH Handovers due to Busy TCH
(Traffic Channel)]} x {100}/
{[K3020:TCH Seizure Requests (Signaling Channel)]
+ [K3010A:TCH Seizure Requests (Traffic Channel)]
+[K3010B:TCH Seizure Requests in TCH Handovers (Traffic Channel)]}
Associated
Counters
None
Notes
1. Unit: %
2.1.6 TCH Seizure Success Rate

This counter provides the rate that the requested TCHs are seized successfully in the very early
assignment procedure, assignment procedure, or handover procedure. Assignment Success Rate
indicates the TCH seizure condition in the assignment procedure. Comparably, TCH Seizure
Success Rate indicates the successful seizure of all the TCHs.
Table 2-6 TCH Seizure Success Rate
Issue 01 (2014-04-29)
KPI Name
TCH Seizure Success Rate
Measurement
Scope
CELL

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
K3043:TCH Seizure Success Rate = {[K3023:Successful TCH Seizures

(Signaling Channel)]
+ [K3013A:Successful TCH Seizures (Traffic Channel)]
+ [K3013B:Successful TCH Seizures in TCH handovers (Traffic
Channel)]} x {100}/
{[K3020:TCH Seizure Requests (Signaling Channel)]
+ [K3010A:TCH Seizure Requests (Traffic Channel)]
+[K3010B:TCH Seizure Requests in TCH Handovers (Traffic Channel)]}
Associated
Counters
None
Notes
Unit: %
2.1.7 Call Establishment Success Rate

This counter provides the rate of successful calls initiated by the MS from the call setup procedure
to the assignment completion procedure.
Table 2-7 Call Establishment Success Rate
KPI Name
Call Establishment Success Rate
Measurement
Scope
CELL
Formula
RA333:Call Establishment Success Rate = {[CA313:Successful

Assignments]
-{[A3100K:Assignment Requests (Signaling Channel) (SDCCH)]
+[A3100A:Assignment Requests (Signaling Channel) (TCH)]
-[A312S:Failed Assignments (Signaling Channel)]
+[CA310A:Assignment Requests (TCH Assigned Repeatedly over A
Interface)]
-[CA312A:Failed Assignments (TCH Assigned Repeatedly over A
Interface)]}} x{100}/
{[A3039J:SDCCH Seizures for Speech Service]
+[A301F:TCHF Seizures for Speech Service]
+[A301HH:TCHH Seizures for Speech Service]}
Issue 01 (2014-04-29)
Associated
Counters
None
Notes
Unit: %

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.1.8 BSS Call Establishment Success Rate

This counter provides the success rates of BSS call establishments.
Table 2-8 BSS Call Establishment Success Rate
KPI Name
BSS Call Establishment Success Rate
Measurement
Scope
CELL
Formula
RA333A:BSS Call Establishment Success Rate = {[RA303G:Success

Rate of Immediate Assignments]/{100}}
x {[RCA313:Assignment Success Rate]/{100}}
x {1 - ([ZTR104C:Call Drop Rate on SDCCH])/{100}}
x {100}
Associated
Counters
RA333:Success Rate of Call Establishment
Notes
Unit: %
2.1.9 Paging Overload Rate

This counter provides the rate of the number of paging overload times of CS and PS services on
the Abis interface to deliver paging messages.
Table 2-9 Paging Overload Rate
KPI Name
Paging Overload Rate
Measurement
Scope
CELL
Formula
RL3188:Paging Overload Rate = {[L3188C:MSG CCCH LOAD IND

(PCH) Messages Sent on Abis Interface (CS Service)]
+[L3188D:MSG CCCH LOAD IND (PCH) Messages Sent on Abis
Interface (PS Service)]} x {100}/
{[A330:Delivered Paging Messages for CS Service]
+[A331:Delivered Paging Messages for PS Service]}
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.2 CS CPU Usage KPI

This chapter describes the CS CPU usage KPI that indicates the mean ratio of the busy time of
the CPU in a granularity period.
2.2.1 Average CPU Usage of the XPU(Only for BSC6900)

This counter provides the average CPU usage of the XPU in a measurement period. It indicates
the load and operating performance of the CPU on the XPU in the measurement period.
Table 2-10 Average CPU Usage of the XPU
KPI Name
Average CPU Usage of the XPU
Measurement
Scope
XPU
Formula
AR9780:Average CPU Usage of the XPU
Associated
Counters
None
Notes
1. Unit: %
2.2.2 Average CPU Usage of the CPU(Only for BSC6910)

This counter provides the average CPU usage of the CPU in a measurement period. It indicates
the load and operating performance of the CPU on the CPU in the measurement period.
Table 2-11 Average CPU Usage of the CPU
KPI Name
Average CPU Usage of the CPU
Measurement
Scope
CPU
Formula
AR9720:Average CPU Usage of the CPU
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

10
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.3 CS Mobility KPIs

This chapter describes the CS mobility KPIs that indicate the handover success rate on the move.
In addition, these KPIs indicate the capability of providing continuous services. A low handover
success rate leads to a high call drop rate.
2.3.1 Handover Success Rate

This counter provides the rate of the total number of successful handovers due to any cause to
the total number of handover requests due to any cause. The purpose of handover is to ensure
the call continuity, improve the speech quality, and reduce the cross interference in the network,
providing better services for the MSs.
Table 2-12 Handover Success Rate
KPI Name
Handover Success Rate
Measurement
Scope
CELL
Formula
RH303:Handover Success Rate

= {[CH313:Number of Successful Outgoing Internal Inter-Cell
Handovers]
+ [CH333:Successful Outgoing External Inter-Cell Handovers]} x {100}/
{[CH310:Number of Outgoing Internal Inter-Cell Handover Requests]
+ [CH330:Outgoing External Inter-Cell Handover Requests]}
Associated
Counters
RH303A:Um-Interface Handover Success Rate
Notes
1. Unit: %
2.3.2 Um-Interface Handover Success Rate

This counter provides the handover success rate on the Um interface after a handover command
is sent and before the handover is complete. Statistics taken by this item exclude target cell
handover failure due to congestion. Therefore, the value of this counter is always greater than
or equal to the value of Handover Success Rate.
Table 2-13 Um-Interface Handover Success Rate
Issue 01 (2014-04-29)
KPI Name
Um-Interface Handover Success Rate
Measurement
Scope
CELL

11
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
RH303A:Um-Interface Handover Success Rate

= {[CH313:Number of Successful Outgoing Internal Inter-Cell
Handovers]
+ [CH333:Successful Outgoing External Inter-Cell Handovers]} x {100}/
{[CH311:Number of Outgoing Internal Inter-Cell Handover Commands]
+ [CH331:Outgoing External Inter-Cell Handover Commands]}
Associated
Counters
RH303:Handover Success Rate
Notes
Unit: %
2.3.3 Intra-BSC Handover Success Rate

This counter provides the intra-BSC handover success rate, including the intra-BSC intra-cell
handovers and intra-BSC inter-cell handovers. It indicates intra-BSC handover, and reduces the
influence of other BSCs.
Table 2-14 Intra-BSC Handover Success Rate
KPI Name
Intra-BSC Handover Success Rate
Measurement
Scope
CELL
Formula
RH303B:Intra-BSC Handover Success Rate

= {[CH303:Successful Internal Intra-Cell Handovers]
+ [CH323:Number of Successful Incoming Internal Inter-Cell
Handovers]} x {100}/
{[CH300:Internal Intra-Cell Handover Requests]
+ [CH320:Number of Incoming Internal Inter-Cell Handover Requests]}
Associated
Counters
RH303C: Um-Interface Intra-BSC Handover Success Rate
Notes
Unit: %
2.3.4 Um-Interface Intra-BSC Handover Success Rate

Compared with Intra-BSC Handover Success Rate, this counter focuses on the influence of the
Um interface on handover. It involves the procedures from sending a handover command to
handover completion, and therefore reduces failures due to channel congestion.
Table 2-15 Um-Interface Intra-BSC Handover Success Rate
KPI Name
Issue 01 (2014-04-29)
Um-Interface Intra-BSC Handover Success Rate

12
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Measurement
Scope
CELL
Formula
RH303C:Um-Interface Intra-BSC Handover Success Rate

= {[CH303:Successful Internal Intra-Cell Handovers]
+ [CH323:Number of Successful Incoming Internal Inter-Cell
Handovers]} x {100}/
{[CH301:Internal Intra-Cell Handover Commands]
+ [CH321:Number of Incoming Internal Inter-Cell Handover Responses]}
Associated
Counters
RH303B:Intra-BSC Handover Success Rate
Notes
Unit: %
2.3.5 Incoming Inter-BSC Handover Success Rate

This counter provides the success rate of incoming inter-BSC handovers. It indicates the interBSC handover interaction.
Table 2-16 Incoming Inter-BSC Handover Success Rate
KPI Name
Incoming Inter-BSC Handover Success Rate
Measurement
Scope
CELL
Formula
TH343:Incoming Inter-BSC Handover Success Rate

= [CH343:Successful Incoming External Inter-Cell Handovers] x {100}/
[CH340:Incoming External Inter-Cell Handover Requests]
Associated
Counters
RH303D: Success Rate of Incoming External Inter-Cell Radio Handovers
Notes
Unit: %
2.3.6 Um-Interface Incoming Inter-BSC Handover Success Rate

This counter provides the success rate of incoming inter-BSC handovers on the Um interface.
It indicates the inter-BSC handover interaction.
Table 2-17 Um-Interface Incoming Inter-BSC Handover Success Rate
Issue 01 (2014-04-29)
KPI Name
Um-Interface Incoming Inter-BSC Handover Success Rate
Measurement
Scope
CELL

13
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
RH303D:Um-Interface Incoming Inter-BSC Handover Success Rate

= [CH343:Successful Incoming External Inter-Cell Handovers] x {100}/
[CH341:Incoming External Inter-Cell Handover Responses]
Associated
Counters
TH343: Incoming Inter-BSC Handover Success Rate
Notes
Unit: %
2.3.7 Outgoing Inter-BSC Handover Success Rate

This counter provides the success rate of outgoing inter-BSC handovers. It indicates the interBSC handover interaction.
Table 2-18 Outgoing Inter-BSC Handover Success Rate
KPI Name
Outgoing Inter-BSC Handover Success Rate
Measurement
Scope
CELL
Formula
TH333:Outgoing Inter-BSC Handover Success Rate

= [CH333:Successful Outgoing External Inter-Cell Handovers] x {100}/
[CH330:Outgoing External Inter-Cell Handover Requests]
Associated
Counters
RH303E: Um-Interface Outgoing Inter-BSC Handover Success Rate
Notes
Unit: %
2.3.8 Um-Interface Outgoing Inter-BSC Handover Success Rate

This counter provides the success rate of outgoing inter-BSC handovers on the Um interface. It
indicates the inter-BSC handover interaction.
Table 2-19 Um-Interface Outgoing Inter-BSC Handover Success Rate
KPI Name
Um-Interface Outgoing Inter-BSC Handover Success Rate
Measurement
Scope
CELL
Formula
RH303E:Um-Interface Outgoing Inter-BSC Handover Success Rate

= [CH333:Successful Outgoing External Inter-Cell Handovers] x {100}/
[CH331:Outgoing External Inter-Cell Handover Commands]
Issue 01 (2014-04-29)

14
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Associated
Counters
TH333: Outgoing Inter-BSC Handover Success Rate
Notes
Unit: %
2.3.9 Success Rate of Dual-Band Handovers (900/850/810-1800/1900)

This counter provides the rate of the number of successful inter-band (900-1800) handovers to
the number of corresponding handover requests.
Table 2-20 Success Rate of Dual-Band Handovers (900/850/810-1800/1900)
KPI Name
Success Rate of Dual-Band Handovers (900/850/810-1800/1900)
Measurement
Scope
CELL
Formula
RH303F:Success Rate of Dual-Band Handovers

(900/850/810-1800/1900)
= {[RH3031G:Incoming Internal Inter-Cell Handover Requests
(900/850/810-1800/1900)]
+ [RH3033G:Incoming External Inter-Cell Handover Requests
(900/850/810-1800/1900)]
+ [RH3035G:Outgoing External Inter-Cell Handover Requests
(900/850/810-1800/1900)]
- {[RH3031F:Failed Incoming Internal Inter-Cell Handovers
(900/850/810-1800/1900)]
+ [RH3033F:Failed Incoming External Inter-Cell Handovers
(900/850/810-1800/1900)]
+ [RH3035F:Failed Outgoing External Inter-Cell Handovers
(900/850/810-1800/1900)]}} x {100}/
{[RH3031G:Incoming Internal Inter-Cell Handover Requests
(900/850/810-1800/1900)]
(900/850/810-1800/1900)]
(900/850/810-1800/1900)]}
Issue 01 (2014-04-29)
Associated
Counters
RH303G: Success Rate of Dual-Band Handovers

(1800/1900-900/850/810)
Notes
Unit: %

15
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.3.10 Success Rate of Dual-Band Handovers

(1800/1900-900/850/810)
This counter provides the rate of the number of successful inter-band (1800-900) handovers to
the number of corresponding handover requests.
Table 2-21 Success Rate of Dual-Band Handovers (1800/1900-900/850/810)
KPI Name
Success Rate of Dual-Band Handovers (1800/1900-900/850/810)
Measurement
Scope
CELL
Formula
RH303G:Success Rate of Dual-Band Handovers

(1800/1900-900/850/810)
= {[RH3032G:Incoming Internal Inter-Cell Handover Requests
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]
- {[RH3032F:Failed Incoming Internal Inter-Cell Handovers
(1800/1900-900/850/810)]
+ [RH3034F:Failed Incoming External Inter-Cell Handovers
(1800/1900-900/850/810)]
+ [RH3036F:Failed Outgoing External Inter-Cell Handovers
(1800/1900-900/850/810)]}} x {100}/
{[RH3032G:Incoming Internal Inter-Cell Handover Requests
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]}
Associated
Counters
RH303F: Success Rate of Dual-Band Handovers

(900/850/810-1800/1900)
Notes
Unit: %
2.4 CS Receive Quality KPIs

This chapter describes the CS receive quality KPIs that indicate the mean receive quality rank
on the TCH.
Issue 01 (2014-04-29)

16
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.4.1 Rx_QUALITY(UPLINK)
This counter provides the proportion of uplink half/full rate in the mean receive quality ranks 0
to 4.
Table 2-22 Rx_QUALITY(UPLINK)
Issue 01 (2014-04-29)
KPI Name
Rx_QUALITY(UPLINK)
Measurement
Scope
TRX

17
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Rx_QUALITY(UPLINK)
={[CS410A:Number of MRs on Uplink TCHF (Mean Receive Quality
Rank 0)]
+ [CS411A:Number of MRs on Uplink TCHF (Mean Receive Quality
Rank 1)]
Rank 2)]
Rank 3)]
Rank 4)]
+ [CS410C:Number of MRs on Uplink TCHH (Mean Rank of Receive
Quality 0)]
+ [CS411C:Number of MRs on Uplink TCHH (Mean Receive Quality
Rank 1)]
Rank 2)]
Rank 3)]
Rank 4)]}x{100}/
{[CS410A:Number of MRs on Uplink TCHF (Mean Receive Quality
Rank 0)]
Rank 1)]
Rank 2)]
Rank 3)]
Rank 4)]
Rank 5)]
Rank 6)]
Rank 7)]
+ [CS410C:Number of MRs on Uplink TCHH (Mean Rank of Receive
Quality 0)]
Rank 1)]
Rank 2)]
Issue 01 (2014-04-29)

18
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI

Rank 3)]
Rank 4)]
Rank 5)]
Rank 6)]
Rank 7)]}
Associated
Counters
None
Notes
None
2.4.2 Rx_QUALITY(DOWNLINK)
This counter provides the proportion of downlink half/full rate in the mean receive quality ranks
0 to 4.
Table 2-23 Rx_QUALITY(DOWNLINK)
Issue 01 (2014-04-29)
KPI Name
Rx_QUALITY(DOWNLINK)
Measurement
Scope
TRX

19
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Rx_QUALITY(DOWNLINK)
= {[CS410B:Number of MRs on Downlink TCHF (Mean Receive Quality
Rank 0)]
+ [CS411B:Number of MRs on Downlink TCHF (Mean Receive Quality
Rank 1)]
Rank 2)]
Rank 3)]
Rank 4)]
+ [CS410D:Number of MRs on Downlink TCHH (Mean Receive Quality
Rank 0)]
Rank 1)]
Rank 2)]
Rank 3)]
Rank 4)]}x{100}/
{[CS410B:Number of MRs on Downlink TCHF (Mean Receive Quality
Rank 0)]
Rank 1)]
Rank 2)]
Rank 3)]
Rank 4)]
Rank 5)]
Rank 6)]
Rank 7)]
Rank 0)]
Rank 1)]
Rank 2)]
Issue 01 (2014-04-29)

20
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI

Rank 3)]
Rank 4)]
Rank 5)]
Rank 6)]
Rank 7)]}
Associated
Counters
None
Notes
None
2.5 CS Resource Usage KPIs

This chapter describes the CS resource Uusage KPIs that are used to monitor the load of hot
spots and the network. These KPIs can serve as references for capacity expansion. The traffic
volume KPIs help operators obtain the ratio of traffic during peak hours to traffic during offpeak hours, to evaluate the system resource usage, and to adjust charges. The equipment
availability KPIs help operators learn about the running status of equipment, such as the running
status of channels. If these KPIs are low, equipment and transmission are faulty.
2.5.1 Traffic Volume on SDCCH

This counter provides the ratio of the duration for which the MS occupies the signaling channel
to the granularity period. The signaling channels include the SDCCHs and the TCHs used for
signaling channels.
Table 2-24 Traffic Volume on SDCCH
Issue 01 (2014-04-29)
KPI Name
Traffic Volume on SDCCH
Measurement
Scope
CELL
Formula
K3004:Traffic Volume on SDCCH = [R3550M:Traffic Volume of

Signaling Channels (SDCCH)]
Associated
Counters
None
Notes

21
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.5.2 Traffic Volume on TCH

This counter provides the frequency of seizing the TCHs, that is, the actual length of activated
TCHs.
Table 2-25 Traffic Volume on TCH
KPI Name
Traffic Volume on TCH
Measurement
Scope
CELL
Formula
K3014:Traffic Volume on TCH

= [AR3551A:Mean Number of Busy TCHs (TCHF) (900/850/810 band)]
+ [AR3551B:Mean Number of Busy TCHs (TCHF) (1800/1900 Band)]
+ [AR3552A:Mean Number of Busy TCHs (TCHH) (900/850/810 band)]
+ [AR3552B:Mean Number of Busy TCHs (TCHH) (1800/1900 Band)]
Associated
Counters
None
Notes
2.5.3 TCHH Traffic Volume

This counter provides the traffic volume on the TCHs of all the cells under the control of the
BSC, excluding the traffic volume in the very early assignment.
Table 2-26 TCHH Traffic Volume
KPI Name
TCHH Traffic Volume
Measurement
Scope
CELL
Formula
K3034:TCHH Traffic Volume

= [AR3552A:Mean Number of Busy TCHs (TCHH) (900/850/810 band)]
+ [AR3552B:Mean Number of Busy TCHs (TCHH) (1800/1900 Band)]
Associated
Counters
None
Notes
None
2.5.4 TCH Availability

This counter provides the rate of available TCHs to configured TCHs.
Issue 01 (2014-04-29)

22
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Table 2-27 TCH Availability

KPI Name
TCH Availability
Measurement
Scope
CELL
Formula
RR307:TCH Availability
= {[AR3027A:Mean Number of Available Channels (TCHF)
(900/850/810 band)]
+ [AR3027B:Mean Number of Available Channels (TCHF) (1800/1900
Band)]
+ [AR3028A:Mean Number of Available Channels (TCHH) (900/850/810
band)]
+ [AR3028B:Mean Number of Available Channels (TCHH) (1800/1900
Band)]} x {100}/
{[AR3017A:Mean Number of Dynamically Configured Channels (TCHF)
(900/850/810 band)]
+ [AR3017B:Mean Number of Dynamically Configured Channels
(TCHF) (1800/1900 Band)]
+ [AR3018A:Mean Number of Dynamically Configured Channels
(TCHH) (900/850/810 band)]
(TCHH) (1800/1900 Band)]}
Associated
Counters
None
Notes
Unit: %
2.5.5 TCH Resource Usage

This counter provides the rate of the actual traffic volume to the theoretical traffic volume.
Table 2-28 TCH Resource Usage
Issue 01 (2014-04-29)
KPI Name
TCH Resource Usage
Measurement
Scope
CELL
Formula
Actual traffic volume divided by the theoretical capacity (if the theoretical
capacity exceeds 12000 Erl, take 12000 Erl for calculation)
Associated
Counters
None
Notes
None

23
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.5.6 TRX Usage

This counter provides the rate of available TRXs in a cell to TRXs configured in the cell.
Table 2-29 TRX Usage
KPI Name
TRX Usage
Measurement
Scope
CELL
Formula
RK3255:TRX Usage
= [S3656:Number of available TRXs in a cell] x {100}/
[S3655:Number of configured TRXs in a cell]
Associated
Counters
None
Notes
Unit: %
2.5.7 SDCCH Availability

This counter provides the rate of available SDCCHs to configured SDCCHs.
Table 2-30 SDCCH Availability
KPI Name
SDCCH Availability
Measurement
Scope
CELL
Formula
RR300:SDCCH Availability
= {[AR3020A:Mean Number of Available Channels (SDCCH)
(900/850/810 band)]
+ [AR3020B:Mean Number of Available Channels (SDCCH) (1800/1900
Band)]} x {100}/
{[AR3010A:Mean Number of Dynamically Configured Channels
(SDCCH) (900/850/810 band)]
(SDCCH) (1800/1900 Band)]}
Issue 01 (2014-04-29)
Associated
Counters
None
Notes
Unit: %

24
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.6 CS Retainability KPIs

This chapter describes the CS retainability KPIs that indicate the ratio of moving MSs to all MSs
as well as the moving frequency. In addition, these KPIs indicate the capability of providing
continuous services. A low success rate leads to low user satisfaction.
2.6.1 Call Drop Rate on TCH per Cell (Including Handover)

This counter provides the rate of TCH call drops to successful TCH seizures after the BSC
assigns the TCH to an MS (including handovers) in a cell.
Table 2-31 Call Drop Rate on TCH per Cell (Including Handover)
Issue 01 (2014-04-29)
KPI Name
Call Drop Rate on TCH per Cell (Including Handover)
Measurement
Scope
CELL

25
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
ZTR304:Call Drop Rate on TCH per Cell (Including Handover) =

[CM33:Call Drops on Traffic Channel] x {100}/
([K3023:Successful TCH Seizures (Signaling Channel)]
Channel)])
When the number of inter-RAT handovers reaches the upper limit, the
value of this counter will be greater than actual value if the following
formula is used:
Call drop rate on TCH per cell (Including Handover) = X * 100/Y
Where,
X = [Call Drops on Traffic Channel];
Y = ([Successful TCH Seizures (Signaling Channel)] + [Successful TCH
Seizures (Traffic Channel)] + [Successful TCH Seizures in TCH
handovers (Traffic Channel)]);
Therefore, it is recommended that the following formula be used when
inter-RAT handovers are detected:
Call drop rate on TCH per cell (Including Handover) = (X + Number of
times the outgoing inter-RAT inter-cell handover timer expires) * {100}/
(Y + Number of successful incoming inter-RAT inter-cell handovers)
Notes:
Number of times the outgoing inter-RAT inter-cell handover timer expires
= [H352C: Failed Outgoing Inter-RAT Inter-Cell Handovers (T8
Expired)];
Number of successful incoming inter-RAT inter-cell handovers =
{[H3609: Incoming Inter-RAT Inter-Cell Handover Requests (TCH)] ([H3627: Failed Incoming Inter-RAT Inter-Cell Handovers (TCHF)] +
[H3628: Failed Incoming Inter-RAT Inter-Cell Handovers (TCHH)])};
Associated
Counters
ZTR304A:Call Drop Rate on TCH per Cell (Excluding Handover)
Notes
1. Unit: %
2.6.2 Call Drop Rate on TCH per Cell (Excluding Handover)

This counter provides the rate of TCH call drops to successful TCH seizures after the BSC
assigns the TCH to an MS (excluding handovers) in a BSC.
Table 2-32 Call Drop Rate on TCH per Cell (Excluding Handover)
KPI Name
Issue 01 (2014-04-29)
Call Drop Rate on TCH per Cell (Excluding Handover)

26
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Measurement
Scope
Issue 01 (2014-04-29)
CELL

27
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula

= [CM33:Call Drops on Traffic Channel] x {100}/
{[K3013A:K3013A:Successful TCH Seizures (Traffic Channel)]
+[CH3209A:Number of Incoming Internal Inter-Cell Handover Requests
(TCH)]
-[CH3229A:Number of Failed Incoming Internal Inter-Cell Handovers
(TCH)]
+[CH3409A:Number of Incoming External Inter-Cell Handover Requests
(TCH)]
-[CH3429A:Number of Failed Incoming External Inter-Cell Handovers
(TCH)]
- ([CH3109A:Number of Outgoing Internal Inter-Cell Handover Requests
(TCH)]
-[CH3129A:Number of Failed Outgoing Internal Inter-Cell Handovers
(TCH)]
+[CH3309A:Number of Outgoing External Inter-Cell Handover Requests
(TCH)]
-[CH3329A:Number of Failed Outgoing External Inter-Cell Handovers
(TCH)])}
When the number of successful outgoing inter-RAT handovers reaches the
upper limit, the value of this counter will be negative or even greater than
100% if the following formula is used:
Call drop rate on TCH per cell (excluding handover) = X * {100}/Y
Where,
X = [Call Drops on Traffic Channel];
Y = {([Successful TCH Seizures (Traffic Channel)]+[Number of
Incoming Internal Inter-Cell Handover Requests (TCH)]-[Number of
Unsuccessful Incoming Internal Inter-Cell Handovers(TCH)]+[Number
of Incoming External Inter-Cell Handover Requests(TCH)]-[Number of
Unsuccessful Incoming External Inter-Cell Handovers(TCH)]-([Number
of Outgoing Internal Inter-Cell Handover Requests(TCH)]-[Number of
Unsuccessful Outgoing Internal Inter-Cell Handovers(TCH)]+[Outgoing
External Inter-Cell Handover Requests(TCH)]-[Failed Outgoing External
Inter-Cell Handovers(TCH)]))};
Therefore, it is recommended that the following formula be used when
inter-RAT handovers are detected:
Call drop rate on TCH per cell (excluding handover) = (X + [H352C: Failed
Outgoing Inter-RAT Inter-Cell Handovers (T8 Expired)]) * {100}/(Y +
{[H3609: Incoming Inter-RAT Inter-Cell Handover Requests (TCH)] ([H3627: Failed Incoming Inter-RAT Inter-Cell Handovers (TCHF)] +
[H3628: Failed Incoming Inter-RAT Inter-Cell Handovers (TCHH)])} {([H3507: Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF)] +
[H3508: Outgoing Inter-RAT Inter-Cell Handover Requests (TCHH)]) ([H3527: Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHF)] +
[H3528: Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHH)])})
Issue 01 (2014-04-29)

28
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Associated
Counters
ZTR304:Call Drop Rate on TCH per Cell (Including Handover)
Notes
1. Unit: %
2.6.3 Traffic Call Drop Rate per Cell

This counter provides the rate of traffic volume to call drops. It indicates the average interval at
which a call drop occurs in a cell.
Table 2-33 Traffic Call Drop Rate per Cell
KPI Name
Traffic Call Drop Rate per Cell
Measurement
Scope
CELL
Formula
ZTR308:Traffic Call Drop Rate per Cell = [K3014:Traffic Volume on

TCHs] x {60} x {100}/
[CM33:Call Drops on Traffic Channel]
Associated
Counters
Notes
1. Unit: %
2.6.4 Radio Drop Rate of TCH

This counter provides the rate of call drops due to faults in the Um interface to total successful
TCH seizures.
Table 2-34 Radio Drop Rate of TCH
Issue 01 (2014-04-29)
KPI Name
Radio Drop Rate of TCH
Measurement
Scope
CELL

29
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
RM333:Radio Drop Rate of TCH = {[CM330:Call Drops on Radio

Interface in Stable State (Traffic Channel)]
+ [CM3606:Call Drops on Radio Interface in Stable State (Signaling
Channel)(TCH)]} x {100} /
{[K3023:Successful TCH Seizures (Signaling Channel)]
Channel)]}
Associated
Counters
ZTR304:Call Drop Rate on TCH per cell (Including Handover)
Notes
Unit: %
2.6.5 Handover Drop Rate of TCH

This counter provides the rate of call drops due to handover failure and failure to return to the
original TCH during the handover to the total successful TCH seizures.
Table 2-35 Handover Drop Rate of TCH
KPI Name
Handover Drop Rate of TCH
Measurement
Scope
CELL
Formula
RH333:Handover Drop Rate of TCH = {[RH3331:Call Drops on Signal

Channel (TCH)]
+ [K3012B:Call Drops in TCH Handovers (Traffic Channel)]} x {100}/
{[K3023:Successful TCH Seizures (Signaling Channel)]
Channel)]}
Associated
Counters
None
Notes
Unit: %
2.6.6 Call Complete Establishment Success Rate

This counter provides the success rate of call completions.
Table 2-36 Call Complete Establishment Success Rate
KPI Name
Issue 01 (2014-04-29)
Call Complete Establishment Success Rate

30
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Measurement
Scope
CELL
Formula
RA333B:Call Complete Establishment Success Rate = [RA333A:BSS

Call Establishment Success Rate] x {1 - [ZTR304A:Call Drop Rate on
TCH per Cell (Excluding Handover)] x {100}
Associated
Counters
None
Notes
1. Unit: %
2.7 PS Accessibility KPIs

This chapter describes the PS accessibility KPIs that indicate whether MSs can easily access
cells. Poor PS accessibility KPIs decrease user satisfaction.
2.7.1 Uplink Assignment Success Rate

This counter provides the uplink assignment success rate during uplink assignment procedure.
Table 2-37 Uplink Assignment Success Rate
KPI Name
Uplink Assignment Success Rate
Measurement
Scope
CELL
Formula
A9513:Uplink Assignment Success Rate

= [A9502:Number of Successful Uplink Assignments] x {100}/
[A9501:Number of Uplink Assignments]
Associated
Counters
None
Notes
1. Unit: %
2.7.2 Downlink Assignment Success Rate

This counter provides the downlink assignment success rate during downlink assignment
procedure.
Issue 01 (2014-04-29)

31
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Table 2-38 Downlink Assignment Success Rate

KPI Name
Downlink Assignment Success Rate
Measurement
Scope
CELL
Formula
A9514:Downlink Assignment Success Rate

= [A9508:Number of Successful Downlink Assignments] x {100}/
[A9507:Number of Downlink Assignments]
Associated
Counters
None
Notes
1. Unit: %
2.7.3 Uplink TBF Establishment Success Rate

This counter provides the uplink TBF establishment success rate during uplink TBF
establishment procedure. The value of this counter is impacted by the bad radio environment
and insufficient resources.
Table 2-39 Uplink TBF Establishment Success Rate
KPI Name
Uplink TBF Establishment Success Rate
Measurement
Scope
CELL
Formula
Uplink TBF Establishment Success Rate

={[A9002:Number of Successful Uplink GPRS TBF Establishments]
+[A9202:Number of Successful Uplink EGPRS TBF Establishments]} x
{100}/
{[A9001:Number of Uplink GPRS TBF Establishment Attempts]
+[A9201:Number of Uplink EGPRS TBF Establishment Attempts]}
Associated
Counters
None
Notes
1. Unit: %
2.7.4 Downlink TBF Establishment Success Rate

This counter provides the success rate of downlink TBF establishments during downlink TBF
establishment procedure. The value of this counter is impacted by the bad radio environment
and insufficient resources.
Issue 01 (2014-04-29)

32
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Table 2-40 Downlink TBF Establishment Success Rate

KPI Name
Downlink TBF Establishment Success Rate
Measurement
Scope
CELL
Formula
Downlink TBF Establishment Success Rate

={[A9102:Number of Successful Downlink GPRS TBF Establishments]
+[A9302:Number of Successful Downlink EGPRS TBF Establishments]}
x {100}/
{[A9101:Number of Downlink GPRS TBF Establishment Attempts]
+[A9301:Number of Downlink EGPRS TBF Establishment Attempts]}
Associated
Counters
None
Notes
1. Unit: %
2.7.5 Uplink EGPRS TBF Establishment Success Rate

This counter provides the success rate of uplink EGPRS TBF establishments during uplink
EGPRS TBF establishment procedure. The value of this counter is impacted by the bad radio
environment and insufficient resources.
Table 2-41 Uplink EGPRS TBF Establishment Success Rate
KPI Name
Uplink EGPRS TBF Establishment Success Rate
Measurement
Scope
CELL
Formula
Uplink EGPRS TBF Establishment Success Rate

= [A9202:Number of Successful Uplink EGPRS TBF Establishments] x
{100}/
[A9201:Number of Uplink EGPRS TBF Establishment Attempts]
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

33
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.7.6 Downlink EGPRS TBF Establishment Success Rate

This counter provides the success rate of downlink EGPRS TBF establishments. The value of
this counter is impacted by the bad radio environment and insufficient resources.
Table 2-42 Downlink EGPRS TBF Establishment Success Rate
KPI Name
Downlink EGPRS TBF Establishment Success Rate
Measurement
Scope
CELL
Formula
Downlink EGPRS TBF Establishment Success Rate

= [A9302:Number of Successful Downlink EGPRS TBF Establishments]
x {100}/
[A9301:Number of Downlink EGPRS TBF Establishment Attempts]
Associated
Counters
None
Notes
1. Unit: %
2.7.7 Uplink TBF Congestion Rate

This counter indicates the rate of failed uplink TBF establishments due to no resource during
the uplink TBF establishment procedure.
Table 2-43 Uplink TBF Congestion Rate
KPI Name
Uplink TBF Congestion Rate
Measurement
Scope
CELL
Formula
Uplink TBF Congestion Rate

={[A9003:Number of Failed Uplink GPRS TBF Establishments due to No
Channel]
+[A9203:Number of Failed Uplink EGPRS TBF Establishments due to
No Channel]} x {100}/
{[A9001:Number of Uplink GPRS TBF Establishment Attempts]
+[A9201:Number of Uplink EGPRS TBF Establishment Attempts]}
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

34
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.7.8 Downlink TBF Congestion Rate

This counter indicates the rate of failed downlink TBF establishments due to no resource during
the downlink TBF establishment procedure.
Table 2-44 Downlink TBF Congestion Rate
KPI Name
Downlink TBF Congestion Rate
Measurement
Scope
CELL
Formula
Downlink TBF Congestion Rate

={[A9103:Number of Failed Downlink GPRS TBF Establishments due to
No Channel]
+[A9303:Number of Failed Downlink EGPRS TBF Establishments due
to No Channel]} x {100}/
{[A9101:Number of Downlink GPRS TBF Establishment Attempts]
+[A9301:Number of Downlink EGPRS TBF Establishment Attempts]}
Associated
Counters
None
Notes
1. Unit: %
2.7.9 Uplink EGPRS TBF Congestion Rate

This counter indicates the rate of failed uplink EGPRS TBF establishments due to no resource
during the uplink EGPRS TBF establishment procedure.
Table 2-45 Uplink EGPRS TBF Congestion Rate
KPI Name
Uplink EGPRS TBF Congestion Rate
Measurement
Scope
CELL
Formula
Uplink EGPRS TBF Congestion Rate

=[A9203:Number of Failed Uplink EGPRS TBF Establishments due to
No Channel] x {100}/
[A9201:Number of Uplink EGPRS TBF Establishment Attempts]
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

35
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.7.10 Downlink EGPRS TBF Congestion Rate

This counter indicates the rate of failed downlink EGPRS TBF establishments due to no resource
during the downlink EGPRS TBF establishment procedure.
Table 2-46 Downlink EGPRS TBF Congestion Rate
KPI Name
Downlink EGPRS TBF Congestion Rate
Measurement
Scope
CELL
Formula
Downlink EGPRS TBF Congestion Rate

=[A9303:Number of Failed Downlink EGPRS TBF Establishments due
to No Channel] x {100}/
[A9301:Number of Downlink EGPRS TBF Establishment Attempts]
Associated
Counters
None
Notes
1. Unit: %
2.8 PS Data Throughput KPIs

This chapter describes the PS data throughput rate KPIs. They involve the performance factors
associated with the MSs, the radio access network, and the core network. Now, the main
performance problem is concerned with the radio access network. Therefore, these KPIs indicate
the end-to-end service data link bearing capability of the GPRS network, which is directly related
to user satisfaction.
2.8.1 Upload Data Throughput (kbit/s)

This counter provides the delay performance of the upload service.
Table 2-47 Upload Data Throughput (kbit/s)
KPI Name
Upload Data Throughput (kbit/s)
Measurement
Scope
None
Formula
Amount of data transmitted every second during upload.

Note:
1. The rate at the IP layer or application layer is appraised.
2. Generally, the file uploaded over FTP is tested on the MS side.
Issue 01 (2014-04-29)

36
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Associated
Counters
None
Notes
2.8.2 Download Data Throughput (kbit/s)

This counter provides the delay performance of the download service.
Table 2-48 Download Data Throughput (kbit/s)
KPI Name
Download Data Throughput (kbit/s)
Measurement
Scope
None
Formula
Amount of data transmitted every second during download.

Note:
1. The rate at the IP layer or application layer is appraised.
2. Generally, the file downloaded over FTP is tested on the MS side.
Associated
Counters
None
Notes
2.9 PS Delay KPIs

This chapter describes the PS delay KPIs that indicate the service response speed of the network.
Long delay decreases user satisfaction.
2.9.1 Ping Delay (ms)

This counter provides the delay performance of the ping service.
Table 2-49 Ping Delay (ms)
Issue 01 (2014-04-29)
KPI Name
Ping Delay (ms)
Measurement
Scope
None
Formula
The difference between the time when the MS sends an ICMP packet of
the Return Request type and the time when the receiving end responds with
an ICMP packet of the Return Acknowledgment type. Two types of Ping
delay are available: Initial Ping Delay and Consecutive Ping Delay.
37
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Associated
Counters
None
Notes
Test methods:
1. Use a dedicated tool (for example, TEMS) to edit the commands for
test.
2. Use the Ping command provided with the operating system to perform
the test.
2.9.2 Mean Delay of PDP Activation (ms)

This counter provides the delay performance during PDP activation.
Table 2-50 Mean Delay of PDP Activation (ms)
KPI Name
Mean Delay of PDP Activation (ms)
Measurement
Scope
None
Formula
The interval between the time when the MS sends the Activate PDP
Context Request message and the time when the MS receives the Activate
PDP Context Accept message.
Associated
Counters
None
Notes
Test methods:
Use a dedicated tool (for example, TEMS) to perform the test. A common
commercial MS cannot be used to perform the test. Generally, the
dedicated tool supports the automatic test, and generates a test report to
obtain the preceding counter.
2.9.3 Mean Delay of Attach (ms)

This counter provides the delay performance during attach.
Table 2-51 Mean Delay of Attach (ms)
Issue 01 (2014-04-29)
KPI Name
Mean Delay of Attach (ms)
Measurement
Scope
None
Formula
The interval between the time when the MS sends the Attach Request
message and the time when the MS sends the Attach Complete message.

38
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Associated
Counters
None
Notes
Test methods:
Use a dedicated tool (for example, TEMS) to perform the test. A common
commercial MS cannot be used to perform the test. Generally, the
dedicated tool supports the automatic test, and generates a test report to
obtain the preceding counter.
2.9.4 Service Interruption Delay for Cell Reselection (ms)

This counter provides the delay performance of MS service disruption during cell reselection.
Table 2-52 Service Interruption Delay for Cell Reselection (ms)
KPI Name
Service Interruption Delay for Cell Reselection (ms)
Measurement
Scope
None
Formula
This counter is appraised in the mode of download test on the application

layer. This counter is defined as follows: the interval between the time
when the original cell receives the last TCP packet and the time when the
target cell receives the first TCP packet.
Associated
Counters
None
Notes
1. The upload test is different from the download test. This counter is
appraised in the mode of download test:
2. The Service Interruption Delay for Cell Reselection (ms) is appraised
through the Um interface on some networks. This counter is defined as
follows: the interval between the time when the Cell Reselection message
is displayed with the MA test tool, such as TEMS, and the time when the
MS initiates the Channel Request message in a new cell. The signaling
shows the interval which is measured manually.
3. The Service Interruption Delay for Cell Reselection (ms) is impacted
by the following factors: Whether the NACC and NC2 modes are enabled;
whether the 2G/3G inter-RAT cell reselection is performed; whether the
cross-RA reselection is performed.
2.10 PS Resource Usage KPIs

This chapter describes the PS resource usage rate KPIs that indicate the network resource usage
and the busy states of services. Therefore, these KPIs can be used to guide network expansion.
Issue 01 (2014-04-29)

39
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.10.1 Uplink PDTCH/PACCH Usage

This counter provides the usage of uplink PDTCHs or PACCHs.
Table 2-53 Uplink PDTCH/PACCH Usage
KPI Name
Uplink PDTCH/PACCH Usage
Measurement
Scope
CELL
Formula
Uplink PDTCH/PACCH Usage

=[R9204:Number of RLC Data Blocks Received on Uplink PDTCH/
PACCH] x {100}/
[R9206:Total Number of Uplink PDTCH/PACCH Blocks]
Associated
Counters
None
Notes
Unit: %
2.10.2 Downlink PDTCH/PACCH Usage

This counter provides the usage of downlink PDTCHs or PACCHs.
Table 2-54 Downlink PDTCH/PACCH Usage
KPI Name
Downlink PDTCH/PACCH Usage
Measurement
Scope
CELL
Formula
Downlink PDTCH/PACCH Usage

=[R9205:Number of RLC Data Blocks Sent on Downlink PDTCH/
PACCH] x {100}/
[R9207:Total Number of Downlink PDTCH/PACCH Blocks]
Associated
Counters
None
Notes
Unit: %
2.10.3 PDCH Occupation Rate

This counter provides the PDCH occupation rate.
Issue 01 (2014-04-29)

40
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Table 2-55 PDCH Occupation Rate

KPI Name
PDCH Occupation Rate
Measurement
Scope
CELL
Formula
PDCH Occupation Rate

=[AR9311:Average Number of Occupied PDCHs] x {100}/
[AR9303:Average Number of Available PDCHs]
Associated
Counters
None
Notes
Unit: %
2.10.4 Proportion of Dynamic PDCHs Reclaimed by BSC

This counter provides the proportion of PDCHs carrying PS services that are preempted by CS
services.
Table 2-56 Proportion of Dynamic PDCHs Reclaimed by BSC
KPI Name
Proportion of Dynamic PDCHs Reclaimed by BSC
Measurement
Scope
CELL
Formula
Proportion of Dynamic PDCHs Reclaimed by BSC

=[R9344:Number of Reclaimed Busy Dynamic PDCHs] x {100}/
[R9343:Number of Reclaimed Dynamic PDCHs]
Associated
Counters
None
Notes
Unit: %
2.11 PS Retainability KPIs

This chapter describes the PS retainability KPIs that mainly involve the uplink and downlink
TBF call drop rates. These KPIs indicate the capability of providing continuous services by the
network and are directly related to user satisfaction. Therefore, a high call drop rate decreases
user satisfaction.
2.11.1 Uplink TBF Drop Rate

This counter provides the rate of uplink TBF abnormal releases due to N3101 or N3103 overflow
after the uplink TBF is set up successfully.
Issue 01 (2014-04-29)

41
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Table 2-57 Uplink TBF Drop Rate

KPI Name
Uplink TBF Drop Rate
Measurement
Scope
CELL
Formula
Uplink TBF Drop Rate

={[A9006:Number of Uplink GPRS TBF Abnormal Releases due to
N3101 Overflow (MS No Response)]
+[A9007:Number of Uplink GPRS TBF Abnormal Releases due to N3103
Overflow (MS No Response)]
+[A9206:Number of Uplink EGPRS TBF Abnormal Releases due to
N3103 Overflow (MS No Response)]} x {100}/
{[A9002:Number of Successful Uplink GPRS TBF Establishments]
+[A9202:Number of Successful Uplink EGPRS TBF Establishments]}
Associated
Counters
None
Notes
1. Unit: %
2.11.2 Downlink TBF Drop Rate

This counter provides the rate of downlink PDU buffer emptying due to TBF abnormal releases
and reestablishment failure after the downlink TBF is set up successfully.
Table 2-58 Downlink TBF Drop Rate
KPI Name
Downlink TBF Drop Rate
Measurement
Scope
CELL
Formula
Downlink TBF Drop Rate

={[A9118:Number of Downlink GPRS Intermit Transfers]
+[A9318:Number of Downlink EGPRS Intermit Transfers]} x {100}/
{[A9102:Number of Successful Downlink GPRS TBF Establishments]
+[A9302:Number of Successful Downlink EGPRS TBF Establishments]}
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

42
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.11.3 Uplink EGPRS TBF Drop Rate

This counter provides the rate of uplink EGPRS TBF abnormal releases due to N3101 or N3103
overflow after the uplink EGPRS TBF is set up successfully.
Table 2-59 Uplink EGPRS TBF Drop Rate
KPI Name
Uplink EGPRS TBF Drop Rate
Measurement
Scope
CELL
Formula
Uplink EGPRS TBF Drop Rate

={[A9206:Number of Uplink EGPRS TBF Abnormal Releases due to
N3103 Overflow (MS No Response)]} x {100}/
[A9202:Number of Successful Uplink EGPRS TBF Establishments]
Associated
Counters
None
Notes
1. Unit: %
2.11.4 Downlink EGPRS TBF Drop Rate

This counter provides the rate of downlink PDU buffer emptying due to EGPRS TBF abnormal
releases and reestablishment failure after the downlink EGPRS TBF is set up successfully.
Table 2-60 Downlink EGPRS TBF Drop Rate
KPI Name
Downlink EGPRS TBF Drop Rate
Measurement
Scope
CELL
Formula
Downlink EGPRS TBF Drop Rate

=[A9318:Number of Downlink EGPRS Intermit Transfers] x {100}/
[A9302:Number of Successful Downlink EGPRS TBF Establishments]
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

43
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.12 PS Transmission Performance KPIs

This chapter describes the PS transmission performance KPIs that indicate the quality of radio
transmission links in a cell. If the RLC data block retransmission rate in a cell is high, the quality
of the radio transmission links in the cell is poor. Therefore, take corresponding measures, such
as RF optimization.
2.12.1 Retransmission Rate of Uplink GPRS RLC Data Blocks

This counter provides the transmission quality of uplink GPRS RLC data blocks.
Table 2-61 Retransmission Rate of Uplink GPRS RLC Data Blocks
KPI Name
Retransmission Rate of Uplink GPRS RLC Data Blocks
Measurement
Scope
CELL
Formula
Retransmission Rate of Uplink GPRS RLC Data Blocks

=([L9001:Total Number of Uplink GPRS RLC Data Blocks]
- [L9006:Number of Valid Uplink RLC Data Blocks Using CS1]
- [L9009:Number of Valid Uplink RLC Data Blocks Using CS4]) x {100}/
[L9001:Total Number of Uplink GPRS RLC Data Blocks]
Associated
Counters
None
Notes
1. Unit: %
2.12.2 Retransmission Rate of Downlink GPRS RLC Data Blocks

This counter provides the transmission quality of downlink GPRS RLC data blocks.
Table 2-62 Retransmission Rate of Downlink GPRS RLC Data Blocks
Issue 01 (2014-04-29)
KPI Name
Retransmission Rate of Downlink GPRS RLC Data Blocks
Measurement
Scope
CELL

44
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Retransmission Rate of Downlink GPRS RLC Data Blocks

=([L9101:Total Number of Downlink GPRS RLC Data Blocks]
- [L9106:Total Number of Valid Downlink RLC Data Blocks Using CS1]
- [L9109:Total Number of Valid Downlink RLC Data Blocks Using CS4])
x {100}/
[L9101:Total Number of Downlink GPRS RLC Data Blocks]
Associated
Counters
None
Notes
1. Unit: %
2.12.3 Retransmission Rate of Uplink EGPRS RLC Data Blocks

This counter provides the transmission quality of uplink EGPRS RLC data blocks.
Table 2-63 Retransmission Rate of Uplink EGPRS RLC Data Blocks
KPI Name
Retransmission Rate of Uplink EGPRS RLC Data Blocks
Measurement
Scope
CELL
Formula
Retransmission Rate of Uplink EGPRS RLC Data Blocks

= ([L9201:Total Number of Uplink EGPRS RLC Data Blocks]
- [L9211:Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks]
- [L9219:Total Number of Valid Uplink EGPRS MCS9 RLC Data
Blocks]) x {100}/
[L9201:Total Number of Uplink EGPRS RLC Data Blocks]
Associated
Counters
Issue 01 (2014-04-29)
None

45
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Notes
1. Unit: %
2.12.4 Retransmission Rate of Downlink EGPRS RLC Data Blocks

This counter provides the transmission quality of downlink EGPRS RLC data blocks.
Table 2-64 Retransmission Rate of Downlink EGPRS RLC Data Blocks
KPI Name
Retransmission Rate of Downlink EGPRS RLC Data Blocks
Measurement
Scope
CELL
Formula
Retransmission Rate of Downlink EGPRS RLC Data Blocks

= ([L9301:Total Number of Downlink EGPRS RLC Data Blocks]
- [L9311:Total Number of Valid Downlink EGPRS MCS1 RLC Data
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]) x {100}/
[L9301:Total Number of Downlink EGPRS RLC Data Blocks]
Associated
Counters
None
Notes
1. Unit: %
Issue 01 (2014-04-29)

46
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.12.5 Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4

This counter provides the rate of coding scheme with CS3/CS4 during uplink GPRS RLC data
transmission.
Table 2-65 Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4
KPI Name
Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4
Measurement
Scope
CELL
Formula
Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4

={[L9008:Number of Valid Uplink RLC Data Blocks Using CS3]
+[L9009:Number of Valid Uplink RLC Data Blocks Using CS4]} x {100}/
{[L9006:Number of Valid Uplink RLC Data Blocks Using CS1]
+[L9007:Number of Valid Uplink RLC Data Blocks Using CS2]
+[L9008:Number of Valid Uplink RLC Data Blocks Using CS3]
+[L9009:Number of Valid Uplink RLC Data Blocks Using CS4]}
Associated
Counters
None
Notes
Unit: %
2.12.6 Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4

This counter provides the rate of coding scheme with CS3/CS4 during downlink GPRS RLC
data transmission.
Table 2-66 Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4
KPI Name
Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4
Measurement
Scope
CELL
Formula
Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4

={[L9108:Total Number of Valid Downlink RLC Data Blocks Using CS3]
+[L9109:Total Number of Valid Downlink RLC Data Blocks Using CS4]}
x {100}/
{[L9106:Total Number of Valid Downlink RLC Data Blocks Using CS1]
+[L9107:Total Number of Valid Downlink RLC Data Blocks Using CS2]
+[L9108:Total Number of Valid Downlink RLC Data Blocks Using CS3]
+[L9109:Total Number of Valid Downlink RLC Data Blocks Using CS4]}
Issue 01 (2014-04-29)

47
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Associated
Counters
None
Notes
Unit: %
2.12.7 Rate of Uplink EGPRS RLC Coding Scheme with MCS7/

MCS8/MCS9
This counter provides the rate of coding scheme with MCS7/MCS8/MCS9 during uplink EGPRS
RLC data transmission.
Table 2-67 Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
KPI Name
Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
Measurement
Scope
CELL
Formula
Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9

={[L9217:Total Number of Valid Uplink EGPRS MCS7 RLC Data
Blocks]
+[L9218:Total Number of Valid Uplink EGPRS MCS8 RLC Data Blocks]
+[L9219:Total Number of Valid Uplink EGPRS MCS9 RLC Data
Blocks]} x {100}/
{[L9211:Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks]
+[L9219:Total Number of Valid Uplink EGPRS MCS9 RLC Data
Blocks]}
Issue 01 (2014-04-29)
Associated
Counters
None
Notes
Unit: %

48
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.12.8 Rate of Downlink EGPRS RLC Coding Scheme with MCS7/

MCS8/MCS9
This counter provides the rate of coding scheme with MCS7/MCS8/MCS9 during downlink
EGPRS RLC data transmission.
Table 2-68 Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
KPI Name
Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
Measurement
Scope
CELL
Formula
Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9

={[L9317:Total Number of Valid Downlink EGPRS MCS7 RLC Data
Blocks]
+[L9318:Total Number of Valid Downlink EGPRS MCS8 RLC Data
Blocks]
Blocks]} x {100}/
{[L9311:Total Number of Valid Downlink EGPRS MCS1 RLC Data
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]
Blocks]}
Issue 01 (2014-04-29)
Associated
Counters
None
Notes
Unit: %

49
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.12.9 Average Throughput of Uplink GPRS RLC per PDCH (kbit/

s)
This counter provides the average bandwidth per PDCH during uplink GPRS RLC data
transmission.
Table 2-69 Average Throughput of Uplink GPRS RLC per PDCH (kbit/s)
KPI Name
Average Throughput of Uplink GPRS RLC per PDCH (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Uplink GPRS RLC per PDCH (kbit/s)

=([L9006:Number of Valid Uplink RLC Data Blocks Using CS1] x{23}
+[L9007:Number of Valid Uplink RLC Data Blocks Using CS2] x{34}
+[L9008:Number of Valid Uplink RLC Data Blocks Using CS3] x{40}
+[L9009:Number of Valid Uplink RLC Data Blocks Using CS4] x{54})
x {8}/
({1024} x [L9001:Total Number of Uplink GPRS RLC Data Blocks] x
{20}/{1000})
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.10 Average Throughput of Downlink GPRS RLC per PDCH

(kbit/s)
This counter provides the average bandwidth per PDCH during downlink GPRS RLC data
transmission.
Table 2-70 Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
Issue 01 (2014-04-29)
KPI Name
Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
Measurement
Scope
CELL

50
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)

=([L9106:Total Number of Valid RLC Downlink Data Blocks Using CS1]
x{23}
+[L9107:Total Number of Valid RLC Downlink Data Blocks Using CS2]
x{34}
x{40}
+[L9109:Total Number of Valid RLC Downlink Data Block Using CS4]
x{54}) x {8}/
({1024}x[L9101:Total Number of Downlink GPRS RLC Data Blocks]x
{20}/{1000})
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.11 Average Throughput of Uplink EGPRS RLC per PDCH

(kbit/s)
This counter provides the average bandwidth per PDCH during uplink EGPRS RLC data
transmission.
Table 2-71 Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
Issue 01 (2014-04-29)
KPI Name
Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
Measurement
Scope
CELL

51
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)

=([L9211:Total Number of Valid Uplink EGPRS MCS1 RLC Data
Blocks]x{22}
x{28}
x{37}
x{44}
x{56}
x{74}
x{56}
x{68}
x{74}) x {8}/
({1024}x([L9202:Total Number of Uplink EGPRS MCS1 RLC Data
Blocks]
+[L9203:Total Number of Uplink EGPRS MCS2 RLC Data Blocks]
+[L9208:Total Number of Uplink EGPRS MCS7 RLC Data Blocks]/{2}
+[L9209:Total Number of Uplink EGPRS MCS8 RLC Data Blocks]/{2}
+[L9210:Total Number of Uplink EGPRS MCS9 RLC Data Blocks]/{2})
x{20}/{1000})
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.12 Average Throughput of Downlink EGPRS RLC per PDCH

(kbit/s)
This counter provides the average bandwidth per PDCH during downlink EGPRS RLC data
transmission.
Issue 01 (2014-04-29)

52
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Table 2-72 Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)
KPI Name
Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)

=([L9311:Total Number of Valid Downlink EGPRS MCS1 RLC Data
Blocks]x{22}
Blocks]x{28}
Blocks]x{37}
Blocks]x{44}
Blocks]x{56}
Blocks]x{74}
Blocks]x{56}
Blocks]x{68}
Blocks]x{74}) x {8}/
({1024}x([L9302:Total Number of Downlink EGPRS MCS1 RLC Data
Blocks]
+[L9303:Total Number of Downlink EGPRS MCS2 RLC Data Blocks]
+[L9307:Total Number of Downlink EGPRS MCS6 RLC data blocks]
+[L9308:Total Number of Downlink EGPRS MCS7 RLC Data Blocks]/
{2}
{2}
{2})x{20}/{1000})
Associated
Counters
None
Notes
1. Unit: kbit/s
Issue 01 (2014-04-29)

53
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
2.12.13 Average Throughput of Uplink GPRS RLC per Cell (kbit/s)

This counter provides the average throughput per cell during uplink GPRS RLC data
transmission.
Table 2-73 Average Throughput of Uplink GPRS RLC per Cell (kbit/s)
KPI Name
Average Throughput of Uplink GPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Uplink GPRS RLC per Cell (kbit/s)

=([L9006:Number of Valid Uplink RLC Data Blocks Using CS1]x{23}
+[L9007:Number of Valid Uplink RLC Data Blocks Using CS2]x{34}
+[L9008:Number of Valid Uplink RLC Data Blocks Using CS3]x{40}
+[L9009:Number of Valid Uplink RLC Data Blocks Using CS4]x{54}) x
{8}/
({1024}x[L9020:Total Duration of Uplink GPRS TBFs])
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.14 Average Throughput of Downlink GPRS RLC per Cell (kbit/

s)
This counter provides the average throughput per cell during downlink GPRS RLC data
transmission.
Table 2-74 Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
Issue 01 (2014-04-29)
KPI Name
Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL

54
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Average Throughput of Downlink GPRS RLC per Cell (kbit/s)

=([L9106:Total Number of Valid RLC Downlink Data Blocks Using CS1]
x{23}
x{34}
x{40}
+[L9109:Total Number of Valid RLC Downlink Data Block Using CS4]
x{54}) x {8}/
({1024}x[L9121:Total Duration of Downlink GPRS TBFs])
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.15 Average Throughput of Uplink EGPRS RLC per Cell (kbit/

s)
This counter provides the average throughput per cell during uplink EGPRS RLC data
transmission.
Table 2-75 Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
Issue 01 (2014-04-29)
KPI Name
Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL

55
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)

=([L9211:Total Number of Valid Uplink EGPRS MCS1 RLC Data
Blocks]x{22}
x{28}
x{37}
x{44}
x{56}
x{74}
x{56}
+[L9218:Number of Valid Uplink EGPRS MCS8 RLC Data Blocks]x
{68}
x{74}) x {8}/
({1024}x[L9235:Total Duration of Uplink EGPRS TBFs])
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.16 Average Throughput of Downlink EGPRS RLC per Cell

(kbit/s)
This counter provides the average throughput per cell during downlink EGPRS RLC data
transmission.
Table 2-76 Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
Issue 01 (2014-04-29)
KPI Name
Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL

56
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Formula
Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)

=([L9311:Total Number of Valid Downlink EGPRS MCS1 RLC Data
Blocks]x{22}
Blocks]x{28}
Blocks]x{37}
Blocks]x{44}
Blocks]x{56}
Blocks]x{74}
Blocks]x{56}
Blocks]x{68}
Blocks]x{74}) x {8}/
({1024}*[L9336:Total Duration of Downlink EGPRS TBFs])
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.17 Average Throughput of Uplink GPRS LLC per User (kbit/s)

This counter provides the average throughput per user during uplink GPRS LLC data
transmission.
Table 2-77 Average Throughput of Uplink GPRS LLC per User (kbit/s)
KPI Name
Average Throughput of Uplink GPRS LLC per User (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Uplink GPRS LLC per User (kbit/s)

=[L9422:Throughput of Uplink GPRS Users LLC PDU]/
([L9421:Total Bytes of Uplink GPRS Users LLC PDUs] x {8}/{1024})
Associated
Counters
Issue 01 (2014-04-29)
None

57
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Notes
1. Unit: kbit/s
2.12.18 Average Throughput of Downlink GPRS LLC per User

(kbit/s)
This counter provides the average throughput per user during downlink GPRS LLC data
transmission.
Table 2-78 Average Throughput of Downlink GPRS LLC per User (kbit/s)
KPI Name
Average Throughput of Downlink GPRS LLC per User (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Downlink GPRS LLC per User (kbit/s)

=[L9526:Throughput of Downlink GPRS Users LLC PDU]/
([L9525:Total Bytes of Downlink GPRS Users LLC PDU] x {8}/{1024})
Associated
Counters
None
Notes
1. Unit: kbit/s
2.12.19 Average Throughput of Uplink EGPRS LLC per User (kbit/

s)
This counter provides the average throughput per user during uplink EGPRS LLC data
transmission.
Table 2-79 Average Throughput of Uplink EGPRS LLC per User (kbit/s)
KPI Name
Average Throughput of Uplink EGPRS LLC per User (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Uplink EGPRS LLC per User (kbit/s)

=[L9424:Throughput of Uplink EGPRS Users LLC PDU]/
([L9423:Total Bytes of Uplink EGPRS Users LLC PDUs] x {8}/{1024})
Associated
Counters
Issue 01 (2014-04-29)
None

58
GBSS16.0&RAN16.0
KPI Reference
2 GSM Service KPI
Notes
1. Unit: kbit/s
2.12.20 Average Throughput of Downlink EGPRS LLC per User

(kbit/s)
This counter provides the average throughput per user during downlink EGPRS LLC data
transmission.
Table 2-80 Average Throughput of Downlink EGPRS LLC per User (kbit/s)
KPI Name
Average Throughput of Downlink EGPRS LLC per User (kbit/s)
Measurement
Scope
CELL
Formula
Average Throughput of Downlink EGPRS LLC per User (kbit/s)

=[L9528:Throughput of Downlink EGPRS Users LLC PDU]/
([L9527:Total Bytes of Downlink EGPRS Users LLC PDU] x {8}/
{1024})
Associated
Counters
None
Notes
1. Unit: kbit/s
Issue 01 (2014-04-29)

59
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
UMTS Service KPI
About This Chapter

The following KPIs are UMTS Service KPIs.
3.1 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.2 Availability
Availability KPIs mainly indicate the utilization for several kinds of network resources such as
Radio, bandwidth or CPU Load.
3.3 Coverage
Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an
RNC or a cluster.
3.4 Mobility
Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or
service mode changing in difference scenarios.
3.5 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.
3.6 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.
3.7 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.
Issue 01 (2014-04-29)

60
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1 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.1.1 IU Paging Success Ratio

Table 3-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 =
Object
RNC
Unit/Range
Note
None
(VS.RANAP.Paging.Succ.IdleUE/VS.RANAP.Paging.Att.IdleUE) x
100%
3.1.2 RRC Setup Success Ratio

Table 3-2 RRC Setup Success Ratio
Name
RRC Setup Success Ratio
Formula
Issue 01 (2014-04-29)

61
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.
Issue 01 (2014-04-29)

62
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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+
Issue 01 (2014-04-29)

63
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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 3.1.4 PS
Radio Access Success Ratio and 3.1.5 CS Radio Access Success Ratio
directly.
Issue 01 (2014-04-29)

64
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1.3 Radio Access Success Ratio

Table 3-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 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.
Issue 01 (2014-04-29)

65
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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
3.1.4 PS Radio Access Success Ratio

Table 3-4 PS Radio Access Success Ratio
Name
Issue 01 (2014-04-29)
PS Radio Access Success Ratio

66
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.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.TmBkgCall +
RRC.AttConnEstab.TmInterCall)] x
PS RAB Setup Success Ratio (RNC) x 100%
Object
CELL, RNC
Unit/Range
Note
None
3.1.5 CS Radio Access Success Ratio

Issue 01 (2014-04-29)

67
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-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.EmgCall)] x
CS RAB Setup Success Ratio (Cell) x 100%
l CS Radio Access Success Ratio (RNC)=
RRC.SuccConnEstab.EmgCall)/
RRC.AttConnEstab.EmgCall)] x
CS RAB Setup Success Ratio (RNC) x 100%
Object
CELL,RNC
Unit/Range
Note
None
3.1.6 AMR RAB Setup Success Ratio
Issue 01 (2014-04-29)

68
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-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) =
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.
(VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR) x 100%
3.1.7 VP RAB Setup Success Ratio

Table 3-7 VP RAB Setup Success Ratio
Name
VP RAB Setup Success Ratio
Formula
Issue 01 (2014-04-29)

69
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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) =
Object
CELL
Unit/Range
Note
(VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64) x 100%
3.1.8 CS RAB Setup Success Ratio

Table 3-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.
Issue 01 (2014-04-29)

70
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.
3.1.9 CS+PS Combined Service RAB Setup Success Rate

Table 3-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
combined service type is CS+PS, CS+2PS, or CS+3PS.
Issue 01 (2014-04-29)

71
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
CS+PS RAB Setup Success ratio=
Object
CELL
Unit/Range
Note
None
(VS.MultiRAB.SuccEstab.CSPS/VS.MultiRAB.AttEstab.CSPS) * 100%
3.1.10 PS+PS Combined Service RAB Setup Success Rate

Table 3-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=
Object
CELL
Unit/Range
Note
None
(VS.MultiRAB.SuccEstab.PSPS/VS.MultiRAB.AttEstab.PSPS)*100%
3.1.11 PS RAB Setup Success Ratio

Issue 01 (2014-04-29)

72
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-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%
Issue 01 (2014-04-29)
Object
CELL, RNC
Unit/Range
Note
None

73
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1.12 HSDPA RAB Setup Success Ratio

Table 3-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
RESPONSE message to the CN.
Associated
Counters
HSDPA RAB Setup Success Ratio (Cell) =
Object
CELL
Unit/Range
Note
(VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%
3.1.13 HSUPA RAB Setup Success Ratio

Table 3-13 HSUPA RAB Setup Success Ratio
Name
HSUPA RAB Setup Success Ratio
Formula
Issue 01 (2014-04-29)

74
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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
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) =
Object
CELL
Unit/Range
Note
(VS.HSUPA.RAB.SuccEstab/VS.HSUPA.RAB.AttEstab) x 100%
3.1.14 PS E-FACH RAB Setup Success Ratio

Table 3-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.
Issue 01 (2014-04-29)
Associated
Counters
PS E-FACH RAB Setup Success Ratio (Cell) =
Object
CELL
Unit/Range
Note
(VS.RAB.SuccEstPS.EFACH/VS.RAB.AttEstPS.EFACH) x 100%

75
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1.15 CS over HSPA RAB Setup Success Ratio

Table 3-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
3.1.16 HSDPA 64QAM RAB Setup Success Ratio

Table 3-16 HSDPA 64QAM RAB Setup Success Ratio
Name
HSDPA 64QAM RAB Setup Success Ratio
Formula
Issue 01 (2014-04-29)

76
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.
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
3.1.17 HSDPA MIMO RAB Setup Success Ratio

Table 3-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.
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.
Issue 01 (2014-04-29)
Associated
Counters
HSDPA MIMO RAB Setup Success Ratio=
Object
CELL
Unit/Range
(VS.HSDPA.RAB.MIMO.SuccEstab/VS.HSDPA.RAB.MIMO.AttEstab) x 100%

77
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
3.1.18 HSDPA DC RAB Setup Success Ratio

Table 3-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
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=
Object
CELL
Unit/Range
Note
(VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x
100%
3.1.19 HSDPA MIMO64QAM RAB Setup Success Ratio

Table 3-19 HSDPA MIMO64QAM RAB Setup Success Ratio
Name
HSDPA MIMO64QAM RAB Setup Success Ratio
Formula
Issue 01 (2014-04-29)

78
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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=
Object
CELL
Unit/Range
Note
(VS.HSDPA.RAB.MIMO64QAM.SuccEstab/
VS.HSDPA.RAB.MIMO64QAM.AttEstab) x 100%
3.1.20 PTM Channel Setup Success Ratio

Table 3-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.
Issue 01 (2014-04-29)
Associated
Counters
PTM Channel Setup Success Ratio=
Object
CELL
Unit/Range
Note
(VS.MBMS.RB.PTM.SuccEstab/ VS.MBMS.RB.PTM.AttEstab)*100%

79
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1.21 PTP Channel Setup Success Ratio

Table 3-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=
Object
CELL
Unit/Range
Note
(VS.MBMS.RB.PTP.SuccEstab/ VS.MBMS.RB.PTP.AttEstab)*100%
3.1.22 RRC Congestion Ratio

Table 3-22 RRC Congestion Ratio
Name
RRC Congestion Ratio
Formula
Description
This KPI is used to check the RRC Congestion Ratio in a cluster.

After receiving an RRC CONNECTION REQUEST message from the UE,
the RNC initiates admission procedures for resources of code, power, CE,
and Iub bandwidth. If the resource admission fails, the RRC Setup 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.
Issue 01 (2014-04-29)

80
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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
3.1.23 CS RAB Congestion Ratio

Table 3-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.
Issue 01 (2014-04-29)

81
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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
3.1.24 PS RAB Congestion Ratio

Table 3-24 PS RAB Congestion Ratio
Name
PS RAB Congestion Ratio
Formula
Description
This KPI is used to check the PS RAB Congestion Ratio in a cluster.

The PS RAB Setup Fails due to Congestion procedure is complete when 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.
Issue 01 (2014-04-29)

82
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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
3.1.25 PS R99 RAB Setup Success Rate

Table 3-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.
Issue 01 (2014-04-29)
Associated
Counters
PS RAB Setup Success Ratio (Cell)=
Object
CELL
Unit/Range
(VS.RAB.SuccEstab.PSR99/ VS.RAB.AttEstab.PSR99) * 100%

83
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
3.1.26 WB AMR RAB Setup Success Rate

Table 3-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)=
Object
CELL
Unit/Range
Note
(VS.RAB.SuccEstabCS.AMRWB / VS.RAB.AttEstabCS.AMRWB)
*100%
3.1.27 Success Ratio of Cell Updates Initiated by CS Service of PCH

UEs
Table 3-27 Success Ratio of Cell Updates Initiated by CS Service of PCH UEs
Name
Success Ratio of Cell Updates Initiated by CS Service of PCH UEs
Formula
Issue 01 (2014-04-29)

84
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI monitors the CS access success rate of UEs in the CELL_PCH or
URA_PCH state.
If the switch for state transition to the CELL_PCH or URA_PCH state is
turned on on the network, smartphones will be always online. If there is no
data transmission for a certain period, the UE will transition to the
CELL_PCH or URA_PCH state instead of the idle mode. In this way, the UE
initiates new services in the CELL_PCH or URA_PCH state.
When there are a large number of smartphones, this KPI can better reflect
user experience.
l The procedure for cell update attempts initiated by UEs in the CELL_PCH
or URA_PCH state is as follows: When receiving from the UE a CELL
UPDATE message with the cause value "uplink data transmission" or
"paging response", the RNC calculates the respective number of cell
update attempts based on the values of "establish cause" contained in the
CELL UPDATE message. This counter is not measured for a CELL
UPDATE message retransmitted by the UE.
l The procedure for successful cell updates initiated by UEs in the
CELL_PCH or URA_PCH state is as follows: When receiving from the
UE a CELL UPDATE message with the cause value "uplink data
transmission" or "paging response", the RNC determines that the cell
update procedure is successful if it receives a response from the UE after
sending the CELL UPDATE CONFIRM message to the UE. Then the
RNC calculates the respective number of successful cell updates based on
the values of "establish cause" contained in the CELL UPDATE message.
For details about the cause values of the CELL UPDATE message, see
section 10.3.3.11 in 3GPP TS 25.331.
Associated
Counters
Success Ratio of Cell Updates Initiated by CS Service of PCH UEs =

(VS.SuccCellUpdt.OrgConvCall.PCH +
VS.SuccCellUpdt.TmConvCall.PCH +
VS.SuccCellUpdt.EmgCall.PCH) /
(VS.AttCellUpdt.OrgConvCall.PCH +
VS.AttCellUpdt.TmConvCall.PCH + VS.AttCellUpdt.EmgCall.PCH ) x
100%
Object
CELL
Unit/Range
Note
3.1.28 Success Ratio of Cell Updates Initiated by New PS Service of

PCH UEs
Table 3-28 Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs
Name
Issue 01 (2014-04-29)
Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs

85
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Formula
Description
This KPI monitors the PS access success rate of UEs in the CELL_PCH or
URA_CELL state.
If the switch for state transition to CELL_PCH or URA_PCH is turned on on
the network, smartphones will be always online. If there is no data
transmission for a certain period, the UE will transition to the CELL_PCH or
URA_PCH state instead of the idle mode. In this way, the UE initiates new
services in the CELL_PCH or URA_PCH state.
user experience.
l The procedure for cell update attempts initiated by UEs in the CEll_PCH
or URA_PCH state is as follows: When receiving from the UE a CELL
UPDATE message with the cause value "uplink data transmission" or
"paging response", the RNC calculates the respective number of cell
update attempts based on the values of "establish cause." This counter is
not measured for a CELL UPDATE message retransmitted by the UE.
l The procedure for successful cell updates initiated by UEs in the
CEll_PCH or URA_PCH state is as follows: When receiving from the UE
a CELL UPDATE message with the cause value "uplink data
transmission" or "paging response", the RNC determines that the cell
update procedure is successful if it receives a response from the UE after
sending the CELL UPDATE CONFIRM message to the UE. Then the
RNC calculates the respective number of successful cell updates based on
the values of "establish cause" contained in the CELL UPDATE message.
For details about the cause values of the CELL UPDATE message, see
section 10.3.3.11 in 3GPPTS 25.331.
Associated
Counters
Success Ratio of Cell Updates Initiated by New PS Service of PCH UEs =

(VS.SuccCellUpdt.OrgInterCall.PCH +
VS.SuccCellUpdt.OrgBkgCall.PCH +
VS.SuccCellUpdt.TmInterCall.PCH +
VS.SuccCellUpdt.TmBkgCall.PCH) /
(VS.AttCellUpdt.OrgInterCall.PCH +
VS.AttCellUpdt.OrgBkgCall.PCH +
VS.AttCellUpdt.TmInterCall.PCH +
VS.AttCellUpdt.TmBkgCall.PCH ) x 100%
Issue 01 (2014-04-29)
Object
CELL
Unit/Range
Note

86
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1.29 CS RAB Setup Success Ratio of PCH UEs

Table 3-29 CS RAB Setup Success Ratio of PCH UEs
Name
CS RAB Setup Success Ratio of PCH UEs
Formula
Description
This KPI monitors the success rate of CS RAB setups initiated by UEs in the
CELL_PCH or URA_PCH state.
If the switch for state transition to the CELL_PCH or URA_PCH state is
turned on on the network, smartphones will be always online. If there is no
data transmission for a certain period, the UE will transition to the
CELL_PCH or URA_PCH state instead of the idle mode. In this way, the UE
initiates new services in the CELL_PCH or URA_PCH state.
user experience.
l The procedure for CS RAB setup attempts initiated by UEs in the
CELL_PCH or URA_PCH state is as follows: A UE in the CELL_PCH
or URA_PCH state initiates CS services and transitions to another state.
After the RNC receives an RAB ASSIGNMENT REQUEST message
from the CS domain of the CN, the RNC calculates the number of CS
RAB setup attempts in the best cell of the UE based on the UE state.
l The procedure for successful CS RAB setups initiated by UEs in the
or URA_PCH state initiates CS services and transitions to another state.
from the CS domain of the CN and responds with an RAB ASSIGNMENT
RESPONSE message, the RNC calculates the number of successful CS
RAB setups in the best cell of the UE based on the UE state.
Associated
Counters
CS RAB Setup Success Ratio of PCH UEs =

( VS.SuccEstabCS.AfterP2F + VS.SuccEstabCS.AfterP2D ) /
( VS.AttEstabCS.AfterP2F+ VS.AttEstabCS.AfterP2D ) x 100%
Issue 01 (2014-04-29)
Object
CELL
Unit/Range
Note

87
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.1.30 New PS RAB Setup Success Ratio of PCH UEs

Table 3-30 New PS RAB Setup Success Ratio of PCH UEs
Name
New PS RAB Setup Success Ratio of PCH UEs
Formula
Description
This KPI monitors the success rate of the PS RAB setups initiated by UEs in
the CELL_PCH and URA_PCH states.
If the switch for state transition to CELL_PCH or URA_PCH is turned on on
the network, smartphones will be always online. If there is no data
transmission for a certain period, the UE will transition to the CELL_PCH or
URA_PCH state instead of the idle mode. In this way, the UE initiates new
services in the CELL_PCH or CELL_PCH state.
user experience.
l The procedure for the PS RAB setup attempt initiated by UEs in the
or URA_PCH state initiates PS services and transitions to another state.
from the PS domain of the CN, the RNC calculates the number of PS RAB
setup attempts in the best cell of the UE based on the UE state.
l The procedure for the successful PS RAB setup initiated by UEs in the
or URA_PCH state initiates PS services and transitions to another state.
from the PS domain of the CN and responds with an RAB ASSIGNMENT
RESPONSE message, the RNC calculates the number of successful PS
RAB setups in the best cell of the UE based on the UE state.
Associated
Counters
New PS RAB Setup Success Ratio of PCH UEs =

( VS.SuccEstabPS.AfterP2F + VS.SuccEstabPS.AfterP2D ) /
( VS.AttEstabPS.AfterP2F+ VS.AttEstabPS.AfterP2D ) x 100%
Object
CELL
Unit/Range
Note
3.2 Availability
Availability KPIs mainly indicate the utilization for several kinds of network resources such as
Radio, bandwidth or CPU Load.
Issue 01 (2014-04-29)

88
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.2.1 Worst Cell Ratio

Table 3-31 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.2 Paging Congestion Ratio

Table 3-32 Paging Congestion Ratio
Name
Issue 01 (2014-04-29)
Paging Congestion Ratio

89
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.2.3 Call Admission Refused Ratio

Issue 01 (2014-04-29)

90
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-33 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 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=
Object
CELL
Unit/Range
Note
[1-VS.RAC.NewCallAcc/VS.RAC.NewCallReq] x 100%
3.2.4 Congested Cell Ratio

Table 3-34 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.
Issue 01 (2014-04-29)

91
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
Congested Cell Ratio =
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.
(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%
3.2.5 Radio Network Unavailability Ratio

Table 3-35 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.2.6 Average CPU Load

Table 3-36 Average CPU Load
Name
Issue 01 (2014-04-29)
Average CPU Load

92
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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
Object
For BSC6900: XPU
For BSC6910: Average CPU Load= VS.SUBSYS.CPULOAD.MEAN
For BSC6910: SUBSYS

Unit/Range
Note
Mean CPU Utility is the CPU average load showed in percentage.
3.2.7 Iub Port Available Bandwidth Utilizing Ratio (UL)

Table 3-37 Iub Port Available Bandwidth Utilizing Ratio (UL)
Name
Iub Port Available Bandwidth Utilizing Ratio (UL)
Formula
Description
Issue 01 (2014-04-29)
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.

93
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.2.8 Iub Port Available Bandwidth Utilizing Ratio (DL)

Table 3-38 Iub Port Available Bandwidth Utilizing Ratio (DL)
Name
Iub Port Available Bandwidth Utilizing Ratio (DL)
Formula
Description
Issue 01 (2014-04-29)
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.
94
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
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.2.9 Cell Unavailability duration

Table 3-39 Cell Unavailability duration
Issue 01 (2014-04-29)
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

95
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Unit/Range
Note
None
3.2.10 HSDPA Unavailability duration

Table 3-40 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
Note
None
3.2.11 HSUPA Unavailability duration

Table 3-41 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
Note
None
3.2.12 CE Consumption for a NodeB Cell
Issue 01 (2014-04-29)

96
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-42 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.2.13 Hardware Configured CE for a NodeB

Table 3-43 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
Object
NodeB
Unit/Range
Numbers
Note
None
VS.HW.DLCreditAvailable
3.2.14 Shared Group Configured License CE for a NodeB

Issue 01 (2014-04-29)

97
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-44 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
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.
VS.LC.DLCreditAvailable.Shared
3.2.15 Shared Group License CE Consumption for a NodeB

Table 3-45 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.2.16 License Group Configured CE for a NodeB

Issue 01 (2014-04-29)

98
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-46 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
Object
NodeB
Unit/Range
Numbers
Note
If only one operator is available on the NodeB, the configured counter value
given above is Zero.
VS.LC.ULCreditAvailable.LicenseGroup.Dedicated
3.2.17 License Group CE Consumption for a NodeB

Table 3-47 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.
3.2.18 RTWP (Received Total Wideband Power)

Issue 01 (2014-04-29)

99
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-48 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.2.19 TCP (Transmitted Carrier Power)

Table 3-49 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 NonHSDPA 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
VS.HSDPA.MeanRequiredPwr
Issue 01 (2014-04-29)

100
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Object
CELL
Unit/Range
dBm
Note
None
3.2.20 R99 Code Utilization

Table 3-50 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.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.
3.2.21 Number of Codes Used by HS-PDSCHs

Issue 01 (2014-04-29)

101
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-51 Number of Codes Used by HS-PDSCHs

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

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

VS.PdschCodeUsed.Min provide the mean, maximum, and minimum
number of codes used by HS-PDSCHs in a cell during a measurement period
respectively.
Associated
Counters
VS.PdschCodeUsed.Mean
VS.PdschCodeUsed.Max
VS.PdschCodeUsed.Min
Object
NodeB
Unit/Range
None
Note
None
3.2.22 HSDPA Efficiency

Table 3-52 HSDPA Efficiency
Name
HSDPA Efficiency
Formula
HSDPA Efficiency = Duration when there is HSDPA data transmission/

Duration when there is HSDPA data in the buffer
Description
This KPI provides the proportion of the duration when there is HSDPA data
transmission to the duration when there is HSDPA data in the buffer.
Associated
Counters
HSDPA efficiency =
Object
NodeB
Unit/Range
Note
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)
indicates the proportion of TTIs with data transmission.
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)/
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean +
VS.HSDPA.ScheInactiveDataTtiRatio.Mean)
VS.HSDPA.ScheInactiveDataTtiRatio.Mean indicates the proportion of

TTIs when there is no data transmission but the scheduling candidate set
contains data from the buffer.
Issue 01 (2014-04-29)

102
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.3 Coverage
Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an
RNC or a cluster.
3.3.1 UL Interference Cell Ratio

Table 3-53 UL Interference Cell Ratio
Name
UL Interference Cell Ratio
Formula
Description
This KPI is used to check how the UL capacity is limited by the UL

interference of all cells in an RNC.
The mean RTWP's measurement is started when the RNC receives a
COMMON MEASUREMENT REPORT message from the NodeB about the
RTWP of a cell and obtains the RTWP of the cell.
Associated
Counters
UL Interference Cell Ratio =

[(The Number Of Cells In which VS.MeanRTWP >-98dBm)/The Total
Number Of Cells In RNC] x 100%
Object
RNC
Unit/Range
Note
-98 dBm is the value obtained based on the references from the commercial
network.
3.3.2 Soft Handover Overhead

Table 3-54 Soft Handover Overhead
KPI Name
Issue 01 (2014-04-29)
Soft Handover Overhead (RNC)

103
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Formula
A1: Number of UEs with 1 RL in the RNC

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

B1: Number of UEs with 2 RLs
C1: Number of UEs with 3 RLs
D1: Number of UEs with 4 RLs
E1: Number of UEs with 5 RLs
F1: Number of UEs with 6 RLs.
Description
This KPI is used to check the consumption of network resources due to soft
handover in an RNC or a Cell. It considered the radio link quantity during the
soft handover.
In the RNC Soft handover ratio, count the mean number of UEs with different
quantity of radio links for RNC from A1 to F1. The RNC periodically samples
of the number of UEs with corresponding radio links in a measurement period.
At the end of the measurement period, the RNC divides the accumulated
number by the sampling times to obtain the soft handover overhead.
The Cell level KPI is only available for cells in a cluster. From A1 to F1 count
the mean number of UEs with different quantity of Radio Links(1~6 radio
links) in the Cell of the active set.
Issue 01 (2014-04-29)

104
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
l Soft Handover Overhead (RNC)=

{[VS.SHO.AS.1.RNC +
(VS.SHO.AS.2Softer.RNC +
VS.SHO.AS.2Soft.RNC)*2 +
(VS.SHO.AS.3Soft2Softer.RNC +
VS.SHO.AS.3Soft.RNC +
VS.SHO.AS.3Softer.RNC )*3 +
VS.SHO.AS.4.RNC*4 +
VS.SHO.AS.5.RNC*5 +
VS.SHO.AS.6.RNC*6 ]/
(VS.SHO.AS.1.RNC +
VS.SHO.AS.2Softer.RNC +
VS.SHO.AS.3Soft2Softer.RNC +
VS.SHO.AS.3Softer.RNC +
VS.SHO.AS.4.RNC +
VS.SHO.AS.5.RNC +
VS.SHO.AS.6.RNC)-1}*100%
l Soft Handover Overhead (Cell)=
[(VS.SHO.AS.1RL +
VS.SHO.AS.2RL +
VS.SHO.AS.3RL +
VS.SHO.AS.4RL +
VS.SHO.AS.5RL +
VS.SHO.AS.6RL )/
(VS.SHO.AS.1RL +
VS.SHO.AS.2RL /2 +
VS.SHO.AS.3RL /3 +
VS.SHO.AS.4RL /4 +
VS.SHO.AS.5RL /5 +
VS.SHO.AS.6RL /6)-1]*100%
Issue 01 (2014-04-29)
Object
RNC, CELL
Unit/Range
Note
None

105
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.4 Mobility
Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or
service mode changing in difference scenarios.
3.4.1 Soft Handover Success Ratio

Table 3-55 Soft Handover Success Ratio
Name
Soft Handover Success Ratio
Formula
Description
This KPI is used to check the soft handover success ratio in an RNC or in a
Cluster, including softer handover.
l The Successful Soft Handover (including softer handovers) procedure is
complete when the RNC receives an ACTIVE SET UPDATE
COMPLETE message from the UE during the soft handover (including
the softer handover) procedure.
l The attempt procedure is complete when the RNC sends an ACTIVE SET
UPDATE message to the UE.
Associated
Counters
Soft Handover Success Ratio (RNC) =

(VS.SHO.Succ.RNC/VS.SHO.Att.RNC) x 100%
Soft Handover Success Ratio (Cell) =
[(VS.SHO.SuccRLAdd+ VS.SHO.SuccRLDel)/(VS.SHO.AttRLAdd
+VS.SHO.AttRLDel)] x 100%
Object
RNC, CELL
Unit/Range
Note
None
3.4.2 Softer Handover Success Ratio

Table 3-56 Softer Handover Success Ratio
Name
Softer Handover Success Ratio
Formula
Issue 01 (2014-04-29)

106
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI is used to check the softer handover success ratio in an RNC or a
Cluster, including softer handover.
l The Successful Softer Handover procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE
during the softer handover procedure.
l The attempt procedure is complete when the RNC sends an ACTIVE SET
Associated
Counters
Softer Handover Success Ratio (RNC) =

(VS.SoHO.Succ.RNC/VS.SoHO.Att.RNC) x 100%
Softer Handover Success Ratio (Cell) =
[(VS.SoHO.SuccRLAdd+VS.SoHO.SuccRLDel)/ (VS.SoHO.AttRLAdd
+VS.SoHO.AttRLDel)] x 100%
Object
RNC, CELL
Unit/Range
Note
None
3.4.3 AMR Soft Handover Success Ratio

Table 3-57 AMR Soft Handover Success Ratio
Name
AMR Soft Handover Success Ratio
Formula
Description
This KPI is used to check the AMR Soft Handover Success ratio in a Cluster,
including softer handover.
The Successful AMR Soft Handover procedure is complete when the RNC
during the soft handover procedure.
The attempt procedure is complete when the RNC sends an ACTIVE SET
Issue 01 (2014-04-29)
Associated
Counters
AMR Soft Handover Success Ratio =
Object
CELL
Unit/Range
Note
The RNC level KPI can be approximately calculated by accumulating all cell
counters within the RNC.
[(VS.SHO.AMR.Succ)/(VS.SHO.AMR.Att)] x 100%

107
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.4.4 CS64 Soft Handover Success Ratio

Table 3-58 CS64 Soft handover Success Ratio
Name
CS64 Soft handover Success Ratio
Formula
Description
This KPI is used to check the CS64 Soft Handover Success ratio in a Cluster,
The Successful CS64 Soft Handover procedure is complete when the RNC
Associated
Counters
CS64 Soft Handover Success Ratio =
Object
CELL
Unit/Range
Note
[(VS.SHO.CS64.Succ)/(VS.SHO.CS64.Att)] x 100%
3.4.5 PS Soft Handover Success Ratio

Table 3-59 PS soft handover Success Ratio
Name
PS soft handover Success Ratio
Formula
Issue 01 (2014-04-29)

108
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI is used to check the PS Soft Handover Success ratio in a Cluster,
The Successful PS Soft Handover procedure is complete when the RNC
Associated
Counters
PS services Soft Handover Success Ratio =
Object
CELL
Unit/Range
Note
[(VS.SHO.PS.Succ)/(VS.SHO.PS.Att)] x 100%
3.4.6 Intra-frequency Hard Handover Success Ratio

Table 3-60 Intra-frequency Hard Handover Success Ratio
Name
Intra-frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to check the intra-frequency hard handover success ratio in
an RNC or a Cluster.
The Intra-frequency Hard Handover Success procedure is complete when the
RNC receives the PHYSICAL CHANNEL RECONFIGURATION
COMPLETE (for example) message from the UE.
The Intra-frequency Hard Handover Attempt procedure is complete when
RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to
the UE.
Issue 01 (2014-04-29)

109
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
l Intra-frequency Hard Handover Success Ratio (Cell) =

[(VS.HHO.SuccIntraFreqOut.IntraNodeB+
VS.HHO.SuccIntraFreqOut.InterNodeBIntraRNC +
VS.HHO.SuccIntraFreqOut.InterRNC )/
(VS.HHO.AttIntraFreqOut.InterNodeBIntraRNC+
VS.HHO.AttIntraFreqOut.InterRNC +
VS.HHO.AttIntraFreqOut.IntraNodeB )] x 100%
l Intra-frequency Hard Handover Success Ratio (RNC) =
[(VS.HHO.SuccIntraFreq.RNC)/(VS.HHO.AttIntraFreq.RNC)] x
100%
Object
RNC, CELL
Unit/Range
Note
None
3.4.7 Inter-frequency Hard Handover Success Ratio

Table 3-61 Inter-frequency Hard Handover Success Ratio
Name
Inter-frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to check the inter-frequency hard handover success ratio in
an RNC or a Cluster.
The Inter-frequency Hard Handover Success procedure is complete when
RNC received a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from the UE.
The Inter-frequency Hard Handover attempts procedure starts when RNC
sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE.
In this case the RNC measures the counter.
Associated
Counters
Inter-frequency Hard Handover Success Ratio (RNC) =

(VS.HHO.SuccInterFreq.RNC/VS.HHO.AttInterFreq.RNC) x 100%
Inter-frequency Hard Handover Success Ratio (Cell) =
(VS.HHO.SuccInterFreqOut/VS.HHO.AttInterFreqOut) x 100%
Issue 01 (2014-04-29)
Object
RNC, CELL
Unit/Range

110
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
None
3.4.8 Service Cell Change Success Ratio with SHO (H2H)

Table 3-62 Service Cell Change Success Ratio with SHO (H2H)
Name
Service Cell Change Success Ratio with SHO (H2H)
Formula
Description
l The HS-DSCH service cell change success with SHO is triggered with
the following messages:
PHYSICAL CHANNEL RECONFIGURATION
TRANSPORT CHANNEL RECONFIGURATION
RADIO BEARER RECONFIGURATION
ACTIVE SET UPDATE
l Accordingly, the UE sends the following messages to the RNC as a
response.
PHYSICAL CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION COMPLETE
ACTIVE SET UPDATE COMPLETE
Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example. When receiving a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from a UE, the RNC measures this item as numerator,
and when sending a PHYSICAL CHANNEL RECONFIGURATION
message to a UE, the RNC measures this item as denominator.
Associated
Counters
Service Cell Change Success Ratio with SHO (H2H) =
Object
CELL
Unit/Range
Note
None
(VS.HSDPA.SHO.ServCellChg.SuccOut/
VS.HSDPA.SHO.ServCellChg.AttOut) x 100%
3.4.9 H2H Intra-Frequency Hard Handover Success Ratio

Issue 01 (2014-04-29)

111
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-63 H2H Intra-Frequency Hard Handover Success Ratio

Name
H2H Intra-Frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to check the intra-frequency hard handover success ratio of
HSDPA service in a Cluster.
l The HS-DSCH service cell change success with SHO is triggered with
the following message:
RADIO BEARER SETUP
RADIO BEARER RELEASE
response.
RADIO BEARER SETUP COMPLETE
RADIO BEARER RELEASE COMPLETE
example, when receiving a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from a UE , the RNC measures this item in the best
cell from which the UE is handed over if an intra-frequency HSDPA hard
handover without channel change is performed.
Issue 01 (2014-04-29)
Associated
Counters
H2H Intra-Frequency Hard Handover Success Ratio =
Object
CELL
Unit/Range
Note
(VS.HSDPA.HHO.H2H.SuccOutIntraFreq/VS.HSDPA.HHO.H2H.AttOutIntraFreq) x 100%

112
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.4.10 H2H Inter-Frequency Hard Handover Success Ratio

Table 3-64 H2H Inter-Frequency Hard Handover Success Ratio
Name
H2H Inter-Frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to indicate the success ratio of inter-frequency hard

handovers from the HSDPA to the HSDPA in a cell.
l The hard handover procedure can be triggered with the following
message:
RADIO BEARER SETUP
response.
example, when receiving a PHYSICAL CHANNEL RECONFIGURATION
COMPLETE message from a UE , the RNC measures this item in the best
cell from which the UE is handed over if an inter-frequency HSDPA hard
handover without channel change is performed.
Associated
Counters
Issue 01 (2014-04-29)
H2H Inter-Frequency Hard Handover Success Ratio=

(VS.HSDPA.HHO.H2H.SuccOutInterFreq/VS.HSDPA.HHO.H2H.AttOutInterFreq) x 100%
Object
CELL
Unit/Range
Note
None

113
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.4.11 H2D Intra-Frequency Hard Handover Success Ratio

Table 3-65 H2D Intra-Frequency Hard Handover Success Ratio
Name
H2D Intra-Frequency Hard Handover Success Ratio
Formula
H2D Intra-Frequency Hard Handover Success Ratio = Number of successful

H2D intra-frequency hard handovers x 100%/Number of H2D intrafrequency hard handover attempts
Description
This KPI provides the success rate of HSDPA-to-DCH intra-frequency hard

handovers in a cell.
A hard handover is triggered by any of the following messages:
l RADIO BEARER RECONFIGURATION
l RADIO BEARER SETUP
l RADIO BEARER RELEASE
Accordingly, a UE may respond with one of the following messages:
l RADIO BEARER RECONFIGURATION COMPLETE
l RADIO BEARER SETUP COMPLETE
l RADIO BEARER RELEASE COMPLETE
Assume that a hard handover is triggered by the RADIO BEARER
RECONFIGURATION message. The number of successful H2D intrafrequency hard handovers is measured in the best cell where the UE camps
on before the hard handover when the RNC receives from the UE a RADIO
BEARER RECONFIGURATION COMPLETE message during an intrafrequency hard handover.
Associated
Counters
H2D Intra-frequency Hard Handover Success Ratio =

(VS.HSDPA.HHO.H2D.SuccOutIntraFreq/ VS.HSDPA.HHO.H2D.AttOutIntraFreq)*100%
Object
CELL
Unit/Range
Note
3.4.12 H2D Inter-Frequency Hard Handover Success Ratio

Table 3-66 H2D Inter-Frequency Hard Handover Success Ratio
Name
H2D Inter-Frequency Hard Handover Success Ratio
Formula
Issue 01 (2014-04-29)

114
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI is used to indicate the success ratio of inter-frequency hard

handovers from the HSDPA to the DCH in a cell.
l The hard handover procedure can be triggered with the following
messages:
RADIO BEARER SETUP
response.
Take the RADIO BEARER RECONFIGURATION message as an example,
when receiving a RADIO BEARER RECONFIGURATION COMPLETE
message from a UE , the RNC measures this item in the best cell from which
the UE is handed over if an inter-frequency hard handover from the HSDPA
to the DCH is performed.
Associated
Counters
H2D Inter-Frequency Hard Handover Success Ratio =
Object
CELL
Unit/Range
Note
None
(VS.HSDPA.HHO.H2D.SuccOutInterFreq/VS.HSDPA.HHO.H2D.AttOutInterFreq) x 100%
3.4.13 E2D Intra-Frequency Hard Handover Success Ratio

Table 3-67 E2D Intra-Frequency Hard Handover Success Ratio
Issue 01 (2014-04-29)
Name
E2D Intra-Frequency Hard Handover Success Ratio
Formula
E2D Intra-Frequency Hard Handover Success Ratio = Number of successful

E2D intra-frequency hard handovers x 100%/Number of E2D intra-frequency
hard handover attempts

115
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the success rate of EDCH-to-DCH intra-frequency hard

handovers in a cell.
The number of E2D intra-frequency hard handover attempts is measured in
the HSUPA serving cell where the UE camps on before the handover when
the RNC sends the UE a RADIO BEARER RECONFIGURATION message
during an EDCH-to-DCH intra-frequency hard handover.
The number of successful E2D intra-frequency hard handovers is measured
in the HSUPA serving cell where the UE camps on before the handover when
the RNC receives from the UE a RADIO BEARER RECONFIGURATION
COMPLETE message during an EDCH-to-DCH intra-frequency hard
handover.
Associated
Counters
E2D Intra-frequency Hard Handover Success Ratio =
Object
CELL
Unit/Range
Note
(VS.HSUPA.HHO.E2D.SuccOutIntraFreq/VS.HSUPA.HHO.E2D.AttOutIntraFreq)*100%
3.4.14 H2D Channel Switch Success Ratio

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

116
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
H2D Channel Switch Success Ratio=
Object
CELL
Unit/Range
Note
(VS.HSDPA.H2D.Succ/VS.HSDPA.H2D.Att) x 100%
3.4.15 D2H Channel Switch Success Ratio

Table 3-69 D2H Channel Switch Success Ratio
Name
D2H Channel Switch Success Ratio
Formula
Description
This KPI is used to check the channel switch success ratio when the UE
switches from DCH to HSDPA i a Cluster.
The number of successful DCH to HS-DSCH channel switch measures when
RNC receives from the UE a RAIDO BEARER RECONFIGURATION
COMPLETE message indicating the channel reconfiguration for HSDPA
service in the DCCC or RAB MODIFY procedure. The RNC measures the
item in the HSDPA serving cell.
The attempt number of D2H channel switch counts when RNC decides to
perform a channel switch, which sends a RADIO BEARER
RECONFIGURATION message to a UE during the DCCC or RAB MODIFY
procedure. In this case, the RNC measures the item in the serving cell of the
HSDPA service according to the transport channels of UEs before and after
the reconfiguration.
The RNC performs the transport channel switch in the same cell.
Issue 01 (2014-04-29)
Associated
Counters
D2H Channel Switch Success Ratio =
Object
CELL
Unit/Range
Note
(VS.HSDPA.D2H.Succ/VS.HSDPA.D2H.Att) x 100%

117
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.4.16 CS W2G Inter-RAT Handover Out Success Ratio

Table 3-70 CS W2G Inter-RAT Handover Out Success Ratio
Name
CS W2G Inter-RAT Handover Out Success Ratio
Formula
Description
This KPI is used to indicate the success ratio of CS Outgoing inter-RAT

handovers in an RNC or a Cluster.
The CS inter-RAT Handover Success procedure is complete when the RNC
receives an IU RELEASE COMMAND message with the cause value of
"Successful Relocation", "Normal Release", or "Network Optimization" after
sending a HANDOVER FROM UTRAN COMMAND message during the
CS outgoing inter-RAT handover. In this case, the outgoing handover
succeeds and this counter is measured.
Number of CS W2G inter-RAT handover attempts = Number of
HANDOVER FROM UTRAN COMMAND messages sent from the RNC
during CS outgoing inter-RAT handovers - Number of CS inter-RAT
handover cancellations caused by UE's failures in receiving the message
Associated
Counters
CS W2G Inter-RAT Handover Out Success Ratio (RNC) =

(VS.IRATHO.SuccOutCS.RNC/VS.IRATHO.AttOutCS.RNC) x 100%
CS W2G Inter-RAT Handover Out Success Ratio (Cell) =
[(IRATHO.SuccOutCS)/(IRATHO.AttOutCS VS.IRATHOCS.Cancel.ReEstab)] x 100%
Object
RNC, CELL
Unit/Range
Note
You are advised to accumulate the related numerators and denominators of

the cell level to calculate RNC-level KPIs. For example, if there are n cells
under an RNC, an RNC-level KPI is calculated in the following formula:
{Sum(IRATHO.SuccOutCS)/[Sum(IRATHO.AttOutCS) - Sum
(VS.IRATHOCS.Cancel.ReEstab)]} x 100%
3.4.17 PS W2G Inter-RAT Handover Out Success Ratio

Table 3-71 PS W2G Inter-RAT Handover Out Success Ratio
Name
Issue 01 (2014-04-29)
PS W2G Inter-RAT Handover Out Success Ratio

118
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Formula
Description
This KPI is used to indicate the success ratio of PS outgoing inter-RAT

handover initiated by the RNC or in the best cell.
The PS W2G Inter-RAT Outgoing Handover successes procedure is complete
when the RNC sends the RANAP IU RELEASE COMPLETE message after
receiving the IU RELEASE COMMAND message with the cause of
"Successful Relocation", "Normal Release" or "Network Optimization." In
this case, the PS outgoing inter-RAT handover succeeds and the counter is
measured.
Number of PS W2G inter-RAT handover attempts = Number of CELL
CHANGE ORDER FROM UTRAN messages sent from the RNC during PS
outgoing inter-RAT handovers - Number of PS inter-RAT handover
cancellations caused by UE's failures in receiving the message
Associated
Counters
PS W2G Inter-RAT Handover Out Success Ratio(RNC) =

(VS.IRATHO.SuccOutPSUTRAN.RNC/
VS.IRATHO.AttOutPSUTRAN.RNC) x 100%
PS W2G Inter-RAT Handover Out Success Ratio (Cell) =
[IRATHO.SuccOutPSUTRAN/(IRATHO.AttOutPSUTRAN VS.IRATHOPS.Cancel.ReEstab)] x 100%
Object
RNC, CELL
Unit/Range
Note
You are advised to accumulate the related numerators and denominators of

the cell level to calculate RNC-level KPIs. For example, if there are n cells
under an RNC, an RNC-level KPI is calculated in the following formula:
{Sum(IRATHO.SuccOutPSUTRAN)/[Sum(IRATHO.AttOutPSUTRAN) Sum(VS.IRATHOPS.Cancel.ReEstab)]} x 100%
3.4.18 PS G2W Inter-RAT Handover In Success Ratio

Table 3-72 PS G2W Inter-RAT Handover In Success Ratio
Name
PS G2W Inter-RAT Handover In Success Ratio
Formula
Issue 01 (2014-04-29)

119
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI is used to check the PS inter-RAT handover in success ratio in a

Cluster.
The PS G2W Inter-RAT Handover successes procedure is complete when the
RNC receives an RRC CONNECTION SETUP COMPLETE message from
the UE. The reasons for RRC connection request is Inter-RAT Cell Change
Order and Inter-RAT Cell Reselection.
The PS G2W Inter-RAT Handover attempts procedure starts when the RNC
receives an RRC CONNECTION REQUEST message from the UE, the
reasons for RRC connection request are Inter-RAT Cell Change Order and
Inter-RAT Cell Reselection.
Associated
Counters
PS G2W Inter-RAT Handover In Success Ratio=

[(RRC.SuccConnEstab.IRATCCO+RRC.SuccConnEstab.IRATCelRes)/
(RRC.AttConnEstab.IRATCCO+RRC.AttConnEstab.IRATCelRes)] x
100%
Object
CELL
Unit/Range
Note
The KPI includes the IRAT cell reselection of UE in idle status.The RNC
level KPI is calculated by aggregating all the cell counters.
3.4.19 HSDPA W2G Inter-RAT Handover Out Success Ratio

Table 3-73 HSDPA W2G Inter-RAT Handover Out Success Ratio
Name
HSDPA W2G Inter-RAT Handover Out Success Ratio
Formula
Description
This KPI is used to check the PS outgoing inter-RAT handover for HSDPA
services initiated by the RNC in the best cell that the UE camps on before the
handover.
The HSDPA Inter-RAT HO successes procedure is complete when the RNC
receives the IU RELEASE COMMAND message. The message contains one
of the following information: "Successful Relocation", "Normal Release",
"Network Optimization" during the PS outgoing inter-RAT handover for
HSDPA services.
The HSDPA Inter-RAT HO attempts procedure starts when the RNC sends
the CELL CHANGE ORDER FROM UTRAN message during the PS
outgoing inter-RAT handover for HSDPA services, the counter is measured
in the best cell that the UE camps on.
Issue 01 (2014-04-29)

120
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
HSDPA W2G Inter-RAT Handover Out Success Ratio=

(VS.IRATHO.HSDPA.SuccOutPSUTRAN/VS.IRATHO.HSDPA.AttOutPSUTRAN) x 100%
Object
CELL
Unit/Range
Note
The KPI includes the IRAT cell reselection of UE in idle status.
3.4.20 SRNC Relocation Success Ratio

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

[(VS.SRELOC.SuccExecUEInvolCS+
VS.SRELOC.SuccExecUEInvolPS +
VS.SRELOC.SuccExecUENonInvolCS +
VS.SRELOC.SuccExecUENonInvolPS)/
(RELOC.SuccPrepUEInvolCS+
RELOC.SuccPrepUENotInvolCS +
RELOC.SuccPrepUEInvolPS+
RELOC.SuccPrepUENotInvolPS)] x 100%
Issue 01 (2014-04-29)
Object
RNC
Unit/Range

121
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
None
3.4.21 TRNC Relocation Success Ratio

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

[(VS.TRELOC.SuccExecUEInvolCS+
VS.TRELOC.SuccExecUEInvolPS+
VS.TRELOC.SuccExecUENotInvolCS+
VS.TRELOC.SuccExecUENotInvolPS)/
(RELOC.SuccResAllocUEInvolCS+
RELOC.SuccResAllocUENotInvolCS+
RELOC.SuccResAllocUEInvolPS+
RELOC.SuccResAllocUENotInvolPS)] x 100%
Object
RNC
Unit/Range
Note
None
3.4.22 E-DCH Soft Handover Success Ratio

Issue 01 (2014-04-29)

122
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-76 E-DCH Soft Handover Success Ratio

Name
E-DCH Soft Handover Success Ratio
Formula
Description
This KPI is used to check EDCH RL additions and deletions due to soft
handover in a cell.
The E-DCH soft Handover Success procedure is complete when the RNC
receives an ACTIVE SET UPDATE COMPLETE message from the UE.An
EDCH link is added or deleted during the soft handover.
The E-DCH soft Handover attempts procedure starts when the RNC sends an
ACTIVE SET UPDATE message to the UE and there is EDCH RL to be
deleted or added during the soft handover.
Associated
Counters
E-DCH Soft Handover Success Ratio=
Object
CELL
Unit/Range
Note
None
(VS.HSUPA.SHO.SuccOut/VS.HSUPA.SHO.AttOut) x 100%
3.4.23 E-DCH Cell Change Success Ratio with SHO

Table 3-77 E-DCH Cell Change Success Ratio with SHO
Name
E-DCH Cell Change Success Ratio with SHO
Formula
Issue 01 (2014-04-29)

123
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI is used to check the success ratio of HSUPA serving cell changes
in soft handover status for cell.
l The successful HSUPA serving cell changes in soft handover status for
cell, this procedure can be triggered with the following messages:
l Accordingly, the UE sends the following messaged to the RNC as a
response:
l Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example, when the RNC receives a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message from the UE, the RNC
measures this item in the original HSUPA serving cell if the HSUPA
serving cell is changed. The item is used to indicate the change of HSUPA
serving cells in the soft handover state instead of the hard handover state.
Description of the denominator:
l Take the PHYSICAL CHANNEL RECONFIGURATION message as an
example, when the RNC sends a PHY CHANNEL
RECONFIGURATION message to the UE. The RNC measures this item
in the original HSUPA serving cell if the HSUPA serving cell is changed.
This item is used to indicate the change of HSUPA serving cells in the
soft handover status instead of the hard handover status.
Associated
Counters
E-DCH Service Cell Change Success Ratio with SHO =
Object
CELL
Unit/Range
Note
None
(VS.HSUPA.SHO.ServCellChg.SuccOut/
VS.HSUPA.SHO.ServCellChg.AttOut) x 100%
3.4.24 E-DCH Cell Change Success Ratio with Inter-HHO

Table 3-78 E-DCH Cell Change Success Ratio with Inter-HHO
Name
Issue 01 (2014-04-29)
E-DCH Cell Change Success Ratio with Inter-HHO

124
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Formula
Description
This KPI is used to check the E-DCH service cell change success ratio with
the Inter-HHO procedure in an RNC or a cluster.
Description of the denominator:
l When the RNC sends the following messages to the UE, the RNC
measures the item in the HSUPA serving cell before the hard handover if
an EDCH-to-EDCH inter-frequency hard handover is performed.
PHYSICAL CHANNEL RECONFIGRATION
TRANSPORT CHANNEL RECONFIGRATION
RADIO BEARER RECONFIGRATION
RADIO BEARER SETUP
l When the RNC receives one of the following messages from the UE, the
RNC measures this item in the HSUPA serving cell before the hard
handover if an EDCH-to-EDCH inter-frequency hard handover is
performed.
Associated
Counters
E-DCH Service Cell Change Success Ratio with Inter-HHO=
Object
CELL
Unit/Range
Note
None
(VS.HSUPA.HHO.E2E.SuccOutInterFreq/VS.HSUPA.HHO.E2E.AttOutInterFreq) x 100%
3.4.25 E2D Channel Switch Success Ratio

Table 3-79 E2D Channel Switch Success Ratio
Name
Issue 01 (2014-04-29)
E2D Channel Switch Success Ratio

125
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Formula
Description
This KPI is used to check the channel switch success ratio when there is UE
handover from E-DCH to DCH in the same cell.
The Switch Channel Type from EDCH to DCH successful attempts procedure
is complete when the RNC receives an RB RECFG CMP message from the
UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the
same cell after reconfigurations, the RNC measures the items in the HSUPA
serving cell by the channel switch type.
The Switch Channel Type from EDCH to DCH attempts procedure starts
when the RNC sends a RADIO BEAR RECONFIGURE message to the UE
during the DCCC or RAB ASSIGN procedure. If the UE camps on the same
cell after reconfigurations, the RNC measures the items in the HSUPA serving
cell by the channel switch type.
Associated
Counters
E2D Channel Switch Success Ratio =
Object
CELL
Unit/Range
Note
None
(VS.HSUPA.E2D.Succ/VS.HSUPA.E2D.Att) x 100%
3.4.26 D2E Channel Switch Success Ratio

Table 3-80 D2E Channel Switch Success Ratio
Name
D2E Channel Switch Success Ratio
Formula
Issue 01 (2014-04-29)

126
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI is used to check the channel switch success ratio when there is UE
handover from E-DCH to DCH in the same cell.
The Switch Channel Type from DCH to EDCH successful attempts procedure
is complete when the RNC receives an RB RECFG CMP message from the
UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the
same cell after reconfigurations, the RNC measures the items in the HSUPA
serving cell by the channel switch type.
The Switch Channel Type from DCH to EDCH attempts procedure starts
when the RNC sends a RADIO BEAR RECONFIGURE message to the UE
during the DCCC or RAB ASSIGN procedure. If the UE camps on the same
cell after reconfigurations, the RNC measures the items in the HSUPA serving
cell by the channel switch type.
Associated
Counters
D2E Channel Switch Success Ratio (Intra Cell) =
Object
CELL
Unit/Range
Note
None
(VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att) x 100%
3.4.27 E2D Handover Success Ratio with Inter HHO

Table 3-81 E2D Handover Success Ratio with Inter HHO
Name
E2D Handover Success Ratio with Inter HHO
Formula
Description
This KPI is used to check the success ratio of HSUPA Inter-Frequency Hard
Handover from EDCH to DCH in a cell.
The Switch Channel Type from EDCH to DCH successful attempts procedure
is complete when the RNC receives a RADIO BEARER
RECONFIGURATION COMPLETE message from the UE. The RNC
measures this item in the HSUPA serving cell before the hard handover if an
EDCH-to-DCH inter-frequency hard handover is performed.
The Switch Channel Type from EDCH to DCH attempts procedure starts
when the RNC sends a RADIO BEARER RECONFIGURATION message
to the UE. The RNC measures this item in the HSUPA serving cell before the
hard handover if an EDCH-to-DCH inter-frequency hard handover is
performed.
Issue 01 (2014-04-29)

127
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
E-DCH to DCH Handover Success Ratio (with Inter HHO) =
Object
CELL
Unit/Range
Note
None
(VS.HSUPA.HHO.E2D.SuccOutInterFreq/VS.HSUPA.HHO.E2D.AttOutInterFreq) x 100%
3.4.28 HSUPA W2G Inter-RAT Handover Out Success Ratio

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

(VS.IRATHO.HSUPA.SuccOutPSUTRAN/VS.IRATHO.HSUPA.AttOutPSUTRAN) x 100%
Object
CELL
Unit/Range
Note
None

128
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.4.29 MBMS Service Mode Switch Success Ratio

Table 3-83 MBMS Service Mode Switch Success Ratio
Name
MBMS Service Mode Switch Success Ratio
Formula
Description
This KPI is used to check the MBMS service mode switch success ratio from
PTP to PTM.
The MBMS Service Mode Switch Success procedure is complete after a
MBMS service is switched from PTP mode to PTM mode and a PTM MBMS
RB is successfully set up.
The MBMS Service Mode Switch attempts procedure starts after the initiation
of transition from PTP mode to PTM mode.
Associated
Counters
MBMS Service Mode Switch Success Ratio from PTP to PTM=
Object
CELL
Unit/Range
Note
None
(VS.MBMS.PTPtoPTM.Succ/VS.MBMS.PTPtoPTM.Att)*100%
3.4.30 CS Inter-Frequency Hard Handover Success Rate

Table 3-84 CS Inter-Frequency Hard Handover Success Rate
Name
CS Inter-Frequency Hard Handover Success Rate
Formula
CS Inter-Frequency Hard Handover Success Rate = Number of successful

CS inter-frequency hard handovers x 100%/Number of CS inter-frequency
hard handover attempts
Description
This KPI provides the success rate of CS inter-frequency hard handovers of

a Cluster.
The number of CS inter-frequency hard handover attempts is measured when
the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION
message during a CS inter-frequency hard handover.
The number of successful CS inter-frequency hard handovers is measured
when the RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message during a CS inter-frequency
hard handover.
Issue 01 (2014-04-29)

129
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
CS Inter-frequency Hard Handover Success Ratio =

(VS.HHO.SuccInterFreqOut.CS/ VS.HHO.AttInterFreqOut.CS) *
100%
Object
CELL
Unit/Range
Note
RNC-level KPIs are obtained by accumulating values of cell-level counter.
3.4.31 PS Inter-Frequency Hard Handover Success Rate

Table 3-85 PS Inter-Frequency Hard Handover Success Rate
Name
PS Inter-Frequency Hard Handover Success Rate
Formula
PS Inter-Frequency Hard Handover Success Rate = Number of successful PS

inter-frequency hard handovers x 100%/Number of PS inter-frequency hard
handover attempts
Description
This KPI provides the success rate of PS inter-frequency hard handovers of

a Cluster.
The number of PS inter-frequency hard handover attempts is measured when
the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION
message during a PS inter-frequency hard handover.
The number of successful PS inter-frequency hard handovers is measured
when the RNC receives from the UE a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message during a PS inter-frequency
hard handover.
Associated
Counters
PS Inter-frequency Hard Handover Success Ratio=
Object
CELL
Unit/Range
Note
RNC-level KPIs are obtained by accumulating values of cell-level counter.
(VS.HHO.SuccInterFreqOut.PS/ VS.HHO.AttInterFreqOut.PS)*100%
3.5 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.
3.5.1 CS Service Drop Ratio

Issue 01 (2014-04-29)

130
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-86 CS Service Drop Ratio

Name
CS Service Drop Ratio
Formula
Description
This KPI provides the ratio of the CS RAB abnormal Releases to the total CS
RAB Releases (Normal Release + Abnormal Release). This KPI is used to
check the retainabililty of CS Service within the UTRAN (RNC or Cluster).
Description of RAB abnormal Release:
The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE
REQUEST message to the CN due to exceptions. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with the
causes other than "User Inactivity", "Normal Release", "Successful
Relocation", "Network Optimization", the RNC measures the items
according to the service types in the best cell that the UE camps on if the
released RABs belong to PS domain.
Associated
Counters
CS Service Drop Ratio (Cell) =

[VS.RAB.AbnormRel.CS/(VS.RAB.AbnormRel.CS+
VS.RAB.NormRel.CS)] x 100%
CS Service Drop Ratio (RNC) =
[VS.RAB.AbnormRel.CS.RNC/(VS.RAB.AbnormRel.CS.RNC+
VS.RAB.NormRel.CS.RNC)] x 100%
Object
CELL, RNC
Unit/Range
Note
This KPI involves CS call drops due to authentication failure during PS

security mode in the cell. You can subtract VS.RAB.AbnormRel.CS.Security from the numerator of the formula to decrease the value of this KPI.
3.5.2 CS Call Drop Rate in CS+PS Combined Services

Table 3-87 CS Call Drop Rate in CS+PS Combined Services
Issue 01 (2014-04-29)
Name
CS Call Drop Rate in CS+PS Combined Services
Formula
CS Call Drop Rate in CS+PS Combined Services = Number of times that a

CS call in a CS+PS combined service drops/Number of CS+PS combined
service release times

131
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the drop rate of CS calls in CS+PS combined services.
It reflects the retainability of CS+PS combined services in an RNC or cluster.
When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST
message. After receiving the message, the CN sends an IU RELEASE
COMMAND message to the RNC. If the IU RELEASE COMMAND
message contains a cause value of abnormal release (causes except "User
Inactivity", "Normal Release", "Successful Relocation", or "Network
Optimization"), then the number of times that a CS call in a CS+PS combined
service drops is measured in the best cell that the UE camps on if the message
is for a CS call in a CS+PS combined service.
Associated
Counters
CS Call Drop Rate in CS+PS Combined Services (Cell) =

(VS.MultiRAB.CSAbnormRel.CSPS/
(VS.MultiRAB.CSNormRel.CSPS +
VS.MultiRAB.CSAbnormRel.CSPS +
VS.MultiRAB.PSNormRel.CSPS))*100%
Object
CELL
Unit/Range
Note
None
3.5.3 PS Call Drop Rate in CS+PS Combined Services

Table 3-88 PS Call Drop Rate in CS+PS Combined Services
Name
PS Call Drop Rate in CS+PS Combined Services
Formula
PS Call Drop Rate in CS+PS Combined Services = Number of times that a

PS connection in a CS+PS combined service fails/Number of CS+PS
combined service release times
Description
This KPI provides the PS connection failure rate in CS+PS combined

services.
It reflects the retainability of CS+PS combined services in an RNC or cluster.
When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST
message. After receiving the message, the CN sends an IU RELEASE
COMMAND message to the RNC. If the IU RELEASE COMMAND
message contains a cause value of abnormal release (causes except "User
Inactivity", "Normal Release", "Successful Relocation", or "Network
Optimization"), then the number of times that a PS connection in a CS+PS
combined service fails is measured in the best cell that the UE camps on if
the message is for a PS service in a CS+PS combined service.
Issue 01 (2014-04-29)

132
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
PS Call Drop Rate in CS+PS Combined Services (Cell)=

(VS.MultiRAB.PSAbnormRel.CSPS/
(VS.MultiRAB.CSNormRel.CSPS + VS.MultiRAB.PSNormRel.CSPS +
VS.MultiRAB.PSAbnormRel.CSPS))*100%
Object
CELL
Unit/Range
Note
None
3.5.4 AMR Call Drop Ratio

Table 3-89 AMR Call Drop Ratio
Name
AMR Call Drop Ratio
Formula
Description
This KPI provides the ratio of AMR RAB abnormal Releases to the total
AMR RAB Releases (Normal Release + Abnormal Release) and is used to
check the retainabililty of AMR Service within the UTRAN (RNC or Cluster).
REQUEST message to the CNdue to exception. If the RNC receives an IU
RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with
any one of the following messages: "User Inactivity","Normal Release",
"Successful Relocation", "Network Optimization", the RNC measures the
items according to the service types in the best cell that the UE camps on if
the released RABs belong to PS domain.
Associated
Counters
AMR Call Drop Ratio (Cell) =

[VS.RAB.AbnormRel.AMR/(VS.RAB.AbnormRel.AMR+
VS.RAB.NormRel.AMR)] x 100%
AMR Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.AMR}+ Sum
{VS.RAB.AbnormRel.AMR.Iur})/
(Sum{VS.RAB.AbnormRel.AMR}+ Sum{VS.RAB.NormRel.AMR}+
Sum{VS.RAB.AbnormRel.AMR.Iur}+
Sum{VS.RAB.NormRel.AMR.Iur} )] x 100%
Issue 01 (2014-04-29)
Object
CELL, RNC
Unit/Range
Note
The RNC level KPIs are calculated by aggregating all the Cell and Iur
counters in SRNC.
133
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.5.5 WB AMR Call Drop Rate

Table 3-90 WB AMR Call Drop Rate
Name
WB AMR Call Drop Rate
Formula
WB AMR Call Drop Rate = Number of abnormally released WB AMR calls

x 100%/Total number of released WB AMR calls
Description
This KPI provides the proportion of abnormally released WB AMR calls to

the total number of released WB AMR calls. It reflects the retainability of
WB AMR calls in an RNC or a cluster.
When a fault occurs, the RNC sends the CN an IU RELEASE REQUEST or
RAB RELEASE REQUEST message. The number of abnormally released
WB AMR calls is measured in the best cell where the UE camps on when the
RNC receives an IU RELEASE COMMAND or RAB ASSIGNMENT
REQUEST message whose cause value is not "User Inactivity", "Normal
Release", "Successful Relocation", or "Network Optimization".
Associated
Counters
WB AMR Call Drop Rate (Cell) =

[VS.RAB.AbnormRel.AMRWB/ (VS.RAB.AbnormRel.AMRWB +
VS.RAB.NormRel.AMRWB)] * 100%
AMRWB Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.AMRWB} + Sum
{VS.RAB.AbnormRel.AMRWB.Iur})/(Sum
{VS.RAB.AbnormRel.AMRWB} + Sum{VS.RAB.NormRel.AMRWB}
+ Sum{VS.RAB.AbnormRel.AMRWB.Iur} + Sum
{VS.RAB.NormRel.AMRWB.Iur} )]*100%
Object
CELL, RNC
Unit/Range
Note
None
3.5.6 VP Call Drop Ratio

Table 3-91 VP Call Drop Ratio
Name
VP Call Drop Ratio
Formula
Issue 01 (2014-04-29)

134
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the ratio of the VP (Video Phone) RAB abnormal Releases
to the total VP RAB Releases (Normal Release + Abnormal Release) and is
used to check the retainabililty of VP Service of the UTRAN (RNC or
Cluster).
REQUEST message to the CN due to exception. If the RNC receives an IU
any one of the following information: "User Inactivity","Normal Release",
Associated
Counters
VP Call Drop Ratio (Cell) =

[VS.RAB.AbnormRel.CS64/(VS.RAB.AbnormRel.CS64
+VS.RAB.NormRel.CS64)] x 100%
VP Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.CS64}+Sum
{VS.RAB.AbnormRel.CS64.Iur})/
(Sum{VS.RAB.AbnormRel.CS64}+Sum{VS.RAB.NormRel.CS64}
+Sum{VS.RAB.AbnormRel.CS64.Iur}+Sum
{VS.RAB.NormRel.CS64.Iur})] x 100%
Object
CELL, RNC
Unit/Range
Note
None
3.5.7 AMR Traffic Drop Ratio

Table 3-92 AMR Traffic Drop Ratio
Name
AMR Traffic Drop Ratio
Formula
Issue 01 (2014-04-29)

135
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the ratio of the AMR Service Erlang to the AMR RAB
Abnormal Releases, which indicates the AMR average Erlang per AMR call
drop within the UTRAN (RNC or Cluster).
Description of the AMR RB counters in the numerator:
Average number of AMR users with different DL rates during the
measurement period.
any one of the following information: "User Inactivity", "Normal Release",
Associated
Counters
l AMR Traffic Drop Ratio (Cell) =

[(VS.RB.AMR.DL.12.2+
VS.RB.AMR.DL.10.2 +
VS.RB.AMR.DL.7.95 +
VS.RB.AMR.DL.7.4 +
VS.RB.AMR.DL.6.7 +
VS.RB.AMR.DL.5.9 +
VS.RB.AMR.DL.5.15 +
VS.RB.AMR.DL.4.75 ) x {SP}/60]/
VS.RAB.AbnormRel.AMR
l AMR Traffic Drop Ratio (RNC) =
[(VS.RB.AMR.DL.4.75.RNC+
VS.RB.AMR.DL.5.15.RNC +
VS.RB.AMR.DL.12.2.RNC ) x {SP}/60]/
(VS.RAB.AbnormRel.AMR.RNC)
Issue 01 (2014-04-29)
Object
CELL, RNC
Unit/Range
The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit
of minute
Note
None

136
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.5.8 VP Traffic Drop Ratio

Table 3-93 VP Traffic Drop Ratio
Name
VP Traffic Drop Ratio
Formula
Description
This KPI provides the ratio of the VP (Video Phone) Service Erlang to the
VP RAB Abnormal Releases, which indicates the VP average Erlang per VP
call drop within the UTRAN (RNC or Cluster).
Description of the VS.RB.CS.Conv.DL.64/VS.RB.CS.Conv.DL.64.RNC:
Average number of VP users with different DL rates during the measurement
period.
Description of RAB Abnormal Release:
REQUEST message to the CN due to exception.
If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT
REQUEST message with any one of the following information: "User
Inactivity", "Normal Release", "Successful Relocation", "Network
Optimization", the RNC measures the items according to the service types in
the best cell that the UE camps on if the released RABs belong to PS domain.
Associated
Counters
VP Traffic Drop Ratio (Cell) =

(VS.RB.CS.Conv.DL.64 x {SP}/60)/VS.RAB.AbnormRel.CS64
VP Traffic Drop Ratio (RNC) =
(VS.RB.CS.Conv.DL.64.RNC x {SP}/60)/
(VS.RAB.AbnormRel.CS64.RNC)
Object
CELL, RNC
Unit/Range
The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit
of minute
Note
None
3.5.9 PS Call Drop Ratio

Table 3-94 PS Call Drop Ratio
Name
PS Call Drop Ratio
Formula
Issue 01 (2014-04-29)

137
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the ratio of the PS RAB abnormal Releases to the total
PSRAB Releases (Normal Release + Abnormal Release) and is used to check
the retainabililty of PS Service within the UTRAN (RNC or Cluster).
Associated
Counters
PS Call Drop Ratio (Cell) =

[VS.RAB.AbnormRel.PS/(VS.RAB.AbnormRel.PS+
VS.RAB.NormRel.PS)] x 100%
PS Call Drop Ratio (RNC) =
[VS.RAB.AbnormRel.PS.RNC/(VS.RAB.AbnormRel.PS.RNC+
VS.RAB.NormRel.PS.RNC)] x 100%
Object
CELL, RNC
Unit/Range
Note
This KPI involves PS connection failures due to authentication failure during

PS security mode in the cell. You can subtract VS.RAB.AbnormRel.PS.Security from the numerator of the formula to decrease the value of this KPI.
3.5.10 PS Call Drop Ratio (PCH)

Table 3-95 PS Call Drop Ratio (PCH)
Name
PS Call Drop Ratio (PCH)
Formula
Issue 01 (2014-04-29)

138
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
Compared with 3.5.9 PS Call Drop Ratio, this KPI deducts abnormal RAB
releases caused by UE's state transition to CELL_PCH or URA_PCH.
Smartphones stay in the always-online state in networks when state transition
to PCH is enabled. If state transition to PCH is enabled and there is no data
transmission for a specific period of time, these UEs transit from connected
mode to the PCH state instead of idle mode, resulting in abnormal PS RAB
releases. As a result, the number of normal PS RAB releases decreases and
the value of denominator Total Number of PS RAB Releases is reduced.
The corresponding KPI deteriorates if the original formula for calculating PS
Call Drop Ratio is used.
A RAB release caused by UE's state transition from CELL_DCH to
CELL_PCH or URA_PCH without PS data transmission should be
considered as a normal RAB release because the transition has no impact on
user experience. Therefore, PCH-related abnormal RAB releases caused by
state transition from CELL_DCH to CELL_PCH or URA_PCH are not taken
into account for calculating PS Call Drop Ratio.
Issue 01 (2014-04-29)

139
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
l PS Call Drop Ratio with PCH (Cell) =

[(VS.RAB.AbnormRel.PSVS.RAB.AbnormRel.PS.PCHVS.RAB.AbnormRel.PS.D2PVS.RAB.AbnormRel.PS.F2P) /
(VS.RAB.AbnormRel.PS+
VS.RAB.NormRel.PSVS.RAB.AbnormRel.PS.PCHVS.RAB.NormRel.PS.PCH+
VS.DCCC.D2P.Succ+
VS.DCCC.Succ.F2P+
VS.DCCC.Succ.F2U+
VS.DCCC.Succ.D2U)] x 100%
l PS Service Drop Ratio with PCH (RNC) =
[(VS.RAB.AbnormRel.PS.RNCSum{VS.RAB.AbnormRel.PS.PCH}Sum{VS.RAB.AbnormRel.PS.D2P}Sum{VS.RAB.AbnormRel.PS.F2P})/
(VS.RAB.AbnormRel.PS.RNC+
VS.RAB.NormRel.PS.RNCSum{VS.RAB.AbnormRel.PS.PCH}Sum{VS.RAB.NormRel.PS.PCH} +
Sum{VS.DCCC.D2P.Succ} +
Sum{VS.DCCC.Succ.F2P} +
Sum{VS.DCCC.Succ.F2U}+
Sum{VS.DCCC.Succ.D2U})] x 100%
Issue 01 (2014-04-29)
Object
CELL, RNC
Unit/Range

140
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
1. A RAB release caused by UE's state transition to PCH state should be

considered as a normal RAB release for calculating PS Call Drop Ratio.
2. Why VS.RAB.normRel.PS.PCH and VS.RAB.AbnormRel.PS.PCH is
subtracted from the denominator?
l If a UE transit to PCH state and then to idle mode, it will be counted
twice respectively in VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P,
VS.DCCC.Succ.F2U, VS.DCCC.Succ.D2U ) and
VS.RAB.NormRel.PS.
l The same reason as VS.RAB.AbnormRel.PS.PCH.
3. The measurement object of the counters in Sum{*} is the cell, the RNC
level KPI can be calculated approximately by aggregating all the cell level
counters in the SRNC. Due to the counters are counted in the best cell of
active set, If the best cell for the PS RAB Establishment located in DRNC
via Iur interface, this scenario is not taken into account in the formula.
3.5.11 PS Call Drop Ratio (PCH & Combined Service)

Table 3-96 PS Call Drop Ratio (PCH & Combined Service)
Name
PS Call Drop Ratio (PCH & Combined Service)
Formula
Description
Compared with 3.5.10 PS Call Drop Ratio (PCH), this KPI deducts
abnormal RAB releases caused by PS service timer expiration after a
successful CS inter-RAT handover in combined CS+PS service.
For CS+PS combined services, after CS inter-RAT handovers are complete,
abnormal RAB releases caused by expiration of the PS service timer are
regarded as problems occurring in GSM networks. Therefore, they are not
taken into account for calculating PS Call Drop Ratio in UMTS networks.
Issue 01 (2014-04-29)

141
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
l PS Call Drop Ratio with PCH (Cell) =

[(VS.RAB.AbnormRel.PSVS.MultiRAB.PSAbnormRel.ResumeExp VS.RAB.AbnormRel.PS.PCH VS.RAB.AbnormRel.PS.D2P VS.RAB.AbnormRel.PS.F2P)/
(VS.RAB.AbnormRel.PS +
VS.RAB.NormRel.PS VS.RAB.AbnormRel.PS.PCH VS.RAB.NormRel.PS.PCH +
VS.DCCC.D2P.Succ +
VS.DCCC.Succ.F2P +
VS.DCCC.Succ.F2U +
VS.DCCC.Succ.D2U)] x 100%
l PS Service Drop Ratio with PCH (RNC) =
[(VS.RAB.AbnormRel.PS.RNC Sum{VS.MultiRAB.PSAbnormRel.ResumeExp} Sum{VS.RAB.AbnormRel.PS.PCH} Sum{VS.RAB.AbnormRel.PS.D2P} Sum{VS.RAB.AbnormRel.PS.F2P})/
(VS.RAB.AbnormRel.PS.RNC +
VS.RAB.NormRel.PS.RNC Sum{VS.RAB.AbnormRel.PS.PCH} Sum{VS.RAB.NormRel.PS.PCH} +
Sum{VS.DCCC.D2P.Succ} +
Sum{VS.DCCC.Succ.F2P} +
Sum{VS.DCCC.Succ.F2U} +
Sum{VS.DCCC.Succ.D2U})] x 100%
Issue 01 (2014-04-29)
Object
Cell, RNC
Unit/Range

142
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
1. A RAB release caused by UE's state transition to PCH state should be

considered as a normal RAB release for calculating PS Call Drop Ratio.
2. Why VS.RAB.normRel.PS.PCH and VS.RAB.AbnormRel.PS.PCH is
subtracted from the denominator?
l If a UE transit to PCH state and then to idle mode, it will be counted
twice respectively in VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P,
VS.DCCC.Succ.F2U, VS.DCCC.Succ.D2U ) and
VS.RAB.NormRel.PS.
l The same reason as VS.RAB.AbnormRel.PS.PCH.
3. The measurement object of the counters in Sum{*} is the cell, the RNC
level KPI can be calculated approximately by aggregating all the cell level
counters in the SRNC. Due to the counters are counted in the best cell of
active set, If the best cell for the PS RAB Establishment located in DRNC
3.5.12 PS R99 Call Drop Ratio

Table 3-97 PS R99 Call Drop Ratio
Name
PS R99 Call Drop Ratio
Formula
Description
This KPI provides the ratio of the PS R99 RAB abnormal Releases to the total
PS R99RAB Releases (Normal Release + Abnormal Release) and is used to
check the retainabililty of PS R99 Service within the UTRAN (RNC or
Cluster).
Issue 01 (2014-04-29)

143
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
PS R99 Call Drop Ratio (Cell) =

(VS.RAB.AbnormRel.PSR99)/(VS.RAB.AbnormRel.PSR99
+VS.RAB.NormRel.PSR99) x 100%
PS R99 Call Drop Ratio (RNC)=
[VS.RAB.AbnormRel.PSR99+
(VS.RAB.AbnormRel.PS.Conv.Iur+
VS.RAB.AbnormRel.PS.Str.Iur+
VS.RAB.AbnormRel.PS.BE.IurVS.RAB.AbnormRel.HSDPA.Iur)]/
[VS.RAB.AbnormRel.PSR99+
VS.RAB.NormRel.PSR99+
(VS.RAB.NormRel.PS.Conv.Iur+
VS.RAB.NormRel.PS.Str.Iur+
VS.RAB.NormRel.PS.BE.IurVS.RAB.NormRel.HSDPA.Iur)+
(VS.RAB.AbnormRel.PS.Conv.Iur+
VS.RAB.AbnormRel.PS.Str.Iur+
VS.RAB.AbnormRel.PS.BE.IurVS.RAB.AbnormRel.HSDPA.Iur)]*100%
Object
CELL
Unit/Range
Note
This KPI involves the call drops of UEs in CELL_PCH, URA_PCH, or

CELL_FACH state.
3.5.13 PS R99 Call Drop Ratio (PCH)

Table 3-98 PS R99 Call Drop Ratio (PCH)
Name
PS R99 Call Drop Ratio (PCH)
Formula
Description
Issue 01 (2014-04-29)
Compared with PS R99 Call Drop Ratio, this KPI takes the PCH state into
account.

144
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
PS R99 Call Drop Ratio with PCH (Cell) =

[(VS.RAB.AbnormRel.PSR99VS.RAB.AbnormRel.PS.PCHVS.RAB.AbnormRel.PS.R99D2PVS.RAB.AbnormRel.PS.F2P)/
(VS.RAB.AbnormRel.PSR99+
VS.RAB.NormRel.PSR99VS.RAB.AbnormRel.PS.PCHVS.RAB.NormRel.PS.PCH+
VS.HSDPA.F2H.Succ+
VS.HSDPA.D2H.Succ+
VS.PSR99.D2P.Succ+
VS.DCCC.Succ.F2P+
VS.DCCC.Succ.F2U)] x 100%
Object
CELL
Unit/Range
Note
The occasion of a UE transferring out of PS R99 state (F2H, F2P, D2H) should
be considered as a normal RAB release for calculating the formula of PS R99
Call Drop Ratio.
RNC level KPI can be calculated approximately by aggregating all the cell
level counters in SRNC. Due to the counters are counted in the best cell of
active set, If the best cell for the PS R99 RAB Establishment located in DRNC
VS.RAB.AbnormRel.PSR99 and VS.RAB.NormRel.PSR99 have already
taken PCH into account, the occasion of the RAB Normal/Abnormal Release
(VS.RAB.AbnormRel.PS.PCH and VS.RAB.NormRel.PS.PCH) should
be excluded off the Denominator.
3.5.14 PS BE Call Drop Ratio

Table 3-99 PS BE Call Drop Ratio
Name
PS BE Call Drop Ratio
Formula
Issue 01 (2014-04-29)

145
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the ratio of the PS BE RAB abnormal Releases to the total
PS BE RAB Releases (Normal Release + Abnormal Release) and is used to
check the retainabililty of PS BE Service of the UTRAN (RNC or Cluster).
Associated
Counters
PS BE Call Drop Ratio (Cell) =

[VS.RAB.AbnormRel.PS.BE/(VS.RAB.AbnormRel.PS.BE +
VS.RAB.NormRel.PS.BE)] x 100%
PS BE Call Drop Ratio (RNC) =
[(Sum{VS.RAB.AbnormRel.PS.BE} + Sum
{VS.RAB.AbnormRel.PS.BE.Iur})/
(Sum{VS.RAB.AbnormRel.PS.BE} + Sum{VS.RAB.NormRel.PS.BE}
+Sum{VS.RAB.AbnormRel.PS.BE.Iur}+
Sum{VS.RAB.NormRel.PS.BE.Iur} )] x 100%
Object
CELL, RNC
Unit/Range
Note
RNC level KPI can be calculated approximately by aggregating all the Cell
and Iur level counters in SRNC.
3.5.15 HSDPA Call Drop Ratio

Table 3-100 HSDPA Call Drop Ratio
Name
HSDPA Call Drop Ratio
Formula
Issue 01 (2014-04-29)

146
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the ratio of the HSDPA RAB abnormal Releases to the
total HSDPA RAB Releases (Normal Release+ Abnormal Release) and is
used to check the retainabililty of HSDPA Service within the UTRAN (RNC
or Cluster).
Associated
Counters
l HSDPA Call Drop Ratio (Cell) =

[(VS.HSDPA.RAB.AbnormRel)/
(VS.HSDPA.RAB.AbnormRel+
VS.HSDPA.RAB.NormRel+
VS.HSDPA.H2D.Succ+
VS.HSDPA.H2F.Succ+
VS.HSDPA.HHO.H2D.SuccOutIntraFreq+
VS.HSDPA.HHO.H2D.SuccOutInterFreq)] x 100%
l HSDPA Call Drop Ratio (RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur})/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}+
Sum{VS.RAB.NormRel.HSDPA.Iur}+
Sum{VS.HSDPA.RAB.NormRel}+
Sum{VS.HSDPA.H2D.Succ}+
Sum{VS.HSDPA.H2F.Succ}+
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq})] x 100%
Object
CELL, RNC
Unit/Range
Note
RNC level KPI is calculated approximately by aggregating all the Cell and
Iur level counters in SRNC.
The successful channel transition is considered as normal HSDPA RAB
release (Including the transitions due to mobility).
3.5.16 HSDPA Call Drop Ratio (PCH)

Issue 01 (2014-04-29)

147
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-101 HSDPA Call Drop Ratio (PCH)

Name
HSDPA Call Drop Ratio (PCH)
Formula
Description
Compared with HSDPA Call Drop Ratio, this KPI takes the PCH state into
account.
Associated
Counters
l HSDPA Service Drop Ratio with PCH (Cell) =

[(VS.HSDPA.RAB.AbnormRelVS.HSDPA.RAB.AbnormRel.H2P)/
(VS.HSDPA.RAB.AbnormRel+
VS.HSDPA.RAB.NormRel+
VS.HSDPA.HHO.H2D.SuccOutIntraFreq+
VS.HSDPA.HHO.H2D.SuccOutInterFreq+
VS.HSDPA.H2D.Succ+
VS.HSDPA.H2F.Succ+
VS.HSDPA.H2P.Succ)] x 100%
l HSDPA Service Drop Ratio with PCH(RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}Sum{VS.HSDPA.RAB.AbnormRel.H2P})/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur}+
Sum{VS.RAB.NormRel.HSDPA.Iur}+
Sum{VS.HSDPA.RAB.NormRel}+
Sum{VS.HSDPA.H2D.Succ}+
Sum{VS.HSDPA.H2F.Succ}+
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq}+
Sum{VS.HSDPA.H2P.Succ})] x 100%
Issue 01 (2014-04-29)
Object
CELL, RNC
Unit/Range
Note
The occasion of a UE transferring out of PS HS-DSCH Channel state (H2D,

H2F, H2P) should be considered as a normal RAB release for calculating the
formula of PS HSDPA Call Drop Ratio.

148
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.5.17 HSUPA Call Drop Ratio

Table 3-102 HSUPA Call Drop Ratio
Name
HSUPA Call Drop Ratio
Formula
Description
This KPI provides the ratio of the HSUPA RAB abnormal Releases to the
total HSUPARAB Releases (Normal Release + Abnormal Release) and is
used to check the retainabililty of HSUPA Service of the UTRAN (RNC or
Cluster).
Associated
Counters
l HSUPA Call Drop Ratio (Cell) =

[VS.HSUPA.RAB.AbnormRel/
(VS.HSUPA.RAB.AbnormRel+
VS.HSUPA.RAB.NormRel +
VS.HSUPA.HHO.E2D.SuccOutIntraFreq +
VS.HSUPA.HHO.E2D.SuccOutInterFreq +
VS.HSUPA.E2F.Succ +
VS.HSUPA.E2D.Succ )] x 100%
l HSUPA Call Drop Ratio (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur} )/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel} +
Sum{VS.RAB.AbnormRel.HSUPA.Iur} +
Sum{VS.RAB.NormRel.HSUPA.Iur} +
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq} +
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq} +
Sum{VS.HSUPA.E2F.Succ} +Sum{VS.HSUPA.E2D.Succ})] x 100%
Issue 01 (2014-04-29)
Object
CELL, RNC
Unit/Range

149
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
RNC level KPI is calculated approximately by aggregating all the Cell and
Iur level counters in SRNC.
The successful channel transition is considered as normal E-DCH release
(Including the transitions due to mobility).
3.5.18 HSUPA Call Drop Ratio (PCH)

Table 3-103 HSUPA Call Drop Ratio (PCH)
Name
HSUPA Call Drop Ratio (PCH)
Formula
Description
Compared with HSUPA Call Drop Ratio, this KPI takes the PCH state into
account.
Associated
Counters
l HSUPA Call Drop Ratio with PCH (Cell) =

[(VS.HSUPA.RAB.AbnormRelVS.HSUPA.RAB.AbnormRel.E2P )/
(VS.HSUPA.RAB.AbnormRel+
VS.HSUPA.RAB.NormRel +
VS.HSUPA.HHO.E2D.SuccOutIntraFreq +
VS.HSUPA.HHO.E2D.SuccOutInterFreq+
VS.HSUPA.E2F.Succ +
VS.HSUPA.E2D.Succ +
VS.HSUPA.E2P.Succ )] x 100%
l HSUPA Call Drop Ratio with PCH (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}Sum{VS.HSUPA.RAB.AbnormRel.E2P} )/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur}+
Sum{VS.RAB.NormRel.HSUPA.Iur}+
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq}+
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq}+
Sum{VS.HSUPA.E2F.Succ} +
Sum{VS.HSUPA.E2D.Succ} +
Sum{VS.HSUPA.E2P.Succ} )] x 100%
Issue 01 (2014-04-29)

150
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Object
CELL, RNC
Unit/Range
Note
The occasion of a UE transferring out of PS E-DCH Channel state (E2D, E2F,

E2P) should be considered as a normal RAB release for calculating the
formula of PS HSUPA Call Drop Ratio.
3.5.19 MBMS Service PTP drop Ratio

Table 3-104 MBMS Service PTP drop Ratio
Name
MBMS Service PTP drop Ratio
Formula
Associated
Counters
MBMS Service PTP Drop Ratio =

[VS.MBMS.RB.PTP.Loss.Abnorm/(VS.MBMS.RB.PTP.Loss.Abnorm
+VS.MBMS.RB.PTP.Loss.norm)]*100%
Object
CELL
Unit/Range
Note
The RNC level KPIs are calculated by aggregating all the cell counters.
3.5.20 DC-HSDPA Call Drop Ratio

Table 3-105 DC-HSDPA Call Drop Ratio
Name
DC-HSDPA Call Drop Ratio
Formula
Issue 01 (2014-04-29)

151
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI evaluates the retainability of DC-HSDPA services in an RNC or a

cluster. And this KPI takes the CELL_PCH or URA_PCH state into account.
l Abnormal release:
When an exception occurs, the RNC sends the CN an IU RELEASE
REQUEST or an RAB RELEASE REQUEST message. If the RNC
receives from the CN an RAB ASSIGNMENT REQUEST message with
a cause value other than "User Inactivity", "Normal Release", "Successful
Relocation", "Network Optimization", or "UE Generated Signalling
ConnectionRelease", this counter is incremented in the best cell for the
UE.
l Normal release:
Normal releases includes RAB releases over the Iu interface and the
switchover of the RAB from a technique to another one, involving the
following scenarios:
RAB releases over the Iu interface
Fallback to the SC-HSDPA RAB through intra-cell channel
switchovers
Fallback to the R99 RAB (including R99 RABs of UEs in the
CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH state)
through intra-cell channel switchovers
Fallback to SC-HSDPA RAB through inter-cell hard handovers
(including intra-frequency and inter-frequency hard handovers)
Fallback to R99 RAB of UEs in the CELL_DCH state through intercell hard handovers (including intra-frequency and inter-frequency
hard handovers)
Fallback to HSDPA RAB of SRB over DCH through the setup of
combined services
Fallback to R99 RAB of UEs in the CELL_DCH state through the
setup of combined services
NOTE
Unless otherwise stated, SRB over HSDPA users are those whose SRBs are carried on
the HSDPA and that are in the CELL_DCH state.
Issue 01 (2014-04-29)
Associated
Counters
Call Drop Rate of DC-HSDPA Services =

[( VS.HSDPA.RAB.DC.AbnormRel
VS.HSDPA.RAB.AbnormRel.DC2P)/(VS.HSDPA.RAB.DC.AbnormRel + VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object
CELL
Unit/Range
Note

152
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.5.21 HSDPA 64QAM Call Drop Ratio

Table 3-106 HSDPA 64QAM Call Drop Ratio
Name
HSDPA 64QAM Call Drop Ratio
Formula
Description
This KPI evaluates the retainability of HSDPA 64QAM services in an RNC

or a cluster. And this KPI takes the CELL_PCH or URA_PCH state into
account.
l Abnormal release:
REQUEST or an RAB RELEASE REQUEST message. When the RNC
receives from the CN an IU RELEASE COMMAND message or an RAB
ASSIGNMENT REQUEST message with a cause value other than "User
Optimization", or "UE Generated Signalling Connection Release", this
counter is incremented in the best cell for the UE.
l Normal release:
Normal releases include the RAB releases over the Iu interface and the
Fallback to the HSDPA RAB through intra-cell channel switchovers
Fallback to HSDPA RAB through inter-cell hard handovers (including
intra-frequency and inter-frequency hard handovers)
hard handovers)
Issue 01 (2014-04-29)
Associated
Counters
Call Drop Rate of HSDPA+64QAM Services =

[( VS.HSDPA.RAB.AbnormRel.64QAM VS.HSDPA.RAB.AbnormRel.64QAM2P )/(VS.HSDPA.RAB.AbnormRel.64QAM +
VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object
CELL
Unit/Range
Note

153
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.5.22 HSDPA MIMO Call Drop Ratio

Table 3-107 HSDPA MIMO Call Drop Ratio
Name
HSDPA MIMO Call Drop Ratio
Formula
Description
This KPI evaluates the retainability of HSDPA services in an RNC or a

l Abnormal release:
l Normal release:
Normal releases includes RAB releases over the Iu interface and the
hard handovers)
Issue 01 (2014-04-29)
Associated
Counters
HSDPA MIMO Call Drop Rate =

[( VS.HSDPA.RAB.AbnormRel.MIMO
VS.HSDPA.RAB.AbnormRel.MIMO2P)/
(VS.HSDPA.RAB.AbnormRel.MIMO +
Object
CELL
Unit/Range
Note

154
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.5.23 HSDPA MIMO+64QAM Call Drop Ratio

Table 3-108 HSDPA MIMO+64QAM Call Drop Ratio
Name
HSDPA MIMO+64QAM Call Drop Ratio
Formula
Description
This KPI evaluates the retainability of HSDPA services in an RNC or a

l Abnormal release:
l Normal release:
Normal releases include the RAB releases over the Iu interface and the
Fallback to the HSDPA MIMO RAB through intra-cell channel
switchovers
Fallback to the HSDPA 64QAM RAB through intra-cell channel
switchovers
Fallback to HSDPA MIMO RAB through inter-cell hard handovers
through inter-cell hard handovers
Fallback to HSDPA 64QAM RAB through inter-cell hard handovers
hard handovers)
Issue 01 (2014-04-29)

155
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
HSDPA MIMO+64QAM Call Drop Rate =

[( VS.HSDPA.RAB.AbnormRel.MIMO64QAM
VS.HSDPA.RAB.AbnormRel.MIMO64QAM2P)/
(VS.HSDPA.RAB.AbnormRel.MIMO64QAM +
Object
CELL
Unit/Range
Note
3.6 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.
3.6.1 Average UL Throughput for PS R99 Service

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

156
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
Average UL Throughput for PS R99 Service (Active Set Cell) =

VS.PS.Bkg.Kbps.UL8 +
VS.PS.Int.Kbps.UL8 +
VS.PS.Str.Kbps.UL8 +
VS.PS.Conv.Kbps.UL
Object
CELL
Unit/Range
kbit/s
Note
None
Table 3-110 Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)
Name
Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)
Description
This KPI provides the average uplink throughput for PS R99 BE services of
a single user in a best cell.
The uplink throughput (excluding the RLC headers and retransmitted data)
for PS BE services of all users on the DCH is accumulated in a measurement
period. At the same time, the number of times when the value of the sampled
uplink throughput is not 0 is accumulated. At the end of the measurement
period, the RNC divides the total uplink throughput by the total sampling
times to obtain the average uplink throughput for PS R99 services of a single
user in a best cell.
Issue 01 (2014-04-29)

157
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)

=
VS.PS.BE.DCH.UL.SumThroughput/
VS.PS.BE.DCH.UL.SamplesThroughput
Object
CELL
Unit/Range
kbit/s
Note
None
3.6.2 Average DL Throughput for PS R99 Service

Table 3-111 Average DL Throughput for PS R99 Service (Active Set Cell)
Name
Average DL Throughput for PS R99 Service (Active Set Cell)
Description
These counters provide the average downlink rates of different PS R99

services in the cells of the active set.
The DL traffic (excluding the RLC header and the retransmitted data, unit:
bit) and the Data transfer duration (unit: ms) of each kind of PS R99 services
are accumulated in the measurement period for the cells that are under the
SRNC. At the end of the measurement period, the RNC divides the total bytes
by the total data transfer time to obtain the Average DL Throughput for each
PS R99 Service.
Issue 01 (2014-04-29)

158
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
Average DL Throughput for PS R99 Service (Active Set Cell) =

VS.PS.Bkg.Kbps.DL8 +
VS.PS.Int.Kbps.DL8 +
VS.PS.Str.Kbps.DL8 +
VS.PS.Conv.Kbps.DL
Object
CELL
Unit/Range
kbit/s
Note
None
Table 3-112 Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)
Name
Issue 01 (2014-04-29)
Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)

159
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the average downlink throughput for PS R99 BE services
of a single user in a best cell.
The downlink throughput (excluding the RLC headers and retransmitted data)
of PS BE services for all users on the DCH is accumulated in a measurement
period. At the same time, the number of times when the value of the sampled
downlink throughput is not 0 is accumulated. At the end of the measurement
period, the RNC divides the total downlink throughput by the total sampling
times to obtain the average downlink throughput for PS R99 services of a
single user in a best cell.
Associated
Counters
Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)

=
VS.PS.BE.DCH.DL.SumThroughput +
VS.PS.BE.DCH.DL.SamplesThroughput
Object
CELL
Unit/Range
kbit/s
Note
None
3.6.3 Average UL BLER for CS Service

Table 3-113 Average UL BLER for CS Service
Name
Average UL BLER for CS Service
Description
These counters provide the UL BLER of AMR and CS 64K Conv. services
on the DCH in the best cell. The counters are triggered in the best cell when
the number of UL TBs carrying the CS services on the DCH reaches the
defined sampling window (500 TBs).
Associated
Counters
VS.ULBler.AMR
Object
CELL
Unit/Range
Note
None
VS.ULBler.CS64
3.6.4 Average UL BLER for PS Service

Table 3-114 Average UL BLER for PS Service
Name
Issue 01 (2014-04-29)
Average UL BLER for PS Service

160
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This counter provides the UL BLER of PS services on the DCH in the best
cell.
The counters are triggered in the best cell when the number of UL TBs
carrying the PS services on the DCH reaches the defined sampling window
(500 TBs).
Associated
Counters
Average UL BLER for PS Service =

VS.ULBler.PS.BE.DCH.8 +
VS.ULBler.PS.BE.RACH +
VS.ULBler.PS.Conv +
VS.ULBler.PS.Str
Object
CELL
Unit/Range
Note
None
3.6.5 HSDPA Throughput

Table 3-115 Mean Throughput for One HSDPA User
Name
Mean Throughput for One HSDPA User
Description
This counter indicates the mean downlink throughput for ONE HSDPA UE
in a cell.
When the data is transferred to an HSDPA serving cell, the RNC measures
the data transfer time of all the UEs and the total bytes sent in the cell. At the
end of the measurement period, the RNC divides the total bytes by the total
data transfer time to obtain the mean downlink throughput of MAC-d flow
in the cell. The RLC header and the retransmitted data are excluded.
Issue 01 (2014-04-29)
Associated
Counters
Mean Throughput for One HSDPA User =
Object
CELL
Unit/Range
kbit/s
VS.HSDPA.MeanChThroughput

161
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
For 3900 series NodeBs, it is recommended that you use the NodeB counters
in the following formula to calculate the single user throughput. These NodeB
counters measure the valid throughput when data exists in the user buffer
every transmission time interval (TTI). In this case, the value of this KPI is
more accurate for UEs. The throughput of a single user at the NodeB MAChs layer is calculated using the following formula:
VS.HSDPA.DataOutput.Traffic/
(VS.HSDPA.DataTtiNum.User x 2)
NOTE
VS.HSDPA.DataOutput.Traffic measures the total traffic volume of the MAC-hs/
MAC-ehs PDUs with ACKs from all users in a TTI within a measurement period. (Unit :
bit).
VS.HSDPA.DataTtiNum.User measures the total number of user-level TTIs (TTI =
2ms) within which there is data to transmit in HSDPA user queue buffers within a
measurement period. (VS.HSDPA.DataTtiNum.User x 2) and converts the number of
TTIs to the data transmission time.
Table 3-116 Mean Throughput for One HSDPA Cell

Name
Mean Throughput for One HSDPA Cell
Description
This counter provides the MAC-hs throughput when at least one HSDPA user
is transferring data at the physical layer during the entire measurement period.
Associated
Counters
Mean Throughput for One HSDPA Cell =
Object
NodeB
Unit/Range
kbit/s
Note
1. We can apply the following formula to get the Mean HSDPA Cell
Throughput within RNC approximately:
VS.DataOutput.Mean/(VS.DataTtiRatio.Mean VS.HSDPA.InactiveDataTtiRatio.Mean)
HSDPA Cell Throughput (RNC Cell) =

VS.HSDPA.MeanChThroughput.TotalBytes x 8/ [{SP} x 60]/1000
Where:
l {SP} is the Statistic Period with the unit of Minute.
l The KPI may not be accurate under the following condition: there is
no HSDPA User transferring data for a while during the total
measurement period. Therefore, the KPI should be evaluated during
busy hour for accuracy.
2. For 3900 series NodeBs, the HSDPA throughput at the MAC-hs layer is
calculated using the following formula:
VS.HSDPA.DataOutput.Traffic/
[(VS.DataTtiRatio.Mean VS.HSDPA.InactiveDataTtiRatio.Mean) x {SP} x 60]
Issue 01 (2014-04-29)

162
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.6.6 HSUPA Throughput

Table 3-117 Mean Throughput for One HSUPA User
Name
Mean Throughput for One HSUPA User
Description
This counter indicates the mean uplink throughput for ONE HSUPA UE in
a cell.
When the data is received in HSUPA active cells, the RNC measures the data
transfer time of all the UEs and the total bytes received in the cell. At the end
of the measurement period, the RNC divides the total bytes by the total data
transfer time to obtain the mean uplink throughput of MAC-d flow in the cell.
The RLC header and the retransfer data are excluded.
Associated
Counters
Mean Throughput for One HSUPA User =
Object
CELL
Unit/Range
kbit/s
Note
It is recommended that you use the NodeB counters in the following formula
to calculate the single user throughput. These NodeB counters measure the
actual transmission rate sampled every transmission time interval (TTI) over
the air interface. In this case, the value of this KPI is more accurate for UEs.
The throughput of a single user transmitting the TRB data at the NodeB MACe/i layer is calculated using the following formula:
VS.HSUPA.MeanChThroughput
(VS.HSUPA.2msTTI.Traffic +
VS.HSUPA.10msTTI.Traffic)/
(VS.HSUPA.2msPDU.TTI.Num x 0.002 +
VS.HSUPA.10msPDU.TTI.Num x 0.01)
Table 3-118 Mean Throughput for One HSUPA Cell

Name
Mean Throughput for One HSUPA Cell
Description
This counter provides the Mean HSUPA Cell Throughput when at least one
HSUPA UE is transmitting data during the entire measurement period.
When the data (including SRB and TRB data) of HSUPA UEs is received in
HSUPA active cells, the NodeB measures the total data that UEs successfully
receive at the MAC-e/i layer in the serving cell. At the same time, the NodeB
measures the number of TTIs when at least one HSUPA UE is transmitting
data to obtain the total transmission duration. (If there are multiple UEs
transmitting data in a TTI, this number is increased by one.) At the end of the
measurement period, the NodeB divides the total successfully received data
by the total transmission duration to obtain the average throughput at the
MAC-e/i layer in one HSUPA cell. When a UE performs a softer handover,
the data of this UE is calculated in both the original and target cells.
Issue 01 (2014-04-29)

163
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
Mean Throughput for One HSUPA Cell =

VS.HSUPA.Thruput.ROTAll/
(VS.HSUPA.DataTtiNum x 0.002)
Object
NodeB
Unit/Range
kbit/s
Note
None
3.6.7 PS UL Throughput of RNC

Table 3-119 PS UL Throughput of RNC
Name
PS UL Throughput of RNC
Description
This measurement item provides the Average or Max uplink throughput for
PS services within an RNC.
l Measurement point for Average UL Throughput
The RNC periodically samples the uplink traffic values of the related PS
services in the PS domain. At the end of the measurement period, the RNC
divides the accumulated values by the number of samples to obtain the
mean uplink traffic of all the PS services in the PS domain. The uplink
traffic of all the PS services in the PS domain refers to the traffic obtained
at the RLC layer. The data does not include the RLC head data.
l Measurement point for Max UL Throughput
The RNC periodically samples uplink traffic values of all the related PS
services in the PS domain. At the end of the measurement period, the RNC
calculates the maximum uplink traffic of all the services in the PS domain
within the RNC. The uplink traffic of all the services in the PS domain
refers to the traffic obtained at the RLC layer. The data does not include
the RLC head data.
Associated
Counters
VS.R99PSLoad.ULThruput.RNC
VS.R99PSLoad.MaxULThruput.RNC
VS.HSUPAPSLoad.ULThruput.RNC
VS.HSUPAPSLoad.MaxULThruput.RNC
Object
RNC
Unit/Range
kbit/s
Note
None
3.6.8 PS DL Throughput of RNC

Issue 01 (2014-04-29)

164
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-120 PS DL Throughput of RNC

Name
PS DL Throughput of RNC
Description
These counters provide the Average or Max downlink throughput for PS

services within an RNC.
l Measurement point for Average DL Throughput
The RNC periodically samples the downlink traffic values of the related
PS services in the PS domain. At the end of the measurement period, the
RNC divides the accumulated values by the number of samples to obtain
the mean downlink traffic of all the PS services in the PS domain. The
downlink traffic of all the PS services in the PS domain refers to the traffic
obtained at the RLC layer. The data does not include the RLC head data.
l Measurement point for Max DL Throughput
The RNC periodically samples the downlink traffic values of all the
related PS services in the PS domain. At the end of the measurement
period, the RNC calculates the maximum downlink traffic of all the
services in the PS domain within the RNC. The downlink traffic of all the
services in the PS domain refers to the traffic obtained at the RLC layer.
The data does not include the RLC head data.
Associated
Counters
VS.R99PSLoad.DLThruput.RNC
VS.HSDPAPSLoad.DLThruput.RNC
VS.R99PSLoad.MaxDLThruput.RNC
VS.HSDPAPSLoad.MaxDLThruput.RNC
Object
RNC
Unit/Range
kbit/s
Note
None
3.6.9 MBMS Service Throughput

Table 3-121 MBMS Service Throughput
Issue 01 (2014-04-29)
Name
MBMS Service Throughput
Description
These KPIs are used to check the throughput of MBMS service in a cell.
Associated
Counters
VS.MBMS.PTM.MeanThroughput
Object
CELL
Unit/Range
kbit/s
Note
None
VS.MBMS.PTP.MeanThroughput

165
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.7 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.
3.7.1 CS Equivalent Erlang of RNC

Table 3-122 CS Equivalent Erlang of RNC
Name
CS Equivalent Erlang of RNC
Description
VS.CSLoad.Erlang.Equiv.RNC
This KPI provides the equivalent Erlang values of all the services in the CS
domain in the RNC.
The RNC periodically takes the samples from the equivalent Erlang values
of all the services in the CS domain. At the end of the measurement period,
the RNC divides the accumulated equivalent Erlang values by the number
of samples to obtain the mean equivalent Erlang values of all the services
in the CS domain.
Each time a CS domain service is established, the RNC converts its rate to
the equivalent Erlang, and then increases the equivalent Erlang of the CS
domain in the current RNC.
Each time a CS domain service is released, the RNC converts its rate to the
equivalent Erlang and decreases the equivalent Erlang of the CS domain in
the current RNC.
VS.CSLoad.MaxErlang.Equiv.RNC
This KPI provides the maximum equivalent Erlang values of all the services
in the CS domain within the RNC.
The RNC periodically takes a sample from the equivalent Erlang values of
all the services in the CS domain. At the end of the period, the RNC
calculates the maximum equivalent Erlang of all the services in the CS
domain within the RNC.
Each time a CS domain service is established, the RNC converts its rate to
the equivalent Erlang, and then increases the equivalent Erlang of the CS
domain in the current RNC.
Each time a CS domain service is released, the RNC decreases the
equivalent Erlang of the CS domain in the current RNC.
Issue 01 (2014-04-29)
Associated
Counters
VS.CSLoad.Erlang.Equiv.RNC
Object
RNC
Unit/Range
Erl
Note
None
VS.CSLoad.MaxErlang.Equiv.RNC

166
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.7.2 Number of CS Users

Table 3-123 Number of CS Users
Name
Number of CS Users
Description
These counters provide the number of CS (AMR and VP) users with different
UL and DL rates in cells of the active set.
The related RB number is sampled periodically in cells of the active set. At
the end of the measurement period, the value of each counter is obtained as
follows: dividing the accumulated value of each sampling point by the
number of sampling times.
Associated
Counters
l Cell Counters
(VS.RB.AMR.DL.12.2+
VS.RB.AMR.DL.10.2+
VS.RB.AMR.DL.7.95+
VS.RB.AMR.DL.7.4+
VS.RB.AMR.DL.6.7+
VS.RB.AMR.DL.5.9+
VS.RB.AMR.DL.5.15+
VS.RB.AMR.DL.4.75);
VS.RB.CS.Conv.DL.64
l RNC Counters
(VS.RB.AMR.DL.4.75.RNC+
VS.RB.AMR.DL.5.15.RNC+
VS.RB.AMR.DL.12.2.RNC);
VS.RB.CS.Conv.DL.64.RNC
Object
CELL, RNC
Unit/Range
None
Note
The Unit is average user number, to get Erlang, the counter value should be
multiplied by {SP}/60, where {SP} is the measurement period (unit: minute).
(Only for BSC6900)For a VP service, V1 platform equals to four Erlangs and
V2 platform equals to two Erlangs.
Issue 01 (2014-04-29)

167
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.7.3 Number of PS R99 Users

Table 3-124 Number of PS R99 Users
Name
Number of PS R99 Users
Description
These counters provide the number of PS R99 users with different UL and
DL rates in cells of the active set.
The related RB number is sampled periodically in cells of the active set. At
the end of the measurement period, the value of each counter is obtained as
follows: dividing the accumulated value of each sampling point by the
number of sampling times.
Issue 01 (2014-04-29)

168
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
Cell Level
l UL Counters:
VS.RB.PS.Bkg.UL.8
VS.RB.PS.Bkg.UL.16
VS.RB.PS.Bkg.UL.32
VS.RB.PS.Bkg.UL.64
VS.RB.PS.Bkg.UL.128
VS.RB.PS.Bkg.UL.144
VS.RB.PS.Bkg.UL.256
VS.RB.PS.Bkg.UL.384
VS.RB.PS.Int.UL.8
VS.RB.PS.Int.UL.16
VS.RB.PS.Int.UL.32
VS.RB.PS.Int.UL.64
VS.RB.PS.Int.UL.128
VS.RB.PS.Int.UL.144
VS.RB.PS.Int.UL.256
VS.RB.PS.Int.UL.384
VS.RB.PS.Conv.UL.42.8
VS.RB.PS.Conv.UL.40
VS.RB.PS.Str.UL.8
VS.RB.PS.Str.UL.16
VS.RB.PS.Str.UL.32
VS.RB.PS.Str.UL.64
VS.RB.PS.Str.UL.128
VS.RB.PS.Str.UL.144
VS.RB.PS.Str.UL.256.384
VS.RB.PS.Conv.UL.64
l DL Counters:
VS.RB.PS.Bkg.DL.8
VS.RB.PS.Bkg.DL.16
VS.RB.PS.Bkg.DL.32
VS.RB.PS.Bkg.DL.64
VS.RB.PS.Bkg.DL.128
VS.RB.PS.Bkg.DL.144
VS.RB.PS.Bkg.DL.256
VS.RB.PS.Bkg.DL.384
Issue 01 (2014-04-29)

169
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
VS.RB.PS.Int.DL.8
VS.RB.PS.Int.DL.16
VS.RB.PS.Int.DL.32
VS.RB.PS.Int.DL.64
VS.RB.PS.Int.DL.128
VS.RB.PS.Int.DL.144
VS.RB.PS.Int.DL.256
VS.RB.PS.Int.DL.384
VS.RB.PS.Conv.DL.42.8
VS.RB.PS.Conv.DL.40
VS.RB.PS.Str.DL.8
VS.RB.PS.Str.DL.16
VS.RB.PS.Str.DL.32
VS.RB.PS.Str.DL.64
VS.RB.PS.Str.DL.128
VS.RB.PS.Str.DL.144
VS.RB.PS.Str.DL.256.384
VS.RB.PS.Conv.DL.64
RNC Counters
l UL Counters:
VS.RB.PS.Bkg.UL.8.RNC
VS.RB.PS.Int.UL.8.RNC
VS.RB.PS.Str.UL.8.RNC
Issue 01 (2014-04-29)

170
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
VS.RB.PS.Str.UL.256.384.RNC
VS.RB.PS.Conv.UL.8.RNC
VS.RB.PS.Conv.UL.38.8.RNC
l DL Counters:
VS.RB.PS.Bkg.DL.8.RNC
VS.RB.PS.Int.DL.8.RNC
VS.RB.PS.Str.DL.8.RNC
VS.RB.PS.Str.DL.256.384.RNC
VS.RB.PS.Conv.DL.8.RNC
Issue 01 (2014-04-29)

171
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
VS.RB.PS.Conv.DL.42.8.RNC
Object
CELL, RNC
Unit/Range
None
Note
The Unit is average user number, to get Erlang, should be multiplied by {SP}/
60;
3.7.4 Number of HSDPA Users

Table 3-125 Number of HSDPA Users
Name
Number of HSDPA Users
Description
This KPI provides the mean and maximum number of HSDPA UEs in an
HSDPA serving cell.
The RNC periodically samples the number of HSDPA UEs in the HSDPA
serving cell. At the end of the measurement period, the RNC obtains the mean
and maximum number of HSDPA UEs.
Associated
Counters
VS.HSDPA.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
None
VS.HSDPA.UE.Max.Cell
3.7.5 Number of HSUPA Users

Table 3-126 Number of HSUPA Users
Name
Issue 01 (2014-04-29)
Number of HSUPA Users

172
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
These KPIs provide the mean and maximum number of HSUPA UEs in an
HSUPA serving cell.
The RNC periodically samples the number of HSUPA UEs in the HSUPA
serving cell. At the end of the measurement period, the RNC obtains the mean
and maximum number of HSUPA UEs.
Associated
Counters
VS.HSUPA.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
VS.HSUPA.UE.Max.Cell
3.7.6 Number of E-FACH Users

Table 3-127 Number of E-FACH Users
Name
Mean Number of E-FACH Users
Description
This KPI provides the average number of UEs that are carried on the E-FACH
in the cell
The system periodically samples the UEs that are carried on the EFACH. At
the end of the measurement period, the average number of UEs that are carried
on the E-FACH in the measurement period is obtained by dividing the
accumulated value of sample data in the period by the number of samples.
Associated
Counters
VS.EFACHUEs
Object
CELL
Unit/Range
None
Note
3.7.7 Number of E-RACH Users

Table 3-128 Number of E-RACH Users
Name
Issue 01 (2014-04-29)
Number of E-RACH Users

173
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provide the average numbers of UEs that are carried on the E-RACH
in the cell.
The RNC takes a sample from the number of UEs carried on the E-RACH in
a cell every 5s. At the end of the measurement period, the average number of
UEs that are carried on the E-RACH is obtained by dividing the accumulated
value of sample data in the period by the number of samples.
Associated
Counters
Number of E-RACH Users =
Object
CELL
Unit/Range
None
Note
You are advised to measure this KPI during busy hours.
VS.ERACHUEs
3.7.8 Number of CS Over HSPA Users

Table 3-129 Number of CS Over HSPA Users
Name
Mean Number of CS Over HSPA Users
Description
This KPI provides the average number of CS over HSPA users in the cell.
The system periodically samples the number of CS Over HSPA. At the end
of a statistical period, the system divides the sampling number by the sum at
each sampling point to obtain the average number of CS Over HSPA during
the period.
Associated
Counters
VS.HSPA.UE.Mean.CS.Conv.Cell
Object
CELL
Unit/Range
None
Note
3.7.9 Number of HSDPA 64QAM Users

Table 3-130 Number of HSDPA 64QAM Users
Name
Issue 01 (2014-04-29)
Mean Number of HSDPA 64QAM Users

174
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the average number of HSDPA 64QAM UEs in an HSDPA
cell.
The number of HSDPA 64QAM UEs is sampled periodically in the HSDPA
cells. At the end of the measurement period, the RNC divides the accumulated
time weight value of each sampling point by the sampling period, thus
obtaining the average number of 64QAM UEs in the HSDPA cell.
Associated
Counters
VS.HSDPA.64QAM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
3.7.10 Number of HSDPA MIMO Users

Table 3-131 Number of HSDPA MIMO Users
Name
Mean Number of HSDPA MIMO Users
Description
This KPI provides the average number of HSDPA MIMO UEs in an HSDPA
cell.
The number of HSDPA MIMO UEs is sampled periodically in the HSDPA
obtaining the average number of MIMO UEs in the HSDPA cell.
Associated
Counters
VS.HSDPA.MIMO.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
3.7.11 Number of HSUPA 16QAM users

Table 3-132 Number of HSUPA 16QAM users
Name
Issue 01 (2014-04-29)
Mean Number of HSUPA 16QAM users

175
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
This KPI provides the average number of HSUPA 16QAM UEs in an HSUPA
cell.
The number of HSUPA 16QAM UEs is sampled periodically in the HSUPA
obtaining the average number of 16QAM UEs in the HSUPA cell.
Associated
Counters
VS.HSUPA.16QAM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
3.7.12 Number of HSDPA MIMO64QAM Users

Table 3-133 Number of HSDPA MIMO64QAM Users
Name
Mean Number of HSDPA MIMO64QAM Users
Description
This KPI provides the average number of HSDPA MIMO64QAM UEs in an

HSDPA cell.
The system periodically samples the number of MIMO+64QAM UEs. At the
end of the measurement period, by dividing the accumulated value of sample
data in the period by the number of samples, the average number of MIMO
+64QAM UEs in the measurement period is obtained.
Associated
Counters
VS.HSDPA.MIMO64QAM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
3.7.13 Number of MBMS Users

Table 3-134 Number of MBMS Users
Name
Issue 01 (2014-04-29)
Mean Number of MBMS Users

176
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Description
The previous measurement counter provides the mean number of UEs that
subscribes to MBMS channel in PTP mode in a cell.
If the MBMS channel is in PTP mode, the number of cell_MBMS UEs is
reported when a connected UE orders or releases the program in the cell.
When the MBMS channel switches from PTM to PTP, the number of UEs
that have currently ordered the program in the cell is reported. When the
MBMS channel switches from PTP to PTM, the number of UEs that have
ordered the program in PTP mode is reported as 0.
Associated
Counters
VS.MBMS.PTP.UE.Channel0.Mean.Cell
VS.MBMS.PTM.UE.Channel0.Mean.Cell
Object
CELL
Unit/Range
None
Note
3.7.14 HSDPA RLC Traffic Volume

Table 3-135 HSDPA RLC Traffic Volume
Name
HSDPA RLC Traffic Volume
Description
This KPI provides the total downlink bytes of all the HSDPA MAC-d flows
in a cell.
When the data is transmitted to an HSDPA serving cell, the RNC measures
the number of total bytes sent in the downlink (including data of all types of
services) at the RLC layer for the MAC-d flow in the cell. The RLC header
and the retransmitted data are excluded.
Issue 01 (2014-04-29)
Associated
Counters
VS.HSDPA.MeanChThroughput.TotalBytes
Object
CELL
Unit/Range
byte
Note
None
177
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.7.15 HSUPA RLC Traffic Volume

Table 3-136 HSUPA RLC Traffic Volume
Name
HSUPA RLC Traffic Volume
Description
This counter provides the total uplink bytes of all the HSUPA MAC-d flows
in a cell.
When data is received in HSUPA active cells, the RNC measures the number
of total bytes received in the uplink (including data of different services) at
the RLC layer for the MAC-d flow in the cell. The RLC header and the
retransmitted data are excluded.
Associated
Counters
VS.HSUPA.MeanChThroughput.TotalBytes
Object
CELL
Unit/Range
byte
Note
None
3.7.16 R99 Service UL Traffic Volume

Table 3-137 R99 Service UL Traffic Volume
Name
R99 Service UL Traffic Volume
Description
These KPIs provide the uplink traffic volume of different R99 services in all
cells of the active set.
The UL traffic volume (excluding the RLC header and the retransmitted data)
of each kind of R99 services over the RLC layer are accumulated for all cells
of the active set within SRNC.
Issue 01 (2014-04-29)

178
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
l CS Domain:
(VS.RB.AMR.UL.12.2 x 12200 +
VS.RB.AMR.UL.10.2 x 10200 +
VS.RB.AMR.UL.7.95 x 7950 +
VS.RB.AMR.UL.7.4 x 7400 +
VS.RB.AMR.UL.5.9 x 5900 +
VS.RB.AMR.UL.5.15 x 5150 +
VS.RB.AMR.UL.4.75 x 4750) x {SP} x 60
l PS Domain:
VS.PS.Bkg.UL.8.Traffic
VS.PS.Int.UL.8.Traffic
VS.PS.Str.UL.8.Traffic
VS.PS.Conv.UL.Traffic
Object
CELL
Unit/Range
bit
Note
None
3.7.17 R99 Service DL Traffic Volume

Issue 01 (2014-04-29)

179
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Table 3-138 R99 Service DL Traffic Volume

Name
R99 Service DL Traffic Volume
Description
These KPIs provide the downlink traffic volume of different R99 services in
all cells of the active set.
The DL traffic volume (excluding the RLC header and the retransmitted data)
of each kind of R99 services over the RLC layer are accumulated for all cells
of the active set within SRNC.
Issue 01 (2014-04-29)

180
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Associated
Counters
l CS Domain:
(VS.RB.AMR.DL.12.2 x 12200 +
VS.RB.AMR.DL.10.2 x 10200 +
VS.RB.AMR.DL.7.95 x 7950 +
VS.RB.AMR.DL.7.4 x 7400 +
VS.RB.AMR.DL.5.9 x 5900 +
VS.RB.AMR.DL.5.15 x 5150 +
VS.RB.AMR.DL.4.75 x 4750) x {SP} x 60
VS.CS.Conv.DL.64.Traffic
VS.CS.Str.DL.57.6.Traffic
l PS Domain:
VS.PS.Bkg.DL.8.Traffic
VS.PS.Int.DL.8.Traffic
VS.PS.Str.DL.8.Traffic
VS.PS.Conv.DL.Traffic
Issue 01 (2014-04-29)
Object
CELL
Unit/Range
bit

181
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
Note
None
3.7.18 E-FACH Traffic Volume

Table 3-139 E-FACH Traffic Volume
Name
E-FACH Traffic Volume
Description
This KPI provides the number of downlink MAC PDU bytes sent by the
CRNC on the E-FACH over the Iub interface in a cell.
The measurement is triggered when the CRNC sends downlink data on the
E-FACH over the Iub interface.
Associated
Counters
VS.CRNCIubBytesEFACH.Tx
Object
CELL
Unit/Range
byte
Note
None
3.7.19 E-RACH Traffic Volume

Table 3-140 E-RACH Traffic Volume
Name
E-RACH Traffic Volume
Description
This KPI provides the bytes of UL MAC PDUs (including the signaling data
and the service data, not including the FP header) received by the CRNC over
the ERACH FP on the Iub interface.
The measurement is triggered when the CRNC sends UL data over the
ERACH FP on the Iub interface.
Issue 01 (2014-04-29)
Associated
Counters
E-RACH Traffic Volume =
Object
CELL
Unit/Range
byte
Note
None
VS.CRNCIubBytesERACH.Rx

182
GBSS16.0&RAN16.0
KPI Reference
3 UMTS Service KPI
3.7.20 Average Number of DC-HSDPA Users

Table 3-141 Average Number of DC-HSDPA Users
Name
Average Number of DC-HSDPA Users
Description
This KPI measures the average number of DC-HSDPA users that use this cell
as the primary or secondary carrier cell.
The RNC takes samples of the number of DC-HSDPA users that use a certain
cell as the primary or secondary cell every 5 seconds in a measurement period.
At the end of the measurement period, the RNC obtains the value of this
counter by dividing the accumulated number by the number of sampling
times.
Issue 01 (2014-04-29)
Associated
Counters
VS.HSDPA.DC.PRIM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
VS.HSDPA.DC.SEC.UE.Mean.Cell

183

Gbss16.0&Ran16.0 Kpi Reference (01) (PDF) - en

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Gbss16.0&Ran16.0 Kpi Reference (01) (PDF) - en

Hochgeladen von

Copyright:

Verfügbare Formate

GBSS16.0&RAN16.

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

The mapping single-mode base station

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

Names of files, directories, folders, and users are in

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

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

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

Huawei Proprietary and Confidential

About This Document

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

2.5.2 Traffic Volume on TCH............................................................................................................................................22

Huawei Proprietary and Confidential

2.11.4 Downlink EGPRS TBF Drop Rate..........................................................................................................................43

3 UMTS Service KPI......................................................................................................................60

Huawei Proprietary and Confidential

3.1.18 HSDPA DC RAB Setup Success Ratio...................................................................................................................78

Huawei Proprietary and Confidential

3.4.2 Softer Handover Success Ratio...............................................................................................................................106

Huawei Proprietary and Confidential

3.5.11 PS Call Drop Ratio (PCH & Combined Service)..................................................................................................141

Huawei Proprietary and Confidential

3.7.18 E-FACH Traffic Volume.......................................................................................................................................182

Huawei Proprietary and Confidential

1 Changes in the GBSS&RAN KPI Reference

Changes in the GBSS&RAN KPI Reference

l 3.7.7 Number of E-RACH Users

Huawei Proprietary and Confidential

1 Changes in the GBSS&RAN KPI Reference

l 3.5.10 PS Call Drop Ratio (PCH)

Huawei Proprietary and Confidential

2 GSM Service KPI

GSM Service KPI

About This Chapter

Huawei Proprietary and Confidential

2 GSM Service KPI

2.8 PS Data Throughput KPIs

Huawei Proprietary and Confidential