You are on page 1of 36

KPI LIBRARY

KPIBASEDACCEPTANCE

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:
Quality of Service (QoS)

Service Accessibilty

Service Retainability

Service Integrity

QoS Network Performance

Features & Functionalities

Design& Resources Dimensioning & Facilities

Reliability Performance Performance Monitoring (Nodes, System)

O&M Maintainabilty (Node, system Performance Availability)

Maintenance Support SLAs Performance

Interfaces, Transmission Transmission Performance and Transport

Availablity Performance

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.

Low Method Measurement Area KPI Domain Measurement Execution Entry and Exit Criteria Conditions/Commercial Implication Required Services/Prerequisites . GENERAL Description of the meaning of the KPI and how the formula is built. All Cluster. Counters Golden Cluster. Description of all the counters included in the formula and their triggering conditions. Not Recommended Definition Formula Alternative Formula User Impact Contractual Information High..) for Drive tests and Statistics.b. Some tips about aggregation method. Eventual comments or notes about KPI inconsistency or statistical limit.c) Area The main six areas for performance monitoring Name SW Release Recommendation KPI Name Applicable SW release Contractual classification of the KPI according to the Ericsson KPI strategy and ITU-T / ETSI specification. Drop call – high) Important contractual implications linked to the specific KPI. Drive Test (general) formula High level formula used for statistics (Counter based) CONTRACTUAL INFORMATION Defines relevance of the KPI to the end user experience (i. Required design and performance improvement services needed for specific KPI contractual commitment. Initial Tuning. MEASUREMENT Description on how to perform the measurement Defines applicable Acceptance measurement area for the KPI Defines KPI Domains as per KPI strategy and ITU-T and ETSI specifications Details on measurement execution (call sequences. Medium. Optimization.e. start stop triggers.4 Fields Description Field Name Description KPI Range/Value a: Recommendation b: User Impact c: Area 1) Completion 2)Accessibility 3)Retainability 4)Integrity 5)Mobility 6)Others Number Structured No of KPI (a.e. QoS. Design. WCDMA RAN P6 Recommended.. Drive Test.) TARGETS AND IMPLICATIONS Verbal argumentation to support Sales in the commercial phase handling risk.. confidence intervals. Network Performance/(sub levels) i. like what network elements are impacting the KPIs or if KPI can replace other KPI(s). Pre requisites to start the measurement like Known limitations and data exclusion (number of samples. Optional.

1 Recommended KPIs No 1 2 3 4 5 6 Recommended KPI Call Completion Success Rate Speech (CCSR Speech) Call Completion Success Rate CS64 (CCSR Video) Call Completion Success Rate PS (CCSR PS) PS Interactive R99 User Throughput (User Throughput R99) PS Interactive HSDPA User Throughput (User Throughput HSDPA) PS Interactive EUL User Throughput (User Throughput EUL) User Impact High High High High High High .4.

Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/.Drop Call Rate (DCR) Speech] within a cell or RNC. 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.1% . divided by the total number of call setup attempts for speech calls. CCSR Speech measured by Drive tests.700 samples needed .1.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 +/.1.2% . RAN nodes. Definition Completion Call Completion Success Rate Speech (CCSR Speech) GENERAL P6 Recommended The Call Completion Success Rate Speech (CCSR Speech) is defined as the ratio of successful normal call disconnections. High KPI Impacted by Radio Env. Calculated with Counter Statistics. It is the probability of successfully initiating. CS Core nodes and interfaces MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences (120s or 180s) set up from idle mode. presents proportion of speech calls which are successfully setup.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI No Area Name 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) SW Rel Recommendation . holding and then terminating a speech call from an end user perspective. Formula Alternative Formula CONTRACTUAL INFORMATION User Impact Contractual Information KPI REDUCTION: Can replace Accessibility (CSSR Speech) and Retainability (1-DCR Speech) KPIs.5% and DCR 0.KPI No Area Name SW Rel Recommendation 1. The terminating party shall be fixed test line.to exclude faults and radio environment impact from the terminating party STATISTICS : High value warning: To reach CCSR of 99% CSSR should be 99.2% .7 h (120s call) or 10h (180s call) of DT measurements with a target of 98% To reach Confidence Interval +/. held and released by the initiating party. CCSR Speech is a product of Accessibility [Call Setup Success Rate (CSSR) Speech] and Retainability [1 .200 samples needed .200 samples needed with target 98% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: MTM calls to be avoided .

1% . MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences (120s or 180s) set up from idle mode. presents proportion of speech calls which are successfully setup.200 samples needed with target 98% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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 COUNTER STATISTICS : High value warning: To reach CCSR of 98% CSSR should be 99% and DCR 1%. 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.2% . Network traffic is traditionally low for this KPI and statistical performance fluctuates. 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 Criteria DRIVE TESTS: To reach Confidence Interval +/.Drop Call Rate (DCR) Video] within a cell or RNC.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 +/. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI No Area Name 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) SW Rel Recommendation . Terminating party is static 3G phone in good radio Env. held and released by the initiating party.1.1.200 samples needed . divided by the total number of call setup attempts for video calls. Definition Completion Call Completion Success Rate CS64 (CCSR Video) GENERAL P6 Recommended The Call Completion Success Rate CS64 (CCSR Video) is defined as the ratio of successful normal call disconnections.1. High KPI Impacted by Radio Env RAN nodes.2% . Calculated with Counter Statistics.700 samples needed . CCSR Video is a product of Accessibility [Call Setup Success Rate (CSSR) Video] and Retainability [1 . CS Core nodes. Formula CCSR(Video) = Alternative Formula # Normal _ Video _ Call _ Disconnections #Video _ Call _ Attempts # RRC _ Success # RAB _ Success # RAB _ Normal _ Re lease × × # RRC _ Attempt # RAB _ Attempt # RAB _ Normal _ Re lease+ # RAB _ Abnormal _ Re lease CONTRACTUAL INFORMATION Contractual Information CCSR (Video) = User Impact KPI REDUCTION: Can replace Accessibility (CSSR Video) and Retainability (1-DCR Video) KPIs.7 h (120s call) or 10h (180s call) of DT measurements with a target of 98% To reach Confidence Interval +/.

Calculated with Counter Statistics. CCSR PS is independent of the throughput of any download. many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 5MB file (FTP). It is the probability of successfully initiating.1. Formula CCSR ( PS ) = Alternative Formula # Normal _ PS _ Call _ Disconnections # PS _ Call _ Attempts # RRC _ Success # RAB _ Success # RAB _ Normal _ Re lease × × # RRC _ Attempt # RAB _ Attempt # RAB _ Normal _ Re lease+ # RAB _ Abnormal _ Re lease CONTRACTUAL INFORMATION Contractual Information CCSR ( PS ) = User Impact High KPI REDUCTION: Can replace Accessibility (CSSR PS) and Retainability (1-DCR PS) KPIs. CCSR PS measured by Drive tests. 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. M-PBN and PS nodes.5Mbps) with a target of 98% STATISTICS: With low sample size it is possible to have CCSR > 100% (terminations greater than new calls) TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : High value warning: To reach CCSR of 99% CSSR should be 99.8% . Definition Completion Call Completion Success Rate PS (CCSR PS) GENERAL P6 Recommended The Call Completion Success Rate PS (CCSR PS) is defined as the ratio of successful normal call disconnections.5% and DCR 0. avg throughput 200kbps) with a target of 98% To reach Confidence Interval +/.8% .11 h of DT measurements (R99. held and released by the initiating party. either HTTP or FTP or UDP. CCSR PS (HSDPA) and CCSR PS (EUL) KPI Impacted by Radio.1. presents proportion of sessions which are successfully setup. throughput 1. Merges all PS Services for Call Completion together.2 h of DT measurements (HS. Session errors (caused by FTP problems.180 samples needed . etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle. CCSR PS is a product of Accessibility [Call Setup Success Rate (CSSR) PS] and Retainability [1 .1.180 samples needed .Drop Call Rate (DCR) PS] within a cell or RNC. holding and then terminating a packet connection from an end user perspective. user aborted.1. including CCSR PS (R99). 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. divided by the total number of call setup attempts for packet calls.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) .

TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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 kbps STATISTICS: Averaged. The terminating party is ideally a UDP server attached to the GGSN within the operator domain.5. data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cell Formula User _ Throughput _( R99) = Alternative Formula RLC _ SDU _ Data(kb) RLC _ SDU _ Duration User _ Throughput _( R99) = User Impact Download _ File _ Size _ in _ kbits Session _ End _ Time(s) − Session _ Start _ Time(s) CONTRACTUAL INFORMATION Contractual Information KPI REDUCTION: None High KPI Impacted by Radio Env. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI No Area Name 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) SW Rel Recommendation . Calculated with Counter Statistics. For high target throughput values. Tested by conducting at least 1000 ping commands from the UE to the test server. Definition Integrity PS Interactive R99 User Throughput DL (User Throughput R99 DL) GENERAL P6 Recommended 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.No Area Name SW Rel Recommendation 1. where all shall be successful. It includes user data but excluding retransmissions. There are no Transmission or Core limitations to maximum user throughput. padding bits. Smaller file size downloads would result in lower counter statistic throughputs. static tests are preferred. Entry and Exit Criteria STATISTICS: Using counter statistics. The download file size divided by the time to complete the download and then taken as the indicator of user throughput. Start Trigger: Time for Session Start for the download Stop Trigger: Time for Session End for the download STATISTICS: Counters for Packet Throughput are calculated on a per RAB basis for R99 DCH PS Interactive Traffic No IP losses shall exist. The most accurate method to measure User Throughput R99 is by Drive tests. and therefore network counters could reflect an inaccurate perception of the network. padding bits. big variations between Drive test and Statistics measurement. RAN nodes. mostly HTTP where there is no need for high speeds (internet site downloaded before switching to 384) and also transitions from HS to 64. User Throughput R99 is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions.1. the user throughput is dependant on the file sizes being downloaded by all end users in the network. MEASUREMENT Measurement Area KPI Domain Method Drive Test/Statistics Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences downloading a file (5MB or 10MB) set up from idle mode. PS Core nodes. data PDU headers and RLC control PDU's.

