50642889 kpi

WCDMA RAN Key PerformanceIndicators

DN05191189Issue 4-3 en draft30/04/2009

# Nokia Siemens Networks 1 (207)

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is not an officialcustomer document and Nokia Siemens Networks does not take responsibility for any errors oromissions in this document. This document is intended for the use of Nokia Siemens Networkscustomers only for the purposes of the agreement under which the document is submitted. Nopart of this documentation may be used, reproduced, modified or transmitted in any form ormeans without the prior written permission of Nokia Siemens Networks. The documentation hasbeen prepared to be used by professional and properly trained personnel, and the customerassumes full responsibility when using it. Nokia Siemens Networks welcomes customercomments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer.

IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, that might arise from the use of this document or the information in it.

THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIREDBY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT,ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THISDOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT TO REVISE THISDOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.

This document and the product it describes are considered protected by copyrights and otherintellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009. All rights reserved.

2 (207) # Nokia Siemens Networks DN05191189Issue 4-3 en draft

30/04/2009

WCDMA RAN Key Performance Indicators

Contents

Contents 3

Summary of changes 7

1 Changes in key performance indicators 13

2 Introduction to WCDMA RAN key performance indicators 212.1 Overview of WCDMA RAN key performance indicators 212.1.1 Structure of key performance indicators 222.1.2 Classification of key performance indicators 232.1.3 Network and user key performance indicators 252.1.4 Summary of different KPI viewpoints 252.2 Calls in WCDMA RAN 292.2.1 Definition of call from the WCDMA RAN perspective 292.2.2 Call Setup Success rates (CSSR) in Nokia Siemens Networks-based

WCDMA RAN 352.2.3 Call Success Rates (CSR) in Nokia Siemens Networks-based WCDMA

RAN 382.3 Resource usage in Nokia Siemens Networks-based WCDMA RAN 392.3.1 Principles for resource reservation related to services 402.3.2 RAB Setup and Access Complete Rates 412.3.3 RAB Success Rates 412.3.4 Packet Session/HSPA Setup Success Rates 412.3.5 Packet Session/HSPA Success Rates 422.3.6 Packet Session/R99 Setup Success Rates 422.3.7 Packet Session/R99 Success Rates 432.4 Different KPI levels 432.4.1 Principles of using defined UMTS architecture 442.4.2 Principles of using defined QoS architecture 452.4.3 Access network level KPIs 452.4.4 RNC function level KPIs 462.4.5 Transport Resource Manager level KPIs 472.4.6 Access point-level KPIs 482.5 System Program Report 492.5.1 Principles of System Program Report 492.5.2 System Program Report content 49

3 Terms and definitions 59

4 Available WCDMA RAN key performance indicators 634.1 KPI ID changes 73

5 Available key performance indicators per formula 795.1 Access network level 795.1.1 Access network level indicators for accessibility 795.1.1.1 Call Setup Success Ratio (CSSR) [%] 795.1.1.2 LCS Setup [%] 865.1.1.3 RRC Setup Complete Ratio [%] 86

DN05191189Issue 4-3 en draft30/04/2009


Contents

5.1.1.4 RRC Setup and Access Complete Ratio [%] 875.1.1.5 RAB Setup and Access Complete Ratio [%] 895.1.1.6 RAB Setup and Access Complete Ratio, Multi-RAB Services [%] 925.1.1.7 Serving Radio Network Subsystem Accessibility Ratio [%] 945.1.2 Access network level indicators for retainability 975.1.2.1 Call Success Ratio (CSR) [%] 975.1.2.2 RRC Success Ratio [%] 975.1.2.3 RAB Success Ratio [%] 985.1.2.4 Packet Session Success Ratio (SSR) [%] 1055.1.2.5 RAB Success Ratio, Multi-RAB Services [%] 1075.1.3 Access network level indicators for usage 1095.1.3.1 CS service duration [minutes] 1095.1.3.2 CS service duration before call drop [minutes] 1105.1.3.3 PS service volume before RAB drop [Mbit/ Dropped RAB] 1125.1.3.4 Erlang [Erlang] 1155.1.4 Access network level indicators for mobility 1155.1.4.1 Intra System Hard Handover Success Ratio [%] 1165.1.4.2 Inter System Hard Handover Success Ratio [%] 1175.1.4.3 Inter System Hard Handover Drop Ratio [%] 1195.2 RNC function level 1225.2.1 RNC function level indicators for accessibility 1225.2.1.1 Packet Session Setup Success Ratio (SSSR) [%] 1225.2.2 RNC function level indicators for retainability 1295.2.2.1 Packet Session Success Ratio (SSR) [%] 1295.2.3 RNC function level indicators for usage 1365.2.3.1 Requested RRC Connection Attempt Numbers [Integer Number] 1365.2.3.2 Requested Service Attempt Numbers [Integer Number] 1375.2.3.3 Requested Packet Session Attempt Numbers [Integer Number] 1425.2.3.4 Requested Handover Attempt Numbers [Integer Number] 1445.2.3.5 Logical Resource Availability [%] 1505.2.3.6 Peak Resource Reservation Numbers [Integer Number] 1525.2.3.7 Allocated Capacity [Mbit/s] 1545.2.3.8 Soft Handover Overhead [%] 1635.2.3.9 Radio layer (MAC or IP) Data Volumes [Mbit] 1645.2.3.10 Average Radio Layer (RLC, MAC or FP) Throughput [Mbit/s] 1665.2.3.11 RAN logical interface data volume [Mbit] 1685.2.3.12 RAN logical interface throughput [Mbit/s] 1695.3 Transport Resource Manager level 1705.3.1 Transport Resource Manager level indicators for accessibility 1705.3.1.1 Transmission Resource Accessibility Ratio [%] 1715.3.2 Transport Resource Manager level indicators for usage 1735.3.2.1 Reserved AAL2 bandwidth [%] 1735.3.2.2 Reserved IP bandwidth [%] 1745.3.2.3 IP Based RAN logical Interface data volume [Mbit] 1745.3.2.4 ATM Based RAN logical Interface data volume [Mbit] 1765.3.2.5 Average ATM layer throughput per RAN logical interface [Mbit/s] 1775.3.2.6 ATM layer traffic load [%] 1795.4 Access point level 1815.4.1 Access point level indicators for usage 1815.4.1.1 Radio Load [dBm] 1815.4.1.2 Logical Resource Availability [%] 1865.4.1.3 HW Resources [%] 187


30/04/2009


5.4.1.4 Radio layer (MAC or FP) Data Volumes [Mbit] 1905.4.1.5 Average Radio Layer (MAC) Throughput [Mbit/s] 1935.4.1.6 Active Throughput [Mbit/s] 1945.4.2 Access point level indicators for mobility 1955.4.2.1 Soft Handover Success Rate [%] 1955.4.2.2 HSPA Serving Cell Change Success Rate [%] 1975.4.3 Access point level indicators for integrity 1995.4.3.1 NRT Retransmission Ratio [%] 1995.4.3.2 Block Error Ratio (BLER) [%] 202

DN05191189Issue 4-3 en draft30/04/2009


Contents


30/04/2009


Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Release-specific information on Key Performance Indicator (KPI) targetshas been removed. Only the latest versions of KPI formulas aredocumented.

In release RAN04, this document appeared with the DN00279399 code.This code was replaced in RAS05/RAS05.1 with the current DN05191189because of major changes in the document structure in the NED onlineview. The document is no longer maintained with the old code.

Changes between issues 4-2 and 4-3

For information on KPI changes see Changes in Key PerformanceIndictors.


For information on KPI changes, see Changes in key performanceindicators.

The information on the KPIs in the section Available Key PerformanceIndicators per formula has been restructured. The KPIs are first arrangedunder four different KPI levels (Access Network, RNC function, TransportResource Manager, Access point) before being grouped into thecategories that were previously used as the top level categories(accessibility, retainability, usage, mobility, integrity). As a result, allchapters under Available key performance indicators per formula are new.The content in the chapters has also been thoroughly updated becausethe structure of the KPI tables has been modified.

There are the following new chapters under Available key performanceindicators per formula:

DN05191189Issue 4-3 en draft30/04/2009


Summary of changes

. Access Network level KPIs. Access network level indicators for accessibility. Access network level indicators for retainability. Access network level indicators for usage. Access network level indicators for mobility

. RNC Function level KPIs. RNC function level indicators for accessibility. RNC function level indicators for retainability. RNC function level indicators for usage

. Transport Resource Manager level KPIs. Transport Resource Manager level indicators for accessibility. Transport Resource Manager level indicators for usage

. Access Point level KPIs. Access point level indicators for usage. Access point level indicators for mobility. Access point level indicators for integrity

As a result of the restructuring of KPI information, the following chaptershave been removed:

. High-level indicators for accessibility

. High-level indicators for retainability

. High-level indicators for usage

. High-level indicators for mobility

. High-level indicators for integrity

Additionally, there are also the following new chapters in the document:

. Resource usage in Nokia Siemens Networks-based WCDMA RAN

. Different KPI levels

. System Program Report

Furthermore, there are the following changes in the document:

Changes in key performance indicators:

Information on the KPI changes has been thoroughly updated.


30/04/2009


Overview of WCDMA RAN key performance indicators:

Information on the structure of key performance indicators and the classesbelonging to the usage category has been updated.

Calls in WCDMA RAN:

The name of the chapter has been changed. The previous name was Callsetup success rates in WCDMA RAN. Section Call Success Rates (CSR)in Nokia Siemens Networks-based WCDMA RAN has been renamed andupdated.

Terms and definitions:

New terms have been added and the definitions for the existing ones havebeen updated.

Available WCDMA RAN key performance indicators:

The name of the chapter has been changed. The previous name wasAvailable WCDMA RAN key performance indicators and given targets.Table Available KPIs in WCDMA RAN has been updated. Section KPI IDchanges has been added.




All KPI IDs have been changed.

All KPI descriptions have been extended to also include a counter namebased formula.

For all KPI descriptions the field “published” has been deleted as useless.

The unit for all throughput and data volume related KPIs have beenchecked and is now consequently either Mbit/s or Mbit.

The KPI change information has been updated to RU10 level.

Overview of WCDMA RAN key performance indicators :

DN05191189Issue 4-3 en draft30/04/2009


Summary of changes

Structure of Key Performance Indicators (=KPI template), Figure KPIviewpoints and the list of measurements have been updated.

Available WCDMA RAN key performance indicators and given targets:

All KPI IDs have been changed.

New KPIs have been added to the table.

The versions of previously existing KPIs have been updated.

High-level indicators for accessibility:

New KPIs have been added and existing ones have been modified. TheKPI versions have been updated for modified KPIs.

High-level indicators for retainability:

One existing KPI have been modified. The KPI version has been updatedfor the modified KPI.

High-level indicators for usage:

New KPIs have been added and existing ones have been modified. TheKPI versions have been updated for modified KPIs.

Sections RAN logical interface data volume [Mbit], RAN logical interfacethroughput [Mbit/s], IP Based RAN logical interface data volume [Mbit],ATM Based RAN logical Interface data volume [Mbit], Average ATM layerthroughput per RAN logical interface [Mbit/s] have been added.

Sections Average ATM layer throughput [kbit/s] and ATM layer DataVolumes [kbit] have been merged to the new sections.

High-level indicators for mobility:

One existing KPI have been modified. The KPI version has been updated.

High-level indicators for integrity:

New KPIs have been added.




30/04/2009



The KPI change information has been updated to RU10 level.

Overview of WCDMA RAN key performance indicators :

Figure KPI viewpoints and the list of measurements have been updated.

Available WCDMA RAN key performance indicators and given targets:

New KPIs have been added to the table.The versions of previouslyexisting KPIs have been updated.

High-level indicators for accessibility:

New KPIs have been added and existing ones have been modified. TheKPI versions have been updated. Section Serving Radio NetworkSubsystem Accessibility Ratio [%] has been added.

High-level indicators for retainability:

New KPIs have been added and existing ones have been modified. TheKPI versions have been updated.

High-level indicators for usage:

New KPIs have been added and existing ones have been modified. TheKPI versions have been updated. Section Iu-PS peak throughput [Mbit/s]has been added.

High-level indicators for mobility:

The KPI versions have been updated.

High-level indicators for integrity:

The KPI versions have been updated.

DN05191189Issue 4-3 en draft30/04/2009


Summary of changes


30/04/2009


1 Changes in key performance indicators

The following changes have been made to WDCMA RAN keyperformance indicators (KPIs) in RU10.

All KPI IDs have been updated:

. RAN_KPI_ID -> RNC_ID

For more information, see KPI ID changes.

All new, updated, and existing KPI formulas have been updated:

. A second formula based on counter (short) names has been added.

. KPI abbreviation has been added to all KPIs.

. The PM measurement related to the KPI has been moved to aseparate field for each KPI. Previously the measurement informationwas included in the KPI description.

At the RU10 E4 phase, a group of KPIs from the System Program Reporthas been added to the WCDMA RAN Key Performance Indicatorsdocument. These KPIs are not new, but they were not included in thecustomer documentation earlier.

Some KPIs have also been dropped from the document. There are thefollowing reasons for dropping KPIs:

. The KPI is not a high-level KPI.

. The KPI has been replaced by another KPI.

. The KPI views have been simplified. This refers to cases where twoKPIs with different views (for example, user and network views) havebeen combined into one.

DN05191189Issue 4-3 en draft30/04/2009


Changes in key performance indicators

Table 1. New KPIs in RU10

KPI See

RNC_960a ATM layer traffic load [%]

RNC_5000a Packet Session Setup Success Ratio (SSSR) [%]

RNC_5002a Packet Session Setup Success Ratio (SSSR) [%]

RNC_5004a Serving Radio Network Subsystem Accessibility Ratio [%]

RNC_5005a Transmission Resource Accessibility Ratio [%]



RNC_5010a Packet Session Success Ratio (SSR) [%]

RNC_5012a Packet Session Success Ratio (SSR) [%]

RNC_5016a Peak Resource Reservation Numbers [Integer number]



RNC_5019a Radio layer (MAC or FP) Data Volumes [Mbit]

RNC_5020a Radio layer (MAC or FP) Data Volumes [Mbit]

RNC_5021a Radio layer (MAC or IP) Data Volumes [Mbit]

RNC_5022a IP based RAN logical interface data volume [Mbit]

RNC_5023a Block Error Ratio (BLER) [%]


RNC_5025a Peak Resource Reservation Numbers [Integer Number]

RNC_5027a RAN logical interface data volume [Mbit]

RNC_5028a Requested Handover Attempt Numbers [Integer Number]

RNC_5029a IP based RAN logical interface data volume [Mbit]


RNC_5031a Transmission Resource Accessibility Ratio [%]

RNC_5032a Average Radio Layer (RLC, MAC or FP) Throughput [Mbit/s]

RNC_5033a Average Radio Layer (RLC, MAC or FP) Throughput [Mbit/s]


RNC_5035a NRT Retransmission Ratio [%]



RNC_5043a Radio layer (MAC or IP) Data Volumes [Mbit]

RNC_5046a Requested Service Attempt Numbers [Integer Number]


30/04/2009


Table 1. New KPIs in RU10 (cont.)

KPI See


RNC_5050a Iu-PS data volume per drop - ATM based

RNC_5051a Iu-PS data volume per drop - IP based

RNC_5052a IP Route Egress Reservation Rate

RNC_7001a HW Resources [%]

RNC_7005a HW Resources [%]

RNC_7063a NRT Retransmission Ratio [%]


Table 2. New KPIs in the document that have already been used in theSystem Program Report

KPI See

RNC_20b RRC Setup Complete Ratio [%]

RNC_219a RRC Setup and Access Complete Ratio [%]

RNC_31a RAB Setup and Access Complete Ratio [%]

RNC_618a RAB Setup and Access Complete Ratio [%]

RNC_741a RAB Setup and Access Complete Ratio, Multi-RAB Services[%]

RNC_232c RAB Success Ratio [%]

RNC_619a RAB Success Ratio [%]

RNC_721c Average Radio Layer (RLC, MAC or FP) Throughput [Mbit/s]

RNC_742a RAB Success Ratio, Multi-RAB Services [%]

RNC_745a CS Service duration [minutes]

RNC_746a CS Service duration [minutes]

RNC_737a CS Service duration before call drop [minutes]

RNC_738a CS Service duration before call drop [minutes]

RNC_302c Inter System Hard Handover Drop Ratio [%]

RNC_303c Inter System Hard Handover Drop Ratio [%]

RNC_218a Requested RRC Connection Attempt Numbers [IntegerNumber]

RNC_214a Requested RRC Connection Attempt Numbers [IntegerNumber]

DN05191189Issue 4-3 en draft30/04/2009



Table 2. New KPIs in the document that have already been used in theSystem Program Report (cont.)

KPI See






RNC_930b Requested Packet Session Attempt Numbers [Integer Number]






RNC_298d Requested Handover Attempt Numbers [Integer Number]

RNC_299c Requested Handover Attempt Numbers [Integer Number]



RNC_614c Allocated Capacity [Mbit/s]

RNC_923b Allocated Capacity [Mbit/s]

RNC_153b Soft Handover Success Rate [%]

RNC_191b Soft Handover Success Rate [%]

Table 3. Updated KPIs in RU10

KPI Description of the update

RNC_916b, RNC_922b The ID and definition have been updated.

The changes are needed because the definition must indicateexplicitly that the KPIs are not only for the NRT cases (sincePacket Sessions can also be RT in RU10).

RNC_941b The unit of the KPI has been changed.

A note has been added because this KPI is valid only forGTPU unit-based RNCs.

RNC_565f The KPI name has been updated.

RNC_918a The object summary level has been updated.


30/04/2009


Table 3. Updated KPIs in RU10 (cont.)

KPI Description of the update

RNC_605a HSDPA user limit-related counters have been added.

A previous note related to previously existed setup failurecounting error removed.

RNC_298d, RNC_300f The formulas have been updated because of a newfunctionality in RU10.

RNC_217e A note has been added.

RNC_576e A new Packet Service indication cause was added to theformula.

RNC_945b, RNC_946b, RNC_950b,RNC_951b

The definitions have been adjusted to better fit the supposedusage.

The unit of the KPIs has been changed.

RNC_732b The definition has been adjusted to better fit the need.

RNC_914c, RNC_915c, RNC_943b,RNC_920b, RNC_921b, RNC_944b

The names and formulas have been updated because RTsessions have been added.

Table 4. Substituted KPIs in RU10

Old KPI New KPI

RNC_954a RNC_5017a

The substitution has been done because the previous KPI wasbased on a measurement that is not available in RU10.

RNC_611b

RNC_613b

RNC_735a

RNC_610a

RNC_734a

RNC_747a

RNC_5032a

RNC_5033a

RNC_5034a

RNC_5035a

RNC_5036a

RNC_5037a

The substitution has been done because of the related PMmeasurement substitution. The counters are still the same.

Table 5. Corrected KPIs in RU10

KPI Description of the correction

RNC_615b

DN05191189Issue 4-3 en draft30/04/2009



Table 5. Corrected KPIs in RU10 (cont.)

KPI Description of the correction

Documentation correction: an already available formulacorrection that has not been documented before.

RNC_605a Formula/Description correction: failed setups notified by theUE have impacts and must be included in the KPI.

Table 6. Deleted KPIs in RU10 (from the document, can still be found in tools)

KPI ID KPI name Reason for the drop

RNC_97a RAB Setup and Access Complete Ratiofor RT Service Excluding Voice [%]

This KPI has been substituted by twoseparate KPIs for UDI and Streaming(RNC_31a and RNC_618a).

RNC_156a RAB Setup and Access Complete Ratiofor NRT Service from the networkperspective

This KPI has been dropped because ofthe decision to only use different KPIsfor user and network perspectives whenabsolutely mandatory.

RNC_171a RAB Setup and Access Complete Ratiofor Multi RAB AMR +NRT Service

This KPI has been substituted by onecommon KPI for all Multi-RAB setup andaccess completions (RNC_741a).

RNC_172a RAB Setup and Access Complete Ratiofor Multi-RAB containing RT + NRTService


RNC_173a RAB Setup and Access Complete Ratiofor Multi-RAB with more than one NRTService


RNC_95d RRC Success Ratio from the networkperspective


RNC_98d RAB Success Ratio, AMR Voice from thenetwork perspective


RNC_160d RAB Success Ratio, RT ServicesExcluding Voice, User perspective

This KPI has been substituted by twoseparate KPIs for UDI and Streaming(RNC_232c and RNC_619a).

RNC_174b RAB Success Ratio, Multi-RAB AMR+NRT Service from the networkperspective

This KPI has been substituted by onecommon KPI for all Multi-RAB success(RNC_742a).

RNC_175b RAB Success Ratio, Multi-RAB AMR+NRT Service from the networkperspective



30/04/2009


Table 6. Deleted KPIs in RU10 (from the document, can still be found in tools)(cont.)


RNC_176b RAB Success Ratio, Multi-RABcontaining RT +NRT Service from thenetwork perspective


RNC_169d Inter System Hard Handover SuccessRatio

This KPI has been deleted because themain need is to follow ISHO RT andNRT separately with RNC_300d andRNC_301d.

RNC_79b Soft Handover Overhead in SRNC This KPI has been deleted because themain need is to follow SHO Overhead inCRNC with RNC_192b.

RNC_16c Average RACH Throughput This KPI has been deleted because it isnot a high-level KPI.

RNC_17c Average FACH Throughput This KPI has been deleted because it isnot a high-level KPI.

RNC_18c Average FACH Throughput This KPI has been deleted because it isnot a high-level KPI.

RNC_170c Average SAB Throughput This KPI has been deleted because it isnot a high-level KPI.

RNC_949b Spreading Code Blocking rate in DL This KPI has been deleted because it isnot a high-level KPI.

RNC_947a Average ratio of utilized CE for DL forHSUPA in BTS

This KPI has been deleted because it isnot a high-level KPI.

RNC_948a Average ratio of utilized CE for UL forHSUPA in BTS

This KPI has been deleted because it isnot a high-level KPI.

RNC_612a NRT HS-DSCH DL RLC Efficiency This KPI has been deleted because it isnot a high-level KPI.

Table 7. KPIs deleted entirely in RU10


RNC_603b Average available Iub capacity forHSDPA

The KPI has been deleted becauserelated counter changes has made it notusable

DN05191189Issue 4-3 en draft30/04/2009




30/04/2009


2 Introduction to WCDMA RAN keyperformance indicators

2.1 Overview of WCDMA RAN key performanceindicators

Key performance indicators (KPIs) are a set of selected indicators used formeasuring the current network performance and trends. KPIs highlight thekey 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 radionetwork based on WCDMA access technology (WCDMA RAN). Theidentification of each defined KPI should represent this technology.However, because of practical and historical reasons the KPI IDs followthe rule used in Nokia Siemens Networks main reporting tool (NetActReporting Suite). Each defined KPI has a unique KPI ID that follows theformat RNC_xxxxy, where xxxxy represents a given unique ID number. Formore details, see Structure of Key Performance Indicators.

Note

There are also other KPIs in the NetAct Reporting Suite that use the IDformat RNC_xxxxy. Only the KPIs that are defined in this document arerecognized by the WCDMA RAN release RU10.

All KPIs described here are based on performance counters. The mainfocus is on formulas. However, some target values for KPIs are given.

Some of the key performance indicators (KPI) are not yet available in theofficial reporting tools..

DN05191189Issue 4-3 en draft30/04/2009


Introduction to WCDMA RAN key performance indicators

For more information on available KPIs, see Available WCDMA RAN keyperformance indicators.

2.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 isused for the KPI ID: RNC_xxxy, where xxxy is the unique numberand y is the NetAct Reporting Suite version.

. KPI version: The version of the KPI.

Version information also includes the maturity mark, that is, the umark. The version can be, for example, 1.0p, where p stands forpreliminary. The u marks are defined as follows:. p for preliminary. KPI is preliminary, that is, the formula is

considered to be working but has not yet been accepted forimplementation and is not found in any reporting tool.

. a for accepted, meaning that the KPI is accepted but not foundin any reporting tool.

. f for frozen, meaning that the KPI is accepted and found inreporting tools but not verified.

. u for published, meaning that it is found in a reporting tool andverified in RAN.

In Phase 1, Phase 2, and Trial documentation the WCDMA RANKPIs introduced in previous releases are automatically frozen KPIs.

In product releases, the KPIs are published and are visible in NOLSRISE.

The RNC_xxxxy versions rise by one when used in the next release(for example, 1.0 -> 2.0). Furthermore, corrections inside a releaseraise the version number by one (for example, 1.0 -> 1.1).

. Description: The official description of the KPI.

. Note (1-n): Note fields related to the generic KPI description.

. Measurement: The description includes a reference to themeasurement in question, for example, M1001: Service Level.

. KPI summarization formula: The formula given in counter numbers.

. KPI formula with short names: The formula given in short names.


30/04/2009


. KPI class: Each KPI belongs to a KPI class. The main classes areaccessibility, retainability, usage, integrity, and mobility. There canalso be additional classification related to each main class. For moreinformation, see Classification of key performance indicators.

. Unit: The unit of the KPI. The possible values are # (stands for thepreviously used ‘integer number’), E (stands for the previously usedErlang), minutes, minutes per drop, percentage, dBm, cell/s, kbps,Mbit and Mbps (stands for previously used Mbit/s).

. Target values: The defined target 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 measurementsthat 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, andNetwork.

. Possible transport measurement values for ATM-basedtransport from the smallest to the largest are: VCC (VirtualChannel Connection), RNC, and Network.

. Possible transport measurement values for IP-based transportfrom the smallest to the largest are: IP Route, RNC andNetwork.

. Object Summary Level notes: This field describes the potentialproblems for the given Object Summary Level.

. Time Summary Levels: Summary levels on reporting timescale.Based on the collection periods for the RAN measurement(s). Thepossible values are: Hour, Day, and Week.

. Time Summary Level notes: This field states the potential problemsfor the given Time Summary Level.

2.1.2 Classification of key performance indicators

The KPIs are first grouped into four different levels. They are the following:

. Access network

. RNC function

DN05191189Issue 4-3 en draft30/04/2009



. 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. EachKPI description also includes the KPI class.

Within a class there can be certain KPIs that include an additionalclassification.

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 KPIs

Mobility

There are no additional classes but for each KPI it should be consideredwhether the KPI is related to the source and/or target cell.


30/04/2009


Integrity

There is the following additional class for the Integrity category:

. Error rate-based KPIs

2.1.3 Network and user key performance indicators

There are some KPIs defined for the same issue but from two differentviewpoints, 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.

2.1.4 Summary of different KPI viewpoints

The following figure illustrates the different KPI viewpoints.

DN05191189Issue 4-3 en draft30/04/2009



Figure 1. KPI viewpoints

USER KPIsKPIClass

Accessibility

Retainability

Mobility

Integrity

Usage

Retainability

Accessibility

KPI Class NETWORK KPIs

RRC signaling related to a UE

L3 signaling related to a UE

L3 Signaling Measurements[14], [15]

RRC Signaling Measurement

KPIOutcome

RAB Success orFailure Rate

RAB/HSDPASuccess orFailure Rate

RB Quality

[2]

PC related to a UE

HC related to a UE

PS, RM related to a UE

[4], [5], [6]

[2], [3], [17]

[2], [3], [7], [17], [20]

[8], [11], [12] [26]

[2], [3], [7]

availability

amounts

Measured error ratesEfficiency

TargetCell

Call /RAB/HSPASuccess Rate

UsageInterfaceAvailability

Plannederrorrates

Call /RAB/HSPASuccess RateRNS ChangeSuccess Rate

SourceCell

User Allocations

RB/AAL2/IP Allocations

Cell/lu-PS Traffic

RB/lub/ATM/IP Throughput

Resource availability

Cell Power levels

Transport capacityload

Allocations

Allocations

Throughput

WCELL

CE

Power

Capacity

User

Data

Logical resource

HW resource

Radio

Transport

[21] [22]

[3] [10] [24]

[8] [11] [16] [23] [25]

[1]

[13]

[1]

[9]

HO Success orFailure Rate


30/04/2009


The numbers in the center part of the figure stand for the following RANmeasurements:

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

[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 networkperspective, and the user perspective, that is, the distinction betweennetwork and user KPIs.

. In the upper pyramid you can see the RAN functionalities and therelated RAN statistical measurements from the user equipment (UE)perspective.

. The lower (inverted) pyramid shows the RAN functionalities and therelated RAN statistical measurements from the network perspective.

DN05191189Issue 4-3 en draft30/04/2009



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. Thereference mark for a measurement, for example, Cell Resource [1]indicates that a KPI has been defined for that measurement. The KPI withthe required information is described in this documentation set. Forcounter (and detailed measurement) descriptions of measurements 1-8,12, 14-18, 20-21 and 26, see RNC Counters - RNW Part. For informationon measurements 9-10, 19, 22 and 24-25, see RNC Counters - Transportand HW Part. For information on measurement numbers 11, 13 and 23,see WBTS Counters.

In the center part, you can also see the contradictions inside the KPIclasses (the different angles in a pyramid layer):

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

. 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 pyramidrepresents the most essential data.

. Visibility of KPIs in monitoring: The top layers of a pyramid becomevisible before the lower layers.


30/04/2009


2.2 Calls in WCDMA RAN

The 3GPP specifications define the 'call' as follows: 'a logical associationbetween several users (this could be connection oriented orconnectionless)'. This definition is not useful when you are measuring thecall setup and releases in the (RAN part of the) network and/or userperspective. Therefore, you must further define the overall and UTRAN-related 3GPP definitions to be able to make call-related key performanceindicators (KPI).

2.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. TheNSS and packet core (PaCo) belong to the Core Network Domain (throughthe underlaying Serving Network Domain) and their functions are part ofthe Serving Stratum.

Figure 2. General UMTS Architecture

The Access Domain and Core Network Domain form the InfrastructureDomain. The Mobile Terminal (MT) and USIM form the User Equipment(UE) and the UE Domain.

HomeNetworkDomain

USIMDomain

MobileEquipmentDomain

AccessNetworkDomain

UserEquipment Domain

CoreNetworkDomain

InfrastructureDomain

ServingNetworkDomain

TransitNetworkDomain

Cu Uu lu

[Zu]

[Yu]

DN05191189Issue 4-3 en draft30/04/2009



The interface (reference point) between the Access and Serving NetworkDomain is defined as Iu. The interface (reference point) between the UEand 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, butthe messages are treated transparently by RAN. There the messages areon the 'Non-Access Stratum' from the RAN perspective.

The Access Stratum is defined as follows: 'The access stratum providesservices related to the transmission of data over the radio interface and themanagement of the radio interface to the other parts of UMTS'.

The Serving Stratum (that is transparent to RAN) consists of protocols andfunctions 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 thatoccurs between the source and destination (the UEs and/or Servers) istransparent to RAN. Therefore, in RAN, you are restricted to the visibleservices and their relationships to calls made in the Service Stratum.

The Network Services are found in the generic QoS architecture in the3GPP specifications about QoS.


30/04/2009


Figure 3. QoS Architecture

The services defined (from top-down) are End-to-End, UMTS Bearer,Radio Access Bearer (RAB), Radio Bearer (RB) and physical bearerservices. The services that are visible (and handled) by the RAN are theRAB, RB, and physical bearer services. The RAB provides services in theIu interface and the RB (and physical bearer) provides services in the Uuinterface. The QoS Architecture includes the parameters for the servicesand the mappings between the services. The defined parameters help tofind 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.

CNGateway

CNEDGENODE

End-to-End Service

UMTS Bearer ServiceExternal

Bearer Service

Radio AccessBearer Service

CN BearerService

RAN AccessBearer Service

BackboneBearer Service

TE/MT LocalBearer Service

RadioBearer Service

PhysicalBearer Service

Physical RadioBearer Service

TE MT RAN TE

UMTS

DN05191189Issue 4-3 en draft30/04/2009



. Streaming 'call': Traffic Class = Streaming. Other parameters are notrelevant.

Tip

The streaming 'call' can be asked by both core domains.

. Packet 'call': Traffic Class = Interactive or Background. Otherparameters 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 providesthe services.

Figure 4. Service Access Points offered by the Access Stratum

NAS

UE

GC Nt DC

AS

GC Nt DC

UE-Uu

NAS

Edge node

GC Nt DC

AS

GC Nt DC

CN-Iu

RAN

GC Nt DC

IF-Uu

RNC Functions

GC Nt DC

RAN-IuUu Svcs:e.g., RRC

Iu Svcs:e.g.,RANAP

Infrastructure SideUser Equipment Side

= SAPs


30/04/2009


The services are provided through Service Access Points (SAP). From theservice (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, theuser needs an access point to use UTRAN services.

The UTRAN Access Point for UEs (to the SAPs), such as UTRAN Cell, isdefined in 3GPP specifications about UTRAN. If the UE has access toUTRAN, it has the possibility to use the reference points (interfaces, see3GPP specifications about UMTS architecture) by using the definedprotocols. Likewise, in the SAP division (connection establishment/releaseand RAB establishment/release) there is an important split in managingthe connection (such as Control plane) and in managing the service (suchas User plane).

Figure 5. Iu and Uu User plane

Non-Access Stratum

Radioprotocols

(1)

Radioprotocols

(1)

Iuprotocols

(2)

Access Stratum

UE UTRAN CNRadio(Uu)

Iu

Iuprotocols

(2)

DN05191189Issue 4-3 en draft30/04/2009



Figure 6. Iu and Uu Control plane

The Control and User plane are handled through protocols that are definedin 3GPP specifications about UTRAN.

User plane protocolsThese protocols implement the actual radio accessbearer service. For example, they carry user datathrough the access stratum.

Control plane protocolsThese protocols control the radio access bearers andthe connection between the UE and the network fordifferent functions (including requesting the service,controlling different transmission resources,controlling handovers and streamlining.) Amechanism for the transparent transfer of NASmessages is also included.

The Radio and Iu protocols:

. Radio interface and Iu interface protocols are found in 3GPPspecifications about UTRAN.

. CM, MM, GMM, SM: This is an example of a set of NAS controlprotocols between the UE and CN. There may be different NASprotocol stacks in parallel.

Non-Access Stratum

Radioprotocols

(1)

Radioprotocols

(1)

Iuprotocols

(2)

Access Stratum

UE UTRAN CNRadio(Uu)

Iu

Iuprotocols

(2)

CM, MM,GMM, SM (3)

CM, MM,GMM, SM (3)


30/04/2009


The connection between the UE and a UTRAN Access Point is the RadioLink (RL), defined in 3GPP specifications about UTRAN. If the UE hasaccess to more than one UTRAN Access points, then it has more than oneRLs.

Call definition

The following definition can be given for a call: The time when the RABuses RB(s) having non-zero bit rate (signalling RBs are not taken intoaccount). This means that either dedicated or shared transport channel isallocated for user plane traffic.

From the RAB perspective, this definition means that a RAB and a call canbe the same thing but alternatively one RAB can handle more than onecall.

2.2.2 Call Setup Success rates (CSSR) in Nokia Siemens Networks-basedWCDMA 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 protocolprocedure RRC Connection Establishment. The RRC protocol is part ofthe Radio Interface Protocol architecture defined by the 3GPP. The RRCprotocol procedure RRC Connection Establishment is described in 3GPPspecifications about Radio Resource Control.

The first part of the Call Setup Success Rate KPI is the success rate ofsetting up the related RRC Connection for the call. When looking at therelationship 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, indicateprecisely what kind of service/call is to follow.

. The service or call that follows the connection setup is notnecessarily set up simultaneously with the RRC. This means theservice or call that uses non-real time (NRT) type of transmission.

Therefore, some additional definitions and assumptions are needed to beable to define the RRC Setup part of the CSSR KPIs for the following calltypes:

DN05191189Issue 4-3 en draft30/04/2009



. Voice: Because the RRC Setup Causes 'Mobile Originated CallConversational' and 'Mobile Terminated Call Conversational' do notspecify whether the call attempt is AMR or UDI, we must use thesecauses 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 ofcounters all the times when a packet call setup starts. In practice,almost every given cause in the RRC setup can later result in apacket call setup, if the RRC connection is kept alive. Here, it isconsidered that only clear indications for the following packet callscan be used. Therefore, 'interactive' and 'background' causes havebeen 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 extradefinitions are also needed for the call types Streaming ‘Call’ and Packet'Call'.

The reason for this is that even if the RAB Services and the RB Servicesare initiated through the defined Access Stratum SAP (defined in 3GPPUTRAN specifications about UTRAN) with RANAP: RAB ASSIGNMENTREQUESTor RANAP: RELOCATION REQUEST procedure, it is possiblethat the RB Service is not needed at this phase. (The used Iu procedure isdefined in the 3GPP specifications on the UTRAN Iu interface RANAPsignalling, and RANAP is defined in the 3GPP specifications on RadioInterface Protocol architecture).

In other words, there is no data to transmit/receive. So, the RB is set upwith 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 Packetsession setup success rates (SSSR) for Streaming and Packet (packetsession is defined in 3GPP specifications about radio transmissiontechnologies). When the session is set up, it means that there is data to bereceived or to be sent. The packet session setup is here considered to bethe point when the reservation of a transport channel starts. The availabletransport channels are defined in the 3GPP specifications about RadioInterface Protocol architecture.

This document gives both CSSR KPIs for all call/service types and acommon SSSR KPI for all sessions combined. When needed the reportingtools can produce separate SSSR KPIs for each ‘call’ type.


30/04/2009


Note

In multi-vendor networks, some vendors do not use the SourceDescriptor Voice parameter. Other radio access bearer (RAB)parameters, such as bit rate, can be used to distinguish if theconversational 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 + MTCConversational + Emergency Call) * Successful RAB setups forConversational with Source Descriptor = Voice) / (All RRC setupattempts (MOC Conversational + MTC Conversational + EmergencyCall) * All RAB setup attempts for Conversational with SourceDescriptor = Voice)

