Singleran Kpi Reference (v900r013c00 - 03) (PDF) - en

SingleRAN
V900R013C00
KPI Reference
Issue 03
Date 2012-02-27
HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 03 (2012-02-27) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i
About This Document
Purpose
The purpose of this document is to specify the SingleRAN 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
BSC6900 V900R013C00
NodeB V100R013
NodeB V200R013
BTS3900 BTS3900V100R002C00SPC011
BTS3000 BTS3000V100R009C00SPC011
BTS3012/BTS3012AE/BTS3012II/
BTS3006C/BTS3002
BTS3000V100R008C11SP03 and later
versions
DBS3900 BTS3000V100R008C11 and later versions
BTS3900/BTS3900A BTS3000V100R008C11 and later versions
BTS3900B/BTS3900E V100R008 and later versions
BTS30/BTS312/BTS3012A V302R007 and later versions
BTS30 and macro BTS312 (EDGE) G3BTS32V302R002C06SP05 and later
versions
BTS30 and macro BTS312 (PCS1900) G3BTS32V302R002C06SP05 and later
versions
Macro BTS3X (AMR) G3BTS32V302R002C06SP05 and later
versions

SingleRAN
KPI Reference About This Document
ii
Intended Audience
This document is intended for:
l Network planners
l Field engineers
l System engineers
Organization
1 Changes in the SingleRAN KPI Reference
This chapter describes the changes made in the SingleRAN 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 a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.

General Conventions
The general conventions that may be found in this document are defined as follows.
SingleRAN
iii
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.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[ ] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }
*
Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]
*
Optional items are grouped in brackets and separated by
vertical bars. Several items or no item can be selected.

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles
are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"
signs. For example, choose File > Create > Folder.

Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
SingleRAN
iv
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.

Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
SingleRAN
v
Contents
About This Document.....................................................................................................................ii
1 Changes in the SingleRAN KPI Reference..............................................................................1
2 GSM Service KPI...........................................................................................................................5
2.1 CS Accessibility KPIs........................................................................................................................................7
2.1.1 Congestion Rate on SDCCH per CELL (Due to Busy).............................................................................7
2.1.2 Call Drop Rate on SDCCH........................................................................................................................7
2.1.3 Assignment Success Rate..........................................................................................................................8
2.1.4 TCH Congestion Rate (Overflow).............................................................................................................8
2.1.5 TCH Seizure Success Rate........................................................................................................................9
2.1.6 Success Rate of Call Establishment.........................................................................................................10
2.1.7 BSS Call Establishment Success Rate.....................................................................................................10
2.1.8 OVERLOAD Rate of Paging..................................................................................................................11
2.2 CS CPU Usage KPI..........................................................................................................................................11
2.2.1 Average CPU Usage of the XPU.............................................................................................................11
2.3 CS Mobility KPIs.............................................................................................................................................12
2.3.1 Handover Success Rate...........................................................................................................................12
2.3.2 Success Rate of Radio Handover.............................................................................................................12
2.3.3 Internal Handover Success Rate per cell.................................................................................................13
2.3.4 Internal Radio Handover Success Rate per cell.......................................................................................14
2.3.5 Success Rate of Incoming External Inter-Cell Handovers......................................................................14
2.3.6 External Incoming Radio Handover Success Rate per Cell....................................................................15
2.3.7 Inter-BSC Outgoing Handover Success Rate..........................................................................................15
2.3.8 Success Rate of External Outgoing Cell Radio Handovers.....................................................................15
2.3.9 Success Rate of Dual-Band Handovers (900/850/810-1800/1900).........................................................16
2.3.10 Success Rate of Dual-Band Handovers (1800/1900-900/850/810).......................................................17
2.4 CS Receive Quality KPIs.................................................................................................................................18
2.4.1 Rx_QUALITY(UPLINK).......................................................................................................................18
2.4.2 Rx_QUALITY(DOWNLINK)................................................................................................................19
2.5 CS Resource Utilization KPIs..........................................................................................................................21
2.5.1 Traffic Volume on SDCCH.....................................................................................................................21
2.5.2 Traffic Volume on TCH..........................................................................................................................21
2.5.3 TCHH Traffic Volume............................................................................................................................22
SingleRAN
KPI Reference Contents
vi
2.5.4 TCH Availability.....................................................................................................................................22
2.5.5 TCH Resource Utilizability.....................................................................................................................23
2.5.6 TRX Usability..........................................................................................................................................23
2.5.7 SDCCH Availability................................................................................................................................24
2.6 CS Retainability KPIs.......................................................................................................................................24
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)........................................................................25
2.6.3 Traffic Call Drop Ratio per cell...............................................................................................................27
2.6.4 Radio Drop Rate of TCH.........................................................................................................................28
2.6.5 Handover Drop Rate of TCH...................................................................................................................28
2.6.6 Call Complete Establishment Success Rate............................................................................................29
2.7 PS Accessibility KPIs.......................................................................................................................................29
2.7.1 Successful Uplink Assignment Rate........................................................................................................29
2.7.2 Successful Downlink Assignment Rate...................................................................................................30
2.7.3 Uplink TBF Establishment Success Rate................................................................................................30
2.7.4 Downlink TBF Establishment Success Rate...........................................................................................31
2.7.5 Uplink EGPRS TBF Establishment Success Rate...................................................................................31
2.7.6 Downlink EGPRS TBF Establishment Success Rate..............................................................................32
2.7.7 Uplink TBF Congestion Rate..................................................................................................................32
2.7.8 Downlink TBF Congestion Rate.............................................................................................................33
2.7.9 Uplink EGPRS TBF Congestion Rate.....................................................................................................33
2.7.10 Downlink EGPRS TBF Congestion Rate..............................................................................................34
2.8 PS Data Throughput KPIs................................................................................................................................34
2.8.1 Upload Data Throughput (kbit/s)............................................................................................................35
2.8.2 Download Data Throughput (kbit/s)........................................................................................................35
2.9 PS delay KPIs...................................................................................................................................................35
2.9.1 PING Delay (ms).....................................................................................................................................36
2.9.2 Mean Delay of PDP Activation (ms).......................................................................................................36
2.9.3 Mean Delay of Attachment (ms).............................................................................................................37
2.9.4 Cell Reselection Time (ms).....................................................................................................................37
2.10 PS Resource Utilization Rate KPIs................................................................................................................38
2.10.1 Uplink PDTCH/PACCH Utilization Rate.............................................................................................38
2.10.2 Downlink PDTCH/PACCH Utilization Rate........................................................................................38
2.10.3 PDCH Occupation Rate.........................................................................................................................39
2.10.4 BSC Reclaimed Dynamic PDCH Rate..................................................................................................39
2.11 PS Retainability KPIs.....................................................................................................................................40
2.11.1 Uplink TBF Drop Rate..........................................................................................................................40
2.11.2 Downlink TBF Drop Rate.....................................................................................................................41
2.11.3 Uplink EGPRS TBF Drop Rate.............................................................................................................41
2.11.4 Downlink EGPRS TBF Drop Rate........................................................................................................42
2.12 PS Transmission Performance KPIs...............................................................................................................42
2.12.1 Retransmission Rate of RLC Uplink GPRS Data Block.......................................................................42
SingleRAN
vii
2.12.2 Retransmission Rate of RLC Downlink GPRS Data Block..................................................................43
2.12.3 Retransmission Rate of Uplink EGPRS RLC Data Block....................................................................43
2.12.4 Retransmission Rate of Downlink EGPRS RLC Data Block................................................................44
2.12.5 Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4.................................................................45
2.12.6 Rate of Downlink GPRS RLC Coding Scheme with CS3/CS4............................................................46
2.12.7 Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9............................................46
2.12.8 Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9.......................................47
2.12.9 Average Throughput of Uplink GPRS RLC per PDCH (kbit/s)...........................................................48
2.12.10 Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)....................................................49
2.12.11 Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s).......................................................49
2.12.12 Average Throughput of Downlink EGPRS RLC per PDCH (kbit/s)..................................................50
2.12.13 Average Throughput of Uplink GPRS RLC per Cell (kbit/s).............................................................52
2.12.14 Average Throughput of Downlink GPRS RLC per Cell (kbit/s)........................................................52
2.12.15 Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)...........................................................53
2.12.16 Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)......................................................54
2.12.17 Average Throughput of Uplink GPRS LLC per User (kbit/s).............................................................55
2.12.18 Average Throughput of Downlink GPRS LLC per User (kbit/s)........................................................55
2.12.19 Average Throughput of Uplink EGPRS LLC per User (kbit/s)..........................................................56
2.12.20 Average Throughput of Downlink EGPRS LLC per User (kbit/s).....................................................56
3 UMTS Service KPI......................................................................................................................58
3.1 Accessibility.....................................................................................................................................................59
3.1.1 IU Paging Success Ratio..........................................................................................................................59
3.1.2 RRC Setup Success Ratio........................................................................................................................59
3.1.3 Radio Access Success Ratio....................................................................................................................62
3.1.4 PS Radio Access Success Ratio...............................................................................................................63
3.1.5 CS Radio Access Success Ratio..............................................................................................................64
3.1.6 AMR RAB Setup Success Ratio.............................................................................................................65
3.1.7 VP RAB Setup Success Ratio.................................................................................................................66
3.1.8 CS RAB Setup Success Ratio..................................................................................................................67
3.1.9 PS RAB Setup Success Ratio..................................................................................................................67
3.1.10 HSDPA RAB Setup Success Ratio.......................................................................................................68
3.1.11 HSUPA RAB Setup Success Ratio.......................................................................................................69
3.1.12 PS E-FACH RAB Setup Success Ratio.................................................................................................70
3.1.13 CS over HSPA RAB Setup Success Ratio............................................................................................70
3.1.14 HSDPA 64QAM RAB Setup Success Ratio.........................................................................................71
3.1.15 HSDPA MIMO RAB Setup Success Ratio...........................................................................................72
3.1.16 HSDPA DC RAB Setup Success Ratio.................................................................................................72
3.1.17 HSDPA MIMO64QAM RAB Setup Success Ratio..............................................................................73
3.1.18 PTM Channel Setup Success Ratio.......................................................................................................74
3.1.19 PTP Channel Setup Success Ratio.........................................................................................................74
3.1.20 RRC Congestion Ratio..........................................................................................................................75
3.1.21 CS RAB Congestion Ratio....................................................................................................................76
SingleRAN
viii
3.1.22 PS RAB Congestion Ratio.....................................................................................................................77
3.2 Availability.......................................................................................................................................................78
3.2.1 Worst Cell Ratio......................................................................................................................................78
3.2.2 Paging Congestion Ratio.........................................................................................................................78
3.2.3 Call Admission Refused Ratio................................................................................................................79
3.2.4 Congested Cell Ratio...............................................................................................................................80
3.2.5 Radio Network Unavailability Ratio.......................................................................................................81
3.2.6 Average CPU Load..................................................................................................................................81
3.2.7 IUB Bandwidth Utilizing Ratio (UL)......................................................................................................82
3.2.8 IUB Bandwidth Utilizing Ratio (DL)......................................................................................................83
3.2.9 Cell Unavailability duration....................................................................................................................84
3.2.10 HSDPA Unavailability duration............................................................................................................85
3.2.11 HSUPA Unavailability duration............................................................................................................85
3.2.12 CE Consumption for a NodeB Cell.......................................................................................................86
3.2.13 Hardware Configured CE for a NodeB.................................................................................................86
3.2.14 Shared Group Configured License CE for a NodeB.............................................................................87
3.2.15 Shared Group License CE Consumption for a NodeB..........................................................................87
3.2.16 License Group Configured CE for a NodeB.........................................................................................88
3.2.17 License Group CE Consumption for a NodeB......................................................................................88
3.2.18 RTWP (Received Total Wideband Power)............................................................................................89
3.2.19 TCP (Transmitted Carrier Power).........................................................................................................89
3.2.20 R99 Code Utilization.............................................................................................................................90
3.3 Coverage...........................................................................................................................................................91
3.3.1 UL Interference Cell Ratio......................................................................................................................91
3.3.2 Soft Handover Overhead.........................................................................................................................91
3.4 Mobility............................................................................................................................................................94
3.4.1 Soft Handover Success Ratio..................................................................................................................94
3.4.2 Softer Handover Success Ratio...............................................................................................................94
3.4.3 AMR Soft Handover Success Ratio........................................................................................................95
3.4.4 CS64 Soft Handover Success Ratio.........................................................................................................96
3.4.5 PS Soft Handover Success Ratio.............................................................................................................96
3.4.6 Intra-frequency Hard Handover Success Ratio.......................................................................................97
3.4.7 Inter-frequency Hard Handover Success Ratio.......................................................................................97
3.4.8 Service Cell Change Success Ratio with SHO (H2H)............................................................................98
3.4.9 H2H Intra-Frequency Hard Handover Success Ratio..............................................................................99
3.4.10 H2H Inter-Frequency Hard Handover Success Ratio..........................................................................100
3.4.11 H2D Inter-frequency Hard Handover Success Ratio...........................................................................101
3.4.12 H2D Channel Switch Success Ratio....................................................................................................102
3.4.13 D2H Channel Switch Success Ratio....................................................................................................103
3.4.14 CS W2G Inter-RAT Handover Out Success Ratio..............................................................................104
3.4.15 PS W2G Inter-RAT Handover Out Success Ratio..............................................................................105
3.4.16 PS G2W Inter-RAT Handover In Success Ratio.................................................................................106
SingleRAN
ix
3.4.17 HSDPA W2G Inter-RAT Handover Out Success Ratio.....................................................................106
3.4.18 SRNC Relocation Success Ratio.........................................................................................................107
3.4.19 TRNC Relocation Success Ratio.........................................................................................................108
3.4.20 E-DCH Soft Handover Success Ratio.................................................................................................109
3.4.21 E-DCH Cell Change Success Ratio with SHO....................................................................................109
3.4.22 E-DCH Cell Change Success Ratio with Inter-HHO..........................................................................111
3.4.23 E2D Channel Switch Success Ratio....................................................................................................111
3.4.24 D2E Channel Switch Success Ratio....................................................................................................112
3.4.25 E2D Handover Success Ratio with Inter HHO...................................................................................113
3.4.26 HSUPA W2G Inter-RAT Handover Out Success Ratio.....................................................................114
3.4.27 MBMS Service Mode Switch Success Ratio......................................................................................114
3.5 Retainability....................................................................................................................................................115
3.5.1 CS Service Drop Ratio..........................................................................................................................115
3.5.2 AMR Call Drop Ratio............................................................................................................................116
3.5.3 VP Call Drop Ratio................................................................................................................................117
3.5.4 AMR Traffic Drop Ratio.......................................................................................................................118
3.5.5 VP Traffic Drop Ratio...........................................................................................................................119
3.5.6 PS Call Drop Ratio................................................................................................................................120
3.5.7 PS Call Drop Ratio (PCH).....................................................................................................................121
3.5.8 PS R99 Call Drop Ratio.........................................................................................................................122
3.5.9 PS R99 Call Drop Ratio (PCH).............................................................................................................123
3.5.10 PS BE Call Drop Ratio........................................................................................................................124
3.5.11 HSDPA Call Drop Ratio......................................................................................................................125
3.5.12 HSDPA Call Drop Ratio (PCH)..........................................................................................................126
3.5.13 HSUPA Call Drop Ratio......................................................................................................................127
3.5.14 HSUPA Call Drop Ratio (PCH)..........................................................................................................129
3.5.15 MBMS Service PTP drop Ratio..........................................................................................................130
3.6 Service Integrity.............................................................................................................................................130
3.6.1 Average UL Throughput for PS R99 Service........................................................................................130
3.6.2 Average DL Throughput for PS R99 Service........................................................................................131
3.6.3 Average UL BLER for CS Service........................................................................................................132
3.6.4 Average UL BLER for PS Service........................................................................................................133
3.6.5 HSDPA Throughput..............................................................................................................................134
3.6.6 HSUPA Throughput..............................................................................................................................135
3.6.7 PS UL Throughput of RNC...................................................................................................................136
3.6.8 PS DL Throughput of RNC...................................................................................................................137
3.6.9 MBMS Service Throughput..................................................................................................................137
3.7 Traffic.............................................................................................................................................................138
3.7.1 CS Equivalent Erlang of RNC...............................................................................................................138
3.7.2 Number of CS Users..............................................................................................................................139
3.7.3 Number of PS R99 Users.......................................................................................................................140
3.7.4 Number of HSDPA Users......................................................................................................................144
SingleRAN
x
3.7.5 Number of HSUPA Users......................................................................................................................144
3.7.6 Number of E-FACH Users....................................................................................................................145
3.7.7 Number of CS Over HSPA Users..........................................................................................................145
3.7.8 Number of HSDPA 64QAM Users.......................................................................................................146
3.7.9 Number of HSDPA MIMO Users.........................................................................................................146
3.7.10 Number of HSUPA 16QAM users......................................................................................................147
3.7.11 Number of HSDPA MIMO64QAM Users..........................................................................................147
3.7.12 Number of MBMS Users.....................................................................................................................147
3.7.13 HSDPA RLC Traffic Volume.............................................................................................................148
3.7.14 HSUPA RLC Traffic Volume.............................................................................................................149
3.7.15 R99 Service UL Traffic Volume.........................................................................................................149
3.7.16 R99 Service DL Traffic Volume.........................................................................................................150
3.7.17 E-FACH Traffic Volume.....................................................................................................................153
SingleRAN
xi
1 Changes in the SingleRAN KPI Reference
This chapter describes the changes made in the SingleRAN KPI Reference.
03 (2012-02-27)
This is the third commercial release of V900R013C00.
l GSM Service KPI
Compared with issue 02 (2011-08-31), this issue does not include any new topics.
Compared with issue 02 (2011-08-31), this issue incorporates the following changes:
Content Description
2.6.2 Call Drop Rate on TCH per Cell
(Excluding Handover)
2.6.1 Call Drop Rate on TCH per Cell
(Including Handover)
Modify another KPI formula that be
used when inter-RAT handovers are
detected.

