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
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.
Copyright (C) Siemens AG 2006

Issued by the Communications Mobile Networks Group
St.-Martin-Strae 76
D-81541 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.
Measurements in Offer Process and Field Acceptance

Tests
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
Scholle, Thomas
Department
SN MN PG NT NE 4
Jens Schneider
SN MN PG NT NE 2
A30862-X1001-C962-2-76-A1

Tests
Table of Contents
Introduction......................................................................................................8
2
2.1
2.2
2.2.1
2.2.2
2.3
Core Network ................................................................................................10

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

Tests
3.2.6.6
3.2.6.7
3.2.6.8
3.2.7
3.2.7.1
3.2.7.2
3.2.7.3
3.2.7.4
3.2.7.5
3.2.7.6
3.2.7.7
3.2.8
3.2.9
3.2.10
3.2.11
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.4.8
Inter- MSCB- Handover Success Ratio ........................................................69

Inter MSC SRNS Relocation Failure Ratio ...................................................70
Handover - Message Flows/Triggerpoints ....................................................71
SMS Analysis ................................................................................................77
SMS Failure Ratio .........................................................................................77
SMS-MT Failure Ratio...................................................................................79
SMS-MT Delivery Failed Ratio......................................................................80
SMS-MT No Facility Ratio.............................................................................81
SMS- MO Failure Ratio .................................................................................82
Mobile Originating SMS Failure Ratio (IuCS interface) ................................83
SMS-MO Delivery failed Ratio ......................................................................84
IN/CAMEL Dialog Failure Ratio.....................................................................85
IN request Failure Ratio ................................................................................86
Supplementary Services Request Failure Ratio ...........................................88
Inter MGW HO Failure Ratio (MSC-S only) ..................................................91
HLR/AC related KPIs ...................................................................................92
MAP Dialog MSRN Provisioning Success Ratio........................................92
Cancel Location Failure Ratio .......................................................................92
MAP Dialog Interrogation Success Ratio...................................................94
IMEI Check Break down................................................................................95
Authentication Vector Request Success Ratio .............................................96
Authentication Failure Ratio (Network authenticates USIM).........................98
Authentication Failure Ratio (Network authenticates SIM) ...........................99
MGW-KPIs ..................................................................................................100
Transcoding Failure Ratio ...........................................................................100
Data Call Failure Ratio ................................................................................100
Data Call Failure Ratio (per call type) .........................................................101
Inserted Announcement Failure Ratio ........................................................102
Inserted Tone Failure Ratio.........................................................................103
Conference Call Establishment Failure Ratio .............................................104
Receiving IP Bearer Negotiation Failure Ratio ...........................................104
Initiating IP Bearer Negotiation Failure Ratio..............................................105
4
4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.5
4.6
4.7
Core-Part of Transaction Delay...................................................................108

Scope of Calculations .................................................................................109
Generic Assumptions ..................................................................................110
Optional Configuration Variants ..................................................................111
Basic Configurations ...................................................................................112
MSC - Roles ................................................................................................112
Modifications of the basic Scenarios...........................................................112
CS4.0 Transaction Delay in TDM based Core Network ..........................113
CS5.0 Transaction Delay in R99 architecture..........................................118
CS5.0 Transaction Delay in R4 architecture............................................123
Abbreviations ..............................................................................................................129
A30862-X1001-C962-2-76-A1

Tests
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

Tests
[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]
Standards:
[ITU E500]
Circuit Switched Core Network Architecture (CS-CNA) CS4.0

Description
P30309-A3357-A054-04-7618
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
A30862-X1001-C962-2-76-A1

Tests
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 doesnt 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

Tests
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.
A30862-X1001-C962-2-76-A1

Tests
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, MSCS 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.
10
A30862-X1001-C962-2-76-A1

Tests
CS5.0 MSC Server

CS4.0 MSC
CS4.0 Server
Part
(CP,LTG,MP)
int.
Mc
internal
MGW Part
(MP,A2BS,TSC)
CS5.0
Server
Part
Mc
CS5.0
ATCA
MGW
CS5.0 Combined MSC

CS5.0
Server
Part
int.
Mc
Mc
CS5.0
ATCA
MGW
internal
MGW Part
CS5.0 MSC
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 KPIs.
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)
A30862-X1001-C962-2-76-A1
11

Tests
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 MMLcommand (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 welldefined 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.
12
A30862-X1001-C962-2-76-A1

Tests
2.2.2
Grade of Service Measurements

As most of the following KPIs 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 KPIs. 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:
A30862-X1001-C962-2-76-A1
13

Tests
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).
14
A30862-X1001-C962-2-76-A1

Tests
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 endto-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].
A30862-X1001-C962-2-76-A1
15

Tests
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.
16
A30862-X1001-C962-2-76-A1

Tests
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:
KPI MSC
CS4.0
CS5.0
IMSI Attach Failure Ratio

Explicit IMSI Detach Success Ratio
System-KPI
Target Value
Core-part of
Network-KPI
(=> Note1)
0,1 %
0,1 %
0.1 %
0.1 %
99.8 %
99.8 %
99.8 %
99.9% (99.90)
99.9% (99.90)
99.9% (99.76)
99.9% (99.76)
Inter MSC Location Area Update Failure

Ratio
0.1%
0.1%
Intra MSC Periodic Location Update Failure

Ratio
0.1%
0.1%
Inter System Location Area Update Failure

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

Ratio (Intra MSC 2G-3G)
0.1%
0.1%
0.1%
0.1%
LUP Success Rate
RAB Assignment Setup Failure Ratio

MOC Answered Calls dropped call rate
Emergency call success ratio
99.8 %
0.5%
0.5%
0.5%
0.5%
99.8%
99.8%
99.8%
MOC Setup Ratio
99.5% (100.0)
99.5% (100.0)
(Modified formula due to Late Assignment)
99.5% (100.0)
99.5% (100.0)
A30862-X1001-C962-2-76-A1
99.8%
17

Tests
Mobile Originated Call Failure Ratio (All
Network)
MOC Traffic Channel Allocation Ratio
MOC-PSTN Success Rate
Data calls success Ratio (MOC-PSTN)

MMC Success Ratio
Data calls success Ratio (MMC)

MTC Traffic Channel Allocation Ratio
MTC Setup Ratio
MTC Success Rate
MTC Failure Ratio

Paging Procedure Failure Ratio
Data calls succes Ratio (MTC)
Handover Success Ratio
Intra-MSC-Handover Success Ratio
Intra MSC Inter System (3G-2G) HO Failure
Ratio
Inter MSC Inter System (3G-2G) HO Failure
Ratio
Inter-MSCA-Handover Success Ratio
Inter-MSCB-Handover Success Ratio
Inter MSC SRNS Relocation Failure Ratio
SMS Failure Ratio
SMS-MT Failure Ratio
SMS-MT Delivery Failed Ratio
SMS-MT No Facility Ratio
18
0.1%
99.5% (100.0)
99.5% (100.0)
0.1%
99.5% (100.0)
99.5% (100.0)
99.5% (99.99)
99.5% (99.99)
99.5% (99.99)
99.5% (99.99)
99.8%
99.8%
99.8%
99.5% (99.99)
99.5% (99.99)
99.8%
99.5% (99.99)
99.5% (99.99)
99.8%
99.8%
99.8%
99.8%
99.5%
99.5%
99.5%
99.5% (99.81)
99.5% (99.81)
99.5%
99.5% (99.81)
99.5% (99.81)
99.5% (99.98)
99.5% (99.98)
99.5% (99.98)
99.5% (99.98)
0.1% (0.04)
0.1% (0.04)
0.1% (0.02)
0.1% (0.02)
X
X
2.0 %
2.0 % (0.00)
2.0 %
2.0 % (0.00)
99.8%
99.8%
99.8%
99.8%
99.0% (99.98)
99.0% (99.98)
99.0% (99.84)
99.0% (99.84)
99.0% (99.98)
99.0% (99.98)
99.0% (99.83)
99.0% (99.83)
X
X
X
1.0 %
1.0 % (0.00)
1.0 %
1.0 %
1.0 % (0.00)
1.0 %
1.0 %
99.0% (100.0)
99.0% (100.0)
1.0 %
99.0% (99.97)
99.0% (99.97)
99.0% (99.95)
99.0% (99.95)
99.0% (99.71)
99.0% (99.71)
1.0%
X
X
X
X
X
1.0% (0.03)
0.5%
0.5% (0.02)
0.5%
0.5% (0.01)
1.0%
1.0% (0.03)
0.5%
0.5% (0.02)
0.5%
0.5% (0.01)
0.5%
0.5%
0.5%
0.5%
0.5%
0.5%
A30862-X1001-C962-2-76-A1

Tests
X
SMS-MO Failure Ratio
Mobile Originating SMS Failure Ratio (IuCS
interface)
SMS-MO Delivery failed Ratio
IN/CAMEL Dialog Failure Ratio
IN request Failure Ratio
Supplementary Services Request Failure
Ratio
Inter MGW HO Failure Ratio (MSC-S only)
0.5%
X
X
0.5%
0.5%
0.5% (0.02)
X
X
0.5%
0.5% (0.02)
0.5%
0.5%
0.5% (0.00)
0.5% (0.00)
0.5%
0.5%
0.5%
0.5%
X
X
0.3%
0.3%
0.3% (0.05)
0.3% (0.05)
0.3%
0.3%
0.3%
0.3%
0.2 %
0.2 %
0.2 %
0.2 %
0.5%
0.5%
Table 3-1: MSC/MSC-S KPIs for Offer
Additional KPIs measuring time values:
KPI MSC [time]

Mean Location Update Duration
CS4.0
CS5.0
Mean Call Setup Time
Mean Holding Time (answer)
Mean Holding Time (seizure)
Total Traffic per Customer (seizure)
Total Speech Traffic per Customer (answer)
Total Call Duration (seizure)
Total Call Duration (answer)
MOC-PSTN or other PLMN Average Speech Call Duration
MMC Average Speech Call Duration
MTC Average Speech Call Duration
Table 3-2: KPIs with Quantity of result Time
A30862-X1001-C962-2-76-A1
19

Tests
HLR/AC KPIs:
KPI HLR/AC
CS4.0
CS5.0
MAP Dialog MSRN Provisioning Success

Ratio (REC HLR)
Cancel Location Failure Ratio (REC HLR)
MAP Dialog Interrogation Success Ratio (REC
MSC)
IMEI Check Break down (REC MSC )
System-KPI
Target Value
Core-part of
Network-KPI
(=> Note1)
99.9%
99.9%
99.9% (99.34)
99.9% (99.34)
0.1 %
0.1 %
0.1 %
0.1 %
99.9%
99.9%
99.9% (99.46)
99.9% (99.46)
99.9%
99.9%
99.9%
99.9%
Authentication Vector Request Success Ratio

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

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

authenticates SIM) (REC VLR)
Table 3-3: HLR/AC related KPIs
Additional KPIs MSC:
KPI MSC
VLR Utilisation (Total subscribers in VLR)
20
CS4.0
CS5.0
Share of VLR Utilisation subscribers from other countries
Share of subscribers in VLR from home country but not in HPLMN
CS Network Congestion Ratio
Busy Hour Call Attempts (BHCA)
MOC per Subscriber for PSTN or other PLMN
Call Forwarding Ratio
MOC - PSTN Ratio
MMC to other MSC per Subscriber
MTC per Subscriber
MTC GSM Call Forwarding Ratio
Intra-MSC-Handover Attempt Ratio
Inter-MSCA-Handover Attempt Ratio
MSC Processor Load
Control Plane ATM PVC Utilisation
User Plane ATM PVC Utilisation
A30862-X1001-C962-2-76-A1

Tests
Signaling Interface Utilisation
Traffic Route Utilisation (non-Iu-CS / non Nb) Internal Routes
Mc-If Reliability Failure Ratio
Answer Seizure ratio
Answer Seizure Ratio per Trunk
External Congestion and Technical Irregularities Release Ratio
MOC-PSTN B-Busy Ratio
MMC B-Busy Ratio
MTC B-Busy Ratio
Inter-MSCB-Handover Attempt Ratio
SMS-MT Absent MS Ratio
SMS-MT MS Memory Full Ratio
MGW availability
Table 3-4: Additional MSC/MSC-S KPIs
MGW-KPIs :
KPI MGW
Transcoding Failure Ratio
Data Call Failure Ratio
Data Call Failure Ratio (per call type)
Inserted Announcement Failure Ratio
Inserted Tone Failure Ratio
Conference Call Establishment Failure Ratio
Receiving IP Bearer Negotiation Failure Ratio
Initiating IP Bearer Negotiation Failure Ratio
CS5.0
System-KPI
Target Value
Core-part of
Network-KPI
0.1%
0.1%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
X
X
X
0.1%
0.2%
0.2%
0.1%
0.2%
0.2%
0.1%
0.1%
0.1%
0.1%
CS4.0
(=> Note1)
Table 3-5: MGW-KPIs
A30862-X1001-C962-2-76-A1
21