Note

In multi-vendor networks, some vendors do not use the SourceDescriptor Voice parameter. The other radio access bearer (RAB)parameters, such as bit rate, can be used to distinguish if theconversational class is Voice.

2. UDI CSSR: (Successful RRC setups (MOC Conversational + MTCConversational) * Successful RAB setups for Conversational withSource Descriptor = Unknown) / (All RRC setup attempts (MOCConversational + MTC Conversational + Emergency Call) * All RABsetup 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 RRCsetup attempts (MOC Streaming + MTC Streaming) * All StreamingSession setup attempts for Streaming)

DN05191189Issue 4-3 en draft30/04/2009



4. Packet Service CSSR: (Successful RRC setups (MOC Interactive +MTC Interactive + MOC Background + MTC Background) *Successful Packet Session setups for Interactive or Backgroundtraffic) / (All RRC setup attempts (MOC Interactive + MTC Interactive+ MOC Background + MTC Background) * All Packet Session setupattempts for Interactive or Background traffic)

5. Packet Session SSSR: (Successful Packet Session setups forStreaming, Interactive or Background traffic) / (All Packet Sessionsetup attempts for Streaming, Interactive or Background traffic)

For full CSSR and SSSR KPI definitions, see Access network levelindicators for accessibility.

For an overview on WCDMA RAN KPIs, see Overview of WCDMA RANkey performance indicators.

2.2.3 Call Success Rates (CSR) in Nokia Siemens Networks-basedWCDMA RAN

A call is released by the CN with either RANAP:RAB ASSIGNMENTREQUEST or RANAP: IU RELEASE COMMAND (defined in 3GPPspecifications about UTRAN Iu interface RANAP signalling). The releasecan be a normal release or a drop.

A call is dropped if one (or more) of the needed parts, such as RAB, RB orRL drops. When we build up CSR KPIs, the following must to beconsidered:

. The Packet Call drop is different than the other call type drops.

. The difference between a normal call release and drop is not alwaysclear.

First of all, the RAB(s), RB and RL for AMR, UDI and Streaming Call callsare so closely tied together that it can be said that if one of these drops, itis visible as a drop in the other two parts. You can quite safely say that allAMR, UDI or Streaming Call drops can be seen directly by the RABservice drop.

Again, for the Packet 'Call', note that the RAB service can still exist even ifthe RB and/or RL drops. Therefore, you should follow the Packet Sessionas the key point for Packet 'call' drops similarly to the CSSRs.

This document gives both CSR KPIs for all call/service types and acommon SSR KPI for all sessions combined. When needed the reportingtools can produce separate SSR KPIs for each ‘call’ type.


30/04/2009


The basic structure of the proposed CSR KPIs per call type is as follows:

1. AMR CSR: 100 - (Abnormal RAB releases for Conversational withSource Descriptor = Voice / All RAB releases for Conversational withSource Descriptor = Voice)

2. UDI CSR: 100 - (Abnormal RAB releases for Conversational withSource Descriptor = Unknown / All RAB releases for Conversationalwith 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 forInteractive or Background traffic / All Packet Service releases forInteractive or Background traffic)

5. Session SSR: 100 – (Abnormal Packet Session releases forInteractive or Background traffic / All Packet Session releases forInteractive or Background traffic)

Note

Call Drop Rate (CDR) = 1 - CSR

For full CSR KPI definitions, see Access network level indicators forretainability.


For target values for WCDMA RAN KPIs, see Available WCDMA RAN keyperformance indicators.

2.3 Resource usage in Nokia Siemens Networks-basedWCDMA RAN

The basic setup and release of a 'call' from the perspective of WCDMARAN implemented by Nokia Siemens Networks was covered in Calls inWCDMA RAN. This helps with defining meaningful 'call'-based setupsuccess and release KPIs.

DN05191189Issue 4-3 en draft30/04/2009



As pointed out earlier, the 3GPP specifications are rather vague in regardto establishing, maintaining and releasing the related service(s) – theWCDMA RAN-related Bearer services illustrated by Figure QoSarchitecture - for the ‘calls’.

This means that there are (usually) multiple possibilities for handlingresources inside a 'call'.

The main issues related to WCDMA RAN resource reservation for differentBearer services are summarized here. They are followed up with the givenKPIs later in the document.

2.3.1 Principles for resource reservation related to services

Generally speaking there are both similarities and differences in theresource reservation between different requested WCDMA RAN services.

The similarities are related to the way the needed resources areestablished, maintained and released. Usually the same external andinternal procedures are utilized.

The differences are related to the nature of the needed service. RTservices constantly need resources (bandwidth) whereas the NRTservices do not need resources all the time.

RT Services vs. needed Resources

The RT service resources discussed in the KPIs can be related toestablishing, maintaining and/or releasing the entire RAB or the ‘PacketSession’, that is, HSPA (HS-DSCH or E-DCH) or R99 (DCH) transportchannels for the RB.

Note

Currently it is not possible to establish ‘Packet Sessions’ forConversational Traffic Class (‘Speech’ or ‘UDI’) RABs.

NRT Services vs. needed Resources

The NRT service resources discussed in the KPIs can be related toestablishing, maintaining and/or releasing the entire RAB or the ‘PacketSession’, that is, HSPA (HS-DSCH or E-DCH) or R99 (DCH) transportchannels for the RB.


30/04/2009


2.3.2 RAB Setup and Access Complete Rates

The KPIs defined in this document cover the needed reservationprocedures of Uu (radio) interface, Access Point (for example, power),BTS function (for example, Channel Elements) and RNC function (forexample, Iu user plane) resources.

RT RAB Setup and Access Complete Rate KPIs

At RT RAB setup, all resources are reserved for all needed BearerServices.

NRT RAB Setup and Access Complete Rate KPIs

At NRT RAB setup, the resources needed for the Radio Access BearerService, RAN Access Bearer Service, and the Physical Bearer service arereserved.

The Radio Bearer and the Physical Radio Bearer Services are onlyestablished. No resources are reserved.

2.3.3 RAB Success Rates

The KPIs defined in this document cover the needed release proceduresof Uu (radio) interface, Access Point (for example, power), BTS function(for example, Channel Elements) and RNC function (for example, Iu userplane) resources.

RT RAB Success Rate KPIs

At RT RAB release, all resources are released for all needed BearerServices.

NRT RAB Success Rate KPIs

At NRT RAB release, all resources are released for all needed BearerServices.

2.3.4 Packet Session/HSPA Setup Success Rates

At Packet Session setup related to HSPA, all the Bearer Services arealready available.

DN05191189Issue 4-3 en draft30/04/2009



The KPIs defined in this document cover the needed reconfigurationprocedures of Uu (radio) interface, Access Point (for example, power),BTS function (for example, Channel Elements) and RNC function (forexample, HSPA user reservation) resources.

RT HSPA Setup Success Rate KPIs

At RT HSPA-related Packet Session setup, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

NRT HSPA Setup Success Rate KPIs

At NRT HSPA-related Packet Session setup, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

2.3.5 Packet Session/HSPA Success Rates

At Packet Session release related to HSPA, all the Bearer Services will bekept, that is, only reconfigurations related to used HSPA-specificresources are released.

The KPIs defined in this document cover the needed reconfigurationprocedures of Uu (radio) interface, Access Point (for example, power),BTS function (for example, Channel Elements) and RNC function (forexample, HSPA user release) resources.

RT HSPA Success Rate KPIs

At RT HSPA-related Packet Session release, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

NRT HSPA Success Rate KPIs

At NRT HSPA-related Packet Session release, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

2.3.6 Packet Session/R99 Setup Success Rates

At Packet Session setup related to R99, all Bearer Services are alreadyavailable.

The KPIs defined in this document cover the needed reconfigurationprocedures of Uu (radio) interface, Access Point (for example, power),BTS function (for example, Channel Elements) and RNC function (forexample, R99 user reservation) resources.


30/04/2009


RT R99 Setup Success Rate KPIs

At RT R99-related Packet Session setup, the resources needed for RadioBearer and Physical Radio Bearer Services are reconfigured.

NRT R99 Setup Success Rate KPIs

At NRT R99-related Packet Session setup, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

2.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 resourcesare released.

The KPIs defined in this document cover the needed reconfigurationprocedures of Uu (radio) interface, Access Point (for example, power),BTS function (for example, Channel Elements) and RNC function (forexample, HSPA user release) resources.

RT R99 Success Rate KPIs

At RT R99-related Packet Session release, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

NRT R99 Success Rate KPIs

At NRT R99-related Packet Session release, the resources needed forRadio Bearer and Physical Radio Bearer Services are reconfigured.

2.4 Different KPI levels

The following topics have been discussed in chapters Calls in WCDMARAN and Resource usage in Nokia Siemens Networks-based WCDMARAN:

. the basic setup and release of ‘call’ from the perspective of WCDMARAN implemented by Nokia Siemens Networks to be able to definemeaningful ‘call’-based setup success and success KPIs.

. the basic principles to understand about WCDMA RAN service-related resource reservation call’ from the perspective of a WCDMARAN implemented by Nokia Siemens Networks to define meaningful‘service’-based setup success and success KPIs.

DN05191189Issue 4-3 en draft30/04/2009



In this chapter a KPI leveling view is created in relation to the UMTS andQoS architectures presented earlier.

KPI leveling is needed to quickly see the relevant (most important) networklevels for KPI follow-up.

2.4.1 Principles of using defined UMTS architecture

The defined UMTS architecture for Access Network Domain includesexternal interfaces towards both Mobile Equipment Domain (part of userEquipment Domain) and Serving Network Domain (part of InfrastructureDomain as well as the Access Network Domain).

The interface towards Mobile Equipment Domain is called Uu and theinterface towards Serving Network Domain is called Iu.

Inside the RAN there is an RNC function that has internal interfacesrelated to capacity reservation towards the external domain interfaces.

The transport resources (ATM or IP) are not managed directly by the RNCfunction. Instead they are managed by the Transport resource manager(TRM).

Finally, there is the UTRAN Access point (WCELL) for managing the RadioLink between the UE and UTRAN.

The following are the used KPI leveling principles based on UMTSArchitecture view:

. If both of the external interfaces - Uu and Iu -are related to thedefined KPI then it is on the highest level from the UMTSarchitecture perspective.

. If either of the external interfaces - Uu or Iu - are related to thedefined KPI then it is on the second level from the UMTSarchitecture perspective.

. When dealing with RNC function-managed internal interfacestowards either one of the external interfaces, the defined KPI is onthe third level from the UMTS architecture perspective.

. The TRM-related KPIs are found on the fourth level from the UMTSarchitecture perspective.

. Finally, the UTRAN Access Point (WCELL)-related issues are on thefifth level from the UMTS architecture perspective.


30/04/2009


2.4.2 Principles of using defined QoS architecture

The needed KPI levels from the UMTS architecture perspective were listedin the previous section.

The QoS architecture only provides additional details to the needed KPIlevels.

2.4.3 Access network level KPIs

The defined access network level-KPIs in this document cover the externalinterfaces of the access network towards either the Uu or Iu interface orboth interfaces.

UMTS architecture view: When the KPIs of this level are used, they followup actions of interest between the Mobile Equipment Domain and/or theService Network Domain from the perspective of the Access NetworkDomain.

QoS architecture view: When the KPIs of this level are used, they givesuccess rates related to 'call' and LCS services.

‘Calls’ are visible in the defined bearer architecture but the LCS utilizes thecontrol plane. Thus, it is not visible in the bearer architecture.

Furthermore, the KPIs of this level provide additional success rates relatedto UE network connection, Radio Access Bearer Service(s), incomingServing Radio Network subsystem change (SRNS) and outgoing HardHandovers to either another SRNS (Intra-System or Inter-FrequencyHHO) or other radio access system (Inter-System HHO).

Radio Access Bearer Service(s) are visible in the defined bearerarchitecture but the other access network level KPIs are not visible in thebearer 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

DN05191189Issue 4-3 en draft30/04/2009



. 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

. Hard Handover Success Rate KPIs. ISHO-related found target cell rate in other Access Network. IFHO and ISHO success rates

2.4.4 RNC function level KPIs

The defined KPIs of the RNC function level cover the internal interfaces ofthe access network towards either Uu or Iu interface.

UMTS architecture view: When the KPIs of this level are used, they followup actions of interest between either the Mobile Equipment Domain orService Network Domain from the perspective of the Access NetworkDomain.

QoS architecture view: When the KPIs of this level are used, they givesuccess rates related to Packet Sessions, availability of internal andexternal logical interfaces, resource request amounts, resource usernumbers, reserved capacity numbers and consumed capacity numbers.

Packet Session(s) are visible in the defined bearer architecture but theother KPIs of the RNC function level are not visible in the bearerarchitecture.


. Packet Session Setup Success (SSSR) KPIs

. Packet Session Success (SSR) KPIs

. Requested RRC Connection attempt number KPIs

. Requested Service attempt number KPIs


30/04/2009


. Requested Packet Session attempt number KPIs

. 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

2.4.5 Transport Resource Manager level KPIs

The defined KPIs of the Transport Resource Manager level in thisdocument cover the external and internal transport interfaces of theaccess network.

UMTS architecture view: When the KPIs of this level are used, they followup actions of interest between the Servicing Network Domain and theAccess Network Domain or fully inside the Access Network Domain.

QoS architecture view: When the KPIs of this level are used, they giveavailability rates, load levels and data volumes of internal transportservices.

The KPIs of the TRM level are not visible in the bearer architecture.


. Reserved transport bandwidth KPIs

. Available transport bandwidth KPIs

DN05191189Issue 4-3 en draft30/04/2009



. Transport Interface volume KPIs

. Transport Interface throughput KPIs

. Transport Interface load KPIs

2.4.6 Access point-level KPIs

The defined Access point level KPIs in this document cover the externaland internal interfaces of access network towards Uu interface.

UMTS architecture view: When the KPIs of this level are used, they followup actions of interest between the Mobile Equipment Domain and theAccess Network Domain or fully inside the Access Network Domain.

QoS architecture view: When the KPIs of this level are used, they giveavailability rates and reservation numbers of logical or physical resourcesand RL-specific issues for data volumes and error rates.

The access point level-KPIs are not visible in the bearer architecture.


. 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

. 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


30/04/2009


. MAC layer active data throughput

. FP layer data volumes

. Block Error Rate KPIs. Service UL and DL. HSDPA efficiency. HSUPA BLER

2.5 System Program Report

All KPIs defined in this document are important basic network level KPIsfor a WCDMA RAN network. In addition to the KPIs defined in thisdocument there are also various KPIs needed for additional purposesfound in different reporting tools.

When extensive (daily or weekly) follow-up is needed, the number of KPIsneeds to be reduced.

For this purpose a System Program report is created on basis of theWCDMA RAN release.

2.5.1 Principles of System Program Report

The System Program report follows the same structures (KPI levels andKPI 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 thereport.

For the KPIs related to the System Program Report, the target values ortarget references are given. The given target value/reference is eitherbased on the values experienced in the live network or maximumreceivable values set by performance and/or capacity targets.

2.5.2 System Program Report content

The performance targets given in the following table are the averagetargets for a cell cluster. Performance of an individual cell may differ fromthe given values.

DN05191189Issue 4-3 en draft30/04/2009



Note

Changes in measurements, calculation formulas, and/or used countersaffect the listed key performance indicator (KPI) values.

Note

The specified targets are not accurate if the load in the network is toolow. The load in the network is too low if the average number of calls percell is lower than (x) during a busy hour.

Note

The specified targets are not accurate if the load in the network ishigher than the planned target load of the network, or if the actual trafficmix differs considerably from the plan.

The following table lists the KPIs that are related to System ProgramReport according to agreed classification.

Table 8. WCDMA RAN KPIs related to System Program Report

KPI Level KPI Class KPI ID Indicates Availablesince

LiveNetworkTarget

Access network Accessibility RNC_20b RRC Connectionsetup success ratio

RAN1.5.2ED

>=RNC_94e

Access network Accessibility RNC_94e RRC Setup andAccess CompleteRatio, from NetworkPerspective

RAN04 > 98.5 %

Access network Accessibility RNC_154d RRC Setup andAccess CompleteRatio

RAN04 > 99%

Access network Accessibility RNC_219a Registration Success RAN1.5.2ED

>=RNC_94e

Access network Accessibility RNC_565f Voice Call SetupSuccess Ratio(CSSR)

RAN05 > 99.2%

Access network Accessibility RNC_30a > 99.6%


30/04/2009


Table 8. WCDMA RAN KPIs related to System Program Report (cont.)


LiveNetworkTarget

RAB Setup andAccess CompleteRatio for Voice

RAN1.5.2ED

Access network Accessibility RNC_566e UDI Call SetupSuccess Ratio(CSSR)

RAN05 > 99%

Access network Accessibility RNC_31a RAB Setup andAccess CompleteRatio for UDI

RAN1.5.2ED

> 99.5%

Access network Accessibility RNC_575d Streaming Call SetupSuccess Ratio(CSSR)

RAN05 > 98%

Access network Accessibility RNC_618a RAB Setup andAccess CompleteRatio for Streaming

RAN1.5.2ED

> 99.5%

Access network Accessibility RNC_576e Packet Service SetupSuccess Ratio(CSSR)

RAN05 > 99.5%

Access network Accessibility RNC_157a RAB Setup andAccess CompleteRatio for NRT Service

RAN1.5.2ED

> 99.7%

Access network Accessibility RNC_916b Packet Session SetupSuccess Ratio(SSSR)

RAS06 No targetcan begiven yet(waiting forRAS06data)

Access network Accessibility RNC_741a Multi RAB Setup andAccess Success Rate

RAN04 =RNC_575d

Access network Retainability RNC_217e RRC Success Ratio RAN1.5.2ED

> 99.5%

Access network Retainability RNC_231c RAB Success Ratio,Voice (CSR)

RAN1.5.2ED

> 99.5%

Access network Retainability RNC_232c RAB Success Ratio,UDI (CSR)

RAN1.5.2ED

> 99%

Access network Retainability RNC_619a RAB Success Ratio,Streaming (CSR)

RAN1.5.2ED

> 99%

Access network Retainability RNC_736a RAB Success Ratio,NRT Services

RAN04 > 99%

Access network Retainability RNC_615b RAN04

DN05191189Issue 4-3 en draft30/04/2009





LiveNetworkTarget

RAB Success Ratio,NRT Services, fromNetwork Perspective

> 95-99 %(dependson inactivitytimersettings,usually 98% isachieved)

Access network Retainability RNC_922b Packet SessionSuccess Ratio (SSR)


Access network Retainability RNC_742a Multi RAB SuccessRate

RAN04 =RNC_619a

Access network Usage/Duration

RNC_745a Voice, Minutes RAS05 6)


RNC_746a UDI, Minutes RAS05 6)


RNC_737a Minutes per DropVoice

RAS05 > 300minutes


RNC_738a Minutes per Drop UDI RAS05 > 300minutes

Access Network Usage/Duration

RNC_5050a Iu-PS data volumeper drop - ATM based

RU10 No targetcan begiven yet(waiting forRU10 data)


RNC_5051a Iu-PS data volumeper drop - IP based

RU10 No targetcan begiven yet(waiting forRU10 data)

Access network Mobility RNC_168a Intra System HardHandover SuccessRatio

RAN1.5.2ED

> 95%

Access network Mobility RNC_300f Inter System RT HardHandover SuccessRatio

RAS05.1ED

> 96%

Access network Mobility RNC_301d Inter System NRTHard HandoverSuccess Ratio

RAS05.1ED

> 85%


30/04/2009




LiveNetworkTarget

Access network Mobility RNC_302c Inter System HHODrop Rate RT

RAS05.1ED

< 0.5%

Access network Mobility RNC_303c Inter System HHODrop Rate NRT

RAS05.1ED

< 5%

RNC function Accessibility RNC_914c HSDPA SetupSuccess Ratio

RU10 No targetcan begiven yet(waiting forRAS06data)

RNC function Accessibility RNC_605a HSDPA ResourceAccessibility for NRTTraffic

RAS06 > 99 %

RNC function Accessibility RNC_915c HSUPA SetupSuccess Ratio


RNC function Accessibility RNC_913a HSUPA ResourceAccessibility for NRTTraffic


RNC function Accessibility RNC_943b R99 Setup SuccessRatio


RNC function Retainability RNC_920b HSDPA SuccessRatio


RNC function Retainability RNC_609a HSDPA ResourceRetainability for NRTTraffic

RAS06 > 99%

RNC function Retainability RNC_921b HSUPA SuccessRatio

RU10

DN05191189Issue 4-3 en draft30/04/2009





LiveNetworkTarget

No targetcan begiven yet(waiting forRAS06data)

RNC function Retainability RNC_919a HSUPA ResourceRetainability for NRTTraffic


RNC function Retainability RNC_944b R99 Success Ratio RU10 No targetcan begiven yet(waiting forRAS06data)

RNC function Usage/RequestedCapacity

RNC_214a RRC Setup Attempts RAN1.5.2ED

1)


RNC_218a Registration Attempts RAN1.5.2ED

1)


RNC_5046a Short MessageService Attempts foridle mode UEs

RU10 6)


RNC_5047a Incoming LocationService Attempts

RU10 6)


RNC_229a RAB Attempts Voice RAN1.5.2ED

2)


RNC_268a RAB Attempts UDI RAN1.5.2ED

2)


RNC_617a RAB AttemptsStreaming

RAN1.5.2ED

2)


RNC_616a RAB Attempts PSInteractive andBackground

RAN1.5.2ED

2)

RNC function RNC_930b RAS06 2)


30/04/2009




LiveNetworkTarget

Usage/RequestedCapacity

Packet Sessionattempts


RNC_740a Multi RAB Attempts RAN1.5.2ED

2)


RNC_926b HSDPA Attempts RAN1.5.2ED

2)


RNC_928b HSUPA Attempts RAN1.5.2ED

2)


RNC_193a Soft HandoverUpdate Attempts, RT

RAN1.5.2ED

3)


RNC_194a Soft HandoverUpdate Attempts,NRT

RAN1.5.2ED

3)


RNC_743a Intra System HardHandover attempts

RAN1.5.2ED

4)


RNC_298d Inter System HardHandover attempts,RT

RAN1.5.2ED

4)


RNC_299c Inter System HardHandover attempts,NRT

RAN1.5.2ED

4)


RNC_5028a Incoming InterSystem ChangeAttempts

RU10 1)


RNC_927a HSDPA Serving CellChange Attempts

RAS06 4)


RNC_929a HSUPA Serving CellChange Attempts

RAS06 4)

RNC function Usage/AllocatedCapacity

RNC_164f Average AllocatedUplink DedicatedChannel Capacity forData Calls inControlling RNC

RAN04 5)

RNC function RNC_165g RAN04 5)

DN05191189Issue 4-3 en draft30/04/2009





LiveNetworkTarget

Usage/AllocatedCapacity

Average AllocatedDownlink DedicatedChannel Capacity forData Calls inControlling RNC


RNC_614b HS-DSCH Selections RAS05 2)


RNC_923b E-DCH Selections RAS05 2)


RNC_192b Soft HandoverOverhead in CRNC

RAN1.5.2ED

3)

RNC function Usage/Throughput

RNC_280b Average CS Erlang RAN04 6)


RNC_5027a Iu-PS GTP total inputtraffic in RNC

RU10 5)


RNC_5021a Iu-PS peakthroughput

RU10 5)


RNC_931c HSUPA MAC-es datavolume at RNC

RAS06 5)


RNC_5043a HSDPA MAC-d datavolume at RNC

RU10 5)


RNC_721c Average MAC-d flowthroughput


Access point Usage/ResourceAvailability

RNC_183c Cell Availability RAN05 > 99.9%


RNC_727a Cell Availability,excluding blocked byuser state (BLU)

RAS05.1 >=RNC_183c

Access point Usage/Throughput

RNC_608b WBTS: HSDPAReceived Data

RAS05 7)


RNC_722c RAS06 8)


30/04/2009




LiveNetworkTarget

WBTS: Active HS-DSCH MAC-dthroughput, networkperspective

Access point Mobility RNC_153b Soft HandoverSuccess Rate RT

RAN1.5.2ED

> 96%

Access point Mobility RNC_191b Soft HandoverSuccess Rate NRT

RAN1.5.2ED

> 96%

Access point Mobility RNC_733a HSDPA Serving CellChange SuccessRate

RAS06 > 99%

Access point Mobility RNC_918a HSUPA Serving CellChange SuccessRate


Access point Integrity/Errorrates

RNC_607c WBTS: HSDPA MAC-hs efficiency

RAS05 N/A


RNC_7063a NB/RSxx BTS: Theaverage ratio of notacknowledged HARQprocesses

RU10 N/A


RNC_917a WBTS: HSDPA MAC-es BLER

RAS06 N/A


RNC_7070a NB/RSxx BTS:HSUPA HARQ notacknowledged Ratio

RU10 N/A

References:

1) See RNC Product Description for Maximum number of RRC ConnectedMode users during Busy Hour (BH).

2) See RNC Product Description for Busy Hour Call Attempts (BHCA).

3) See RNC Product Description for assumed SHO Proportions in relationto established calls.

4) See RNC Product Description for assumed HHO Proportions in relationto established calls.

DN05191189Issue 4-3 en draft30/04/2009



5) See RNC Product Description for maximum supported throughput.

6) See RNC Product Description for maximum supported Erlang.

7) See BTS Product Description for maximum HSDPA cell-supportedthroughput.

8) See BTS Product Description for maximum HSDPA user-supportedthroughput.


30/04/2009


3 Terms and definitions

The following terms used in the document are defined in 3GPPspecifications:

. Call

. UE Domain

. Uu or UMTS Radio Interface

. Access Domain

. Iu

. Infrastructure Domain

. Core Network Domain

. Service Domain

. Access Stratum

. Service Stratum

. Network Connection = Radio Resource Control

. Network Service = Radio Access Bearer (RAB) Service

. RAN Service = Radio Bearer (RB) Service

. Service Access Point (SAP)

. UTRAN Access Point

. Radio link

. Packet Session = DCH/HS-DSCH 'live time'

. Packet Call = Packet's sending interval

Call-related definitions

DN05191189Issue 4-3 en draft30/04/2009


Terms and definitions

Call The combination of the RAB(s), RB and the RL for aUE. It is also obligatory that the RB is configured tocarry user data.

Call Type A call type can be distinguished from the relatedservice, that is, RAB parameters. The call typesdistinguished by this document are Voice, UDI,Streaming Call (DCH), Streaming Session (E-DCH/HS-DSCH) and Packet Session.

In this document, Packet Session is considered to bea Packet Call described in Calls in WCDMA RAN.

CCH Service Common Channel (CCH) Utilization = Datatransmitted on RACH or FACH

Mobile Status RRC State = varies from idle ( = no networkconnection) to URA_PCH or Cell_PCH (= NetworkConnection + Network Service) to CELL_FACH(Network Connection + Network Service + 'CCH'Service) to CELL_DCH (Network Connection +Network Service + RAN Service)

Packet Service A RAB with RAB QoS parameters: Traffic Class =Interactive or Background.

The RRC setup has been done with cause codes:MOC Interactive, MTC Interactive, MOC Backgroundor MTC Background.

Packet Session A call with RAB/RB QoS parameters: Traffic Class =Interactive or Background. Here a call refers to theDCH/HS-DSCH/E-DCH live time, that is, the time thesession is active for traffic.

The RRC setup has been done with cause codes:MOC Interactive, MTC Interactive, MOC Backgroundor MTC Background.

In this document, Packet Session is considered to bea Packet 'Call' described in Calls in WCDMA RAN.

Packet 'Call' See Packet Session.

Packet Call Packet's sending interval inside a DCH/HS-DSCH/E-DCH transport channel with RAB/RB QoSparameters: Traffic Class = Streaming, Interactive orBackground. A packet call ends every time there is asilent period in transmission. The session can still beup even if there is no data sending ongoing.

The RRC setup has been done with the followingcause codes: MOC Streaming, MTC Streaming,MOC Interactive, MTC Interactive, MOC Backgroundor MTC Background.


30/04/2009


Streaming 'Call' A call with RAB/RB QoS parameters: Traffic Class =Streaming.

The RRC setup has been done with the followingcause codes: MOC Streaming and MTC Streaming.

Streaming ServiceA RAB with RAB QoS parameters: Traffic Class =Streaming.


Streaming SessionA call with RAB/RB QoS parameters: Traffic Class =Streaming. A call here means the HS-DSCH/E-DCH'live time', that is, the time the session is active fortraffic.


In this document, a Streaming Session is consideredto be a Streaming 'Call' described in Calls in WCDMARAN.

UDI Call A call with RAB/RB QoS parameters: Traffic Class =Conversational; Statistics Source Descriptor =Unknown.

The RRC setup has been done with the followingcause codes: MOC Conversational or MTCConversational.

Voice Call A call with RAB/RB QoS parameters: Traffic Class =Conversational; Statistics Source Descriptor = Voice.

The RRC setup has been done with the followingcause codes: MOC Conversational, MTCConversational and Emergency call.

Definitions related to mobility

Inter System ChangeAn Inter System Change covers in addition to ISHOcell re-selections between systems done by UEs inthe idle mode.

Inter System Hard HandoverAn Inter System Hard Handover (ISHO) covers onlythe cases that include moving a call from a system(for example, 3G) to another (for example, GSM).

Currently the ISHO KPI in the document refers toHOs between GSM and 3G.

DN05191189Issue 4-3 en draft30/04/2009


Terms and definitions

Tip

There are also cases where the CELL_FACH or CELL_PCH states donot have an active radio access bearer (RAB).


30/04/2009


4 Available WCDMA RAN key performanceindicators

This section contains a summary of the current understanding of KPIs tobe followed in 3G radio access networks.

The KPI development work is always ongoing, and therefore the providedformulas and their target values are updated frequently.

Network acceptance targets are not covered here. If a KPI described hereis also part of an acceptance agreement, the acceptance target for the KPIdepends on the acceptance agreement.

Previously a target value or a reference was available for all documentedKPIs. The approach has now changed. For information on any targetvalues or references, see the KPIs in System Program Report.

In the following table you can see all the key performance indicators inWCDMA RAN.

In the table, the following information is given:

. KPI level

The level of the key performance indicators.

. KPI class

The KPI class and possible additional classification

. KPI ID

The ID of the key performance indicator.

. Latest KPI version

The version of the latest and recommended key performanceindicator.

DN05191189Issue 4-3 en draft30/04/2009


Available WCDMA RAN key performance indicators

. Indicates

States what the key performance indicator is used for.

. Available since

The availability of the key performance indicator as a counter. Showsthe release when the KPI became available.

Table 9. Available KPIs in WCDMA RAN

KPI level KPI class KPI ID LatestKPIversion

Indicates Availablesince

Access network Accessibility RNC_20b 1.0u RRC Connection SetupSuccess Ratio

RAN1.5.2ED

Access network Accessibility RNC_94e 6.5u RRC Setup and AccessComplete Ratio, fromNetwork Perspective

RAN04

Access network Accessibility RNC_154d 6.5u RRC Setup and AccessComplete Ratio

RAN04

Access network Accessibility RNC_219a 2.1u Registration Success RAN1.5.2ED

Access network Accessibility RNC_565f 6.6u Voice Call SetupSuccess Ratio (CSSR)

RAN05

Access network Accessibility RNC_30a 6.5u RAB Setup and AccessComplete Ratio for Voice

RAN1.5.2ED

Access network Accessibility RNC_566e 6.6u UDI Call Setup SuccessRatio (CSSR)

RAN05

Access network Accessibility RNC_31a 1.1u RAB Setup AccessSuccess Ratio for UDI

RAN1.5.2ED

Access network Accessibility RNC_575d 6.5u Streaming Call SetupSuccess Ratio (CSSR)

RAN05

Access network Accessibility RNC_618a 1.1u RAB Setup AccessSuccess Ratio forStreaming

RAN1.5.2ED

Access network Accessibility RNC_576e 1.0u Packet Service SetupSuccess Ratio (CSSR)

RAN05

Access network Accessibility RNC_157a 6.5u RAB Setup and AccessComplete Ratio for NRTService

RAN1.5.2ED

Access network Accessibility RNC_916b 2.6u Packet Session SetupSuccess Ratio (SSSR)

RAS06

Access network Accessibility RNC_741a 1.1u Multi RAB Setup andAccess Success Ratio

RAN04


30/04/2009


Table 9. Available KPIs in WCDMA RAN (cont.)



Access network Accessibility RNC_544a 5.3u LCS Setup and AccessComplete Ratio

RAN04

Access network Accessibility RNC_5008a 1.2u Relocation Success inTarget RNC for CS

RU10

Access network Accessibility RNC_5009a 1.2u Relocation Success inTarget RNC for PS

RU10

Access network Accessibility RNC_5004a 1.1u Incoming Inter SystemHHO Success in TargetRNC for CS

RU10

Access network Accessibility RNC_5030a 1.0u Incoming Inter SystemHard Handover SuccessRate in Target RNC forPS

RU10

Access network Retainability RNC_217e 6.5u RRC Success Ratio RAN1.5.2ED

Access network Retainability RNC_231c 6.5u RAB Success Ratio,Voice (CSR)

RAN1.5.2ED

Access network Retainability RNC_232c 1.1u RAB Success Ratio, UDI(CSR)

RAS05.1

Access network Retainability RNC_619a 1.1u RAB Success Ratio,Streaming (CSR)

RAS05.1

Access network Retainability RNC_736a 3.4u RAB Success Ratio,NRT Services

RAN04

Access network Retainability RNC_615b 6.3u RAB Success Ratio,NRT Services, fromNetwork Perspective

RAN04

Access network Retainability RNC_922b 2.6u Packet Session SuccessRatio (SSR)

RAS06

Access network Retainability RNC_742a 1.1u Multi RAB Success Ratio RAN04


RNC_745a 2.2u Voice, Minutes RAS05.1ED


RNC_746a 2.1u UDI, Minutes RAS05.1ED


RNC_737a 2.1u Minutes per Drop Voice RAS05.1ED


RNC_738a 2.1u Minutes per Drop UDI RAS05.1ED


RNC_5050a 1.0u Iu-PS data volume perdrop - ATM based

RU10

DN05191189Issue 4-3 en draft30/04/2009







RNC_5051a 1.0u Iu-PS data volume perdrop - IP based

RU10

Access network Mobility RNC_168a 6.4u Intra System HardHandover Success Ratio

RAN1.5.2ED

Access network Mobility RNC_300f 1.0u Inter System RT HardHandover Success Ratio

RAS05.1ED

Access network Mobility RNC_301d 3.4u Inter System NRT HardHandover Success Ratio

RAS05.1ED

Access network Mobility RNC_302c 2.1u Inter System HHO DropRate RT

RAS05.1ED

Access network Mobility RNC_303c 2.1u Inter System HHO DropRate NRT

RAS05.1ED

RNC function Accessibility RNC_605a 4.5u HSDPA ResourceAccessibility for NRTTraffic

RAN05

RNC function Accessibility RNC_5000a 1.2u HSDPA ResourceAccessibility for RTTraffic

RU10

RNC function Accessibility RNC_914c 1.0u HSDPA Setup SuccessRatio

