cs core kpis for offer and field acceptance test

s

CS Domain Network Engineering

Top KPIs for CS Core Measurements in Offer Process and Field Acceptance Tests

Up to CS 5.0

March 2007

Robert Kirsch, Network Engineering SN MN PG NT NE 4

Measurements in Offer Process and Field Acceptance Tests

CS5.0 Top KPIs for CS Core Measurements

Copyright (C) Siemens AG 2006

Issued by the Communications Mobile Networks Group St.-Martin-Straße 76 D-81541 München

Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

2

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties for their own purposes could violate the rights of their owners.

Measurements in Offer Process and Field Acceptance Tests CS5.0 Top KPIs for CS Core Measurements

A30862-X1001-C962-2-76-A1 3

Issue history Issue Number

Date of Issue Reason for Update

01/AFI 10/2006 Update of the CS4.0 Version of this document; Chapter 6 –Core Part Transaction delay – is new ; CS.5.0 AFI Version (Initial version for CS5.0)

01/IUS 11/2006 IUS Version 01/IUS 03/2007 Update of the IUS Version;

Chapter 3: correction of KPI formulas (important ones: MOC, MTC, MMC – Success Ratios); update of the measured KPI values. Chapter 4.5 – 4.7 : update of transaction delay values due to new MCS-core measurements

Authors In addition to the author named on the cover page the following persons have collaborated on this document:

Name Department Scholle, Thomas SN MN PG NT NE 4 Jens Schneider SN MN PG NT NE 2


4 A30862-X1001-C962-2-76-A1

Table of Contents

1 Introduction......................................................................................................8

2 Core Network ................................................................................................10 2.1 From CS4.0 to CS5.0 ....................................................................................10 2.2 Core KPI Overview........................................................................................12 2.2.1 KPI.................................................................................................................12 2.2.2 Grade of Service Measurements ..................................................................13 2.3 Areas of Impact to KPI Target Values...........................................................13

3 Definition of KPI.............................................................................................15 3.1 KPI Measurement Conditions .......................................................................15 3.2 KPIs for MSC.................................................................................................22 3.2.1 Mobility and Security .....................................................................................22 3.2.1.1 IMSI Attach Failure Ratio ..............................................................................22 3.2.1.2 Explicit IMSI Detach Success Ratio ..............................................................23 3.2.1.3 LUP Success Ratio .......................................................................................24 3.2.1.4 Inter MSC Location Area Update Failure Ratio.............................................25 3.2.1.5 Intra MSC Periodic Location Update Failure Ratio .......................................27 3.2.1.6 Inter System Location Area Update Failure Ratio (Intra MSC 3G-2G) .........28 3.2.1.7 Inter System Location Area Update Failure Ratio (Intra MSC 2G-3G) .........29 3.2.2 General Call Analysis ....................................................................................29 3.2.2.1 RAB Assignment Setup Failure Ratio ...........................................................29 3.2.2.2 MOC Answered Calls – dropped call rate .....................................................32 3.2.3 Mobile Originated Traffic Analysis.................................................................33 3.2.3.1 Emergency call success ratio........................................................................33 3.2.3.2 MOC Setup Ratio ..........................................................................................34 3.2.3.3 Mobile Originated Call Failure Ratio (All Network)........................................35 3.2.3.4 MOC Traffic Channel Allocation Ratio ..........................................................37 3.2.3.5 MOC-PSTN Success Rate............................................................................38 3.2.3.6 Data calls success Ratio (MOC-PSTN) ........................................................44 3.2.4 MMC KPIs .....................................................................................................46 3.2.4.1 MMC Success Ratio......................................................................................46 3.2.4.2 Data calls success Ratio (MMC) ...................................................................51 3.2.5 Mobile Terminating Traffic KPIs ....................................................................53 3.2.5.1 MTC Success Ratio.......................................................................................53 3.2.5.2 MTC Failure Ratio .........................................................................................57 3.2.5.3 Paging Procedure Failure Ratio ....................................................................59 3.2.5.4 Data calls succes Ratio (MTC).....................................................................60 3.2.5.5 MTC Traffic Channel Allocation Ratio ...........................................................63 3.2.6 Handover KPIs ..............................................................................................64 3.2.6.1 Handover Success Ratio...............................................................................64 3.2.6.2 Intra-MSC-Handover Success Ratio .............................................................65 3.2.6.3 Intra MSC Inter System (3G-2G) HO failure Ratio........................................66 3.2.6.4 Inter MSC Inter System (3G-2G) HO Failure Ratio.......................................68 3.2.6.5 Inter-MSCA-Handover Success Ratio...........................................................68


A30862-X1001-C962-2-76-A1 5

3.2.6.6 Inter- MSCB- Handover Success Ratio ........................................................69 3.2.6.7 Inter MSC SRNS Relocation Failure Ratio ...................................................70 3.2.6.8 Handover - Message Flows/Triggerpoints ....................................................71 3.2.7 SMS Analysis ................................................................................................77 3.2.7.1 SMS Failure Ratio .........................................................................................77 3.2.7.2 SMS-MT Failure Ratio...................................................................................79 3.2.7.3 SMS-MT Delivery Failed Ratio......................................................................80 3.2.7.4 SMS-MT No Facility Ratio.............................................................................81 3.2.7.5 SMS- MO Failure Ratio .................................................................................82 3.2.7.6 Mobile Originating SMS Failure Ratio (IuCS interface) ................................83 3.2.7.7 SMS-MO Delivery failed Ratio ......................................................................84 3.2.8 IN/CAMEL Dialog Failure Ratio.....................................................................85 3.2.9 IN request Failure Ratio ................................................................................86 3.2.10 Supplementary Services Request Failure Ratio ...........................................88 3.2.11 Inter MGW HO Failure Ratio (MSC-S only) ..................................................91 3.3 HLR/AC related KPIs ...................................................................................92 3.3.1 MAP Dialog – MSRN Provisioning Success Ratio........................................92 3.3.2 Cancel Location Failure Ratio .......................................................................92 3.3.3 MAP Dialog – Interrogation Success Ratio...................................................94 3.3.4 IMEI Check Break down................................................................................95 3.3.5 Authentication Vector Request Success Ratio .............................................96 3.3.6 Authentication Failure Ratio (Network authenticates USIM).........................98 3.3.7 Authentication Failure Ratio (Network authenticates SIM) ...........................99 3.4 MGW-KPIs ..................................................................................................100 3.4.1 Transcoding Failure Ratio ...........................................................................100 3.4.2 Data Call Failure Ratio ................................................................................100 3.4.3 Data Call Failure Ratio (per call type) .........................................................101 3.4.4 Inserted Announcement Failure Ratio ........................................................102 3.4.5 Inserted Tone Failure Ratio.........................................................................103 3.4.6 Conference Call Establishment Failure Ratio .............................................104 3.4.7 Receiving IP Bearer Negotiation Failure Ratio ...........................................104 3.4.8 Initiating IP Bearer Negotiation Failure Ratio..............................................105

4 Core-Part of Transaction Delay...................................................................108 4.1 Scope of Calculations .................................................................................109 4.2 Generic Assumptions ..................................................................................110 4.3 Optional Configuration Variants ..................................................................111 4.4 Basic Configurations ...................................................................................112 4.4.1 MSC - Roles................................................................................................112 4.4.2 Modifications of the basic Scenarios...........................................................112 4.5 CS4.0 – Transaction Delay in TDM based Core Network ..........................113 4.6 CS5.0 – Transaction Delay in R99 architecture..........................................118 4.7 CS5.0 – Transaction Delay in R4 architecture............................................123

Abbreviations..............................................................................................................129


6 A30862-X1001-C962-2-76-A1

List of Figures and Tables Figure 2-1: Step from CS4.0 MSC to CS5.0 MSC Server & CS 5.0 Combined MSC. 11

Table 3-1: MSC/MSC-S KPIs for Offer ........................................................................ 19 Table 3-2: KPIs with Quantity of result Time ............................................................... 19 Table 3-3: HLR/AC related KPIs.................................................................................. 20 Table 3-4: ‘Additional’ MSC/MSC-S KPIs.................................................................... 21 Table 3-5: MGW-KPIs.................................................................................................. 21 Table 3-6: ‘Additional’ MGW-KPIs ............................................................................... 22

References

[PM_CONCEPT] Performance Measurements Counter Concept and Guideline P30309-A1958-A000-06-7618 Gerald Huber/ PSE MCS CS 22

[KPI_basic] KPI for Offer Process and Field Acceptance Test Basic Document A30862-X1001-D007-1-76A1

[E2E_KPIs] UMTS End-to-End Key Performance Indicators for Offer Process and Field Acceptance Tests (UMR4.0/UCR4.0) A50016-G5000-G534-5-7618 Jens Schneider / Com MN PG NT NE 2

[CNT_descr_CS40 ] Traffic and Performance Data Counter Description A50016-D1112-G802-5-7618

[CNT_descr_CS50 ] Traffic and Performance Data Counter Description A50016-E1113-G802-1-7618

[MGW_Sys_Arch] Media Gateway System Architecture Functional Specification P30309-A4207-A255-02-76J1

[KPI_descr_CS50] Description of Key Performance Indicators (KPI) for Circuit Switched Domain (CS5.0) P30309-A0002-A055-08-7618

[MSC_Sys_Arch] Functional Specification System Architecture MSC/VLR and Standalone MSC-Server CS5.0, SR13 P30309-A2433-A055-02-7618


A30862-X1001-C962-2-76-A1 7

[KPI_descr_MGW] Description of Key Performance Indicators (KPI) for Circuit Switched Domain (CS5.0) MGW-Part P30309-A0001-A055-03-7618

[PERF_DES_CS40] Performance Description CS4.0 P30309-A1171-A054-**7618 Dieter Seifert

[PERF_DES_CS50] Performance Description CS5.0 P30309-A1171-A055-03-7618 Dieter Seifert

[PERF_REQ_CS40] Performance Requirement Specification CS 4.0 P30309-A1820-A054-**-7618 Dieter Seifert

[PERF_REQ_CS50] Performance Requirement Specification CS 5.0 P30309-A1820-A055-02-7626 Dieter Seifert

[CNA_CS40] Circuit Switched Core Network Architecture (CS-CNA) CS4.0 Description P30309-A3357-A054-04-7618

Standards: [ITU E500] ITU-T Recommendation E.500, Traffic intensity measurement

principles, 11/98

[ITU E543] ITU-T Recommendation E.543, Grades of service in digital international telephone exchanges, 11/88

[3GPP_43005 ] 3GPP TS 43.005, V5.x.x, Technical performance objectives

[3GPP_23.107] 3GPP TS 23.107, Quality of Service (QoS) concept and architecture

[3GPP_29.414] 3GPP TS 29.414, Core network Nb data transport and transport signalling

[3GPP_32401] 3GPP TS 32.401, 5.x.x, Performance Management, Concept and Requirements

[3GPP_32.403 ] 3GPP TS 32.403 Performance Management, Performance measurements - UMTS and combined UMTS/GSM


8 A30862-X1001-C962-2-76-A1

1 Introduction

Currently, GSM/UMTS is deployed in many mobile operators’ networks. Since UMTS technology is totally different from existing GSM technology, equipment vendors such as SIEMENS have to face a great challenge. They have to prove that UMTS technology is able to provide at least the same network quality and performance as users have experienced from existing GSM networks.

Here are where field acceptance tests become a crucial issue, especially after committing to a supply contract. The purpose of field acceptance test is to verify that the system performance and the radio network planning is compliant with agreed objectives inside a representative area as referred to as network under test.

This document assumes that acceptance tests are usually executed as type acceptance under lab conditions. The main focus of lab tests is to verify the contract in terms of supported features, performance and interoperability on network element level. Afterwards, the network rollout is done with the tested equipment and software load as agreed at type acceptance. During the rollout phase, tests to verify the network quality under real field conditions are carried out. Depending on the individual terms of contract, Siemens may or may not be responsible to prove that offered or requested GSM/UMTS network quality can be achieved under field conditions.

This document specifies Key Performance Indicators (KPI) as the basic network quality indicator for offer process and approval of committed performance indicators but doesn’t support performance analysis, performance monitoring and network optimization.

This document is written for network planners and technical sales to support them in getting an impression which parts of the core network are more or less critical. For this reason the focus was on KPIs representing the failure ratio, because from network engineering point of view they are the most significant KPIs.

For general statements about KPI definitions, PM use cases, measurement methods, test conditions and hints concerning the negotiation phase the reader is refered to the basic document [KPI_basic]

In section 2 the evolution step to a fully 3GPP/Rel4 compliant architecture is presented. Additionally remarks concerning the impact area to KPIs are given.

In section 3 the relevant KPIs for the Offer Process are listed. For each KPI is stated:

• The definition of the KPI • The level of measurement • The System-KPI target values • The measuring method, required counters and formulas • The message flow and the trigger points

If additional KPIs are available but not relevant for the offer phase and therefore not described in detail, they are listed in separated(additional) lists.


A30862-X1001-C962-2-76-A1 9

The last section contains considerations about the delay/setup times influenced by the core network. Due to lack of ressources only some basic measurements(-> atomics) are available and for this reason an analytical approach was chosen to calculate the presented values.


10 A30862-X1001-C962-2-76-A1

2 Core Network

2.1 From CS4.0 to CS5.0

This chapter gives a short overview of the CS4.0 and CS5.0 release with respect to the network elements (NE) which are located inside the core network and are part of the circuit switched domain(CS). The following NEs are relevant: MSC/VLR, MSC-S, HLR and MGW.

All KPIs mentioned in this document are related to network elements MSC/VLR, MSC-S and MGW located in the CS domain. The most of them are basing on measurements where the corresponding trigger points are located in signalling flows. These signalling flows are assigned to special interfaces defined in the CS domain.

The CS4.0 release introduces two important features from the core network planning point of view: ATM in Core and TrFO (Transcoder Free Operation). Those features provide new steps in core network evolution by introducing ATM based interfaces and technology for core network element connections.

In CS4.0, IP transport was only possible with the IP – Trunk Gateway, an external OEM product to enable TDM over IP transport. In CS5.0 the standalone MGW is introduced which is supporting VoIP interfaces based on 3GPP R4 and 5 standards. The transport of VoIP packets (AMR or G.711 based) and of CS Data is supported based on [3GPP_29.414] for the Nb Core interface.

The highlight of CS5.0 is the introduction of so called split architecture in accordance with 3GPP Release 4 specification. This means that CS5.0 brings us a physical separation of transport and control by means of introduction a stand alone MGW and MSC-S. (Remark: in CS4.0 separation of transport and control was only a logical separation.)

In the following figure the CS5.0 step from a classic MSC to both a combined MSC with an optional MSC Server functionality and a standalone MSC Server is shown from an abstract system architecture view.


A30862-X1001-C962-2-76-A1 11

Figure 2-1: Step from CS4.0 MSC to CS5.0 MSC Server & CS 5.0 Combined MSC

For an overview of the interfaces supported by the CS4.0 MSC, see[CNA_CS40] and for the CS5.0 MSC-S, see [MSC_Sys_Arch].

A detailed description of the system-architecture of the MGW could be found in [MGW_Sys_Arch].

Late Assignment

With the introduction of CS4.0 the feature ‘Late Assignment’ is active. Due to this feature the call flow experienced changes which have also an impact on some KPI formulas.Therefore a few modifications are necessary for some Core KPI’s.

Hint:

If project specific KPI formulas are used they can also be influenced by this feature. (For more information see :Technical Sales Info No.296)

Improvements in CS5.0

With the introduction of CS5.0 HW-changes are introduced which cause an essential improvement in delay behaviour.( see : Chapter 4 ‘Core-Part of Transaction delay’)

CS5.0

Server Part

Mc

CS5.0 MSC Server

internal MGW Part

(MP,A2BS,TSC)

int. Mc

CS4.0 Server Part

(CP,LTG,MP)

CS4.0 MSC

internal MGW Part

int. Mc

CS5.0 Server

Part

CS5.0 Combined MSC

Mc CS5.0 ATCA MGW

CS5.0 ATCA MGW

CS5.0 MSC


12 A30862-X1001-C962-2-76-A1

• The introduction of the 128 kbit/s message channel together with message channel compression leads to an improved message transport.This will cause an delay reduction from ~25 % .

• The introduction of the MCP (only for R4 architecture) will cause an delay reduction from ~40 % .

The new external Mc-IF will cause additional degradation of the call setup times due to the additional necessary H.248 messages transferred over this interface. But it is expected that the new HW (MCH, MCP) will compensate this.

Moreover these HW introduction will result in better EtE-values of MOC, MTC and MMC call setup times.

2.2 Core KPI Overview

The top KPIs for CS-Core are mainly associated with the MSC-S/MGW KPIs, because the MSC-S/MGW has interfaces to the important network elements in the CS domain. Therefore the performance of the CS-Core network should be measured mainly in the MSC-S/MGW.

The available PM counters for CS4.0 are described in detail in [CNT_DESCR_CS40] , for CS5.0 they could be found in [CNT_DESCR_CS50].

An overview of the general performance measurement counter concept see [PM_CONCEPT].

In order to measure traffic in the entire MSC a lot of data concerning the traffic load, grade of service and features can be recorded by counters. This data are collected during the main tasks controlled by the MSC such as Call setup (speech,data), Handover, SMS etc. The traffic measurements inside the MSC are MP related traffic data(SSNC) or CP related traffic data. Measurements can be started via MML-command (REC MSC, REC HLR etc). The PM data are administered and collected by the Switch-Commander (SC).

2.2.1 KPI By definition, a Key Performance Indicator is any measurement counter or combination of measurement counters that serve basic (load) traffic measurements, measurements for network configuration verification, grade of service measurements, Quality of Service measurements and traffic model measurements in mobile operator networks, which is performed on a regular base.

These measurements consist of a well-defined and limited set of KPIs. In addition, Key Performance Indicators for Siemens as an equipment vendor comprise a well-defined and limited set of key parameters that are used to describe the performance of a given network element in order to develop, dimension, configure and plan this network element. These KPIs mainly represent traffic model measurements.


A30862-X1001-C962-2-76-A1 13

2.2.2 Grade of Service Measurements As most of the following KPI’s are coming from the measurement area ‘Grade of Service’ now a detailed description :

By definition, Grade of Service measurements comprise two different types of measurements: delay measurements and measurements to determine the probability of mishandling or failure of certain scenarios.

The latter is given by counting the number of malfunctions and the overall number of events. The taken ratio provides the desired measurement.

Failure ratio measurements shall be supported and provided by core network elements.

Delay measurements are difficult to achieve since it requires measuring delays between different points of the network. In addition, the calculation of the 95% quantile cannot directly be measured if the target value is obtained by adding or subtracting measures, which itself follow the 95% quantile. Usually, delay measurements are carried out with external equipment.

Therefore, the provision of delay measurement at the network elements itself are not required. That applies to delays of signalling events (e.g. call set up time) as well as delays when a data packet traverses through a network (e.g. ping delay).

So GoS related KPIs comprise all types of rates that indicate the success or failure of main procedures within the network (Success Rates, Drop Rates, Failure Rates)

2.3 Areas of Impact to KPI Target Values

This document defines a set of CS-Core KPIs that allow both SIEMENS and network operators to determine the quality within their deployed GSM/UMTS networks. Naturally the quality of the measurements with the help of KPIs is depending on a lot of factors which influence the target values of the presented KPI’s. In particular the following areas have an essential impact on the resulting KPI target values.

System / Platform

This area covers all impacts that are basic properties of the products themselves. Those properties comprise:


14 A30862-X1001-C962-2-76-A1

• System performance (behavior of unloaded and loaded network elements)

• System configuration (hardware and software configuration of network elements, basic/default parameter settings)

• Feature set

Network

This area covers all impacts that appear once the network elements are to be prepared and deployed for real network operation, and comprise

• Network design and topology

• Network configuration (DB settings for network operation and enabling of network features)

• Cluster/field conditions (in particular radio conditions due to real air interface)

• Traffic profile (actual traffic model in field) and network load (traffic under network operation)

Furthermore the resulting KPI value is influenced by the way how measurements are conducted. First issue in this context are the KPI definitions (trigger, reference points, reference message flows incl. treatment of optional network scenarios). Depending on the choosen conditions the KPIs will differ in their target values.

Additionally the target values are affected by the used Measurement methodology (e.g. stationary vs. mobile use, used equipment/methods, test conditions).


A30862-X1001-C962-2-76-A1 15

3 Definition of KPI

This section specifies in detail the scenarios, target values, conditions and measurement methods for the selected KPIs. KPIs have been selected based on the current experience from GSM/UMTS projects and from recent use cases that SIEMENS had to face. A further source for KPIs stem from concept works within the Network Engineering department of SIEMENS.

