KPI Library - Definitions, Formula

KPI LIBRARYKPIBASEDACCEPTANCE

1 Introduction

The most important part of any acceptance (giving “thumbs up or down” from the customer) is the level of the required thresholds, can they be reached and how much effort is needed to reach them. Each of these “tricky” thresholds (KPI) can increase financial risk significantly. That’s why we have to approach the KPI issue with extreme caution and always bear in mind potential financial implications.

If the number of KPIs, or the scope of measurement (method, area, success criteria) is large, the collection and post processing of data, can be time and resource consuming. On the other hand, KPI targets are sometimes so high that they are almost impossible to achieve. Furthermore, if the acceptance and exclusion criteria are not well defined, a lot of effort will need to be put into the tuning and optimization activities in order to bring the network to an acceptable condition.

This document lists the set of KPIs that should be measured, the way that they should be measured and the commercial impact of this. If the customer is asking for an alternative KPI, the arguments against the alternative and potential risk analysis will also be found in this document.

Special attention has been paid to the calculation of the number of samples needed to reach certain KPI levels. The number of samples directly affects the measurement time and the number of resources involved, hence it also affects the cost of the acceptance procedure.

These variables will dictate the types of services that are necessary to perform, and the amount of time and effort needed to collect the data necessary to achieve the targets.

2 How to use the KPI Library

The document can be used during the entire sales process. Before the actual contract negotiation, the document is valuable for understanding the Ericsson KPI and acceptance approach. During this phase, it is possible to influence the customer to adopt the Ericsson way of thinking.

When the customer’s acceptance proposal is on the table, the document can be used as a cook-book in order to assess the differences between the methodologies and to assess the risks. If the risks are too big to accept, the document offers argumentation why another set of KPIs, or measurement areas, or exclusion criteria should be used.

It is of utmost importance to understand that KPI values (targets) and questions like “can we achieve 99%” should not be considered as simple “yes or no” type of technical question.

Pure values (targets) are just one of the variables in Ericsson’s strategy and approach in how to handle KPIs in a structured way.

The KPI Library contains very sensitive internal information and none of its contents should be open to customers.

3 KPI Library Content

KPIs in the library are divided according to the Ericsson KPI handling strategy mapped on ITU-T and ETSI specifications:

Contractual KPIs are classified into:

Recommended (QoS – most used services)

Optional (QoS - most used services)

Not Recommended (Network Performance PIs, other QoS services)

In this document main focus will be detailed description of Recommended and Optional KPIs.

Availablity Performance

Quality of ServiceQuality of Service(QoS)(QoS)

Service Integrity

Service Retainability

Service Accessibilty

QoSQoS

Network PerformanceNetwork Performance

Resources & Facilities

ReliabilityPerformance

MaintainabiltyPerformance

MaintenanceSupport

PerformanceTransmissionPerformance

Design&Dimensioning

Features & Functionalities

PerformanceMonitoring

(Nodes, System)

O&M(Node, system

Availability)SLAs

Interfaces, Transmission and Transport

4 Fields Description

Field Name Description Range/Value

KPI

Number Structured No of KPI (a.b.c)a: Recommendationb: User Impactc: Area

Area The main six areas for performance monitoring

1) Completion2)Accessibility3)Retainability4)Integrity5)Mobility6)Others

Name KPI Name

SW Release Applicable SW release i.e. WCDMA RAN P6

RecommendationContractual classification of the KPI according to the Ericsson KPI strategy and ITU-T / ETSI specification.

Recommended; Optional; Not Recommended

GENERAL

Definition

Description of the meaning of the KPI and how the formula is built; Description of all the counters included in the formula and their triggering conditions; Eventual comments or notes about KPI inconsistency or statistical limit. Some tips about aggregation method.

Formula Drive Test (general) formula

Alternative Formula High level formula used for statistics (Counter based)

CONTRACTUAL INFORMATION

User ImpactDefines relevance of the KPI to the end user experience (i.e. Drop call – high)

High; Medium; Low

Contractual InformationImportant contractual implications linked to the specific KPI, like what network elements are impacting the KPIs or if KPI can replace other KPI(s).

MEASUREMENT

Method Description on how to perform the measurement Drive Test; Counters

Measurement AreaDefines applicable Acceptance measurement area for the KPI

Golden Cluster; All Cluster;

KPI DomainDefines KPI Domains as per KPI strategy and ITU-T and ETSI specifications

QoS; Network Performance/(sub levels)

Measurement ExecutionDetails on measurement execution (call sequences, start stop triggers..) for Drive tests and Statistics.

Entry and Exit CriteriaPre requisites to start the measurement like Known limitations and data exclusion (number of samples, confidence intervals..)

TARGETS AND IMPLICATIONS

Conditions/Commercial Implication

Verbal argumentation to support Sales in the commercial phase handling risk.

Required Services/Prerequisites

Required design and performance improvement services needed for specific KPI contractual commitment.

Design; Initial Tuning; Optimization..

4.1 Recommended KPIs

No Recommended KPI User Impact

1 Call Completion Success Rate Speech (CCSR Speech) High

2 Call Completion Success Rate CS64 (CCSR Video) High

3 Call Completion Success Rate PS (CCSR PS) High

4 PS Interactive R99 User Throughput (User Throughput R99) High

5 PS Interactive HSDPA User Throughput (User Throughput HSDPA) High

6 PS Interactive EUL User Throughput (User Throughput EUL) High

KPINo Area Name SW Rel Recommendation

1.1.1. Completion Call Completion Success Rate Speech (CCSR Speech) P6 Recommended

GENERALDefinition

The Call Completion Success Rate Speech (CCSR Speech) is defined as the ratio of successful normal call disconnections, divided by the total number of call setup attempts for speech calls. It is the probability of successfully initiating, holding and then terminating a speech call from an end user perspective.

CCSR Speech measured by Drive tests, presents proportion of speech calls which are successfully setup, held and released by the initiating party.

Calculated with Counter Statistics, CCSR Speech is a product of Accessibility [Call Setup Success Rate (CSSR) Speech] and Retainability [1 - Drop Call Rate (DCR) Speech] within a cell or RNC.

Formula

attemptsCallSpeech

ionsDisconnectCallSpeechNormalSpeechCCSR

__#

___#)(

Alternative Formula

)Re__#Re__(#

Re__#

__#

__#

_#

_#)(

lAbnormalRABlNormalRAB

lNormalRAB

EstAttemptRAB

EstSuccRAB

AttemptRRC

SuccessRRCSpeechCCSR

CONTRACTUAL INFORMATIONUser Impact Contractual Information

HighKPI REDUCTION: Can replace Accessibility (CSSR Speech) and Retainability (1-DCR Speech) KPIs.

KPI Impacted by Radio Env. RAN nodes, CS Core nodes and interfaces

MEASUREMENTMethod Measurement Area KPI Domain

Drive Test/Counters Golden Cluster/All Clusters QoS

Measurement Execution

DRIVE TESTS:Drive test with call sequences (120s or 180s) set up from idle mode. The terminating party shall be fixed test line. Start Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Disconnect UL (normal call clearing)

STATISTICS:Counters for Speech Accessibility and Speech Retainability agregated on Cell or RNC level.Entry and Exit CriteriaDRIVE TESTS: To reach Confidence Interval +/- 2% - 200 samples needed - 7 h (120s call) or 10h (180s call) of DT measurements with a target of 98%To reach Confidence Interval +/- 1% - 700 samples needed - 25 h (120s call) or 35h (180s call) of DT measurements with a target of 98%STATISTICS:With low sample size it is possible to have CCSR > 100% (terminations greater than new calls)To reach Confidence Interval +/- 2% - 200 samples needed with target 98%