padding bits. Ericsson Controlled Environment Best In Class (NETQB) / Optimized 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) Results in Ericsson Controlled Environment is for UE Category 7/8.1. PS Core nodes.1. Entry and Exit Criteria STATISTICS: Using counter statistics. Definition Integrity PS Interactive HSDPA User Throughput (User Throughput HSDPA) GENERAL P6 Recommended 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. The download file size divided by the time to complete the download and taken as the indicator of user throughput. Feature dependent (Dyn Code allocation). MEASUREMENT Measurement Area KPI Domain Method Drive Test/Statistics Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences downloading a file (50MB) set up from idle mode. the user throughput is dependant on the file sizes being downloaded by all end users in the network. Start Trigger: Time for Session Start for the download Stop Trigger: Time for Session End for the download STATISTICS: Counters for Packet Throughput are calculated on a per RAB basis for HSDPA PS Interactive Traffic and agregated on Cell or RNC level. RAN nodes. No IP losses shall exist. TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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.5. data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cell Formula User _ Throughput _( HSDPA) = Alternative Formula RLC _ SDU _ Data(kb) RLC _ SDU _ Duration User _ Throughput _( HSDPA) = User Impact Download _ File _ Size _ in _ kbits Session _ End _ Time( s) − Session _ Start _ Time(s) CONTRACTUAL INFORMATION Contractual Information KPI REDUCTION: None High KPI Impacted by Radio Env. where all shall be successful. User Throughput HSDPA is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions. It includes user data but excluding retransmissions. big variations between Drive test and Statistics measurement. Tested by conducting at least 1000 ping commands from the UE to the test server. For high target throughput values. and therefore network counters could reflect an inaccurate perception of the network. static tests are preferred. There are no Transmission or Core limitations to maximum user throughput. The terminating party is ideally a UDP server attached to the GGSN within the operator domain. padding bits. data PDU headers and RLC control PDU's. Smaller file size downloads would result in lower counter statistic throughputs. The most accurate method to measure User Throughput HSDPA is by Drive tests. Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI No Area Name SW Rel Recommendation . Calculated with Counter Statistics.

big variations between Drive test and Statistics measurement.) Stop Trigger: Time for Session End for the upload (or when the last acknowledgement of a user data packet is received in the UE. For high target throughput values. The upload file size divided by the time to complete the upload and taken as the indicator of user throughput. padding bits.1. the user throughput is dependant on the file sizes being downloaded by all end users in the network.1. Entry and Exit Criteria GENERAL: No IP losses shall exist. Transmission Capacity. There are no Transmission or Core limitations to maximum user throughput. STATISTICS: Using counter statistics. padding bits.5. It includes user data but excluding retransmissions. The most accurate method to measure User Throughput EUL is by Drive tests. User Throughput EUL is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions. data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cell Formula User _ Throughput _( EUL) = Alternative Formula RLC _ SDU _ Data(kb) RLC _ SDU _ Duration User _ Throughput _( EUL) = User Impact Upload _ File _ Size _ in _ kbits Session _ End _ Time( s) − Session _ Start _ Time( s) CONTRACTUAL INFORMATION Contractual Information KPI REDUCTION: None High Highly Feature Dependant: KPI Impacted by Radio Env. static tests are preferred. TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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.) STATISTICS: Counters for Packet Throughput are calculated on a per RAB basis for EUL PS Interactive and aggregated on Cell or RNC level. RBS Hardware. Tested by conducting at least 1000 ping commands from the UE to the test server. Calculated with Counter Statistics. Smaller file size downloads would result in lower counter statistic throughputs. data PDU headers and RLC control PDU's. Start Trigger: Time for Session Start for the upload (or when the first acknowledgement of a user data packet is received in the UE. where all shall be successful. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) . PS Core nodes. The terminating party is ideally a UDP server attached to the GGSN within the operator domain. Definition Integrity PS Interactive EUL User Throughput (User Throughput EUL) GENERAL P6 Recommended 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. RAN nodes. MEASUREMENT Measurement Area KPI Domain Method Drive Test/Statistics Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences downloading a file (1MB or 5MB) set up from idle mode. and therefore network counters could reflect an inaccurate perception of the network.