Compared with issue 02 (2011-08-31), this issue does not exclude any topics.
l UMTS Service KPI
Content Description
3.2.8 IUB Bandwidth Utilizing
Ratio (DL)
3.2.7 IUB Bandwidth Utilizing
Ratio (UL)
Added the scenario where the value of this KPI
is incorrect to Note.

SingleRAN
KPI Reference 1 Changes in the SingleRAN KPI Reference
1
02 (2011-08-31)
This is the second commercial release of V900R013C00.
l GSM Service KPI
Content Description
2.6.2 Call Drop Rate on TCH per
Cell (Excluding Handover)
Add another KPI formula that be used when inter-
RAT handovers are detected.

l UMTS Service KPI
Content Description
3.4.10 H2H Inter-Frequency Hard
Handover Success Ratio
The description of the KPI is optimized.

01 (2011-04-25)
This is the first commercial release of V900R013C00.
Compared with issue Draft A (2011-01-31), this issue does not include any new topics.
Compared with issue Draft A (2011-01-31), this issue does not incorporate any changes.
Compared with issue Draft A (2011-01-31), this issue does not exclude any topics.
Draft A (2011-01-31)
This is the Draft A release of V900R013C00.
l GSM Service KPI
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not include any
new topics.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not incorporate
any changes.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not exclude any
topics.
l UMTS Service KPI
Compared with issue 02 (2010-09-20) of V900R012C01, this issue does not include any
new topics.
SingleRAN
2
Compared with issue 02 (2010-09-20) of V900R012C01, this issue incorporates the
following changes:
Content Description
3.1.2 RRC Setup Success Ratio Correct the counter name
fromRRC.SuccConnEstab.OrgItrCall to
RRC.SuccConnEstab.OrgInterCall
3.5.2 AMR Call Drop Ratio Correct the counter name
VS.RAB.NormRel.AMRWB.Iur to
VS.RAB.NormRel.AMR.Iur
3.7.16 R99 Service DL Traffic
Volume
Correct the counter name VS.PS.Int.DUL.
32.Traffic to VS.PS.Int.DL.32.Traffic
3.5.12 HSDPA Call Drop Ratio
(PCH)
Correct the counter name
VS.RAB.NormRel.HSUPA.Iur to
VS.RAB.NormRel.HSDPA.Iur
3.6.5 HSDPA Throughput Correct the counter name VS.DataOutput.User-
Data to VS.DataOutput.Mean/
(VS.DataTtiRatio.Mean-
VS.HSDPA.InactiveDataTtiRatio.Mean)
3.4.6 Intra-frequency Hard
Handover Success Ratio
VS.HHO.AttIntraFreqOut.InterRNC to
VS.HHO.AttIntraFreqOut.IntraNodeB
3.5.7 PS Call Drop Ratio (PCH) Correct the counter name VS.DCCC.Succ.F2P
to VS.DCCC.F2P.Succ
3.5.9 PS R99 Call Drop Ratio
(PCH)
Correct the counter name VS.PSR99.F2P.Succ
to VS.DCCC.Succ.F2P
3.1.4 PS Radio Access Success
Ratio
RRC.SuccConnEstab.OrgItrCall to
RRC.SuccConnEstab.OrgInterCall

topics.
Compared with issue 01 (2010-04-10) of V900R012C01, this issue includes the following
new topics:
3.1.20 RRC Congestion Ratio
3.1.21 CS RAB Congestion Ratio
3.1.22 PS RAB Congestion Ratio
3.4.6 Intra-frequency Hard Handover Success Ratio
3.4.3 AMR Soft Handover Success Ratio
3.4.4 CS64 Soft Handover Success Ratio
3.4.5 PS Soft Handover Success Ratio
SingleRAN
3
3.2.12 CE Consumption for a NodeB Cell
3.2.13 Hardware Configured CE for a NodeB
3.2.14 Shared Group Configured License CE for a NodeB
3.2.15 Shared Group License CE Consumption for a NodeB
3.2.16 License Group Configured CE for a NodeB
3.2.17 License Group CE Consumption for a NodeB
3.6.4 Average UL BLER for PS Service
3.2.18 RTWP (Received Total Wideband Power)
3.2.19 TCP (Transmitted Carrier Power)
3.2.20 R99 Code Utilization
3.5.1 CS Service Drop Ratio
3.5.10 PS BE Call Drop Ratio
3.5.7 PS Call Drop Ratio (PCH)
3.5.9 PS R99 Call Drop Ratio (PCH)
3.5.12 HSDPA Call Drop Ratio (PCH)
3.5.14 HSUPA Call Drop Ratio (PCH)
3.6.5 HSDPA Throughput
3.6.6 HSUPA Throughput
3.7.3 Number of PS R99 Users
Compared with issue 01 (2010-04-10) of V900R012C01, this issue incorporates the
following changes:
Content Description
3.2.10 HSDPA Unavailability
duration
Correct the counter name VS.Hsdpa.Unavail-
Time to VS.Cell.HSDPA.UnavailTime
3.7.4 Number of HSDPA Users Modify the KPI name from Mean Number of
HSDPA Users to Number of HSDPA Users
New counter VS.HSDPA.UE.Max.Cell was
added in the section Associated Counters
3.7.5 Number of HSUPA Users Modify the KPI name from Mean Number of
HSUPA Users to Number of HSUPA Users
New counter VS.HSUPA.UE.Max.Cell was
added in the section Associated Counters

topics.
SingleRAN
4
2 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 success rate of handovers on the
move. In addition, these KPIs indicate the capability of providing continuous services. A low
handover success rate may lead 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 Utilization KPIs
This chapter describes the CS Resource Utilization KPIs that are used to monitor the load of hot
cells and the network. These KPIs can serve as references for capacity expansion. The traffic
volume KPIs help to obtain the ratio of busy-hour traffic to idle-hour traffic, to evaluate the
utilization of system resources, and to adjust charges. The equipment availability KPIs help to
know the running status of equipment, such as the running status of channels. If these KPIs are
low, equipment and transmission may be faulty.
2.6 CS Retainability KPIs
This chapter describes the CS Retainability KPIs that indicate the ratio of moving MSs to all
MSs, 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 directly affect user satisfaction.
2.8 PS Data Throughput KPIs
SingleRAN
KPI Reference 2 GSM Service KPI
5
This chapter describes the PS Data Throughput Rate KPIs. They involve the performance factors
associated with the terminals, 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 affects user satisfaction.
2.10 PS Resource Utilization Rate KPIs
This chapter describes the PS Resource Utilization Rate KPIs that indicate the utilization of the
network resource and the busy states of services. Thus, 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. Thus, an increase in call drop rate directly
leads to a decrease in 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.
SingleRAN
6
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 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-1 Congestion Rate on SDCCH per CELL (Due to Busy)
KPI Name Congestion Rate on SDCCH per CELL (Due to Busy)
Measurement
Scope
CELL
Formula Congestion Rate on SDCCH per CELL (Due to Busy) = [Failed SDCCH
Seizures due to Busy SDCCH] x{100%}/
[SDCCH Seizure Requests]
RR370 = K3001 x 100%/K3000
Associated
Counters
None
Notes 1. Unit: %
2. This KPI is crucial.

2.1.2 Call Drop Rate on SDCCH
This counter provides the rate of call drops that occur when the SDCCH is occupied.
Table 2-2 Call Drop Rate on SDCCH
KPI Name Call Drop Rate on SDCCH
Measurement
Scope
CELL
Formula Call Drop Rate on SDCCH = [Call Drops on SDCCH] x {100%}/
[Successful SDCCH Seizures]
ZTR104C = CM30 x 100%/K3003
Associated
Counters
None
SingleRAN
7
Notes 1. Unit: %

2.1.3 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-3 Assignment Success Rate
KPI Name Assignment Success Rate
Measurement
Scope
CELL
Formula Assignment Success Rate = [Successful Assignments] x {100%}/
[Assignment Requests]
RCA313 = CA313 x 100%/CA310
Associated
Counters
None
Notes 1. Unit: %

2.1.4 TCH Congestion Rate (Overflow)
This counter provides the rate of the number of failed assignments or handovers due to no idle
TCHs to the number of TCH seizure requests.
Table 2-4 TCH Congestion Rate (Overflow)
KPI Name TCH Congestion Rate (Overflow)
Measurement
Scope
CELL
SingleRAN
8
Formula TCH Congestion Rate (Overflow) = {[Failed TCH Seizures due to Busy
TCH (Signaling Channel)]
+ [Failed TCH Seizures due to Busy TCH (Traffic Channel)]
+ [Failed TCH Seizures in TCH Handovers due to Busy TCH (Traffic
Channel)]} x {100%}/
{[TCH Seizure Requests (Signaling Channel)]
+ [TCH Seizure Requests (Traffic Channel)]
+[TCH Seizure Requests in TCH Handovers (Traffic Channel)]}
K3041 = (K3021+K3011A+K3011B) x100%/(K3020+K3010A
+K3010B)
Associated
Counters
None
Notes 1. Unit: %

2.1.5 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-5 TCH Seizure Success Rate
KPI Name TCH Seizure Success Rate
Measurement
Scope
CELL
Formula TCH Seizure Success Rate = {[Successful TCH Seizures (Signaling
Channel)]
+ [Successful TCH Seizures (Traffic Channel)]
+ [Successful TCH Seizures in TCH handovers (Traffic Channel)]} x
{100%}/
{[TCH Seizure Requests (Signaling Channel)]
+ [TCH Seizure Requests (Traffic Channel)]
+[TCH Seizure Requests in TCH Handovers (Traffic Channel)]}
K3043 = (K3023+K3013A+K3013B) x 100%/(K3020+K3010A
+K3010B)
Associated
Counters
None
Notes Unit: %

SingleRAN
9
2.1.6 Success Rate of Call Establishment
This counter provides the rate of successful calls initiated by the MS from the call setup procedure
to the assignment completion procedure.
Table 2-6 Success Rate of Call Establishment
KPI Name Success Rate of Call Establishment
Measurement
Scope
CELL
Formula Success Rate of Call Establishment = {[Successful Assignments]
-{[Assignment Requests (Signaling Channel) (SDCCH)]
+[Assignment Requests (Signaling Channel) (TCH)]
-[Failed Assignments (Signaling Channel)]
+[Assignment Requests (TCH Assigned Repeatedly over A Interface)]
-[Failed Assignments (TCH Assigned Repeatedly over A Interface)]}} x
{100%}/
{[SDCCH Seizures for Speech Service]
+[TCHF Seizures for Speech Service]
+[TCHH Seizures for Speech Service]}
RA333 = {CA313-{A3100K + A3100A - A312S + CA310A-CA312A}}
x {100%}/{A3039J + A301F + A301HH}
Associated
Counters
None
Notes Unit: %

2.1.7 BSS Call Establishment Success Rate
This counter provides the rate of successful call setup from call origination to successful call
access.
Table 2-7 BSS Call Establishment Success Rate
KPI Name BSS Call Establishment Success Rate
Measurement
Scope
CELL
Formula BSS Call Establishment Success Rate = {[Success Rate of Immediate
Assignments]/{100}}
x {[Assignment Success Rate]/{100}}
x {1 - ([Call Drop Rate on SDCCH])/{100}}
x {100} x 100%
RA333A = (RA303G x RCA313)(1-ZTR104C) x 100%
SingleRAN
10
Associated
Counters
RA333:Success Rate of Call Establishment
Notes Unit: %

2.1.8 OVERLOAD Rate of Paging
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-8 OVERLOAD Rate of Paging
KPI Name OVERLOAD Rate of Paging
Measurement
Scope
CELL
Formula OVERLOAD Rate of Paging = {[MSG CCCH LOAD IND (PCH)
Messages Sent on Abis Interface (CS Service)]
+[MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface (PS
Service)]} x {100}/
{[Delivered Paging Messages for CS Service]
+[Delivered Paging Messages for PS Service]}
RL3188 = (L3188C + L3188D) x 100%/(A330 + A331)
Associated
Counters
None
Notes 1. Unit: %

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
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-9 Average CPU Usage of the XPU
KPI Name Average CPU Usage of the XPU
Measurement
Scope
XPU
SingleRAN
11
Formula None
Associated
Counters
None
Notes 1. Unit: %

2.3 CS Mobility KPIs
This chapter describes the CS Mobility KPIs that indicate the success rate of handovers on the
move. In addition, these KPIs indicate the capability of providing continuous services. A low
handover success rate may lead 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,
thus providing better services for the MSs.
Table 2-10 Handover Success Rate
KPI Name Handover Success Rate
Measurement
Scope
CELL
Formula Handover Success Rate
= {[Number of Successful Outgoing Internal Inter-Cell Handovers]
+ [Successful Outgoing External Inter-Cell Handovers]} x {100%}/
{[Number of Outgoing Internal Inter-Cell Handover Requests]
+ [Outgoing External Inter-Cell Handover Requests]}
RH303 = (CH313 + CH333) x 100%/(CH310 + CH330)
Associated
Counters
RH303A:Success Rate of Radio Handover
Notes 1. Unit: %

2.3.2 Success Rate of Radio Handover
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 excludes target cell
handover failure due to congestion. Thus, Success Rate of Radio Handover is always greater
than or equal to Handover Success Rate.
SingleRAN
12
Table 2-11 Success Rate of Radio Handover
KPI Name Success Rate of Radio Handover
Measurement
Scope
CELL
Formula Success Rate of Radio Handover
= {[Number of Successful Outgoing Internal Inter-Cell Handovers]
+ [Successful Outgoing External Inter-Cell Handovers]} x {100%}/
{[Number of Outgoing Internal Inter-Cell Handover Commands]
+ [Outgoing External Inter-Cell Handover Commands]}
RH303A = (CH313 + CH333) x 100%/(CH311 + CH331)
Associated
Counters
RH303:Handover Success Rate
Notes Unit: %

2.3.3 Internal Handover Success Rate per cell
This counter provides the intra-BSC handover success rate, including the internal intra-cell
handovers and internal inter-cell handovers. It indicates intra-BSC handover, and reduces the
influence of other BSCs.
Table 2-12 Internal Handover Success Rate per cell
KPI Name Internal Handover Success Rate per cell
Measurement
Scope
CELL
Formula Internal Handover Success Rate per cell
= {[Successful Internal Intra-Cell Handovers]
+ [Number of Successful Incoming Internal Inter-Cell Handovers]} x
{100%}/
{[Internal Intra-Cell Handover Requests]
+ [Number of Incoming Internal Inter-Cell Handover Requests]}
RH303B = (CH303 + CH323) x 100%/(CH300 + CH320)
Associated
Counters
RH303C: Intra-BSC Radio Handover Success Rate
Notes Unit: %