Failure ratios/success ratios of the MSC and MGW with their interfaces to the whole network are the most significant as they provide important information about the status of the network. If a failure ratio increases, the dimensioning of the network has to be checked, something is wrong with a network element or with the connection between two network elements. The availability of counters and aspects from an end-to-end point of view are further conditions for the selection of KPIs.

3.1 KPI Measurement Conditions

Performance measurements shall be conducted under defined conditions in order to obtain basic reference KPI values. System KPI values represent the values that shall be achieved under lab conditions in an unloaded system. A System KPI refers to standard scenarios related to a lab environment and in particular to Network Element specific performance. System KPI values are based on the system performance requirement specifications for the SIEMENS GERAN/UTRAN and core network product lines.

Most of the KPIs are from the measurement area Grade of Service (ITU-E493) and comprise the following measurements:

• Measure failure rates for basic signalling procedures

• Measure failure rate and malfunctions on data traffic

These measurements should be performed under the following condtions :

• No hardware saturation for TSC, A2BS, LTGs, MCH, MB, …

• CPU load on the network elements and the network element managers < 60%

• Load on signaling links < 0.2 Erlang

KPIs are highly impacted by the load within the network. Therefore, the definition of the specific load conditions for the network under test shall be part of any mutually agreed acceptance test document. The specific upper and lower thresholds for each load categorie of the relevant network elements and interfaces of each domain could be found in [KPI_basic].


16 A30862-X1001-C962-2-76-A1

Furthermore the following network parameterization is required for the tests:

• No Mobile Number Portability

• Partly separately for GSM and UMTS

• No Rerouting (Overflowtraffic)

• No optimized dynamic Routing

• No IN- features

• with ciphering

• with authentication

• with prepaid/postpaid services (which increases the load dependent on the number of prepaid/postpaid subscribers)

• without IMEI interworking

• subscriber / LUP state : attached

• with Gs interworking (network operation mode I)

• HLR extern

• No unconditional call forwarding

• No conditional call forwarding

• MOC/MTC/MMC with forward and backward bearer establishment

• Measurements done separately for voice, BS20 and BS30 service ( due to unavailability of separate counters)

• no subscriber-dependent digit processing and feature control in MSC

The relevant KPIs are extracted from the corresponding document of the MSC [KPI_descr_CS50 ] and the MGW [KPI_descr_MGW ].

The tables below show the KPIs and their target values in an overview. Each KPI is described in detail in the following chapters. Message flows and trigger points of the KPIs are presented as far as they currently are available. The tables with ‘additional’ KPIs are not so important during the offer phase so for the details of this KPIs, see [KPI_descr_CS50 ] and [KPI_descr_MGW ]. They are presented in this document only for the sake of completeness and no statement with respect to target values are given. KPIs either constructed by HLR-counters or by counters triggered from HLR could be found in an own table. All of them are relevant for the offer phase and therefore are described in the subsequent sections,

The proposed target values of the System-KPIs are estimated values which are derived from performance requirements and they have to be verified by lab measurement.


A30862-X1001-C962-2-76-A1 17

The counter values, which are described here, cumulate the events not over an endless time period, but over a time period of 15 minutes. It must be done in this way, because the significance of failure would be smaller and smaller when the time period is endless and the success counts increases much quicker in relation to the unsuccessful counts.

Note1:

Under the assumption of a well dimensioned core network which meets the before mentioned conditions only the radio part of the network causing a degradation of the KPI values in an field environment (Under lab conditions it may be possible to separate the influence of the core part with an RAN emulator).Therefore an degradation of the System-KPI values due to the CS core network is not expected

Note2:

The bold written numbers are measured values from systemtest; the other values are based on estimation.

MSC KPIs:

CS4.0KPI MSC

CS5.0System-KPI Target Value

Core-part of Network-KPI

(=> Note1)

X ≤ 0,1 % ≤ 0,1 % IMSI Attach Failure Ratio

X ≤ 0.1 % ≤ 0.1 % X ≥ 99.8 % ≥ 99.8 %

Explicit IMSI Detach Success Ratio X ≥ 99.8 % ≥ 99.8 % X ≥99.9% (99.90) ≥99.9% (99.90)

LUP Success Rate X ≥99.9% (99.76) ≥99.9% (99.76) Inter MSC Location Area Update Failure

Ratio X ≤ 0.1% ≤ 0.1% Intra MSC Periodic Location Update Failure

Ratio X ≤ 0.1% ≤ 0.1% Inter System Location Area Update Failure

Ratio (Intra MSC 3G-2G) X ≤ 0.1% ≤ 0.1% Inter System Location Area Update Failure

Ratio (Intra MSC 2G-3G) X ≤ 0.1% ≤ 0.1%

RAB Assignment Setup Failure Ratio X ≤ 0.1% ≤ 0.1% X ≤ 0.5% ≤ 0.5%

MOC Answered Calls – dropped call rate X ≤ 0.5% ≤ 0.5% X ≥ 99.8% ≥ 99.8%

Emergency call success ratio X ≥ 99.8% ≥ 99.8% X ≥99.5% (100.0) ≥99.5% (100.0) MOC Setup Ratio

(Modified formula due to ‘Late Assignment’) X ≥99.5% (100.0) ≥ 99.5% (100.0)


18 A30862-X1001-C962-2-76-A1

Mobile Originated Call Failure Ratio (All Network) X ≤ 0.1% ≤ 0.1%

X ≥99.5% (100.0) ≥99.5% (100.0) MOC Traffic Channel Allocation Ratio

X ≥99.5% (100.0) ≥99.5% (100.0) X ≥99.5% (99.99) ≥99.5% (99.99) MOC-PSTN Success Rate

X ≥99.5% (99.99) ≥99.5% (99.99) X ≥ 99.8% ≥ 99.8%

Data calls success Ratio (MOC-PSTN) X ≥ 99.8% ≥ 99.8% X ≥99.5% (99.99) ≥99.5% (99.99) MMC Success Ratio

X ≥99.5% (99.99) ≥99.5% (99.99) X ≥ 99.8% ≥ 99.8%

Data calls success Ratio (MMC) X ≥ 99.8% ≥ 99.8% X ≥ 99.5% ≥ 99.5%

MTC Traffic Channel Allocation Ratio X ≥ 99.5% ≥ 99.5% X ≥99.5% (99.81) ≥99.5% (99.81)

MTC Setup Ratio X ≥99.5% (99.81) ≥99.5% (99.81) X ≥99.5% (99.98) ≥99.5% (99.98) MTC Success Rate

X ≥99.5% (99.98) ≥99.5% (99.98) X ≤0.1% (0.04) ≤0.1% (0.04)

MTC Failure Ratio X ≤0.1% (0.02) ≤0.1% (0.02) X ≤ 2.0 % ≤ 2.0 %

Paging Procedure Failure Ratio X ≤2.0 % (0.00) ≤2.0 % (0.00) X ≥ 99.8% ≥ 99.8%

Data calls succes Ratio (MTC) X ≥ 99.8% ≥ 99.8% X ≥99.0% (99.98) ≥99.0% (99.98)

Handover Success Ratio X ≥99.0% (99.84) ≥99.0% (99.84) X ≥99.0% (99.98) ≥99.0% (99.98)

Intra-MSC-Handover Success Ratio X ≥99.0% (99.83) ≥99.0% (99.83) X ≤ 1.0 % ≤ 1.0 % Intra MSC Inter System (3G-2G) HO Failure

Ratio X ≤1.0 % (0.00) ≤1.0 % (0.00) X ≤ 1.0 % ≤ 1.0 % Inter MSC Inter System (3G-2G) HO Failure

Ratio X ≤ 1.0 % ≤ 1.0 % X ≥99.0% (100.0) ≥99.0% (100.0)

Inter-MSCA-Handover Success Ratio X ≥99.0% (99.97) ≥99.0% (99.97) X ≥99.0% (99.95) ≥99.0% (99.95)

Inter-MSCB-Handover Success Ratio X ≥99.0% (99.71) ≥99.0% (99.71) X ≤ 1.0% ≤ 1.0%

Inter MSC SRNS Relocation Failure Ratio X ≤1.0% (0.03) ≤1.0% (0.03) X ≤ 0.5% ≤ 0.5%

SMS Failure Ratio X ≤0.5% (0.02) ≤0.5% (0.02) X ≤ 0.5% ≤ 0.5%

SMS-MT Failure Ratio X ≤0.5% (0.01) ≤0.5% (0.01) X ≤ 0.5% ≤ 0.5%

SMS-MT Delivery Failed Ratio X ≤ 0.5% ≤ 0.5%

SMS-MT No Facility Ratio X ≤ 0.5% ≤ 0.5%


A30862-X1001-C962-2-76-A1 19

X ≤ 0.5% ≤ 0.5% X ≤ 0.5% ≤ 0.5%

SMS-MO Failure Ratio X ≤0.5% (0.02) ≤0.5% (0.02) X ≤ 0.5% ≤ 0.5% Mobile Originating SMS Failure Ratio (IuCS

interface) X ≤0.5% (0.00) ≤0.5% (0.00) X ≤ 0.5% ≤ 0.5%

SMS-MO Delivery failed Ratio X ≤ 0.5% ≤ 0.5% X ≤ 0.3% ≤ 0.3%

IN/CAMEL Dialog Failure Ratio X ≤0.3% (0.05) ≤0.3% (0.05) X ≤ 0.3% ≤ 0.3%

IN request Failure Ratio X ≤ 0.3% ≤ 0.3% X ≤ 0.2 % ≤ 0.2 % Supplementary Services Request Failure

Ratio X ≤ 0.2 % ≤ 0.2 %

Inter MGW HO Failure Ratio (MSC-S only) X ≤ 0.5% ≤ 0.5%

Table 3-1: MSC/MSC-S KPIs for Offer

Additional KPIs measuring time values:

KPI MSC [time] CS4.0 CS5.0

Mean Location Update Duration X X Mean Call Setup Time X Mean Holding Time (answer) X Mean Holding Time (seizure) X X Total Traffic per Customer (seizure) X X Total Speech Traffic per Customer (answer) X X Total Call Duration (seizure) X Total Call Duration (answer) X MOC-PSTN or other PLMN Average Speech Call Duration X X MMC Average Speech Call Duration X X MTC Average Speech Call Duration X X

Table 3-2: KPIs with Quantity of result Time


20 A30862-X1001-C962-2-76-A1

HLR/AC KPIs:

CS4.0 KPI HLR/AC

CS5.0 System-KPI Target Value


(=> Note1) X ≥ 99.9% ≥ 99.9% MAP Dialog – MSRN Provisioning Success

Ratio (REC HLR) X ≥99.9% (99.34) ≥99.9% (99.34) X ≤ 0.1 % ≤ 0.1 %

Cancel Location Failure Ratio (REC HLR) X ≤ 0.1 % ≤ 0.1 % X ≥ 99.9% ≥ 99.9% MAP Dialog – Interrogation Success Ratio (REC

MSC) X ≥99.9% (99.46) ≥99.9% (99.46) X ≥ 99.9% ≥ 99.9%

IMEI Check Break down (REC MSC ) X ≥ 99.9% ≥ 99.9% X ≥99.9% (100.0) ≥99.9% (100.0) Authentication Vector Request Success Ratio

(REC VLR) X ≥99.9% (100.0) ≥99.9% (100.0) Authentication Failure Ratio (Network

authenticates USIM) (REC VLR) X ≥99.9% (100.0) ≥99.9% (100.0) Authentication Failure Ratio (Network

authenticates SIM) (REC VLR) X ≥99.9% (100.0) ≥99.9% (100.0)

Table 3-3: HLR/AC related KPIs

Additional KPIs MSC:

KPI MSC CS4.0 CS5.0

VLR Utilisation (Total subscribers in VLR) X X Share of VLR Utilisation subscribers from other countries X Share of subscribers in VLR from home country but not in HPLMN X CS Network Congestion Ratio X X Busy Hour Call Attempts (BHCA) X X MOC per Subscriber for PSTN or other PLMN X X Call Forwarding Ratio X X MOC - PSTN Ratio X X MMC to other MSC per Subscriber X X MTC per Subscriber X X MTC GSM Call Forwarding Ratio X X Intra-MSC-Handover Attempt Ratio X X Inter-MSCA-Handover Attempt Ratio X X MSC Processor Load X X Control Plane ATM PVC Utilisation X X User Plane ATM PVC Utilisation X X


A30862-X1001-C962-2-76-A1 21

Signaling Interface Utilisation X X Traffic Route Utilisation (non-Iu-CS / non Nb) – Internal Routes X X Mc-If Reliability Failure Ratio X X Answer Seizure ratio X X Answer Seizure Ratio per Trunk X X External Congestion and Technical Irregularities Release Ratio X MOC-PSTN B-Busy Ratio X X MMC B-Busy Ratio X X MTC B-Busy Ratio X X Inter-MSCB-Handover Attempt Ratio X X SMS-MT Absent MS Ratio X X SMS-MT MS Memory Full Ratio X X MGW availability X

Table 3-4: ‘Additional’ MSC/MSC-S KPIs

MGW-KPIs :

CS4.0

KPI MGW CS5.0

System-KPI Target Value


(=> Note1) Transcoding Failure Ratio

X ≤ 0.1% ≤ 0.1% Data Call Failure Ratio X ≤ 0.2% ≤ 0.2% Data Call Failure Ratio (per call type) X ≤ 0.2% ≤ 0.2% Inserted Announcement Failure Ratio X ≤ 0.2% ≤ 0.2% Inserted Tone Failure Ratio X ≤ 0.1% ≤ 0.1%

X ≤ 0.2% ≤ 0.2% Conference Call Establishment Failure Ratio X ≤ 0.2% ≤ 0.2% Receiving IP Bearer Negotiation Failure Ratio X ≤ 0.1% ≤ 0.1% Initiating IP Bearer Negotiation Failure Ratio X ≤ 0.1% ≤ 0.1%

Table 3-5: MGW-KPIs


22 A30862-X1001-C962-2-76-A1

Additional MGW-KPIs :

KPI MGW CS4.0 CS5.0

ATM Level Volume (per MGW / per VC) X X PVC Utilisation X X IP Level Volume X AMR Usage X X PDU Volume X X MGW Processor Usage X MGW Memory Usage X Call Transcoding Ratio X AAL2 Level Error Ratio (per error type) X X Receiving IP Bearer Negotiation Failure Ratio per error type X Initiating IP Bearer Negotiation Failure Ratio per error type X IP Bearer Negotiation Encoding/Decoding Failure Ratio X

Table 3-6: ‘Additional’ MGW-KPIs

3.2 KPIs for MSC

3.2.1 Mobility and Security

3.2.1.1 IMSI Attach Failure Ratio

Description:

This KPI indicates the failure ratio for IMSI attach procedure.

The indicator is expressed as the one’s complement of the number of successfully completed IMSI attach procedures divided by the total number of IMSI attach requests.

Level of measurement:

3G MSC/MSC-S (UCR5.0/SR13.0) and for the MSC (UCR3.0/SR11.0) by patch

2G+3G MSC/MSC-S

System-KPI target value:

Equal to or less than 0.1%

KPI-formula:

2G+3G:


A30862-X1001-C962-2-76-A1 23

%100ATT_IMSI_WITH_LOCUPD_REQUESTS

ATTACH_IMSI_WITH_LOCUPD_SUCC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

3G:

%100ATT_IMSI_WITH_LOCUPD_REQUESTS_U

ATT_IMSI_WITH_LOCUPD_SUCC_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

Message Flows/Triggerpoints :

3.2.1.2 Explicit IMSI Detach Success Ratio

Description:

This KPI reveals the success of the explicit IMSI detach procedure. Level of measurement:

Per MSC / MSC-S


24 A30862-X1001-C962-2-76-A1


Equal to or greater than 99.8% KPI-formula: 2G+3G:

%100

_TMSIETACH_WITHRECEIVED_D_IMSIETACH_WITHRECEIVED_D

MSI_DETACHEXPLICIT_IKPI ×

⎟⎟⎠

⎞⎜⎜⎝

⎛+

+=

Message Flows/Triggerpoints:

MS/UE

CR(IMSI_DETACH_INDICATION)

MSC/VLR

if IMSI within detach : + RECEIVED_DETACH_WITH_IMSIif TMSI within detach : + RECEIVED_DETACH_WITH_TMSI

If successful detached : + EXPLICIT_IMSI_DETACH

IMSI_DETACH

CREF()

BSC/RNC

3.2.1.3 LUP Success Ratio Description:

The number of successful Location Update Procedures in relation to the total number of attempted Location Update Procedures.


A30862-X1001-C962-2-76-A1 25


Per MSC System-KPI target value:

Equal to or greater than 99.9% KPI-formula: 2G+3G:

%100Q_COM_LUPSERVICE_RE_

STS_LOCUPDSUCC_REQUE×

+=

LOCUPDREQUESTSKPI


3.2.1.4 Inter MSC Location Area Update Failure Ratio Description:

This KPI indicates the failure ratio of Location Area Update procedures when two GMSCs are involved. The indicator is expressed as the one’s complement of the


26 A30862-X1001-C962-2-76-A1

number of successful Inter MSC Location Updates divided by the number of Inter MSC Location Update attempts.


Per MSC/MSC-S System-KPI target value:

≤ 0.1%

KPI-formula: 2G+3G:

%100

CB_MSC_HO_MSSUBSEQ_MSCATTEMPTSSC_MSC_OG_HANDOVER_M

NOWNS_PVLR_UNKVLR_CHANGE– WNS_PVLR_KNOVLR_CHANGE–

_NULLLOCUPD_LAI– STS_LOCUPDSUCC_REQUE

1 ×

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛+

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

−=KPI

3G:

%100LOCUPD_MSC_INTER_REQUESTS_U

LOCUPD_MSC_INTER_SUCC_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


SUCC_REQUESTS_LOCUPD Trigger: each time LOCATION UPDATE ACCEPT is received.

LOCUPD_LAI_NULL Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS/RNC.

VLR_CHANGES_PVLR_KNOWN Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS and the PVLR is known from the LAC.

VLR_CHANGES_PVLR_UNKNOWN Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS and the PVLR is unknown

REQUESTS_LOCUPD_INTRA_VLR Trigger: each time LOCATION UPDATE REQUEST for an intra VLR location is received

U_SUCC_INTER_MSC_LOCUPD Transmission of Update Location Accepted message from RNC

U_REQUESTS_INTER_MSC_LOCUPD Reception of a Location Update Request message from RNC


A30862-X1001-C962-2-76-A1 27

3.2.1.5 Intra MSC Periodic Location Update Failure Ratio

Description:

This KPI indicates the failure ratio of Periodic Location Area Update procedures.

The indicator is expressed as the one’s complement of the number of successful Periodic MSC Location Updates divided by the number of Periodic MSC Location Update attempts. Level of measurement:

Per 3G MSC/MSC-S


≤ 0.1% KPI-formula: 2G+3G:

%100A_VLROCUPD_INTRREQUESTS_L

NOWNS_PVLR_UNKVLR_CHANGE - WNS_PVLR_KNOVLR_CHANGE -

_NULLLOCUPD_LAI -STS_LOCUPDSUCC_REQUE

×⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

=KPI

3G:

%100LOCUPD_PER_MSC_INTRA_REQUESTS_U

LOCUPD_PER_MSC_INTRA_SUCC_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


U_SUCC_INTRA_MSC_PER_LOCUPD Transmission of periodic Update Location Accepted message from RNC SUCC_REQUESTS_LOCUPD: Number of successfully handled requests for location updating (normal, periodic). Trigger: each time LOCATION UPDATE ACCEPT is received. Message flow: see also chapter “LUP success rate”.


28 A30862-X1001-C962-2-76-A1

3.2.1.6 Inter System Location Area Update Failure Ratio (Intra MSC 3G-2G) Description:

This KPI indicates the failure ratio of Intersystem (3G 2G) Location Area Updates when one 3GMSC is involved.

The indicator is expressed as the one’s complement of the number of successful Intersystem (3G 2G) Location Area Updates divided by the number of Intersystem (3G 2G) Location Area Updates attempts.


3G MSC/MSC-S


≤ 0.1% KPI-formula:

2G:

%100LOCUPD_G2G3_MSC_INTRA_REQUESTS

LOCUPD_G2G3_MSC_INTRA_SUCC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


SUCC_INTRA_MSC_3G2G_LOCUPD Transmission of Update Location Accepted message from BSC REQUESTS_INTRA_MSC_3G2G_LOCUPD Reception of a Location Update Request message from BSC

BSC/RNC MSC

