3 g ran kpi document

3G RAN Key Performance Indicators

DN00279399 Issue 0.5 Draft

© Nokia Oyj

1 (62)


The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is not an official customer document and Nokia Networks does not take responsibility for any errors or omissions in this document. No part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia Networks. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia Networks and the customer.

Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. UNDER NO CIRCUMSTANCES SHALL NOKIA BE RESPONSIBLE FOR ANY LOSS OF USE, DATA, OR INCOME, COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, PROPERTY DAMAGE, PERSONAL INJURY OR ANY SPECIAL, INDIRECT, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES HOWSOEVER CAUSED.

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

This document and the product it describes are considered protected by copyright according to the applicable laws.

NOKIA and Nokia Connecting People are registered trademarks of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2004. All rights reserved. Reproduction, transfer, distribution or storage of part or all of the contents in this document in any form without the prior written permission of Nokia is prohibited.

2 (62) © Nokia Oyj

DN00279399Issue 0.5 Draft

Contents

Contents

1 Introduction ..........................................................................................6 1.1 The structure of listed Key Performance Indicators ................................6 1.2 Viewpoints of the Key Performance Indicators .......................................6 1.2.1 KPI classification ....................................................................................7 1.2.2 Network or user KPI ...............................................................................7 1.2.3 Summary of KPI viewpoints....................................................................8 1.3 Call Setup Success Rates (CSSR).........................................................9

2 Defined targets for WCDMA RAN Key Performance Indicators............................................................................................11

3 Available Key Performance Indicators in RAN1.5............................16 3.1 High Level Indicators for Accessibility...................................................16 3.1.1 RRC Setup and Access Complete Ratio [%] ........................................16 3.1.2 RAB Setup and Access Complete Ratio, Voice [%] ..............................18 3.1.3 RAB Setup and Access Complete Ratio, RT Service Other

Than Voice [%].....................................................................................18 3.2 High Level Indicators for Retainability...................................................19 3.2.1 RRC Drop Ratio [%] .............................................................................19 3.2.2 RAB Drop Ratio, Voice [%]...................................................................20 3.2.3 RAB Drop Ratio, RT Services Other Than Voice [%]............................21 3.2.4 RAB Drop Ratio, NRT Services [%]......................................................23 3.3 High Level Indicators for Usage............................................................24 3.3.1 Cell Availability [%] ...............................................................................24 3.3.2 Average Uplink Load [dBm]..................................................................24 3.3.3 Average Downlink Load [dBm] .............................................................26 3.3.4 Average RACH Throughput [kbit/s] ......................................................27 3.3.5 Average FACH Throughput [kbit/s].......................................................28 3.3.6 Average PCH Throughput [kbit/s] .........................................................28 3.4 High Level Indicators for Mobility..........................................................29 3.4.1 Soft Handover Overhead [%]................................................................29

4 Available Key Performance Indicators in RAN04.............................31 4.1 High Level Indicators for Accessibility...................................................31 4.1.1 RRC Setup and Access Complete Ratio [%] ........................................31 4.1.2 RAB Setup and Access Complete Ratio, NRT Services [%] .................32 4.1.3 RAB Setup and Access Complete Ratio, Multi RAB Services

[%]........................................................................................................33 4.1.4 LCS Setup [%]......................................................................................36 4.2 High Level Indicators for Retainability...................................................37 4.2.1 RRC Drop Ratio [%] .............................................................................37 4.2.2 RAB Drop Ratio, Voice [%]...................................................................39 4.2.3 RAB Drop Ratio, RT Services Other Than Voice [%]............................41 4.2.4 RAB Drop Ratio, NRT Services [%]......................................................44

4.3 High Level Indicators for Usage............................................................49 4.2.5 RAB Drop Ratio, Multi RAB Services [%] .............................................45


© Nokia Oyj

3 (62)


4.3.1 Noise floor of the System [dBm] ...........................................................49 4.3.2 Average SAB Throughput [kbit/s]..........................................................50 4.3.3 Allocated UL Dedicated Channel Capacity [kbit/s] ................................51 4.3.4 Allocated DL Dedicated Channel Capacity [kbit/s] ................................53 4.4 High Level Indicators for Mobility ..........................................................56 4.4.1 Soft Handover Success Rate [%]..........................................................56 4.4.2 Soft Handover Overhead [%]................................................................56 4.4.3 Intra System Hard Handover Success Ratio [%]...................................57 4.4.4 Inter System Hard Handover Success Ratio [%]...................................58

4 (62) © Nokia Oyj


Summary of changes

Summary of changes This is the fifth draft issue of this document.


© Nokia Oyj

5 (62)


IntroductionThis document defines various Key Performance Indicators (KPIs) for Nokia 3G Networks. The main focus is on formulas. However, some numerical target values for KPIs are listed.

Currently only Radio Access Network KPIs are covered.

The document includes the following chapters:

• Introduction

• Targets of the KPIs

• RAN1.5 KPIs

• RAN04 KPIs (new and modified KPIs from earlier RAN releases)

• Appendices (KPI template)

• References

NOTE! Some of the KPIs are not yet available in our official reporting tools. These are marked separately in each KPI description.

1.1 The structure of listed Key Performance Indicators

All listed items for each KPI are based on a common template. The template is found in Appendix A.

1.2 Viewpoints of the Key Performance Indicators

When creating KPIs the following issues have been considered:

• What is the common classification of each KPI

6 (62) © Nokia Oyj


Introduction

• Does the KPI indicate the Network or User view of the calculated outcome

• What should each KPI tell the operator

• What kind of target values can there be for each KPI

1.2.1 KPI classification

The KPIs follow the commonly used classification:

• Accessibility

• Retainability

• Usage

• Mobility

• Integrity

The classification is visible in subchapters for a KPI Class for each release. Each KPI description also includes the KPI Class. Inside the class there can be certain KPIs that include an additional classification:

Usage • Resource availability based KPIs

• Resource allocation KPIs

• Load based KPIs

• Throughput based KPIs

Mobility • KPI is related to the Source and/or Target Cell

1.2.2 Network or user KPI

In order to distinguish if the KPI indicates the network or user viewpoint, the following information is added to the KPI definition:

• KPI IDs ending with an A means that the KPI is created from the user viewpoint for example RAN_KPI_0001A


© Nokia Oyj

7 (62)


1.2.3 Summary of KPI viewpoints

The following picture illustrates the items described in Chapter 1.2:

RAN_KPI containing A = USER KPIsKPI Class

Accessibility

Retainability

Mobility

Integrity

Usage

Retainability

Accessibility

KPI Class RAN_KPI = NETWORK KPIs

RRC signaling related to a UE

L3 signaling related to a UE

L3 Signaling Measurements

RRC Signaling Measurement

KPI Outcome

RAB Success orFailure Rate


HO Success orFailure Rate

RB Quality

RB AllocationsCell Traffic/Power



Source Cell

Target Cell

AvailabilityLoad

AllocationsThroughput

LCS [7]

Service Level [2]

PC related to a UE

HC related to a UE

PS, RM related to a UE

Intra System HHO [4], Soft HO [5], Inter System HHO [6]

Cell Resource [1] Traffic [3]

Service Level [2]

LCS [7]

Radio Connection Performance

Figure 1. Summary of KPI Viewpoints

The picture includes the viewpoints previously described in the introduction chapter:

• To the left: The classification of the KPIs (KPI Class)

• In the middle: The separation of the user and network defined KPIs (RAN_KPI vs. RAN_KPI_xxx_A)

8 (62) © Nokia Oyj


Introduction

• To the right: What each KPI should indicate (KPI Outcome)

The pyramids illustrate:

• The upper pyramid: RAN functionalities and related RAN statistical measurements from the user equipment (UE) perspective.

• The lower (reversed) pyramid: RAN functionalities and related RAN statistical measurements from the network perspective.

RAN measurements are listed inside the pyramids. The KPIs are based on the counters found in the RAN measurements. The reference mark for a measurement, for example Cell Resource [1] indicates that a KPI(s) has been defined for the measurement. The KPI with the required information is described in this document, but the counter (and detailed measurement) description is found in the given reference document.

• The amounts of the statistical data related to the defined KPIs (and classes)

− When you go down the pyramid the number of data increases (there are more bricks in a pyramid in the lower layers than in the upper layers)

• The importance of each KPI (class)

− The tops of the pyramids represent the most essential data (the top layers of a pyramid becomes visible before the lower layers)

• The contradictions inside the KPI classes (the different angles to a pyramid layer)

− Usage

− The availability of resources vs. the allocations of the available resources

− The load of allocated resources vs. the gain (=throughput)

− Mobility

− The HO in the Source Cell vs. the Target Cell

1.3 Call Setup Success Rates (CSSR)

In the GSM world, the Call Setup Success Rates (CSSR) are the most followed up KPIs. It is natural to think that this is the same in the WCDMA world. But when we move to WCDMA, the call setup is not done exactly the same way as in GSM.


© Nokia Oyj

9 (62)


In GSM, the UE first seizes the SDDCH channel and after that – if the user needs to establish a call – the network allocates a TCH channel for the user and the call can be established.

Therefore, in GSM we are able to calculate the CSSR based upon the moment that the network starts to allocate a TCH (or more than one) for call establishment. The reason is that we know that every time we start to allocate a TCH we know that a call setup starts.

In WCDMA, the UE asks for an RRC channel and after that the network sends the RRC configuration to the UE. After the UE has successfully established the RRC connection, further signalling can take place. Depending on the received RRC setup cause, the network expects a call establishment (=RAB) next.

Therefore, in WCDMA we are not able to calculate the CSSR reliably. The reason is that an RRC can be asked for a cause (for example, registration) that does not specify everything what will happen. Therefore, if the UE asks the RRC for the registration cause it is possible that during the time the RRC is up the user decides to start a call. When the RRC is up and running, the call request is going in the NAS (Non Access Stratum) layer which is not visible to RAN part of the 3G network.

10 (62) © Nokia Oyj


Defined targets for WCDMA RAN Key Performance Indicators


Tables 1 and 2 (RAN 1.5 and RAN04 Key Performance Indicators) contain a summary of the current understanding of KPIs to be followed in 3G RAN. The KPI development work is still ongoing, and the finalisation of used formulas and their target values can be done only with practical knowledge of the 3G networks and measured performance data.

It should be noted that the listed targets are not Nokia guarantee values. Any change in measurements, calculation formula and/or used counters will effect to the listed goals.

This document does not cover network acceptance targets. If a KPI listed in this document is part of an acceptance agreement, the acceptance target for the KPI depends on the acceptance agreement.

The performance goals in the table below are the average goals for a cell cluster. The performance of individual cells may differ from the listed values.

The KPIs listed in the table are explained separately in corresponding subchapters.

Note 1: The listed targets are obsolete if and when the load in the network is too low. The load is considered to be too low if the average number of calls per cell is lower than 300 calls during busy hour.

Note 2: The listed targets are obsolete if and when the load in the network is higher than the planned target load of the network or if the actual traffic mix differs considerably from the planned assumptions.


© Nokia Oyj

11 (62)


Table 1. RAN 1.5 Key Performance Indicators

KPI ID KPI Class Indicates Live Network Target

RAN_KPI_0001 Accessibility (Network)

RRC Accessibility Rates

> 97 %

RAN_KPI_0001A Accessibility (User)

RRC Accessibility Rates

N/A

(some of the counters are not available at the document delivery)

RAN_KPI_0002 Accessibility RAB (AMR) Accessibility Rates

