Performance Indicators
DN05191189
Issue 08
Approval Date 2014-03-05
document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Solutions and Networks. The documen- tation has been prepared to be used by professional and properly trained personnel, and the cus-tomer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments as part of the process of continuous development and improvement of the documenta-tion.
The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability aris-ing in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Solutions and Networks and the customer. However, Nokia Solutions and Networks has made all reasonable efforts to ensure that the instructions con-tained in the document are adequate and free of material errors and omissions. Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document.
Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DA-TA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respec-tive owners, and they are mentioned for identification purposes only.
Copyright © Nokia Solutions and Networks 2014. All rights reserved
f
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components. If you should have questions regarding our Environmental Policy or any of the environmental ser-vices we offer, please contact us at Nokia Solutions and Networks for any additional information.
1.1.1 Structure of key performance indicators... 16 1.1.2 Classification of key performance indicators ... 17 1.1.3 Network and user key performance indicators... 18 1.1.4 Summary of different KPI viewpoints... 18 1.2 Calls in WCDMA RAN... 21 1.2.1 Definition of call from the WCDMA RAN perspective...21 1.2.2 Call Setup Success rates (CSSR) in NSN-based WCDMA RAN.26 1.2.3 Call Success Rates (CSR) in NSN-based WCDMA RAN... 28 1.3 Resource usage in NSN-based WCDMA RAN... 29 1.3.1 Principles for resource reservation related to services... 29 1.3.2 RAB Setup and Access Complete Rates... 29 1.3.3 RAB Success Rates... 30 1.3.4 Packet Session/HSPA Setup Success Rates...30 1.3.5 Packet Session/HSPA Success Rates... 30 1.3.6 Packet Session/R99 Setup Success Rates... 31 1.3.7 Packet Session/R99 Success Rates... 31 1.4 Different KPI levels...31 1.4.1 Principles of using defined UMTS architecture... 32 1.4.2 Principles of using defined QoS architecture... 32 1.4.3 Access network level KPIs... 32 1.4.4 RNC function level KPIs... 33 1.4.5 Transport Resource Manager level KPIs... 34 1.4.6 Access point-level KPIs...35 1.5 System Program Report...36 1.5.1 Principles of System Program Report ... 36 1.5.2 System Program Report content... 36 2 Terms and definitions... 47 3 Available WCDMA RAN key performance indicators... 50 4 Available Key Performance Indicators per Formula... 64 4.1 Access network level...64 4.1.1 Access network level indicators for accessibility... 64 4.1.1.1 Call Setup Success Ratio (CSSR) [%]... 64 4.1.1.2 LCS Setup [%]...71 4.1.1.3 RRC Setup Complete Ratio [%]... 72 4.1.1.4 RRC Setup and Access Complete Ratio [%]... 72 4.1.1.5 RAB Setup and Access Complete Ratio [%]... 75
4.1.2 Access network level indicators for retainability... 85 4.1.2.1 Call Success Ratio (CSR) [%]... 85 4.1.2.2 RRC Success Ratio [%]... 85 4.1.2.3 RRC Connection releases [#]...86 4.1.2.4 RAB Success Ratio [%]...87 4.1.2.5 Packet Session Success Ratio (SSR) [%]... 94 4.1.2.6 RAB Success Ratio, Multi-RAB Services [%]...96 4.1.2.7 HS-FACH Success Ratio [%]... 96 4.1.3 Access network level indicators for usage... 97 4.1.3.1 CS service duration [minutes]... 97 4.1.3.2 PS duration [minutes]... 98 4.1.3.3 CS service duration before call drop [minutes]... 99 4.1.3.4 PS service duration before call drop [minutes]...101 4.1.3.5 PS service volume before RAB drop [Mbit/ Dropped RAB]...103 4.1.3.6 Erlang [Erlang]... 107 4.1.3.7 Requested SRNS Relocation Attempt Numbers [Integer Number].. 108 4.1.3.8 Requested Handover Attempt Numbers [Integer Number]... 109 4.1.4 Access network level indicators for mobility... 112 4.1.4.1 Intra System Hard Handover Success Ratio [%]...112 4.1.4.2 Inter System Hard Handover Success Ratio [%]...113 4.1.4.3 Inter System Hard Handover Drop Ratio [%]...117 4.2 RNC function level... 121 4.2.1 RNC function level indicators for accessibility...121 4.2.1.1 Packet Session Setup Success Ratio (SSSR) [%]...121 4.2.2 RNC function level indicators for retainability...127 4.2.2.1 Packet Session Success Ratio (SSR) [%]... 127 4.2.3 RNC function level indicators for usage... 134 4.2.3.1 Requested RRC Connection Attempt Numbers [Integer Number]... 134 4.2.3.2 Requested Service Attempt Numbers [Integer Number]... 135 4.2.3.3 Requested Packet Session Attempt Numbers [Integer Number]... 140 4.2.3.4 Requested SRNS Relocation Attempt Numbers [Integer Number].. 143 4.2.3.5 Requested Handover Attempt Numbers [Integer Number]... 146 4.2.3.6 Requested state transition numbers... 150 4.2.3.7 Capacity restrictions... 150 4.2.3.8 Logical Resource Availability [%]... 151 4.2.3.9 User Resource Reservation Numbers [Integer Number]... 152 4.2.3.10 Allocated Capacity [Mbit/s]... 157 4.2.3.11 Soft Handover Overhead [%]... 164
4.3.2.2 Reserved IP bandwidth [%]... 174 4.3.2.3 IP Based RAN logical Interface data volume [Mbit]... 178 4.3.2.4 ATM Based RAN logical Interface data volume [Mbit]...179 4.3.2.5 Average ATM layer throughput per RAN logical interface [Mbit/s]... 181 4.3.2.6 ATM layer traffic load [%]... 183 4.3.2.7 IP layer traffic load...184 4.4 Access point level... 185 4.4.1 Access point level indicators for usage... 185 4.4.1.1 Radio Load [dBm]... 185 4.4.1.2 Logical Resource Availability [%]... 189 4.4.1.3 HW Resources [%]... 191 4.4.1.4 User Resource Reservation Numbers [Integer Number]... 195 4.4.1.5 HSPA Scheduler resource utilization [%]... 197 4.4.1.6 Radio layer (MAC or FP) Data Volumes [Mbit]...198 4.4.1.7 Average Radio Layer (MAC) Throughput [Mbit/s]... 202 4.4.1.8 Active Throughput [Mbit/s]... 203 4.4.2 Access point level indicators for mobility...206 4.4.2.1 Soft Handover Success Rate [%]... 206 4.4.2.2 HSPA Serving Cell Change Success Rate [%]... 208 4.4.3 Access point level indicators for integrity... 210 4.4.3.1 NRT Retransmission Ratio [%]...210 4.4.3.2 Block Error Ratio (BLER) [%]... 213 4.4.3.3 Radio interface transmission utilization [%]...218 4.4.3.4 Radio interface quality...218
Figure 2 General UMTS Architecture... 22
Figure 3 QoS Architecture... 23
Figure 4 Service Access Points offered by the Access Stratum... 24
Figure 5 Iu and Uu User plane...25
Table 7 Packet Service Setup Success Ratio (CSSR)...68 Table 8 Packet Session Setup Success Ratio (SSSR)... 70 Table 9 LCS Setup and Access Complete Ratio...71 Table 10 RRC Connection setup Success Ratio...72 Table 11 RRC Setup and Access Complete Ratio, from Network Perspective.72 Table 12 RRC Setup and Access Complete Ratio... 73 Table 13 Registration Success...74 Table 14 RAB Setup and Access Complete Ratio for Voice... 75 Table 15 RAB Setup and Access Complete Ratio for UDI... 75 Table 16 RAB Setup and Access Complete Ratio for Streaming...76 Table 17 RAB Setup and Access Complete Ratio for NRT Service... 76 Table 18 Multi RAB setup and access Success Ratio...77 Table 19 HS-FACH Setup Success ratio...78 Table 20 Relocation Success in Target RNC for CS... 79 Table 21 Relocation Success in Target RNC for PS... 79 Table 22 Incoming Inter System HHO Success in Target RNC for CS... 80 Table 23 Incoming Inter System Hard Handover Success Rate in Target RNC for PS ...80 Table 24 SRNS Relocation prep Success Rate UE not involved CS... 81 Table 25 SRNS Relocation prep Success Rate UE not involved PS... 82 Table 26 SRNS Relocation UE involved CS Success Rate (HHO)...82 Table 27 SRNS Relocation UE involved PS Success Rate (HHO)... 83 Table 28 Incoming LTE PS ISHO preparation Success Ratio... 83 Table 29 Outgoing LTE PS ISHO Preparation Success Rate... 84 Table 30 Incoming LTE PS ISHO Relocation Complete Success Ratio...84 Table 31 RRC Success Ratio...85 Table 32 RRC connection releases with LTE redirection... 86 Table 33 RAB Success Ratio, Voice (CSR)... 87 Table 34 RAB Success Ratio, Voice (CSR) (re-establishment included)... 88 Table 35 RAB Success Ratio, RT Services Excluding Voice, User perspective... 89 Table 36 RAB Success ratio, UDI (CSR)... 90 Table 37 RAB Success Ratio, Streaming (CSR)...91
Table 41 Multi RAB Success Ratio...96 Table 42 HS-FACH Success Ratio...96 Table 43 Voice, Minutes... 97 Table 44 UDI, Minutes...97 Table 45 NRT RAB duration... 98 Table 46 NRT Sessions duration...99 Table 47 Minutes per Drop Voice... 99 Table 48 Minutes per Drop UDI...100 Table 49 PS RAB minutes per drop... 101 Table 50 PS DCH minutes per drop... 102 Table 51 Iu-PS data volume per drop - ATM based... 103 Table 52 Iu-PS data volume per drop - IP based... 104 Table 53 HSDPA received data per PS RAB drop including PCH... 105 Table 54 HSDPA received data per PS RAB drop excluding PCH... 106 Table 55 Average CS Erlang... 107 Table 56 Incoming Inter RNC HHO Attempts for CS...108 Table 57 Incoming Inter RNC HHO Attempts for PS...109 Table 58 ISHO Attempts RT... 109 Table 59 ISHO Attempts NRT...110 Table 60 Outgoing LTE PS ISHO Preparation Attempts...111 Table 61 Intra System Hard Handover Success Ratio... 112 Table 62 GSM Inter System RT Hard Handover Success Ratio... 113 Table 63 GSM Inter System NRT Hard Handover Success Ratio...115 Table 64 LTE ISHO Success ratio... 116 Table 65 GSM ISHO Drop Rate RT...117 Table 66 GSM ISHO Drop Rate NRT... 118 Table 67 LTE ISHO Drop Rate... 120 Table 68 HSDPA Resource Accessibility for NRT Traffic... 121 Table 69 HSDPA Resource Accessibility for RT Traffic...122 Table 70 HSDPA Setup Success Ratio... 123 Table 71 HSUPA Resource Accessibility for NRT Traffic... 124 Table 72 HSUPA Resource Accessibility for RT Traffic...125 Table 73 HSUPA Setup Success Ratio... 126 Table 74 R99 Setup Success Ratio...126 Table 75 HSDPA Resource Retainability for NRT Traffic... 127 Table 76 HSDPA Resource Retainability for RT Traffic...128 Table 77 HSDPA Success Ratio... 129
Table 85 RAB Attempts UDI...135 Table 86 RAB Attempts Streaming...136 Table 87 RAB Attempts PS Interactive and Background... 137 Table 88 Multi RAB attempts...137 Table 89 Short Message Service Attempts for idle mode UEs...138 Table 90 Intra RNC Inter frequency HO Success Rate RT... 138 Table 91 NAS BHCA... 139 Table 92 Incoming Location Service Attempts... 139 Table 93 Packet Session attempts... 140 Table 94 R99 Packet Session Attempts... 141 Table 95 HSDPA attempts...141 Table 96 HSUPA attempts...142 Table 97 HS-FACH session attempts...142 Table 98 SRNS Relocation UE not involved CS Attempts... 143 Table 99 SRNS Relocation UE not involved PS Attempts... 143 Table 100 Incoming Inter System HHO Attempts (CS)... 144 Table 101 Incoming Inter System Change Attempts (PS)...145 Table 102 Incoming LTE PS ISHO preparation requests... 145 Table 103 Soft HO Update Attempts, RT... 146 Table 104 Soft HO Update Attempts, NRT...146 Table 105 Intra System Hard Handover Attempts...147 Table 106 Intra RNC HHO Attempts for CS... 148 Table 107 HSDPA Serving Cell Change Attempts... 148 Table 108 HSUPA Serving Cell Change Attempts... 149 Table 109 Intra RNC Inter frequency HO Attempts NRT...149 Table 110 Number of state transitions...150 Table 111 Mass event handler duration... 150 Table 112 Iu Availability...151 Table 113 Iur Availability... 151 Table 114 Peak number of HSPA users in RNC ... 152 Table 115 Peak number of HSDPA users in RNC...153 Table 116 Peak number of HSUPA users in RNC...153 Table 117 Peak number of RRC Connected Mode Users in RNC... 154
Table 121 Average Allocated Uplink Dedicated Channel Capacity for CS Voice in Controlling RNC...157 Table 122 Average Allocated Uplink Dedicated Channel Capacity for Data Calls in Controlling RNC...158 Table 123 Average Allocated Downlink Dedicated Channel Capacity for CS Voice in Controlling RNC... 159 Table 124 Average Allocated Downlink Dedicated Channel Capacity for Data Calls in Controlling RNC...161 Table 125 HS-DSCH selections... 162 Table 126 E-DCH selections... 163 Table 127 Soft Handover Overhead in CRNC...164 Table 128 HSUPA MAC-es data volume at RNC... 165 Table 129 HSDPA MAC-d data volume at RNC... 166 Table 130 Iu-PS peak throughput...167 Table 131 Average NRT DCH DL Throughput... 167 Table 132 Average NRT HS-DSCH DL Throughput...168 Table 133 Average MAC-d flow throughput... 169 Table 134 HSUPA MAC-es average throughput at RNC... 169 Table 135 Intra RNC Inter frequency HO Success Rate RT... 170 Table 136 Intra RNC Inter frequency HO Success Rate NRT...171 Table 137 AAL2 connection reservation success rate... 172 Table 138 IP Route Accessibility for outgoing traffic... 172 Table 139 IP Route Accessibility for incoming iub traffic... 173 Table 140 AAL2 path average reserved bandwidth... 174 Table 141 Max Reserved IP based route bandwidth...174 Table 142 IP based Iub Uplink maximum reservation rate at Flexi BTS... 175 Table 143 IP based Iub Uplink maximum reservation rate at Ultrasite BTS ...176 Table 144 IP based Iub Uplink maximum reservation rate at Flexi BTS - VLAN... 176 Table 145 IP based Iub Uplink maximum reservation rate at Ultrasite BTS -VLAN... 177 Table 146 Outgoing IP route traffic volume... 178 Table 147 Incoming IP route traffic volume... 178 Table 148 ATM interface based incoming Data Volume (RNC side)... 179 Table 149 ATM interface based outgoing Data Volume (RNC side)... 180 Table 150 ATM interface based average throughput for outgoing traffic (RNC side)...181 Table 151 ATM interface based average throughput for incoming traffic (RNC side)...182
Table 159 Average HSPA Downlink Load... 189 Table 160 Cell Availability... 189 Table 161 Cell Availability, excluding blocked by user state (BLU)... 190 Table 162 Average ratio of utilized CE for DL in BTS... 191 Table 163 Average ratio of utilized CE for UL in BTS... 191 Table 164 Base Band Usage Ratio Licensing - Uplink CE - Mean...192 Table 165 Base Band Usage Ratio Licensing - Downlink CE - Mean... 192 Table 166 Average ratio of utilized R99 CE for DL in BTS... 193 Table 167 Average ratio of utilized R99 CE for UL in BTS... 193 Table 168 Average HSDPA Processing Sets Utilization ratio...194 Table 169 Average HSUPA Processing Sets Utilization ratio...194 Table 170 Peak number of HSDPA users in WBTS... 195 Table 171 Peak number of HSUPA users in WBTS... 196 Table 172 Average number of active users with MIMO...196 Table 173 Average number of active DC HSDPA users...197 Table 174 E-DCH 2ms TTI utilization... 197 Table 175 HSDPA received data... 198 Table 176 Iub data volume DL in BTS...199 Table 177 Iub data volume UL in BTS...199 Table 178 HSDPA MAC-d data volume at BTS...200 Table 179 HS-FACH data volume downlink... 201 Table 180 HS-FACH data volume uplink...201 Table 181 HSDPA MAC-d average net throughput at BTS... 202 Table 182 Active HS-DSCH end user throughput ... 202 Table 183 Active HS-DSCH cell throughput...203 Table 184 Active HSUPA cell throughput... 204 Table 185 Average HSUPA user throughput... 205 Table 186 Soft Handover Success Ratio...206 Table 187 Soft Handover Success Rate RT...207 Table 188 Soft Handover Success Rate NRT... 208 Table 189 HSDPA Serving Cell Change Success Rate... 208 Table 190 HSUPA Serving Cell Change Success Rate... 209 Table 191 NRT DCH DL Efficiency...210
Table 195 Real Time Radio Bearer (AMR excluded) UL BLER... 213 Table 196 Non Real Time Radio Bearer UL BLER...214 Table 197 HSUPA MAC-e BLER... 215 Table 198 HSUPA HARQ not acknowledged Ratio...216 Table 199 Voice RB DL BLER...216 Table 200 Real Time Radio Bearer (AMR excluded) DL BLER... 217 Table 201 CPC efficiency... 218 Table 202 Average reported CQI... 218
Release-specific information on key performance indicator (KPI) targets has been removed. Only the latest versions of KPI formulas are documented. For more information see WCDMA RAN, Rel. RU30, Changes document. In release RAN04, this document appeared with the DN00279399 code. This code was replaced in RAS05/RAS05.1 with the current DN05191189 because of major changes in the document structure in the NED online view. The document is no longer maintained with the old code. Please note that our issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation.
g
Flexi Direct content is on Flexi Direct RU40 level, and is not valid for RU50. Changes between issues 07D (2014-01-10, RU40) and 08 (2014-03-05, RU50)• New KPIs are listed in the following table:
KPI ID KPI name
RNC_5500a LTE ISHO Success ratio RNC_5501a LTE ISHO Drop Rate RNC_5502a Outgoing LTE PS ISHO Preparation Success Rate RNC_5503a Outgoing LTE PS ISHO Preparation Attempts • Modified KPIs are listed in the following table: KPI ID
Formula updated Description of
modifications RNC_5021b No "Note" field has been updated. RNC_5050b No "Note 1" field has been updated. RNC_300h No "Name", "Abbreviation" and "Description" fields have been updated.
KPI ID
Formula updated Description of
modifications RNC_301f No "Name", "Abbreviation" and "Description" fields have been updated. RNC_302e No "Name", "Abbreviation" and "Description" fields have been updated. RNC_303e No "Name", "Abbreviation" and "Description" fields have been updated. • Removed KPIs are listed in the following table:
KPI ID KPI name
RNC_941b Iu-PS GTP average input traffic rate in RNC RNC_5027a Iu-PS GTP total input traffic in RNC
Changes between issues 07C (2013-11-21,RU40) and 07D (2014-01-10, RU40) Updated the KPI ID versioning description in subchapter Structure of key performance indicators to clarify the relationship between the KPI documentation and NetAct Reporting Suite (for example, for RNC_706, the documentation started with b-version and a-version has not been documented). #unique_3/unique_3_Connect_42_GUID-45D99576-AF73-4397-9FE9-5BAA616C21E7 has been updated. #unique_4/unique_4_Connect_42_OCT1751249111 has been updated. • New KPI is listed in the following table:
KPI ID KPI name Status
RNC_5093b Voice Call Setup Success Ratio (RRC+CU)
New
• Modified KPI is listed in the following table:
KPI ID Formula updated Description of modifications
KPI ID Formula updated Description of modifications
RNC_5486a No “Description” field has been updated and “Note” field has been added.
1 Introduction to WCDMA RAN Key
Performance Indicators
1.1 Overview of WCDMA RAN key performance
indicators
Key performance indicators (KPIs) are a set of selected indicators used for measuring the current network performance and trends. KPIs highlight the key factors of network monitoring and warn in time of potential problems. KPIs are also used for prioritizing the corrective actions. The KPIs described here are the basic network level KPIs for the radio network based on WCDMA access technology (WCDMA RAN). The identification of each defined KPI should represent this technology. However, because of practical and historical reasons the KPI IDs follow the rule used in NSN main reporting tool (NetAct Reporting Suite). Each defined KPI has a unique KPI ID that follows the format RNC_xxxxy, where xxxxy
represents a given unique ID number. For more details, see Structure of Key Performance Indicators.
g
There are also other KPIs in the NetAct Reporting Suite that use the ID format RNC_xxxxy. Only the KPIs that are defined in this document are recognized by the WCDMA RAN release RU40. All KPIs described here are based on performance counters. The main focus is on formulas. However, some typical values for KPIs are given. Some of the key performance indicators (KPI) are not yet available in the official reporting tools. For more information on available KPIs, see Available WCDMA RAN key performance indicators.1.1.1 Structure of key performance indicators
All the items described for each KPI are based on a common template. The template includes the following items:
• KPI name: The official name of the KPI.
• KPI abbreviation: An abbreviation of the KPI name.
• KPI ID: The WCDMA RAN ID of the KPI. The following format is used for the KPI ID:
RNC_xxxy, where xxxy is the unique number and y is the NetAct Reporting Suite version. Only one KPI version at a time is found in the document. From the perspective of this document, what matters is the current version used in the NetAct Reporting Suite. It should be noted that NetAct Reporting Suite versioning always starts with version a. However, this might not always be the case for the document, the documentation for a KPI can also start from a later version (for example, b-version). • Description: The official description of the KPI. • Note (1-n): Note fields related to the generic KPI description.
• KPI class: Each KPI belongs to a KPI class. The main classes are accessibility, retainability, usage, integrity, and mobility. There can also be additional classification related to each main class. For more information, see Classification of key performance indicators. • Unit: The unit of the KPI. The possible values are # (stands for the previously used ‘integer number’), E (stands for the previously used Erlang), minutes, minutes per drop, percentage, dBm, cell/s, kbps, Mbit and Mbps (stands for previously used Mbit/s). • Typical values: The defined typical values in accepted (=live) networks for the KPI. See System Program Report. • Object Summary Levels: Summary levels of the reported objects. These levels are based on the targets for the RAN measurements that provide the counters belonging to the KPI. – There are different targets for Radio and Transport measurements. – Possible radio measurement values from the smallest to the largest are: RB (Radio Bearer), Cell, LCG (Local Cell Group), Cluster of Cells, BTS (Base Station), RNC, Area, City, and Network. – Possible transport measurement values for ATM-based transport from the smallest to the largest are: VCC (Virtual Channel Connection), RNC, and Network. – Possible transport measurement values for IP-based transport from the smallest to the largest are: IP Route, RNC and Network. • Object Summary Level notes: This field describes the potential problems for the given Object Summary Level. • Time Summary Levels: Summary levels on reporting timescale. Based on the collection periods for the RAN measurement(s). The possible values are: Hour, Day, and Week. • Time Summary Level notes: This field states the potential problems for the given Time Summary Level.
1.1.2 Classification of key performance indicators
The KPIs are first grouped into four different levels. They are the following: • Access network • RNC function • Transport Resource Manager • Access point For more information on the KPI levels, see Different KPI levels. Under each level, the KPIs are grouped into the following categories: • Accessibility • Retainability
• Usage • Mobility • Integrity The KPIs are grouped according to these categories in each release. Each KPI description also includes the KPI class. Within a class there can be certain KPIs that include an additional classification.
Usage
There are the following additional classifications for the Usage category: • Resource capacity-based KPIs • Resource availability-based KPIs • HW resource-based KPIs • Resource allocation KPIs • Load-based KPIs • Throughput-based KPIs • Transmission load-based KPIs • Duration-based KPIsMobility
There are no additional classes but for each KPI it should be considered whether the KPI is related to the source and/or target cell.Integrity
There is the following additional class for the Integrity category: • Error rate-based KPIs • Radio Interference based KPIs1.1.3 Network and user key performance indicators
There are some KPIs defined for the same issue but from two different viewpoints, that is, network and user viewpoints.
For such KPIs the differentiation is done in the KPI Name, for example, RRC Setup and Access Complete Ratio, from network perspective.
1.1.4 Summary of different KPI viewpoints
Accessibility Retainability Mobility Integrity Usage Retainability Accessibility
KPIClass NETWORK KPIs
RRCsignalingrelatedtoaUE L3signalingrelatedtoaUE L3SignalingMeasurements [14], [15] RRCSignalingMeasurement RABSuccessor FailureRate RAB/HSDPA Successor FailureRate RBQuality [2] PCrelatedtoaUE HCrelatedtoaUE PS,RMrelatedtoaUE [4],[5],[6] [2], [3], [17] [2],[3],[7],[17],[20] [8], [11], [12][26] [2], [3], [7] availability amounts Measurederrorrates Efficiency Target Cell Call/RAB/HSPA SuccessRate Usage Interface Availability Planned error rates Call/RAB/HSPA SuccessRate RNSChange SuccessRate Source Cell User Allocations RB/AAL2/IP Allocations Cell/lu-PS Traffic RB/lub/ATM/IP Throughput Resourceavailability CellPowerlevels Transportcapacity load Allocations Allocations Throughput WCELL CE Power Capacity User Data Logicalresource HWresource Radio Transport [21][22] [3][10][24] [8][11][16][23][25] [1] [13] [1] [9] HOSuccessor FailureRate The numbers in the center part of the figure stand for the following RAN measurements: [1] Cell Resource [2] Service Level [3] Traffic [4] Intra System HHO [5] Soft HO [6] Inter System HHO [7] LCS
[8] Radio Connection Performance Measurement RLC AM [9] AAL2 Resource Res. [10] AAL2 Path CAC Res. [11] HSDPA in WBTS [12] Radio Connection Performance Measurement OLPC [13] WBTS HW Resource Measurement [14] L3 Signaling at Iu Measurement [15] L3 Signaling at Iur Measurement [16] IU-PS Performance [17] Packet Call Measurement [18] Cell Throughput Measurement [19] DSP Performance in RNC (until RAS06) [20] L3 Relocation Signaling Measurement [21] RNC Capacity Usage Measurement [22] DSP Performance in DSP Service Statistics [23] Frame Protocol in WBTS [24] RNC IP CAC Measurement [25] IP Route Measurement [26] Radio Connection Performance Measurement UEQ The two pyramids in the figure illustrate the two perspectives: the network perspective, and the user perspective, that is, the distinction between network and user KPIs. • In the upper pyramid you can see the RAN functionalities and the related RAN statistical measurements from the user equipment (UE) perspective. • The lower (inverted) pyramid shows the RAN functionalities and the related RAN statistical measurements from the network perspective. The column on the left shows the classification of the KPIs (KPI Class). In the center part (column), you can see the related RAN measurements. The KPIs are based on the counters found in the RAN measurements. The reference mark for a measurement, for example, Cell Resource [1] indicates that a KPI has been defined for that measurement. The KPI with the required information is described in this documentation set. For counter (and detailed measurement) descriptions of measurements 1-8, 12, 14-18, 20-21 and 26, see RNC Counters - RNW Part. For
• Usage – The availability of resources versus the allocation of the available resources. – The load of allocated resources versus the gain (throughput). – The data amounts versus the gain (throughput). • Mobility – Handover in the Source Cell versus the Target Cell • Integrity – Planned error rates versus achieved error rates The right column shows the KPI outcome, that is, the issues that the KPI indicates. • Amount of statistical data related to the defined KPIs and classes: When you go down the pyramid, the amount of data increases. • Importance of each KPI and KPI class: The top of each pyramid represents the most essential data. • Visibility of KPIs in monitoring: The top layers of a pyramid become visible before the lower layers.
1.2 Calls in WCDMA RAN
The 3GPP specifications define the 'call' as follows: 'a logical association between several users (this could be connection oriented or connectionless)'. This definition is not useful when you are measuring the call setup and releases in the (RAN part of the) network and/or user perspective. Therefore, you must further define the overall and UTRAN-related 3GPP definitions to be able to make call-related key performance indicators (KPI).
1.2.1 Definition of call from the WCDMA RAN perspective
The general UMTS architecture defined by 3GPP places RAN (and BSS) in the Access Domain and it functions as a part of the Access Stratum. The NSS and packet core (PaCo) belong to the Core Network Domain (through the underlaying Serving Network Domain) and their functions are part of the Serving Stratum.
Figure 2 General UMTS Architecture Home Network Domain USIM Domain Mobile Equipment Domain Access Network Domain User Equipment Domain Core Network Domain Infrastructure Domain Serving Network Domain Transit Network Domain Cu Uu lu [Zu] [Yu] The Access Domain and Core Network Domain form the Infrastructure Domain. The Mobile Terminal (MT) and USIM form the User Equipment (UE) and the UE Domain. The interface (reference point) between the Access and Serving Network Domain is defined as Iu. The interface (reference point) between the UE and the Infrastructure Domain is defined as Uu (=UMTS Radio Interface). There is a direct interface between the UE and Infrastructure Domain. The 'interface' is handled by sending messages over the Access Stratum, but the messages are treated transparently by RAN. There the messages are on the 'Non-Access Stratum' from the RAN perspective. The Access Stratum is defined as follows: 'The access stratum provides services related to the transmission of data over the radio interface and the management of the radio interface to the other parts of UMTS'. The Serving Stratum (that is transparent to RAN) consists of protocols and functions needed to route and transmit data/information (user or network-generated) from the source to the destination. Because the Access Stratum is under the Serving Stratum, everything that occurs between the source and destination (the UEs and/or Servers) is transparent to RAN. Therefore, in RAN, you are restricted to the visible services and their relationships to calls made in the Service Stratum. The Network Services are found in the generic QoS architecture in the 3GPP specifications about QoS.
NODE End-to-EndService UMTSBearerService External BearerService Radio Access BearerService CNBearer Service RAN Access BearerService Backbone BearerService TE/MT Local BearerService Radio BearerService Physical BearerService PhysicalRadio BearerService The services defined (from top-down) are End-to-End, UMTS Bearer, Radio Access Bearer (RAB), Radio Bearer (RB) and physical bearer services. The services that are visible (and handled) by the RAN are the RAB, RB, and physical bearer services. The RAB provides services in the Iu interface and the RB (and physical bearer) provides services in the Uu interface. The QoS Architecture includes the parameters for the services and the mappings between the services. The defined parameters help to find the relationships of the call to each service (layer). The defined calls (and how they are derived from the QoS parameters) are as follows: • Voice: Traffic Class = Conversational; Source Statistics Descriptor = Voice. Other parameters are not relevant. • UDI: Traffic Class = Conversational; Source Statistics Descriptor = Unknown. Other parameters are not relevant. • Streaming 'call': Traffic Class = Streaming. Other parameters are not relevant.
t
The streaming 'call' can be asked by both core domains. • Packet 'call': Traffic Class = Interactive or Background. Other parameters are not relevant. There can be more than one call, for example, RAB for one user (UE). The 3GPP specifications about Access Stratum define how RAN provides the services.Figure 4 Service Access Points offered by the Access Stratum NAS UE GC Nt DC AS GC Nt DC UE-Uu NAS Edgenode GC Nt DC AS GC Nt DC CN-Iu RAN GC Nt DC IF-Uu RNCFunctions GC Nt DC RAN-Iu UuSvcs: e.g.,RRC IuSvcs: e.g., RANAP InfrastructureSide UserEquipmentSide =SAPs
The services are provided through Service Access Points (SAP). From the service (or call) perspective, the relevant services are (set of operations): • UE Initiated Connection Establishment • Connection Release • IF Side initiated Radio Access Bearer Establishment • IF Side initiated Radio Access Bearer Release This means that in addition to RAB and RB, also other factors are relevant. From the call perspective, the connection to RAN is essential, that is, the user needs an access point to use UTRAN services. The UTRAN Access Point for UEs (to the SAPs), such as UTRAN Cell, is defined in 3GPP specifications about UTRAN. If the UE has access to UTRAN, it has the possibility to use the reference points (interfaces, see 3GPP specifications about UMTS architecture) by using the defined protocols. Likewise, in the SAP division (connection establishment/release and RAB establishment/release) there is an important split in managing the connection (such as Control plane) and in managing the service (such as User plane).
Radio protocols (1) Radio protocols (1) Iu protocols (2) AccessStratum UE UTRAN CN Radio (Uu) Iu Iu protocols (2) Figure 6 Iu and Uu Control plane Non-AccessStratum Radio protocols (1) Radio protocols (1) Iu protocols (2) AccessStratum UE UTRAN CN Radio (Uu) Iu Iu protocols (2) CM,MM, GMM,SM(3) CM,MM, GMM,SM(3) The Control and User plane are handled through protocols that are defined in 3GPP specifications about UTRAN.
User plane protocols
These protocols implement the actual radio access bearer service. For example, they carry user data through the access stratum.
Control plane protocols
These protocols control the radio access bearers and the connection between the UE and the network for different functions (including requesting the service, controlling different transmission resources, controlling handovers and streamlining.) A mechanism for the transparent transfer of NAS messages is also included. The Radio and Iu protocols: • Radio interface and Iu interface protocols are found in 3GPP specifications about UTRAN. • CM, MM, GMM, SM: This is an example of a set of NAS control protocols between the UE and CN. There may be different NAS protocol stacks in parallel.
The connection between the UE and a UTRAN Access Point is the Radio Link (RL), defined in 3GPP specifications about UTRAN. If the UE has access to more than one UTRAN Access points, then it has more than one RLs.
Call definition
The following definition can be given for a call: The time when the RAB uses RB(s) having non-zero bit rate (signalling RBs are not taken into account). This means that either dedicated or shared transport channel is allocated for user plane traffic. From the RAB perspective, this definition means that a RAB and a call can be the same thing but alternatively one RAB can handle more than one call.1.2.2 Call Setup Success rates (CSSR) in NSN-based WCDMA
RAN
The UE has access to RAN services through the UTRAN Access Point, that is, UTRAN Cell. It does this by using the (radio) RRC protocol procedure RRC Connection Establishment. The RRC protocol is part of the Radio Interface Protocol architecture defined by the 3GPP. The RRC protocol procedure RRC Connection Establishment is described in 3GPP specifications about Radio Resource Control. The first part of the Call Setup Success Rate KPI is the success rate of setting up the related RRC Connection for the call. When looking at the relationship between the RRC and the required service for the desired call, some problems can be found. • The setup causes for the RRC do not, in most cases, indicate precisely what kind of service/call is to follow. • The service or call that follows the connection setup is not necessarily set up simultaneously with the RRC. This means the service or call that uses non-real time (NRT) type of transmission. Therefore, some additional definitions and assumptions are needed to be able to define the RRC Setup part of the CSSR KPIs for the following call types: • Voice: Because the RRC Setup Causes 'Mobile Originated Call Conversational' and 'Mobile Terminated Call Conversational' do not specify whether the call attempt is AMR or UDI, we must use these causes in CSSR KPI for both AMR and UDI. • UDI: See Voice. • Streaming ‘Call’: There are unambiguous setup causes for this. • Packet 'Call': The 3GPP has not clearly defined how to start a packet 'call'. For this reason, it is extremely difficult to define on the basis of counters all the times when a packet call setup starts. In practice, almost every given cause in the RRC setup can later result in a packet call setup, if the RRC connection is kept alive. Here, it is considered that only clear indications for the following packet calls can be used. Therefore, 'interactive' and 'background' causes have been selected for the RRC part of Packet Call CSSR formulas. After the RRC Connection (and the RL) are established, the RAN Services (RAB and RB) are still missing from a complete call setup. Some extra definitions are also needed for the call types Streaming ‘Call’ and Packet 'Call'.RANAP signalling, and RANAP is defined in the 3GPP specifications on Radio Interface Protocol architecture). In other words, there is no data to transmit/receive. So, the RB is set up with any traffic carrying capability. Therefore, for Streaming ‘Calls’ and Packet 'Calls' you – in principle - should not follow the service setup in the CSSR KPIs, but the Packet session setup success rates (SSSR) for Streaming and Packet (packet session is defined in 3GPP specifications about radio transmission technologies). When the session is set up, it means that there is data to be received or to be sent. The packet session setup is here considered to be the point when the reservation of a transport channel starts. The available transport channels are defined in the 3GPP specifications about Radio Interface Protocol architecture. This document gives both CSSR KPIs for all call/service types and a common SSSR KPI for all sessions combined. When needed the reporting tools can produce separate SSSR KPIs for each ‘call’ type.
g
In multi-vendor networks, some vendors do not use the Source Descriptor Voice parameter. Other radio access bearer (RAB) parameters, such as bit rate, can be used to distinguish if the conversational class is Voice. The basic structure of the proposed CSSR KPIs per call type is as follows: 1. AMR CSSR: (Successful RRC setups (MOC Conversational + MTC Conversational + Emergency Call) * Successful RAB setups for Conversational with Source Descriptor = Voice) / (All RRC setup attempts (MOC Conversational + MTC Conversational + Emergency Call) * All RAB setup attempts for Conversational with Source Descriptor = Voice)g
In multi-vendor networks, some vendors do not use the Source Descriptor Voice parameter. The other radio access bearer (RAB) parameters, such as bit rate, can be used to distinguish if the conversational class is Voice. 2. UDI CSSR: (Successful RRC setups (MOC Conversational + MTC Conversational) * Successful RAB setups for Conversational with Source Descriptor = Unknown) / (All RRC setup attempts (MOC Conversational + MTC Conversational + Emergency Call) * All RAB setup attempts for Conversational with Source Descriptor = Unknown) 3. Streaming Service CSSR: Streaming Session-based SSSR: (Successful RRC setups (MOC Streaming + MTC Streaming) * Successful Streaming Session setups for Streaming) / (All RRC setup attempts (MOC Streaming + MTC Streaming) * All Streaming Session setup attempts for Streaming) 4. Packet Service CSSR: (Successful RRC setups (MOC Interactive + MTC Interactive + MOC Background + MTC Background) * Successful Packet Session setups for Interactive or Background traffic) / (All RRC setup attempts (MOC Interactive + MTC Interactive + MOC Background + MTC Background) * All Packet Session setup attempts for Interactive or Background traffic)5. Packet Session SSSR: (Successful Packet Session setups for Streaming, Interactive or Background traffic) / (All Packet Session setup attempts for Streaming, Interactive or Background traffic) For full CSSR and SSSR KPI definitions, see Access network level indicators for accessibility. For an overview on WCDMA RAN KPIs, see Overview of WCDMA RAN key performance indicators.
1.2.3 Call Success Rates (CSR) in NSN-based WCDMA RAN
A call is released by the CN with either RANAP:RAB ASSIGNMENT REQUEST or RANAP: IU RELEASE COMMAND (defined in 3GPP specifications about UTRAN Iu interface RANAP signalling). The release can be a normal release or a drop. A call is dropped if one (or more) of the needed parts, such as RAB, RB or RL drops. When we build up CSR KPIs, the following must to be considered: • The Packet Call drop is different than the other call type drops. • The difference between a normal call release and drop is not always clear. First of all, the RAB(s), RB and RL for AMR, UDI and Streaming Call calls are so closely tied together that it can be said that if one of these drops, it is visible as a drop in the other two parts. You can quite safely say that all AMR, UDI or Streaming Call drops can be seen directly by the RAB service drop. Again, for the Packet 'Call', note that the RAB service can still exist even if the RB and/or RL drops. Therefore, you should follow the Packet Session as the key point for Packet 'call' drops similarly to the CSSRs. This document gives both CSR KPIs for all call/service types and a common SSR KPI for all sessions combined. When needed the reporting tools can produce separate SSR KPIs for each ‘call’ type. The basic structure of the proposed CSR KPIs per call type is as follows: 1. AMR CSR: 100 - (Abnormal RAB releases for Conversational with Source Descriptor = Voice / All RAB releases for Conversational with Source Descriptor = Voice) 2. UDI CSR: 100 - (Abnormal RAB releases for Conversational with Source Descriptor = Unknown / All RAB releases for Conversational with Source Descriptor = Unknown) 3. Streaming Call CSR: 100 - (Abnormal RAB releases for Streaming / All RAB releases for Streaming) 4. Packet 'Call' CSR: 100 – (Abnormal Packet Service releases for Interactive or Background traffic / All Packet Service releases for Interactive or Background traffic) 5. Session SSR: 100 – (Abnormal Packet Session releases for Interactive or Background traffic / All Packet Session releases for Interactive or Background traffic)
g
Call Drop Rate (CDR) = 1 - CSR For full CSR KPI definitions, see Access network level indicators for retainability. For an overview on WCDMA RAN KPIs, see Overview of WCDMA RAN key performance indicators.The basic setup and release of a 'call' from the perspective of WCDMA RAN
implemented by NSN was covered in Calls in WCDMA RAN. This helps with defining meaningful 'call'-based setup success and release KPIs.
As pointed out earlier, the 3GPP specifications are rather vague in regard to establishing, maintaining and releasing the related service(s) – the WCDMA RAN-related Bearer services illustrated by the figure QoS architecture - for the ‘calls’.
This means that there are (usually) multiple possibilities for handling resources inside a 'call'.
The main issues related to WCDMA RAN resource reservation for different Bearer services are summarized here. They are followed up with the given KPIs later in the document.
1.3.1 Principles for resource reservation related to services
Generally speaking there are both similarities and differences in the resource reservation between different requested WCDMA RAN services. The similarities are related to the way the needed resources are established, maintained and released. Usually the same external and internal procedures are utilized. The differences are related to the nature of the needed service. RT services constantly need resources (bandwidth) whereas the NRT services do not need resources all the time.
RT Services vs. needed Resources
The RT service resources discussed in the KPIs can be related to establishing,
maintaining and/or releasing the entire RAB or the ‘Packet Session’, that is, HSPA (HS-DSCH or E-DCH) or R99 (DCH) transport channels for the RB.
g
Currently it is not possible to establish ‘Packet Sessions’ for Conversational Traffic Class (‘Speech’ or ‘UDI’) RABs.NRT Services vs. needed Resources
The NRT service resources discussed in the KPIs can be related to establishing, maintaining and/or releasing the entire RAB or the ‘Packet Session’, that is, HSPA (HS-DSCH or E-DCH) or R99 (DCH) transport channels for the RB.
1.3.2 RAB Setup and Access Complete Rates
The KPIs defined in this document cover the needed reservation procedures of Uu (radio) interface, Access Point (for example, power), BTS function (for example, Channel Elements) and RNC function (for example, Iu user plane) resources.
RT RAB Setup and Access Complete Rate KPIs
At RT RAB setup, all resources are reserved for all needed Bearer Services.
NRT RAB Setup and Access Complete Rate KPIs
At NRT RAB setup, the resources needed for the Radio Access Bearer Service, RAN Access Bearer Service, and the Physical Bearer service are reserved.
The Radio Bearer and the Physical Radio Bearer Services are only established. No resources are reserved.
1.3.3 RAB Success Rates
The KPIs defined in this document cover the needed release procedures of Uu (radio) interface, Access Point (for example, power), BTS function (for example, Channel Elements) and RNC function (for example, Iu user plane) resources.
RT RAB Success Rate KPIs
At RT RAB release, all resources are released for all needed Bearer Services.
NRT RAB Success Rate KPIs
At NRT RAB release, all resources are released for all needed Bearer Services.
1.3.4 Packet Session/HSPA Setup Success Rates
At Packet Session setup related to HSPA, all the Bearer Services are already available. The KPIs defined in this document cover the needed reconfiguration procedures of Uu (radio) interface, Access Point (for example, power), BTS function (for example, Channel Elements) and RNC function (for example, HSPA user reservation) resources.
RT HSPA Setup Success Rate KPIs
At RT HSPA-related Packet Session setup, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
NRT HSPA Setup Success Rate KPIs
At NRT HSPA-related Packet Session setup, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
1.3.5 Packet Session/HSPA Success Rates
At Packet Session release related to HSPA, all the Bearer Services will be kept, that is, only reconfigurations related to used HSPA-specific resources are released.
The KPIs defined in this document cover the needed reconfiguration procedures of Uu (radio) interface, Access Point (for example, power), BTS function (for example, Channel Elements) and RNC function (for example, HSPA user release) resources.
NRT HSPA Success Rate KPIs
At NRT HSPA-related Packet Session release, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
1.3.6 Packet Session/R99 Setup Success Rates
At Packet Session setup related to R99, all Bearer Services are already available. The KPIs defined in this document cover the needed reconfiguration procedures of Uu (radio) interface, Access Point (for example, power), BTS function (for example, Channel Elements) and RNC function (for example, R99 user reservation) resources.
RT R99 Setup Success Rate KPIs
At RT R99-related Packet Session setup, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
NRT R99 Setup Success Rate KPIs
At NRT R99-related Packet Session setup, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
1.3.7 Packet Session/R99 Success Rates
At Packet Session release related to R99, all Bearer Services will be kept, that is, only reconfigurations related to the used R99-specific resources are released.
The KPIs defined in this document cover the needed reconfiguration procedures of Uu (radio) interface, Access Point (for example, power), BTS function (for example, Channel Elements) and RNC function (for example, HSPA user release) resources.
RT R99 Success Rate KPIs
At RT R99-related Packet Session release, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
NRT R99 Success Rate KPIs
At NRT R99-related Packet Session release, the resources needed for Radio Bearer and Physical Radio Bearer Services are reconfigured.
1.4 Different KPI levels
The following topics have been discussed in chapters Calls in WCDMA RAN and Resource usage in NSN-based WCDMA RAN:
• the basic setup and release of ‘call’ from the perspective of WCDMA RAN
• the basic principles to understand about WCDMA RAN service-related resource reservation call’ from the perspective of a WCDMA RAN implemented by NSN to define meaningful ‘service’-based setup success and success KPIs. In this chapter a KPI leveling view is created in relation to the UMTS and QoS architectures presented earlier. KPI leveling is needed to quickly see the relevant (most important) network levels for KPI follow-up.
1.4.1 Principles of using defined UMTS architecture
The defined UMTS architecture for Access Network Domain includes external interfaces towards both Mobile Equipment Domain (part of user Equipment Domain) and Serving Network Domain (part of Infrastructure Domain as well as the Access Network Domain). The interface towards Mobile Equipment Domain is called Uu and the interface towards Serving Network Domain is called Iu. Inside the RAN there is an RNC function that has internal interfaces related to capacity reservation towards the external domain interfaces. The transport resources (ATM or IP) are not managed directly by the RNC function. Instead they are managed by the Transport resource manager (TRM). Finally, there is the UTRAN Access point (WCELL) for managing the Radio Link between the UE and UTRAN. The following are the used KPI leveling principles based on UMTS Architecture view: • If both of the external interfaces - Uu and Iu -are related to the defined KPI then it is on the highest level from the UMTS architecture perspective. • If either of the external interfaces - Uu or Iu - are related to the defined KPI then it is on the second level from the UMTS architecture perspective. • When dealing with RNC function-managed internal interfaces towards either one of the external interfaces, the defined KPI is on the third level from the UMTS architecture perspective. • The TRM-related KPIs are found on the fourth level from the UMTS architecture perspective. • Finally, the UTRAN Access Point (WCELL)-related issues are on the fifth level from the UMTS architecture perspective.
1.4.2 Principles of using defined QoS architecture
The needed KPI levels from the UMTS architecture perspective were listed in the previous section.
The QoS architecture only provides additional details to the needed KPI levels.
1.4.3 Access network level KPIs
The defined access network level-KPIs in this document cover the external interfaces of the access network towards either the Uu or Iu interface or both interfaces.
‘Calls’ are visible in the defined bearer architecture but the LCS utilizes the control plane. Thus, it is not visible in the bearer architecture. Furthermore, the KPIs of this level provide additional success rates related to UE network connection, Radio Access Bearer Service(s), incoming Serving Radio Network subsystem change (SRNS) and outgoing Hard Handovers to either another SRNS (Intra-System or Inter-Frequency HHO) or other radio access system (Inter-System HHO). Radio Access Bearer Service(s) are visible in the defined bearer architecture but the other access network level KPIs are not visible in the bearer architecture. The following KPI types are related to this KPI level: • CSSR KPIs • CSR KPIs • SSSR - for all combined sessions - KPIs • SSR - for all combined sessions - KPIs • LCS setup KPIs • RRC Setup and Access Complete Rate KPIs • RRC Success Rate KPIs • RAB Setup and Access Complete Rate KPIs • RAB Success Rate KPIs • Serving Radio Network Subsystem (SRNS) Accessibility KPIs • CS Service duration KPIs – CS Service minutes – CS Service minutes until drop – Average CS Erlang • PS Duration KPIs – NRT RAB duration – NRT Sessions Duration • Hard Handover Success Rate KPIs – ISHO-related found target cell rate in other Access Network – IFHO and ISHO success rates
1.4.4 RNC function level KPIs
The defined KPIs of the RNC function level cover the internal interfaces of the access network towards either Uu or Iu interface.
UMTS architecture view: When the KPIs of this level are used, they follow up actions of interest between either the Mobile Equipment Domain or Service Network Domain from the perspective of the Access Network Domain.
QoS architecture view: When the KPIs of this level are used, they give success rates related to Packet Sessions, availability of internal and external logical interfaces, resource request amounts, resource user numbers, reserved capacity numbers and consumed capacity numbers. Packet Session(s) are visible in the defined bearer architecture but the other KPIs of the RNC function level are not visible in the bearer architecture. The following KPI types are related to this KPI level: • Packet Session Setup Success (SSSR) KPIs • Packet Session Success (SSR) KPIs • Requested RRC Connection attempt number KPIs • Requested Service attempt number KPIs • Requested Packet Session attempt number KPIs • Requested SRNS Relocations • Requested Handover attempt number KPIs • RNC logical resource availability KPIs – Iu interface Availability – Iur interface Availability • RNC user resource number KPIs – HSPA (peak) user numbers – RRC (peak) user numbers • RNC Iu (and Iur) Interface Capacity KPIs – Iu-PS data volume – Iu-PS throughput • RNC BTS interface Capacity KPIs – Allocated R99 Capacity – HSUPA data volume • Soft Handover Capacity KPIs – Soft Handover Overhead • Hard Handover Capacity KPIs – Inter System HHO related UE measurement numbers
1.4.5 Transport Resource Manager level KPIs
The defined KPIs of the Transport Resource Manager level in this document cover the external and internal transport interfaces of the access network. UMTS architecture view: When the KPIs of this level are used, they follow up actions of interest between the Servicing Network Domain and the Access Network Domain or fully inside the Access Network Domain. QoS architecture view: When the KPIs of this level are used, they give availability rates, load levels and data volumes of internal transport services.
• Transport Interface volume KPIs
• Transport Interface throughput KPIs
• Transport Interface load KPIs
1.4.6 Access point-level KPIs
The defined Access point level KPIs in this document cover the external and internal interfaces of access network towards Uu interface. UMTS architecture view: When the KPIs of this level are used, they follow up actions of interest between the Mobile Equipment Domain and the Access Network Domain or fully inside the Access Network Domain. QoS architecture view: When the KPIs of this level are used, they give availability rates and reservation numbers of logical or physical resources and RL-specific issues for data volumes and error rates. The access point level-KPIs are not visible in the bearer architecture. The following KPI types are related to this KPI level: • HW resource KPIs – Channel Element availability – Channel Element utilization • Radio Load KPIs – Access Point noise level – R99 UL and DL load – HSPA DL load – HSPA UL load • Logical resource Availability KPIs – Cell Availability – SF blocking rate • Peak Resource Reservation Numbers • HSPA Scheduler resource utilization KPIs • Soft Handover Success Rate KPIs • Hard Handover Success Rate KPIs – HSPA serving Cell Change Success • Radio layer capacity KPIs – RLC layer throughputs – MAC layer data volumes – MAC layer active data throughput
– FP layer data volumes • Block Error Rate KPIs – Service UL and DL – HSDPA efficiency – HSUPA BLER • Radio interface transmission utilization KPIs
1.5 System Program Report
All KPIs defined in this document are important basic network level KPIs for a WCDMA RAN network. In addition to the KPIs defined in this document there are also various KPIs needed for additional purposes found in different reporting tools. When extensive (daily or weekly) follow-up is needed, the number of KPIs needs to be reduced. For this purpose a System Program report is created on basis of the WCDMA RAN release.
1.5.1 Principles of System Program Report
The System Program report follows the same structures (KPI levels and KPI classes) as used elsewhere in this document. All KPIs of the access network level are part of the report. Only some of the defined KPIs from the other KPI levels are needed for the report. For the KPIs related to the System Program Report, typical measured values are given when available. The value is either based on the measured performance in the live network or the maximum receivable values measured in a laboratory environment.
1.5.2 System Program Report content
The performance targets given in the following table are the average targets for a cell cluster. Performance of an individual cell may differ from the given values.
g
Changes in measurements, calculation formulas, and/or used counters affect the listed key performance indicator (KPI) values.g
The specified targets are not accurate if the load in the network is too low. The load in the network is too low if the average number of calls per cell is lower than (x) during a busy hour.g
The specified targets are not accurate if the load in the network is higher than the planned target load of the network, or if the actual traffic mix differs considerably from the plan. The following table lists the KPIs that are related to System Program Report according to agreed classification.Typical Measured Value
Access network Accessibility RNC_20b RRC Connection setup success ratio
RAN 1.5.2ED
>= RNC_94e Access network Accessibility RNC_94e RRC Setup and
Access Complete Ratio, from Network Perspective
RAN04 > 98.5 %
Access network Accessibility RNC_154d RRC Setup and Access Complete Ratio
RAN04 > 99%
Access network Accessibility RNC_219a Registration Success RAN 1.5.2ED
>= RNC_94e Access network Accessibility RNC_565f Voice Call Setup
Success Ratio (CSSR)
RAN05 > 99.2%
Access network Accessibility RNC_5093b Voice Call Setup Success Ratio (RRC+CU)
RU30 EP1
-Access network Accessibility RNC_30a RAB Setup and Access Complete Ratio for Voice
RAN 1.5.2ED
> 99.6%
Access network Accessibility RNC_566e UDI Call Setup Success Ratio (CSSR)
RAN05 > 99%
Access network Accessibility RNC_31a RAB Setup and Access Complete Ratio for UDI
RAN 1.5.2ED
> 99.5%
Access network Accessibility RNC_575d Streaming Call Setup Success Ratio (CSSR)
RAN05 > 98%
Access network Accessibility RNC_618a RAB Setup and Access Complete Ratio for Streaming
RAN 1.5.2ED
> 99.5%
Access network Accessibility RNC_576e Packet Service Setup Success Ratio (CSSR)
Table 1 WCDMA RAN KPIs related to System Program Report (Cont.)
KPI Level KPI Class KPI ID Indicates Available
since Live Network Typical Measured Value
Access network Accessibility RNC_157a RAB Setup and Access Complete Ratio for NRT Service
RAN 1.5.2ED
> 99.7%
Access network Accessibility RNC_916b Packet Session Setup Success Ratio (SSSR)
RAS06 N/A
Access network Accessibility RNC_741b Multi RAB Setup and Access Success Rate
RAN04 =
RNC_575d Access network Retainability RNC_217f RRC Success Ratio RAN
1.5.2ED
> 99.5%
Access network Retainability RNC_231d RAB Success Ratio, Voice (CSR)
RAN 1.5.2ED
> 99.5%
Access network Retainability RNC_232e RAB Success Ratio, UDI (CSR)
RAN 1.5.2ED
> 99%
Access network Retainability RNC_619b RAB Success Ratio, Streaming (CSR)
RAN 1.5.2ED
> 99%
Access network Retainability RNC_736b RAB Success Ratio, NRT Services
RAN04 > 99%
Access network Retainability RNC_615c RAB Success Ratio, NRT Services, from Network Perspective RAN04 > 95-99 % (depends on inactivity timer settings, usually 98 % is achieved) Access network Retainability RNC_922b Packet Session
Success Ratio (SSR)
RAS06 N/A
Access network Retainability RNC_742b Multi RAB Success Rate
RAN04 =
RNC_619a Access network Retainability RNC_5434a RAB Success Ratio,
Voice (CSR) (re-establishment included)
Typical Measured Value Access network Usage/Requested Capacity RNC_5068a MTC share of requested SMS RU20 N/A Access network Usage/Requested Capacity RNC_5070a Intra RNC Inter frequency HO Attempts NRT RU20 N/A Access network Usage/Requested Capacity RNC_5072a SRNS Relocation UE not involved CS Attempts RU20 N/A Access network Usage/Requested Capacity RNC_5074a SRNS Relocation UE not involved PS Attempts RU20 N/A Access network Usage/Requested Capacity RNC_5078a Incoming Inter System HHO Attempts (CS) RU20 N/A Access network Usage/Requested Capacity RNC_5079a Incoming Inter System Change Attempts (PS) RU20 N/A
Access network Usage/Duration RNC_745a Voice, Minutes RAS05 6)
Access network Usage/Duration RNC_746a UDI, Minutes RAS05 6)
Access network Usage/Duration RNC_737b Minutes per Drop Voice
RAS05 > 300 minutes Access network Usage/Duration RNC_738b Minutes per Drop UDI RAS05 > 300
minutes Access Network Usage/Duration RNC_5058a NRT RAB duration RU20 N/A Access Network Usage/Duration RNC_5059a NRT Sessions
duration
RU20 N/A
Access network Usage/Duration RNC_5082a PS RAB minutes per drop
RU20 N/A
Access network Usage/Duration RNC_5083a PS DCH minutes per drop