SingleRAN
13
2.3.4 Internal Radio Handover Success Rate per cell
Compared with Internal Handover Success Rate per cell, 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 thus reduces failures due to channel congestion.
Table 2-13 Internal Radio Handover Success Rate per cell
KPI Name Internal Radio Handover Success Rate per cell
Measurement
Scope
CELL
Formula Internal Radio Handover Success Rate per cell
= {[Successful Internal Intra-Cell Handovers]
+ [Number of Successful Incoming Internal Inter-Cell Handovers]} x
{100%}/
{[Internal Intra-Cell Handover Commands]
+ [Number of Incoming Internal Inter-Cell Handover Responses]}
RH303C = (CH303 + CH323) x 100%/(CH301 + CH321)
Associated
Counters
RH303B:Intra-BSC Handover Success Rate
Notes Unit: %

2.3.5 Success Rate of Incoming External Inter-Cell Handovers
This counter provides the success rate of incoming inter-BSC handovers. It indicates the inter-
BSC handover interaction.
Table 2-14 Success Rate of Incoming External Inter-Cell Handovers
KPI Name Success Rate of Incoming External Inter-Cell Handovers
Measurement
Scope
CELL
Formula Success Rate of Incoming External Inter-Cell Handovers
= [Successful Incoming External Inter-Cell Handovers] x {100%}/
[Incoming External Inter-Cell Handover Requests]
TH343 = CH343 x 100%/CH340
Associated
Counters
RH303D: Success Rate of Incoming External Inter-Cell Radio Handovers
Notes Unit: %

SingleRAN
14
2.3.6 External Incoming Radio Handover Success Rate per Cell
This counter provides the success rate of incoming inter-BSC handovers on the Um interface.
It indicates the inter-BSC handover interaction.
Table 2-15 External Incoming Radio Handover Success Rate per Cell
KPI Name External Incoming Radio Handover Success Rate per Cell
Measurement
Scope
CELL
Formula External Incoming Radio Handover Success Rate per Cell
= [Successful Incoming External Inter-Cell Handovers] x {100%}/
[Incoming External Inter-Cell Handover Responses]
RH303D = CH343 x 100%/CH341
Associated
Counters
TH343: Success Rate of Incoming External Inter-Cell Handovers
Notes Unit: %

2.3.7 Inter-BSC Outgoing Handover Success Rate
This counter provides the success rate of outgoing inter-BSC handovers. It indicates the inter-
BSC handover interaction.
Table 2-16 Inter-BSC Outgoing Handover Success Rate
KPI Name Inter-BSC Outgoing Handover Success Rate
Measurement
Scope
CELL
Formula Success Rate of Outgoing External Inter-Cell Handovers
= [Successful Outgoing External Inter-Cell Handovers] x {100%}/
[Outgoing External Inter-Cell Handover Requests]
TH333 = CH333 x 100%/CH330
Associated
Counters
RH303E: Success Rate of External Outgoing Cell Radio Handovers
Notes Unit: %

2.3.8 Success Rate of External Outgoing Cell Radio Handovers
This counter provides the success rate of outgoing inter-BSC handovers on the Um interface. It
indicates the inter-BSC handover interaction.
SingleRAN
15
Table 2-17 Success Rate of External Outgoing Cell Radio Handovers
KPI Name Success Rate of External Outgoing Cell Radio Handovers
Measurement
Scope
CELL
Formula Success Rate of External Outgoing Cell Radio Handovers
= [Successful Outgoing External Inter-Cell Handovers] x {100%}/
[Outgoing External Inter-Cell Handover Commands]
RH303E = CH333 x 100%/CH331
Associated
Counters
TH333: Success Rate of Outgoing External Inter-Cell Handovers
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-18 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
SingleRAN
16
Formula Success Rate of Dual-Band Handovers (900/850/810-1800/1900)
= {[Incoming Internal Inter-Cell Handover Requests
(900/850/810-1800/1900)]
+ [Incoming External Inter-Cell Handover Requests
(900/850/810-1800/1900)]
+ [Outgoing External Inter-Cell Handover Requests
(900/850/810-1800/1900)]
- {[Failed Incoming Internal Inter-Cell Handovers
(900/850/810-1800/1900)]
+ [Failed Incoming External Inter-Cell Handovers
(900/850/810-1800/1900)]
+ [Failed Outgoing External Inter-Cell Handovers
(900/850/810-1800/1900)]}} x {100%}/
{[Incoming Internal Inter-Cell Handover Requests
(900/850/810-1800/1900)]
(900/850/810-1800/1900)]
(900/850/810-1800/1900)]}
RH303F = {(RH3031G + RH3033G + RH3035G) - (RH3031F +
RH3033F + RH3035F)} x 100%/(RH3031G + RH3033G + RH3035G)
Associated
Counters
RH303G: Success Rate of Dual-Band Handovers
(1800/1900-900/850/810)
Notes Unit: %

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-19 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
SingleRAN
17
Formula Success Rate of Dual-Band Handovers (1800/1900-900/850/810)
= {[Incoming Internal Inter-Cell Handover Requests
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]
- {[Failed Incoming Internal Inter-Cell Handovers
(1800/1900-900/850/810)]
+ [Failed Incoming External Inter-Cell Handovers
(1800/1900-900/850/810)]
+ [Failed Outgoing External Inter-Cell Handovers
(1800/1900-900/850/810)]}} x {100%}/
{[Incoming Internal Inter-Cell Handover Requests
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]
(1800/1900-900/850/810)]}
RH303G = {(RH3032G + RH3034G + RH3036G) - (RH3032F +
RH3034F + RH3036F)} x 100%/(RH3032G + RH3034G + RH3036G)
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.
2.4.1 Rx_QUALITY(UPLINK)
This counter provides the ratio of uplink half/full rate in the mean receive quality ranks 0 to 4.
Table 2-20 Rx_QUALITY(UPLINK)
KPI Name Rx_QUALITY(UPLINK)
Measurement
Scope
TRX
SingleRAN
18
Formula Rx_QUALITY(UPLINK)
={[Number of MRs on Uplink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Uplink TCHF (Mean Receive Quality Rank 1)]
+ [Number of MRs on Uplink TCHH (Mean Rank of Receive Quality 0)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 1)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 4)]}x
{100%}/
{[Number of MRs on Uplink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Uplink TCHH (Mean Rank of Receive Quality 0)]
+ [Number of MRs on Uplink TCHH (Mean Receive Quality Rank 7)]}
(CS410A + CS411A + CS412A + CS413A + CS414A + CS410C +
CS411C + CS412C + CS413C + CS414C) x{100%}/
(CS410A + CS411A + CS412A + CS413A + CS414A + CS415A +
CS416A + CS417A + CS410C + CS411C + CS412C + CS413C + CS414C
+ CS415C + CS416C + CS417C)
Associated
Counters
None
Notes None

2.4.2 Rx_QUALITY(DOWNLINK)
This counter provides the ratio of downlink half/full rate in the mean receive quality ranks 0 to
4.
SingleRAN
19
Table 2-21 Rx_QUALITY(DOWNLINK)
KPI Name Rx_QUALITY(DOWNLINK)
Measurement
Scope
TRX
Formula Rx_QUALITY(DOWNLINK)
= {[Number of MRs on Downlink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHF (Mean Receive Quality Rank 1)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 4)]}
x{100%}/
{[Number of MRs on Downlink TCHF (Mean Receive Quality Rank 0)]
+ [Number of MRs on Downlink TCHH (Mean Receive Quality Rank 7)]}
(CS410B + CS411B + CS412B + CS413B + CS414B + CS410D +
CS411D + CS412D + CS413D + CS414D) x {100%}/
(CS410B + CS411B + CS412B + CS413B + CS414B + CS415B +
CS416B + CS417B + CS410D + CS411D + CS412D + CS413D + CS414D
+ CS415D + CS416D + CS417D)
Associated
Counters
None
SingleRAN
20
Notes None

2.5 CS Resource Utilization KPIs
This chapter describes the CS Resource Utilization KPIs that are used to monitor the load of hot
cells and the network. These KPIs can serve as references for capacity expansion. The traffic
volume KPIs help to obtain the ratio of busy-hour traffic to idle-hour traffic, to evaluate the
utilization of system resources, and to adjust charges. The equipment availability KPIs help to
know the running status of equipment, such as the running status of channels. If these KPIs are
low, equipment and transmission may be 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-22 Traffic Volume on SDCCH
KPI Name Traffic Volume on SDCCH
Measurement
Scope
CELL
Formula Traffic Volume on SDCCH = [Traffic Volume of Signaling Channels
(SDCCH)]
K3004 = R3550M
Associated
Counters
None
Notes 1. This KPI is crucial.

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-23 Traffic Volume on TCH
KPI Name Traffic Volume on TCH
Measurement
Scope
CELL
SingleRAN
21
Formula Traffic Volume on TCH
= [Mean Number of Busy TCHs (TCHF) (900/850/810 band)]
+ [Mean Number of Busy TCHs (TCHF) (1800/1900 Band)]
+ [Mean Number of Busy TCHs (TCHH) (900/850/810 band)]
+ [Mean Number of Busy TCHs (TCHH) (1800/1900 Band)]
K3014 = AR3551A + AR3551B + AR3552A + AR3552B
Associated
Counters
None

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-24 TCHH Traffic Volume
KPI Name TCHH Traffic Volume
Measurement
Scope
CELL
Formula TCHH Traffic Volume
= [Mean Number of Busy TCHs (TCHH) (900/850/810 band)]
+ [Mean Number of Busy TCHs (TCHH) (1800/1900 Band)]
K3034 = AR3552A + AR3552B
Associated
Counters
None
Notes None

2.5.4 TCH Availability
This counter provides the rate of available TCHs to configured TCHs.
Table 2-25 TCH Availability
KPI Name TCH Availability
Measurement
Scope
CELL
SingleRAN
22
Formula TCH Availability
= {[Mean Number of Available Channels (TCHF) (900/850/810 band)]
+ [Mean Number of Available Channels (TCHF) (1800/1900 Band)]
+ [Mean Number of Available Channels (TCHH) (900/850/810 band)]
+ [Mean Number of Available Channels (TCHH) (1800/1900 Band)]} x
{100%}/
{[Mean Number of Dynamically Configured Channels (TCHF)
(900/850/810 band)]
+ [Mean Number of Dynamically Configured Channels (TCHF)
(1800/1900 Band)]
+ [Mean Number of Dynamically Configured Channels (TCHH)
(900/850/810 band)]
+ [Mean Number of Dynamically Configured Channels (TCHH)
(1800/1900 Band)]}
RR307 = (AR3027A + AR3027B + AR3028A + AR3028B) x 100%/
(AR3017A + AR3017B + AR3018A + AR3018B)
Associated
Counters
None
Notes Unit: %

2.5.5 TCH Resource Utilizability
This counter provides the rate of the actual traffic volume to the theoretical traffic volume.
Table 2-26 TCH Resource Utilizability
KPI Name TCH Resource Utilizability
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

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

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

2.6 CS Retainability KPIs
This chapter describes the CS Retainability KPIs that indicate the ratio of moving MSs to all
MSs, the moving frequency. In addition, these KPIs indicate the capability of providing
continuous services. A low success rate leads to low user satisfaction.
SingleRAN
24
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-29 Call Drop Rate on TCH per Cell (Including Handover)
KPI Name Call Drop Rate on TCH per Cell (Including Handover)
Measurement
Scope
CELL
Formula Call Drop Rate on TCH per Cell (Including Handover) = [Call Drops on
Traffic Channel] x {100%}/
{[Successful TCH Seizures (Signaling Channel)]
+ [Successful TCH Seizures in TCH handovers (Traffic Channel)]}
ZTR304 = CM33 x 100%/(K3023+K3013A+K3013B)
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-30 Call Drop Rate on TCH per Cell (Excluding Handover)
KPI Name Call Drop Rate on TCH per Cell (Excluding Handover)
Measurement
Scope
CELL
SingleRAN
25
Formula Call Drop Rate on TCH per Cell (Excluding Handover)
= [Call Drops on Traffic Channel] x {100%}/
{[Successful TCH Seizures (Traffic Channel)]
+[Number of Incoming Internal Inter-Cell Handover Requests (TCH)]
-[Number of Failed Incoming Internal Inter-Cell Handovers(TCH)]
+[Number of Incoming External Inter-Cell Handover Requests(TCH)]
-[Number of Failed Incoming External Inter-Cell Handovers(TCH)]
- ([Number of Outgoing Internal Inter-Cell Handover Requests(TCH)]
-[Number of Failed Outgoing Internal Inter-Cell Handovers(TCH)]
+[Number of Outgoing External Inter-Cell Handover Requests(TCH)]
-[Number of Failed Outgoing External Inter-Cell Handovers(TCH)])}
ZTR304A = CM33 x 100%/{K3013A + CH3209A - CH3229A +
CH3409A - CH3429A - (CH3109A - CH3129A + CH3309A - CH3329A)}
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 + Number of
times the outgoing inter-RAT inter-cell handover timer expires) * {100}/
(Y + Number of successful incoming inter-RAT inter-cell handovers -
Number of successful outgoing inter-RAT inter-cell handovers)
Notes:
(1) If an MS is handed over between a GSM cell and a UMTS cell,
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)])};
Number of successful outgoing inter-RAT inter-cell handovers =
{([H3507: Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF)] +
SingleRAN
26
[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)])};
(2) If an MS is handed over between a GSM cell and a TDD cell,
Number of times the outgoing inter-RAT inter-cell handover timer expires
= [H352C1: Failed Outgoing Inter-RAT Inter-Cell Handovers (T8
Expired) (TDD)];
Number of successful incoming inter-RAT inter-cell handovers =
{[H36091: Incoming Inter-RAT Inter-Cell Handover Requests (TCH)
(TDD)] - ([H36271: Failed Incoming Inter-RAT Inter-Cell Handovers
(TCHF) (TDD)] + [H36281: Failed Incoming Inter-RAT Inter-Cell
Handovers (TCHH) (TDD)])};
Number of successful outgoing inter-RAT inter-cell handovers =
{([H35071: Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF)
(TDD)] + [H35081: Outgoing Inter-RAT Inter-Cell Handover Requests
(TCHH) (TDD)]) - ([H35171: Outgoing Inter-RAT Inter-Cell Handover
Commands (TCHF) (TDD)] + [H35181: Outgoing Inter-RAT Inter-Cell
Handover Commands (TCHH) (TDD)])};
Associated
Counters
ZTR304:Call Drop Rate on TCH per Cell (Including Handover)
Notes 1. Unit: %

2.6.3 Traffic Call Drop Ratio per cell
This counter provides the ratio of traffic volume to call drops. It indicates the average interval
at which a call drop occurs in a cell.
Table 2-31 Traffic Call Drop Ratio per cell
KPI Name Traffic Call Drop Ratio per cell
Measurement
Scope
CELL
Formula Traffic Call Drop Ratio per cell = [Traffic Volume on TCHs] x {60} x
100%/
[Call Drops on Traffic Channel]
ZTR308 = 60 x K3014 x 100%/CM33
Associated
Counters
ZTR304A:Call Drop Rate on TCH per Cell (Excluding Handover)
Notes 1. Unit: %

SingleRAN
27
2.6.4 Radio Drop Rate of TCH
This counter provides the rate of call drops due to the Um interface to total successful TCH
seizures.
Table 2-32 Radio Drop Rate of TCH
KPI Name Radio Drop Rate of TCH
Measurement
Scope
CELL
Formula Radio Drop Rate of TCH = {[Call Drops on Radio Interface in Stable State
(Traffic Channel)]
+ [Call Drops on Radio Interface in Stable State (Signaling Channel)
(TCH)]} x {100%} /
RM333 = (CM330 + CM3606) x 100%/(K3023+K3013A+K3013B)
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-33 Handover Drop Rate of TCH
KPI Name Handover Drop Rate of TCH
Measurement
Scope
CELL
Formula Handover Drop Rate of TCH = {[Call Drops on Signal Channel (TCH)]
+ [Call Drops in TCH Handovers (Traffic Channel)]} x {100%}/
RH333 = (RH3331+K3012B) x 100%/(K3023+K3013A+K3013B)
Associated
Counters
None
Notes Unit: %