RAS06

RNC function Accessibility RNC_913a 2.3u HSUPA ResourceAccessibility for NRTTraffic

RAS06

RNC function Accessibility RNC_5002a 1.1u HSUPA ResourceAccessibility for RTTraffic

RU10

RNC function Accessibility RNC_915c 1.0u HSUPA Setup SuccessRatio

RAS06

RNC function Accessibility RNC_943b 1.0u R99 Setup SuccessRatio

RAS06

RNC function Retainability RNC_609a 4.4u HSDPA ResourceRetainability for NRTTraffic

RAN05

RNC function Retainability RNC_5010a 1.2u HSDPA ResourceRetainability for RTTraffic

RU10

RNC function Retainability RNC_920b 1.0u HSDPA Success Ratio RAS06

RNC function Retainability RNC_919a 2.4u RAS06


30/04/2009





HSUPA resourceRetainability for NRTTraffic

RNC function Retainability RNC_5012a 1.1u HSUPA resourceRetainability for RTTraffic

RU10

RNC function Retainability RNC_921b 1.0u HSUPA Success Ratio RAS06

RNC function Retainability RNC_944b 1.0u R99 Success Ratio RAS06


RNC_214a 2.1u RRC Setup Attempts RAN1.5.2ED


RNC_218a 2.1u Registration Attempts RAN1.5.2ED


RNC_5046a 1.0u Short Message ServiceAttempts for idle modeUEs

RU10


RNC_5047a 1.0u Incoming LocationService Attempts

RU10


RNC_229a 2.1u RAB Attempts Voice RAN1.5.2ED


RNC_268a 2.1u RAB Attempts UDI RAN1.5.2ED


RNC_617a 2.1u RAB Attempts Streaming RAN1.5.2ED


RNC_616a 2.1u RAB Attempts PSInteractive andBackground

RAN1.5.2ED


RNC_930b 2.2u Packet Session attempts RAS06


RNC_740a 2.1u Multi RAB Attempts RAN1.5.2ED


RNC_926b 1.0u HSDPA Attempts RAN1.5.2ED

DN05191189Issue 4-3 en draft30/04/2009







RNC_928b 1.0u HSUPA Attempts RAN1.5.2ED


RNC_193a 2.1u Soft Handover UpdateAttempts, RT

RAN1.5.2ED


RNC_194a 2.1u Soft Handover UpdateAttempts, NRT

RAN1.5.2ED


RNC_743a 2.1u Intra System HardHandover attempts

RAN1.5.2ED


RNC_298d 1.0u Inter System HardHandover attempts, RT

RAN1.5.2ED


RNC_299c 2.1u Inter System HardHandover attempts, NRT

RAN1.5.2ED


RNC_5028a 1.0u Incoming Inter SystemChange Attempts

RU10


RNC_927a 2.2u HSDPA Serving CellChange Attempts

RAS06


RNC_929a 2.2u HSUPA Serving CellChange Attempts

RAS06

RNC function Usage/ResourceAvailability

RNC_728a 3.3u Iu Availability RAS05.1

RNC function Usage/ResourceAvailability

RNC_729a 3.3u Iur Availability RAS05.1


RNC_162c 7.3u Average Allocated UplinkDedicated ChannelCapacity for CS Voice inControlling RNC

RAN1.5.2ED


RNC_163c 7.3u Average AllocatedDownlink DedicatedChannel Capacity for CSVoice in Controlling RNC

RAN1.5.2ED

RNC function RNC_164f 6.3u RAN04


30/04/2009






Average Allocated UplinkDedicated ChannelCapacity for Data Callsin Controlling RNC


RNC_165g 6.3u Average AllocatedDownlink DedicatedChannel Capacity forData Calls in ControllingRNC

RAN04


RNC_614c 1.0u HS-DSCH selections RAS05


RNC_923b 1.0u E-DCH selections RAS06


RNC_192b 6.4u Soft Handover Overheadin CRNC

RAN1.5.2ED


RNC_5025a 1.1u Peak number of RRCConnected Mode Usersin RNC

RU10


RNC_5016a 1.2u Maximum number ofVoice calls per RNC

RU10


RNC_5017a 1.2u Peak number of HSDPAusers in RNC

RU10


RNC_5018a 1.2u Peak number of HSUPAusers in RNC

RU10


RNC_280b 6.4u Average CS Erlang RAN04


RNC_5021a 1.2u Iu-PS peak throughput RU10


RNC_941b 3.3u Iu-PS GTP Average inputtraffic rate in RNC

RAS05.1ED


RNC_5027a 1.2u Iu-PS GTP total inputtraffic in RNC [Mbit]

RU10


RNC_5032a 1.0u Average NRT DCH DLThroughput

RAN05

RNC function RNC_5033a 1.0u RAN05

DN05191189Issue 4-3 en draft30/04/2009






Usage/Throughput

Average NRT HS-DSCHDL Throughput


RNC_5043a 1.0u HSDPA MAC-d datavolume at RNC

RU10


RNC_721c 1.0u Average MAC-d flowthroughput

RAS06


RNC_952c 1.0u HSUPA MAC-es averagethroughput at RNC

RAS06


RNC_931c 1.0u HSUPA MAC-es datavolume at RNC

RAS06

RNC function Integrity/Errorrates

RNC_5034a 1.0u Non Real Time RadioBearer UL BLER

RU10

RNC function Integrity/Errorrates

RNC_5035a 1.0u NRT DCH DL Efficiency RU10

Transport ResourceManager

Accessibility RNC_602a 4.3u AAL2 connectionreservation success rate

RAN05


Accessibility RNC_5005a 1.2u IP Route Accessibility RU10


Accessibility RNC_5031a 1.0u IP Route Accessibility forincoming iub traffic

RU10



RNC_601a 4.4u AAL2 path averagereserved bandwidth

RAN05



RNC_5052a 1.0u IP Route EgressReservation Rate

RU10


Usage/Throughput

RNC_950b 2.3u ATM interface basedaverage throughput foroutgoing traffic (RNCside)

RAS06


Usage/Throughput

RNC_951b 2.3u ATM interface basedaverage throughput forincoming traffic (RNCside)

RAS06


Usage/Throughput

RNC_945b 2.3u ATM interface basedoutgoing Data Volume(RNC side)

RAS06


Usage/Throughput

RNC_946b 2.3u RAS06


30/04/2009





ATM interface basedincoming Data Volume(RNC side)


Usage/Throughput

RNC_5022a 1.1u Outgoing IP route trafficvolume

RU10


Usage/Throughput

RNC_5029a 1.1u Incoming IP route trafficvolume

RU10


Usage/Transmissionload

RNC_960a 1.1u ATM VCC specificincoming traffic load

RU10


Usage/Transmissionload

RNC_732b 3.3u ATM VCC specificoutgoing traffic load

RAS05.1


RNC_183c 7.5u Cell Availability RAN05


RNC_727a 3.4u Cell Availability,excluding blocked byuser state (BLU)

RAS05.1

Access point Usage/RadioLoad

RNC_177b 6.4u Noise floor of the System RAN1.5.2ED


RNC_101b 6.3u Average Uplink R99Load

RAN1.5.2ED


RNC_102b 6.3u Average R99 DownlinkLoad

RAN1.5.2ED


RNC_1180a 2.4u Average HSUPA UplinkLoad

RAS06


RNC_1181a 2.4u Average HSPA DownlinkLoad

RAS06

Access point Usage/HWResources

RNC_730a 3.3u Average ratio of utilizedCE for DL in BTS

RAS05.1


RNC_731a 3.3u Average ratio of utilizedCE for UL in BTS

RAS05.1


RNC_7001a 1.0u NB/RSxx BTS: Theaverage license relateduplink channel elementusage ratio

RU10


RNC_7005a 1.0u RU10

DN05191189Issue 4-3 en draft30/04/2009






NB/RSxx BTS: Theaverage license relateddownlink channelelement usage ratio


RNC_5019a 1.2u Iub data volume DL inBTS

RU10


RNC_608b 4.5u HSDPA received data RAN05


RNC_739c 2.3u HSDPA MAC-d datavolume at BTS

RAS06


RNC_606d 5.3u HSDPA MAC-d Averagenet throughput at BTS

RAN05


RNC_722c 2.5u WBTS: Active HS-DSCHMAC-d throughput,network perspective

RAS06


RNC_5020a 1.2u Iub data volume UL inBTS

RU10

Access point Mobility RNC_195a 6.3u Soft Handover SuccessRate

RAN1.5.2ED

Access point Mobility RNC_153b 2.1u Soft Handover SuccessRate, RT

RAN1.5.2ED

Access point Mobility RNC_191b 2.1u Soft Handover SuccessRate, NRT

RAN1.5.2ED

Access point Mobility RNC_733a 3.4u HSDPA Serving CellChange Success Rate

RAS05

Access point Mobility RNC_918a 2.5u HSUPA Serving CellChange Success Rate

RAS06


RNC_607c 4.3u HSDPA MAC-hsefficiency

RAN05


RNC_7063a 1.0u NB/RSxx BTS: Theaverage ratio of notacknowledged HARQprocesses

RU10


RNC_5037a 1.0u Voice RB UL BLER RU10


RNC_5036a 1.0u Real Time Radio BearerUL BLER

RU10


RNC_917a 2.6u HSUPA MAC-es BLER RAS06


30/04/2009






RNC_7070a 1.0u NB/RSxx BTS: HSUPAHARQ not acknowledgedRatio

RU10


RNC_5023a 2.4u Voice DL BLER RU10


RNC_5024a 2.4u Real Time Radio Bearer(Voice excluded) DLBLER

RU10

For basic information on WCDMA RAN KPIs, see Overview of WCDMARAN key performance indicators.

For more information on different indicators, see the following:

. Access Network level KPIs. Access network level indicators for accessibility. Access network level indicators for retainability. Access network level indicators for usage. Access network level indicators for mobility

. RNC Function level KPIs. RNC function level indicators for accessibility. RNC function level indicators for retainability. RNC function level indicators for usage

. Transport Resource Manager level KPIs. Transport Resource Manager level indicators for accessibility. Transport Resource Manager level indicators for usage

. Access Point level KPIs. Access point level indicators for usage. Access point level indicators for mobility. Access point level indicators for integrity

4.1 KPI ID changes

The following table lists the KPI ID changes in RU10.

DN05191189Issue 4-3 en draft30/04/2009



Column RNC KPI ID contains the RNC version of the KPI ID, which is usedin this document. The format of this ID is RNC_xxxy where xxx stands forthe number of the KPI. Column RAN KPI ID contains the correspondingRAN KPI ID used in the earlier versions of the document.

The RNC KPI IDs where the value of xxx in RNC_xxxy is over 5000 are notlisted in this table, because these KPIs do not have a corresponding RANKPI ID.

Table 10. KPI ID changes

RNC KPI ID RAN KPI ID

RNC_101b RAN_KPI_0009


RNC_1180a RAN_KPI_0065


RNC_1182a RAN_KPI_CSR_UDI

RNC_1183a RAN_KPI_CSR_STREAMING_CALL

RNC_154d RAN_KPI_0001A

RNC_157a RAN_KPI_0004A

RNC_160d RAN_KPI_0007A

RNC_162c RAN_KPI_0014


RNC_164f RAN_KPI_0016

RNC_165g RAN_KPI_0017


RNC_169d RAN_KPI_0022












30/04/2009


Table 10. KPI ID changes (cont.)






RNC_217e RAN_KPI_0005A

RNC_231c RAN_KPI_0006A


RNC_300f RAN_KPI_0057




RNC_565f RAN_KPI_CSSR_AMR

RNC_566e RAN_KPI_CSSR_UDI

RNC_575d RAN_KPI_CSSR_STREAMING_CALL

RNC_576d RAN_KPI_CSSR_PACKET_SERVICE













RNC_727a RAN_KPI_0018B





DN05191189Issue 4-3 en draft30/04/2009



Table 10. KPI ID changes (cont.)





RNC_736a RAN_KPI_0008A







RNC_916b RAN_KPI_SSSR_PACKET_SESSION_NRT






RNC_922b RAN_KPI_SSR_PACKET_SESSION_NRT
















30/04/2009


DN05191189Issue 4-3 en draft30/04/2009




30/04/2009


5 Available key performance indicators performula

5.1 Access network level

5.1.1 Access network level indicators for accessibility

The services and resources related to the KPIs are described in Radionetwork in the 3G system and UTRAN Resource Model overview inWCDMA RAN System Overview.


5.1.1.1 Call Setup Success Ratio (CSSR) [%]

Table 11. Voice Call Setup Success Ratio (CSSR)

KPI name Voice Call Setup Success Ratio (CSSR)

KPI abbreviation CSSR CS Voice

KPI ID RNC_565f

KPI version 6.6u

Description AMR Call Setup Success Ratio [%] over the reportingperiod.

Note 1 The RRC request repetitions done by UE after RRC rejectare included in the formula.

Note 2 The occurred cell re-selections are subtracted both from thenumerator and denominator because they are notconsidered as call attempts from mobile end-user point ofview. The UE has made a new RRC connection via anothercell and Attempts-counter is updated in the new cell for thenew attempt.

DN05191189Issue 4-3 en draft30/04/2009


Available key performance indicators per formula

Table 11. Voice Call Setup Success Ratio (CSSR) (cont.)

Note 3 The possible directed retries are subtracted from the RABdenominator because they are not considered as callattempts from mobile end-user point of view. The RANdirects the UE to GSM at RAB setup and therefore the RABsetup attempt doesn't in fact happen at all in RAN.

Measurement M1001: Service Level

KPI formula 100* sum([M1001C22] - [M1001C23] + [M1001C32] -[M1001C33] + [M1001C40] - [M1001C41] - [M1001C562] -[M1001C553] - [M1001C558]) / sum([M1001C22] +[M1001C32] + [M1001C40] - [M1001C573] - [M1001C578] -[M1001C582] - [M1001C562] - [M1001C553] - [M1001C558]- [M1001C617]) * sum([M1001C115]) / sum([M1001C66] -[M1001C640])

KPI formula with short names 100* sum([MOC_CONV_CALL_ATTS] -[MOC_CONV_CALL_FAILS] + [MTC_CONV_CALL_ATTS] -[MTC_CONV_CALL_FAILS] + [EMERGENCY_CALL_ATTS]- [EMERGENCY_CALL_FAILS] -[RRC_ACC_REL_EMERGENCY] -[RRC_ACC_REL_MO_CONV] -[RRC_ACC_REL_MT_CONV]) / sum([MOC_CONV_CALL_ATTS] + [MTC_CONV_CALL_ATTS]+ [EMERGENCY_CALL_ATTS] -[RRC_ATT_REP_MO_CONV] -[RRC_ATT_REP_MT_CONV] -[RRC_ATT_REP_EMERGENCY] -[RRC_ACC_REL_EMERGENCY] -[RRC_ACC_REL_MO_CONV] -[RRC_ACC_REL_MT_CONV] -[RRC_CONN_STP_REJ_EMERG_CALL]) * sum([RAB_ACC_COMP_CS_VOICE]) / sum([RAB_STP_ATT_CS_VOICE] -[RRC_ACT_REL_DIRECTED_RETRY])

KPI class Accessibility

Unit Percentage

Target values > 99.2 %

Object Summary Levels Network, RNC

Object Summary Level notes -

Time Summary Levels Week, Day, Hour

Time Summary Level notes -

Table 12. UDI Call Setup Success Ratio (CSSR)

KPI name UDI Call Setup Success Ratio (CSSR)


30/04/2009


Table 12. UDI Call Setup Success Ratio (CSSR) (cont.)

KPI abbreviation UDI CSSR

KPI ID RNC_566e

KPI version 6.6u

Description UDI Call Setup Success Ratio [%] over the reporting period.




KPI formula 100 * sum([M1001C22] - [M1001C23] + [M1001C32] -[M1001C33] - [M1001C553] - [M1001C558]) / sum([M1001C22] + [M1001C32] - [M1001C573] - [M1001C578] -[M1001C553] - [M1001C558]) * sum([M1001C116]) / sum([M1001C67])

KPI formula with short names 100 * sum([MOC_CONV_CALL_ATTS] -[MOC_CONV_CALL_FAILS] + [MTC_CONV_CALL_ATTS] -[MTC_CONV_CALL_FAILS] - [RRC_ACC_REL_MO_CONV]- [RRC_ACC_REL_MT_CONV]) / sum([MOC_CONV_CALL_ATTS] + [MTC_CONV_CALL_ATTS] -[RRC_ATT_REP_MO_CONV] -[RRC_ATT_REP_MT_CONV] -[RRC_ACC_REL_MO_CONV] -[RRC_ACC_REL_MT_CONV]) * sum([RAB_ACC_COMP_CS_CONV]) / sum([RAB_STP_ATT_CS_CONV])


Unit Percentage

Target values > 99 %





Table 13. Streaming Call Setup Success Ratio (CSSR)

KPI name Streaming Call Setup Success Ratio (CSSR)

DN05191189Issue 4-3 en draft30/04/2009



Table 13. Streaming Call Setup Success Ratio (CSSR) (cont.)

KPI abbreviation Stream CSSR

KPI ID RNC_575d

KPI version 6.5u

Description Streaming Call Setup Success Ratio [%] over the reportingperiod.




KPI formula 100 * sum([M1001C24] - [M1001C25] + [M1001C34] -[M1001C35] - [M1001C554] - [M1001C559]) / sum([M1001C24] + [M1001C34] - [M1001C574] - [M1001C579] -[M1001C554] - [M1001C559]) * sum([M1001C117] +[M1001C119]) / sum([M1001C68] + [M1001C70])

KPI formula with short names 100 * sum([MOC_STREA_CALL_ATTS] -[MOC_STREA_CALL_FAILS] + [MTC_STREA_CALL_ATTS]- [MTC_STREA_CALL_FAILS] -[RRC_ACC_REL_MO_STREAMING] -[RRC_ACC_REL_MT_STREAMING]) / sum([MOC_STREA_CALL_ATTS] +[MTC_STREA_CALL_ATTS] -[RRC_ATT_REP_MO_STREAMING] -[RRC_ATT_REP_MT_STREAMING] -[RRC_ACC_REL_MO_STREAMING] -[RRC_ACC_REL_MT_STREAMING]) * sum([RAB_ACC_COMP_CS_STREA] +[RAB_ACC_COMP_PS_STREA]) / sum([RAB_STP_ATT_CS_STREA] +[RAB_STP_ATT_PS_STREA])


Unit Percentage







30/04/2009


Table 14. Packet Service Setup Success Ratio (CSSR)

KPI name Packet Service Setup Success Ratio (CSSR)

KPI abbreviation CSSR PS NRT

KPI ID RNC_576e

KPI version 1.0u

Description Packet Service Setup Success Ratio [%] over the reportingperiod.



Note 3 In RU10 it was decided that also RRC ConnectionEstablishment requests with 'high priority signaling' areinterpreted as Packet Service requests.


KPI formula 100 * sum([M1001C26] - [M1001C27] + [M1001C28] -[M1001C29] + [M1001C36] - [M1001C37] + [M1001C38] -[M1001C39] + [M1001C50] - [M1001C51] + [M1001C52] -[M1001C53] - [M1001C560] - [M1001C556] - [M1001C567] -[M1001C555] - [M1001C561] - [M1001C568]) / sum([M1001C26] + [M1001C28] + [M1001C50] + [M1001C36] +[M1001C38] + [M1001C52] - [M1001C580] - [M1001C575] -[M1001C587] - [M1001C576] - [M1001C581] - [M1001C590]- [M1001C560] - [M1001C556] - [M1001C567] -[M1001C555] - [M1001C561] - [M1001C568]) * sum([M1001C120]+[M1001C121]) /sum([M1001C71]+[M1001C72])

KPI formula with short names 100 * sum([MOC_INTER_CALL_ATTS] -[MOC_INTER_CALL_FAILS] + [MOC_BACKG_CALL_ATTS]- [MOC_BACKG_CALL_FAILS] +[MTC_INTER_CALL_ATTS] - [MTC_INTER_CALL_FAILS] +[MTC_BACKG_CALL_ATTS] - [MTC_BACKG_CALL_FAILS]+ [MOC_HIGH_PRIOR_SIGN_ATTS] -[MOC_HIGH_PRIOR_SIGN_FAILS] +[MTC_HIGH_PRIOR_SIGN_ATTS] -[MTC_HIGH_PRIOR_SIGN_FAILS] -[RRC_ACC_REL_INTERACTIVE] -[RRC_ACC_REL_MO_BACKGROUND] -[RRC_ACC_REL_MO_HIGH_PR_SIGN] -[RRC_ACC_REL_MO_INTERACTIVE] -[RRC_ACC_REL_MT_BACKGROUND] -[RRC_ACC_REL_MO_LOW_PR_SIGN]) / sum([MOC_INTER_CALL_ATTS] +[MOC_BACKG_CALL_ATTS] +

DN05191189Issue 4-3 en draft30/04/2009



Table 14. Packet Service Setup Success Ratio (CSSR) (cont.)

[MOC_HIGH_PRIOR_SIGN_ATTS] +[MTC_INTER_CALL_ATTS] + [MTC_BACKG_CALL_ATTS]+ [MTC_HIGH_PRIOR_SIGN_ATTS] -[RRC_ATT_REP_INTERACTIVE] -[RRC_ATT_REP_MO_INTERACTIVE] -[RRC_ATT_REP_MO_HIGH_PR_SIGN] -[RRC_ATT_REP_MO_BACKGROUND] -[RRC_ATT_REP_MT_BACKGROUND] -[RRC_ATT_REP_MT_HIGH_PR_SIGN] -[RRC_ACC_REL_INTERACTIVE] -[RRC_ACC_REL_MO_BACKGROUND] -[RRC_ACC_REL_MO_HIGH_PR_SIGN] -[RRC_ACC_REL_MO_INTERACTIVE] -[RRC_ACC_REL_MT_BACKGROUND] -[RRC_ACC_REL_MO_LOW_PR_SIGN]) * sum([RAB_ACC_COMP_PS_INTER]+[RAB_ACC_COMP_PS_BACKG]) /sum([RAB_STP_ATT_PS_INTER]+[RAB_STP_ATT_PS_BACKG])


Unit Percentage






Table 15. Packet Session Setup Success Ratio (SSSR)

KPI name Packet Session Setup Success Ratio (SSSR)

KPI abbreviation Packet Session stp SR

KPI ID RNC_916b

KPI version 2.6u

Description Packet Session Setup Success Ratio over the reportingperiod.

Note For differences between Packet Service, Packet Sessionand Packet call, see WCDMA RAN Key PerformanceIndicators.

Measurement M1022: Packet Call

KPI formula


30/04/2009


Table 15. Packet Session Setup Success Ratio (SSSR) (cont.)

100* sum([M1022C21] + [M1022C22] + [M1022C23] +[M1022C24] + [M1022C25] + [M1022C26] + [M1022C27] +[M1022C28] + [M1022C29] + [M1022C30] + [M1022C31] +[M1022C32]+ [M1022C190] + [M1022C191] + [M1022C192]+ [M1022C193] + [M1022C194] + [M1022C195]) / sum([M1022C3] + [M1022C4] + [M1022C5] + [M1022C6] +[M1022C7] + [M1022C8] + [M1022C181] + [M1022C182] +[M1022C183])

KPI formula with short names 100* sum([HS_E_REQ_HS_E_ALLO_INT] +[HS_E_REQ_HS_E_ALLO_BGR] +[HS_E_REQ_HS_D_ALLO_INT] +[HS_E_REQ_HS_D_ALLO_BGR] +[HS_D_REQ_HS_D_ALLO_INT] +[HS_D_REQ_HS_D_ALLO_BGR] +[HS_E_REQ_D_D_ALLO_INT] +[HS_E_REQ_D_D_ALLO_BGR] +[HS_D_REQ_D_D_ALLO_INT] +[HS_D_REQ_D_D_ALLO_BGR] +[D_D_REQ_D_D_ALLO_INT] +[D_D_REQ_D_D_ALLO_BGR]+[HS_E_REQ_HS_E_ALLO_STRE] +[HS_E_REQ_HS_D_ALLO_STRE] +[HS_D_REQ_HS_D_ALLO_STRE] +[HS_E_REQ_D_D_ALLO_STRE] +[HS_D_REQ_D_D_ALLO_STRE] +[D_D_REQ_D_D_ALLO_STRE]) / sum([PS_ATT_HSDSCH_EDCH_INT] +[PS_ATT_HSDSCH_EDCH_BGR] +[PS_ATT_HSDSCH_DCH_INT] +[PS_ATT_HSDSCH_DCH_BGR] +[PS_ATT_DCH_DCH_INT] + [PS_ATT_DCH_DCH_BGR] +[PS_ATT_HSDSCH_EDCH_STRE] +[PS_ATT_HSDSCH_DCH_STRE] +[PS_ATT_DCH_DCH_STRE])


Unit Percentage

Target values

Object Summary Levels Network, City, Area, RNC, Cluster of cells, Cell




DN05191189Issue 4-3 en draft30/04/2009



5.1.1.2 LCS Setup [%]

Table 16. LCS Setup and Access Complete Ratio

KPI name LCS Setup and Access Complete Ratio

KPI abbreviation LCS stp and acc CR

KPI ID RNC_544a

KPI version 5.3u

Description LCS Setup and Access Complete Ratio [%] over thereporting period. Covers the phase from Location ReportingRequest to Location Control Report.

Measurement M1011: Location Services

KPI formula 100* sum([M1011C0] - [M1011C2]) / sum([M1011C0])

KPI formula with short names 100* sum([NBR_OF_LCS_REQUESTS] -[NBR_OF_FAILED_LOCREQ]) / sum([NBR_OF_LCS_REQUESTS])


Unit Percentage

Target values N/A (Not enough experience yet)





5.1.1.3 RRC Setup Complete Ratio [%]

Table 17. RRC Connection setup Success Ratio

KPI name RRC Connection setup Success Ratio

KPI abbreviation RRC conn stp SR

KPI ID RNC_20b

KPI version 1.0u

Description RRC Connection setup success ratio.


KPI formula 100*sum([M1001C1]) / sum([M1001C0] + [M1001C259] -[M1001C260])

KPI formula with short names


30/04/2009


Table 17. RRC Connection setup Success Ratio (cont.)

100*sum([RRC_CONN_STP_COMP]) / sum([RRC_CONN_STP_ATT] +[RRC_CONN_SETUP_COMP_AFT_DIR] -[RRC_CON_SETUP_COMP_DIRECTED])


Unit #

Target values -



Time Summary Levels Total; week; weeklyBH; day; dailyBH; hour


5.1.1.4 RRC Setup and Access Complete Ratio [%]

Table 18. RRC Setup and Access Complete Ratio, from Network Perspective

KPI name RRC Setup and Access Complete Ratio, from NetworkPerspective

KPI abbreviation RRC stp and acc CR NW

KPI ID RNC_94e

KPI version 6.5u

Description RRC Setup and Access Complete Ratio [%] over thereporting period. Covers RRC Setup and Access phases(From RRC Connection Request to RRC Connection SetupComplete).

Note RRC connection is needed also for other purposes than acall (SMS, LU, Detach, etc.).


KPI formula 100* sum([M1001C8] + [M1001C260]) / sum([M1001C0] +[M1001C259] - [M1001C617])

KPI formula with short names 100* sum([RRC_CONN_ACC_COMP] +[RRC_CON_SETUP_COMP_DIRECTED]) / sum([RRC_CONN_STP_ATT] +[RRC_CONN_SETUP_COMP_AFT_DIR] -[RRC_CONN_STP_REJ_EMERG_CALL])


Unit Percentage

Target values > 98.5%

DN05191189Issue 4-3 en draft30/04/2009



Table 18. RRC Setup and Access Complete Ratio, from Network Perspective(cont.)





Table 19. RRC Setup and Access Complete Ratio

KPI name RRC Setup and Access Complete Ratio

KPI abbreviation RRC stp and acc CR

KPI ID RNC_154d

KPI version 6.5u

Description RRC Setup and Access Complete Ratio [%] over thereporting period. Covers RRC Setup and Access phases(From RRC Connection Request to RRC Connection SetupComplete). Note1: RRC connection is needed also for otherpurposes than a call (SMS, LU, Detach, etc.).

Note -


KPI formula 100* sum([M1001C8] + [M1001C260]) / sum([M1001C0] -[M1001C242] - [M1001C241] + [M1001C259] -[M1001C617])

KPI formula with short names 100* sum([RRC_CONN_ACC_COMP] +[RRC_CON_SETUP_COMP_DIRECTED]) / sum([RRC_CONN_STP_ATT] -[RRC_CONN_SETUP_ATT_REPEAT] -[RRC_CONN_ACC_REL_CELL_RESEL] +[RRC_CONN_SETUP_COMP_AFT_DIR] -[RRC_CONN_STP_REJ_EMERG_CALL])


Unit Percentage







30/04/2009


Table 20. Registration Success

KPI name Registration Success

KPI abbreviation Regist succ

KPI ID RNC_219a

KPI version 2.1u

Description Success rate of Registrations

Note Registration means either network entry, change of locationarea or periodical location update.


KPI formula 100* sum([M1001C46]- [M1001C47]) / sum([M1001C46])

KPI formula with short names 100* sum([REGISTRATION_ATTS]-[REGISTRATION_FAILS]) / sum([REGISTRATION_ATTS])


Unit Percentage

Target values OPEN





5.1.1.5 RAB Setup and Access Complete Ratio [%]

Table 21. RAB Setup and Access Complete Ratio for Voice

KPI name RAB Setup and Access Complete Ratio for Voice

KPI abbreviation RAB stp and acc CR Voice

KPI ID RNC_30a

KPI version 6.5u

Description RAB Setup and Access Complete Ratio [%] for voice callsover the reporting period. Covers RAB Setup and Accessphases (From RAB Assignment Request to Radio BearerSetup Complete).

Note RRC connection is needed before RAB setup in order tomake a call.


KPI formula 100* sum([M1001C115]) / sum([M1001C66])

DN05191189Issue 4-3 en draft30/04/2009



Table 21. RAB Setup and Access Complete Ratio for Voice (cont.)

KPI formula with short names 100* sum([RAB_ACC_COMP_CS_VOICE]) / sum([RAB_STP_ATT_CS_VOICE])


Unit Percentage






Table 22. RAB Setup and Access Complete Ratio for UDI

KPI name RAB Setup and Access Complete Ratio for UDI

KPI abbreviation RAB stp&acc CR UDI

KPI ID RNC_31a

KPI version 1.1u

Description RAB Setup and Access Complete Ratio for CS video calls i.e. UDI.

Note UDI basically means video calls.


KPI formula 100*sum([M1001C116]) / sum([M1001C67])

KPI formula with short names 100*sum([RAB_ACC_COMP_CS_CONV]) / sum([RAB_STP_ATT_CS_CONV])


Unit Percentage







30/04/2009


Table 23. RAB Setup and Access Complete Ratio for Streaming

KPI name RAB Setup and Access Complete Ratio for Streaming

KPI abbreviation RAB stp&acc CR for Stream

KPI ID RNC_618a

KPI version 1.1u

Description RAB Setup Access success ratio for Streaming calls.


KPI formula 100*sum([M1001C119] + [M1001C117]) / sum([M1001C70]+ [M1001C68])

KPI formula with short names 100*sum([RAB_ACC_COMP_PS_STREA] +[RAB_ACC_COMP_CS_STREA]) / sum([RAB_STP_ATT_PS_STREA] +[RAB_STP_ATT_CS_STREA])


Unit Percentage






Table 24. RAB Setup and Access Complete Ratio for NRT Service

KPI name RAB Setup and Access Complete Ratio for NRT Service

KPI abbreviation RAB stp&acc CR NRT srv

KPI ID RNC_157a

KPI version 6.5u

Description RAB Setup and Access Complete Ratio [%] for NRTservices over the reporting period. Covers RAB Setup andAccess phases (From RAB Assignment Request to RadioBearer Setup Complete).

Note 1 RRC connection is needed before RAB setup in order tomake a call.


KPI formula 100* sum([M1001C120] + [M1001C121]) / sum([M1001C71]+ [M1001C72])


DN05191189Issue 4-3 en draft30/04/2009



Table 24. RAB Setup and Access Complete Ratio for NRT Service (cont.)

100* sum([RAB_ACC_COMP_PS_INTER] +[RAB_ACC_COMP_PS_BACKG]) / sum([RAB_STP_ATT_PS_INTER] +[RAB_STP_ATT_PS_BACKG])


Unit Percentage






5.1.1.6 RAB Setup and Access Complete Ratio, Multi-RAB Services [%]

All Multi RAB services

Table 25. Multi RAB setup and access Success Ratio

KPI name Multi RAB setup and access Success Ratio

KPI abbreviation M-RAB stp and acc SR

KPI ID RNC_741a

KPI version 1.1u

Description Multi RAB setup and success rate. This includes all thedifferent multi RAB types. Covers RAB Setup and Accessphases (From RAB Assignment Request to Radio BearerSetup Complete).

Note 1 RRC connection is needed before RAB setup in order tomake a call.


KPI formula 100 * sum( [M1001C287] + [M1001C288] + [M1001C289] +[M1001C290] + [M1001C291] + [M1001C292] +[M1001C299] + [M1001C300] + [M1001C301] +[M1001C302] + [M1001C303] + [M1001C304] +[M1001C319] + [M1001C320] + [M1001C321] +[M1001C322] + [M1001C323] + [M1001C324] +[M1001C308] + [M1001C309] + [M1001C310] +[M1001C312] )/sum( [M1001C281] + [M1001C282] +[M1001C283] + [M1001C284] + [M1001C285] +[M1001C286] + [M1001C293] + [M1001C294] +[M1001C295] + [M1001C296] + [M1001C297] +


30/04/2009


Table 25. Multi RAB setup and access Success Ratio (cont.)

[M1001C298] + [M1001C313] + [M1001C314] +[M1001C315] + [M1001C316] + [M1001C317] +[M1001C318] + [M1001C305] + [M1001C306] +[M1001C307] + [M1001C311] )

KPI formula with short names 100 * sum( [RAB_ACCC_CS12_2_1PSNRT64_64] +[RAB_ACCC_CS12_2_1PSNRT64_128] +[RAB_ACCC_CS12_2_2PSNRT_I_I] +[RAB_ACCC_CS12_2_2PSNRT_I_B] +[RAB_ACCC_CS12_2_2PSNRT_B_B] +[RAB_ACCC_CS12_2_3PSNRT] +[RAB_ACCC_CS_AMM_1PSNRT64_64] +[RAB_ACCC_CS_AMM_1PSNRT64_128] +[RAB_ACCC_CS_AMM_2PSNRT_I_I] +[RAB_ACCC_CS_AMM_2PSNRT_I_B] +[RAB_ACCC_CS_AMM_2PSNRT_B_B] +[RAB_ACCC_CS_AMM_3PSNRT] +[RAB_ACC_PSS_GEM_1PSNRT64_64] +[RAB_ACC_PSS_GEM_1PSNRT64_128] +[RAB_ACC_PSS_GEM_1PSNRT64_384] +[RAB_ACC_PSS_GLM_1PSNRT64_64] +[RAB_ACC_PSS_GLM_1PSNRT64_128] +[RAB_ACC_PSS_GLM_1PSNRT64_384] +[RAB_ACC_COMPL_2PSNRT_I_I] +[RAB_ACC_COMPL_2PSNRT_I_B] +[RAB_ACC_COMPL_2PSNRT_B_B] +[RAB_ACC_COMPL_3PSNRT] ) /sum([RAB_S_A_CS_12_2_1PSNRT64_64] +[RAB_S_A_CS_12_2_1PSNRT64_128] +[RAB_S_A_CS_12_2_2PSNRT_I_I] +[RAB_S_A_CS_12_2_2PSNRT_I_B] +[RAB_S_A_CS_12_2_2PSNRT_B_B] +[RAB_S_A_CS_12_2_3PSNRT] +[RAB_S_A_CS_AMM_1PSNRT64_64] +[RAB_S_A_CS_AMM_1PSNRT64_128] +[RAB_S_A_CS_AMM_2PSNRT_I_I] +[RAB_S_A_CS_AMM_2PSNRT_I_B] +[RAB_S_A_CS_AMM_2PSNRT_B_B] +[RAB_S_A_CS_AMM_3PSNRT] +[RAB_S_A_PSS_GEM_1PSNRT64_64] +[RAB_S_A_PSS_GEM_1PSNRT64_128] +[RAB_S_A_PSS_GEM_1PSNRT64_384] +[RAB_S_A_PSS_GLM_1PSNRT64_64] +[RAB_S_A_PSS_GLM_1PSNRT64_128] +[RAB_S_A_PSS_GLM_1PSNRT64_384] +[RAB_SETUP_ATT_2PSNRT_I_I] +[RAB_SETUP_ATT_2PSNRT_I_B] +[RAB_SETUP_ATT_2PSNRT_B_B] +[RAB_SETUP_ATT_3PSNRT] )