TARGETS AND IMPLICATIONSConditions/Commercial Implication Required Services / Prerequisites

DRIVE TESTS:MTM calls to be avoided - to exclude faults and radio environment impact from the terminating partySTATISTICS : High value warning: To reach CCSR of 99% CSSR should be 99.5% and DCR 0.5%

1) RND or RND Review2) Initial Tuning3) Troubleshooting4) Optimization (Statistics)

Ericsson Controlled Environment

Best In Class (NETQB) / Optimized

Average (NetQB) / Tuned

Pre launched / Initially Tuned (no data)KPI

No Area Name SW Rel Recommendation

1.1.1. Completion Call Completion Success Rate CS64 (CCSR Video) P6 Recommended

GENERALDefinition

The Call Completion Success Rate CS64 (CCSR Video) is defined as the ratio of successful normal call disconnections, divided by the total number of call setup attempts for video calls. It is the probability of successfully initiating, holding and then terminating a video call from an end user perspective.

CCSR Video measured by Drive tests, presents proportion of speech calls which are successfully setup, held and released by the initiating party.

Calculated with Counter Statistics, CCSR Video is a product of Accessibility [Call Setup Success Rate (CSSR) Video] and Retainability [1 - Drop Call Rate (DCR) Video] within a cell or RNC.

Formula

Alternative Formula


HighKPI REDUCTION: Can replace Accessibility (CSSR Video) and Retainability (1-DCR Video) KPIs.

KPI Impacted by Radio Env RAN nodes, CS Core nodes,




DRIVE TESTS:Drive test with call sequences (120s or 180s) set up from idle mode. Terminating party is static 3G phone in good radio Env. Start Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Disconnect UL (normal call clearing)

STATISTICS:Counters for Speech Accessibility and Speech Retainability aggregated on Cell or RNC level.Entry and Exit CriteriaDRIVE TESTS: To reach Confidence Interval +/- 2% - 200 samples needed - 7 h (120s call) or 10h (180s call) of DT measurements with a target of 98%To reach Confidence Interval +/- 1% - 700 samples needed - 25 h (120s call) or 35h (180s call) of DT measurements with a target of 98%STATISTICS:With low sample size it is possible to have CCSR > 100% (terminations greater than new calls)To reach Confidence Interval +/- 2% - 200 samples needed with target 98%


DRIVE TESTS:Impacts on the drive test route as Video Calls are unable to perform a IRAT handover to a GSM network and abnormal releases may occur on the cluster edgesCOUNTER STATISTICS : High value warning: To reach CCSR of 98% CSSR should be 99% and DCR 1%. Network traffic is traditionally low for this KPI and statistical performance fluctuates.





Pre launched / Initially Tuned (no data)


1.1.1. Completion Call Completion Success Rate PS (CCSR PS) P6 Recommended

GENERALDefinition

The Call Completion Success Rate PS (CCSR PS) is defined as the ratio of successful normal call disconnections, divided by the total number of call setup attempts for packet calls. It is the probability of successfully initiating, holding and then terminating a packet connection from an end user perspective.

CCSR PS is independent of the throughput of any download, either HTTP or FTP or UDP. The KPI is the ability of the network to setup and maintain a packet radio access bearer independent of the user session on the bearer. Session errors (caused by FTP problems, user aborted, etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.

CCSR PS measured by Drive tests, presents proportion of sessions which are successfully setup, held and released by the initiating party.

Calculated with Counter Statistics, CCSR PS is a product of Accessibility [Call Setup Success Rate (CSSR) PS] and Retainability [1 - Drop Call Rate (DCR) PS] within a cell or RNC.Formula

Alternative Formula


High

KPI REDUCTION: Can replace Accessibility (CSSR PS) and Retainability (1-DCR PS) KPIs. Merges all PS Services for Call Completion together, including CCSR PS (R99), CCSR PS (HSDPA) and CCSR PS (EUL)

KPI Impacted by Radio, M-PBN and PS nodes; many factors outside E/// controlMEASUREMENT

Method Measurement Area KPI Domain



DRIVE TESTS:Drive test downloading a 5MB file (FTP). The terminating party is a FTP server attached to the GGSN Start Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Deactivate PDP Context UL (normal packet clearing)COUNTER STATISTICS:Counters for Packet Accessibility and Packet Retainability aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1.8% - 180 samples needed - 11 h of DT measurements (R99; avg throughput 200kbps) with a target of 98%To reach Confidence Interval +/- 1.8% - 180 samples needed - 2 h of DT measurements (HS; throughput 1.5Mbps) with a target of 98%STATISTICS:With low sample size it is possible to have CCSR > 100% (terminations greater than new calls)


DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : High value warning: To reach CCSR of 99% CSSR should be 99.5% and DCR 0.5%

1) RND or RND Review2) Initial Tuning3) Troubleshooting (E2E)4) Optimization (Statistics)





KPI


1.1.5. IntegrityPS Interactive R99 User Throughput DL (User Throughput R99 DL)

P6 Recommended

GENERALDefinition

The Packet-Switched Interactive R99 User Throughput (User Throughput R99) is the average user throughput for PS Data in Downlink evaluation (kbps) on a R99 DCH/FACH Radio Bearer. It includes user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's.

The most accurate method to measure User Throughput R99 is by Drive tests. The download file size divided by the time to complete the download and then taken as the indicator of user throughput. For high target throughput values, static tests are preferred.

Calculated with Counter Statistics, User Throughput R99 is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cellFormula

Alternative Formula


High

KPI REDUCTION: None

KPI Impacted by Radio Env. RAN nodes, PS Core nodes; big variations between Drive test and Statistics measurement.


Drive Test/Statistics Golden Cluster/All Clusters QoSMeasurement Execution

DRIVE TESTS:Drive test with call sequences downloading a file (5MB or 10MB) set up from idle mode. The terminating party is ideally a UDP server attached to the GGSN within the operator domain.Start Trigger: Time for Session Start for the download Stop Trigger: Time for Session End for the downloadSTATISTICS:Counters for Packet Throughput are calculated on a per RAB basis for R99 DCH PS Interactive Traffic No IP losses shall exist. Tested by conducting at least 1000 ping commands from the UE to the test server, where all shall be successful. There are no Transmission or Core limitations to maximum user throughput. Entry and Exit Criteria

STATISTICS: Using counter statistics, the user throughput is dependant on the file sizes being downloaded by all end users in the network. Smaller file size downloads would result in lower counter statistic throughputs, and therefore network counters could reflect an inaccurate perception of the network.


GENERAL:Big deviations between Drive test results (mostly high speeds) and Statistics(low speeds in average)!! As many operators have HS enabled Statistics (average throughput) goes down!!DRIVE TESTS:Usually FTP big files in tuned areas (mostly on 384 RAB) achieving speeds above 250 kbpsSTATISTICS: Averaged, mostly HTTP where there is no need for high speeds (internet site downloaded before switching to 384) and also transitions from HS to 64.







1.1.5. IntegrityPS Interactive HSDPA User Throughput (User Throughput HSDPA)

P6 Recommended

GENERALDefinition

The PS Interactive HSDPA User Throughput (User Throughput HSDPA) is the average user throughput for PS Data in Downlink or Uplink evaluation (kbps) on a HSDPA Radio Bearer. It includes user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's.