4.2 Optional KPIs No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 Optional KPI Call Setup Success Rate Speech (CSSR Speech) Drop Call Rate Speech (DCR Speech) Call Setup Success Rate CS64 (CSSR CS64) Drop Call Rate CS64 (DCR CS64) Call Setup Success Rate PS (CSSR PS) Drop Call Rate PS (DCR PS) Call Setup Time Speech (CST Speech) BLER Quality Speech Uplink (BLER Speech) Call Setup Time CS64 (CST CS64) BLER Quality CS64 Uplink (BLER CS64) Call Setup Success Rate PS R99 (CSSR PS R99) Call Setup Success Rate PS HSDPA (CSSR PS HSDPA) Call Setup Success Rate PS EUL (CSSR PS EUL) Drop Call Rate PS R99 (DCR PS R99) Drop Call Rate PS HSDPA (DCR PS HSDPA) Drop Call Rate PS EUL (DCR PS EUL) Minutes per Drop PS Interactive (MPD PS) IRAT Handover Success Rate Speech (IRAT Speech) IRAT Cell Change Success Rate for PS Interactive (IRATCC PS) BLER Quality PS Uplink (BLER PS) PDP Context Activation Time PS (PDP Act Time PS) PS Interactive R99 User Throughput UL (User Throughput R99 UL) User Impact High High High High High High Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium .

and interfaces MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences (20s) set up from idle mode.0. High KPI Impacted by Radio Env.7 h (20s call) or DT measurements with a target of 99% STATISTICS: To reach Confidence Interval +/. CSSR Speech measured by Drive tests. CS Core nodes.2. RRC Setup Success should be 99.5% . Definition Accessibility Call Setup Success Rate Speech (CSSR Speech) GENERAL P6 Optional The Call Setup Success Rate Speech (CCSR Speech) is defined as the ratio of successful call setups.4. It is the probability of successfully initiating a speech call from an end user perspective.16. Transmission Capacity.0.1% . Formula CSSR( Speech) = Alternative Formula # Successful _ Speech _ Call _ Setups # Speech _ Call _ Attempts # RRC _ Success # RAB _ Success × # RRC _ Attempt # RAB _ Attempt CONTRACTUAL INFORMATION Contractual Information CSSR( Speech) = User Impact KPI REDUCTION: Can replace RRC Accessibility CS and RAB Accessibility Speech KPIs.400 samples needed . CCSR Speech is a product of the RRC Setup Success Rate and the RAB Setup Success Rate for Speech within a cell or RNC.1500 samples needed with target 99% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: MTM calls to be avoided .to exclude faults and radio environment impact from the terminating party STATISTICS : High value warning: To reach CSSR of 99%. Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/.5% and RAB Setup Success should be 99.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) .1.4 h (20s call) of DT measurements with a target of 99% To reach Confidence Interval +/.5% .KPI No Area Name SW Rel Recommendation 2. Calculated with Counter Statistics. The terminating party shall be fixed test line. presents the proportion of speech calls which are successfully setup by the initiating party. 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. divided by the total number of call setup attempts for speech calls. RAN nodes.1500 samples needed .

0. 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.1500 samples needed . Definition Retainability Drop Call Rate Speech (DCR Speech) GENERAL P6 Optional The Drop Call Rate Speech (DCR Speech) is defined as the ratio of abnormal call disconnections. DCR Speech measured by Drive tests.1500 samples needed with target 1% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: MTM calls to be avoided .1% .13. Calculated with Counter Statistics.50 h (120s call) or 75h (180s call) of DT measurements with a target of 1% STATISTICS: To reach Confidence Interval +/. presents the proportion of speech calls which are successfully released after a specified holding time from when the call was successfully setup.3 h (120s call) or 20h (180s call) of DT measurements with a target of 1% To reach Confidence Interval +/.5% . The terminating party shall be fixed test line.400 samples needed .1.3. Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/.5% .to exclude faults and radio environment impact from the terminating party STATISTICS : High value warning: Difficult to achieve a high value without extensive optimization and sufficient traffic levels Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) . CS Core nodes and interfaces MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences (120s or 180s) set up from idle mode. RAN nodes.0.KPI No Area Name SW Rel Recommendation 2. Start Trigger: Alerting DL Stop Trigger: Disconnect UL (normal call clearing) STATISTICS: Counters for RAB Retainability Speech on Cell or RNC level. It is the probability of successfully holding and terminating a call once it has been successfully initiated. divided by the total number of successful call setups for speech calls. Formula DCR(Speech) = Alternative Formula # Abnormal _ Speech _ Call _ Disconnections # Successful _ Speech _ Call _ Setups # Abnormal _ RAB _ Re lease _ Speech # Abnormal _ RAB _ Re lease _ Speech+ # Normal _ RAB _ Re lease _ Speech CONTRACTUAL INFORMATION Contractual Information DCR( Speech) = User Impact KPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate High KPI Impacted by Radio Env.

Terminating party is static 3G phone in good radio Env. Definition Accessibility Call Setup Success Rate CS64 (CSSR CS64) GENERAL P6 Optional The Call Setup Success Rate CS64 (CCSR CS64) is defined as the ratio of successful call setups.0.1.2500 samples needed with target 98. and interfaces MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences (40s) set up from idle mode.5% .2% STATISTICS: To reach Confidence Interval +/.35 h (40s call) or DT measurements with a target of 98. presents the proportion of video calls which are successfully setup by the initiating party.2500 samples needed .2% To reach Confidence Interval +/. CS Core nodes. RRC Setup Success should be 99 % and RAB Setup Success should be 99%. CSSR CS64 measured by Drive tests. Formula CSSR (CS 64) = # Successful _ CS 64 _ Call _ Setups # CS 64 _ Call _ Attempts Alternative Formula CSSR(CS 64) = User Impact # RRC _ Success # RAB _ Success _ CS 64 × # RRC _ Attempt # RAB _ Attempt _ CS 64 CONTRACTUAL INFORMATION Contractual Information KPI REDUCTION: Can replace RRC Accessibility CS and RAB Accessibility Video KPIs. RAN nodes.0. CSSR CS64 is a product of the RRC Setup Success Rate and the RAB Setup Success Rate for Video within a cell or RNC. 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.10 h (40s call) of DT measurements with a target of 98.2.2% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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%. Transmission Capacity. It is the probability of successfully initiating a video call from an end user perspective. Calculated with Counter Statistics.1% . divided by the total number of call setup attempts for video calls.5% . Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/.700 samples needed . High KPI Impacted by Radio Env.KPI No Area Name SW Rel Recommendation 2. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) .