Unit Percentage

Target values OPEN

DN05191189Issue 4-3 en draft30/04/2009



Table 25. Multi RAB setup and access Success Ratio (cont.)





5.1.1.7 Serving Radio Network Subsystem Accessibility Ratio [%]

Table 26. Relocation Success in Target RNC for CS

KPI name Relocation Success in Target RNC for CS

KPI abbreviation Reloc succ trg RNC for CS

KPI ID RNC_5008a

KPI version 1.2u

Description The Relocation success inside RAN in Target RNCincluding both "UE not involved" (SRNC Relocation) and"UE involved" (Inter HHO) cases. The viewpoint is CS andtherefore MSC cases are counted.

Note 1 The incoming CS based relocation cancellations by CN areconsidered as a failed CS relocation in this formula.

Measurement M1009: L3 Relocation

KPI formula 100 * sum([M1009C77] + [M1009C193]) / sum([M1009C26]+ [M1009C142])

KPI formula with short names 100 * sum([SRNS_RELOC_COMPL_RNC_MSC] +[INTER_HHO_COMPL_IN_RNC_MSC]) / sum([SRNS_RELOC_IN_REQ_CONTR_MSC] +[INTER_RNC_HHO_IN_REQ_MSC])


Unit Percentage

Target values -






30/04/2009


Table 27. Relocation Success in Target RNC for PS

KPI name Relocation Success in Target RNC for PS

KPI abbreviation Reloc succ trg RNC for PS

KPI ID RNC_5009a

KPI version 1.2u

Description The Relocation success inside RAN including both "UE notinvolved" (SRNC Relocation) and "UE involved" (Inter HHO)cases. The viewpoint is PS and therefore SGSN cases arecounted.

Note 1 The incoming PS based relocation cancellations by CN areconsidered as a failed PS relocation in this formula.


KPI formula 100* sum([M1009C78] + [M1009C194]) / sum([M1009C27]+[M1009C143])

KPI formula with short names 100* sum([SRNS_RELOC_COMPL_RNC_SGSN] +[INTER_HHO_COMPL_IN_RNC_SGSN]) / sum([SRNS_RELOC_IN_REQ_CONTR_SGSN]+[INTER_RNC_HHO_REQ_SGSN])


Unit Percentage

Target values -





Table 28. Incoming Inter System HHO Success in Target RNC for CS

KPI name Incoming Inter System HHO Success in Target RNC for CS

KPI abbreviation Inc ISHHO succ trgtRNC CS

KPI ID RNC_5004a

KPI version 1.1u

Description The Incoming Inter System HHO success for CS core.

Note 1 The incoming CS ISHO cancellations by CN are consideredas a failed CS ISHO in this formula.



DN05191189Issue 4-3 en draft30/04/2009



Table 28. Incoming Inter System HHO Success in Target RNC for CS (cont.)

KPI formula with short names 100* sum([IS_COMPL_TARGET_RNC]) / sum([IS_HHO_IN_PREP_REQ])


Unit Percentage

Target values -





Table 29. Incoming Inter System Hard Handover Success Rate in Target RNCfor PS

KPI name Incoming Inter System Hard Handover Success Rate inTarget RNC for PS

KPI abbreviation Inc ISHHO succ trgtRNC PS

KPI ID RNC_5030a

KPI version 1.0u

Description The Incoming Inter System Hard Handover success rate forPS domain.


KPI formula 100 - 100* (sum([M1001C45]) / sum([M1001C44] -[M1001C584] - [M1001C564]))

KPI formula with short names 100 - 100* (sum([CELL_CHNG_ORD_FAILS]) / sum([CELL_CHNG_ORD_ATTS] -[RRC_ATT_REP_INTER_RAT_CCO] -[RRC_ACC_REL_INTER_RAT_CCO]))


Unit Percentage

Target values -






30/04/2009


5.1.2 Access network level indicators for retainability



5.1.2.1 Call Success Ratio (CSR) [%]

AMR Call Success Ratio (CSR) is the same as RNC_231c. See RABSuccess Ratio.

UDI Call Success Ratio (CSR) is the same as RNC_232c. See RABSuccess Ratio.

Streaming Call Success Ratio (CSR) is the same as RNC_619a. See RABSuccess Ratio.

Packet Service Success Ratio (CSR) is the same as RNC_736a. See RABSuccess Ratio.

Multi Service Success Ratio (CSR) is the same as RNC_742a. See RABSuccess Ratio.

5.1.2.2 RRC Success Ratio [%]

Note

The normal release counter in the formula includes also the caseswhen CN has released the RRC connection with cause ‘unspecified’.

Table 30. RRC Success Ratio

KPI name RRC Success Ratio

KPI abbreviation RRC SR

KPI ID RNC_217e

KPI version 6.5u

Description RRC Success Ratio [%] over the reporting period. CoversRRC Active Phase of a call.

Note

DN05191189Issue 4-3 en draft30/04/2009



Table 30. RRC Success Ratio (cont.)

The normal release counter in the formula includes also thecases when CN has released the RRC connection withcause 'unspecified'.


KPI formula 100-100* sum([M1001C14] + [M1001C15] + [M1001C16] +[M1001C17] + [M1001C18] + [M1001C21] + [M1001C391]) /sum([M1001C12] + [M1001C13] + [M1001C643] +[M1001C800] + [M1001C642] + [M1001C803] +[M1001C14] + [M1001C15] + [M1001C16] + [M1001C17] +[M1001C18] + [M1001C21] + [M1001C391])

KPI formula with short names 100-100* sum([RRC_CONN_ACT_REL_P_EMP] +[RRC_CONN_ACT_FAIL_IU] +[RRC_CONN_ACT_FAIL_RADIO] +[RRC_CONN_ACT_FAIL_BTS] +[RRC_CONN_ACT_FAIL_IUR] +[RRC_CONN_ACT_FAIL_RNC] +[RRC_CONN_ACT_FAIL_UE]) / sum([RRC_CONN_ACT_COMP] +[RRC_CONN_ACT_REL_SRNC] +[RRC_CONN_ACT_REL_GANHO] +[RRC_CONN_ACT_REL_HHO] +[RRC_CONN_ACT_REL_INTRA_HHO] +[RRC_CONN_ACT_REL_ISHO] +[RRC_CONN_ACT_REL_P_EMP] +[RRC_CONN_ACT_FAIL_IU] +[RRC_CONN_ACT_FAIL_RADIO] +[RRC_CONN_ACT_FAIL_BTS] +[RRC_CONN_ACT_FAIL_IUR] +[RRC_CONN_ACT_FAIL_RNC] +[RRC_CONN_ACT_FAIL_UE])

KPI class Retainability

Unit Percentage






5.1.2.3 RAB Success Ratio [%]

Table 31. RAB Success Ratio, Voice (CSR)

KPI name RAB Success Ratio, Voice (CSR)


30/04/2009


Table 31. RAB Success Ratio, Voice (CSR) (cont.)

KPI abbreviation RAB SR Voice

KPI ID RNC_231c

KPI version 6.5u

Description RAB Success Ratio for AMR Voice [%] over the reportingperiod. Covers RAB Active Phase of a call. This is takinginto notice just calls which has ended this cell, but mighthave been started in other cells.


KPI formula 100-100* sum([M1001C144] + [M1001C145] + [M1001C146]+ [M1001C147] + [M1001C148] + [M1001C150] +[M1001C392]) / sum([M1001C136] + [M1001C143] +[M1001C144] + [M1001C145] + [M1001C146] +[M1001C147] + [M1001C148] + [M1001C150] +[M1001C392])

KPI formula with short names 100-100* sum([RAB_ACT_REL_CS_VOICE_P_EMP] +[RAB_ACT_FAIL_CS_VOICE_IU] +[RAB_ACT_FAIL_CS_VOICE_RADIO] +[RAB_ACT_FAIL_CS_VOICE_BTS] +[RAB_ACT_FAIL_CS_VOICE_IUR] +[RAB_ACT_FAIL_CS_VOICE_RNC] +[RAB_ACT_FAIL_CS_VOICE_UE]) / sum([RAB_ACT_COMP_CS_VOICE] +[RAB_ACT_REL_CS_VOICE_SRNC] +[RAB_ACT_REL_CS_VOICE_P_EMP] +[RAB_ACT_FAIL_CS_VOICE_IU] +[RAB_ACT_FAIL_CS_VOICE_RADIO] +[RAB_ACT_FAIL_CS_VOICE_BTS] +[RAB_ACT_FAIL_CS_VOICE_IUR] +[RAB_ACT_FAIL_CS_VOICE_RNC] +[RAB_ACT_FAIL_CS_VOICE_UE])


Unit Percentage






Table 32. RAB Success ratio, UDI (CSR)

KPI name RAB Success ratio, UDI (CSR)

DN05191189Issue 4-3 en draft30/04/2009



Table 32. RAB Success ratio, UDI (CSR) (cont.)

KPI abbreviation RAB SR UDI

KPI ID RNC_232c

KPI version 1.1u

Description Complement of RAB drop ratio.

Note 1 UDI basically means video calls.

Note 2 The formula is taking into notice just calls which has endedthis cell, but might have been started in other cells.


KPI formula 100-100* sum([M1001C155] + [M1001C156] + [M1001C157]+ [M1001C160] + [M1001C158] + [M1001C159] +[M1001C393] + [M1001C152]) / sum([M1001C137] +[M1001C151] + [M1001C152] + [M1001C155] +[M1001C156] + [M1001C157] + [M1001C160] +[M1001C158] + [M1001C159] + [M1001C393])

KPI formula with short names 100-100* ([RAB_ACT_FAIL_CS_CONV_IU] +[RAB_ACT_FAIL_CS_CONV_RADIO] +[RAB_ACT_FAIL_CS_CONV_BTS] +[RAB_ACT_FAIL_CS_CONV_RNC] +[RAB_ACT_FAIL_CS_CONV_IUR] +[RAB_ACT_FAIL_CS_CONV_I_CHK] +[RAB_ACT_FAIL_CS_CONV_UE] +[RAB_ACT_REL_CS_CONV_P_EMP]) /([RAB_ACT_COMP_CS_CONV] +[RAB_ACT_REL_CS_CONV_SRNC] +[RAB_ACT_REL_CS_CONV_P_EMP] +[RAB_ACT_FAIL_CS_CONV_IU] +[RAB_ACT_FAIL_CS_CONV_RADIO] +[RAB_ACT_FAIL_CS_CONV_BTS] +[RAB_ACT_FAIL_CS_CONV_RNC] +[RAB_ACT_FAIL_CS_CONV_IUR] +[RAB_ACT_FAIL_CS_CONV_I_CHK] +[RAB_ACT_FAIL_CS_CONV_UE])


Unit Percentage

Target values > 99%






30/04/2009


Table 33. RAB Success Ratio, Streaming (CSR)

KPI name RAB Success Ratio, Streaming (CSR)

KPI abbreviation RAB SR Streaming

KPI ID RNC_619a

KPI version 1.1u

Description RAB Success Ratio for Streaming Services from userperspective over the reporting period. Covers RAB ActivePhase of a call.

Note The formula is taking into notice just calls which has endedthis cell, but might have been started in other cells.


KPI formula 100-100* sum([M1001C154] + [M1001C170] + [M1001C161]+ [M1001C162] + [M1001C163] + [M1001C164] +[M1001C166] + [M1001C179] + [M1001C180] +[M1001C181] + [M1001C182] + [M1001C184] +[M1001C394] + [M1001C396]) / sum([M1001C138] +[M1001C140] + [M1001C154] + [M1001C153] +[M1001C170] + [M1001C169] + [M1001C161] +[M1001C162] + [M1001C163] + [M1001C164] +[M1001C166] + [M1001C179] + [M1001C180] +[M1001C181] + [M1001C182] + [M1001C184] +[M1001C394] + [M1001C396])

KPI formula with short names 100-100* sum([RAB_ACT_REL_CS_STREA_P_EMP] +[RAB_ACT_REL_PS_STREA_P_EMP] +[RAB_ACT_FAIL_CS_STREA_IU] +[RAB_ACT_FAIL_CS_STREA_RADIO] +[RAB_ACT_FAIL_CS_STREA_BTS] +[RAB_ACT_FAIL_CS_STREA_IUR] +[RAB_ACT_FAIL_CS_STREA_RNC] +[RAB_ACT_FAIL_PS_STREA_IU] +[RAB_ACT_FAIL_PS_STREA_RADIO] +[RAB_ACT_FAIL_PS_STREA_BTS] +[RAB_ACT_FAIL_PS_STREA_IUR] +[RAB_ACT_FAIL_PS_STREA_RNC] +[RAB_ACT_FAIL_CS_STREA_UE] +[RAB_ACT_FAIL_PS_STREA_UE]) / sum([RAB_ACT_COMP_CS_STREA] +[RAB_ACT_COMP_PS_STREA] +[RAB_ACT_REL_CS_STREA_P_EMP] +[RAB_ACT_REL_CS_STREA_SRNC] +[RAB_ACT_REL_PS_STREA_P_EMP] +[RAB_ACT_REL_PS_STREA_SRNC] +[RAB_ACT_FAIL_CS_STREA_IU] +[RAB_ACT_FAIL_CS_STREA_RADIO] +[RAB_ACT_FAIL_CS_STREA_BTS] +[RAB_ACT_FAIL_CS_STREA_IUR] +[RAB_ACT_FAIL_CS_STREA_RNC] +[RAB_ACT_FAIL_PS_STREA_IU] +[RAB_ACT_FAIL_PS_STREA_RADIO] +

DN05191189Issue 4-3 en draft30/04/2009



Table 33. RAB Success Ratio, Streaming (CSR) (cont.)

[RAB_ACT_FAIL_PS_STREA_BTS] +[RAB_ACT_FAIL_PS_STREA_IUR] +[RAB_ACT_FAIL_PS_STREA_RNC] +[RAB_ACT_FAIL_CS_STREA_UE] +[RAB_ACT_FAIL_PS_STREA_UE])


Unit Percentage

Target values > 99%





Table 34. RAB Success Ratio, NRT Services, from Network Perspective

KPI name RAB Success Ratio, NRT Services, from NetworkPerspective

KPI abbreviation RAB SR NRT serv NW

KPI ID RNC_615b

KPI version 6.3u

Description RAB Success Ratio for NRT Services [%] over the reportingperiod. Covers RAB Active Phase of a call.

Note For NRT RABs pre-emption is not possible.


KPI formula 100-100* sum([M1001C185] + [M1001C186] +[M1001C187] + [M1001C188] + [M1001C190] +[M1001C191] + [M1001C192] + [M1001C193] +[M1001C194] + [M1001C196] + [M1001C398] +[M1001C397]) / sum([M1001C141] + [M1001C142]) +[M1001C171] + [M1001C172] + [M1001C185] +[M1001C186] + [M1001C187] + [M1001C188] +[M1001C190] + [M1001C191] + [M1001C192] +[M1001C193] + [M1001C194] + [M1001C196] +[M1001C398] + [M1001C397])

KPI formula with short names 100-100* sum([RAB_ACT_FAIL_PS_INTER_IU] +[RAB_ACT_FAIL_PS_INTER_RADIO] +[RAB_ACT_FAIL_PS_INTER_BTS] +[RAB_ACT_FAIL_PS_INTER_IUR] +[RAB_ACT_FAIL_PS_INTER_RNC] +[RAB_ACT_FAIL_PS_BACKG_IU] +


30/04/2009


Table 34. RAB Success Ratio, NRT Services, from Network Perspective(cont.)

[RAB_ACT_FAIL_PS_BACKG_RADIO] +[RAB_ACT_FAIL_PS_BACKG_BTS] +[RAB_ACT_FAIL_PS_BACKG_IUR] +[RAB_ACT_FAIL_PS_BACKG_RNC] +[RAB_ACT_FAIL_PS_BACKG_UE] +[RAB_ACT_FAIL_PS_INTER_UE]) / sum([RAB_ACT_COMP_PS_INTER] +[RAB_ACT_COMP_PS_BACKG]) +[RAB_ACT_REL_PS_INTER_SRNC] +[RAB_ACT_REL_PS_BACKG_SRNC] +[RAB_ACT_FAIL_PS_INTER_IU] +[RAB_ACT_FAIL_PS_INTER_RADIO] +[RAB_ACT_FAIL_PS_INTER_BTS] +[RAB_ACT_FAIL_PS_INTER_IUR] +[RAB_ACT_FAIL_PS_INTER_RNC] +[RAB_ACT_FAIL_PS_BACKG_IU] +[RAB_ACT_FAIL_PS_BACKG_RADIO] +[RAB_ACT_FAIL_PS_BACKG_BTS] +[RAB_ACT_FAIL_PS_BACKG_IUR] +[RAB_ACT_FAIL_PS_BACKG_RNC] +[RAB_ACT_FAIL_PS_BACKG_UE] +[RAB_ACT_FAIL_PS_INTER_UE])


Unit Percentage

Target values > 95-99 % (depends on inactivity timer settings, usually 98% is achieved)





Table 35. RAB Success Ratio, NRT Services

KPI name RAB Success Ratio, NRT Services

KPI abbreviation RAB SR NRT Services

KPI ID RNC_736a

KPI version 3.4u

Description RAB Success Ratio for NRT Services [%] from userperspective over the reporting period. Covers RAB ActivePhase of a call.

Note 1 For NRT RABs pre-emption is not possible.

DN05191189Issue 4-3 en draft30/04/2009



Table 35. RAB Success Ratio, NRT Services (cont.)