SingleRAN
28
2.6.6 Call Complete Establishment Success Rate
This counter provides the rate of call complete setup from call origination to successful speech
disconnection.
Table 2-34 Call Complete Establishment Success Rate
KPI Name Call Complete Establishment Success Rate
Measurement
Scope
CELL
Formula Call Complete Establishment Success Rate = [BSS Call Establishment
Success Rate] x {1 - [Call Drop Rate on TCH per Cell (Excluding
Handover)] x 100%
RA333B = RA333A x (1-ZTR304A) 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 directly affect user satisfaction.
2.7.1 Successful Uplink Assignment Rate
This counter provides the uplink assignment success rate during uplink assignment procedure.
Table 2-35 Successful Uplink Assignment Rate
KPI Name Successful Uplink Assignment Rate
Measurement
Scope
CELL
Formula Successful Uplink Assignment Rate
= [Number of Successful Uplink Assignments] x {100%}/
[Number of Uplink Assignments]
A9513 = A9502 x 100%/A9501
Associated
Counters
None
Notes 1. Unit: %

SingleRAN
29
2.7.2 Successful Downlink Assignment Rate
This counter provides the downlink assignment success rate during downlink assignment
procedure.
Table 2-36 Successful Downlink Assignment Rate
KPI Name Successful Downlink Assignment Rate
Measurement
Scope
CELL
Formula Successful Downlink Assignment Rate
= [Number of Successful Downlink Assignments] x {100%}/
[Number of Downlink Assignments]
A9514 = A9508 x 100% /A9507
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-37 Uplink TBF Establishment Success Rate
KPI Name Uplink TBF Establishment Success Rate
Measurement
Scope
CELL
Formula Uplink TBF Establishment Success Rate
={[Number of Successful Uplink GPRS TBF Establishments]
+[Number of Successful Uplink EGPRS TBF Establishments]} x {100%}/
{[Number of Uplink GPRS TBF Establishment Attempts]
+[Number of Uplink EGPRS TBF Establishment Attempts]}
(A9002 + A9202) x 100%/(A9001 + A9201)
Associated
Counters
None
Notes 1. Unit: %

SingleRAN
30
2.7.4 Downlink TBF Establishment Success Rate
This counter provides the downlink TBF establishment success rate during downlink TBF
establishment procedure. The value of this counter is impacted by the bad radio environment
and insufficient resources.
Table 2-38 Downlink TBF Establishment Success Rate
KPI Name Downlink TBF Establishment Success Rate
Measurement
Scope
CELL
Formula Downlink TBF Establishment Success Rate
={[Number of Successful Downlink GPRS TBF Establishments]
+[Number of Successful Downlink EGPRS TBF Establishments]} x
{100%}/
{[Number of Downlink GPRS TBF Establishment Attempts]
+[Number of Downlink EGPRS TBF Establishment Attempts]}
(A9102 + A9302) x 100%/(A9101 + A9301)
Associated
Counters
None
Notes 1. Unit: %

2.7.5 Uplink EGPRS TBF Establishment Success Rate
This counter provides the rate of successful 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-39 Uplink EGPRS TBF Establishment Success Rate
KPI Name Uplink EGPRS TBF Establishment Success Rate
Measurement
Scope
CELL
Formula Uplink EGPRS TBF Establishment Success Rate
= [Number of Successful Uplink EGPRS TBF Establishments] x {100%}/
[Number of Uplink EGPRS TBF Establishment Attempts]
A9202 x 100%/A9201
Associated
Counters
None
SingleRAN
31
Notes 1. Unit: %

2.7.6 Downlink EGPRS TBF Establishment Success Rate
This counter provides the rate of successful downlink EGPRS TBF establishments during
downlink EGPRS TBF establishment procedure. The value of this counter is impacted by the
bad radio environment and insufficient resources.
Table 2-40 Downlink EGPRS TBF Establishment Success Rate
KPI Name Downlink EGPRS TBF Establishment Success Rate
Measurement
Scope
CELL
Formula Downlink EGPRS TBF Establishment Success Rate
= [Number of Successful Downlink EGPRS TBF Establishments] x
{100%}/
[Number of Downlink EGPRS TBF Establishment Attempts]
A9302 x 100%/A9301
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-41 Uplink TBF Congestion Rate
KPI Name Uplink TBF Congestion Rate
Measurement
Scope
CELL
SingleRAN
32
Formula Uplink TBF Congestion Rate
={[Number of Failed Uplink GPRS TBF Establishments due to No
Channel]
+[Number of Failed Uplink EGPRS TBF Establishments due to No
Channel]} x {100%}/
{[Number of Uplink GPRS TBF Establishment Attempts]
+[Number of Uplink EGPRS TBF Establishment Attempts]}
(A9003 + A9203) x 100%/(A9001 + A9201)
Associated
Counters
None
Notes 1. Unit: %

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-42 Downlink TBF Congestion Rate
KPI Name Downlink TBF Congestion Rate
Measurement
Scope
CELL
Formula Downlink TBF Congestion Rate
={[Number of Failed Downlink GPRS TBF Establishments due to No
Channel]
+[Number of Failed Downlink EGPRS TBF Establishments due to No
Channel]} x {100%}/
{[Number of Downlink GPRS TBF Establishment Attempts]
+[Number of Downlink EGPRS TBF Establishment Attempts]}
(A9103 + A9303) x 100%/(A9101 + A9301)
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.
SingleRAN
33
Table 2-43 Uplink EGPRS TBF Congestion Rate
KPI Name Uplink EGPRS TBF Congestion Rate
Measurement
Scope
CELL
Formula Uplink EGPRS TBF Congestion Rate
=[Number of Failed Uplink EGPRS TBF Establishments due to No
Channel] x {100%}/
[Number of Uplink EGPRS TBF Establishment Attempts]
A9203 x 100%/A9201
Associated
Counters
None
Notes 1. Unit: %

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-44 Downlink EGPRS TBF Congestion Rate
KPI Name Downlink EGPRS TBF Congestion Rate
Measurement
Scope
CELL
Formula Downlink EGPRS TBF Congestion Rate
=[Number of Failed Downlink EGPRS TBF Establishments due to No
Channel] x {100%}/
[Number of Downlink EGPRS TBF Establishment Attempts]
A9303 x 100%/A9301
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 terminals, the radio access network, and the core network. Now, the main
performance problem is concerned with the radio access network. Therefore, these KPIs indicate
SingleRAN
34
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-45 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.
Associated
Counters
None

2.8.2 Download Data Throughput (kbit/s)
This counter provides the delay performance of the download service.
Table 2-46 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

2.9 PS delay KPIs
This chapter describes the PS Delay KPIs that indicate the service response speed of the network.
Long delay affects user satisfaction.
SingleRAN
35
2.9.1 PING Delay (ms)
This counter provides the delay performance of the ping service.
Table 2-47 PING Delay (ms)
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.
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-48 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.

SingleRAN
36
2.9.3 Mean Delay of Attachment (ms)
This counter provides the delay performance during attachment.
Table 2-49 Mean Delay of Attachment (ms)
KPI Name Mean Delay of Attachment (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.
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 Cell Reselection Time (ms)
This counter provides the delay performance of MS service disruption during cell reselection.
Table 2-50 Cell Reselection Time (ms)
KPI Name Cell Reselection Time (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
SingleRAN
37
Notes 1. The upload test is different from the download test. This counter is
appraised in the mode of download test:
2. The Cell Reselection Time 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 Cell Reselection Time 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 Utilization Rate KPIs
This chapter describes the PS Resource Utilization Rate KPIs that indicate the utilization of the
network resource and the busy states of services. Thus, these KPIs can be used to guide network
expansion.
2.10.1 Uplink PDTCH/PACCH Utilization Rate
This counter provides the utilization of uplink PDTCHs or PACCHs.
Table 2-51 Uplink PDTCH/PACCH Utilization Rate
KPI Name Uplink PDTCH/PACCH Utilization Rate
Measurement
Scope
CELL
Formula Uplink PDTCH/PACCH Utilization Rate
=[Number of RLC Data Blocks Received on Uplink PDTCH/PACCH] x
{100%}/
[Total Number of Uplink PDTCH/PACCH Blocks]
R9204 x 100%/R9206
Associated
Counters
None
Notes Unit: %

2.10.2 Downlink PDTCH/PACCH Utilization Rate
This counter provides the utilization of downlink PDTCHs or PACCHs.
SingleRAN
38
Table 2-52 Downlink PDTCH/PACCH Utilization Rate
KPI Name Downlink PDTCH/PACCH Utilization Rate
Measurement
Scope
CELL
Formula Downlink PDTCH/PACCH Utilization Rate
=[Number of RLC Data Blocks Sent on Downlink PDTCH/PACCH] x
{100%}/
[Total Number of Downlink PDTCH/PACCH Blocks]
R9205 x 100%/R9207
Associated
Counters
None
Notes Unit: %

2.10.3 PDCH Occupation Rate
This counter provides the utilization of PDCHs.
Table 2-53 PDCH Occupation Rate
KPI Name PDCH Occupation Rate
Measurement
Scope
CELL
Formula PDCH Occupation Rate
=[Average Number of Occupied PDCHs] x {100%}/
[Average Number of Available PDCHs]
AR9311 x 100%/AR9303
Associated
Counters
None
Notes Unit: %

2.10.4 BSC Reclaimed Dynamic PDCH Rate
This counter provides the rate of the PDCH (bearing the PS service) preempted by the CS service.
Table 2-54 BSC Reclaimed Dynamic PDCH Rate
KPI Name BSC Reclaimed Dynamic PDCH Rate
Measurement
Scope
CELL
SingleRAN
39
Formula BSC Reclaimed Dynamic PDCH Rate
=[Number of Reclaimed Busy Dynamic PDCHs] x {100%}/
[Number of Reclaimed Dynamic PDCHs]
R9344 x 100%/R9343
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. Thus, an increase in call drop rate directly
leads to a decrease in 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.
Table 2-55 Uplink TBF Drop Rate
KPI Name Uplink TBF Drop Rate
Measurement
Scope
CELL
Formula Uplink TBF Drop Rate
={[Number of Uplink GPRS TBF Abnormal Releases due to N3101
Overflow (MS No Response)]
+[Number of Uplink GPRS TBF Abnormal Releases due to N3103
+[Number of Uplink EGPRS TBF Abnormal Releases due to N3101
Overflow (MS No Response)]} x {100%}/
{[Number of Successful Uplink GPRS TBF Establishments]
+[Number of Successful Uplink EGPRS TBF Establishments]}
(A9006 + A9007 + A9206 + A9207) x 100%/(A9002 + A9202)
Associated
Counters
None
Notes 1. Unit: %

SingleRAN
40
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-56 Downlink TBF Drop Rate
KPI Name Downlink TBF Drop Rate
Measurement
Scope
CELL
Formula Downlink TBF Drop Rate
={[Number of Downlink GPRS Intermit Transfers]
+[Number of Downlink EGPRS Intermit Transfers]} x {100%}/
{[Number of Successful Downlink GPRS TBF Establishments]
+[Number of Successful Downlink EGPRS TBF Establishments]}
(A9118 + A9318) x 100%/(A9102 + A9302)
Associated
Counters
None
Notes 1. Unit: %

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-57 Uplink EGPRS TBF Drop Rate
KPI Name Uplink EGPRS TBF Drop Rate
Measurement
Scope
CELL
Formula Uplink EGPRS TBF Drop Rate
={[Number of Uplink EGPRS TBF Abnormal Releases due to N3101
Overflow (MS No Response)]} x {100%}/
[Number of Successful Uplink EGPRS TBF Establishments]
(A9206 + A9207) x 100%/A9202
Associated
Counters
None
SingleRAN
41
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-58 Downlink EGPRS TBF Drop Rate
KPI Name Downlink EGPRS TBF Drop Rate
Measurement
Scope
CELL
Formula Downlink EGPRS TBF Drop Rate
=[Number of Downlink EGPRS Intermit Transfers] x {100%}/
[Number of Successful Downlink EGPRS TBF Establishments]
A9318 x 100%/A9302
Associated
Counters
None
Notes 1. Unit: %

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 RLC Uplink GPRS Data Block
This counter provides the quality of uplink GPRS RLC data transmission.
Table 2-59 Retransmission Rate of RLC Uplink GPRS Data Block
KPI Name Retransmission Rate of RLC Uplink GPRS Data Block
Measurement
Scope
CELL
SingleRAN
42
Formula Retransmission Rate of Uplink GPRS RLC Data Blocks
=([Total Number of Uplink GPRS RLC Data Blocks]
- [Number of Valid Uplink RLC Data Blocks Using CS1]
- [Number of Valid Uplink RLC Data Blocks Using CS4]) x {100%}/
[Total Number of Uplink GPRS RLC Data Blocks]
{L9001 - (L9006 + L9007 + L9008 + L9009)} x 100%/L9001
Associated
Counters
None
Notes 1. Unit: %

2.12.2 Retransmission Rate of RLC Downlink GPRS Data Block
This counter provides the quality of downlink GPRS RLC data transmission.
Table 2-60 Retransmission Rate of RLC Downlink GPRS Data Block
KPI Name Retransmission Rate of RLC Downlink GPRS Data Block
Measurement
Scope
CELL
Formula Retransmission Rate of Downlink GPRS RLC Data Blocks
=([Total Number of Downlink GPRS RLC Data Blocks]
- [Total Number of Valid Downlink RLC Data Blocks Using CS1]
- [Total Number of Valid Downlink RLC Data Blocks Using CS4]) x
{100%}/
[Total Number of Downlink GPRS RLC Data Blocks]
{L9101 - (L9106 + L9107 + L9108 + L9109)} x 100%/L9101
Associated
Counters
None
Notes 1. Unit: %

2.12.3 Retransmission Rate of Uplink EGPRS RLC Data Block
This counter provides the quality of uplink EGPRS RLC data transmission.
SingleRAN
43
Table 2-61 Retransmission Rate of Uplink EGPRS RLC Data Block
KPI Name Retransmission Rate of Uplink EGPRS RLC Data Block
Measurement
Scope
CELL
Formula Retransmission Rate of Uplink EGPRS RLC Data Blocks
= ([Total Number of Uplink EGPRS RLC Data Blocks]
- [Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks]
- [Total Number of Valid Uplink EGPRS MCS9 RLC Data Blocks]) x
{100%}/
[Total Number of Uplink EGPRS RLC Data Blocks]
{L9201 - (L9211 + L9212 + L9213 + L9214 + L9215 + L9216 + L9217
+ L9218 + L9219)} x 100%/L9201
Associated
Counters
None
Notes 1. Unit: %

2.12.4 Retransmission Rate of Downlink EGPRS RLC Data Block
This counter provides the quality of downlink EGPRS RLC data transmission.
Table 2-62 Retransmission Rate of Downlink EGPRS RLC Data Block
KPI Name Retransmission Rate of Downlink EGPRS RLC Data Block
Measurement
Scope
CELL
SingleRAN
44
Formula Retransmission Rate of Downlink EGPRS RLC Data Blocks
= ([Total Number of Downlink EGPRS RLC Data Blocks]
- [Total Number of Valid Downlink EGPRS MCS1 RLC Data Blocks]
- [Total Number of Valid Downlink EGPRS MCS9 RLC Data Blocks]) x
{100%}/
[Total Number of Downlink EGPRS RLC Data Blocks]
{L9301 - (L9311 + L9312 + L9313 + L9314 + L9315 + L9316 + L9317
+ L9318 + L9319)} x 100%/L9301
Associated
Counters
None
Notes 1. Unit: %

2.12.5 Rate of Uplink GPRS RLC Coding Scheme with CS3/CS4
This counter provides the rate of coding scheme with CS3/4 during uplink GPRS RLC data
transmission.
Table 2-63 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
={[Number of Valid Uplink RLC Data Blocks Using CS3]
+[Number of Valid Uplink RLC Data Blocks Using CS4]} x {100%}/
{[Number of Valid Uplink RLC Data Blocks Using CS1]
+[Number of Valid Uplink RLC Data Blocks Using CS2]
+[Number of Valid Uplink RLC Data Blocks Using CS3]
+[Number of Valid Uplink RLC Data Blocks Using CS4]}
(L9008 + L9009) x 100%/(L9006 + L9007 + L9008 + L9009)
Associated
Counters
None
SingleRAN
45
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/4 during downlink GPRS RLC data
transmission.
Table 2-64 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
={[Total Number of Valid Downlink RLC Data Blocks Using CS3]
+[Total Number of Valid Downlink RLC Data Blocks Using CS4]} x
{100%}/
{[Total Number of Valid Downlink RLC Data Blocks Using CS1]
+[Total Number of Valid Downlink RLC Data Blocks Using CS2]
+[Total Number of Valid Downlink RLC Data Blocks Using CS3]
+[Total Number of Valid Downlink RLC Data Blocks Using CS4]}
(L9108 + L9109) x 100%/(L9106 + L9107 + L9108 + L9109)
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-65 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
SingleRAN
46
Formula Rate of Uplink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
={[Total Number of Valid Uplink EGPRS MCS7 RLC Data Blocks]
+[Total Number of Valid Uplink EGPRS MCS8 RLC Data Blocks]
+[Total Number of Valid Uplink EGPRS MCS9 RLC Data Blocks]} x
{100%}/
{[Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks]
+[Total Number of Valid Uplink EGPRS MCS9 RLC Data Blocks]}
(L9217 + L9218 + L9219) x 100%/(L9211 + L9212 + L9213 + L9214 +
L9215 + L9216 + L9217 + L9218 + L9219)
Associated
Counters
None
Notes Unit: %

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-66 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
SingleRAN
47
Formula Rate of Downlink EGPRS RLC Coding Scheme with MCS7/MCS8/MCS9
={[Total Number of Valid Downlink EGPRS MCS7 RLC Data Blocks]
+[Total Number of Valid Downlink EGPRS MCS8 RLC Data Blocks]
+[Total Number of Valid Downlink EGPRS MCS9 RLC Data Blocks]} x
{100%}/
{[Total Number of Valid Downlink EGPRS MCS1 RLC Data Blocks]
+[Total Number of Valid Downlink EGPRS MCS9 RLC Data Blocks]}
(L9317 + L9318 + L9319) x 100%/(L9311 + L9312 + L9313 + L9314 +
L9315 + L9316 + L9317 + L9318 + L9319)
Associated
Counters
None
Notes Unit: %

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-67 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)
=([Number of Valid Uplink RLC Data Blocks Using CS1] x{23}
+[Number of Valid Uplink RLC Data Blocks Using CS2] x{34}
+[Number of Valid Uplink RLC Data Blocks Using CS3] x{40}
+[Number of Valid Uplink RLC Data Blocks Using CS4] x{54}) x {8}/
({1024} x [Total Number of Uplink GPRS RLC Data Blocks] x{20}/
{1000})
(L9006 x {23} + L9007 x{34} + L9008 x{40} + L9009 x{54}) x {8}/
({1024} x L9001 x {20}/{1000})
SingleRAN
48
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-68 Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
KPI Name Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
Measurement
Scope
CELL
Formula Average Throughput of Downlink GPRS RLC per PDCH (kbit/s)
=([Total Number of Valid RLC Downlink Data Blocks Using CS1]x{23}
+[Total Number of Valid RLC Downlink Data Blocks Using CS2]x{34}
+[Total Number of Valid RLC Downlink Data Block Using CS4]x{54})
x {8}/
({1024}x[Total Number of Downlink GPRS RLC Data Blocks]x{20}/
{1000})
(L9106 x{23} + L9107 x{34} + L9108 x{40} + L9109 x{54}) x {8}/
({1024} x L9101 x {20}/{1000})
Associated
Counters
None

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-69 Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
KPI Name Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
SingleRAN
49
Measurement
Scope
CELL
Formula Average Throughput of Uplink EGPRS RLC per PDCH (kbit/s)
=([Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks]x{22}
+[Total Number of Valid Uplink EGPRS MCS2 RLC Data Blocks]x{28}
+[Total Number of Valid Uplink EGPRS MCS9 RLC Data Blocks]x{74})
x {8}/
({1024}x([Total Number of Uplink EGPRS MCS1 RLC Data Blocks]
+[Total Number of Uplink EGPRS MCS2 RLC Data Blocks]
+[Total Number of Uplink EGPRS MCS7 RLC Data Blocks]/{2}
+[Total Number of Uplink EGPRS MCS8 RLC Data Blocks]/{2}
+[Total Number of Uplink EGPRS MCS9 RLC Data Blocks]/{2})x{20}/
{1000})
(L9211 x{22} + L9212 x{28} + L9213 x{37} + L9214 x{44} + L9215 x
{56} + L9216 x{74} + L9217 x{56} + L9218 x{68} + L9219 x{74}) x
{8}/
({1024}x(L9202 + L9203 + L9204 + L9205 + L9206 + L9207 + L9208/
{2} + L9209/{2} + L9210/{2})x{20}/{1000})
Associated
Counters
None

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.
SingleRAN
50
Table 2-70 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)
=([Total Number of Valid Downlink EGPRS MCS1 RLC Data Blocks]x
{22}
+[Total Number of Valid Downlink EGPRS MCS2 RLC Data Blocks]x
{28}
{37}
{44}
{56}
{74}
{56}
{68}
{74}) x {8}/
({1024}x([Total Number of Downlink EGPRS MCS1 RLC Data Blocks]
+[Total Number of Downlink EGPRS MCS2 RLC Data Blocks]
+[Total Number of Downlink EGPRS MCS6 RLC data blocks]
+[Total Number of Downlink EGPRS MCS7 RLC Data Blocks]/{2}
+[Total Number of Downlink EGPRS MCS8 RLC Data Blocks]/{2}
+[Total Number of Downlink EGPRS MCS9 RLC Data Blocks]/{2})x
{20}/{1000})
(L9311 x {22} + L9312 x{28} + L9313 x{37} + L9314 x{44} + L9315 x
{56} + L9316 x{74} + L9317 x{56} + L9318 x{68} + L9319 x{74}) x
{8}/
({1024} x (L9302 + L9303 + L9304 + L9305 + L9306 + L9307 + L9308/
{2} + L9309/{2} + L9310/{2}) x{20}/{1000})
Associated
Counters
None
SingleRAN
51

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-71 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)
=([Number of Valid Uplink RLC Data Blocks Using CS1]x{23}
+[Number of Valid Uplink RLC Data Blocks Using CS2]x{34}
+[Number of Valid Uplink RLC Data Blocks Using CS3]x{40}
+[Number of Valid Uplink RLC Data Blocks Using CS4]x{54}) x {8}/
({1024}x[Total Duration of Uplink GPRS TBFs])
(L9006 x{23} + L9007 x{34} + L9008 x{40} + L9009 x{54}) x{8}/
({1024} x L9020)
Associated
Counters
None

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-72 Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL
SingleRAN
52
Formula Average Throughput of Downlink GPRS RLC per Cell (kbit/s)
=([Total Number of Valid RLC Downlink Data Blocks Using CS1]x{23}
+[Total Number of Valid RLC Downlink Data Block Using CS4]x{54})
x {8}/
({1024}x[Total Duration of Downlink GPRS TBFs])
(L9106 x {23} + L9107 x {34} + L9108 x {40} + L9109 x {54}) x {8}/
({1024}*L9121)
Associated
Counters
None

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-73 Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL
Formula Average Throughput of Uplink EGPRS RLC per Cell (kbit/s)
=([Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks]x{22}
+[Total Number of Valid Uplink EGPRS MCS9 RLC Data Blocks]x{74})
x {8}/
({1024}x[Total Duration of Uplink EGPRS TBFs])
(L9211 x{22} + L9212 x{28} + L9213 x{37} + L9214 x{44} + L9215 x
{56} + L9216 x{74} + L9217 x{56} + L9218 x{68} + L9219 x{74}) x
{8}/({1024} x L9235)
SingleRAN
53
Associated
Counters
None

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-74 Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
KPI Name Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
Measurement
Scope
CELL
Formula Average Throughput of Downlink EGPRS RLC per Cell (kbit/s)
=([Total Number of Valid Downlink EGPRS MCS1 RLC Data Blocks]x
{22}
{28}
{37}
{44}
{56}
{74}
{56}
{68}
{74}) x {8}/
({1024}*[Total Duration of Downlink EGPRS TBFs])
(L9311 x{22} + L9312 x {28} + L9313 x {37} + L9314 x {44} + L9315
x {56} + L9316 x {74} + L9317 x {56} + L9318 x {68} + L9319 x {74})
x {8}/({1024} x L9336)
Associated
Counters
None
SingleRAN
54

2.12.17 Average Throughput of Uplink GPRS LLC per User (kbit/s)
This counter provides the average throughput per MS during uplink GPRS LLC data
transmission.
Table 2-75 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)
=[Throughput of Uplink GPRS Users LLC PDU]/
([Total Bytes of Uplink GPRS Users LLC PDUs] x {8}/{1024})
L9422/(L9421 x {8}/{1024})
Associated
Counters
None