The most accurate method to measure User Throughput HSDPA is by Drive tests. The download file size divided by the time to complete the download and taken as the indicator of user throughput. For high target throughput values, static tests are preferred.

Calculated with Counter Statistics, User Throughput HSDPA is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cellFormula

Alternative Formula


High

KPI REDUCTION: None

KPI Impacted by Radio Env. RAN nodes, PS Core nodes; big variations between Drive test and Statistics measurement. Feature dependent (Dyn Code allocation).


Drive Test/Statistics Golden Cluster/All Clusters QoS


DRIVE TESTS:Drive test with call sequences downloading a file (50MB) set up from idle mode. The terminating party is ideally a UDP server attached to the GGSN within the operator domain.Start Trigger: Time for Session Start for the download Stop Trigger: Time for Session End for the downloadSTATISTICS:Counters for Packet Throughput are calculated on a per RAB basis for HSDPA PS Interactive Traffic and agregated on Cell or RNC level.Entry and Exit Criteria

STATISTICS:Using counter statistics, the user throughput is dependant on the file sizes being downloaded by all end users in the network. Smaller file size downloads would result in lower counter statistic throughputs, and therefore network counters could reflect an inaccurate perception of the network. No IP losses shall exist. Tested by conducting at least 1000 ping commands from the UE to the test server, where all shall be successful. There are no Transmission or Core limitations to maximum user throughput.


GENERAL:Big deviations between Drive test results (mostly high speeds achieved) and Statistics (low speeds in average)!!HSDPA UE Category Dependancy affects the maximum end user throughput DRIVE TESTS:Handover attempts to 2G cells are to be avoided or mitigated in the KPI Analysis as the throughput will be degraded.






Results in Ericsson Controlled Environment is for UE Category 7/8.


1.1.5. Integrity PS Interactive EUL User Throughput (User Throughput EUL) P6 Recommended

GENERALDefinition

The PS Interactive EUL User Throughput (User Throughput EUL) is the average user throughput for PS Data in Uplink evaluation (kbps) on a EUL Radio Bearer. It includes user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's.

The most accurate method to measure User Throughput EUL is by Drive tests. The upload file size divided by the time to complete the upload and taken as the indicator of user throughput. For high target throughput values, static tests are preferred.

Calculated with Counter Statistics, User Throughput EUL is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cellFormula

Alternative Formula


High

KPI REDUCTION: None

Highly Feature Dependant: KPI Impacted by Radio Env. RAN nodes, PS Core nodes, Transmission Capacity, RBS Hardware; big variations between Drive test and Statistics measurement.


Drive Test/Statistics Golden Cluster/All Clusters QoS


DRIVE TESTS:Drive test with call sequences downloading a file (1MB or 5MB) set up from idle mode. The terminating party is ideally a UDP server attached to the GGSN within the operator domain.Start Trigger: Time for Session Start for the upload (or when the first acknowledgement of a user data packet is received in the UE.) Stop Trigger: Time for Session End for the upload (or when the last acknowledgement of a user data packet is received in the UE.)STATISTICS:Counters for Packet Throughput are calculated on a per RAB basis for EUL PS Interactive and aggregated on Cell or RNC level.Entry and Exit CriteriaGENERAL:No IP losses shall exist. Tested by conducting at least 1000 ping commands from the UE to the test server, where all shall be successful. There are no Transmission or Core limitations to maximum user throughput.STATISTICS:Using counter statistics, the user throughput is dependant on the file sizes being downloaded by all end users in the network. Smaller file size downloads would result in lower counter statistic throughputs, and therefore network counters could reflect an inaccurate perception of the network.


GENERAL:Big deviations between Drive test results (mostly high speeds achieved) and Statistics (low speeds in average)!!

DRIVE TESTS:Handover attempts to 2G cells are to be avoided or mitigated in the KPI Analysis as the throughput will be degraded.






4.2 Optional KPIs

No Optional KPI User Impact

1 Call Setup Success Rate Speech (CSSR Speech) High

2 Drop Call Rate Speech (DCR Speech) High

3 Call Setup Success Rate CS64 (CSSR CS64) High

4 Drop Call Rate CS64 (DCR CS64) High

5 Call Setup Success Rate PS (CSSR PS) High

6 Drop Call Rate PS (DCR PS) High

7 Call Setup Time Speech (CST Speech) Medium

8 BLER Quality Speech Uplink (BLER Speech) Medium

9 Call Setup Time CS64 (CST CS64) Medium

10 BLER Quality CS64 Uplink (BLER CS64) Medium

11 Call Setup Success Rate PS R99 (CSSR PS R99) Medium

12 Call Setup Success Rate PS HSDPA (CSSR PS HSDPA) Medium

13 Call Setup Success Rate PS EUL (CSSR PS EUL) Medium

14 Drop Call Rate PS R99 (DCR PS R99) Medium

15 Drop Call Rate PS HSDPA (DCR PS HSDPA) Medium

16 Drop Call Rate PS EUL (DCR PS EUL) Medium

17 Minutes per Drop PS Interactive (MPD PS) Medium

18 IRAT Handover Success Rate Speech (IRAT Speech) Medium

19 IRAT Cell Change Success Rate for PS Interactive (IRATCC PS) Medium

20 BLER Quality PS Uplink (BLER PS) Medium

21 PDP Context Activation Time PS (PDP Act Time PS) Medium

22PS Interactive R99 User Throughput UL (User Throughput R99 UL) Medium


2.1.2. Accessibility Call Setup Success Rate Speech (CSSR Speech) P6 Optional

GENERALDefinition

The Call Setup Success Rate Speech (CCSR Speech) is defined as the ratio of successful call setups, divided by the total number of call setup attempts for speech calls. It is the probability of successfully initiating a speech call from an end user perspective.

CSSR Speech measured by Drive tests, presents the proportion of speech calls which are successfully setup by the initiating party.

Calculated with Counter Statistics, CCSR Speech is a product of the RRC Setup Success Rate and the RAB Setup Success Rate for Speech within a cell or RNC.

Formula

Alternative Formula


HighKPI REDUCTION: Can replace RRC Accessibility CS and RAB Accessibility Speech KPIs.

KPI Impacted by Radio Env. RAN nodes, CS Core nodes, Transmission Capacity; and interfaces




DRIVE TESTS:Drive test with call sequences (20s) set up from idle mode. The terminating party shall be fixed test line. Start Trigger: Call Attempt or first RRC Connection Request UL Stop Trigger: Alerting DL

STATISTICS:Counters for RRC Accessibility CS and RAB Accessibility Speech on Cell or RNC level.Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 4.4 h (20s call) of DT measurements with a target of 99%To reach Confidence Interval +/- 0.5% - 1500 samples needed - 16.7 h (20s call) or DT measurements with a target of 99%STATISTICS:To reach Confidence Interval +/- 0.5% - 1500 samples needed with target 99%


DRIVE TESTS:MTM calls to be avoided - to exclude faults and radio environment impact from the terminating partySTATISTICS : High value warning: To reach CSSR of 99%, RRC Setup Success should be 99.5% and RAB Setup Success should be 99.5%





Pre launched / Initially Tuned


2.1.3. Retainability Drop Call Rate Speech (DCR Speech) P6 Optional

GENERALDefinition

The Drop Call Rate Speech (DCR Speech) is defined as the ratio of abnormal call disconnections, divided by the total number of successful call setups for speech calls. It is the probability of successfully holding and terminating a call once it has been successfully initiated.