Tests
Additional MGW-KPIs :
KPI MGW
CS4.0
CS5.0
ATM Level Volume (per MGW / per VC)
PVC Utilisation
AMR Usage
PDU Volume
IP Level Volume
MGW Processor Usage
MGW Memory Usage
Call Transcoding Ratio
AAL2 Level Error Ratio (per error type)
Receiving IP Bearer Negotiation Failure Ratio per error type
Initiating IP Bearer Negotiation Failure Ratio per error type
IP Bearer Negotiation Encoding/Decoding Failure Ratio
Table 3-6: Additional MGW-KPIs
3.2
3.2.1
3.2.1.1
KPIs for MSC

Mobility and Security
IMSI Attach Failure Ratio
Description:
This KPI indicates the failure ratio for IMSI attach procedure.
The indicator is expressed as the ones 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:
22
A30862-X1001-C962-2-76-A1

Tests
SUCC _ LOCUPD _ WITH _ IMSI _ ATTACH

100%
KPI = 1
REQUESTS _ LOCUPD _ WITH _ IMSI _ ATT
3G:
U _ SUCC _ LOCUPD _ WITH _ IMSI _ ATT

100%
KPI = 1
U _ REQUESTS _ LOCUPD _ WITH _ IMSI _ ATT
Message Flows/Triggerpoints :
3.2.1.2
Explicit IMSI Detach Success Ratio

Description:
This KPI reveals the success of the explicit IMSI detach procedure.
Per MSC / MSC-S
A30862-X1001-C962-2-76-A1
23

Tests
Equal to or greater than 99.8%
KPI-formula:
2G+3G:
KPI =
EXPLICIT_I MSI_DETACH
100%
RECEIVED_D ETACH_WITH _IMSI +
+ RECEIVED_D ETACH_WITH _TMSI
Message Flows/Triggerpoints:
MS/UE
IMSI_DETACH
BSC/RNC
MSC/VLR
CR(IMSI_DETACH_INDICATION)
CREF()
if IMSI within detach : + RECEIVED_DETACH_WITH_IMSI

if TMSI within detach : + RECEIVED_DETACH_WITH_TMSI
If successful detached : + EXPLICIT_IMSI_DETACH
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.
24
A30862-X1001-C962-2-76-A1

Tests
Per MSC
KPI-formula:
2G+3G:
KPI =
SUCC_REQUESTS_LOCUPD
100%
REQUESTS _ LOCUPD + SERVICE_REQ_COM_LUP
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 ones complement of the
A30862-X1001-C962-2-76-A1
25

Tests
number of successful Inter MSC Location Updates divided by the number of Inter
MSC Location Update attempts.
Per MSC/MSC-S
0.1%
KPI-formula:
2G+3G:

LOCUPD_LAI_NULL

VLR_CHANGES_PVLR_KNOWN

VLR_CHANGES_PVLR_UNKNOWN
KPI = 1
100%
HANDOVER_M
SC_MSC_OG_
ATTEMPTS
+ SUBSEQ_MSC_MSC_HO_MSCB
3G:
U _ SUCC _ INTER _ MSC _ LOCUPD

100%
KPI = 1
U _ REQUESTS _ INTER _ MSC _ LOCUPD
LOCUPD_LAI_NULL
Trigger: each time LOCATION UPDATE Trigger: each time LOCATION UPDATE
ACCEPT is sent to the BSS/RNC.
ACCEPT is received.
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
U_SUCC_INTER_MSC_LOCUPD
REQUESTS_LOCUPD_INTRA_VLR
Trigger: each time LOCATION UPDATE Transmission of Update Location
Accepted message from RNC
REQUEST for an intra VLR location is
received
U_REQUESTS_INTER_MSC_LOCUPD
Reception of a Location Update Request

message from RNC
26
A30862-X1001-C962-2-76-A1

Tests
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 ones complement of the number of successful
Periodic MSC Location Updates divided by the number of Periodic MSC Location
Update attempts.
Per 3G MSC/MSC-S

0.1%
KPI-formula:
2G+3G:
LOCUPD_LAI
_NULL
- VLR_CHANGES_PVLR_KNOWN
- VLR_CHANGES_PVLR_UNKNOWN
KPI =
100%
REQUESTS_LOCUPD_INTRA_VLR
3G:
U _ SUCC _ INTRA _ MSC _ PER _ LOCUPD

100%
KPI = 1
U
_
REQUESTS _ INTRA _ MSC _ PER _ LOCUPD
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.
A30862-X1001-C962-2-76-A1
27

Tests
3.2.1.6
Inter System Location Area Update Failure Ratio (Intra MSC 3G-2G)
Description:
This KPI indicates the failure ratio of Intersystem (3G2G) Location Area Updates
when one 3GMSC is involved.
Intersystem (3G2G) Location Area Updates divided by the number of Intersystem
(3G2G) Location Area Updates attempts.
3G MSC/MSC-S
0.1%
KPI-formula:
2G:
SUCC _ INTRA _ MSC _ 3G2G _ LOCUPD

100%
KPI = 1
REQUESTS _ INTRA _ MSC _ 3G2G _ LOCUPD
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
Location Update
Request
REQUESTS_INTRA_MSC_3G2G_LOCUPD /
Update Location
Accepted
SUCC_INTRA_MSC_3G2G_LOCUPD /
28
A30862-X1001-C962-2-76-A1

Tests
3.2.1.7
Inter System Location Area Update Failure Ratio (Intra MSC 2G-3G)
Description:
This KPI indicates the failure ratio of Intersystem (2G3G) Location Area Updates
when one 3G MSC is involved. The indicator is expressed as the ones complement of
the number of successful Intersystem (2G3G) Location Area Updates divided by the
number of Intersystem (2G3G) Location Area Updates attempts.
3G MSC/MSC-S
0.1%
KPI-formula:
SUCC _ INTRA _ MSC _ 2G3G _ LOCUPD

100%
KPI = 1
REQUESTS
_ INTRA _ MSC _ 2G3G _ LOCUPD
Transmission of Update Location Accepted message from RNC
Reception of a Location Update Request message from RNC
Messsage flow: see chapter before
3.2.2
3.2.2.1
General Call Analysis

RAB Assignment Setup Failure Ratio
Description:
This KPI indicates the failure ratio of RAB assignment setup.
completed RAB Assignment setups divided by the total number of RAB assignment
setup attempts.
Per MSC/MSC-S
A30862-X1001-C962-2-76-A1
29

Tests
KPI-formula:
2G+3G: per MSC:
MTER:
CALL _ TCH _ ALLOCATION ( MTER)

100%
KPI = 1
GEN _ TRAFFIC _ CHAN _ REQ( MTER)
MOC:
CALL _ TCH _ ALLOCATION ( MORTR)

100%
KPI = 1
GEN _ TRAFFIC _ CHAN _ REQ( MORTR)
Removing RNC causes:
MTER:
CALL _ TCH _ ALLOCATION ( MTER)

KPI = 1
100%
GEN _ TRAFFIC _ CHAN _ REQ( MTER)
+ UNS_BS_REASON(MTER)

MOC:
CALL _ TCH _ ALLOCATION ( MORTR)

KPI = 1
100%
_
_
_
(
)
GEN
TRAFFIC
CHAN
REQ
MORTR

+ UNS_BS_REASON( MORTR)

3G:
per MSC:
MTER:
U _ CALL _ TCH _ ALLOCATION ( MTER)

100%
KPI = 1
U _ GEN _ TRAFFIC _ CHAN _ REQ( MTER)
MOC:
U _ CALL _ TCH _ ALLOCATION ( MORTR)

100%
KPI = 1
U _ GEN _ TRAFFIC _ CHAN _ REQ( MORTR)
Removing RNC causes:
MTER:
30
A30862-X1001-C962-2-76-A1

Tests
U _ CALL _ TCH _ ALLOCATION ( MTER)

KPI = 1
100%
U
GEN
TRAFFIC
CHAN
REQ
MTER
_
_
_
_
(
)

+ U_UNS_RNC_REASON(MTER)

MOC:
U _ CALL _ TCH _ ALLOCATION ( MORTR)

KPI = 1
100%
_
_
_
_
(
)
U
GEN
TRAFFIC
CHAN
REQ
MORTR

+ U_UNS_RNC_REASON(MORTR)
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
PROHIBITED, RESET, RESET CIRCUIT is received for call before digit analysis is
performed.
A30862-X1001-C962-2-76-A1
31

Tests
3.2.2.2
MOC Answered Calls dropped call rate

Description:
This KPI reveals the ratio of dropped calls after answered.
Per cell
32
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
KPI =
REL_ANSW_C ALL_BS_REA SON

100%
ANSW_ORIG_ CALL + ANSW_INCOM _CALL
I
+ REL_ANSW_C ALL_BS_REA SON
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
3.2.3.1
Mobile Originated Traffic Analysis

Emergency call success ratio
Description:
This KPI reveals the ratio of dropped calls after answered.
Per MSC / MSC-S
KPI-formula:
KPI =
TS12_EMERG _CALL_TCH_ALL (MORTR )

100%
EMERGENCY_TS12_ATTEM PTS(MORTR )
TS12_EMERG_CALL_TCH_ALL(MORTR)
A30862-X1001-C962-2-76-A1
33

Tests
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.
Per MSC/MSC-S
KPI-formula:
2G+3G:
Until SR11.0, UR3.0:
Sum =
CALL _ ATTEMPTS ( MORTR)
CALL _ END _ CALL _ FORW ( MORTR)
UNS _ REQ _ DEST _ ERR( MORTR)
UNS _ MS _ BLOCKED( MORTR)
KPI =
GEN _ TRAFF _ CHAN _ REQ( MORTR)

100%
Sum
For SR12.0, UR4.0 or after:
Sum =
CALL _ ATTEMPTS ( MORTR)
CALL _ END _ CALL _ FORW ( MORTR)

UNS _ REQ _ DEST _ ERR( MORTR)
UNS _ MS _ BLOCKED( MORTR)
CALL_REL_BEF_ALERT(MORTR )
KPI =
INTERNAL _ BSSAP _ SEIZURE ( MORTR)

100%
Sum
GEN_TRAFF_CHAN_REQ (MORTR)
34
A30862-X1001-C962-2-76-A1

Tests
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.
established calls divided by the total number of mobile originated call attempts.
Per MSC/MSC-S
0.1%
KPI-formula:
A30862-X1001-C962-2-76-A1
35

Tests
Per 3G MSC:
KPI =
U _ SN _ THROUGH _ CONNECTIONS(MOUT _ PLMN)
+ U _ SN _ THROUGH _ CONNECTIONS(MOUT _ NOT _ PLMN)
+ U _ SN _ THROUGH _ CONNECTIONS _ SAME _ MSC +
U_CALL_END_CALL_FORW (MOUT _ PLMN) +
1 U_CALL_END_CALL_FORW (MOUT _ NOT _ PLMN)

100%
U _ CALL _ ATTEMPTS(MORTR)
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.
36
A30862-X1001-C962-2-76-A1

Tests
3.2.3.4
MOC Traffic Channel Allocation Ratio

Description:
Provides the success ratio of the channel allocation
Per MSC/MSC-S
A30862-X1001-C962-2-76-A1
37

Tests
KPI-formula:
2G+3G:
KPI =
CALL _ TCH _ ALLOCATION ( MORTR) +
TS11 _ EMERG _ CALL _ TCH _ ALL( MORTR) +

TS12 _ EMERG _ CALL _ TCH _ ALL( MORTR)
GEN _ TRAFF _ CHAN _ REQ( MORTR)
100%
3G:
KPI =
U _ CALL _ TCH _ ALLOCATION ( MORTR) +
U _ TS11 _ EMERG _ CALL _ TCH _ ALL( MORTR ) +