Note 2 As the formula is based on active fail counters it means inthis case that when RAB drops in CELL_PCH state that twofail counters are updated. This is taken into account in theformula (the drops in CELL_PCH subtracted from all drops.


KPI formula 100-100* sum([M1001C185] + [M1001C186] + [M1001C187]+ [M1001C188] + [M1001C190] + [M1001C191] +[M1001C192] + [M1001C193] + [M1001C194] +[M1001C196] + [M1001C398] + [M1001C397] -[M1001C594] - [M1001C593]) / sum([M1001C141] +[M1001C142] + [M1001C171] + [M1001C172] +[M1001C185] + [M1001C186] + [M1001C187] +[M1001C188] + [M1001C190] + [M1001C191] +[M1001C192] + [M1001C193] + [M1001C194] +[M1001C196] + [M1001C398] + [M1001C397])

KPI formula with short names 100-100* sum([RAB_ACT_FAIL_PS_INTER_IU] +[RAB_ACT_FAIL_PS_INTER_RADIO] +[RAB_ACT_FAIL_PS_INTER_BTS] +[RAB_ACT_FAIL_PS_INTER_IUR] +[RAB_ACT_FAIL_PS_INTER_RNC] +[RAB_ACT_FAIL_PS_BACKG_IU] +[RAB_ACT_FAIL_PS_BACKG_RADIO] +[RAB_ACT_FAIL_PS_BACKG_BTS] +[RAB_ACT_FAIL_PS_BACKG_IUR] +[RAB_ACT_FAIL_PS_BACKG_RNC] +[RAB_ACT_FAIL_PS_BACKG_UE] +[RAB_ACT_FAIL_PS_INTER_UE] -[RAB_ACT_FAIL_PS_BACKG_PCH] -[RAB_ACT_FAIL_PS_INT_PCH]) / sum([RAB_ACT_COMP_PS_INTER] +[RAB_ACT_COMP_PS_BACKG] +[RAB_ACT_REL_PS_INTER_SRNC] +[RAB_ACT_REL_PS_BACKG_SRNC] +[RAB_ACT_FAIL_PS_INTER_IU] +[RAB_ACT_FAIL_PS_INTER_RADIO] +[RAB_ACT_FAIL_PS_INTER_BTS] +[RAB_ACT_FAIL_PS_INTER_IUR] +[RAB_ACT_FAIL_PS_INTER_RNC] +[RAB_ACT_FAIL_PS_BACKG_IU] +[RAB_ACT_FAIL_PS_BACKG_RADIO] +[RAB_ACT_FAIL_PS_BACKG_BTS] +[RAB_ACT_FAIL_PS_BACKG_IUR] +[RAB_ACT_FAIL_PS_BACKG_RNC] +[RAB_ACT_FAIL_PS_BACKG_UE] +[RAB_ACT_FAIL_PS_INTER_UE])


Unit Percentage

Target values > 99%



30/04/2009


Table 35. RAB Success Ratio, NRT Services (cont.)




5.1.2.4 Packet Session Success Ratio (SSR) [%]

Table 36. Packet Session Success Ratio

KPI name Packet Session Success Ratio

KPI abbreviation Packet Session SR

KPI ID RNC_922b

KPI version 2.6u

Description The Packet Session Success Ratio for Streaming,Interactive and Background Services.

Note 1 For differences between Packet Service, Packet Sessionand Packet call, see RAN KPI Document. The pre-emptionsare not considered in formula.


KPI formula 100-100* sum([M1022C57] + [M1022C58] + [M1022C59] +[M1022C60] + [M1022C61] + [M1022C62] + [M1022C63] +[M1022C64] + [M1022C65] + [M1022C66] + [M1022C67] +[M1022C68] + [M1022C208] + [M1022C209] +[M1022C210] + [M1022C211] + [M1022C212] +[M1022C213]) / sum([M1022C57] + [M1022C58] +[M1022C59] + [M1022C60] + [M1022C61] + [M1022C62] +[M1022C63] + [M1022C64] + [M1022C65] + [M1022C66] +[M1022C67] + [M1022C68] + [M1022C45] + [M1022C46] +[M1022C47] + [M1022C48] + [M1022C49] + [M1022C50] +[M1022C208] + [M1022C209] + [M1022C210] +[M1022C211] + [M1022C212] + [M1022C213] +[M1022C202] + [M1022C203] + [M1022C204])

KPI formula with short names 100-100* sum([PS_REL_RL_FAIL_HS_E_INT] +[PS_REL_RL_FAIL_HS_E_BGR] +[PS_REL_RL_FAIL_HS_D_INT] +[PS_REL_RL_FAIL_HS_D_BGR] +[PS_REL_RL_FAIL_D_D_INT] +[PS_REL_RL_FAIL_D_D_BGR] +[PS_REL_OTH_FAIL_HS_E_INT] +[PS_REL_OTH_FAIL_HS_E_BGR] +[PS_REL_OTH_FAIL_HS_D_INT] +[PS_REL_OTH_FAIL_HS_D_BGR] +[PS_REL_OTH_FAIL_D_D_INT] +[PS_REL_OTH_FAIL_D_D_BGR] +

DN05191189Issue 4-3 en draft30/04/2009



Table 36. Packet Session Success Ratio (cont.)

[PS_REL_RL_FAIL_HS_E_STRE] +[PS_REL_RL_FAIL_HS_D_STRE] +[PS_REL_RL_FAIL_D_D_STRE] +[PS_REL_OTH_FAIL_HS_E_STRE] +[PS_REL_OTH_FAIL_HS_D_STRE] +[PS_REL_OTH_FAIL_D_D_STRE]) / sum([PS_REL_RL_FAIL_HS_E_INT] +[PS_REL_RL_FAIL_HS_E_BGR] +[PS_REL_RL_FAIL_HS_D_INT] +[PS_REL_RL_FAIL_HS_D_BGR] +[PS_REL_RL_FAIL_D_D_INT] +[PS_REL_RL_FAIL_D_D_BGR] +[PS_REL_OTH_FAIL_HS_E_INT] +[PS_REL_OTH_FAIL_HS_E_BGR] +[PS_REL_OTH_FAIL_HS_D_INT] +[PS_REL_OTH_FAIL_HS_D_BGR] +[PS_REL_OTH_FAIL_D_D_INT] +[PS_REL_OTH_FAIL_D_D_BGR] +[PS_REL_NORM_HS_E_INT] +[PS_REL_NORM_HS_E_BGR] +[PS_REL_NORM_HS_D_INT] +[PS_REL_NORM_HS_D_BGR] +[PS_REL_NORM_D_D_INT] +[PS_REL_NORM_D_D_BGR] +[PS_REL_RL_FAIL_HS_E_STRE] +[PS_REL_RL_FAIL_HS_D_STRE] +[PS_REL_RL_FAIL_D_D_STRE] +[PS_REL_OTH_FAIL_HS_E_STRE] +[PS_REL_OTH_FAIL_HS_D_STRE] +[PS_REL_OTH_FAIL_D_D_STRE] +[PS_REL_NORM_HS_E_STRE] +[PS_REL_NORM_HS_D_STRE] +[PS_REL_NORM_D_D_STRE])


Unit Percentage

Target values -






30/04/2009


5.1.2.5 RAB Success Ratio, Multi-RAB Services [%]

All Multi-RAB services

Table 37. Multi RAB Success Ratio

KPI name Multi RAB Success Ratio

KPI abbreviation Multi RAB SR

KPI ID RNC_742a

KPI version 1.1u

Description Multi RAB success rate. The KPI includes all the differentmulti RAB types, and covers RAB Active Phase of a call.


KPI formula 100 - 100 * ( sum( [M1001C503] + [M1001C504] +[M1001C505] + [M1001C506] + [M1001C507] +[M1001C508] + [M1001C509] + [M1001C510] +[M1001C511] + [M1001C512] + [M1001C513] +[M1001C514] + [M1001C515] + [M1001C516] +[M1001C517] + [M1001C518] + [M1001C519] +[M1001C520] + [M1001C521] + [M1001C522] +[M1001C523] + [M1001C524] + [M1001C525] +[M1001C526] + [M1001C527] + [M1001C528] +[M1001C529] ) / sum( [M1001C341] + [M1001C342] +[M1001C343] + [M1001C344] + [M1001C345] +[M1001C346] + [M1001C503] + [M1001C504] +[M1001C505] + [M1001C506] + [M1001C507] +[M1001C508] + [M1001C509] + [M1001C510] +[M1001C511] + [M1001C512] + [M1001C513] +[M1001C514] + [M1001C515] + [M1001C516] +[M1001C357] + [M1001C358] + [M1001C359] +[M1001C360] + [M1001C361] + [M1001C362] +[M1001C363] + [M1001C364] + [M1001C365] +[M1001C517] + [M1001C518] + [M1001C519] +[M1001C520] + [M1001C521] + [M1001C522] +[M1001C523] + [M1001C524] + [M1001C525] +[M1001C353] + [M1001C354] + [M1001C355] +[M1001C356] + [M1001C526] + [M1001C527] +[M1001C528] + [M1001C529] ) )

KPI formula with short names 100 - 100 * ( sum( [RAB_FAIL_AMR122_PSNRT6464] +[RAB_FAIL_AMR122_PSNRT64128] +[RAB_FAIL_AMR122_PSNRT64384] +[RAB_FAIL_AMR122_2PSNRTI] +[RAB_FAIL_AMR122_PSNRT_I_B] +[RAB_FAIL_AMR122_2PSNRTB] +[RAB_FAIL_AMR122_3PSNRT] +[RAB_FAIL_AMRMM_PSNRT6464] +[RAB_FAIL_AMRMM_PSNRT64128] +[RAB_FAIL_AMRMM_PSNRT64384] +[RAB_FAIL_AMRMM_2PSNRTI] +[RAB_FAIL_AMRMM_PSNRT_I_B] +

DN05191189Issue 4-3 en draft30/04/2009



Table 37. Multi RAB Success Ratio (cont.)

[RAB_FAIL_AMRMM_2PSNRTB] +[RAB_FAIL_AMRMM_3PSNRT] +[RAB_FAIL_CSCONV_PSNRT6464] +[RAB_FAIL_CSCONV_PSNRT64128] +[RAB_FAIL_CSCONV_PSNRT64384] +[RAB_FAIL_PSS_GEM_PSNRT6464] +[RAB_FAIL_PSS_GEM_PSNRT64128] +[RAB_FAIL_PSS_GEM_PSNRT64384] +[RAB_FAIL_PSS_GLM_PSNRT6464] +[RAB_FAIL_PSS_GLM_PSNRT64128] +[RAB_FAIL_PSS_GLM_PSNRT64384] +[RAB_ACT_FAIL_2PSNRTI] +[RAB_ACT_FAIL_PSNRT_I_B] +[RAB_ACT_FAIL_2PSNRTB] + [RAB_ACT_FAIL_3PSNRT]) / sum( [RAB_ACTC_CS12_2_1PSNRT64_64] +[RAB_ACTC_CS12_2_1PSNRT64_128] +[RAB_ACTC_CS12_2_2PSNRT_I_I] +[RAB_ACTC_CS12_2_2PSNRT_I_B] +[RAB_ACTC_CS12_2_2PSNRT_B_B] +[RAB_ACTC_CS12_2_3PSNRT] +[RAB_FAIL_AMR122_PSNRT6464] +[RAB_FAIL_AMR122_PSNRT64128] +[RAB_FAIL_AMR122_PSNRT64384] +[RAB_FAIL_AMR122_2PSNRTI] +[RAB_FAIL_AMR122_PSNRT_I_B] +[RAB_FAIL_AMR122_2PSNRTB] +[RAB_FAIL_AMR122_3PSNRT] +[RAB_FAIL_AMRMM_PSNRT6464] +[RAB_FAIL_AMRMM_PSNRT64128] +[RAB_FAIL_AMRMM_PSNRT64384] +[RAB_FAIL_AMRMM_2PSNRTI] +[RAB_FAIL_AMRMM_PSNRT_I_B] +[RAB_FAIL_AMRMM_2PSNRTB] +[RAB_FAIL_AMRMM_3PSNRT] +[RAB_ACT_PSS_GEM_1PSNRT64_64] +[RAB_ACT_PSS_GEM_1PSNRT64_128] +[RAB_ACT_PSS_GEM_1PSNRT64_384] +[RAB_ACT_PSS_GLM_1PSNRT64_64] +[RAB_ACT_PSS_GLM_1PSNRT64_128] +[RAB_ACT_PSS_GLM_1PSNRT64_384] +[RAB_ACT_CS_CONV_1PSNRT64_64] +[RAB_ACT_CS_CONV_1PSNRT64_128] +[RAB_ACT_CS_CONV_1PSNRT64_384] +[RAB_FAIL_CSCONV_PSNRT6464] +[RAB_FAIL_CSCONV_PSNRT64128] +[RAB_FAIL_CSCONV_PSNRT64384] +[RAB_FAIL_PSS_GEM_PSNRT6464] +[RAB_FAIL_PSS_GEM_PSNRT64128] +[RAB_FAIL_PSS_GEM_PSNRT64384] +[RAB_FAIL_PSS_GLM_PSNRT6464] +[RAB_FAIL_PSS_GLM_PSNRT64128] +[RAB_FAIL_PSS_GLM_PSNRT64384] +[RAB_ACT_COMPL_2PSNRT_I_I] +


30/04/2009


Table 37. Multi RAB Success Ratio (cont.)

[RAB_ACT_COMPL_2PSNRT_I_B] +[RAB_ACT_COMPL_2PSNRT_B_B] +[RAB_ACT_COMPL_3PSNRT] +[RAB_ACT_FAIL_2PSNRTI] +[RAB_ACT_FAIL_PSNRT_I_B] +[RAB_ACT_FAIL_2PSNRTB] + [RAB_ACT_FAIL_3PSNRT]) )


Unit Percentage

Target values OPEN





5.1.3 Access network level indicators for usage



5.1.3.1 CS service duration [minutes]

Table 38. Voice, Minutes

KPI name Voice, Minutes

KPI abbreviation Voice min

KPI ID RNC_745a

KPI version 2.2u

Description Voice minutes. The actual service usage, does not includeSHO overhead.

Note -


KPI formula sum ( [M1001C199] ) / 6000

DN05191189Issue 4-3 en draft30/04/2009



Table 38. Voice, Minutes (cont.)

KPI formula with short names sum ( [AVG_RAB_HLD_TM_CS_VOICE] ) / 6000

KPI class Usage/Duration

Unit min

Target values OPEN

Object Summary Levels Network; City; Area; RNC; WBTS; Cluster of cells; Cell




Table 39. UDI, Minutes

KPI name UDI, Minutes

KPI abbreviation UDI min

KPI ID RNC_746a

KPI version 2.1u

Description CS video calls minutes, i.e. UDI minutes. The actual serviceusage, does not include SHO overhead.


KPI formula sum ( [M1001C201] ) / 6000

KPI formula with short names sum ( [AVG_RAB_HLD_TM_CS_CONV] ) / 6000


Unit min

Target values OPEN





5.1.3.2 CS service duration before call drop [minutes]

Table 40. Minutes per Drop Voice

KPI name Minutes per Drop Voice


30/04/2009


Table 40. Minutes per Drop Voice (cont.)

KPI abbreviation Min per Drop Voice

KPI ID RNC_737a

KPI version 2.1u

Description The average minutes per drop for CS Voice. This is theuser perspective, so the pre-emptions and UE causes arealso counted in as failures.


KPI formula (sum( [M1001C199] ) /(100*60)) / sum( [M1001C144] +[M1001C145] + [M1001C146] + [M1001C147] +[M1001C148] + [M1001C150] + [M1001C392])

KPI formula with short names (sum( [AVG_RAB_HLD_TM_CS_VOICE] ) /(100*60)) / sum([RAB_ACT_REL_CS_VOICE_P_EMP] +[RAB_ACT_FAIL_CS_VOICE_IU] +[RAB_ACT_FAIL_CS_VOICE_RADIO] +[RAB_ACT_FAIL_CS_VOICE_BTS] +[RAB_ACT_FAIL_CS_VOICE_IUR] +[RAB_ACT_FAIL_CS_VOICE_RNC] +[RAB_ACT_FAIL_CS_VOICE_UE])


Unit Minutes/drop

Target values Depends on Traffic.





Table 41. Minutes per Drop UDI

KPI name Minutes per Drop UDI

KPI abbreviation Min per Drop UDI

KPI ID RNC_738a

KPI version 2.1u

Description The average minutes per drop for UDI. This is the userperspective, so the pre-emptions and UE causes are alsocounted in as failures.

Note 1 UDI basically means video calls.


DN05191189Issue 4-3 en draft30/04/2009



Table 41. Minutes per Drop UDI (cont.)

KPI formula (sum( [M1001C201] )/(100*60)) / sum( [M1001C152] +[M1001C155] + [M1001C156] + [M1001C157] +[M1001C158] + [M1001C160] + [M1001C393])

KPI formula with short names (sum( [AVG_RAB_HLD_TM_CS_CONV] )/(100*60)) / sum([RAB_ACT_REL_CS_CONV_P_EMP] +[RAB_ACT_FAIL_CS_CONV_IU] +[RAB_ACT_FAIL_CS_CONV_RADIO] +[RAB_ACT_FAIL_CS_CONV_BTS] +[RAB_ACT_FAIL_CS_CONV_IUR] +[RAB_ACT_FAIL_CS_CONV_RNC] +[RAB_ACT_FAIL_CS_CONV_UE])


Unit Minutes/drop

Target values OPEN





5.1.3.3 PS service volume before RAB drop [Mbit/ Dropped RAB]

Table 42. Iu-PS data volume per drop - ATM based

KPI name Iu-PS data volume per drop - ATM based

KPI abbreviation Iu-PS DV per drop ATMbase

KPI ID RNC_5050a

KPI version 1.0u

Description The average Volume per drop for Packet Switched Data.This is the user perspective, so the pre-emptions and UEcauses are also counted in as failures

Note 1 This KPI is valid only for RNCs using ATM based Iu-PSinterface either with NIS1 or NPS1 interface unit.

Note 2 ATM headers are included in the KPI.

Measurement M1001: Service Level M530: ATM VC

KPI formula (sum([M530C0] * 53 * 8 / 1 000 000) / sum([M1001C170] +[M1001C179]+ [M1001C180] + [M1001C181] +[M1001C182] + [M1001C184] + [M1001C185] +[M1001C186] + [M1001C187] + [M1001C188] +


30/04/2009


Table 42. Iu-PS data volume per drop - ATM based (cont.)

[M1001C190] + [M1001C191] + [M1001C192] +[M1001C193] + [M1001C194] + [M1001C196] +[M1001C398] + [M1001C397] - [M1001C594] -[M1001C593]))

KPI formula with short names (sum([IN_TOT_CELLS_VC] * 53 * 8 / 1 000 000) / sum([RAB_ACT_REL_PS_STREA_P_EMP] +[RAB_ACT_FAIL_PS_STREA_IU]+[RAB_ACT_FAIL_PS_STREA_RADIO] +[RAB_ACT_FAIL_PS_STREA_BTS] +[RAB_ACT_FAIL_PS_STREA_IUR] +[RAB_ACT_FAIL_PS_STREA_RNC] +[RAB_ACT_FAIL_PS_INTER_IU] +[RAB_ACT_FAIL_PS_INTER_RADIO] +[RAB_ACT_FAIL_PS_INTER_BTS] +[RAB_ACT_FAIL_PS_INTER_IUR] +[RAB_ACT_FAIL_PS_INTER_RNC] +[RAB_ACT_FAIL_PS_BACKG_IU] +[RAB_ACT_FAIL_PS_BACKG_RADIO] +[RAB_ACT_FAIL_PS_BACKG_BTS] +[RAB_ACT_FAIL_PS_BACKG_IUR] +[RAB_ACT_FAIL_PS_BACKG_RNC] +[RAB_ACT_FAIL_PS_BACKG_UE] +[RAB_ACT_FAIL_PS_INTER_UE] -[RAB_ACT_FAIL_PS_BACKG_PCH] -[RAB_ACT_FAIL_PS_INT_PCH]))


Unit Mbit / Dropped RAB

Target values -





Table 43. Iu-PS data volume per drop - IP based

KPI name Iu-PS data volume per drop - IP based

KPI abbreviation Iu-PS DV per drop IPbased

KPI ID RNC_5051a

KPI version 1.0u

Description The average Volume per drop for Packet Switched Data.This is the user perspective, so the pre-emptions and UEcauses are also counted in as failures

DN05191189Issue 4-3 en draft30/04/2009



Table 43. Iu-PS data volume per drop - IP based (cont.)

Note 1 This KPI is valid only for RNCs using NPGE unit in Iu-PSinterface.

Note 2 IP and UDP headers are included in KPI.

Measurement M1001: Service Level M568: IP Route

KPI formula (sum([M568C1] * 8 / 1000) / sum([M1001C170] +[M1001C179]+ [M1001C180] + [M1001C181] +[M1001C182] + [M1001C184] + [M1001C185] +[M1001C186] + [M1001C187] + [M1001C188] +[M1001C190] + [M1001C191] + [M1001C192] +[M1001C193] + [M1001C194] + [M1001C196] +[M1001C398] + [M1001C397] - [M1001C594] -[M1001C593]))

KPI formula with short names (sum([IN_DATA_IP_ROUTE] * 8 / 1000) / sum([RAB_ACT_REL_PS_STREA_P_EMP] +[RAB_ACT_FAIL_PS_STREA_IU]+[RAB_ACT_FAIL_PS_STREA_RADIO] +[RAB_ACT_FAIL_PS_STREA_BTS] +[RAB_ACT_FAIL_PS_STREA_IUR] +[RAB_ACT_FAIL_PS_STREA_RNC] +[RAB_ACT_FAIL_PS_INTER_IU] +[RAB_ACT_FAIL_PS_INTER_RADIO] +[RAB_ACT_FAIL_PS_INTER_BTS] +[RAB_ACT_FAIL_PS_INTER_IUR] +[RAB_ACT_FAIL_PS_INTER_RNC] +[RAB_ACT_FAIL_PS_BACKG_IU] +[RAB_ACT_FAIL_PS_BACKG_RADIO] +[RAB_ACT_FAIL_PS_BACKG_BTS] +[RAB_ACT_FAIL_PS_BACKG_IUR] +[RAB_ACT_FAIL_PS_BACKG_RNC] +[RAB_ACT_FAIL_PS_BACKG_UE] +[RAB_ACT_FAIL_PS_INTER_UE] -[RAB_ACT_FAIL_PS_BACKG_PCH] -[RAB_ACT_FAIL_PS_INT_PCH]))


Unit Mbit / Dropped RAB

Target values -






30/04/2009


5.1.3.4 Erlang [Erlang]

Table 44. Average CS Erlang

KPI name Average CS Erlang

KPI abbreviation Avg CS erl

KPI ID RNC_280b

KPI version 6.4u

Description CS Erlang meaning the CS RAB holding time.

Note 1 This KPI can be used to see the total Erlang volume in Iu-CS and compare the average value to defined performancevalue.

Note 2 In the formula all the CS holding time counters has beenweighed to correspond 1 AMR.

Note 3 This KPI is mainly meant for busy hour follow-up.


KPI formula sum([M1001C199] + [M1001C368] * 64/12.2 + [M1001C370]* 14.4/12.2 + [M1001C372] * 57.6/12.2) / sum(PERIOD_DURATION)*100*60

KPI formula with short names sum([AVG_RAB_HLD_TM_CS_VOICE] +[RAB_HOLD_TIME_CS_CONV_64] * 64/12.2 +[RAB_HOLD_TIME_CS_STREAM_14_4] * 14.4/12.2 +[RAB_HOLD_TIME_CS_STREAM_57_6] * 57.6/12.2) / sum(PERIOD_DURATION)*100*60

KPI class Usage/Throughput

Unit E

Target values Depends on Traffic.





5.1.4 Access network level indicators for mobility

The services and resources related to the KPIs are described in Radionetwork in the 3G system and UTRAN Resource Model overviewinWCDMA RAN System Overview.

DN05191189Issue 4-3 en draft30/04/2009




5.1.4.1 Intra System Hard Handover Success Ratio [%]

Table 45. Intra System Hard Handover Success Ratio

KPI name Intra System Hard Handover Success Ratio

KPI abbreviation Intra-Sys HHO SR

KPI ID RNC_168a

KPI version 6.4u

Description Intra System Hard Handover Success Ratio [%] for thereporting period in the Source Cell of the Hard Handover.

Measurement M1008: Intra System Handover

KPI formula 100* sum([M1008C6] + [M1008C15] + [M1008C55] +[M1008C59] + [M1008C63] + [M1008C103] + [M1008C107]+ [M1008C111]) / sum([M1008C4] + [M1008C5] +[M1008C13] + [M1008C14] + [M1008C54] + [M1008C58] +[M1008C62] + [M1008C102] + [M1008C106] +[M1008C110])

KPI formula with short names 100* sum([SUCC_HHO_CAUSED_SHO_INCAP_RT] +[SUCC_HHO_SHO_INCAP_NRT] +[SUCC_INTRA_INTRA_HHO_ATT_RT] +[SUCC_INTRA_INTER_HHO_ATT_RT] +[SUCC_INTER_HHO_ATT_RT] +[SUCC_INTRA_INTRA_HHO_ATT_NRT] +[SUCC_INTRA_INTER_HHO_ATT_NRT] +[SUCC_INTER_HHO_ATT_NRT]) / sum([HHO_ATT_CAUSED_SHO_INCAP_RT] +[IMMED_HHO_CSD_SHO_INCAP_RT] +[HHO_ATT_CAUSED_SHO_INCAP_NRT] +[IMMED_HHO_CSD_SHO_INCAP_NRT] +[INTRA_INTRA_HHO_ATT_RT] +[INTRA_INTER_HHO_ATT_RT] + [INTER_HHO_ATT_RT] +[INTRA_INTRA_HHO_ATT_NRT] +[INTRA_INTER_HHO_ATT_NRT] +[INTER_HHO_ATT_NRT])

KPI class Mobility

Unit Percentage







30/04/2009


5.1.4.2 Inter System Hard Handover Success Ratio [%]

Table 46. Inter System RT Hard Handover Success Ratio

KPI name Inter System RT Hard Handover Success Ratio

KPI abbreviation Inter sys RT Hard HO SR

KPI ID RNC_300f

KPI version 1.0u

Description Inter System Real Time User Hard Handover Success Ratio[%] for the reporting period in the Source Cell of the HardHandover.

Note 1 The Real Time and Non Real Time Inter System HO differsin nature. Therefore the ISHO KPI is splitted in RT and NRTparts.

Note 2 The Multi RAB ISHOs are only updated to RT counters.This because the NRT RB follows the RT parameters whenpart of RT + NRT Multi RAB.

Measurement M1010: Inter System Handover

KPI formula 100* sum([M1010C19]+ [M1010C23]+ [M1010C27]+[M1010C31]+ [M1010C35]+ [M1010C77] + [M1010C98] +[M1010C198]+ [M1010C197]+ [M1010C149] + [M1010C150]+ [M1010C152] + [M1010C151] + [M1010C153] +[M1010C186] + [M1010C220]) / sum([M1010C18]+[M1010C22]+ [M1010C26]+ [M1010C30]+ [M1010C34]+[M1010C76] + [M1010C97] + [M1010C196]+ [M1010C195]+[M1010C137] + [M1010C138] + [M1010C140] +[M1010C139] + [M1010C141] + [M1010C185]+[M1010C219])

KPI formula with short names 100* sum([SUCC_IS_HHO_UL_DCH_Q_RT]+[SUCC_IS_HHO_UE_TRX_PWR_RT]+[SUCC_IS_HHO_DL_DPCH_PWR_RT]+[SUCC_IS_HHO_CPICH_RSCP_RT]+[SUCC_IS_HHO_CPICH_ECNO_RT]+[SUCC_IS_HHO_IM_IMS_RT] +[SUCC_IS_HHO_EMERG_CALL] +[SUCC_IS_HHO_LB_CAPA_DL_RT]+[SUCC_IS_HHO_LB_CAPA_UL_RT]+[SUCC_IS_HHO_LB_PRX_TOT_RT] +[SUCC_IS_HHO_LB_PTX_TOT_RT] +[SUCC_IS_HHO_LB_RES_LIM_RT] +[SUCC_IS_HHO_LB_RSVR_SC_RT] +[SUCC_IS_HHO_SB_RT] + [SUCC_IS_HHO_WPS_RT] +[SUCC_GANHO_AMR_RT]) / sum([IS_HHO_ATT_UL_DCH_Q_RT]+[IS_HHO_ATT_UE_TRX_PWR_RT]+[IS_HHO_ATT_DPCH_PWR_RT]+[IS_HHO_ATT_CPICH_RSCP_RT]+[IS_HHO_ATT_CPICH_ECNO_RT]+[IS_HHO_ATT_IM_IMS_RT] +

DN05191189Issue 4-3 en draft30/04/2009



Table 46. Inter System RT Hard Handover Success Ratio (cont.)

[IS_HHO_ATT_EMERG_CALL] +[IS_HHO_ATT_LB_CAPA_DL_RT]+[IS_HHO_ATT_LB_CAPA_UL_RT]+[IS_HHO_ATT_LB_PRX_TOT_RT] +[IS_HHO_ATT_LB_PTX_TOT_RT] +[IS_HHO_ATT_LB_RES_LIM_RT] +[IS_HHO_ATT_LB_RSVR_SC_RT] +[IS_HHO_ATT_SB_RT] +[IS_HHO_ATT_UL_DCH_WPS_RT]+[ATT_GANHO_AMR_RT])

KPI class Mobility

Unit Percentage






Table 47. Inter System NRT Hard Handover Success Ratio

KPI name Inter System NRT Hard Handover Success Ratio

KPI abbreviation Inter sys NRT Hard HO SR

KPI ID RNC_301d

KPI version 3.4u

Description Inter System Non Real Time User Hard Handover SuccessRatio [%] for the reporting period in the Source Cell of theHard Handover.

Note 1 The Real Time and Non Real Time Inter System HO differsin nature. Therefore the ISHO KPI is splitted in RT and NRTparts.

Note 2 The Multi RAB ISHOs are only updated to RT counters.This because the NRT RB follows the RT parameters whenpart of RT + NRT Multi RAB.


KPI formula 100* sum([M1010C57]+ [M1010C61]+ [M1010C65]+[M1010C69]+ [M1010C73] + [M1010C84] + [M1010C157] +[M1010C156] + [M1010C154] + [M1010C155] +[M1010C159] + [M1010C158] + [M1010C160]) / sum


30/04/2009


Table 47. Inter System NRT Hard Handover Success Ratio (cont.)

([M1010C56]+ [M1010C60]+ [M1010C64]+ [M1010C68]+[M1010C72] + [M1010C83] + [M1010C145] + [M1010C144]+ [M1010C142] + [M1010C143] + [M1010C147] +[M1010C146] + [M1010C148])

KPI formula with short names 100* sum([SUCC_IS_HHO_UL_DCH_Q_NRT]+[SUCC_IS_HHO_UE_TRX_PWR_NRT]+[SUCC_IS_HHO_DL_DPCH_PWR_NRT]+[SUCC_IS_HHO_CPICH_RSCP_NRT]+[SUCC_IS_HHO_CPICH_ECNO_NRT] +[SUCC_IS_HHO_IM_IMS_NRT] +[SUCC_IS_HHO_LB_CAPA_DL_NRT] +[SUCC_IS_HHO_LB_CAPA_UL_NRT] +[SUCC_IS_HHO_LB_PRX_TOT_NRT] +[SUCC_IS_HHO_LB_PTX_TOT_NRT] +[SUCC_IS_HHO_LB_RES_LIM_NRT] +[SUCC_IS_HHO_LB_RSVR_SC_NRT] +[SUCC_IS_HHO_SB_NRT]) / sum([IS_HHO_ATT_UL_DCH_Q_NRT]+[IS_HHO_ATT_UE_TRX_PWR_NRT]+[IS_HHO_ATT_DL_DPCH_PWR_NRT]+[IS_HHO_ATT_CPICH_RSCP_NRT]+[IS_HHO_ATT_CPICH_ECNO_NRT] +[IS_HHO_ATT_IM_IMS_NRT] +[IS_HHO_ATT_LB_CAPA_DL_NRT] +[IS_HHO_ATT_LB_CAPA_UL_NRT] +[IS_HHO_ATT_LB_PRX_TOT_NRT] +[IS_HHO_ATT_LB_PTX_TOT_NRT] +[IS_HHO_ATT_LB_RES_LIM_NRT] +[IS_HHO_ATT_LB_RSVR_SC_NRT] +[IS_HHO_ATT_SB_NRT])

KPI class Mobility

Unit Percentage






5.1.4.3 Inter System Hard Handover Drop Ratio [%]

Table 48. Inter System HHO Drop Rate RT

KPI name ISHO Drop Rate RT

KPI abbreviation ISHO DR RT

DN05191189Issue 4-3 en draft30/04/2009



Table 48. Inter System HHO Drop Rate RT (cont.)

KPI ID RNC_302c

KPI version 2.1u

Description ISHO Drop Rate RT, contains real drops, not all failedISHOs.

Note Inter RNC RT ISHO attempt includes cases when UE hasalso any additional NRT service.


KPI formula 100* sum( [M1010C21] + [M1010C25] + [M1010C29] +[M1010C33] + [M1010C37] + [M1010C79] + [M1010C100] +[M1010C173] + [M1010C174] + [M1010C175] +[M1010C176] + [M1010C177] ) / sum( [M1010C18] +[M1010C22] + [M1010C26] + [M1010C30] + [M1010C34] +[M1010C76] + [M1010C97] + [M1010C137] + [M1010C138]+ [M1010C140] + [M1010C139] + [M1010C141] )

KPI formula with short names 100* sum( [CON_DRPS_IS_HHO_UL_DCH_Q_RT] +[CON_DRPS_IS_HHO_UE_PWR_RT] +[CON_DRPS_IS_HHO_DL_DPCH_RT] +[CON_DRPS_IS_HHO_RSCP_RT] +[CON_DRPS_IS_HHO_ECNO_RT] +[CON_DRPS_IS_HHO_IM_IMS_RT] +[CON_DRPS_IS_HHO_EMERG_CALL] +[CONDR_IS_HHO_LB_PRX_TOT_RT] +[CONDR_IS_HHO_LB_PTX_TOT_RT] +[CONDR_IS_HHO_LB_RSVR_SC_RT] +[CONDR_IS_HHO_LB_RES_LIM_RT] +[CONDR_IS_HHO_SB_RT] ) / sum([IS_HHO_ATT_UL_DCH_Q_RT] +[IS_HHO_ATT_UE_TRX_PWR_RT] +[IS_HHO_ATT_DPCH_PWR_RT] +[IS_HHO_ATT_CPICH_RSCP_RT] +[IS_HHO_ATT_CPICH_ECNO_RT] +[IS_HHO_ATT_IM_IMS_RT] +[IS_HHO_ATT_EMERG_CALL] +[IS_HHO_ATT_LB_PRX_TOT_RT] +[IS_HHO_ATT_LB_PTX_TOT_RT] +[IS_HHO_ATT_LB_RES_LIM_RT] +[IS_HHO_ATT_LB_RSVR_SC_RT] +[IS_HHO_ATT_SB_RT] )

KPI class Mobility

Unit Percentage

Target values OPEN






30/04/2009


Table 49. Inter System HHO Drop Rate NRT

KPI name ISHO Drop Rate NRT

KPI abbreviation ISHO DR NRT

KPI ID RNC_303c

KPI version 2.1u

Description ISHO Drop Rate NRT, contains real drops, not all failedISHOs.

Note Inter RNC NRT ISHO attempt excludes cases when UE hasalso any RT service.


KPI formula 100* sum( [M1010C57] + [M1010C61] + [M1010C65] +[M1010C69] + [M1010C73] + [M1010C84] + [M1010C157] +[M1010C156] + [M1010C154] + [M1010C155] +[M1010C159] + [M1010C158] + [M1010C160] ) / sum([M1010C56] + [M1010C60] + [M1010C64] + [M1010C68] +[M1010C72] + [M1010C83] + [M1010C145] + [M1010C144]+ [M1010C142] + [M1010C143] + [M1010C147] +[M1010C146] + [M1010C148] )

KPI formula with short names 100* sum( [SUCC_IS_HHO_UL_DCH_Q_NRT] +[SUCC_IS_HHO_UE_TRX_PWR_NRT] +[SUCC_IS_HHO_DL_DPCH_PWR_NRT] +[SUCC_IS_HHO_CPICH_RSCP_NRT] +[SUCC_IS_HHO_CPICH_ECNO_NRT] +[SUCC_IS_HHO_IM_IMS_NRT] +[SUCC_IS_HHO_LB_CAPA_DL_NRT] +[SUCC_IS_HHO_LB_CAPA_UL_NRT] +[SUCC_IS_HHO_LB_PRX_TOT_NRT] +[SUCC_IS_HHO_LB_PTX_TOT_NRT] +[SUCC_IS_HHO_LB_RES_LIM_NRT] +[SUCC_IS_HHO_LB_RSVR_SC_NRT] +[SUCC_IS_HHO_SB_NRT] ) / sum([IS_HHO_ATT_UL_DCH_Q_NRT] +[IS_HHO_ATT_UE_TRX_PWR_NRT] +[IS_HHO_ATT_DL_DPCH_PWR_NRT] +[IS_HHO_ATT_CPICH_RSCP_NRT] +[IS_HHO_ATT_CPICH_ECNO_NRT] +[IS_HHO_ATT_IM_IMS_NRT] +[IS_HHO_ATT_LB_CAPA_DL_NRT] +[IS_HHO_ATT_LB_CAPA_UL_NRT] +[IS_HHO_ATT_LB_PRX_TOT_NRT] +[IS_HHO_ATT_LB_PTX_TOT_NRT] +[IS_HHO_ATT_LB_RES_LIM_NRT] +[IS_HHO_ATT_LB_RSVR_SC_NRT] +[IS_HHO_ATT_SB_NRT] )

KPI class Mobility

DN05191189Issue 4-3 en draft30/04/2009



Table 49. Inter System HHO Drop Rate NRT (cont.)

Unit Percentage

Target values OPEN





5.2 RNC function level

5.2.1 RNC function level indicators for accessibility



5.2.1.1 Packet Session Setup Success Ratio (SSSR) [%]

Table 50. HSDPA Resource Accessibility for NRT Traffic

KPI name HSDPA Resource Accessibility for NRT Traffic

KPI abbreviation HSDPA res acc NRT traf

KPI ID RNC_605a

KPI version 4.5u

Description The accessibility of all started resource allocations for HS-DSCH for NRT Traffic. The number of times when HS-DSCH channel has been established divided by the numberof times when HS-DSCH channel has been selected by cellspecific PS.

Note The times that the DCH is selected due to high R99 poweris not included in the formula.

Measurement M1002: Traffic

KPI formula


30/04/2009


Table 50. HSDPA Resource Accessibility for NRT Traffic (cont.)

100* sum([M1002C385]+[M1002C389]) / sum([M1002C385]+ [M1002C389] + [M1002C401] + [M1002C402] +[M1002C413] + [M1002C416] + [M1002C417] +[M1002C421] + [M1002C424] + [M1002C425] +[M1002C415] + [M1002C423] + [M1002C475] +[M1002C476])

KPI formula with short names 100* sum([ALLO_HS_DSCH_FLOW_INT]+[ALLO_HS_DSCH_FLOW_BGR]) / sum([ALLO_HS_DSCH_FLOW_INT] +[ALLO_HS_DSCH_FLOW_BGR] +[REJ_HS_DSCH_RET_INT] + [REJ_HS_DSCH_RET_BGR]+ [SETUP_FAIL_RNC_HS_DSCH_INT] +[SETUP_FAIL_BTS_HS_DSCH_INT] +[SETUP_FAIL_IUB_HS_TOTAL_INT] +[SETUP_FAIL_RNC_HS_DSCH_BGR] +[SETUP_FAIL_BTS_HS_DSCH_BGR] +[SETUP_FAIL_IUB_HS_TOTAL_BGR] +[SETUP_FAIL_UE_HS_DSCH_INT] +[SETUP_FAIL_UE_HS_DSCH_BGR] +[DCH_SEL_MAX_HSDPA_USERS_INT] +[DCH_SEL_MAX_HSDPA_USERS_BGR])


Unit Percentage

Target values OPEN





Table 51. HSDPA Resource Accessibility for RT Traffic

KPI name HSDPA Resource Accessibility for RT Traffic

KPI abbreviation HSDPA res acc for RT traf

KPI ID RNC_5000a

KPI version 1.2u

Description The accessibility of all started resource allocations for HS-DSCH for RT Traffic. The number of times when HS-DSCHchannel has been established divided by the number oftimes when HS-DSCH channel has been selected by cellspecific PS.

Note The times that the DCH is selected due to high R99 poweris not included in the formula.

DN05191189Issue 4-3 en draft30/04/2009



Table 51. HSDPA Resource Accessibility for RT Traffic (cont.)


KPI formula 100 * sum([M1002C569]) / sum([M1002C569] +[M1002C591] + [M1002C577] + [M1002C581] +[M1002C584] + [M1002C585] + [M1002C602])

KPI formula with short names 100 * sum([ALLO_HS_DSCH_FLOW_STR]) / sum([ALLO_HS_DSCH_FLOW_STR] +[DCH_SEL_MAX_HSDPA_USERS_STR] +[REJ_HS_DSCH_RET_STR] +[SETUP_FAIL_RNC_HS_DSCH_STR] +[SETUP_FAIL_BTS_HS_DSCH_STR] +[SETUP_FAIL_IUB_HS_TOTAL_STR] +[DL_DCH_SEL_HSDPA_POWER_STR])


Unit Percentage

Target values See Targets for WCDMA RAN key performance indicators.





Table 52. HSDPA Setup Success Ratio

KPI name HSDPA Setup Success Ratio from user perspective

KPI abbreviation HSDPA stp SR Usr

KPI ID RNC_914c

KPI version 1.0u

Description HSDPA Setup Success Ratio [%] for Streaming, Interactiveand Background Services from user perspective over thereporting period.

Note The capacity requests by HSDPA capable UE to cells thatare not configured to support HSDPA are excluded byspecific counters in the formula.


KPI formula 100* sum([M1022C190] + [M1022C21] + [M1022C22] +[M1022C191] + [M1022C23] + [M1022C24] + [M1022C192]+ [M1022C25] + [M1022C26]) / sum([M1022C181] +[M1022C3] + [M1022C4] + [M1022C182] + [M1022C5] +[M1022C6] - [M1022C222] - [M1022C221] - [M1022C220] -[M1022C219] - [M1022C218] - [M1022C217])


30/04/2009


Table 52. HSDPA Setup Success Ratio (cont.)

KPI formula with short names 100* sum([HS_E_REQ_HS_E_ALLO_STRE] +[HS_E_REQ_HS_E_ALLO_INT] +[HS_E_REQ_HS_E_ALLO_BGR] +[HS_E_REQ_HS_D_ALLO_STRE] +[HS_E_REQ_HS_D_ALLO_INT] +[HS_E_REQ_HS_D_ALLO_BGR] +[HS_D_REQ_HS_D_ALLO_STRE] +[HS_D_REQ_HS_D_ALLO_INT] +[HS_D_REQ_HS_D_ALLO_BGR]) / sum([PS_ATT_HSDSCH_EDCH_STRE] +[PS_ATT_HSDSCH_EDCH_INT] +[PS_ATT_HSDSCH_EDCH_BGR] +[PS_ATT_HSDSCH_DCH_STRE] +[PS_ATT_HSDSCH_DCH_INT] +[PS_ATT_HSDSCH_DCH_BGR] -[HS_D_REQ_D_D_ALLO_STR_CELL] -[HS_D_REQ_D_D_ALLO_BGR_CELL] -[HS_D_REQ_D_D_ALLO_INT_CELL] -[HS_E_REQ_D_D_ALLO_STR_CELL] -[HS_E_REQ_D_D_ALLO_BGR_CELL] -[HS_E_REQ_D_D_ALLO_INT_CELL])


Unit Percentage

Target values OPEN





Table 53. HSUPA Resource Accessibility for NRT Traffic

KPI name HSUPA Resource Accessibility for NRT Traffic

KPI abbreviation HSUPA res acc NRT traf

KPI ID RNC_913a

KPI version 2.3u

Description The accessibility of all started resource allocations for E-DCH for NRT Traffic. The number of times when E-DCHchannel has been established divided by the number oftimes when HS-DSCH channel has been selected by cellspecific PS.

Note This KPI includes all reservations, also all SHO branchesincluded in HSUPA AS.

DN05191189Issue 4-3 en draft30/04/2009



Table 53. HSUPA Resource Accessibility for NRT Traffic (cont.)


KPI formula 100* sum([M1002C531] + [M1002C532]) / sum([M1002C531] + [M1002C532] + [M1002C520] +[M1002C519] + [M1002C516] + [M1002C515] +[M1002C517] + [M1002C518] + [M1002C526] +[M1002C525] + [M1002C530] + [M1002C529] +[M1002C528] + [M1002C527] + [M1002C524] +[M1002C523])

KPI formula with short names 100* sum([ALLO_SUCCESS_EDCH_INT] +[ALLO_SUCCESS_EDCH_BGR]) / sum([ALLO_SUCCESS_EDCH_INT] +[ALLO_SUCCESS_EDCH_BGR] +[EDCH_ALLO_CANC_NA_AS_BGR] +[EDCH_ALLO_CANC_NA_AS_INT] +[UL_DCH_SEL_MAX_HSUPA_USR_BGR] +[UL_DCH_SEL_MAX_HSUPA_USR_INT] +[UL_DCH_SEL_BTS_HW_INT] +[UL_DCH_SEL_BTS_HW_BGR] +[SETUP_FAIL_EDCH_BTS_BGR] +[SETUP_FAIL_EDCH_BTS_INT] +[SETUP_FAIL_EDCH_OTHER_BGR] +[SETUP_FAIL_EDCH_OTHER_INT] +[SETUP_FAIL_EDCH_TRANS_BGR] +[SETUP_FAIL_EDCH_TRANS_INT] +[SETUP_FAIL_EDCH_UE_BGR] +[SETUP_FAIL_EDCH_UE_INT])


Unit Percentage

Target values -





Table 54. HSUPA Resource Accessibility for RT Traffic

KPI name HSUPA Resource Accessibility for RT Traffic

KPI abbreviation HSUPA res acc for RT traf

KPI ID RNC_5002a

KPI version 1.1u

Description


30/04/2009


Table 54. HSUPA Resource Accessibility for RT Traffic (cont.)

The accessibility of all started resource allocations for E-DCH for RT Traffic. The number of times when E-DCHchannel has been established divided by the number oftimes when HS-DSCH channel has been selected by cellspecific PS.

Note This KPI includes all reservations, also all SHO branchesincluded in HSUPA AS.


KPI formula 100* sum([M1002C607]) / sum([M1002C607] +[M1002C599] + [M1002C600] + [M1002C601] +[M1002C603] + [M1002C604] + [M1002C605] +[M1002C606])

KPI formula with short names 100* sum([ALLO_SUCCESS_EDCH_STR]) / sum([ALLO_SUCCESS_EDCH_STR] +[UL_DCH_SEL_MAX_HSUPA_USR_STR] +[UL_DCH_SEL_BTS_HW_STR] +[EDCH_ALLO_CANC_NA_AS_STR] +[SETUP_FAIL_EDCH_UE_STR] +[SETUP_FAIL_EDCH_BTS_STR] +[SETUP_FAIL_EDCH_TRANS_STR] +[SETUP_FAIL_EDCH_OTHER_STR])


Unit Percentage

Target values -





Table 55. HSUPA Setup Success Ratio

KPI name HSUPA Setup Success Ratio from user perspective

KPI abbreviation HSUPA stp SR Usr

KPI ID RNC_915c

KPI version 1.0u

Description HSUPA Setup Success Ratio [%] for Streaming, Interactiveand Background Services from user perspective over thereporting period.

Note

DN05191189Issue 4-3 en draft30/04/2009



Table 55. HSUPA Setup Success Ratio (cont.)

The capacity requests by HSUPA capable UE to cells thatare not configured to support HSDPA are excluded byspecific counters in the formula.


KPI formula 100* sum([M1022C190] + [M1022C21] + [M1022C22]) /sum([M1022C181] + [M1022C3] + [M1022C4] -[M1022C222] - [M1022C215] - [M1022C214] - [M1022C219]- [M1022C218] - [M1022C217])

KPI formula with short names 100* sum([HS_E_REQ_HS_E_ALLO_STRE] +[HS_E_REQ_HS_E_ALLO_INT] +[HS_E_REQ_HS_E_ALLO_BGR]) / sum([PS_ATT_HSDSCH_EDCH_STRE] +[PS_ATT_HSDSCH_EDCH_INT] +[PS_ATT_HSDSCH_EDCH_BGR] -[HS_D_REQ_D_D_ALLO_STR_CELL] -[HS_E_REQ_HS_D_ALLO_BGR_CELL] -[HS_E_REQ_HS_D_ALLO_INT_CELL] -[HS_E_REQ_D_D_ALLO_STR_CELL] -[HS_E_REQ_D_D_ALLO_BGR_CELL] -[HS_E_REQ_D_D_ALLO_INT_CELL])


Unit Percentage

Target values OPEN





Table 56. R99 Setup Success Ratio

KPI name R99 Setup Success Ratio from user perspective

KPI abbreviation R99 stp SR Usr

KPI ID RNC_943b

KPI version 1.0u

Description R99 Setup Success Ratio for Streaming, Interactive andBackground Services [%] from user perspective over thereporting period.


KPI formula 100* sum([M1022C195] + [M1022C31] + [M1022C32]) /sum([M1022C183] + [M1022C7] + [M1022C8])


30/04/2009


Table 56. R99 Setup Success Ratio (cont.)

KPI formula with short names 100* sum([D_D_REQ_D_D_ALLO_STRE] +[D_D_REQ_D_D_ALLO_INT] +[D_D_REQ_D_D_ALLO_BGR]) / sum([PS_ATT_DCH_DCH_STRE] + [PS_ATT_DCH_DCH_INT]+ [PS_ATT_DCH_DCH_BGR])


Unit Percentage

Target values OPEN





5.2.2 RNC function level indicators for retainability



5.2.2.1 Packet Session Success Ratio (SSR) [%]

Table 57. HSDPA Resource Retainability for NRT Traffic

KPI name HSDPA Resource Retainability for NRT Traffic

KPI abbreviation HSDPA res retain NRT traf

KPI ID RNC_609a

KPI version 4.4u

Description The retainability of all successfully allocated HS-DSCHresources for NRT traffic.

Note 1 The normal transition from HS-DSCH to FACH/DCH areconsidered as a normal HS-DSCH release (includingtransitions due to mobility and pre-emption).

Note 2 The fallbacks and other possible normal release countersare not included in the formula. They are already included inthe Normal release counters.

DN05191189Issue 4-3 en draft30/04/2009



Table 57. HSDPA Resource Retainability for NRT Traffic (cont.)


KPI formula 100* sum([M1002C407] + [M1002C410]) / sum([M1002C407] + [M1002C410] + [M1002C408] +[M1002C411] + [M1002C479] + [M1002C482])

KPI formula with short names 100* sum([REL_ALLO_NORM_HS_DSCH_INT] +[REL_ALLO_NORM_HS_DSCH_BGR]) / sum([REL_ALLO_NORM_HS_DSCH_INT] +[REL_ALLO_NORM_HS_DSCH_BGR] +[REL_ALLO_OTH_FAIL_HSDSCH_INT] +[REL_ALLO_OTH_FAIL_HSDSCH_BGR] +[REL_ALLO_RL_FAIL_HS_DSCH_INT] +[REL_ALLO_RL_FAIL_HS_DSCH_BGR])


Unit Percentage

Target values -





Table 58. HSDPA Resource Retainability for RT Traffic

KPI name HSDPA Resource Retainability for RT Traffic

KPI abbreviation HSDPA res retain RT traf

KPI ID RNC_5010a

KPI version 1.2u

Description The retainability of all successfully allocated HS-DSCHresources for RT traffic.

Note 1 The normal transition from HS-DSCH to FACH/DCH areconsidered as a normal HS-DSCH release (includingtransitions due to mobility and pre-emption).

Note 2 The fallbacks and other possible normal release countersare not included in the formula. They are already included inthe Normal release counters.


KPI formula 100 * sum([M1002C578]) / sum([M1002C578] +[M1002C594] + [M1002C579])



30/04/2009


Table 58. HSDPA Resource Retainability for RT Traffic (cont.)

100 * sum([REL_ALLO_NORM_HS_DSCH_STR]) / sum([REL_ALLO_NORM_HS_DSCH_STR] +[REL_ALLO_RL_FAIL_HS_DSCH_STR] +[REL_ALLO_OTH_FAIL_HSDSCH_STR])


Unit Percentage

Target values -





Table 59. HSDPA Success Ratio

KPI name HSDPA Success Ratio from user perspective

KPI abbreviation HSDPA SR Usr

KPI ID RNC_920b

KPI version 1.0u

Description The HSDPA Success Ratio for Streaming, Interactive andBackground Services from user perspective.

Note Switching from HSPA to R99 is considered as a normalHSPA release in the formula.


KPI formula 100-100* sum([M1022C208] + [M1022C57] + [M1022C58] +[M1022C209] + [M1022C59] + [M1022C60] + [M1022C211]+ [M1022C63] + [M1022C64] + [M1022C212] + [M1022C65]+ [M1022C66]) / sum([M1022C208] + [M1022C57] +[M1022C58] + [M1022C209] + [M1022C59] + [M1022C60] +[M1022C211] + [M1022C63] + [M1022C64] + [M1022C212]+ [M1022C65] + [M1022C66] + [M1022C202] + [M1022C45]+ [M1022C46] + [M1022C203] + [M1022C47] + [M1022C48]+ [M1022C197] + [M1022C35] + [M1022C36] +[M1022C198] + [M1022C37] + [M1022C38])

KPI formula with short names 100-100* sum([PS_REL_RL_FAIL_HS_E_STRE] +[PS_REL_RL_FAIL_HS_E_INT] +[PS_REL_RL_FAIL_HS_E_BGR] +[PS_REL_RL_FAIL_HS_D_STRE] +[PS_REL_RL_FAIL_HS_D_INT] +[PS_REL_RL_FAIL_HS_D_BGR] +[PS_REL_OTH_FAIL_HS_E_STRE] +

DN05191189Issue 4-3 en draft30/04/2009



Table 59. HSDPA Success Ratio (cont.)

[PS_REL_OTH_FAIL_HS_E_INT] +[PS_REL_OTH_FAIL_HS_E_BGR] +[PS_REL_OTH_FAIL_HS_D_STRE] +[PS_REL_OTH_FAIL_HS_D_INT] +[PS_REL_OTH_FAIL_HS_D_BGR]) / sum([PS_REL_RL_FAIL_HS_E_STRE] +[PS_REL_RL_FAIL_HS_E_INT] +[PS_REL_RL_FAIL_HS_E_BGR] +[PS_REL_RL_FAIL_HS_D_STRE] +[PS_REL_RL_FAIL_HS_D_INT] +[PS_REL_RL_FAIL_HS_D_BGR] +[PS_REL_OTH_FAIL_HS_E_STRE] +[PS_REL_OTH_FAIL_HS_E_INT] +[PS_REL_OTH_FAIL_HS_E_BGR] +[PS_REL_OTH_FAIL_HS_D_STRE] +[PS_REL_OTH_FAIL_HS_D_INT] +[PS_REL_OTH_FAIL_HS_D_BGR] +[PS_REL_NORM_HS_E_STRE] +[PS_REL_NORM_HS_E_INT] +[PS_REL_NORM_HS_E_BGR] +[PS_REL_NORM_HS_D_STRE] +[PS_REL_NORM_HS_D_INT] +[PS_REL_NORM_HS_D_BGR] +[PS_SWI_HS_E_TO_D_D_STRE] +[PS_SWI_HS_E_TO_D_D_INT] +[PS_SWI_HS_E_TO_D_D_BGR] +[PS_SWI_HS_D_TO_D_D_STRE] +[PS_SWI_HS_D_TO_D_D_INT] +[PS_SWI_HS_D_TO_D_D_BGR])


Unit Percentage

Target values OPEN





Table 60. HSUPA resource Retainability for NRT Traffic

KPI name HSUPA resource Retainability for NRT Traffic

KPI abbreviation HSUPA res retain NRT traf

KPI ID RNC_919a

KPI version 2.4u


30/04/2009


Table 60. HSUPA resource Retainability for NRT Traffic (cont.)

Description The retainability of all successfully allocated E-DCHresources for NRT traffic.

Note This KPI includes all HSUPA resource releases i.e. for allSHO branches included in HSUPA AS.


KPI formula 100* sum([M1002C535] + [M1002C536] + [M1002C537] +[M1002C538]) / sum([M1002C535] + [M1002C536] +[M1002C537] + [M1002C538] + [M1002C539] +[M1002C540] + [M1002C541] + [M1002C542])

KPI formula with short names 100* sum([REL_EDCH_NORM_INT] +[REL_EDCH_NORM_BGR] +[REL_EDCH_HSDSCH_SCC_INT] +[REL_EDCH_HSDSCH_SCC_BGR]) / sum([REL_EDCH_NORM_INT] + [REL_EDCH_NORM_BGR] +[REL_EDCH_HSDSCH_SCC_INT] +[REL_EDCH_HSDSCH_SCC_BGR] +[REL_EDCH_RL_FAIL_INT] + [REL_EDCH_RL_FAIL_BGR]+ [REL_EDCH_OTHER_FAIL_INT] +[REL_EDCH_OTHER_FAIL_BGR])


Unit Percentage

Target values -





Table 61. HSUPA Resource Retainability for RT Traffic

KPI name HSUPA Resource Retainability for RT Traffic

KPI abbreviation HSUPA res retain RT traf

KPI ID RNC_5012a

KPI version 1.1u

Description The retainability of all successfully allocated E-DCHresources for RT traffic.

Note This KPI includes all HSUPA resource releases, that is, forall SHO branches included in HSUPA AS.


KPI formula

DN05191189Issue 4-3 en draft30/04/2009



Table 61. HSUPA Resource Retainability for RT Traffic (cont.)

100 * sum([M1002C609] + [M1002C610]) / sum([M1002C609] + [M1002C610] + [M1002C611] +[M1002C612])

KPI formula with short names 100 * sum([REL_EDCH_NORM_STR] +[REL_EDCH_HSDSCH_SCC_STR]) / sum([REL_EDCH_NORM_STR] +[REL_EDCH_HSDSCH_SCC_STR] +[REL_EDCH_RL_FAIL_STR] +[REL_EDCH_OTHER_FAIL_STR])


Unit Percentage

Target values -





Table 62. HSUPA Success Ratio

KPI name HSUPA Success Ratio from user perspective

KPI abbreviation HSUPA SR Usr

KPI ID RNC_921b

KPI version 1.0u

Description The HSUPA Success Ratio for Streaming, Interactive andBackground Services from user perspective.

Note Switching from HSPA to R99 is considered as a normalHSPA release in the formula.


KPI formula 100-100* sum([M1022C208] + [M1022C57] + [M1022C58] +[M1022C211] + [M1022C63] + [M1022C64]) / sum([M1022C208] + [M1022C57] + [M1022C58] + [M1022C211]+ [M1022C63] + [M1022C64] + [M1022C202] + [M1022C45]+ [M1022C46] + [M1022C197] + [M1022C35] +[M1022C36])

KPI formula with short names 100-100* sum([PS_REL_RL_FAIL_HS_E_STRE] +[PS_REL_RL_FAIL_HS_E_INT] +[PS_REL_RL_FAIL_HS_E_BGR] +[PS_REL_OTH_FAIL_HS_E_STRE] +[PS_REL_OTH_FAIL_HS_E_INT] +[PS_REL_OTH_FAIL_HS_E_BGR]) / sum


30/04/2009


Table 62. HSUPA Success Ratio (cont.)

([PS_REL_RL_FAIL_HS_E_STRE] +[PS_REL_RL_FAIL_HS_E_INT] +[PS_REL_RL_FAIL_HS_E_BGR] +[PS_REL_OTH_FAIL_HS_E_STRE] +[PS_REL_OTH_FAIL_HS_E_INT] +[PS_REL_OTH_FAIL_HS_E_BGR] +[PS_REL_NORM_HS_E_STRE] +[PS_REL_NORM_HS_E_INT] +[PS_REL_NORM_HS_E_BGR] +[PS_SWI_HS_E_TO_D_D_STRE] +[PS_SWI_HS_E_TO_D_D_INT] +[PS_SWI_HS_E_TO_D_D_BGR])


Unit Percentage

Target values OPEN





Table 63. R99 Success Ratio

KPI name R99 Success Ratio from user perspective

KPI abbreviation R99 SR Usr

KPI ID RNC_944b

KPI version 1.0u

Description The R99 Success Ratio for Streaming, Interactive andBackground Services from user perspective.


KPI formula 100-100* sum([M1022C210] + [M1022C61] + [M1022C62] +[M1022C213] + [M1022C67] + [M1022C68]) / sum([M1022C210] + [M1022C61] + [M1022C62] + [M1022C213]+ [M1022C67] + [M1022C68] + [M1022C204] + [M1022C49]+ [M1022C50])

KPI formula with short names 100-100* sum([PS_REL_RL_FAIL_D_D_STRE] +[PS_REL_RL_FAIL_D_D_INT] +[PS_REL_RL_FAIL_D_D_BGR] +[PS_REL_OTH_FAIL_D_D_STRE] +[PS_REL_OTH_FAIL_D_D_INT] +[PS_REL_OTH_FAIL_D_D_BGR]) / sum([PS_REL_RL_FAIL_D_D_STRE] +

DN05191189Issue 4-3 en draft30/04/2009



Table 63. R99 Success Ratio (cont.)

[PS_REL_RL_FAIL_D_D_INT] +[PS_REL_RL_FAIL_D_D_BGR] +[PS_REL_OTH_FAIL_D_D_STRE] +[PS_REL_OTH_FAIL_D_D_INT] +[PS_REL_OTH_FAIL_D_D_BGR] +[PS_REL_NORM_D_D_STRE] +[PS_REL_NORM_D_D_INT] +[PS_REL_NORM_D_D_BGR])


Unit Percentage

Target values OPEN





5.2.3 RNC function level indicators for usage



5.2.3.1 Requested RRC Connection Attempt Numbers [Integer Number]

Table 64. Registration Attempts

KPI name Registration Attempts

KPI abbreviation Regist att

KPI ID RNC_218a

KPI version 2.1u

Description Number of registration attempts.

Note Registration means either network entry, change of locationarea or periodical location update.


KPI formula sum([M1001C46])


30/04/2009


Table 64. Registration Attempts (cont.)

KPI formula with short names sum([REGISTRATION_ATTS])

KPI class Usage/Requested Capacity

Unit #

Target values -





Table 65. RRC Setup Attempts

KPI name RRC Setup Attempts

KPI abbreviation RRC Setup att

KPI ID RNC_214a

KPI version 2.1u

Description The number of RRC connection setup attempts.



KPI formula with short names sum([RRC_CONN_STP_ATT])


Unit #

Target values -





5.2.3.2 Requested Service Attempt Numbers [Integer Number]

Table 66. RAB Attempts Voice

KPI name RAB Attempts Voice

DN05191189Issue 4-3 en draft30/04/2009



Table 66. RAB Attempts Voice (cont.)

KPI abbreviation RAB att Voice

KPI ID RNC_229a

KPI version 2.1u

Description Number of RAB setup attempts requested for CSConversational calls with RAB QoS parameter 'sourcedescriptor' = Speech.



KPI formula with short names sum([RAB_STP_ATT_CS_VOICE])


Unit #

Target values -





Table 67. RAB Attempts UDI

KPI name RAB Attempts UDI

KPI abbreviation RAB att UDI

KPI ID RNC_268a

KPI version 2.1u

Description Number of RAB setup attempts requested for CSConversational calls with RAB QoS parameter 'sourcedescriptor' = UDI.

Note UDI basically means video calls.



KPI formula with short names sum([RAB_STP_ATT_CS_CONV])


Unit #

Target values -



30/04/2009


Table 67. RAB Attempts UDI (cont.)




Table 68. RAB Attempts Streaming

KPI name RAB Attempts Streaming

KPI abbreviation RAB att Streaming

KPI ID RNC_617a

KPI version 2.1u

Description Number of RAB setup attempts requested for streamingcalls.


KPI formula sum([M1001C68] + [M1001C70])

KPI formula with short names sum([RAB_STP_ATT_CS_STREA] +[RAB_STP_ATT_PS_STREA])


Unit #

Target values -





Table 69. RAB Attempts PS Interactive and Background

KPI name RAB Attempts PS Interactive and Background

KPI abbreviation RAB att PS Ia and Bg

KPI ID RNC_616a

KPI version 2.1u

Description Number of RAB setup attempts requested for PS Interactiveor Background calls. This counter update is dependingabout profile setting in registry.

DN05191189Issue 4-3 en draft30/04/2009



Table 69. RAB Attempts PS Interactive and Background (cont.)


KPI formula sum([M1001C71] + [M1001C72])

KPI formula with short names sum([RAB_STP_ATT_PS_INTER] +[RAB_STP_ATT_PS_BACKG])


Unit #

Target values -





Table 70. Multi RAB attempts

KPI name Multi RAB attempts

KPI abbreviation M-RAB att

KPI ID RNC_740a

KPI version 2.1u

Description Multi RAB attempts.

Note The current formula lacks all possible Multi-RAB attemptsdue to missing counters.


KPI formula sum([M1001C281] + [M1001C282] + [M1001C283] +[M1001C284] + [M1001C285] + [M1001C286] +[M1001C293] + [M1001C294] + [M1001C295] +[M1001C296] + [M1001C297] + [M1001C298] +[M1001C313] + [M1001C314] + [M1001C315] +[M1001C316] + [M1001C317] + [M1001C318] +[M1001C305] + [M1001C306] + [M1001C307] +[M1001C311])

KPI formula with short names sum([RAB_S_A_CS_12_2_1PSNRT64_64] +[RAB_S_A_CS_12_2_1PSNRT64_128] +[RAB_S_A_CS_12_2_2PSNRT_I_I] +[RAB_S_A_CS_12_2_2PSNRT_I_B] +[RAB_S_A_CS_12_2_2PSNRT_B_B] +[RAB_S_A_CS_12_2_3PSNRT] +[RAB_S_A_CS_AMM_1PSNRT64_64] +[RAB_S_A_CS_AMM_1PSNRT64_128] +[RAB_S_A_CS_AMM_2PSNRT_I_I] +


30/04/2009


Table 70. Multi RAB attempts (cont.)

[RAB_S_A_CS_AMM_2PSNRT_I_B] +[RAB_S_A_CS_AMM_2PSNRT_B_B] +[RAB_S_A_CS_AMM_3PSNRT] +[RAB_S_A_PSS_GEM_1PSNRT64_64] +[RAB_S_A_PSS_GEM_1PSNRT64_128] +[RAB_S_A_PSS_GEM_1PSNRT64_384] +[RAB_S_A_PSS_GLM_1PSNRT64_64] +[RAB_S_A_PSS_GLM_1PSNRT64_128] +[RAB_S_A_PSS_GLM_1PSNRT64_384] +[RAB_SETUP_ATT_2PSNRT_I_I] +[RAB_SETUP_ATT_2PSNRT_I_B] +[RAB_SETUP_ATT_2PSNRT_B_B] +[RAB_SETUP_ATT_3PSNRT])


Unit #

Target values See RNC Product Description for Busy Hour Call Attempts(BHCA)





Table 71. Short Message Service Attempts for idle mode UEs

KPI name Short Message Service Attempts for idle mode UEs

KPI abbreviation Inc SMS att

KPI ID RNC_5046a

KPI version 1.0u

Description Number of Short Message Service attempts requested forUEs in idle mode.


KPI formula sum ([M1001C54] + [M1001C56])

KPI formula with short names sum ([MOC_LOW_PRIOR_SIGN_ATTS] +[MTC_LOW_PRIOR_SIGN_ATTS])


Unit #

Target values -


DN05191189Issue 4-3 en draft30/04/2009



Table 71. Short Message Service Attempts for idle mode UEs (cont.)




Table 72. Incoming Location Service Attempts

KPI name Incoming Location Service Attempts

KPI abbreviation Inc LCS att

KPI ID RNC_5047a

KPI version 1.0u

Description Number of Location Service attempts requested.

Measurement M1011: Location Services

KPI formula sum ([M1011C0])

KPI formula with short names sum ([NBR_OF_LCS_REQUESTS])


Unit #

Target values -





5.2.3.3 Requested Packet Session Attempt Numbers [Integer Number]

Table 73. Packet Session attempts

KPI name Packet Session attempts

KPI abbreviation Packet Session att

KPI ID RNC_930b

KPI version 2.2u

Description Packet Session Setup Attempts over the reporting period.

Note For differences between Packet Service, Packet Sessionand Packet call, see RAN KPI Document.


30/04/2009


Table 73. Packet Session attempts (cont.)


KPI formula sum ( [M1022C3] + [M1022C4] + [M1022C5] + [M1022C6] +[M1022C7] + [M1022C8] + [M1022C181] + [M1022C182] +[M1022C183] )

KPI formula with short names sum ( [PS_ATT_HSDSCH_EDCH_INT] +[PS_ATT_HSDSCH_EDCH_BGR] +[PS_ATT_HSDSCH_DCH_INT] +[PS_ATT_HSDSCH_DCH_BGR] +[PS_ATT_DCH_DCH_INT] + [PS_ATT_DCH_DCH_BGR] +[PS_ATT_HSDSCH_EDCH_STRE] +[PS_ATT_HSDSCH_DCH_STRE] +[PS_ATT_DCH_DCH_STRE] )


Unit #

Target values See RNC Product Description for Busy Hour Call Attempts(BHCA).





Table 74. HSDPA attempts

KPI name HSDPA attempts

KPI abbreviation HSDPA att

KPI ID RNC_926b

KPI version 1.0u

Description HSDPA attempts from user perspective over the reportingperiod.


KPI formula sum ( [M1022C3] + [M1022C4] + [M1022C181] +[M1022C5] + [M1022C6] + [M1022C182])

KPI formula with short names sum ( [PS_ATT_HSDSCH_EDCH_INT] +[PS_ATT_HSDSCH_EDCH_BGR] +[PS_ATT_HSDSCH_EDCH_STRE] +[PS_ATT_HSDSCH_DCH_INT] +[PS_ATT_HSDSCH_DCH_BGR] +[PS_ATT_HSDSCH_DCH_STRE])


DN05191189Issue 4-3 en draft30/04/2009



Table 74. HSDPA attempts (cont.)

Unit #

Target values See RNC Product Description for Busy Hour Call Attempts(BHCA)





Table 75. HSUPA attempts

KPI name HSUPA attempts

KPI abbreviation HSUPA att

KPI ID RNC_928b

KPI version 1.0u

Description HSUPA attempts from user perspective over the reportingperiod.


KPI formula sum ( [M1022C3] + [M1022C4] + [M1022C181])

KPI formula with short names sum ( [PS_ATT_HSDSCH_EDCH_INT] +[PS_ATT_HSDSCH_EDCH_BGR] +[PS_ATT_HSDSCH_EDCH_STRE])


Unit #

Target values -





5.2.3.4 Requested Handover Attempt Numbers [Integer Number]

Table 76. Soft HO Update Attempts, RT

KPI name Soft HO Update Attempts, RT


30/04/2009


Table 76. Soft HO Update Attempts, RT (cont.)

KPI abbreviation Soft HO Update att RT

KPI ID RNC_193a

KPI version 2.1u

Description Number of active set updates, RT.

Note SHO attempt includes cases when UE has also anyadditional NRT service.

Measurement M1007: Soft Handover


KPI formula with short names sum ([SUCC_UPDATES_ON_SHO_FOR_RT] +[UNSUCC_UPDATES_ON_SHO_FOR_RT])


Unit #

Target values See RNC Product Description for assumed SHOProportions in relation to established calls.





Table 77. Soft HO Update Attempts, NRT

KPI name Soft HO Update Attempts, NRT

KPI abbreviation Soft HO Update att NRT

KPI ID RNC_194a

KPI version 2.1u

Description Number of active set updates, NRT.

Note SHO attempt excludes cases when UE has also any RTservice.



KPI formula with short names sum ([SUCC_UPDATES_ON_SHO_FOR_NRT] +[UNSUCC_UPDATES_ON_SHO_NRT])


Unit #

DN05191189Issue 4-3 en draft30/04/2009



Table 77. Soft HO Update Attempts, NRT (cont.)

Target values -





Table 78. Intra System Hard Handover Attempts

KPI name Intra System Hard Handover Attempts

KPI abbreviation Intra System HHO Att

KPI ID RNC_743a

KPI version 2.1u

Description Number of Inter RNC Intra Frequency Hard Handoverattempts and all Intra RNC/Inter RNC Inter Frequency HardHandover Attempts.

Note Inter RNC Intra Frequency HHO can occur when Inter RNCSHO is not possible due to parameter settings or Iurunavailability.


KPI formula sum([M1008C4] + [M1008C5] + [M1008C13] + [M1008C14]+ [M1008C54] + [M1008C58] + [M1008C62] + [M1008C102]+ [M1008C106] + [M1008C110])

KPI formula with short names sum([HHO_ATT_CAUSED_SHO_INCAP_RT] +[IMMED_HHO_CSD_SHO_INCAP_RT] +[HHO_ATT_CAUSED_SHO_INCAP_NRT] +[IMMED_HHO_CSD_SHO_INCAP_NRT] +[INTRA_INTRA_HHO_ATT_RT] +[INTRA_INTER_HHO_ATT_RT] + [INTER_HHO_ATT_RT] +[INTRA_INTRA_HHO_ATT_NRT] +[INTRA_INTER_HHO_ATT_NRT] +[INTER_HHO_ATT_NRT])


Unit #

Target values See RNC Product Description for assumed HHOProportions in relation to established calls.





30/04/2009


Table 78. Intra System Hard Handover Attempts (cont.)


Table 79. Soft Handover Update Attempts, RT

KPI name ISHO Attempts RT

KPI abbreviation ISHO att RT

KPI ID RNC_298d

KPI version 1.0u

Description Number of RT ISHO attempts, which has been started afterISHO measurements.

Note Inter RNC RT ISHO attempt includes cases when UE hasalso any additional NRT service.


KPI formula sum( [M1010C18] + [M1010C22] + [M1010C26] +[M1010C30] + [M1010C34] + [M1010C76] + [M1010C97] +[M1010C137] + [M1010C138] + [M1010C140] +[M1010C139] + [M1010C141] + [M1010C219] +[M1010C196] + [M1010C195] + [M1010C185] +[M1010C215])

KPI formula with short names sum( [IS_HHO_ATT_UL_DCH_Q_RT] +[IS_HHO_ATT_UE_TRX_PWR_RT] +[IS_HHO_ATT_DPCH_PWR_RT] +[IS_HHO_ATT_CPICH_RSCP_RT] +[IS_HHO_ATT_CPICH_ECNO_RT] +[IS_HHO_ATT_IM_IMS_RT] +[IS_HHO_ATT_EMERG_CALL] +[IS_HHO_ATT_LB_PRX_TOT_RT] +[IS_HHO_ATT_LB_PTX_TOT_RT] +[IS_HHO_ATT_LB_RES_LIM_RT] +[IS_HHO_ATT_LB_RSVR_SC_RT] +[IS_HHO_ATT_SB_RT] + [ATT_GANHO_AMR_RT] +[IS_HHO_ATT_LB_CAPA_DL_RT] +[IS_HHO_ATT_LB_CAPA_UL_RT] +[IS_HHO_ATT_UL_DCH_WPS_RT] +[IS_HHO_ATT_DR_AMR_RT])


Unit #

Target values -




DN05191189Issue 4-3 en draft30/04/2009



Table 79. Soft Handover Update Attempts, RT (cont.)


Table 80. Soft Handover Update Attempts, NRT

KPI name ISHO Attempts NRT

KPI abbreviation ISHO att NRT

KPI ID RNC_299c

KPI version 2.1u

Description Number of NRT ISHO attempts, which has been startedafter ISHO measurements.

Note Inter RNC NRT ISHO attempt excludes cases when UE hasalso any RT service.


KPI formula sum( [M1010C56] + [M1010C60] + [M1010C64] +[M1010C68] + [M1010C72] + [M1010C83] + [M1010C145] +[M1010C144] + [M1010C142] + [M1010C143] +[M1010C147] + [M1010C146] + [M1010C148] )

KPI formula with short names sum( [IS_HHO_ATT_UL_DCH_Q_NRT] +[IS_HHO_ATT_UE_TRX_PWR_NRT] +[IS_HHO_ATT_DL_DPCH_PWR_NRT] +[IS_HHO_ATT_CPICH_RSCP_NRT] +[IS_HHO_ATT_CPICH_ECNO_NRT] +[IS_HHO_ATT_IM_IMS_NRT] +[IS_HHO_ATT_LB_CAPA_DL_NRT] +[IS_HHO_ATT_LB_CAPA_UL_NRT] +[IS_HHO_ATT_LB_PRX_TOT_NRT] +[IS_HHO_ATT_LB_PTX_TOT_NRT] +[IS_HHO_ATT_LB_RES_LIM_NRT] +[IS_HHO_ATT_LB_RSVR_SC_NRT] +[IS_HHO_ATT_SB_NRT] )


Unit #

Target values -






30/04/2009


Table 81. Incoming Inter System Change Attempts

KPI name Incoming Inter System Change Attempts

KPI abbreviation Inc IS Change att

KPI ID RNC_5028a

KPI version 1.0u

Description Number of Inter System Change attempts requested.

Note The KPI includes CS ISHO, commanded PS ISHO and idlemode PS inter RAT cell re-selections.


KPI formula sum ([M1001C219] + [M1001C44] + [M1001C42])

KPI formula with short names sum ([INTER_SYS_HHO_ATTS] +[CELL_CHNG_ORD_ATTS] +[INTR_RAT_CELL_RE_SEL_ATTS])


Unit #

Target values -





Table 82. HSDPA Serving Cell Change Attempts

KPI name HSDPA Serving Cell Change Attempts

KPI abbreviation HSDPA SCC att

KPI ID RNC_927a

KPI version 2.2u

Description HSDPA Serving Cell Change Attempts over the reportingperiod in the Source Cell.


KPI formula sum ( [M1008C213] + [M1008C214] + [M1008C215] +[M1008C216] )

KPI formula with short names sum ( [SCC_STARTED_CPICH_ECNO] +[SCC_STARTED_UL_SIR_ERROR] +[SCC_STARTED_ACTIVE_SET_UPD] +[SCC_STARTED_OTHER_REASON] )


DN05191189Issue 4-3 en draft30/04/2009



Table 82. HSDPA Serving Cell Change Attempts (cont.)

Unit #

Target values -





Table 83. HSUPA Serving Cell Change Attempts

KPI name HSUPA Serving Cell Change Attempts

KPI abbreviation HSUPA SCC att

KPI ID RNC_929a

KPI version 2.2u

Description HSUPA Serving Cell Change Attempts over the reportingperiod in the Source Cell.

Note E-DCH Serving cell change can only occur when a HS-DSCH Serving Cell change is executed.



KPI formula with short names sum([EDCH_SCC_STARTED])


Unit #

Target values -





5.2.3.5 Logical Resource Availability [%]

Table 84. Iu Availability

KPI name Iu Availability


30/04/2009


Table 84. Iu Availability (cont.)

KPI abbreviation Iu avail

KPI ID RNC_728a

KPI version 3.3u

Description The percentage of time when the Iu interface SCCPsubsystem is in working state.

Measurement M1003: L3 signaling at Iu


KPI formula with short names 100* sum([IU_AVAILABILITY]) / sum([IU_AVAILABILITY_DENOM])

KPI class Usage/Resource Availability

Unit Percentage

Target values N/A





Table 85. Iur Availability

KPI name Iur Availability

KPI abbreviation Iur avail

KPI ID RNC_729a

KPI version 3.3u

Description The percentage of time when the Iur interface SCCPsubsystem is in working state.

Measurement M1004: L3 signaling at Iur


KPI formula with short names 100* sum([IUR_AVAILABILITY]) / sum([IUR_AVAILABILITY_DENOM])


Unit Percentage

Target values N/A



DN05191189Issue 4-3 en draft30/04/2009



Table 85. Iur Availability (cont.)



5.2.3.6 Peak Resource Reservation Numbers [Integer Number]

Table 86. Peak number of HSDPA users in RNC

KPI name Peak number of HSDPA users in RNC

KPI abbreviation Peak nr HSDPA usr in RNC

KPI ID RNC_5017a

KPI version 1.2u

Description Peak Number of simultaneous HSDPA connections in oneRNC over the reporting period.

Note HSUPA call does not update counters for this object even ifit uses HSDPA in downlink. As RNC capacity is common forHSPA users and the defined KPIs are separately forHSDPA and HSUPA users (RNC_5018a) a checking of bothHSPA user KPIs is needed in order to evaluate RNC HSPAcapacity.

Measurement M609: DSP Service Statistics

KPI formula max([M609C1])

KPI formula with short names max([DSP_SERVICE_PEAK_RES_ALLOC])

KPI class Usage/Allocated Capacity

Unit #

Target values See Targets for WCDMA RAN key performance indicators


Object Summary Level notes The related measurement is not HSDPA resource specific, itmeasures all DSP resources. Therefore the used countermeasures all possible DSP services and the measurementobject - ALLHSDPA - is utilized for counter data separation.



Table 87. Peak number of HSUPA users in RNC

KPI name Peak number of HSUPA users in RNC


30/04/2009


Table 87. Peak number of HSUPA users in RNC (cont.)

KPI abbreviation Peak nr HSUPA usr in RNC

KPI ID RNC_5018a

KPI version 1.2u

Description Peak Number of simultaneous HSUPA connections in oneRNC over the reporting period.

Note As RNC capacity is common for HSPA users and thedefined KPIs are separately for HSDPA and HSUPA users(RNC_5017a) a checking of both HSPA user KPIs isneeded in order to evaluate RNC HSPA capacity.

Measurement M609: DSP Service Statistics


KPI formula with short names max([DSP_SERVICE_PEAK_RES_ALLOC])


Unit #



Object Summary Level notes The related measurement is not HSUPA resource specific, itmeasures all DSP resources. Therefore the used countermeasures all possible DSP services and the measurementobject - ALLHSUPA - is utilised for counter data separation.



Table 88. Peak number of RRC Connected Mode Users in RNC

KPI name Peak number of RRC Connected Mode Users in RNC

KPI abbreviation Pnr RRC Conn Mode usr RNC

KPI ID RNC_5025a

KPI version 1.1u

Description Peak Number of simultaneous RRC Connected Mode Usersin one RNC over the reporting period.

Measurement M802: RNC Capacity Usage

KPI formula max ([M802C18])

KPI formula with short names max ([MAX_RRC_CONN_MODE_USERS])


Unit #

DN05191189Issue 4-3 en draft30/04/2009



Table 88. Peak number of RRC Connected Mode Users in RNC (cont.)

Target values -


Object Summary Level notes



Table 89. Maximum number of Voice calls per RNC

KPI name Maximum number of Voice calls per RNC

KPI abbreviation Max nr Voice calls perRNC

KPI ID RNC_5016a

KPI version 1.2u

Description Peak Number of simultaneous AMR calls in one RNC overthe reporting period.



KPI formula with short names max([AMR_MAX])


Unit #

Target values See Targets for WCDMA RAN key performance indicators.





5.2.3.7 Allocated Capacity [Mbit/s]

CS voice call

Table 90. Average Allocated Uplink Dedicated Channel Capacity for CS Voicein Controlling RNC

KPI name Average Allocated Uplink Dedicated Channel Capacity forCS Voice in Controlling RNC


30/04/2009


Table 90. Average Allocated Uplink Dedicated Channel Capacity for CS Voicein Controlling RNC (cont.)

KPI abbreviation Alloc UL DCH cap CS Voice

KPI ID RNC_162c

KPI version 7.3u

Description Allocated Uplink Dedicated Channel Capacity [Mbit/s] forCS Voice in Controlling RNC for the reporting period. Thesethroughput calculations are based on resource allocationcounters and do not show as such the actual throughput butallocated capacity.

Note The counters in the formula include soft handoveroverheads.


KPI formula sum((4.75*[M1002C34]) + (4.75*[M1002C270])+ (5.15*[M1002C35]) + (5.15*[M1002C271])+ (5.9*[M1002C36]) +(5.9*[M1002C272]) + (6.7*[M1002C37]) + (6.7*[M1002C273]) + (7.4*[M1002C38]) + (7.4*[M1002C274]) +(7.95*[M1002C39]) + (7.95*[M1002C275]) + (10.2*[M1002C40]) + (10.2*[M1002C276]) + (12.2 * [M1002C41])+ (12.2*[M1002C277]) + (12.65 * [M1002C494]) + (12.65 *[M1002C489]) + (6.6 * [M1002C496]) + (6.6 *[M1002C490])+ (8.85 *[M1002C495])) / sum(PERIOD_DURATION)*60*100000

KPI formula with short names sum((4.75*[DUR_FOR_AMR_4_75_UL_IN_SRNC]) + (4.75*[DURA_FOR_AMR_4_75_UL_IN_DRNC])+ (5.15*[DUR_FOR_AMR_5_15_UL_IN_SRNC]) + (5.15*[DURA_FOR_AMR_5_15_UL_IN_DRNC])+ (5.9*[DUR_FOR_AMR_5_9_UL_IN_SRNC]) + (5.9*[DURA_FOR_AMR_5_9_UL_IN_DRNC]) + (6.7*[DUR_FOR_AMR_6_7_UL_IN_SRNC]) + (6.7*[DURA_FOR_AMR_6_7_UL_IN_DRNC]) + (7.4*[DUR_FOR_AMR_7_4_UL_IN_SRNC]) + (7.4*[DURA_FOR_AMR_7_4_UL_IN_DRNC]) + (7.95*[DUR_FOR_AMR_7_95_UL_IN_SRNC]) + (7.95*[DURA_FOR_AMR_7_95_UL_IN_DRNC]) + (10.2*[DUR_FOR_AMR_10_2_UL_IN_SRNC]) + (10.2*[DURA_FOR_AMR_10_2_UL_IN_DRNC]) + (12.2 *[DUR_FOR_AMR_12_2_UL_IN_SRNC]) + (12.2*[DURA_FOR_AMR_12_2_UL_IN_DRNC]) + (12.65 *[DURA_FOR_WAMR_12_65_DRNC]) + (12.65 *[DURA_FOR_WAMR_12_65_SRNC]) + (6.6 *[DURA_FOR_WAMR_6_6_DRNC]) + (6.6 *[DURA_FOR_WAMR_6_6_SRNC]) + (8.85 *[DURA_FOR_WAMR_8_85_DRNC])) / sum(PERIOD_DURATION)*60*100000


Unit Mbps

Target values Depends on Traffic and DCH capacity.

DN05191189Issue 4-3 en draft30/04/2009



Table 90. Average Allocated Uplink Dedicated Channel Capacity for CS Voicein Controlling RNC (cont.)





R99 data calls

Table 91. Average Allocated Uplink Dedicated Channel Capacity for DataCalls in Controlling RNC

KPI name Average Allocated Uplink Dedicated Channel Capacity forData Calls in Controlling RNC

KPI abbreviation Allo UL dch cap Data Call

KPI ID RNC_164f

KPI version 6.3u

Description Allocated Uplink Dedicated Channel Capacity [Mbit/s] forData Calls in Controlling RNC over the reporting period.These throughput calculations are based on resourceallocation counters and do not show as such the actualthroughput but allocated capacity.



KPI formula sum((64*[M1002C177]) + (64*[M1002C69]) + (14.4*[M1002C76]) + (57.6*[M1002C78]) + (8*[M1002C190])+ (16*[M1002C191])+ (32*[M1002C192])+ (64*[M1002C193])+(128*[M1002C194])+ (8*[M1002C206]) + (8*[M1002C222]) +(16*[M1002C207]) + (16*[M1002C223]) + (32*[M1002C208])+ (32*[M1002C224]) + (64*[M1002C209]) + (64*[M1002C225]) + (128*[M1002C210]) + (128*[M1002C226])+ (256*[M1002C211]) + (256 *[M1002C227]) + (384*[M1002C213]) + (384*[M1002C229]) + (8*[M1002C315]) +(14.4*[M1002C316])+ (16*[M1002C317]) + (32*[M1002C319]) + (57.6*[M1002C321]) + (64*[M1002C322]) +(128*[M1002C323]) + (256*[M1002C324]) (384*[M1002C326])) / sum(PERIOD_DURATION)*60*100000

KPI formula with short names sum((64*[DUR_PS_CONV_64_UL_IN_SRNC]) + (64*[ALLO_DUR_CS_CONV_64_IN_SRNC]) + (14.4*[ALLO_DUR_NTRANS_STRM_14_4_UL]) + (57.6*[ALLO_DUR_NTRANS_STRM_56_7_UL]) + (8*[DUR_PS_STREAM_8_UL_IN_SRNC])+ (16*


30/04/2009


Table 91. Average Allocated Uplink Dedicated Channel Capacity for DataCalls in Controlling RNC (cont.)

[DUR_PS_STREAM_16_UL_IN_SRNC])+ (32*[DUR_PS_STREAM_32_UL_IN_SRNC])+ (64*[DUR_PS_STREAM_64_UL_IN_SRNC])+ (128*[DUR_PS_STREAM_128_UL_IN_SRNC])+ (8*[DUR_PS_INTERA_8_UL_IN_SRNC]) + (8*[DUR_PS_BACKG_8_UL_IN_SRNC]) + (16*[DUR_PS_INTERA_16_UL_IN_SRNC]) + (16*[DUR_PS_BACKG_16_UL_IN_SRNC]) + (32*[DUR_PS_INTERA_32_UL_IN_SRNC]) + (32*[DUR_PS_BACKG_32_UL_IN_SRNC]) + (64*[DUR_PS_INTERA_64_UL_IN_SRNC]) + (64*[DUR_PS_BACKG_64_UL_IN_SRNC]) + (128*[DUR_PS_INTERA_128_UL_IN_SRNC]) + (128*[DUR_PS_BACKG_128_UL_IN_SRNC]) + (256*[DUR_PS_INTERA_256_UL_IN_SRNC]) + (256 *[DUR_PS_BACKG_256_UL_IN_SRNC]) + (384*[DUR_PS_INTERA_384_UL_IN_SRNC]) + (384*[DUR_PS_BACKG_384_UL_IN_SRNC]) + (8*[DURA_FOR_DATA_8_UL_IN_DRNC]) + (14.4*[DURA_FOR_DATA_14_4_UL_DRNC])+ (16*[DURA_FOR_DATA_16_UL_IN_DRNC]) + (32*[DURA_FOR_DATA_32_UL_IN_DRNC]) + (57.6*[DURA_FOR_DATA_57_6_UL_DRNC]) + (64*[DURA_FOR_DATA_64_UL_IN_DRNC]) + (128*[DURA_FOR_DATA_128_UL_IN_DRNC]) + (256*[DURA_FOR_DATA_256_UL_IN_DRNC]) (384*[DURA_FOR_DATA_384_UL_IN_DRNC])) / sum(PERIOD_DURATION)*60*100000


Unit Mbps

Target values See RNC Product Description for maximum supportedthroughput





CS voice call

Table 92. Average Allocated Downlink Dedicated Channel Capacity for CSVoice in Controlling RNC

KPI name Average Allocated Downlink Dedicated Channel Capacityfor CS Voice in Controlling RNC

DN05191189Issue 4-3 en draft30/04/2009



Table 92. Average Allocated Downlink Dedicated Channel Capacity for CSVoice in Controlling RNC (cont.)

KPI abbreviation Allo DL dch cap CS V CRNC

KPI ID RNC_163c

KPI version 7.3u

Description Allocated Downlink Dedicated Channel Capacity [Mbit/s] forCS Voice in Controlling RNC for the reporting period. Thesethroughput calculations are based on resource allocationcounters and do not show as such the actual throughput butallocated capacity.



KPI formula sum((4.75*[M1002C42]) + (4.75*[M1002C278]) + (5.15*[M1002C43]) + (5.15*[M1002C279]) + (5.9*[M1002C44]) +(5.9*[M1002C280]) + (6.7*[M1002C45]) + (6.7*[M1002C281]) + (7.4*[M1002C46]) + (7.4*[M1002C282]) +(7.95*[M1002C47]) + (7.95*[M1002C283]) + (10.2*[M1002C48]) + (10.2*[M1002C284]) + (12.2*[M1002C49]) +(12.2*[M1002C285]) + (12.65 * [M1002C494]) + (12.65 *[M1002C489]) + (6.6 * [M1002C496])+ (6.6 *[M1002C490])+ (8.85 *[M1002C495])) / sum(PERIOD_DURATION)*60*100000

KPI formula with short names sum((4.75*[DUR_FOR_AMR_4_75_DL_IN_SRNC]) + (4.75*[DURA_FOR_AMR_4_75_DL_IN_DRNC]) + (5.15*[DUR_FOR_AMR_5_15_DL_IN_SRNC]) + (5.15*[DURA_FOR_AMR_5_15_DL_IN_DRNC]) + (5.9*[DUR_FOR_AMR_5_9_DL_IN_SRNC]) + (5.9*[DURA_FOR_AMR_5_9_DL_IN_DRNC]) + (6.7*[DUR_FOR_AMR_6_7_DL_IN_SRNC]) + (6.7*[DURA_FOR_AMR_6_7_DL_IN_DRNC]) + (7.4*[DUR_FOR_AMR_7_4_DL_IN_SRNC]) + (7.4*[DURA_FOR_AMR_7_4_DL_IN_DRNC]) + (7.95*[DUR_FOR_AMR_7_95_DL_IN_SRNC]) + (7.95*[DURA_FOR_AMR_7_95_DL_IN_DRNC]) + (10.2*[DUR_FOR_AMR_10_2_DL_IN_SRNC]) + (10.2*[DURA_FOR_AMR_10_2_DL_IN_DRNC]) + (12.2*[DUR_FOR_AMR_12_2_DL_IN_SRNC]) + (12.2*[DURA_FOR_AMR_12_2_DL_IN_DRNC]) + (12.65 *[DURA_FOR_WAMR_12_65_DRNC]) + (12.65 *[DURA_FOR_WAMR_12_65_SRNC]) + (6.6 *[DURA_FOR_WAMR_6_6_DRNC])+ (6.6 *[DURA_FOR_WAMR_6_6_SRNC]) + (8.85 *[DURA_FOR_WAMR_8_85_DRNC])) / sum(PERIOD_DURATION)*60*100000


Unit Mbps



30/04/2009


Table 92. Average Allocated Downlink Dedicated Channel Capacity for CSVoice in Controlling RNC (cont.)





R99 data calls

Table 93. Average Allocated Downlink Dedicated Channel Capacity for DataCalls in Controlling RNC

KPI name Average Allocated Downlink Dedicated Channel Capacityfor Data Calls in Controlling RNC

KPI abbreviation Allo DL dch cap DCal CRNC

KPI ID RNC_165g

KPI version 6.3u

Description Allocated Downlink Dedicated Channel Capacity [Mbit/s] forData Calls in Controlling RNC over the reporting period.These throughput calculations are based on resourceallocation counters and as such are not showing actualthroughput but allocated capacity.



KPI formula sum((64*[M1002C69]) + (14.4*[M1002C79]) + (57.6*[M1002C81]) + (8*[M1002C198]) + (16*[M1002C199]) + (32*[M1002C200]) + (64*[M1002C201]) + (128*[M1002C202]) +(256*[M1002C203]) + (384*[M1002C205]) + (8*[M1002C214]) + (8*[M1002C230]) + (16*[M1002C215]) +(16*[M1002C231]) + (32*[M1002C216]) + (32*[M1002C232])+ (64*[M1002C217]) + (64*[M1002C233]) + (128*[M1002C218]) + (128*[M1002C234]) + (256*[M1002C219])+ (256*[M1002C235]) + (384*[M1002C221]) + (384*[M1002C237]) + (8*[M1002C327]) + (14.4*[M1002C328]) +(16*[M1002C329]) + (32*[M1002C331]) + (57.6 *[M1002C333]) + (64*[M1002C334]) + (128*[M1002C335]) +(256*[M1002C336]) + (384*[M1002C338])) / sum(PERIOD_DURATION)*60*100000

KPI formula with short names sum((64*[ALLO_DUR_CS_CONV_64_IN_SRNC]) + (14.4*[ALLO_DUR_NTRANS_STRM_14_4_DL]) + (57.6*[ALLO_DUR_NTRANS_STRM_56_7_DL]) + (8*[DUR_PS_STREAM_8_DL_IN_SRNC]) + (16*

DN05191189Issue 4-3 en draft30/04/2009



Table 93. Average Allocated Downlink Dedicated Channel Capacity for DataCalls in Controlling RNC (cont.)

[DUR_PS_STREAM_16_DL_IN_SRNC]) + (32*[DUR_PS_STREAM_32_DL_IN_SRNC]) + (64*[DUR_PS_STREAM_64_DL_IN_SRNC]) + (128*[DUR_PS_STREAM_128_DL_IN_SRNC]) + (256*[DUR_PS_STREAM_256_DL_IN_SRNC]) + (384*[DUR_PS_STREAM_384_DL_IN_SRNC]) + (8*[DUR_PS_INTERA_8_DL_IN_SRNC]) + (8*[DUR_PS_BACKG_8_DL_IN_SRNC]) + (16*[DUR_PS_INTERA_16_DL_IN_SRNC]) + (16*[DUR_PS_BACKG_16_DL_IN_SRNC]) + (32*[DUR_PS_INTERA_32_DL_IN_SRNC]) + (32*[DUR_PS_BACKG_32_DL_IN_SRNC]) + (64*[DUR_PS_INTERA_64_DL_IN_SRNC]) + (64*[DUR_PS_BACKG_64_DL_IN_SRNC]) + (128*[DUR_PS_INTERA_128_DL_IN_SRNC]) + (128*[DUR_PS_BACKG_128_DL_IN_SRNC]) + (256*[DUR_PS_INTERA_256_DL_IN_SRNC]) + (256*[DUR_PS_BACKG_256_DL_IN_SRNC]) + (384*[DUR_PS_INTERA_384_DL_IN_SRNC]) + (384*[DUR_PS_BACKG_384_DL_IN_SRNC]) + (8*[DURA_FOR_DATA_8_DL_IN_DRNC]) + (14.4*[DURA_FOR_DATA_14_4_DL_DRNC]) + (16*[DURA_FOR_DATA_16_DL_IN_DRNC]) + (32*[DURA_FOR_DATA_32_DL_IN_DRNC]) + (57.6 *[DURA_FOR_DATA_57_6_DL_DRNC]) + (64*[DURA_FOR_DATA_64_DL_IN_DRNC]) + (128*[DURA_FOR_DATA_128_DL_IN_DRNC]) + (256*[DURA_FOR_DATA_256_DL_IN_DRNC]) + (384*[DURA_FOR_DATA_384_DL_IN_DRNC])) / sum(PERIOD_DURATION)*60*100000


Unit Mbps

Target values See RNC Product Description for maximum supportedthroughput.





HSPA selections

Table 94. HS-DSCH selections

KPI name HS-DSCH selections


30/04/2009


Table 94. HS-DSCH selections (cont.)

KPI abbreviation HS-DSCH selections

KPI ID RNC_614b

KPI version 1.0u

Description The number of times when HS-DSCH channel has beenselected by cell specific packet scheduler.


KPI formula sum ([M1002C385] + [M1002C389] + [M1002C569] +[M1002C475] + [M1002C476] + [M1002C591] +[M1002C401] + [M1002C402] + [M1002C577] +[M1002C413] + [M1002C415] + [M1002C416] +[M1002C417] + [M1002C421] + [M1002C423] +[M1002C424] + [M1002C425] + [M1002C581] +[M1002C585] + [M1002C583] + [M1002C584] +[M1002C602] + [M1002C521] + [M1002C522])

KPI formula with short names sum ([ALLO_HS_DSCH_FLOW_INT] +[ALLO_HS_DSCH_FLOW_BGR] +[ALLO_HS_DSCH_FLOW_STR] +[DCH_SEL_MAX_HSDPA_USERS_INT] +[DCH_SEL_MAX_HSDPA_USERS_BGR] +[DCH_SEL_MAX_HSDPA_USERS_STR] +[REJ_HS_DSCH_RET_INT] + [REJ_HS_DSCH_RET_BGR]+ [REJ_HS_DSCH_RET_STR] +[SETUP_FAIL_RNC_HS_DSCH_INT] +[SETUP_FAIL_UE_HS_DSCH_INT] +[SETUP_FAIL_BTS_HS_DSCH_INT] +[SETUP_FAIL_IUB_HS_TOTAL_INT] +[SETUP_FAIL_RNC_HS_DSCH_BGR] +[SETUP_FAIL_UE_HS_DSCH_BGR] +[SETUP_FAIL_BTS_HS_DSCH_BGR] +[SETUP_FAIL_IUB_HS_TOTAL_BGR] +[SETUP_FAIL_RNC_HS_DSCH_STR] +[SETUP_FAIL_IUB_HS_TOTAL_STR] +[SETUP_FAIL_UE_HS_DSCH_STR] +[SETUP_FAIL_BTS_HS_DSCH_STR] +[DL_DCH_SEL_HSDPA_POWER_STR] +[DL_DCH_SEL_HSDPA_POWER_INT] +[DL_DCH_SEL_HSDPA_POWER_BGR])


Unit #

Target values OPEN





DN05191189Issue 4-3 en draft30/04/2009



Table 95. E-DCH selections

KPI name E-DCH selections

KPI abbreviation E-DCH selections

KPI ID RNC_923b

KPI version 1.0u

Description The number of times when E-DCH channel has beenselected by cell specific packet scheduler for NRT Traffic.


KPI formula sum ([M1002C531] + [M1002C532] + [M1002C607] +[M1002C520] + [M1002C519] + [M1002C601] +[M1002C516] + [M1002C515] + [M1002C517] +[M1002C518] + [M1002C600] + [M1002C526] +[M1002C525] + [M1002C604] + [M1002C530] +[M1002C529] + [M1002C606] + [M1002C528] +[M1002C527] + [M1002C605] + [M1002C524] +[M1002C523] + [M1002C603] )

KPI formula with short names sum ([ALLO_SUCCESS_EDCH_INT] +[ALLO_SUCCESS_EDCH_BGR] +[ALLO_SUCCESS_EDCH_STR] +[EDCH_ALLO_CANC_NA_AS_BGR] +[EDCH_ALLO_CANC_NA_AS_INT] +[EDCH_ALLO_CANC_NA_AS_STR] +[UL_DCH_SEL_MAX_HSUPA_USR_BGR] +[UL_DCH_SEL_MAX_HSUPA_USR_INT] +[UL_DCH_SEL_BTS_HW_INT] +[UL_DCH_SEL_BTS_HW_BGR] +[UL_DCH_SEL_BTS_HW_STR] +[SETUP_FAIL_EDCH_BTS_BGR] +[SETUP_FAIL_EDCH_BTS_INT] +[SETUP_FAIL_EDCH_BTS_STR] +[SETUP_FAIL_EDCH_OTHER_BGR] +[SETUP_FAIL_EDCH_OTHER_INT] +[SETUP_FAIL_EDCH_OTHER_STR] +[SETUP_FAIL_EDCH_TRANS_BGR] +[SETUP_FAIL_EDCH_TRANS_INT] +[SETUP_FAIL_EDCH_TRANS_STR] +[SETUP_FAIL_EDCH_UE_BGR] +[SETUP_FAIL_EDCH_UE_INT] +[SETUP_FAIL_EDCH_UE_STR] )


Unit #

Target values -






30/04/2009


5.2.3.8 Soft Handover Overhead [%]

Table 96. Soft Handover Overhead in CRNC

KPI name Soft Handover Overhead in CRNC

KPI abbreviation SHO Overhead in CRNC

KPI ID RNC_192b

KPI version 6.4u

Description Soft Handover Overhead [%] for Controlling RNC over thereporting period.

Note 1 In the SHO Measurement the counters are both for RNCand WCELL. This formula is purely using the cell levelcounters.

Note 2 The formula will not work properly in border areas. Thisbecause that for the DRNC cells in the AS there will not beany counter updates.


KPI formula 100* (sum([M1007C0] + [M1007C19] + [M1007C1] +[M1007C20] + [M1007C2] + [M1007C21]) / sum(([M1007C0]+ [M1007C19]) + ([M1007C1] + [M1007C20])/2 +([M1007C2] + [M1007C21])/3) - 1)

KPI formula with short names 100* (sum([ONE_CELL_IN_ACT_SET_FOR_RT] +[ONE_CELL_IN_ACT_SET_FOR_NRT] +[TWO_CELLS_IN_ACT_SET_FOR_RT] +[TWO_CELLS_IN_ACT_SET_FOR_NRT] +[THREE_CELLS_IN_ACT_SET_RT] +[THREE_CELLS_IN_ACT_SET_NRT]) / sum(([ONE_CELL_IN_ACT_SET_FOR_RT] +[ONE_CELL_IN_ACT_SET_FOR_NRT]) +([TWO_CELLS_IN_ACT_SET_FOR_RT] +[TWO_CELLS_IN_ACT_SET_FOR_NRT])/2 +([THREE_CELLS_IN_ACT_SET_RT] +[THREE_CELLS_IN_ACT_SET_NRT])/3) - 1)


Unit Percentage

Target values 40 % (Average AS size = 1.4)





DN05191189Issue 4-3 en draft30/04/2009



5.2.3.9 Radio layer (MAC or IP) Data Volumes [Mbit]

Table 97. HSUPA MAC-es data volume at RNC

KPI name HSUPA MAC-es data volume at RNC

KPI abbreviation HSUPA MAC-es DV at RNC

KPI ID RNC_931c

KPI version 1.0u

Description HSUPA MAC-es total throughput based on MAC-es PDUsin RNC.

Note 1 The BTS is assumed to be capable of forwarding allsuccessfully received MAC-es PDUs to RNC.

Note 2 This KPI is mainly meant for following up overall traffic.

Measurement M1023: Cell Throughput

KPI formula sum([M1023C10] + [M1023C23])*8 / 1000000

KPI formula with short names sum([NRT_EDCH_UL_DATA_VOL] +[RT_E_DCH_UL_STREA_DATA])*8 / 1000000


Unit Mbit


Object Summary Levels Network, RNC, BTS




Table 98. HSDPA MAC-d data volume at RNC

KPI name HSDPA MAC-d data volume at RNC

KPI abbreviation HSDPA DL vol SRNC side

KPI ID RNC_5043a

KPI version 1.0u

Description Total Data Volume for HSDPA Downlink Traffic in ServingRNC for the reporting period on Iub. The Downlink Trafficincludes HS-DSCH (MAC-hs) traffic.


KPI formula sum([M1023C8])*8 / 1000000


30/04/2009


Table 98. HSDPA MAC-d data volume at RNC (cont.)

KPI formula with short names sum([HS_DSCH_DATA_VOL])*8 / 1000000


Unit Mbit






Table 99. Iu-PS peak throughput

KPI name Iu-PS peak throughput

KPI abbreviation Iu-PS peak throughput

KPI ID RNC_5021a

KPI version 1.2u

Description Peak Iu-PS throughput calls in one RNC over the reportingperiod.

Note This KPI works only with NPGE and NPS1 HW, not withGTPU.


KPI formula sum([M802C9]) / 1000

KPI formula with short names sum([IU_PS_THR_PEAK]) / 1000


Unit Mbps






DN05191189Issue 4-3 en draft30/04/2009



5.2.3.10 Average Radio Layer (RLC, MAC or FP) Throughput [Mbit/s]

Table 100. Average NRT DCH DL Throughput

KPI name Average NRT DCH DL Throughput

KPI abbreviation Avg NRT DCH DL thp NW

KPI ID RNC_5032a

KPI version 1.0u

Description The net throughput in Downlink for Interactive andBackground Class traffic using DCH. The throughputexcludes RLC retransmissions.

Measurement M1026: RCPM RLC WCEL

KPI formula sum (All NRT DCHs ([M1026C15]*[M1026C29])) / sum((PERIOD_DURATION)*60*1000)

KPI formula with short names sum (All NRT DCHs ([RLC_AM_PDU_DL_NET_TP_W]*[RLC_AM_DL_MEAS_TIME_W])) / sum((PERIOD_DURATION)*60*1000)


Unit Mbps






Table 101. Average NRT HS-DSCH DL Throughput

KPI name Average NRT HS-DSCH DL Throughput

KPI abbreviation Avg NRT HS-DSCH DL thp NW

KPI ID RNC_5033a

KPI version 1.0u

Description The net throughput in Downlink for Streaming, Interactiveand Background Class traffic using HS-DSCH. Thethroughput excludes RLC retransmissions.

Measurement M1026: RCPM RLC WCEL

KPI formula sum (All RT + NRT HS-DSCHs ([M1026C15]*[M1026C26]))/ sum((PERIOD_DURATION)*60*1000)



30/04/2009


Table 101. Average NRT HS-DSCH DL Throughput (cont.)

sum (All RT + NRT HS-DSCHs([RLC_AM_PDU_DL_NET_TP_W]*[RLC_AM_SDU_SUM_TR_DEL_STAD_W])) / sum((PERIOD_DURATION)*60*1000)


Unit Mbps

Target values Depends on Traffic and available HS-DSCH capacity. ThisKPI can be used to follow up HSDPA throughputperformance from user perspective but it is not intended forlive network performance verification purposes.





Table 102. Average MAC-d flow throughput

KPI name Average MAC-d flow throughput

KPI abbreviation Avg MAC-d flow thp

KPI ID RNC_721c

KPI version 1.0u

Description The average MAC-d flow throughput calculated as the totalHSDPA MAC-d throughput at the BTS divided by the totalHSDPA MAC-d allocations. This includes the whole MAC-dallocation time including any inactive periods.

Measurement M5000: HSPA in WBTS; M1002: Traffic

KPI formula sum ([M5000C126] - [M5000C127]) / sum ([M1002C393] +[M1002C397]) / 100 ))