DCR Speech measured by Drive tests, presents the proportion of speech calls which are successfully released after a specified holding time from when the call was successfully setup.

Calculated with Counter Statistics, DCR Speech is the ratio of abnormally released calls divided by the sum of the abnormally and normal released Speech RABs within a cell or RNC.

Formula

Alternative Formula


HighKPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate





DRIVE TESTS:Drive test with call sequences (120s or 180s) set up from idle mode. The terminating party shall be fixed test line. Start Trigger: Alerting DL Stop Trigger: Disconnect UL (normal call clearing)

STATISTICS:Counters for RAB Retainability Speech on Cell or RNC level.Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 13.3 h (120s call) or 20h (180s call) of DT measurements with a target of 1%To reach Confidence Interval +/- 0.5% - 1500 samples needed - 50 h (120s call) or 75h (180s call) of DT measurements with a target of 1%STATISTICS:To reach Confidence Interval +/- 0.5% - 1500 samples needed with target 1%


DRIVE TESTS:MTM calls to be avoided - to exclude faults and radio environment impact from the terminating partySTATISTICS : High value warning: Difficult to achieve a high value without extensive optimization and sufficient traffic levels







2.1.2. Accessibility Call Setup Success Rate CS64 (CSSR CS64) P6 Optional

GENERALDefinition

The Call Setup Success Rate CS64 (CCSR CS64) is defined as the ratio of successful call setups, divided by the total number of call setup attempts for video calls. It is the probability of successfully initiating a video call from an end user perspective.

CSSR CS64 measured by Drive tests, presents the proportion of video calls which are successfully setup by the initiating party.

Calculated with Counter Statistics, CSSR CS64 is a product of the RRC Setup Success Rate and the RAB Setup Success Rate for Video within a cell or RNC.

Formula

Alternative Formula


HighKPI REDUCTION: Can replace RRC Accessibility CS and RAB Accessibility Video KPIs.

KPI Impacted by Radio Env. RAN nodes, CS Core nodes, Transmission Capacity; and interfaces




DRIVE TESTS:Drive test with call sequences (40s) set up from idle mode. Terminating party is static 3G phone in good radio Env.Start Trigger: Call Attempt or first RRC Connection Request UL Stop Trigger: Alerting DL

STATISTICS:Counters for RRC Accessibility and RAB Accessibility Video on Cell or RNC level.Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 700 samples needed - 10 h (40s call) of DT measurements with a target of 98.2%To reach Confidence Interval +/- 0.5% - 2500 samples needed - 35 h (40s call) or DT measurements with a target of 98.2%STATISTICS:To reach Confidence Interval +/- 0.5% - 2500 samples needed with target 98.2%


DRIVE TESTS:Impacts on the drive test route as Video Calls are unable to perform a IRAT handover to a GSM network and call setup problems may occur on the cluster edges STATISTICS : High value warning: To reach CSSR of 98%, RRC Setup Success should be 99 % and RAB Setup Success should be 99%.







2.1.3. Retainability Drop Call Rate CS64 (DCR CS64) P6 Optional

GENERALDefinition

The Drop Call Rate CS64 (DCR CS64) is defined as the ratio of abnormal call disconnections, divided by the total number of successful call setups for CS64 (video) calls. It is the probability of successfully holding and terminating a video call once it has been successfully initiated.

DCR CS64 measured by Drive tests, presents the proportion of video calls which are successfully released after a specified holding time from when the call was successfully setup.

Calculated with Counter Statistics, DCR CS64 is the ratio of abnormally released calls divided by the sum of the abnormally and normal released calls for Video RABs within a cell or RNC.

Formula

Alternative Formula


HighKPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate





DRIVE TESTS:Drive test with call sequences (120s or 180s) set up from idle mode. Terminating party is static 3G phone in good radio Env.Start Trigger: Alerting DL Stop Trigger: Disconnect UL (normal call clearing)

STATISTICS:Counters for RAB Retainability CS64 (Video) on Cell or RNC level.Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1.5% - 250 samples needed - 8.5 h (120s call) or 13h (180s call) of DT measurements with a target of 1.5%To reach Confidence Interval +/- 1% - 600 samples needed - 20 h (120s call) or 30h (180s call) of DT measurements with a target of 1.5%STATISTICS:To reach Confidence Interval +/- 1% - 600 samples needed with target 1.5%


DRIVE TESTS:Impacts on the drive test route as Video Calls are unable to perform a IRAT handover to a GSM network and abnormal releases may occur on the cluster edges STATISTICS : High value warning: Video Calls are unable to perform a IRAT handover and together with worldwide low traffic volumes, makes a high value KPI difficult to achieve






KPI


2.1.2. Accessibility Call Setup Success Rate PS (CSSR PS) P6 Optional

GENERALDefinition

The Call Setup Success Rate PS (CSSR PS) is defined as the ratio of successful call setups, divided by the total number of call setup attempts for packet calls. It is the probability of successfully initiating a packet connection from an end user perspective and includes the PDP context activation and bearer setup for the R99 service.

CSSR PS measured by Drive tests, presents the proportion of packet interactive calls which are successfully setup by the initiating party.

Calculated with Counter Statistics, CCSR PS is a product of RRC Accessibility PS and RAB Accessibility PS within a cell or RNC.

Formula

Alternative Formula


High

KPI REDUCTION: Can replace RRC Accessibility PS and RAB Accessibility PS KPIs. Merges all PS Services for Call Setup Success Rate together, including CSSR PS (R99), CSSR PS (HSDPA) and CSSR PS (EUL)

KPI Impacted by Radio, M-PBN and PS nodes; Transmission Capacity; many factors outside E/// control




DRIVE TESTS:Drive test downloading a 1MB file (FTP). If a single drive test is used to measure a Throughput KPI and CSSR PS, DCR PS then a larger file should be downloaded, e.g. 5MB or 10MB. The terminating party is a FTP server attached to the GGSN Start Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Activate PDP Accept DLSTATISTICS:Counters for RRC Accessibility PS and RAB Accessibility PS are aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 5.6 h of DT measurements (R99; avg throughput 200kbps downloading a 1MB file) with a target of 99%To reach Confidence Interval +/- 1% - 400 samples needed - 2.2 h of DT measurements (HS; throughput 1.5Mbps downloading a 1MB file) with a target of 99%STATISTICS:To reach Confidence Interval +/- 1% - 400 samples needed with a target of 99%


DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : High value warning: To reach CSSR of 99%, RRC Accessibility PS should be 99.5% and RAB Accessibility PS should be 99.5%







2.1.3. Retainability Drop Call Rate PS (DCR PS) P6 Optional

GENERALDefinition

The Drop Call Rate PS (DCR PS) is defined as the ratio of abnormal call disconnections, divided by the total number of successful call setups for packet connections. It is the probability of successfully holding and then terminating a packet connection from an end user perspective.