2.12.18 Average Throughput of Downlink GPRS LLC per User
(kbit/s)
This counter provides the average throughput per MS during downlink GPRS LLC data
transmission.
Table 2-76 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)
=[Throughput of Downlink GPRS Users LLC PDU]/
([Total Bytes of Downlink GPRS Users LLC PDU] x {8}/{1024})
L9526/(L9525 x {8}/{1024})
Associated
Counters
None
SingleRAN
55

2.12.19 Average Throughput of Uplink EGPRS LLC per User (kbit/
s)
This counter provides the average throughput per MS during uplink EGPRS LLC data
transmission.
Table 2-77 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)
=[Throughput of Uplink EGPRS Users LLC PDU]/
([Total Bytes of Uplink EGPRS Users LLC PDUs] x {8}/{1024})
L9424/(L9423 x {8}/{1024})
Associated
Counters
None

2.12.20 Average Throughput of Downlink EGPRS LLC per User
(kbit/s)
This counter provides the average throughput per MS during downlink EGPRS LLC data
transmission.
Table 2-78 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)
=[Throughput of Downlink EGPRS Users LLC PDU]/
([Total Bytes of Downlink EGPRS Users LLC PDU] x {8}/{1024})
L9528/(L9527 x {8}/{1024})
SingleRAN
56
Associated
Counters
None
SingleRAN
57
3 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.
SingleRAN
KPI Reference 3 UMTS Service KPI
58
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 =
(VS.RANAP.Paging.Succ.IdleUE/VS.RANAP.Paging.Att.IdleUE) x
100%
Object RNC
Unit/Range %
Note None

3.1.2 RRC Setup Success Ratio
Table 3-2 RRC Setup Success Ratio
Name RRC Setup Success Ratio
Formula
SingleRAN
59
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.
SingleRAN
60
Associated
Counters
l RRC Setup Success Ratio (Cell.Service) =
[(RRC.SuccConnEstab.OrgConvCall+
RRC.SuccConnEstab.OrgStrCall +
RRC.SuccConnEstab.OrgInterCall +
RRC.SuccConnEstab.OrgBkgCall +
RRC.SuccConnEstab.OrgSubCall +
RRC.SuccConnEstab.TmConvCall +
RRC.SuccConnEstab.TmStrCall +
RRC.SuccConnEstab.TmItrCall +
RRC.SuccConnEstab.TmBkgCall +
RRC.SuccConnEstab.EmgCall +
RRC.SuccConnEstab.Unkown +
RRC.SuccConnEstab.OrgHhPrSig +
RRC.SuccConnEstab.OrgLwPrSig +
RRC.SuccConnEstab.CallReEst +
RRC.SuccConnEstab.TmHhPrSig +
RRC.SuccConnEstab.TmLwPrSig )/
(RRC.AttConnEstab.OrgConvCall+
RRC.AttConnEstab.OrgStrCall +
RRC.AttConnEstab.OrgInterCall +
RRC.AttConnEstab.OrgBkgCall +
RRC.AttConnEstab.OrgSubCall +
RRC.AttConnEstab.TmConvCall +
RRC.AttConnEstab.TmStrCall +
RRC.AttConnEstab.TmInterCall +
RRC.AttConnEstab.TmBkgCall +
RRC.AttConnEstab.EmgCall +
RRC.AttConnEstab.Unknown +
RRC.AttConnEstab.OrgHhPrSig +
RRC.AttConnEstab.OrgLwPrSig +
RRC.AttConnEstab.CallReEst +
RRC.AttConnEstab.TmHhPrSig +
RRC.AttConnEstab.TmLwPrSig )] x 100%
l RRC Setup Success Ratio (Cell.Other) =
[(RRC.SuccConnEstab.IRATCelRes+
RRC.SuccConnEstab.IRATCCO +
RRC.SuccConnEstab.Reg +
RRC.SuccConnEstab.Detach )/
(RRC.AttConnEstab.IRATCelRes+
RRC.AttConnEstab.IRATCCO +
SingleRAN
61
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.

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.
SingleRAN
62
Associated
Counters
l Radio Access Success Ratio (Cell) =
3.1.2 RRC Setup Success Ratio*
{[(VS.RAB.SuccEstabCS.Conv+
VS.RAB.SuccEstabCS.Str )+
(VS.RAB.SuccEstabPS.Conv+
VS.RAB.SuccEstabPS.Str +
VS.RAB.SuccEstabPS.Int +
VS.RAB.SuccEstabPS.Bkg )]/
[(VS.RAB.AttEstabCS.Conv+
VS.RAB.AttEstabCS.Str )+
(VS.RAB.AttEstabPS.Conv+
VS.RAB.AttEstabPS.Str +
VS.RAB.AttEstabPS.Int +
VS.RAB.AttEstabPS.Bkg )]} x 100%
l Radio Access Success Ratio (RNC) =
3.1.2 RRC Setup Success Ratio*
{[(VS.RAB.SuccEstabCS.Conv.RNC+
VS.RAB.SuccEstabCS.Str.RNC )+
(VS.RAB.SuccEstabPS.Conv.RNC+
VS.RAB.SuccEstabPS.Str.RNC +
VS.RAB.SuccEstabPS.Int.RNC +
VS.RAB.SuccEstabPS.Bkg.RNC )]/
[(VS.RAB.AttEstabCS.Conv.RNC+
VS.RAB.AttEstabCS.Str.RNC )+
(VS.RAB.AttEstabPS.Conv.RNC+
VS.RAB.AttEstabPS.Str.RNC +
VS.RAB.AttEstabPS.Int.RNC +
VS.RAB.AttEstabPS.Bkg.RNC )]} x 100%
Object CELL, RNC
Unit/Range %
Note None

3.1.4 PS Radio Access Success Ratio
Table 3-4 PS Radio Access Success Ratio
Name PS Radio Access Success Ratio
SingleRAN
63
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.TmItrCall )/
(RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.TmInterCall )]*
3.1.9 PS RAB Setup Success Ratio x 100%
l PS Radio Access Success Ratio (RNC) =
[(RRC.SuccConnEstab.OrgBkgCall+
RRC.SuccConnEstab.TmItrCall )/
(RRC.AttConnEstab.OrgBkgCall+
RRC.AttConnEstab.TmInterCall )]*
3.1.9 PS RAB Setup Success Ratio x 100%
Object CELL, RNC
Unit/Range %
Note None

3.1.5 CS Radio Access Success Ratio
SingleRAN
64
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 )]*
3.1.8 CS RAB Setup Success Ratio x 100%
l CS Radio Access Success Ratio (RNC) =
RRC.SuccConnEstab.EmgCall )/
RRC.AttConnEstab.EmgCall )]*
3.1.8 CS RAB Setup Success Ratio x 100%
Object CELL,RNC
Unit/Range %
Note None

3.1.6 AMR RAB Setup Success Ratio
Table 3-6 AMR RAB Setup Success Ratio
Name AMR RAB Setup Success Ratio
SingleRAN
65
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the AMR Service.
AMR RAB Setup Attempt Procedure is complete when the RNC receives an
RAB ASSIGNMENT REQUEST message from the CN for the CS narrow
band AMR services.
The AMR RAB Setup Success Procedure starts when the UE sends a RADIO
BEARER SETUP COMPLETE message to the RNC. This procedure is
complete when the RNC sends an RAB ASSIGNMENT RESPONSE
message to the CN in the CS domain.
Associated
Counters
AMR RAB Setup Success Ratio(Cell) =
(VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR) x 100%
Object CELL
Unit/Range %

3.1.7 VP RAB Setup Success Ratio
Table 3-7 VP RAB Setup Success Ratio
Name VP RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB setup success ratio of CS 64 Kbit/s
conversational services in an RNC or a cluster.
VP (Video Phone) RAB Setup Attempt Procedure is complete when the RNC
receives an RAB ASSIGNMENT REQUEST message from the CN (The
RAB type is for the CS 64 Kbit/s conversational service).
VP RAB Setup Success Procedure starts when the UE sends a RADIO
BEARER SETUP COMPLETE message to RNC. This procedure is complete
when the RNC sends an RAB ASSIGNMENT RESPONSE message to the
CN in the CS domain.
Associated
Counters
VP RAB Setup Success Ratio (Cell) =
(VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64) x 100%
Object CELL
Unit/Range %
SingleRAN
66

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