> 98.5 %

RAN_KPI_0003 Accessibility RAB (RT) Accessibility Rates

> 98 %

RAN_KPI_0004 Accessibility RAB (NRT) Accessibility Rates

> 98 %

RAN_KPI_0005 Retainability (Network)

(drop rate)

RRC Retainability Rates

N/A (Use RAB Retainability instead)


(drop rate)

RAB (AMR) Retainability Rates

< 4 %


(drop rate)

RAB (RT) Retainability Rates

< 4 %

RAN_KPI_0008 Retainability

(drop rate)

RAB (NRT) Retainability Rates

< 4 %

RAN_KPI_0009 Usage Total Uplink Inteference

N/A (depends on PrxNoise and Traffic)




RAN_KPI_0010 Usage Total Downlink Power

N/A (depends on Traffic)

RAN_KPI_0011 Usage RACH Throughput

Depends on Traffic and CCH capacity.

RAN_KPI_0012 Usage FACH Throughput

Depends on Traffic and CCH capacity.

RAN_KPI_0013 Usage PCH Throughput Depends on Traffic and CCH capacity.

RAN_KPI_0018 Usage WCELL Availability

> 99 %

RAN_KPI_0019 Mobility Soft Handover Overhead for One Cell

40 % (Average AS size = 1.4)

Table 2. RAN04 Key Performance Indicators

KPI ID KPI Class Indicates Live Network Target

RAN_KPI_0026 Accessibility MultiRAB (AMR+NRT) Accessibility Rates

N/A (Not enough experience yet)

RAN_KPI_0027 Accessibility MultiRAB (RT+NRT) Accessibility Rates


RAN_KPI_0028 Accessibility MultiRAB (NRT+NRT) Accessibility Rates


RAN_KPI_0005 Retainability (Network) (drop rate)




© Nokia Oyj

13 (62)


RAN_KPI_0005A Retainability (User) (drop rate)





N/A (Use the 0006A KPI instead)



< 4 %



N/A (Use the 0007A KPI instead)



< 4 %

RAN_KPI_0008 Retainability (drop rate)

RAB (NRT) Retainability Rates

< 4 %


MultiRAB (AMR+NRT) Retainability Rates



MultiRAB (RT+NRT) Retainability Rates



MultiRAB (NRT+NRT) Retainability Rates


RAN_KPI_0032 Usage Noise floor of the System

<

-102 dBm

RAN_KPI_0014 Usage Allocated Uplink Dedicated Channel Capacity for CS Voice

Depends on Traffic and DCH capacity.

RAN_KPI_0015 Usage Allocated Downlink Dedicated

Depends on Traffic and DCH




Channel Capacity for CS Voice

capacity.

RAN_KPI_0016 Usage Allocated Uplink Dedicated Channel Capacity for Data Calls


RAN_KPI_0017 Usage Allocated Downlink Dedicated Channel Capacity for Data Calls


RAN_KPI_0025 Usage SAB Throughput N/A (Not enough experience yet)

RAN_KPI_0020 Mobility Soft Handover Success Rate

> 98 %

RAN_KPI_0021 Mobility Intra System Hard Handover Success Rate


RAN_KPI_0022 Mobility Inter System Hard Handover Success Rate



© Nokia Oyj

15 (62)


Available Key Performance Indicators in RAN1.5

3.1 High Level Indicators for Accessibility

3.1.1 RRC Setup and Access Complete Ratio [%]

KPI NAME: RRC Setup and Access Complete Ratio from the network point of view

Published: 20.04.2004

KPI ID: RAN_KPI_0001

KPI version: 1.0u

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

This KPI is based on Service Level Measurement [2].

Note 1: RRC connection is needed also for other purposes than a call (SMS, LU, Detach, etc.).

KPI Formula:

% M1001C0) ( sumM1001C8) ( sum *100

KPI Class: Accessibility

Target values: See Chapter 2.




Object Summary Levels: Cell, Cluster of Cells, RNC, City, and Network.

Object Summary Level notes:

Time Summary Levels: Hour, Day, Week.

Time Summary Level notes:

KPI NAME: RRC Setup and Access Complete Ratio from end user perspective


KPI ID: RAN_KPI_0001A

KPI version: 1.0u




KPI Formula:

% M1001C241)-M1001C242-M1001C0 ( sum

M1001C8) ( sum *100








© Nokia Oyj

17 (62)


3.1.2 RAB Setup and Access Complete Ratio, Voice [%]

KPI NAME: RAB Setup and Access Complete Ratio for AMR Voice


KPI ID: RAN_KPI_0002.

KPI version: 1.0u

Description: RAB Setup and Access Complete Ratio [%] for voice calls over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).


Note 1: RRC connection is needed before RAB setup in order to make a call.

KPI Formula:

% M1001C66) ( sum

M1001C115) ( sum *100







3.1.3 RAB Setup and Access Complete Ratio, RT Service Other Than Voice [%]

KPI NAME: RAB Setup and Access Complete Ratio for RT Service Excluding Voice



KPI version: 1.0u




Description: RAB Setup and Access Complete Ratio [%] for RT service excluding voice over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).



KPI Formula:

%

M1001C70)M1001C69M1001C68

M1001C67 ( sumM1001C119)M1001C118M1001C117

M1001C116 ( sum

*100

++

+

++

+







3.2 High Level Indicators for Retainability

3.2.1 RRC Drop Ratio [%]

KPI NAME: RRC Drop Ratio from network perspective



KPI version: 1.0u


© Nokia Oyj

19 (62)


Description: RRC Drop Ratio [%] over the reporting period. Covers RRC Active Phase of a call.


Note 1: In this KPI, RRC Releases due to pre-emption are considered as successful case.

Note 2: In RAN1.5 and RAN04 the CN related RAB releases due to failure is included in the counter M1001C12.

KPI Formula:

% )8M1001C ( sum

M1001C14)M1001C13