DCR PS R99 is independent of the throughput of any download or upload, either HTTP or FTP or UDP. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. Session errors (caused by FTP problems, user aborted, etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.

DCR PS measured by Drive tests, presents the proportion of PS radio bearers which are held and normally released by the initiating party.

Calculated with Counter Statistics, DCR PS is the ratio of abnormally released calls divided by the sum of the abnormally released and normal released for Packet RABs within a cell or RNC.Formula

Alternative Formula


High

KPI REDUCTION: Merges all PS Services for Drop Rate together, including DCR PS (R99), DCR PS (HSDPA) and DCR PS (EUL)

KPI Impacted by Radio, M-PBN and PS nodes; many factors outside E/// controlMEASUREMENT

Method Measurement Area KPI Domain



DRIVE TESTS:Drive test downloading a 5MB or 10MB file (FTP). The terminating party is a FTP server attached to the GGSN Start Trigger: Activate PDP Accept DL Stop Trigger: Deactivate PDP Context UL (normal packet clearing)STATISTICS:Counters for Packet Retainability aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 23 h of DT measurements (R99; avg throughput 200kbps) for a 5MB file and a target of 1%To reach Confidence Interval +/- 1% - 400 samples needed - 4 h of DT measurements (HS; throughput 1.5Mbps) for a 5MB file and a target of 1%STATISTICS:To reach Confidence Interval +/- 1% - 400 samples needed with a target of 99%


DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : Transitions between channel states make a high target difficult to obtain. Different UE’s and behaviour impact heavily on the network counters and perceived performance






Results from NetqB are not shown as a different statistical formula is used


2.2.2. Accessibility Call Setup Time Speech (CST Speech) P6 Optional

GENERALDefinition

The Call Setup Time Speech (CST Speech) is defined as the duration of time taken to access the Speech service successfully, meaning that speech connection is established. The setup time is a taken as a Mobile Originating Connection (MOC) for Speech from a UE to a PSTN terminating connection.

CST Speech measured by Drive tests, presents the average call setup time of speech calls which are successfully setup by the initiating party.

CST Speech is unable to be collected and calculated with network counter statistics.

Formula

Alternative Formula


Medium

KPI REDUCTION: Can replace RRC Setup Time and RAB Setup Time Speech KPIs.

KPI Impacted by Radio Env. RAN nodes, CS Core nodes and interfaces. Radio Optimization and Tuning has a limited influence on the KPI target.


Drive Test Golden Cluster QoS


DRIVE TESTS:Drive test with call sequences (20s) set up from idle mode. The terminating party shall be fixed test line. Start Trigger: Time of “Call Attempt” or first “RRC Connection Request” UL Stop Trigger: Time of “Alerting” DL

STATISTICS:None available for this KPIEntry and Exit Criteria

DRIVE TESTS:Recommended to sample 300 calls for the measurement criteria but can also be collected from the samples for CCSR Speech or CSSR Speech.

STATISTICS:None available for this KPI


DRIVE TESTS:MTM calls to be avoided – even in a stationary condition, the call setup time would be affected by the radio environment in the terminating party. Calls longer than 30s setup (before the “Alerting” message should be classified as a failed call setup and excluded.STATISTICS : None available for this KPI

1) Initial Tuning2) Troubleshooting (CS E2E)






2.2.4. Integrity BLER Quality Speech Uplink (BLER Speech Uplink) P6 Optional

GENERALDefinition

The BLER Quality Speech Uplink (BLER Speech) is defined as the ratio of faulty transport blocks to transmitted transport blocks for a speech connection. BLER is an indication of speech quality since a block error means that the entire speech frame is erased and needs to be replaced, therefore affecting the perceived quality of the connection. Impacting BLER and Speech Quality are the interference, noise limitations, mobile speed (fading frequency) and time dispersion.

BLER Speech Uplink defined in this KPI is an uplink measurement only and can be calculated with network counter statistics or network recordings.

Formula

Alternative Formula


Medium

KPI REDUCTION: Partly is related to Speech Quality (MOS-PESQ)

KPI Impacted by Radio Env. RAN nodes and parameter settings. Ericsson should control the parameters for setting BLER targets for each service.


Drive Test/Counters Golden Cluster QoS


DRIVE TESTS:Calls should be set up in a similar manner to CCSR Speech and DCR Speech. Results can be collected via the UETR recording function INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the UE IMSI.STATISTICS:Statistics can be obtained using the performance CTR measurement INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the Cluster Cell Set. Network RNC level counters collect statistics on the the number of Transport Blocks and number of Faulty Transport Blocks for an RNC-wide perspective.Entry and Exit Criteria

DRIVE TESTS: Recommended to have at least 600 normally terminated Speech Calls collected during a drive for CCSR Speech or DCR Speech.STATISTICS:Recommended to have at least 600 normally terminated Speech Calls during a 5 hour collection period.


Downlink BLER is not uniformly reported by different UE’s. UETR / CTR Downlink BLER are reported as % and therefore can be inaccurate when aggredated together. This KPI therefore only measures the Uplink BLER.STATISTICS: When calculating Uplink BLER using CTR measurements, up to 16 simultaneous UE’s can be recorded in the selected Cluster (Not all calls are represented). RNC level statistics cannot be broken into Clusters.

1) RND or RND Review (Dimensioning)2) Troubleshooting (CS)





Results in this Bar Graph for Uplink BLER using RNC level counters.


2.2.2. Accessibility Call Setup Time CS64 (CST CS64) P6 Optional

GENERALDefinition

The Call Setup Time CS64 (CST CS64) is defined as the duration of time taken to access the CS64 (video) service successfully, meaning that video connection is established. The setup time is a taken as a Mobile Originating Connection (MOC) for video to another UE terminating connection (UE to UE).

CST CS64 measured by Drive tests, presents the average call setup time of video calls which are successfully setup by the initiating party.

CST CS64 is unable to be collected and calculated with network counter statistics.

Formula

Alternative Formula


Medium

KPI REDUCTION: Can replace RRC Setup Time and RAB Setup Time Video KPIs.





DRIVE TESTS:Drive test with call sequences (40s) set up from idle mode. Terminating party is static 3G phone in good radio Env.Start Trigger: Time of “Call Attempt” or first “RRC Connection Request” UL Stop Trigger: Time of “Alerting” DL

STATISTICS:None available for this KPIEntry and Exit Criteria

DRIVE TESTS:Recommended to sample 300 calls for the measurement criteria but can also be collected from the samples for CCSR CS64 or CSSR CS64.



DRIVE TESTS:Time needed for terminating UE for automatic answer should be deducted from the calculations or included in the KPI. This is roughly 2s. Calls longer than 30s setup (before the “Alerting” message should be classified as a failed call setup and excluded.STATISTICS : None available for this KPI

1) Initial Tuning2) Troubleshooting (CS E2E)






2.2.4. Integrity BLER Quality CS64 Uplink (BLER CS64 Uplink) P6 Optional

GENERALDefinition

The BLER Quality CS64 Uplink (BLER CS64 Uplink) is defined as the ratio of faulty transport blocks to transmitted transport blocks for a CS64 (video) connection. BLER is an indication of quality since a block error means that the frame is erased or needs to be replaced, therefore affecting the perceived quality of the connection. Impacting BLER and Quality is the interference, noise limitations, mobile speed (fading frequency) and time dispersion.

BLER CS64 Uplink defined in this KPI is an uplink measurement only and can be calculated with network counter statistics or network recordings.

Formula

Alternative Formula


Medium

KPI REDUCTION: None

KPI Impacted by Radio Env. RAN nodes and parameter settings. Ericsson should control the parameters for setting BLER targets for each service.




DRIVE TESTS:Calls should be set up in a similar manner to CCSR CS64 and DCR CS64. Results can be collected via the UETR recording function INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the UE IMSI.STATISTICS:Statistics can be obtained using the performance CTR measurement INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the Cluster Cell Set. Network RNC level counters collect statistics on the the number of Transport Blocks and number of Faulty Transport Blocks for an RNC-wide perspective.Entry and Exit Criteria