Terminating party is static 3G phone in good radio Env.600 samples needed .1% .1.KPI No Area Name SW Rel Recommendation 2.5% STATISTICS: To reach Confidence Interval +/. Start Trigger: Alerting DL Stop Trigger: Disconnect UL (normal call clearing) STATISTICS: Counters for RAB Retainability CS64 (Video) on Cell or RNC level. Formula DCR(CS 64) = # Abnormal _ CS 64 _ Call _ Disconnections # Successful _ CS 64 _ Call _ Setups # Abnormal _ RAB _ Re lease _ CS 64 # Abnormal _ RAB _ Re lease _ CS 64+ # Normal _ RAB _ Re lease _ CS 64 CONTRACTUAL INFORMATION Contractual Information Alternative Formula DCR (CS 64) = User Impact KPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate High KPI Impacted by Radio Env.1% .5 h (120s call) or 13h (180s call) of DT measurements with a target of 1.5% .3. CS Core nodes and interfaces MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences (120s or 180s) set up from idle mode. Definition Retainability Drop Call Rate CS64 (DCR CS64) GENERAL P6 Optional The Drop Call Rate CS64 (DCR CS64) is defined as the ratio of abnormal call disconnections. It is the probability of successfully holding and terminating a video call once it has been successfully initiated. makes a high value KPI difficult to achieve Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) . DCR CS64 measured by Drive tests. divided by the total number of successful call setups for CS64 (video) calls. RAN nodes.600 samples needed with target 1. presents the proportion of video calls which are successfully released after a specified holding time from when the call was successfully setup.8.1. Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/.5% To reach Confidence Interval +/. Calculated with Counter Statistics.20 h (120s call) or 30h (180s call) of DT measurements with a target of 1.250 samples needed .5% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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. 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.

1% . DCR PS then a larger file should be downloaded.2 h of DT measurements (HS.2. divided by the total number of call setup attempts for packet calls. If a single drive test is used to measure a Throughput KPI and CSSR PS. CCSR PS is a product of RRC Accessibility PS and RAB Accessibility PS within a cell or RNC.400 samples needed .5Mbps downloading a 1MB file) with a target of 99% STATISTICS: To reach Confidence Interval +/.1.6 h of DT measurements (R99. throughput 1.400 samples needed with a target of 99% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : High value warning: To reach CSSR of 99%. Merges all PS Services for Call Setup Success Rate together. presents the proportion of packet interactive calls which are successfully setup by the initiating party. RRC Accessibility PS should be 99. Transmission Capacity.400 samples needed . CSSR PS measured by Drive tests. e. Formula CSSR( PS ) = Alternative Formula # Successful _ PS _ Call _ Setups # PS _ Call _ Attempts # RRC _ Success # RAB _ Success × # RRC _ Attempt # RAB _ Attempt CONTRACTUAL INFORMATION Contractual Information CSSR( PS ) = User Impact High KPI REDUCTION: Can replace RRC Accessibility PS and RAB Accessibility PS KPIs. Definition Accessibility Call Setup Success Rate PS (CSSR PS) GENERAL P6 Optional The Call Setup Success Rate PS (CSSR PS) is defined as the ratio of successful call setups.2. 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.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) .1% .5. 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 DL STATISTICS: 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 +/. M-PBN and PS nodes.No Area Name SW Rel Recommendation 2. Calculated with Counter Statistics. avg throughput 200kbps downloading a 1MB file) with a target of 99% To reach Confidence Interval +/.g. CSSR PS (HSDPA) and CSSR PS (EUL) KPI Impacted by Radio. 5MB or 10MB. many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 1MB file (FTP).5% and RAB Accessibility PS should be 99.1% . including CSSR PS (R99).

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 +/. 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.400 samples needed . Formula DCR( PS ) = Alternative Formula # Abnormal _ PS _ Call _ Disconnections # Successful _ PS _ Call _ Setups # RAB _ Abnormal _ Re lease # RAB _ Normal _ Re lease+ # RAB _ Abnormal _ Re lease Contractual Information DCR( PS ) = User Impact CONTRACTUAL INFORMATION High KPI REDUCTION: Merges all PS Services for Drop Rate together.23 h of DT measurements (R99. Calculated with Counter Statistics. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. DCR PS (HSDPA) and DCR PS (EUL) KPI Impacted by Radio.KPI No Area Name SW Rel Recommendation 2. Different UE’s and behaviour impact heavily on the network counters and perceived performance Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) Results from NetqB are not shown as a different statistical formula is used .1.4 h of DT measurements (HS.5Mbps) for a 5MB file and a target of 1% STATISTICS: To reach Confidence Interval +/. Session errors (caused by FTP problems. It is the probability of successfully holding and then terminating a packet connection from an end user perspective. avg throughput 200kbps) for a 5MB file and a target of 1% To reach Confidence Interval +/. throughput 1. presents the proportion of PS radio bearers which are held and normally released by the initiating party. user aborted.1% .1% . many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 5MB or 10MB file (FTP).400 samples needed with a target of 99% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : Transitions between channel states make a high target difficult to obtain. divided by the total number of successful call setups for packet connections. etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle. Definition Retainability Drop Call Rate PS (DCR PS) GENERAL P6 Optional The Drop Call Rate PS (DCR PS) is defined as the ratio of abnormal call disconnections. M-PBN and PS nodes.3. DCR PS R99 is independent of the throughput of any download or upload. DCR PS measured by Drive tests.400 samples needed . including DCR PS (R99). either HTTP or FTP or UDP.1% .

.

Radio Optimization and Tuning has a limited influence on the KPI target. STATISTICS: None available for this KPI TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: MTM calls to be avoided – even in a stationary condition. presents the average call setup time of speech calls which are successfully setup by the initiating party.KPI No Area Name SW Rel Recommendation 2. Calls longer than 30s setup (before the “Alerting” message should be classified as a failed call setup and excluded.2. CS Core nodes and interfaces. CST Speech is unable to be collected and calculated with network counter statistics. Medium KPI Impacted by Radio Env. meaning that speech connection is established. STATISTICS : None available for this KPI Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) Initial Tuning 2) Troubleshooting (CS E2E) . MEASUREMENT Measurement Area KPI Domain Method Drive Test Measurement Execution Golden Cluster QoS DRIVE TESTS: Drive test with call sequences (20s) set up from idle mode. Formula CST (Speech) = ∑ Speech _ Call _ Setup _ Time _(Time @ Start _ Trigger − Time @ Stop _ Trigger) # Successful _ Speech _ Call _ Setups CONTRACTUAL INFORMATION Alternative Formula User Impact Contractual Information KPI REDUCTION: Can replace RRC Setup Time and RAB Setup Time Speech KPIs. RAN nodes. The setup time is a taken as a Mobile Originating Connection (MOC) for Speech from a UE to a PSTN terminating connection.2. Start Trigger: Time of “Call Attempt” or first “RRC Connection Request” UL Stop Trigger: Time of “Alerting” DL STATISTICS: None available for this KPI Entry 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. CST Speech measured by Drive tests. the call setup time would be affected by the radio environment in the terminating party. Definition Accessibility Call Setup Time Speech (CST Speech) GENERAL P6 Optional The Call Setup Time Speech (CST Speech) is defined as the duration of time taken to access the Speech service successfully. The terminating party shall be fixed test line.