KPI formula with short names sum ([RECEIVED_HS_MACD_BITS] -[DISCARDED_HS_MACD_BITS]) / sum([ALLO_DUR_HS_DSCH_FLOW_INT] +[ALLO_DUR_HS_DSCH_FLOW_BGR]) / 100 ))


Unit kbps

Target values OPEN



DN05191189Issue 4-3 en draft30/04/2009



Table 102. Average MAC-d flow throughput (cont.)



Table 103. HSUPA MAC-es average throughput at RNC

KPI name HSUPA MAC-es average throughput at RNC

KPI abbreviation HSUPA MAC-es avg thp RNC

KPI ID RNC_952c

KPI version 1.0u

Description HSUPA MAC-es average throughput based on MAC-esPDUs in RNC.

Note 1 The BTS is assumed to be capable of forwarding allsuccessfully received MAC-es PDUs to RNC.



KPI formula sum([M1023C10] + [M1023C23]) * 8 / sum(PERIOD_DURATION)*1000000*60

KPI formula with short names sum([NRT_EDCH_UL_DATA_VOL] +[RT_E_DCH_UL_STREA_DATA]) * 8 / sum(PERIOD_DURATION)*1000000*60


Unit Mbps

Target values Depends on Traffic and available E-DCH capacity. This KPIcan be used to follow up HSUPA throughput performancefrom network perspective but it is not intended for livenetwork performance verification purposes.