DRIVE TESTS: Recommended to have at least 600 normally terminated Video Calls collected during a drive for CCSR CS64 or DCR CS64.STATISTICS:Recommended to have at least 600 normally terminated Video Calls during a 5 hour collection period.



1) RND or RND Review (Dimensioning)2) Troubleshooting (CS)






2.1.2. Accessibility Call Setup Success Rate PS R99 (CSSR PS R99) P6 Optional

GENERALDefinition

The Call Setup Success Rate PS R99 (CSSR PS R99) is defined as the ratio of successful call setups, divided by the total number of call setup attempts for packet calls using a R99 radio bearer. It is the probability of successfully initiating a R99 packet connection from an end user perspective resulting in a R99 connection of up to 384kbps and includes the PDP context activation and bearer setup for the R99 service.

CSSR PS R99 measured by Drive tests, presents the proportion of R99 radio bearers which are successfully setup by the initiating party.

Calculated with Counter Statistics, CCSR PS R99 is a product of RRC Accessibility (PS) and RAB Accessibility R99 (PS) within a cell or RNC.Formula

Alternative Formula


MediumKPI REDUCTION: Can replace RRC Accessibility PS and RAB Accessibility R99 PS KPIs.

KPI Impacted by Radio, M-PBN and PS nodes; many factors outside E/// control




DRIVE TESTS:Drive test downloading a 500KB file (FTP). If a single drive test is used to measure a Throughput KPI and CCSR PS R99 then a larger file should be downloaded, e.g. 5MB or 10MB. The terminating party is a FTP server attached to the GGSNStart Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Activate PDP Accept DLCOUNTER STATISTICS:Counters for Packet Accessibility are aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 2.5 h of DT measurements (R99; avg throughput 200kbps downloading a 500KB file) with a target of 99%

STATISTICS:With low sample size it is possible to have CSSR > 100%. With a confidence of +/- 1% - 400 samples needed for a target of 99%


DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : To reach CSSR of 99%, RRC Accessibility should be 99.5% and RAB R99 Accessibility should be 99.5%







2.1.2. Accessibility Call Setup Success Rate PS HSDPA (CSSR PS HSDPA) P6 Optional

GENERALDefinition

The Call Setup Success Rate PS HSDPA (CSSR PS HSDPA) is defined as the ratio of successful call setups, divided by the total number of call setup attempts for packet calls using a HSDPA radio bearer. It is the probability of successfully initiating a HSDPA packet connection from an end user perspective resulting in a HSDPA connection and includes the PDP context activation and bearer setup for the HSDPA service.

CSSR PS HSDPA measured by Drive tests, presents the proportion of sessions which are successfully setup by the initiating party.

Calculated with Counter Statistics, CCSR PS HSDPA is a product of RRC Accessibility (PS) and RAB HSDPA Accessibility (PS) within a cell or RNC.Formula

Alternative Formula


MediumKPI REDUCTION: Can replace RRC Accessibility PS and RAB HSDPA Accessibility PS KPIs.





DRIVE TESTS:Drive test downloading a 1MB file (FTP). If a single drive test is used to measure a Throughput KPI and CCSR PS then a larger file should be downloaded, e.g. 5MB or 10MB. The terminating party is a FTP server attached to the GGSNStart Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Activate PDP Accept DLCOUNTER STATISTICS:Counters for Packet Accessibility are aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 1.7 h of DT measurements (HS; throughput 1.5Mbps downloading a 1MB file) with a target of 99%



DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : High value warning: To reach CSSR of 99%, RRC Accessibility should be 99.5% and RAB HSDPA Accessibility should be 99.5%







2.1.2. Accessibility Call Setup Success Rate PS EUL (CSSR PS EUL) P6 Optional

GENERALDefinition

The Call Setup Success Rate PS EUL (CSSR PS EUL) is defined as the ratio of successful call setups, divided by the total number of call setup attempts for packet calls using a EUL radio bearer. It is the probability of successfully initiating an EUL packet connection from an end user perspective resulting in a EUL connection and includes the PDP context activation and bearer setup for the EUL service.

CSSR PS EUL measured by Drive tests, presents the proportion of sessions which are successfully setup by the initiating party.

Calculated with Counter Statistics, CCSR PS EUL is a product of RRC Accessibility (PS) and RAB Accessibility EUL (PS) within a cell or RNC.Formula

Alternative Formula


MediumKPI REDUCTION: Can replace RRC Accessibility PS and RAB Accessibility EUL PS KPIs.





DRIVE TESTS:Drive test uploading a 500KB file (FTP). The terminating party is a FTP server attached to the GGSNStart Trigger: Call Attempt or first RRC Connection Request Stop Trigger: Activate PDP Accept DLCOUNTER STATISTICS:Counters for Packet Accessibility are aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 1.5 h of DT measurements (EUL; avg throughput 400kbps uploading a 500KB file) with a target of 99%



DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : High value warning: To reach CSSR of 99%, RRC Accessibility should be 99.5% and RAB EUL Accessibility should be 99.5%






NetqB data is currently unavailabe for EUL Statistics


2.1.3. Retainability Drop Call Rate PS R99 (DCR PS R99) P6 Optional

GENERALDefinition

The Drop Call Rate PS R99 (DCR PS R99) is defined as the ratio of abnormal call disconnections, divided by the total number of successful call setups for packet connections using a R99 radio bearer. It is the probability of successfully holding and then terminating a R99 packet connection from an end user perspective.