U _ TS12 _ EMERG _ CALL _ TCH _ ALL( MORTR)
U _ GEN _ TRAFF _ CHAN _ REQ( MORTR )
100%
CALL_TCH_ALLOCATION
Trigger: each time ASSIGNMENT
COMPLETE is received.
U_GEN_TRAFF_CHAN_REQ (MORTR)
REQUEST is sent to the RNC after the
previous receipt of CM SERVICE
REQUEST.
TS11_EMERG_CALL_TCH_ALL
TS12_EMERG_CALL_TCH_ALL
COMPLETE is received for TS11 calls. COMPLETE is received for TS12 calls.
GEN_TRAFF_CHAN_REQ (MORTR) U_CALL_TCH_ALLOCATION (MORTR)
REQUEST is sent to the BSC after the COMPLETE is received.
previous receipt of CM SERVICE
REQUEST.
U_TS12_EMERG_CALL_TCH_ALL
COMPLETE is received for TS12
UMTS calls.
3.2.3.5
U_TS11_EMERG_CALL_TCH_ALL
COMPLETE is received for TS11 UMTS
calls.
MOC-PSTN Success Rate

Description:
The number of successful MOC-PSTN or other PLMN speech calls ratio.
Per MSC/ MSC-S
38
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
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:
Call _ Answers =
SPEECH _ CALLS _ WITH _ ANSWER( MOUT _ NOT _ PLMN )
+ BS _ REL _ WITH _ ANSWER( MOUT _ NOT _ PLMN )
+ TS11 _ EMERG _ WITH _ ANSWER( MOUT _ NOT _ PLMN )
+ TS12 _ EMERG _ WITH _ ANSWER( MOUT _ NOT _ PLMN )
+ 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)
KPI _ 01 =
Call _ Answers
100%
2G 3GCallAttempts
MOC-PSTN B-Busy Ratio:
KPI _ 02 =
UNS _ MS _ BUSY ( MOUT _ NOT _ PLMN )

100%
2G 3GCallAttem pts
MOC-PSTN A-Release Ratio:
A30862-X1001-C962-2-76-A1
39

Tests
CALL _ REL _ BEF _ ALERT ( MOUT _ NOT _ PLMN )

100%
2G3GCallAttempts
KPI _ 03 =
MOC-PSTN No-Answer Ratio:
No _ Answers =
CALL _ REL _ ALERT ( MOUT _ NOT _ PLMN ) +
CALL _ TIOUT _ ALERT ( MOUT _ NOT _ PLMN )
KPI _ 04 =
No _ Answers
100%
2G3GCallAttempts
MMC UNS RAN Ratio:
KPI _ 05 =
UNS_BS_REASON( MOUT _ NOT _ PLMN )

100%
2G3GCallAttempts
MMC REL EXCHANGE Ratio:
KPI _ 06 =
CALL_REL_EXCHANGE( MOUT _ NOT _ PLMN )

100%
2G 3GCallAttempts
MOC-PSTN Success Rate:
KPI = KPI _ 01 + KPI _ 02 + KPI _ 03 + KPI _ 04 + KPI _ 05 + KPI _ 06

3G:
MOC-PSTN Answer Ratio:
Call _ Answers =
U _ SPEECH _ CALLS _ WITH _ ANSWER( MOUT _ NOT _ PLMN ) +
U _ RNC _ REL _ WITH _ ANSWER( MOUT _ NOT _ PLMN ) +
U _ TS11 _ EMERG _ WITH _ ANSWER( MOUT _ NOT _ PLMN ) +
U _ TS12 _ EMERG _ WITH _ ANSWER( MOUT _ NOT _ PLMN )
KPI _ 01 =
Call _ Answers
100%
U _ CALL _ ATTEMPTS ( MOUT _ NOT _ PLMN ) +
U_CA_DATA(MOUT_NOT_PLMN)
UMTS-MOC-PSTN B-Busy Ratio:
40
A30862-X1001-C962-2-76-A1

Tests
KPI _ 02 =
U _ UNS _ MS _ BUSY ( MOUT _ NOT _ PLMN )

100%
UMTS-MOC-PSTN A-Release Ratio:
KPI _ 03 =
U _ CALL _ REL _ BEF _ ALERT ( MOUT _ NOT _ PLMN )

100%
U_CA_DATA(MOUT_NOT_P LMN)
UMTS-MOC-PSTN No-Answer Ratio:
No _ Answers =
U _ CALL _ REL _ ALERT ( MOUT _ NOT _ PLMN ) +
U _ CALL _ TI _ OUT _ ALERT ( MOUT _ NOT _ PLMN )
KPI _ 04 =
No _ Answers
100%
MMC UNS RAN Ratio:
KPI _ 05 =
UNS_RNC_RE ASON ( MOUT _ NOT _ PLMN )

100%
U
_ CALL _ ATTEMPTS ( MOUT _ NOT _ PLMN ) +
U_CA_DATA(MOUT_NOT_P LMN)
UMTS-MOC-PSTN Success Rate:
KPI = KPI _ 01 + KPI _ 02 + KPI _ 03 + KPI _ 04 + KPI _ 05

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.
A30862-X1001-C962-2-76-A1
41

Tests
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):
PROHIBITED,
RESET, RESET CIRCUIT is received after digit analysis has been performed.
U_SPEECH_CALLS_WITH_ANSWER (MOUT_NOT_PLMN)
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)
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.
42
A30862-X1001-C962-2-76-A1

Tests
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)
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)
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)
respective Message ANM
A30862-X1001-C962-2-76-A1
43

Tests
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.
Per MSC/ MSC-S
KPI-formula:
CDA analog service
KPI =
DATACDA_ANA_WITH_ANS WER(MOUT_N OT_PLMN)

100%
DATACDA_ANA_ATTEMPTS (MOUT_NOT_PLMN)
CDA digital services:
KPI =
DATACDA_DIG_WITH_ANS WER(MOUT_N OT_PLMN)

100%
DATACDA_DIG_ATTEMPTS (MOUT_NOT_ PLMN)
CDS analog services:
KPI =
DATACDS_ANA_WITH_ANS WER(MOUT_N OT_PLMN)

100%
DATACDS_ANA_ATTEMPTS (MOUT_NOT_PLMN)
CDS digital services:
KPI =
DATACDAS_D IG_WITH_AN SWER(MOUT_ NOT_PLMN)

100%
DATACDS_DIG_ATTEMPTS (MOUT_NOT_ PLMN)
2G only(services not supported by the external MGW):
Alternate speech/facsimile services:
KPI =
ALTFAXSP_W ITH_ANSWER (MOUT_NOT_ PLMN)

100%
ALTFAXSP_CALL_ATTEMP TS(MOUT_NO T_PLMN)
Data calls for automatic facsimile group 3:
KPI =
FAX3_WITH_ ANSWER(MOU T_NOT_PLMN )

100%
FAX3_CALL_ATTEMPTS(M OUT_NOT_PL MN)
Alternate speech/data or speech followed by data services:
KPI =
44
ALT_SPEECH _DATA_ ANS WER (MOUT_NOT_ PLMN)

100%
ALT_SPEECH _DATA_ATTE MPTS(MOUT_ NOT_PLMN)
A30862-X1001-C962-2-76-A1

Tests
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):
respective message:
ANM
DATACDA_DIG_ATTEMPTS(MOUT_
NOT_PLMN):
type:
DATACDS_DIG_WITH_ANSWER
(MOUT_NOT_PLMN):
respective message:
ANM
DATACDS_DIG_ATTEMPTS(MOUT_NOT
_PLMN):
type:
ALTFAXSP_WITH_ANSWER(MOUT_
NOT_PLMN);
Trigger: each time the connection has
actually been released in response to the
receipt of the respective message:
ANM
ALTFAXSP_CALL_ATTEMPTS(MOUT_
NOT_PLMN):
type:
MOUT_PLMN / MOUT_NOT_PLMN: In
FAX3_WITH_ANSWER(MOUT_NOT_P
LMN):
respective message:
ANM
FAX3_CALL_ATTEMPTS(MOUT_NOT_P
LMN):
type
and SET UP is sent.
A30862-X1001-C962-2-76-A1
45

Tests
3.2.4
3.2.4.1
DATACDS_ANA_WITH_ANSWER
(MOUT_NOT_PLMN):
respective message:
ANM
DATACDS_ANA_ATTEMPTS(MOUT_NO
T_PLMN):
type:
ALT_SPEECH_DATA_ ANSWER
(MOUT_NOT_PLMN):
Trigger: each time the digit analysis
after interrogation results in the relevant
traffic type:
general, the values of this counter
include traffic without interrogation
unless international interrogation is
applied.
ALT_SPEECH_DATA_ATTEMPTS(MOUT
_NOT_PLMN):
type:
MMC KPIs
MMC Success Ratio

Description:
The number of successful MMC calls.
Per MSC/ MSC-S
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)
46
A30862-X1001-C962-2-76-A1

Tests
+ DED_PAD_ATTEMPTS (MOUT_PLMN)
+ DATACDS_ANA_ATTEMPTS (MOUT_PLMN)
+ DATACDS_DIG_ATTEMPTS (MOUT_PLMN)
+ ALT_SPEECH_DATA_ATTEMPTS (MOUT_PLMN)
MMC Answer Ratio:
Call _ Answers =
SPEECH _ CALLS _ WITH _ ANSWER( MOUT _ PLMN )
+ BS _ REL _ WITH _ ANSWER( MOUT _ PLMN )
+ 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)
KPI _ 01 =
Call _ Answers
100%
2G 3GCallAttempts
MMC B-Busy Ratio:
KPI _ 02 =
UNS _ MS _ BUSY ( MOUT _ PLMN )

100%
2G 3GCallAttempts
MMC A-Release Ratio:
KPI _ 03 =
CALL _ REL _ BEF _ ALERT ( MOUT _ PLMN )

100%
2G3GCallAttempts
MMC No-Answer Ratio:
No _ Answers =
CALL _ REL _ ALERT ( MOUT _ PLMN ) +
CALL _ TIOUT _ ALERT ( MOUT _ PLMN )
KPI _ 04 =
No _ Answers
100%
2G3GCallAttempts
MMC UNS RAN Ratio:
A30862-X1001-C962-2-76-A1
47

Tests
KPI _ 05 =
UNS_BS_REASON( MOUT _ PLMN )

100%
2G 3GCallAttempts
KPI _ 06 =
CALL_REL_EXCHANGE( MOUT _ PLMN )

100%
2G3GCallAttempts
MMC Success Rate:
3G:
UMTS-MMC Answer Ratio:
Call _ Answers =
U _ SPEECH _ CALLS _ WITH _ ANSWER ( MOUT _ PLMN ) +
U_CC_ANSW_DATA (MOUT_PLMN) +
U _ RNC _ REL _ WITH _ ANSWER ( MOUT _ PLMN )
KPI _ 01 =
Call _ Answers
100%
U _ CALL _ ATTEMPTS ( MOUT _ PLMN ) +
U_CA_DATA (MOUT_PLMN)
UMTS-MMC B-Busy Ratio:
KPI _ 02 =
U _ UNS _ MS _ BUSY ( MOUT _ PLMN )

100%
UMTS-MMC A-Release Ratio:
KPI _ 03 =
U _ CALL _ REL _ BEF _ A _ ALERT ( MOUT _ PLMN )

100%
U_CA_DATA (MOUT_PLMN )
UMTS-MMC No-Answer Ratio:
48
A30862-X1001-C962-2-76-A1

Tests
No _ Answers =
U _ CALL _ REL _ A _ ALERT ( MOUT _ PLMN ) +
U _ CALL _ TI _ OUT _ ALERT ( MOUT _ PLMN )
KPI _ 04 =
No _ Answers
100%
_
_
( MOUT _ PLMN ) +
U
CALL
ATTEMPTS
MMC UNS RAN Reasons:
KPI _ 05 =
UNS_RNC_RE ASON( MOUT _ PLMN )

100%
U
_ CALL _ ATTEMPTS ( MOUT _ PLMN ) +
UMTS-MMC Success Rate:
KPI = KPI _ 01 + KPI _ 02 + KPI _ 03 + KPI _ 04 + KPI _ 05
SPEECH_CALLS_WITH_ANSWER(M
OUT_PLMN)
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
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).
A30862-X1001-C962-2-76-A1
49