5.2.3.11 RAN logical interface data volume [Mbit]

Table 104. Iu-PS GTP total input traffic in RNC


30/04/2009


Table 104. Iu-PS GTP total input traffic in RNC (cont.)

KPI name Iu-PS GTP total input traffic in RNC

KPI abbreviation Iu-PS GTP tot inpTraf RNC

KPI ID RNC_5027a

KPI version 1.2u

Description The total GTP input traffic rate to RNC in Iu-PS interface.The traffic includes user and GTP control plane traffic. Thecounter INPUT_BYTES_TOTAL_UDP is input traffic tosingle GTPU in RNC. For the KPI it is needed to aggregateall the GTPU related counters up to RNC level.

Note 1 This KPI can be used to see the total throughput volume inIu-PS and compare the average value to definedperformance value. The performance requirement for RNCincludes the GTP headers, which are not included to thisKPI. In order to include the GTP headers the value ofINPUT_IP_PACKETS_TOTAL*8 (this is the amount of GTPheader bytes) should be added to the result. It should alsobe noted that the counter unit is 10 bytes and therefore themultiplication with 10 is included in the formula.


Note 3 This KPI works only in RNC s with GTPU units.

Measurement M801: Iu PS Performance measurement

KPI formula sum([M801C0])*10*8 / 1000000

KPI formula with short names sum([INPUT_BYTES_TOTAL_UDP])*10*8 / 1000000


Unit Mbit

Target values -

Object Summary Levels Network, RNC, BTS, LCG




5.2.3.12 RAN logical interface throughput [Mbit/s]

Table 105. Iu-PS GTP average input traffic rate in RNC

KPI name Iu-PS GTP average input traffic rate in RNC

KPI abbreviation Iu-PS GTP avg inpTraf RNC

KPI ID RNC_941b

DN05191189Issue 4-3 en draft30/04/2009



Table 105. Iu-PS GTP average input traffic rate in RNC (cont.)

KPI version 3.3u

Description The average GTP input traffic rate to RNC in Iu-PSinterface. The traffic includes user and GTP control planetraffic. The counter INPUT_BYTES_TOTAL_UDP is inputtraffic to single GTPU in RNC. For the KPI it is needed toaggregate all the GTPU related counters up to RNC level.

Note 1 This KPI can be used to see the total throughput volume inIu-PS and compare the average value to definedperformance value. The performance requirement for RNCincludes the GTP headers, which are not included to thisKPI. In order to include the GTP headers the value ofINPUT_IP_PACKETS_TOTAL*8 (this is the amount of GTPheader bytes) should be added to the result.


Note 3 This KPI works only in RNC s with GTPU units.

Measurement M801: Iu PS Performance measurement

KPI formula sum([M801C0])*10*8 / sum(PERIOD_DURATION)*1000000*60

KPI formula with short names sum([INPUT_BYTES_TOTAL_UDP])*10*8 / sum(PERIOD_DURATION)*1000000*60


Unit Mbps

Target values -





5.3 Transport Resource Manager level

5.3.1 Transport Resource Manager level indicators for accessibility




30/04/2009


5.3.1.1 Transmission Resource Accessibility Ratio [%]

Table 106. AAL2 connection reservation success rate

KPI name AAL2 connection reservation success rate

KPI abbreviation AAL2 conn reservation SR

KPI ID RNC_602a

KPI version 4.3u

Description The transport resource request success ratio [%]. This KPIdescribes the average success rate of the transportresource reservation attempts for AAL2 type connections.The low success rate increases the number of unsuccessfulRAB setups and requires further troubleshooting in transportlayer.

Measurement M800: AAL2 Resource Reservation Measurement

KPI formula 100* sum([M800C4]) / sum([M800C4] + [M800C5] +[M800C1] + [M800C2] + [M800C3])

KPI formula with short names 100* sum([AAL2_SUCCEEDED]) / sum([AAL2_SUCCEEDED] + [AAL2_REJECTED] +[RES_EXT_CAP] + [RES_INT_CAP] + [RES_OTHER])


Unit Percentage

Target values N/A (Not enough experience yet)

Object Summary Levels Network, RNC, VCC




Table 107. IP Route Accessibility for outgoing traffic

KPI name IP Route Accessibility for outgoing traffic

KPI abbreviation IP Route Acc out

KPI ID RNC_5005a

KPI version 1.2u

Description The transport resource request success ratio [%]. This KPIdescribes the average success rate of the transportresource reservation attempts for IP Route basedconnections every/selected interface where IP is used.

Measurement M804: IP CAC Accessibility

DN05191189Issue 4-3 en draft30/04/2009



Table 107. IP Route Accessibility for outgoing traffic (cont.)

KPI formula 100* sum([M804C0]) / sum([M804C0] + [M804C1] +[M804C2] + [M804C3])

KPI formula with short names 100* sum([SUCC_RNC_IP_RES]) / sum([SUCC_RNC_IP_RES] + [FAIL_RNC_IP_RES_EXT] +[FAIL_RNC_IP_RES_INT] + [FAIL_RNC_IP_RES_OTHER])


Unit Percentage

Target values -

Object Summary Levels Network, RNC, IP Route




Table 108. IP Route Accessibility for incoming iub traffic

KPI name IP Route Accessibility for incoming iub traffic

KPI abbreviation IP Route Acc Iub In

KPI ID RNC_5031a

KPI version 1.0u

Description The transport resource request success ratio [%]. This KPIdescribes the average success rate of the transportresource reservation attempts for IP Route basedconnections every/selected interface where IP is used.

Measurement M804: IP CAC Accessibility

KPI formula 100* sum([M804C4]) / sum([M804C4] + [M804C5] +[M804C6])

KPI formula with short names 100* sum([SUCC_BTS_IP_RES]) / sum([SUCC_BTS_IP_RES] +[FAIL_BTS_IP_RES_EXT_TRANS] +[FAIL_BTS_IP_RES_OTHER_TRANS])


Unit Percentage

Target values -





30/04/2009


Table 108. IP Route Accessibility for incoming iub traffic (cont.)


5.3.2 Transport Resource Manager level indicators for usage



5.3.2.1 Reserved AAL2 bandwidth [%]

Table 109. AAL2 path average reserved bandwidth

KPI name AAL2 path average reserved bandwidth

KPI abbreviation Alloc avg cap of CBR VCC

KPI ID RNC_601a

KPI version 4.4u

Description The ratio between average reserved bandwidth and totalbandwidth of AAL2 path estimated by CAC duringmeasurement period. The AAL2 path is an ATM VCCbetween two AAL type 2 entities. The high reservation levelmay cause blocking of radio bearer setup.

Measurement M550: AAL2 Path CAC Resource Measurement

KPI formula 100* sum([M550C1] / [M550C7]) / sum([M550C0])

KPI formula with short names 100* sum([SUM_RESERVED_CELL_RATE] /[NBR_SAMPLES]) / sum([AAL2_PATH_GUAR_CELL_RATE])


Unit Percentage

Target values Depends on Traffic and AAL2 capacity.

Object Summary Levels Network, RNC, VCC




DN05191189Issue 4-3 en draft30/04/2009



5.3.2.2 Reserved IP bandwidth [%]

Table 110. IP Route Egress Reservation Rate

KPI name IP Route Egress Reservation Rate

KPI abbreviation IP Route Egress rsv Rate

KPI ID RNC_5052a

KPI version 1.0u

Description This tells the reservation rate of guaranteed IP transportresources.

Measurement M568: IP Route

KPI formula 100 *(sum ([M568C3]/[M568C9]) / [M568C2]) -> 100 *(sum([M568C3]/[M568C9]) / sum[M568C2])

KPI formula with short names 100 *(sum ([SUM_RESERVED_RATE_IP_ROUTE]/[NBR_SAMPLES_IP_ROUTE]) / sum[COMMITTED_BIT_RATE_IP_ROUTE])


Unit %

Target values -





5.3.2.3 IP Based RAN logical Interface data volume [Mbit]

Table 111. Outgoing IP route traffic volume

KPI name Outgoing IP route traffic volume

KPI abbreviation Outg IP route traf vol

KPI ID RNC_5022a

KPI version 1.1u

Description Total outgoing data volume for IP based Traffic inControlling RNC for the reporting period for a selectedlogical interface. The outgoing Traffic includes all user planeand control plane traffic between RNC and BTS/neighbourRNC/CN (depends on what is the receiving NE).

Note The IP Route measurement doesn't include the related NEinformation in the object for other interface than Iub.


30/04/2009


Table 111. Outgoing IP route traffic volume (cont.)

Measurement M568: IP Route measurement


KPI formula with short names sum([OUT_DATA_IP_ROUTE])*8 / 1000


Unit Mbit

Target values -





Table 112. Incoming IP route traffic volume

KPI name Incoming IP route traffic volume

KPI abbreviation Inc IP route traf vol

KPI ID RNC_5029a

KPI version 1.1u

Description Total incoming data volume for IP based Traffic inControlling RNC for the reporting period for a selectedlogical interface. The incoming Traffic includes all user planeand control plane traffic between RNC and BTS/neighbourRNC/CN (depends what is the sending NE).

Note The IP Route measurement doesn't include the related NEinformation in the object for other interfaces than Iub.

Measurement M568: IP Route measurement


KPI formula with short names sum([IN_DATA_IP_ROUTE])*8 / 1000


Unit Mbit

Target values -





DN05191189Issue 4-3 en draft30/04/2009



5.3.2.4 ATM Based RAN logical Interface data volume [Mbit]

Table 113. ATM interface based incoming Data Volume (RNC side)

KPI name ATM interface based incoming Data Volume (RNC side)

KPI abbreviation ATM If ba inc DV RNCside

KPI ID RNC_946b

KPI version 2.3u

Description Total incoming data volume for ATM based Traffic inControlling RNC for the reporting period for a selectedlogical interface The incoming Traffic includes all user planeand control plane traffic between RNC and BTS/neighbourRNC/CN (depends what is the sending NE). In the caseO&M uses traffic dedicated VPC it can be left out ofmeasurement to increase the number of measured Iub links,see NOTE3.

Note 1 The ATM VP measurement doesn't include the related NEinformation in the object. It must be derived from anothersource.

Note 2 (In case of Iub interface measuring)! The use of this KPIrequires that there exist dedicated VP(s) between RNC andNodeB for the Iub links to be monitored. If several BTS sitesare sharing same VP in RNC end this KPI can not be usedto monitor Iub specific throughput.


Measurement M529: ATM VP Traffic Measurement


KPI formula with short names sum([IN_TOT_CELLS_VP])*53*8 / 1000000


Unit Mbit

Target values -





Table 114. ATM interface based outgoing Data Volume (RNC side)

KPI name ATM interface based outgoing Data Volume (RNC side)


30/04/2009


Table 114. ATM interface based outgoing Data Volume (RNC side) (cont.)

KPI abbreviation ATM If ba out DV RNC side

KPI ID RNC_945b

KPI version 2.3u

Description Total Outgoing data volume for ATM based Traffic inControlling RNC for the reporting period for a selectedlogical interface The outgoing Traffic includes all user planeand control plane traffic between RNC and BTS/neighbourRNC/CN (depends what is the sending NE). In the caseO&M uses traffic dedicated VPC it can be left out ofmeasurement to increase the number of measured Iub links,see NOTE3.






KPI formula with short names sum([EG_TOT_CELLS_VP])*53*8 / 1000000


Unit Mbit

Target values -





5.3.2.5 Average ATM layer throughput per RAN logical interface [Mbit/s]

Table 115. ATM interface based average throughput for outgoing traffic (RNCside)

KPI name ATM interface based average throughput for outgoing traffic(RNC side)

KPI abbreviation Iub DL avg thp (RNC side)

DN05191189Issue 4-3 en draft30/04/2009



Table 115. ATM interface based average throughput for outgoing traffic (RNCside) (cont.)

KPI ID RNC_950b

KPI version 2.3u

Description Average throughput for outgoing ATM based Traffic inControlling RNC for the reporting period for a selectedlogical interface The outgoing Traffic includes all user planeand control plane traffic between RNC and BTS/neighbourRNC/CN (depends what is the sending NE). In the caseO&M uses traffic dedicated VPC it can be left out ofmeasurement to increase the number of measured Iub links,see NOTE3.






KPI formula with short names sum([EG_TOT_CELLS_VP])*53*8 / sum(PERIOD_DURATION)*1000000*60


Unit Mbps

Target values -





Table 116. ATM interface based average throughput for incoming traffic (RNCside)

KPI name ATM interface based average throughput for incoming traffic(RNC side)

KPI abbreviation Iub UL avg thp (RNC side)


30/04/2009


Table 116. ATM interface based average throughput for incoming traffic (RNCside) (cont.)

KPI ID RNC_951b

KPI version 2.3u

Description Average throughput for incoming ATM based Traffic inControlling RNC for the reporting period for a selectedlogical interface The incoming Traffic includes all user planeand control plane traffic between RNC and BTS/neighbourRNC/CN (depends what is the sending NE). In the caseO&M uses traffic dedicated VPC it can be left out ofmeasurement to increase the number of measured Iub links,see NOTE3.






KPI formula with short names sum([IN_TOT_CELLS_VP])*53*8 / sum(PERIOD_DURATION)*1000000*60


Unit Mbps

Target values -





5.3.2.6 ATM layer traffic load [%]

Table 117. ATM VCC specific incoming traffic load

KPI name ATM VCC specific incoming traffic load

KPI abbreviation ATM VCC spec inc traf ld

DN05191189Issue 4-3 en draft30/04/2009



Table 117. ATM VCC specific incoming traffic load (cont.)

KPI ID RNC_960a

KPI version 1.1u

Description This KPI shows the incoming ATM layer traffic load forsingle ATM VC connection. The load is measured in RNCingress direction. It depends on the selected configuration,which traffic type utilises one VCC. The ATM VCC trafficthroughput is compared to the VCC PCR (in the case ofCBR connection) or MDCR (in the case of UBR+connection) to calculate the load [%]. If there is dedicatedVC connection used for HSDPA, this KPI can be used tofollow the HSDPA load over Iub and the same applies toother traffic types as well.

Note 1 If VCC is UBR type the MDCR or PCR value is alwaysreported as "0" and the calculation can not be done.

Note 2 If UBR+ is in use the KPI can give results over 100%.

Measurement M530: ATM VC Traffic Measurement

KPI formula 100* sum([M530C0]) / sum([M530C4]*PERIOD_DURATION)*60

KPI formula with short names 100* sum([IN_TOT_CELLS_VC]) / sum([IN_CAP_VC]*PERIOD_DURATION)*60

KPI class Usage/Transmission load

Unit Percentage






Table 118. ATM VCC specific outgoing traffic load

KPI name ATM VCC specific outgoing traffic load

KPI abbreviation ATM VCC traf load Iub DL

KPI ID RNC_732b

KPI version 3.3u

Description This KPI shows the outgoing ATM layer traffic load forsingle ATM VC connection. The load is measured in RNCegress direction. It depends on the selected configuration,which traffic type utilises one VCC. The ATM VCC trafficthroughput is compared to the VCC PCR (in the case of


30/04/2009


Table 118. ATM VCC specific outgoing traffic load (cont.)

CBR connection) or MDCR (in the case of UBR+connection) to calculate the load [%]. If there is dedicatedVC connection used for HSDPA, this KPI can be used tofollow the HSDPA load over Iub and the same applies toother traffic types as well.

Note 1 If VCC is UBR type the MDCR or PCR value is alwaysreported as "0" and the calculation can not be done.

Note 2 If UBR+ is in use the KPI can give results over 100%.

Measurement M530: ATM VC Traffic Measurement

KPI formula 100* sum([M530C1]) / sum([M530C7]*PERIOD_DURATION)*60

KPI formula with short names 100* sum([EG_TOT_CELLS_VC]) / sum([EG_CAP_VC]*PERIOD_DURATION)*60

KPI class Usage/Transmission load

Unit Percentage






5.4 Access point level

5.4.1 Access point level indicators for usage



5.4.1.1 Radio Load [dBm]

Table 119. Noise floor of the System