3.1.9 PS RAB Setup Success Ratio
Table 3-9 PS RAB Setup Success Ratio
Name PS RAB Setup Success Ratio
SingleRAN
67
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.Bkg )] x 100%
l PS RAB Setup Success Ratio (RNC) =
[(VS.RAB.SuccEstabPS.Bkg.RNC+
VS.RAB.SuccEstabPS.Str.RNC +
VS.RAB.SuccEstabPS.Conv.RNC +
VS.RAB.SuccEstabPS.Int.RNC )/
(VS.RAB.AttEstabPS.Conv.RNC+
VS.RAB.AttEstabPS.Bkg.RNC +
VS.RAB.AttEstabPS.Int.RNC +
VS.RAB.AttEstabPS.Str.RNC )] x 100%
Object CELL, RNC
Unit/Range %
Note None

3.1.10 HSDPA RAB Setup Success Ratio
SingleRAN
68
Table 3-10 HSDPA RAB Setup Success Ratio
Name HSDPA RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB Setup Success Ratio of PS services that
are carried by HSDPA in a cluster.
The HSDPA RAB Setup Attempt Procedure is complete when the RNC
receives an RAB ASSIGNMENT REQUEST message from the CN for
setting up the HSDPA service.
The HSDPA RAB Setup Success Procedure starts when the RNC receives a
RESPONSE message to the CN.
Associated
Counters
HSDPA RAB Setup Success Ratio (Cell) =
(VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%
Object CELL
Unit/Range %

3.1.11 HSUPA RAB Setup Success Ratio
Table 3-11 HSUPA RAB Setup Success Ratio
Name HSUPA RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSUPA service
in an RNC or a cluster.
The HSUPA RAB Setup Success Procedure starts when the RNC receives a
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.
SingleRAN
69
Associated
Counters
HSUPA RAB Setup Success Ratio (Cell) =
(VS.HSUPA.RAB.SuccEstab/VS.HSUPA.RAB.AttEstab) x 100%
Object CELL
Unit/Range %

3.1.12 PS E-FACH RAB Setup Success Ratio
Table 3-12 PS E-FACH RAB Setup Success Ratio
Name PS E-FACH RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB setup success ratio of the E-FACH service
in an RNC or a cluster.
Successful PS RAB Setup on E-FACH Procedure starts when the RNC
receives a RADIO BEARER SETUP COMPLETE message from the UE.
This procedure is complete when the RNC sends an RAB ASSIGNMENT
RESPONSE message to the SGSN in the PS domain.
The procedure of Attempts of PS RAB Setup on E-FACH is complete when
the RNC receives an RAB ASSIGNMENT REQUEST message from the
SGSN, and the PS service is established on the EFACH.
Associated
Counters
PS E-FACH RAB Setup Success Ratio (Cell) =
(VS.RAB.SuccEstPS.EFACH/VS.RAB.AttEstPS.EFACH) x 100%
CELL
Unit/Range %

3.1.13 CS over HSPA RAB Setup Success Ratio
Table 3-13 CS over HSPA RAB Setup Success Ratio
Name CS over HSPA RAB Setup Success Ratio
SingleRAN
70
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 %

3.1.14 HSDPA 64QAM RAB Setup Success Ratio
Table 3-14 HSDPA 64QAM RAB Setup Success Ratio
Name HSDPA 64QAM RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the 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.
SingleRAN
71
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 %

3.1.15 HSDPA MIMO RAB Setup Success Ratio
Table 3-15 HSDPA MIMO RAB Setup Success Ratio
Name HSDPA MIMO RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO
service in an RNC or a cluster.
The HSDPA MIMO RAB Setup Success procedure starts when the RNC
receives a RADIO BEARER SETUP COMPLETE message from the UE.
The HSDPA MIMO RAB Setup Attempt procedure is complete when the
RNC receives an RAB ASSIGNMENT REQUEST message from the CN for
setting up the HSDPA service using MIMO.
Associated
Counters
HSDPA MIMO RAB Setup Success Ratio=
(VS.HSDPA.RAB.MIMO.SuccEstab/VS.HSDPA.RAB.MIMO.AttEs-
tab) x 100%
Object CELL
Unit/Range %

3.1.16 HSDPA DC RAB Setup Success Ratio
Table 3-16 HSDPA DC RAB Setup Success Ratio
Name HSDPA DC RAB Setup Success Ratio
SingleRAN
72
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA DC
RAB service in an RNC or a cluster.
The HSDPA DC RAB Setup Success procedure starts when the RNC receives
a RADIO BEARER SETUP COMPLETE message from the UE. This
The HSDPA DC RAB Setup Attempt procedure is complete when the RNC
receives from the CN an RAB ASSIGNMENT REQUEST message for
setting up the HSDPA service using DC-HSDPA.
Associated
Counters
HSDPA DC RAB Setup Success Ratio=
(VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x
100%
Object CELL
Unit/Range %

3.1.17 HSDPA MIMO64QAM RAB Setup Success Ratio
Table 3-17 HSDPA MIMO64QAM RAB Setup Success Ratio
Name HSDPA MIMO64QAM RAB Setup Success Ratio
Formula
Description This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO
64QAM service in an RNC or a cluster.
The HSDPA MIMO 64QAM RAB Setup Success procedure starts when the
RNC receives a RADIO BEARER SETUP COMPLETE message from the
UE. This procedure is complete when the RNC sends an RAB
ASSIGNMENT RESPONSE message to the CN.
The HSDPA MIMO 64QAM RAB Setup Attempt procedure is complete
when the RNC receives an RAB ASSIGNMENT REQUEST message from
the CN for setting up the HSDPA service using MIMO+64QAM.
Associated
Counters
HSDPA MIMO64QAM RAB Setup Success Ratio=
(VS.HSDPA.RAB.MIMO64QAM.SuccEstab/
VS.HSDPA.RAB.MIMO64QAM.AttEstab) x 100%
SingleRAN
73
Object CELL
Unit/Range %

3.1.18 PTM Channel Setup Success Ratio
Table 3-18 PTM Channel Setup Success Ratio
Name PTM Channel Setup Success Ratio
Formula
Description This KPI is used to check the Channel Setup Success Rate of MBMS service
in PTM mode.
When the RB of PTM MBMS service is successfully set up, the PTM Channel
RB is successfully set up.
When the RNC initiates the setup of PTM MBMS service, the PTM Channel
RB Setup Attempt.
Associated
Counters
PTM Channel Setup Success Ratio=
(VS.MBMS.RB.PTM.SuccEstab/VS.MBMS.RB.PTM.AttEstab) x
100%
Object CELL
Unit/Range %

3.1.19 PTP Channel Setup Success Ratio
Table 3-19 PTP Channel Setup Success Ratio
Name PTP Channel Setup Success Ratio
Formula
SingleRAN
74
Description This KPI is used to check the Channel Setup Success Rate of MBMS service
in PTP mode.
The PTP Channel RB Setup Success Procedure is as follows:
When the UE initiates a request to set up an MBMS, the RNC, in response to
the UE's request, initiates PTP RB setup, and the PTP RB is successfully set
up.
The PTP Channel RB Setup Attempt Procedure:
The RNC initiates PTP RB setup after the UE initiates an MBMS setup
request.
Associated
Counters
PTP Channel Setup Success Ratio=
(VS.MBMS.RB.PTP.SuccEstab/VS.MBMS.RB.PTP.AttEstab) x 100%
Object CELL
Unit/Range %

3.1.20 RRC Congestion Ratio
Table 3-20 RRC Congestion Ratio
Name RRC Congestion Ratio
Formula
Description This KPI is used to check the RRC Congestion Ratio in a cluster.
After receiving an RRC CONNECTION REQUEST message from the UE,
the RNC initiates admission procedures for resources of code, power, CE,
and Iub bandwidth. If the resource admission fails, the RRC Setup Failure
due to Congestion procedure is complete when the RNC sends an RRC
CONNECTION REJECT message to the UE.
The RRC Connection Attempt for service Procedure is complete when the
RNC receives an RRC CONNECTION REQUEST message from the UE.
Associated
Counters
RRC Congestion Ratio=
[(VS.RRC.Rej.ULPower.Cong+
VS.RRC.Rej.DLPower.Cong +
VS.RRC.Rej.ULIUBBand.Cong +
VS.RRC.Rej.DLIUBBand.Cong +
VS.RRC.Rej.ULCE.Cong +
VS.RRC.Rej.DLCE.Cong +
VS.RRC.Rej.Code.Cong )/
VS.RRC.AttConnEstab.Sum ] x 100%
SingleRAN
75
Object CELL
Unit/Range %
Note None

3.1.21 CS RAB Congestion Ratio
Table 3-21 CS RAB Congestion Ratio
Name CS RAB Congestion Ratio
Formula
Description This KPI is used to check the CS RAB Congestion Ratio in a cluster.
The CS RAB Setup Fails due to Congestion procedure is complete when the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The
message contains one of the following RAB assignment responses: "No
Radio Resources Available in Target cell", "Requested Maximum Bit Rate
not Available", "Requested Maximum Bit Rate for UL not Available",
"Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit
Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not
Available".
The CS RAB Setup Attempt Procedure starts when the RNC receives an RAB
ASSIGNMENT REQUEST message from the CN in the CS domain. The
message contains one of the following RAB assignment requests:
Conversational Services, streaming Services.
Associated
Counters
CS RAB Congestion Ratio=
[(VS.RAB.FailEstabCS.DLIUBBand.Cong+
VS.RAB.FailEstabCS.ULIUBBand.Cong +
VS.RAB.FailEstabCS.ULCE.Cong +
VS.RAB.FailEstabCS.DLCE.Cong +
VS.RAB.FailEstabCS.Code.Cong +
VS.RAB.FailEstabCS.ULPower.Cong +
VS.RAB.FailEstabCS.DLPower.Cong )/
(VS.RAB.AttEstabCS.Conv+
VS.RAB.AttEstabCS.Str )] x100%
Object CELL
Unit/Range %
Note None

SingleRAN
76
3.1.22 PS RAB Congestion Ratio
Table 3-22 PS RAB Congestion Ratio
Name PS RAB Congestion Ratio
Formula
Description This KPI is used to check the PS RAB Congestion Ratio in a cluster.
The PS RAB Setup Fails due to Congestion procedure is complete when the
RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The
message contains information about one of the following RAB assignment
responses: "No Radio Resources Available in Target cell", "Requested
Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL
not Available", "Requested Guaranteed Bit Rate not Available", "Requested
Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate
for UL not Available".
The PS RAB Setup Attempt Procedure starts when the RNC receives an RAB
ASSIGNMENT REQUEST message from the SGSN in the PS domain. The
message contains information about one of the following RAB assignment
requests: Conversational services, Streaming services, Interactive Services,
Background Services.
Associated
Counters
PS RAB Congestion Ratio=
[(VS.RAB.FailEstabPS.DLIUBBand.Cong+
VS.RAB.FailEstabPS.ULIUBBand.Cong +
VS.RAB.FailEstabPS.ULCE.Cong +
VS.RAB.FailEstabPS.DLCE.Cong +
VS.RAB.FailEstabPS.Code.Cong +
VS.RAB.FailEstabPS.ULPower.Cong +
VS.RAB.FailEstabPS.DLPower.Cong )/
VS.RAB.AttEstabPS.Bkg )] x 100%
Object CELL
Unit/Range %
Note None

SingleRAN
77
3.2 Availability
Availability KPIs mainly indicate the utilization for several kinds of network resources such as
Radio, bandwidth or CPU Load.
3.2.1 Worst Cell Ratio
Table 3-23 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-24 Paging Congestion Ratio
Name Paging Congestion Ratio
SingleRAN
78
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
SingleRAN
79
Table 3-25 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=
[1-VS.RAC.NewCallAcc/VS.RAC.NewCallReq] x 100%
Object CELL
Unit/Range %

3.2.4 Congested Cell Ratio
Table 3-26 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.
SingleRAN
80
Associated
Counters
Congested Cell Ratio =
(The Number Of Cells, in which VS.LCC.OLC.UL.Num>0 or
VS.LCC.OLC.DL.Num>0 On Busy Hour/The Total Number Of Cells In
RNC) x 100%
Object CELL
Unit/Range %
Note The number of congested cells is calculated by aggregating the cells that are
congested in DL or UL directions during busy hours.

3.2.5 Radio Network Unavailability Ratio
Table 3-27 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-28 Average CPU Load
Name Average CPU Load
SingleRAN
81
Formula Average CPU Load = XPU usage of the XPU in the measurement period
Description This KPI provides the CPU usage of the XPU in a measurement period. It
also indicates the load and operating performance of CPU on the XPU in the
measurement period.
The CPU usage of the XPU is accumulated every second in the measurement
period.
Associated
Counters
Average CPU Load= VS.XPU.CPULOAD.MEAN
Object XPU
Unit/Range %
Note Mean CPU Utility is the CPU average load showed in percentage.

3.2.7 IUB Bandwidth Utilizing Ratio (UL)
Table 3-29 IUB Bandwidth Utilizing Ratio (UL)
Name IUB Bandwidth Utilizing Ratio (UL)
Formula
Description This KPI is used to check the ratio of consumption of Iub bandwidth and
configured Iub bandwidth in a NodeB for downlink during busy hours. The
consumption of interactive and background services cannot maintain the full
rate all the time on the configured Iub bandwidth.
The UL Bandwidth could be measured on ATM Physical Ports or IP physical
Ports. The numerator is defined as the average used bandwidth on an ATM
or IP physical ports during a measurement period counted by NodeB. The
NodeB measures the used UL bandwidth on the physical port every five
seconds for 15 minutes and then calculates the average value. The counter
and the physical port have one-to-one relation, and they are all used for traffic
measurement at the physical layer.
SingleRAN
82
Associated
Counters
l IUB Bandwidth Utilizing Ratio (ATM_UL) =
[(VS.ATMUlAvgUsed.1+
VS.ATMUlAvgUsed.2+
VS.ATMUlAvgUsed.3+
VS.ATMUlAvgUsed.4)/
(VS.ATMUlTotal.1+
VS.ATMUlTotal.2+
VS.ATMUlTotal.3+
VS.ATMUlTotal.4)] x 100%
l IUB Bandwidth Utilizing Ratio (IP_UL) =
[(VS.IPUlAvgUsed.1+
VS.IPUlAvgUsed.2+
VS.IPUlAvgUsed.3+
VS.IPUlAvgUsed.4)/
(VS.IPUlTotal.1+
VS.IPUlTotal.2+
VS.IPUlTotal.3+
VS.IPUlTotal.4)] x 100%
Object NodeB
Unit/Range %
Note The counters in the formula are measured on the NodeB side.
In Iub over IP mode, the NodeB-level counters VS.IPUlTotal.1,
VS.IPUlTotal.2, VS.IPUlTotal.3, and VS.IPUlTotal.4 provide the physical
bandwidths of ports rather than the actual available bandwidths of ports.
Therefore, if the actual available bandwidth of a port is different from the
physical bandwidth of the port, the value of this KPI calculated by using this
formula is incorrect, and you are advised to use the actual available
bandwidths as the denominator to calculate this KPI.

3.2.8 IUB Bandwidth Utilizing Ratio (DL)
Table 3-30 IUB Bandwidth Utilizing Ratio (DL)
Name IUB Bandwidth Utilizing Ratio (DL)
Formula
SingleRAN
83
Description This KPI is used to check the ratio of consumption of Iub bandwidth and
configured Iub bandwidth in a NodeB for downlink during busy hours. The
consumption of interactive and background services cannot maintain the full
rate all the time on the configured Iub bandwidth.
The DL Bandwidth could be measured on ATM Physical Ports or IP physical
Ports. The numerator is defined as the average used bandwidth on an ATM
or IP physical ports during a measurement period counted by NodeB. The
NodeB measures the used DL bandwidth on the physical port every five
seconds for 15 minutes and then calculates the average value. The counter
and the physical port have one-to-one relation, and they are all used for traffic
measurement at the physical layer.
Associated
Counters
l IUB Bandwidth Utilizing Ratio (ATM_DL) =
[(VS.ATMDIAvgUsed.1+
VS.ATMDLAvgUsed.2+
VS.ATMDLAvgUsed.3+
VS.ATMDLAvgUsed.4)/
(VS.ATMDLTotal.1+
VS.ATMDLTotal.2+
VS.ATMDLTotal.3+
VS.ATMDLTotal.4)] x 100%
l IUB Bandwidth Utilizing Ratio (IP_DL) =
[(VS.IPDLAvgUsed.1+
VS.IPDLAvgUsed.2+
VS.IPDLAvgUsed.3+
VS.IPDLAvgUsed.4)/
(VS.IPDLTotal.1+
VS.IPDLTotal.2+
VS.IPDLTotal.3+
VS.IPDLTotal.4)] x 100%
Object NodeB
Unit/Range %
Note The counters in the formula are measured on the NodeB side.
In Iub over IP mode, the NodeB-level counters VS.IPDLTotal.1,
VS.IPDLTotal.2, VS.IPDLTotal.3, and VS.IPDLTotal.4 provide the
physical bandwidths of ports rather than the actual available bandwidths of
ports. Therefore, if the actual available bandwidth of a port is different from
the physical bandwidth of the port, the value of this KPI calculated by using
this formula is incorrect, and you are advised to use the actual available
bandwidths as the denominator to calculate this KPI.

3.2.9 Cell Unavailability duration
SingleRAN
84
Table 3-31 Cell Unavailability duration
Name Cell Unavailability duration
Description This KPI is used to check the total duration of the unavailability of a cell
caused by system fault in a measurement period.
Associated
Counters
VS.Cell.UnavailTime.Sys
Object CELL
Unit/Range s
Note None

3.2.10 HSDPA Unavailability duration
Table 3-32 HSDPA Unavailability duration
Name HSDPA Unavailability duration
Description This KPI is used to check the total duration of unavailability of the HSDPA
service in a cell,caused by system fault in a measurement period.
Associated
Counters
VS.Cell.HSDPA.UnavailTime
Object CELL
Unit/Range s
Note None

3.2.11 HSUPA Unavailability duration
Table 3-33 HSUPA Unavailability duration
Name HSUPA Unavailability duration
Description This KPI is used to check the total duration of unavailability of the HSUPA
service in a cell,caused by system fault in a measurement period.
Associated
Counters
VS.Cell.HSUPA.UnavailTime
Object CELL
Unit/Range s
SingleRAN
85
Note None

3.2.12 CE Consumption for a NodeB Cell
Table 3-34 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-35 Hardware Configured CE for a NodeB
Name Hardware Configured CE for a NodeB
Description Number of UL/DL CEs configured for a NodeB.
Associated
Counters
VS.HW.ULCreditAvailable
VS.HW.DLCreditAvailable
Object NodeB
Unit/Range Numbers
SingleRAN
86
Note None

3.2.14 Shared Group Configured License CE for a NodeB
Table 3-36 Shared Group Configured License CE for a NodeB
Name Shared Group Configured License CE for a NodeB
Description The Configured DL/UL CEs for the Shared Group.
Associated
Counters
VS.LC.ULCreditAvailable.Shared
VS.LC.DLCreditAvailable.Shared
Object NodeB
Unit/Range Numbers
Note If only one operator is available on the NodeB, the configured counters given
above should be used to evaluate the total configured License CE in the
NodeB.

3.2.15 Shared Group License CE Consumption for a NodeB
Table 3-37 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
SingleRAN
87
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
Table 3-38 License Group Configured CE for a NodeB
Name License Group Configured CE for a NodeB
Description The Number of DL CEs configured for a license Group.
Associated
Counters
VS.LC.DLCreditAvailable.LicenseGroup.Dedicated
VS.LC.ULCreditAvailable.LicenseGroup.Dedicated
Object NodeB
Unit/Range Numbers
Note If only one operator is available on the NodeB, the configured counter value
given above is Zero.

3.2.17 License Group CE Consumption for a NodeB
Table 3-39 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
SingleRAN
88
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)
Table 3-40 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-41 TCP (Transmitted Carrier Power)
Name TCP (Transmitted Carrier Power)
Description l The first 3 counters provide the Maximum/Minimum/Mean Transmitted
Power of Carrier for a cell.
l The second 3 counters provide the Maximum/Minimum/Mean
Transmitted Power of Carrier for Non-HSDPA Cell.
l The third 3 counters provide Maximum/Minimum/Mean Required Power
by HS-DSCH for Cell.
SingleRAN
89
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
Object CELL
Unit/Range dBm
Note None