Tests
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_PL
MN):
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(MO
UT_PLMN)
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
U_CALL_REL_ALERT
(MOUT_PLMN)
COMPLETE is received after the alert
signal is sent and before CONNECT is
received, for a UMTS call.
U_CALL_REL_BEF_ALERT
(MOUT_PLMN)
Trigger: RELEASE (clear backward or clear
U_CALL_TI_OUT_ALERT
(MOUT_PLMN)
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_PLM
N)
SUBSYSTEM PROHIBITED,
RESET, RESET CIRCUIT is received
for UMTS call
after digit analysis has been
performed.
50
A30862-X1001-C962-2-76-A1

Tests
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_PL
MN):
Trigger: In general, the values of this

counter include traffic without interrogation
unless international interrogation is
applied.
U_CA_DATA (MOUT_PLMN):
Trigger: each time SET UP is received
and digit analysis results in this traffic type
(data call attempts only).
3.2.4.2
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_CC_ANSW_DATA (MOUT_PLMN)
Trigger: each time the connection is released in
Message ANM
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.
Per MSC/ MSC-S
KPI-formula:
Per MSC:
CDA analog service:
KPI =
DATACDA_ANA_WITH_ANS WER(MOUT_P LMN)

100%
DATACDA_ANA_ATTEMPTS (MOUT_PLMN)
KPI =
DATACDA_DIG_WITH_ANS WER(MOUT_P LMN)

100%
DATACDA_DIG_ATTEMPTS (MOUT_PLMN)
A30862-X1001-C962-2-76-A1
51

Tests
KPI =
DATACDS_ANA_WITH_ANS WER(MOUT_P LMN)

100%
DATACDS_ANA_ATTEMPTS (MOUT_PLMN)
KPI =
DATACDAS_D IG_WITH_AN SWER(MOUT_ NOT_PLMN)

100%
DATACDS_DIG_ATTEMPTS (MOUT_NOT_ PLMN)

Alternate speech/facsimile services:
KPI =
ALTFAXSP_W ITH_ANSWER (MOUT_PLMN)

100%
ALTFAXSP_CALL_ATTEMP TS(MOUT_PL MN)
Data calls for automatic facsimile group 3:
KPI =
FAX3_WITH_ ANSWER(MOU T_NOT_PLMN )

100%
FAX3_CALL_ATTEMPTS(M OUT_NOT_PL MN)
Alternate speech/data or speech followed by data services:
KPI =
ALT_SPEECH _DATA_ ANS WER (MOUT_PLMN)

100%
ALT_SPEECH _DATA_ATTE MPTS(MOUT_PLMN)
52
(MOUT__PLMN):
respective message:
ANM
DATACDA_ANA_ATTEMPTS(MOUT_PL
MN):
type:
DATACDA_DIG_WITH_ANSWER
(MOUT_ PLMN):
respective message:
ANM
DATACDA_DIG_ATTEMPTS(MOUT_
PLMN):
type:
A30862-X1001-C962-2-76-A1

Tests
3.2.5
3.2.5.1
DATACDS_DIG_WITH_ANSWER
(MOUT_PLMN):
respective message:
ANM
DATACDS_DIG_ATTEMPTS(MOU_PLM
N):
type:
ALTFAXSP_WITH_ANSWER(MOUT_
PLMN);
receipt of the respective message:
ANM
ALTFAXSP_CALL_ATTEMPTS(MOUT_
PLMN):
type:
FAX3_WITH_ANSWER(MOUT_PLMN):
respective message:
ANM
FAX3_CALL_ATTEMPTS(MOUT_PLMN)
:
type
and SET UP is sent.
(MOUT_PLMN):
respective message:
ANM
DATACDS_ANA_ATTEMPTS(MOUT_PL
MN):
type:
Mobile Terminating Traffic KPIs

MTC Success Ratio
Description:
The number of successful MTC speech calls.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
53

Tests
KPI-formula:
Hint: the CF feature must be activated
2G+3G:
MTER Answer Ratio:
Call _ Answers =
SPEECH _ CALLS _ WITH _ ANSWER( MTER)
+ BS _ REL _ WITH _ ANSWER( MTER)
+ 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)
KPI _ 01 =
Call _ Answers
100%
CALL _ ATTEMPTS ( MTER)
MTER B-Busy Ratio:
KPI _ 02 =
UNS _ MS _ BUSY(MTER )
100%
CALL _ ATTEMPTS(MTER )
MTER A-Release Ratio:
KPI _ 03 =
CALL _ REL _ BEF _ ALERT(MTER )
100%
CALL _ ATTEMPTS (MTER )
MTER No-Answer Ratio:
KPI _ 04 =
CALL _ REL _ ALERT(MTER )

100%
CALL _ ATTEMPTS(MTER )
MTER Call Forwarding Ratio:
KPI _ 05 =
CALL _ END _ CALL _ FORW ( MTER)

100%
MMC UNS RAN Ratio:
KPI _ 06 =
54
UNS_BS_REASON ( MTER)
100%
A30862-X1001-C962-2-76-A1

Tests
KPI _ 07 =
CALL_REL_EXCHANGE( MTER )
100%
CALL _ ATTEMPTS ( MTER )
MTER Success Rate:
KPI = KPI _ 01 + KPI _ 02 + KPI _ 03 + KPI _ 04 + KPI _ 05 +

KPI _ 06 + KPI _ 07
3G:
MTER Answer Ratio:
Call _ Answers =
U _ SPEECH _ CALLS _ WITH _ ANSWER ( MTER ) +
U_CC_ANSW_DATA (MTER) +
U _ RNC _ REL _ WITH _ ANSWER ( MTER )
KPI _ 01 =
Call _ Answers
100%
U _ CALL _ ATTEMPTS ( MTER )
MTER B-Busy Ratio:
KPI _ 02 =
U _ UNS _ MS _ BUSY ( MTER)

100%
U _ CALL _ ATTEMPTS ( MTER)
MTER A-Release Ratio:
KPI _ 03
=
U _ CALL _ REL _ BEF _ ALERT ( MTER )

100 %
MTER No-Answer Ratio:
KPI _ 04 =
U _ CALL _ REL _ ALERT ( MTER)

100%
U _ CALL _ ATTEMPTS ( MTER)
MTER Call Forwarding Ratio:
KPI _ 05 =
A30862-X1001-C962-2-76-A1
U _ CALL _ END _ CALL _ FORW ( MTER )

100%
55

Tests
MMC UNS RAN Ratio:
KPI _ 06 =
UNS_RNC_RE ASON( MTER )
100%
MTER Success Ratio:
56
SPEECH_CALLS_WITH_ANSWER
(MTER)
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
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.
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):
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)
released in response the CONNECT
message.
A30862-X1001-C962-2-76-A1

Tests
3.2.5.2
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
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
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
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
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.
MTC Failure Ratio

Description:
This KPI indicates the failure ratio of mobile terminating calls.
established mobile terminating calls divided by the number of mobile terminating call
attempts.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
57

Tests

KPI-formula:
2G+3G:
CALL _ TCH _ ALLOCATION(MTER)

100%
KPI = 1
RECEIVED _ PAG _ RESP(MTER)
3G:
U _ CALL _ TCH _ ALLOCATION(MTER)

100%
KPI = 1
U _ RECEIVED _ PAG _ RESP(MTER)
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.
58
A30862-X1001-C962-2-76-A1

Tests
3.2.5.3
Paging Procedure Failure Ratio

Description:
This KPI indicates the failure ratio of paging procedures.
paging procedures divided by the number of paging attempts.
Per MSC/ MSC-S
KPI-formula:
2G+3G:
RECEIVED _ PAG _ RESP

100%
KPI = 1
STARTED _ PAGING _ PROC
STARTED_PAGING_PROC
Incremented each time PAGING is sent.
RECEIVED_PAG_RESP
Increment each time PAGING RESPONSE is received from the BSC
A30862-X1001-C962-2-76-A1
59

Tests
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.
Per MSC/ MSC-S
KPI-formula:
Per MSC:
CDA analog services:
KPI =
DATACDA_ANA_WITH_ANS WER(MTER)
100%
DATACDA_ANA_ATTEMPTS (MTER)
KPI =
DATACDA_DIG_WITH_ANS WER(MTER)
100%
DATACDA_DIG_ATTEMPTS (MTER)

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

Tests
KPI =
DATACDS_ANA_WITH_ANS WER(MTER)
100%
DATACDS_ANA_ATTEMPTS (MTER)
KPI =
DATACDAS_DIG_WITH_AN SWER(MTER)
100%
DATACDS_DIG_ATTEMPTS (MTER)

alternate speech/facsimile services:
KPI =
ALTFAXSP_W ITH_ANSWER (MTER)

100%
ALTFAXSP_CALL_ATTEMP TS(MTER)
automatic facsimile group 3:
KPI =
FAX3_WITH_ ANSWER(MTE R)
100%
FAX3_CALL_ATTEMPTS(M TER)
Alternate speech/data or speech followed by data:
KPI =
ALT_SPEECH _DATA_ WIT H_ANSWER (MTER)

100%
ALT_SPEECH _DATA_ATTE MPTS(MTER)
(MTER):
respective
message:
MTER: CONNECT
DATACDA_ANA_ATTEMPTS(MTER):
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):
respective
message:
MTER: CONNECT
DATACDA_DIG_ATTEMPTS(MTER):
type:
the A interface.
A30862-X1001-C962-2-76-A1
61

Tests
62
ALTFAXSP_WITH_ANSWER(MTER);
receipt
of the respective message:
MTER: CONNECT
ALTFAXSP_CALL_ATTEMPTS(MTER):
type:
the A interface.
FAX3_WITH_ANSWER(MTER):
respective message:
MTER: CONNECT
FAX3_CALL_ATTEMPTS
type and SET UP is sent.
(MTER):
respective
message:
MTER: CONNECT
MOUT_PLMN, MOUT_NOT_PLMN: ANM
DATACDS_ANA_ATTEMPTS(MTER):
type:
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):
respective
message:
MTER: CONNECT
DATACDS_DIG_ATTEMPTS(MTER):
type:
the A interface.
ALT_SPEECH_DATA_ ANSWER (MTER):

CONNECT
Message.
ALT_SPEECH_DATA_ATTEMPTS(MTER
):
type:
the A interface.
A30862-X1001-C962-2-76-A1

Tests
3.2.5.5
MTC Traffic Channel Allocation Ratio

Description:
Provides the success ratio of the chanel allocation
Per MSC/ MSC-S
KPI-formula:
2G+3G:
KPI =
CALL _ TCH _ ALLOCATION ( MTER )

100%
GEN _ TRAFF _ CHAN _ REQ ( MTER )
KPI =
U _ CALL _ TCH _ ALLOCATION ( MTER )

100%
U _ GEN _ TRAFF _ CHAN _ REQ( MTER )
3G:
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
U_GEN_TRAFF_CHAN_REQ (MTER)
Trigger: each time ASSIGNMENT REQUEST is sent to the RNC after the previous
A30862-X1001-C962-2-76-A1
63

Tests
3.2.6
3.2.6.1
Handover KPIs
Handover Success Ratio
Description:
The number of successful handover in relation to the number of attempted handover.
Per MSC/ MSC-S
KPI-formula:
2G+3G:
HO _ Success =
SUCC _ COMPLETED _ HO +
SUCC _ MSC _ MSC _ HO _ MSCA +
SUCC _ MSC _ MSC _ HO _ MSCB +
SUCC _ SUBSEQ _ MSC _ MSC _ HO _ MSCB +
SUCC _ HO _ SEC _ MSC _ MSC _ HO _ MSCB
HO _ Attempts =
HANDOVER _ ATTEMPTS +
SUBSEQ _ MSC _ MSC _ HO _ MSCA +
HANDOVER _ MSC _ MSC _ IC _ ATTEMPTS
KPI =
64
HO _ Success
100%
HO _ Attempts
A30862-X1001-C962-2-76-A1

Tests
3G:
HO _ Success =
U _ SUCC _ COMPLETED _ HO +
U _ SUCC _ MSC _ MSC _ HO _ MSCA +
U _ SUCC _ MSC _ MSC _ HO _ MSCB +
U _ SUCC _ SUBSEQ _ MSC _ MSC _ HO _ MSCB +
U _ SUCC _ HO _ SEC _ MSC _ MSC _ HO _ MSCB
HO _ Attempts =
U _ HANDOVER _ ATTEMPTS +
U _ SUBSEQ _ MSC _ MSC _ HO _ MSCA +
U _ HANDOVER _ MSC _ MSC _ IC _ ATTEMPTS
KPI =
HO _ Success
100%
HO _ Attempts
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.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
65