M1001C12 ( sum

*100 - 100

++

KPI Class: Retainability



Object Summary Level notes: Note that the best active set cell may change during the call. Therefore, the object of the measurement can be different for connection establishment (setup and access phases) and release counters (active phase) of the same call.


Time Summary Level notes: Note that an established call can be started and ended in two separate measurement intervals. Therefore, the RAB Active and RAB and DCH holding time counters stating the RAB active releases and durations are recorded in the measurement interval during which the call was released.

3.2.2 RAB Drop Ratio, Voice [%]

KPI NAME: RAB Drop Ratio, AMR Voice from Network Perspective



KPI version: 1.0u




Description: RAB Drop Ratio for AMR Voice [%] over the reporting period. Covers RAB Active Phase of a call.


Note 1: In this KPI, RAB Releases due to pre-emption are considered as successful case.

KPI Formula:

% )115M1001C ( sum

)M1001C144M1001C143

M1001C136 ( sum

*100 - 100 +

+







3.2.3 RAB Drop Ratio, RT Services Other Than Voice [%]

KPI NAME: RAB Drop Ratio, RT Services Excluding Voice



KPI version: 1.0u




© Nokia Oyj

21 (62)



KPI Formula:

%

) M1001C119 M1001C118 M1001C117

M1001C116 ( sum) M1001C170

M1001C169 M1001C168 M1001C167 M1001C154 M1001C153 M1001C152

M1001C151 ( sum

M1001C140) M1001C139 M1001C138

M1001C137 ( sum

*100 - 100

+++

++++++++

+++










3.2.4 RAB Drop Ratio, NRT Services [%]

KPI NAME: RAB Drop Ratio, NRT Services, from Network Perspective



KPI version: 1.0u



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

KPI Formula:

%

M1001C121) M1001C120 ( sum

M1001C172) M1001C171 ( sum

M1001C142) M1001C141 ( sum

*100 - 100

+

++

+




Object Summary Level notes: Note that the best active set cell may change during the call. Therefore the object of the measurement can be different for connection establishment (setup and access phases) and release counters (active phase) of the same call.




© Nokia Oyj

23 (62)


3.3 High Level Indicators for Usage

3.3.1 Cell Availability [%]

KPI NAME: Cell Availability



KPI version: 1.0u

Description: The availability of the WCELLs under a Controlling RNC (CRNC).

This KPI is based on Cell Resource Measurement [1].

KPI Formula:

%) 60)* DURATION" PERDIOD" / ) 20*M1000C73 ( ( * 100

(Where PERIOD DURATION measurement interval in minutes.)

KPI Class: Usage




Time Summary Levels: Hour


3.3.2 Average Uplink Load [dBm]

KPI NAME: Average Uplink Load


Published: (internal information)


KPI version: 1.0u

Description: Average received uplink power [dBm] shows the uplink loading of a cell over the reporting period.




This measurement is based on Cell Resource Measurement [1], where the total uplink interference (RSSI) of a cell is measured.

Note: Calculation notes

The counter values are given in standardised RSSI values (0…621). This means that the values must be converted to dBm values (-112.1 … -50.0) before the KPI can be calculated.

It is possible that the counter in the formula is not updated during the measurement period, meaning that the denominator counter is not updated. These samples should be filtered out.

When using the formula, linear scale has to be used with calculations. This means that the dBm values in the counters must be converted to Watts and, after the calculation is done, the result must be converted back to dBms.

KPI Formula:

dBm )) M1000C9 M1000C7 M1000C5 M1000C3

(M1000C1 / ) M1000C9 *M1000C8

M1000C7 * M1000C6 M1000C5 *M1000C4 M1000C3 * M1000C2

M1000C1* (M1000C0 ( average

++++

++++

KPI Class: Usage







© Nokia Oyj

25 (62)


3.3.3 Average Downlink Load [dBm]

KPI NAME: Average Downlink Load


Published: (internal information)


KPI version: 1.0u

Internal KPI ID (only for internal use): rnc_102a

Description: Average transmitted downlink power [dBm] shows the downlink loading of a cell over the reporting period.

This measurement is based on Cell Resource Measurement [1], where the total transmitted power of a cell is measured.


When using the formula, linear scale has to be used with calculations. This means that the dBm values in the counters must be converted to Watts and, after the calculation is done, the result must be converted back to dBms.

It is possible that the counter in the formula is not updated during the measurement period, meaning that the denominator counter is not updated. These samples should be filtered out.

The calculation must also include a division by 100 in order to take out the raw counter unit value multiplication by 100.

KPI Formula:

dBm 100/) ) M100023 M100021 M1000C19M1000C17

(M1000C15 / ) M100023* M1000C22

M100021* M1000C620 M1000C19* M1000C18 M1000C17* M1000C16