DN05191189Issue 4-3 en draft30/04/2009



Table 119. Noise floor of the System (cont.)

KPI name Noise floor of the System

KPI abbreviation Noise floor of the System

KPI ID RNC_177b

KPI version 6.4u

Description Average PrxNoise [dBm] of a cell over the reporting period.

Measurement M1000: Cell Resource

KPI formula avg([M1000C10])

KPI formula with short names avg([AVE_PRX_NOISE])

Formula note 1 When using the formula, linear scale has to be used withcalculations. This means that the dBm values in thecounters must be converted to Watts and after thecalculation is done, the result must be converted back todBms. It is possible that the counter in the formula is notupdated during the measurement period, that is, thedenominator counter is not updated. These samples shouldbe filtered out. The calculation must also include a divisionby - 100 in order to take out the raw counter unit valuemultiplication by -100.

Formula note 2 Pre-calculated values The counter M1000C10 alreadyshows the average dBm level. Therefore, the denomcounter M1000C11 is not used in the formula.

KPI class Usage/Radio Load

Unit -100.0*dBm

Target values < -102 dBm





Table 120. Average Uplink R99 Load

KPI name Average Uplink R99 Load

KPI abbreviation Avg UL R99 Load

KPI ID RNC_101b

KPI version 6.3u

Description Average received uplink power [dBm] shows the uplinkloading of a cell over the reporting period.


30/04/2009


Table 120. Average Uplink R99 Load (cont.)


KPI formula -112 + 0.1 *avg(sum( [M1000C0] * [M1000C1] + [M1000C2]* [M1000C3] + [M1000C4] * [M1000C5] + [M1000C6] *[M1000C7] + [M1000C8] * [M1000C9]) / sum([M1000C1] +[M1000C3] + [M1000C5] + [M1000C7] + [M1000C9]))

KPI formula with short names -112 + 0.1 *avg(sum( [AVE_PRXTOT_CLASS_0] *[PRXTOT_DENOM_0] + [AVE_PRXTOT_CLASS_1] *[PRXTOT_DENOM_1] + [AVE_PRXTOT_CLASS_2] *[PRXTOT_DENOM_2] + [AVE_PRXTOT_CLASS_3] *[PRXTOT_DENOM_3] + [AVE_PRXTOT_CLASS_4] *[PRXTOT_DENOM_4]) / sum([PRXTOT_DENOM_0] +[PRXTOT_DENOM_1] + [PRXTOT_DENOM_2] +[PRXTOT_DENOM_3] + [PRXTOT_DENOM_4]))

Formula note The counter values are given in standardised RSSI values(0-621). This means that the values must be converted todBm values (-112.1 - -50.0) before the KPI can becalculated. It is possible that the counter in the formula isnot updated during the measurement period, meaning thatthe denominator counter is not updated. These samplesshould be filtered out. When using the formula, linear scalehas to be used with calculations. This means that the dBmvalues in the counters must be converted to Watts and,after the calculation is done, the result must be convertedback to dBms.


Unit dBm

Target values Depends on PrxNoise and Traffic.





Table 121. Average HSUPA Uplink Load

KPI name Average HSUPA Uplink Load

KPI abbreviation Avg HSUPA UL Load

KPI ID RNC_1180a

KPI version 2.4u

Description Average received uplink power [dBm] for HSUPA of a cellover the reporting period.

DN05191189Issue 4-3 en draft30/04/2009



Table 121. Average HSUPA Uplink Load (cont.)

Measurement M5000: HSPA in WBTS


KPI formula with short names avg([HSUPA_UL_PWR_AVG])


Unit dBm

Target values -





Table 122. Average R99 Downlink Load

KPI name Average R99 Downlink Load

KPI abbreviation Avg DL R99 Load

KPI ID RNC_102b

KPI version 6.3u

Description Average transmitted downlink power [dBm] shows thedownlink loading of a cell over the reporting period. Thepower is purely related to R99 and no HSPA (HSDPA orHSUPA DL) power is included.


KPI formula avg( sum([M1000C14]*[M1000C15] + [M1000C16]*[M1000C17] + [M1000C18]*[M1000C19] + [M1000C20]*[M1000C21] + [M1000C22]*[M1000C23]) / sum([M1000C15]+ [M1000C17] + [M1000C19] + [M1000C21] + [M1000C23])/100)

KPI formula with short names avg( sum([AVE_PTXTOT_CLASS_0]*[PTXTOT_DENOM_0]+ [AVE_PTXTOT_CLASS_1]*[PTXTOT_DENOM_1] +[AVE_PTXTOT_CLASS_2]*[PTXTOT_DENOM_2] +[AVE_PTXTOT_CLASS_3]*[PTXTOT_DENOM_3] +[AVE_PTXTOT_CLASS_4]*[PTXTOT_DENOM_4]) / sum([PTXTOT_DENOM_0] + [PTXTOT_DENOM_1] +[PTXTOT_DENOM_2] + [PTXTOT_DENOM_3] +[PTXTOT_DENOM_4])/100)

Formula note When using the formula, linear scale has to be used withcalculations. This means that the dBm values in thecounters must be converted to Watts and, after thecalculation is done, the result must be converted back to


30/04/2009


Table 122. Average R99 Downlink Load (cont.)

dBms. It is possible that the counter in the formula is notupdated during the measurement period, meaning that thedenominator counter is not updated. These samples shouldbe filtered out. The calculation must also include a divisionby 100 in order to take out the raw counter unit valuemultiplication by 100.


Unit dBm

Target values Depends on Traffic





Table 123. Average HSPA Downlink Load

KPI name Average HSPA Downlink Load

KPI abbreviation Avg HSPA DL Load

KPI ID RNC_1181a

KPI version 2.4u

Description Average transmitted downlink power [dBm] for HSPA of acell over the reporting period.



KPI formula with short names avg([AVE_HSPA_DL_POWER])

Formula note When using the formula, linear scale has to be used withcalculations. This means that the dBm values in thecounters must be converted to Watts and, after thecalculation is done, the result must be converted back todBms.


Unit dBm

Target values -




DN05191189Issue 4-3 en draft30/04/2009



Table 123. Average HSPA Downlink Load (cont.)


5.4.1.2 Logical Resource Availability [%]

Table 124. Cell Availability

KPI name Cell Availability

KPI abbreviation Cell avail

KPI ID RNC_183c

KPI version 7.5u

Description The availability of the WCELLs under a Controlling RNC(CRNC).

Note 1 This KPI was changed in RAS05.1 due to new counters.

Note 2 This KPI tells the "user" point of view.



KPI formula with short names 100* sum([AVAIL_WCELL_IN_WO_STATE]) / sum([AVAIL_WCELL_EXISTS_IN_RNW_DB])


Unit Percentage






Table 125. Cell Availability, excluding blocked by user state (BLU)

KPI name Cell Availability, excluding blocked by user state (BLU)

KPI abbreviation Cell avail excl BLU

KPI ID RNC_727a

KPI version 3.4u

Description


30/04/2009


Table 125. Cell Availability, excluding blocked by user state (BLU) (cont.)

Cell Availability, excluding blocked by user state (BLU). TheKPI gives cell availability defined as the percentage of timethe cell(s) is in working state. This KPI shows specificallythe availability on times when the cell has not been BLU.


KPI formula 100* sum([M1000C178]) / sum([M1000C180] -[M1000C179])

KPI formula with short names 100* sum([AVAIL_WCELL_IN_WO_STATE]) / sum([AVAIL_WCELL_EXISTS_IN_RNW_DB] -[AVAIL_WCELL_BLOCKED_BY_USER])


Unit Percentage

Target values -





5.4.1.3 HW Resources [%]

Table 126. Average ratio of utilized CE for DL in BTS

KPI name Average ratio of utilized CE for DL in BTS

KPI abbreviation Avg R utilized CE DL BTS

KPI ID RNC_730a

KPI version 3.3u

Description Average ratio of utilized CE for DL in BTS [%].

Note The details of BTS CE usage and measuring of these aredescribed in the referred BTS counters document.

Measurement M5001: WBTS HW Resource Measurement


KPI formula with short names 100* sum([AVG_USED_CE_DL]) / sum([AVE_AVAIL_CE])

KPI class Usage/HW Resources

Unit Percentage

Target values Depends on Traffic and CE capacity.


DN05191189Issue 4-3 en draft30/04/2009



Table 126. Average ratio of utilized CE for DL in BTS (cont.)




Table 127. Average ratio of utilized CE for UL in BTS

KPI name Average ratio of utilized CE for UL in BTS

KPI abbreviation Avg R utilized CE UL BTS

KPI ID RNC_731a

KPI version 3.3u

Description Average ratio of utilized CE for UL in BTS [%].

Note The details of BTS CE usage and measuring of these aredescribed in the referred BTS counters document.

Measurement M5001: WBTS HW Resource Measurement


KPI formula with short names 100* sum([AVG_USED_CE_UL]) / sum([AVE_AVAIL_CE])


Unit Percentage

Target values Depends on Traffic and CE capacity.





The following KPIs (RNC_7001a and RNC_7005a) need to be used incase the whole network or an area of the network is based on NB/RSxxBTSs.

Table 128. The average license related uplink channel element usage ratio

KPI name The average license related uplink channel element usageratio

KPI abbreviation BB Usg License UL CE Mean

KPI ID RNC_7001a


30/04/2009


Table 128. The average license related uplink channel element usage ratio(cont.)

KPI version 1.0u

Description The average license related uplink channel element usageratio.

Measurement M92001: NodeB Resource

KPI formula avg([bbUsageRatioLicense_0_0])

KPI formula with short names avg([bbUsageRatioLicenseULCEMean])


Unit Percentage

Target values





Table 129. The average license related downlink channel element usage ratio

KPI name The average license related downlink channel elementusage ratio

KPI abbreviation BB Usg License DL CE Mean

KPI ID RNC_7005a

KPI version 1.0u

Description The average license related downlink channel elementusage ratio

Measurement M92001: NodeB Resource

KPI formula avg([bbUsageRatioLicense_2_0])

KPI formula with short names avg([bbUsageRatioLicenseDLCEMean])


Unit Percentage

Target values





DN05191189Issue 4-3 en draft30/04/2009



5.4.1.4 Radio layer (MAC or FP) Data Volumes [Mbit]

Table 130. HSDPA received data

KPI name HSDPA received data

KPI abbreviation HSDPA rcvd Data

KPI ID RNC_608b

KPI version 4.5u

Description Amount of data received in NodeB from the RNC in MAC-dPDUs.


KPI formula sum([M5000C126]) / 1000

KPI formula with short names sum([RECEIVED_HS_MACD_BITS]) / 1000


Unit Mbit

Target values Depends on Traffic and Iub capacity available for HSDPA.





The following KPI (RNC_5043a) needs to be used in case the wholenetwork or an area of the network is based on NB/RSxx BTSs.

Table 131. HSDPA MAC-d data volume at RNC

KPI name HSDPA MAC-d data volume at RNC

KPI abbreviation HSDPA DL vol SRNC side

KPI ID RNC_5043a

KPI version 1.0u

Description Total Data Volume for HSDPA Downlink Traffic [kbit/s] inServing RNC for the reporting period on Iub. The DownlinkTraffic includes HS-DSCH (MAC-hs) traffic.


KPI formula (([M1023C8]) *8) / 1 000 000

KPI formula with short names (([HS_DSCH_DATA_VOL]) *8) / 1 000 000


30/04/2009


Table 131. HSDPA MAC-d data volume at RNC (cont.)


Unit Mbit

Target values -





Table 132. Iub data volume DL in BTS

KPI name Iub data volume DL in BTS

KPI abbreviation Iub data vol DL in BTS

KPI ID RNC_5019a

KPI version 1.2u

Description Iub data volume in DL on BTS side for the reporting periodon Iub. The Downlink Traffic includes all Dedicated Channel(DCH) user plane + control plane FP payload (excluding FPheader data) traffic and HSDPA shared channel (HS-DSCH)FP payload (excluding FP header data) traffic between RNCand BTS.

Measurement M5003: Frame Protocol in WBTS

KPI formula sum([M5003C4] + [M5003C6] + [M5003C20])*8 / 1000

KPI formula with short names sum([CCH_DATA_FROM_IUB] + [DCH_DATA_FROM_IUB]+ [HSDSCH_DATA_FROM_IUB])*8 / 1000


Unit Mbit

Target values -





DN05191189Issue 4-3 en draft30/04/2009



Table 133. Iub data volume UL in BTS

KPI name Iub data volume UL in BTS

KPI abbreviation Iub data vol UL in BTS

KPI ID RNC_5020a

KPI version 1.2u

Description FP layer total Iub Throughput volume UL on BTS side forthe reporting period on Iub. The Uplink Traffic includes alluser plane and control plane FP payload (excluding FPheader data) traffic between RNC and BTS.

Measurement M5003: FP Layer in WBTS

KPI formula sum([M5003C3] + [M5003C5] + [M5003C7])*8 / 1000

KPI formula with short names sum([CCH_DATA_TO_IUB_INTERFACE] +[DCH_DATA_TO_IUB] + [EDCH_DATA_TO_IUB])*8 / 1000


Unit Mbit

Target values -





Table 134. HSDPA MAC-d data volume at BTS

KPI name HSDPA MAC-d data volume at BTS

KPI abbreviation HSDPA MAC-d DV at BTS

KPI ID RNC_739c

KPI version 2.3u

Description HSDPA MAC-d net throughput i.e.successfully deliveredMAC-d PDU data to HSDPA Capable UEs assuming thatMAC-hs is capable of delivering the PDUs.

Note 1 The MAC-hs is assumed to be capable of delivering allMAC-d PDUs to UEs.

Note 2 This KPI can be used to see the total HSDPA throughputper cell and compare the average value to definedperformance value.




30/04/2009


Table 134. HSDPA MAC-d data volume at BTS (cont.)

KPI formula sum([M5000C126]-[M5000C127]) / 1000

KPI formula with short names sum([RECEIVED_HS_MACD_BITS]-[DISCARDED_HS_MACD_BITS]) / 1000


Unit Mbit

Target values Depends on Traffic.KPI can be used to follow HSDPAthroughput.





5.4.1.5 Average Radio Layer (MAC) Throughput [Mbit/s]

Table 135. HSDPA MAC-d average net throughput at BTS

KPI name HSDPA MAC-d average net throughput at BTS

KPI abbreviation HSDPA MAC-d avg thp BTS

KPI ID RNC_606d

KPI version 5.3u

Description HSDPA MAC-d net throughput i.e.successfully deliveredMAC-d PDU data to HSDPA Capable UEs assuming thatMAC-hs is capable of delivering the PDUs.

Note 1 The MAC-hs is assumed to be capable of delivering allMAC-d PDUs to UEs.

Note 2 This KPI can be used to see the total HSDPA throughputper cell and compare the average value to definedperformance value.



KPI formula sum([M5000C126] - [M5000C127]) / sum(PERIOD_DURATION)*1000*60

KPI formula with short names sum([RECEIVED_HS_MACD_BITS] -[DISCARDED_HS_MACD_BITS]) / sum(PERIOD_DURATION)*1000*60


Unit Mbps

DN05191189Issue 4-3 en draft30/04/2009



Table 135. HSDPA MAC-d average net throughput at BTS (cont.)

Target values Depends on Traffic. KPI can be used to follow HSDPAthroughput.





5.4.1.6 Active Throughput [Mbit/s]

Table 136. Active HS-DSCH MAC-d throughput, network perspective

KPI name Active HS-DSCH MAC-d throughput, network perspective

KPI abbreviation Act HS-DSCH MAC-d thp NW

KPI ID RNC_722c

KPI version 2.5u

Description The average active HS-DSCH MAC-d throughput fromnetwork perspective calculated as the HSDPA MAC-dthroughput at BTS, divided by the active HS-DSCH timefrom the network perspective. The active time refers to thescheduled TTIs, i.e. when sending data. The throughput islooked at from MAC-d layer, i.e. how much MAC-d leveldata the HS-DSCH is able to successfully transfer to UEsusing the scheduled TTIs, so this considers also the MAC-hs efficiency.


KPI formula sum([M5000C126]-[M5000C127]) * 500 / sum([M5000C69] +[M5000C70] + [M5000C71] + [M5000C72] + [M5000C73] +[M5000C74]) * 1000

KPI formula with short names sum([RECEIVED_HS_MACD_BITS]-[DISCARDED_HS_MACD_BITS]) * 500 / sum([HS_SCCH_PWR_DIST_CLASS_0] +[HS_SCCH_PWR_DIST_CLASS_1] +[HS_SCCH_PWR_DIST_CLASS_2] +[HS_SCCH_PWR_DIST_CLASS_3] +[HS_SCCH_PWR_DIST_CLASS_4] +[HS_SCCH_PWR_DIST_CLASS_5]) * 1000


Unit Mbps

Target values See BTS Product Description for maximum HSDPA usersupported throughput


30/04/2009


Table 136. Active HS-DSCH MAC-d throughput, network perspective (cont.)





5.4.2 Access point level indicators for mobility



5.4.2.1 Soft Handover Success Rate [%]

Table 137. Soft Handover Success Ratio

KPI name Soft Handover Success Ratio

KPI abbreviation SHO SR

KPI ID RNC_195a

KPI version 6.3u

Description Soft Handover Success Rate means branch addition,branch deletion or branch replacement over the reportingperiod in the Source Cell of the Soft Handover. It iscompared how many successful Active set updates thereare compared to initial Addition/Replacement/Deletionrequests.

Note This formula is excluding periodical reports, which mightoccur if for example RNC is busy and cannot processimmediately initial request.


KPI formula 100* sum([M1007C15]+ [M1007C32]) / sum([M1007C10] +[M1007C11] + [M1007C12] + [M1007C27] + [M1007C28] +[M1007C29])

KPI formula with short names 100* sum([SUCC_UPDATES_ON_SHO_FOR_RT]+[SUCC_UPDATES_ON_SHO_FOR_NRT]) / sum([CELL_ADD_REQ_ON_SHO_FOR_RT] +[CELL_DEL_REQ_ON_SHO_FOR_RT] +

DN05191189Issue 4-3 en draft30/04/2009



Table 137. Soft Handover Success Ratio (cont.)

[CELL_REPL_REQ_ON_SHO_FOR_RT] +[CELL_ADD_REQ_ON_SHO_FOR_NRT] +[CELL_DEL_REQ_ON_SHO_FOR_NRT] +[CELL_REPL_REQ_ON_SHO_FOR_NRT])

KPI class Mobility

Unit Percentage






Table 138. Soft Handover Success Rate RT

KPI name Soft Handover Success Rate RT

KPI abbreviation Soft HO SR RT

KPI ID RNC_153b

KPI version 2.1u

Description Success rate for all started active set updates (addition,deletion, replacement), RT.

Note SHO attempt includes cases when UE has also anyadditional NRT service.


KPI formula 100 * sum( [M1007C15] ) / sum( [M1007C10] + [M1007C12]+ [M1007C11] )

KPI formula with short names 100 * sum( [SUCC_UPDATES_ON_SHO_FOR_RT] ) / sum([CELL_ADD_REQ_ON_SHO_FOR_RT] +[CELL_REPL_REQ_ON_SHO_FOR_RT] +[CELL_DEL_REQ_ON_SHO_FOR_RT] )

KPI class Mobility

Unit Percentage







30/04/2009


Table 139. Soft Handover Success Rate NRT

KPI name Soft Handover Success Rate NRT

KPI abbreviation Soft HO SR NRT

KPI ID RNC_191b

KPI version 2.1u

Description Success rate for all started active set updates (addition,deletion, replacement), NRT.

Note SHO attempt excludes cases when UE has also any RTservice.


KPI formula 100 * sum( [M1007C32] ) / sum( [M1007C27] + [M1007C29]+ [M1007C28] )

KPI formula with short names 100 * sum( [SUCC_UPDATES_ON_SHO_FOR_NRT] ) /sum( [CELL_ADD_REQ_ON_SHO_FOR_NRT] +[CELL_REPL_REQ_ON_SHO_FOR_NRT] +[CELL_DEL_REQ_ON_SHO_FOR_NRT] )

KPI class Mobility

Unit Percentage






5.4.2.2 HSPA Serving Cell Change Success Rate [%]

Table 140. HSDPA Serving Cell Change Success Rate

KPI name HSDPA Serving Cell Change Success Rate

KPI abbreviation HSDPA SCC SR

KPI ID RNC_733a

KPI version 3.4u

Description HSDPA Serving Cell Change Success Rate over thereporting period in the Source Cell.


DN05191189Issue 4-3 en draft30/04/2009



Table 140. HSDPA Serving Cell Change Success Rate (cont.)

KPI formula 100* sum([M1008C222] + [M1008C223]) / sum([M1008C213] + [M1008C214] + [M1008C215] +[M1008C216])

KPI formula with short names 100* sum([SCC_INTRA_BTS_SUCCESSFUL] +[SCC_INTER_BTS_SUCCESSFUL]) / sum([SCC_STARTED_CPICH_ECNO] +[SCC_STARTED_UL_SIR_ERROR] +[SCC_STARTED_ACTIVE_SET_UPD] +[SCC_STARTED_OTHER_REASON])

KPI class Mobility

Unit Percentage

Target values See System Program Report.





Table 141. HSUPA Serving Cell Change Success Rate

KPI name HSUPA Serving Cell Change Success Rate

KPI abbreviation HSUPA SCC SR

KPI ID RNC_918a

KPI version 2.5u

Description HSUPA Serving Cell Success Ratio [%] for the reportingperiod in the Source Cell of the Hard Handover.

Note The HSUPA Serving Cell Change are only done when theHSDPA Serving Cell Change is needed.


KPI formula 100* sum([M1008C240] + [M1008C241]) / sum([M1008C239])

KPI formula with short names 100* sum([EDCH_SCC_INTRA_BTS_SUCCESS] +[EDCH_SCC_INTER_BTS_SUCCESS]) / sum([EDCH_SCC_STARTED])

KPI class Mobility

Unit Percentage

Target values See System Program Report.



30/04/2009


Table 141. HSUPA Serving Cell Change Success Rate (cont.)




5.4.3 Access point level indicators for integrity



5.4.3.1 NRT Retransmission Ratio [%]

Table 142. NRT DCH DL Efficiency

KPI name NRT DCH DL Efficiency

KPI abbreviation NRT DCH DL Efficiency NW

KPI ID RNC_5035a

KPI version 1.0u

Description The efficiency of selected Background Radio Bearers inDownlink using DCH. The bit rate of once transmittedbackground RLC PDUs divided by the bit rate of alltransmitted background RLC PDUs.

Measurement M1026 RCPM RLC WCEL

KPI formula 100* avg(All NRT DCHs([M1026C15] / [M1026C12]))

KPI formula with short names 100* avg(All NRT DCHs([RLC_AM_PDU_DL_NET_TP_W] /[RLC_AM_PDU_DL_GR_TP_W]))

KPI class Integrity/Error rates

Unit Percentage

Target values Depends on the BLER target of the service





DN05191189Issue 4-3 en draft30/04/2009



Table 143. HSDPA MAC-hs efficiency

KPI name HSDPA MAC-hs efficiency

KPI abbreviation HSDPA MAC-hs efficiency

KPI ID RNC_607c

KPI version 4.3u

Description HSDPA Successful transmission ratio i.e. efficiency ofHSDPA data transmission between BTS and HSDPACapable UEs done by MAC-hs. Based on successfully sentMAC-hs PDUs divided by totally sent MAC-hs PDUs. (Totalnumber of all successful sent MAC-hs PDUs divided bytotal number of all transmitted MAC-hs PDUs (includingretransmissions)).


KPI formula 100* sum([M5000C0] + [M5000C1] + [M5000C2] +[M5000C3] + [M5000C4] + [M5000C5]) / sum([M5000C49] +[M5000C50] + [M5000C51] + [M5000C52] + [M5000C53] +[M5000C86] + [M5000C87] + [M5000C88] + [M5000C89] +[M5000C90] + [M5000C91] + [M5000C92] + [M5000C93] +[M5000C94] + [M5000C95] + [M5000C54] + [M5000C55] +[M5000C56] + [M5000C57] + [M5000C58] + [M5000C96] +[M5000C97] + [M5000C98] + [M5000C99] + [M5000C100] +[M5000C101] + [M5000C102] + [M5000C103] +[M5000C104] + [M5000C105] + [M5000C59] + [M5000C60]+ [M5000C61] + [M5000C62] + [M5000C63] + [M5000C106]+ [M5000C107] + [M5000C108] + [M5000C109] +[M5000C110] + [M5000C111] + [M5000C112] +[M5000C113] + [M5000C114] + [M5000C115] + [M5000C64]+ [M5000C65] + [M5000C66] + [M5000C67] + [M5000C68]+ [M5000C116] + [M5000C117] + [M5000C118] +[M5000C119] + [M5000C120] + [M5000C121] +[M5000C122] + [M5000C123] + [M5000C124] +[M5000C125])

KPI formula with short names 100* sum([MAC_HS_PDU_RETR_DIST_CL_0] +[MAC_HS_PDU_RETR_DIST_CL_1] +[MAC_HS_PDU_RETR_DIST_CL_2] +[MAC_HS_PDU_RETR_DIST_CL_3] +[MAC_HS_PDU_RETR_DIST_CL_4] +[MAC_HS_PDU_RETR_DIST_CL_5]) / sum([ORIG_TRANS_1_CODE_QPSK] +[ORIG_TRANS_2_CODE_QPSK] +[ORIG_TRANS_3_CODE_QPSK] +[ORIG_TRANS_4_CODE_QPSK] +[ORIG_TRANS_5_CODE_QPSK] +[ORIG_TRANS_6_CODE_QPSK] +[ORIG_TRANS_7_CODE_QPSK] +[ORIG_TRANS_8_CODE_QPSK] +[ORIG_TRANS_9_CODE_QPSK] +


30/04/2009


Table 143. HSDPA MAC-hs efficiency (cont.)

[ORIG_TRANS_10_CODE_QPSK] +[ORIG_TRANS_11_CODE_QPSK] +[ORIG_TRANS_12_CODE_QPSK] +[ORIG_TRANS_13_CODE_QPSK] +[ORIG_TRANS_14_CODE_QPSK] +[ORIG_TRANS_15_CODE_QPSK] +[ORIG_TRANS_1_CODE_16QAM] +[ORIG_TRANS_2_CODE_16QAM] +[ORIG_TRANS_3_CODE_16QAM] +[ORIG_TRANS_4_CODE_16QAM] +[ORIG_TRANS_5_CODE_16QAM] +[ORIG_TRANS_6_CODE_16QAM] +[ORIG_TRANS_7_CODE_16QAM] +[ORIG_TRANS_8_CODE_16QAM] +[ORIG_TRANS_9_CODE_16QAM] +[ORIG_TRANS_10_CODE_16QAM] +[ORIG_TRANS_11_CODE_16QAM] +[ORIG_TRANS_12_CODE_16QAM] +[ORIG_TRANS_13_CODE_16QAM] +[ORIG_TRANS_14_CODE_16QAM] +[ORIG_TRANS_15_CODE_16QAM] +[RETRANS_1_CODE_QPSK] +[RETRANS_2_CODE_QPSK] +[RETRANS_3_CODE_QPSK] +[RETRANS_4_CODE_QPSK] +[RETRANS_5_CODE_QPSK] +[RETRANS_6_CODE_QPSK] +[RETRANS_7_CODE_QPSK] +[RETRANS_8_CODE_QPSK] +[RETRANS_9_CODE_QPSK] +[RETRANS_10_CODE_QPSK] +[RETRANS_11_CODE_QPSK] +[RETRANS_12_CODE_QPSK] +[RETRANS_13_CODE_QPSK] +[RETRANS_14_CODE_QPSK] +[RETRANS_15_CODE_QPSK] +[RETRANS_1_CODE_16QAM] +[RETRANS_2_CODE_16QAM] +[RETRANS_3_CODE_16QAM] +[RETRANS_4_CODE_16QAM] +[RETRANS_5_CODE_16QAM] +[RETRANS_6_CODE_16QAM] +[RETRANS_7_CODE_16QAM] +[RETRANS_8_CODE_16QAM] +[RETRANS_9_CODE_16QAM] +[RETRANS_10_CODE_16QAM] +[RETRANS_11_CODE_16QAM] +[RETRANS_12_CODE_16QAM] +[RETRANS_13_CODE_16QAM] +[RETRANS_14_CODE_16QAM] +[RETRANS_15_CODE_16QAM])


DN05191189Issue 4-3 en draft30/04/2009



Table 143. HSDPA MAC-hs efficiency (cont.)

Unit Percentage

Target values Depends on radio conditions






Table 144. The average ratio of not acknowledged HARQ processes

KPI name The average ratio of not acknowledged HARQ processes

KPI abbreviation HARQ Non-Ack Ratio Mean

KPI ID RNC_7063a

KPI version 1.0u

Description The average ratio of non-acknowledged HARQ processes

Measurement M92003: NodeB HSDPA

KPI formula avg([hsNackRatio_0])

KPI formula with short names avg([hsNackRatioMean])


Unit Percentage

Target values





5.4.3.2 Block Error Ratio (BLER) [%]

Table 145. Voice RB UL BLER

KPI name Voice RB UL BLER

KPI abbreviation Voice RB UL BLER NW


30/04/2009


Table 145. Voice RB UL BLER (cont.)

KPI ID RNC_5037a

KPI version 1.0u

Description The measured Block Error Rate for Voice Radio Bearers inUplink.

Note 1 Allowed RCPM parameters must be given (SHO related) =>All active set sizes allowed. If one cell is problematic, andfurther information is needed from that cell, then it ispossible to set active set size to 1. This KPI measures onlyA DCH (for example, AMR 12.2 has 3 coordinated DCHs:A, B, and C).

Measurement M1025 RCPM OLPC RNC

KPI formula 100* avg( sum of AMR RBs([M1025C5]) / sum([M1025C5]+[M1025C4]) )

KPI formula with short names 100* avg( sum of AMR RBs([UL_CRC_NOKS_R]) / sum([UL_CRC_NOKS_R]+ [UL_CRC_OKS_R]) )


Unit Percentage






Table 146. Real Time Radio Bearer (AMR excluded) UL BLER

KPI name Real Time Radio Bearer (AMR excluded) UL BLER

KPI abbreviation RT RB UL BLER NW

KPI ID RNC_5036a

KPI version 1.0u

Description The measured Block Error Rate for Conversational Class(AMR excluded) and Streaming Radio Bearers in Uplink.

Measurement M1025 RCPM OLPC WCEL

KPI formula 100* avg( (sum of Conversational (AMR excluded) RBs([M1025C5]) + sum of Streaming RBs ([M1025C5])) / (sumof Conversational (AMR excluded) RBs ([M1025C5] +[M1025C4]) + sum of Streaming RBs([M1025C5]+[M1025C5])) )

DN05191189Issue 4-3 en draft30/04/2009



Table 146. Real Time Radio Bearer (AMR excluded) UL BLER (cont.)

KPI formula with short names 100* avg( (sum of Conversational (AMR excluded) RBs([UL_CRC_NOKS_R]) + sum of Streaming RBs([UL_CRC_NOKS_R])) / (sum of Conversational (AMRexcluded) RBs ([UL_CRC_NOKS_R] + [UL_CRC_OKS_R])+ sum of Streaming RBs([UL_CRC_NOKS_R]+[UL_CRC_NOKS_R])) )


Unit Percentage






Table 147. Non Real Time Radio Bearer UL BLER

KPI name Non Real Time Radio Bearer UL BLER

KPI abbreviation NRT RB UL BLER NW

KPI ID RNC_5034a

KPI version 1.0u

Description The measured Block Error Rate for Interactive Class andBackground Class Radio Bearers in Uplink.

Measurement M1025 RCPM OLPC RNC

KPI formula 100* avg( (sum of Interactive RBs([M1025C5]) + sum ofBackground RBs([M1025C5])) / (sum of Interactive RBs([M1025C5]+ [M1025C4]) + sum of Background RBs([M1025C5]+ [M1025C4])) )

KPI formula with short names 100* avg( (sum of Interactive RBs([UL_CRC_NOKS_R]) +sum of Background RBs([UL_CRC_NOKS_R])) / (sum ofInteractive RBs([UL_CRC_NOKS_R]+ [UL_CRC_OKS_R]) +sum of Background RBs([UL_CRC_NOKS_R]+[UL_CRC_OKS_R])) )


Unit Percentage





30/04/2009


Table 147. Non Real Time Radio Bearer UL BLER (cont.)



Table 148. HSUPA MAC-es BLER

KPI name HSUPA MAC-es BLER

KPI abbreviation HSUPA MAC-es BLER

KPI ID RNC_917a

KPI version 2.6u

Description The measured Block Error Rate for HSUPA Radio Bearersin Uplink. Block Error Rate calculated based on HARQ firstand successful transmissions compared to all successfultransmissions and failed transmissions.

Measurement M1016: RCPM OLPC

KPI formula 100-100* sum([M5000C128]) / sum([M5000C128] +[M5000C129] + [M5000C130] + [M5000C131] +[M5000C132] + [M5000C133] + [M5000C134] +[M5000C135] + [M5000C136] + [M5000C137] +[M5000C138] + [M5000C139] + [M5000C140] +[M5000C142])

KPI formula with short names 100-100* sum([MACE_PDU_RETR_00_COUNTER]) / sum([MACE_PDU_RETR_00_COUNTER] +[MACE_PDU_RETR_01_COUNTER] +[MACE_PDU_RETR_02_COUNTER] +[MACE_PDU_RETR_03_COUNTER] +[MACE_PDU_RETR_04_COUNTER] +[MACE_PDU_RETR_05_COUNTER] +[MACE_PDU_RETR_06_COUNTER] +[MACE_PDU_RETR_07_COUNTER] +[MACE_PDU_RETR_08_COUNTER] +[MACE_PDU_RETR_09_COUNTER] +[MACE_PDU_RETR_10_COUNTER] +[MACE_PDU_RETR_11_COUNTER] +[MACE_PDU_RETR_12_COUNTER] +[MACE_PDU_HARQ_FAIL_COUNTER])


Unit Percentage


Object Summary Levels Network, City, Area, RNC, Cluster of cells, Cell, RB



DN05191189Issue 4-3 en draft30/04/2009



Table 148. HSUPA MAC-es BLER (cont.)



Table 149. HSUPA HARQ not acknowledged Ratio

KPI name HSUPA HARQ not acknowledged Ratio

KPI abbreviation E-DCH HARQ Non-Ack Ratio

KPI ID RNC_7070a

KPI version 1.0u

Description HSUPA Hybrid Automatic Repeat Request (HARQ) notacknowledged Ratio.

Measurement M92004: NodeB HSUPA

KPI formula 100* avg( [edchHarqRetr_0_0] / ([edchHarqRetr_0_0] +[edchHarqRetr_1_0]) )

KPI formula with short names 100* avg( [edchHarqRetrMean] / ([edchHarqRetrMean] +[edchHarqRetrRecPDUMean]) )


Unit Percentage

Target values





Table 150. Voice RB DL BLER

KPI name Voice RB DL BLER

KPI abbreviation Voice RB DL BLER

KPI ID RNC_5023a

KPI version 2.4u

Description The measured Block Error Rate for AMR Radio Bearers inDownlink.

Measurement M1018: RCPM UEQ


30/04/2009


Table 150. Voice RB DL BLER (cont.)

KPI formula 100* sum (AMR RBs [M1018C0])

KPI formula with short names 100* sum (AMR RBs [UEQ_AVE_BLER])


Unit Percentage






Table 151. Real Time Radio Bearer (AMR excluded) DL BLER

KPI name Real Time Radio Bearer (AMR excluded) DL BLER

KPI abbreviation RT Radio Bearer DL BLER

KPI ID RNC_5024a

KPI version 2.4u

Description The measured Block Error Rate for Conversational Class(AMR excluded) and Streaming Radio Bearers in Downlink.

Measurement M1018: RCPM UEQ

KPI formula 100* sum( sum of Conversational (AMR excluded) RBs[M1018C0]) + sum of CS Streaming RBs [M1018C0])

KPI formula with short names 100* sum( sum of Conversational (AMR excluded) RBs[UEQ_AVE_BLER]) + sum of CS Streaming RBs[UEQ_AVE_BLER])


Unit Percentage

Target values -





DN05191189Issue 4-3 en draft30/04/2009



Date post:	10-Feb-2017
Category:	Documents
Upload:	emerson-eduardo-rodrigues-pmp
View:	524 times
Download:	15 times

50642889 kpi

Documents