2. MEASUREMENT Measurement Area KPI Domain Method Drive Test/Counters Measurement Execution 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: When calculating Uplink BLER using CTR measurements. RAN nodes and parameter settings. noise limitations. BLER is an indication of speech quality since a block error means that the entire speech frame is erased and needs to be replaced. 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. TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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. STATISTICS: Statistics can be obtained using the performance CTR measurement INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the Cluster Cell Set. BLER Speech Uplink defined in this KPI is an uplink measurement only and can be calculated with network counter statistics or network recordings. Impacting BLER and Speech Quality are the interference.4. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review (Dimensioning) 2) Troubleshooting (CS) Results in this Bar Graph for Uplink BLER using RNC level counters. . Formula BLER _UL _(Speech) = # Number _ of _ Faulty _ Transport _ Blocks _ Speech Alternative Formula # Number _ of _ Transport _ Blocks _ Speech CONTRACTUAL INFORMATION User Impact Contractual Information KPI REDUCTION: Partly is related to Speech Quality (MOS-PESQ) Medium KPI Impacted by Radio Env. This KPI therefore only measures the Uplink BLER. therefore affecting the perceived quality of the connection. Ericsson should control the parameters for setting BLER targets for each service. up to 16 simultaneous UE’s can be recorded in the selected Cluster (Not all calls are represented). STATISTICS: Recommended to have at least 600 normally terminated Speech Calls during a 5 hour collection period. RNC level statistics cannot be broken into Clusters. Network RNC level counters collect statistics on the the number of Transport Blocks and number of Faulty Transport Blocks for an RNC-wide perspective. mobile speed (fading frequency) and time dispersion.KPI No Area Name SW Rel Recommendation 2. Definition Integrity BLER Quality Speech Uplink (BLER Speech Uplink) GENERAL P6 Optional The BLER Quality Speech Uplink (BLER Speech) is defined as the ratio of faulty transport blocks to transmitted transport blocks for a speech connection.

Terminating party is static 3G phone in good radio Env. CST CS64 is unable to be collected and calculated with network counter statistics. STATISTICS : None available for this KPI Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) Initial Tuning 2) Troubleshooting (CS E2E) . 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 TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Time needed for terminating UE for automatic answer should be deducted from the calculations or included in the KPI. Medium KPI Impacted by Radio Env. RAN nodes.KPI No Area Name SW Rel Recommendation 2. meaning that video connection is established.2. Definition Accessibility Call Setup Time CS64 (CST CS64) GENERAL P6 Optional The Call Setup Time CS64 (CST CS64) is defined as the duration of time taken to access the CS64 (video) service successfully. presents the average call setup time of video calls which are successfully setup by the initiating party. The setup time is a taken as a Mobile Originating Connection (MOC) for video to another UE terminating connection (UE to UE).2. CST CS64 measured by Drive tests. MEASUREMENT Measurement Area KPI Domain Method Drive Test Measurement Execution Golden Cluster QoS DRIVE TESTS: Drive test with call sequences (40s) set up from idle mode. Start Trigger: Time of “Call Attempt” or first “RRC Connection Request” UL Stop Trigger: Time of “Alerting” DL STATISTICS: None available for this KPI Entry 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. CS Core nodes and interfaces. Radio Optimization and Tuning has a limited influence on the KPI target. Formula CST (CS 64) = ∑ CS 64 _ Call _ Setup _ Time _(Time @ Start _ Trigger − Time @ Stop _ Trigger) # Successful _ CS 64 _ Call _ Setups CONTRACTUAL INFORMATION Alternative Formula User Impact Contractual Information KPI REDUCTION: Can replace RRC Setup Time and RAB Setup Time Video KPIs. This is roughly 2s.

RNC level statistics cannot be broken into Clusters. Results can be collected via the UETR recording function INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the UE IMSI. MEASUREMENT Measurement Area KPI Domain Method Drive Test/Counters Measurement Execution Golden Cluster QoS DRIVE TESTS: Calls should be set up in a similar manner to CCSR CS64 and DCR CS64. Definition Integrity BLER Quality CS64 Uplink (BLER CS64 Uplink) GENERAL P6 Optional 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. UETR / CTR Downlink BLER are reported as % and therefore can be inaccurate when aggredated together. RAN nodes and parameter settings. therefore affecting the perceived quality of the connection. STATISTICS: Recommended to have at least 600 normally terminated Video Calls during a 5 hour collection period. Network RNC level counters collect statistics on the the number of Transport Blocks and number of Faulty Transport Blocks for an RNC-wide perspective. Ericsson should control the parameters for setting BLER targets for each service. This KPI therefore only measures the Uplink BLER. BLER CS64 Uplink defined in this KPI is an uplink measurement only and can be calculated with network counter statistics or network recordings. up to 16 simultaneous UE’s can be recorded in the selected Cluster (Not all calls are represented).KPI No Area Name SW Rel Recommendation 2. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review (Dimensioning) 2) Troubleshooting (CS) . mobile speed (fading frequency) and time dispersion.2. noise limitations. STATISTICS: When calculating Uplink BLER using CTR measurements.4. 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. TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites Downlink BLER is not uniformly reported by different UE’s. Impacting BLER and Quality is the interference. STATISTICS: Statistics can be obtained using the performance CTR measurement INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the Cluster Cell Set. Formula BLER _ UL(CS 64) = # Number _ of _ Faulty _ Transport _ Blocks _ CS 64 Alternative Formula # Number _ of _ Transport _ Blocks _ CS 64 CONTRACTUAL INFORMATION User Impact Contractual Information KPI REDUCTION: None Medium KPI Impacted by Radio Env. BLER is an indication of quality since a block error means that the frame is erased or needs to be replaced.

If a single drive test is used to measure a Throughput KPI and CCSR PS R99 then a larger file should be downloaded.KPI No Area Name SW Rel Recommendation 2. 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.2.1.5 h of DT measurements (R99. Medium KPI Impacted by Radio.1% . CSSR PS R99 measured by Drive tests. avg throughput 200kbps downloading a 500KB file) with a target of 99% STATISTICS: With low sample size it is possible to have CSSR > 100%. 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 DL COUNTER STATISTICS: Counters for Packet Accessibility are aggregated on Cell or RNC level Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/. divided by the total number of call setup attempts for packet calls using a R99 radio bearer. 5MB or 10MB. With a confidence of +/. M-PBN and PS nodes. many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 500KB file (FTP).400 samples needed for a target of 99% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : To reach CSSR of 99%. e.400 samples needed . CCSR PS R99 is a product of RRC Accessibility (PS) and RAB Accessibility R99 (PS) within a cell or RNC.1% .5% and RAB R99 Accessibility should be 99. presents the proportion of R99 radio bearers which are successfully setup by the initiating party.g.2.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) . Definition Accessibility Call Setup Success Rate PS R99 (CSSR PS R99) GENERAL P6 Optional The Call Setup Success Rate PS R99 (CSSR PS R99) is defined as the ratio of successful call setups. Calculated with Counter Statistics. RRC Accessibility should be 99. Formula CSSR( PS _ R99) = Alternative Formula # Successful _ PS _ R99 _ Call _ Setups # PS _ R99 _ Call _ Attempts # RRC _ Success # RAB _ R99 _ Success × # RRC _ Attempt # RAB _ R99 _ Attempt CONTRACTUAL INFORMATION Contractual Information CSSR( PS _ R99) = User Impact KPI REDUCTION: Can replace RRC Accessibility PS and RAB Accessibility R99 PS KPIs.