M1000C15* (M1000C14 ( average

++++

++++

(The number 100 in the formula represents the raw counter dBm value correction.)




KPI Class: Usage






3.3.4 Average RACH Throughput [kbit/s]

KPI NAME: Average RACH Throughput



KPI version: 1.0u

Description: Average RACH Throughput [kbit/s] over the reporting period. Includes both the user and signalling data.

This measurement is based on Cell Resource Measurement [1], where the average RACH Throughput of a cell is measured.

KPI Formula:

kbit/s ) M1000C61M1000C60 ( average

KPI Class: Usage







© Nokia Oyj

27 (62)


3.3.5 Average FACH Throughput [kbit/s]

KPI NAME: Average FACH Throughput



KPI version: 1.0u

Description: Average FACH Throughput [kbit/s] over the reporting period. Includes both the user and signalling data.

This measurement is based on Cell Resource Measurement [1], where the average FACH Throughput of a cell is measured.

KPI Formula:


KPI Class: Usage






3.3.6 Average PCH Throughput [kbit/s]

KPI NAME: Average PCH Throughput



KPI version: 1.0u

Description: Average PCH Throughput [kbit/s] over the reporting period. Includes both the user and signalling data.

This KPI is based on Cell Resource Measurement [1], where the average PCH Throughput of a cell is measured.




KPI Formula:


KPI Class: Usage






3.4 High Level Indicators for Mobility

3.4.1 Soft Handover Overhead [%]

KPI NAME: Soft Handover Overhead for One Cell



KPI version: 1.0u

Description: Soft Handover Overhead [%] over the reporting period for One Cell.

This KPI is based on Soft Handover (SHO) Measurement [5] where Active Set sizes are measured.

Note 1: In the SHO Measurement, the counters are both for RNC and WCELL. This formula is purely using the cell level counters.


© Nokia Oyj

29 (62)


KPI Formula:

% 100*) 1

) M1007C24 M1007C23 M1007C22 M1007C21 M1007C20 M1007C19

M1007C5 M1007C4 M1007C3 M1007C2

M1007C1 M1007C0 ( sum6 * ) M1007C24 (M1007C5 sum 5 * ) M1007C23 (M1007C4 sum 4* ) M1007C22 M1007C3 ( sum 3* ) M1007C21 M1007C2 ( sum2* ) M1007C20 M1007C1 ( sum

1* M1007C19) M1007C0 ( sum

( −

++++++

++++

+++++++++++

+

KPI Class: Mobility


Object Summary Levels: Cell






Available Key Performance Indicators in RAN04


4.1 High Level Indicators for Accessibility

4.1.1 RRC Setup and Access Complete Ratio [%]

KPI NAME: RRC Setup and Access Complete Ratio from end user perspective.

Published: This KPI is approved.


KPI version: 2.0a

KPI Formula:

% M1001C260)-M1001C259 M1001C241-M1001C242-M1001C0 ( sum

M1001C8) ( sum *100+


Target values: See also Chapter 2.






© Nokia Oyj

31 (62)





4.1.2 RAB Setup and Access Complete Ratio, NRT Services [%]

KPI NAME: RAB Setup and Access Complete Ratio for NRT Service from Network perspective

Published: This KPI is accepted


KPI version: 1.0a

Description: RAB Setup and Access Complete Ratio [%] for NRT services over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).



Note 2: The RAB reject due to a previous anchoring case is taken into account.

KPI Formula:

%

)M1001C113-M1001C118-

M1001C72M1001C71 ( sum

M1001C121)M1001C120 ( sum

*100+

+










KPI NAME: RAB Setup and Access Complete Ratio for NRT Service from User perspective

Published: This KPI is accepted


KPI version: 1.0a

Description: RAB Setup and Access Complete Ratio [%] for NRT services over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).



KPI Formula:

%

)M1001C72M1001C71 ( sum

M1001C121)M1001C120 ( sum

*100+

+







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

Multi RAB AMR+NRT Service KPI NAME: RAB Setup and Access Complete Ratio for Multi RAB AMR+NRT Service

Published: This KPI is approved


KPI version: 1.0a


© Nokia Oyj

33 (62)


Description: RAB Setup and Access Complete Ratio [%] for Multi RAB AMR+NRT Service services over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).



KPI Formula:

%

M1001C298) M1001C297 M1001C296 M1001C295 M1001C294 M1001C293

M1001C286 M1001C285 M1001C284 M1001C283

M1001C282 (M1001C281 sum) M1001C304 M1001C303

M1001C302 M1001C301 M1001C300 M1001C299M1001C292 M1001C291 M1001C290 M1001C289

M1001C288 M1001C287 ( sum

*100

++++++++++

+++++++++++

+







RT (excluding AMR) + NRT KPI NAME: RAB Setup and Access Complete Ratio for Multi RAB containing RT +NRT Service



KPI version: 1.0a




Description: RAB Setup and Access Complete Ratio [%] for Multi RAB containing RT+NRT Services over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).



KPI Formula:

%

) M1001C318 M1001C317M1001C316 M1001C315 M1001C314

(M1001C313 sum) M1001C324

M1001C323 M1001C322 M1001C321 M1001C320

M1001C319 ( sum

*100

+++++

+++++







More than one NRT service KPI NAME: RAB Setup and Access Complete Ratio for Multi RAB with more than one NRT Service



KPI version: 1.0a


© Nokia Oyj

35 (62)


Description: RAB Setup and Access Complete Ratio [%] for Multi RAB with more than one NRT Service over the reporting period. Covers RAB Setup and Access phases (From RAB Assignment Request to Radio Bearer Setup Complete).



KPI Formula:

%

M1001C311) M1001C307 M1001C306

(M1001C305 sumM1001C312) M1001C310 M1001C309

M1001C308 ( sum

*100

+++

+++







4.1.4 LCS Setup [%]

KPI NAME: LCS Setup and Complete Ratio



KPI version: 1.0a

Description: LCS Setup and Access Complete Ratio [%] over the reporting period. Covers the phase from Location Reporting Request to Location Control Report.

This KPI is based on Location Services Measurement [7].




KPI Formula:

% M1011C0) ( sum

M1011C2)-M1011C0 ( sum *100



Object Summary Levels: RNC and Network.




4.2 High Level Indicators for Retainability

4.2.1 RRC Drop Ratio [%]

KPI NAME: RRC Drop Ratio from network perspective



KPI version: 2.0a



Note 1: In this KPI RRC Releases due to pre-emption are considered as successful case.


© Nokia Oyj

37 (62)


KPI Formula:

%

)M1001C21 20M1001CM1001C1918M1001C

M1001C17M1001C1615M1001C M1001C14

M1001C13 M1001C12 ( sum)M1001C21 20M1001C