Tests
KPI-formula:
Intra _ MSC _ HO _ Success =

SUCC _ COMPLETED _ HO +
SUCC _ HO _ SEC _ MSC _ MSC _ HO _ MSCB
2G+3G:
Intra _ MSC _ HO _ Attempts =

HANDOVER _ ATTEMPTS
HANDOVER _ MSC _ MSC _ OG _ ATTEMPTS
SUBSEQ _ MSC _ MSC _ HO _ MSCB
KPI =
Intra _ MSC _ HO _ Success

100%
Intra _ MSC _ HO _ Attempts
Intra _ MSC _ HO _ Success =

U _ SUCC _ COMPLETED _ HO +
U _ SUCC _ HO _ SEC _ MSC _ MSC _ HO _ MSCB
3G:
Intra _ MSC _ HO _ Attempts =

U _ HANDOVER _ ATTEMPTS
U _ HANDOVER _ MSC _ MSC _ OG _ ATTEMPTS
U _ SUBSEQ _ MSC _ MSC _ HO _ MSCB
KPI =
(Remark:
Intra _ MSC _ HO _ Success

100%
Intra _ MSC _ HO _ Attempts
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 (3G2G) Hand Over procedures
when one 3GMSC is involved.
66
A30862-X1001-C962-2-76-A1

Tests
Intersystem (3G2G) Intra MSC HO procedures divided by the number of
Intersystem (3G2G) Intra MSC HO attempts.
Per MSC/ MSC-S
1.0 %
KPI-formula:
U _ INTRA _ HANDOVER _ UMTS _ TO _ GSM

100%
KPI = 1
U _ INTRA _ HO _ ATT _ UMTS _ TO _ GSM
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
MS/UE
RNC
3G-MSC
BSC
Relocation Required
Handover Request
Handover Request Ack
Relocation Command
RRC Handover Command
Handover Detect
U_INTRA_HO_ATT_
UMTS_TO_GSM
RRC Handover Complete
Iu Release Command
Handover Complete
Iu Release Complete
U_INTRA_HANDOVE
R_UMTS_TO_GSM
A30862-X1001-C962-2-76-A1
67

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

Description:
This KPI indicates the failure ratio of Intersystem (3G2G) Hand Over procedures
when one 3GMSC and one 2GMSC are involved.
Intersystem (3G2G) Inter MSC HO procedures divided by the number of
Intersystem (3G2G) Inter MSC HO attempts.
Per MSC/ MSC-S
KPI-formula:
KPI =
U _ INTER _ HANDOVER _ UMTS _ TO _ GSM

1
100%
U _ INTER _ MSC _ MSC _ HO _ ATT _ UMTS _ GSM _ OG
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
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.
68
A30862-X1001-C962-2-76-A1

Tests
Per MSC/ MSC-S
KPI-formula:
2G+3G:
Inter _ MSCA _ HO _ Attempts =

HANDOVER _ MSC _ MSC _ OG _ ATTEMPTS +
SUBSEQ _ MSC _ MSC _ HO _ MSCA
KPI =
3G:
SUCC _ MSC _ MSC _ HO _ MSCA

100%
Inter _ MSCA _ HO _ Attempts
Inter _ MSCA _ HO _ Attempts =

U _ HANDOVER _ MSC _ MSC _ OG _ ATTEMPTS +
U _ SUBSEQ _ MSC _ MSC _ HO _ MSCA
KPI =
U _ SUCC _ MSC _ MSC _ HO _ MSCA

100%
U _ Inter _ MSCA _ HO _ Attempts
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.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
69

Tests
KPI-formula:
Inter _ MSCB _ HO _ Success =

SUCC _ MSC _ MSC _ HO _ MSCB +
SUCC _ SUBSEQ _ MSC _ MSC _ HO _ MSCB
2G+3G:
Inter _ MSCB _ HO _ Attempts =

HANDOVER _ MSC _ MSC _ IC _ ATTEMPTS +
SUBSEQ _ MSC _ MSC _ HO _ MSCB
KPI =
Inter _ MSCB _ HO _ Success

100%
Inter _ MSCB _ HO _ Attempts
Inter _ MSCB _ HO _ Success =

U _ SUCC _ MSC _ MSC _ HO _ MSCB +
U _ SUCC _ SUBSEQ _ MSC _ MSC _ HO _ MSCB
3G:
Inter _ MSCB _ HO _ Attempts =

U _ HANDOVER _ MSC _ MSC _ IC _ ATTEMPTS +
U _ SUBSEQ _ MSC _ MSC _ HO _ MSCB
KPI =
U _ Inter _ MSCB _ HO _ Success

100%
U _ Inter _ MSCB _ HO _ Attempts
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 ones complement of the number of successful Inter
MSC SRNS relocations divided by the number of Inter MSC SRNS relocation
attempts.
70
A30862-X1001-C962-2-76-A1

Tests
Per MSC/ MSC-S
KPI-formula:
Per MSC:
KPI =
U _ SUCC _ MSC _ MSC _ HO _ MSCA
U
_
INTER
_
HANDOVER
_
UMTS
_
TO
_
GSM
1 U _ HANDOVER _ MSC _ MSC _ OG _ ATTEMPTS

100%
U
_
INTER
_
MSC
_
MSC
_
HO
_
ATT
_
UMTS
_
GSM
_
OG
3.2.6.8
Handover - Message Flows/Triggerpoints
GSM Inter MSC Handover :
A30862-X1001-C962-2-76-A1
71

Tests
GSM Intra MSC Handover:
GSM Subsequent Inter-MSC Handover Back to A:
GSM Subsequent Inter MSC Handover:
72
A30862-X1001-C962-2-76-A1

Tests
GSM Subsequent Intra MSC-B Handover:
UMTS Inter MSC Handover:
A30862-X1001-C962-2-76-A1
73

Tests
UMTS Intra MSC Handover:

MS/UE
RNC old
RNC new
3G-MSC
Relocation Required
Relocation Request
ERQ
+
U_HANDOVER_
ATTEMPTS
ECF
Relocation Command
Handover Access
Relocation Request Ackn
Relocation Detect
Relocation Complete
+
U_SUCC_COMPLET
ED_HO
Iu Release Command
REL
RLC
Iu Release Complete
74
A30862-X1001-C962-2-76-A1

Tests
UMTS Subsequent Inter MSC Handover Back to A:
MS/UE
RNC old
3G-MSC-B
Relocation Required
3G-MSC-A
+
U_SUBSEQ_MSC_MSC_H
O_MSCA
+ U_HANDOVER_ATTEMPTS
Request : Prepare Subsequent Handover
+ U_SUBSEQ_MSC_MSC_HO_MSCB
RNC new
Relocation Request
ERQ
ECF
Relocation Command
Response : Prepare Subsequent Handover
Handover Access
Relocation Detect
Relocation Complete
Request : Send End Signal
Iu Release Command
+ U_SUCC_MSC_MSC_HO_MSCB
REL
+
U_SUCC_MSC_MSC_HO_
MSCA
RLC
Iu Release Complete
REL
RLC
UMTS Subsequent Inter MSC Handover:
A30862-X1001-C962-2-76-A1
75

Tests
UMTS Subsequent Intra MSC-B Handover:
MS/UE
RNC old
RNC new
3G-MSC-B
3G-MSC-A
Relocation Required
Relocation Request
+
U_HANDOVER_ATT
EMPTS
ERQ
ECF
Relocation Command
Handover Access

+
U_SUCC_HO_SEC_MSC_
MSC_HO_MSCB
Relocation Detect
Relocation Complete
Iu Release Command
REL
RLC
Process Access
Signalling(HO_PERFORMED)
Iu Release Complete
Intra MSC Inter System (3G-2G) Handover:

MS/UE
RNC
3G-MSC
BSC
Relocation Required
Handover Request
Handover Request Ack
Relocation Command
U_INTRA_HO_ATT
_UMTS_TO_GSM

Handover Detect
Iu Release Command
U_INTRA_HANDOVE
R_UMTS_TO_GSM
Handover Complete
Iu Release Complete
76
A30862-X1001-C962-2-76-A1

Tests
Inter MSC Inter System (3G-2G) Handover:
MS/UE
RNC
3G-MSC
BSC
BSC
Relocation Required
Prepare Handover
U_INTRA_HO_ATT_UMTS_TO_G
SM
Prepare Handover
Response
Handover Request
Handover Request
Ack
Relocation Command
Handover Detect
Handover Complete
Send End Signal request
Iu Release Command
Iu Release Complete
3.2.7
3.2.7.1
Send End Signal

Response
U_INTRA_HANDOVER_
UMTS_TO_GSM
SMS Analysis
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.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
77

Tests
KPI-formula:
2G+3G
SUCCESS = SUCC _ SMS _ INC + SUCC _ SMS _ OTG

ATTEMPTS =
SMS _ INC _ ATTEMPTS + SMS _ OTG _ ATTEMPTS
SUCCESS
KPI = 1
100%
ATTEMPTS
3G
SUCCESS = U _ SUCC _ SMS _ INC + U _ SUCC _ SMS _ OTG

ATTEMPTS =
U _ SMS _ INC _ ATTEMPTS + U _ SMS _ OTG _ ATTEMPTS
SUCCESS
KPI = 1
100%
ATTEMPTS
MS/UE
BSC/RNC
2G/3G-GMSC/VLR
HLR
SMS-GW
CM_Service_Request
(CM Service Type=SMS)
Paging, Authentication, Security

CP DATA
(RP_MO_DATA(SMS_SUBMIT))
+ U_SMS_SER_REQ_ATTEMPTS
CP ACK
+ (U_)SMS_OTG_ATTEMPTS
MAP_MO Forward Short Message

(SC Address, MSIsdn, RP_UD(SMS_SUBMIT))
+ (U_)SUCC_SMS_OTG
MAP_MO Forward Short Message Ack
(RP_UD(SMS_SUBMIT_REPORT))
CP DATA
(RP_ACK(SMS_SUBMIT_REPORT))
CP ACK
78
A30862-X1001-C962-2-76-A1

Tests
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.
Per MSC/ MSC-S
KPI-formula:
2G+3G:
SUCC _ SMS _ INC

100%
KPI = 1
SMS _ INC _ ATTEMPTS
3G:
U _ SUCC _ SMS _ INC

100%
KPI = 1
U _ SMS _ INC _ ATTEMPTS
A30862-X1001-C962-2-76-A1
79

Tests
(For 3G the attempt counter is incremented after Paging).
MS/UE
BSC/RNC
2G/3G-GMSC/VLR
HLR
SMS-GW
MAP_Send Routing Info For SM

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

(IMSI/LMSI, MSC)
MAP_MT Forward Short Message
(SC Address, IMSI/LMSI, RP_UD(SMS_DELIVER))
+ U_SMS_INC_ATTEMPTS
CP DATA
(RP_MT_DATA(SMS_DELIVER))
CP ACK
CP DATA
(RP_ACK(SMS_DELIVER_REPORT)
CP ACK
+ (U_)SUCC_SMS_INC
MAP_MT Forward Short Message Ack

(RP_UD(SMS_DELIVERY_REPORT))
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.
Per MSC/ MSC-S
80
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
2G+3G:
KPI =
UNS _ SMS _ INC _ DELIVERY _ FAIL

100%
MS/UE
BSC/RNC
2G/3G-GMSC/VLR
HLR
SMS-GW
MAP_Send Routing Info For SM

(MSIsdn, SM-RO-PRI, SC Address)
MAP_Send Routing Info For SM Ack
(IMSI/LMSI, MSC)
+ SMS_INC_ATTEMPTS
MAP_MT Forward Short Message

(SC Address, IMSI/LMSI, RP_UD(SMS_DELIVER))
the MSC detects any

error
+ 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))
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.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
81

Tests
KPI-formula:
2G+3G:
KPI =
UNS _ SMS _ INC _ NO _ FACILITY

100%
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.
Per MSC/ MSC-S
KPI-formula:
82
2G+3G :
SUCC _ SMS _ OTG

100%
KPI = 1
SMS _ OTG _ ATTEMPTS
3G:
U _ SUCC _ SMS _ OTG

100%
KPI = 1
U _ SMS _ OTG _ ATTEMPTS
A30862-X1001-C962-2-76-A1

Tests
MS/UE
BSC/RNC
2G/3G-GMSC/VLR
HLR
SMS-GW
CM_Service_Request