3.2.20 R99 Code Utilization
Table 3-42 R99 Code Utilization
Name R99 Code Utilization
Formula
Description The occupied codes are the codes occupied by the common channel and 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 %
SingleRAN
90
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.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-43 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-44 Soft Handover Overhead
KPI Name Soft Handover Overhead (RNC)
SingleRAN
91
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.
SingleRAN
92
Associated
Counters
l Soft Handover Overhead (RNC) =
{[VS.SHO.AS.1.RNC +
(VS.SHO.AS.2Softer.RNC +
VS.SHO.AS.2Soft.RNC ) x 2 +
(VS.SHO.AS.3Soft2Softer.RNC +
VS.SHO.AS.3Soft.RNC +
VS.SHO.AS.3Softer.RNC ) x 3 +
VS.SHO.AS.4.RNC x 4 +
VS.SHO.AS.5.RNC x 5 +
VS.SHO.AS.6.RNC x 6]/
(VS.SHO.AS.1.RNC+
VS.SHO.AS.2Softer.RNC +
VS.SHO.AS.3Soft2Softer.RNC +
VS.SHO.AS.3Softer.RNC +
VS.SHO.AS.4.RNC +
VS.SHO.AS.5.RNC +
VS.SHO.AS.6.RNC ) - 1} x 100%
l Soft Handover Overhead (Cell) =
[(VS.SHO.AS.1RL+
VS.SHO.AS.2RL +
VS.SHO.AS.3RL +
VS.SHO.AS.4RL +
VS.SHO.AS.5RL +
VS.SHO.AS.6RL )/
(VS.SHO.AS.1RL+
VS.SHO.AS.2RL /2 +
VS.SHO.AS.3RL /3 +
VS.SHO.AS.4RL /4 +
VS.SHO.AS.5RL /5 +
VS.SHO.AS.6RL /6)-1] x 100%
Object RNC, CELL
Unit/Range %
Note None

SingleRAN
93
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-45 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-46 Softer Handover Success Ratio
Name Softer Handover Success Ratio
Formula
SingleRAN
94
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-47 AMR Soft Handover Success Ratio
Name AMR Soft Handover Success Ratio
Formula
Description This KPI is used to check the AMR Soft Handover Success ratio in an RNC
or 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
Associated
Counters
AMR Soft Handover Success Ratio =
[(VS.SHO.AMR.Succ)/(VS.SHO.AMR.Att)] x 100%
Object CELL
Unit/Range %
Note The RNC level KPI can be approximately calculated by accumulating all cell
counters within the RNC.

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

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

3.4.6 Intra-frequency Hard Handover Success Ratio
Table 3-50 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.
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.
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
SingleRAN
97
Table 3-51 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.
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%
Object RNC, CELL
Unit/Range %
Note None

3.4.8 Service Cell Change Success Ratio with SHO (H2H)
Table 3-52 Service Cell Change Success Ratio with SHO (H2H)
Name Service Cell Change Success Ratio with SHO (H2H)
Formula
SingleRAN
98
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
PHYSICAL CHANNEL RECONFIGURATION FAILURE
TRANSPORT CHANNEL RECONFIGURATION COMPLETE
TRANSPORT CHANNEL RECONFIGURATION FAILURE
RADIO BEARER RECONFIGURATION COMPLETE
RADIO BEARER RECONFIGURATION FAILURE
ACTIVE SET UPDATE COMPLETE
ACTIVE SET UPDATE FAILURE Message
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) =
(VS.HSDPA.SHO.ServCellChg.SuccOut/
VS.HSDPA.SHO.ServCellChg.AttOut) x 100%
Object CELL
Unit/Range %
Note None

3.4.9 H2H Intra-Frequency Hard Handover Success Ratio
Table 3-53 H2H Intra-Frequency Hard Handover Success Ratio
Name H2H Intra-Frequency Hard Handover Success Ratio
Formula
SingleRAN
99
Description This KPI is used to check the intra-frequency hard handover success ratio of
HSDPA service in an RNC or a cluster.
l The HS-DSCH service cell change success with SHO is triggered with
the following message:
response.
RADIO BEARER SETUP COMPLETE
RADIO BEARER SETUP FAILURE
RADIO BEARER RELEASE COMPLETE
RADIO BEARER RELEASE FAILURE
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.
Associated
Counters
H2H Intra-Frequency Hard Handover Success Ratio =
(VS.HSDPA.HHO.H2H.SuccOutIntraFreq/VS.HSDPA.HHO.H2H.At-
tOutIntraFreq) x 100%
Object CELL
Unit/Range %
Note None

3.4.10 H2H Inter-Frequency Hard Handover Success Ratio
Table 3-54 H2H Inter-Frequency Hard Handover Success Ratio
Name H2H Inter-Frequency Hard Handover Success Ratio
Formula
SingleRAN
100
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:
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
H2H Inter-Frequency Hard Handover Success Ratio=
(VS.HSDPA.HHO.H2H.SuccOutInterFreq/VS.HSDPA.HHO.H2H.At-
tOutInterFreq) x 100%
Object CELL
Unit/Range %
Note None

3.4.11 H2D Inter-frequency Hard Handover Success Ratio
Table 3-55 H2D Inter-frequency Hard Handover Success Ratio
Name H2D Inter-frequency Hard Handover Success Ratio
Formula
SingleRAN
101
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
RADIO BEARER RELEASE message
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 =
(VS.HSDPA.HHO.H2D.SuccOutInterFreq/VS.HSDPA.HHO.H2D.At-
Object CELL
Unit/Range %
Note None

3.4.12 H2D Channel Switch Success Ratio
Table 3-56 H2D Channel Switch Success Ratio
Name H2D Channel Switch Success Ratio
Formula
SingleRAN
102
Description This KPI is used to check the channel switch success ratio when UE switches
from HSDPA to DCH in an RNC or 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.
Associated
Counters
H2D Channel Switch Success Ratio=
(VS.HSDPA.H2D.Succ/VS.HSDPA.H2D.Att) x 100%
Object CELL
Unit/Range %
Note None

3.4.13 D2H Channel Switch Success Ratio
Table 3-57 D2H Channel Switch Success Ratio
Name D2H Channel Switch Success Ratio
Formula
SingleRAN
103
Description This KPI is used to check the channel switch success ratio when the UE
switches from DCH to HSDPA in an RNC or 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.
Associated
Counters
D2H Channel Switch Success Ratio =
(VS.HSDPA.D2H.Succ/VS.HSDPA.D2H.Att) x 100%
Object CELL
Unit/Range %
Note None

3.4.14 CS W2G Inter-RAT Handover Out Success Ratio
Table 3-58 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 RNC
receives an IU RELEASE COMMAND message. The message contains one
of the following information: "Successful Relocation", "Normal Release",
"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.
The CS inter-RAT Handover attempts procedure starts when the RNC sends
a HANDOVER FROM UTRAN COMMAND message to the UE during the
CS outgoing inter-RAT handover.
SingleRAN
104
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) x 100%
Object RNC, CELL
Unit/Range %
Note None

3.4.15 PS W2G Inter-RAT Handover Out Success Ratio
Table 3-59 PS W2G Inter-RAT Handover Out Success Ratio
Name PS W2G Inter-RAT Handover Out Success Ratio
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 IU RELEASE COMPLETE message after receiving
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. In this
case, the PS outgoing inter-RAT handover succeeds and the counter is
measured.
The PS W2G Inter-RAT Outgoing Handover attempts procedure starts when
the RNC sends the CELL CHANGE ORDER FROM UTRAN message
during the PS outgoing inter-RAT handover.
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) x 100%
Object RNC, CELL
Unit/Range %
Note None

SingleRAN
105
3.4.16 PS G2W Inter-RAT Handover In Success Ratio
Table 3-60 PS G2W Inter-RAT Handover In Success Ratio
Name PS G2W Inter-RAT Handover In Success Ratio
Formula
Description This KPI is used to check the PS inter-RAT handover in success ratio in an
RNC or 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.IRAT-
CelRes)/
(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.

3.4.17 HSDPA W2G Inter-RAT Handover Out Success Ratio
Table 3-61 HSDPA W2G Inter-RAT Handover Out Success Ratio
Name HSDPA W2G Inter-RAT Handover Out Success Ratio
Formula
SingleRAN
106
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
"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.
Associated
Counters
HSDPA W2G Inter-RAT Handover Out Success Ratio=
(VS.IRATHO.HSDPA.SuccOutPSUTRAN/VS.IRATHO.HSDPA.At-
tOutPSUTRAN) x 100%
Object CELL
Unit/Range %
Note The KPI includes the IRAT cell reselection of UE in idle status.

3.4.18 SRNC Relocation Success Ratio
Table 3-62 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
"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).
SingleRAN
107
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%
Object RNC
Unit/Range %
Note None

3.4.19 TRNC Relocation Success Ratio
Table 3-63 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.
SingleRAN
108
Associated
Counters
TRNC Relocation Success Ratio =
[(VS.TRELOC.SuccExecUEInvol+
VS.TRELOC.SuccExecUENotInvol )/
(RELOC.SuccResAllocUEInvolCS+
RELOC.SuccResAllocUENotInvolCS +
RELOC.SuccResAllocUEInvolPS +
RELOC.SuccResAllocUENotInvolPS )] x 100%
Object RNC
Unit/Range %
Note None

3.4.20 E-DCH Soft Handover Success Ratio
Table 3-64 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=
(VS.HSUPA.SHO.SuccOut/VS.HSUPA.SHO.AttOut) x 100%
Object CELL
Unit/Range %
Note None

3.4.21 E-DCH Cell Change Success Ratio with SHO
SingleRAN
109
Table 3-65 E-DCH Cell Change Success Ratio with SHO
Name E-DCH Cell Change Success Ratio with SHO
Formula
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 =
(VS.HSUPA.SHO.ServCellChg.SuccOut/
VS.HSUPA.SHO.ServCellChg.AttOut) x 100%
Object CELL
Unit/Range %
Note None

SingleRAN
110
3.4.22 E-DCH Cell Change Success Ratio with Inter-HHO
Table 3-66 E-DCH Cell Change Success Ratio with Inter-HHO
Name E-DCH Cell Change Success Ratio with Inter-HHO
Formula
Description This KPI is used to check the E-DCH service cell change success ratio with
the Inter-HHO procedure in an RNC or a cluster.
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.
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
RADIO BEARER RELEASE
Associated
Counters
E-DCH Service Cell Change Success Ratio with Inter-HHO=
(VS.HSUPA.HHO.E2E.SuccOutInterFreq/VS.HSUPA.HHO.E2E.At-
Object CELL
Unit/Range %
Note None

3.4.23 E2D Channel Switch Success Ratio
SingleRAN
111
Table 3-67 E2D Channel Switch Success Ratio
Name E2D Channel Switch Success Ratio
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 =
(VS.HSUPA.E2D.Succ/VS.HSUPA.E2D.Att) x 100%
Object CELL
Unit/Range %
Note None

3.4.24 D2E Channel Switch Success Ratio
Table 3-68 D2E Channel Switch Success Ratio
Name D2E Channel Switch Success Ratio
Formula
SingleRAN
112
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) =
(VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att) x 100%
Object CELL
Unit/Range %
Note None

3.4.25 E2D Handover Success Ratio with Inter HHO
Table 3-69 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.
Associated
Counters
E-DCH to DCH Handover Success Ratio (with Inter HHO) =
(VS.HSUPA.HHO.E2D.SuccOutInterFreq/VS.HSUPA.HHO.E2D.At-
SingleRAN
113
Object CELL
Unit/Range %
Note None

3.4.26 HSUPA W2G Inter-RAT Handover Out Success Ratio
Table 3-70 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
HSUPA W2G Inter-RAT Handover Out Success Ratio =
(VS.IRATHO.HSUPA.SuccOutPSUTRAN/VS.IRATHO.HSUPA.At-
tOutPSUTRAN) x 100%
Object CELL
Unit/Range %
Note None

3.4.27 MBMS Service Mode Switch Success Ratio
SingleRAN
114
Table 3-71 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=
(VS.MBMS.PTPtoPTM.Succ/VS.MBMS.PTPtoPTM.Att) x 100%
Object CELL
Unit/Range %
Note None

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
Table 3-72 CS Service Drop Ratio
Name CS Service Drop Ratio
Formula
SingleRAN
115
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 None

3.5.2 AMR Call Drop Ratio
Table 3-73 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.
SingleRAN
116
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%
Object CELL, RNC
Unit/Range %
Note The RNC level KPIs are calculated by aggregating all the Cell and Iur
counters in SRNC.

3.5.3 VP Call Drop Ratio
Table 3-74 VP Call Drop Ratio
Name VP Call Drop Ratio
Formula
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",
SingleRAN
117
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.4 AMR Traffic Drop Ratio
Table 3-75 AMR Traffic Drop Ratio
Name AMR Traffic Drop Ratio
Formula
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",
SingleRAN
118
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)
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.5 VP Traffic Drop Ratio
Table 3-76 VP Traffic Drop Ratio
Name VP Traffic Drop Ratio
Formula
SingleRAN
119
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.6 PS Call Drop Ratio
Table 3-77 PS Call Drop Ratio
Name PS Call Drop Ratio
Formula
SingleRAN
120
Description This KPI provides the ratio of the PS RAB abnormal Releases to the total PS
RAB 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 None

3.5.7 PS Call Drop Ratio (PCH)
Table 3-78 PS Call Drop Ratio (PCH)
Name PS Call Drop Ratio (PCH)
Formula
Description Compared with PS Call Drop Ratio, these KPIs take the PCH state into
account.
Since more and more smart phones camp on and keep Always Online in the
network, if the PCH transition is switched on while no data transferring for
a period, these UEs usually transfer from connected state into Cell PCH state
instead of Idle state, that is, the occasion of RAB normal release for
transferring into IDLE state will greatly decrease than that in the conditions
without PCH transition.
From user's point of view, the occasion of a UE transferring into PCH state
should be considered as a normal RAB release for calculating the formula of
PS Call Drop Ratio.
SingleRAN
121
Associated
Counters
l PS Call Drop Ratio with PCH (Cell) =
[(VS.RAB.AbnormRel.PS-
VS.RAB.AbnormRel.PS.PCH -
VS.RAB.AbnormRel.PS.D2P -
VS.RAB.AbnormRel.PS.F2P ) /
(VS.RAB.AbnormRel.PS+
VS.RAB.NormRel.PS -
VS.RAB.NormRel.PS.PCH +
VS.DCCC.D2P.Succ +
VS.DCCC.Succ.F2P )] x 100%
l PS Service Drop Ratio with PCH (RNC) =
[(VS.RAB.AbnormRel.PS.RNC-
Sum{VS.RAB.AbnormRel.PS.PCH}-
Sum{VS.RAB.AbnormRel.PS.D2P}-
Sum{VS.RAB.AbnormRel.PS.F2P})/
(VS.RAB.AbnormRel.PS.RNC+
VS.RAB.NormRel.PS.RNC -
Sum{VS.RAB.AbnormRel.PS.PCH}-
Sum{VS.RAB.NormRel.PS.PCH} +
Sum{VS.DCCC.D2P.Succ} +
Sum{VS.DCCC.Succ.F2P})] x 100%
Object CELL, RNC
Unit/Range %
Note The occasion of a UE transferring into PCH state should be considered as a
normal RAB release for calculating the formula of PS Call Drop Ratio.
Why VS.RAB.normRel.PS.PCH is subtracted in the denominator?
l If a UE transfers into PCH state and then go to the IDLE state, it will be
counted twice respectively in VS.DCCC.D2P.Succ(or
VS.DCCC.Succ.F2P) and VS.RAB.NormRel.PS.
The same reason as VS.RAB.AbnormRel.PS.PCH.
The measurement object of the counters in Sum{*} is the cell, the RNC 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.8 PS R99 Call Drop Ratio
SingleRAN
122
Table 3-79 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).
Associated
Counters
PS R99 Call Drop Ratio (Cell) =
(VS.RAB.AbnormRel.PSR99)/(VS.RAB.AbnormRel.PSR99
+VS.RAB.NormRel.PSR99) x 100%
Object CELL
Unit/Range %
Note 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 is located in
DRNC through Iur interface, no counters for the scenario exists in SRNC.