M1001C1918M1001C M1001C17M1001C16 M1001C15 ( sum

*100

++++++++

+++++

++



Note 2: In RAN1.5 and RAN04, the CN related RAB releases due to failure are included in the counter M1001C12.





KPI NAME: RRC Drop Ratio from User perspective



KPI version: 1.0a






KPI Formula:

%

)M1001C21 20M1001CM1001C1918M1001C

M1001C17M1001C1615M1001C M1001C14

M1001C13 M1001C12 ( sum)M1001C21 20M1001C

M1001C1918M1001C M1001C17M1001C16 M1001C15 M1001C14 ( sum

*100

++++++++

+++++

+++



Note 2: In RAN1.5 and RAN04, the CN related RAB releases due to failure are included in the counter M1001C12.





4.2.2 RAB Drop Ratio, Voice [%]

KPI NAME: RAB Drop Ratio, AMR Voice from Network Perspective



KPI version: 2.0a




© Nokia Oyj

39 (62)



KPI Formula:

%

)150M1001CM1001C149148M1001C

M1001C147M1001C146 M1001C145 M1001C144 M1001C143 M1001C142 ( sum

)150M1001CM1001C149148M1001C

M1001C147M1001C146 M1001C145 ( sum

*100

+++

+++++

+++

++







KPI NAME: RAB Drop Ratio, AMR Voice from User perspective



KPI version: 1.0a






KPI Formula:

%

)150M1001CM1001C149148M1001C

M1001C147M1001C146 M1001C145 M1001C144 M1001C143 M1001C142 ( sum

)150M1001CM1001C149148M1001C

M1001C147M1001C146 M1001C145 M1001C144 ( sum

*100

+++

+++++

+++

+++







4.2.3 RAB Drop Ratio, RT Services Other Than Voice [%]

KPI NAME: RAB Drop Ratio, RT Services Excluding Voice, Network Perspective



KPI version: 2.0a





© Nokia Oyj

41 (62)


KPI Formula:

%

)M1001C184M1001C183M1001C182M1001C181M1001C180M1001C179 M1001C166 M1001C165M1001C164

M1001C163M1001C162 M1001C161 M1001C160 M1001C159M1001C158

M1001C157M1001C156 M1001C1551001C169 M1001C140