CP DATA
+ U_SMS_SER_REQ_ATTEMPTS
CP ACK
+ (U_)SMS_OTG_ATTEMPTS

+ (U_)SUCC_SMS_OTG
MAP_MO Forward Short Message Ack
(RP_UD(SMS_SUBMIT_REPORT))
CP DATA
(RP_ACK(SMS_SUBMIT_REPORT))
CP ACK
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 ones complement of the number of SMS
successfully acknowledged by the MSC divided by the total number of SMS attempts
received.
Per MSC/ MSC-S
A30862-X1001-C962-2-76-A1
83

Tests
KPI-formula:
Per MSC:
U _ SMS _ OTG _ ATTEMPTS

100%
KPI = 1
U _ SMS _ SER _ REQ _ ATTEMPTS
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.
Per MSC/ MSC-S
KPI-formula:
2G+3G:
84
KPI =
UNS _ SMS _ OTG _ DELIVERY _ FAIL

100%
SMS _ OTG _ ATTEMPTS
A30862-X1001-C962-2-76-A1

Tests
MS/UE
BSC/RNC
2G/3G-GMSC/VLR
HLR
SMS-GW
CM_Service_Request
Authentication, Security
CP DATA
CP ACK
+ SMS_OTG_ATTEMPTS
+ UNS_SMS_OTG_DELIVERY_FAIL

MAP_MO Forward Short Message Error

(RP_UD(User error = unknown SC, SC
congestion, invalid SMS address, subscriber not
SC subscriber))
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
Per MSC/ MSC-S
KPI-formula:
A30862-X1001-C962-2-76-A1
85

Tests
For MORTR and MICTR :
x (MORTR, MICTR )
KPI =
IN _ OVERLOAD( x ) +
+ IN _ NO _ ANSW _ SCP( x ) +
IN _ SERV _ CHECK( x )
IN _ ATTEMPTS( x )
100%
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 ones complement of the number of answered IN
requests divided by the total number of IN requests sent out by the MSC.
Per MSC/ MSC-S
86
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
2G+3G:
ERROR/REJECT MSG SENT BY SSP
+ TIMEOUT ON RESPONSE
+ ABORTED BY SCP OR REMOTE TCAP
+ ABORT LOCALLY BY SSP
+ ERROR/REJECTION MESSAGE FROM SCP

+ MESSAGE NOT ACCEPTED BY TCAP
KPI =
100%
ATTEMPTED_ DIALOG _INITIATIO NS
ATTEMPTED_DIALOG _INITIATIONS:
Trigger: trial to send TCAP primitive
TC_BEGIN_REQ or when
C:SCP_CONTROLLED_INPUT_RESPON
SE (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_ACEPT
ED
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
A30862-X1001-C962-2-76-A1
87

Tests
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.
Per MSC/ MSC-S
Per SS
KPI-formula:
Per SS:
SUCC _ INVOC _ SERV _ CALL _ FORWARD

100%
KPI = 1
INVOC _ SERV _ CALL _ FORWARD
SUCC _ INVOC _ AOC _ CHARGE

100%
KPI = 1
INVOC _ SERV _ AOC _ CHARGE
SUCC _ INVOC _ AOC _ INFO

100%
KPI = 1
_ AOC _ CHARGE _ INFO
INVOC
SUCC _ INVOC _ MULTIPARTY

100%
KPI = 1
INVOC _ SERV _ MULTIPARTY
SUCC _ INVOC _ PUT _ HOLD

100%
KPI = 1
INVOC _ SERV _ PUT _ HOLD
SUCC _ INVOC _ RETRIEVE _ HOLD

100%
KPI = 1
INVOC _ SERV _ RETRIEVE _ HOLD
SUCC _ INVOC _ CALL _ BACK

100%
KPI = 1
INVOC _ SERV _ CALL _ BACK
88
A30862-X1001-C962-2-76-A1

Tests
SUCC _ INVOC _ CALL _ TRANSFER

100%
KPI = 1
INVOC _ SERV _ CALL _ TRANSFER
SUCC _ INVOC _ CCBS _ MORTR

100%
KPI = 1
INVOC
_ SERV _ CCBS _ MORTR
SUCC _ INVOC _ CCBS _ MTER

100%
KPI = 1
INVOC _ SERV _ CCBS _ MTER
SUCC_INVOC_SPLIT_MPTY
100%
KPI = 1
INVOC_SERV_SPLIT_MPTY
Per MSC:
SUCC _ INVOC _ SERV _ CALL _ FORWARD +
SUCC _ INVOC _ AOC _ CHARGE +
SUCC _ INVOC _ AOC _ INFO +
SUCC _ INVOC _ MULTIPARTY +
SUCC _ INVOC _ SPLIT _ MPTY +
SUCC _ INVOC _ PUT _ HOLD +
SUCC _ INVOC _ RETRIEVE _ HOLD +
SUCC _ INVOC _ CALL _ BACK +
SUCC _ INVOC _ CALL _ TRANSFER +
SUCC _ INVOC _ CCBS _ MORTR +
SUCC _ INVOC _ CCBS _ MTER
KPI = 1
100%
INVOC _ SERV _ CALL _ FORWARD +
INVOC _ SERV _ AOC _ CHARGE +
INVOC _ AOC _ CHARGE _ INFO +
INVOC _ SERV _ MULTIPARTY +
INVOC _ SERV _ SPLIT _ MPTY +
INVOC _ SERV _ PUT _ HOLD +
INVOC _ SERV _ RETRIEVE _ HOLD +
INVOC _ SERV _ CALL _ BACK +
INVOC _ SERV _ CALL _ TRANSFER +
INVOC _ SERV _ CCBS _ MORTR +
INVOC _ SERV _ CCBS _ MTER
A30862-X1001-C962-2-76-A1
89

Tests
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
INVOC_SERV_MULTIPARTY
each time this service is invoked and recognized during database access.
SUCC_INVOC_MULTIPARTY
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.
90
A30862-X1001-C962-2-76-A1

Tests
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
SUCC_INVOC_CALL_BACK
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.
Per MSC/ MSC-S
KPI-formula:
2G+3G:
KPI =
SUCC_INTER_MGW_HO
100
INTER_MGW_ HO_ATTS
SUCC_INTER_MGW_HO
Trigger: This counter will be triggered on receiving the ISCCP message
HO_EXECUTED.
A30862-X1001-C962-2-76-A1
91

Tests
INTER_MGW_HO_ATTS
Trigger: Number of MGW outgoing requests for inter-MGW
3.3
3.3.1
HLR/AC related KPIs

MAP Dialog MSRN Provisioning Success Ratio
Description:
This KPI reveals the success ratio of the MSRN provisioning procedure.
Per HLR
KPI-formula:
KPI =
RECVD _ MSRN
100%
SND _ PROV _ MSRN
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.
Per HLR
92
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
2G+3G
KPI =
UNS_CANLOCMSG_ANY_OTHER +
+ UNS_CANLOCMSG_UNIDENT_SUB +
+ UNS_SUB_ADMIN_CANLOC_UNIDENT_MS +
+ UNS_SUB_ADMIN_CANLOC_ANY_OTHER +
+ UNS_CANLOC_UNIDENT_SUB_SS +
+ UNS_CANLOC_ANY_OTHER_SS
SND_CAN_LOC_MSG_LOC_UPD +
+ SND_CAN_LOC_MSG_SUB_ADMIN +
+ SENT_CAN_L OC_MSG_AFTER_SCI
100%
UNS_CANLOCMSG_ANY_OTHER
Trigger: each time TC-END UERROR/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_UNIDEN
T_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_OTHER
Trigger: 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
SND_CAN_LOC_MSG_SUB_ADMIN
Trigger: each time CANCEL LOCATION Trigger: each time CAN MSUB (subscriber is
is sent.
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.
A30862-X1001-C962-2-76-A1
93

Tests
3.3.3
MAP Dialog Interrogation Success Ratio

Description:
This KPI reveals the success ratio of the interrogation procedure.
Per MSC
KPI-formula:
2G+3G
COMPL _ INTERROGAT IONS[MORTR] +

+ COMPL _ INTERROGAT IONS[MICTR ]
KPI =
100%
STARTED _ INTERROGAT IONS[MORTR ] +
+ STARTED _ INTERROGAT IONS[MICTR ]
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
94
A30862-X1001-C962-2-76-A1

Tests
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
Per MSC
KPI-formula:
2G+3G:
White answers:
KPI =
A30862-X1001-C962-2-76-A1
NUM_IMEI_CHECK_WHITE
100
NUM_TOTAL_ START_IMEI _CHECK
95

Tests
Grey answers:
KPI =
NUM_IMEI_CHECK_GREY
100
Black answers:
KPI =
NUM_IMEI_CHECK_BLACK
100
NUM_TOTAL_START_IMEI_CHECK
IMEI Unknown:
KPI =
NUM_IMEI_CHECK_UNKNOWN
100
NUM_TOTAL_START_IMEI_CHECK:
NUM_IMEI_CHECK_WHITE
Trigger: each time CHECK IMEI is sent to Trigger: each time the EIR sends a
the EIR.
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.
Per MSC
96
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
2G,3G :
RECV_AUTH_INF = RECVD_AUTH_INF_TRIPLES_HLR +
RECVD_AUTH_INF_QUINTETS_HLR
KPI =
RECV_AUTH_INF
100%
SEND_PAR_REQ_AUTH_VE C_TO_HLR
MS/UE
BSC
2G-MSC
HLR/AC
If no triplets available -> request some

SEND_AUTHENTICATION_INFO(triplets)
+ SEND_PAR_REQ_AUTH_VEC_TO_HLR
SEND_AUTHENTICATION_INFO(triplets)
+ RECVD_AUTH_INF_TRIPLES_HLR
AUTHENTICATION_REQUEST
AUTHENTICATION_FAILURE
AUTHENTICATION_REQUEST
AUTHENTICATION_FAILURE
If normal authentication : + AUTH_REQ

If authentication after CKSN mismatch :
+ AUTH_REQ_CKSN_MISMATCH
count the appropriate failure counter
+ AUTH_SYNCRON_FAIL_RECEIVED
+ AUTH_MAC_FAIL_RECEIVED
+ AUTH_SRES_MISMATCH
AUTHENTICATION_FAILURE_REPORT
+ AUTH_AUTH_FAIL_REP_REQ
AUTHENTICATION_FAILURE_REPORT
response
+ AUTH_AUTH_FAIL_REP_SUCC
A30862-X1001-C962-2-76-A1
97

Tests
3.3.6
Authentication Failure Ratio (Network authenticates USIM)

Description:
This KPI indicates the failure ratio of USIM authentication procedures performed by
the Network.
authentication procedures divided by the number of authentication attempts.
Per MSC
KPI-formula:
USIM _ AUTH _ RES _ XRES _ MISMATCH

100%
KPI =
AUTH _ REQ _ WITH _ AUTN
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
98
A30862-X1001-C962-2-76-A1

Tests
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.
authentication procedures divided by the number of authentication attempts.
Per MSC
KPI-formula:
3G
AUTH _ SRES _ MISMATCH

100%
KPI =
AUTH _ REQ + AUTH _ REQ _ CKSN _ MISMATCH
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.
A30862-X1001-C962-2-76-A1
99

Tests
AUTH_REQ_CKSN_MISMATCH
Each time AUTHENTICATION REQUEST is sent to the MS after detection of CKSN
mismatch.
Message Flows:
3.4
3.4.1
see chapter before
MGW-KPIs
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.
Per MGW
KPI-formula:
Attempted_ Voice_Calls =
calls_trfo + calls_transc + calls_double_tr + rej_calls
KPI =
rej_calls
100%
Attempted_ Voice_Calls
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.
100
A30862-X1001-C962-2-76-A1

Tests
This KPI reveals the correct working of MGW with respect to error free data call
handling (BS20 t/nt, BS30).
Per MGW
KPI-formula:
Unsucc_Data_Calls =
rej_bs20_t + rej_bs20_n t + rej_bs30_u p + rej_uns_da ta_call
Attempted_ Data_Calls =
calls _ bs20 _ t + calls _ bs20 _ nt + calls _ bs30 _ up +
rej_bs20_t + rej_bs20_n t + rej_bs30_u p + rej_uns_da ta_call
KPI =
Unsucc_Data_Calls
100%
Attempted_ Data_Calls
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.
A30862-X1001-C962-2-76-A1
101

Tests
Per MGW
KPI-formula:
KPI_1 =
rej_bs20_t
100%
calls_bs20_t + rej _ bs20 _ t
KPI_2 =
rej_bs20_n t
100%
calls_bs20_nt + rej_bs20_nt
KPI_3 =
rej_bs30_u p
100%
calls _ bs30 _ up + rej_bs30_up
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.
Per MGW
102
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
KPI =
fail_ann
100%
ins_ann + fail_ann
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.
Per MGW
KPI-formula:
KPI =
fail_tones
100%
ins_tones + fail_tones
Not available.
A30862-X1001-C962-2-76-A1
103

Tests
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.
Per MGW
KPI-formula:
Internal MGW:
KPI =
INVOC_SERV_MULTIPART Y - SUCC_INVOC_MULTIPART Y
100%
INVOC_SERV_MULTIPART Y
External MGW:
KPI =
rej_mpty
100%
mpty + rej_mpty
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.
Per MGW
104
A30862-X1001-C962-2-76-A1

Tests
KPI-formula:
KPI =
IPBCP_Requ est_Incomi ng - IPBCP_Acce pted_Outgo ing

100%
IPBCP_Requ est_Incomi ng
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.
Per MGW
KPI-formula:
KPI =
IPBCP_Requ est_Outgoi ng - IPBCP_Acce pted_Incom ing

100%
IPBCP_Requ est_Outgoi ng
A30862-X1001-C962-2-76-A1
105

Tests
MGW:O
MSC-S:O
MSC-S:T
MGW:T
AddReq (C?,T?,TunOpt=1,...)
Prepare Bearer
AddRsp (C1,T2,TunOpt=1,...)
+ IPBCP_Request_Outgoing
Notify.Ind (C1,T2,BIT,...)
+ IPBCP_Request_Incoming
Notify.Rsp (C1,T2,...)
Tunnel Info Up
Prepare Bearer +
Tunnel Info Down
IAM (ConnFw,Scl,BIT,...)
AddReq (C?,T?,TunOpt=1,BIT,...)
APM (ConFw_Not_SelCodec,ScAcll,BIT,...)
Tunnel Info Up
ModReq (C1,T2,BIT,...)
+ IPBCP_Accepted_Incoming
+ IPBCP_Accepted_Outgoing
ModRsp (C1,T2,...)
Tunnel Info Down
CN_Fast_Forward
12.9.05
Fast Forward Tunneling

MGW:O
MSC-S:O
MSC-S:T
MGW:T
Prepare Bearer
Tunnel Info Up
IAM (ConnBw,Scl,BIT,...)
+
IPBCP_Request_Incom
ing
Prepare Bearer +
Tunnel Info Down
APM (SelectedCodec,ScAcl)
AddReq (C?,T?,TunOpt=1,BIT,...)
ModReq (C1,T2,Codec,...)
Modify Char
ModRsp (C1,T2,...)
APM (BIT,...)
ModRsp (C1,T2,...)
Tunnel Info Up
+
IPBCP_Accepted_Outg
oing
Tunnel Info Down

CN_Fast_Backward
12.9.05
Fast Backward Tunneling
106
A30862-X1001-C962-2-76-A1

Tests
Delayed Forward Tunneling

MGW:O
MSC-S:O
MSC-S:T
MGW:T
Prepare Bearer
IAM (ConnBw,Scl,...)
APM (SelectedCodec,ScAcl)
AddReq (C?,T?,TunOpt=2,Est,...)
ModReq (C1,T2,Codec,...)
Modify Char
ModRsp (C1,T2,...)
Establish Bearer
Tunnel Info Down
APM (BIT,...)
+ IPBCP_Request_Incoming
+ IPBCP_Accepted_Outgoing
Tunnel Info Up
ModRsp (C1,T2,...)
Tunnel Info Up
APM (BIT,...)
ModRsp (C2,T3,...)
CN_Delayed_Backward
Tunnel Info Down
12.9.05
Delayed Backward Tunneling
A30862-X1001-C962-2-76-A1
107

Tests
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.
108
A30862-X1001-C962-2-76-A1

Tests
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 - its 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) :
A30862-X1001-C962-2-76-A1
109

Tests
4.2
call setup (MOC, MTC, MMC)
SMS (MO, MT)
MSC-Handover
LUP
HLR procedures
Important MSC procedures
SCP(MSC)
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:
110
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

Tests
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
Message channel(128 kbit/s)

SCP delay
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]
this improvement in CS5.0 will
result in an delay reduction of ~25
%.
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.248messages :