2.5Mbps downloading a 1MB file) with a target of 99% STATISTICS: With low sample size it is possible to have CSSR > 100%. presents the proportion of sessions which are successfully setup by the initiating party. divided by the total number of call setup attempts for packet calls using a HSDPA radio bearer. many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 1MB file (FTP). e. 5MB or 10MB. Medium KPI Impacted by Radio. 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. Formula CSSR( PS _ HSDPA) = Alternative Formula # Successful _ HSDPA _ R99 _ Call _ Setups # PS _ HSDPA _ Call _ Attempts # RRC _ Success # RAB _ HSDPA _ Success × # RRC _ Attempt # RAB _ HSDPA _ Attempt Contractual Information CSSR( PS _ HSDPA) = User Impact CONTRACTUAL INFORMATION KPI REDUCTION: Can replace RRC Accessibility PS and RAB HSDPA Accessibility PS KPIs. Definition Accessibility Call Setup Success Rate PS HSDPA (CSSR PS HSDPA) GENERAL P6 Optional The Call Setup Success Rate PS HSDPA (CSSR PS HSDPA) is defined as the ratio of successful call setups. With a confidence of +/. If a single drive test is used to measure a Throughput KPI and CCSR PS then a larger file should be downloaded. throughput 1.1.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) .400 samples needed for a target of 99% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : High value warning: To reach CSSR of 99%. M-PBN and PS nodes.KPI No Area Name SW Rel Recommendation 2. CSSR PS HSDPA measured by Drive tests. RRC Accessibility should be 99.g.7 h of DT measurements (HS.1.1% . CCSR PS HSDPA is a product of RRC Accessibility (PS) and RAB HSDPA Accessibility (PS) within a cell or RNC.400 samples needed . Calculated with Counter Statistics.5% and RAB HSDPA Accessibility should be 99. 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 DL COUNTER STATISTICS: Counters for Packet Accessibility are aggregated on Cell or RNC level Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/.1% .

divided by the total number of call setup attempts for packet calls using a EUL radio bearer.5% and RAB EUL Accessibility should be 99. CSSR PS EUL measured by Drive tests.400 samples needed . With a confidence of +/. Calculated with Counter Statistics. Definition Accessibility Call Setup Success Rate PS EUL (CSSR PS EUL) GENERAL P6 Optional The Call Setup Success Rate PS EUL (CSSR PS EUL) is defined as the ratio of successful call setups.1% .KPI No Area Name SW Rel Recommendation 2. M-PBN and PS nodes.1% . CCSR PS EUL is a product of RRC Accessibility (PS) and RAB Accessibility EUL (PS) within a cell or RNC. 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 DL COUNTER STATISTICS: Counters for Packet Accessibility are aggregated on Cell or RNC level Entry and Exit Criteria DRIVE TESTS: To reach Confidence Interval +/. 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. many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test uploading a 500KB file (FTP). Formula CSSR( PS _ EUL) = Alternative Formula # Successful _ EUL _ R99 _ Call _ Setups # PS _ EUL _ Call _ Attempts # RRC _ Success # RAB _ EUL _ Success × # RRC _ Attempt # RAB _ EUL _ Attempt Contractual Information CSSR( PS _ EUL) = User Impact CONTRACTUAL INFORMATION KPI REDUCTION: Can replace RRC Accessibility PS and RAB Accessibility EUL PS KPIs.400 samples needed for a target of 99% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : High value warning: To reach CSSR of 99%. RRC Accessibility should be 99. Medium KPI Impacted by Radio.5 h of DT measurements (EUL. avg throughput 400kbps uploading a 500KB file) with a target of 99% STATISTICS: With low sample size it is possible to have CSSR > 100%. presents the proportion of sessions which are successfully setup by the initiating party.2.1.5% Ericsson Controlled Environment Best In Class (NETQB) / Optimized 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) NetqB data is currently unavailabe for EUL Statistics Average (NetQB) / Tuned Pre launched / Initially Tuned .1.

3. presents the proportion of R99 radio bearers which are held and normally released by the initiating party. avg throughput 200kbps) for a 5MB file and a target of 1% STATISTICS: To reach Confidence Interval +/.KPI No Area Name SW Rel Recommendation 2. 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. Calculated with Counter Statistics. DCR PS R99 measured by Drive tests. Formula DCR( PS _ R99) = # Abnormal _ PS _ R99 _ Call _ Disconnections # Successful _ PS _ R99 _ Call _ Setups # RAB _ Abnormal _ Re lease _ R99 # RAB _ Normal _ Re lease _ R99+ # RAB _ Abnormal _ Re lease _ R99 CONTRACTUAL INFORMATION Contractual Information Alternative Formula DCR( PS _ R99) = User Impact KPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate Medium KPI Impacted by Radio.400 samples needed . etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle. Ericsson Controlled Environment Best In Class (NETQB) / Optimized 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) Results from NetqB are not shown as a different statistical formula is used Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) . DCR PS R99 is independent of the throughput of any download. either HTTP or FTP or UDP. Ericsson therefore recommends the KPI Minutes per Drop PS Interactive (MPD PS) MEASUREMENT Measurement Area KPI Domain Method Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 5MB file (FTP). Definition Retainability Drop Call Rate PS R99 (DCR PS R99) GENERAL P6 Optional The Drop Call Rate PS R99 (DCR PS R99) is defined as the ratio of abnormal call disconnections.1% . many factors outside E/// control. user aborted. 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.1. divided by the total number of successful call setups for packet connections using a R99 radio bearer. 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 Criteria DRIVE TESTS: To reach Confidence Interval +/. M-PBN and PS nodes.1% .400 samples needed with a target of 1% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : Drop rate is heavily impacted by channel state transitions including URA / FACH / DCH / HSDPA and by different UE’s.23 h of DT measurements (R99. It is the probability of successfully holding and then terminating a R99 packet connection from an end user perspective. 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.