153M1001C138M1001C M1001C151 M1001C137 ( sum


M1001C163M1001C162 M1001C161 M1001C160 M1001C159M1001C158

M1001C157M1001C156 M1001C155 ( sum

*100

++++++++++++++++++

++++

++++++++++++++++

++










KPI NAME: RAB Drop Ratio, RT Services Excluding Voice, User Perspective


KPI ID: RAN_KPI_0007A.

KPI version: 1.0a



KPI Formula:

%


M1001C163M1001C162 M1001C161 M1001C160 M1001C159M1001C158

M1001C157M1001C156 M1001C1551001C169 MM1001C140

153M1001C138M1001C M1001C151 M1001C137 ( sum


M1001C163M1001C162 M1001C161 M1001C160 M1001C159M1001C158

M1001C157M1001C156 M1001C155 ( sum

*100

++++++++++++++++++

++++

++++++++++++++++

++






Time Summary Level notes: Note that an established call can be started and ended in two separate measurement intervals. Therefore, the RAB Active and RAB and DCH holding time counters stating the RAB active releases and


© Nokia Oyj

43 (62)


durations are recorded in the measurement interval during which the call was released.

4.2.4 RAB Drop Ratio, NRT Services [%]

KPI NAME: RAB Drop Ratio, NRT Services



KPI version: 2.0a




KPI Formula:

%


M1001C187M1001C186 M1001C185 172M1001C142M1001C

M1001C171 M1001C141 ( sum)M1001C196M1001C195M1001C194

M1001C193M1001C192M1001C191 M1001C190 M1001C189M1001C188

M1001C187M1001C186 M1001C185 ( sum

*100

++++++++++++

+++

+++++++++

++






Time Summary Level notes: Note that an established call can be started and ended in two separate measurement intervals. Therefore, the RAB Active and




RAB and DCH holding time counters stating the RAB active releases and durations are recorded in the measurement interval during which the call was released.

4.2.5 RAB Drop Ratio, Multi RAB Services [%]

Multi RAB AMR+NRT Service KPI NAME: RAB Drop Ratio, Multi RAB AMR+NRT Service from Network Perspective



KPI version: 1.0a

Description: RAB Drop Ratio for Multi RAB AMR+NRT Service [%] over the reporting period. Covers RAB Active Phase of a call.


Note 1: In this KPI RAB Releases due to pre-emption are NOT considered.


© Nokia Oyj

45 (62)


KPI Formula:

%

M1001C304) M1001C303M1001C302 M1001C301 M1001C300 M1001C299M1001C292 M1001C291 M1001C290 M1001C289

M1001C288 (M1001C287 sum) M1001C352

M1001C351 M1001C350 M1001C349 M1001C348 M1001C347 M1001C346 M1001C345 M1001C344 M1001C343 M1001C342

M1001C341 ( sum

*100

++++++++++

++++++++++++










Multi RAB RT + NRT Service KPI NAME: RAB Drop Ratio, Multi RAB containing RT +NRT Service from Network Perspective



KPI version: 1.0a

Description: RAB Drop Ratio for Multi RAB containing RT +NRT Service [%] over the reporting period. Covers RAB Active Phase of a call.


Note 1: In this KPI RAB Releases due to pre-emption are NOT considered.

KPI Formula:

%

) M1001C324 M1001C323 M1001C322 M1001C321 M1001C320

(M1001C319 sumM1001C362) M1001C361 M1001C360 M1001C359 M1001C358

M1001C357 ( sum

*100

+++++

+++++







© Nokia Oyj

47 (62)



Multi RAB AMR + NRT Service KPI NAME: RAB Drop Ratio, Multi RAB containing more than one NRT Services, from Network Perspective



KPI version: 1.0a

Description: RAB Drop Ratio, Multi RAB containing more than one NRT Services, [%] over the reporting period. Covers RAB Active Phase of a call.



KPI Formula:

%

M1001C312) M1001C310 M1001C309

(M1001C308 sum) M1001C356

M1001C355 M1001C354

M1001C353 ( sum

*100

+++

+++










4.3 High Level Indicators for Usage

4.3.1 Noise floor of the System [dBm]

KPI NAME: Noise floor of the System [dBm]



KPI version: 1.0a

Description: Average PrxNoise [dBm] of a cell over the reporting period.

This measurement is based on Cell Resource Measurement [1], where the PrxNoise of a cell is measured.


When using the formula, linear scale has to be used with calculations. This means that the dBm values in the counters must be converted to Watts and after the calculation is done, the result must be converted back to dBms.

It is possible that the counter in the formula is not updated during the measurement period, that is, the denominator counter is not updated. These samples should be filtered out.

The calculation must also include a division by - 100 in order to take out the raw counter unit value multiplication by -100.

Note 2: Pre-calculated values

The counter M1000C10 already shows the average dBm level. Therefore, the denom counter M1000C11 is not used in the formula.

KPI Formula:

dBm 100- / ' M1000C10


© Nokia Oyj

49 (62)


(The number - 100 in the formula represents the raw counter dBm value correction.)

KPI Class: Usage






4.3.2 Average SAB Throughput [kbit/s]

KPI NAME: Average SAB Throughput.



KPI version: 1.0a

Description: Average SAB Throughput [kbit/s] over the reporting period. Includes both the user and signalling data.

This measurement is based on Cell Resource Measurement [1], where the average SAB Throughput of a cell is measured.

KPI Formula:


KPI Class: Usage









4.3.3 Allocated UL Dedicated Channel Capacity [kbit/s]

CS Voice Call KPI NAME: Allocated UL Dedicated Channel Capacity for CS Voice



KPI version: 1.0a

Description: Allocated Uplink Dedicated Channel Capacity [kbit/s] for CS Voice in Serving RNC for the reporting period. These throughput calculations are based on resource allocation counters and do not show as such the actual throughput but allocated capacity.

The KPI is based on Traffic Measurement [3].

Note 1: The counters in the formula include soft handover overheads.

KPI Formula:

kbit/s 360000 / ) M1002C277 * 12.2 M1002C41 * 12.2

M1002C276 * 10.2 M1002C40 * 10.2 M1002C275 * 7.95M1002C39 * 7.95M1002C274 * 7.4M1002C38 * 7.4M1002C273 * 6.7 M1002C37 * 6.7 M1002C272 * 5.9 M1002C36 * 5.9 M1002C271 * 5.15M1002C35 * 5.15

M1002C270 * 4.75M1002C34 * (4.75 average

++++++++++++++

+

KPI Class: Usage




© Nokia Oyj

51 (62)



Time Summary Levels: Hour.


• The defined formula is valid for one-hour measurement periods.

• The allocation duration counters are updated when the DCH is released.

Data Calls KPI NAME: Allocated UL Dedicated Channel Capacity for Data Calls



KPI version: 1.0p

Description: Allocated Uplink Dedicated Channel Capacity [kbit/s] for Data Calls in Controlling RNC over the reporting period. These throughput calculations are based on resource allocation counters and do not show as such the actual throughput but allocated capacity.

These KPIs are based on Traffic Measurement [3].


KPI Formula:

kbit/s 360000 / ) M1002C302 * 384M1002C229 * 384M1002C213 * 384 M1002C73 * 384M1002C299 * 128

M1002C226 * 128M1002C210 * 128 M1002C70 * 128

M1002C298 * 64M1002C225 * 64M1002C209 * 64 M1002C69 * 64

M1002C297 * 56.7M1002C78 * (56.7 average

+++++++++++++




KPI Class: Usage



Object Summary Level notes.





4.3.4 Allocated DL Dedicated Channel Capacity [kbit/s]

CS Voice Call KPI NAME: Allocated DL Dedicated Channel Capacity for CS Voice



KPI version: 1.0u

Description: Allocated Downlink Dedicated Channel Capacity [kbit/s] for CS Voice in Serving RNC for the reporting period. These throughput calculations are based on resource allocation counters and do not show as such the actual throughput but allocated capacity.




© Nokia Oyj

53 (62)


KPI Formula:

kbit/s 360000 / ) M1002C285 * 12.2 M1002C49 * 12.2

M1002C284 * 10.2 M1002C48 * 10.2 M1002C283 * 7.95M1002C47 * 7.95M1002C282 * 7.4M1002C46 * 7.4M1002C281 * 6.7 M1002C45 * 6.7 M1002C280 * 5.9 M1002C44 * 5.9 M1002C279 * 5.15M1002C43 * 5.15

M1002C278 * 4.75M1002C42 * (4.75 average

++++++++++++++

+

KPI Class: Usage




Time Summary Levels: Hour.



• The allocation duration counters are updated when the DCH is released

Data Calls KPI NAME: Allocated DL Dedicated Channel Capacity for Data Calls



KPI version: 1.0p




Description: Allocated Downlink Dedicated Channel Capacity [kbit/s] for Data Calls in Controlling RNC over the reporting period. These throughput calculations are based on resource allocation counters and as such are not showing actual throughput but allocated capacity.



KPI Formula:

kbit/s 360000 / ) M1002C338* 384M1002C237 * 384M1002C221 * 384

M1002C335 * 128M1002C234 * 128M1002C218 * 128

M1002C334 * 64M1002C233 * 64M1002C217 * 64 M1002C69 * 64

M1002C333 * 56.7M1002C81 * (56.7 average

+++++++++++

KPI Class: Usage









© Nokia Oyj

55 (62)


4.4 High Level Indicators for Mobility

4.4.1 Soft Handover Success Rate [%]

KPI NAME: Soft Handover Success Ratio



KPI version: 1.0a

Description: Soft Handover Success Rate meaning branch addition, branch deletion or branch replacement over the reporting period in the Source Cell of the Soft Handover.

This KPI is based on Soft Handover Measurement [5] where Active Set sizes are measured.

KPI Formula:

%

M100729) M1007C28 M1007C27 M1007C12111007(M1007C10 sum

M1007C32) (M1007C15 sum

*100

++++

+CM

KPI Class: Mobility






4.4.2 Soft Handover Overhead [%]

KPI NAME: Soft Handover Overhead for Area level



KPI version: 1.0a




Description: Soft Handover Overhead [%] on area level over the reporting period.

This KPI is based on Soft Handover Measurement [5] where Active Set sizes are measured.

Note 1: In the SHO Measurement the counters are both for RNC and WCELL. This formula is purely using the cell level counters.

KPI Formula:

% 100*) 1

)/6) M1007C24 (M1007C5 )/5 M1007C23 (M1007C4 4M1007C22)/ (M1007C3 /3M1007C21) (M1007C2

/2M1007C20) (M1007C1 M1007C19) (M1007C0 ( sum

6 * ) M1007C24 (M1007C5 sum 5 * ) M1007C23 (M1007C4 sum

4* ) M1007C22 M1007C3 ( sum 3* ) M1007C21 M1007C2 ( sum2* ) M1007C20 M1007C1 ( sum

1* M1007C19) M1007C0 ( sum

( −

++++++++++

+++++++++++

+

KPI Class: Mobility


Object Summary Levels: Cluster of Cells, RNC, City, and Network.




4.4.3 Intra System Hard Handover Success Ratio [%]

KPI NAME: Intra System Hard Handover Success Ratio




© Nokia Oyj

57 (62)


KPI version: 1.0a

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

This KPI is based on Intra System Handover Measurement [4] where Intra System HHO triggering and outcome is measured.

KPI Formula:

%

)M1008C110)M1008C106(M1008C102 M1008C62) M1008C58 (M1008C54

M1008C14)(M1008C13 M1008C5)((M1008C4 sum

))M10008C111M1008C107(M1008C103M1008C63)M1008C59(M1008C55

M1008C15) ((M1008C6 sum

*100

++++++

+++

+++++

++

KPI Class: Mobility






4.4.4 Inter System Hard Handover Success Ratio [%]

KPI NAME: Inter System Hard Handover Success Ratio



KPI version: 1.0a

Description: Inter System Hard Handover Success Ratio [%] for the reporting period in the Source Cell of the Hard Handover.

This KPI is based on Inter System Handover Measurement [6] where Inter System HHO triggering and outcome is measured.




KPI Formula:

%

M1010C72)M1010C68 M1010C64 M1010C60 M1010C56M1010C34M1010C30M1010C26

M1010C22(M1010C18 sum M1010C73)M1010C69

M1010C65 M1010C61 M1010C57M1010C35M1010C31M1010C27

M1010C23(M1010C19 sum

*100

++++++++

+++++++++

+

KPI Class: Mobility







© Nokia Oyj

59 (62)


Appendix

Official KPI template

KPI NAME: Official name of the KPI.

Published: The date of publishing. If not given, then the status of the KPI is visible. The status of the KPI is also visible in the KPI version field.

KPI ID: RAN ID of the KPI. The form is the following ”RAN_KPI_number”. If the given value is not “RAN_KPI_number”, then the KPI is not recognised by RAN.

KPI version: Version of the KPI.

The version includes also the “maturity mark”, that is, u mark:

1.0a = a stands for accepted KPI, meaning that it is accepted but not found in any reporting tool.

1.0f = f stands for frozen KPI, meaning that it is accepted and found in reporting tools but not verified.

1.0u = u stands for published KPI, meaning that it is found in a reporting tool and verified in RAN.

Description: The official description of the KPI. The description includes also the measurement reference Example: This KPI is based on Service Level Measurement [2].

Note1-n: Official note fields for customer documentation.

KPI Formula: The formula given in counter numbers. This version of the formula is the one that is used in customer documentation.

KPI Class: The KPI must belong to a KPI Class.

The Classes are: Accessibility, Retainability, Usage, Integrity, and Mobility.


Object Summary Levels: Summary levels on reporting object scale. Based on the target(s) for the RAN measurement(s) that provides the counters belonging to the KPI.

Possible values: Cell, Cluster of Cells, RNC, City, and Network.

Object Summary Level notes: This field states the possible problems for a given Object Summary level.

Time Summary Levels: Summary levels on reporting timescale. Based on the collection periods for the RAN measurement(s).

Possible values: Hour, Day, Week.



Appendix

Time Summary Level notes: This field states the possible problems for a given Time Summary level.


© Nokia Oyj

61 (62)


References [1] RNC Performance Counters: Cell Resource Measurement (dn99581291, RN1.5.2 ed2, version 3.0; RN2.0)

[2] RNC Performance Counters: Service Level Measurement (dn99581291, version 3.0)

[3] RNC Performance Counters: Traffic Measurement (dn99581291, version 3.0)

[4] RNC Performance Counters: Intra System Hard Handover Measurement (dn99581291, version 3.0)

[5] RNC Performance Counters: Soft Handover Measurement (dn99581291, version 3.0)

[6] RNC Performance Counters: Inter System Hard Handover Measurement (dn99581291, version 3.0)

[7] RNC Performance Counters: Location Services Measurement (dn99581291 RN2.0 version)



Date post:	16-Jul-2015
Category:	Engineering
Upload:	varun-dhiman
View:	283 times
Download:	1 times

3 g ran kpi document

Engineering