DCR PS R99 is independent of the throughput of any download, either HTTP or FTP or UDP. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. Session errors (caused by FTP problems, user aborted, etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.

DCR PS R99 measured by Drive tests, presents the proportion of R99 radio bearers which are held and normally released by the initiating party.

Calculated with Counter Statistics, DCR PS R99 is the ratio of abnormally released calls divided by the sum of the abnormally released and normal released within a cell or RNC while on a R99 radio bearer.Formula

Alternative Formula


Medium

KPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate

KPI Impacted by Radio, M-PBN and PS nodes; many factors outside E/// control. Warning: Statistics for DCR may not reflect end user experience due to missing idle to active transitions which can result in a poor achieved value for the KPI. Ericsson therefore recommends the KPI Minutes per Drop PS Interactive (MPD PS)




DRIVE TESTS:Drive test downloading a 5MB file (FTP). The terminating party is a FTP server attached to the GGSN Start Trigger: Activate PDP Accept DL Stop Trigger: Deactivate PDP Context UL (normal packet clearing)COUNTER STATISTICS:Counters for Packet R99 Retainability aggregated on Cell or RNC level Entry and Exit CriteriaDRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 23 h of DT measurements (R99; avg throughput 200kbps) for a 5MB file and a target of 1%STATISTICS:To reach Confidence Interval +/- 1% - 400 samples needed with a target of 1%


DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : Drop rate is heavily impacted by channel state transitions including URA / FACH / DCH / HSDPA and by different UE’s.








2.1.3. Retainability Drop Call Rate PS HSDPA (DCR PS HSDPA) P6 Optional

GENERALDefinition

The Drop Call Rate PS HSDPA (DCR PS HSDPA) is defined as the ratio of abnormal call disconnections, divided by the total number of successful call setups for packet connections using a HSDPA radio bearer. It is the probability of successfully holding and then terminating a R99 packet connection from an end user perspective.

DCR PS HSDPA is independent of the throughput of any download, either HTTP or FTP or UDP. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. Session errors (caused by FTP problems, user aborted, etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.

DCR PS HSDPA measured by Drive tests, presents the proportion of HSDPA radio bearers which are held and normally released by the initiating party.

Calculated with Counter Statistics, DCR PS HSDPA is the ratio of abnormally released calls divided by the sum of the abnormally released and normal released within a cell or RNC while on a HSDPA radio bearer.Formula

Alternative Formula


Medium


KPI Impacted by Radio, M-PBN and PS nodes; many factors outside E/// controlWarning: Statistics for DCR may not reflect end user experience due to missing idle to active transitions which can result in a poor achieved value for the KPI. Ericsson therefore recommends the KPI Minutes per Drop PS Interactive (MPD PS)




DRIVE TESTS:Drive test downloading a 5MB file (FTP). The terminating party is a FTP server attached to the GGSN Start Trigger: Activate PDP Accept DL Stop Trigger: Deactivate PDP Context UL (normal packet clearing)COUNTER STATISTICS:Counters for Packet HSDPA Retainability aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 4 h of DT measurements (HS; throughput 1.5Mbps) for a 5MB file and a target of 1%STATISTICS:To reach Confidence Interval +/- 1% - 400 samples needed with a target of 1%










2.1.3. Retainability Drop Call Rate PS EUL (DCR PS EUL) P6 Optional

GENERALDefinition

The Drop Call Rate PS EUL (DCR PS EUL) is defined as the ratio of abnormal call disconnections, divided by the total number of successful call setups for packet connections using a EUL radio bearer. It is the probability of successfully holding and then terminating a EUL packet connection from an end user perspective.

DCR PS EUL is independent of the throughput of any upload, either HTTP or FTP or UDP. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. Session errors (caused by FTP problems, user aborted, etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.

DCR PS EUL measured by Drive tests, presents the proportion of EUL radio bearers which are held and normally released by the initiating party.

Calculated with Counter Statistics, DCR PS EUL is the ratio of abnormally released calls divided by the sum of the abnormally released and normal released within a cell or RNC while on a EUL radio bearer.Formula

Alternative Formula


Medium


KPI Impacted by Radio, M-PBN and PS nodes; many factors outside E/// controlWarning: Statistics for DCR may not reflect end user experience due to missing idle to active transitions which can result in a poor achieved value for the KPI. Ericsson therefore recommends the KPI Minutes per Drop PS Interactive (MPD PS)




DRIVE TESTS:Drive test downloading a 5MB file (FTP). The terminating party is a FTP server attached to the GGSN Start Trigger: Activate PDP Accept DL Stop Trigger: Deactivate PDP Context UL (normal packet clearing)COUNTER STATISTICS:Counters for Packet EUL Retainability aggregated on Cell or RNC level Entry and Exit CriteriaDRIVE TESTS: To reach Confidence Interval +/- 1% - 400 samples needed - 12 h of DT measurements (EUL; throughput 400kbps) for a 5MB file and a target of 1%STATISTICS:To reach Confidence Interval +/- 1% - 400 samples needed with a target of 1%


DRIVE TESTS:Calls to internet servers be avoided – many components can be outside E/// responsibilitySTATISTICS : Drop rate is heavily impacted by channel state transitions including URA / FACH / DCH / EUL and by different UE’s.








2.1.3. Retainability Minutes per Drop PS Interactive (MPD PS) P6 Optional

GENERALDefinition

The Minutes per Drop PS Interactive (MPD PS) is defined as the ratio of the total end user time where a packet connection is maintained after being successfully set up divided by the abnormal call disconnections. It is the probable length of time a PS interactive call can be held by the end user before the packet connection is abnormally terminated.

MPD PS is independent of the throughput of any download, either HTTP or FTP or UDP. The KPI is the ability of the network to maintain a packet radio access bearer for a certain time period independent of the user session on the bearer. Session errors (caused by FTP problems, user aborted, etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.

MPD PS measured by Drive tests, presents the proportion of time PS radio bearers are held by the number of abnormally released packet connections.

Calculated with Counter Statistics, MPD PS is the ratio of the average users using the PS radio bearer during the measurement period divided by the number of abnormally released calls within a cell or RNC.Formula

Alternative Formula


MediumKPI REDUCTION: Can replace DCR PS (which includes R99, HSDPA and EUL DCR)





DRIVE TESTS:Drive test downloading a 5MB file (FTP). The terminating party is a FTP server attached to the GGSN Start Trigger: Activate PDP Accept DL Stop Trigger: Deactivate PDP Context UL (normal packet clearing)COUNTER STATISTICS:Counters for Packet Retainability and Utilization aggregated on Cell or RNC level Entry and Exit Criteria

DRIVE TESTS: To reach Confidence Interval +/- 1.8% - 180 samples needed - 11 h of DT measurements (R99; avg throughput 200kbps)To reach Confidence Interval +/- 1.8% - 180 samples needed - 2 h of DT measurements (HS; throughput 1.5Mbps)

STATISTICS:With low sample size it is possible to have DCR > 100% (terminations greater than new calls)








Still to be updated.


2.2.5. Mobility IRAT Handover Success Rate Speech (IRAT Speech) P6 Optional

GENERALDefinition

The Inter Radio Access Technology Handover Success Rate for Speech (IRAT Speech) is defined as the ratio of successful handovers to GSM over the number of attempted handovers to GSM. It is the probability of successfully performing a handover from WCDMA to GSM and continuing the call without end user interruption.

IRAT Speech Handovers can be measured either by Drive tests or Statistics data although due to difficulties in drive test collection, Statistics is recommended. In the case of a drive test, a normal drive within the coverage area may not have sufficient number of samples where IRAT handover is performed and it is recommended that a separate drive route along the borders of the coverage be covered.

Calculated with Statistics, IRAT Speech is a ratio of the number of successful Handovers over the number of attempted handovers. The counters are only incremented if a GSM relation exists between the Target and the Source Cell where the Source cell is the Best Cell in the Active Set. This can be aggregated to Cell and RNC levelFormula

Alternative Formula


Medium

KPI REDUCTION: None

KPI Impacted by GSM Network performance and interfaces between GSM and UMTS (neighbouring definitions on GSM and UMTS side)


Drive Test/Counters Golden Cluster/All Clusters – specialized drive route QoS


DRIVE TESTS:Drive test with call sequences (360s) set up from idle mode. The terminating party shall be fixed test line. Start Trigger: Handover from UTRAN Command Stop Trigger: Handover from UTRAN FailureSTATISTICS:Counters for IRAT Handover Attempts and Success, collected at GSM Relation level and aggregated to Cell and RNC levelEntry and Exit Criteria

DRIVE TESTS: Neighbour relations must be defined and updated frequently (during rollout). Special drive route needed (cluster edges)To reach Confidence Interval +/- 2% – 190 samples needed - 18 h of DT measurements with a target of 98%STATISTICS:The counters are only incremented if a GSM relation exists between the Target and the Source Cell


DRIVE TESTS:Highly dependent on the 3G/2G neighbour relations (during network rollout)

STATISTICS : Counter KPI heavily impacted by repeated failures between a 3G source cell to a 2G target cell in the case of a stationary end user, adding risk to a high value KPI target

1) RND or RND Review2) Initial Tuning3) Troubleshooting (E2E and GSM)4) Optimization (Statistics)






2.2.5. MobilityIRAT Cell Change Success Rate for PS Interactive (IRATCC PS)

P6 Optional

GENERALDefinition