KPI No Area Name SW Rel Recommendation 2. Ericsson Controlled Environment Best In Class (NETQB) / Optimized 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) Results from NetqB are not shown as a different statistical formula is used Average (NetQB) / Tuned Pre launched / Initially Tuned .400 samples needed with a target of 1% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : Drop rate is heavily impacted by channel state transitions including URA / FACH / DCH / HSDPA and by different UE’s. throughput 1. divided by the total number of successful call setups for packet connections using a HSDPA radio bearer. Ericsson therefore recommends the KPI Minutes per Drop PS Interactive (MPD PS) MEASUREMENT Measurement Area KPI Domain Method Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 5MB file (FTP). Definition Retainability Drop Call Rate PS HSDPA (DCR PS HSDPA) GENERAL P6 Optional The Drop Call Rate PS HSDPA (DCR PS HSDPA) is defined as the ratio of abnormal call disconnections. Session errors (caused by FTP problems. user aborted.3. presents the proportion of HSDPA radio bearers which are held and normally released by the initiating party. 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. Calculated with Counter Statistics. M-PBN and PS nodes. It is the probability of successfully holding and then terminating a R99 packet connection from an end user perspective. DCR PS HSDPA measured by Drive tests. 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.1% .4 h of DT measurements (HS. Formula DCR(PS _ HSDPA) = # Abnormal _ PS _ HSDPA _ Call _ Disconnections # Successful _ PS _ HSDPA _ Call _ Setups Alternative Formula # RAB _ Abnormal _ Re lease _ HSDPA # RAB _ Normal _ Re lease _ HSDPA+ # RAB _ Abnormal _ Re lease _ HSDPA CONTRACTUAL INFORMATION User Impact Contractual Information DCR( PS _ HSDPA) = KPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate Medium KPI Impacted by Radio.1% .400 samples needed . 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. 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 is independent of the throughput of any download. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. either HTTP or FTP or UDP.5Mbps) for a 5MB file and a target of 1% STATISTICS: To reach Confidence Interval +/.

Ericsson therefore recommends the KPI Minutes per Drop PS Interactive (MPD PS) MEASUREMENT Measurement Area KPI Domain Method Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 5MB file (FTP).1% .1% . Formula DCR(PS _ EUL) = # Abnormal _ PS _ EUL _ Call _ Disconnections # Successful _ PS _ EUL _ Call _ Setups Alternative Formula # RAB _ Abnormal _ Re lease _ EUL # RAB _ Normal _ Re lease _ EUL+ # RAB _ Abnormal _ Re lease _ EUL CONTRACTUAL INFORMATION User Impact Contractual Information DCR( PS _ EUL) = KPI REDUCTION: Partly incorporates Soft/Softer Handover Success Rate Medium KPI Impacted by Radio. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) Results from NetqB are not shown as a different statistical formula is used . etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle. divided by the total number of successful call setups for packet connections using a EUL radio bearer.3. DCR PS EUL measured by Drive tests.400 samples needed with a target of 1% TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : Drop rate is heavily impacted by channel state transitions including URA / FACH / DCH / EUL and by different UE’s. 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 Criteria DRIVE TESTS: To reach Confidence Interval +/. Definition Retainability Drop Call Rate PS EUL (DCR PS EUL) GENERAL P6 Optional The Drop Call Rate PS EUL (DCR PS EUL) is defined as the ratio of abnormal call disconnections. 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. presents the proportion of EUL radio bearers which are held and normally released by the initiating party. It is the probability of successfully holding and then terminating a EUL packet connection from an end user perspective. Session errors (caused by FTP problems.1. The KPI is the ability of the network to maintain a packet radio access bearer independent of the user session on the bearer. user aborted.12 h of DT measurements (EUL. 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. either HTTP or FTP or UDP. DCR PS EUL is independent of the throughput of any upload. throughput 400kbps) for a 5MB file and a target of 1% STATISTICS: To reach Confidence Interval +/. M-PBN and PS nodes.KPI No Area Name SW Rel Recommendation 2. Calculated with Counter Statistics.400 samples needed .

M-PBN and PS nodes. throughput 1. avg throughput 200kbps) To reach Confidence Interval +/. Definition Retainability Minutes per Drop PS Interactive (MPD PS) GENERAL P6 Optional 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.3. etc) should not be counted unless the radio access bearer is also abnormally released or there is an abnormal transition to idle.KPI No Area Name SW Rel Recommendation 2. many factors outside E/// control MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test downloading a 5MB file (FTP). MPD PS is independent of the throughput of any download. either HTTP or FTP or UDP. Formula MPD( PS ) = ∑ Time _ Holding _ PS _ Connections(min) # RAB _ Abnormal _ Re lease _ PS Alternative Formula MPD( PS ) = User Impact Measurement _ Period × Average _ No _ PS _ Users # RAB _ Abnormal _ Re lease _ PS CONTRACTUAL INFORMATION Contractual Information KPI REDUCTION: Can replace DCR PS (which includes R99. MPD PS measured by Drive tests.1.11 h of DT measurements (R99. presents the proportion of time PS radio bearers are held by the number of abnormally released packet connections.8% .2 h of DT measurements (HS.8% . user aborted. 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 +/. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Still to be updated. Calculated with Counter Statistics.180 samples needed .1.180 samples needed . HSDPA and EUL DCR) Medium KPI Impacted by Radio. Session errors (caused by FTP problems.5Mbps) STATISTICS: With low sample size it is possible to have DCR > 100% (terminations greater than new calls) TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Calls to internet servers be avoided – many components can be outside E/// responsibility STATISTICS : Drop rate is heavily impacted by channel state transitions including URA / FACH / DCH / HSDPA and by different UE’s. 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.1. 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. Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E) 4) Optimization (Statistics) . 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.

Statistics is recommended.2% – 190 samples needed .KPI No Area Name SW Rel Recommendation 2. Start Trigger: Handover from UTRAN Command Stop Trigger: Handover from UTRAN Failure STATISTICS: Counters for IRAT Handover Attempts and Success.5. 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. IRAT Speech is a ratio of the number of successful Handovers over the number of attempted handovers. Definition Mobility IRAT Handover Success Rate Speech (IRAT Speech) GENERAL P6 Optional 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.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 TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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 Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E and GSM) 4) Optimization (Statistics) . collected at GSM Relation level and aggregated to Cell and RNC level Entry and Exit Criteria DRIVE TESTS: Neighbour relations must be defined and updated frequently (during rollout). 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. The terminating party shall be fixed test line. Calculated with Statistics. 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. This can be aggregated to Cell and RNC level Formula IRAT _ Success( Speech) = Alternative Formula # Successful _ IRAT _ Handovers # Attempted _ IRAT _ Handovers # " Handover _ from _ UTRAN _ Failure" IRAT _ Success( Speech) = 1 − CONTRACTUAL INFORMATION # " Handover _ from _ UTRAN _ Command " User Impact Contractual Information KPI REDUCTION: None Medium KPI Impacted by GSM Network performance and interfaces between GSM and UMTS (neighbouring definitions on GSM and UMTS side) MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster/All Clusters – specialized drive route QoS DRIVE TESTS: Drive test with call sequences (360s) set up from idle mode. In the case of a drive test. Special drive route needed (cluster edges) To reach Confidence Interval +/.2.

