RAN16.0
KPI Reference Issue
02
Date
2014-03-28
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd. Address:
Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China
Website:
http://www.huawei.com
Email:
[email protected]
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
i
RAN16.0 KPI Reference
About This Document
About This Document Purpose This document describes the RAN KPI and the counters for KPI calculation. The definition of KPI is derived based on the commercial network requirement.
Product Versions The following table lists the product versions included in this document. Product Name
Product Version
BSC6910
V100R015C00
BSC6900
V900R015C00
BTS3900
V100R008C00
BTS3900A
The mapping single-mode base station version is:
BTS3900L
NodeB: V200R015C00
BTS3900C BTS3900AL DBS3900 BTS3812AE
NodeB: V100R015C00
BTS3812A BTS3812E DBS3800
Intended Audience This document is intended for: Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
ii
RAN16.0 KPI Reference
About This Document
l
Network planning engineers
l
Field engineers
l
System engineers
Organization 1 Changes in the RAN KPI Reference This chapter describes the changes made in the RAN KPI Reference. 2 Accessibility Accessibility is the ability of a user to obtain the requested service from the system. RRC connection and RAB setup are the main procedures of accessibility. 3 Availability Availability KPIs mainly indicate the utilization for several kinds of network resources such as Radio, bandwidth or CPU Load. 4 Coverage Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an RNC or a cluster. 5 Mobility Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or service mode changing in difference scenarios. 6 Retainability Retainability is defined as the ability of a user to retain its requested service for the required duration once connected. The RNC level KPIs can be calculated by aggregating all the cell counters and Iur counters. 7 Service Integrity Service Integrity KPIs mainly indicate the service capabilities for PS/HSPA throughput during busy hours in each cell and the service UL Average BLER for evaluating the UL BLER value of services in each cell. 8 Traffic Traffic-related KPIs are used to check the circulated traffic such as CS Equivalent Erlang, PS Traffic, and Mean UE number for various kinds of services in an RNC or a Cluster.
Conventions Symbol Conventions The symbols that may be found in this document are defined as follows. Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iii
RAN16.0 KPI Reference
About This Document
Symbol
Description Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results. NOTICE is used to address practices not related to personal injury. Calls attention to important information, best practices and tips. NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.
General Conventions The general conventions that may be found in this document are defined as follows. Convention
Description
Times New Roman
Normal paragraphs are in Times New Roman.
Boldface
Names of files, directories, folders, and users are in boldface. For example, log in as user root.
Italic
Book titles are in italics.
Courier New
Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows.
Issue 02 (2014-03-28)
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
iv
RAN16.0 KPI Reference
About This Document
Convention
Description
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention
Description
Boldface
Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.
>
Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format
Description
Key
Press the key. For example, press Enter and press Tab.
Key 1+Key 2
Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently.
Key 1, Key 2
Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
v
RAN16.0 KPI Reference
Issue 02 (2014-03-28)
About This Document
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.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
vi
RAN16.0 KPI Reference
Contents
Contents About This Document.....................................................................................................................ii 1 Changes in the RAN KPI Reference..........................................................................................1 2 Accessibility....................................................................................................................................4 2.1 IU Paging Success Ratio.................................................................................................................................................5 2.2 RRC Setup Success Ratio...............................................................................................................................................5 2.3 Radio Access Success Ratio...........................................................................................................................................8 2.4 PS Radio Access Success Ratio....................................................................................................................................10 2.5 CS Radio Access Success Ratio...................................................................................................................................11 2.6 AMR RAB Setup Success Ratio..................................................................................................................................12 2.7 VP RAB Setup Success Ratio......................................................................................................................................13 2.8 CS RAB Setup Success Ratio.......................................................................................................................................14 2.9 CS+PS Combined Service RAB Setup Success Rate...................................................................................................15 2.10 PS+PS Combined Service RAB Setup Success Rate.................................................................................................16 2.11 PS RAB Setup Success Ratio.....................................................................................................................................16 2.12 HSDPA RAB Setup Success Ratio............................................................................................................................18 2.13 HSUPA RAB Setup Success Ratio............................................................................................................................18 2.14 PS E-FACH RAB Setup Success Ratio......................................................................................................................19 2.15 CS over HSPA RAB Setup Success Ratio.................................................................................................................20 2.16 HSDPA 64QAM RAB Setup Success Ratio..............................................................................................................20 2.17 HSDPA MIMO RAB Setup Success Ratio................................................................................................................21 2.18 HSDPA DC RAB Setup Success Ratio......................................................................................................................22 2.19 HSDPA MIMO64QAM RAB Setup Success Ratio...................................................................................................22 2.20 PTM Channel Setup Success Ratio............................................................................................................................23 2.21 PTP Channel Setup Success Ratio..............................................................................................................................24 2.22 RRC Congestion Ratio...............................................................................................................................................24 2.23 CS RAB Congestion Ratio.........................................................................................................................................25 2.24 PS RAB Congestion Ratio..........................................................................................................................................26 2.25 PS R99 RAB Setup Success Rate...............................................................................................................................27 2.26 WB AMR RAB Setup Success Rate..........................................................................................................................28
3 Availability...................................................................................................................................29 3.1 Worst Cell Ratio...........................................................................................................................................................30 Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
vii
RAN16.0 KPI Reference
Contents
3.2 Paging Congestion Ratio..............................................................................................................................................30 3.3 Call Admission Refused Ratio.....................................................................................................................................31 3.4 Congested Cell Ratio....................................................................................................................................................32 3.5 Radio Network Unavailability Ratio............................................................................................................................33 3.6 Average CPU Load.......................................................................................................................................................34 3.7 Iub Port Available Bandwidth Utilizing Ratio (UL)....................................................................................................34 3.8 Iub Port Available Bandwidth Utilizing Ratio (DL)....................................................................................................35 3.9 Cell Unavailability duration.........................................................................................................................................36 3.10 HSDPA Unavailability duration.................................................................................................................................37 3.11 HSUPA Unavailability duration.................................................................................................................................37 3.12 CE Consumption for a NodeB Cell............................................................................................................................37 3.13 Hardware Configured CE for a NodeB......................................................................................................................38 3.14 Shared Group Configured License CE for a NodeB..................................................................................................38 3.15 Shared Group License CE Consumption for a NodeB...............................................................................................39 3.16 License Group Configured CE for a NodeB..............................................................................................................39 3.17 License Group CE Consumption for a NodeB...........................................................................................................40 3.18 RTWP (Received Total Wideband Power).................................................................................................................40 3.19 TCP (Transmitted Carrier Power)..............................................................................................................................41 3.20 R99 Code Utilization..................................................................................................................................................42 3.21 Number of Codes Used by HS-PDSCHs....................................................................................................................42 3.22 HSDPA Efficiency.....................................................................................................................................................43
4 Coverage........................................................................................................................................44 4.1 UL Interference Cell Ratio...........................................................................................................................................45 4.2 Soft Handover Overhead..............................................................................................................................................45
5 Mobility.........................................................................................................................................48 5.1 Soft Handover Success Ratio.......................................................................................................................................49 5.2 Softer Handover Success Ratio....................................................................................................................................49 5.3 AMR Soft Handover Success Ratio.............................................................................................................................50 5.4 CS64 Soft Handover Success Ratio..............................................................................................................................51 5.5 PS Soft Handover Success Ratio..................................................................................................................................51 5.6 Intra-frequency Hard Handover Success Ratio............................................................................................................52 5.7 Inter-frequency Hard Handover Success Ratio............................................................................................................53 5.8 Service Cell Change Success Ratio with SHO (H2H).................................................................................................54 5.9 H2H Intra-Frequency Hard Handover Success Ratio...................................................................................................54 5.10 H2H Inter-Frequency Hard Handover Success Ratio.................................................................................................56 5.11 H2D Intra-Frequency Hard Handover Success Ratio.................................................................................................57 5.12 H2D Inter-Frequency Hard Handover Success Ratio.................................................................................................57 5.13 E2D Intra-Frequency Hard Handover Success Ratio.................................................................................................58 5.14 H2D Channel Switch Success Ratio...........................................................................................................................59 5.15 D2H Channel Switch Success Ratio...........................................................................................................................60 5.16 CS W2G Inter-RAT Handover Out Success Ratio.....................................................................................................61 Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
viii
RAN16.0 KPI Reference
Contents
5.17 PS W2G Inter-RAT Handover Out Success Ratio.....................................................................................................61 5.18 PS G2W Inter-RAT Handover In Success Ratio........................................................................................................62 5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio............................................................................................63 5.20 SRNC Relocation Success Ratio................................................................................................................................64 5.21 TRNC Relocation Success Ratio................................................................................................................................65 5.22 E-DCH Soft Handover Success Ratio........................................................................................................................66 5.23 E-DCH Cell Change Success Ratio with SHO...........................................................................................................66 5.24 E-DCH Cell Change Success Ratio with Inter-HHO.................................................................................................67 5.25 E2D Channel Switch Success Ratio...........................................................................................................................68 5.26 D2E Channel Switch Success Ratio...........................................................................................................................69 5.27 E2D Handover Success Ratio with Inter HHO..........................................................................................................70 5.28 HSUPA W2G Inter-RAT Handover Out Success Ratio............................................................................................71 5.29 MBMS Service Mode Switch Success Ratio.............................................................................................................72 5.30 CS Inter-Frequency Hard Handover Success Rate.....................................................................................................72 5.31 PS Inter-Frequency Hard Handover Success Rate.....................................................................................................73
6 Retainability.................................................................................................................................74 6.1 CS Service Drop Ratio.................................................................................................................................................75 6.2 CS Call Drop Rate in CS+PS Combined Services.......................................................................................................75 6.3 PS Call Drop Rate in CS+PS Combined Services........................................................................................................76 6.4 AMR Call Drop Ratio...................................................................................................................................................77 6.5 WB AMR Call Drop Rate............................................................................................................................................78 6.6 VP Call Drop Ratio.......................................................................................................................................................78 6.7 AMR Traffic Drop Ratio..............................................................................................................................................79 6.8 VP Traffic Drop Ratio..................................................................................................................................................81 6.9 PS Call Drop Ratio.......................................................................................................................................................81 6.10 PS Call Drop Ratio (PCH)..........................................................................................................................................82 6.11 PS Call Drop Ratio (PCH & Combined Service).......................................................................................................85 6.12 PS R99 Call Drop Ratio..............................................................................................................................................87 6.13 PS R99 Call Drop Ratio (PCH)..................................................................................................................................88 6.14 PS BE Call Drop Ratio...............................................................................................................................................89 6.15 HSDPA Call Drop Ratio.............................................................................................................................................90 6.16 HSDPA Call Drop Ratio (PCH).................................................................................................................................92 6.17 HSUPA Call Drop Ratio.............................................................................................................................................93 6.18 HSUPA Call Drop Ratio (PCH).................................................................................................................................94 6.19 MBMS Service PTP drop Ratio.................................................................................................................................95 6.20 DC-HSDPA Call Drop Ratio......................................................................................................................................96 6.21 HSDPA 64QAM Call Drop Ratio..............................................................................................................................98 6.22 HSDPA MIMO Call Drop Ratio................................................................................................................................99 6.23 HSDPA MIMO+64QAM Call Drop Ratio...............................................................................................................100
7 Service Integrity.........................................................................................................................102 7.1 Average UL Throughput for PS R99 Service.............................................................................................................103 Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
ix
RAN16.0 KPI Reference
Contents
7.2 Average DL Throughput for PS R99 Service.............................................................................................................104 7.3 Average UL BLER for CS Service.............................................................................................................................106 7.4 Average UL BLER for PS Service.............................................................................................................................106 7.5 HSDPA Throughput...................................................................................................................................................107 7.6 HSUPA Throughput...................................................................................................................................................109 7.7 PS UL Throughput of RNC........................................................................................................................................110 7.8 PS DL Throughput of RNC........................................................................................................................................111 7.9 MBMS Service Throughput.......................................................................................................................................112
8 Traffic...........................................................................................................................................113 8.1 CS Equivalent Erlang of RNC....................................................................................................................................114 8.2 Number of CS Users...................................................................................................................................................114 8.3 Number of PS R99 Users............................................................................................................................................115 8.4 Number of HSDPA Users...........................................................................................................................................120 8.5 Number of HSUPA Users...........................................................................................................................................120 8.6 Number of E-FACH Users.........................................................................................................................................121 8.7 Number of E-RACH Users.........................................................................................................................................121 8.8 Number of CS Over HSPA Users...............................................................................................................................122 8.9 Number of HSDPA 64QAM Users............................................................................................................................122 8.10 Number of HSDPA MIMO Users............................................................................................................................123 8.11 Number of HSUPA 16QAM users...........................................................................................................................123 8.12 Number of HSDPA MIMO64QAM Users...............................................................................................................124 8.13 Number of MBMS Users..........................................................................................................................................124 8.14 HSDPA RLC Traffic Volume..................................................................................................................................125 8.15 HSUPA RLC Traffic Volume..................................................................................................................................126 8.16 R99 Service UL Traffic Volume..............................................................................................................................126 8.17 R99 Service DL Traffic Volume..............................................................................................................................127 8.18 E-FACH Traffic Volume..........................................................................................................................................130 8.19 E-RACH Traffic Volume.........................................................................................................................................130 8.20 Average Number of DC-HSDPA Users...................................................................................................................131
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
x
RAN16.0 KPI Reference
1 Changes in the RAN KPI Reference
1
Changes in the RAN KPI Reference
This chapter describes the changes made in the RAN KPI Reference.
02 (2014-03-28) This is the Draft A release of RAN15.0. Compared with Issue RAN15.0 01 (2013-05-04), this issue includes the new topic: l
8.7 Number of E-RACH Users
l
8.19 E-RACH Traffic Volume
l
6.20 DC-HSDPA Call Drop Ratio
l
6.21 HSDPA 64QAM Call Drop Ratio
l
6.22 HSDPA MIMO Call Drop Ratio
l
6.23 HSDPA MIMO+64QAM Call Drop Ratio
l
8.20 Average Number of DC-HSDPA Users
Compared with Issue RAN15.0 01 (2013-05-04), this issue incorporates the following changes:
Issue 02 (2014-03-28)
Content
Description
6.10 PS Call Drop Ratio (PCH)
Modified the formula by adding counters VS.DCCC.Succ.F2U and VS.DCCC.Succ.D2U to the denominator. The modified formula is more accurate according to the KPI description.
6.11 PS Call Drop Ratio (PCH & Combined Service)
Modified the formula by adding counters VS.DCCC.Succ.F2U and VS.DCCC.Succ.D2U to the denominator. The modified formula is more accurate according to the KPI description.
7.1 Average UL Throughput for PS R99 Service
Added the KPI "Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)."
7.2 Average DL Throughput for PS R99 Service
Added the KPI "Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)."
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
1
RAN16.0 KPI Reference
1 Changes in the RAN KPI Reference
Content
Description
7.5 HSDPA Throughput
Added the formula of calculating HSDPA throughput for 3900 series base stations in Note.
7.6 HSUPA Throughput
Modified the formula of calculating "Mean Throughput for One HSUPA Cell" in Note. In earlier KPI references, this KPI is measured at the MAC-d layer. In this version, this KPI is measured at the MAC-e/i layer over the air interface and therefore more accurate for UEs.
Compared with Issue RAN15.0 01 (2013-05-04), this issue does not exclude any topics.
01 (2013-05-04) This is the first commercial release of RAN15.0. Compared with issue RAN15.0 Draft A (2013-01-30), this issue includes the new topic: l
6.11 PS Call Drop Ratio (PCH & Combined Service)
Compared with issue RAN15.0 Draft A (2013-01-30), this issue incorporates the following changes. Content
Description
2.20 PTM Channel Setup Success Ratio
Removed the note that these KPIs apply only to the BSC6900 because they can apply to the BSC6910 now.
2.21 PTP Channel Setup Success Ratio 5.29 MBMS Service Mode Switch Success Ratio 6.19 MBMS Service PTP drop Ratio 7.9 MBMS Service Throughput 8.13 Number of MBMS Users 5.16 CS W2G Inter-RAT Handover Out Success Ratio 5.17 PS W2G Inter-RAT Handover Out Success Ratio
Deducted the number of inter-RAT handover cancellations from the denominator of the formula for calculating the cell-level KPI.
Compared with issue RAN15.0 Draft A (2013-01-30), this issue does not exclude any topics.
Draft A (2013-01-30) This is the Draft A release of RAN15.0. Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
2
RAN16.0 KPI Reference
1 Changes in the RAN KPI Reference
Compared with issue RAN14.0 02 (2012-06-30)), this issue includes the new topic: l
The BSC6910 is introduced in RAN15.0. This document applies to the BSC6900 and BSC6910.
Compared with issue RAN14.0 02 (2012-06-30), this issue incorporates the following changes: Content
Description
3.6 Average CPU Load
Added a formula for BSC6910 in the KPI.
2.20 PTM Channel Setup Success Ratio
Added a note that these KPI were only for BSC6900.
2.21 PTP Channel Setup Success Ratio 5.29 MBMS Service Mode Switch Success Ratio 6.19 MBMS Service PTP drop Ratio 7.9 MBMS Service Throughput 8.13 Number of MBMS Users
Compared with issue RAN14.0 02 (2012-06-30), this issue does not exclude any topics.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
3
RAN16.0 KPI Reference
2 Accessibility
2
Accessibility
About This Chapter Accessibility is the ability of a user to obtain the requested service from the system. RRC connection and RAB setup are the main procedures of accessibility.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
4
RAN16.0 KPI Reference
2 Accessibility
2.1 IU Paging Success Ratio Table 2-1 IU Paging Success Ratio Name
IU Paging Success Ratio
Formula
Description
This KPI is used to check the successful paging responses to the pagings from the Core Network (CN) in one RNC. The Attempt Paging Procedure starts when the CN sends a PAGING message to the RNC, and is complete when the UE in idle mode receives the PAGING TYPE 1 message from the RNC. The Successful Paging Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE in idle mode.
Associated Counters
IU Paging Success Ratio =
Object
RNC
Unit/Range
%
Note
None
(VS.RANAP.Paging.Succ.IdleUE/VS.RANAP.Paging.Att.IdleUE) x 100%
2.2 RRC Setup Success Ratio Table 2-2 RRC Setup Success Ratio Name
RRC Setup Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
5
RAN16.0 KPI Reference
2 Accessibility
Description
Description of RRC Setup Success Ratio for service requests: l The RRC Connection Attempt for service Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE. The message contains information about one of the following service types requested by the UE: Conversational Call, Streaming Call, Background Call, Interactive Call, Originating Subscribed Traffic Call, Emergency Call, High Priority Signaling, Low Priority Signaling, Cause Unknown, Call Re-Establishment. For details on the reason types, see section 10.3.3.11 in 3GPP TS 25.331. l The RRC Setup Success for Service Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE. Description of RRC Setup Success Ratio for other causes: l RRC Connection Attempt for Other reasons Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE. The message contains information about one of the following service types requested by the UE: Inter-RAT cell re-selection, Inter-RAT cell change order, Registration and Detach. l The RRC Setup Success for Other reasons Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
6
RAN16.0 KPI Reference
2 Accessibility
Associated Counters
l RRC Setup Success Ratio (Cell.Service) = [(RRC.SuccConnEstab.OrgConvCall+ RRC.SuccConnEstab.OrgStrCall+ RRC.SuccConnEstab.OrgInterCall+ RRC.SuccConnEstab.OrgBkgCall+ RRC.SuccConnEstab.OrgSubCall+ RRC.SuccConnEstab.TmConvCall+ RRC.SuccConnEstab.TmStrCall+ RRC.SuccConnEstab.TmItrCall+ RRC.SuccConnEstab.TmBkgCall+ RRC.SuccConnEstab.EmgCall+ RRC.SuccConnEstab.Unkown+ RRC.SuccConnEstab.OrgHhPrSig+ RRC.SuccConnEstab.OrgLwPrSig+ RRC.SuccConnEstab.CallReEst+ RRC.SuccConnEstab.TmHhPrSig+ RRC.SuccConnEstab.TmLwPrSig)/ (RRC.AttConnEstab.OrgConvCall+ RRC.AttConnEstab.OrgStrCall+ RRC.AttConnEstab.OrgInterCall + RRC.AttConnEstab.OrgBkgCall+ RRC.AttConnEstab.OrgSubCall+ RRC.AttConnEstab.TmConvCall+ RRC.AttConnEstab.TmStrCall+ RRC.AttConnEstab.TmInterCall+ RRC.AttConnEstab.TmBkgCall+ RRC.AttConnEstab.EmgCall+ RRC.AttConnEstab.Unknown+ RRC.AttConnEstab.OrgHhPrSig+ RRC.AttConnEstab.OrgLwPrSig+ RRC.AttConnEstab.CallReEst+ RRC.AttConnEstab.TmHhPrSig+ RRC.AttConnEstab.TmLwPrSig )] x 100% l RRC Setup Success Ratio (Cell.Other) = [(RRC.SuccConnEstab.IRATCelRes+ RRC.SuccConnEstab.IRATCCO+ RRC.SuccConnEstab.Reg+ RRC.SuccConnEstab.Detach)/ (RRC.AttConnEstab.IRATCelRes+
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
7
RAN16.0 KPI Reference
2 Accessibility
RRC.AttConnEstab.IRATCCO+ RRC.AttConnEstab.Reg+ RRC.AttConnEstab.Detach)] x 100% Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters. The following counters provide the number of RRC connection setup requests that are resent after the first RRC connection setup request of the UE is rejected due to resource insufficiency. You can subtract these counters from the denominator of the formula to increase the value of this KPI: l RRC.AttConnEstab.Rep.OrgConvCall l RRC.AttConnEstab.Rep.OrgStrCall l RRC.AttConnEstab.Rep.OrgInterCall l RRC.AttConnEstab.Rep.OrgBkgCall l RRC.AttConnEstab.Rep.TmConvCall l RRC.AttConnEstab.Rep.TmStrCall l RRC.AttConnEstab.Rep.TmInterCall l RRC.AttConnEstab.Rep.TmBkgCall l RRC.AttConnEstab.Rep.OrgSubCall l RRC.AttConnEstab.Rep.EmgCall l RRC.AttConnEstab.Rep.IRATCelRes l RRC.AttConnEstab.Rep.IRATCCO l RRC.AttConnEstab.Rep.Reg l RRC.AttConnEstab.Rep.Detach l RRC.AttConnEstab.Rep.OrgHhPrSig l RRC.AttConnEstab.Rep.OrgLwPrSig l RRC.AttConnEstab.Rep.CallReEst l RRC.AttConnEstab.Rep.TmHhPrSig l RRC.AttConnEstab.Rep.TmLwPrSig l RRC.AttConnEstab.Rep.Unknown The formula of CS and PS radio access success ratio refer to the 2.4 PS Radio Access Success Ratio and 2.5 CS Radio Access Success Ratio directly.
2.3 Radio Access Success Ratio Table 2-3 Radio Access Success Ratio Name Issue 02 (2014-03-28)
Radio Access Success Ratio Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
8
RAN16.0 KPI Reference
2 Accessibility
Formula
Description
This KPI is used to check the Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not provided in this call setup procedure. Description of the RAB Setup Attempt Procedure and the RAB Setup Success Procedure: The RAB Setup Attempt Procedure starts when the CN sends an RAB ASSIGNMENT REQUEST message to the RNC. The message contains information about one of the following service types: CS Conversational RAB Establishments, CS Streaming RAB Establishments, PS Conversational RAB Establishment, PS Background RAB Establishments, PS Interactive RAB Establishments, PS Streaming RAB Establishments. The RAB Setup Attempt Procedure is complete When the RNC receives an RAB ASSIGNMENT REQUEST message from the CN. The RAB Setup Success Procedure is complete when the RNC sends to the CN an RAB ASSIGNMENT RESPONSE message.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
9
RAN16.0 KPI Reference
2 Accessibility
Associated Counters
l Radio Access Success Ratio (Cell) = RRC Setup Success Ratio (Cell.Service) x {[(VS.RAB.SuccEstabCS.Conv + VS.RAB.SuccEstabCS.Str) + (VS.RAB.SuccEstabPS.Conv + VS.RAB.SuccEstabPS.Str + VS.RAB.SuccEstabPS.Int + VS.RAB.SuccEstabPS.Bkg)]/ [(VS.RAB.AttEstabCS.Conv + VS.RAB.AttEstabCS.Str) + (VS.RAB.AttEstabPS.Conv + VS.RAB.AttEstabPS.Str + VS.RAB.AttEstabPS.Int + VS.RAB.AttEstabPS.Bkg)]} x 100% l Radio Access Success Ratio (RNC)= RRC Setup Success Ratio (Cell.Service) x {[(VS.RAB.SuccEstabCS.Conv.RNC+ VS.RAB.SuccEstabCS.Str.RNC)+ (VS.RAB.SuccEstabPS.Conv.RNC+ VS.RAB.SuccEstabPS.Str.RNC + VS.RAB.SuccEstabPS.Int.RNC + VS.RAB.SuccEstabPS.Bkg.RNC)]/ [(VS.RAB.AttEstabCS.Conv.RNC + VS.RAB.AttEstabCS.Str.RNC) + (VS.RAB.AttEstabPS.Conv.RNC + VS.RAB.AttEstabPS.Str.RNC + VS.RAB.AttEstabPS.Int.RNC + VS.RAB.AttEstabPS.Bkg.RNC)]} x 100%
Object
CELL, RNC
Unit/Range
%
Note
None
2.4 PS Radio Access Success Ratio Table 2-4 PS Radio Access Success Ratio Name
Issue 02 (2014-03-28)
PS Radio Access Success Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
10
RAN16.0 KPI Reference
2 Accessibility
Formula
Description
This KPI is used to check the PS Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not provided in this call setup procedure. The PS RRC Setup Attempt Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE. The message contains information about one of the following service types: Originating Interactive Call, Terminating Interactive Call, Originating Background Call, Terminating Background Call. The PS RRC Setup Success Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE.
Associated Counters
l PS Radio Access Success Ratio (Cell) = [(RRC.SuccConnEstab.OrgBkgCall + RRC.SuccConnEstab.OrgInterCall + RRC.SuccConnEstab.TmBkgCall + RRC.SuccConnEstab.TmItrCall)/ (RRC.AttConnEstab.OrgBkgCall + RRC.AttConnEstab.OrgInterCall + RRC.AttConnEstab.TmBkgCall + RRC.AttConnEstab.TmInterCall )] x PS RAB Setup Success Ratio (Cell) x 100% l PS Radio Access Success Ratio (RNC) = [(RRC.SuccConnEstab.OrgBkgCall + RRC.SuccConnEstab.OrgInterCall + RRC.SuccConnEstab.TmBkgCall + RRC.SuccConnEstab.TmItrCall)/ (RRC.AttConnEstab.OrgBkgCall + RRC.AttConnEstab.OrgInterCall + RRC.AttConnEstab.TmBkgCall + RRC.AttConnEstab.TmInterCall)] x PS RAB Setup Success Ratio (RNC) x 100%
Object
CELL, RNC
Unit/Range
%
Note
None
2.5 CS Radio Access Success Ratio Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
11
RAN16.0 KPI Reference
2 Accessibility
Table 2-5 CS Radio Access Success Ratio Name
CS Radio Access Success Ratio
Formula
Description
This KPI is used to check the Radio Access Success Ratio. The details of the Access Failures caused by the SCCP congestion are not provided in this call setup procedure. The CS RRC Setup Attempt Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE.The message contains information about one of the following service types: Originating Conversational Call, Terminating Conversational Call, Emergency Call. The CS RRC Setup Success Procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE.
Associated Counters
l CS Radio Access Success Ratio (Cell)= [(RRC.SuccConnEstab.OrgConvCall+ RRC.SuccConnEstab.TmConvCall+ RRC.SuccConnEstab.EmgCall)/ (RRC.AttConnEstab.OrgConvCall+ RRC.AttConnEstab.TmConvCall+ RRC.AttConnEstab.EmgCall)] x CS RAB Setup Success Ratio (Cell) x 100% l CS Radio Access Success Ratio (RNC)= [(RRC.SuccConnEstab.OrgConvCall+ RRC.SuccConnEstab.TmConvCall+ RRC.SuccConnEstab.EmgCall)/ (RRC.AttConnEstab.OrgConvCall+ RRC.AttConnEstab.TmConvCall+ RRC.AttConnEstab.EmgCall)] x CS RAB Setup Success Ratio (RNC) x 100%
Object
CELL,RNC
Unit/Range
%
Note
None
2.6 AMR RAB Setup Success Ratio
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
12
RAN16.0 KPI Reference
2 Accessibility
Table 2-6 AMR RAB Setup Success Ratio Name
AMR RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB Setup Success Ratio of the AMR Service. AMR RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for the CS narrow band AMR services. The AMR RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE message to the RNC. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.
Associated Counters
AMR RAB Setup Success Ratio(Cell) =
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters. If inter-RAT DRD is enabled during RAB setup, an AMR RAB setup is measured as an AMR RAB setup failure regardless of whether the DRD succeeds. As a result, the value of this KPI is smaller than actual value. Therefore, it is recommended that you add VS.IRATHO.SuccOutCS.DR to the numerator of the formula for calculating this KPI if inter-RAT DRD is enabled during RAB setup.
(VS.RAB.SuccEstabCS.AMR/VS.RAB.AttEstab.AMR) x 100%
2.7 VP RAB Setup Success Ratio Table 2-7 VP RAB Setup Success Ratio Name
VP RAB Setup Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
13
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the RAB setup success ratio of CS 64 Kbit/s conversational services in an RNC or a cluster. VP (Video Phone) RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN (The RAB type is for the CS 64 Kbit/s conversational service). VP RAB Setup Success Procedure starts when the UE sends a RADIO BEARER SETUP COMPLETE message to RNC. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.
Associated Counters
VP RAB Setup Success Ratio (Cell) =
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.RAB.SuccEstCS.Conv.64/VS.RAB.AttEstCS.Conv.64) x 100%
2.8 CS RAB Setup Success Ratio Table 2-8 CS RAB Setup Success Ratio Name
CS RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB Setup Success Ratio of all CS services in an RNC or a cluster. The CS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN in the CS domain.The message contains information about one of the following service types: Conversational Services, streaming Services. The CS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN in the CS domain.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
14
RAN16.0 KPI Reference
2 Accessibility
Associated Counters
l CS RAB Setup Success Ratio (Cell) = [(VS.RAB.SuccEstabCS.Conv+ VS.RAB.SuccEstabCS.Str)/ (VS.RAB.AttEstabCS.Conv+ VS.RAB.AttEstabCS.Str)] x 100% l CS RAB Setup Success Ratio (RNC) = [(VS.RAB.SuccEstabCS.Conv.RNC+ VS.RAB.SuccEstabCS.Str.RNC)/ (VS.RAB.AttEstabCS.Conv.RNC+ VS.RAB.AttEstabCS.Str.RNC)] x 100%
Object
CELL, RNC
Unit/Range
%
Note
If inter-RAT DRD is enabled during RAB setup, a CS RAB setup is measured as a CS RAB setup failure regardless of whether the DRD succeeds. As a result, the value of this KPI is smaller than actual value. Therefore, it is recommended that you add VS.IRATHO.SuccOutCS.DR to the numerator of the formula for calculating this KPI if inter-RAT DRD is enabled during RAB setup.
2.9 CS+PS Combined Service RAB Setup Success Rate Table 2-9 CS+PS Combined Service RAB Setup Success Rate Name
CS+PS Combined Service RAB Setup Success Rate
Formula
CS+PS Combined Service RAB Setup Success Rate = Number of successfully set up CS+PS combined service RABs x 100%/Number of CS +PS combined service RAB setup attempts
Description
This KPI provides the setup success rate of CS+PS combined services. Number of CS+PS combined service RAB setup attempts: When the RNC receives from the CN an RAB ASSIGNMENT REQUEST message and one or more RABs of the UE already exists in the cell, the RNC checks the RAB type carried in the message and determines the combined service type based on the existing RAB type of the UE. The number of CS+PS combined service RAB setup attempts is measured in the best cell that the UE camps on if the combined service type is CS+PS, CS+2PS, or CS+3PS. Number of successfully set up CS+PS combined service RABs: When the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE and one or more RABs of a UE already exists in the cell, the RNC checks the RAB type and determines the combined service type based on the existing RAB type of the UE. The number of successfully set up CS+PS combined service RABs is measured in the best cell that the UE camps on if the combined service type is CS+PS, CS+2PS, or CS+3PS.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
15
RAN16.0 KPI Reference
2 Accessibility
Associated Counters
CS+PS RAB Setup Success ratio=
Object
CELL
Unit/Range
%
Note
None
(VS.MultiRAB.SuccEstab.CSPS/VS.MultiRAB.AttEstab.CSPS) * 100%
2.10 PS+PS Combined Service RAB Setup Success Rate Table 2-10 PS+PS Combined Service RAB Setup Success Rate Name
PS+PS Combined Service RAB Setup Success Rate
Formula
PS+PS Combined Service RAB Setup Success Rate = Number of successfully set up PS+PS combined service RABs x 100%/Number of PS +PS combined service RAB setup attempts
Description
This KPI provides the setup success rate of PS+PS combined services. Number of PS+PS combined service RAB setup attempts: When the RNC receives from the CN an RAB ASSIGNMENT REQUEST message and one or more RABs of the UE already exists in the cell, the RNC checks the RAB type carried in the message and determines the combined service type based on the existing RAB type of the UE. The number of PS+PS combined service RAB setup attempts is measured in the best cell that the UE camps on if the combined service type is 2PS, 3PS, or 4PS. Number of successfully set up PS+PS combined service RABs: When the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN after receiving an RADIO BEARER SETUP COMPLETE message from the UE and one or more RABs of a UE already exists in the cell, the RNC checks the RAB type and determines the combined service type based on the existing RAB type of the UE. The number of successfully set up PS+PS combined service RABs is measured in the best cell that the UE camps on if the combined service type is 2PS, 3PS, or 4PS.
Associated Counters
PS+PS RAB Setup Success ratio=
Object
CELL
Unit/Range
%
Note
None
(VS.MultiRAB.SuccEstab.PSPS/VS.MultiRAB.AttEstab.PSPS)*100%
2.11 PS RAB Setup Success Ratio Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
16
RAN16.0 KPI Reference
2 Accessibility
Table 2-11 PS RAB Setup Success Ratio Name
PS RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB Setup Success Ratio of all PS services in an RNC or a cluster. The PS RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN in the PS domain, the message contains information about one of the following service types: Conversational services, Streaming services, Interactive Services, Background Services. The PS RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the SGSN in the PS domain.
Associated Counters
l PS RAB Setup Success Ratio (Cell) = [(VS.RAB.SuccEstabPS.Conv+ VS.RAB.SuccEstabPS.Str + VS.RAB.SuccEstabPS.Int + VS.RAB.SuccEstabPS.Bkg )/ (VS.RAB.AttEstabPS.Conv+ VS.RAB.AttEstabPS.Str + VS.RAB.AttEstabPS.Int + VS.RAB.AttEstabPS.Bkg )] x 100% l PS RAB Setup Success Ratio (RNC) = [(VS.RAB.SuccEstabPS.Bkg.RNC+ VS.RAB.SuccEstabPS.Str.RNC + VS.RAB.SuccEstabPS.Conv.RNC + VS.RAB.SuccEstabPS.Int.RNC )/ (VS.RAB.AttEstabPS.Conv.RNC+ VS.RAB.AttEstabPS.Bkg.RNC + VS.RAB.AttEstabPS.Int.RNC + VS.RAB.AttEstabPS.Str.RNC )] x 100%
Issue 02 (2014-03-28)
Object
CELL, RNC
Unit/Range
%
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
17
RAN16.0 KPI Reference
2 Accessibility
2.12 HSDPA RAB Setup Success Ratio Table 2-12 HSDPA RAB Setup Success Ratio Name
HSDPA RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB Setup Success Ratio of PS services that are carried by HSDPA in a cluster. The HSDPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service. The HSDPA RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN.
Associated Counters
HSDPA RAB Setup Success Ratio (Cell) =
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.HSDPA.RAB.SuccEstab/VS.HSDPA.RAB.AttEstab) x 100%
2.13 HSUPA RAB Setup Success Ratio Table 2-13 HSUPA RAB Setup Success Ratio Name
HSUPA RAB Setup Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
18
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the RAB Setup Success Ratio of the HSUPA service in an RNC or a cluster. The HSUPA RAB Setup Success Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The HSUPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSUPA service.
Associated Counters
HSUPA RAB Setup Success Ratio (Cell) =
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.HSUPA.RAB.SuccEstab/VS.HSUPA.RAB.AttEstab) x 100%
2.14 PS E-FACH RAB Setup Success Ratio Table 2-14 PS E-FACH RAB Setup Success Ratio Name
PS E-FACH RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB setup success ratio of the E-FACH service in an RNC or a cluster. Successful PS RAB Setup on E-FACH Procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the SGSN in the PS domain. The procedure of Attempts of PS RAB Setup on E-FACH is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN, and the PS service is established on the EFACH.
Issue 02 (2014-03-28)
Associated Counters
PS E-FACH RAB Setup Success Ratio (Cell) =
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.RAB.SuccEstPS.EFACH/VS.RAB.AttEstPS.EFACH) x 100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
19
RAN16.0 KPI Reference
2 Accessibility
2.15 CS over HSPA RAB Setup Success Ratio Table 2-15 CS over HSPA RAB Setup Success Ratio Name
CS over HSPA RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB setup success ratio of the CS over HSPA service. When the RAB is set for the CS conversational service and is carried on an HSPA channel, the CS over HSPA RAB Setup Success Procedure starts when the RNC receives an RADIO BEARER SETUP COMPLETE message from UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to CN. The CS over HSPA RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN, and the RAB is set up on an HSPA channel.
Associated Counters
CS over HSPA RAB Setup Success Ratio (Cell) = (VS.HSPA.RAB.SuccEstab.CS.Conv/ VS.HSPA.RAB.AttEstab.CS.Conv) x 100%
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
2.16 HSDPA 64QAM RAB Setup Success Ratio Table 2-16 HSDPA 64QAM RAB Setup Success Ratio Name
HSDPA 64QAM RAB Setup Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
20
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the RAB Setup Success Ratio of the HSDPA 64QAM service in an RNC or a cluster. The HSDPA 64 QAM RAB Setup Success Procedure starts when the RNC receives an RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The HSDPA 64QAM RAB Setup Attempt Procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service using 64QAM.
Associated Counters
HSDPA 64QAM RAB Setup Success Ratio (Cell) = (VS.HSDPA.RAB.64QAM.SuccEstab/VS.HSDPA.RAB. 64QAM.AttEstab) x 100%
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
2.17 HSDPA MIMO RAB Setup Success Ratio Table 2-17 HSDPA MIMO RAB Setup Success Ratio Name
HSDPA MIMO RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO service in an RNC or a cluster. The HSDPA MIMO RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The HSDPA MIMO RAB Setup Attempt procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service using MIMO.
Issue 02 (2014-03-28)
Associated Counters
HSDPA MIMO RAB Setup Success Ratio=
Object
CELL
Unit/Range
%
(VS.HSDPA.RAB.MIMO.SuccEstab/VS.HSDPA.RAB.MIMO.AttEstab) x 100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
21
RAN16.0 KPI Reference
2 Accessibility
Note
The RNC level KPI is calculated by aggregating all the cell counters.
2.18 HSDPA DC RAB Setup Success Ratio Table 2-18 HSDPA DC RAB Setup Success Ratio Name
HSDPA DC RAB Setup Success Ratio
Formula
Description
This KPI is used to check the RAB Setup Success Ratio of the HSDPA DC RAB service in an RNC or a cluster. The HSDPA DC RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The HSDPA DC RAB Setup Attempt procedure is complete when the RNC receives from the CN an RAB ASSIGNMENT REQUEST message for setting up the HSDPA service using DC-HSDPA.
Associated Counters
HSDPA DC RAB Setup Success Ratio=
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.HSDPA.RAB.DC.SuccEstab/VS.HSDPA.RAB.DC.AttEstab) x 100%
2.19 HSDPA MIMO64QAM RAB Setup Success Ratio Table 2-19 HSDPA MIMO64QAM RAB Setup Success Ratio Name
HSDPA MIMO64QAM RAB Setup Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
22
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the RAB Setup Success Ratio of the HSDPA MIMO 64QAM service in an RNC or a cluster. The HSDPA MIMO 64QAM RAB Setup Success procedure starts when the RNC receives a RADIO BEARER SETUP COMPLETE message from the UE. This procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The HSDPA MIMO 64QAM RAB Setup Attempt procedure is complete when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN for setting up the HSDPA service using MIMO+64QAM.
Associated Counters
HSDPA MIMO64QAM RAB Setup Success Ratio=
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.HSDPA.RAB.MIMO64QAM.SuccEstab/ VS.HSDPA.RAB.MIMO64QAM.AttEstab) x 100%
2.20 PTM Channel Setup Success Ratio Table 2-20 PTM Channel Setup Success Ratio Name
PTM Channel Setup Success Ratio
Formula
Description
This KPI is used to check the Channel Setup Success Rate of MBMS service in PTM mode. When the RB of PTM MBMS service is successfully set up, the PTM Channel RB is successfully set up. When the RNC initiates the setup of PTM MBMS service, the PTM Channel RB Setup Attempt.
Issue 02 (2014-03-28)
Associated Counters
PTM Channel Setup Success Ratio=
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.MBMS.RB.PTM.SuccEstab/ VS.MBMS.RB.PTM.AttEstab)*100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
23
RAN16.0 KPI Reference
2 Accessibility
2.21 PTP Channel Setup Success Ratio Table 2-21 PTP Channel Setup Success Ratio Name
PTP Channel Setup Success Ratio
Formula
Description
This KPI is used to check the Channel Setup Success Rate of MBMS service in PTP mode. The PTP Channel RB Setup Success Procedure is as follows: When the UE initiates a request to set up an MBMS, the RNC, in response to the UE's request, initiates PTP RB setup, and the PTP RB is successfully set up. The PTP Channel RB Setup Attempt Procedure: The RNC initiates PTP RB setup after the UE initiates an MBMS setup request.
Associated Counters
PTP Channel Setup Success Ratio=
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
(VS.MBMS.RB.PTP.SuccEstab/ VS.MBMS.RB.PTP.AttEstab)*100%
2.22 RRC Congestion Ratio Table 2-22 RRC Congestion Ratio Name
RRC Congestion Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
24
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the RRC Congestion Ratio in a cluster. After receiving an RRC CONNECTION REQUEST message from the UE, the RNC initiates admission procedures for resources of code, power, CE, and Iub bandwidth. If the resource admission fails, the RRC Setup Failure due to Congestion procedure is complete when the RNC sends an RRC CONNECTION REJECT message to the UE. The RRC Connection Attempt for service Procedure is complete when the RNC receives an RRC CONNECTION REQUEST message from the UE.
Associated Counters
RRC Congestion Ratio= [(VS.RRC.Rej.ULPower.Cong+ VS.RRC.Rej.DLPower.Cong + VS.RRC.Rej.ULIUBBand.Cong + VS.RRC.Rej.DLIUBBand.Cong + VS.RRC.Rej.ULCE.Cong + VS.RRC.Rej.DLCE.Cong + VS.RRC.Rej.Code.Cong )/ VS.RRC.AttConnEstab.Sum ] x 100%
Object
CELL
Unit/Range
%
Note
None
2.23 CS RAB Congestion Ratio Table 2-23 CS RAB Congestion Ratio Name
CS RAB Congestion Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
25
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the CS RAB Congestion Ratio in a cluster. The CS RAB Setup Fails due to Congestion procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message contains one of the following RAB assignment responses: "No Radio Resources Available in Target cell", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available". The CS RAB Setup Attempt Procedure starts when the RNC receives an RAB ASSIGNMENT REQUEST message from the CN in the CS domain. The message contains one of the following RAB assignment requests: Conversational Services, streaming Services.
Associated Counters
CS RAB Congestion Ratio= [(VS.RAB.FailEstabCS.DLIUBBand.Cong+ VS.RAB.FailEstabCS.ULIUBBand.Cong+ VS.RAB.FailEstabCS.ULCE.Cong + VS.RAB.FailEstabCS.DLCE.Cong + VS.RAB.FailEstabCS.Code.Cong + VS.RAB.FailEstabCS.ULPower.Cong+ VS.RAB.FailEstabCS.DLPower.Cong)/ (VS.RAB.AttEstabCS.Conv+ VS.RAB.AttEstabCS.Str)] x100%
Object
CELL
Unit/Range
%
Note
None
2.24 PS RAB Congestion Ratio Table 2-24 PS RAB Congestion Ratio Name
PS RAB Congestion Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
26
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI is used to check the PS RAB Congestion Ratio in a cluster. The PS RAB Setup Fails due to Congestion procedure is complete when the RNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message contains information about one of the following RAB assignment responses: "No Radio Resources Available in Target cell", "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for UL not Available", "Requested Guaranteed Bit Rate not Available", "Requested Guaranteed Bit Rate for DL not Available", "Requested Guaranteed Bit Rate for UL not Available". The PS RAB Setup Attempt Procedure starts when the RNC receives an RAB ASSIGNMENT REQUEST message from the SGSN in the PS domain. The message contains information about one of the following RAB assignment requests: Conversational services, Streaming services, Interactive Services, Background Services.
Associated Counters
PS RAB Congestion Ratio= [VS.RAB.FailEstabPS.DLIUBBand.Cong+ VS.RAB.FailEstabPS.ULIUBBand.Cong+ VS.RAB.FailEstabPS.ULCE.Cong+ VS.RAB.FailEstabPS.DLCE.Cong+ VS.RAB.FailEstabPS.Code.Cong+ VS.RAB.FailEstabPS.ULPower.Cong+ VS.RAB.FailEstabPS.DLPower.Cong+ VS.RAB.FailEstabPS.HSDPAUser.Cong+ VS.RAB.FailEstabPS.HSUPAUser.Cong/ VS.RAB.AttEstabPS.Str+ VS.RAB.AttEstabPS.Int+ VS.RAB.AttEstabPS.Bkg] x 100%
Object
CELL
Unit/Range
%
Note
None
2.25 PS R99 RAB Setup Success Rate Table 2-25 PS R99 RAB Setup Success Rate
Issue 02 (2014-03-28)
Name
PS R99 RAB Setup Success Rate
Formula
PS R99 RAB Setup Success Rate = Number of successfully set up PS R99 RABs x 100%/Number of PS R99 RAB setup attempts
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
27
RAN16.0 KPI Reference
2 Accessibility
Description
This KPI provides the PS R99 RAB setup success rate. The number of PS R99 RAB setup attempts is measured in the best cell where the UE camps on when the RNC receives from the PS CN an RAB ASSIGNMENT REQUEST message. After receiving this message, the RNC attempts to set up an RAB for the service based on the network configuration. The number of successfully set up PS R99 RABs is measured in the best cell where the UE camps on when the RNC sends the CN an RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE if the RAB is for a PS R99 service.
Associated Counters
PS RAB Setup Success Ratio (Cell)=
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
(VS.RAB.SuccEstab.PSR99/ VS.RAB.AttEstab.PSR99) * 100%
2.26 WB AMR RAB Setup Success Rate Table 2-26 WB AMR RAB Setup Success Rate Name
WB AMR RAB Setup Success Rate
Formula
WB AMR RAB Setup Success Rate = Number of successfully set up WB AMR RABs x 100%/Number of WB AMR RAB setup attempts
Description
This KPI provides the WB AMR RAB setup success rate. The number of WB AMR RAB setup attempts is measured in the best cell where the UE camps on when the RNC receives from the CS CN an RAB ASSIGNMENT REQUEST message for a WB AMR voice service. The number of successfully set up WB AMR RABs is measured in the best cell where the UE camps on when the RNC sends the CN an RAB ASSIGNMENT RESPONSE message after receiving a RADIO BEARER SETUP COMPLETE message from the UE if the RAB is for a WB AMR voice service.
Issue 02 (2014-03-28)
Associated Counters
AMR WB RAB Setup Success Ratio(Cell)=
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
(VS.RAB.SuccEstabCS.AMRWB / VS.RAB.AttEstabCS.AMRWB) *100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
28
RAN16.0 KPI Reference
3 Availability
3
Availability
About This Chapter Availability KPIs mainly indicate the utilization for several kinds of network resources such as Radio, bandwidth or CPU Load.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
29
RAN16.0 KPI Reference
3 Availability
3.1 Worst Cell Ratio Table 3-1 Worst Cell Ratio Name
Worst Cell Ratio
Formula
Description
This KPI is used to check the Availability of the cells with poor call drop ratio or call setup success ratio in an RNC or a cluster. Description of the numerator: The number of Cells in which AMR RAB Setup Success Ratio 3%.
Associated Counters
Worst Cell Ratio = {[The Number Of Cells, In which (AMR RAB Setup Success Ratio (Cell) < 95% and VP RAB Setup Success Ratio (Cell) =< 95%) or (AMR Call Drop Ratio > 3% and VP Call Drop Ratio > 3%)]/The Total Number Of Cells In RNC} x 100%
Object
CELL
Unit/Range
%
Note
95% and 3% are the values obtained based on the references from the commercial network with the condition of that the traffic of AMR voice and video call is greater than 0.1 Erlang.
3.2 Paging Congestion Ratio Table 3-2 Paging Congestion Ratio Name
Issue 02 (2014-03-28)
Paging Congestion Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
30
RAN16.0 KPI Reference
3 Availability
Formula
Description
Paging Congestion Ratio (RNC): This KPI is used to check the consumption of PCCH bandwidth during busy hours. l Description of the numerator: The Failures to Respond to PAGING Message From CN counted if the RNC does not send a PAGING type 1 or PAGING type 2 message. The reason is that the RNC does not send a PAGING message due to congestion causes such as Iu flow control or high CPU usage. l Description of the denominator: The Number of PAGING Message from CN is counted when RNC receives a PAGING message from the CN included CS and PS PAGING. Paging Congestion Ratio (Cell): This KPI is used to check the consumption of PCCH bandwidth during the busy hour. l Description of the numerator: This counter provides the number of losses of PAGING TYPE 1 message due to PCH congestion in a cell. l Description of the denominator: This counter provides the number of paging messages of PAGING TYPE 1 sent by the RNC in a cell.
Associated Counters
l IU Paging Congestion Ratio (RNC)= [(VS.RANAP.CsPaging.Loss+ VS.RANAP.PsPaging.Loss)/ (VS.RANAP.CsPaging.Att+ VS.RANAP.PsPaging.Att)] x 100% l IU Paging Congestion Ratio (Cell) = (VS.RRC.Paging1.Loss.PCHCong.Cell/VS.UTRAN.AttPaging1) x 100%
Object
RNC, CELL
Unit/Range
%
Note
None
3.3 Call Admission Refused Ratio Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
31
RAN16.0 KPI Reference
3 Availability
Table 3-3 Call Admission Refused Ratio Name
Call Admission Refused Ratio
Formula
Description
This KPI is used to check the admission refused ratio of new calls during busy hours in an RNC or a cluster. l Description of the numerator: The failed number of Cell Resource Requests for New Call setup is counted after RNC requesting cell resources for the UE successfully. l Description of the denominator: The number of Cell Resource Requests during RAB establishment for Cell. After RNC receiving the RAB ASSIGNMENT REQUEST message from CN, the RNC requests cell resources for the UE and the counter is pegged in the cell where the UE camps on.
Associated Counters
Call admission Refused Ratio=
Object
CELL
Unit/Range
%
Note
The RNC level KPI is calculated by aggregating all the cell counters.
[1-VS.RAC.NewCallAcc/VS.RAC.NewCallReq] x 100%
3.4 Congested Cell Ratio Table 3-4 Congested Cell Ratio Name
Congested Cell Ratio
Formula
Description
This KPI is used to check the utility ratio of radio network resources during busy hours in an RNC or a cluster. It is the rate of congested cell during the busy hour to total number of cells in RNC. Description of the numerator: The number of congested cells counted after RNC receiving the COMMON MESUREMENT REPORT message from NodeB. The RNC measures when overload congestion occurs at UL or DL.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
32
RAN16.0 KPI Reference
3 Availability
Associated Counters
Congested Cell Ratio =
Object
CELL
Unit/Range
%
Note
The number of congested cells is calculated by aggregating the cells that are congested in DL or UL directions during busy hours.
(The Number Of Cells, in which VS.LCC.OLC.UL.Num>0 or VS.LCC.OLC.DL.Num>0 On Busy Hour/The Total Number Of Cells In RNC) x 100%
3.5 Radio Network Unavailability Ratio Table 3-5 Radio Network Unavailability Ratio Name
Radio Network Unavailability Ratio
Formula
Description
This KPI describes the ratio of cell unavailable duration to the number of cells in RNC during busy hours. It is used to check the impact of the degrading of the network performance caused by the unavailable cells during busy hours in an RNC. Description of the numerator: The cell unavailable time is started to count when the cell is out of service, or the channel is barred through the LMT in a measurement period, or problem of CCH such as failed synchronization, or equipment faults.
Associated Counters
Issue 02 (2014-03-28)
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
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
33
RAN16.0 KPI Reference
3 Availability
3.6 Average CPU Load Table 3-6 Average CPU Load Name
Average CPU Load
Formula
For BSC6900: Average CPU Load = CPU usage of the XPU subsystem in the measurement period For BSC6910: Average CPU Load = CPU usage of the subsystem in the measurement period
Description
This KPI provides the mean CPU usage of a subsystem in the measurement period. It indicates the load and operating performance of the CPU on the subsystem in the measurement period. The CPU usage of the subsystem is sampled every second in the measurement period. Then, average CPU usage of the subsystem is the accumulated value divided by the number of sampling times.
Associated Counters
For BSC6900: Average CPU Load= VS.XPU.CPULOAD.MEAN
Object
For BSC6900: XPU
For BSC6910: Average CPU Load= VS.SUBSYS.CPULOAD.MEAN
For BSC6910: SUBSYS Unit/Range
%
Note
Mean CPU Utility is the CPU average load showed in percentage.
3.7 Iub Port Available Bandwidth Utilizing Ratio (UL) Table 3-7 Iub Port Available Bandwidth Utilizing Ratio (UL) Name
Iub Port Available Bandwidth Utilizing Ratio (UL)
Formula
Description
Issue 02 (2014-03-28)
This KPI is used to check consumption of NodeB Iub port available bandwidth utilizing ratio. The Bandwidth could be measured on ATM Physical Ports or IP physical Ports.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
34
RAN16.0 KPI Reference
3 Availability
Associated Counters
l Iub Port Available Bandwidth Utilizing Ratio (ATM_UL) = [(VS.ATMUlAvgUsed.1+ VS.ATMUlAvgUsed.2+ VS.ATMUlAvgUsed.3+ VS.ATMUlAvgUsed.4)/ (VS.ATMUlTotal.1+ VS.ATMUlTotal.2+ VS.ATMUlTotal.3+ VS.ATMUlTotal.4)] x 100% l Iub Port Available Bandwidth Utilizing Ratio (IP_UL) = [(VS.IPUlAvgUsed.1+ VS.IPUlAvgUsed.2+ VS.IPUlAvgUsed.3+ VS.IPUlAvgUsed.4)/ (VS.IPUlTotal.1+ VS.IPUlTotal.2+ VS.IPUlTotal.3+ VS.IPUlTotal.4)] x 100%
Object
NodeB
Unit/Range
%
Note
The counters in the formula are measured on the NodeB side. In Iub over IP mode, the NodeB-level counters VS.IPUlTotal.1, VS.IPUlTotal.2, VS.IPUlTotal.3, and VS.IPUlTotal.4 provide the available physical bandwidths of ports rather than the actual available bandwidths of ports. Therefore, this KPI can not be used to check the Iub actual bandwidth utilizing ratio.
3.8 Iub Port Available Bandwidth Utilizing Ratio (DL) Table 3-8 Iub Port Available Bandwidth Utilizing Ratio (DL) Name
Iub Port Available Bandwidth Utilizing Ratio (DL)
Formula
Description
Issue 02 (2014-03-28)
This KPI is used to check consumption of NodeB Iub port available bandwidth utilizing ratio. The Bandwidth could be measured on ATM Physical Ports or IP physical Ports. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
35
RAN16.0 KPI Reference
3 Availability
Associated Counters
l Iub Port Available Bandwidth Utilizing Ratio (ATM_DL) = [(VS.ATMDIAvgUsed.1+ VS.ATMDLAvgUsed.2+ VS.ATMDLAvgUsed.3+ VS.ATMDLAvgUsed.4)/ (VS.ATMDLTotal.1+ VS.ATMDLTotal.2+ VS.ATMDLTotal.3+ VS.ATMDLTotal.4)] x 100% l Iub Port Available Bandwidth Utilizing Ratio (IP_DL) = [(VS.IPDLAvgUsed.1+ VS.IPDLAvgUsed.2+ VS.IPDLAvgUsed.3+ VS.IPDLAvgUsed.4)/ (VS.IPDLTotal.1+ VS.IPDLTotal.2+ VS.IPDLTotal.3+ VS.IPDLTotal.4)] x 100%
Object
NodeB
Unit/Range
%
Note
The counters in the formula are measured on the NodeB side. In Iub over IP mode, the NodeB-level counters VS.IPDLTotal.1, VS.IPDLTotal.2, VS.IPDLTotal.3, and VS.IPDLTotal.4 provide the available physical bandwidths of ports rather than the actual available bandwidths of ports. Therefore, this KPI can not be used to check the Iub actual bandwidth utilizing ratio.
3.9 Cell Unavailability duration Table 3-9 Cell Unavailability duration
Issue 02 (2014-03-28)
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
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
36
RAN16.0 KPI Reference
3 Availability
Unit/Range
s
Note
None
3.10 HSDPA Unavailability duration Table 3-10 HSDPA Unavailability duration Name
HSDPA Unavailability duration
Description
This KPI is used to check the total duration of unavailability of the HSDPA service in a cell,caused by system fault in a measurement period.
Associated Counters
VS.Cell.HSDPA.UnavailTime
Object
CELL
Unit/Range
s
Note
None
3.11 HSUPA Unavailability duration Table 3-11 HSUPA Unavailability duration Name
HSUPA Unavailability duration
Description
This KPI is used to check the total duration of unavailability of the HSUPA service in a cell,caused by system fault in a measurement period.
Associated Counters
VS.Cell.HSUPA.UnavailTime
Object
CELL
Unit/Range
s
Note
None
3.12 CE Consumption for a NodeB Cell
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
37
RAN16.0 KPI Reference
3 Availability
Table 3-12 CE Consumption for a NodeB Cell Name
CE Consumption for a NodeB Cell
Description
The resources for license groups are measured based on the usage of CEs in each license group. This measurement indicates the consumption of baseband resources in the NodeB. The corresponding counters listed below give the Average/Maximum number of UL/DL and HSUPA CEs consumption for an operator.
Associated Counters
VS.ULCE.Mean.Shared VS.ULCE.Max.Shared VS.DLCE.Mean.Shared VS.DLCE.Max.Shared VS.ULCE.Mean.Dedicated VS.ULCE.Max.Dedicated VS.DLCE.Mean.Dedicated VS.DLCE.Max.Dedicated
Object
NodeB CELL
Unit/Range
Numbers
Note
If only one Operator is available on the NodeB, the Dedicated Counter value is always Zero and the Shared CE counters should be used to check actual consumption of the Cell in NodeB.
3.13 Hardware Configured CE for a NodeB Table 3-13 Hardware Configured CE for a NodeB Name
Hardware Configured CE for a NodeB
Description
Number of UL/DL CEs configured for a NodeB.
Associated Counters
VS.HW.ULCreditAvailable
Object
NodeB
Unit/Range
Numbers
Note
None
VS.HW.DLCreditAvailable
3.14 Shared Group Configured License CE for a NodeB Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
38
RAN16.0 KPI Reference
3 Availability
Table 3-14 Shared Group Configured License CE for a NodeB Name
Shared Group Configured License CE for a NodeB
Description
The Configured DL/UL CEs for the Shared Group.
Associated Counters
VS.LC.ULCreditAvailable.Shared
Object
NodeB
Unit/Range
Numbers
Note
If only one operator is available on the NodeB, the configured counters given above should be used to evaluate the total configured License CE in the NodeB.
VS.LC.DLCreditAvailable.Shared
3.15 Shared Group License CE Consumption for a NodeB Table 3-15 Shared Group License CE Consumption for a NodeB Name
Shared Group License CE Consumption for a NodeB
Description
The Average/Maximum/Minimum number of shared DL/UL CEs consumed by an operator, or by HSUPA service.
Associated Counters
VS.LC.ULMean.LicenseGroup.Shared VS.LC.ULMax.LicenseGroup.Shared VS.LC.ULMin.LicenseGroup.Shared VS.HSUPA.LC.ULMean.LicenseGroup.Shared VS.HSUPA.LC.ULMax.LicenseGroup.Shared VS.HSUPA.LC.ULMin.LicenseGroup.Shared VS.LC.DLMean.LicenseGroup.Shared VS.LC.DLMax.LicenseGroup.Shared VS.LC.DLMin.LicenseGroup.Shared
Object
NodeB
Unit/Range
Numbers
Note
If only one operator is available on the NodeB, the shared counters given above should be used to evaluate the total License CE Consumption in the NodeB.
3.16 License Group Configured CE for a NodeB Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
39
RAN16.0 KPI Reference
3 Availability
Table 3-16 License Group Configured CE for a NodeB Name
License Group Configured CE for a NodeB
Description
The Number of DL CEs configured for a license Group.
Associated Counters
VS.LC.DLCreditAvailable.LicenseGroup.Dedicated
Object
NodeB
Unit/Range
Numbers
Note
If only one operator is available on the NodeB, the configured counter value given above is Zero.
VS.LC.ULCreditAvailable.LicenseGroup.Dedicated
3.17 License Group CE Consumption for a NodeB Table 3-17 License Group CE Consumption for a NodeB Name
License Group CE Consumption for a NodeB
Description
The Average/Maximum/Minimum number of shared DL/UL CEs consumed by a licensed group, or by HSUPA services.
Associated Counters
l UL Statistics VS.LC.ULMean.LicenseGroup VS.LC.ULMax.LicenseGroup VS.LC.ULMin.LicenseGroup VS.HSUPA.LC.ULMin.LicenseGroup VS.HSUPA.LC.ULMean.LicenseGroup VS.HSUPA.LC.ULMax.LicenseGroup l DL Statistics VS.LC.DLMean.LicenseGroup VS.LC.DLMax.LicenseGroup VS.LC.DLMin.LicenseGroup
Object
NodeB
Unit/Range
Numbers
Note
If only one operator is available on the NodeB, the counter value given above is Zero.
3.18 RTWP (Received Total Wideband Power) Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
40
RAN16.0 KPI Reference
3 Availability
Table 3-18 RTWP (Received Total Wideband Power) Name
RTWP (Received Total Wideband Power)
Description
The first 3 counters given below provide the RTWP measurement values of a cell in the RNC, Mean/Maximum/Minimum Power of Totally Received Bandwidth for Cell. The last 3 counters provide average, maximum and minimum received scheduled E-DCH power shared in the measurement period for cell.
Associated Counters
VS.MaxRTWP VS.MinRTWP VS.MeanRTWP VS.HSUPA.MeanRSEPS VS.HSUPA.MaxRSEPS VS.HSUPA.MinRSEPS
Object
CELL
Unit/Range
dBm; %
Note
None
3.19 TCP (Transmitted Carrier Power) Table 3-19 TCP (Transmitted Carrier Power) Name
TCP (Transmitted Carrier Power)
Description
l The first 3 counters provide the Maximum/Minimum/Mean Transmitted Power of Carrier for a cell. l The second 3 counters provide the Maximum/Minimum/Mean NonHSDPA Transmitted Carrier Power for a Cell. l The third 3 counters provide Maximum/Minimum/Mean Power Required by HS-DSCH for a Cell.
Associated Counters
VS.MaxTCP VS.MinTCP VS.MeanTCP VS.MaxTCP.NonHS VS.MinTCP.NonHS VS.MeanTCP.NonHS VS.HSDPA.MaxRequiredPwr VS.HSDPA.MinRequiredPwr VS.HSDPA.MeanRequiredPwr
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
41
RAN16.0 KPI Reference
3 Availability
Object
CELL
Unit/Range
dBm
Note
None
3.20 R99 Code Utilization Table 3-20 R99 Code Utilization Name
R99 Code Utilization
Formula
Description
The occupied codes are the codes occupied by R99 user. The code number is normalized to SF = 256, that is, converted to the code number when SF = 256. The counters given below provide the number of single-RAB and Multi-RAB UEs that occupy the DL R99 codes with Spreading Factor (SF) of 4/8/16/32/64/128/256.
Associated Counters
R99 Code Utilization = [(VS.SingleRAB.SF4+VS.MultRAB.SF4) x 64+ (VS.SingleRAB.SF8+VS.MultRAB.SF8) x 32+ (VS.SingleRAB.SF16+VS.MultRAB.SF16) x 16+ (VS.SingleRAB.SF32+VS.MultRAB.SF32) x 8+ (VS.SingleRAB.SF64+VS.MultRAB.SF64) x 4+ (VS.SingleRAB.SF128+VS.MultRAB.SF128) x 2 + (VS.SingleRAB.SF256+VS.MultRAB.SF256)]/256 x 100%
Object
CELL
Unit/Range
%
Note
The occupied codes are normalized to SF = 256. Total Code utilization for a cell can be calculated approximately by using the following formula: VS.RAB.SFOccupy /256 The value would be greater than the real usage as the code for HSDPA was reserved initially.
3.21 Number of Codes Used by HS-PDSCHs Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
42
RAN16.0 KPI Reference
3 Availability
Table 3-21 Number of Codes Used by HS-PDSCHs Name
Number of Codes Used by HS-PDSCHs
Formula
HSDPA Efficiency = Duration when there is HSDPA data transmission/ Duration when there is HSDPA data in the buffer
Description
The counters VS.PdschCodeUsed.Mean, VS.PdschCodeUsed.Max, and VS.PdschCodeUsed.Min provide the mean, maximum, and minimum number of codes used by HS-PDSCHs in a cell during a measurement period respectively.
Associated Counters
VS.PdschCodeUsed.Mean VS.PdschCodeUsed.Max VS.PdschCodeUsed.Min
Object
NodeB
Unit/Range
None
Note
None
3.22 HSDPA Efficiency Table 3-22 HSDPA Efficiency Name
HSDPA Efficiency
Formula
HSDPA Efficiency = Duration when there is HSDPA data transmission/ Duration when there is HSDPA data in the buffer
Description
This KPI provides the proportion of the duration when there is HSDPA data transmission to the duration when there is HSDPA data in the buffer.
Associated Counters
HSDPA efficiency =
Object
NodeB
Unit/Range
%
Note
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean) indicates the proportion of TTIs with data transmission.
(VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean)/ (VS.DataTtiRatio.Mean - VS.HSDPA.InactiveDataTtiRatio.Mean + VS.HSDPA.ScheInactiveDataTtiRatio.Mean)
VS.HSDPA.ScheInactiveDataTtiRatio.Mean indicates the proportion of TTIs when there is no data transmission but the scheduling candidate set contains data from the buffer.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
43
RAN16.0 KPI Reference
4 Coverage
4
Coverage
About This Chapter Coverage KPIs are used for monitoring cell Interference status and Soft Handover Gain in an RNC or a cluster.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
44
RAN16.0 KPI Reference
4 Coverage
4.1 UL Interference Cell Ratio Table 4-1 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.
4.2 Soft Handover Overhead Table 4-2 Soft Handover Overhead KPI Name
Issue 02 (2014-03-28)
Soft Handover Overhead (RNC)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
45
RAN16.0 KPI Reference
4 Coverage
Formula
A1: Number of UEs with 1 RL in the RNC B1: Number of UEs with 2 RLs in the RNC C1: Number of UEs with 3 RLs in the RNC D1: Number of UEs with 4 RLs in the RNC E1: Number of UEs with 5 RLs in the RNC F1: Number of UEs with 6 RLs in the RNC.
A1: Number of UEs with 1 RL B1: Number of UEs with 2 RLs C1: Number of UEs with 3 RLs D1: Number of UEs with 4 RLs E1: Number of UEs with 5 RLs F1: Number of UEs with 6 RLs. Description
This KPI is used to check the consumption of network resources due to soft handover in an RNC or a Cell. It considered the radio link quantity during the soft handover. In the RNC Soft handover ratio, count the mean number of UEs with different quantity of radio links for RNC from A1 to F1. The RNC periodically samples of the number of UEs with corresponding radio links in a measurement period. At the end of the measurement period, the RNC divides the accumulated number by the sampling times to obtain the soft handover overhead. The Cell level KPI is only available for cells in a cluster. From A1 to F1 count the mean number of UEs with different quantity of Radio Links(1~6 radio links) in the Cell of the active set.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
46
RAN16.0 KPI Reference
4 Coverage
Associated Counters
l Soft Handover Overhead (RNC)= {[VS.SHO.AS.1.RNC + (VS.SHO.AS.2Softer.RNC + VS.SHO.AS.2Soft.RNC)*2 + (VS.SHO.AS.3Soft2Softer.RNC + VS.SHO.AS.3Soft.RNC + VS.SHO.AS.3Softer.RNC )*3 + VS.SHO.AS.4.RNC*4 + VS.SHO.AS.5.RNC*5 + VS.SHO.AS.6.RNC*6 ]/ (VS.SHO.AS.1.RNC + VS.SHO.AS.2Softer.RNC + VS.SHO.AS.2Soft.RNC + VS.SHO.AS.3Soft2Softer.RNC + VS.SHO.AS.3Soft.RNC + VS.SHO.AS.3Softer.RNC + VS.SHO.AS.4.RNC + VS.SHO.AS.5.RNC + VS.SHO.AS.6.RNC)-1}*100% l Soft Handover Overhead (Cell)= [(VS.SHO.AS.1RL + VS.SHO.AS.2RL + VS.SHO.AS.3RL + VS.SHO.AS.4RL + VS.SHO.AS.5RL + VS.SHO.AS.6RL )/ (VS.SHO.AS.1RL + VS.SHO.AS.2RL /2 + VS.SHO.AS.3RL /3 + VS.SHO.AS.4RL /4 + VS.SHO.AS.5RL /5 + VS.SHO.AS.6RL /6)-1]*100%
Issue 02 (2014-03-28)
Object
RNC, CELL
Unit/Range
%
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
47
RAN16.0 KPI Reference
5 Mobility
5
Mobility
About This Chapter Mobility KPIs are used to monitor the successful ratio for several kinds of handover features or service mode changing in difference scenarios.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
48
RAN16.0 KPI Reference
5 Mobility
5.1 Soft Handover Success Ratio Table 5-1 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
5.2 Softer Handover Success Ratio Table 5-2 Softer Handover Success Ratio Name
Softer Handover Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
49
RAN16.0 KPI Reference
5 Mobility
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 UPDATE message to the UE.
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
5.3 AMR Soft Handover Success Ratio Table 5-3 AMR Soft Handover Success Ratio Name
AMR Soft Handover Success Ratio
Formula
Description
This KPI is used to check the AMR Soft Handover Success ratio in a Cluster, including softer handover. The Successful AMR Soft Handover procedure is complete when the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure. The attempt procedure is complete when the RNC sends an ACTIVE SET UPDATE message to the UE.
Issue 02 (2014-03-28)
Associated Counters
AMR Soft Handover Success Ratio =
Object
CELL
Unit/Range
%
[(VS.SHO.AMR.Succ)/(VS.SHO.AMR.Att)] x 100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
50
RAN16.0 KPI Reference
5 Mobility
Note
The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.
5.4 CS64 Soft Handover Success Ratio Table 5-4 CS64 Soft handover Success Ratio Name
CS64 Soft handover Success Ratio
Formula
Description
This KPI is used to check the CS64 Soft Handover Success ratio in a Cluster, including softer handover. The Successful CS64 Soft Handover procedure is complete when the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure. The attempt procedure is complete when the RNC sends an ACTIVE SET UPDATE message to the UE.
Associated Counters
CS64 Soft Handover Success Ratio =
Object
CELL
Unit/Range
%
Note
The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.
[(VS.SHO.CS64.Succ)/(VS.SHO.CS64.Att)] x 100%
5.5 PS Soft Handover Success Ratio Table 5-5 PS soft handover Success Ratio Name
PS soft handover Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
51
RAN16.0 KPI Reference
5 Mobility
Description
This KPI is used to check the PS Soft Handover Success ratio in a Cluster, including softer handover. The Successful PS Soft Handover procedure is complete when the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE during the soft handover procedure. The attempt procedure is complete when the RNC sends an ACTIVE SET UPDATE message to the UE.
Associated Counters
PS services Soft Handover Success Ratio =
Object
CELL
Unit/Range
%
Note
The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.
[(VS.SHO.PS.Succ)/(VS.SHO.PS.Att)] x 100%
5.6 Intra-frequency Hard Handover Success Ratio Table 5-6 Intra-frequency Hard Handover Success Ratio Name
Intra-frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to check the intra-frequency hard handover success ratio in an RNC or a Cluster. The Intra-frequency Hard Handover Success procedure is complete when the RNC receives the PHYSICAL CHANNEL RECONFIGURATION COMPLETE (for example) message from the UE. The Intra-frequency Hard Handover Attempt procedure is complete when RNC sends the PHYSICAL CHANNEL RECONFIGURATION message to the UE.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
52
RAN16.0 KPI Reference
5 Mobility
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
5.7 Inter-frequency Hard Handover Success Ratio Table 5-7 Inter-frequency Hard Handover Success Ratio Name
Inter-frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to check the inter-frequency hard handover success ratio in an RNC or a Cluster. The Inter-frequency Hard Handover Success procedure is complete when RNC received a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE. The Inter-frequency Hard Handover attempts procedure starts when RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE. In this case the RNC measures the counter.
Associated Counters
Inter-frequency Hard Handover Success Ratio (RNC) = (VS.HHO.SuccInterFreq.RNC/VS.HHO.AttInterFreq.RNC) x 100% Inter-frequency Hard Handover Success Ratio (Cell) = (VS.HHO.SuccInterFreqOut/VS.HHO.AttInterFreqOut) x 100%
Issue 02 (2014-03-28)
Object
RNC, CELL
Unit/Range
% Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
53
RAN16.0 KPI Reference
5 Mobility
Note
None
5.8 Service Cell Change Success Ratio with SHO (H2H) Table 5-8 Service Cell Change Success Ratio with SHO (H2H) Name
Service Cell Change Success Ratio with SHO (H2H)
Formula
Description
l The HS-DSCH service cell change success with SHO is triggered with the following messages: PHYSICAL CHANNEL RECONFIGURATION TRANSPORT CHANNEL RECONFIGURATION RADIO BEARER RECONFIGURATION ACTIVE SET UPDATE l Accordingly, the UE sends the following messages to the RNC as a response. PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE ACTIVE SET UPDATE COMPLETE Take the PHYSICAL CHANNEL RECONFIGURATION message as an example. When receiving a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE, the RNC measures this item as numerator, and when sending a PHYSICAL CHANNEL RECONFIGURATION message to a UE, the RNC measures this item as denominator.
Associated Counters
Service Cell Change Success Ratio with SHO (H2H) =
Object
CELL
Unit/Range
%
Note
None
(VS.HSDPA.SHO.ServCellChg.SuccOut/ VS.HSDPA.SHO.ServCellChg.AttOut) x 100%
5.9 H2H Intra-Frequency Hard Handover Success Ratio Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
54
RAN16.0 KPI Reference
5 Mobility
Table 5-9 H2H Intra-Frequency Hard Handover Success Ratio Name
H2H Intra-Frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to check the intra-frequency hard handover success ratio of HSDPA service in a Cluster. l The HS-DSCH service cell change success with SHO is triggered with the following message: PHYSICAL CHANNEL RECONFIGURATION TRANSPORT CHANNEL RECONFIGURATION RADIO BEARER RECONFIGURATION RADIO BEARER SETUP RADIO BEARER RELEASE l Accordingly, the UE sends the following messages to the RNC as a response. PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER SETUP COMPLETE RADIO BEARER RELEASE COMPLETE Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when receiving a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE , the RNC measures this item in the best cell from which the UE is handed over if an intra-frequency HSDPA hard handover without channel change is performed.
Issue 02 (2014-03-28)
Associated Counters
H2H Intra-Frequency Hard Handover Success Ratio =
Object
CELL
Unit/Range
%
Note
The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.
(VS.HSDPA.HHO.H2H.SuccOutIntraFreq/VS.HSDPA.HHO.H2H.AttOutIntraFreq) x 100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
55
RAN16.0 KPI Reference
5 Mobility
5.10 H2H Inter-Frequency Hard Handover Success Ratio Table 5-10 H2H Inter-Frequency Hard Handover Success Ratio Name
H2H Inter-Frequency Hard Handover Success Ratio
Formula
Description
This KPI is used to indicate the success ratio of inter-frequency hard handovers from the HSDPA to the HSDPA in a cell. l The hard handover procedure can be triggered with the following message: PHYSICAL CHANNEL RECONFIGURATION TRANSPORT CHANNEL RECONFIGURATION RADIO BEARER RECONFIGURATION RADIO BEARER SETUP RADIO BEARER RELEASE l Accordingly, the UE sends the following messages to the RNC as a response. PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER SETUP COMPLETE RADIO BEARER RELEASE COMPLETE Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when receiving a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from a UE , the RNC measures this item in the best cell from which the UE is handed over if an inter-frequency HSDPA hard handover without channel change is performed.
Associated Counters
Issue 02 (2014-03-28)
H2H Inter-Frequency Hard Handover Success Ratio= (VS.HSDPA.HHO.H2H.SuccOutInterFreq/VS.HSDPA.HHO.H2H.AttOutInterFreq) x 100%
Object
CELL
Unit/Range
%
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
56
RAN16.0 KPI Reference
5 Mobility
5.11 H2D Intra-Frequency Hard Handover Success Ratio Table 5-11 H2D Intra-Frequency Hard Handover Success Ratio Name
H2D Intra-Frequency Hard Handover Success Ratio
Formula
H2D Intra-Frequency Hard Handover Success Ratio = Number of successful H2D intra-frequency hard handovers x 100%/Number of H2D intrafrequency hard handover attempts
Description
This KPI provides the success rate of HSDPA-to-DCH intra-frequency hard handovers in a cell. A hard handover is triggered by any of the following messages: l RADIO BEARER RECONFIGURATION l RADIO BEARER SETUP l RADIO BEARER RELEASE Accordingly, a UE may respond with one of the following messages: l RADIO BEARER RECONFIGURATION COMPLETE l RADIO BEARER SETUP COMPLETE l RADIO BEARER RELEASE COMPLETE Assume that a hard handover is triggered by the RADIO BEARER RECONFIGURATION message. The number of successful H2D intrafrequency hard handovers is measured in the best cell where the UE camps on before the hard handover when the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message during an intrafrequency hard handover.
Associated Counters
H2D Intra-frequency Hard Handover Success Ratio = (VS.HSDPA.HHO.H2D.SuccOutIntraFreq/ VS.HSDPA.HHO.H2D.AttOutIntraFreq)*100%
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
5.12 H2D Inter-Frequency Hard Handover Success Ratio Table 5-12 H2D Inter-Frequency Hard Handover Success Ratio Name
Issue 02 (2014-03-28)
H2D Inter-Frequency Hard Handover Success Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
57
RAN16.0 KPI Reference
5 Mobility
Formula
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 RECONFIGURATION RADIO BEARER SETUP RADIO BEARER RELEASE l Accordingly, the UE sends the following messages to the RNC as a response. RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER SETUP COMPLETE RADIO BEARER RELEASE COMPLETE Take the RADIO BEARER RECONFIGURATION message as an example, when receiving a RADIO BEARER RECONFIGURATION COMPLETE message from a UE , the RNC measures this item in the best cell from which the UE is handed over if an inter-frequency hard handover from the HSDPA to the DCH is performed.
Associated Counters
H2D Inter-Frequency Hard Handover Success Ratio =
Object
CELL
Unit/Range
%
Note
None
(VS.HSDPA.HHO.H2D.SuccOutInterFreq/VS.HSDPA.HHO.H2D.AttOutInterFreq) x 100%
5.13 E2D Intra-Frequency Hard Handover Success Ratio Table 5-13 E2D Intra-Frequency Hard Handover Success Ratio
Issue 02 (2014-03-28)
Name
E2D Intra-Frequency Hard Handover Success Ratio
Formula
E2D Intra-Frequency Hard Handover Success Ratio = Number of successful E2D intra-frequency hard handovers x 100%/Number of E2D intra-frequency hard handover attempts
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
58
RAN16.0 KPI Reference
5 Mobility
Description
This KPI provides the success rate of EDCH-to-DCH intra-frequency hard handovers in a cell. The number of E2D intra-frequency hard handover attempts is measured in the HSUPA serving cell where the UE camps on before the handover when the RNC sends the UE a RADIO BEARER RECONFIGURATION message during an EDCH-to-DCH intra-frequency hard handover. The number of successful E2D intra-frequency hard handovers is measured in the HSUPA serving cell where the UE camps on before the handover when the RNC receives from the UE a RADIO BEARER RECONFIGURATION COMPLETE message during an EDCH-to-DCH intra-frequency hard handover.
Associated Counters
E2D Intra-frequency Hard Handover Success Ratio =
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
(VS.HSUPA.HHO.E2D.SuccOutIntraFreq/VS.HSUPA.HHO.E2D.AttOutIntraFreq)*100%
5.14 H2D Channel Switch Success Ratio Table 5-14 H2D Channel Switch Success Ratio Name
H2D Channel Switch Success Ratio
Formula
Description
This KPI is used to check the channel switch success ratio when UE switches from HSDPA to DCH in a Cluster. The number of successful HS-DSCH to DCH channel switch measures when RNC receives a RAIDO BEARER RECONFIGURATION COMPLETE message from the UE indicating the channel reconfiguration for HSDPA service in the DCCC or RAB MODIFY procedure. The RNC measures the item in the HSDPA serving cell. The attempt number of H2D channel handover counts when RNC decides to perform a channel handover, which sends a RADIO BEARER RECONFIGURATION message to a UE during the DCCC or RAB MODIFY procedure. In this case, the RNC measures the item in the serving cell of the HSDPA service according to the transport channels of UEs before and after the reconfiguration. The RNC performs the transport channel Switch in the same cell.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
59
RAN16.0 KPI Reference
5 Mobility
Associated Counters
H2D Channel Switch Success Ratio=
Object
CELL
Unit/Range
%
Note
The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.
(VS.HSDPA.H2D.Succ/VS.HSDPA.H2D.Att) x 100%
5.15 D2H Channel Switch Success Ratio Table 5-15 D2H Channel Switch Success Ratio Name
D2H Channel Switch Success Ratio
Formula
Description
This KPI is used to check the channel switch success ratio when the UE switches from DCH to HSDPA i a Cluster. The number of successful DCH to HS-DSCH channel switch measures when RNC receives from the UE a RAIDO BEARER RECONFIGURATION COMPLETE message indicating the channel reconfiguration for HSDPA service in the DCCC or RAB MODIFY procedure. The RNC measures the item in the HSDPA serving cell. The attempt number of D2H channel switch counts when RNC decides to perform a channel switch, which sends a RADIO BEARER RECONFIGURATION message to a UE during the DCCC or RAB MODIFY procedure. In this case, the RNC measures the item in the serving cell of the HSDPA service according to the transport channels of UEs before and after the reconfiguration. The RNC performs the transport channel switch in the same cell.
Issue 02 (2014-03-28)
Associated Counters
D2H Channel Switch Success Ratio =
Object
CELL
Unit/Range
%
Note
The RNC level KPI can be approximately calculated by accumulating all cell counters within the RNC.
(VS.HSDPA.D2H.Succ/VS.HSDPA.D2H.Att) x 100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
60
RAN16.0 KPI Reference
5 Mobility
5.16 CS W2G Inter-RAT Handover Out Success Ratio Table 5-16 CS W2G Inter-RAT Handover Out Success Ratio Name
CS W2G Inter-RAT Handover Out Success Ratio
Formula
Description
This KPI is used to indicate the success ratio of CS Outgoing inter-RAT handovers in an RNC or a Cluster. The CS inter-RAT Handover Success procedure is complete when the RNC receives an IU RELEASE COMMAND message with the cause value of "Successful Relocation", "Normal Release", or "Network Optimization" after sending a HANDOVER FROM UTRAN COMMAND message during the CS outgoing inter-RAT handover. In this case, the outgoing handover succeeds and this counter is measured. Number of CS W2G inter-RAT handover attempts = Number of HANDOVER FROM UTRAN COMMAND messages sent from the RNC during CS outgoing inter-RAT handovers - Number of CS inter-RAT handover cancellations caused by UE's failures in receiving the message
Associated Counters
CS W2G Inter-RAT Handover Out Success Ratio (RNC) = (VS.IRATHO.SuccOutCS.RNC/VS.IRATHO.AttOutCS.RNC) x 100% CS W2G Inter-RAT Handover Out Success Ratio (Cell) = [(IRATHO.SuccOutCS)/(IRATHO.AttOutCS VS.IRATHOCS.Cancel.ReEstab)] x 100%
Object
RNC, CELL
Unit/Range
%
Note
You are advised to accumulate the related numerators and denominators of the cell level to calculate RNC-level KPIs. For example, if there are n cells under an RNC, an RNC-level KPI is calculated in the following formula: {Sum(IRATHO.SuccOutCS)/[Sum(IRATHO.AttOutCS) - Sum (VS.IRATHOCS.Cancel.ReEstab)]} x 100%
5.17 PS W2G Inter-RAT Handover Out Success Ratio Table 5-17 PS W2G Inter-RAT Handover Out Success Ratio Name
Issue 02 (2014-03-28)
PS W2G Inter-RAT Handover Out Success Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
61
RAN16.0 KPI Reference
5 Mobility
Formula
Description
This KPI is used to indicate the success ratio of PS outgoing inter-RAT handover initiated by the RNC or in the best cell. The PS W2G Inter-RAT Outgoing Handover successes procedure is complete when the RNC sends the RANAP IU RELEASE COMPLETE message after receiving the IU RELEASE COMMAND message with the cause of "Successful Relocation", "Normal Release" or "Network Optimization." In this case, the PS outgoing inter-RAT handover succeeds and the counter is measured. Number of PS W2G inter-RAT handover attempts = Number of CELL CHANGE ORDER FROM UTRAN messages sent from the RNC during PS outgoing inter-RAT handovers - Number of PS inter-RAT handover cancellations caused by UE's failures in receiving the message
Associated Counters
PS W2G Inter-RAT Handover Out Success Ratio(RNC) = (VS.IRATHO.SuccOutPSUTRAN.RNC/ VS.IRATHO.AttOutPSUTRAN.RNC) x 100% PS W2G Inter-RAT Handover Out Success Ratio (Cell) = [IRATHO.SuccOutPSUTRAN/(IRATHO.AttOutPSUTRAN VS.IRATHOPS.Cancel.ReEstab)] x 100%
Object
RNC, CELL
Unit/Range
%
Note
You are advised to accumulate the related numerators and denominators of the cell level to calculate RNC-level KPIs. For example, if there are n cells under an RNC, an RNC-level KPI is calculated in the following formula: {Sum(IRATHO.SuccOutPSUTRAN)/[Sum(IRATHO.AttOutPSUTRAN) Sum(VS.IRATHOPS.Cancel.ReEstab)]} x 100%
5.18 PS G2W Inter-RAT Handover In Success Ratio Table 5-18 PS G2W Inter-RAT Handover In Success Ratio Name
PS G2W Inter-RAT Handover In Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
62
RAN16.0 KPI Reference
5 Mobility
Description
This KPI is used to check the PS inter-RAT handover in success ratio in a Cluster. The PS G2W Inter-RAT Handover successes procedure is complete when the RNC receives an RRC CONNECTION SETUP COMPLETE message from the UE. The reasons for RRC connection request is Inter-RAT Cell Change Order and Inter-RAT Cell Reselection. The PS G2W Inter-RAT Handover attempts procedure starts when the RNC receives an RRC CONNECTION REQUEST message from the UE, the reasons for RRC connection request are Inter-RAT Cell Change Order and Inter-RAT Cell Reselection.
Associated Counters
PS G2W Inter-RAT Handover In Success Ratio= [(RRC.SuccConnEstab.IRATCCO+RRC.SuccConnEstab.IRATCelRes)/ (RRC.AttConnEstab.IRATCCO+RRC.AttConnEstab.IRATCelRes)] x 100%
Object
CELL
Unit/Range
%
Note
The KPI includes the IRAT cell reselection of UE in idle status.The RNC level KPI is calculated by aggregating all the cell counters.
5.19 HSDPA W2G Inter-RAT Handover Out Success Ratio Table 5-19 HSDPA W2G Inter-RAT Handover Out Success Ratio Name
HSDPA W2G Inter-RAT Handover Out Success Ratio
Formula
Description
This KPI is used to check the PS outgoing inter-RAT handover for HSDPA services initiated by the RNC in the best cell that the UE camps on before the handover. The HSDPA Inter-RAT HO successes procedure is complete when the RNC receives the IU RELEASE COMMAND message. The message contains one of the following information: "Successful Relocation", "Normal Release", "Network Optimization" during the PS outgoing inter-RAT handover for HSDPA services. The HSDPA Inter-RAT HO attempts procedure starts when the RNC sends the CELL CHANGE ORDER FROM UTRAN message during the PS outgoing inter-RAT handover for HSDPA services, the counter is measured in the best cell that the UE camps on.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
63
RAN16.0 KPI Reference
5 Mobility
Associated Counters
HSDPA W2G Inter-RAT Handover Out Success Ratio= (VS.IRATHO.HSDPA.SuccOutPSUTRAN/VS.IRATHO.HSDPA.AttOutPSUTRAN) x 100%
Object
CELL
Unit/Range
%
Note
The KPI includes the IRAT cell reselection of UE in idle status.
5.20 SRNC Relocation Success Ratio Table 5-20 SRNC Relocation Success Ratio Name
SRNC Relocation Success Ratio
Formula
Description
This KPI is used to check the relocation executions (UE involved and UE not involved) initiated by SRNC according to different CN domains. The SRNC Relocation Success procedure is complete when the SRNC receives an IU RELEASE COMMAND message. The message contains one of the following information: "Successful Relocation", "Normal Release", "Network Optimization". In this case, the SRNC measures the related counter according to the CN domain. The SRNC Relocation Attempts procedure starts when the SRNC receives a RELOCATION COMMAND message from the CN in the CS domain. In this case, the SRNC measures the related counter according to different relocation types (CS, PS, UE involved, UE not involved).
Associated Counters
SRNC Relocation Success Ratio = [(VS.SRELOC.SuccExecUEInvolCS+ VS.SRELOC.SuccExecUEInvolPS + VS.SRELOC.SuccExecUENonInvolCS + VS.SRELOC.SuccExecUENonInvolPS)/ (RELOC.SuccPrepUEInvolCS+ RELOC.SuccPrepUENotInvolCS + RELOC.SuccPrepUEInvolPS+ RELOC.SuccPrepUENotInvolPS)] x 100%
Issue 02 (2014-03-28)
Object
RNC
Unit/Range
% Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
64
RAN16.0 KPI Reference
5 Mobility
Note
None
5.21 TRNC Relocation Success Ratio Table 5-21 TRNC Relocation Success Ratio Name
TRNC Relocation Success Ratio
Formula
Description
This KPI is used to check the TRNC relocation executions (UE involved and UE not involved) initiated by SRNC according to different CN domains. The TRNC Relocation Success procedure is complete when the TRNC relocation is complete, and when the TRNC sends a RELOCATION COMPLETE message to the CN. In this case, the TRNC measures the related counters according to different relocation types. If the UE connects to both the CS domain and the PS domain at the same time, the related counters are increased by one each time the TRNC sends a RELOCATION COMPLETE message to the CNs in the CS domain and PS domain. When the resource allocation for TRNC relocation is complete, the TRNC sends a RELOCATION REQUEST ACKNOWLEDGE message to the CN in the CS or the PS domain. In this case, the TRNC measures the related counter according to different relocation types.
Associated Counters
TRNC Relocation Success Ratio = [(VS.TRELOC.SuccExecUEInvolCS+ VS.TRELOC.SuccExecUEInvolPS+ VS.TRELOC.SuccExecUENotInvolCS+ VS.TRELOC.SuccExecUENotInvolPS)/ (RELOC.SuccResAllocUEInvolCS+ RELOC.SuccResAllocUENotInvolCS+ RELOC.SuccResAllocUEInvolPS+ RELOC.SuccResAllocUENotInvolPS)] x 100%
Issue 02 (2014-03-28)
Object
RNC
Unit/Range
%
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
65
RAN16.0 KPI Reference
5 Mobility
5.22 E-DCH Soft Handover Success Ratio Table 5-22 E-DCH Soft Handover Success Ratio Name
E-DCH Soft Handover Success Ratio
Formula
Description
This KPI is used to check EDCH RL additions and deletions due to soft handover in a cell. The E-DCH soft Handover Success procedure is complete when the RNC receives an ACTIVE SET UPDATE COMPLETE message from the UE.An EDCH link is added or deleted during the soft handover. The E-DCH soft Handover attempts procedure starts when the RNC sends an ACTIVE SET UPDATE message to the UE and there is EDCH RL to be deleted or added during the soft handover.
Associated Counters
E-DCH Soft Handover Success Ratio=
Object
CELL
Unit/Range
%
Note
None
(VS.HSUPA.SHO.SuccOut/VS.HSUPA.SHO.AttOut) x 100%
5.23 E-DCH Cell Change Success Ratio with SHO Table 5-23 E-DCH Cell Change Success Ratio with SHO Name
E-DCH Cell Change Success Ratio with SHO
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
66
RAN16.0 KPI Reference
5 Mobility
Description
This KPI is used to check the success ratio of HSUPA serving cell changes in soft handover status for cell. Description of the numerator: l The successful HSUPA serving cell changes in soft handover status for cell, this procedure can be triggered with the following messages: PHYSICAL CHANNEL RECONFIGURATION TRANSPORT CHANNEL RECONFIGURATION RADIO BEARER RECONFIGURATION l Accordingly, the UE sends the following messaged to the RNC as a response: PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE l Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC receives a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message from the UE, the RNC measures this item in the original HSUPA serving cell if the HSUPA serving cell is changed. The item is used to indicate the change of HSUPA serving cells in the soft handover state instead of the hard handover state. Description of the denominator: l Take the PHYSICAL CHANNEL RECONFIGURATION message as an example, when the RNC sends a PHY CHANNEL RECONFIGURATION message to the UE. The RNC measures this item in the original HSUPA serving cell if the HSUPA serving cell is changed. This item is used to indicate the change of HSUPA serving cells in the soft handover status instead of the hard handover status.
Associated Counters
E-DCH Service Cell Change Success Ratio with SHO =
Object
CELL
Unit/Range
%
Note
None
(VS.HSUPA.SHO.ServCellChg.SuccOut/ VS.HSUPA.SHO.ServCellChg.AttOut) x 100%
5.24 E-DCH Cell Change Success Ratio with Inter-HHO Table 5-24 E-DCH Cell Change Success Ratio with Inter-HHO Name
Issue 02 (2014-03-28)
E-DCH Cell Change Success Ratio with Inter-HHO
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
67
RAN16.0 KPI Reference
5 Mobility
Formula
Description
This KPI is used to check the E-DCH service cell change success ratio with the Inter-HHO procedure in an RNC or a cluster. Description of the denominator: l When the RNC sends the following messages to the UE, the RNC measures the item in the HSUPA serving cell before the hard handover if an EDCH-to-EDCH inter-frequency hard handover is performed. PHYSICAL CHANNEL RECONFIGRATION TRANSPORT CHANNEL RECONFIGRATION RADIO BEARER RECONFIGRATION RADIO BEARER SETUP RADIO BEARER RELEASE Description of the numerator: 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. PHYSICAL CHANNEL RECONFIGURATION COMPLETE TRANSPORT CHANNEL RECONFIGURATION COMPLETE RADIO BEARER RECONFIGURATION COMPLETE RADIO BEARER SETUP COMPLETE RADIO BEARER RELEASE COMPLETE
Associated Counters
E-DCH Service Cell Change Success Ratio with Inter-HHO=
Object
CELL
Unit/Range
%
Note
None
(VS.HSUPA.HHO.E2E.SuccOutInterFreq/VS.HSUPA.HHO.E2E.AttOutInterFreq) x 100%
5.25 E2D Channel Switch Success Ratio Table 5-25 E2D Channel Switch Success Ratio Name
Issue 02 (2014-03-28)
E2D Channel Switch Success Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
68
RAN16.0 KPI Reference
5 Mobility
Formula
Description
This KPI is used to check the channel switch success ratio when there is UE handover from E-DCH to DCH in the same cell. The Switch Channel Type from EDCH to DCH successful attempts procedure is complete when the RNC receives an RB RECFG CMP message from the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving cell by the channel switch type. The Switch Channel Type from EDCH to DCH attempts procedure starts when the RNC sends a RADIO BEAR RECONFIGURE message to the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving cell by the channel switch type.
Associated Counters
E2D Channel Switch Success Ratio =
Object
CELL
Unit/Range
%
Note
None
(VS.HSUPA.E2D.Succ/VS.HSUPA.E2D.Att) x 100%
5.26 D2E Channel Switch Success Ratio Table 5-26 D2E Channel Switch Success Ratio Name
D2E Channel Switch Success Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
69
RAN16.0 KPI Reference
5 Mobility
Description
This KPI is used to check the channel switch success ratio when there is UE handover from E-DCH to DCH in the same cell. The Switch Channel Type from DCH to EDCH successful attempts procedure is complete when the RNC receives an RB RECFG CMP message from the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving cell by the channel switch type. The Switch Channel Type from DCH to EDCH attempts procedure starts when the RNC sends a RADIO BEAR RECONFIGURE message to the UE during the DCCC or RAB ASSIGN procedure. If the UE camps on the same cell after reconfigurations, the RNC measures the items in the HSUPA serving cell by the channel switch type.
Associated Counters
D2E Channel Switch Success Ratio (Intra Cell) =
Object
CELL
Unit/Range
%
Note
None
(VS.HSUPA.D2E.Succ/VS.HSUPA.D2E.Att) x 100%
5.27 E2D Handover Success Ratio with Inter HHO Table 5-27 E2D Handover Success Ratio with Inter HHO Name
E2D Handover Success Ratio with Inter HHO
Formula
Description
This KPI is used to check the success ratio of HSUPA Inter-Frequency Hard Handover from EDCH to DCH in a cell. The Switch Channel Type from EDCH to DCH successful attempts procedure is complete when the RNC receives a RADIO BEARER RECONFIGURATION COMPLETE message from the UE. The RNC measures this item in the HSUPA serving cell before the hard handover if an EDCH-to-DCH inter-frequency hard handover is performed. The Switch Channel Type from EDCH to DCH attempts procedure starts when the RNC sends a RADIO BEARER RECONFIGURATION message to the UE. The RNC measures this item in the HSUPA serving cell before the hard handover if an EDCH-to-DCH inter-frequency hard handover is performed.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
70
RAN16.0 KPI Reference
5 Mobility
Associated Counters
E-DCH to DCH Handover Success Ratio (with Inter HHO) =
Object
CELL
Unit/Range
%
Note
None
(VS.HSUPA.HHO.E2D.SuccOutInterFreq/VS.HSUPA.HHO.E2D.AttOutInterFreq) x 100%
5.28 HSUPA W2G Inter-RAT Handover Out Success Ratio Table 5-28 HSUPA W2G Inter-RAT Handover Out Success Ratio Name
HSUPA W2G Inter-RAT Handover Out Success Ratio
Formula
Description
This KPI is used to check the HSUPA service Inter-RAT handover success ratio from WCDMA to GPRS in the best cell that the UE camps on. The HSUPA W2G Inter-RAT Handover Out success procedure is complete when the RNC receives an IU RELEASE COMMAND message. The message contains one of the following information: "Successful Relocation", "Normal Release", "Network Optimization" and sends an IU RELEASE COMPLETE message during the PS outgoing inter-RAT handover for HSUPA services. In this case, the PS outgoing handover succeeds and this counter is measured in the best cell that the UE camps on before the handover. The HSUPA W2G Inter-RAT Handover Out attempts procedure starts when the RNC sends a CELL CHANGE ORDER FROM UTRAN message to the UE during the PS outgoing inter-RAT handover for HSUPA services. In this case, this counter is measured in the best cell that the UE camps on.
Associated Counters
Issue 02 (2014-03-28)
HSUPA W2G Inter-RAT Handover Out Success Ratio = (VS.IRATHO.HSUPA.SuccOutPSUTRAN/VS.IRATHO.HSUPA.AttOutPSUTRAN) x 100%
Object
CELL
Unit/Range
%
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
71
RAN16.0 KPI Reference
5 Mobility
5.29 MBMS Service Mode Switch Success Ratio Table 5-29 MBMS Service Mode Switch Success Ratio Name
MBMS Service Mode Switch Success Ratio
Formula
Description
This KPI is used to check the MBMS service mode switch success ratio from PTP to PTM. The MBMS Service Mode Switch Success procedure is complete after a MBMS service is switched from PTP mode to PTM mode and a PTM MBMS RB is successfully set up. The MBMS Service Mode Switch attempts procedure starts after the initiation of transition from PTP mode to PTM mode.
Associated Counters
MBMS Service Mode Switch Success Ratio from PTP to PTM=
Object
CELL
Unit/Range
%
Note
None
(VS.MBMS.PTPtoPTM.Succ/VS.MBMS.PTPtoPTM.Att)*100%
5.30 CS Inter-Frequency Hard Handover Success Rate Table 5-30 CS Inter-Frequency Hard Handover Success Rate Name
CS Inter-Frequency Hard Handover Success Rate
Formula
CS Inter-Frequency Hard Handover Success Rate = Number of successful CS inter-frequency hard handovers x 100%/Number of CS inter-frequency hard handover attempts
Description
This KPI provides the success rate of CS inter-frequency hard handovers of a Cluster. The number of CS inter-frequency hard handover attempts is measured when the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message during a CS inter-frequency hard handover. The number of successful CS inter-frequency hard handovers is measured when the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message during a CS inter-frequency hard handover.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
72
RAN16.0 KPI Reference
5 Mobility
Associated Counters
CS Inter-frequency Hard Handover Success Ratio = (VS.HHO.SuccInterFreqOut.CS/ VS.HHO.AttInterFreqOut.CS) * 100%
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counter.
5.31 PS Inter-Frequency Hard Handover Success Rate Table 5-31 PS Inter-Frequency Hard Handover Success Rate Name
PS Inter-Frequency Hard Handover Success Rate
Formula
PS Inter-Frequency Hard Handover Success Rate = Number of successful PS inter-frequency hard handovers x 100%/Number of PS inter-frequency hard handover attempts
Description
This KPI provides the success rate of PS inter-frequency hard handovers of a Cluster. The number of PS inter-frequency hard handover attempts is measured when the RNC sends the UE a PHYSICAL CHANNEL RECONFIGURATION message during a PS inter-frequency hard handover. The number of successful PS inter-frequency hard handovers is measured when the RNC receives from the UE a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message during a PS inter-frequency hard handover.
Issue 02 (2014-03-28)
Associated Counters
PS Inter-frequency Hard Handover Success Ratio=
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counter.
(VS.HHO.SuccInterFreqOut.PS/ VS.HHO.AttInterFreqOut.PS)*100%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
73
RAN16.0 KPI Reference
6 Retainability
6
Retainability
About This Chapter 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.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
74
RAN16.0 KPI Reference
6 Retainability
6.1 CS Service Drop Ratio Table 6-1 CS Service Drop Ratio Name
CS Service Drop Ratio
Formula Description
This KPI provides the ratio of the CS RAB abnormal Releases to the total CS RAB Releases (Normal Release + Abnormal Release). This KPI is used to check the retainabililty of CS Service within the UTRAN (RNC or Cluster). Description of RAB abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CN due to exceptions. If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with the causes other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to PS domain.
Associated Counters
CS Service Drop Ratio (Cell) = [VS.RAB.AbnormRel.CS/(VS.RAB.AbnormRel.CS+ VS.RAB.NormRel.CS)] x 100% CS Service Drop Ratio (RNC) = [VS.RAB.AbnormRel.CS.RNC/(VS.RAB.AbnormRel.CS.RNC+ VS.RAB.NormRel.CS.RNC)] x 100%
Object
CELL, RNC
Unit/Range
%
Note
This KPI involves CS call drops due to authentication failure during PS security mode in the cell. You can subtract VS.RAB.AbnormRel.CS.Security from the numerator of the formula to decrease the value of this KPI.
6.2 CS Call Drop Rate in CS+PS Combined Services Table 6-2 CS Call Drop Rate in CS+PS Combined Services
Issue 02 (2014-03-28)
Name
CS Call Drop Rate in CS+PS Combined Services
Formula
CS Call Drop Rate in CS+PS Combined Services = Number of times that a CS call in a CS+PS combined service drops/Number of CS+PS combined service release times
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
75
RAN16.0 KPI Reference
6 Retainability
Description
This KPI provides the drop rate of CS calls in CS+PS combined services. It reflects the retainability of CS+PS combined services in an RNC or cluster. When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization"), then the number of times that a CS call in a CS+PS combined service drops is measured in the best cell that the UE camps on if the message is for a CS call in a CS+PS combined service.
Associated Counters
CS Call Drop Rate in CS+PS Combined Services (Cell) = (VS.MultiRAB.CSAbnormRel.CSPS/ (VS.MultiRAB.CSNormRel.CSPS + VS.MultiRAB.CSAbnormRel.CSPS + VS.MultiRAB.PSNormRel.CSPS))*100%
Object
CELL
Unit/Range
%
Note
None
6.3 PS Call Drop Rate in CS+PS Combined Services Table 6-3 PS Call Drop Rate in CS+PS Combined Services Name
PS Call Drop Rate in CS+PS Combined Services
Formula
PS Call Drop Rate in CS+PS Combined Services = Number of times that a PS connection in a CS+PS combined service fails/Number of CS+PS combined service release times
Description
This KPI provides the PS connection failure rate in CS+PS combined services. It reflects the retainability of CS+PS combined services in an RNC or cluster. When a failure occurs, the RNC sends the CN an IU RELEASE REQUEST message. After receiving the message, the CN sends an IU RELEASE COMMAND message to the RNC. If the IU RELEASE COMMAND message contains a cause value of abnormal release (causes except "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization"), then the number of times that a PS connection in a CS+PS combined service fails is measured in the best cell that the UE camps on if the message is for a PS service in a CS+PS combined service.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
76
RAN16.0 KPI Reference
6 Retainability
Associated Counters
PS Call Drop Rate in CS+PS Combined Services (Cell)= (VS.MultiRAB.PSAbnormRel.CSPS/ (VS.MultiRAB.CSNormRel.CSPS + VS.MultiRAB.PSNormRel.CSPS + VS.MultiRAB.PSAbnormRel.CSPS))*100%
Object
CELL
Unit/Range
%
Note
None
6.4 AMR Call Drop Ratio Table 6-4 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). Description of RAB abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB RELEASE REQUEST message to the CNdue to exception. If the RNC receives an IU RELEASE COMMAND/RAB ASSIGNMENT REQUEST message with any one of the following messages: "User Inactivity","Normal Release", "Successful Relocation", "Network Optimization", the RNC measures the items according to the service types in the best cell that the UE camps on if the released RABs belong to PS domain.
Associated Counters
AMR Call Drop Ratio (Cell) = [VS.RAB.AbnormRel.AMR/(VS.RAB.AbnormRel.AMR+ VS.RAB.NormRel.AMR)] x 100% AMR Call Drop Ratio (RNC) = [(Sum{VS.RAB.AbnormRel.AMR}+ Sum {VS.RAB.AbnormRel.AMR.Iur})/ (Sum{VS.RAB.AbnormRel.AMR}+ Sum{VS.RAB.NormRel.AMR}+ Sum{VS.RAB.AbnormRel.AMR.Iur}+ Sum{VS.RAB.NormRel.AMR.Iur} )] x 100%
Issue 02 (2014-03-28)
Object
CELL, RNC
Unit/Range
%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
77
RAN16.0 KPI Reference
6 Retainability
Note
The RNC level KPIs are calculated by aggregating all the Cell and Iur counters in SRNC.
6.5 WB AMR Call Drop Rate Table 6-5 WB AMR Call Drop Rate Name
WB AMR Call Drop Rate
Formula
WB AMR Call Drop Rate = Number of abnormally released WB AMR calls x 100%/Total number of released WB AMR calls
Description
This KPI provides the proportion of abnormally released WB AMR calls to the total number of released WB AMR calls. It reflects the retainability of WB AMR calls in an RNC or a cluster. When a fault occurs, the RNC sends the CN an IU RELEASE REQUEST or RAB RELEASE REQUEST message. The number of abnormally released WB AMR calls is measured in the best cell where the UE camps on when the RNC receives an IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message whose cause value is not "User Inactivity", "Normal Release", "Successful Relocation", or "Network Optimization".
Associated Counters
WB AMR Call Drop Rate (Cell) = [VS.RAB.AbnormRel.AMRWB/ (VS.RAB.AbnormRel.AMRWB + VS.RAB.NormRel.AMRWB)] * 100% AMRWB Call Drop Ratio (RNC) = [(Sum{VS.RAB.AbnormRel.AMRWB} + Sum {VS.RAB.AbnormRel.AMRWB.Iur})/(Sum {VS.RAB.AbnormRel.AMRWB} + Sum{VS.RAB.NormRel.AMRWB} + Sum{VS.RAB.AbnormRel.AMRWB.Iur} + Sum {VS.RAB.NormRel.AMRWB.Iur} )]*100%
Object
CELL, RNC
Unit/Range
%
Note
None
6.6 VP Call Drop Ratio Table 6-6 VP Call Drop Ratio Name
Issue 02 (2014-03-28)
VP Call Drop Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
78
RAN16.0 KPI Reference
6 Retainability
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). Description of RAB abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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 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
6.7 AMR Traffic Drop Ratio Table 6-7 AMR Traffic Drop Ratio Name
AMR Traffic Drop Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
79
RAN16.0 KPI Reference
6 Retainability
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. Description of RAB abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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
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.5.9.RNC + VS.RB.AMR.DL.6.7.RNC + VS.RB.AMR.DL.7.4.RNC + VS.RB.AMR.DL.7.95.RNC + VS.RB.AMR.DL.10.2.RNC + VS.RB.AMR.DL.12.2.RNC ) x {SP}/60]/ (VS.RAB.AbnormRel.AMR.RNC)
Issue 02 (2014-03-28)
Object
CELL, RNC
Unit/Range
The unit of the numerator is Erlang; {SP} is the Statistic Period with the unit of minute
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
80
RAN16.0 KPI Reference
6 Retainability
6.8 VP Traffic Drop Ratio Table 6-8 VP Traffic Drop Ratio Name
VP Traffic Drop Ratio
Formula
Description
This KPI provides the ratio of the VP (Video Phone) Service Erlang to the VP RAB Abnormal Releases, which indicates the VP average Erlang per VP call drop within the UTRAN (RNC or Cluster). Description of the VS.RB.CS.Conv.DL.64/VS.RB.CS.Conv.DL.64.RNC: Average number of VP users with different DL rates during the measurement period. Description of RAB Abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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
6.9 PS Call Drop Ratio Table 6-9 PS Call Drop Ratio Name
Issue 02 (2014-03-28)
PS Call Drop Ratio
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
81
RAN16.0 KPI Reference
6 Retainability
Formula
Description
This KPI provides the ratio of the PS RAB abnormal Releases to the total PSRAB Releases (Normal Release + Abnormal Release) and is used to check the retainabililty of PS Service within the UTRAN (RNC or Cluster). Description of RAB Abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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
PS Call Drop Ratio (Cell) = [VS.RAB.AbnormRel.PS/(VS.RAB.AbnormRel.PS+ VS.RAB.NormRel.PS)] x 100% PS Call Drop Ratio (RNC) = [VS.RAB.AbnormRel.PS.RNC/(VS.RAB.AbnormRel.PS.RNC+ VS.RAB.NormRel.PS.RNC)] x 100%
Object
CELL, RNC
Unit/Range
%
Note
This KPI involves PS connection failures due to authentication failure during PS security mode in the cell. You can subtract VS.RAB.AbnormRel.PS.Security from the numerator of the formula to decrease the value of this KPI.
6.10 PS Call Drop Ratio (PCH) Table 6-10 PS Call Drop Ratio (PCH) Name
PS Call Drop Ratio (PCH)
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
82
RAN16.0 KPI Reference
6 Retainability
Description
Compared with 6.9 PS Call Drop Ratio, this KPI deducts abnormal RAB releases caused by UE's state transition to CELL_PCH or URA_PCH. Smartphones stay in the always-online state in networks when state transition to PCH is enabled. If state transition to PCH is enabled and there is no data transmission for a specific period of time, these UEs transit from connected mode to the PCH state instead of idle mode, resulting in abnormal PS RAB releases. As a result, the number of normal PS RAB releases decreases and the value of denominator Total Number of PS RAB Releases is reduced. The corresponding KPI deteriorates if the original formula for calculating PS Call Drop Ratio is used. A RAB release caused by UE's state transition from CELL_DCH to CELL_PCH or URA_PCH without PS data transmission should be considered as a normal RAB release because the transition has no impact on user experience. Therefore, PCH-related abnormal RAB releases caused by state transition from CELL_DCH to CELL_PCH or URA_PCH are not taken into account for calculating PS Call Drop Ratio.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
83
RAN16.0 KPI Reference
6 Retainability
Associated Counters
l PS Call Drop Ratio with PCH (Cell) = [(VS.RAB.AbnormRel.PSVS.RAB.AbnormRel.PS.PCHVS.RAB.AbnormRel.PS.D2PVS.RAB.AbnormRel.PS.F2P) / (VS.RAB.AbnormRel.PS+ VS.RAB.NormRel.PSVS.RAB.AbnormRel.PS.PCHVS.RAB.NormRel.PS.PCH+ VS.DCCC.D2P.Succ+ VS.DCCC.Succ.F2P+ VS.DCCC.Succ.F2U+ VS.DCCC.Succ.D2U)] x 100% l PS Service Drop Ratio with PCH (RNC) = [(VS.RAB.AbnormRel.PS.RNCSum{VS.RAB.AbnormRel.PS.PCH}Sum{VS.RAB.AbnormRel.PS.D2P}Sum{VS.RAB.AbnormRel.PS.F2P})/ (VS.RAB.AbnormRel.PS.RNC+ VS.RAB.NormRel.PS.RNCSum{VS.RAB.AbnormRel.PS.PCH}Sum{VS.RAB.NormRel.PS.PCH} + Sum{VS.DCCC.D2P.Succ} + Sum{VS.DCCC.Succ.F2P} + Sum{VS.DCCC.Succ.F2U}+ Sum{VS.DCCC.Succ.D2U})] x 100%
Issue 02 (2014-03-28)
Object
CELL, RNC
Unit/Range
%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
84
RAN16.0 KPI Reference
6 Retainability
Note
1. A RAB release caused by UE's state transition to PCH state should be considered as a normal RAB release for calculating PS Call Drop Ratio. 2. Why VS.RAB.normRel.PS.PCH and VS.RAB.AbnormRel.PS.PCH is subtracted from the denominator? l If a UE transit to PCH state and then to idle mode, it will be counted twice respectively in VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P, VS.DCCC.Succ.F2U, VS.DCCC.Succ.D2U ) and VS.RAB.NormRel.PS. l The same reason as VS.RAB.AbnormRel.PS.PCH. 3. The measurement object of the counters in Sum{*} is the cell, the RNC level KPI can be calculated approximately by aggregating all the cell level counters in the SRNC. Due to the counters are counted in the best cell of active set, If the best cell for the PS RAB Establishment located in DRNC via Iur interface, this scenario is not taken into account in the formula.
6.11 PS Call Drop Ratio (PCH & Combined Service) Table 6-11 PS Call Drop Ratio (PCH & Combined Service) Name
PS Call Drop Ratio (PCH & Combined Service)
Formula
Description
Compared with 6.10 PS Call Drop Ratio (PCH), this KPI deducts abnormal RAB releases caused by PS service timer expiration after a successful CS inter-RAT handover in combined CS+PS service. For CS+PS combined services, after CS inter-RAT handovers are complete, abnormal RAB releases caused by expiration of the PS service timer are regarded as problems occurring in GSM networks. Therefore, they are not taken into account for calculating PS Call Drop Ratio in UMTS networks.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
85
RAN16.0 KPI Reference
6 Retainability
Associated Counters
l PS Call Drop Ratio with PCH (Cell) = [(VS.RAB.AbnormRel.PSVS.MultiRAB.PSAbnormRel.ResumeExp VS.RAB.AbnormRel.PS.PCH VS.RAB.AbnormRel.PS.D2P VS.RAB.AbnormRel.PS.F2P)/ (VS.RAB.AbnormRel.PS + VS.RAB.NormRel.PS VS.RAB.AbnormRel.PS.PCH VS.RAB.NormRel.PS.PCH + VS.DCCC.D2P.Succ + VS.DCCC.Succ.F2P + VS.DCCC.Succ.F2U + VS.DCCC.Succ.D2U)] x 100% l PS Service Drop Ratio with PCH (RNC) = [(VS.RAB.AbnormRel.PS.RNC Sum{VS.MultiRAB.PSAbnormRel.ResumeExp} Sum{VS.RAB.AbnormRel.PS.PCH} Sum{VS.RAB.AbnormRel.PS.D2P} Sum{VS.RAB.AbnormRel.PS.F2P})/ (VS.RAB.AbnormRel.PS.RNC + VS.RAB.NormRel.PS.RNC Sum{VS.RAB.AbnormRel.PS.PCH} Sum{VS.RAB.NormRel.PS.PCH} + Sum{VS.DCCC.D2P.Succ} + Sum{VS.DCCC.Succ.F2P} + Sum{VS.DCCC.Succ.F2U} + Sum{VS.DCCC.Succ.D2U})] x 100%
Issue 02 (2014-03-28)
Object
Cell, RNC
Unit/Range
%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
86
RAN16.0 KPI Reference
6 Retainability
Note
1. A RAB release caused by UE's state transition to PCH state should be considered as a normal RAB release for calculating PS Call Drop Ratio. 2. Why VS.RAB.normRel.PS.PCH and VS.RAB.AbnormRel.PS.PCH is subtracted from the denominator? l If a UE transit to PCH state and then to idle mode, it will be counted twice respectively in VS.DCCC.D2P.Succ (or VS.DCCC.Succ.F2P, VS.DCCC.Succ.F2U, VS.DCCC.Succ.D2U ) and VS.RAB.NormRel.PS. l The same reason as VS.RAB.AbnormRel.PS.PCH. 3. The measurement object of the counters in Sum{*} is the cell, the RNC level KPI can be calculated approximately by aggregating all the cell level counters in the SRNC. Due to the counters are counted in the best cell of active set, If the best cell for the PS RAB Establishment located in DRNC via Iur interface, this scenario is not taken into account in the formula.
6.12 PS R99 Call Drop Ratio Table 6-12 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). Description of RAB Abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
87
RAN16.0 KPI Reference
6 Retainability
Associated Counters
PS R99 Call Drop Ratio (Cell) = (VS.RAB.AbnormRel.PSR99)/(VS.RAB.AbnormRel.PSR99 +VS.RAB.NormRel.PSR99) x 100% PS R99 Call Drop Ratio (RNC)= [VS.RAB.AbnormRel.PSR99+ (VS.RAB.AbnormRel.PS.Conv.Iur+ VS.RAB.AbnormRel.PS.Str.Iur+ VS.RAB.AbnormRel.PS.BE.IurVS.RAB.AbnormRel.HSDPA.Iur)]/ [VS.RAB.AbnormRel.PSR99+ VS.RAB.NormRel.PSR99+ (VS.RAB.NormRel.PS.Conv.Iur+ VS.RAB.NormRel.PS.Str.Iur+ VS.RAB.NormRel.PS.BE.IurVS.RAB.NormRel.HSDPA.Iur)+ (VS.RAB.AbnormRel.PS.Conv.Iur+ VS.RAB.AbnormRel.PS.Str.Iur+ VS.RAB.AbnormRel.PS.BE.IurVS.RAB.AbnormRel.HSDPA.Iur)]*100%
Object
CELL
Unit/Range
%
Note
This KPI involves the call drops of UEs in CELL_PCH, URA_PCH, or CELL_FACH state.
6.13 PS R99 Call Drop Ratio (PCH) Table 6-13 PS R99 Call Drop Ratio (PCH) Name
PS R99 Call Drop Ratio (PCH)
Formula
Description
Issue 02 (2014-03-28)
Compared with PS R99 Call Drop Ratio, this KPI takes the PCH state into account.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
88
RAN16.0 KPI Reference
6 Retainability
Associated Counters
PS R99 Call Drop Ratio with PCH (Cell) = [(VS.RAB.AbnormRel.PSR99VS.RAB.AbnormRel.PS.PCHVS.RAB.AbnormRel.PS.R99D2PVS.RAB.AbnormRel.PS.F2P)/ (VS.RAB.AbnormRel.PSR99+ VS.RAB.NormRel.PSR99VS.RAB.AbnormRel.PS.PCHVS.RAB.NormRel.PS.PCH+ VS.HSDPA.F2H.Succ+ VS.HSDPA.D2H.Succ+ VS.PSR99.D2P.Succ+ VS.DCCC.Succ.F2P+ VS.DCCC.Succ.F2U)] x 100%
Object
CELL
Unit/Range
%
Note
The occasion of a UE transferring out of PS R99 state (F2H, F2P, D2H) should be considered as a normal RAB release for calculating the formula of PS R99 Call Drop Ratio. RNC level KPI can be calculated approximately by aggregating all the cell level counters in SRNC. Due to the counters are counted in the best cell of active set, If the best cell for the PS R99 RAB Establishment located in DRNC 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.
6.14 PS BE Call Drop Ratio Table 6-14 PS BE Call Drop Ratio Name
PS BE Call Drop Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
89
RAN16.0 KPI Reference
6 Retainability
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). Description of RAB Abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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
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.
6.15 HSDPA Call Drop Ratio Table 6-15 HSDPA Call Drop Ratio Name
HSDPA Call Drop Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
90
RAN16.0 KPI Reference
6 Retainability
Description
This KPI provides the ratio of the HSDPA RAB abnormal Releases to the total HSDPA RAB Releases (Normal Release+ Abnormal Release) and is used to check the retainabililty of HSDPA Service within the UTRAN (RNC or Cluster). Description of RAB Abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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
l HSDPA Call Drop Ratio (Cell) = [(VS.HSDPA.RAB.AbnormRel)/ (VS.HSDPA.RAB.AbnormRel+ VS.HSDPA.RAB.NormRel+ VS.HSDPA.H2D.Succ+ VS.HSDPA.H2F.Succ+ VS.HSDPA.HHO.H2D.SuccOutIntraFreq+ VS.HSDPA.HHO.H2D.SuccOutInterFreq)] x 100% l HSDPA Call Drop Ratio (RNC) = [(Sum{VS.HSDPA.RAB.AbnormRel}+ Sum{VS.RAB.AbnormRel.HSDPA.Iur})/ (Sum{VS.HSDPA.RAB.AbnormRel}+ Sum{VS.RAB.AbnormRel.HSDPA.Iur}+ Sum{VS.RAB.NormRel.HSDPA.Iur}+ Sum{VS.HSDPA.RAB.NormRel}+ Sum{VS.HSDPA.H2D.Succ}+ Sum{VS.HSDPA.H2F.Succ}+ Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+ Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq})] x 100%
Object
CELL, RNC
Unit/Range
%
Note
RNC level KPI is calculated approximately by aggregating all the Cell and Iur level counters in SRNC. The successful channel transition is considered as normal HSDPA RAB release (Including the transitions due to mobility).
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
91
RAN16.0 KPI Reference
6 Retainability
6.16 HSDPA Call Drop Ratio (PCH) Table 6-16 HSDPA Call Drop Ratio (PCH) Name
HSDPA Call Drop Ratio (PCH)
Formula
Description
Compared with HSDPA Call Drop Ratio, this KPI takes the PCH state into account.
Associated Counters
l HSDPA Service Drop Ratio with PCH (Cell) = [(VS.HSDPA.RAB.AbnormRelVS.HSDPA.RAB.AbnormRel.H2P)/ (VS.HSDPA.RAB.AbnormRel+ VS.HSDPA.RAB.NormRel+ VS.HSDPA.HHO.H2D.SuccOutIntraFreq+ VS.HSDPA.HHO.H2D.SuccOutInterFreq+ VS.HSDPA.H2D.Succ+ VS.HSDPA.H2F.Succ+ VS.HSDPA.H2P.Succ)] x 100% l HSDPA Service Drop Ratio with PCH(RNC) = [(Sum{VS.HSDPA.RAB.AbnormRel}+ Sum{VS.RAB.AbnormRel.HSDPA.Iur}Sum{VS.HSDPA.RAB.AbnormRel.H2P})/ (Sum{VS.HSDPA.RAB.AbnormRel}+ Sum{VS.RAB.AbnormRel.HSDPA.Iur}+ Sum{VS.RAB.NormRel.HSDPA.Iur}+ Sum{VS.HSDPA.RAB.NormRel}+ Sum{VS.HSDPA.H2D.Succ}+ Sum{VS.HSDPA.H2F.Succ}+ Sum{VS.HSDPA.HHO.H2D.SuccOutIntraFreq}+ Sum{VS.HSDPA.HHO.H2D.SuccOutInterFreq}+ Sum{VS.HSDPA.H2P.Succ})] x 100%
Issue 02 (2014-03-28)
Object
CELL, RNC
Unit/Range
%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
92
RAN16.0 KPI Reference
6 Retainability
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.
6.17 HSUPA Call Drop Ratio Table 6-17 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). Description of RAB Abnormal Release: The RNC initially sends an IU RELEASE REQUEST/RAB 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.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
93
RAN16.0 KPI Reference
6 Retainability
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).
6.18 HSUPA Call Drop Ratio (PCH) Table 6-18 HSUPA Call Drop Ratio (PCH) Name
HSUPA Call Drop Ratio (PCH)
Formula
Description
Issue 02 (2014-03-28)
Compared with HSUPA Call Drop Ratio, this KPI takes the PCH state into account.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
94
RAN16.0 KPI Reference
6 Retainability
Associated Counters
l HSUPA Call Drop Ratio with PCH (Cell) = [(VS.HSUPA.RAB.AbnormRelVS.HSUPA.RAB.AbnormRel.E2P )/ (VS.HSUPA.RAB.AbnormRel+ VS.HSUPA.RAB.NormRel + VS.HSUPA.HHO.E2D.SuccOutIntraFreq + VS.HSUPA.HHO.E2D.SuccOutInterFreq+ VS.HSUPA.E2F.Succ + VS.HSUPA.E2D.Succ + VS.HSUPA.E2P.Succ )] x 100% l HSUPA Call Drop Ratio with PCH (RNC) = [(Sum{VS.HSUPA.RAB.AbnormRel}+ Sum{VS.RAB.AbnormRel.HSUPA.Iur}Sum{VS.HSUPA.RAB.AbnormRel.E2P} )/ (Sum{VS.HSUPA.RAB.AbnormRel}+ Sum{VS.HSUPA.RAB.NormRel}+ Sum{VS.RAB.AbnormRel.HSUPA.Iur}+ Sum{VS.RAB.NormRel.HSUPA.Iur}+ Sum{VS.HSUPA.HHO.E2D.SuccOutIntraFreq}+ Sum{VS.HSUPA.HHO.E2D.SuccOutInterFreq}+ Sum{VS.HSUPA.E2F.Succ} + Sum{VS.HSUPA.E2D.Succ} + Sum{VS.HSUPA.E2P.Succ} )] x 100%
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.
6.19 MBMS Service PTP drop Ratio Table 6-19 MBMS Service PTP drop Ratio Name
MBMS Service PTP drop Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
95
RAN16.0 KPI Reference
6 Retainability
Associated Counters
MBMS Service PTP Drop Ratio = [VS.MBMS.RB.PTP.Loss.Abnorm/(VS.MBMS.RB.PTP.Loss.Abnorm +VS.MBMS.RB.PTP.Loss.norm)]*100%
Object
CELL
Unit/Range
%
Note
The RNC level KPIs are calculated by aggregating all the cell counters.
6.20 DC-HSDPA Call Drop Ratio Table 6-20 DC-HSDPA Call Drop Ratio Name
DC-HSDPA Call Drop Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
96
RAN16.0 KPI Reference
6 Retainability
Description
This KPI evaluates the retainability of DC-HSDPA services in an RNC or a cluster. And this KPI takes the CELL_PCH or URA_PCH state into account. l Abnormal release: When an exception occurs, the RNC sends the CN an IU RELEASE REQUEST or an RAB RELEASE REQUEST message. If the RNC receives from the CN an RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling ConnectionRelease", this counter is incremented in the best cell for the UE. l Normal release: Normal releases includes RAB releases over the Iu interface and the switchover of the RAB from a technique to another one, involving the following scenarios: – RAB releases over the Iu interface – Fallback to the SC-HSDPA RAB through intra-cell channel switchovers – Fallback to the R99 RAB (including R99 RABs of UEs in the CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH state) through intra-cell channel switchovers – Fallback to SC-HSDPA RAB through inter-cell hard handovers (including intra-frequency and inter-frequency hard handovers) – Fallback to R99 RAB of UEs in the CELL_DCH state through intercell hard handovers (including intra-frequency and inter-frequency hard handovers) – Fallback to HSDPA RAB of SRB over DCH through the setup of combined services – Fallback to R99 RAB of UEs in the CELL_DCH state through the setup of combined services NOTE Unless otherwise stated, SRB over HSDPA users are those whose SRBs are carried on the HSDPA and that are in the CELL_DCH state.
Issue 02 (2014-03-28)
Associated Counters
Call Drop Rate of DC-HSDPA Services = [( VS.HSDPA.RAB.DC.AbnormRel — VS.HSDPA.RAB.AbnormRel.DC2P)/(VS.HSDPA.RAB.DC.AbnormRel + VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
97
RAN16.0 KPI Reference
6 Retainability
6.21 HSDPA 64QAM Call Drop Ratio Table 6-21 HSDPA 64QAM Call Drop Ratio Name
HSDPA 64QAM Call Drop Ratio
Formula
Description
This KPI evaluates the retainability of HSDPA 64QAM services in an RNC or a cluster. And this KPI takes the CELL_PCH or URA_PCH state into account. l Abnormal release: When an exception occurs, the RNC sends the CN an IU RELEASE REQUEST or an RAB RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE COMMAND message or an RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", this counter is incremented in the best cell for the UE. l Normal release: Normal releases include the RAB releases over the Iu interface and the switchover of the RAB from a technique to another one, involving the following scenarios: – RAB releases over the Iu interface – Fallback to the HSDPA RAB through intra-cell channel switchovers – Fallback to the R99 RAB (including R99 RABs of UEs in the CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH state) through intra-cell channel switchovers – Fallback to HSDPA RAB through inter-cell hard handovers (including intra-frequency and inter-frequency hard handovers) – Fallback to R99 RAB of UEs in the CELL_DCH state through intercell hard handovers (including intra-frequency and inter-frequency hard handovers)
Issue 02 (2014-03-28)
Associated Counters
Call Drop Rate of HSDPA+64QAM Services = [( VS.HSDPA.RAB.AbnormRel.64QAM — VS.HSDPA.RAB.AbnormRel.64QAM2P )/(VS.HSDPA.RAB.AbnormRel.64QAM + VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
98
RAN16.0 KPI Reference
6 Retainability
6.22 HSDPA MIMO Call Drop Ratio Table 6-22 HSDPA MIMO Call Drop Ratio Name
HSDPA MIMO Call Drop Ratio
Formula
Description
This KPI evaluates the retainability of HSDPA services in an RNC or a cluster. And this KPI takes the CELL_PCH or URA_PCH state into account. l Abnormal release: When an exception occurs, the RNC sends the CN an IU RELEASE REQUEST or an RAB RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE COMMAND message or an RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", this counter is incremented in the best cell for the UE. l Normal release: Normal releases includes RAB releases over the Iu interface and the switchover of the RAB from a technique to another one, involving the following scenarios: – RAB releases over the Iu interface – Fallback to the HSDPA RAB through intra-cell channel switchovers – Fallback to the R99 RAB (including R99 RABs of UEs in the CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH state) through intra-cell channel switchovers – Fallback to HSDPA RAB through inter-cell hard handovers (including intra-frequency and inter-frequency hard handovers) – Fallback to R99 RAB of UEs in the CELL_DCH state through intercell hard handovers (including intra-frequency and inter-frequency hard handovers)
Issue 02 (2014-03-28)
Associated Counters
HSDPA MIMO Call Drop Rate = [( VS.HSDPA.RAB.AbnormRel.MIMO — VS.HSDPA.RAB.AbnormRel.MIMO2P)/ (VS.HSDPA.RAB.AbnormRel.MIMO + VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object
CELL
Unit/Range
%
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
99
RAN16.0 KPI Reference
6 Retainability
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
6.23 HSDPA MIMO+64QAM Call Drop Ratio Table 6-23 HSDPA MIMO+64QAM Call Drop Ratio Name
HSDPA MIMO+64QAM Call Drop Ratio
Formula
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
100
RAN16.0 KPI Reference
6 Retainability
Description
This KPI evaluates the retainability of HSDPA services in an RNC or a cluster. And this KPI takes the CELL_PCH or URA_PCH state into account. l Abnormal release: When an exception occurs, the RNC sends the CN an IU RELEASE REQUEST or an RAB RELEASE REQUEST message. When the RNC receives from the CN an IU RELEASE COMMAND message or an RAB ASSIGNMENT REQUEST message with a cause value other than "User Inactivity", "Normal Release", "Successful Relocation", "Network Optimization", or "UE Generated Signalling Connection Release", this counter is incremented in the best cell for the UE. l Normal release: Normal releases include the RAB releases over the Iu interface and the switchover of the RAB from a technique to another one, involving the following scenarios: – RAB releases over the Iu interface – Fallback to the HSDPA RAB through intra-cell channel switchovers – Fallback to the HSDPA MIMO RAB through intra-cell channel switchovers – Fallback to the HSDPA 64QAM RAB through intra-cell channel switchovers – Fallback to the R99 RAB (including R99 RABs of UEs in the CELL_DCH, CELL_FACH, CELL_PCH, and URA_PCH state) through intra-cell channel switchovers – Fallback to HSDPA RAB through inter-cell hard handovers (including intra-frequency and inter-frequency hard handovers) – Fallback to HSDPA MIMO RAB through inter-cell hard handovers (including intra-frequency and inter-frequency hard handovers) through inter-cell hard handovers – Fallback to HSDPA 64QAM RAB through inter-cell hard handovers (including intra-frequency and inter-frequency hard handovers) – Fallback to R99 RAB of UEs in the CELL_DCH state through intercell hard handovers (including intra-frequency and inter-frequency hard handovers)
Issue 02 (2014-03-28)
Associated Counters
HSDPA MIMO+64QAM Call Drop Rate = [( VS.HSDPA.RAB.AbnormRel.MIMO64QAM — VS.HSDPA.RAB.AbnormRel.MIMO64QAM2P)/ (VS.HSDPA.RAB.AbnormRel.MIMO64QAM + VS.HSDPA.RAB.NormRel.DC.All )] x 100%
Object
CELL
Unit/Range
%
Note
RNC-level KPIs are obtained by accumulating values of cell-level counters.
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
101
RAN16.0 KPI Reference
7 Service Integrity
7
Service Integrity
About This Chapter 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.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
102
RAN16.0 KPI Reference
7 Service Integrity
7.1 Average UL Throughput for PS R99 Service Table 7-1 Average UL Throughput for PS R99 Service (Active Set Cell) Name
Average UL Throughput for PS R99 Service (Active Set Cell)
Description
These counters provide the average uplink rates of different PS R99 services in the cells of the active set. The UL traffic (excluding the RLC header and the retransmitted data, unit: bit) and the Data transfer duration (unit: ms) of each kind of PS R99 services are accumulated in the measurement period for the cells that are under the SRNC. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the Average UL Throughput for each PS R99 Service.
Associated Counters
Average UL Throughput for PS R99 Service (Active Set Cell) = 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.Bkg.Kbps.UL144 + VS.PS.Bkg.Kbps.UL256 + VS.PS.Bkg.Kbps.UL384 + 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.Int.Kbps.UL144 + VS.PS.Int.Kbps.UL256 + VS.PS.Int.Kbps.UL384 + 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
Issue 02 (2014-03-28)
Object
CELL
Unit/Range
kbit/s
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
103
RAN16.0 KPI Reference
7 Service Integrity
Note
None
Table 7-2 Average UL Throughput for PS R99 BE Service of a Single User (Best Cell) Name
Average UL Throughput for PS R99 BE Service of a Single User (Best Cell)
Description
This KPI provides the average uplink throughput for PS R99 BE services of a single user in a best cell. The uplink throughput (excluding the RLC headers and retransmitted data) for PS BE services of all users on the DCH is accumulated in a measurement period. At the same time, the number of times when the value of the sampled uplink throughput is not 0 is accumulated. At the end of the measurement period, the RNC divides the total uplink throughput by the total sampling times to obtain the average uplink throughput for PS R99 services of a single user in a best cell.
Associated Counters
Average UL Throughput for PS R99 BE Service of a Single User (Best Cell) = VS.PS.BE.DCH.UL.SumThroughput/ VS.PS.BE.DCH.UL.SamplesThroughput
Object
CELL
Unit/Range
kbit/s
Note
None
7.2 Average DL Throughput for PS R99 Service Table 7-3 Average DL Throughput for PS R99 Service (Active Set Cell) Name
Average DL Throughput for PS R99 Service (Active Set Cell)
Description
These counters provide the average downlink rates of different PS R99 services in the cells of the active set. The DL traffic (excluding the RLC header and the retransmitted data, unit: bit) and the Data transfer duration (unit: ms) of each kind of PS R99 services are accumulated in the measurement period for the cells that are under the SRNC. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the Average DL Throughput for each PS R99 Service.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
104
RAN16.0 KPI Reference
7 Service Integrity
Associated Counters
Average DL Throughput for PS R99 Service (Active Set Cell) = 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.Bkg.Kbps.DL144 + VS.PS.Bkg.Kbps.DL256 + VS.PS.Bkg.Kbps.DL384 + 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.Int.Kbps.DL144 + VS.PS.Int.Kbps.DL256 + VS.PS.Int.Kbps.DL384 + 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.Str.Kbps.DL144 + VS.PS.Str.Kbps.DL256 + VS.PS.Str.Kbps.DL384 + VS.PS.Conv.Kbps.DL
Object
CELL
Unit/Range
kbit/s
Note
None
Table 7-4 Average DL Throughput for PS R99 BE Service of a Single User (Best Cell) Name
Issue 02 (2014-03-28)
Average DL Throughput for PS R99 BE Service of a Single User (Best Cell)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
105
RAN16.0 KPI Reference
7 Service Integrity
Description
This KPI provides the average downlink throughput for PS R99 BE services of a single user in a best cell. The downlink throughput (excluding the RLC headers and retransmitted data) of PS BE services for all users on the DCH is accumulated in a measurement period. At the same time, the number of times when the value of the sampled downlink throughput is not 0 is accumulated. At the end of the measurement period, the RNC divides the total downlink throughput by the total sampling times to obtain the average downlink throughput for PS R99 services of a single user in a best cell.
Associated Counters
Average DL Throughput for PS R99 BE Service of a Single User (Best Cell) = VS.PS.BE.DCH.DL.SumThroughput + VS.PS.BE.DCH.DL.SamplesThroughput
Object
CELL
Unit/Range
kbit/s
Note
None
7.3 Average UL BLER for CS Service Table 7-5 Average UL BLER for CS Service Name
Average UL BLER for CS Service
Description
These counters provide the UL BLER of AMR and CS 64K Conv. services on the DCH in the best cell. The counters are triggered in the best cell when the number of UL TBs carrying the CS services on the DCH reaches the defined sampling window (500 TBs).
Associated Counters
VS.ULBler.AMR
Object
CELL
Unit/Range
%
Note
None
VS.ULBler.CS64
7.4 Average UL BLER for PS Service Table 7-6 Average UL BLER for PS Service Name
Issue 02 (2014-03-28)
Average UL BLER for PS Service
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
106
RAN16.0 KPI Reference
7 Service Integrity
Description
This counter provides the UL BLER of PS services on the DCH in the best cell. The counters are triggered in the best cell when the number of UL TBs carrying the PS services on the DCH reaches the defined sampling window (500 TBs).
Associated Counters
Average UL BLER for PS Service = VS.ULBler.PS.BE.DCH.8 + VS.ULBler.PS.BE.DCH.16 + VS.ULBler.PS.BE.DCH.32 + VS.ULBler.PS.BE.DCH.64 + VS.ULBler.PS.BE.DCH.128 + VS.ULBler.PS.BE.DCH.144 + VS.ULBler.PS.BE.DCH.256 + VS.ULBler.PS.BE.DCH.384 + VS.ULBler.PS.BE.RACH + VS.ULBler.PS.Conv + VS.ULBler.PS.Str
Object
CELL
Unit/Range
%
Note
None
7.5 HSDPA Throughput Table 7-7 Mean Throughput for One HSDPA User Name
Mean Throughput for One HSDPA User
Description
This counter indicates the mean downlink throughput for ONE HSDPA UE in a cell. When the data is transferred to an HSDPA serving cell, the RNC measures the data transfer time of all the UEs and the total bytes sent in the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean downlink throughput of MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.
Issue 02 (2014-03-28)
Associated Counters
Mean Throughput for One HSDPA User =
Object
CELL
Unit/Range
kbit/s
VS.HSDPA.MeanChThroughput
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
107
RAN16.0 KPI Reference
7 Service Integrity
Note
For 3900 series NodeBs, it is recommended that you use the NodeB counters in the following formula to calculate the single user throughput. These NodeB counters measure the valid throughput when data exists in the user buffer every transmission time interval (TTI). In this case, the value of this KPI is more accurate for UEs. The throughput of a single user at the NodeB MAChs layer is calculated using the following formula: VS.HSDPA.DataOutput.Traffic/ (VS.HSDPA.DataTtiNum.User x 2) NOTE VS.HSDPA.DataOutput.Traffic measures the total traffic volume of the MAC-hs/ MAC-ehs PDUs with ACKs from all users in a TTI within a measurement period. (Unit : bit). VS.HSDPA.DataTtiNum.User measures the total number of user-level TTIs (TTI = 2ms) within which there is data to transmit in HSDPA user queue buffers within a measurement period. (VS.HSDPA.DataTtiNum.User x 2) and converts the number of TTIs to the data transmission time.
Table 7-8 Mean Throughput for One HSDPA Cell Name
Mean Throughput for One HSDPA Cell
Description
This counter provides the MAC-hs throughput when at least one HSDPA user is transferring data at the physical layer during the entire measurement period.
Associated Counters
Mean Throughput for One HSDPA Cell =
Object
NodeB
Unit/Range
kbit/s
Note
1. We can apply the following formula to get the Mean HSDPA Cell Throughput within RNC approximately:
VS.DataOutput.Mean/(VS.DataTtiRatio.Mean VS.HSDPA.InactiveDataTtiRatio.Mean)
HSDPA Cell Throughput (RNC Cell) = VS.HSDPA.MeanChThroughput.TotalBytes x 8/ [{SP} x 60]/1000 Where: l {SP} is the Statistic Period with the unit of Minute. l The KPI may not be accurate under the following condition: there is no HSDPA User transferring data for a while during the total measurement period. Therefore, the KPI should be evaluated during busy hour for accuracy. 2. For 3900 series NodeBs, the HSDPA throughput at the MAC-hs layer is calculated using the following formula: VS.HSDPA.DataOutput.Traffic/ [(VS.DataTtiRatio.Mean VS.HSDPA.InactiveDataTtiRatio.Mean) x {SP} x 60]
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
108
RAN16.0 KPI Reference
7 Service Integrity
7.6 HSUPA Throughput Table 7-9 Mean Throughput for One HSUPA User Name
Mean Throughput for One HSUPA User
Description
This counter indicates the mean uplink throughput for ONE HSUPA UE in a cell. When the data is received in HSUPA active cells, the RNC measures the data transfer time of all the UEs and the total bytes received in the cell. At the end of the measurement period, the RNC divides the total bytes by the total data transfer time to obtain the mean uplink throughput of MAC-d flow in the cell. The RLC header and the retransfer data are excluded.
Associated Counters
Mean Throughput for One HSUPA User =
Object
CELL
Unit/Range
kbit/s
Note
It is recommended that you use the NodeB counters in the following formula to calculate the single user throughput. These NodeB counters measure the actual transmission rate sampled every transmission time interval (TTI) over the air interface. In this case, the value of this KPI is more accurate for UEs. The throughput of a single user transmitting the TRB data at the NodeB MACe/i layer is calculated using the following formula:
VS.HSUPA.MeanChThroughput
(VS.HSUPA.2msTTI.Traffic + VS.HSUPA.10msTTI.Traffic)/ (VS.HSUPA.2msPDU.TTI.Num x 0.002 + VS.HSUPA.10msPDU.TTI.Num x 0.01)
Table 7-10 Mean Throughput for One HSUPA Cell Name
Issue 02 (2014-03-28)
Mean Throughput for One HSUPA Cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
109
RAN16.0 KPI Reference
7 Service Integrity
Description
This counter provides the Mean HSUPA Cell Throughput when at least one HSUPA UE is transmitting data during the entire measurement period. When the data (including SRB and TRB data) of HSUPA UEs is received in HSUPA active cells, the NodeB measures the total data that UEs successfully receive at the MAC-e/i layer in the serving cell. At the same time, the NodeB measures the number of TTIs when at least one HSUPA UE is transmitting data to obtain the total transmission duration. (If there are multiple UEs transmitting data in a TTI, this number is increased by one.) At the end of the measurement period, the NodeB divides the total successfully received data by the total transmission duration to obtain the average throughput at the MAC-e/i layer in one HSUPA cell. When a UE performs a softer handover, the data of this UE is calculated in both the original and target cells.
Associated Counters
Mean Throughput for One HSUPA Cell = VS.HSUPA.Thruput.ROTAll/ (VS.HSUPA.DataTtiNum x 0.002)
Object
NodeB
Unit/Range
kbit/s
Note
None
7.7 PS UL Throughput of RNC Table 7-11 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.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
110
RAN16.0 KPI Reference
7 Service Integrity
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
7.8 PS DL Throughput of RNC Table 7-12 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
Issue 02 (2014-03-28)
Object
RNC
Unit/Range
kbit/s
Note
None
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
111
RAN16.0 KPI Reference
7 Service Integrity
7.9 MBMS Service Throughput Table 7-13 MBMS Service Throughput
Issue 02 (2014-03-28)
Name
MBMS Service Throughput
Description
These KPIs are used to check the throughput of MBMS service in a cell.
Associated Counters
VS.MBMS.PTM.MeanThroughput
Object
CELL
Unit/Range
kbit/s
Note
None
VS.MBMS.PTP.MeanThroughput
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
112
RAN16.0 KPI Reference
8 Traffic
8
Traffic
About This Chapter Traffic-related KPIs are used to check the circulated traffic such as CS Equivalent Erlang, PS Traffic, and Mean UE number for various kinds of services in an RNC or a Cluster.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
113
RAN16.0 KPI Reference
8 Traffic
8.1 CS Equivalent Erlang of RNC Table 8-1 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
Object
RNC
Unit/Range
Erl
Note
None
VS.CSLoad.MaxErlang.Equiv.RNC
8.2 Number of CS Users Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
114
RAN16.0 KPI Reference
8 Traffic
Table 8-2 Number of CS Users Name
Number of CS Users
Description
These counters provide the number of CS (AMR and VP) users with different UL and DL rates in cells of the active set. The related RB number is sampled periodically in cells of the active set. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Associated Counters
l Cell Counters (VS.RB.AMR.DL.12.2+ VS.RB.AMR.DL.10.2+ VS.RB.AMR.DL.7.95+ VS.RB.AMR.DL.7.4+ VS.RB.AMR.DL.6.7+ VS.RB.AMR.DL.5.9+ VS.RB.AMR.DL.5.15+ VS.RB.AMR.DL.4.75); VS.RB.CS.Conv.DL.64 l RNC Counters (VS.RB.AMR.DL.4.75.RNC+ VS.RB.AMR.DL.5.15.RNC+ VS.RB.AMR.DL.5.9.RNC+ VS.RB.AMR.DL.6.7.RNC+ VS.RB.AMR.DL.7.4.RNC+ VS.RB.AMR.DL.7.95.RNC+ VS.RB.AMR.DL.10.2.RNC+ VS.RB.AMR.DL.12.2.RNC); VS.RB.CS.Conv.DL.64.RNC
Object
CELL, RNC
Unit/Range
None
Note
The Unit is average user number, to get Erlang, the counter value should be multiplied by {SP}/60, where {SP} is the measurement period (unit: minute). (Only for BSC6900)For a VP service, V1 platform equals to four Erlangs and V2 platform equals to two Erlangs.
8.3 Number of PS R99 Users
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
115
RAN16.0 KPI Reference
8 Traffic
Table 8-3 Number of PS R99 Users Name
Number of PS R99 Users
Description
These counters provide the number of PS R99 users with different UL and DL rates in cells of the active set. The related RB number is sampled periodically in cells of the active set. At the end of the measurement period, the value of each counter is obtained as follows: dividing the accumulated value of each sampling point by the number of sampling times.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
116
RAN16.0 KPI Reference
8 Traffic
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.Conv.UL.39.2 VS.RB.PS.Conv.UL.38.8 VS.RB.PS.Str.UL.8 VS.RB.PS.Str.UL.16 VS.RB.PS.Str.UL.32 VS.RB.PS.Str.UL.64 VS.RB.PS.Str.UL.128 VS.RB.PS.Str.UL.144 VS.RB.PS.Str.UL.256.384 VS.RB.PS.Conv.UL.64 l DL Counters: VS.RB.PS.Bkg.DL.8 VS.RB.PS.Bkg.DL.16 VS.RB.PS.Bkg.DL.32 VS.RB.PS.Bkg.DL.64 VS.RB.PS.Bkg.DL.128 VS.RB.PS.Bkg.DL.144 VS.RB.PS.Bkg.DL.256 VS.RB.PS.Bkg.DL.384
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
117
RAN16.0 KPI Reference
8 Traffic
VS.RB.PS.Int.DL.8 VS.RB.PS.Int.DL.16 VS.RB.PS.Int.DL.32 VS.RB.PS.Int.DL.64 VS.RB.PS.Int.DL.128 VS.RB.PS.Int.DL.144 VS.RB.PS.Int.DL.256 VS.RB.PS.Int.DL.384 VS.RB.PS.Conv.DL.42.8 VS.RB.PS.Conv.DL.40 VS.RB.PS.Conv.DL.39.2 VS.RB.PS.Conv.DL.38.8 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.Bkg.UL.16.RNC VS.RB.PS.Bkg.UL.32.RNC VS.RB.PS.Bkg.UL.64.RNC VS.RB.PS.Bkg.UL.128.RNC VS.RB.PS.Bkg.UL.144.RNC VS.RB.PS.Bkg.UL.256.RNC VS.RB.PS.Bkg.UL.384.RNC VS.RB.PS.Int.UL.8.RNC VS.RB.PS.Int.UL.16.RNC VS.RB.PS.Int.UL.32.RNC VS.RB.PS.Int.UL.64.RNC VS.RB.PS.Int.UL.128.RNC VS.RB.PS.Int.UL.144.RNC VS.RB.PS.Int.UL.256.RNC VS.RB.PS.Int.UL.384.RNC VS.RB.PS.Str.UL.8.RNC Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
118
RAN16.0 KPI Reference
8 Traffic
VS.RB.PS.Str.UL.16.RNC VS.RB.PS.Str.UL.32.RNC VS.RB.PS.Str.UL.64.RNC VS.RB.PS.Str.UL.128.RNC VS.RB.PS.Str.UL.144.RNC VS.RB.PS.Str.UL.256.384.RNC VS.RB.PS.Conv.UL.8.RNC VS.RB.PS.Conv.UL.16.RNC VS.RB.PS.Conv.UL.32.RNC VS.RB.PS.Conv.UL.64.RNC VS.RB.PS.Conv.UL.38.8.RNC VS.RB.PS.Conv.UL.42.8.RNC VS.RB.PS.Conv.UL.40.RNC VS.RB.PS.Conv.UL.39.2.RNC l DL Counters: VS.RB.PS.Bkg.DL.8.RNC VS.RB.PS.Bkg.DL.16.RNC VS.RB.PS.Bkg.DL.32.RNC VS.RB.PS.Bkg.DL.64.RNC VS.RB.PS.Bkg.DL.128.RNC VS.RB.PS.Bkg.DL.144.RNC VS.RB.PS.Bkg.DL.256.RNC VS.RB.PS.Bkg.DL.384.RNC VS.RB.PS.Int.DL.8.RNC VS.RB.PS.Int.DL.16.RNC VS.RB.PS.Int.DL.32.RNC VS.RB.PS.Int.DL.64.RNC VS.RB.PS.Int.DL.128.RNC VS.RB.PS.Int.DL.144.RNC VS.RB.PS.Int.DL.256.RNC VS.RB.PS.Int.DL.384.RNC VS.RB.PS.Str.DL.8.RNC VS.RB.PS.Str.DL.16.RNC VS.RB.PS.Str.DL.32.RNC VS.RB.PS.Str.DL.64.RNC VS.RB.PS.Str.DL.128.RNC VS.RB.PS.Str.DL.144.RNC VS.RB.PS.Str.DL.256.384.RNC VS.RB.PS.Conv.DL.8.RNC Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
119
RAN16.0 KPI Reference
8 Traffic
VS.RB.PS.Conv.DL.16.RNC VS.RB.PS.Conv.DL.32.RNC VS.RB.PS.Conv.DL.64.RNC VS.RB.PS.Conv.DL.42.8.RNC VS.RB.PS.Conv.DL.40.RNC VS.RB.PS.Conv.DL.39.2.RNC VS.RB.PS.Conv.DL.38.8.RNC Object
CELL, RNC
Unit/Range
None
Note
The Unit is average user number, to get Erlang, should be multiplied by {SP}/ 60;
8.4 Number of HSDPA Users Table 8-4 Number of HSDPA Users Name
Number of HSDPA Users
Description
This KPI provides the mean and maximum number of HSDPA UEs in an HSDPA serving cell. The RNC periodically samples the number of HSDPA UEs in the HSDPA serving cell. At the end of the measurement period, the RNC obtains the mean and maximum number of HSDPA UEs.
Associated Counters
VS.HSDPA.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
None
VS.HSDPA.UE.Max.Cell
8.5 Number of HSUPA Users Table 8-5 Number of HSUPA Users Name
Issue 02 (2014-03-28)
Number of HSUPA Users
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
120
RAN16.0 KPI Reference
8 Traffic
Description
These KPIs provide the mean and maximum number of HSUPA UEs in an HSUPA serving cell. The RNC periodically samples the number of HSUPA UEs in the HSUPA serving cell. At the end of the measurement period, the RNC obtains the mean and maximum number of HSUPA UEs.
Associated Counters
VS.HSUPA.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
VS.HSUPA.UE.Max.Cell
8.6 Number of E-FACH Users Table 8-6 Number of E-FACH Users Name
Mean Number of E-FACH Users
Description
This KPI provides the average number of UEs that are carried on the E-FACH in the cell The system periodically samples the UEs that are carried on the EFACH. At the end of the measurement period, the average number of UEs that are carried on the E-FACH in the measurement period is obtained by dividing the accumulated value of sample data in the period by the number of samples.
Associated Counters
VS.EFACHUEs
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.7 Number of E-RACH Users Table 8-7 Number of E-RACH Users Name
Issue 02 (2014-03-28)
Number of E-RACH Users
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
121
RAN16.0 KPI Reference
8 Traffic
Description
This KPI provide the average numbers of UEs that are carried on the E-RACH in the cell. The RNC takes a sample from the number of UEs carried on the E-RACH in a cell every 5s. At the end of the measurement period, the average number of UEs that are carried on the E-RACH is obtained by dividing the accumulated value of sample data in the period by the number of samples.
Associated Counters
Number of E-RACH Users =
Object
CELL
Unit/Range
None
Note
You are advised to measure this KPI during busy hours.
VS.ERACHUEs
8.8 Number of CS Over HSPA Users Table 8-8 Number of CS Over HSPA Users Name
Mean Number of CS Over HSPA Users
Description
This KPI provides the average number of CS over HSPA users in the cell. The system periodically samples the number of CS Over HSPA. At the end of a statistical period, the system divides the sampling number by the sum at each sampling point to obtain the average number of CS Over HSPA during the period.
Associated Counters
VS.HSPA.UE.Mean.CS.Conv.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.9 Number of HSDPA 64QAM Users Table 8-9 Number of HSDPA 64QAM Users Name
Issue 02 (2014-03-28)
Mean Number of HSDPA 64QAM Users
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
122
RAN16.0 KPI Reference
8 Traffic
Description
This KPI provides the average number of HSDPA 64QAM UEs in an HSDPA cell. The number of HSDPA 64QAM UEs is sampled periodically in the HSDPA cells. At the end of the measurement period, the RNC divides the accumulated time weight value of each sampling point by the sampling period, thus obtaining the average number of 64QAM UEs in the HSDPA cell.
Associated Counters
VS.HSDPA.64QAM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.10 Number of HSDPA MIMO Users Table 8-10 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 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 MIMO UEs in the HSDPA cell.
Associated Counters
VS.HSDPA.MIMO.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.11 Number of HSUPA 16QAM users Table 8-11 Number of HSUPA 16QAM users Name
Issue 02 (2014-03-28)
Mean Number of HSUPA 16QAM users
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
123
RAN16.0 KPI Reference
8 Traffic
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 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 16QAM UEs in the HSUPA cell.
Associated Counters
VS.HSUPA.16QAM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.12 Number of HSDPA MIMO64QAM Users Table 8-12 Number of HSDPA MIMO64QAM Users Name
Mean Number of HSDPA MIMO64QAM Users
Description
This KPI provides the average number of HSDPA MIMO64QAM UEs in an HSDPA cell. The system periodically samples the number of MIMO+64QAM UEs. At the end of the measurement period, by dividing the accumulated value of sample data in the period by the number of samples, the average number of MIMO +64QAM UEs in the measurement period is obtained.
Associated Counters
VS.HSDPA.MIMO64QAM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.13 Number of MBMS Users Table 8-13 Number of MBMS Users Name
Issue 02 (2014-03-28)
Mean Number of MBMS Users
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
124
RAN16.0 KPI Reference
8 Traffic
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 VS.MBMS.PTP.UE.Channel1.Mean.Cell VS.MBMS.PTM.UE.Channel1.Mean.Cell VS.MBMS.PTP.UE.Channel2.Mean.Cell VS.MBMS.PTM.UE.Channel2.Mean.Cell VS.MBMS.PTP.UE.Channel3.Mean.Cell VS.MBMS.PTM.UE.Channel3.Mean.Cell VS.MBMS.PTP.UE.Channel4.Mean.Cell VS.MBMS.PTM.UE.Channel4.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
8.14 HSDPA RLC Traffic Volume Table 8-14 HSDPA RLC Traffic Volume Name
HSDPA RLC Traffic Volume
Description
This KPI provides the total downlink bytes of all the HSDPA MAC-d flows in a cell. When the data is transmitted to an HSDPA serving cell, the RNC measures the number of total bytes sent in the downlink (including data of all types of services) at the RLC layer for the MAC-d flow in the cell. The RLC header and the retransmitted data are excluded.
Issue 02 (2014-03-28)
Associated Counters
VS.HSDPA.MeanChThroughput.TotalBytes
Object
CELL
Unit/Range
byte
Note
None Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
125
RAN16.0 KPI Reference
8 Traffic
8.15 HSUPA RLC Traffic Volume Table 8-15 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
8.16 R99 Service UL Traffic Volume Table 8-16 R99 Service UL Traffic Volume Name
R99 Service UL Traffic Volume
Description
These KPIs provide the uplink traffic volume of different R99 services in all cells of the active set. The UL traffic volume (excluding the RLC header and the retransmitted data) of each kind of R99 services over the RLC layer are accumulated for all cells of the active set within SRNC.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
126
RAN16.0 KPI Reference
8 Traffic
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.Bkg.UL.16.Traffic VS.PS.Bkg.UL.32.Traffic VS.PS.Bkg.UL.64.Traffic VS.PS.Bkg.UL.128.Traffic VS.PS.Bkg.UL.144.Traffic VS.PS.Bkg.UL.256.Traffic VS.PS.Bkg.UL.384.Traffic VS.PS.Int.UL.8.Traffic VS.PS.Int.UL.16.Traffic VS.PS.Int.UL.32.Traffic VS.PS.Int.UL.64.Traffic VS.PS.Int.UL.128.Traffic VS.PS.Int.UL.144.Traffic VS.PS.Int.UL.256.Traffic VS.PS.Int.UL.384.Traffic VS.PS.Str.UL.8.Traffic VS.PS.Str.UL.16.Traffic VS.PS.Str.UL.32.Traffic VS.PS.Str.UL.64.Traffic VS.PS.Str.UL.128.Traffic VS.PS.Conv.UL.Traffic
Object
CELL
Unit/Range
bit
Note
None
8.17 R99 Service DL Traffic Volume Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
127
RAN16.0 KPI Reference
8 Traffic
Table 8-17 R99 Service DL Traffic Volume Name
R99 Service DL Traffic Volume
Description
These KPIs provide the downlink traffic volume of different R99 services in all cells of the active set. The DL traffic volume (excluding the RLC header and the retransmitted data) of each kind of R99 services over the RLC layer are accumulated for all cells of the active set within SRNC.
Issue 02 (2014-03-28)
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
128
RAN16.0 KPI Reference
8 Traffic
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.Bkg.DL.16.Traffic VS.PS.Bkg.DL.32.Traffic VS.PS.Bkg.DL.64.Traffic VS.PS.Bkg.DL.128.Traffic VS.PS.Bkg.DL.144.Traffic VS.PS.Bkg.DL.256.Traffic VS.PS.Bkg.DL.384.Traffic VS.PS.Int.DL.8.Traffic VS.PS.Int.DL.16.Traffic VS.PS.Int.DL.32.Traffic VS.PS.Int.DL.64.Traffic VS.PS.Int.DL.128.Traffic VS.PS.Int.DL.144.Traffic VS.PS.Int.DL.256.Traffic VS.PS.Int.DL.384.Traffic VS.PS.Str.DL.8.Traffic VS.PS.Str.DL.16.Traffic VS.PS.Str.DL.32.Traffic VS.PS.Str.DL.64.Traffic VS.PS.Str.DL.128.Traffic VS.PS.Str.DL.144.Traffic VS.PS.Str.DL.256.Traffic VS.PS.Str.DL.384.Traffic VS.PS.Conv.DL.Traffic
Issue 02 (2014-03-28)
Object
CELL
Unit/Range
bit
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
129
RAN16.0 KPI Reference
8 Traffic
Note
None
8.18 E-FACH Traffic Volume Table 8-18 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
8.19 E-RACH Traffic Volume Table 8-19 E-RACH Traffic Volume Name
E-RACH Traffic Volume
Description
This KPI provides the bytes of UL MAC PDUs (including the signaling data and the service data, not including the FP header) received by the CRNC over the ERACH FP on the Iub interface. The measurement is triggered when the CRNC sends UL data over the ERACH FP on the Iub interface.
Issue 02 (2014-03-28)
Associated Counters
E-RACH Traffic Volume =
Object
CELL
Unit/Range
byte
Note
None
VS.CRNCIubBytesERACH.Rx
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
130
RAN16.0 KPI Reference
8 Traffic
8.20 Average Number of DC-HSDPA Users Table 8-20 Average Number of DC-HSDPA Users Name
Average Number of DC-HSDPA Users
Description
This KPI measures the average number of DC-HSDPA users that use this cell as the primary or secondary carrier cell. The RNC takes samples of the number of DC-HSDPA users that use a certain cell as the primary or secondary cell every 5 seconds in a measurement period. At the end of the measurement period, the RNC obtains the value of this counter by dividing the accumulated number by the number of sampling times.
Issue 02 (2014-03-28)
Associated Counters
VS.HSDPA.DC.PRIM.UE.Mean.Cell
Object
CELL
Unit/Range
None
Note
The KPI should be collected during busy hour.
VS.HSDPA.DC.SEC.UE.Mean.Cell
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
131