REQUESTS_INTRA_MSC_3G2G_LOCUPD /REQUESTS_INTRA_MSC_2G3G_LOCUPD

Location Update Request

Update Location Accepted

SUCC_INTRA_MSC_3G2G_LOCUPD /SUCC_INTRA_MSC_2G3G_LOCUPD


A30862-X1001-C962-2-76-A1 29

3.2.1.7 Inter System Location Area Update Failure Ratio (Intra MSC 2G-3G)

Description:

This KPI indicates the failure ratio of Intersystem (2G 3G) Location Area Updates when one 3G MSC is involved. The indicator is expressed as the one’s complement of the number of successful Intersystem (2G 3G) Location Area Updates divided by the number of Intersystem (2G 3G) Location Area Updates attempts. Level of measurement:

3G MSC/MSC-S System-KPI target value:

≤ 0.1% KPI-formula:

%100LOCUPD_G3G2_MSC_INTRA_REQUESTS

LOCUPD_G3G2_MSC_INTRA_SUCC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


SUCC_INTRA_MSC_2G3G_LOCUPD Transmission of Update Location Accepted message from RNC REQUESTS_INTRA_MSC_2G3G_LOCUPD Reception of a Location Update Request message from RNC

Messsage flow: see chapter before

3.2.2 General Call Analysis

3.2.2.1 RAB Assignment Setup Failure Ratio

Description:

This KPI indicates the failure ratio of RAB assignment setup.

The indicator is expressed as the one’s complement of the number of successfully completed RAB Assignment setups divided by the total number of RAB assignment setup attempts.


Per MSC/MSC-S


30 A30862-X1001-C962-2-76-A1



KPI-formula:

2G+3G: per MSC:

MTER:

%100)(___

)(__1 ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

MTERREQCHANTRAFFICGENMTERALLOCATIONTCHCALLKPI

MOC:

%100)(___

)(__1 ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

MORTRREQCHANTRAFFICGENMORTRALLOCATIONTCHCALLKPI

Removing RNC causes:

MTER:

%100

SON(MTER)UNS_BS_REA)(___

)(__1 ×

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛+

−=MTERREQCHANTRAFFICGEN

MTERALLOCATIONTCHCALLKPI

MOC:

%100

)SON(UNS_BS_REA)(___

)(__1 ×

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛+

−=

MORTRMORTRREQCHANTRAFFICGEN

MORTRALLOCATIONTCHCALLKPI

3G: per MSC:

MTER:

%100)(____

)(___1 ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

MTERREQCHANTRAFFICGENUMTERALLOCATIONTCHCALLUKPI

MOC:

%100)(____

)(___1 ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

MORTRREQCHANTRAFFICGENUMORTRALLOCATIONTCHCALLUKPI

Removing RNC causes:

MTER:


A30862-X1001-C962-2-76-A1 31

%100

R)REASON(MTEU_UNS_RNC_)(____

)(___1 ×

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛+

−=MTERREQCHANTRAFFICGENU

MTERALLOCATIONTCHCALLUKPI

MOC:

%100

)REASON(U_UNS_RNC_)(____

)(___1 ×

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

⎟⎟⎠

⎞⎜⎜⎝

⎛+

−=

MORTRMORTRREQCHANTRAFFICGENU

MORTRALLOCATIONTCHCALLUKPI


U_CALL_TCH_ALLOCATION Trigger: Each time ASSIGNMENT COMPLETE is received.

U_GEN_TRAFF_CHAN_REQ Trigger: Each time ASSIGNMENT REQUEST is sent to the RNC for: • MTER: after previous paging.

• MORTR: after the previous receipt of CM SERVICE REQUEST

U_UNS_RNC_REASON Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received for UMTS call before digit analysis is performed.

U_UNS_BS_REASON

Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received for call before digit analysis is performed.


32 A30862-X1001-C962-2-76-A1

3.2.2.2 MOC Answered Calls – dropped call rate

Description:

This KPI reveals the ratio of dropped calls after answered.


Per cell


A30862-X1001-C962-2-76-A1 33



KPI-formula:

%100I

SONALL_BS_REAREL_ANSW_C_CALLANSW_INCOMCALLANSW_ORIG_

SONALL_BS_REAREL_ANSW_CKPI ×

⎟⎟⎠

⎞⎜⎜⎝

⎛+

+=


REL_ANSW_CALL_BS_REASON Trigger: after CONNECT ACK, each time SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMMAND/CLEAR REQUEST are received. ANSW_ORIG_CALL Trigger: release of call when previous CONNECT ACK is received. ANSW_INCOM_CALLS:~ Trigger: release of call when previous CONNECT ACK is received.

3.2.3 Mobile Originated Traffic Analysis

3.2.3.1 Emergency call success ratio Description:

This KPI reveals the ratio of dropped calls after answered. Level of measurement:

Per MSC / MSC-S System-KPI target value:

Equal to or greater than 99.8% KPI-formula:

( )( ) %100MORTRPTSTS12_ATTEMEMERGENCY_MORTR ALL_CALL_TCH_TS12_EMERGKPI ×=


TS12_EMERG_CALL_TCH_ALL(MORTR)


34 A30862-X1001-C962-2-76-A1

Trigger: each time ASSIGNMENT COMPLETE is received for TS12 calls.

EMERGENCY_TS12_ATTEMPTS(MORTR) Trigger: each time CM SERVICE REQUEST indicating an emergency call is received.

3.2.3.2 MOC Setup Ratio Description:

This KPI indicates the Setup success ratio of mobile originated calls. Level of measurement:



2G+3G: Until SR11.0, UR3.0:

%100)(___

)(__)(___

)(___)(_

×=

−−

−=

SumMORTRREQCHANTRAFFGENKPI

MORTRBLOCKEDMSUNSMORTRERRDESTREQUNS

MORTRFORWCALLENDCALLMORTRATTEMPTSCALL

Sum

For SR12.0, UR4.0 or after:

( )

%100)(__

MORTREF_ALERTCALL_REL_B)(__

)(___)(___

)(_

×=

−−

−−

=

SumMORTRSEIZUREBSSAPINTERNALKPI

MORTRBLOCKEDMSUNSMORTRERRDESTREQUNS

MORTRFORWCALLENDCALLMORTRATTEMPTSCALL

Sum


GEN_TRAFF_CHAN_REQ (MORTR)


A30862-X1001-C962-2-76-A1 35

Trigger: each time ASSIGNMENT REQUEST is sent to the BSC after the previous receipt of CM SERVICE REQUEST.

CALL_ATTEMPTS (MORTR) Indicates how many call attempts have taken place, independently of the received BS or TS. CALL_END_CALL_FORW(MORTR) Trigger: each time call forwarding treatment (e.g., busy, unconditional no paging response) is invoked and the previous call setup is ended UNS_REQ_DEST_ERR (MORTR): Trigger: on receipt of internal release (CP) after digit analysis failed. UNS_MS_BLOCKED (MORTR): Trigger: each time a call is released due to barring of outgoing calls (calling subscriber) or of incoming calls (called subscriber).

CALL_REL_BEF_ALERT(MORTR) Trigger: Trigger: each time RELEASE COMPLETE is received for a call before the alerting signal is received. INTERNAL_BSSAP_SEIZURE (MORTR) Trigger: After evaluation of DT1(SETUP), after the CP internally selected a BSSAP trunk.

3.2.3.3 Mobile Originated Call Failure Ratio (All Network) Description:

This KPI indicates the failure ratio of mobile originated calls.

The indicator is expressed as the one’s complement of the number of successfully established calls divided by the total number of mobile originated call attempts. Level of measurement: Per MSC/MSC-S

System-KPI target value: ≤ 0.1%

KPI-formula:


36 A30862-X1001-C962-2-76-A1

Per 3G MSC:

%100)MORTR(ATTEMPTS_CALL_U

)PLMN_NOT_MOUT(_CALL_FORWU_CALL_END)PLMN_MOUT(_CALL_FORWU_CALL_END

MSC_SAME_SCONNECTION_THROUGH_SN_U)PLMN_NOT_MOUT(SCONNECTION_THROUGH_SN_U

)PLMN_MOUT(SCONNECTION_THROUGH_SN_U

1

KPI

×

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+++

+

−

=


U_CALL_ATTEMPTS(MORTR) Upon receipt of each CM SERVICE REQUEST with SERVICE TYPE = mobile originating call or establishment of all emergency call attempts. Short message service and SS activation are not included.

U_SN_THROUGH_CONNECTIONS Transmission of IAM towards Network

U_SN_THROUGH_CONNECTIONS_SAME_MSC Receive of CALL CONFIRMED and MOC+MTC in the same MSC

U_CALL_END_CALL_FORW: Trigger: each time call forwarding treatment (e.g., busy, unconditional no paging response) is invoked and old UMTS call setup is thereby ended.


A30862-X1001-C962-2-76-A1 37

3.2.3.4 MOC Traffic Channel Allocation Ratio Description:

Provides the success ratio of the channel allocation Level of measurement:


Equal to or greater than 99.5%


38 A30862-X1001-C962-2-76-A1

KPI-formula:

2G+3G:

%100)(___

)(____12)(____11

)(__

×⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+

+

=MORTRREQCHANTRAFFGEN

MORTRALLTCHCALLEMERGTSMORTRALLTCHCALLEMERGTS

MORTRALLOCATIONTCHCALL

KPI

3G:

%100)(____

)(____12_)(____11_

)(___

×⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛+

+

=MORTRREQCHANTRAFFGENU

MORTRALLTCHCALLEMERGTSUMORTRALLTCHCALLEMERGTSU

MORTRALLOCATIONTCHCALLU

KPI


CALL_TCH_ALLOCATION Trigger: each time ASSIGNMENT COMPLETE is received.

U_GEN_TRAFF_CHAN_REQ (MORTR) Trigger: each time ASSIGNMENT REQUEST is sent to the RNC after the previous receipt of CM SERVICE REQUEST.

TS11_EMERG_CALL_TCH_ALL Trigger: each time ASSIGNMENT COMPLETE is received for TS11 calls.

TS12_EMERG_CALL_TCH_ALL Trigger: each time ASSIGNMENT COMPLETE is received for TS12 calls.

GEN_TRAFF_CHAN_REQ (MORTR) Trigger: each time ASSIGNMENT REQUEST is sent to the BSC after the previous receipt of CM SERVICE REQUEST.

U_CALL_TCH_ALLOCATION (MORTR) Trigger: each time ASSIGNMENT COMPLETE is received.

U_TS12_EMERG_CALL_TCH_ALL Trigger: each time ASSIGNMENT COMPLETE is received for TS12 UMTS calls.

U_TS11_EMERG_CALL_TCH_ALL Trigger: each time ASSIGNMENT COMPLETE is received for TS11 UMTS calls.

3.2.3.5 MOC-PSTN Success Rate

Description:

The number of successful MOC-PSTN or other PLMN speech calls ratio. Level of measurement:

Per MSC/ MSC-S


A30862-X1001-C962-2-76-A1 39



2G+3G: 2G3GCallAttempts = CALL_ATTEMPTS(MOUT_NOT_PLMN) + DATACDA_ANA_ATTEMPTS (MOUT_NOT_PLMN) + DATACDA_DIG_ATTEMPTS (MOUT_NOT_PLMN) + ALTFAXSP_CALL_ATTEMPTS (MOUT_NOT_PLMN) + FAX3_CALL_ATTEMPTS (MOUT_NOT_PLMN) + DED_PAD_ATTEMPTS (MOUT_NOT_PLMN) + DATACDS_ANA_ATTEMPTS (MOUT_NOT_PLMN) + DATACDS_DIG_ATTEMPTS (MOUT_NOT_PLMN) + ALT_SPEECH_DATA_ATTEMPTS (MOUT_NOT_PLMN)

MOC-PSTN Answer Ratio:

%10032

_01_

T_PLMN)ER(MOUT_NO_DATA_ANSWALT_SPEECHOT_PLMN)WER(MOUT_NG_WITH_ANSDATACDS_DIOT_PLMN)WER(MOUT_NA_WITH_ANSDATACDS_AN

LMN)MOUT_NOT_PTH_ANSWER(DED_PAD_WI)T_NOT_PLMNANSWER(MOUFAX3_WITH_PLMN)(MOUT_NOT_ITH_ANSWERALTFAXSP_WOT_PLMN)WER(MOUT_NG_WITH_ANSDATACDA_DIOT_PLMN)WER(MOUT_NA_WITH_ANSDATACDA_AN

)__(___12)__(___11

)__(___)__(___

_

×=

+++++++++++

=

ptsGCallAttemGAnswersCallKPI

PLMNNOTMOUTANSWERWITHEMERGTSPLMNNOTMOUTANSWERWITHEMERGTS

PLMNNOTMOUTANSWERWITHRELBSPLMNNOTMOUTANSWERWITHCALLSSPEECH

AnswersCall

MOC-PSTN B-Busy Ratio:

%10032

)__(__02_ ×=ptsGCallAttemG

PLMNNOTMOUTBUSYMSUNSKPI

MOC-PSTN A-Release Ratio:


40 A30862-X1001-C962-2-76-A1

%10032

)__(___03_ ×=ptsGCallAttemG

PLMNNOTMOUTALERTBEFRELCALLKPI

MOC-PSTN No-Answer Ratio:

%10032

_04_

)__(__)__(__

_

×=

+=

ptsGCallAttemGAnswersNoKPI

PLMNNOTMOUTALERTTIOUTCALLPLMNNOTMOUTALERTRELCALL

AnswersNo

MMC UNS RAN Ratio:

%10032

)__(SONUNS_BS_REA05_ ×=ptsGCallAttemG

PLMNNOTMOUTKPI

MMC REL EXCHANGE Ratio:

%10032

)__(XCHANGECALL_REL_E06_ ×=ptsGCallAttemG

PLMNNOTMOUTKPI

MOC-PSTN Success Rate:

06_05_04_03_02_01_ KPIKPIKPIKPIKPIKPIKPI +++++=

3G: MOC-PSTN Answer Ratio:

%100

LMN)MOUT_NOT_PU_CA_DATA()__(__

_01_

)__(___12_)__(___11_

)__(____)__(____

_

×

⎭⎬⎫

⎩⎨⎧ +

=

++

+=

PLMNNOTMOUTATTEMPTSCALLUAnswersCallKPI

PLMNNOTMOUTANSWERWITHEMERGTSUPLMNNOTMOUTANSWERWITHEMERGTSU

PLMNNOTMOUTANSWERWITHRELRNCUPLMNNOTMOUTANSWERWITHCALLSSPEECHU

AnswersCall

UMTS-MOC-PSTN B-Busy Ratio:


A30862-X1001-C962-2-76-A1 41

%100

LMN)MOUT_NOT_PU_CA_DATA()__(__)__(___02_ ×

⎭⎬⎫

⎩⎨⎧ +

=PLMNNOTMOUTATTEMPTSCALLUPLMNNOTMOUTBUSYMSUNSUKPI

UMTS-MOC-PSTN A-Release Ratio:

%100


)__(____03_ ×

⎭⎬⎫

⎩⎨⎧ +

=PLMNNOTMOUTATTEMPTSCALLU

PLMNNOTMOUTALERTBEFRELCALLUKPI

UMTS-MOC-PSTN No-Answer Ratio:

%100


_04_

)__(____)__(___

_

×

⎭⎬⎫

⎩⎨⎧ +

=

+=

PLMNNOTMOUTATTEMPTSCALLUAnswersNoKPI

PLMNNOTMOUTALERTOUTTICALLUPLMNNOTMOUTALERTRELCALLU

AnswersNo

MMC UNS RAN Ratio:

%100

LMN)MOUT_NOT_PU_CA_DATA()__(__)__(ASONUNS_RNC_RE05_ ×

⎭⎬⎫

⎩⎨⎧ +

=PLMNNOTMOUTATTEMPTSCALLUPLMNNOTMOUTKPI

UMTS-MOC-PSTN Success Rate:

05_04_03_02_01_ KPIKPIKPIKPIKPIKPI ++++=


SPEECH_CALLS_WITH_ANSWER (MOUT_NOT_PLMN) Trigger: each time the connection is released in response to the receipt of the respective Message ANM.

TS11_EMERG_WITH_ANSWER (MOUT_NOT_PLMN) TS12_EMERG_WITH_ANSWER (MOUT_NOT_PLMN) Trigger: each time the connection has actually been released in response to the receipt of ANM.

UNS_MS_BUSY (MOUT_NOT_PLMN) each time the RELEASE UBM is received from the following exchange, with reason “subscriber busy”.


42 A30862-X1001-C962-2-76-A1

CALL_REL_ALERT (MOUT_NOT_PLMN) Trigger: each time, on receipt of RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM. Note: Counts also direct calls to announcement with is no charge.

UNS_BS_REASON (MOUT_NOT_PLMN): Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received after digit analysis has been performed.

U_SPEECH_CALLS_WITH_ANSWER (MOUT_NOT_PLMN) Trigger: each time the connection is released in response to the receipt of the respective Message ANM

U_TS11_EMERG_WITH_ANSWER (MOUT_NOT_PLMN) U_TS12_EMERG_WITH_ANSWER (MOUT_NOT_PLMN) Trigger: each time the connection has actually been released in response to the receipt of ANM for UMTS call.

U_UNS_MS_BUSY (MOUT_NOT_PLMN) each time the RELEASE UBM is received from the following exchange, with reason “subscriber busy”, for UMTS calls.

U_CALL_REL_ALERT (MOUT_NOT_PLMN) Trigger: each time RELEASE COMPLETE is received after the alert signal is sent and before CONNECT is received, for a UMTS call. Note: Counts also direct calls to announcement with is no charge.

U_CALL_TI_OUT_ALERT (MOUT_NOT_PLMN) Trigger: each time RELEASE COMPLETE is received due to alert supervision timeout (internal event in MSC).

U_CALL_ATTEMPTS (MOUT_NOT_PLMN) Trigger: each time SET UP is received and digit analysis results in this traffic type (speech call attempts only), UMTS.

BS_REL_WITH_ANSWER (MOUT_NOT_PLMN) Trigger: on each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ are received for a particular reason.

CALL_ATTEMPTS (MOUT_NOT_PLMN):

Trigger: each time the SET UP is received and digit analysis results in this traffic type (speech call attempts only).

CALL_REL_BEF_ALERT (MOUT_NOT_PLMN)

Trigger: RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM.

CALL_TI_OUT_ALERT (MOUT_NOT_PLMN)

Trigger: each time RELEASE COMPLETE is received due to alert supervision timeout (internal event in MSC).

CALL_REL_EXCHANGE (MOUT_NOT_PLMN): Trigger: each time RELEASE is received indicating clear backward or UBM with causes different from busy, CUG reject, destination error.


A30862-X1001-C962-2-76-A1 43

U_RNC_REL_WITH_ANSWER (MOUT_NOT_PLMN)

Trigger: on each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ are received for a particular reason.

U_UNS_MS_BUSY(MOUT_NOT_PLMN)

each time the RELEASE UBM is received from the following exchange, with reason “subscriber busy”, for UMTS calls.

U_CALL_ATTEMPTS (MOUT_NOT_PLMN)

Trigger: each time the SET UP is received and digit analysis results in this traffic type (speech call attempts only), for UMTS call.

U_CALL_REL_BEF_ALERT (MOUT_NOT_PLMN)

Trigger: RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM.

U_UNS_RNC_REASON (MOUT_PLMN) Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received for UMTS call after digit analysis has been performed.

DATACDA_ANA_ATTEMPTS(MOUT_NOT_PLMN), DATACDA_DIG_ATTEMPTS(MOUT_NOT_PLMN), ALTFAXSP_CALL_ATTEMPTS(MOUT_NOT_PLMN), FAX3_CALL_ATTEMPTS(MOUT_NOT_PLMN), DED_PAD_ATTEMPTS(MOUT_NOT_PLMN), DATACDS_ANA_ATTEMPTS(MOUT_NOT_PLMN), DATACDS_DIG_ATTEMPTS(MOUT_NOT_PLMN), ALT_SPEECH_DATA_ATTEMPTS(MOUT_NOT_PLMN): Trigger: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

U_CA_DATA (MOUT_NOT_PLMN): Trigger: each time SET UP is received and digit analysis results in this traffic type (data call attempts only). DATACDA_ANA_WITH_ANSWER(MOUT_NOT_PLMN) DATACDA_DIG_WITH_ANSWER(MOUT_NOT_PLMN), ALTFAXSP_WITH_ANSWER(MOUT_NOT_PLMN), FAX3_WITH_ANSWER(MOUT_NOT_PLMN), DED_PAD_WITH_ANSWER(MOUT_NOT_PLMN), DATACDS_ANA_WITH_ANSWER(MOUT_NOT_PLMN), DATACDS_DIG_WITH_ANSWER(MOUT_NOT_PLMN), ALT_SPEECH_DATA_ANSWER(MOUT_NOT_PLMN): Trigger: Each time the connection is released in response to the receipt of the respective message ANM.

U_CC_ANSW_DATA (MOUT_NOT_PLMN) Trigger: each time the connection is released in response to the receipt of the respective Message ANM


44 A30862-X1001-C962-2-76-A1

3.2.3.6 Data calls success Ratio (MOC-PSTN) Description:

This KPI gives a ratio of the number of answered calls in relation to the number of attempts, for several Data services, broken down by service type. Level of measurement:

Per MSC/ MSC-S System-KPI target value:


CDA analog service

%100PLMN)(MOUT_NOT_A_ATTEMPTSDATACDA_AN

OT_PLMN)WER(MOUT_NA_WITH_ANSDATACDA_ANKPI ×=

CDA digital services:

%100PLMN)(MOUT_NOT_G_ATTEMPTSDATACDA_DI

OT_PLMN)WER(MOUT_NG_WITH_ANSDATACDA_DIKPI ×=

CDS analog services:

%100PLMN)(MOUT_NOT_A_ATTEMPTSDATACDS_AN

OT_PLMN)WER(MOUT_NA_WITH_ANSDATACDS_ANKPI ×=

CDS digital services:

%100PLMN)(MOUT_NOT_G_ATTEMPTSDATACDS_DI

NOT_PLMN)SWER(MOUT_IG_WITH_ANDATACDAS_DKPI ×=

2G only(services not supported by the external MGW):

Alternate speech/facsimile services:

%100T_PLMN)TS(MOUT_NOALL_ATTEMPALTFAXSP_C

PLMN)(MOUT_NOT_ITH_ANSWERALTFAXSP_WKPI ×=

Data calls for automatic facsimile group 3:

%100MN)OUT_NOT_PLATTEMPTS(MFAX3_CALL_

)T_NOT_PLMNANSWER(MOUFAX3_WITH_KPI ×=

Alternate speech/data or speech followed by data services:

%100NOT_PLMN)MPTS(MOUT__DATA_ATTEALT_SPEECH

PLMN)(MOUT_NOT_ WER_DATA_ ANSALT_SPEECHKPI ×=


A30862-X1001-C962-2-76-A1 45


DATACDA_ANA_WITH_ANSWER (MOUT_ NOT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDA_ANA_ATTEMPTS(MOUT_ NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

DATACDA_DIG_WITH_ANSWER (MOUT_ NOT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDA_DIG_ATTEMPTS(MOUT_ NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

DATACDS_DIG_WITH_ANSWER (MOUT_NOT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDS_DIG_ATTEMPTS(MOUT_NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

ALTFAXSP_WITH_ANSWER(MOUT_ NOT_PLMN); Trigger: each time the connection has actually been released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

ALTFAXSP_CALL_ATTEMPTS(MOUT_ NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

FAX3_WITH_ANSWER(MOUT_NOT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

FAX3_CALL_ATTEMPTS(MOUT_NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type and SET UP is sent.


46 A30862-X1001-C962-2-76-A1

DATACDS_ANA_WITH_ANSWER (MOUT_NOT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDS_ANA_ATTEMPTS(MOUT_NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

ALT_SPEECH_DATA_ ANSWER (MOUT_NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

ALT_SPEECH_DATA_ATTEMPTS(MOUT_NOT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

3.2.4 MMC KPIs

3.2.4.1 MMC Success Ratio Description:

The number of successful MMC calls.




KPI-formula:

2G+3G:

2G3GCallAttempts = CALL_ATTEMPTS(MOUT_PLMN) + DATACDA_ANA_ATTEMPTS (MOUT_PLMN) + DATACDA_DIG_ATTEMPTS (MOUT_PLMN) + ALTFAXSP_CALL_ATTEMPTS (MOUT_PLMN) + FAX3_CALL_ATTEMPTS (MOUT_PLMN)


A30862-X1001-C962-2-76-A1 47

+ DED_PAD_ATTEMPTS (MOUT_PLMN) + DATACDS_ANA_ATTEMPTS (MOUT_PLMN) + DATACDS_DIG_ATTEMPTS (MOUT_PLMN) + ALT_SPEECH_DATA_ATTEMPTS (MOUT_PLMN)

MMC Answer Ratio:

%10032

_01_

MN)ER(MOUT_PL_DATA_ANSWALT_SPEECHLMN)WER(MOUT_PG_WITH_ANSDATACDS_DILMN)WER(MOUT_PA_WITH_ANSDATACDS_AN

MOUT_PLMN)TH_ANSWER(DED_PAD_WIT_PLMN)ANSWER(MOUFAX3_WITH_

)(MOUT_PLMNITH_ANSWERALTFAXSP_WLMN)WER(MOUT_PG_WITH_ANSDATACDA_DILMN)WER(MOUT_PA_WITH_ANSDATACDA_AN

)_(___)_(___

_

×=

+++++++++

=

ptsGCallAttemGAnswersCallKPI

PLMNMOUTANSWERWITHRELBSPLMNMOUTANSWERWITHCALLSSPEECH

AnswersCall

MMC B-Busy Ratio:

%10032

)_(__02_ ×=ptsGCallAttemG

PLMNMOUTBUSYMSUNSKPI

MMC A-Release Ratio:

%10032

)_(___03_ ×=ptsGCallAttemG

PLMNMOUTALERTBEFRELCALLKPI

MMC No-Answer Ratio:

%10032

_04_

)_(__)_(__

_

×=

+=

ptsGCallAttemGAnswersNoKPI

PLMNMOUTALERTTIOUTCALLPLMNMOUTALERTRELCALL

AnswersNo

MMC UNS RAN Ratio:


48 A30862-X1001-C962-2-76-A1

%10032

)_(SONUNS_BS_REA05_ ×=ptsGCallAttemG

PLMNMOUTKPI


%10032

)_(XCHANGECALL_REL_E06_ ×=ptsGCallAttemG

PLMNMOUTKPI

MMC Success Rate:

06_05_04_03_02_01_ KPIKPIKPIKPIKPIKPIKPI +++++= 3G:

UMTS-MMC Answer Ratio:

%100

)(MOUT_PLMNU_CA_DATA )_(__

_01_

)_(____)(MOUT_PLMNDATA U_CC_ANSW_

)_(_____

×

⎭⎬⎫

⎩⎨⎧ +

=

++

=

PLMNMOUTATTEMPTSCALLUAnswersCallKPI

PLMNMOUTANSWERWITHRELRNCU

PLMNMOUTANSWERWITHCALLSSPEECHUAnswersCall

UMTS-MMC B-Busy Ratio:

%100

)(MOUT_PLMNU_CA_DATA )_(__)_(___02_ ×

⎭⎬⎫

⎩⎨⎧ +

=PLMNMOUTATTEMPTSCALLUPLMNMOUTBUSYMSUNSUKPI

UMTS-MMC A-Release Ratio:

%100


)_(_____03_ ×

⎭⎬⎫

⎩⎨⎧ +

=PLMNMOUTATTEMPTSCALLU

PLMNMOUTALERTABEFRELCALLUKPI

UMTS-MMC No-Answer Ratio:


A30862-X1001-C962-2-76-A1 49

%100


_04_

)_(____)_(____

_

×

⎭⎬⎫

⎩⎨⎧ +

=

+=

PLMNMOUTATTEMPTSCALLUAnswersNoKPI

PLMNMOUTALERTOUTTICALLUPLMNMOUTALERTARELCALLU

AnswersNo

MMC UNS RAN Reasons:

%100

)(MOUT_PLMNU_CA_DATA )_(__)_(ASONUNS_RNC_RE05_ ×

⎭⎬⎫

⎩⎨⎧ +

=PLMNMOUTATTEMPTSCALLUPLMNMOUTKPI

UMTS-MMC Success Rate:

05_04_03_02_01_ KPIKPIKPIKPIKPIKPI ++++=


SPEECH_CALLS_WITH_ANSWER(MOUT_PLMN) Trigger: each time the connection is released in response to the receipt of the respective Message ANM

BS_REL_WITH_ANSWER (MOUT_PLMN) Trigger: on each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ are received for a particular reason.

UNS_MS_BUSY (MOUT_PLMN) Trigger: each time the RELEASE UBM is received from the following exchange, with reason “subscriber busy”.

CALL_REL_BEF_ALERT (MOUT_PLMN) Trigger: RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM.

CALL_REL_ALERT (MOUT_PLMN) Trigger: each time, on receipt of RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM. Note: Counts also direct calls to announcement with is no charge.

CALL_TI_OUT_ALERT (MOUT_PLMN) Trigger: each time RELEASE COMPLETE is received due to alert supervision timeout (internal event in MSC).


50 A30862-X1001-C962-2-76-A1

CALL_ATTEMPTS(MOUT_PLMN): Trigger: each time the SET UP is received and digit analysis results in this traffic type (speech call attempts only).

UNS_BS_REASON(MOUT_PLMN): Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received. – MORTR: from the BSS before digit analysis is performed. – MTER: before digit analysis is performed. – MOUT_PLMN, MOUT_NOT_PLMN: after digit analysis has been performed.

CALL_REL_EXCHANGE(MOUT_PLMN): Trigger: each time RELEASE is received indicating clear backward or UBM with causes different from busy, CUG reject, destination error.

U_SPEECH_CALLS_WITH_ANSWER(MOUT_PLMN) Trigger: each time the connection is released in response to the receipt of the respective Message ANM

U_RNC_REL_WITH_ANSWER (MOUT_PLMN) Trigger: on each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ are received for a particular reason.

U_UNS_MS_BUSY(MOUT_PLMN) each time the RELEASE UBM is received from the following exchange, with reason “subscriber busy”, for UMTS calls.

U_CALL_REL_ALERT (MOUT_PLMN) Trigger: each time RELEASE COMPLETE is received after the alert signal is sent and before CONNECT is received, for a UMTS call. Note: Counts also direct calls to announcement with is no charge.

U_CALL_REL_BEF_ALERT (MOUT_PLMN) Trigger: RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM.

U_CALL_TI_OUT_ALERT (MOUT_PLMN) Trigger: each time RELEASE COMPLETE is received due to alert supervision timeout (internal event in MSC).

U_CALL_ATTEMPTS(MOUT_PLMN): Trigger: each time the SET UP is received and digit analysis results in this traffic type (speech call attempts only), for UMTS call.

U_UNS_RNC_REASON(MOUT_PLMN) Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received for UMTS call – MOUT_PLMN, MOUT_NOT_PLMN: after digit analysis has been performed.


A30862-X1001-C962-2-76-A1 51

DATACDA_ANA_ATTEMPTS(MOUT_PLMN), DATACDA_DIG_ATTEMPTS(MOUT_PLMN), ALTFAXSP_CALL_ATTEMPTS(MOUT_PLMN), FAX3_CALL_ATTEMPTS(MOUT_PLMN), DED_PAD_ATTEMPTS(MOUT_PLMN), DATACDS_ANA_ATTEMPTS(MOUT_PLMN), DATACDS_DIG_ATTEMPTS(MOUT_PLMN), ALT_SPEECH_DATA_ATTEMPTS(MOUT_PLMN): Trigger: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

DATACDA_ANA_WITH_ANSWER(MOUT_PLMN) DATACDA_DIG_WITH_ANSWER(MOUT_PLMN), ALTFAXSP_WITH_ANSWER(MOUT_PLMN), FAX3_WITH_ANSWER(MOUT_PLMN), DED_PAD_WITH_ANSWER(MOUT_PLMN), DATACDS_ANA_WITH_ANSWER(MOUT_PLMN), DATACDS_DIG_WITH_ANSWER(MOUT_PLMN), ALT_SPEECH_DATA_ANSWER(MOUT_PLMN): Trigger: Each time the connection is released in response to the receipt of the respective message ANM.

U_CA_DATA (MOUT_PLMN): Trigger: each time SET UP is received and digit analysis results in this traffic type (data call attempts only).

U_CC_ANSW_DATA (MOUT_PLMN) Trigger: each time the connection is released in response to the receipt of the respective Message ANM

3.2.4.2 Data calls success Ratio (MMC) Description:

This procedure gives a ratio of the number of answered calls in relation to the number of attempts, Data services, broken down by service type. Level of measurement:

Per MSC/ MSC-S



KPI-formula:

Per MSC:

CDA analog service:

%100)(MOUT_PLMNA_ATTEMPTSDATACDA_AN

LMN)WER(MOUT_PA_WITH_ANSDATACDA_ANKPI ×=


%100)(MOUT_PLMNG_ATTEMPTSDATACDA_DI

LMN)WER(MOUT_PG_WITH_ANSDATACDA_DIKPI ×=



52 A30862-X1001-C962-2-76-A1

%100)(MOUT_PLMNA_ATTEMPTSDATACDS_AN

LMN)WER(MOUT_PA_WITH_ANSDATACDS_ANKPI ×=


%100PLMN)(MOUT_NOT_G_ATTEMPTSDATACDS_DI

NOT_PLMN)SWER(MOUT_IG_WITH_ANDATACDAS_DKPI ×=


Alternate speech/facsimile services:

%100MN)TS(MOUT_PLALL_ATTEMPALTFAXSP_C

)(MOUT_PLMNITH_ANSWERALTFAXSP_WKPI ×=

Data calls for automatic facsimile group 3:

%100MN)OUT_NOT_PLATTEMPTS(MFAX3_CALL_

)T_NOT_PLMNANSWER(MOUFAX3_WITH_KPI ×=

Alternate speech/data or speech followed by data services:

%100PLMN)MPTS(MOUT__DATA_ATTEALT_SPEECH

)(MOUT_PLMN WER_DATA_ ANSALT_SPEECHKPI ×=


DATACDA_ANA_WITH_ANSWER (MOUT__PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDA_ANA_ATTEMPTS(MOUT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

DATACDA_DIG_WITH_ANSWER (MOUT_ PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDA_DIG_ATTEMPTS(MOUT_ PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.


A30862-X1001-C962-2-76-A1 53

DATACDS_DIG_WITH_ANSWER (MOUT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDS_DIG_ATTEMPTS(MOU_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

ALTFAXSP_WITH_ANSWER(MOUT_ PLMN); Trigger: each time the connection has actually been released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

ALTFAXSP_CALL_ATTEMPTS(MOUT_ PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

FAX3_WITH_ANSWER(MOUT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

FAX3_CALL_ATTEMPTS(MOUT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type and SET UP is sent.

DATACDS_ANA_WITH_ANSWER (MOUT_PLMN): Trigger: each time the connection is released in response to the receipt of the respective message: – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDS_ANA_ATTEMPTS(MOUT_PLMN): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

3.2.5 Mobile Terminating Traffic KPIs

3.2.5.1 MTC Success Ratio Description:

The number of successful MTC speech calls. Level of measurement:




54 A30862-X1001-C962-2-76-A1

KPI-formula:

Hint: the CF feature must be activated

2G+3G: MTER Answer Ratio:

%100)(_

_01_

(MTER) ER_DATA_ANSWALT_SPEECH :(MTER) WERG_WITH_ANSDATACDS_DI :(MTER) WERA_WITH_ANSDATACDS_AN

:(MTER) TH_ANSWERDED_PAD_WI :(MTER) ANSWERFAX3_WITH_

:(MTER) ITH_ANSWERALTFAXSP_W :(MTER) WERG_WITH_ANSDATACDA_DI :(MTER) WERA_WITH_ANSDATACDA_AN

)(___)(___

_

×=

+++++++++

=

MTERATTEMPTSCALLAnswersCallKPI

MTERANSWERWITHRELBSMTERANSWERWITHCALLSSPEECH

AnswersCall

MTER B-Busy Ratio:

%100)MTER(ATTEMPTS_CALL

)MTER(BUSY_MS_UNS02_KPI ×=

MTER A-Release Ratio:

%100)MTER(ATTEMPTS_CALL

)MTER(ALERT_BEF_REL_CALL03_KPI

×

=

MTER No-Answer Ratio:

%100)MTER(ATTEMPTS_CALL)MTER(ALERT_REL_CALL04_KPI ×=

MTER Call Forwarding Ratio:

%100)(_

)(___05_ ×=MTERATTEMPTSCALL

MTERFORWCALLENDCALLKPI

MMC UNS RAN Ratio:

%100)(_)(SONUNS_BS_REA06_ ×=

MTERATTEMPTSCALLMTERKPI


A30862-X1001-C962-2-76-A1 55


%100)(_

)(XCHANGECALL_REL_E07_ ×=MTERATTEMPTSCALL

MTERKPI

MTER Success Rate:

07_06_05_04_03_02_01_

KPIKPIKPIKPIKPIKPIKPIKPI

++++++=

3G:

MTER Answer Ratio:

%100)(__

_01_

)(____(MTER)DATA U_CC_ANSW_

)(_____

×=

++

=

MTERATTEMPTSCALLUAnswersCallKPI

MTERANSWERWITHRELRNCU

MTERANSWERWITHCALLSSPEECHUAnswersCall

MTER B-Busy Ratio:

%100)(__

)(___02_ ×=MTERATTEMPTSCALLU

MTERBUSYMSUNSUKPI

MTER A-Release Ratio:

%100)(__

)(____03_

×=MTERATTEMPTSCALLU

MTERALERTBEFRELCALLUKPI

MTER No-Answer Ratio:

%100)(__)(___04_ ×=

MTERATTEMPTSCALLUMTERALERTRELCALLUKPI

MTER Call Forwarding Ratio:

%100)(__

)(____05_ ×=MTERATTEMPTSCALLU

MTERFORWCALLENDCALLUKPI


56 A30862-X1001-C962-2-76-A1

MMC UNS RAN Ratio:

%100)(__

)(ASONUNS_RNC_RE06_

×

=

MTERATTEMPTSCALLUMTER

KPI

MTER Success Ratio:

6_05_04_03_02_01_ KPIKPIKPIKPIKPIKPIKPI +++++=


SPEECH_CALLS_WITH_ANSWER (MTER) Trigger: each time the connection is released in response the CONNECT message.

BS_REL_WITH_ANSWER (MTER) Trigger: on each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ are received for a particular reason.

UNS_MS_BUSY (MTER) Trigger: each time the Release message is sent to the previous exchange with reason “subscriber busy”:

CALL_REL_BEF_ALERT(MTER): Trigger: RELEASE COMPLETE before alerting signal is received.

CALL_REL_ALERT (MTER) Trigger: Each time, on receipt of subscriber related RELEASE, RELEASE COMPLETE or DISCONNECT after alerting is sent and before CONNECT is received. Note: Counts also direct calls to announcement with is no charge.

CALL_END_CALL_FORW (MTER) Trigger: each time call forwarding treatment (e.g., busy, unconditional no paging response) is invoked and the previous call setup is ended.

CALL_ATTEMPTS(MTER) Trigger: each time the respective message is involved: – MTER: each time PAGING is sent. The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent (all call attempts).

UNS_BS_REASON(MOUT_PLMN): Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received. – MTER: before digit analysis is performed.

CALL_REL_EXCHANGE(MOUT_PLMN): Trigger: each time RELEASE is received indicating clear forward.

U_SPEECH_CALLS_WITH_ANSWER (MTER) Trigger: each time the connection is released in response the CONNECT message.


A30862-X1001-C962-2-76-A1 57

U_RNC_REL_WITH_ANSWER (MTER): Trigger: each time CONNECT ACK is received when SUBSYSTEM PROHIBITED, RESET,RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ for particular reason(s) were received for a UMTS call.

U_UNS_MS_BUSY (MTER) Trigger: each time the Release message is sent to the previous exchange with reason “subscriber busy”, far a UMTS call.:

U_CALL_REL_BEF_ALERT(MTER): Trigger: RELEASE COMPLETE before alerting signal is received.

U_CALL_REL_ALERT (MTER) Trigger: Trigger: Each time, on receipt of subscriber related RELEASE, RELEASE COMPLETE or DISCONNECT after alerting is sent and before CONNECT is received Note: Counts also direct calls to announcement with is no charge.

U_CALL_END_CALL_FORW (MTER) Trigger: each time call forwarding treatment (e.g., busy, no paging response) is invoked and the previous call setup is ended.

U_CALL_ATTEMPTS(MTER) Trigger: each time the respective message is involved: – MTER: each time PAGING Response is received.

U_UNS_RNC_REASON(MOUT_PLMN) Trigger: each time RELEASE COMPLETE / CLEAR REQUEST or SUBSYSTEM PROHIBITED, RESET, RESET CIRCUIT is received for UMTS call before digit analysis is performed.

U_CC_ANSW_DATA (MTER) Trigger: Each time the connection is released in response to the receipt of the respective message CONNECT, UMTS data calls.

DATACDA_ANA_WITH_ANSWER(MTER) DATACDA_DIG_WITH_ANSWER(MTER), ALTFAXSP_WITH_ANSWER(MTER), FAX3_WITH_ANSWER(MTER), DED_PAD_WITH_ANSWER(MTER), DATACDS_ANA_WITH_ANSWER(MTER), DATACDS_DIG_WITH_ANSWER(MTER), ALT_SPEECH_DATA_ANSWER(MTER): Trigger: Each time the connection is released in response to the receipt of the respective message CONNECT.

U_CA_DATA (MTER): Trigger: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. For UMTS data calls.

3.2.5.2 MTC Failure Ratio Description:

This KPI indicates the failure ratio of mobile terminating calls.

The indicator is expressed as the one’s complement of the number of successfully established mobile terminating calls divided by the number of mobile terminating call attempts. Level of measurement:

Per MSC/ MSC-S


58 A30862-X1001-C962-2-76-A1



KPI-formula:

2G+3G: %100)MTER(RESP_PAG_RECEIVED)MTER(ALLOCATION_TCH_CALL1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

3G:

%100)MTER(RESP_PAG_RECEIVED_U)MTER(ALLOCATION_TCH_CALL_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

Message Flows/Triggerpoints: CALL_TCH_ALLOCATION each time ASSIGNMENT COMPLETE is received U_CALL_TCH_ALLOCATION Each time “RAB ASSIGNMENT RESPONSE” is received.

RECEIVED_PAG_RESP each time PAGING RESPONSE is received from the BSC/RNC.

U_RECEIVED_PAG_RESP each time PAGING RESPONSE is received from the RNC.


A30862-X1001-C962-2-76-A1 59

3.2.5.3 Paging Procedure Failure Ratio Description:

This KPI indicates the failure ratio of paging procedures.

The indicator is expressed as the one’s complement of the number of successful paging procedures divided by the number of paging attempts. Level of measurement:



KPI-formula:

2G+3G: %100PROC_PAGING_STARTED

RESP_PAG_RECEIVED1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


STARTED_PAGING_PROC Incremented each time PAGING is sent.

RECEIVED_PAG_RESP Increment each time PAGING RESPONSE is received from the BSC


60 A30862-X1001-C962-2-76-A1

3.2.5.4 Data calls succes Ratio (MTC)

Description:

This procedure gives a ratio of the number of answered calls in relation to the number of attempts, for several Data services, broken down by service type. Level of measurement:



KPI-formula:

Per MSC: CDA analog services:

%100(MTER)A_ATTEMPTSDATACDA_AN

WER(MTER)A_WITH_ANSDATACDA_ANKPI ×=


%100(MTER)G_ATTEMPTSDATACDA_DI

WER(MTER)G_WITH_ANSDATACDA_DIKPI ×=



A30862-X1001-C962-2-76-A1 61

%100(MTER)A_ATTEMPTSDATACDS_AN

WER(MTER)A_WITH_ANSDATACDS_ANKPI ×=


%100(MTER)G_ATTEMPTSDATACDS_DI

SWER(MTER)IG_WITH_ANDATACDAS_DKPI ×=


alternate speech/facsimile services:

%100TS(MTER)ALL_ATTEMPALTFAXSP_C

(MTER)ITH_ANSWERALTFAXSP_WKPI ×=

automatic facsimile group 3:

%100TER)ATTEMPTS(MFAX3_CALL_

R)ANSWER(MTEFAX3_WITH_KPI ×=

Alternate speech/data or speech followed by data:

%100MPTS(MTER)_DATA_ATTEALT_SPEECH

(MTER) H_ANSWER_DATA_ WITALT_SPEECHKPI ×=


DATACDA_ANA_WITH_ANSWER (MTER): Trigger: each time the connection is released in response to the receipt of the respective message: – MTER: CONNECT

DATACDA_ANA_ATTEMPTS(MTER): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface.

DATACDA_DIG_WITH_ANSWER (MTER): Trigger: each time the connection is released in response to the receipt of the respective message: – MTER: CONNECT

DATACDA_DIG_ATTEMPTS(MTER): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface.


62 A30862-X1001-C962-2-76-A1

ALTFAXSP_WITH_ANSWER(MTER); Trigger: each time the connection has actually been released in response to the receipt of the respective message: – MTER: CONNECT

ALTFAXSP_CALL_ATTEMPTS(MTER): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface.

FAX3_WITH_ANSWER(MTER): Trigger: each time the connection is released in response to the receipt of the respective message: – MTER: CONNECT

FAX3_CALL_ATTEMPTS Trigger: each time the digit analysis after interrogation results in the relevant traffic type and SET UP is sent.

DATACDS_ANA_WITH_ANSWER (MTER): Trigger: each time the connection is released in response to the receipt of the respective message: – MTER: CONNECT – MOUT_PLMN, MOUT_NOT_PLMN: ANM

DATACDS_ANA_ATTEMPTS(MTER): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface.– MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied.

DATACDS_DIG_WITH_ANSWER (MTER): Trigger: each time the connection is released in response to the receipt of the respective message: – MTER: CONNECT

DATACDS_DIG_ATTEMPTS(MTER): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface.

ALT_SPEECH_DATA_ ANSWER (MTER): Trigger: each time the connection is released in response to the receipt of the CONNECT Message.

ALT_SPEECH_DATA_ATTEMPTS(MTER): Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface.


A30862-X1001-C962-2-76-A1 63

3.2.5.5 MTC Traffic Channel Allocation Ratio Description:

Provides the success ratio of the chanel allocation Level of measurement:



KPI-formula:

2G+3G:

%100)(___)(__×=

MTERREQCHANTRAFFGENMTERALLOCATIONTCHCALLKPI

3G:

%100

)(____)(___×=

MTERREQCHANTRAFFGENUMTERALLOCATIONTCHCALLUKPI


CALL_TCH_ALLOCATION (MTER) Trigger: each time ASSIGNMENT COMPLETE is received.

U_CALL_TCH_ALLOCATION (MTER) Trigger: each time ASSIGNMENT COMPLETE is received.

GEN_TRAFF_CHAN_REQ (MTER) Trigger: each time ASSIGNMENT REQUEST is sent to the BSC after the previous receipt of CM SERVICE REQUEST.

U_GEN_TRAFF_CHAN_REQ (MTER) Trigger: each time ASSIGNMENT REQUEST is sent to the RNC after the previous receipt of CM SERVICE REQUEST.


64 A30862-X1001-C962-2-76-A1

3.2.6 Handover KPIs

3.2.6.1 Handover Success Ratio Description:

The number of successful handover in relation to the number of attempted handover. Level of measurement:



KPI-formula:

2G+3G:

%100

Attempts_HOSuccess_HOKPI

ATTEMPTS_IC_MSC_MSC_HANDOVERMSCA_HO_MSC_MSC_SUBSEQ

ATTEMPTS_HANDOVERAttempts_HO

MSCB_HO_MSC_MSC_SEC_HO_SUCCMSCB_HO_MSC_MSC_SUBSEQ_SUCC

MSCB_HO_MSC_MSC_SUCCMSCA_HO_MSC_MSC_SUCC

HO_COMPLETED_SUCCSuccess_HO

×=

++

=

+++

+=


A30862-X1001-C962-2-76-A1 65

3G:

%100Attempts_HOSuccess_HOKPI

ATTEMPTS_IC_MSC_MSC_HANDOVER_UMSCA_HO_MSC_MSC_SUBSEQ_U

ATTEMPTS_HANDOVER_UAttempts_HO

MSCB_HO_MSC_MSC_SEC_HO_SUCC_UMSCB_HO_MSC_MSC_SUBSEQ_SUCC_U

MSCB_HO_MSC_MSC_SUCC_UMSCA_HO_MSC_MSC_SUCC_U

HO_COMPLETED_SUCC_USuccess_HO

×=

++

=

+++

+=


See Chaper : ‘Handover – Message Flows/Triggerpoints’

3.2.6.2 Intra-MSC-Handover Success Ratio Description:

The number of successful Intra-MSC handover in relation to the number of attempted Intra-MSC handover. Level of measurement:




66 A30862-X1001-C962-2-76-A1

KPI-formula:

2G+3G:

%100Attempts_HO_MSC_IntraSuccess_HO_MSC_IntraKPI

MSCB_HO_MSC_MSC_SUBSEQATTEMPTS_OG_MSC_MSC_HANDOVER

ATTEMPTS_HANDOVERAttempts_HO_MSC_Intra

MSCB_HO_MSC_MSC_SEC_HO_SUCCHO_COMPLETED_SUCC

Success_HO_MSC_Intra

×=

−−=

+=

3G:

%100Attempts_HO_MSC_IntraSuccess_HO_MSC_IntraKPI

MSCB_HO_MSC_MSC_SUBSEQ_UATTEMPTS_OG_MSC_MSC_HANDOVER_U

ATTEMPTS_HANDOVER_UAttempts_HO_MSC_Intra

MSCB_HO_MSC_MSC_SEC_HO_SUCC_UHO_COMPLETED_SUCC_U

Success_HO_MSC_Intra

×=

−−

=

+=

(Remark: R4: CS5 INTER_MGW_INTRA MSC HO missing)



3.2.6.3 Intra MSC Inter System (3G-2G) HO failure Ratio Description:

This KPI indicates the failure ratio of Intersystem (3G 2G) Hand Over procedures when one 3GMSC is involved.


A30862-X1001-C962-2-76-A1 67

The indicator is expressed as the one’s complement of the number of successful Intersystem (3G 2G) Intra MSC HO procedures divided by the number of Intersystem (3G 2G) Intra MSC HO attempts. Level of measurement:


≤ 1.0 %

KPI-formula:

%100GSM_TO_UMTS_ATT_HO_INTRA_U

GSM_TO_UMTS_HANDOVER_INTRA_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


U_INTRA_HANDOVER_UMTS_TO_GSM Each time MSC receives HANDOVER COMPLETE from the BSS, with radio source indicator set to UMTS and target source indicator set to GSM. U_INTRA_HO_ATT_UMTS_TO_GSM Each time RELOCATION REQUIRED is received within one MSC, with radio source indicator set to UMTS and target source indicator set to GSM.

Relocation Required

Handover Request

Handover Request Ack

Relocation Command

RRC Handover Command

MS/UE

Handover Detect

RRC Handover Complete

Handover CompleteIu Release Command

Iu Release Complete

U_INTRA_HANDOVER_UMTS_TO_GSM

U_INTRA_HO_ATT_UMTS_TO_GSM

RNC 3G-MSC BSC


68 A30862-X1001-C962-2-76-A1

3.2.6.4 Inter MSC Inter System (3G-2G) HO Failure Ratio Description:

This KPI indicates the failure ratio of Intersystem (3G 2G) Hand Over procedures when one 3GMSC and one 2GMSC are involved.

The indicator is expressed as the one’s complement of the number of successful Intersystem (3G 2G) Inter MSC HO procedures divided by the number of Intersystem (3G 2G) Inter MSC HO attempts. Level of measurement:



KPI-formula:

%100

OG_GSM_UMTS_ATT_HO_MSC_MSC_INTER_UGSM_TO_UMTS_HANDOVER_INTER_U1

KPI

×⎟⎟⎠

⎞⎜⎜⎝

⎛−

=


U_INTER_HANDOVER_UMTS_TO_GSM: each time HANDOVER COMPLETE is received for handover back to the MSCA, or each time SEND END SIGNAL is received from the MSC-B for handover to MSCB, both with radio source indicator set to UMTS and target source indicator set to GSM. U_INTER_MSC_MSC_HO_ATT_UMTS_GSM_OG: Each time RELOCATION REQUIRED is received within one MSC, with radio source indicator set to UMTS and target source indicator set to GSM.

Message flows: See Chaper : ‘Handover – Message Flows/Triggerpoints’

3.2.6.5 Inter-MSCA-Handover Success Ratio Description:

The number of successful Inter-MSC handover in relation to the number of attempted Inter-MSC handover at the old MSC.


A30862-X1001-C962-2-76-A1 69




KPI-formula:

2G+3G:

%100Attempts_HO_MSCA_Inter

MSCA_HO_MSC_MSC_SUCCKPI

MSCA_HO_MSC_MSC_SUBSEQATTEMPTS_OG_MSC_MSC_HANDOVER

Attempts_HO_MSCA_Inter

×=

+=

3G:

%100Attempts_HO_MSCA_Inter_U

MSCA_HO_MSC_MSC_SUCC_UKPI

MSCA_HO_MSC_MSC_SUBSEQ_UATTEMPTS_OG_MSC_MSC_HANDOVER_U

Attempts_HO_MSCA_Inter

×=

+=



3.2.6.6 Inter- MSCB- Handover Success Ratio Description: The number of successful Inter-MSC handover in relation to the number of attempted Inter-MSC handover at the new MSC. Level of measurement:




70 A30862-X1001-C962-2-76-A1

KPI-formula:

2G+3G:

%100Attempts_HO_MSCB_InterSuccess_HO_MSCB_InterKPI

MSCB_HO_MSC_MSC_SUBSEQATTEMPTS_IC_MSC_MSC_HANDOVER

Attempts_HO_MSCB_Inter

MSCB_HO_MSC_MSC_SUBSEQ_SUCCMSCB_HO_MSC_MSC_SUCC

Success_HO_MSCB_Inter

×=

+=

+=

3G:

%100Attempts_HO_MSCB_Inter_USuccess_HO_MSCB_Inter_UKPI

MSCB_HO_MSC_MSC_SUBSEQ_UATTEMPTS_IC_MSC_MSC_HANDOVER_U

Attempts_HO_MSCB_Inter

MSCB_HO_MSC_MSC_SUBSEQ_SUCC_UMSCB_HO_MSC_MSC_SUCC_U

Success_HO_MSCB_Inter

×=

+=

+=



3.2.6.7 Inter MSC SRNS Relocation Failure Ratio Description:

This KPI indicates the failure ratio of servicing RNC relocation procedures when two 3GMSCs are involved.

The indicator is expressed as the one’s complement of the number of successful Inter MSC SRNS relocations divided by the number of Inter MSC SRNS relocation attempts.


A30862-X1001-C962-2-76-A1 71




KPI-formula:

Per MSC:

%100

_____________

__________

1 ×

⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜

⎝

⎛

−

−−

=

OGGSMUMTSATTHOMSCMSCINTERUATTEMPTSOGMSCMSCHANDOVERU

GSMTOUMTSHANDOVERINTERUMSCAHOMSCMSCSUCCU

KPI



3.2.6.8 Handover - Message Flows/Triggerpoints

GSM Inter MSC Handover :


72 A30862-X1001-C962-2-76-A1

GSM Intra MSC Handover:

GSM Subsequent Inter-MSC Handover Back to A:

GSM Subsequent Inter MSC Handover:


A30862-X1001-C962-2-76-A1 73

GSM Subsequent Intra MSC-B Handover:

UMTS Inter MSC Handover:


74 A30862-X1001-C962-2-76-A1

UMTS Intra MSC Handover:

Relocation Required

Relocation Request

Relocation Request AcknRelocation Command


MS/UE

Handover Access Relocation Detect

RRC Handover Complete Relocation Complete

Iu Release Command

Iu Release Complete

+ U_SUCC_COMPLET

ED_HO

+ U_HANDOVER_

ATTEMPTS

RNC old RNC new 3G-MSC

ERQ

ECF

RLC

REL


A30862-X1001-C962-2-76-A1 75

UMTS Subsequent Inter MSC Handover Back to A:

RNC new

Relocation Required

Request : Prepare Subsequent Handover

Relocation Request AcknRelocation CommandRRC Handover Command

MS/UE

Handover Access

Relocation Detect


Relocation Complete

Iu Release Command

Iu Release Complete

3G-MSC-A

Relocation Request

Response : Prepare Subsequent Handover

Request : Send End Signal

+ U_SUCC_MSC_MSC_HO_MSCB

+ U_SUCC_MSC_MSC_HO_

MSCA

+ U_HANDOVER_ATTEMPTS

+ U_SUBSEQ_MSC_MSC_HO_MSCB

+ U_SUBSEQ_MSC_MSC_H

O_MSCA

RNC old 3G-MSC-B

ERQ

ECF

REL

RLC

REL

RLC

UMTS Subsequent Inter MSC Handover:


76 A30862-X1001-C962-2-76-A1

UMTS Subsequent Intra MSC-B Handover:

Relocation Required

Relocation Request

Relocation Request AcknRelocation Command


MS/UE

Handover Access Relocation Detect

RRC Handover Complete Relocation Complete

Iu Release Command

Iu Release Complete

+ U_HANDOVER_ATT

EMPTS

RNC old RNC new 3G-MSC-B

ERQ

ECF

RLC

REL

+ U_SUCC_HO_SEC_MSC_

MSC_HO_MSCB

3G-MSC-A

Process Access Signalling(HO_PERFORMED)

Intra MSC Inter System (3G-2G) Handover:

Relocation Required

Handover Request


Relocation Command


MS/UE

Handover Detect


Handover CompleteIu Release Command

Iu Release Complete

U_INTRA_HANDOVER_UMTS_TO_GSM


RNC 3G-MSC BSC


A30862-X1001-C962-2-76-A1 77

Inter MSC Inter System (3G-2G) Handover:

Relocation Required

Handover Request


Relocation Command


MS/UE

Handover Detect


Handover Complete

Iu Release Command

Iu Release CompleteU_INTRA_HANDOVER_

UMTS_TO_GSM


RNC 3G-MSC BSC BSC

Prepare Handover

Prepare Handover Response

Send End Signal request

Send End Signal Response

3.2.7 SMS Analysis

3.2.7.1 SMS Failure Ratio Description:

The number of failed incoming and failed outgoing SMS messages in relation to the number of attempted incoming and attempted outgoing SMS messages. Level of measurement:




78 A30862-X1001-C962-2-76-A1

KPI-formula:

2G+3G

%100ATTEMPTSSUCCESS1KPI

ATTEMPTS_OTG_SMSATTEMPTS_INC_SMSATTEMPTS

OTG_SMS_SUCCINC_SMS_SUCCSUCCESS

×⎟⎠⎞

⎜⎝⎛ −=

+=

+=

3G

%100ATTEMPTSSUCCESS1KPI

ATTEMPTS_OTG_SMS_UATTEMPTS_INC_SMS_UATTEMPTS

OTG_SMS_SUCC_UINC_SMS_SUCC_USUCCESS

×⎟⎠⎞

⎜⎝⎛ −=

+=

+=


2G/3G-GMSC/VLRMS/UE BSC/RNC

CM_Service_Request(CM Service Type=SMS)

HLR

+ (U_)SUCC_SMS_OTG

SMS-GW

CP DATA(RP_ACK(SMS_SUBMIT_REPORT))

MAP_MO Forward Short Message Ack(RP_UD(SMS_SUBMIT_REPORT))

Paging, Authentication, Security

+ (U_)SMS_OTG_ATTEMPTS MAP_MO Forward Short Message(SC Address, MSIsdn, RP_UD(SMS_SUBMIT))

CP DATA(RP_MO_DATA(SMS_SUBMIT))

CP ACK

CP ACK

+ U_SMS_SER_REQ_ATTEMPTS


A30862-X1001-C962-2-76-A1 79

3.2.7.2 SMS-MT Failure Ratio

Description:

The number of unsuccessful incoming SMS messages in relation to the number of attempted incoming SMS messages. Level of measurement:



KPI-formula:

2G+3G: %100ATTEMPTS_INC_SMS

INC_SMS_SUCC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

3G: %100ATTEMPTS_INC_SMS_U

INC_SMS_SUCC_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


80 A30862-X1001-C962-2-76-A1


(For 3G the attempt counter is incremented after Paging).


CP ACK

HLR

+ SMS_INC_ATTEMPTS

SMS-GW

MAP_Send Routing Info For SM(MSIsdn, SM-RO-PRI, SC Address)

CP DATA(RP_MT_DATA(SMS_DELIVER))

MAP_Send Routing Info For SM Ack(IMSI/LMSI, MSC)

MAP_MT Forward Short Message(SC Address, IMSI/LMSI, RP_UD(SMS_DELIVER))


CP DATA(RP_ACK(SMS_DELIVER_REPORT)

CP ACK

+ (U_)SUCC_SMS_INC MAP_MT Forward Short Message Ack(RP_UD(SMS_DELIVERY_REPORT))

+ U_SMS_INC_ATTEMPTS

Figure: SMS-MT succesful

3.2.7.3 SMS-MT Delivery Failed Ratio Description:

The number of unsuccessful SMS-MT due to “Delivery Failed” in relation to the number of attempted SM-MT. Level of measurement:




A30862-X1001-C962-2-76-A1 81

KPI-formula:


FAIL_DELIVERY_INC_SMS_UNSKPI ×=


2G/3G-GMSC/VLRMS/UE BSC/RNC HLR

+ SMS_INC_ATTEMPTS

SMS-GW

MAP_Send Routing Info For SM(MSIsdn, SM-RO-PRI, SC Address)

MAP_Send Routing Info For SM Ack(IMSI/LMSI, MSC)

MAP_MT Forward Short Message(SC Address, IMSI/LMSI, RP_UD(SMS_DELIVER))

+ UNS_SMS_INC_DELIVERY_FAIL MAP_MT Forward Short Message Error(RP_UD(User error = unknown SC, SC congestion, invalid SMS address, subscriber not SC subscriber))


the MSC detects any error

Figure: SMS-MT delivery failure

3.2.7.4 SMS-MT No Facility Ratio Description:

The number of unsuccessful SMS-MT due to “No Facility” in relation to the number of attempted SM-MT. Level of measurement:




82 A30862-X1001-C962-2-76-A1

KPI-formula:


FACILITY_NO_INC_SMS_UNSKPI ×=

Message Flows/Triggerpoints: UNS_SMS_INC_NO_FACILITY: Trigger: each time FORWARD SHORT MESSAGE ERROR indicating “facility not supported” is sent to the SMS gateway.

SMS_INC_ATTEMPTS Trigger: each time FORWARD SHORT MESSAGE is received from the SMS gateway.

3.2.7.5 SMS- MO Failure Ratio Description:

The number of unsuccessful outgoing SMS messages in relation to the number of attempted outgoing SMS messages. Level of measurement:



KPI-formula:

2G+3G : %100ATTEMPTS_OTG_SMS

OTG_SMS_SUCC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

3G: %100ATTEMPTS_OTG_SMS_U

OTG_SMS_SUCC_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


A30862-X1001-C962-2-76-A1 83




HLR

+ (U_)SUCC_SMS_OTG

SMS-GW

CP DATA(RP_ACK(SMS_SUBMIT_REPORT))

MAP_MO Forward Short Message Ack(RP_UD(SMS_SUBMIT_REPORT))


+ (U_)SMS_OTG_ATTEMPTS MAP_MO Forward Short Message(SC Address, MSIsdn, RP_UD(SMS_SUBMIT))


CP ACK

CP ACK

+ U_SMS_SER_REQ_ATTEMPTS

Figure: SMS_MO successful

3.2.7.6 Mobile Originating SMS Failure Ratio (IuCS interface) Description:

This KPI indicates the failure ratio of mobile originating SMS on the interface between RNC and MSC (IuCS).

The indicator is expressed as the one’s complement of the number of SMS successfully acknowledged by the MSC divided by the total number of SMS attempts received. Level of measurement:




84 A30862-X1001-C962-2-76-A1

KPI-formula:

Per MSC:

%100ATTEMPTS_REQ_SER_SMS_U

ATTEMPTS_OTG_SMS_U1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=


U_SMS_SER_REQ_ATTEMPTS Each time the CM_Service_Request is received with CM ServiceType equal to SMS

U_SMS_OTG_ATTEMPTS Each time the FORWARD SHORT MESSAGE is sent to the SMS gateway when radio source indicator is set to UMTS.

Message Flows : See chapter: ‘SMS - MO Failure Ratio’

3.2.7.7 SMS-MO Delivery failed Ratio Description:

The number of unsuccessful SMS-MO due to “Delivery Failed” in relation to the number of attempted SM-MO. Level of measurement:



KPI-formula:

2G+3G: %100ATTEMPTS_OTG_SMS

FAIL_DELIVERY_OTG_SMS_UNSKPI ×=


A30862-X1001-C962-2-76-A1 85




HLR

+ UNS_SMS_OTG_DELIVERY_FAIL

SMS-GW

MAP_MO Forward Short Message Error(RP_UD(User error = unknown SC, SC congestion, invalid SMS address, subscriber not SC subscriber))

Authentication, Security

+ SMS_OTG_ATTEMPTS MAP_MO Forward Short Message(SC Address, MSIsdn, RP_UD(SMS_SUBMIT))


CP ACK

Figure: SMS_MO delivery failure

3.2.8 IN/CAMEL Dialog Failure Ratio Description:

This KPI reveals the ratio of released call due to the IN/CAMEL problems Level of measurement:



KPI-formula:


86 A30862-X1001-C962-2-76-A1

For MORTR and MICTR :

%100)x(ATTEMPTS_IN

)x(CHECK_SERV_IN)x(SCP_ANSW_NO_IN

)x(OVERLOAD_IN

KPI

)MICTR,MORTR€(x

×⎥⎥⎥

⎦

⎤

⎢⎢⎢

⎣

⎡++

+

=


IN_ATTEMPTS Trigger: each time interworking to an IN service control point (SCP) is started upon detection of a subscribed IN service or as a result of digit evaluation (e.g., dial an IN directory number) being part of a call setup. IN_NO_ANSW_SCP Trigger: each time an IN dialog to the SCP is started and no answer is received within a timer schedule. The call setup is then released IN_OVERLOAD Trigger: each time call setup with prompted call handling is released due to IN overload prevention measures. IN_SERV_CHECK: Trigger: each time that the SSP releases a call due to exeeded IN traffic restrictions values

3.2.9 IN request Failure Ratio Description:

This KPI indicates the failure ratio of request to the Intelligent Network.

The indicator is expressed as the one’s complement of the number of answered IN requests divided by the total number of IN requests sent out by the MSC. Level of measurement:




A30862-X1001-C962-2-76-A1 87

KPI-formula:

2G+3G:

%100NS_INITIATIO DIALOGATTEMPTED_

TCAPBY ACCEPTEDNOT MESSAGESCP FROM MESSAGE CTIONERROR/REJE

SSPBY LOCALLY ABORTTCAP REMOTE OR SCPBY ABORTED

RESPONSE ON TIMEOUTSSPBY SENT MSG CTERROR/REJE

KPI ×

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+++++

=


ATTEMPTED_DIALOG _INITIATIONS: Trigger: trial to send TCAP primitive TC_BEGIN_REQ or when C:SCP_CONTROLLED_INPUT_RESPONSE (ServiceFilteringResponse) is received.

ERROR/REJECT MSG SENT BY SSP Trigger: send TC_U_ERR_req, TC_U_REJ_req and dialog handling primitives (TC_CONTINUE for CA dialogs and TC_END_req for MESSAGE_FROM_TCAP_NOT_ACEPTED

TIMEOUT ON RESPONSE Trigger: expiry of timers T_SSF and T_ERR.

ABORTED BY SCP OR REMOTE TCAP Trigger: receipt of TC_U_ABORT_ind from the SCP.

ABORT LOCALLY BY SSP: Trigger: – TC_U_ABORT with User_Info 'InterfaceEvent' (except 'SSF-Timer Expired'), 'InternalEvent' and 'SRFEvent' – TC_END (local) sent in internal error situations. – TC_U_ABORT or TC_END (local) cannot be sent because the 'provider status' has already been set to 'terminated' – The number of CP detected opened NCA dialogs with Message_Type /= BEGIN (not for SINAP1 dialogs)

MESSAGE NOT ACCEPTED BY TCAP Trigger: reception of the following TCAP responses: – TC_ASN_ind, TC_Alarm_ind, TC_NOTICE with any cause – TC_L_REJ_ind when leading to an unsuccessful dialog – TC_P_ABORT


88 A30862-X1001-C962-2-76-A1

3.2.10 Supplementary Services Request Failure Ratio Description:

This KPI reveals the success ratio for invocation of supplementary services (Call Forwarding, Advice of Charge, Charging Info, Multiparty, Put on Hold, Retrieve from Hold, Call Back, Call Transfer, MORTR&MTER CCBS, Multiparty Split).

Hint: network parameterization call forwarding feature must be activated. Level of measurement:

Per MSC/ MSC-S Per SS System-KPI target value:


KPI-formula:

Per SS:

%100FORWARD_CALL_SERV_INVOC

FORWARD_CALL_SERV_INVOC_SUCC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

%100CHARGE_AOC_SERV_INVOCCHARGE_AOC_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100___

___1 ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

INFOCHARGEAOCINVOCINFOAOCINVOCSUCCKPI

%100MULTIPARTY_SERV_INVOCMULTIPARTY_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100HOLD_PUT_SERV_INVOCHOLD_PUT_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100HOLD_RETRIEVE_SERV_INVOCHOLD_RETRIEVE_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100BACK_CALL_SERV_INVOCBACK_CALL_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=


A30862-X1001-C962-2-76-A1 89

%100TRANSFER_CALL_SERV_INVOCTRANSFER_CALL_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100MORTR_CCBS_SERV_INVOCMORTR_CCBS_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100MTER_CCBS_SERV_INVOCMTER_CCBS_INVOC_SUCC1KPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛−=

%100Y_SPLIT_MPTINVOC_SERVY_SPLIT_MPTSUCC_INVOC1KPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛−=

Per MSC:

%100

____________

______

_____

_________

____________

______

_____

______

____

1 ×

⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

++

++

++++++

++

++

+++

++

+

−=

MTERCCBSSERVINVOCMORTRCCBSSERVINVOCTRANSFERCALLSERVINVOCBACKCALLSERVINVOC

HOLDRETRIEVESERVINVOCHOLDPUTSERVINVOC

MPTYSPLITSERVINVOCMULTIPARTYSERVINVOC

INFOCHARGEAOCINVOCCHARGEAOCSERVINVOCFORWARDCALLSERVINVOC

MTERCCBSINVOCSUCCMORTRCCBSINVOCSUCCTRANSFERCALLINVOCSUCCBACKCALLINVOCSUCC

HOLDRETRIEVEINVOCSUCCHOLDPUTINVOCSUCC

MPTYSPLITINVOCSUCCMULTIPARTYINVOCSUCC

INFOAOCINVOCSUCCCHARGEAOCINVOCSUCC

FORWARDCALLSERVINVOCSUCC

KPI


90 A30862-X1001-C962-2-76-A1


INVOC_SERV_CALL_FORWARD CFU: each time a forwarded-to-number is received after HLR interrogation. CFBeach time call is forwarded after busy state is detected.: CFNRy: each time this timer has expired. CFNRc: each time – in GMSC: when an interrogation of the HLR has then delivered a forwarded-to number for a detached subscriber. – in VMSC: when an MTC has then been forwarded due to either no paging response or to radio congestion.

SUCC_INVOC_SERV_CALL_FORWARD CFU: each time a forwarded-to-number is received after HLR interrogation. CFB: each time call is forwarded after busy state is detected, CFNRy: each time this timer has expired. CFNRc: each time – in GMSC: when an interrogation of the HLR has then delivered a forwarded-to number for a detached subscriber. – in VMSC: when an MTC has then been forwarded due to either no paging response or to radio congestion.

INVOC_SERV_AOC_CHARGE each time this service is invoked.

SUCC_INVOC_AOC_CHARGE each time this service is invoked and successfully processed in the home exchange.

INVOC_SERV_AOC_INFO each time this service is invoked.

SUCC_INVOC_AOC_INFO each time this service is invoked and successfully processed in the home exchange.

INVOC_SERV_MULTIPARTY each time this service is invoked and recognized during database access.

SUCC_INVOC_MULTIPARTY each time this service is invoked and successfully processed in the home exchange.

INVOC_SERV_PUT_HOLD each time the call on hold is released and this service is recognized during database access.

SUCC_INVOC_PUT_HOLD each time the call on hold is released and successfully processed in the home exchange.

INVOC_SERV_RETRIEVE_HOLD each time the call on hold is released and this service is recognized during database access.

SUCC_INVOC_RETRIEVE_HOLD each time the call on hold is released and successfully processed in the home exchange.

INVOC_SERV_CCBS_MORTR each time the CCBS REQUEST is sent from MSC-A.


A30862-X1001-C962-2-76-A1 91

SUCC_INVOC_CCBS_MORTR each time an IAM is sent to the MSC-B after the previous receipt of REMOTE USER FREE.

INVOC_SERV_CCBS_MTER each time CCBS REQUEST is received in MSC-B.

SUCC_INVOC_CCBS_MTER each time an IAM is received in the MSC-B after the previous receipt of REMOTE USER FREE.

INVOC_SERV_CALL_BACK each time this service is invoked and recognized during database access.

SUCC_INVOC_CALL_BACK each time this service is invoked and recognized during database access.

INVOC_SERV_CALL_TRANSFER each time this service is invoked and call transfer condition is recognized during database access.

SUCC_INVOC_CALL_TRANSFER each time a new configuration is set up, a release or facility message is sent to the MS including RETURN RESULT in response to INVOKE SS.

INVOC_SERV_SPLIT_MPTY Trigger: each time this service is invoked and recognized during database access.

3.2.11 Inter MGW HO Failure Ratio (MSC-S only) Description:

The number of successful Inter MGW handover in relation to the number of attempted inter MGW handover. Level of measurement:



KPI-formula:

2G+3G: 100HO_ATTSINTER_MGW_

_MGW_HOSUCC_INTER KPI ×=


SUCC_INTER_MGW_HO Trigger: This counter will be triggered on receiving the ISCCP message HO_EXECUTED.


92 A30862-X1001-C962-2-76-A1

INTER_MGW_HO_ATTS Trigger: Number of MGW outgoing requests for inter-MGW

3.3 HLR/AC related KPIs

3.3.1 MAP Dialog – MSRN Provisioning Success Ratio Description:

This KPI reveals the success ratio of the MSRN provisioning procedure. Level of measurement:

Per HLR System-KPI target value:


%100MSRN_PROV_SND

MSRN_RECVDKPI ×=


RECVD_MSRN Trigger: each time a roaming number is returned from a VLR as a successful response to PROVIDE ROAMING NUMBER.

SND_PROV_MSRN Trigger: each time SEND PROVIDE ROAMING NUMBER is sent to the VLR.

3.3.2 Cancel Location Failure Ratio Description:

This KPI reveals the success ratio of the MSRN provisioning procedure. Level of measurement:

Per HLR


A30862-X1001-C962-2-76-A1 93


Equal to or less than 0.1% KPI-formula:

2G+3G

%100

ER_SCIOC_MSG_AFTSENT_CAN_LADMINC_MSG_SUB_SND_CAN_LO

UPDC_MSG_LOC_SND_CAN_LO_SS_ANY_OTHERUNS_CANLOC

UB_SS_UNIDENT_SUNS_CANLOC_ANY_OTHERMIN_CANLOCUNS_SUB_AD

S_UNIDENT_MMIN_CANLOCUNS_SUB_ADT_SUBMSG_UNIDENUNS_CANLOC

HERMSG_ANY_OTUNS_CANLOC

KPI ×

⎟⎟⎟

⎠

⎞

⎜⎜⎜

⎝

⎛

+++

+

⎟⎟⎟⎟⎟⎟⎟⎟

⎠

⎞

⎜⎜⎜⎜⎜⎜⎜⎜

⎝

⎛

+++

++++

+++

=


UNS_CANLOCMSG_ANY_OTHER Trigger: each time TC-END U-ERROR/REJECT/CANCEL is received upon sending CANCEL LOCATION to the VLR.

UNS_CANLOCMSG_UNIDENT_SUB Trigger: each time TC-END U-ERROR is received upon sending CANCEL LOCATION to the VLR.

UNS_SUB_ADMIN_CANLOC_UNIDENT_MS Trigger: each time TC-END U-ERROR due to unidentified subscriber is received from the VLR upon sending CANCEL LOCATION via CAN SUB.

UNS_SUB_ADMIN_CANLOC_ANY_OTHERTrigger: each time TC-END U-ERROR (negative VLR response) is received from the VLR or TC-CANCEL (HLR timer expires) upon sending CANCEL LOCATION via an MML command.

UNS_CANLOC_UNIDENT_SUB_SS Trigger: each time CANCEL LOCATION is sent to the VLR and TC-Error due to “unidentified subscriber” is received.

UNS_CANLOC_ANY_OTHER_SS Trigger: each time CANCEL LOCATION is sent to the VLR and TC-Reject, TC-Abort is received or HLR timer has expired due to no reply from VLR.

SND_CAN_LOC_MSG_LOC_UPD Trigger: each time CANCEL LOCATION is sent.

SND_CAN_LOC_MSG_SUB_ADMIN Trigger: each time CAN MSUB (subscriber is deleted in HLR or VLR database) is sent.

SENT_CAN_LOC_MSG_AFTER_SCI Trigger: each time CAN MSUB (subscriber is deleted in HLR or VLR database) is sent.


94 A30862-X1001-C962-2-76-A1

3.3.3 MAP Dialog – Interrogation Success Ratio Description:

This KPI reveals the success ratio of the interrogation procedure. Level of measurement:



2G+3G

[ ][ ][ ][ ]

%100

MICTRIONSINTERROGAT_STARTEDMORTRIONSINTERROGAT_STARTEDMICTRIONSINTERROGAT_COMPL

MORTRIONSINTERROGAT_COMPL

KPI ×

⎥⎦

⎤⎢⎣

⎡+

+

⎥⎦

⎤⎢⎣

⎡+

+

=


COMPL_INTERROGATIONS Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR

STARTED_INTERROGATIONS Trigger: each time SEND ROUTING INFO is sent on receipt of SETUP


A30862-X1001-C962-2-76-A1 95

3.3.4 IMEI Check Break down

Description:

This KPI indicates gives the break down of the IMEI Check answers.

The indicator is expressed as type of answer for IMEI check in relation to the number of IMEI checks

Note: EIR must be configured Level of measurement:



2G+3G: White answers:

100_CHECKSTART_IMEINUM_TOTAL_

HECK_WHITENUM_IMEI_CKPI ×=


96 A30862-X1001-C962-2-76-A1

Grey answers:


HECK_GREYNUM_IMEI_CKPI ×=

Black answers:


HECK_BLACKNUM_IMEI_C×=KPI

IMEI Unknown:


WNHECK_UNKNONUM_IMEI_CKPI ×=


NUM_TOTAL_START_IMEI_CHECK: Trigger: each time CHECK IMEI is sent to the EIR.

NUM_IMEI_CHECK_WHITE Trigger: each time the EIR sends a white list after having performed an IMEI check.

NUM_IMEI_CHECK_GREY Trigger: each time the EIR sends a grey list after having performed an IMEI check.

NUM_IMEI_CHECK_BLACK Trigger: each time the EIR sends a black list after having performed an IMEI check.

NUM_IMEI_CHECK_UNKNOWN Trigger: each time the EIR sends IMEI unknown after having performed an IMEI check.

3.3.5 Authentication Vector Request Success Ratio Description:

This KPI reveals the success of the authentication procedure. Level of measurement:




A30862-X1001-C962-2-76-A1 97

KPI-formula:

2G,3G :

%100C_TO_HLREQ_AUTH_VESEND_PAR_R

INFRECV_AUTH_KPI

ETS_HLR_INF_QUINTRECVD_AUTHES_HLR_INF_TRIPLRECVD_AUTHINFRECV_AUTH_

×=

+=


2G-MSCMS/UE BSC

If normal authentication : + AUTH_REQIf authentication after CKSN mismatch :

+ AUTH_REQ_CKSN_MISMATCHAUTHENTICATION_REQUESTAUTHENTICATION_REQUEST

AUTHENTICATION_FAILUREAUTHENTICATION_FAILURE

count the appropriate failure counter+ AUTH_SYNCRON_FAIL_RECEIVED

+ AUTH_MAC_FAIL_RECEIVED+ AUTH_SRES_MISMATCH

SEND_AUTHENTICATION_INFO(triplets)

SEND_AUTHENTICATION_INFO(triplets)

HLR/AC

If no triplets available -> request some

+ SEND_PAR_REQ_AUTH_VEC_TO_HLR

+ RECVD_AUTH_INF_TRIPLES_HLR

AUTHENTICATION_FAILURE_REPORT

AUTHENTICATION_FAILURE_REPORT response

+ AUTH_AUTH_FAIL_REP_REQ

+ AUTH_AUTH_FAIL_REP_SUCC


98 A30862-X1001-C962-2-76-A1

3.3.6 Authentication Failure Ratio (Network authenticates USIM)

Description:

This KPI indicates the failure ratio of USIM authentication procedures performed by the Network.

The indicator is expressed as the one’s complement of the number of successful authentication procedures divided by the number of authentication attempts.


Per MSC



KPI-formula:

%100AUTN_WITH_REQ_AUTHMISMATCH_XRES_RES_AUTH_USIMKPI ×⎟⎟

⎠

⎞⎜⎜⎝

⎛=

Message Flows/Triggerpoints: USIM_AUTH_XRES_MISMATCH Fails because an erroneous RES is received as Authentication and Ciphering Response, except SRES AUTH_REQ_WITH_AUTN

Transmission of an “Authentication and Ciphering Request” with quintets to RNC. Retries not counted.mismatch


A30862-X1001-C962-2-76-A1 99

3.3.7 Authentication Failure Ratio (Network authenticates SIM) Description:

This KPI indicates the failure ratio of 2G-SIM authentication procedures performed by the Network.

The indicator is expressed as the one’s complement of the number of successful authentication procedures divided by the number of authentication attempts. Level of measurement:


Equal to or greater than 99.9% KPI-formula: 3G

%100MISMATCH_CKSN_REQ_AUTHREQ_AUTH

MISMATCH_SRES_AUTHKPI ×⎟⎟⎠

⎞⎜⎜⎝

⎛+

=


AUTH_SRES_MISMATCH Fails because an erroneous RES is received as Authentication and Ciphering Response, except SRES mismatch AUTH_REQ Transmission of an “Authentication and Ciphering Request” with triplets to RNC. Retries not counted.


100 A30862-X1001-C962-2-76-A1

AUTH_REQ_CKSN_MISMATCH Each time AUTHENTICATION REQUEST is sent to the MS after detection of CKSN mismatch. Message Flows: see chapter before

3.4 MGW-KPIs

3.4.1 Transcoding Failure Ratio Description:

The number of unsuccessful (rejected) voice calls due to transcoding-failure in relation to the total number of attempted voice calls.

This KPI should be used to verify the correct working of MGW, i.e. the calls set up correctly. Level of measurement:

Per MGW System-KPI target value:


100%sVoice_CallAttempted_

rej_callsKPI

rej_callsle_trcalls_doubsccalls_trancalls_trfosVoice_CallAttempted_

×=

+++=


Not available.

3.4.2 Data Call Failure Ratio Description:

The number of unsuccessful (rejected) data calls in relation to the total number of attempted data calls.


A30862-X1001-C962-2-76-A1 101

This KPI reveals the correct working of MGW with respect to error free data call handling (BS20 t/nt, BS30). Level of measurement:



100%Data_CallsAttempted_

a_CallsUnsucc_DatKPI

ta_callrej_uns_daprej_bs30_utrej_bs20_nrej_bs20_tup_30bs_callsnt_20bs_callst_20bs_calls

Data_CallsAttempted_

ta_callrej_uns_daprej_bs30_utrej_bs20_nrej_bs20_ta_CallsUnsucc_Dat

×=

++++++

=

+++=


Not available.

3.4.3 Data Call Failure Ratio (per call type) Description:

The number of unsuccessful (rejected) data calls per call type in relation to the total number of attempted data calls.

The data call rejection rate can be evaluated for each data service sepearately (BS20 T, BS20 NT, …) and for all data services at once. This KPI delivers first information whether data services are handled properly. Furthermore a bad KPI value can also indicate insufficient inter working functions on the MSB.


102 A30862-X1001-C962-2-76-A1




100%ej_bs30_uprup_30bs_allsc

prej_bs30_uKPI_3

100%ej_bs20_ntr_ntcalls_bs20

trej_bs20_nKPI_2

100%t_20bs_rej_tcalls_bs20

rej_bs20_tKPI_1

×+

=

×+

=

×+

=


Not available.

3.4.4 Inserted Announcement Failure Ratio Description:

The number of unsuccessful inserted announcements in relation to the total number of inserted announcements.

This measurements can be used to check whteher the insertion of announcements functions well. A bad KPI value would be proof for either insufficient announcement capacity on one MGW or a proof for a configuration error within the announcements. Level of measurement:

Per MGW


A30862-X1001-C962-2-76-A1 103



100%fail_annins_ann

fail_annKPI ×+

=


Not available.

3.4.5 Inserted Tone Failure Ratio Description:

The number of unsuccessful inserted tones in relation to the total number of inserted tones.

This measurements can be used to check whteher the insertion of tones functions well. A bad KPI value would be proof for insufficient tone capacity on one MSB. Level of measurement:



100%fail_tonesins_tones

fail_tonesKPI ×+

=


Not available.


104 A30862-X1001-C962-2-76-A1

3.4.6 Conference Call Establishment Failure Ratio Description:

The number of unsuccessful established conference calls in relation to the total number of conference calls.

This measurements can be used to check whether the multiparty devices are working properly. A bad KPI value would be proof for insufficient multiparty channles on one MSB. Level of measurement:



KPI-formula: Internal MGW:

100%Y_MULTIPARTINVOC_SERV

Y_MULTIPARTSUCC_INVOC-Y_MULTIPARTINVOC_SERVKPI

×

=

External MGW:

100%rej_mptympty

rej_mptyKPI ×+

=


Not available.

3.4.7 Receiving IP Bearer Negotiation Failure Ratio Description:

The number of unsuccessful IP-Bearer negotiations requested by another MGW in relation to the attempted IP Bearer negotiations requested by another MGW. Level of measurement:




A30862-X1001-C962-2-76-A1 105

KPI-formula:

100%ngest_IncomiIPBCP_Requ

ingpted_OutgoIPBCP_Acce-ngest_IncomiIPBCP_RequKPI ×=


See next section

3.4.8 Initiating IP Bearer Negotiation Failure Ratio Description:

The number of unsuccessful IP-Bearer negotiations initiated by the MGW in relation to the attempted IP Bearer negotiations initiated by the MGW.

This KPI reveals the quality of the tunnel for the IP transport bearer that is used for communication between MGWs that are not handled by the same MSC-S. A bad KPI value will show encoding/decoding, protocol errors and lack of MGW resources for outgoing IPBCP messages.. This KPI can be influenced by insufficient resources or high load within the MGW that lead to a timer expiry. Level of measurement:

Per MGW



100%ngest_OutgoiIPBCP_Requ

ingpted_IncomIPBCP_Acce-ngest_OutgoiIPBCP_RequKPI ×=



106 A30862-X1001-C962-2-76-A1

AddRsp (C1,T2,TunOpt=1,...)

Notify.Rsp (C1,T2,...)

MSC-S:O MSC-S:T MGW:TMGW:O

AddReq (C?,T?,TunOpt=1,...)

Prepare Bearer

Notify.Ind (C1,T2,BIT,...)

Tunnel Info Up IAM (ConnFw,Scl,BIT,...)AddReq (C?,T?,TunOpt=1,BIT,...)


Prepare Bearer + Tunnel Info Down


Notify.Rsp (C2,T3,...)Tunnel Info UpAPM (ConFw_Not_SelCodec,ScAcll,BIT,...)

ModReq (C1,T2,BIT,...)

Tunnel Info DownModRsp (C1,T2,...)

CN_Fast_Forward 12.9.05

+ IPBCP_Request_Outgoing

+ IPBCP_Accepted_Incoming

+ IPBCP_Request_Incoming

+ IPBCP_Accepted_Outgoing

Fast Forward Tunneling





Prepare Bearer


Tunnel Info Up IAM (ConnBw,Scl,BIT,...)

AddReq (C?,T?,TunOpt=1,BIT,...)


Prepare Bearer + Tunnel Info Down



Tunnel Info Up

APM (BIT,...)ModReq (C1,T2,BIT,...)

Tunnel Info DownModRsp (C1,T2,...)

CN_Fast_Backward 12.9.05

APM (SelectedCodec,ScAcl)ModReq (C1,T2,Codec,...)

ModRsp (C1,T2,...)Modify Char



+ IPBCP_Request_Incom

ing

+ IPBCP_Accepted_Outg

oing

Fast Backward Tunneling


A30862-X1001-C962-2-76-A1 107

Delayed Forward Tunneling




AddReq (C?,T?,TunOpt=2,“Est“,...)






Prepare Bearer

Tunnel Info Up

APM (BIT,...)ModReq (C2,T3,BIT,...)

ModRsp (C2,T3,...)Tunnel Info Down

CN_Delayed_Backward 12.9.05

IAM (ConnBw,Scl,...)

Establish Bearer

APM (BIT,...)

APM (SelectedCodec,ScAcl)

ModReq (C1,T2,Codec,...)

ModRsp (C1,T2,...)Modify Char

ModReq (C1,T2,BIT,...)

ModRsp (C1,T2,...)

Tunnel Info Down

Tunnel Info Up

+ IPBCP_Request_Incoming

+ IPBCP_Accepted_Outgoing



Delayed Backward Tunneling


108 A30862-X1001-C962-2-76-A1

4 Core-Part of Transaction Delay

Due to the great amount of requirements,combinations,scenarios and technologies it is necessary to specify the important parameters(Delay, setup times) with an analytical approach.

To get an impression of all the possible configurations and preconditions most important are mentioned now:

• R99 and R4 architecture

• Transport technologies core: TDM, ATM, IP

• 2G , 3G technologies

• Different network topologies, e.g. MGWext, int ; MSC, MSC-S

• Use of different features (NP, IN)

• Many network parameters(e.g. with respect to Uu)

• Signaling in core: SS7, SIGTRAN, different bandwiths

• Different call scenarios: forward/backward bearer establishment, BS20/30,TrFO,TFO, …

• Load scenarios: low load, normal load, high load

• …

So it is clear that only the most important standard procedures and some basic network configurations will be considered in this chapter. Until now no customer demands ATM in core and it is furthermore less attractive with the introduction IP. So only TDM and IP are considered.

The delay in the core network mainly consists of the

- CS-Core NE MSC

and

- the signaling network.

CS-Core NE MSC:

The processing delay within the MSC mainly results from the internal communication between the different processors – CP113, GP, MP:SLT. Thereby the contribution of the central processor CP113 can be neglected.

Core Signaling Network:

The delay caused by message transfer within the Core Network (MAP, INAP/CAMEL) cannot be neglected.


A30862-X1001-C962-2-76-A1 109

• The processing time in a HLR (classic, “I” or “d”) for a standard MAP dialog is in the same range as the overall delay due to the message transport in a SS7 network (NB, HSL including transfer over some relay points). The same is valid in case of SCP (INAP/CAMEL).

• Although the parameters are sometimes customer specific - it’s simply not possible to analyze the consequences of different network topologies (e.g., SS7). General statements will be related to a typical ‘well configured’ network, e.g., SS7 overlay network with optimal MSC-HLR connection, transit layer for call routing.

Hint:

The network operator defines which destination is to be reached with which protocol. There is no effect from the signalling user on the choice of the transmission type.In principle TDM, ATM and IP are possible types of signalling backbone networks.

Delay times measured in an EtE environment have the advantage for the customer , that he can compare the KPI values with benchmark values of other customers. First values of the call setup times(core part) are available inside the EtE-KPI documents:

2G:

GSM/EDGE End-to-End Key Performance Indicators in Offer Process and Field Acceptance Test (BR7, BR8, BR9)

V 2.0 (Reviewed and updated version)

July 2005

3G :

UMTS End-to-End Key Performance Indicators for Offer Process and Field Acceptance Tests (UMR4.0/UCR4.0)

A50016-G5000-F534-2-7618

Furthermore the message flows of different call types (MOC, MTC, MMC) are available in this documents.

The values presented there are used as a starting point to calculate with an analytical approach the call setup/delay times inside the following basic network configurations.

4.1 Scope of Calculations

The delay calculations will be done for the following topics as far as basic values available ( not available values are denoted as n.a. inside the following tables) :


110 A30862-X1001-C962-2-76-A1

• call setup (MOC, MTC, MMC)

• SMS (MO, MT)

• MSC-Handover

• LUP

• HLR procedures

• Important MSC procedures

• SCP(MSC)

4.2 Generic Assumptions

All delay calculations will be done under normal load conditions by using the recommended network configuration and parameterization as mentioned before (see: chapter 3). So all the delay calculations will be done under the following conditions:

• GSM case 100k subscriber with SAG standard traffic model with 0.5 BHCA and 12 mErl (see Performance Requirement Spec. for CS 4.0 and CS 5.0)

• UMTS case 100k subscriber with SAG standard traffic model with 0.5 BHCA and 14 mErl (see Performance Requirement Spec. for CS 4.0 and CS 5.0)

• MSC/MSC-S and GMSC with CP Load A according to [3GPP43005]

• CPU load on the network elements and the network element managers < 67%

• No hardware saturation in MPs, LTGs, LICs, TSCs, …

• Load on traffic links < 75%

• Load on signalling links < 0.2 Erlang

• Subscriber state IMSI attached (only for combined LUP also GPRS attached)

• No call forwarding (conditional and unconditional)

• No MNP

• No IN/CAMEL service unless otherwise noted

• No IMEI check unless otherwise noted

• No Authentication procedure unless otherwise noted

• No CCBS

• No Gs interworking

• Off-Air Call Setup (OACSU) disabled in the MSC

• No subscriber-dependent digit processing and feature control in MSC (SDDPFC)


A30862-X1001-C962-2-76-A1 111

4.3 Optional Configuration Variants

These assumptions are essential with respect to the delay results inside the basic configurations and are taken into account during the following calculations.(If these assumptions are not suitable for the considered network the delay values must be recalculated) :

Assumptions for delay considerations

MCP with the introduction of MCP in CS5.0 the call set-up delay caused by the internal MSC processing will be reduced by about 40%. [PERF_DES_CS50]

Message channel(128 kbit/s) this improvement in CS5.0 will result in an delay reduction of ~25 % .

SCP –delay TDM case : 150 ms (= SCP delay + #7 link delay) ;

IP case : 100 ms (only SCP delay)

STP – delay UL 16 ms, DL 16 ms

#7 loop additional delay caused by #7 loop : ~ 300 ms (no load)

TMSC relay of IAM message : 300 ms,

relay of ANM,ACM, COT : 60 ms per message

CMN same assumption as for TMSC

Mc-IF one pair of (Req+Resp)-H.248- messages :

50 ms ( link-delay+MGW-delay, no load) + 25 ms (MSC-delay , no load)

NSL 20% link load, 64 kbit/s


112 A30862-X1001-C962-2-76-A1

4.4 Basic Configurations The different configurations which are used for delay calculations are presented in the following subchapters.

Note: this are only basic scenarios for calculating delay and setup times and their values may change with more complex network topologies.

4.4.1 MSC - Roles In the different network configurations (R99 integrated architecture and R4 separated architecture) the MSC can play different roles:

• First the visited MSC (VMSC) functionality, which manages the interworking with and connection to the radio network for the mobile originating and mobile terminating call scenario.

• As second, the simple transit case, which is identical to the same case in a fixed network call and is handled by the transit MSC (TMSC) functionality.

• Finally, the interworking with and connection to other networks is performed by the gateway MSC (GMSC).

Additionally in CS5.0 separated architecture (R4) the following entities are new:

• The MSC Server (MSCS) is handling exclusively signalling in separated architecture. It is controlling one or more external MGWs and has no internal MGW. Its function is comparable with the server part of the MSC and both entities may be combined within a combined MSC.

• The external Media Gateway (MGW, ATCA-MGW) is handling exclusively transport (IP, ATM, TDM) and transport signalling (AAL2 control plane, IPBCP). It is controlled by one MSCS or Combined MSC at a time via Mc-IF. Its function is comparable to the MGW part of the integrated MSC.

• The interworking with and connection to other networks is performed by the gateway MSC (GMSC).

• The Call Mediation Node (CMN) is handling exclusively signalling and is not controlling any MGW. Since its function is comparable to the MSCS and both may be combined within one entity,

This different MSC roles are relevant for the different scenarios mentioned in the following chapters.

4.4.2 Modifications of the basic Scenarios

In great networks additional NE are located due to several reasons,e.g. simplification of the network structure, support of lower administration effort and better use of ressources.

Therefore also the following modification are considered in some cases:


A30862-X1001-C962-2-76-A1 113

STP : the HLR is connected via STP ;

the MGW is connected via STP(Mc-IF with STP) to the MSC

TMSC: MSC A and MSC B are connected via one or two TMSCs CMN : Interworking between MSC-S A and MSC-S B is done via CMN (relay

of BICC messages based on routing information)

This is a late feature of CS5.0

4.5 CS4.0 – Transaction Delay in TDM based Core Network

Scenarios for Delay-Calculations:


114 A30862-X1001-C962-2-76-A1

Results:

Scope Measurement Type Value

MSC A -> PSTN A

MOC /2G

Comments: Scenario (1); Def.: A mobile user initiates a voice call to a landline telephone (mobile originated call).The Call Setup Time is defined as the time between the SCCP CR: CM Service request message and the reception of DT1(DTAP: ALERT) message.

Authentication time not taken into account.

Preconditions: It is recommended not to route the MOC to a fixed subscriber within the real national PSTN but instead to address a fixed subscriber line within the domain of the PLMN. Otherwise the PSTN reaction time can hardly be controlled during the field acceptance test; During the call setup no HLR inter-working is performed in the core network; MSC/VLR one NE;

1.23 s

MSC A -> PSTN A prepaid MOC

MOC /2G Comments: Scenario (1); MSC/VLR/SSP one NE; Assumptions: SCP-delay = 150 ms; Signalling Link: NB with UR=20%;

1.43 s

MSC A -> MSC B using TDM -> PSTN B

MOC /2G Comments: Scenario (2) ; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

1.71 s

MSC A -> PSTN A

MOC /3G

Comments: Scenario (1); Authentication time not taken into account; Def.: A mobile user initiates a voice call (AMR12.2) to a landline telephone (mobile originated call). The call setup time is the interval between the reception of the RANAP INITIAL UE MESSAGE(L3 Service Request) message and the submission of the RANAP DIRECT TRANSFER(L3 ALERT) message. Preconditions: Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message; During the call setup no HLR inter-working is performed in the core network;

1.89 s


A30862-X1001-C962-2-76-A1 115

Scope Measurement Type ValuePerform a voice call setup to a PSTN within same country; MSC A -> PSTN A prepaid MOC

MOC /3G Comments: Scenario (1); MSC/VLR/SSP one NE; Assumptions: SCP-delay = 150 ms; Signalling Link: NB with UR=20%;

2.08 s


MOC /3G Comments: Scenario (2) ; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.44 s

PSTN A -> MSC A

MTC /2G

Comments: Scenario (1); MSC/VLR/GMSC one NE; Authentication time not taken into account;

Def.: A landline user initiates a voice call to a mobile user (MTC - Mobile Terminated Call). The call setup time is the interval between the reception of a ISUP:INITIAL ADDRESS MESSAGE(MSISDN) message ( “a”) and the submission of the message ISUP ADDRESS COMPLETE (“k”). Preconditions: Perform a voice call setup to a PSTN within same country; It is assumed that during the call setup no additional HLR inter-working apart from normal interrogation is performed (MAP SEND ROUTING INFORMATION procedure; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message;

1.33 s

PSTN B -> MSC B -> MSC A using TDM MTC /2G Comments: Scenario (2) ; MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

1.81 s

PSTN A -> MSC A MTC /3G Comments: Scenario (1); MSC/VLR/GMSC one NE

Def.: A landline user initiates a voice call (AMR12.2) to a mobile user (MTC - Mobile Terminated Call). The call setup time is the interval between the reception of a ISUP INITIAL ADDRESS MESSAGE message and the submission of the RANAP DIRECT TRANSFER(L3 CONNECT) message. Preconditions: It is assumed that during the call setup no additional HLR inter-working apart from normal interrogation is performed; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Perform a voice call setup to a PLMN within same country;

2.39 s

PSTN B -> MSC B -> MSC A using TDM MTC /3G Comments: Scenario (2) ; MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.94 s

MSC A -> MSC A

MMC /2G

Comments: Scenario (1); MIC-case; Authentication time not taken into account; Def.: A mobile user initiates a voice call to another mobile user of the same

2.00 s


116 A30862-X1001-C962-2-76-A1

Scope Measurement Type ValuePLMN (MMC - Mobile-Mobile Call). The call setup time is the interval between the reception of the message SCCP(BSSMAP:Complete L3 Info(CM Service request)) and the submission of the message DT1(DTAP:Alert). Preconditions: Perform a voice call setup to an MS roaming within the same MSC area; It is assumed that during the call setup no additional HLR interworking apart from normal interrogation is performed (MAP: SEND ROUTING INFORMATION procedure; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message; MSC A -> MSC B using TDM

MMC /2G

Comments: Scenario (2); MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.47 s

MSC A -> MSC A

MMC /3G

Comments: Scenario (1) ; MIC-case; Authentication time not taken into account;

Def.: A mobile user initiates a voice call (AMR12.2) to another mobile user (MMC - Mobile Mobile Call). The call setup time is the interval between the reception of a RANAP INITIAL UE MESSAGE (L3 Service Request) message and the submission of the message RANAP DIRECT TRANSFER(L3 Alert). Preconditions: It is assumed that both mobile users are attached to the same MSC; It is also assumed that during the call setup no additional HLR inter-working is performed.; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC;

2.98 s

MSC A -> MSC B using TDM

MMC /3G Comments: Scenario (2); MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

3.54 s

SMS-MO

SMS /2G

Comments: MSC=SMS-GMSC; SM-SC is testequipment; => messages between MSC and SMS_GMSC don’t occur => no delay of SM-MSC Def.: Begin of measurement with reception of SCCP: CR (BSSMAP: Complete L3 Info (CM: SERVICE REQUEST)) message; end of measurement with submission of DT1 (CP-DATA(RP-DATA-ACK(SMS-Submit- Report))) message.

0.54 s

SMS-MT

SMS /2G

Comments: MSC=SMS-GMSC=HLR; SM-SC is testequipment => messages between MSC and SMS-GMSC don’t occur => no delay of SM-MSC => no messages to HLR Def.: Begin of measurement with SM-SC----> MSC: BEG (Send Routing Info for SM); End of measurement with submission of FORWARD_SM_END message.

1.05 s

SMS-MO SMS /3G n.a.

SMS-MT SMS /3G n.a.

TDM: Intra MSC Intra System Handover GSM MSC-HO Comments: 0.81 s


A30862-X1001-C962-2-76-A1 117

Scope Measurement Type ValueDef.: Begin of measurement with reception of DT1 (BSSMAP: HO Required) message; End of measurement with submission of DT1(BSSMAP: Clear Command (Handover Successful)) message.

MSC-HO TDM: Inter MSC Intra System Handover GSM n.a. MSC-HO TDM: Inter MSC Intra System Handover UMTS n.a MSC-HO TDM: Inter MSC Inter System Handover GSM -> UMTS n.a. MSC-HO TDM: Inter MSC Inter System Handover UMTS -> GSM n.a. MSC-HO TDM: Intra MSC Inter System Handover GSM -> UMTS n.a. MSC-HO TDM: Intra MSC Inter System Handover UMTS -> GSM n.a.

Inter MSC LUP

LUP /2G

Comments: Def.: A mobile user switches its mobile station on and attaches for the CS domain services. The procedure is the Location Update (IMSI Attach) according to [3GPP24.008]. The CS Location Update Time is the interval between the reception of the SCCP: CR (BSSMAP: COMPLETE L3 INFO(LOCATION UPDATE REQUEST)) message and the submission of the DT1(DTAP: LOCATION UPDATE ACCEPT) message. Precondition: IMSI att. in old MSC, old LAI stored on SIM, idle mode

0.94 s

3G: LUP(IMSI-Attach) / Intra MSC LUP

LUP /3G

Comments: Def.: A mobile user switches its mobile station on and attaches for the CS domain services. The procedure is the Location Update with IMSI attach according to [3GPP 24.008] and [3GPP23012]. The CS Location Update Time is the interval between the reception of the RANAP INITIAL UE MESSAGE(L3 LOCATION UPDATE REQUEST) message and the submission of the RANAP Iu RELEASE COMMAND message. Precondition: It is assumed that an Intra-MSC Location Update procedure is performed from a UE to an MSC/VLR that has already stored the associated subscriber record in the VLR (no change of MSC area since the last detach).

0.48 s

Interrogation Procedure (SRI)

MSC proc. Comments: Start Message: SEND_ROUTING_INFO; End Message: SEND_ROUTING_INFO_ACK; Note : value from MTC/2G

0.21 s

Send Identification Procedure (LUP)

MSC proc. Comments: Start Message: SEND_IDENTIFICATION; End Message: SEND_INDENTIFICATION_ACK; Note: value from LUP/2G

0.10 s

Send Authentication Procedure (AUTH)

MSC proc. Comments: Start Message: SEND_AUTHENTICATION_INFO; End Message: SEND_AUTHENTICATION_INFO_ACK; (MAP-Authentication)

34 ms

SCP Dialogue for PPS SCP(MSC) Comments: Start Message: INITIAL_DP ( MSC A(SSP) to SCP); End Message: REQUEST_REPORT_BCSM_EVENT (SCP to MSC A(SSP));

0.31 s


118 A30862-X1001-C962-2-76-A1

4.6 CS5.0 – Transaction Delay in R99 architecture

CS5.0 scenarios /classical architecture :


A30862-X1001-C962-2-76-A1 119

Results:


MSC A -> PSTN A

MOC/2G

Scenario (3) Def.: A mobile user initiates a voice call to a landline telephone (mobile originated call).The Call Setup Time is defined as the time between the SCCP CR: CM Service request message and the reception of DT1(DTAP: ALERT) message.



0.88 s


MOC/2G Scenario (3) MSC/VLR/SSP one NE; Assumptions: SCP-delay = 150 ms; Signalling Link: NB with UR=20%;

1.07 s


MOC/2G Scenario (4) MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

1.35 s

MSC A -> PSTN A

MOC/3G

Scenario (3) Authentication time not taken into account; Def.: A mobile user initiates a voice call (AMR12.2) to a landline telephone (mobile originated call). The call setup time is the interval between the reception of the RANAP INITIAL UE MESSAGE(L3 Service Request) message and the submission of the RANAP DIRECT TRANSFER(L3 ALERT) message. Preconditions: Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message; During the call setup no HLR inter-working is performed in the core network; Perform a voice call setup to a PSTN within same country;

1.57 s


MOC/3G Scenario (3) MSC/VLR/SSP one NE; Assumptions: SCP-delay = 150 ms; Signalling Link: NB with UR=20%;

1.77 s


MOC/3G Scenario (4) MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.17 s

PSTN A -> MSC A

MTC/2G

Scenario (3) MSC/VLR/GMSC one NE; Authentication time not taken into account;


1.20 s

MTC/2G PSTN B -> MSC B -> MSC A using TDM 1.67 s


120 A30862-X1001-C962-2-76-A1

Scope Measurement Type ValueScenario (4) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ; PSTN A -> MSC A MTC/3G Scenario (3) MSC/VLR/GMSC one NE

Def.: A landline user initiates a voice call (AMR12.2) to a mobile user (MTC - Mobile Terminated Call). The call setup time is the interval between the reception of a ISUP INITIAL ADDRESS MESSAGE message and the submission of the RANAP DIRECT TRANSFER(L3 CONNECT) message. Preconditions: It is assumed that during the call setup no additional HLR inter-working apart from normal interrogation is performed; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Perform a voice call setup to a PLMN within same country;

1.44 s

PSTN B -> MSC B -> MSC A using TDM MTC/3G Scenario (4) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.00 s

MSC A -> MSC A

MMC/2G

Scenario (3) MIC-case; Authentication time not taken into account; Def.: A mobile user initiates a voice call to another mobile user of the same PLMN (MMC - Mobile-Mobile Call). The call setup time is the interval between the reception of the message SCCP(BSSMAP:Complete L3 Info(CM Service request)) and the submission of the message DT1(DTAP:Alert). Preconditions: Perform a voice call setup to an MS roaming within the same MSC area; It is assumed that during the call setup no additional HLR interworking apart from normal interrogation is performed (MAP: SEND ROUTING INFORMATION procedure; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message;

1.69 s

MSC A -> MSC B using TDM

MMC/2G Scenario (4) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.17 s

MSC A -> MSC A

MMC/3G

Scenario (3) MIC-case; Authentication time not taken into account;


2.86 s

MSC A -> MSC B using TDM MMC/3G Scenario (4) 3.41 s


A30862-X1001-C962-2-76-A1 121

Scope Measurement Type ValueMSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

SMS-MO

SMS /2G

Comments: MSC=SMS-GMSC; SM-SC is testequipment; => messages between MSC and SMS_GMSC don’t occur => no delay of SM-MSC Def.: Begin of measurement with reception of SCCP: CR (BSSMAP: Complete L3 Info (CM: SERVICE REQUEST)) message; end of measurement with submission of DT1 (CP-DATA(RP-DATA-ACK(SMS-Submit- Report))) message.

0.54 s

SMS-MT

SMS /2G

Comments: MSC=SMS-GMSC=HLR; SM-SC is testequipment => messages between MSC and SMS-GMSC don’t occur => no delay of SM-MSC => no messages to HLR Def.: Begin of measurement with SM-SC----> MSC: BEG (Send Routing Info for SM); End of measurement with submission of FORWARD_SM_END message.

1.05 s

SMS-MO SMS /3G n.a.

SMS-MT SMS /3G n.a.

TDM: Intra MSC Intra System Handover GSM

MSC-HO /2G

Comments: Def.: Begin of measurement with reception of DT1 (BSSMAP: HO Required) message; End of measurement with submission of DT1(BSSMAP: Clear Command (Handover Successful)) message.

0.81 s

MSC-HO /2G TDM: Inter MSC Intra System Handover GSM n.a.

MSC-HO /3G TDM: Inter MSC Intra System Handover UMTS n.a.

MSC-HO /2G3G TDM: Inter MSC Inter System Handover GSM -> UMTS n.a.

MSC-HO /2G3G TDM: Inter MSC Inter System Handover UMTS -> GSM n.a.

MSC-HO /2G3G TDM: Intra MSC Inter System Handover GSM -> UMTS n.a.

MSC-HO /2G3G TDM: Intra MSC Inter System Handover UMTS -> GSM n.a.

Inter MSC LUP

LUP /2G

Comments: Def.: A mobile user switches its mobile station on and attaches for the CS domain services. The procedure is the Location Update (IMSI Attach) according to [3GPP24.008]. The CS Location Update Time is the interval between the reception of the SCCP: CR (BSSMAP: COMPLETE L3 INFO(LOCATION UPDATE REQUEST)) message and the submission of the DT1(DTAP: LOCATION UPDATE ACCEPT) message. Precondition: IMSI att. in old MSC, old LAI stored on SIM, idle mode

0.94 s

LUP(IMSI-Attach) / Intra MSC LUP

LUP /3G

Comments: Def.: A mobile user switches its mobile station on and attaches for the CS domain services. The procedure is the Location Update with IMSI attach according to [3GPP 24.008] and [3GPP23012]. The CS Location Update Time is the interval between the reception of the RANAP INITIAL UE MESSAGE(L3 LOCATION UPDATE REQUEST) message and the submission of the RANAP Iu RELEASE COMMAND message.

0.48 s


122 A30862-X1001-C962-2-76-A1

Scope Measurement Type ValuePrecondition: It is assumed that an Intra-MSC Location Update procedure is performed from a UE to an MSC/VLR that has already stored the associated subscriber record in the VLR (no change of MSC area since the last detach).

Interrogation Procedure (SRI)

MSC proc. Comments: Start Message: SEND_ROUTING_INFO; End Message: SEND_ROUTING_INFO_ACK; Note : value from MTC/2G

0.21 s

Send Identification Procedure (LUP)

MSC proc. Comments: Start Message: SEND_IDENTIFICATION; End Message: SEND_INDENTIFICATION_ACK; Note: value from LUP/2G

0.10 s

Send Authentication Procedure (AUTH)

MSC proc.

Comments: Start Message: SEND_AUTHENTICATION_INFO; End Message: SEND_AUTHENTICATION_INFO_ACK; (MAP-Authentication)

34 ms

SCP Dialogue for PPS SCP(MSC) Comments: Start Message: INITIAL_DP ( MSC A(SSP) to SCP); End Message: REQUEST_REPORT_BCSM_EVENT (SCP to MSC A(SSP));

0.31 s


A30862-X1001-C962-2-76-A1 123

4.7 CS5.0 – Transaction Delay in R4 architecture

CS5.0 scenarios /separated architecture


124 A30862-X1001-C962-2-76-A1


A30862-X1001-C962-2-76-A1 125

Results:


MGW A -> PSTN A

MOC /2G

Comments: Scenario (5) Def.: A mobile user initiates a voice call to a landline telephone (mobile originated call).The Call Setup Time is defined as the time between the SCCP CR: CM Service request message and the reception of DT1(DTAP: ALERT) message.



1.17 s

MGW A -> PSTN A

MOC /2G Comments: Scenario (5a) MSC with MCP

0.82 s

MGW A -> PSTN A MOC /2G Scenario (5)

Mc-IF via STP 1.23 s

MGW A -> MGW B using TDM -> PSTN B MOC /2G Scenario (6)

#7-Loop => 510 ms delay 2.22 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MOC /2G Scenario (6)



MSC/STP=MSC A; MSC B = TMSC; 2.19 s

MGW A -> MGW B using TDM -> PSTN B MOC /2G Scenario (7a)

MSC with MCP 1.84 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MOC /2G Scenario (7) 3.01 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MOC /2G Scenario (7a)

MSC with MCP 2.66 s

MGW A -> PSTN A

MOC /3G

Scenario (5) Authentication time not taken into account; Def.: A mobile user initiates a voice call (AMR12.2) to a landline telephone (mobile originated call). The call setup time is the interval between the reception of the RANAP INITIAL UE MESSAGE(L3 Service Request) message and the submission of the RANAP DIRECT TRANSFER(L3 ALERT) message. Preconditions: Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message; During the call setup no HLR inter-working is performed in the core network; Perform a voice call setup to a PSTN within same country;

1.71 s

MGW A -> PSTN A MOC /3G Scenario (5a)

MSC with MCP 1.07 s





MGW A -> MGW B using TDM -> PSTN B MOC /3G Scenario (7) 2.81 s


126 A30862-X1001-C962-2-76-A1

Scope Measurement Type ValueMSC/STP=MSC A; MSC B = TMSC; MGW A -> MGW B using TDM -> PSTN B

MOC /3G Scenario (7a) MSC with MCP

2.17 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MOC /3G Scenario (7) 3.56 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MOC /3G Scenario (7a)

MSCs with MCP 2.92 s


additional: CMN between the two MSC-Ss 4.04 s

PSTN A -> MGW A

MTC /2G

Scenario (5) MSC/VLR/GMSC one NE; Authentication time not taken into account;


1.41 s

PSTN A -> MGW A MTC /2G Scenario (5a)

MSC with MCP 0.93 s

MGW A -> MGW B using TDM -> PSTN B MTC /2G Scenario (6)


MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MTC /2G Scenario (6)


MGW A -> MGW B using TDM -> PSTN B

MTC /2G Scenario (7) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.43 s

MGW A -> MGW B using TDM -> PSTN B MTC /2G Scenario (7a)

MSC with MCP 1.95 s


3.78 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MTC /2G Scenario (7a)

MSC with MCP 3.31 s

PSTN A -> MGW A

MTC /3G

Scenario (5) MSC/VLR/GMSC one NE

Def.: A landline user initiates a voice call (AMR12.2) to a mobile user (MTC - Mobile Terminated Call). The call setup time is the interval between the reception of a ISUP INITIAL ADDRESS MESSAGE message and the submission of the RANAP DIRECT TRANSFER(L3 CONNECT) message. Preconditions: It is assumed that during the call setup no additional HLR inter-working apart from normal interrogation is performed;

1.59 s


A30862-X1001-C962-2-76-A1 127

Scope Measurement Type ValueThe PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Perform a voice call setup to a PLMN within same country; PSTN A -> MGW A

MTC /3G Scenario (5a) MSC with MCP

1.01 s





MGW A -> MGW B using TDM -> PSTN B

MTC /3G Scenario (7) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.69 s


additional: 1 TMSC between A and B side 3.25 s


additional: 2 TMSCs between A and B side 3.80 s


additional: 1 STP between A and B side 2.77 s


additional: 2 STP between A and B side 2.85 s

MGW A -> MGW B using TDM -> PSTN B MTC /3G Scenario (7a)

MSC with MCP 2.11 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MTC /3G 2 server, 2 MGWs (Scenario 7) 3.97 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MTC /3G Scenario (7a)

MSC with MCP 3.39 s

MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment MTC /3G Scenario (7) additional: CMN between the two MSCSs

4.45 s

MGW A -> MGW A

MMC /2G

Scenario (5) MIC-case; Authentication time not taken into account; Def.: A mobile user initiates a voice call to another mobile user of the same PLMN (MMC - Mobile-Mobile Call). The call setup time is the interval between the reception of the message SCCP(BSSMAP:Complete L3 Info(CM Service request)) and the submission ofthe message DT1(DTAP:Alert). Preconditions: Perform a voice call setup to an MS roaming within the same MSC area; It is assumed that during the call setup no additional HLR interworking apart from normal interrogation is performed (MAP: SEND ROUTING INFORMATION procedure; The PAGING procedure as initiated by the core network is assumed to be successful with the first paging request sent by the MSC; Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message;

2.29 s

MGW A -> MGW A MMC /2G Scenario (5a)

MSC with MCP 1.61 s

MGW A -> MGW B using TDM

MMC /2G Scenario (7) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

2.76 s

MMC /2G MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment 4.15 s


128 A30862-X1001-C962-2-76-A1

Scope Measurement Type ValueScenario (7) MGW A -> MGW A

MMC /3G

Scenario (5) MIC-case; Authentication time not taken into account;


3.16 s

MGW A -> MGW A MMC /3G Scenario (5a)

MSC with MCP 2.02 s

MGW A -> MGW B using TDM

MMC /3G 2 server , 2 MGWs (Scenario 7) MSC/VLR/GMSC one NE; MSC B acting as a TMSC; Assumptions: Signalling Link: NB with UR=20% ;

3.74 s

MGW A -> MGW B using TDM MMC /3G Scenario (7)

additional: 1 TMSC between A and B side 4.31 s

MGW A -> MGW B using TDM MMC /3G Scenario (7)

additional: 2 TMSCs between A and B side 4.87 s

MGW A -> MGW B using IP(GE) using Fast Forward Bearer Establishment MMC /3G Scenario (7)

5.03 s

MGW A -> MGW B using IP(GE) using Fast Forward Bearer Establishment MMC /3G Scenario (7)

additional: CMN between the two MSCSs 5.51 s

Intra MGW HO HO Scenario (5) n.a.

Inter_MGW_Intra_MSC-S HO Scenario (6)

Nb over TDM ; n.a.

Inter_MGW_Intra_MSC-S HO Scenario (6)

Nb over IP ; n.a.

Basic_Inter_MSC-S_HO HO Scenario (7)

Nb over TDM ; n.a.

Basic_Inter_MSC-S_HO HO Scenario (7)

Nb over IP ; n.a.

Remark:

Due to comparison with Nb over TDM it is assumed for the IP case that the call setup procedure is performed in a simple way, i.e. without codec negotiation for example.


A30862-X1001-C962-2-76-A1 129

Abbreviations ACK Acknowledge AFI Available for First Inspection APN Access Point Name BSS Base Station System BSSGP Base Station System GPRS Protocol CMN Call Mediation Node CN Core Network CPU Central Processing Unit CS Circuit Switched DL Downlink GGSN Gateway GPRS Support Node GMSC Gateway Mobile Service Switching Center GPRS General Packet Radio Service GR GPRS Release GSM Global system for mobile communication GTP-U GTP User Plane HLR Home Location Register IMEI International Mobile Equipment Identity IMSI International Mobile Subscriber Identity IP Internet Protocol IPS Intelligent Packet Solution ITU International Telecommunication Union ITU-T Telecommunications Standardization Section of ITU IUS Inspected Updated and Stored IWMSC Interworking MSC KPI Key Performance Indicator LA Location Area LLC Logical Link Control MM Mobility Management MP Main Processor MS Mobile Station MSC Mobile-services Switching Center NSL Narrowband Signalling Link PDP Packet Data Protocol PDU Packet Data Unit PM Performance Management PMM Packet Mobility Management PO Packet Oriented PS Packet Switched RA Routing Area RAB Radio Access Bearer RAN Radio Access Network RANAP RAN Application Part RAU Routing Area Update RNC Radio Network Controller RNS Radio Network Subsystem RRC Radio Resource Control SGSN Serving GPRS Support Node SIM GSM Subscriber Identity Module SMS Short Message Service SP Service Processor SRNS Serving Radio Network System


130 A30862-X1001-C962-2-76-A1

SSG Service Selection Gateway TC Traffic Class UCR UMTS Core Release UE User Equipment UL Uplink UMTS Universal Mobile Telecommunication System USIM Universal Subscriber Identity Module UTRAN UMTS Terrestrial Radio Access Network VLR Visitor Location Register

cs core kpis for offer and field acceptance test

Documents

core network

core kpi overview

field acceptance tests

offer process

ius version chapter

definition of kpi

grade of service measurements

measured kpi values