In the case of a drive test.5. Statistics are recommended. Definition Mobility IRAT Cell Change Success Rate for PS Interactive (IRATCC PS) GENERAL P6 Optional 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.KPI No Area Name SW Rel Recommendation 2. It is the probability of successfully performing a cell change from WCDMA to GSM and continuing the packet connection without the packet call terminating. adding risk to a high value KPI target Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting (E2E and GSM) 4) Optimization (Statistics) . collected at GSM Relation level and aggregated to Cell and RNC level Entry and Exit Criteria DRIVE TESTS: Neighbour relations must be defined and updated frequently (during rollout). IRAT Cell Change PS Handovers can be measured either by Drive tests or Statistics data although due to difficulties in drive test collection. Calculated with Statistics. Special drive route needed (cluster edges) To reach Confidence Interval +/.18 h of DT measurements STATISTICS: The counters are only incremented if a GSM relation exists between the Target and the Source Cell TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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. 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.2. IRAT Cell Change PS is a ratio of the number of successful cell change over the number of attempted cell changes. 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. This can be aggregated to Cell and RNC level Formula IRATCC _ Success( PS ) = 1 − Alternative Formula IRATCC _ Success( PS ) = 1 − User Impact # " Cell _ Change _ Order _ from _ UTRAN _ Failure" # "Cell _ Change _ Order _ from _ UTRAN _ Command " # Cell _ Change _ Order _ Success CONTRACTUAL INFORMATION # Cell _ Change _ Order _ Attempt Contractual Information KPI REDUCTION: None Medium KPI Impacted by GSM Network performance and interfaces between GSM and UMTS (neighbouring definitions on GSM and UMTS side) MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution 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 GGSN Start Trigger: Cell Change Order from UTRAN Command Stop Trigger: Cell Change Order from UTRAN Failure STATISTICS: Counters for IRAT Cell Change Attempts and Success.2% (target 98%) – 190 samples needed .

noise limitations. BLER PS Uplink defined in this KPI is an uplink measurement only and can be calculated with network counter statistics or network recordings. 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.4. STATISTICS: Recommended to have at least 600 normally terminated Speech Calls during a 5 hour collection period. Impacting BLER and Quality is the interference.KPI No Area Name SW Rel Recommendation 2. BLER is an indication of quality since a block error means that the entire frame is erased or retransmitted. up to 16 simultaneous UE’s can be recorded in the selected Cluster (Not all calls are represented). TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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. therefore affecting the perceived quality of the connection and limiting the throughput. RAN nodes MEASUREMENT Method Measurement Area KPI Domain Drive Test/Counters Measurement Execution Golden Cluster QoS DRIVE TESTS: Calls should be set up in a similar manner to CCSR PS and DCR PS.2. STATISTICS: Statistics can be obtained using the performance CTR measurement INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the Cluster Cell Set. RNC level statistics cannot be broken into Clusters. mobile speed (fading frequency) and time dispersion. Formula BLER _ UL( PS ) = # Number _ of _ Faulty _ Transport _ Blocks _ PS Alternative Formula # Number _ of _ Transport _ Blocks _ PS CONTRACTUAL INFORMATION User Impact Contractual Information KPI REDUCTION: None Medium KPI Impacted by Radio Env. Definition Integrity BLER Quality PS Uplink (BLER PS Uplink) GENERAL P6 Optional 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. Network RNC level counters collect statistics on the the number of Transport Blocks and number of Faulty Transport Blocks for an RNC-wide perspective. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review (Dimensioning) 2) Troubleshooting . This KPI therefore only measures the Uplink BLER. STATISTICS: When calculating Uplink BLER using CTR measurements. Results can be collected via the UETR recording function INTERNAL_ MEAS_ TRANSPORT_ CHANNEL_BLER after setup for the UE IMSI.

CS Core nodes and interfaces. STATISTICS : None available for this KPI Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) KPI 1) Initial Tuning 2) Troubleshooting (E2E) . 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. 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” DL STATISTICS: None available for this KPI Entry and Exit Criteria DRIVE TESTS: Recommended to sample 300 calls for the measurement criteria. Formula PDP _ Act _ Time(PS ) = Alternative Formula ∑ PDP _ Context _ Activation _ Time _(Time @ Start _ Trigger − Time @ Stop _ Trigger) # Successful _ PDP _ Context _ Activation _ Accept CONTRACTUAL INFORMATION Contractual Information User Impact KPI REDUCTION: None Medium KPI Impacted by Radio Env.2. If a single drive test is used to measure a Throughput KPI and CCSR PS then a larger file should be downloaded. MEASUREMENT Measurement Area KPI Domain Method Drive Test Measurement Execution Golden Cluster QoS DRIVE TESTS: Drive test downloading a 1MB file (FTP).2. Results larger than 20s should be discarded as a failed attempt. Definition Accessibility PDP Context Activation Time PS (PDP Act Time PS) GENERAL P6 Optional 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.g. STATISTICS: None available for this KPI TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites DRIVE TESTS: Congestion or delay in the Core Network nodes have an impact on this KPI. RAN nodes. 5MB or 10MB. Radio Optimization and Tuning has a limited influence on the KPI target. e. From an end user perspective.KPI No Area Name SW Rel Recommendation 2. 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.

TARGETS AND IMPLICATIONS Conditions/Commercial Implication Required Services / Prerequisites 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 UL DRIVE TESTS:Usually large FTP large files in tuned areas (mostly on 384 RAB) achieve speeds above 250 kbps STATISTICS: Averaged. MEASUREMENT Measurement Area KPI Domain Method Drive Test/Statistics Measurement Execution Golden Cluster/All Clusters QoS DRIVE TESTS: Drive test with call sequences downloading a file (1MB or 5MB) set up from idle mode. data PDU headers and RLC control PDU's. padding bits. Definition Integrity PS Interactive R99 User Throughput UL (User Throughput R99 UL) GENERAL P6 Optional 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. the user throughput is dependant on the file sizes being downloaded by all end users in the network.) STATISTICS: Counters for Packet Throughput are calculated on a per RAB basis for R99 DCH UL PS Interactive. Entry and Exit Criteria GENERAL: No IP losses shall exist. 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. User Throughput R99 UL is a ratio of the sampled RLC throughput measurements (including user data but excluding retransmissions. Calculated with Counter Statistics. The terminating party is ideally a UDP server attached to the GGSN within the operator domain. static tests are preferred. Tested by conducting at least 1000 ping commands from the UE to the test server. PS Core nodes. Smaller file size downloads would result in lower counter statistic throughputs.2. For high target throughput values.4. RAN nodes. RBS Hardware.) Stop Trigger: Time for Session End for upload (or when the last acknowledgement of a user data packet is received in UE. Start Trigger: Time for Session Start for upload (or when the first acknowledgement of a user data packet is received in UE. where all shall be successful. data PDU headers and RLC control PDU's) in kbits/s divided by the number of times data was transmitted in the cell Formula User _ Throughput _( R99) = Alternative Formula RLC _ SDU _ Data(kb) RLC _ SDU _ Duration User _ Throughput _( R99) = User Impact Upload _ File _ Size _ in _ kbits Session _ End _ TimeCONTRACTUAL (s) − Session _ StartINFORMATION _ Time(s) Contractual Information KPI REDUCTION: None Medium Highly Feature Dependant: Impacted by Radio Env. and therefore network counters could reflect an inaccurate perception of the network. There are no Transmission or Core limitations to maximum user throughput.No Area Name SW Rel Recommendation 2. Ericsson Controlled Environment Best In Class (NETQB) / Optimized Average (NetQB) / Tuned Pre launched / Initially Tuned (no data) 1) RND or RND Review 2) Initial Tuning 3) Troubleshooting 4) Optimization (Statistics) . The upload file size divided by the time to complete the upload and then taken as the indicator of user throughput. large variations between Drive test and Statistics measurement. It includes user data but excluding retransmissions. padding bits. The most accurate method to measure User Throughput R99 UL is by Drive tests. STATISTICS: Using counter statistics.