50 ms ( link-delay+MGW-delay, no
load) + 25 ms (MSC-delay , no
load)
NSL
A30862-X1001-C962-2-76-A1
20% link load, 64 kbit/s
111

Tests
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:
112
A30862-X1001-C962-2-76-A1

Tests
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:
A30862-X1001-C962-2-76-A1
113

Tests
Results:
Scope
Measurement Type
Value
MSC A -> PSTN A

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.
MOC /2G
MOC /2G
MOC /2G
MOC /3G
Authentication time not taken into account.
1.23 s
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;
MSC A -> PSTN A prepaid MOC
Comments:
Scenario (1);
MSC/VLR/SSP one NE;
Assumptions: SCP-delay = 150 ms; Signalling Link: NB with UR=20%;
MSC A -> MSC B using TDM -> PSTN B
Comments:
Scenario (2) ;
MSC B acting as a TMSC;
Assumptions: Signalling Link: NB with UR=20% ;
MSC A -> PSTN A
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.
1.43 s
1.71 s
1.89 s
Preconditions:
Turn MSC feature OACSU (off air call setup) off to avoid early ALERT message;
114
A30862-X1001-C962-2-76-A1

Tests
Scope
MOC /3G
MOC /3G
Measurement Type
Perform a voice call setup to a PSTN within same country;
MSC A -> PSTN A
prepaid MOC
Comments:
Scenario (1);
MSC/VLR/SSP one NE;
Comments:
Scenario (2) ;
Value
2.08 s
2.44 s
PSTN A -> MSC A

Comments:
Scenario (1);
MSC/VLR/GMSC one NE;
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
MTC /2G
MTC /2G
MTC /3G
ISUP:INITIAL ADDRESS MESSAGE(MSISDN) message ( a) and the

submission of the message ISUP ADDRESS COMPLETE (k).
Preconditions:
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;
PSTN B -> MSC B -> MSC A using TDM
Comments:
Scenario (2) ;
PSTN A -> MSC A
Comments:
Scenario (1);
MSC/VLR/GMSC one NE
1.33 s
1.81 s
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
2.39 s
RANAP DIRECT TRANSFER(L3 CONNECT) message.
MTC /3G
MMC /2G
Preconditions:
from normal interrogation is performed;
Perform a voice call setup to a PLMN within same country;
Comments:
Scenario (2) ;
MSC A -> MSC A
Comments:
Scenario (1);
MIC-case;
2.94 s
2.00 s
Def.: A mobile user initiates a voice call to another mobile user of the same
A30862-X1001-C962-2-76-A1
115

Tests
Scope
Measurement Type
Value
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).
MMC /2G
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;
MSC A -> MSC B using TDM
Comments:
Scenario (2);
MSC A -> MSC A
Comments:
Scenario (1) ;
MIC-case;
2.47 s
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
MMC /3G
a RANAP INITIAL UE MESSAGE (L3 Service Request) message and the
2.98 s
submission of the message RANAP DIRECT TRANSFER(L3 Alert).
MMC /3G
SMS /2G
SMS /2G
SMS /3G
SMS /3G
MSC-HO
116
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.;
Comments:
Scenario (2);
SMS-MO
Comments:
MSC=SMS-GMSC; SM-SC is testequipment;
=> messages between MSC and SMS_GMSC dont 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.
SMS-MT
Comments:
MSC=SMS-GMSC=HLR; SM-SC is testequipment
=> messages between MSC and SMS-GMSC dont occur
=> 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.
SMS-MO
SMS-MT
TDM: Intra MSC Intra System Handover GSM

Comments:
3.54 s
0.54 s
1.05 s
n.a.
n.a.
0.81 s
A30862-X1001-C962-2-76-A1

Tests
Scope
MSC-HO
MSC-HO
MSC-HO
MSC-HO
MSC-HO
MSC-HO
Measurement Type
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.
TDM: Inter MSC Intra System Handover GSM
TDM: Inter MSC Intra System Handover UMTS
TDM: Inter MSC Inter System Handover GSM -> UMTS
TDM: Inter MSC Inter System Handover UMTS -> GSM
TDM: Intra MSC Inter System Handover GSM -> UMTS
TDM: Intra MSC Inter System Handover UMTS -> GSM
Value
n.a.
n.a
n.a.
n.a.
n.a.
n.a.
Inter MSC LUP

Comments:
LUP /2G
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.
0.94 s
Precondition:
IMSI att. in old MSC, old LAI stored on SIM, idle mode
3G: LUP(IMSI-Attach) / Intra MSC LUP
Comments:
LUP /3G
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
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).
MSC proc.
MSC proc.
MSC proc.
Interrogation Procedure (SRI)

Comments:
Start Message: SEND_ROUTING_INFO;
End Message: SEND_ROUTING_INFO_ACK;
Note : value from MTC/2G
Send Identification Procedure (LUP)
Comments:
Start Message: SEND_IDENTIFICATION;
End Message: SEND_INDENTIFICATION_ACK;
Note: value from LUP/2G
Send Authentication Procedure (AUTH)
Comments:
Start Message: SEND_AUTHENTICATION_INFO;
End Message: SEND_AUTHENTICATION_INFO_ACK;
0.21 s
0.10 s
34 ms
(MAP-Authentication)
SCP(MSC)
A30862-X1001-C962-2-76-A1
SCP Dialogue for PPS

Comments:
Start Message: INITIAL_DP ( MSC A(SSP) to SCP);
End Message: REQUEST_REPORT_BCSM_EVENT (SCP to MSC A(SSP));
0.31 s
117

Tests
4.6
CS5.0 Transaction Delay in R99 architecture

CS5.0 scenarios /classical architecture :
118
A30862-X1001-C962-2-76-A1

Tests
Results:
Scope
Measurement Type
Value
MSC A -> PSTN A

Scenario (3)
MOC/2G
MOC/2G
MOC/2G
MOC/3G
MOC/3G
MOC/3G

Preconditions:
MSC/VLR one NE;
MSC A -> PSTN A prepaid MOC
Scenario (3)
MSC/VLR/SSP one NE;
Scenario (4)
MSC A -> PSTN A
Scenario (3)
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:
MSC A -> PSTN A
prepaid MOC
Scenario (3)
MSC/VLR/SSP one NE;
Scenario (4)
0.88 s
1.07 s
1.35 s
1.57 s
1.77 s
2.17 s
PSTN A -> MSC A

Scenario (3)
ISUP:INITIAL ADDRESS MESSAGE(MSISDN) message ( a) and the
MTC/2G
submission of the message ISUP ADDRESS COMPLETE (k).
1.20 s
MTC/2G
Preconditions:
from normal interrogation is performed (MAP SEND ROUTING INFORMATION
procedure;
1.67 s
A30862-X1001-C962-2-76-A1
119

Tests
Scope
MTC/3G
Measurement Type
Value
Scenario (4)
PSTN A -> MSC A
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
MTC/3G
Preconditions:
from normal interrogation is performed;
Scenario (4)
1.44 s
2.00 s
MSC A -> MSC A

Scenario (3)
MIC-case;
MMC/2G
MMC/2G
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:
procedure;
Scenario (4)
MSC A -> MSC A
Scenario (3)
MIC-case;
1.69 s
2.17 s
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
MMC/3G
a RANAP INITIAL UE MESSAGE (L3 Service Request) message and the
2.86 s
MMC/3G
120
Preconditions:
performed.;
Scenario (4)
3.41 s
A30862-X1001-C962-2-76-A1

Tests
Scope
Measurement Type
Value

SMS /2G
SMS /2G
SMS /3G
SMS /3G
SMS-MO
Comments:
MSC=SMS-GMSC; SM-SC is testequipment;
=> messages between MSC and SMS_GMSC dont occur
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.
SMS-MT
Comments:
MSC=SMS-GMSC=HLR; SM-SC is testequipment
=> messages between MSC and SMS-GMSC dont occur
=> 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.
SMS-MO
SMS-MT
0.54 s
1.05 s
n.a.
n.a.
TDM: Intra MSC Intra System Handover GSM

Comments:
MSC-HO
/2G
MSC-HO
/2G
MSC-HO
/3G
MSC-HO
/2G3G
MSC-HO
/2G3G
MSC-HO
/2G3G
MSC-HO
/2G3G
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
TDM: Inter MSC Intra System Handover GSM
n.a.
TDM: Inter MSC Intra System Handover UMTS
n.a.
TDM: Inter MSC Inter System Handover GSM -> UMTS
n.a.
TDM: Inter MSC Inter System Handover UMTS -> GSM
n.a.
TDM: Intra MSC Inter System Handover GSM -> UMTS
n.a.
TDM: Intra MSC Inter System Handover UMTS -> GSM
n.a.
Inter MSC LUP

Comments:
LUP /2G
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.
0.94 s
Precondition:
IMSI att. in old MSC, old LAI stored on SIM, idle mode
LUP(IMSI-Attach) / Intra MSC LUP
Comments:
LUP /3G
A30862-X1001-C962-2-76-A1
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
121

Tests
Scope
Measurement Type
Value
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).
MSC proc.
MSC proc.
MSC proc.
Interrogation Procedure (SRI)