The Inter Radio Access Technology Cell Change Success Rate for PS Interactive (IRAT CC PS) is defined as the ratio of successful cell changes to GSM over the number of attempted cell changes to GSM. It is the probability of successfully performing a cell change from WCDMA to GSM and continuing the packet connection without the packet call terminating.

IRAT Cell Change PS Handovers can be measured either by Drive tests or Statistics data although due to difficulties in drive test collection, Statistics are recommended. In the case of a drive test, a normal drive within the coverage area may not have sufficient number of samples where IRAT cell change is performed and it is recommended that a separate drive route along the borders of the coverage be covered.

Calculated with Statistics, IRAT Cell Change PS is a ratio of the number of successful cell change over the number of attempted cell changes. The counters are only incremented if a GSM relation exists between the Target and the Source Cell where the Source cell is the Best Cell in the Active Set. This can be aggregated to Cell and RNC levelFormula

Alternative Formula


Medium

KPI REDUCTION: None

KPI Impacted by GSM Network performance and interfaces between GSM and UMTS (neighbouring definitions on GSM and UMTS side)


Drive Test/Counters Golden Cluster/All Clusters – specialized drive route QoS


DRIVE TESTS:Drive test with call sequences (360s) set up from idle mode. The terminating party is a FTP server attached to the GGSNStart Trigger: Cell Change Order from UTRAN Command Stop Trigger: Cell Change Order from UTRAN FailureSTATISTICS:Counters for IRAT Cell Change Attempts and Success, collected at GSM Relation level and aggregated to Cell and RNC levelEntry and Exit Criteria

DRIVE TESTS: Neighbour relations must be defined and updated frequently (during rollout). Special drive route needed (cluster edges)To reach Confidence Interval +/- 2% (target 98%) – 190 samples needed - 18 h of DT measurements STATISTICS:The counters are only incremented if a GSM relation exists between the Target and the Source Cell


DRIVE TESTS:Highly dependent on the 3G/2G neighbour relations (during network rollout)

STATISTICS : Counter KPI heavily impacted by repeated failures between a 3G source cell to a 2G target cell in the case of a stationary end user, adding risk to a high value KPI target

1) RND or RND Review2) Initial Tuning3) Troubleshooting (E2E and GSM)4) Optimization (Statistics)






2.2.4. Integrity BLER Quality PS Uplink (BLER PS Uplink) P6 Optional

GENERALDefinition

The BLER Quality PS Uplink (BLER PS Uplink) is defined as the ratio of faulty transport blocks to transmitted transport blocks for a packet (PS) connection. BLER is an indication of quality since a block error means that the entire frame is erased or retransmitted, therefore affecting the perceived quality of the connection and limiting the throughput. Impacting BLER and Quality is the interference, noise limitations, mobile speed (fading frequency) and time dispersion.

BLER PS Uplink defined in this KPI is an uplink measurement only and can be calculated with network counter statistics or network recordings.

Formula

Alternative Formula


MediumKPI REDUCTION: None

KPI Impacted by Radio Env. RAN nodes




DRIVE TESTS:Calls should be set up in a similar manner to CCSR PS and DCR PS. Results can be collected via the UETR recording function INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the UE IMSI.STATISTICS:Statistics can be obtained using the performance CTR measurement INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the Cluster Cell Set. Network RNC level counters collect statistics on the the number of Transport Blocks and number of Faulty Transport Blocks for an RNC-wide perspective.Entry and Exit Criteria

DRIVE TESTS: Recommended to have at least 600 normally terminated Speech Calls collected during a drive for CCSR PS or DCR PS.STATISTICS:Recommended to have at least 600 normally terminated Speech Calls during a 5 hour collection period.



1) RND or RND Review (Dimensioning)2) Troubleshooting






2.2.2. Accessibility PDP Context Activation Time PS (PDP Act Time PS) P6 Optional

GENERALDefinition

The PDP Context Activation Time PS (PDP Act Time PS) is defined as the length of the time it takes to activate a PDP context. From an end user perspective, it is the time taken from idle mode to the network providing the end user with an assigned IP address and negotiated QoS parameters.

PDP Act Time PS measured by Drive tests, presents the average PDP context activation time when setting up a packet connection.

PDP Act Time PS is unable to be collected or measured with network counter statistics.

Formula

Alternative Formula


Medium

KPI REDUCTION: None





DRIVE TESTS:Drive test downloading a 1MB file (FTP). If a single drive test is used to measure a Throughput KPI and CCSR PS then a larger file should be downloaded, e.g. 5MB or 10MB. The terminating party is a FTP server attached to the GGSN Start Trigger: Time of “Call Attempt” or first “RRC Connection Request” UL Stop Trigger: Time of “Activate PDP Context Accept” DLSTATISTICS:None available for this KPIEntry and Exit Criteria

DRIVE TESTS:Recommended to sample 300 calls for the measurement criteria.



DRIVE TESTS: Congestion or delay in the Core Network nodes have an impact on this KPI. Results larger than 20s should be discarded as a failed attempt.

STATISTICS : None available for this KPI

1) Initial Tuning2) Troubleshooting (E2E)




Pre launched / Initially Tuned (no data)KPI


2.2.4. IntegrityPS Interactive R99 User Throughput UL (User Throughput R99 UL)

P6 Optional

GENERALDefinition

The Packet-Switched Interactive R99 User Throughput UL (User Throughput R99 UL) is the average user throughput for PS Data in Uplink evaluation (kbps) on a R99 Radio Bearer. It includes user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's.

The most accurate method to measure User Throughput R99 UL is by Drive tests. The upload file size divided by the time to complete the upload and then taken as the indicator of user throughput. For high target throughput values, static tests are preferred.

Calculated with Counter Statistics, User Throughput R99 UL is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions, padding bits, data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cellFormula

Alternative Formula


Medium

KPI REDUCTION: None

Highly Feature Dependant: Impacted by Radio Env. RAN nodes, PS Core nodes; RBS Hardware; large variations between Drive test and Statistics measurement.


Drive Test/Statistics Golden Cluster/All Clusters QoSMeasurement Execution

DRIVE TESTS:Drive test with call sequences downloading a file (1MB or 5MB) set up from idle mode. The terminating party is ideally a UDP server attached to the GGSN within the operator domain.Start Trigger: Time for Session Start for upload (or when the first acknowledgement of a user data packet is received in UE.) Stop Trigger: Time for Session End for upload (or when the last acknowledgement of a user data packet is received in UE.)STATISTICS: Counters for Packet Throughput are calculated on a per RAB basis for R99 DCH UL PS Interactive.Entry and Exit CriteriaGENERAL:No IP losses shall exist. Tested by conducting at least 1000 ping commands from the UE to the test server, where all shall be successful. There are no Transmission or Core limitations to maximum user throughput.STATISTICS:Using counter statistics, the user throughput is dependant on the file sizes being downloaded by all end users in the network. Smaller file size downloads would result in lower counter statistic throughputs, and therefore network counters could reflect an inaccurate perception of the network.


GENERAL:Big deviations between Drive test results (mostly high speeds) and Statistics(low speeds in average)!! High R99 throughput would depend on the optional RAB combinations availabe in the network for R99 ULDRIVE TESTS:Usually large FTP large files in tuned areas (mostly on 384 RAB) achieve speeds above 250 kbpsSTATISTICS: Averaged, mostly HTTP where there is no need for high speeds (internet site downloaded before switching to 384) and also transitions from 64/128/384 to EUL.






Documents

KPI Library - Definitions, Formula