3.5.9 PS R99 Call Drop Ratio (PCH)
Table 3-80 PS R99 Call Drop Ratio (PCH)
Name PS R99 Call Drop Ratio (PCH)
Formula
Description Compared with PS R99 Call Drop Ratio, this KPI takes the PCH state into
account.
SingleRAN
123
Associated
Counters
PS R99 Call Drop Ratio with PCH (Cell) =
[(VS.RAB.AbnormRel.PSR99-
VS.RAB.AbnormRel.PS.R99D2P -
VS.RAB.AbnormRel.PS.F2P )/
(VS.RAB.AbnormRel.PSR99+
VS.RAB.NormRel.PSR99 -
VS.RAB.NormRel.PS.PCH +
VS.HSDPA.F2H.Succ +
VS.HSDPA.D2H.Succ +
VS.PSR99.D2P.Succ +
VS.DCCC.Succ.F2P )] x 100%
Object CELL
Unit/Range %
Note The occasion of a UE transferring out of PS R99 state (F2H, F2P, D2H) 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
via Iur interface, this scenario is not taken into account in the formula.
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.10 PS BE Call Drop Ratio
Table 3-81 PS BE Call Drop Ratio
Name PS BE Call Drop Ratio
Formula
SingleRAN
124
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.

Table 3-82 HSDPA Call Drop Ratio
Name HSDPA Call Drop Ratio
Formula
SingleRAN
125
Description This KPI provides the ratio of the HSDPA RAB abnormal Releases to the
total HSDPARAB 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 HS-DSCH release
(Including the transitions due to mobility).

3.5.12 HSDPA Call Drop Ratio (PCH)
SingleRAN
126
Table 3-83 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.AbnormRel-
VS.HSDPA.RAB.AbnormRel.H2P )/
(VS.HSDPA.RAB.AbnormRel+
VS.HSDPA.RAB.NormRel +
VS.HSDPA.HHO.H2D.SuccOutIntraFreq +
VS.HSDPA.HHO.H2D.SuccOutInterFreq +
VS.HSDPA.H2D.Succ +
VS.HSDPA.H2F.Succ +
VS.HSDPA.H2P.Succ )] x 100%
l HSDPA Service Drop Ratio with PCH(RNC) =
[(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur} -
Sum{VS.HSDPA.RAB.AbnormRel.H2P} )/
(Sum{VS.HSDPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSDPA.Iur} +
Sum{VS.RAB.NormRel.HSDPA.Iur} +
Sum{VS.HSDPA.RAB.NormRel} +
Sum{VS.HSDPA.H2D.Succ} +
Sum{VS.HSDPA.H2F.Succ} +
Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq} +
Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq} +
Sum{VS.HSDPA.H2P.Succ} )] x 100%
Object CELL, RNC
Unit/Range %
Note The occasion of a UE transferring out of PS HS-DSCH Channel state (H2D,
H2F, H2P) should be considered as a normal RAB release for calculating the
formula of PS HSDPA Call Drop Ratio.

3.5.13 HSUPA Call Drop Ratio
SingleRAN
127
Table 3-84 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%
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 E-DCH release
(Including the transitions due to mobility).

SingleRAN
128
3.5.14 HSUPA Call Drop Ratio (PCH)
Table 3-85 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.AbnormRel-
VS.HSUPA.RAB.AbnormRel.E2P )/
(VS.HSUPA.RAB.AbnormRel+
VS.HSUPA.RAB.NormRel +
VS.HSUPA.HHO.E2D.SuccOutIntraFreq +
VS.HSUPA.HHO.E2D.SuccOutInterFreq +
VS.HSUPA.E2F.Succ +
VS.HSUPA.E2D.Succ +
VS.HSUPA.E2P.Succ )] x 100%
l HSUPA Call Drop Ratio with PCH (RNC) =
[(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.RAB.AbnormRel.HSUPA.Iur} -
Sum{VS.HSUPA.RAB.AbnormRel.E2P} )/
(Sum{VS.HSUPA.RAB.AbnormRel}+
Sum{VS.HSUPA.RAB.NormRel} +
Sum{VS.RAB.AbnormRel.HSUPA.Iur} +
Sum{VS.RAB.NormRel.HSUPA.Iur} +
Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq} +
Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq} +
Sum{VS.HSUPA.E2F.Succ} +
Sum{VS.HSUPA.E2D.Succ} +
Sum{VS.HSUPA.E2P.Succ} )] x 100%
Object CELL, RNC
Unit/Range %
Note The occasion of a UE transferring out of PS E-DCH Channel state (E2D, E2F,
E2P) should be considered as a normal RAB release for calculating the
formula of PS HSUPA Call Drop Ratio.

SingleRAN
129
3.5.15 MBMS Service PTP drop Ratio
Table 3-86 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)] x 100%
Object CELL
Unit/Range %
Note The RNC level KPIs are calculated by aggregating all the cell 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.6.1 Average UL Throughput for PS R99 Service
Table 3-87 Average UL Throughput for PS R99 Service
Name Average UL Throughput for PS R99 Service
Description These counters provide the average uplink rates of different PS R99 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.
SingleRAN
130
Associated
Counters
VS.PS.Bkg.Kbps.UL8
VS.PS.Bkg.Kbps.UL16
VS.PS.Bkg.Kbps.UL32
VS.PS.Bkg.Kbps.UL64
VS.PS.Bkg.Kbps.UL128
VS.PS.Int.Kbps.UL8
VS.PS.Int.Kbps.UL16
VS.PS.Int.Kbps.UL32
VS.PS.Int.Kbps.UL64
VS.PS.Int.Kbps.UL128
VS.PS.Str.Kbps.UL8
VS.PS.Str.Kbps.UL16
VS.PS.Str.Kbps.UL32
VS.PS.Str.Kbps.UL64
VS.PS.Str.Kbps.UL128
VS.PS.Conv.Kbps.UL
Object CELL
Unit/Range Kbit/s
Note None

3.6.2 Average DL Throughput for PS R99 Service
Table 3-88 Average DL Throughput for PS R99 Service
Name Average DL Throughput for PS R99 Service
SingleRAN
131
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.
Associated
Counters
VS.PS.Bkg.Kbps.DL8
VS.PS.Bkg.Kbps.DL16
VS.PS.Bkg.Kbps.DL32
VS.PS.Bkg.Kbps.DL64
VS.PS.Bkg.Kbps.DL128
VS.PS.Int.Kbps.DL8
VS.PS.Int.Kbps.DL16
VS.PS.Int.Kbps.DL32
VS.PS.Int.Kbps.DL64
VS.PS.Int.Kbps.DL128
VS.PS.Str.Kbps.DL8
VS.PS.Str.Kbps.DL16
VS.PS.Str.Kbps.DL32
VS.PS.Str.Kbps.DL64
VS.PS.Str.Kbps.DL128
VS.PS.Conv.Kbps.DL
Object CELL
Unit/Range Kbit/s
Note None

3.6.3 Average UL BLER for CS Service
SingleRAN
132
Table 3-89 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
VS.ULBler.CS64
Object CELL
Unit/Range %
Note None

3.6.4 Average UL BLER for PS Service
Table 3-90 Average UL BLER for PS Service
Name Average UL BLER for PS Service
Description This counter provides the UL BLER of PS services on the DCH in the 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
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

SingleRAN
133
3.6.5 HSDPA Throughput
Table 3-91 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.
Associated
Counters
VS.HSDPA.MeanChThroughput
Object CELL
Unit/Range Kbit/s
Note None

Table 3-92 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
VS.DataOutput.Mean/(VS.DataTtiRatio.Mean-
VS.HSDPA.InactiveDataTtiRatio.Mean)
Object NodeB
Unit/Range Kbit/s
Note We can apply the following formula to get the Mean HSDPA Cell Throughput
within RNC approximately:
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.

SingleRAN
134
3.6.6 HSUPA Throughput
Table 3-93 Mean Throughput for One HSUPA User
Name Mean Throughput for One HSUPA User
Description This counter indicates the mean downlink 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
VS.HSUPA.MeanChThroughput
Object CELL
Unit/Range Kbit/s
Note None

Table 3-94 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 user is transferring data during the entire measurement period.
Average bit rate of MAC-d data flows that the NodeB receives successfully
from all users over the time when data is transferred during a measurement
period. The time when there is data transfer during a measurement period is
calculated as follows: Sampling times of data transfer x length of the sampling
period If the number of received MAC-d PDU bits is 0 in a certain sampling
period, which is 10 ms in length, the NodeB does not count this period.
Associated
Counters
VS.HSUPA.MeanBitRate.WithData
Object NodeB
Unit/Range Kbit/s
SingleRAN
135
Note We can apply the following formula to get the Mean HSUPA Cell Throughput
within the RNC approximately:
HSUPA Cell Throughput (RNC Cell) =
VS.HSUPA.MeanChThroughput.TotalBytes x 8/[{SP} x 60]/1000
Where:
{SP} is the Statistic Period with the unit of Minute.
The KPI may not be accurate under the following condition: there is no
HSUPA User transferring data for a while during the total measurement
period. Therefore, the KPI should be evaluated during busy hour for accuracy.

3.6.7 PS UL Throughput of RNC
Table 3-95 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

SingleRAN
136
3.6.8 PS DL Throughput of RNC
Table 3-96 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
VS.MBMSPSLoad.DLThruput.RNC
VS.MBMSPSLoad.MaxDLThruput.RNC
Object RNC
Unit/Range kbit/s
Note None

3.6.9 MBMS Service Throughput
Table 3-97 MBMS Service Throughput
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
VS.MBMS.PTP.MeanThroughput
SingleRAN
137
Object CELL
Unit/Range kbit/s
Note None

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-98 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.
Associated
Counters
VS.CSLoad.Erlang.Equiv.RNC
VS.CSLoad.MaxErlang.Equiv.RNC
SingleRAN
138
Object RNC
Unit/Range Erl
Note None

3.7.2 Number of CS Users
Table 3-99 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.12.2.RNC );
VS.RB.CS.Conv.DL.64.RNC
Object CELL, RNC
Unit/Range None
SingleRAN
139
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).
For a VP service, V1 platform equals to four Erlangs and V2 platform equals
to two Erlangs.

3.7.3 Number of PS R99 Users
Table 3-100 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.
SingleRAN
140
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
VS.RB.PS.Int.DL.8
SingleRAN
141
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
SingleRAN
142
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
SingleRAN
143
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-101 Number of HSDPA Users
Name Number of HSDPA Users
Description This KPI provides the mean, maximum and minimum 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
VS.HSDPA.UE.Max.Cell
Object CELL
Unit/Range None
Note None

3.7.5 Number of HSUPA Users
Table 3-102 Number of HSUPA Users
Name Number of HSUPA Users
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.
SingleRAN
144
Associated
Counters
VS.HSUPA.UE.Mean.Cell
VS.HSUPA.UE.Max.Cell
Object CELL
Unit/Range None
Note The KPI should be collected during busy hour.

3.7.6 Number of E-FACH Users
Table 3-103 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

3.7.7 Number of CS Over HSPA Users
Table 3-104 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
SingleRAN
145
Unit/Range None

3.7.8 Number of HSDPA 64QAM Users
Table 3-105 Number of HSDPA 64QAM Users
Name Mean Number of HSDPA 64QAM Users
Description This KPI provides the average number of HSDPA 64QAM UEs in an 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

3.7.9 Number of HSDPA MIMO Users
Table 3-106 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

SingleRAN
146
3.7.10 Number of HSUPA 16QAM users
Table 3-107 Number of HSUPA 16QAM users
Name Mean Number of HSUPA 16QAM users
Description This KPI provides the average number of HSUPA 16QAM UEs in an 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

3.7.11 Number of HSDPA MIMO64QAM Users
Table 3-108 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

3.7.12 Number of MBMS Users
SingleRAN
147
Table 3-109 Number of MBMS Users
Name Mean Number of MBMS Users
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

3.7.13 HSDPA RLC Traffic Volume
Table 3-110 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.
Associated
Counters
VS.HSDPA.MeanChThroughput.TotalBytes
Object CELL
Unit/Range byte
SingleRAN
148
Note None

3.7.14 HSUPA RLC Traffic Volume
Table 3-111 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.15 R99 Service UL Traffic Volume
Table 3-112 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.
SingleRAN
149
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.16 R99 Service DL Traffic Volume
SingleRAN
150
Table 3-113 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.
SingleRAN
151
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
Object CELL
Unit/Range bit
Note None
SingleRAN
152

3.7.17 E-FACH Traffic Volume
Table 3-114 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
SingleRAN
153

Singleran Kpi Reference (v900r013c00 - 03) (PDF) - en

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Singleran Kpi Reference (v900r013c00 - 03) (PDF) - en

Încărcat de

Drepturi de autor:

Formate disponibile

SingleRAN

S-ar putea să vă placă și