Comments:
Start Message: SEND_ROUTING_INFO;
End Message: SEND_ROUTING_INFO_ACK;
Note : value from MTC/2G
Send Identification Procedure (LUP)
Comments:
Start Message: SEND_IDENTIFICATION;
End Message: SEND_INDENTIFICATION_ACK;
0.21 s
0.10 s
Note: value from LUP/2G

Send Authentication Procedure (AUTH)
Comments:
Start Message: SEND_AUTHENTICATION_INFO;
End Message: SEND_AUTHENTICATION_INFO_ACK;
34 ms
(MAP-Authentication)
SCP(MSC)
122
SCP Dialogue for PPS

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

Tests
4.7
CS5.0 Transaction Delay in R4 architecture

CS5.0 scenarios /separated architecture
A30862-X1001-C962-2-76-A1
123

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

Tests
Results:
Scope
Measurement Type
Value
MGW A -> PSTN A

Comments:
Scenario (5)
MOC /2G
1.17 s
Preconditions:
MOC /2G
MOC /2G
MOC /2G
MOC /2G
MOC /2G
MOC /2G
MOC /2G
MOC /2G
MSC/VLR one NE;
MGW A -> PSTN A
Comments:
Scenario (5a)
MSC with MCP
MGW A -> PSTN A
Scenario (5)
Mc-IF via STP
MGW A -> MGW B using TDM -> PSTN B
Scenario (6)
#7-Loop => 510 ms delay
MGW A -> MGW B using IP(GE) -> PSTN B Fast Forward Bearer Establishment
Scenario (6)
Scenario (7)
MSC/STP=MSC A; MSC B = TMSC;
Scenario (7a)
MSC with MCP
Scenario (7)
Scenario (7a)
MSC with MCP
MGW A -> PSTN A
Scenario (5)
0.82 s
1.23 s
2.22 s
3.53 s
2.19 s
1.84 s
3.01 s
2.66 s
MOC /3G
MOC /3G
MOC /3G
MOC /3G
MOC /3G
A30862-X1001-C962-2-76-A1
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:
MGW A -> PSTN A
Scenario (5a)
MSC with MCP
Scenario (6)
Scenario (6)
Scenario (7)
1.71 s
1.07 s
2.76 s
4.01 s
2.81 s
125

Tests
Scope
MOC /3G
MOC /3G
MOC /3G
MOC /3G
Measurement Type
Value
MSC/STP=MSC A; MSC B = TMSC;

Scenario (7a)
MSC with MCP
Scenario (7)
Scenario (7a)
MSCs with MCP
Scenario (7)
additional: CMN between the two MSC-Ss
2.17 s
3.56 s
2.92 s
4.04 s
PSTN A -> MGW A

Scenario (5)
MTC /2G
MTC /2G
MTC /2G
MTC /2G
MTC /2G
MTC /2G
MTC /2G
MTC /2G
ISUP:INITIAL ADDRESS MESSAGE(MSISDN) message ( a) and the submission

of the message ISUP ADDRESS COMPLETE (k).
Preconditions:
It is assumed that during the call setup no additional HLR inter-working apart from
normal interrogation is performed (MAP SEND ROUTING INFORMATION
procedure;
PSTN A -> MGW A
Scenario (5a)
MSC with MCP
Scenario (6)
Scenario (6)
Scenario (7)
Scenario (7a)
MSC with MCP
Scenario (7)
Scenario (7a)
MSC with MCP
PSTN A -> MGW A
Scenario (5)
MSC/VLR/GMSC one NE
1.41 s
0.93 s
2.46 s
4.29 s
2.43 s
1.95 s
3.78 s
3.31 s
Def.: A landline user initiates a voice call (AMR12.2) to a mobile user (MTC MTC /3G
Mobile Terminated Call). The call setup time is the interval between the reception
1.59 s

Preconditions:
It is assumed that during the call setup no additional HLR inter-working apart from
normal interrogation is performed;
126
A30862-X1001-C962-2-76-A1

Tests
Scope
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
MTC /3G
Measurement Type
PSTN A -> MGW A
Scenario (5a)
MSC with MCP
Scenario (6)
Scenario (6)
Scenario (7)
Scenario (7)
additional: 1 TMSC between A and B side
Scenario (7)
additional: 2 TMSCs between A and B side
Scenario (7)
additional: 1 STP between A and B side
Scenario (7)
additional: 2 STP between A and B side
Scenario (7a)
MSC with MCP
2 server, 2 MGWs (Scenario 7)
Scenario (7a)
MSC with MCP
Scenario (7)
additional: CMN between the two MSCSs
Value
1.01 s
2.64 s
4.48 s
2.69 s
3.25 s
3.80 s
2.77 s
2.85 s
2.11 s
3.97 s
3.39 s
4.45 s
MGW A -> MGW A

Scenario (5)
MIC-case;
MMC /2G
MMC /2G
MMC /2G
MMC /2G
A30862-X1001-C962-2-76-A1
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:
procedure;
MGW A -> MGW A
Scenario (5a)
MSC with MCP
MGW A -> MGW B using TDM
Scenario (7)
2.29 s
1.61 s
2.76 s
4.15 s
127

Tests
Scope
Measurement Type
Value
Scenario (7)
MGW A -> MGW A
Scenario (5)
MIC-case;
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
MMC /3G
RANAP INITIAL UE MESSAGE (L3 Service Request) message and the
3.16 s
MMC /3G
MMC /3G
MMC /3G
MMC /3G
MMC /3G
MMC /3G
HO
HO
HO
HO
HO
Preconditions:
performed.;
MGW A -> MGW A
Scenario (5a)
MSC with MCP
2 server , 2 MGWs (Scenario 7)
Scenario (7)
additional: 1 TMSC between A and B side
Scenario (7)
additional: 2 TMSCs between A and B side
MGW A -> MGW B using IP(GE) using Fast Forward Bearer Establishment
Scenario (7)
MGW A -> MGW B using IP(GE) using Fast Forward Bearer Establishment
Scenario (7)
additional: CMN between the two MSCSs
Intra MGW HO
Scenario (5)
Inter_MGW_Intra_MSC-S
Scenario (6)
Nb over TDM ;
Inter_MGW_Intra_MSC-S
Scenario (6)
Nb over IP ;
Basic_Inter_MSC-S_HO
Scenario (7)
Nb over TDM ;
Basic_Inter_MSC-S_HO
Scenario (7)
Nb over IP ;
2.02 s
3.74 s
4.31 s
4.87 s
5.03 s
5.51 s
n.a.
n.a.
n.a.
n.a.
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.
128
A30862-X1001-C962-2-76-A1

Tests
Abbreviations
ACK
AFI
APN
BSS
BSSGP
CMN
CN
CPU
CS
DL
GGSN
GMSC
GPRS
GR
GSM
GTP-U
HLR
IMEI
IMSI
IP
IPS
ITU
ITU-T
IUS
IWMSC
KPI
LA
LLC
MM
MP
MS
MSC
NSL
PDP
PDU
PM
PMM
PO
PS
RA
RAB
RAN
RANAP
RAU
RNC
RNS
RRC
SGSN
SIM
SMS
SP
SRNS
A30862-X1001-C962-2-76-A1
Acknowledge
Available for First Inspection
Access Point Name
Base Station System
Base Station System GPRS Protocol
Call Mediation Node
Core Network
Central Processing Unit
Circuit Switched
Downlink
Gateway GPRS Support Node
Gateway Mobile Service Switching Center
General Packet Radio Service
GPRS Release
Global system for mobile communication
GTP User Plane
Home Location Register
International Mobile Equipment Identity
International Mobile Subscriber Identity
Internet Protocol
Intelligent Packet Solution
International Telecommunication Union
Telecommunications Standardization Section of ITU
Inspected Updated and Stored
Interworking MSC
Key Performance Indicator
Location Area
Logical Link Control
Mobility Management
Main Processor
Mobile Station
Mobile-services Switching Center
Narrowband Signalling Link
Packet Data Protocol
Packet Data Unit
Performance Management
Packet Mobility Management
Packet Oriented
Packet Switched
Routing Area
Radio Access Bearer
Radio Access Network
RAN Application Part
Routing Area Update
Radio Network Controller
Radio Network Subsystem
Radio Resource Control
Serving GPRS Support Node
GSM Subscriber Identity Module
Short Message Service
Service Processor
Serving Radio Network System
129

Tests
SSG
TC
UCR
UE
UL
UMTS
USIM
UTRAN
VLR
130
Service Selection Gateway

Traffic Class
UMTS Core Release
User Equipment
Uplink
Universal Mobile Telecommunication System
Universal Subscriber Identity Module
UMTS Terrestrial Radio Access Network
Visitor Location Register
A30862-X1001-C962-2-76-A1

CS Core KPIs For Offer and Field Acceptance Test

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS Core KPIs For Offer and Field Acceptance Test

Uploaded by

Copyright:

Available Formats

s

Robert Kirsch, Network Engineering SN MN PG NT NE 4

Measurements in Offer Process and Field

Copyright (C) Siemens AG 2006

Measurements in Offer Process and Field Acceptance

Reason for Update

Update of the CS4.0 Version of this document;

Update of the IUS Version;

Measurements in Offer Process and Field Acceptance

Core Network ................................................................................................10

Measurements in Offer Process and Field Acceptance

Inter- MSCB- Handover Success Ratio ........................................................69

Core-Part of Transaction Delay...................................................................108

Measurements in Offer Process and Field Acceptance

List of Figures and Tables

KPI for Offer Process and Field Acceptance Test

UMTS End-to-End Key Performance Indicators for Offer

[CNT_descr_CS40 ] Traffic and Performance Data

Media Gateway System Architecture

Description of Key Performance Indicators (KPI)

Measurements in Offer Process and Field Acceptance

Description of Key Performance Indicators (KPI)

[PERF_DES_CS40] Performance Description CS4.0

Circuit Switched Core Network Architecture (CS-CNA) CS4.0

ITU-T Recommendation E.543, Grades of service in digital

3GPP TS 43.005, V5.x.x, Technical performance objectives

3GPP TS 23.107, Quality of Service (QoS) concept and

3GPP TS 29.414, Core network Nb data transport and transport

3GPP TS 32.401, 5.x.x,

Measurements in Offer Process and Field Acceptance

The definition of the KPI

Measurements in Offer Process and Field Acceptance

Measurements in Offer Process and Field Acceptance

From CS4.0 to CS5.0

Measurements in Offer Process and Field Acceptance

CS5.0 MSC Server

CS5.0 Combined MSC

Measurements in Offer Process and Field Acceptance

Core KPI Overview

Measurements in Offer Process and Field Acceptance

Grade of Service Measurements

Areas of Impact to KPI Target Values

Measurements in Offer Process and Field Acceptance

System performance (behavior of unloaded and loaded network elements)

System configuration (hardware and software configuration of network elements,

Network design and topology

Measurements in Offer Process and Field Acceptance

KPI Measurement Conditions

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,

Load on signaling links < 0.2 Erlang

Measurements in Offer Process and Field Acceptance

Furthermore the following network parameterization is required for the tests:

No Mobile Number Portability

Partly separately for GSM and UMTS

No optimized dynamic Routing

with prepaid/postpaid services (which increases the load dependent on the

without IMEI interworking

subscriber / LUP state : attached

with Gs interworking (network operation mode I)

No unconditional call forwarding