information, traffic data administration, traffic measurement, siemens

Information

Traffic Data Administration

Traffic Measurement

A50016-D1109-G801-6-7618

2 A50016-D1109-G801-6-7618

Traffic Measurement InformationTraffic Data Administration

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to complywith the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Spannung. Einige Teilekönnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen undSachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert undwartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerätemüssen die zutreffenden Sicherheitsbestimmungen erfüllen.

Trademarks:

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

Copyright (C) Siemens AG 2002.

Issued by Information and Communication MobileHofmannstraße 51D-81359 München

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

A50016-D1109-G801-6-7618 3

InformationTraffic Data Administration

Traffic Measurement

Reason for UpdateSummary:

This document is updated with counters missing in chapter 15.

Details:

Chapter/Section Reason for Update

Chapter 15.3.1 Counters missing from previous issue: number-

OfTransitMessagesProcessed; all ludts - parame-

ters; segmentationFailed.

Issue HistoryIssue

Number

Date of issue Reason for Update

1 10/2000 New version.

2 2/2001 Specific MTP and SCCP counters.

3 10/2001 Fault Report CLO 178

5 02/2002 Missing MP counters

6 02/2002 Missing SS7-specific Traffic Measurement Counters

4 A50016-D1109-G801-6-7618


A50016-D1109-G801-6-7618 5


Traffic Measurement

This document consists of a total of 188 pages. All pages are issue 6.

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1 Methods of Determining Grade of Service Data . . . . . . . . . . . . . . . . . . . . . 142.2 Collection of Mobile-specific Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3 Traffic Measurement Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3 Traffic Measurement in the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.1 Basic counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.1.1 Miscellaneous part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1.2 Time/duration related part (1) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.3 Time/duration related part (2) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.1.4 Load and demand related part (1) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.1.5 Load and demand related part (2) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.1.6 Load and demand related part: LTG pooling . . . . . . . . . . . . . . . . . . . . . . . 313.1.7 Load and demand related part: Gs interface . . . . . . . . . . . . . . . . . . . . . . . 323.1.8 Load and demand related part: Location services . . . . . . . . . . . . . . . . . . . 333.1.9 Grade of service related part: unsuccessful calls . . . . . . . . . . . . . . . . . . . . 353.1.10 Grade of service related part: unsuccessful LTG pooling . . . . . . . . . . . . . . 393.1.11 Grade of service related part: successful call establishment . . . . . . . . . . . 403.1.12 Grade of service related part: answered calls. . . . . . . . . . . . . . . . . . . . . . . 443.2 Handover Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.2.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.2.2 Grade of service related part: handover establishment . . . . . . . . . . . . . . . 483.2.3 Grade of service related part: successful completed handovers . . . . . . . . 493.3 Short Message Service Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493.3.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503.3.2 Grade of service related part: successful services . . . . . . . . . . . . . . . . . . . 503.3.3 Grade of service related part: unsuccessful services . . . . . . . . . . . . . . . . . 513.4 ASCI Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4 Traffic Measurement for SS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.1 Supplementary Service: Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 584.2 Supplementary Service: Call Barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.3 Special Services: number of invocations . . . . . . . . . . . . . . . . . . . . . . . . . . 594.4 Special Services: number of successfully completed invocations . . . . . . . 60

5 Cell-related Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625.2 Handover part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6 Traffic-structure Measurement for HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7 Traffic Measurement in IWE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667.2 Grade of service related part: unsuccessful attempts. . . . . . . . . . . . . . . . . 687.3 Grade of service related part: forced released calls . . . . . . . . . . . . . . . . . . 69

6 A50016-D1109-G801-6-7618


7.4 Grade of service related part: holding times . . . . . . . . . . . . . . . . . . . . . . . . 717.5 Grade of service related part: upgrading and downgrading . . . . . . . . . . . . . 737.6 Alternate speech fax 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

8 Traffic Measurement in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758.1 Installation related part. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758.2 Load and grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768.3 Security functions related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818.4 External interworking related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848.5 Combined paging and combined location update part. . . . . . . . . . . . . . . . . 87

9 Location-area Related Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . 89

10 Traffic Measurement in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9110.1 Structure and Installation Related Part (1) of (3) . . . . . . . . . . . . . . . . . . . . . 9110.2 Structure and Installation Related Part (2) of (3) . . . . . . . . . . . . . . . . . . . . . 9310.3 Structure and Installation Related Part (3) of (3) . . . . . . . . . . . . . . . . . . . . . 9910.4 Mobility Management/Call Handling/Authentication. . . . . . . . . . . . . . . . . . 10010.4.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10010.4.2 Grade of service related part for mobility management . . . . . . . . . . . . . . . 10310.4.3 Grade of service related part for call handling . . . . . . . . . . . . . . . . . . . . . . 10510.4.4 Grade of service related part for subscriber data. . . . . . . . . . . . . . . . . . . . 10710.5 Subscriber Controlled Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10810.5.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10810.5.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11010.6 Short Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11310.6.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11310.6.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11310.7 Data Service with GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11410.7.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11410.7.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11510.8 Overload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

11 Traffic Measurement in AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

12 Traffic Measurement in EIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11912.1 Structure and installation related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11912.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

13 Conventional SSS Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 12113.1 Trunk Group Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12213.1.1 Index 1: seizure and traffic volume data . . . . . . . . . . . . . . . . . . . . . . . . . . 12213.1.2 Index 2: additional trunk group data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12313.1.3 Index 3: data on successful calls without reaching their destination . . . . . 12413.1.4 Index 4: data on refused calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12513.1.5 Index 5: data on refused calls at CCS7 trunk groups. . . . . . . . . . . . . . . . . 12613.1.6 Index 6,7: data of non-hierarchical trunk groups . . . . . . . . . . . . . . . . . . . . 12613.2 Destination Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12713.3 CP Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13013.4 LTG Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13013.5 GP Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

A50016-D1109-G801-6-7618 7


Traffic Measurement

13.6 DLU Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13213.7 Announcement Group Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . 13413.8 PBX Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13513.8.1 Service-related data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13613.8.2 Service-independent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

14 MP Load Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13814.1 Measurement Object for VCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13814.2 Measurement Object for MH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

15 SS7-specific Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14215.1 MTP Measurement (SSNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14215.1.1 Net element measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14415.1.2 Signaling point utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 14515.1.3 Obligatory signaling point utilization measurement. . . . . . . . . . . . . . . . . . 14515.1.4 Network MSU measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14515.1.5 Signaling point measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14515.1.6 Link set duration measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14515.1.7 Destination point measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14615.1.8 Obligatory link duration measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 14615.1.9 Link duration measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14715.1.10 Obligatory link utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 14715.1.11 Link utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14815.1.12 Link congestion measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14915.2 CCS7-specific Measurement (CCNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 14915.2.1 CCS7 Route Set Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15015.2.2 CCS7 Link Set Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15115.2.3 CCS7 Grade of Service Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 15115.2.4 CCS7 Link load Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15215.2.5 CCS7 Discarded MSU Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15315.2.6 CCS7 Measurement of all MSUs Received, Transmitted, Forwarded . . . 15415.2.7 Measuring Statistics Data at SSP/SCP Interface . . . . . . . . . . . . . . . . . . . 15415.3 SCCP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15515.3.1 SCCP Counters with SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15615.3.1.1 SCCP error performance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 15615.3.1.2 SCCP utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15815.3.1.3 SCCP quality of service measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 15915.3.2 SCCP Counters with CCNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16015.3.2.1 SCCP utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16015.3.2.2 SCCP quality of service measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 16115.3.2.3 SCCP error performance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 16215.4 TCAP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

16 Mobile-Specific Traffic Supervision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

17 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

18 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

8 A50016-D1109-G801-6-7618


IllustrationsFig. 2.1 Grade of service model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Fig. 3.1 Traffic types in scope of the observed MSC . . . . . . . . . . . . . . . . . . . . . . 20

A50016-D1109-G801-6-7618 9


Traffic Measurement

TablesTab. 2.1 Traffic measurement jobs in D900/D1800/D1900 . . . . . . . . . . . . . . . . . 17

Tab. 14.1 Object classes for MP load measurements . . . . . . . . . . . . . . . . . . . . . 138

Tab. 15.1 Object classes for MTP measurements . . . . . . . . . . . . . . . . . . . . . . . . 143

Tab. 15.2 Measurement for CCS7 signaling data . . . . . . . . . . . . . . . . . . . . . . . . 149

Tab. 15.3 Object classes for SCCP measurements. . . . . . . . . . . . . . . . . . . . . . . 156

Tab. 16.1 Traffic counter functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Tab. 16.2 Particular calculations with OMT output. . . . . . . . . . . . . . . . . . . . . . . . 173

10 A50016-D1109-G801-6-7618


A50016-D1109-G801-6-7618 11


Traffic Measurement

1 IntroductionOptimum traffic conditions can be achieved in the Public Land Mobile Network (PLMN)thanks to an increasingly sophisticated range of variations in network design and trafficrouting. This involves the increased intermeshing of the network nodes and thus a great-er planning effort. Careful, future-oriented planning makes it possible, in the majority ofcases, to avoid traffic bottlenecks and overload situations, even in the face of major traf-fic fluctuations.

Traffic data acquisition is therefore of decisive importance for the telecommunicationscarriers with respect to• traffic handling

Traffic bottlenecks can be detected as early as possible.A consistently high quality of service can be ensured, resulting from the grade of ser-vice, call processing performance and transmission quality.

• traffic forecastingNetwork nodes can be composed for the long-term, demand-oriented expansion ofthe networks.

Contrary to the systems of older technology, the D900/D1800/D1900 system does notrequire any special equipment for traffic data acquisition. A broad range of intra-systemfunctions is available for the tasks at hand. These functions collect and process trafficdata from all parts of the network nodes and trunk groups. For instance, the call process-ing programs include traffic data registration and specific programs record traffic mea-surement data.

The numerous tasks in traffic data acquisition are subdivided into two areas for the pur-pose of more convenient management and handling:– traffic supervision– traffic measurement

Traffic supervision

Traffic supervision implies that traffic flows, losses in the trunk network, and other vari-ables which affect the quality of service must be determined. To provide the requiredquality of service, the telecommunications equipment in operation at any time musttherefore be supervised, continuously or periodically. Therefore, traffic data for the op-eration is recorded and call processing traffic of the network nodes and the switchingnetwork is analyzed.

The grade of service is affected by the modes of operation (e.g. a delay or a loss ) as-sociated with the dimensioning of the serving trunk groups. To ensure an adequategrade of service for switching operations in the individual network nodes, softwarecounts are periodically compared with predefined threshold values. Should thesethreshold values be exceeded, messages and data indicating any irregularities in callprocessing are output. A result is, for instance, that faulty trunks (transmission paths)can be blocked at short notice, or traffic overloads can be anticipated and prevented,e.g. by traffic management measures.

12 A50016-D1109-G801-6-7618


Traffic measurement

Traffic data acquisition is also used to verify whether the traffic data taken as a planningbasis is still correct. Therefore, the dimensioning of trunk groups is an important plan-ning task. To ensure sufficient traffic handling capacity, the grade of service in the busyhour is prespecified when trunk groups have to be expanded or added.

Traffic has to be processed not only by trunk groups and switching networks, but alsoby all the control devices associated with them. It is essential to know how often the de-vices will be used within a given time. A gauge of this demand is the mean number ofcalls offered per unit of time, the number of call attempts during the busy hour (i.e., theBHCA value), the number of successful switching network (SN) through-connections.Measurements of these traffic variables indicate the call load on the call processors andon the control devices, and the requirements for the switching network.

Traffic measurement registers events and duration of states in the system or systemparts. Hence, basic data for the long-term expansion of call-processing equipment isavailable to meet a growth in telecommunications traffic over time. Since the traffic datafrom the peak traffic periods must be used as the basis for planning work, traffic mea-surements must be carried out during these periods.

Traffic measurement in D900/D1800/D1900

Traffic data acquisition creates the necessary conditions for reliable traffic planning,such as– a prediction of the traffic development, which forms the basis for expansion of the

call-processing equipment and the network.– the assessment and supervision of past or future investments.– the monitoring of current traffic in order to ensure switching operation and constant

quality of service. This means: recognition of traffic bottlenecks during the switchingoperation and also of insufficiently used or unused capacity.

Various types of data are collected independently of each other in theD900/D1800/D1900 system. They are collected in and by every system element and forevery main unit or logical/functional configuration (e.g. entire MSC), trunk groups, loca-tion area or cells). Therefore, a number of counters for the registration of events in thenetwork elements are implemented. So, all kinds of traffic data are collected from thetraffic flows between these elements, i.e. specific messages being exchanged within thenetwork are counted. The counters are continuously updated by the call-processing SW.As soon as a traffic measurement job is started, the results wil be processed to the mag-netic disk. They can then be used to calculate the load, the utilization and the grade ofservice of the system.

Traffic measurement jobs in the D900/D1800/D1900 system are subdivided into mobile-specific, conventional, and CCS7-specific traffic measurement jobs.

A50016-D1109-G801-6-7618 13


Traffic Measurement

• Mobile-specific traffic measurementUnlike the PSTN, ISDN, a PLMN consists of additional, mobile-specific units suchas VLR, HLR, AC, IWE, EIR. The traffic measurement data of these units must beregistered.Because a PLMN deals with call processing and transmission in a different way thana PSTN/ISDN does, data must be recorded for modified or additional mobile-specificfunctions or procedures. Examples of mobility events are:– location update,– authentication,– paging,– roaming,– handover.

• Conventional traffic measurementConventional traffic measurement prepares jobs that register data on user traffic orsignaling traffic. Some of the functions measured in the course of such jobs are han-dled as the PLMN; within this respect, only the MSC takes part in user traffic. Con-sequently, some of these traffic measurement jobs are relevant in the PLMN.Examples of such events are:– start of call setup in a GMSC,– connection with announcement groups.Measurements that effect the PBXs are typical for a combined switching center.

• CCS7-specific traffic measurementAS for the PSTN/ISDN, signaling data traffic applies to CCS7 routes to destinationpoint codes (DPCs), the load on signaling links, the transfer of message signalingunits, the availability of routing areas. The traffic measurement that prepares jobs toregister these signaling data is relevant in the PLMN too.

For dimensioning the whole PLMN, traffic measurement data on manufacturer-specificsubunits and auxiliary units (e.g. use of conference modules) must also be registered.Nevertheless, this data is not dealt with in the document

The counters from this document marked with * are described by means of a call flow ina separate document “Traffic Counter Description”. In this way it is possible to exactlyshow the point in the call flow where the counter is triggered by a specific message.

14 A50016-D1109-G801-6-7618


2 ImplementationTraffic data acquisition in all parts of the PLMN nodes and trunk groups is important toensure a consistently high quality of service in traffic handling. This encompasses:– the grade of service– the call processing performance– the transmission quality

A broad range of intra-system functions is available for the tasks at hand. To this end,the call processing programs from all units integrate traffic data registration by which itis possible to continuously count traffic-affecting messages being exchanged within thenetwork. This data is registered in measurement counters.

The Traffic Measurement document describes all possible counters being provided forthe registration of events all over the D900/D1800/D1900 system. By carrying out theappropriate traffic measurement jobs, relevant data will be collected.The document Monitoring of Traffic Counters contains information and commands fortraffic supervision. In this way the operator is able to get knowledge of:– traffic flows between the network nodes;– losses in the trunk network;– variables affecting the quality of service.

2.1 Methods of Determining Grade of Service DataThe model in Fig. 2.1 is used for obtaining the data for grade of service measurement.According to this model, requests and attempts for certain services and system func-tions are offered to or generated by the PLMN and its units. These requests and at-tempts can be generated either by the mobile subscriber (e.g. by raising the handset) orby the system (e.g. by starting a handover or location update).

Fig. 2.1 Grade of service model

requestsattempts

unsuccessfully terminated

successfully completed

system behavior

behavior of mobile subscriber

reasons relating to the user/the network

A50016-D1109-G801-6-7618 15


Traffic Measurement

The requests and attempts bring about activities in the system which are carried out witha certain grade of service. Some attempts are completed successfully, others are termi-nated without success (loss, abandonment or rejection).• Successfully completed actions can lead to further activities (e.g. successful inter-

rogation leads to call setup to the visited MSC).• Unsuccessful attempts can be offered again or automatically repeated by the sys-

tem. A distinction can be made between the following groups of unsuccessfully ter-minated attempts.– mobile subscriber behavior

(e.g. replacing handset during call setup, incorrect dialing)– system behavior

(e.g. lack of resources, overload, technical faults)– user or network related reasons

(e.g. certain features or options are blocked or not provided, subscriber blockedby the operating company)

Certain errors within the grade of service measurement jobs are derived from the errorcauses within the messages of the protocols used (e.g. MAP, BSSAP error causes).Since these causes are very detailed, they are often summarized in a number ofcounters.

Two release events can be distinguished.– The release event detected by the call processing software of the LTG’s group pro-

cessor is sent as a reason for call failure (RCF) in the release message from theLTGs to the CP.

– The release event detected by the call processing software of the coordination pro-cessor (CP) is sent as a reason for call termination (RCT) in a command (e.g.) to theLTGs.

Some of the data recorded via load and seizure-related traffic measurement jobs is alsonecessary for grade of service measurement (e.g. the number of calls offered is neces-sary for traffic load and, together with successfully completed calls, for grade of servicemeasurements). Load and seizure-related traffic measurement and grade of servicemeasurement can thus be carried out in one measurement job.

2.2 Collection of Mobile-specific DataTo collect mobile-specific traffic data, the operator has to activate a measurement jobby an MML command (see ). Appropriate commands exist to collect the relevant datafor the measurement of the traffic load and grade of service in the differentD900/D1800/D1900 units.– in the MSC– in the IWE– in the VLR– in the HLR– in the AC– in the EIR

There are also commands to collect data regarding the traffic in the radio cells and thelocation areas. Even the data collection regarding invocations of call forwarding and callbarring can be started with an MML command.

The operator has to specify within the command– the objects to be measured,

16 A50016-D1109-G801-6-7618


– the recording period, and– the output device.

There are three types (with the same format) to output files onto magnetic disk. The fileformat is fully described in an appropriate document that will be delivered with the sys-tem SW load. It describes the output of the measured data such that it is possible to cre-ate postprocessing programs for this data.• A time-controlled measurement job with output to individual files being created and

assigned to the measurement job.Such file can record all the data arising during traffic measurement (one file per job,one traffic measurement type).

• Continuous measurement job with output to day files collecting only the data relatingto one measurement day.Such file is assigned to only one specific measurement job, i.e., only one traffic mea-surement type per file. Up to seven files can exist simultaneously for each job. If theoperator does not delete the file after it is evaluated, it is overwritten on the sameday of the following week.

• Continuous measurement job with output to cyclic files, collecting only data relatedto each measurement period of 15 minutes.The operator can optionally assign such file to any created traffic measurement jobfrom Tab. 2.1, except for REC INSTAT for which no output to a cyclic file can be se-lected. For each started measurement type, the proper results are then written intoa separate cyclic file on disk every 15 minutes.

Usually the measurement data is taken continuously but is processed only after the op-erator has entered an MML command. The CP main memory reads the data of the re-spective counters and outputs it to specified devices. This takes place every fifteenminutes during the active traffic measurement intervals, irrespective of the file type.

Subsequently, MML command TRANS FILE allows to activate the transfer of the mea-surement data from magnetic disk to tape, either locally at the CP or centrally at theO&M processor (OMP).– Individual files can only be transferred at the end of a measurement job or if the job

is aborted.– Day files can be transferred after the day concerned.– Cyclic files can be transferred at any moment of the day. To avoid losing measure-

ment data, it may be kept on disk for a maximum of 2 days only before being trans-ferred to tape.

A50016-D1109-G801-6-7618 17


Traffic Measurement

2.3 Traffic Measurement JobsTab. 2.1 gives an overview of the traffic measurement jobs integrated in theD900/D1800/D1900 system and refers to the sections with a detailed explanation.

Recording job Measurement designation Chapter

Mobile-specific traffic measurement:

REC MSC MSC Traffic Measurement 3

REC SSERV Traffic Measurement for Supplementary Services(SS)

4

REC INTCELL (IN-TCREL)

Cell-related Traffic Measurement 5

REC INTCELL(HOTRFS)

Traffic-Structure Measurement for Handover 6

REC IWE Traffic Measurement in IWE 7

REC VLR VLR Traffic Measurement 8

REC LOCAREA Location-Area related Traffic Measurement 9

REC HLR HLR Traffic Measurement 10

REC AC AC Traffic Measurement 11

REC EIR EIR Traffic Measurement 12

Conventional SSS traffic measurement

REC TGRP Trunk Group Traffic Measurement 13.1

REC DEST Destination Traffic Measurement 13.2

REC CP CP Traffic Measurement 13.3

REC LTG LTG Traffic Measurement 13.4

REC GP GP Traffic Measurement 13.5

REC DLU DLU Traffic Measurement 13.6

REC ANGRP Announcement Group Traffic Measurement 13.7

REC PBX PBX Traffic Measurement 13.8

CR MPLDME MP Load Measurements 14

CCS7-specific traffic measurement

REC C7RSET CCS7 Route Set Measurement 15.2.1

REC C7LSET CCS7 Link Set Measurement 15.2.2

REC C7GOS CCS7 Grade of service Measurement 15.2.3

REC C7LLOAD CCS7 Link Load Measurement 15.2.4

REC C7DCDMSU CCS7 Discarded MSU Measurement 15.2.5

REC C7MSU CCS7 Measurement of all MSUs Received, Transmit-ted, Forwarded

15.2.6

Tab. 2.1 Traffic measurement jobs in D900/D1800/D1900

18 A50016-D1109-G801-6-7618


REC INSTAT Measuring Statistics Data at SSP/SCP Interface 15.2.7

REC SCTC SCCP/TCAP Traffic Measurement 15.3.2/15.4

Recording job Measurement designation Chapter

Tab. 2.1 Traffic measurement jobs in D900/D1800/D1900

A50016-D1109-G801-6-7618 19


Traffic Measurement

3 Traffic Measurement in the MSCIn order to measure traffic in the entire MSC, a lot of data concerning the– traffic load,– traffic grade of service,– features

can be recorded by counters.

This data is collected during the main tasks controlled by the MSC, such as:– call setup for speech and data,– handover,– short message service.

Traffic measurement can be started in the MSC by entering the command REC MSC inwhich one can additionally specify:– the basic counters– the handover counters– the short message service (SMS) counters– the advanced speech call items (ASCI) counters

Traffic types

Within the MSC basic traffic measurement part, most of the counters can be differenti-ated by several traffic types . The traffic types are within scope of the observed MSC(see Fig. 3.1) and inform about the origin and the destination of the call.

The observed MSC detects whether the call to be handled has been either originated inits own area, or transmitted by another exchange. From this point of view one can dis-tinguish:• mobile originating traffic (MORTR)

All traffic being initiated by a mobile subscriber in the area of the observed MSC,whatever the destination will be.

• mobile incoming traffic (MICTR)Mobile traffic that has been directed to the observed MSC by another exchange.

From digit translation, possibly followed by an interrogation process, the observed MSCknows where to find the destination of the call. This changes the original traffic type intoone of the following types:• mobile terminating traffic (MTER)

This applies to the traffic directed towards each mobile station in the area of the ob-served MSC.

• mobile originating outgoing traffic to a mobile party who is subscribed in the homePLMN (MOUT_PLMN), wherever he is actually roaming.

• mobile originating outgoing traffic to a party from the PSTN or another PLMN(MOUT_NOT_PLMN).

• mobile transit traffic (MTRAN)Traffic that has neither been initiated in nor will terminate at the observed MS.

These traffic types differ from those proposed in the GSM Recommendation 12.04 be-cause it is not always possible to distinguish between the traffic types as a result of therouting strategy used between networks.– PLMN → PLMN– PSTN → PLMN– PLMN → PSTN

20 A50016-D1109-G801-6-7618


Fig. 3.1 Traffic types in scope of the observed MSC

3.1 Basic countersBasic counters are to collect the call setup data for both speech and data calls. This dataapplies to standard and mobile-specific functions.

This description enumerates all the mobile-specific counters that are registered by theMSC basic traffic measurement. Due to the abundance of these counters, the descrip-tion is further divided into several parts in order to give a better summary and meaningof the counters offered:• a miscellaneous part• a time/duration related part• a load and demand related part focussing on:

– LTG pooling,– Gs interface,– location services.

• a grade of service related part focussing on:– unsuccessful calls,– unsuccessful LTG pooling,

MICTR

BSS

MIC

TR

MO

UT

NO

T P

LMN

MTRAN

MORTR

MORTR

MTERBSS

MTER

BSS

BSS

observed MSC

PSTN PLMN

PLMN

MICTR

MSC

MT

RA

NMOUT PLMN

MIC

TR

MO

UT

NO

T P

LMN

MO

UT

PLM

N

A50016-D1109-G801-6-7618 21


Traffic Measurement

– successful call establishments,– answered calls.

3.1.1 Miscellaneous part

NUM_RESET

indicates how many RESET messages are received.

Trigger: each time RESET is received from the BSC.

NUM_RESET_CIRCUIT

indicates how many RESET CIRCUIT messages are received

Trigger: each time RESET CIRCUIT is received from the BSC.

NUM_SSP_BSSAP

indicates how many SUBSYSTEM PROHIBITED messages for subsystem BSSAP arereceived

Trigger: each time SUBSYSTEM PROHIBITED is received from the BSC.

NUM_SIGN_POINT_PROHIB

indicates how many SIGNALING POINT PROHIBITED messages are received.

Trigger: each time SIGNALING POINT PROHIBITED is received from the BSC.

NUM_CALLS_REL_BS

indicates how many calls are released because one of the messages referred to in “trig-ger” is received.

Trigger: each time RESET, RESET CIRCUIT, SUBSYSTEM PROHIBITED (subsystem= BSSAP) or SIGNALING POINT PROHIBITED is received.

NUM_RECEIVED_OVERLOAD

indicates how many overload messages are received.

Trigger: each time OVERLOAD is received from the BSC.

NUM_SEND_OVERLOAD

indicates how many overload events have occurred.

Trigger: each time the MSC sends OVERLOAD messages to all connected BSCs.

NUM_RECEIVED_GCP

indicates how many GCP primitives are received.

Trigger: each time GCP (general congestion primitive) is received from the CCS7 linksystem.

NUM_RECEIVED_CIP

indicates how many CIP primitives are received.

Trigger: each time CIP (congestion indication primitive) is received from the CCS7 link.

22 A50016-D1109-G801-6-7618


NUM_RECEIVED_CLASSM_UPD

indicates how many CLASSMARK UPDATE messages are received.

Trigger: each time CLASSMARK UPDATE is received.

NUM_TOTAL_START_IMEI_CHECK

indicates how often IMEI check procedures are started.

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

NUM_IMEI_CHECK_WHITE

indicates how often the IMEI check procedure leading to a white list equipment is started

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

NUM_IMEI_CHECK_GREY

indicates how often the IMEI check procedure leading to a grey list equipment is started.

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

NUM_IMEI_CHECK_BLACK

indicates how often the IMEI check procedure leading to a black list equipment is started

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

NUM_IMEI_CHECK_UNKNOWN

indicates how often the IMEI check procedure leading to unknown equipment is started.

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

NUM_IMEI_CHECK_LUP

indicates how often IMEI checks are started by a location update.

Trigger: each time CHECK IMEI is sent with reason location update because of IMSI at-tach or normal location update.

NUM_IMEI_CHECK_PER_LUP

indicates how often IMEI checks are started by a periodic location update.

Trigger: each time CHECK IMEI is sent with reason location update because of periodiclocation update.

NUM_TONES_DTMF

indicates how many DTMF tones are sent by the MS.

Trigger: each time START DTMF is received.

NUM_NO_SPCH_BSSAP_LTG

indicates how often no free speech channel was found in the BSSAP LTG.

Trigger: upon each failure to seize a BSSAP-LTG (internal condition; reason: no freespeech channel available in this LTG).

NUM_ATT_SCP_DIALOGS_LNP

indicates how many queries are initiated to the number portability (NP) database in theservice control point (SCP).

A50016-D1109-G801-6-7618 23


Traffic Measurement

Trigger: each time the MSC sends an IDP message to the SCP.

NUM_SUCC_SCP_DIALOGS_LNP

indicates how often the NP database is successfully queried.

Trigger: each time the SCP sends CONNECT in reply to an NP database query contain-ing either a location routing number (LRN) or the same number as the one being sent.

LNP_QUERIES_LRN

indicates how many LRNs the NP database in the SCP returns after being queried; i.e.the investigated subscriber number is a ported one.

Trigger: each time the NP returns a local roaming number.

LNP_MISROUTED_CALL.

indicates how many calls were released because they were misrouted to a ported num-ber; applies to PCS1900 networks only.

Trigger: each time a release message of this type is received.

LNP_UNALLOC_NUM_MICTR

indicates how often the HLR returns “unknown subscriber” after being interrogated withan LRN.

Trigger: each time the HLR returns ‘unknown subscriber’ after being interrogated withan LRN; also each time in the case of incoming calls with an LRN of a ported in fixedsubscriber for which no code point exists; i.e. the ported in fixed subscriber has not beencreated in the MSC database.

LNP_VACANT_CODE

indicates how often the digit translation of an LRN of either a ported out subscriber or aported in mobile subscriber fails; i.e. there exists no code point for the LRN concerned.

Trigger: each time that the digit translation of an LRN of either a ported out subscriberor a ported in mobile subscriber fails.

NUM_ATT_SCP_DIALOGS_SMS

indicates how often an attempt for a short message has successfully invoked an IN func-tionality.

Trigger: each time IN TRIGGER to start an IN function is received.

NUM_ATT_SCP_DIALOGS_USSD.

indicates how often an attempt for unstructured SS data has successfully invoked an INfunctionality.

Trigger: each time INTR USSD to start an IN function is received.

NUM_SWITCH_LTGPOOL

indicates how often an initial LTG has switched over to another one to continue call es-tablishment.

Trigger: each time NRELAY contains another LTG than the one involved in this servicerequest.

24 A50016-D1109-G801-6-7618


3.1.2 Time/duration related part (1) of (2)

TIME_CALL_SET_U_SERV

is the average time to provide the “call setup” service.

Trigger:– starts each time SET UP is received (MOC) or sent (MTC)– stops each time ASSIGNMENT COMPLETE is received

NUM_CALL_SET_UP_CONTRIB

indicates the number of calls contributing to “call setup time”

Trigger: each time ASSIGNMENT COMPLETE is received (for the calculation of the av-erage setup time).

TIME_LUP_SERV

Accumulated time to provide service location update

Trigger:– starts each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received– stops each time LOCATION UPDATE ACCEPT is sent

NUM_LUP_CONTRIB

indicates the number of location updates contributing to “location update service time”.

Trigger: each time a location update contributing to TIME LUP SERV is received (for thecalculation of the mean holding time).

TRAFF_VOL_SUCC_PAGING

indicates the duration of the paging procedure (unit 50ms). Only successful paging pro-cedures are included, but no timeout cases

Trigger:– starts each time PAGING is sent– stops each time PAGING RESPONSE is received

3.1.3 Time/duration related part (2) of (2)

TRAFFIC_VOLUME

indicates the sum of all holding times.

Trigger: start and stop depend on the message of the respective traffic type:

MORTR:starts each time CM SERVICE REQUEST is received;stops each time RELEASE COMPLETE is received.

MICTR: starts each time IAM is received;stops each time RELEASE COMPLETE is received.

MTER: starts each time PAGING is sent;stops each time RELEASE COMPLETE is received,or at paging time-out.

MOUT_(NOT)_PLMN:starts with proper result of digit analysis after interrogation;stops when RELEASE COMPLETE is sent or received,or with an unsuccessful call attempt before IAM is sent.

MTRAN:starts with proper result of the digit analysis;

A50016-D1109-G801-6-7618 25


Traffic Measurement

stops when RELEASE COMPLETE is received.

DUR_OF_CONV_SPEECH_SERV

indicates duration of conversation for speech services.Trigger: start and stop depend on the message of the respective traffic type:

MTER: starts each time CONNECT is received;stops each time call is released.

MOUT_(NOT)_PLMN:starts each time ANSWER is received;stops each time call is released.

DUR_OF_CONVERSATION

indicates duration of conversation for MTRAN.Trigger:

starts each time ANSWER is received;stops each time call is released.

DUR_OF_CONV_DATACDA_ANA

indicates the duration of conversation for data CDA (circuit duplex asynchronous) ana-log services.Trigger: start and stop depend on the message of the respective traffic type:



DUR_OF_CONV_DATACDA_DIG

indicates the duration of conversation for data CDA digital services.Trigger: start and stop depend on the message of the respective traffic type:



DUR_OF_CONV_ALTFAXSP

indicates the duration of conversation for alternate speech/facsimile services.Trigger: start and stop depend on the message of the respective traffic type:



DUR_OF_CONV_FAX3

indicates the duration of conversation for the automatic facsimile group 3 service.Trigger: start and stop depend on the message of the respective traffic type:

26 A50016-D1109-G801-6-7618




DUR_OF_CONV_DED_PAD

indicates the duration of conversation for dedicated PAD (packet assembler/disassem-bler) access for MOUT_NOT_PLMN.Trigger:

starts each time ANSWER is received;stops each time call is released.

DUR_OF_CONV_DATACDS_ANA

indicates the duration of conversation for data CDS (circuit duplex synchronous) analogservices.Trigger: start and stop depend on the message of the respective traffic type:



DUR_OF_CONV_DATACDS_DIG

indicates the duration of conversation for data CDS digital services.Trigger: start and stop depend on the message of the respective traffic type:



DUR_ALT_SPEECH_DATA

indicates the duration of conversation for alternate speech/data or speech followed bydata services.Trigger: start and stop depend on the message of the respective traffic type:



3.1.4 Load and demand related part (1) of (2)CALL_ATTEMPTS.indicates how many call attempts have taken place, independently of the received BSor TS (except for MOUT_(NOT)_PLMN).Trigger: each time the respective message is involved:

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.

A50016-D1109-G801-6-7618 27


Traffic Measurement

MICTR: each time IAM is received (all call attempts).MTER: each time PAGING is sent.

The exact trigger condition is the detection of a MSRN of the home MSCby digit processing; this usually causes a paging message to be sent(all call attempts).The following cases are exceptions: busy MS, invocation of service callwait and overload related to A-interface.

MOUT_(NOT)_PLMN:upon receipt of SET UP and digit analysis results in this traffictype (speech call attempts only).

MTRAN:each time IAM is received and digit analysis results in outgoing traffic(all call attempts).

DATACDA_ANA_ATTEMPTSindicates how many call attemps have taken place for data CDA analog services.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:

MTER: The exact trigger condition is the detection of a MSRN of the home MSCby digit processing; this usually causes a paging message to be sent.The following cases are exceptions: busy MS, invocation of service callwait and overload related to A-interface.

MOUT_PLMN:MOUT_NOT_PLMN: In general, the values of this counter will include traffic without

interrogation unless international interrogation is applied.

DATACDA_DIG_ATTEMPTSindicates how many call attempts have taken place for data CDA digital services.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:


MOUT_PLMNMOUT_NOT_PLMN: In general, the values of this counter will include traffic without


ALTFAXSP_CALL_ATTEMPTSindicates how many call attempts for alternate speech/facsimile services have takenplace.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:




FAX3_CALL_ATTEMPTSindicates how many call attempts for the automatic facsimile group 3 service have takenplace.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:

28 A50016-D1109-G801-6-7618


MTER: each time SET UP is sentMOUT_(NOT)_PLMN

DED_PAD_ATTEMPTSindicates how many call attempts to a foreign network for dedicated PAD access servic-es have taken place for MOUT_NOT_PLMN.Trigger: each time the digit analysis after interrogation results in this traffic type.

DATACDS_ANA_ATTEMPTSindicates the number of call attempts for data CDS analog services.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:




DATACDS_DIG_ATTEMPTSindicates the number of call attempts for data CDS digital services.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:




ALT_SPEECH_DATA_ATTEMPTSindicates the number of call attempts for alternate speech/data or speech followed bydata services.Trigger: each time the digit analysis after interrogation results in the relevant traffic type:




EMERGENCY_TS12_ATTEMPTSindicates the number of emergency call attempts (TS12) for MORTR.Trigger: each time CM SERVICE REQUEST indicating an emergency call is received.

MSC_MSC_HO_CALL_ATTEMPTSindicates the number of call attempts caused by inter MSC handover for MTER;(MSC-B is the home MSC).

A50016-D1109-G801-6-7618 29


Traffic Measurement

Trigger: each time IAM is received from MSC-A and digit processing detects a handovernumber.

STARTED_PAGING_PROCindicates the number of started initial paging procedures for MTER.Trigger: each time PAGING is sent.

STARTED_PAG_RETRY_PROCindicates the number of started paging retry procedures for MTER.Trigger: each time PAGING is sent after the first expiry of the paging timer.

STARTED_INTERROGATIONSindicates the number of started interrogations.Trigger: each time SEND ROUTING INFO is sent upon receipt of SETUP

MORTR:to another MSMICTR

STARTED_INT_SER_CODE_DIGindicates the number of started interrogations including service code digits.Trigger: each time SEND ROUTING INFO is sent to the HLR and digit analysis revealsthat the MSISDN is a short code or a service code directory number.

MORTR:to another MSMICTR

SET_UP_SERV_CODEindicates the number of received setup messages containing short code digits or servicecodes for MORTR.Trigger: each time SET UP is received from the MS and digit analysis reveals that theMSISDN is a short code or a service code directory number.

GEN_TRAFF_CHAN_REQindicates the number of generated traffic channel requests.Trigger: each time ASSIGNMENT REQUEST is sent to the BSC

MORTR:after the previous receipt of CM SERVICE REQUEST.MTER: after previous paging.MOUT_(NOT)_PLMN: the counter is only incremented in the case of rerouting,

e.g. COC failure.

ACTIVE_QUEUINGindicates the number of calls where queuing was active.Trigger: each time QUEUING INDICATION is received from the BSC. The counter willbe actualized when ASSIGNMENT COMPLETE or RELEASE COMPLETE is receivedfor the call.

MORTRMTERMOUT_(NOT)_PLMN

30 A50016-D1109-G801-6-7618


IMEI_CHECKSindicates the number of IMEI checks caused by call setup.Trigger: each time CHECK IMEI is sent to the EIR.

MORTRMTER

IN_ATTEMPTSindicates the number of call attempts invoking IN functions.Trigger: each time an interworking to an IN service control point (SCP) is started as aresult of digit evaluation (e.g. dial an IN directory number) being part of a call setup.

MORTRMICTR

IN_TRANSindicates the number of call attempts invoking IN functionality, whereby no interworkingwith the IN SCP is started (e.g. televoting with service filtering so that precounting isdone in the SSP).Trigger: each time an interworking to IN SCP is started for a non call-related transaction.

MORTRMICTR

OACSU_ATTEMPTSindicates the number of attempted calls with OACSU for MOUT_(NOT)_PLMN.Trigger: each time SET UP is received and OACSU treatment is initiated for the propertraffic type.

CCBSThe CCBS service is activated by a mobile subscriber at the MSC-A. This CCBS requestis sent to the MSC-B of the called subscriber where it initiates an activation as well. Thiscounter indicates the number of activation attempts.Trigger: each time a CCBS REQUEST activating CCBS

MORTR: is sent by the MSC-A.MTER: is received from the MSC-A

CCBS_RECALLOnce the busy subscriber at the MSC-B is released he can recall the subscriber at theMSC-A. This counter indicates the number of CCBS recall attempts.Trigger: each time REMOTE USER FREE

MORTR:is received from the MSC-A.MTER: is sent by the MSC-B

3.1.5 Load and demand related part (2) of (2)SERVICE_REQ_SCI_INDEPENDENTindicates how often call-independent services were requested via SCI.Trigger: each time CM SERVICE REQUEST is received for SS activation without beinginvolved in a call.

A50016-D1109-G801-6-7618 31


Traffic Measurement

SERVICE_REQ_SCI_CALL_RELindicates how often services were requested via SCI during a parallel call.Trigger: each time CM SERVICE REQUEST is received for SS during a call.

SERVICE_REQ_LOC_UPDindicates how often service requests for location update are received.Trigger: each time COMPLETE L3 INFO with LOCATION UPDATE REQUEST is re-ceived.

RECVD_POS_ACK_FROM_GSMSCFindicates how often the GSM service control function has sent a positve acknowledge-ment.Trigger: each time a message containing a positive acknowledgement is received.

SENT_NOTIF_SS_INV_TO_GSMSCFindicates how often the GSM service control function is requested to invoke a supple-mentary service.Trigger: each time SS INVOCATION NOTIFY is sent to the GSM service control func-tion.

3.1.6 Load and demand related part: LTG poolingThese counters are intended to collect data about the use of LTG pools. LTG poolingprovides a group of circuits that support the same channel types.– a specific speech transcoder is provided to transmit speech on the radio interface,

allowing speech transmission via half rate channels (HR) or full rate channels (FR).– circuit switched user data is handled by the channel coding for transmission via FR

channels on the radio interface at specific rates:a rate of 6 kbit/s results from channel coding TCH/F4.8a rate of 12 kbit/s results from channel coding TCH/F9.6a rate of 14.5 kbit/s results from channel coding TCH/F14.4

– the high-speed circuit-switched data (HSCSD) facility enables data to be transportedby the PLMN using 2 traffic channels at the radio interface for the same data call.This facility just applies to 9.6 and 14.4 user data rates for BS20. The correspondingrates at the radio interface are 12 and 14.5 kbits/s.

CA_SPEECHindicates the number of attempts for speech calls for which a trunk providing the properchannel attributes is seized.Trigger: each time SET UP C containing the channel attributes required to seize theproper trunk is sent for

HR (V1 or V3)FR (V1 or V2 or V3)

CA_DATA_FRindicates the number of attempts for data calls for which a trunk providing the properchannel attributes for specific rates on the radio interface is seized.Trigger: each time SET UP C containing the channel attributes required to seize theproper LTG is sent for

12K

32 A50016-D1109-G801-6-7618


14.5K14.5K only

CA_HSCSD_2FRindicates the number of attempts for high-speed data calls for which a trunk providing 2channels with the proper attributes is seized.Trigger: each time SET UP C containing the channel attributes required to seize theproper LTG is sent for

12 only14.5K14.5K only

3.1.7 Load and demand related part: Gs interfaceTIME_COM_LUP_SERVAccumulated time to provide service combined location update being handled via theGs interface.Trigger:

starts each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is receivedstops each time LOCATION UPDATE RESPONSE or REJECT is sent

SERVICE_REQ_COM_LUPindicates how often service requests for a combined location update are received.Trigger: each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received viathe Gs interface.

NUM_COM_LUP_CONTRIBindicates how many combined location updates have caused the ‘combined location up-date service time’.

TV_SUCC_COM_PAGINGindicates the duration of successfully completed paging procedures (in 50 ms units).Trigger:

starts each time PAGING is sentstops each time PAGING RESPONSE is received.

CA_COM_PAGINGindicates the number of started combined paging procedures.Trigger: each time PAGING is sent on both the A interface and the Gs interface.

CA_COM_PAGING_RETRYindicates how often a combined paging procedure is retried after rejection on the Gs in-terface.Trigger: each time PAGING is sent on both the A interface and the Gs interface afterPAGING REJECT on the latter has been received.

NUM_COM_PAGING_RET_Aindicates the number of started paging procedures on the A interface after an unsuc-cessful attempt on the Gs interface.

A50016-D1109-G801-6-7618 33


Traffic Measurement

Trigger: each time PAGING is sent on the A interface upon PAGING REJECT on the Gsinterface has been received.

CCU_COM_PAGINGindicates the number of calls terminated because the combined paging procedure didnot succeed.Trigger: each time the connection is released because the paging timer expired for thesecond time.

CCS_COM_PAGING_RESindicates the number of successfully completed combined paging procedures.Trigger: each time PAGING RESPONSE is received from the BSC.

3.1.8 Load and demand related part: Location servicesThe initial position of any mobile station from which the subscriber makes an emergencycall must be delivered to a public safety answering point, as required for PCS1900 net-works. Such call will trigger location measurement equipment in the MSC that interfaceswith the gateway mobile location center. The latter manages the overall coordination ofresources required to perform the positioning of the calling MS. Within this respect anemergency services routing key (ESRK) can be allocated for call and MS identification.

ESRK_ALLOC_ATTindicates the number of attempts for allocating an ESRK.Trigger: each time the digit evaluation results into an emergency call.

SUCC_ESRK_ALLOC_ATTindicates the number of successful attempts allocating an ESRK.Trigger: each time such key is found after the digit evaluation.

LOCATION_ATTEMPTSindicates the number of location attempts.Trigger: each time DT1:PERFORM LCS is sent to the LTG.

UNS_LOC_ATT_CONGESTIONindicates the number of unsuccessful location attempts due to congestion.Trigger: each time DT1:PERFORM LCS RESP is received indicating unsuccessful po-sitioning.

SUCC_LOC_ATTindicates the total number of successful location attempts.Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_TAindicates the number of successful location attempts as a result of using the ’time ad-vance’ positioning method.Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-

34 A50016-D1109-G801-6-7618


tioning.

SUCC_LOC_ATT_TOAindicates the number of successful location attempts as a result of using the ’time of ar-rival’ positioning method.Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_MOB_ASSIST_E_OTDindicates the number of successful location attempts as a result of using the ’enhancedobserved time difference’ positioning method (MS assisted calculation).Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_MOB_BASED_E_OTDindicates the number of successful location attempts as a result of using the ’enhancedobserved time difference’ positioning method (MS based calculation).Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_MOB_ASSIST_GPSindicates the number of successful location attempts as a result of using the ’global po-sitioning system’ (MS assisted calculation).Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_MOB_BASED_GPSindicates the number of successful location attempts as a result of using the ’global po-sitioning system’ (MS based calculation).Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_CONV_GPSindicates the number of successful location attempts as a result of using the convention-al ’global positioning system’.Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_UNKNOWN_POSindicates the number of successful location attempts as a result of using an unknownpositioning method.Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

POS_SEND_TO_GMLCindicates the number of attempts for transferring both MS position estimate and emer-gency call origination to the gateway mobile location center

A50016-D1109-G801-6-7618 35


Traffic Measurement

Trigger: each time the first SUBSCRIBER LOCATION REPORT is successfully sent.

SUCC_POS_SEND_TO_GMLCindicates the number of successful transfers of the MS position estimate and the emer-gency call origination to the gateway mobile location centerTrigger: each time SUBSCRIBER LOCATION REPORT ACK is received upon sendingthe report.

3.1.9 Grade of service related part: unsuccessful calls*REL_BEFORE_ACMindicates how many calls are released in the forward direction before ACM is sent forMICTR.Trigger: upon each release in forward direction

in GMSC: before ACM is sent and after receipt of IAM.in VMSC: before address-complete condition and after receipt of IAM (release

before PAGING after receipt of IAM).

*UNS_PAGINGindicates how many incoming calls are terminated due to an unsuccessful paging pro-cedure.Trigger: upon each release of the connection by the second expiry of the paging timer.

*UNS_REQ_DEST_ERRindicates how many calls are terminated because the requested destination was un-known, blocked or could not be charged.Trigger: each time the respective message is involved:

*MORTR:upon receipt of internal release (CP) after digit analysis failed.*MTER: upon receipt of RELEASE COMPLETE (cause: destination is unknown,

blocked or could not be zoned).*MOUT_(NOT)_PLMN:upon rECEIPT of ISUP message RELEASE COMPLETE /

UNSUCCESSFUL BACKWARD MESSAGE after digitanalysis (cause: destination is unknown, blocked or could notbe zoned).

*MTRAN:upon receipt of RELEASE COMPLETE/UBM (cause: destination isunknown, blocked or could not be zoned).

*UNS_TECHN_FAULTindicates how many calls are terminated due to technical faults in the home MSC.Trigger: each time the MSC causes a technical fault (e.g. software fault, plausibilitycheck, hardware fault).

*MORTR*MICTR*MTER*MOUT_(NOT)_PLMN*MTRAN

36 A50016-D1109-G801-6-7618


*UNS_SERV_CHECKindicates how many calls are terminated due to negative service facility checks or neg-ative compatibility checks.Trigger: each time the relevant message with the proper cause:

*MORTR:RELEASE COMPLETE (e.g. service not implemented) is sent to theBSS.

*MICTR:TC-U-ERROR (BS or TS not provisioned, facility not supported, forwardingviolation) is received from the HLR in reply to SEND ROUTING INFO.

*MTER: RELEASE COMPLETE (e.g. service not implemented) is sent to theprevious exchange or the BSS.

*MOUT_(NOT)_PLMN:RELEASE COMPLETE (e.g. service not implemented) issent

to the BSS.

*UNS_MS_BLOCKEDindicates how many calls are terminated because the subscriber was blocked by oper-ator determined barring, by administration, or by SS. Because there are unblockabledestinations, the destination must be determined if the described barring conditions arefulfilled.Trigger: each time a call is released due to:

*MORTR:barring of outgoing calls (calling subscriber) or of incoming calls (calledsubscriber).

*MICTR:due to the interrogation result “CALL BARRED”.*MTER: the interrogation result “CALL BARRED” for the called subscriber.

*UNS_MS_BUSYindicates how many calls are terminated because the requested subscriber is alreadybusy.Trigger: each time the relevant message (including RELEASE messages) with reason“subscriber busy”:

*MTER: UBM is sent to the previous exchange.*MOUT_(NOT)_PLMN:RELEASE UBM is received from the following exchange.

*UNS_CONGESTIONindicates how many calls are terminated due to (trunk) congestion in the home MSC.Trigger: each time trunk seizure is not successful due to congestion:

*MORTR:BSS trunk*MTER: BSS trunk at B side.*MOUT_(NOT)_PLMN: trunk at B side.*MTRAN: trunk at B side.

*UNS_SN_CONGESTIONindicates how many calls are terminated due to switching network (SN) congestion.Trigger: each time a failure during SN through-connection occurs.

*MORTR*MTER*MOUT_(NOT)_PLMN

A50016-D1109-G801-6-7618 37


Traffic Measurement

*UNS_LACK_IWEindicates how many calls are terminated due to lack of IWEs.Trigger: each time the seizure of IWE was not successful due to unavailable IWE.

*MORTR*MTER*MOUT_(NOT)_PLMN

*UNS_SECURITY_FAILindicates how many calls are terminated due to authentication/security failure.Trigger: each time AUTHENTICATION REJECT is sent to the BSS.

*MORTR*MTER

*UNS_LINK_FAILindicates how many calls are terminated due to failure/congestion/overload on associ-ated CCS7 signaling system links.Trigger: each time a call is released due to CCS7 failure (e.g. upon receipt of ”STOPTRAFFIC”).


*UNS_PROTO_ERRORindicates how many calls are terminated due to protocol errors.Trigger: each time a protocol error was detected but the call could be identified.


*UNS_NETW_MANAGEMENTindicates how many calls are terminated due to network management activities.Trigger: each time trunk resource management detects a network management event .

*MOUT_(NOT)_PLMN*MTRAN

*UNS_OVERLOADindicates how many calls/transactions are terminated due to overload prevention.Trigger: each time a call is internally released due to an overload situation.

*MORTR*MICTR*MTER

*UNS_BS_REASONindicates how many calls are terminated during setup due to BSS/radio-related reasonsTrigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PRO-

38 A50016-D1109-G801-6-7618


HIBITED, RESET, RESET CIRCUIT is received*MORTR:from the BSS before digit analysis is performed.*MTER: before digit analysis is performed.*MOUT_(NOT)_PLMN:after digit analysis has been performed.

UNS_BLACK_LISTindicates how many calls are terminated because the IMEI check indicates black listequipment.Trigger: each time a result indicating ‘black list’ is received from the EIR in reply toCHECK IMEI.

MTERMOUT_(NOT)_PLMN

UNS_IMEI_UNKNOWNindicates how many calls are terminated because IMEI check indicates unknown equip-ment.Trigger: each time a result indicating ‘IMEI unknown’ is received from the EIR in reply toCHECK IMEI.

MTERMOUT_(NOT)_PLMN

UNS_MS_DETACHindicates how many calls are terminated because the called MS was detached/absent.Trigger: each time a detached or absent subscriber is detected

MORTR:by a negative reply by the HLR to SEND ROUTING INFO.MICTR: by a negative reply by the HLR to SEND ROUTING INFO.MTER: in the VLR database causing the call to be released.

UNS_CUG_REJECTindicates how many calls are terminated due to CUG reject.Trigger: the proper CUG error cause is reported by

MORTR:sending RELEASE COMPLETE to the BSS.MICTR: sending RELEASE to the previous MSC.MOUT_(NOT)_PLMN: receiving RELEASE/UBM from the subsequent MSC.

IN_OVERLOADindicates the number of IN calls that are released due to SCP overload or automatic callgapping initiated by SCP.Trigger: each time call setup with prompted call handling is released due to IN overloadprevention measures.

MORTRMICTR

IN_NO_ANSW_SCPindicates the number of IN calls that are released due to missing answer from SCP.Trigger: each time an IN dialog to the SCP is started and no answer is received within atimer schedule. The call setup is then released.

MORTR

A50016-D1109-G801-6-7618 39


Traffic Measurement

MICTR

IN_ERROR_SCPindicates the number of IN calls that are released because SCP sends unsuitable infor-mation (e.g. (new) call numbers sent from the SCP cannot be recognized/connected inthe MSC, data is unreadable).Trigger: each time a connection is released because the IN SCP data received is insuf-ficient to establish it.

MORTRMICTR

IN_SERV_CHECKindicates the number of IN calls that are released because the required IN service is notactive, e.g. not allowed for subscriber or not supported by SCP.Trigger: each time the SCP releases a call due to service/facility checks.

MORTRMICTR

IN_ERROR_DESTindicates the number of IN calls that are released because the called IN number is un-known.Trigger: each time the SCP releases a call because the called number is unknown.

MORTRMICTR

3.1.10 Grade of service related part: unsuccessful LTG poolingCCU_SPEECHindicates how many attempts for speech calls are terminated because a trunk providingthe proper channel attributes could not be seized.Trigger: each time the trunk could not be seized upon sending SET UP C with channelattributes for

HR (V1 or V3)FR (V1 or V2 or V3)

CCU_DATA_FRindicates how many attempts for data calls are terminated because a trunk providing theproper channel attributes for specific rates on the radio interface could not be seized.Trigger: each time the LTG could not be seized upon sending SET UP C with channelattributes for

12K14.5K14.5K only

CCU_HSCSD_2FRindicates how many attempts for high-speed data calls are terminated because a trunkproviding 2 channels containing the proper attributes could not be seized.Trigger: each time the LTG could not be seized upon sending SET UP C with channelattributes for

40 A50016-D1109-G801-6-7618


12 only14.5K14.5K only

3.1.11 Grade of service related part: successful call establishmentRECEIVED_PAG_RESPindicates the number of received paging response messages for MTER.Trigger: each time PAGING RESPONSE is received from the BSC.

CALL_TCH_ALLOCATIONindicates the number of calls with successfully completed traffic channel (TCH) alloca-tion.Trigger: each time ASSIGNMENT COMPLETE is received.

MORTRMTER

TS11_EMERG_CALL_TCH_ALLindicates the number of outgoing emergency calls with successfully completed trafficchannel allocation for emergency calling (TS11).Trigger: each time ASSIGNMENT COMPLETE is received for TS11 calls.

TS12_EMERG_CALL_TCH_ALLindicates the number of outgoing emergency calls with successfully completed trafficchannel allocation for emergency calling (TS12).Trigger: each time ASSIGNMENT COMPLETE is received for TS12 calls.

COMPL_SCI_INDEPENDENTindicates the number of successfully performed call-independent SCIs for MORTR.Trigger: each time RELEASE COMPLETE with facility information element (return-re-sult) is received in response to operate SS, i.e. activate/deactivate/register/erase/inter-rogate SS, register PW or process unstructured SS data.

COMPL_SCI_CALL_RELindicates the number of successfully performed call-related SCIs for MORTR.Trigger: each time RELEASE COMPLETE with facility information element (return-re-sult) is received in response to operate SS.

COMPL_INTERROGATIONSindicates the number of calls with successfully completed interrogations.Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR.

MORTRMICTR

COMPL_INTERROGATIONS_SCindicates the number of calls with successfully completed interrogations containing ser-vice codes.Trigger: each time TC-RESULT is received in response to SEND ROUTING INFO con-taining short-codes or short-service-codes.

A50016-D1109-G801-6-7618 41


Traffic Measurement

MORTRMICTR

CALL_INT_MS_OWN_MSCindicates the number of calls with successfully completed interrogations leading to MSin home MSC.Trigger: each time a positive result of SEND ROUTING INFO is received from the HLRand the MSRN evaluation results in paging.

MORTRMICTR

SN_THROUGH_CONNECTIONSindicates the number of successful call attempts.Trigger: each time

MTER: CALL CONFIRMED is received.MOUT_(NOT)_PLMN: IAM is sent to the next exchange.MTRAN: IAM is sent to the next exchange.

CALL_REL_EXCHANGEindicates how many calls are terminatedby the previous exchange for MTER, andby the following exchange for MOUT_(NOT)_PLMN, andby the previous/following exchange for MTRAN.Trigger: each time RELEASE is received

MTER: indicating clear forward.MOUT_(NOT)_PLMN: indicating clear backward) or UBM with causes different from

busy, CUG reject, destination error.MTRAN: indicating clear forward or clear backward.

CALL_REL_BEF_A_ALERTindicates how many calls are released by the A-subscriber before alerting.Trigger: each time RELEASE COMPLETE is received before alert with relevant rea-son(s), for:

MOUT_(NOT)_PLMN

CALL_REL_A_ALERTindicates how many calls are released by the A-subscriber during alerting.Trigger: each time RELEASE COMPLETE is received after alert and before CONNECTwith relevant reason(s), for:

MOUT_(NOT)_PLMN

CALL_REL_BEF_ALERTindicates how many calls are released before alerting the destination.Trigger: each time upon receipt of

MTER: RELEASE COMPLETE before alerting signal is received.MTRAN:RELEASE (clear backward or clear forward) before alert signal is received.

CALL_REL_ALERTindicates how many calls are released before connect is received for MTER and during

42 A50016-D1109-G801-6-7618


alerting for MTRAN.Trigger: each time upon receipt of

MTER: RELEASE COMPLETE after alerting is sent and before CONNECT isreceived.

MTRAN:RELEASE (clear backward or clear forward) before receipt of ANSWERand after receipt of ACM.

CALL_TIOUT_ALERTindicates how many calls are released by alert supervision time-out.Trigger: each time RELEASE COMPLETE is received due to alert supervision time-out(internal event in MSC), for:

MOUT_(NOT)_PLMN

CALL_WHITE_LISTindicates the number of successful calls with white listed equipment.Trigger: each time TC-RESULT (white list IMEI) is received from the EIR in response tocheck IMEI at call setup.

MORTRMTER

CALL_GREY_LISTindicates the number of successful calls with grey listed equipment.Trigger: each time TC-RESULT (grey list IMEI) is received from the EIR in response tocheck IMEI at call setup.

MORTRMTER

CALL_END_CALL_FORWindicates how many calls are ended due to start of call forwarding.Trigger: each time call forwarding treatment (e.g. busy, unconditional no paging re-sponse) is invoked and old call setup is thereby ended.

MORTRMICTRMTER

IN_REROUTEindicates how many calls are ended due to rerouting by IN.Trigger: each time an answer from SCP is received and call is rerouted to a new desti-nation included in the SCP response.

MORTRMICTR

ANN_NO_ERRORindicates how many calls are intercepted to an announcement without a known call re-lease reason.Trigger: each time a call is intercepted to an announcement by digit processing, call rout-ing without previous error (e.g. recorded announcements in call setup for queuing).

MORTRMICTR

A50016-D1109-G801-6-7618 43


Traffic Measurement

MTER

ANN_ERRORindicates how many calls are intercepted to an announcement after a call releasing er-ror.Trigger: each time call setup encounters an error that terminates further call handlingand the call is intercepted to an announcement (e.g. announcement: subscriber cannotbe reached by deactivated subscribers).

MORTRMICTRMTER

REROUTE_BEFORE_SNindicates how many calls are rerouted before SN through-connection.Trigger: each time a connection is rerouted to new directory numbers by digit evaluation(e.g. installation of code processing) before through-connection of the original call setup.

MORTRMICTRMTERMOUT_(NOT)_PLMNMTRAN

REROUTE_AFTER_SNindicates how many calls are rerouted after SN through-connection.Trigger: each time a connection is rerouted to new directory numbers by digit evaluation(e.g. installation of code processing) after SN through-connection in the home MSC; itcan be caused by backward messages (UBM/Release) of the subsequent MSC.

MTERMOUT_(NOT)_PLMNMTRAN

SN_REROUTE_CALLindicates the number of through-connections in the switching network (SN) for reroutedcalls.Trigger: each time time a through-connection of the routed call setup is successful. An-alog: SN THROUGH CONNECTIONS for routed connections changed to a new desti-nation.


CALL_TRANSFERindicates how many call transfers are completed by new resource configuration estab-lishing.Trigger: each time Release or Facility with return-result is sent to the BSS in responseto INVOKE SS.

MTERMTRAN

44 A50016-D1109-G801-6-7618


OACSU_RELSUBindicates how many calls are released by subscribers during OACSU treatment.Trigger: each time RELEASE COMPLETE during OACSU handling is received due to:a) release of the B-subscriber before a traffic channel is allocated on the A-interface;b) release of the A-subscriber before an answer of the B-subscriber is received, for:

MOUT_(NOT)_PLMN

OACSU_TCH_ALLOCindicates the number of call attempts with OACSU and successful traffic channel alloca-tion.Trigger: each time time ASSIGNMENT COMPLETE is received for a MOC with OACSUtreatment, for:

MOUT_(NOT)_PLMN

CALL_CCBSindicates the number of successful CCBS call attempts.Trigger: each time IAM

MORTR:is sent to destination MSC (MSC-B) after previous receipt of REMOTEUSER FREE.

MTER: is received from originating MSC (MSC-A) after previously sent REMOTEUSER FREE.

3.1.12 Grade of service related part: answered callsSPEECH_CALLS_WITH_ANSWERindicates how many speech calls are answered.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.

MTER: CONNECTMOUT_(NOT)_PLMN: ANM

CALLS_WITH_ANSWERindicates the number of answered calls for MTRAN.Trigger:each time the connection has actually been released in reply to the receipt ofANM.

TS11_EMERG_WITH_ANSWERindicates the number of answered emergency calls (TS11).Trigger: each time the connection has actually been released in reply to the receipt ofANM.

TS12_EMERG_WITH_ANSWER.indicates the number of answered emergency calls (TS12)Trigger: each time the connection has actually been released in reply to the receipt ofANM.

DATACDA_ANA_WITH_ANSWERindicates the number of answered data calls for CDA analog services.Trigger: each time the connection has actually been released in reply to the receipt of

A50016-D1109-G801-6-7618 45


Traffic Measurement

the respective message.MTER: CONNECTMOUT_(NOT)_PLMN: ANM

DATACDA_DIG_WITH_ANSWERindicates the number of answered data calls for CDA digital services.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.


ALTFAXSP_WITH_ANSWERindicates the number of answered data calls with alternation from speech to facsimile.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.


FAX3_WITH_ANSWERindicates the number of answered data calls for automatic facsimile group 3.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.


DED_PAD_WITH_ANSWERindicates the number of answered calls for dedicated PAD CDA services.Trigger: each time the connection has actually been released in reply to the receipt ofANM.

DATACDS_ANA_WITH_ANSWERindicates the number of answered data calls for CDS analog services.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.


DATACDS_DIG_WITH_ANSWERindicates the number of answered data calls for CDS digital services.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.


ALT_SPEECH_DATA_ANSWERindicates the number of answered alternate speech/data or speech followed by datacalls.Trigger: each time the connection has actually been released in reply to the receipt ofthe respective message.

46 A50016-D1109-G801-6-7618



BS_REL_WITH_ANSWERindicates the number of answered calls terminated due to BSS/radio-related reasons(e.g. loss of connection).Trigger: upon each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RE-SET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ for particular reason(s)were received.

MTERMOUT_(NOT)_PLMN

REROUTE_NEW_DESTindicates the number of answered calls that were rerouted to a new call destination (e.g.by IN SCP Interworking).Trigger: each time ANSWER/CONNECT are received.


OACSU_WITH_ANSWERindicates the number of answered calls with OACSU.Trigger: each time ANM is received for a MOC with OACSU treatment, for:

MOUT_(NOT)_PLMN

3.2 Handover CountersFor the measurement of handover traffic in the MSC, a number of handover countershas been implemented. It should be underlined that these counters only apply to MSCcontrolled handovers. Counters for BSC controlled handover are defined in the BSC.Since the MSC has no knowledge about BSC-controlled handover attempts (only suc-cessful handovers are reported), the inclusion of HANDOVER PERFORMED would in-crease the handover success rate. Because the receipt of this message will indicate aBSC-controlled handover, it will not be used to trigger the counter HO_PERFORMED.The traffic types do not affect the handover traffic measurement.

The handover traffic measurement relies on counters that make up– a load and demand related part and– a grade of service related part focussing:

handover establishments,successful completed handovers.

To be able to exactly know when the counter is triggered, the proper call flows for somehandover counters are presented in “Description of Measurement Counters”.

3.2.1 Load and demand related partHANDOVER_ATTEMPTSindicates the number of handover requests.

A50016-D1109-G801-6-7618 47


Traffic Measurement

Trigger: upon receipt of HANDOVER REQUIRED without SDCCH indication.

CA_HANDOVER_SDCCHindicates the number of handover attempts using a stand alone dedicated control chan-nel (applies to SMS, SCI and USSD).Trigger: upon receipt of HANDOVER REQUIRED with SDCCH indication.

HANDOVER_DATA_CALL_ATTEMPTSindicates the number of handover requests for data calls.Trigger: upon each receipt of HANDOVER REQUIRED, data call active.

HANDOVER_UPLINK_QUALITYindicates the number of handover requests due to uplink quality.Trigger: upon each receipt of HANDOVER REQUIRED, uplink quality.

HANDOVER_UPLINK_STRENGTHindicates the number of handover requests due to uplink strength.Trigger: upon each receipt of HANDOVER REQUIRED, uplink strength.

HANDOVER_DOWNLINK_QUALITYindicates the number of handover requests due to downlink quality.Trigger: upon each receipt of HANDOVER REQUIRED, downlink quality.

HANDOVER_DOWNLINK_STRENGTHindicates the number of handover requests due to downlink strength.Trigger: upon each receipt of HANDOVER REQUIRED, downlink strength.

HANDOVER_DISTANCEindicates the number of handover requests due to distance.Trigger: upon each receipt of HANDOVER REQUIRED, distance.

HANDOVER_BETTER_CELLindicates the number of handover requests due to better cell.Trigger: upon each receipt of HANDOVER REQUIRED, better cell.

HANDOVER_RESP_TO_MSCindicates the number of handover requests due to response to MSC invocation.Trigger: upon each receipt of HANDOVER REQUIRED, response to MSC invocation.

HANDOVER_OP_MAINT_INTindicates the number of handover requests caused by O&M intervention.Trigger: upon each receipt of HANDOVER REQUIRED, O&M intervention.

HANDOVER_DIRECTED_RETRYindicates the number of handover requests due to directed retry.Trigger: upon each receipt of HANDOVER REQUIRED, directed retry.

48 A50016-D1109-G801-6-7618


HANDOVER_MSC_MSC_OG_ATTEMPTSindicates the number of outgoing requests for inter-MSC handover (home MSC = MSC-A).Trigger: each time PERFORM HANDOVER is sent to MSC-B.

HANDOVER_MSC_MSC_OG_DAT_ATTindicates the number of outgoing requests for inter-MSC handover for data calls (homeMSC = MSC-A).Trigger: each time PERFORM HANDOVER is sent to MSC-B during active data call.

*HANDOVER_MSC_MSC_IC_ATTEMPTSindicates the number of incoming requests for inter-MSC handover (home MSC = MSC-B).Trigger: each time HANDOVER REQUIRED is received from MSC-A.

*SUBSEQ_MSC_MSC_HO_MSCBindicates the number of requests for subsequent inter-MSC handover (home MSC =MSC-B).Trigger: each time PERFORM SUBSEQUENT HANDOVER is sent to MSC-A.

SUBSEQ_MSC_MSC_HO_MSCAindicates the number of requests for subsequent inter-MSC handover (home MSC =MSC-A).Trigger: each time PERFORM SUBSEQUENT HANDOVER is received from MSC-B.

3.2.2 Grade of service related part: handover establishmentHO_PERFORMEDindicates the number of handovers autonomously performed by the BSS.Trigger: each time the MSC-A receives HANDOVER PERFORMED from the BSS.

HO_CONFERENCEindicates the number of conferences built up during all handover attempts.Trigger: upon each handover for speech call, as follows:for intra-MSC handover: MSC sends HANDOVER COMMAND to BSCfor inter-MSC handover: MSC-A sends IAM to MSC-B/MSC-B’for inter-MSC handover back to MSC-A: result (PREPARE SUBSEQUENT

HANDOVER) is sent to MSC-B.

HO_OLD_CELLindicates the number of handovers completed in the old cell.Trigger: each time the HANDOVER COMMAND is sent to the BSS by MSC-A.

CCS_SDCCH_ALLOCindicates the number of succesful allocations of stand alone dedicated control channels.Trigger: each time upon receipt of SEIZ FOR HO ACK.

A50016-D1109-G801-6-7618 49


Traffic Measurement

3.2.3 Grade of service related part: successful completed handoversSUCC_COMPLETED_HOindicates the number of successfully completed intra-MSC handovers.Trigger: each time MSC receives HANDOVER COMPLETE from the BSS.

SUCC_COMPL_HO_SDCCHindicates the number of successfully completed intra-MSC handovers using stand alonededicated control channels.Trigger: each time upon receipt of HO EXECUTED.

SUCC_COMPL_HO_DATA_CALLSindicates the number of successfully completed intra-MSC controlled handovers for datacalls.Trigger: each time MSC-B receives HANDOVER COMPLETE from the BSS during ac-tive data call.

SUCC_MSC_MSC_HO_MSCAindicates the number of successful inter-MSC handovers where the home MSC acts asMSC-A.Trigger: each time HANDOVER COMPLETE is received for handover back to MSC-A,and each time SEND END SIGNAL is received from MSC-B for handover to MSC-B.

SUCC_DATA_MSC_MSC_HO_MSCAindicates the number of successful inter-MSC handovers for data calls where the homeMSC acts as MSC-A.Trigger: each time SEND END SIGNAL is received from MSC-B during active data call.

*SUCC_MSC_MSC_HO_MSCBindicates the number of successful inter-MSC handovers where the home MSC acts asMSC-B/MSC-B'.Trigger: each time the SEND END SIGNAL is sent to MSC-A.

*SUCC_SUBSEQ_MSC_MSC_HO_MSCBindicates the number of successful subsequent inter-MSC handovers.Trigger: each time the END SIGNAL is received in response to the handover command.

*SUCC_HO_SEC_MSC_MSC_HO_MSCBindicates the number of intra-MSC handovers after previous inter-MSC handover (homeMSC = MSC-B).Trigger: each time the HANDOVER COMPLETE is received from the BSS for intra-MSChandover in MSC-B.

3.3 Short Message Service CountersFor the measurement of the traffic related to the short message service (SMS), a num-ber of SMS counters are implemented in the MSC.The traffic types do not affect SMS traffic measurement.

The SMS traffic measurement relies on counters that make up:– a load and demand related part

50 A50016-D1109-G801-6-7618


– a grade of service related part focussing:successful short message services, andunsuccessful short message services.

3.3.1 Load and demand related partSMS_INC_ATTEMPTSindicates the number of SMS messages received from the SMS gateway (home MSC =serving MSC).Trigger: each time the FORWARD SHORT MESSAGE is received from the SMS gate-way.

SMS_OTG_ATTEMPTSindicates the number of SMS messages sent to the SMS gateway (home MSC=servingMSC).Trigger: each time the FORWARD SHORT MESSAGE is sent to the SMS gateway.

SMS_INC_PARALLELindicates the number of parallel SMS-MT invocations.Trigger: each time the FORWARD SHORT MESSAGE is received from the SMS gate-way.The setup of SMS-MT is a parallel transaction (e.g. to a call).

SMS_OTG_PARALLELindicates the number of parallel SMS-MO invocations.Trigger: each time the FORWARD SHORT MESSAGE is sent to the SMS gateway.Thesetup of SMS-MO is a parallel transaction.

SMS_INC_PARALLEL_MEM_AV_INVindicates the number of parallel SMS memory available invocations.Trigger: each time READY FOR SM (GSM phase 2) is sent to the HLR. SM is a paralleltransaction to a call/other transaction.

SMS_SER_REQ_ATTEMPTSindicates the number of received CM SERVICE REQUEST messages for service SMS.Trigger: each time the CM SERVICE REQUEST including service type SMS is receivedfrom the MS.

RECEIVE_RP DATA_ATTEMPTSindicates the number of SMS messages that are received from the MS.Trigger: each time RP DATA is received from the MS.

SEND_RP DATA_ATTEMPTSindicates the number of SMS messages that are sent to the MS.Trigger: each time RP DATA is sent to the MS.

3.3.2 Grade of service related part: successful servicesSUCC_SMS_INCindicates the number of successfully acknowledged SMS messages that are receivedfrom the SMS gateway (home MSC = serving MSC).

A50016-D1109-G801-6-7618 51


Traffic Measurement

Trigger: each time FORWARD SHORT MESSAGE ACK is sent to the SMS gateway.

SUCC_SMS_OTGindicates the number of successfully acknowledged SMS messages that are sent to theSMS gateway (home MSC = serving MSC).Trigger: each time FORWARD SHORT MESSAGE ACK is received by the SMS gate-way.

SUCC_SMS_RECEIVE_RP_ACKindicates the number of mobile terminated SMS messages acknowledged by the MS.Trigger: each time RP ACK is received by the MS.

SUCC_SMS_SEND_RP_ACKindicates the number of sent mobile originated SMS messages acknowledged by theMS.Trigger: each time RP ACK is sent to the MS.

SUCC_MULT_SMS_OTGindicates the number of successfully acknowledged sent multiple SMS messages.Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is received asacknowledgement from the SMS gateway for multiple short message transfer.

Note: first short message is acknowledged as SUCCESSFUL SHORT MESSAGEOUTGOING.

SUCC_MULT_SMS_INCindicates the number of successfully acknowledged received multiple SMS messages.Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is sent as ac-knowledgement to the SMS gateway for multiple short message transfer.

Note: last short message is acknowledged as SUCCESSFUL SHORT MESSAGEOUTGOING.

3.3.3 Grade of service related part: unsuccessful servicesUNS_SMS_INC_ABSENT_MSindicates the number of SMS messages that is received from the SMS gateway due toabsent subscriber (home MSC = serving MSC).Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating ‘absent sub-scriber’ is sent to the SMS gateway.

UNS_SMS_OTG_UNIDENT_MSindicates the number of SMS messages that is sent to the SMS gateway due to uniden-tified subscriber (home MSC = serving MSC).Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating ‘unidentifiedsubscriber’ is received from the SMS gateway.

UNS_SMS_OTG_NO_FACILITYindicates the number of SMS messages that is sent to the SMS gateway due to facilitynot supported (home MSC = serving MSC).Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating ‘facility not sup-

52 A50016-D1109-G801-6-7618


ported’ is received from the SMS gateway.

UNS_SMS_INC_DELIVERY_FAILindicates the number of SMS messages that is received from the SMS gateway due toshort message delivery failure (home MSC = serving MSC).Trigger: each time a FORWARD SHORT MESSAGE ERROR is sent to the SMS gate-way with either of the following error codes: unknown SC, SC congestion, invalid SMSaddress, subscriber not SC subscriber.

UNS_SMS_OTG_DELIVERY_FAILindicates the number of SMS messages that is sent to the SMS gateway due to SM de-livery failure (home MSC = serving MSC).Trigger: each time a FORWARD SHORT MESSAGE ERROR is received from the SMSgateway with either of the following error codes: unknown SC, SC congestion, invalidSMS address, subscriber not SC subscriber.

UNS_SMS_REC_RP_MEMORYindicates the number of mobile terminated SMS messages that is refused due to mem-ory capacity exceeded.Trigger: each time an RP ERROR is received from the MS for this reason.

UNS_SMS_SEND_RP_UNASSIGN_NUMindicates the number of mobile originated SMS messages that is refused due to unas-signed number.Trigger: each time an RP ERROR indicating unassigned number is sent to the MS.

UNS_SMS_SEND_RP_SUB_ERRindicates the number of mobile originated SMS messages that is refused due to sub-scriber data (e.g. call barred, unknown subscriber).Trigger: each time an RP ERROR with the proper reason is sent to the MS.

UNS_SMS_SEND_RP_FAC_CHECK_ERRindicates the number of mobile originated SMS messages that is refused due to facilityerrors (e.g. facility rejected, facility not implemented).Trigger: each time an SMS MO handling message RP ERROR with the proper reasonis sent to the MS.

UNS_SMS_REC_RP_PROT_ERRindicates the number of mobile terminated SMS messages that is refused due to proto-col or message related errors.Trigger: each time RP ERROR with the proper reason is received from the MS.

UNS_SMS_SEND_RP_PROT_ERRindicates the number of mobile originated SMS messages that is refused due to protocolor message related errors.Trigger: each time RP ERROR with the proper reason is sent to the MS.

UNS_SMS_INC_PARALLEL_MS_STATEindicates the number of unsuccessful parallel SMS MT message transfers due to MS

A50016-D1109-G801-6-7618 53


Traffic Measurement

transaction state.Trigger: each time an SMS MT handling RP ERROR due to “message not compatiblewith short message protocol state” or status message for particular reason(s) is receivedfrom the MS.

UNS_MULT_SMS_OTGindicates the number of multiple SMS messages sent that were handled unsuccessfully.Trigger: each time a FORWARD SHORT MESSAGE ERROR is received from the SMSgateway or an RP ERROR is sent to the MS for multiple SMS.

UNS_MULT_SMS_INCindicates the number of multiple SMS messages received that were handled unsuccess-fully.Trigger: each time a FORWARD SHORT MESSAGE ERROR is sent to the SMS gate-way or an RP ERROR is sent to the MS for multiple SMS.

3.4 ASCI CountersASCI is short for advanced speech call items and provides for services to a GSM sub-scriber to establish voice group calls (VGCs) and to use voice broadcasting (VB). By justcalling a single number particular subscribers from a given geographical area can begrouped in a parallel connection.– the VGC is initiated by a dispatcher for a speech conversation between one talking

and several listening subscribers.– the VB is initiated by a dispatcher to broadcast into a predefined area to a particluar

group of subscribers within this area.

In addition the service can be assigned an enhanced multi-level precedence and pre-emption (eMLLP) service. This specifies how to handle precedence levels within thePLMN including pre-emption of ongoing calls. With respect to these services, a groupcall register (GCR) is implemented where the relevant attributes are assigned by regis-tration, such as:– a list of radio cells from the own MSC of which the service areas are composed;– a list of the dispatchers’ identities;– information about the used codecs for half or full rate channels.

A group call can also involve a number of cells being located in one or more relay MSCsbeing connected to the anchor MSC.

TV_VGCSindicates the sum of holding times (i.e. traffic volume in sec) as a result of voice groupcalls.Trigger: each time a CM SERVICE REQUEST with service type VGCS is received.

TV_VBSindicates the sum of holding times (i.e. traffic volume in sec) as a result of broadcasting.Trigger: each time a CM SERVICE REQUEST with service type VBS is received.

CA_SERV_SUB_VGCSindicates how often a service subscriber has attempted to originate a voice group call.Trigger: each time a CM SERVICE REQUEST with service type VGCS is received.

54 A50016-D1109-G801-6-7618


CA_SERV_SUB_VBSindicates how often a service subscriber has attempted to originate a voice broadcast.Trigger: each time a CM SERVICE REQUEST with service type VBS is received.

CCU_OVERLOAD_INIT_VGCS_VBSindicates how many attemps for the VGCS or the VBS were rejected due to MSC over-load.Trigger: each time a CM SERVICE REJECT is sent upon receiving a request for VGCor VB service.

CA_MOB_DISPATCH_VGCS_VBS.indicates how many attemps are initiated by a mobile dispatcher for a VG or VB call-Trigger: each time digit translation has detected a VG or VB call upon receiving SETUP.

CA_FIX_DISPATCH_VGCS_VBSindicates how many attemps are initiated by a dispatcher from the fixed network for aVG or VB call.Trigger: each time digit translation has detected a VG or VB call upon receiving DIGITBLOCK C.

NUM_ATRIB_REQ_GCRindicates the number of requests to the GCR for retrieval of the appropriate attributes.Trigger: each time VGCS ATR REQ is sent to the GCR upon receiving SETUP.

NUM_ATRIB_RESPONSE_GCRindicates the number of requests to the GCR for retrieval of the appropriate attributes.Trigger: each time the GCR returns the requested attributes with VGCS ATR RE-SPONSE.

CCS_DISPATCH_RECONN_VGCS_VBSindicates how often a dispatcher, upon originating a group call, is reconnected to a re-cently created group connection (included in the group again).Trigger: each time VGCS ATR RES with busy indication is received.

CCU_SERV_SUB_BUSY_VGCS_VBSindicates how often a group call from a service subscriber is terminated unsuccessfullybecause the group is already involved in a call.Trigger: each time TERMINATION indicating busy is sent to the service subscriber uponreceiving VGCS ATR RES.

NUM_CELL_SETUP_RESP_GCRindicates the number of radio cells involved in the group call setup.Trigger: each time upon setup request to each cell indicated in VGCS ATR RESPONSEfrom the GCR.

NUM_DISPATCH_SETUP_RESP_GCRindicates the number of dispatchers involved in the group call setup.Trigger: each time upon setup request to each dispatcher indicated in VGCS ATR RE-

A50016-D1109-G801-6-7618 55


Traffic Measurement

SPONSE from the GCR.

NUM_VGCS_VBS_SETUP_BSC_REQindicates the number of requests to the BSCs intended for VG calls or broadcasting.Trigger: each time VGCS/VBS SET UP is sent.

NUM_VGCS_VBS_TCH_ALLOC_REQindicates the number of traffic channel requests to the cells intended for VG calls orbroadcasting.Trigger: each time VGCS/VBS ASS REQ is sent.

NUM_VGCS_VBS_SETUP_BSC_ACKindicates the number of acknowledgements received from the BSCs to establish a groupcall.Trigger:each time VGCS/VBS SETUP ACK is received.

NUM_VGCS_VBS_TCH_ALLOC_ACKindicates the number of acknowledgements received from the cells to establish a groupcall.Trigger: each time VGCS/VBS ASS COM is received.

NUM_SUCC_SETUP_DISP_VGCS_VBSindicates how often a group call to a dispatcher is set up successfully.Trigger: each time IAM containing the dispatcher identity is sent by the group call anchorMSC or PAGE MS is sent by the MS.

CCU_OVERLOAD_SETUP_VGCS_VBSindicates the number of group call attempts being terminated unsuccessfully due tooverload after traffic attributes have been retrieved from GCRTrigger: each time the ASCI configuration is released due to an MSC internal overload.

CCU_LACK_CONF_UNITindicates the number of group call attempts being terminated unsuccessfully due to lackof ASCI conference resources in the MSC.Trigger: each time the ASCI configuration is released due to a lack of resources in theMSC.

CC_ANSW_VGCS_VBSindicates how many voice group calls and voice broadcasting events were answered.Trigger:each time ASCI CONNECT is sent to the conference LTG.

NUM_VGCS_TALK_RELindicates how often the actual talker in a voice group call has given up his speaker func-tion.Trigger:each time the MSC receives UPLINK REL IND from the BSC.

NUM_VGCS_TALK_REQindicates how often the MSC is requested for a talker function.

56 A50016-D1109-G801-6-7618


Trigger: each time the BSC sends UPLINK REQUEST to the MSC.

NUM_VGCS_TALK_ACKindicates how often a request for a talker function is allocated to the new speaker.Trigger:each time the MSC sends UPLINK REQUEST ACK.

NUM_VGCS_TALK_REJECTindicates how many requests for a talker function are rejected because the new speakerhas already been selected in another BSC.Trigger: each time the MSC sends UPLINK REJECT COMMAND.

NUM_VGCS_TALK_CONFIRMindicates how often the BSC has established dedicated resources for the new talker.Trigger: each time the MSC receives UPLINK REQUEST CONFIRM from a BSC.

NUM_ASCI_CALL_SETUP_TO_RMSCindicates how often a voice group call (VGC) or voice broadcasting (VB) has been setup to a relay MSC.Trigger: each time PREPARE GROUP CALL is sent to the relay MSC.

NUM_ASCI_CALL_SETUP_RECVD_RMSCindicates how often the relay MSC has received a request to set up a voice group call(VGC) or voice broadcasting (VB).Trigger: each time the relay MSC receives PREPARE GROUP CALL.

NUM_REQ_GCNRindicates how often a group call number is requested.Trigger: each time an internal procedure for allocating a GC NR is invoked upon receiv-ing PREPARE GROUP CALL.

NUM_ALLOC_GCNRindicates how often a group call number is allocated.Trigger: each time the relay MSC successfully allocates a GC NR upon receiving PRE-PARE GROUP CALL.

NUM_SEND_GCNR_TO_AMSCindicates how often a group call number is sent to the anchor MSC.Trigger: each time the relay MSC sends PREPARE GROUP CALL ACK.

NUM_RECVD_GCNR_IN_AMSCindicates how often the anchor MSC has received a group call number.Trigger: each time the anchor MSC receives PREPARE GROUP CALL ACK.

CA_VGCS_VBS_TERMindicates how often the anchor MSC has set up a link for attempts to terminate the groupcall in a relay MSC.Trigger: each time the digit translation results into MOB ASCI TERM upon receiving

A50016-D1109-G801-6-7618 57


Traffic Measurement

DIGIT BLOCK C.

SUCC_LINK_SETUP_TO_RMSCindicates how often links are successfully set up to a relay MSC.Trigger: each time the anchor MSC receives SENT GROUP CALL END SIGNAL.

SERV_SUB_VGCS_ATTEMPTS_IN_RMSCindicates how often service subscribers initiate voice group calls in the relay MSC.Trigger: each time ROUTE TO AMSC is received from the group call register.

SERV_SUB_VBS_ATTEMPTS_IN_RMSCindicates how often service subscribers initiate voice broadcasting in the relay MSC.Trigger: each time ROUTE TO AMSC is received from the group call register.

CA_MOB_SERV_SUB_IN_RMSCindicates how often the anchor MSC receives call attempts initiated by service subscrib-ers in the relay MSC.Trigger: each time digit analysis triggers a group call setup upon receiving DIGITBLOCK C.

CA_PTP_EMLPP_0indicates how often a mobile subscriber has set up a point-to-point call with a given pri-ority level. A counter is provided for each level; i.e. from level 0 (high) up to level 4 (low).Trigger: each time the following message is applied, indicating the eMLLP priority de-rived from the VLR.

MOC: ASSIGN REQUEST is sent on A interface.CM SERVICE REQUEST is received.

MTC: PAGING is sent.

CA_VGCS_VBS_EMLPP_Aindicates how often group calls have been set up with a given priority level. A counter isprovided for each level; i.e. from level A (high) up to level 4 (low).Trigger: each time the GCR sends VGCS ATR RESPONSE containing the attributesand the eMLLP priority.

58 A50016-D1109-G801-6-7618


4 Traffic Measurement for SSA supplementary service (SS) modifies or enhances the basic service and is used in as-sociation with one or all implemented basic services (speech or data service). In orderto collect information on the use of those services, a number of counters is implementedfor each SS. No distinction is made between the basic service group (telephony, facsim-ile transmission, bearer service) the service may be associated with.

Since the MSC is involved each time an SS is called in, the measurement of the resultingtraffic is carried out in the MSC. Therefore, measurement can be started there by enter-ing command REC SSERV.

The counters of the SS data in the MSC are focussed on:– call forwarding data– call barring data– special services for which can be registered:

the number of all invocations andthe number of successfully completed invocations

4.1 Supplementary Service: Call ForwardingINVOC_SERV_CALL_FORWARDindicates the number of invocations for call forwarding with respect to the proper condi-tion.Trigger:

CFU: each time a forwarded-to-number is received after HLR interrogation.CFB: each time a 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 aforwarded-to-number for a detached subscriber.

in VMSC: when an MTC has then been forwarded due to either no pagingresponse or to radio congestion.

SUCC_INVOC_SERV_CALL_FORWARDindicates the number of successful invocations for call forwarding with respect to theproper condition.Trigger:

CFU: each time a forwarded-to-number is received after HLR interrogation.CFB: each time a 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 aforwarded-to-number for a detached subscriber.

in VMSC: when an MTC has then been forwarded due to either no pagingresponse or to radio congestion.

A50016-D1109-G801-6-7618 59


Traffic Measurement

4.2 Supplementary Service: Call BarringSUCC_INVOC_SERV_CALL_BARRINGindicates how many invocations to bar all outgoing/incoming calls were completed suc-cessfully.Trigger: each time a specific service is invoked and successfully processed in the homeexchange.

4.3 Special Services: number of invocationsINVOC_SERV_AOC_CHARGEindicates the number of invocations for advice of charge, charging level.Trigger: each time this service is invoked.

INVOC_SERV_AOC_INFOindicates the number of invocations for advice of charge, information level.Trigger: each time this service is invoked.

INVOC_SERV_MULTIPARTYindicates the number of invocations for multiparty service.Trigger: each time this service is invoked and recognized during database access.

INVOC_SERV_PUT_HOLDindicates how often the SS for putting calls on hold is invoked.Trigger: each time the call on hold is released and this service is recognized during da-tabase access.

INVOC_SERV_RETRIEVE_HOLDindicates how often the service to retrieve held calls is invoked.Trigger: each time the call on hold is released and this service is recognized during da-tabase access.

INVOC_SERV_CLIPindicates the number of invocations for calling line identification presentation.Trigger: each time this service is invoked and recognized during database access.

INVOC_SERV_CLIRindicates the number of invocations for calling line identification restriction.Trigger: each time this service is invoked and recognized during database access.

INVOC_SERV_CALL_BACKindicates the number of invocations for call back.Trigger: each time this service is invoked and recognized during database access.

INVOC_SERV_CALL_TRANSFERindicates the number of invocations for call transfer.Trigger: each time this service is invoked and call transfer condition is recognized duringdatabase access.

60 A50016-D1109-G801-6-7618


INVOC_SERV_UUSindicates the number of invocations for user-to-user signaling service 1.Trigger: each time SETUP/EMERGENCY SETUP including the UUS1 indication is re-ceived.

INVOC_SERV_CCBS_MORTRindicates the number of invocations for the service completion of calls to busy subscriberfor MORTR.Trigger: each time the CCBS REQUEST is sent from MSC-A.

INVOC_SERV_CCBS_MTERindicates the number of invocations for the service completion of calls to busy subscriberfor MTER.Trigger: each time CCBS REQUEST is received in MSC-B.

4.4 Special Services: number of successfully completed invo-cationsSUCC_INVOC_AOC_CHARGEindicates how many invocations are completed successfully for advice of charge, charg-ing level.Trigger: each time this service is invoked and successfully processed in the home ex-change.

SUCC_INVOC_AOC_INFOindicates how many invocations are completed successfully for advice of charge, infor-mation level.Trigger: each time this service is invoked and successfully processed in the home ex-change.

SUCC_INVOC_MULTIPARTYindicates how many invocations are completed successfully for multiparty service.Trigger: each time this service is invoked and successfully processed in the home ex-change.

SUCC_INVOC_PUT_HOLDindicates how often a call is successfully put on hold.Trigger: each time the call on hold is released and successfully processed in the homeexchange.

SUCC_INVOC_RETRIEVE_HOLDindicates how often a held call is successfully retrieved.Trigger: each time the call on hold is released and successfully processed in the homeexchange.

SUCC_INVOC_CALL_BACKindicates how many invocations are completed successfully for call back.Trigger: each time this service is invoked and recognized during database access.

A50016-D1109-G801-6-7618 61


Traffic Measurement

SUCC_INVOC_CALL_TRANSFERindicates how many invocations are completed successfully for call transfer.Trigger: each time a new configuration is set up, a release or facility message is sent tothe MS including RETURN RESULT in response to INVOKE SS.

SUCC_INVOC_CCBS_MORTRindicates how many invocations are completed successfully for service completion ofcalls to busy subscriber for MORTR.Trigger: each time an IAM is sent to the MSC-B after the previous receipt of REMOTEUSER FREE.

SUCC_INVOC_CCBS_MTERindicates how many invocations are completed successfully for service completion ofcalls to busy subscriber for MTER.Trigger: each time an IAM is received in the MSC-B after the previous receipt of RE-MOTE USER FREE.

62 A50016-D1109-G801-6-7618


5 Cell-related Traffic MeasurementA number of cell-related counters is implemented for measuring the traffic on each in-dividual radio cell and its associated resources. They retrieve data on the radio interfacein order to plan and to dimension the entire radio service area. This cell-related trafficmeasurement is started by entering command REC INTCELL and selecting parameterINTCREL causing these counters to run for each cell.

The measurement of internal cell-related traffic relies on counters that make up:– a load and demand related part– a handover part.

5.1 Load and demand related part*ORIG_CALL_ATTEMPTSindicates the number of attempted calls for MORTR.Trigger: upon receipt of CM SERVICE REQUEST with the CM service type: mobile orig-inating call or emergency call establishment. Short message service and SS activationare not included.

*INCOM_CALL_ATTEMPTSindicates the number of attempted calls for MTER.Trigger: each time PAGING RESPONSE is received.

ORIG_CALL_ATT_TCH_REQindicates the number of attempted originating calls with traffic channel request.Trigger: with an originating call, each time ASSIGNMENT REQUEST is sent to the BSC.

INCOM_CALL_ATT_TCH_REQindicates the number of attempted incoming calls with traffic channel request.Trigger: with a terminating call, each time ASSIGNMENT REQUEST is sent to the BSC.

ORIG_CALL_ATT_QUEUINGindicates the number of attempted originating calls where queuing was active for MOR-TR.Trigger: each time the QUEUING INDICATION is received.

INCOM_CALL_ATT_QUEUINGindicates the number of attempted incoming calls where queuing was active for MTER.Trigger: each time the QUEUING INDICATION is received.

*ORIG_CALL_SUCC_TCH_ALLOCindicates the number of mobile originating calls with successful traffic channel alloca-tion.Trigger: each time ASSIGNMENT COMPLETE is received without previous queuing.It is also (internally) triggered for technical reasons for the second, parallel call in caseof the call held function without receipt of ASSIGNMENT COMPLETE on the A-Interface(compare MSC measurement).

A50016-D1109-G801-6-7618 63


Traffic Measurement

*INCOM_CALL_SUCC_TCH_ALLOCindicates the number of mobile terminating calls with successful traffic channel alloca-tion.Trigger: upon each receipt of ASSIGNMENT COMPLETE without previous queuing.It can also be (internally) triggered in the same way as described for originating calls.

ORIG_CALL_QUEUE_TCH_ALLOCindicates the number of attempted originating calls for which queuing is active and a traf-fic channel was successffully allocated for MORTR.Trigger: each time ASSIGNMENT COMPLETE is received after receipt of QUEUING IN-DICATION.

INCOM_CALL_QUEUE_TCH_ALLOCindicates the number of attempted incoming calls for which queuing was active and atraffic channel was allocated successfully for MORTR.Trigger: each time ASSIGNMENT COMPLETE is received and queuing is active.

*REL_CALL_BS_REASONindicates the number of calls that were terminated during setup for base station/radiorelated reasons.Trigger: during call setup, prior to CONNECT, each time SUBSYSTEM PROHIBITED,RESET, RESET CIRCUIT, RELEASE COMMAND/CLEAR REQUEST are received.

*REL_ANSW_CALL_BS_REASONindicates the number of answered calls that are terminated for base station/radio relatedreasons.Trigger: after CONNECT ACK, each time SUBSYSTEM PROHIBITED, RESET, RESETCIRCUIT, RELEASE COMMAND/CLEAR REQUEST are received.

ANSW_ORIG_CALLindicates the number of answered calls for MORTR.Trigger: release of call when previous CONNECT ACK is received.

ANSW_INCOM_CALLSindicates the number of answered calls for MTER.Trigger: release of call when previous CONNECT ACK is received.

5.2 Handover partHO_REQUIREDindicates how many handover requests are received.Trigger: each time HANDOVER REQUIRED is received.

INTRACELL_HO_MSCindicates the number of successfully performed MSC controlled intra-cell handovers.Trigger: each time HANDOVER COMPLETE is received.

64 A50016-D1109-G801-6-7618


INTRACELL_HO_BSCindicates the number of successfully performed BSS controlled intra-cell handovers.Trigger: each time HANDOVER PERFORMED is received.

INTERCELL_HO_OUTGindicates the number of successfully performed outgoing inter-cell handovers.Trigger: each time HANDOVER COMPLETE is received.

INTERCELL_HO_INCindicates the number of successfully performed incoming inter-cell handovers.Trigger: each time HANDOVER COMPLETE is received.

A50016-D1109-G801-6-7618 65


Traffic Measurement

6 Traffic-structure Measurement for HOFor a detailed analysis of the traffic flow between two radio cells caused by handovers,both cells are measured; the target cell can belong to either the MSC being measuredor to another MSC. Only MSC controlled handovers are registered.

Therefore, two matrices are built up for every cell (identified by a LACOD and a cell iden-tity CI) of the MSC area.– One matrix consists of origin cells where all outgoing handovers (attempts and suc-

cessful completions leaving the cell) are measured.– The other matrix consists of target cells where all incoming handovers (attempts and

successful completions entering the cell) are measured.

The measurement of such cell-related traffic data is started by entering command RECINTCELL and selecting parameter HOTRFS causing the handover counters to run forall cells.

HANDOVER_ATTEMPTSindicates for each origin/target cell the respective handover attempts.Trigger: each time a HANDOVER REQUEST is sent to the BSS in reply to a HAN-DOVER REQUIRED.

SUCCESSFUL_HANDOVERSindicates for each origin/target cell the respective handovers being completed success-fully.Trigger: each time a HANDOVER COMPLETE is received.

66 A50016-D1109-G801-6-7618


7 Traffic Measurement in IWEIn order to handle data services, it is necessary to introduce functionally different typesof interworking equipment (IWE) that carry out e.g. rate adaptations towards the BSS,and modem and codec functions towards the external network. For this purpose it is im-portant to collect traffic data involving any type of IWE.In addition, this traffic measurement sets the requirement profile of the different data ser-vices required by the subscribers.

The measurement of IWE traffic data is started by entering command REC IWE causingIWE counters to run.

This traffic measurement relies on counters that make up:– a load and demand related part– a grade of service related part focussing on:

unsuccessful attempts,forced released calls,holding times

– alternate speech fax 3

7.1 Load and demand related partIWE_ANALOG_TPindicates how many attempts were made to interconnect an IWE for the transfer of an-alog data at a given user rate in circuit duplex asynchronous (CDA) and transparentmode.Trigger: each time the IWE device is selected for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S1200/75 B/S14400 B/S19200 B/S28800 B/S

IWE_ANALOG_NTPindicates how many attempts were made to interconnect an IWE for the transfer of an-alog data at a given user rate in circuit duplex asynchronous (CDA) and non-transparentmode.Trigger: each time the IWE device is selected for the respective bearer service of:


A50016-D1109-G801-6-7618 67


Traffic Measurement

IWE_DIGITAL_TPindicates how many attempts were made to interconnect an IWE for the transfer of dig-ital data at a given user rate in circuit duplex asynchronous (CDA) and transparentmode.Trigger: each time the IWE device is selected for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S

IWE_DIGITAL_NTPindicates how many attempts were made to interconnect an IWE for the transfer of dig-ital data at a given user rate in circuit duplex asynchronous (CDA) and non-transparentmode.Trigger: each time the IWE device is selected for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S38400 B/S

IWE_FAX3_TPindicates how many attempts were made to interconnect an IWE for fax group 3 com-munication, transparent mode.Trigger: each time the IWE device is selected for teleservice 61 at a user rate of:

2400 B/S4800 B/S9600 B/S

IWE_ANACDS_NTPindicates how many attempts were made to interconnect an IWE for the transfer of an-alog data at a given user rate in CDS and in non-transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

IWE_DIGCDS_NTPindicates how many attempts were made to interconnect an IWE for the transfer of dig-ital data at a given user rate in CDS and in non-transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

68 A50016-D1109-G801-6-7618


7.2 Grade of service related part: unsuccessful attemptsUNS_IWE_ANALOG_TPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of analog data at a given user rate in CDA and transpar-ent mode.Trigger: each time the IWE device is selected for the respective bearer service of:


UNS_IWE_ANALOG_NTPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of analog data at a given user rate in CDA and non-transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:


UNS_IWE_DIGITAL_TPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of digital data in CDA and transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S

UNS_IWE_DIGITAL_NTPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of digital data in CDA and non-transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:

300 B/S1200 B/S2400 B/S

A50016-D1109-G801-6-7618 69


Traffic Measurement

4800 B/S9600 B/S19200 B/S38400 B/S

UNS_IWE_FAX3_TPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for fax group 3 in transparent mode.Trigger: each time the IWE device is selected for teleservice 61 at a user rate of:

2400 B/S4800 B/S9600 B/S

UNS_IWE_ANACDS_NTPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of analog datafor the transfer of digital data at a givenuser rate in CDS and non-transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

UNS_IWE_DIGCDS_NTPindicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of digital data in CDS and non-transparent mode.Trigger: each time the IWE device is selected for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

7.3 Grade of service related part: forced released callsFRC_IWE_ANALOG_TPindicates how many calls are forced released by the IWE for analog data at a given userrate in CDA and transparent mode.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for the respective bearer service of:


70 A50016-D1109-G801-6-7618


FRC_IWE_ANALOG_NTPindicates how many calls are forced released by the IWE for analog data at a given userrate in CDA and non-transparent mode.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for the respective bearer service of:


FRC_IWE_DIGITAL_TPindicates how many calls are forced released by the IWE for digital data at a given userrate in CDA and transparent mode.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S

FRC_IWE_DIGITAL_NTPindicates how many calls are forced released by the IWE for digital data at a given userrate in CDA and non-transparent mode.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S38400 B/S

FRC_IWE_FAX3_TPiindicates how many calls are forced released by the IWE for fax group 3 communicationin transparent mode due to lack of resources.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for teleservice 61 at a user rate of:

2400 B/S4800 B/S9600 B/S

A50016-D1109-G801-6-7618 71


Traffic Measurement

FRC_IWE_ANACDS_NTPindicates how many calls are forced released by the IWE for analog data at a given userrate in CDS and non-transparent mode.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

FRC_IWE_DIGCDS_NTPindicates how many calls are forced released by the IWE for digital data at a given userrate in CDS and non-transparent mode.Trigger: each time a forced release due to an IWE malfunction takes place, orat a 30 seconds time-out for IWE synchronization for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

7.4 Grade of service related part: holding timesTV_IWE_ANALOG_TPindicates how long the IWE device is interconnected for all calls insofar they concern thetransfer of analog data at a given user rate in CDA and transparent mode.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:


TV_IWE_ANALOG_NTPindicates how long the IWE device is interconnected for all calls insofar they concern thetransfer of analog data at a given user rate in CDA and non-transparent mode.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S1200/75 B/S14400 B/S19200 B/S

72 A50016-D1109-G801-6-7618


28800 B/S

TV_IWE_DIGITAL_TPindicates how long the IWE device is interconnected for all calls insofar they concern thetransfer of digital data at a given user rate in CDA and transparent mode.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S

TV_IWE_DIGITAL_NTPindicates how long the IWE device is interconnected for all calls insofar they concern thetransfer of digital data at a given user rate in CDA and non-transparent mode.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S19200 B/S38400 B/S

TV_IWE_FAX3_TPindicates how long the IWE device is interconnected for fax group 3 calls in transparentmode.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for teleservice 61 at a user rate of:

2400 B/S4800 B/S9600 B/S

TV_IWE_ANACDS_NTPindicates how long the IWE device is interconnected for all calls insofar they concern thetransfer of analog data at a given user rate in CDS and non-transparent mode.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

TV_IWE_DIGCDS_NTPindicates how long the IWE device is interconnected for all calls insofar they concern thetransfer of digital data at a given user rate in CDS and non-transparent mode.

A50016-D1109-G801-6-7618 73


Traffic Measurement

Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:

1200 B/S2400 B/S4800 B/S9600 B/S

7.5 Grade of service related part: upgrading and downgradingUPGRADING_USER_INITindicates how many level upgrades were initated by the user; i.e. when the user has re-quested a higher user rate at the air interface than the actual one.Trigger: each time MODIFY RESULT for successful upgrading is sent to BSSAP-LTG.

UPGRADING_NETWORK_INITindicates how many level upgrades were initated by the network.Trigger: each time UPDATE CHANNEL for upgrading during handover is sent toBSSAP-LTG.

DOWNGRADING_USER_INITindicates how many level downgrades were initated by the user; i.e. when the user hasrequested a lower user rate at the air interface than the actual one.Trigger: each time MODIFY RESULT for successful downgrading is sent to BSSAP-LTG.

DOWNGRADING_NETWORK_INITindicates how many level downgrades were initated by the network.Trigger: each time UPDATE CHANNEL for downgrading during handover is sent toBSSAP-LTG.

UNS_UPGRADING_USER_INITindicates how many level upgrades were initated by the user unsuccessfully. In thatcase, the old configuration will be restored.Trigger: each time MODIFY RESULT indicating an unsuccessful upgrading is sent toBSSAP-LTG.

UNS_DOWNGRADING_USER_INITindicates how many level downgrades were initated by the user unsuccessfully. In thatcase, the old configuration will be restored.Trigger: each time MODIFY RESULT indicating an unsuccessful downgrading is sent toBSSAP-LTG.

74 A50016-D1109-G801-6-7618


7.6 Alternate speech fax 3IWE_SP_FAX3_TPindicates how many attempts are made to interconnect an IWE for alternate speech/fac-simile group 3, transparent mode for fax transmission only.Trigger: each time the IWE device is selected for teleservice 61 in transparent mode.

UNS_IWE_SP_FAX3_TPindicates how many unsuccessful attempts are made to interconnect an IWE for alter-nate speech/facsimile group 3, transparent mode, due to lack of IWE.Trigger: upon each failure to seize an IWE device for teleservice 61 in transparent mode.

FRC_IWE_SP_FAX3_TPindicates how many calls are forced released by IWE for alternate speech/facsimilegroup 3, transparent mode.Trigger: upon each call that is forced released due to IWE malfunction, or at a 30 sec-onds timeout for IWE synchronization.

TV_SP_FAX3_TPindicates the total holding time to interconnect an IWE for alternate speech/facsimilegroup 3, transparent mode for fax transmission only.Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease).

A50016-D1109-G801-6-7618 75


Traffic Measurement

8 Traffic Measurement in the VLRThe VLR is a dynamic subscriber database consisting of data on home and foreign sub-scribers who are roaming in the VLR area. This requires the following functions:– mobility management functions, such as location updating– safeguarding functions, such as: authentication, encryption, TMSI reallocation– interworking functions with the previous VLR and the HLR to retrieve information

from.

Therefore, traffic data can be collected in the VLR by entering the command REC VLR.Traffic data measurement in the VLR relies on counters that make up:– the installation related part focussing on non-static data (e.g. numbers of registered

subscribers in the VLR database)– load and grade of service related part– security functions related part– external interworking related part– combined paging and combined location update part

8.1 Installation related partENTRY_USED_OWNindicates the number of subscribers of home PLMN registered in the VLR.Trigger: for each home MS:

increased when an entry in the VLR is created;decreased when an entry in the VLR is deleted.

ENTRY_USED_FOREIGNindicates the number of subscribers of other PLMNs registered in the VLR.Trigger: for each foreign MS:

increased when an entry in the VLR is created;decreased when an entry in the VLR is deleted.

ENTRY_SS_ACTindicates the number of subscribers with activated SS.Trigger: VLR entry exists (home and foreign MS) and subscriber has activated one SS.

ENTRY_OP_BARRindicates how many subscribers being barred by the operator are registered in the VLR.Trigger: each time the VLR has received INSERT SUBSCRIBER DATA indicating:

- Ph 1: an operator outgoing call barring status;- Ph 2: an ODB subscription.

ENTRY_USED_DETACHindicates the number of detached subscribers in the VLR.Trigger: each time VLR entry exists and entry is implicitly or explicitly marked as de-tached.

DETACH_MSG_TMSI_NO_IMSI_CORRindicates the number of received DETACH messages with TMSI and no IMSI correlationis found.

76 A50016-D1109-G801-6-7618


Trigger: each time COMPLETE LAYER 3 including IMSI detach indication and TMSI isreceived and no TMSI/IMSI correlation is found.

VLR_AREA_LEAVES_OWN_PLMNindicates the number of location updates at which the subscriber of the home PLMNleaves the VLR area.Trigger: each time CANCEL LOCATION for a home MS is received in PVLR.

VLR_AREA_LEAVES_FOREIGN_PLMNindicates the number of location updates at which the subscriber of a foreign PLMNleaves the VLR area.Trigger: each time CANCEL LOCATION for a foreign MS is received in PVLR.

LA_CHANGES_OWN_PLMNindicates the number of location area changes at which the subscriber of the homePLMN stays in the VLR area.Trigger: each time Location Update REQUEST for home MS is received, whereby newLAI belongs to home (old) VLR area.

LA_CHANGES_FOREIGN_PLMNindicates the number of location area changes at which the subscriber of a foreignPLMN stays in the VLR area.Trigger: each time Location Update REQUEST is received, whereby the new LAI be-longs to home (old) VLR area.

EXPLICIT_IMSI_DETACHindicates the number of handled procedures for an explicit IMSI detach.Trigger: each time COMPLETE LAYER 3 with IMSI detach indication is received.

IMPLICIT_IMSI_DETACHindicates the number of implicit handled IMSI detach procedures.Trigger: each time PROVIDE MSRN, SEND INFO IC, SEND INFO IC SM is receivedand the time for periodic location updating is exceeded.

8.2 Load and grade of service related partREQUESTS_LOCUPDindicates the number of requests for location updating (normal, periodic attach, invalidIMSI attach).Trigger: each time LOCATION UPDATE REQUEST is received.

REQUEST_LOCUPD_INTRA_VLRindicates the number of attempted location updatings (normal, periodic, IMSI attach)within the VLR.Trigger: each time LOCATION UPDATE REQUEST for an intra VLR location is re-ceived.

A50016-D1109-G801-6-7618 77


Traffic Measurement

REQUEST_LOCUPD_INTER_VLRindicates the number of attempted normal location updatings between VLRs.Trigger: each time LOCATION UPDATE REQUEST is received and LAC translation in-dicates VLR area change.

REQUESTS_PERIODIC_LOCUPDindicates the number of requests for periodic location updating.Trigger: each time LOCATION UPDATE REQUEST containing type “periodic” is re-ceived.

REQUESTS_LOCUPD_WITH_IMSI_ATTindicates the number of requests for location updating caused by IMSI attach.Trigger: each time LOCATION UPDATE REQUEST containing type “IMSI attach” is re-ceived.

SUCC_REQUESTS_LOCUPDindicates the number of successfully handled requests for location updating (normal, pe-riodic).Trigger: each time LOCATION UPDATE ACCEPT is received.

SUCC_LOCUPD_WITH_IMSI_ATTACHindicates the number of successfully handled location update requests for an IMSI at-tach.Trigger: each time LOCATION UPDATE ACCEPT containing “IMSI attach” is sent to theBSS.

LOCUPD_LAI_NULLindicates the number of location updates with old LAI = 0 (e.g. at registration with MSrecovery).Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS.

CALL_WITH_UNIDENT_SUBindicates the number of MOCs with “unidentified subscriber” causing location updating.Trigger: each time Service request (CMS REQ) is received and MS unknown in the VLRor location area is not allowed.

LA_CHANGES_AFTER_RECOVindicates the number of location area changes within the VLR after VLR recovery.Trigger: each time LOCATION UPDATE REQUEST is received, LAI new belongs tohome (old) VLR area and a VLR recovery has occurred (this causes HLR interworkingnot to be performed without previous recovery).

VLR_CHANGES_PVLR_KNOWNindicates the number of VLR area changes where the PVLR is known.Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS and the PVLR isknown from the LAC.

78 A50016-D1109-G801-6-7618


VLR_CHANGES_PVLR_UNKNOWNindicates the number of VLR area changes where the PVLR is unknown.Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS and the PVLR isunknown.

REQUESTS_LOCUPD_TO_HLRindicates the number of requests for location updating sent to the HLR.Trigger: each time LOCATION UPDATE ACCEPT is sent to the HLR.

RESULTS_LOCUPD_FROM_HLRindicates the number of successes from HLR for location updating.Trigger: each time TC-END result-L for UPDATE LOCATION is received from the HLR.

INTW_HLR_RESTOR_HLRindicates the number of additional location update interworkings between VLR and HLRcaused by HLR restoration.Trigger: each time TC-BEGIN invoke UPDATE LOCATION is sent to HLR after previousHLR restoration.

RESULTS_LOCUPD_FROM_PVLRindicates the number of successes from PVLR for location updating.Trigger: each time TC-END result-L for UPDATE LOCATION is received from the PVLR.

RECEIVED_DETACH_WITH_IMSIindicates the number of received detach messages with IMSI.Trigger: each time IMSI DETACH including MS identification by IMSI is received.

RECEIVED_DETACH_WITH_TMSIindicates the number of received detach messages with TMSI.Trigger: each time IMSI DETACH including the MS identification by TMSI is received.

RECEIVED_DETACH_NO_VLR_ENTRYindicates the number of received detach messages with no corresponding VLR entry.Trigger: each time IMSI DETACH is received and no VLR entry is found for the corre-sponding IMSI/TMSI.

INTW_HLR_UNKNOWN_SUBindicates the number of unsuccessful HLR interworkings because the subscriber wasnot known.Trigger: each time TC-END U-Error due to unknown subscriber is received from HLR inresponse to TC-BEGIN invoke UPDATE LOCATION.

INTW_HLR_ROAMING_NOT_ALLOWEDindicates the number of unsuccessful HLR interworkings because roaming is not al-lowed.Trigger: each time TC-END U-Error due to roaming not allowed is received from HLR inresponse to TC-BEGIN invoke UPDATE LOCATION.

A50016-D1109-G801-6-7618 79


Traffic Measurement

INTW_HLR_TCAP_TIMER_EXPIRYindicates the number of unsuccessful HLR interworkings because TCAP timer expired.Trigger: each time T-LU expires (no HLR response).

INTW_HLR_DEST_OUT_OF_SERVICEindicates the number of unsuccessful HLR interworkings because the destination wasout of service.Trigger: each time TC-NOTICE is received due to destination out of service.

INTW_HLR_SYSTEM_FAILUREindicates the number of unsuccessful HLR interworkings because the HLR systemfailed.Trigger: each time TC-END U-ERROR is received from the HLR due to system failure.

INTW_HLR_TCAP_ABORTindicates the number of unsuccessful HLR interworkings because the TCAP aborted.Trigger: each time TC-ABORT is received.

INTW_HLR_PROTOCOL_ERRORSindicates the number of unsuccessful HLR interworkings due to protocol errors (invoke,result, error, general problems).Trigger: upon each occurrence of unsuccessful UPDATE LOCATION or INSERT SUB-SCRIBER DATA dialogs due to protocol errors, such as: REJECT component receiveddue to protocol error, L REJECT received due to internal protocol error.

INTW_HLR_OTHER_REASONSindicates the number of unsuccessful HLR interworkings due to reasons different fromthose covered by the previous counters.Trigger: upon each occurrence of an unsuccessful UPDATE LOCATION dialog e.g. TC-END U-ERROR unexpected data value, missing data in INSERT SUBSCRIBER DATA,missing resources in the VLR, subscriber cancelled in the meantime.

INTW_PVLR_UNIDENT_SUBindicates the number of unsuccessful PVLR interworkings because the subscriber can-not be identified.Trigger: each time TC END U-ERROR due to unidentified subscriber is received fromthe PVLR in response to

- Ph1: TC BEGIN invoke SEND PARAMETERS- Ph2: TC BEGIN invoke SEND IDENTIFICATION

INTW_PVLR_TCAP_TIMER_EXPIRYindicates the number of unsuccessful PVLR interworkings because the TCAP timer ex-pired.Trigger: each time timer expires.

- Ph1: T-par- Ph2: T-si

80 A50016-D1109-G801-6-7618


INTW_PVLR_DEST_OUT_OF_SERVICEindicates the number of unsuccessful PVLR interworkings because the destination wasout of service.Trigger: each time TC-NOTICE is received due to destination out of service.

INTW_PVLR_TCAP_ABORTindicates the number of unsuccessful PVLR interworkings due to TCAP abort.Trigger: each time TC-ABORT is received from TCAP.

INTW_PVLR_PROTOCOL_ERRORSindicates the number of unsuccessful PVLR interworkings due to protocol errors (in-voke, result, error, general problems).Trigger: each time that protocol errors are detected in the MAP dialog to PVLR.

- Ph1: SEND PARAMETERS- Ph2: SEND IDENTIFICATION

INTW_PVLR_OTHER_REASONSindicates the number of unsuccessful PVLR interworkings because of reasons differentfrom those covered by the previous counters.Trigger: each time that errors during MAP dialog to PVLR are detected that are not cov-ered by the other counters for PVLR interworking.

INTW_BSS_IMSI_UNKNOWN_IN_HLRindicates the number of unsuccessful BSS interworkings because the IMSI is not knownin the HLR.Trigger: each time LOCATION UPDATE REJECT indicating IMSI unknown is sent to theMS.

INTW_BSS_ILLEGAL_SUBindicates the number of unsuccessful BSS interworkings because the subscriber was il-legal.Trigger: each time LOCATION UPDATE REJECT indicating illegal MS is sent to the MS.

INTW_BSS_PLMN_NOT_ALLOWEDindicates the number of UNSUCCESSFUL BSS interworkings because the PLMN wasnot allowed.Trigger: each time LOCATION UPDATE REJECT indicating PLMN not allowed is sentto the MS.

INTW_BSS_LOCAREA_NOT_ALLOWEDindicates the number of unsuccessful BSS interworkings because the location area wasnot allowed.Trigger: each time LOCATION UPDATE REJECT indicating location area not allowedis sent to the MS.

INTW_BSS_NETWORK_FAILUREindicates the number of unsuccessful BSS interworkings because the network hasfailed.

A50016-D1109-G801-6-7618 81


Traffic Measurement

Trigger: each time LOCATION UPDATE REJECT indicating network failure is sent tothe MS.

INTW_BSS_RADIO_REASONS1indicates the number of unsuccessful BSS interworkings due to radio/BSS-related rea-sons concerning BSS/MSC connection failures.Trigger: the receipt of CLEAR REQUEST.

INTW_BSS_RADIO_REASONS2indicates the number of unsuccessful BSS interworkings because the radio/BSS-relatedreasons concerning protocol errors - (new) LAI unknown (database inconsistency).Trigger: each time LOCATION UPDATE REJECT is sent to the MS due to unspecifiedprotocol error.

INTW_BSS_LAI_UNKNOWNindicates the number of unsuccessful BSS interworkings because the (new) LAI is notknown.Trigger: each time LOCATION UPDATE REQUEST is received and the new LAI doesnot exist in the VLR.

INTW_BSS_SECOND_TRANS_LOCUPDindicates the number of unsuccessful BSS interworkings due to second transaction forlocation updating (MS failure).Trigger: each time LOCATION UPDATE REJECT is sent to the MS due to network fail-ure when the second transaction was recognized.

INTW_BSS_OTHER_REASONSindicates the number of unsuccessful BSS interworkings for reasons that are not cov-ered by the previous counters.Trigger: each time LOCATION UPDATE REJECT is sent to the MS with error that arenot covered by the other counters for BSS interworking.

INTW_BSS_ILLEGAL_MEindicates the number of unsuccessful BSS interworkings because the mobile equipment(ME) is from the black list or unknown.Trigger: each time message Location Update Reject indicating “Illegal ME” is sent to theBSC/MS.

CAMEL_PSIindicates the number of information requests received from the HLR in order to retrievethe subscriber’s location intended for CAMEL services.Trigger: each time PROVIDE SUBSCRIBER INFO is received from the HLR.

8.3 Security functions related partSUB_IDENTIFIED_WITH_TMSIindicates the number of handled transactions (e.g. MOC, MTC, SCI) where the subscrib-er was identified with TMSI.

82 A50016-D1109-G801-6-7618


Trigger: each time TMSI is used unciphered on the air interface (from MS).

SUB_IDENTIFIED_WITH_IMSIindicates the number of handled transactions (e.g. MOC, MTC, SCI) where subscriberwas identified with IMSI.Trigger: each time IMSI is used unciphered on the air interface (from MS).

IDENTITY_REQUESTSindicates the total number of identity requests.Trigger: each time IDENTITY REQUEST is sent on the A-Interface.

IDENT_REQ_CORR_FAILUREindicates the number of identity requests caused by failure of the IMSI/TMSI correlation.Trigger: each time IDENTITY REQUEST is sent on the A-Interface after detection of IM-SI/TMSI correlation failure.

IDENT_REQ_INTW_PVLR_FAILUREindicates the number of identity requests caused by failure of interworking with PVLR.Trigger: each time IDENTITY REQUEST is sent on the A-Interface after a PVLR inter-working failure.

IDENT_REQ_AUTH_FAILUREindicates the number of identity requests caused by authentication failure when sub-scriber was previously identified with TMSI.Trigger: each time IDENTITY REQUEST is sent on the A-Interface after detection of au-thentication failure.

AUTH_REQindicates the number of authentication requests.Trigger: each time AUTHENTICATION REQUEST is sent to the MS.

AUTHENTICATION REQUEST_CKSN_MISMATCHindicates the number of authentication requests initiated by a mismatch of the cipher keysequence number (CKSN).Trigger: each time AUTHENTICATION REQUEST is sent to the MS after detection ofCKSN mismatch.

CIPHERING_REQindicates the number of ciphering requests.Trigger: each time CIPHERING COMMAND is sent to the MS.

SEND_PARAM_REQ_TRIPLES_TO_HLRindicates how often a request for triples is sent to the HLR.Trigger: upon sending the appropriate message to the HLR.

- Ph1: SEND PARAMETERS- Ph2: SEND AUTHENTICATION INFO

A50016-D1109-G801-6-7618 83


Traffic Measurement

SEND_PARAM_REQ_SUBDAT_TO_HLRindicates how often a request for parameters (e.g. IMSI) is sent to the HLR.Trigger: upon sending the appropriate message to the HLR.

- Ph1: SEND PARAMETERS- Ph2: RESTORE DATA

RECVD_AUTH_INF_TRIPLES_HLRindicates the number of acknowledgments containing triples that are received from theHLR.Trigger: each time TC-END Return Result-L is received from the HLR in response to


SEND_PARAM_REQ_TRIPLES_TO_PVLRindicates how often a request for triples is sent to the PVLR.Trigger: each time SEND IDENTIFICATION is sent to the PVLR.

RECVD_AUTH_INF_TRIPLES_PVLRindicates the number of acknowledgments containing triples received from the PVLR.Trigger: each time TC-END Return Result-L is received from PVLR in response to


SEND_PAR_RECVD_FROM_OTHER_VLRindicates the number of messages received from other VLRs requesting triples.Trigger: each time SEND IDENTIFICATION is received.

SEND_TRIPLES_TO_VLRindicates the number of successful authentication sets that are received and sent to oth-er VLRs.Trigger: each time TC-END Return Result-L is sent to other VLR in response to


AUTH_WITH_ILLEGAL_SUBindicates the number of authentications with outcome ”illegal subscriber”.Trigger: each time AUTHENTICATION REJECT indicating illegal MS is sent toBSC/MS.

WRITTEN_MISMATCH_RECORDSindicates the number of written mismatch records.Trigger: each time AUTHENTICATION REJECT indicating illegal MS was sent anddataset was saved successfully.

REUSED_TRIPLESindicates the number of reused triples.Trigger: each time AUTHENTICATION REQUEST containing an old triple is sent to theMS.

84 A50016-D1109-G801-6-7618


ATTEMPTED_TMSI_REALLOCATIONSindicates the number of attempted TMSI reallocations.Trigger: each time TMSI REALLOCATION COMMAND or LOC UPD ACC containing aTIMSI reallocation request is sent to BSC/MS.

TMSI_REALLOC_NOT_ANSWEREDindicates the number of VLR database requests achieving two (old/new) allocated TM-SIs (missing MS answer after reallocation).Trigger: each time COMPLETE LAYER 3 INFO containing IMSI/TMSI that leads to de-letion of old TMSI is received.

SUCCESSFUL_TMSI_REALLOCindicates the number of successful TMSI reallocations.Trigger: each time TMSI REALLOCATION COMPLETE is received from MS/BSC.

EMPTY_RESPONSE_TO_AUTH_SETindicates the number of empty responses to requests for authentication sets.Trigger: each time SEND AUTHENTICATION INFO is sent to the HLR and TC-RE-SULT/Response is received without authentication triples included.

SUCC_CIPH_MODE_CTRL_PROCindicates the number of successful ciphering mode control procedures.Trigger: each time CIPHERING MODE COMPLETE is received from MS/BSC.

8.4 External interworking related partINSERT_FROM_HLR_LOCUPDindicates the number of messages containing subscriber data that is received from theHLR during location update.Trigger: each time INSERT SUBSCRIBER DATA is received from the HLR in responseto UPDATE LOCATION.

INSERT_FROM_HLR_OCI_SCIindicates the number of messages containing subscriber data that is received from theHLR during subscriber or operator controlled input.Trigger: each time INSERT SUBSCRIBER DATA is received from HLR due to operatoror subscriber controlled input.

DELETE_FROM_HLRindicates the number of relevant messages received from the HLR.Trigger: each time DELETE SUBSCRIBER DATA is received from the HLR.

PROVIDE_MSRN_RECEIVEDindicates the number of relevant messages received from the HLR.Trigger: each time PROVIDE ROAMING NUMBER is received.

MORE_THAN_ONE_MSRN_ALLOCindicates how often more than one MSRN was allocated for the same subscriber.

A50016-D1109-G801-6-7618 85


Traffic Measurement

Trigger: each time PROVIDE ROAMING NUMBER is received.The MSRN is allocated for the called MS and another MSRN (up to 3 possible) allocatedfor this MS.

MSRN_TIMER_EXPIRESindicates how often the MSRN release supervision timer expires.Trigger: each time that, with MSRN allocated, the timer for MSRN allocation expirescausing the MSRN to be released.

RESETS_RECEIVED_FROM_HLRindicates how often a reset message is received from the HLR.Trigger: each time RESET is received.

ACT_TRACEMODE_FROM_HLRindicates how often the relevant message is received from the HLR.Trigger: each time ACTIVATE TRACEMODE is received.

DEACT_TRACEMODE_FROM_HLRindicates how often the relevant message is received from the HLR.Trigger: each time DEACTIVATE TRACEMODE is received.

RESTORE_DATA_TO_HLRindicates how often the relevant message is sent to the HLR.Trigger: each time RESTORE DATA is sent.

MS_MEMORY_AVAIL_TO_HLRindicates the number of relevant messages sent to the HLR.Trigger: each time the proper message is sent to the HLR.

- Ph1: NOTE MS PRESENT- Ph2: READY FOR SM including “memory available”

SUCCESS_MS_MEMORY_AVAILindicates the number of successful relevant messages to the HLR.Trigger: each time TC-RESULT is received from the HLR upon sending the proper mes-sage.

- Ph1: NOTE MS PRESENT- Ph2: READY FOR SM including “memory available”

SENT_PURGE_MS_MSG_TO_HLRindicates how many mobile subscriber purging messages the VLR has sent to the HLR.When a new subscriber record is created in the VLR whose database is filled to 80%while the subscriber’s last radio access is older than 5 days, the VLR will inform the HLR.Trigger: each time GENERATE ENTRY is sent provided the proper conditions are met.

REG_SS_TO_HLRindicates how many registrations for all SS are sent to the HLR.Trigger: each time REGISTER SS is sent.

86 A50016-D1109-G801-6-7618


ERA_SS_TO_HLRindicates how many erasures for all SS are sent to the HLR.Trigger: each time ERASURE SS is sent.

ACT_SS_TO_HLRindicates how many activations for all SS are sent to the HLR.Trigger: each time ACTIVATE SS is sent.

DEACT_SS_TO_HLRindicates how many deactivations for all SS are sent to the HLR.Trigger: each time DEACTIVATE SS is sent.

CHECK_SS_FROM_HLRindicates how many messages for SS checks are received from the HLR.Trigger: each time REGISTER SS, ACTIVATE SS, etc. for SS is sent and the SS checkresult is received.

INTERROG_TO_HLRindicates how many SS interrogations the VLR sends to the HLR.Trigger: each time INTERROGATE SS is sent.

INTERROG_HANDLED_BY_VLRindicates how many SS interrogations are handled by the VLR without HLR interwork-ing.Trigger: each time INTERROGATE SS is received from the BSC/MS.

INTERROG_UNSUCC_SUBSCRindicates how many SS interrogations are unsuccessfully handled due to subscriber be-havior.Trigger: each time MAP errors (illegal SS operation, SS error status, SS not available,SS incompatibility) are received.

INTERROG_UNSUCC_SYSTEMindicates how many SS interrogations are unsuccessfully handled due to system behav-ior.Trigger: each time MAP errors (unknown subscriber, unexpected data value, data miss-ing) are received.

UNSTRUC_SS_DATA_TO_HLRindicates how many messages for unstructured SS are sent.Trigger: each time PROCESS UNSTRUCTURED SS REQUEST is sent to the HLR.

INVOKE_SS_BAOCindicates the number of successful invocations of all outgoing barring services.Trigger: each time that, during MOC or SMS-MO establishment, data base access rec-ognizes that the SS “barring of all outgoing calls” is active for the subscriber.

A50016-D1109-G801-6-7618 87


Traffic Measurement

INVOKE_SS_BOICindicates the number of successful invocations of all outgoing international barring ser-vices.Trigger: each time that, during MOC or SMS-MO establishment, data base access rec-ognizes that the SS “barring of all outgoing international calls” is active for the subscrib-er.

SENT_NI_USSD_TO_MSindicates how many messages for unstructured supplementary service data being initi-ated by the network are sent to the BSSAP-LTG.Trigger: each time USS REQUEST or USS NOTIFY after a successful paging is sent.

SENT_MI_USSD_TO_HLRindicates how many messages for unstructured supplementary service data being initi-ated by the mobile station are sent to the HLR.Trigger: each time ProcessUnstructuredSS is sent.

8.5 Combined paging and combined location update partCOM_LUP_REQindicates the number of location update requests (normal combined location updating).Trigger: each time UDT(LOCATION UPDATE REQUEST) is received from the BSSAP-LTG.

COM_LUP_IMSI_ATTACH_REQindicates the number of combined location update requests caused by IMSI attach.Trigger: each time COMBINED LOCATION UPDATE REQUEST containing type “IMSIattach” is received.

SUCC_COM_LUPindicates the number of successfully handled combined location update requests.Trigger: each time LOCATION UPDATE ACCEPT is received via the Gs interface.

SUCC_COM_LUP_IMSI_ATTACHindicates the number of successfully handled combined location update requests byIMSI attach.Trigger: each time LOCATION UPDATE ACCEPT containing “IMSI attach” is sent to theBSS via the Gs interface.

COM_LUP_LAI_NULLindicates the number of combined location updates with old LAI = 0 (e.g. upont registra-tion with MS recovery).Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS via the Gs inter-face.

REQ_COM_LUP_TO_HLRindicates the number of combined location update requests sent to the HLR.Trigger: each time LOCATION UPDATE ACCEPT is sent to the HLR via the Gs inter-face.

88 A50016-D1109-G801-6-7618


RES_COM_LUP_FROM_HLRindicates the number of successes from HLR for combined location updating.Trigger: each time TC-END result-L for UPDATE LOCATION is received from the HLRvia the Gs interface.

RES_COM_LUP_FROM_PVLRindicates the number of successes from a previous VLR for combined location updating.Trigger: each time TC-END result-L for UPDATE LOCATION is received from the PVLRvia the Gs interface.

BSSAP_PL_UNKNOWNindicates the number of unknown messages received with respect to BSSAP+.Trigger: each time an unknown UDT message is received from the BSSAP-LTG.

BSSAP_PL_DECODING_ERRindicates the number of decoding errors with respect to BSSAP+.Trigger: each time a UDT message with a decoding error is received from the BSSAP-LTG.

A50016-D1109-G801-6-7618 89


Traffic Measurement

9 Location-area Related Traffic MeasurementA number of appropriate counters are implemented for the measurement of traffic be-tween location areas. Since the sizing of location areas versus MSC/ VLR areas has astrong impact on the load caused by location update and paging procedures, data withinthis respect is collected.

After all, as location areas increase in size, the load due to location update is reducedwhereas the load due to paging is increased and the size of the MSC/VLR areas affectsthe frequency of inter-MSC handovers.

Therefore, counters for data relating to location areas are implemented in the CP data-base on which the measurement concerned relies.This traffic measurement can be started by entering command REC LOCAREA .

PAG_PROCindicates how many paging procedures started for MTER.Trigger:each time PAGING is sent.

RETRY_PAGindicates how many paging retry procedures started for MTER.Trigger: each time PAGING is sent after expiry of the paging timer.

SUCC_PAGindicates the number of successfully completed paging procedures.Trigger: each time PAGING RESPONSE is received.

LOC_UPDindicates the number of received requests for location updating.Trigger: each time COMPLETE LAYER 3 containing LOCATION UPDATE REQUESTis received.

NO_OF_MSindicates how many mobile subscribers registered in the location area.Trigger: increases upon creation of entry, decreases upon deletion of entry.

NO_OF_AMSindicates the number of attached mobile subscribers in the location area.Trigger: upon set/reset of detach state in the VLR.

REQ_COM_PAGindicates how often a paging procedure is started for a combined subscriber (registeredas both GSM and GPRS subscriber).Trigger: each time PAGING is sent (addressing via an SGSN number).

SEC_COM_PAGindicates how often a paging procedure is retried after rejected paging on the Gs inter-face.Trigger: each time PAGING is sent (addressing via an SGSN number) after the pagingtimer has been expired.

90 A50016-D1109-G801-6-7618


SUCC_COM_PAGindicates how often a paging procedure for a combined subscriber has been success-fully completed.Trigger:each time PAGING RESPONSE is received (addressing via an SGSN number).

A50016-D1109-G801-6-7618 91


Traffic Measurement

10 Traffic Measurement in the HLRThe HLR is a fixed subscriber database containing all the data on subscribers whosehome location is in the PLMN, requiring the following functions:– mobility management functions, such as location registration– call handling functions, such as interrogation– handling of subscriber controlled inputs.

Therefore, traffic data can be collected in the HLR by entering the command REC HLRThis traffic measurement relies on counters in the HLR that make up:– a structure and installation related part, such as

number of subscribers registered in the HLR database,number of subscribers provided with specific services

– load and demand related part andgrade of service related part for

mobility management/call handling/authentication– load and demand related part and

grade of service related part forsubscriber controlled input

– load and demand related part andgrade of service related part for

short message service– an overload related part

10.1 Structure and Installation Related Part (1) of (3)SUB_REGISTERED_IN_HLRindicates how many mobile subscribers are registered in the HLR.Trigger: each time a mobile subscriber is created successfully by CR MSUB.

WLL_SUB_REGISTERED_IN_HLRindicates how many wireless local loop (WLL) subscribers are registered in the HLR.Trigger: after a successful MML command:

increased by CR MSUB or MOD MSUB, ordecreased by CAN MSUB

LINKED_SUB_REGISTERED_IN_HLRindicates how many linked subscribers are registered in the HLR.Trigger: after a successful MML command:

increased by CR MSUBLINK, ordecreased by CAN MSUBLINK

RESTR_SUB_ALL_GSM_PLMNindicates the number of subscribers with the subscription restriction ”all GSM PLMNs”.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

RESTR_SUB_1_NAT_ALL_VPLMNindicates the number of subscribers with the subscription restriction ”one national andall international GSM PLMNs”.

92 A50016-D1109-G801-6-7618


Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

RESTR_SUB_HOME_PLMN_ONLYindicates the number of subscribers with the subscription restriction ”home PLMN only”.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

BLOCKED_SUB_REGISTERED_IN_HLRindicates the number of administrative blocked subscribers registered in the HLR.Trigger: increased/decreased each time a mobile subscriber is successfully blocked/un-blocked.

SUB_WITH_ODB_OUTGOINGindicates the number of subscribers with operator determined barring for outgoing calls.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

SUB_WITH_ODB_INCOMINGindicates the number of subscribers with operator determined barring for incoming calls.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

SUB_WITH_ODB_ROAMindicates the number of subscribers with operator determined barring for roaming.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

SUB_WITH_ODB_PREMIUM_RATEindicates the number of subscribers with operator determined barring for premium ratecalls.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

SUB_WITH_ODB_SPECIFIC_HPLMNindicates the number of subscribers with operator determined barring for home PLMN-specific barring.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

SUB_WITH_ODB_SS_MANAGEMENTindicates the number of subscribers with operator determined barring for SS manage-ment.Trigger: increased/decreased each time the appropriate subscription restriction for amobile subscriber is successfully changed by CR MSUB or MOD MSUB.

SUB_WITH_IMSI_TRACE_ACTIVEindicates the number of subscribers for whom IMSI tracing is active.

A50016-D1109-G801-6-7618 93


Traffic Measurement

Trigger: after a successful MML command.increased by ACT IMSITRACdecreased by DACT IMSITRAC

OWN_SUB_ROAM_IN_FOREIGN_PLMNindicates the number of subscribers for whom IMSI tracing is active.Trigger:

increased upon each location update from the VLR of foreign PLMN and a VLRnumber different from the VLR number in the HLR or recovery with data loss for this MSsince last location update;

decreased with each cancel location to VLR of foreign PLMN and no recovery forthis MS since the last location update.

10.2 Structure and Installation Related Part (2) of (3)SPEECH_TRANSMISSIONindicates the number of subscribers with the provision for speech services.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB.

SHORT_MSG_SERVICE_MTindicates the number of subscribers with the provision for short message services, mo-bile terminated.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB.

SHORT_MSG_SERVICE_MOindicates the number of subscribers with the provision for short message services, mo-bile originated.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB.

FACSIMILE_SERVICESindicates the number of subscribers with the provision for facsimile services.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB.

DATA_CDAindicates the number of subscribers being provisioned with the bearer service to transferanalog data at a given user rate in CDA and transparent mode.Trigger: increased/decreased each time the respective bearer service for a mobile sub-scriber is successfully changed by CR MSUB or MOD MSUB for:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S1200/75 B/S

94 A50016-D1109-G801-6-7618


DATA_CDSindicates the number of subscribers being provisioned with the bearer service to transferanalog data at a given user rate in CDS and transparent mode.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB for:

1200 B/S2400 B/S4800 B/S9600 B/S

ALTERN_SPEECH_DATAindicates the number of subscribers with the provision alternate speech/data services.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB.

SPEECH_FOLLOWED_BY_DATAindicates the number of subscribers with the provision speech followed by data services.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB.

PAD_CDAindicates the number of subscribers with the provision for PAD (packet assembler/dis-assembler) access at a given user rate via modem circuit duplex asynchronous.Trigger: increased/decreased each time the specified service for a mobile subscriber issuccessfully changed by CR MSUB or MOD MSUB for:

300 B/S1200 B/S2400 B/S4800 B/S9600 B/S

CALL_FORW_UNCONDITIONALindicates the number of mobile subscribers with the provision ”call forwarding uncondi-tional”.Trigger: after a successful MML command for the specified SS of a subscriber:

increased by ENTR CFSERV;decreased by CAN CFSERV

CALL_FORW_ON_MS_BUSYindicates the number of mobile subscribers with the provision ”call forwarding on mobilesubscriber busy”.Trigger: after a successful MML command for the specified SS of a subscriber.

increased by ENTR CFSERVdecreased by CAN CFSERV

CALL_FORW_ON_NO_REPLYindicates the number of mobile subscribers with the provision ”call forwarding on no re-ply”.Trigger: after a successful MML command for the specified SS of a subscriber.

A50016-D1109-G801-6-7618 95


Traffic Measurement


CALL_FORW_ON_MS_NOT_REACHindicates the number of mobile subscribers with the provision ”call forwarding on MS notreachable”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_BARR_OUTG_CALLSindicates the number of mobile subscribers with the provision ”barring of all outgoingcalls”.Trigger: after a successful MML command for the specified SS of a subscriber.

increased by ENTR CBSERVdecreased by CAN CBSERV

CALL_BARR_OUTG_INT_CALLSindicates the number of mobile subscribers with the provision ”barring of all outgoing in-ternational calls”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_BARR_OUTG_INT_CALL_HPLMNindicates the number of mobile subscribers with the provision ”barring of all outgoing in-ternational calls except those directed to the home PLMN country”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_BARR_INC_CALLSindicates the number of mobile subscribers with the provision ”barring of all incomingcalls”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_BARR_INC_ROAM_OUT_HPLMNindicates the number of mobile subscribers with the provision ”barring of all incomingcalls when roaming outside the HPLMN”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_LINE_IDENT_PRESENTindicates the number of mobile subscribers with the provision “calling line identificationpresentation” (CLIP).Trigger: after a successful MML command for the specified SS of a subscriber.

96 A50016-D1109-G801-6-7618


increased by ENTR GCSERVdecreased by CAN GCSERV

CALL_LINE_IDENT_RESTRindicates the number of mobile subscribers with the provision “calling line identificationrestriction” (CLIR).Trigger: after a successful MML command for the specified SS of a subscriber.


CONN_LINE_IDENT_PRESENTindicates the number of mobile subscribers with the provision “connected line identifica-tion presentation” (COLP).Trigger: after a successful MML command for the specified SS of a subscriber.


CONN_LINE_IDENT_RESTRindicates the number of mobile subscribers with the provision “connected line identifica-tion restriction” (COLR).Trigger: after a successful MML command for the specified SS of a subscriber.


AOC_CHARGING_LEVELindicates the number of mobile subscribers with the provision “advice of charge, charg-ing level”.Trigger: after a successful MML command for the specified SS of a subscriber.


AOC_INFORM_LEVELindicates the number of mobile subscribers with the provision “advice of charge, infor-mation level”.Trigger: after a successful MML command for the specified SS of a subscriber.


MULTI_PARTY_SERVICEindicates the number of mobile subscribers with the provision “multi party service”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_BACKindicates the number of mobile subscribers with the provision “call back”.Trigger: after a successful MML command for the specified SS of a subscriber.

increased by ENTR CALLBACKdecreased by CAN CALLBACK

A50016-D1109-G801-6-7618 97


Traffic Measurement

CLOSED_USER_GROUPindicates the number of mobile subscribers with the provision “closed user group”.Trigger: after a successful MML command for the specified SS of a subscriber.

increased by ENTR CUGSERVdecreased by CAN CUGSERV

HOT_BILLINGindicates the number of mobile subscribers with the provision “hot billing”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_HOLDindicates the number of mobile subscribers with the provision “call hold”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_WAITINGindicates the number of mobile subscribers with the provision “call waiting”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALL_TRANSFERindicates the number of mobile subscribers with the provision of “call transfer”.Trigger: after a successful MML command for the specified SS of a subscriber.


CALLS_COMPL_BUSY_SUBindicates the number of mobile subscribers with the provision “call completion to busysubscriber”.Trigger: after a successful MML command for the specified SS of a subscriber.


IN_SERVICE_CLASS_MARK_MTCindicates the number of mobile subscribers with the provision “class mark MTC for INservices”.Trigger: after a successful MML command for the specified service.

increased by ENTR OPRSERVdecreased by CAN OPRSERV

IN_SERVICE_CLASS_MARK_MOCindicates the number of mobile subscribers with the provision “class mark MOC for INservices”.Trigger: after a successful MML command for the specified service.

increased by ENTR OPRSERV

98 A50016-D1109-G801-6-7618


decreased by CAN OPRSERV

USER_SIG1indicates the number of mobile subscribers with the provision “user-to-user signalingservice 1”.Trigger: after a successful MML command for the specified service.


FOLLOW_MEindicates the number of mobile subscribers with the provision “follow me”.Trigger: after a successful MML command for the specified service.

increased by ENTR OPRSERVdecreased by CAN OPRSERV

CALL_FORW_DEFin addition to the other call forwarding services, this service too has its own counter thatindicates the number of mobile subscribers with the provision “cal forwarding by default”Trigger: after a successful MML command for the specified SS of a subscriber.


DATA_CDA_GBSindicates the number of mobile subscribers being provisioned with the general bearerservice to transfer analog data at an appropriate user rate in CDA.Trigger: increased/decreased each time the respective bearer service for a mobile sub-scriber is successfully created or modified by CR MSUB or MOD MSUB.

DATA_CDS_GBSindicates the number of mobile subscribers being provisioned with the general bearerservice to transfer analog data at an appropriate user rate in CDS.Trigger: increased/decreased each time the respective bearer service for a mobile sub-scriber is successfully created or modified by CR MSUB or MOD MSUB.

PAD_CDA_GBSindicates the number of subscribers with the provision for PAD (packet assembler/dis-assembler) access at a user rate from the general bearer service via modem circuit du-plex asynchronous.Trigger: increased/decreased each time the respective bearer service for a mobile sub-scriber is successfully created or modified by CR MSUB or MOD MSUB.

MSUB _REGISTERED_GPRSindicates how many mobile GPRS subscribers (General Packet Radio Service) are reg-istered in the HLR.Trigger: increased/decreased each time the respective service for a mobile subscriberis successfully created or modified by CR MSUB or MOD MSUB.

A50016-D1109-G801-6-7618 99


Traffic Measurement

MSUB _ROAM_FOREIGN_GPRS_PLMNindicates the number of mobile subscribers currently roaming in a foreign GPRS PLMNTrigger:

increased upon each location update from the SGSN of foreign GPRS PLMN thenumber of which differs from the SGSN number in the HLR,or recovery with data loss for this MS since last location update;

decreased with each cancel location to SGSN of foreign GPRS PLMN and no recov-ery for this MS has taken place since the last location update.

CAMEL_USSDindicates how many mobile subscribers with the provision unstructured supplementaryservice data for CAMEL are registered in the HLR.Trigger: increased/decreased each time a mobile subscriber is successfully administrat-ed for the respective service (via CR / MOD / CAN MSUB).

NUM_MSUB _SS_CSIindicates how many mobile subscribers with the provision CAMEL subscription informa-tion are registered in the HLR.Trigger: increased/decreased each time a mobile subscriber is successfully administrat-ed for the CAMEL service (via ENTR / CAN OPRSERV).

NUM_MSUB _GPRS_CSIindicates how many mobile GPRS subscribers with the provision CAMEL subscriptioninformation are registered in the HLR.Trigger: increased/decreased each time a GPRS subscriber is successfully administrat-ed for the CAMEL service (via ENTR / CAN OPRSERV).

NATIONAL_FEATURE_1indicates the number of mobile subscribers with the provision of national feature 1. Upto 15 of these counters are provided.Trigger: after a successful MML command for the specified feature.

increased by ENTR MBSUFTdecreased by CAN MBSUFT

10.3 Structure and Installation Related Part (3) of (3)ASCI_VBSindicates how many mobile subscribers with the provision voice broadcast service(VBS) for ASCI radio network are registered in the HLR.Trigger: each time a mobile subscriber is created or modified successfully by CR MSUBor MOD MSUB.

ASCI_VGCSindicates how many mobile subscribers with the provision voice group call service(VGCS) for ASCI radio network are registered in the HLR.Trigger: each time a mobile subscriber is created or modified successfully by CR MSUBor MOD MSUB.

100 A50016-D1109-G801-6-7618


ASCI_EMLPPindicates how many mobile subscribers with the provision enhanced multilevel prece-dence and preemption service (eMLPP) for ASCI radio network are registered in theHLR.Trigger: each time a mobile subscriber is created or modified successfully by ENTR GC-SERV or can GCSERV.

NO_OF_LMUindicates how many location measurements units are registered in the HLR.Trigger: increased/decreased each time an LMU mobile subscriber is successfully ad-ministrated (via CR / MOD / CAN MSUB).

10.4 Mobility Management/Call Handling/Authentication

10.4.1 Load and demand related partRECVD_UPD_LOC_MSG_VLR_HPLMNindicates how often a request for location updating is received from a VLR of the homePLMN (HPLMN).Trigger: each time UPDATE LOCATION with valid VLR number is received from theHPLMN.

RECVD_UPD_LOC_MSG_VLR_VPLMNindicates how often a request for location updating is received from a VLR of anotherPLMN (visited PLMN).Trigger: each time UPDATE LOCATION with valid VLR number is received from anotherPLMN.

SND_CAN_LOC_MSG_LOC_UPDindicates how often a request for location canceling is sent to the PVLR due to an up-dating procedure.Trigger: each time CANCEL LOCATION is sent.

SND_CAN_LOC_MSG_SUB_ADMINindicates how often a request for location canceling is sent to the VLR due to subscriberadministration.Trigger: each time CAN MSUB (subscriber is deleted in HLR or VLR database) is sent.

SND_INS_SUBDT_MSGindicates how often a message containing subscriber data is sent to the VLR due to lo-cation updating.Trigger: each time INSERT SUBSCRIBER DATA is sent to the VLR.

SND_INS_SUBDT_MSG_SUB_ADMINindicates how often a message containing subscriber data is sent to the VLR due to sub-scriber administration.Trigger: each time MML commands, causing an update of the HLR database, such asMOD MSUB, ENTR CFSERV, ENTR CBSERV, CAN CFSERV are sent.

A50016-D1109-G801-6-7618 101


Traffic Measurement

SND_DEL_SUBDT_MSG_SUB_ADMINindicates how often a message for deleting subscriber data is sent to the VLR due tosubscriber administration.Trigger: each time MML commands, causing an update of the HLR database, such asMOD MSUB, ENTR CFSERV, ENTR CBSERV, CAN CFSERV are sent.

RECVD_SEND_ROUT_INFO_MSG_GMSCindicates how often a request for routing information is received from a gateway MSC.Trigger: each time SEND ROUTING INFO is received. The directory number is a servicenumber (e.g. for mailbox service).

RECVD_SEND_ROUT_INFO_MSG_SCODEindicates how often a request for routing information containing service codes is re-ceived.Trigger: each time SEND ROUTING INFO containing service codes is received.

RECVD_SEND_PARAM_PRindicates how often messages for parameter request (e.g. IMSI) are received.Trigger: each time the proper message is received.

- Ph1: SEND PARAMETERS including authenication triples- Ph2: RESTORE DATA

RECVD_SEND_PARAM_ARindicates how often messages requesting authentication data is received.The implemented counter measures the number of triplets the HLR requests from theAC.Trigger: each time the proper message is received.


RECVD_SEND_PARAM_AR_PRindicates how often messages requesting parameter and authentication data are re-ceived.Trigger: each time SEND PARAMETERS is received, including authentication triplesand subscriber data (Ph1).

SENT_RESET_HLRindicates how often a reset message is sent to the HLR.Trigger: each time RESET is sent to the HLR.

RECVD_RESET_VLRindicates how often a reset message is received from a VLR.Trigger: each time RESET is received from the HLR.

RECVD_RESTORE_DATAindicates how often the relevant message is received from a VLR.Trigger: each time RESTORE DATA is received from the VLR.

102 A50016-D1109-G801-6-7618


REUSED_TRIPLESindicates the number of reused triples.Trigger: each time the HLR requests triples from the AC, but they are not delivered. TheHLR then reuses triples (internal event in the HLR).

SWITCHES_TO_LINKED_MSindicates the number of switches to linked MS.

SND_ACT_TRACEMODEindicates how often tracing is activated after a location update.Trigger: each time ACTIVATE TRACEMODE is sent after a location update.

ADMIN_ACT_TRACEMODEindicates how often tracing is activated due to subscriber administration.Trigger: each time ACTIVATE TRACEMODE is sent upon the MML command ACT IM-SITRAC.

ADMIN_DEACT_TRACEMODEindicates how often tracing is deactivated due to subscriber administration.Trigger: each time DEACTIVATE TRACEMODE is sent upon the MML command DACTIMSITRAC.

RECVD_ACT_FOLLOW_MEindicates how often follow me is activated.Trigger: each time ACTIVATE FOLLOW ME is received from the MS.

RECVD_DEACT_FOLLOW_MEindicates how often follow me is deactivated.Trigger: each time DEACTIVATE FOLLOW ME is received from the MS.

UNRELDIRWhen an HLR in a CDMA(IS-95) PLMN has lost all transient data, it informs all VLRsconcerned. The latter’s addresses are retrieved from the restoration list by which a mes-sage to indicate the failure can be sent.Trigger: each time UNRELIABLE ROAMING DATA DIRECTIVE is sent to national andinternational VLRs.

SENT_PSIThe inter-PLMN mobility of GSM mobile subscribers using CAMEL services can be ex-amined. As to mobile terminating calls, the HLR can provide information on the subscrib-er’s location or status when interrogated by the gateway MSC initiated by a GSM servicecontrol function. The interrogation requests are counted in the HLR.Indicates the number of MAP messages PROVIDE SUBSCRIBER INFO (contains ei-ther the last radio cell being affected by the subscriber or his status) that the HLR hassent to the VLR.Trigger: each time the HLR receives

SEND ROUTING INFO from the gateway GMSC, orANY TIME INTERROGATION from the GSM service control function.

A50016-D1109-G801-6-7618 103


Traffic Measurement

RECVD_ATIAnother way to retrieve information on the subscriber’s location or status is possiblewithout having the subscriber involved in a call. In this case the HLR is directly interro-gated by the GSM service control function.Indicates how often the HLR has received an interrogation message directly from theCAMEL server (its address is included in ATI invoke). This message drives the HLR fora dialog with the VLR.Trigger: each time ANY TIME INTERROGATION is received from the GSM service con-trol function.

SENT_NI_USSD_TO_VLRIndicates how often the GSM service control function has sent a USSD message initiat-ed by the network to the VLR.Trigger: each time USS REQUEST or USS NOTIFY is sent to the MSC/VLR for the firsttime.

RECVD_CCBS_REQ_IN_HLR_Aindicates how often the HLR of the calling side (A) receives a request from MSC-A forthe completion of a call to a busy subscriber.Trigger: each time a mobile subscriber invokes CCBS REQUEST after his call attemptmeets a busy subscriber.

RECVD_CCBS_REQ_IN_HLR_Bindicates how often the HLR of the called side (B) receives a request for the completionof a call to its busy subscriber.Trigger: each time the HLR-A sends CCBS REQUEST after being invoked by a mobilesubscriber calling a busy subscriber.

10.4.2 Grade of service related part for mobility managementUNS_UPLOCMSG_VLR_HPLMN_SUB_BEHindicates how often a location update from a VLR of the HPLMN was unsuccessfullyhandled by the HLR, due to subscriber behavior (MAP error: roaming not allowed).Trigger: each time TC-END U-ERROR including the proper MAP error is sent to the VLRdue to e.g. location update with old SIM card, ODB of roaming, roaming not allowed,AOC not supported in the VLR.

UNS_UPLOCMSG_VLR_HPLMN_IRR_VLRindicates how often a location update from a VLR of the HPLMN was unsuccessfullyhandled by the HLR, due to irregular VLR behavior (MAP errors: data missing, unknownsubscriber, unexpected data value).Trigger: each time TC-END U-ERROR including the proper MAP error is sent to theVLR.

UNS_UPLOCMSG_VLR_HPLMN_IRR_SYSindicates how often a location update from a VLR of the HPLMN was unsuccessfullyhandled by the HLR, due to irregular system behavior (any other cause for a negativeresponse to VLR).Trigger: each time TC-ABORT, TC-END REJECT, TC-END U-ERROR (due to internal

104 A50016-D1109-G801-6-7618


failure in HLR) is sent to the VLR upon receipt of UPDATE LOCATION.

UNS_UPLOCMSG_VLR_VPLMN_SUB_BEHindicates how often a location update from a VLR of the visited PLMN was unsuccess-fully handled by the HLR, due to subscriber behavior (MAP error: roaming not allowed).Trigger: each time TC-END U-ERROR including the proper MAP error is sent to the VLRdue to e.g. location update with old SIM card, ODB of roaming, roaming not allowed,AOC not supported in the VLR.

UNS_UPLOCMSG_VLR_VPLMN_IRR_VLRindicates how often a location update from a VLR of the visited PLMN was unsuccess-fully handled by the HLR, due to irregular VLR behavior (MAP errors: data missing, un-known subscriber, unexpected data value).Trigger: each time TC-END U-ERROR including the proper MAP error is sent to theVLR.

UNS_UPLOCMSG_VLR_VPLMN_IRR_SYSindicates how often a location update from a VLR of the visited PLMN was unsuccess-fully handled by the HLR, due to irregular system behavior (any other cause for a neg-ative response to the VLR).Trigger: each time TC-ABORT, TC-END REJECT, TC-END U-ERROR (due to internalfailure in HLR) is sent to the VLR upon receipt of UPDATE LOCATION.

UNS_CANLOCMSG_UNIDENT_SUBindicates how often a location could not be canceled in the VLR due to unidentified sub-scriber indicated by a MAP error.Trigger: each time TC-END U-ERROR is received upon sending CANCEL LOCATIONto the VLR.

UNS_CANLOCMSG_ANY_OTHERindicates how often a location could not be canceled in the VLR due to a negative out-come or HLR timer expiry.Trigger: each time TC-END U-ERROR/REJECT/CANCEL is received upon sendingCANCEL LOCATION to the VLR.

UNS_INS_SUBDT_MSGindicates how often the VLR could not deliver subscriber data for a location update dueto negative outcome or HLR timer expiry.Trigger: each time TC-END U-ERROR/REJECT/CANCEL is received upon sending IN-SERT SUBSCRIBER DATA to the VLR.

UNS_ACT_TRACEMODEindicates how often tracing was activated unsuccessfully messages after a location up-date.Trigger: each time a TC-ERROR is sent on ACTIVATE TRACEMODE.

UNS_ACT_FOLLOW_ME_MS_BEHindicates how often follow me was activated unsuccessfully due to subscriber behavior.

A50016-D1109-G801-6-7618 105


Traffic Measurement

Trigger: each time TC-END U-ERROR is sent on ACTIVATE FOLLOW ME.

UNS_ACT_FOLLOW_ME_SYS_BEHindicates how often follow me was activated unsuccessfully due to system behavior.Trigger: each time TC-END U-ERROR is sent upon ACTIVATE FOLLOW ME.

UNS_DEACT_FOLLOW_ME_MS_BEHindicates how often follow me was activated unsuccessfully due to subscriber behavior.Trigger: each time TC-END U-ERROR is sent upon DEACTIVATE FOLLOW ME.

UNS_DEACT_FOLLOW_ME_SYS_BEHindicates how often follow me was activated unsuccessfully due to system behavior.Trigger: each time TC-END U-ERROR is sent upon DEACTIVATE FOLLOW ME.

UNS_RECVD_PSIindicates the number of negative responses that the VLR returns to the PROVIDE SUB-SCRIBER INFO requests (CAMEL service) from the HLR sent beforehand.Trigger: each time the VLR sends a message to indicate an abort, a time-out, a rejectionor a user error in response to PROVIDE SUBSCRIBER INFO

10.4.3 Grade of service related part for call handlingSND_PROV_MSRNindicates how often the relevant message is sent to the VLRTrigger: each time SEND PROVIDE ROAMING NUMBER is sent to the VLR.

RECVD_MSRNindicates how often MSRN is received from the VLRs.Trigger: each time a roaming number is returned from a VLR as a successful responseto PROVIDE ROAMING NUMBER.

SENT_MSRN_TO_GMSCindicates how often MSRN is returned to GMSC.Trigger: each time SEND ROUTING INFO RESULT containing MSRN or subscriber ser-vice address is sent to GMSC.

SENT_FORW_TO_NO_TO_GMSCindicates how often many forwarded-to-numbers are sent to GMSC.Trigger: each time SEND ROUTING INFO RESULT containing forwarding data is sentto GMSC.

UNS_SNDROUTINFMSG_BLCKD_BARRindicates how often requests for routing information to the HLR are unsuccessfully han-dled due to barring or operator determined barring.Trigger: each time TC-END U-ERROR is received due to call barred.

UNS_SNDROUTINFMSG_CF_VIOLindicates how often requests for routing information to the HLR are unsuccessfully han-

106 A50016-D1109-G801-6-7618


dled due to call forwarding violations.Trigger: each time TC-END U-ERROR including proper MAP error is sent to the GMSCin response to SEND ROUTING INFO due to number of forwardings exceeded.

UNS_SNDROUTINFMSG_SUB_ERRORindicates how often requests for routing information to the HLR are unsuccessfully han-dled there due to subscription check errors (MAP errors: teleservice not provisioned,bearer service not provisioned).Trigger: each time TC-END U-ERROR including proper MAP error is sent to GMSC inresponse to SEND ROUTING INFO.

UNS_SNDROUTINFMSG_GMSC_BEHindicates how often requests for routing information to the HLR are unsuccessfully han-dled there due to irregular system behavior (MAP errors: unexpected data value, datamissing).Trigger: each time TC-END TC-U-ERROR including proper MAP error is sent to GMSCin response to SEND ROUTING INFO.

UNS_SNDROUTINFMSG_MS_BEHindicates how often requests for routing information to the HLR are unsuccessfully han-dled there due to subscriber behavior (MAP errors: unknown subscriber, absent sub-scriber, call barred, CUG reject). “Forwarding violation” is not included here because itaffects a separate counter.Trigger: each time TC-END TC-U-ERROR including proper MAP error is sent to GMSCin response to SEND ROUTING INFO.

UNS_SNDROUTINFMSG_SEC_CAUSESindicates how often requests for routing information to the HLR are unsuccessfully han-dled there due to other causes (MAP errors such as facility not supported, system fail-ure).Trigger: each time TC-END U-ERROR including proper MAP error is received from VLRin response to PROVIDE ROAMING NUMBER.

UNS_SNDROUTINFMSG_LOST_LOCindicates how often requests for routing information to the HLR are unsuccessfully han-dled there due to lost location information.Trigger: each time SEND ROUTING INFORMATION is received and no VLR addressis stored in the HLR.

UNS_RESTORE_DATAindicates the number of unsuccessfully handled RESTORE DATA messages.Trigger: each time TC-ABORT, TC-END U-ERROR, TC-REJ is sent to the VLR uponreceipt of RESTORE DATA.

UNS_CALL_SS_BICindicates the number of successful invocations of barring of all incoming calls.Trigger: each time that, during MTC or SMS-MT establishment, data base access rec-ognizes that barring of all incoming calls is active for this subscriber.

A50016-D1109-G801-6-7618 107


Traffic Measurement

UNS_CALL_SS_BICROAMindicates the number of successful invocations of barring of all incoming calls whenroaming outside the HPLMN country.Trigger: each time that, during MTC or SMS-MT establishment, data base access rec-ognizes that barring of all incoming calls when roaming outside the HPLMN is active forthis subscriber.

UNS_CCBS_REQ_SUB_BEHindicates the number of unsuccessful CCBS requests due to subscriber behavior (e.g.no CCBS recall, timer expiry at calling side or at called side).Trigger: each time the HLR receives a message indicating a CCBS cancel (time-out ofthe CCBS service timer or call supervision timer).

UNS_CCBS_REQ_OTHERindicates the number of unsuccessful CCBS requests due to system behavior (e.g. MAPerrors, system failure).Trigger: each time the HLR receives an error message after CCBS REQUEST, or whensuspend handling is concerned.

10.4.4 Grade of service related part for subscriber dataUNS_INS_SUBDT_MSG_SUB_ADMINindicates how often the VLR has unsuccessfully handled a message with subscriberdata being initiated via subscriber administration.Trigger: each time TC-END U-ERROR (negative VLR response) is received from theVLR or TC-CANCEL (HLR timer expires) upon sending INSERT SUBSCRIBER DATAvia an MML command.

UNS_DEL_SUBDT_MSG_SUB_ADMINindicates how often the VLR has unsuccessfully handled a request to delete subscriberdata being initiated via subscriber administration.Trigger: each time TC-END U-ERROR (negative VLR response) is received from theVLR or TC-CANCEL (HLR timer expires) upon sending DELETE SUBSCRIBER DATAvia an MML command.

UNS_SUB_ADMIN_CANLOC_UNIDENT_MSindicates how often the VLR has unsuccessfully handled a request to cancel location be-ing initiated via subscriber administration.Trigger: each time TC-END U-ERROR due to unidentified subscriber is received fromthe VLR upon sending CANCEL LOCATION via CAN SUB.

UNS_SUB_ADMIN_CANLOC_ANY_OTHERindicates how often the VLR has unsuccessfully handled a request to deactivate tracingbeing initiated via subscriber administration.Trigger: each time TC-END U-ERROR (negative VLR response) is received from theVLR or TC-CANCEL (HLR timer expires) upon sending CANCEL LOCATION via anMML command.

108 A50016-D1109-G801-6-7618


UNS_ACT_TRACEMODE_SUB_ADMINindicates how often the VLR has unsuccessfully handled a request to activate tracingbeing initiated via subscriber administration. The operator must first activate IMSI trac-ing.Trigger: each time TC-END U-ERROR (negative VLR response) is received from theVLR or TC-CANCEL (HLR timer expires) upon sending ACTIVATE TRACEMODE viaan MML command.

UNS_DEACT_TRACEMODE_SUB_ADMINindicates how often the VLR has unsuccessfully handled a request to deactivate tracingbeing initiated via subscriber administration.Trigger: each time TC-END U-ERROR (negative VLR response) is received from theVLR or TC-CANCEL (HLR timer expires) upon sending DEACTIVATE TRACEMODEvia an MML command.

UNS_SND_PARAM_PRindicates how often requests for parameters are unsuccessfully handled.Trigger: each time SEND PARAMETERS requesting authentication triples to the VLR isreplied to with TC END, TC ABORT, TC REJECT or no response (Ph1).

UNS_SND_PARAM_ARindicates how often requests for authentication data are unsuccessfully handled.Trigger: each time TC-END U-ERROR/TC-REJ/TC-CANCEL is sent upon receipt of:


UNS_SND_PARAM_AR_PRindicates how often requests for authentication data and subscriber data are handledunsuccessfully.Trigger: each time TC-ABORT TC-END TC-ERROR/TC-REJ is sent to the VLR uponreceipt of SEND PARAMETERS.

10.5 Subscriber Controlled Input

10.5.1 Load and demand related partRECVD_MSG_REGISTER_SSindicates how often an SS is registered by SCI.Trigger: each time REGISTER SS is received from the VLR.

RECVD_MSG_REGISTER_PWindicates how often an SS for password is registered by SCI.Trigger: each time REGISTER PW is received from the VLR.

RECVD_MSG_ERASE_SSindicates how often an SS is erased by SCI.Trigger: each time ERASE SS is received from the VLR.

A50016-D1109-G801-6-7618 109


Traffic Measurement

RECVD_MSG_ACT_SSindicates how often an SS call wait is activated by SCITrigger: each time ACTIVATE SS is received.

RECVD_MSG_DEACT_SSindicates how often an SS for call wait is deactivated by SCI.Trigger: each time DEACTIVATE SS is received from the VLR.

RECVD_MSG_INTERROG_SSindicates how often each SS is interrogated by SCI.Trigger: each time INTERROGATE SS is received from the HLR.

SENT_INSERT_MS_DATA_AFTER_SCIindicates how often subscriber data is sent to the VLR after an SCI command.Trigger: each time INSERT SUBSCRIBER DATA is sent to the VLR.

SENT_CAN_LOC_MSG_ AFTER_SCIindicates how often a request to cancel location is sent to the VLR after an SCI com-mand.Trigger: each time CANCEL LOCATION is sent to the VLR upon reception of OPERATESS.

SENT_FORW_CHECK_SS_INDICindicates how often a proper message is sent to the VLR after an SCI command.Trigger: each time FORWARD CHECK SS INDICATION is sent to the VLR.

RECVD_MSG_UNSTRUCTURED_SS_DATAindicates how often an unstructured SS is requested.Trigger: each time PROCESS UNSTRUCTURED SS REQUEST is received.

RECVD_MSG_REGISTER_CALLBACKindicates how often call back is registered.Trigger: each time REGISTER SS (type “call back”) is received.

RECVD_MSG_ERASE_CALLBACKindicates how often call back is erased.Trigger: each time ERASE SS (type “call back”) is erased.

RECVD_MSG_ACT_CALLBACKindicates how often call back is activated.Trigger: each time ACTIVATE SS (type “call back”) is received.

RECVD_MSG_DEACT_CALLBACKindicates how often call back is deactivated.Trigger: each time DEACTIVATE SS (“call back”) is received.

110 A50016-D1109-G801-6-7618


RECVD_MSG_INTERROG_CALLBACKindicates how often call back is interrogated.Trigger: each time INTERROGATE SS (type “call back”) is received.

RECVD_CAMEL_USSD_TO_GSMSCFindicates how many unstructured SS data for CAMEL is requested.Trigger: each time that PROCESS UNSTRUCTURED SS DATA REQUEST with a ser-vice code for the CAMEL USSD application from the MSC/VLR is received by the HLRin the HPLMN.

10.5.2 Grade of service related partSubscriber controlled inputs (SCI) can be handled successfully thanks to:

subscriber behavior;SCI may be affected by statements or restrictions, such as illegal SS operation, SS errorstatus, SS not available, SS specific error, BS or TS not provisioned, SS subscriptionviolation, SS incompatibility, bad password or invalid format.

irregular system behavior.The system may then not be able to reply to an SCI because unknown subscriber, un-expected data value, data missing, system failure, or any other unsuccessful outcomeis sent to the VLR.

UNS_RESP_REGISTER_SS_SUB_BEHindicates how many SCIs for REGISTER SS are unsuccessfully handled due to sub-scriber behavior.Trigger: each time TC-U-ERROR containing the proper cause is sent to the VLR.

UNS_RESP_REGISTER_SS_SYS_BEHindicates how many SCIs for REGISTER SS are unsuccessfully handled due to irregularsystem behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_REGISTER_PW_SUB_BEHindicates how many SCIs for REGISTER PW are unsuccessfully handled due to sub-scriber behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_REGISTER_PW_SYS_BEHindicates how many SCIs for REGISTER PW are unsuccessfully handled due to irregu-lar system behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_ERASE_SS_SUB_BEHindicates how many SCIs for ERASE SS are unsuccessfully handled due to subscriberbehavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_ERASE_SS_SYS_BEHindicates how many SCIs for ERASE SS are unsuccessfully handled due to irregular

A50016-D1109-G801-6-7618 111


Traffic Measurement

system behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_ACT_SS_SUB_BEHindicates how many SCIs for ACTIVATE SS are unsuccessfully handled due to sub-scriber behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_ACT_SS_SYS_BEHindicates how many SCIs for ACTIVATE SS are unsuccessfully handled due to irregularsystem behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_DEACT_SS_SUB_BEHindicates how many SCIs for DEACTIVATE SS are unsuccessfully handled due to sub-scriber behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_DEACT_SS_SYS_BEHindicates how many SCIs for DEACTIVATE SS are unsuccessfully handled due to irreg-ular system behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_INTERROG_SS_SUB_BEHindicates how many SCIs for INTERROGATE SS are unsuccessfully handled due tosubscriber behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_INTERROG_SS_SYS_BEHindicates how many SCIs for INTERROGATE SS are unsuccessfully handled due to ir-regular system behavior.Trigger: each time TC-END ERROR containing the proper cause is sent to the VLR.

UNS_RESP_INS_SUBDT_SSindicates how often subscriber data sent to the VLR after an SCI is unsuccessfully han-dled.Trigger: each time a negative result is received from the VLR or the HLR timer expiresdue to no reply upon sending INSERT SUBSCRIBER DATA.

UNS_CANLOC_UNIDENT_SUB_SSindicates how often a request to cancel a location is unsuccessfully handled becausethe subscriber is not known in the VLR.Trigger: each time CANCEL LOCATION is sent to the VLR and TC-Error due to “uniden-tified subscriber” is received.

UNS_CANLOC_ANY_OTHER_SSindicates how often a request to cancel a location is unsuccessfully handled due to anyother reason.

112 A50016-D1109-G801-6-7618


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

UNS_RESP_UNSTRUCTURED_SS_DATAindicates how many requests for an unstructured SS are handled unsuccessfully.Trigger: each time a negative result (TC-ERROR, TC-ABORT, TC-REJECT) is sent tothe VLR or HLR timer has expired due to no reply from VLR.

UNS_RESP_REGISTER_CALLBACKindicates how many SCI’s for REGISTER CALLBACK are handled unsuccessfully.Trigger: each time a negative result (TC-ERROR, TC-ABORT, TC-REJECT) is sent tothe VLR upon receiving REGISTER SS (call back).

UNS_RESP_ERASE_CALLBACKindicates how many SCI’s for ERASE CALLBACK are handled unsuccessfully.Trigger: each time a negative result (TC-ERROR, TC-ABORT, TC-REJECT) is sent tothe VLR upon receiving REGISTER SS (call back).

UNS_RESP_ACT_CALLBACKindicates how many SCI’s for ACTIVATE CALLBACK are handled unsuccessfully.Trigger: each time a negative result (TC-ERROR, TC-ABORT, TC-REJECT) is sent tothe VLR upon receiving REGISTER SS (call back).

UNS_RESP_DEACT_CALLBACKindicates how many SCI’s for DEACTIVATE CALLBACK are handled unsuccessfully.Trigger: each time a negative result (TC-ERROR, TC-ABORT, TC-REJECT) is sent tothe VLR upon receiving REGISTER SS (call back).

UNS_RESP_INTERROG_CALLBACKindicates how many SCI’s for INTERROGATE CALLBACK are handled unsuccessfullyTrigger: each time a negative result (TC-ERROR, TC-ABORT, TC-REJECT) is sent tothe VLR upon receiving REGISTER SS (call back).

UNS_CAMEL_USSD_BY_HLRindicates how many unstructured SS data for CAMEL is received by the HLR but reject-ed afterwards.Trigger: each time that PROCESS UNSTRUCTURED SS DATA REQUEST messagewith a service code for the CAMEL USSD application is received but rejected afterwardsby the HLR before sending to the GSM service control function, i.e. the CAMEL USSDmessage could not be sent by MAP.

RECVD_CAMEL_USSD_BY_GSMSCFindicates how many unstructured SS data for CAMEL is received by the GSM servicecontrol function but rejected afterwards.Trigger: each time that PROCESS UNSTRUCTURED SS DATA REQUEST messagewith a service code for the CAMEL USSD application is sent by the CAMEL USSD ap-plication in the HLR to the GSMSCF, but rejected afterwards. SystemFailure, unexpect-edDataValue or timer expiry in HLR (no response from GSMSCF).

A50016-D1109-G801-6-7618 113


Traffic Measurement

10.6 Short Message Service

10.6.1 Load and demand related partRECVD_SND_ROUTING_INFO_SMindicates how often routing info is requested for a short message.Trigger: each time SEND ROUTING INFORMATION FOR SM is received.

RECVD_SET_MWDindicates how many messages delivering short message data are received from thegateway MSC.Trigger: each time the HLR receives the respective message.

- Ph1: SET MWD- Ph2: REPORT SM DELIVERY STATUS indicating absent subscriber or

MS memory capacity exceeded

RECVD_NOTE_MS_PRESENTindicates how often is indicated that an MS was ready for SMS.Trigger: each time the HLR receives the respective message.

- Ph1: NOTE SM PRESENT- Ph2: READY FOR SM with alert reason = MS present

SND_ALERT_SERVICE_CENTERindicates how often the service center for SMS is alerted.Trigger: each time the HLR receives the respective message.

- Ph1: NOTE SM PRESENT- Ph2: READY FOR SM

SUCC_ALERT_SERVICE_CENTERindicates the number of successful alert messages to the service center.Trigger: each time the HLR receives a successful ALERT SERVICE CENTER ACK (Ph2).

10.6.2 Grade of service related partUNS_ADMBLCKD_OR_CALLBARRindicates how often a routing info request for an SM is handled unsuccessfully due toadministrative blocking or call barring.Trigger: each time TC-U-ERROR due to call barred is sent to GMSC in response to thisrequest.

UNS_SUBSCRIPTION_ERRORindicates how often a routing info request for an SM is handled unsuccessfully due tosubscription errors.Trigger: each time TC-U-ERROR due to subscription error is sent to GMSC in responseto this request.

UNS_GMSC_BEHAVIORindicates how often a routing info request for an SM is handled unsuccessfully due to

114 A50016-D1109-G801-6-7618


GMSC behavior.Trigger: each time TC-U-ERROR is sent to GMSC in response to this request.

UNS_SUB_ BEHAVIORindicates how many messages referred to below are unsuccessfully handled by the HLRdue to subscriber behavior.Trigger: each time the HLR sends TC-U-ERROR to the gateway MSC in reply to SENDROUTING INFO FOR SMS.

UNS_SECONDARY_CAUSESindicates how often a routing info request for an SM is handled unsuccessfully due tosecondary causes.Trigger: each time TC-U-ERROR is sent to GMSC in response to this request.

UNS_LOST_LOCATIONindicates how often a routing info request for an SM is handled unsuccessfully due tolost location.Trigger: each time TC-U-ERROR is received from the VLR in response to ProvideRoaming Number for SMS.

UNS_RECVD_SET_MWDindicates how often the delivery of SM data was unsuccessfully handled.Trigger: each time TC-U-ERROR, TC-ABORT or TC-U-REJECT is sent to VLR upon re-ceiving:

- Ph1: SET MWD- Ph2: REPORT SM DELIVERY STATUS (absent subscriber or MS memory

capacity is exceeded)

10.7 Data Service with GPRSThe General Packet Radio System (GPRS) is a packet switched data service in a GSMnetwork for mobile access to the Internet and other packet data networks. GPRS allowsthe service subscriber to send and receive data in an end-to-end transfer mode. Assuch, the HLR is enhanced with a database for GPRS subscribers.

10.7.1 Load and demand related partRECVD_LOCUPD_HPLMNindicates how often a request for GPRS location update was received from the SGSNof the home PLMN.Trigger: each time UPDATE GPRS LOCATION is received from the SGSN of theHPLMN.

RECVD_LOCUPD_VPLMNindicates how often a request for GPRS location update was received from the SGSNof the visited PLMN.Trigger: each time UPDATE GPRS LOCATION is received from the SGSN of theVPLMN.

A50016-D1109-G801-6-7618 115


Traffic Measurement

SENT_CAN_LOC_SGSN_CHANGEindicates how often a request for location canceling was sent to the old SGSN due to achange of the SGSN.Trigger: each time CANCEL GPRS LOCATION is received from the SGSN of theHPLMN.

SENT_CAN_LOC_SUB_ADMINindicates how often a request for location canceling was sent to the SGSN due to sub-scriber administration.Trigger: each time MML command CAN MSUB is received from the SGSN of theHPLMN.

SENT_INS_DEL_SUB_DATAindicates how often a request for subscriber insertion/deletion is sent to the SGSN dueto subscriber administration.Trigger: each time an MML command updating the HLR database is received, such asCR/MOD MSUB, ENTR/CAN GPRSERV, ....

SENT_RESET_TO_SGSNindicates how often a reset request is sent to the SGSN.Trigger: each time RESET is sent from the HLR to the SGSN due to recovery or MMLcommand ACT HLRUPD.

10.7.2 Grade of service related partUNS_LOC_UPD_HPLMN_SUB_BEHindicates how often a GPRS location update from the SGSN of the home PLMN wasunsuccessfully handled by the VLR due to irregular subscriber behavior.Trigger: each time TC-END U-ERROR including the proper MAP error is sent, such as:IMSI unknown, GPRS subscription unknown, ODB of roaming, roaming not allowed,user remote reject, user local reject, ISD timer expiry.

UNS_LOC_UPD_VPLMN_SUB_BEHindicates how often a GPRS location update from the SGSN of the VPLMN was unsuc-cessfully handled by the VLR due to irregular subscriber behaviorTrigger: each timeTC-END U-ERROR including the proper MAP error is sent, such as:IMSI unknown, GPRS subscription unknown, ODB of roaming, roaming not allowed,user remote reject, user local reject, ISD timer expiry.

UNS_LOC_UPD_HPLMN_OTHERindicates how often a GPRS location update from the SGSN of the home PLMN wasunsuccessfully handled by the VLR due to causes different from irregular subscriber be-havior.Trigger: each time an internal failure (e.g. MAP error) occurs in the HLR upon handlingGPRS LOC UPD from the home PLMN.

UNS_LOC_UPD_VPLMN_OTHERindicates how often a GPRS location update from the SGSN of the VPLMN was unsuc-cessfully handled by the VLR due to causes different from irregular subscriber behavior.

116 A50016-D1109-G801-6-7618


Trigger: each time an internal failure (e.g. MAP error) occurs in the HLR upon handlingGPRS LOC UPD from the visited PLMN.

UNS_CAN_LOC_SGSN_CHANGEindicates how often the old SGSN has unsuccessfully cancelled the GPRS location aftera change of SGSN.Trigger: each time timer expires in the HLR or a negative response is returned from theold SGSN upon receiving CANCEL LOCATION from the new SGSN.

UNS_CAN_LOC_SUB_ADMINindicates how often a GPRS location in the SGSN is unsuccessfully cancelled upon ap-propriate subscriber administration.Trigger: each time timer expires in the HLR or a negative response is returned from theSGSN while executing the MML command.

UNS_INS_DEL_SUB_DATAindicates how often GPRS subscriber data is inserted/deleted in the SGSN upon appro-priate subscriber administration.Trigger: each time timer expires in the HLR or a negative response is returned from theSGSN while executing the appropriate MML command.

10.8 OverloadThe following messages which were rejected in the HLR due to overload are countedand are therefore not to be considered in the calculation of successfully handled mes-sages.

UNS_MTC_OVLindicates how many mobile terminating calls were unsuccessfully handled due to over-load.Trigger: each time the HLR has rejected SEND ROUTING INFO because the formerwas overloaded.

UNS_LOC_UPD_OVLindicates how many location updates were handled unsuccessfully due to overload.Trigger: each time the HLR has rejected LOCATION UPDATE because the former wasoverloaded.

UNS_SND_PARAM_OVLindicates how many requests for parameters were handled unsuccessfully due to over-load.Trigger: each time the respective message is rejected due to HLR overload.


UNS_SS_OVLindicates how many SCI’s were handled unsuccessfully due to overload.Trigger: each time Register SS, Activate SS, Deactivate SS, ERASE SS are rejecteddue to HLR overload.

A50016-D1109-G801-6-7618 117


Traffic Measurement

UNS_SMS_OVLindicates how often a routing info request for SM is lost due to HLR overload.Trigger: each time SEND ROUTING INFORMATION for SMS is discarded (rejected)due to HLR overload.

118 A50016-D1109-G801-6-7618


11 Traffic Measurement in ACThe authentication center (AC) contains several security boxes that stores the keys andalgorithms required for the creation of the authentication parameters (covered by tri-ples). In the AC, a record of triples is generated for each mobile subscriber, usually be-fore entering the network. This record is filled up with new triples each time the previousones have been used (replenish mechanism).These triples are used by the VLR for authentication tests, i.e. to prove whether a mobilesubscriber is authorized to enter the network and to set up calls.

So, counters related to triple data are implemented in the AC on which traffic measure-ment relies. This traffic measurement can be started by entering command REC AC.

TRIPLES_REQUESTED_BY_HLRindicates the number of triples requested by the HLR.Trigger: each time SEND PARAMETERS is received.

TRIPLES_RETURNED_TO_HLRindicates the number of triples returned to the HLR.Trigger:each time SEND PARAMETERS RESULT is sent to the VLR.

REUSED_TRIPLESIndicates the number of reused triples.Trigger:each time the request for triples from the HLR is unsuccessful due to an internalevent in AC.

A50016-D1109-G801-6-7618 119


Traffic Measurement

12 Traffic Measurement in EIRThe equipment identification register (EIR) contains a database with information aboutthe device types and identity numbers of all mobile stations authorized in their servicearea. This is realized by classifying each station in one list out of three.– a white list for allowed mobile stations– a grey list for mobile stations to be observed– a black list for disconnected mobile users.

On receipt of a request from the MSC, the EIR looks for the mobile radio equipmentidentification concerned (IMEI; international mobile equipment identity) in the database(white, grey and black list). It then replies to the MSC whether the IMEI is unknown oron the white, grey or black list. Such IMEI consists of

a type approval code (TAC),a final assembly code (FAC),a serial number (SNR)

being stored in the white list.

So, counters related to these lists are implemented in the EIR on which traffic measure-ment relies. This traffic measurement can be started by entering command REC EIR.

12.1 Structure and installation related partNO_OF_BLACK_IMEIindicates the number of IMEIs in the black list of the EIR database.Trigger: each time an entry changes an administrative input (CR IMEI; CAN IMEI).

NO_OF_GREY_IMEIindicates the number of IMEIs in grey list of the EIR database.Trigger: each time an entry changes an administrative input (CR IMEI; CAN IMEI).

NO_OF_WHITE_IMEIindicates the number of IMEIs in white list of the EIR database.Trigger: each time an entry changes an administrative input (CR IMEI; CAN IMEI).

NO_OF_TAC_FACindicates the number of areas (defined by the codes TAC and FAC) created in the EIRdatabase.Trigger: each time a new area entry in the white list is created by administration.

12.2 Grade of service related partNO_OF_IMEI_CHECK_MESSAGESindicates the number of IMEI check messages received in the EIR.Trigger: each time CHECK IMEI is received from MSC.

NO_OF_UNSUCC_MESSAGESindicates the number of incorrect messages received in the EIR.Trigger: each time a message indicating a user-error, system-failure or unexpected datavalue is returned to MSC or TC-U-REJECT upon receiving CHECK IMEI.

120 A50016-D1109-G801-6-7618


NO_OF_BLACK_EQUIPMENTiindicates the number of IMEI checks that directs to a black list.Trigger: each time the EIR returns TC-RESULT indicating a black list status in reply toa CHECK IMEI.

NO_OF_GREY_EQUIPMENTindicates the number of IMEI checks that directs to a grey listTrigger: each time the EIR returns TC-RESULT indicating a grey list status in reply to aCHECK IMEI.

NO_OF_WHITE_EQUIPMENTindicates the number of IMEI checks that directs to a white list.Trigger: each time the EIR returns TC-RESULT indicating a white list status in reply toa CHECK IMEI.

NO_OF_UNKNOWN_EQUIPMENTindicates the number of IMEI checks resulting in unknown equipment.Trigger: each time TC-U-ERROR indicating “unknown equipment” is returned to MSC inreply to CHECK IMEI.

A50016-D1109-G801-6-7618 121


Traffic Measurement

13 Conventional SSS Traffic MeasurementTraffic measurement also provides counters for data about the conventional units of theswitching subsystem (SSS) suited for planning and configuration purposes.– REC TRGP

for traffic data about trunk groups– REC DEST

for traffic data about the destination– REC CP

for traffic data about the coordination processor– REC LTG

for traffic data about line/trunk groups– REC GP

for traffic data about the group processor in the LTG– REC DLU

for traffic data about the digital line unit– REC ANGRP

for traffic data about announcement groups– REC PBX

for traffic data about private exchanges

The results of each traffic measurement are stored on a disk in the CP. Upon retrievingthem via a traffic file, some additional information on the outcome of the measurementis inserted. Each result includes information on the data quality and availability of themeasurement, besides some other aspects that may differ from unit to unit. The aspectsdisplayed at the OMT of the network node can differ from those recorded on tape in theOMC.

Data qualityThe output indicates once per measurement interval (15 minutes) whether data corrup-tion has taken place.

AvailabilityThe output at the end of the measurement interval indicates whether data for the respec-tive unit was available.

1/ SECURE data has not been corrupted2/ TIME_CORR system time is corrected during interval3/ NO_INIT insecure data; counter initialization has failed due to

e.g. recovery or CP overload<========> displayed after each line at the OMT

<============> added to each record on tape

1/ blank data is available2/ DEL data has been deleted during interval3/ NONE data could not be registered due to

e.g. recovery or CP overload<===> displayed after each line at the OMT

<=======> added to each record on tape

122 A50016-D1109-G801-6-7618


13.1 Trunk Group Traffic MeasurementThe assignment and utilization of trunk groups in PLMN is the same as in PSTN. So therelevant traffic data to be recorded apply to nodes from both networks. Therefore, thesetraffic measurement and supervision functions can be used by the MSC operator withoutany mobile-specific alterations.

The new, additional procedures used during call setup at the radio interface (e.g. pagingprocedure, authentication, ciphering) are executed via a signaling connection (SCCP).These procedures do not use any trunk-group-related resources and have no influenceon the grade of service of the trunk groups; therefore, they do not require any modifica-tion to the existing traffic measurement and supervision for trunk groups.The following supervisory functions are applied:– all trunks busy time supervision– traffic load supervision– handover supervision.

Therefore, counters are provided on which relies traffic measurement for trunk group da-ta: event counters, holding time and overload counters. This traffic measurement isstarted by entering command REC TGRP.

Index and operation mode are additional constants being inserted when the counter re-sults are retrieved via a traffic file (at the OMT or the OMC) in order to allow the mea-sured data to be allocated.– Index

All data about trunk groups will be sorted by a control index when transferring it todisk in the CP. The indices (1--7) refer to counters with respect to specific kind of da-ta:

(1): seizure and traffic volume data(2): additional trunk group data(3): data on successful calls without reaching their destination(4): data on refused calls(5): data on refused calls at CCS7 trunk groups(6,7): data on non-hierarchical trunk groups( not mobile-specific)

As far as the type of trunk group has been implemented, the relevant counter datawill be transferred. Therefore, it may happen that some indices are not indicated dur-ing measurement.

– TGNO and OPMODEEach trunk group is identified by its number, and has a code representing its opera-tion mode.

13.1.1 Index 1: seizure and traffic volume data*CC:I(O)indicates how often a trunk group was seized, i.e. carried calls in CP database, by in-coming (outgoing) traffic.Trigger: start and stop depend on the message of the respective trunk type:

startsat receipt (sending) of IAM: for ISDN trunks

incoming traffic: IC

outgoing traffic: OG

bothway traffic: BW

A50016-D1109-G801-6-7618 123


Traffic Measurement

at sending of ASSIGNMENT REQ or HO REQ: for BSSAP trunksstops at release of trunk, e.g. REL COM

*TV:I(O)indicates the sum of holding times (i.e. traffic volume) for seizures of a trunk groupthrough incoming (outgoing) traffic.Trigger: start and stop depend on the message of the respective trunk type:

startsat receipt (sending) of IAM: for ISDN trunksat sending of ASSIGNMENT REQ or HO REQ: for BSSAP trunks

stops at release of trunk, e.g. REL COM

*CCS_ANSWER:I (O)indicates how often the trunk group was successfully seized by incoming (outgoing)calls that were answered at the mobile station (called terminal)Trigger: each time the call is released.

TV_ANSWER:I (O)indicates the volume of incoming (outgoing) traffic for the trunk group that has been an-swered at the mobile station (called terminal).

13.1.2 Index 2: additional trunk group data*CONNECTED LINESindicates the number of connected trunks. With respect to a bothway trunk group, thisrepresents the total number of trunks set up for IC and OG.

NO OF BLO LINESTraffic load which has not been handled because a number of trunks in the group wereblocked during the measurement interval.

*SEMI BLOCKED LINESindicates the number of trunks blocked semipermanently for O&M reasons. The counterindicates the current value at the end of each quarter hour.

*TRANS BLOCKED LINESindicates the number of trunks blocked transiently (i.e. blocking status is not caused byany O&M reason in the home exchange). The value is updated at the end of each quar-ter hour and applies to IC and OG.Trigger: actual number of transiently blocked trunks at the end of the measured interval.

TV SEMI BLOLIsum of blocking durations (traffic volume) due to maintenance caused by semiperma-nent trunk blocking.

TV TRANS BLOLIvolume counter for transiently blocked trunks in the group; see also “TRANS BLOCKEDLINES”.

124 A50016-D1109-G801-6-7618


TGRP BLO TIME: Oindicates the sum of the time in seconds for OG during which the trunk group was in asemipermanent or transient blocking state. A bothway trunk group can still accept ICthen.

ATB TIMEtotal blocking time due to all-trunks-busy in seconds for OG or, in bothway trunk groups,for both IC and OG.Trigger:

starts at seizure of the last free trunk of the group.stops at release of a trunk after previous ATB-condition.

*NUMBER OF ATBindicates the number of occurrences of ATB, i.e. the number of times that all availabletrunks in the group were busy.Trigger: each time the last free trunk in the group is seized.

13.1.3 Index 3: data on successful calls without reaching their destination*CCS CONGESTIONindicates the number of calls released after trunk group seizure (CC:O) because thebackward signal for “congestion” (all trunks busy) was received in the subsequent MSC

CCS INCMP DIALindicates the number of calls released after trunk group seizure (CC:O) because callingparty goes on-hook after incomplete dialing or interdigit time-out in the own MSC.

CCS LINK FAILUREindicates the number of calls released after trunk group seizure (CC:O) because accessto the outgoing trunk was not possible. Call release is initiated by the LTG at the calledend.

CCS UNALL NUMindicates the number of calls released after trunk group seizure (CC:O) because the di-aled directory number was not created or because the calling party is not authorized tomake calls to this destination (CUG, service).

CCS RELORIG ENDTOENDindicates the number of calls released after trunk group seizure (CC:O) due to “clear for-ward” from the previous MSC without knowledge of the reason for release.

CCS SUB BUSYindicates the number of calls released after trunk group seizure (CC:O) because thebackward signal “subscriber terminal busy” was received.

*CCS INT TECHN IRREGindicates the number of calls released after trunk group seizure (CC:O) due to technicalfault (e.g. LTG failure on A- or B-side) in the own MSC.

A50016-D1109-G801-6-7618 125


Traffic Measurement

*CCS EXT TECHN IRREGindicates the number of calls released after seizure of the outgoing trunk group (CC:O)due to a technical fault in the subsequent MSC after SN through-connection.

*CCS UNANSWEREDindicates the number of calls released after trunk group seizure (CC:O) because thecalled party does not answer (time-out of ringing time supervision) or because the call-ing party of the own MSC or the incoming call goes on-hook during ringing.

13.1.4 Index 4: data on refused calls*CCU SUM OFL/LOSSindicates the number of unsuccessful attempts to seize the trunk group. This representsthe sum of overflow calls and lost calls. For trunk groups in the high-usage route or finalroute, it represents the sum of lost calls.

*CCU LOST CALLSindicates the number of calls offered to the trunk group as first-choice route which thenoverflowed but were unsuccessful in all alternative routes. This also includes calls re-jected after being offered to the final trunk group as first-choice route.

CCU NM TGRP BLOCKINGindicates the number of attempts to seize the trunk group rejected due to network man-agement actions (cancel, skip, ...) in the trunk group (lost calls).Trigger: at each attempt to seize a trunk group blocked by network management.

*CCU TECHN IRREGULARindicates the number of attempts to seize the trunk group rejected due to a technicalfault when entering the trunk busy status or due to SN blocking (no access to outgoingtrunk) (lost calls).

CCU TGRP BLOCKEDindicates the number of calls offered to a trunk group which overflowed (high-usage cir-cuit group) or were rejected (final circuit group or only-choice circuit group) because thetrunk group was blocked for administration or maintenance.

CCU TRUNK RESERVATIONindicates the number of calls offered to trunk group which overflowed (high-usage circuitgroup) or were rejected (final circuit group or only-choice circuit group) because thetrunks in the group were reserved.

CCU ALL TRUNKS BUSYindicates the number of calls offered to a trunk group which overflowed (high-usage cir-cuit group) or were rejected (final circuit group or only-choice circuit group) because allthe trunks in the group were marked busy in the CP.

126 A50016-D1109-G801-6-7618


13.1.5 Index 5: data on refused calls at CCS7 trunk groupsNUMB CCS7 DPC OLOADindicates the number of occurrences on which destination point code (DPC) overloadwas recorded for the CCS7 trunk group.

CCS7 DPC OLOADindicates the overload duration (in seconds) due to DPC overload in the CCS7 trunkgroup.

*CCS CCS7 CALL FAILindicates the number of calls released after trunk group seizure (CC:O) because the linesignal CALL FAILURE (for TUP) was received, or because certain line signals (IUC forISUP) in CCS7 messages were received, from which RCF CALL FAILURE was derived

*CCU CCS7 CCNC OLOADindicates the number of calls offered to a circuit group with CCS7 signaling which over-flowed (high-usage circuit group) or were rejected (final circuit group or only-choice cir-cuit group) due to CCNC overload in the own MSC.

CCU CCS7 DPC OLOADindicates the number of calls offered to a circuit group with CCS7 signaling which over-flowed (high usage circuit group) or were rejected (final circuit group or only-choice cir-cuit group) due to DPC overload in the subsequent MSC.

CCU CCS7 DPC OL ACCindicates the number of calls offered to a circuit group with CCS7 signaling which over-flowed (high-usage circuit group) or were rejected (final circuit group or only-choicegroup) because the transmission buffer of the links for the selected outgoing server wasfull.

13.1.6 Index 6,7: data of non-hierarchical trunk groupsWhen trunk groups are organized in a non-hierarchical way, a routing mechanism canbe provided to distribute the traffic load among several trunk groups. Traffic is normallyrouted via a direct trunk group (primary route). Depending on its occupation, traffic canbe routed via alternative trunk groups (a first-choice or a second-choice route).

CC: NH DIRECT: Oindicates the number of calls carried at the direct trunk group by successful outgoing sei-zures (connection is switched through SN).

TV: NH DIRECT: Oindicates the traffic volume handled at the direct trunk group on successful outgoing sei-zures.

CCS NH DIRECT ANSW: Oindicates the number of outgoing calls being successfuly seized in the direct trunkgroup, and answered on the called terminal.

A50016-D1109-G801-6-7618 127


Traffic Measurement

CCU NH DIRECT OFLindicates the number of those unsuccessful attempts for seizing in a direct trunk group,that result into an overflow to an alternative trunk group.

CC:NH ALT1: Oindicates the number of calls carried at the alternative trunk group (first-choice) becauseof successful outgoing seizures (connection is switched through the SN).

TV NH ALT1: Oindicates the traffic volume handled by the alternative trunk group because of successfuloutgoing seizures.

CCS NH ALT1 ANSW: Oindicates the number of outgoing calls being successfuly handled in the alternative trunkgroup, and answered on the called terminal.

CC NH ALT1 REROUTINGindicates the number of events for outgoing seizures of an alternative trunk group whichhave been rerouted to another trunk group because e.g. the next exchange finds no freetrunk.

CCU NH ALT1 LOSTindicates the number of unsuccessful attempts to seize an alternative trunk group whichcannot be rerouted any longer to search for a free trunk.

CC: NH ALT2: O . . CCS NH ALT2 ANSW: OThese three counters have the same function as described for the first-choice route(ALT1), but now they apply to an alternative trunk group (second-choice route).

CCU NH ALT2indicates the number of unsuccessful attempts to seize an alternative trunk group (sec-ond-choice).

13.2 Destination Traffic MeasurementThe measurement of traffic towards specific destinations is used to obtain planning datafor network design (e.g. creation of high-usage routes) and grade of service data forthese destinations.

Therefore, counters are implemented on which relies traffic measurement for destina-tion data. This measurement can be started by command REC DEST by specifyingthem as an object group. A maximum of 512 internal and external destinations simulta-neously can be measured.

Index, DESTLAC, DEST, ORIG and ZDIG are additional constants being inserted whenthe counter results are retrieved via a traffic file (at the OMT or the OMC) in order to allowthe measured data to be allocated.– Index

Index 50 or 51 is used only at the tape interface for data control.

128 A50016-D1109-G801-6-7618


– DESTLACThis local area code of the destination is only relevant if the CP serves more thanone local network from which internal destinations have to be measured.

– DESTThe directory number of the measured destination is indicated by its code point.

– ORIGThe originating mark is entered in the call processing database for incoming trunkgroups and subscriber groups. Traffic to the destinations can be measured in rela-tionship with the origin (optional parameter); i.e. from one or several origins (max.255) to one given destination. If this is not specified, all calls to this destination aretaken into account.

– ZDIGThe language digit for accessing the operator position. This digit modifies, for exam-ple, the destination number; i.e. input of this digit in the destination number meansthat traffic to the position accessed by the language digit is measured.

CCindicates how many calls to the destination are accepted in the home MSC; i.e. the callis switched through the SN in the home MSC and e.g. C:SETUP C and C:SEIZURE CBT have been sent from the CP to the LTGs.

TCtotal holding time (traffic carried in dErl).

TC WITH ANSWERSum of holding times (traffic carried in dErl) resulting from calls answered at the calledstation. The duration of an answered call is added to the counter at the end of the call,or in the case of long-duration calls, an additional count e.g. 1800 seconds is added.This intermediate time can be administered in the CP.

CCS CCS7 CALL FAILindicates the number of calls that, after being connected by the SN of the home MSC,are rejected upon receiving line signal CALL FAILURE.

CCS CONGESTIONindicates the number of calls that, after being connected by the SN of the home MSC,are rejected upon receiving line signal “congestion”.

CCS INCMP DIALindicates the number of calls that, after being connected by the SN of the home MSC,are released because the calling party went on-hook after incomplete dialing or becauseinterdigit time supervision timed out in the home MSC.

CCS LINK FAILUREindicates the number of calls released by the LTG after connection through the SN be-cause at the B-side the group switch could not be set in the LTG or DIU, or because nofree time slot could be seized.

A50016-D1109-G801-6-7618 129


Traffic Measurement

CCS UNALL NUMindicates the number of calls that, after being connected by the SN of the home MSC,are released due to “number unobtainable” in the subsequent MSC.

CCS OPERATOR RELEASEindicates the number of calls released by the operator after connection through the SN,e.g. because an audible “busy” tone was received. (only for outgoing operator traffic.

CCS RELORIG ENDTOENDindicates the number of calls that, after being connected by the SN of the home MSC,are released due to a CLEAR FORWARD from the home MSC, without indicating theactual reason for call failure, e.g. “congestion”.

CCS SUB BUSYindicates the number of calls that, after being connected by the SN of the home MSC,are released due to “subscriber busy”.

CCS INT TECHN IRREGindicates the number of calls that, after being connected by the SN of the home MSC,are released due to technical irregularities and radio subsystem faults.

CCS EXT TECHN IRREGindicates the number of calls released after connection through the SN due to technicalfaults in the following MSC.

CCS UNANSWEREDindicates how many times a successful through switching of the SN in the home ex-change was rejected because the B-subscriber’s device has not answered.

CCS WITH ANSWERindicates the number of calls answered at the called station. This event is not counteduntil the end of the call.

CCU CONGESTIONindicates how many calls untimely end before being trough connected by the SN of thehome MSC upon receiving line signal “congestion”, “subscriber busy” or CCNC overloadin the home MSC or due to overload in the subsequent MSC.

CCU NM CODE BLOCKINGindicates the number of calls rejected in the home MSC before being connected throughthe SN due to network management action. Such action reduces in stages or completelyblocks traffic to specific destinations.

CCU NM TGRP BLOCKINGindicates the number of calls rejected in the home MSC prior to connection through theSN because they were not authorized to access the outgoing trunk group (e.g. trunk res-ervation).

130 A50016-D1109-G801-6-7618


CCU TECHN IRREGULARindicates the number of calls prematurely terminated in the home MSC prior to connec-tion through the SN due to internal blocking in the SN, number unobtainable or internalor external irregularities from the originating MSC.

13.3 CP Traffic MeasurementFor the measurement of traffic in the CP of each network unit (MSC, VLR and HLR) dataconcerning

call processing loadtotal load


Therefore, holding time counters are implemented on which relies CP traffic measure-ment. This measurement can be started by entering command REC CP.

Integration time and output are additional constants being inserted when the counter re-sults are retrieved via a traffic file (at the OMT or OMC) in order to allow the measureddata to be allocated.

Integration timeA measurement interval takes 15 minutes (900 seconds). And the counters for trafficmeasurement are constantly updated in a 4 second cycle.To be able to define whether the processor was heavily loaded some time within this in-terval, an integration time is introduced. By specifying this time at command input, theresults can be output each multiple (from 1 up to 255) of 4 seconds, instead of just atthe end of the interval.

OutputThe output at the end of the measurement interval indicates whether the processor

has been active: specific load valuewas not active: *has not been created: blank.

13.4 LTG Traffic MeasurementIn order to determine the busy period for the network node and the code receiver groups,a lot of data concerning

calls offered to the exchangenot accepted calls due to a lack of resources in the LTGtraffic offered to the code receiver groups

are recorded in counters.

Therefore, counters are implemented on which relies LTG traffic measurement: eventcounters, holding time and waiting time counters. All these counters are continuously

counter for processorsCARRIED_TRAFFIC:

BAPM BAPS CAP0 CAP1 --------- CAP9

call processing load in miliErlangTOTAL_INTENSITY:

BAPM BAPS CAP0 CAP1 --------- CAP9

total load in miliErlang

A50016-D1109-G801-6-7618 131


Traffic Measurement

updated by the call-processing software in the line/trunk groups (LTGs) and their datais collected at measurement intervals of 15 minutes.

This traffic measurement can be started by entering the command REC LTG. A param-eter allows the operating personnel to specify whether or not code receiver measure-ment data have to be output. The LTG measurement is used only in the MSC as the LTGin the VLR and HLR just offers channels for CCS7 signaling and not for user traffic.

LTG numberis a number or a name by which each LTG is identified. This number is inserted whenthe counter results are retrieved via a traffic file (at the OMT or OMC) in order to allowthe measurement data to be allocated.

• The following data is output for each LTG:

SLC:OFF CALLSindicates the number of calls offered by subscriber line circuits SLC (lines).

SLC:ACC CALLS GPindicates the number of calls accepted by the LTG from subscriber line circuits for in-coming subscriber traffic (originating traffic).

SLC:REJ CALLS OLindicates the number of calls from subscriber line circuits rejected by the GP. Possiblereasons for rejection: LTG/CP CPU overload, SEIZURE A calling rate too high, lack ofGP resources such as lack of heap or threshold exceeded in task or available queue.Calls rejected due to lack of code receivers are not counted.

TR CIRC:OFF CALLSindicates the number of calls offered by incoming trunk circuits.

TR CIRC:ACC CALLS GPindicates the number of calls accepted by the LTG from trunk circuits for incoming traffic.

TR CIRC:REJ CALLS OLindicates the number of calls from trunk circuits rejected by the GP. Possible reasonsfor rejection: LTG/CP CPU overload, SEIZURE A calling rate too high, lack of GP re-sources, for example lack of heap or threshold exceeded in task queue or availablequeue. Calls rejected due to lack of code receivers are not counted.

• The following data is recorded for each code receiver group:

CRM/CRP:TCSum of holding times (traffic carried in mErl).

CRM/CRP:SUMMARY EFFECTSindicates the number of calls offered.

132 A50016-D1109-G801-6-7618


CRM/CRP:ACCEPTED CALLSindicates the number of calls accepted.

CRM/CRP:SUM DELAYSSum of delay times.

CRM/CRP:NUMBER OF DELAYSindicates the number of calls which had to wait for a code receiver.

CRM/CRP:DELTHR EXCEEDEDindicates the number of calls which had to wait more than a defined time (default 3 sec-onds, selection range 1 to 20 seconds) for a code receiver.

CRM/CRP:NUMB OF CONNECTindicates the number of connected code receivers.

CRM/CRP:NUMB OF BLOCKEDindicates the number of blocked code receivers (current value at the end of the integra-tion period).

• The following data is recorded for each group processor (GP):

GP_IDRindicates for each GP the number of routine tests that have run.

GP_MEAindicates for each GP the average time (in microseconds) for the execution of the test.

13.5 GP Traffic MeasurementIn order to collect in the CP just those data with which the load of the group processor(GP) can be calculated, a part of the counters being implemented for the LTG are usedfor the GP traffic measurement as well.

The measurement relying on these counters can be started by entering command RECGP.

13.6 DLU Traffic MeasurementFor the measurement of the traffic in the LTG concerning the digital line unit (DLU), datato determine the time at which the busy hour occurs for the subscribers served by thisDLU can be recorded by counters. With respect to mobile equipment, the DLU that in-corporates the interworking equipment (called data service unit) is involved in this mea-surement.

Therefore, counters are implemented on which relies traffic measurement of each DLU:event counters, holding time and blocking time counters. This measurement is startedby entering the command REC DLU for each DIU.

A50016-D1109-G801-6-7618 133


Traffic Measurement

The DLU and DIU number are additional constants being inserted when the counter re-sults are retrieved via a traffic file (at the OMT or OMC) in order to allow the measure-ment data to be allocated.– An external DLU number .– The DIU number is composed of a TSG, a GP and a DIU number.

CC:I(O)indicates how often calls have been originated by (terminated at) connected subscrib-ers; incoming (outgoing) traffic.

TC:I(O)indicates the traffic carried in mErl of incoming (outgoing) traffic for connected calling(called) subscribers.

CONNECTED_CHANNELSindicates the number of channels provided for call traffic.

BLOCKED_CHANNELSindicates the number of blocked channels.

SUM_CH_BLO_TIMEindicates the sum of time in seconds during which the channels were blocked for main-tenance (max. 900 s). The blocking time is totaled for each channel every 15 minutes.

CC_SCI_D_CHANNELindicates the number of purely D-channels that are accepted for SCIs, i.e., channel sei-zures in the LTG and in the CP are not counted.

• The following data is recorded in the CP per DLU:

CCU:INTERNALindicates how many calls are rejected in the CP due to lack of channels in internal trafficwhen both the calling and called party are in the same network node. The lack of chan-nels can be a lack of time slots in the LTG pair or a failure of the LTG through which theDLU is connected.

CCU:TERMINATINGindicates how many calls are rejected in the CP due to lack of channels when traffic isoffered to called subscribers in the network node on incoming trunks. The lack of chan-nels can be a lack of time slots in the LTG pair or a failure of the LTG through which theDLU is connected

134 A50016-D1109-G801-6-7618


13.7 Announcement Group Traffic MeasurementFor the measurement of traffic in announcement groups, specific data concerning loadand grade of service can be recorded by counters.

Therefore, counters are implemented on which relies traffic measurement of the an-nouncement group: event counters, holding time and overload counters. This measure-ment is started by entering the command REC ANGRP.

They are updated either implicitly (i) or explicitly (e) as marked further on for eachcounter.– (i) when an announcement line is marked busy or idle in the database;– (e) at the end of a call using a grade of service value in the database obtained by

the call processing/traffic measurement software. This update takes place by meansof the reason for call failure (RCF) in the release message.

Index and TGNO are additional constants being inserted when the counter results areretrieved via a traffic file (at the OMT or OMC) in order to allow the measurement datato be allocated. Each count is either (i) for implicit or (e) for explicit update.– Index

Index 1 or 2 are used only at the tape interface for data control.– TGNO

The trunk group number or the corresponding announcement group name.

CONNECTED_LINES (i)indicates the number of announcement lines in the group.

SEIZE_MAXIMUM (i)Sum of the maximum possible number of listeners (broadcasting) of all announcementlines in the group.

SEMI_BLOCKED_LINES (i)indicates the number of semipermanently blocked lines. The counter indicates a currentvalue at the end of each quarter hour.

TC_SEMI_BLOLI (i)indicates the sum of blocking times of semipermanently blocked lines (traffic carried indErl); broadcasting is left aside.

TRANS_BLOCKED_LINES (i)indicates the number of transiently blocked lines.The value is updated at the end of each quarter hour.

TC_TRANS_BLOLI (i)indicates the sum of blocking times (traffic carried) in dErl of the transiently blockedlines.

ANGRP_BLO_TIME (i)indicates the sum of the maintenance-related blocking times of the announcementgroup in seconds.

A50016-D1109-G801-6-7618 135


Traffic Measurement

TC (i)indicates the sum of holding times (traffic carried in dErl) for calls accepted by the an-nouncement group, i.e. for broadcast announcement group, this is the number of ac-cepted listeners (n per line).

CC (i)indicates how often calls have been accepted by the announcement group, i.e. for abroadcasting announcement group, this is the number of accepted listeners (n per line)

CCU_ATB (i)indicates the number of calls rejected due to “announcement group busy”.Trigger: each time the last free position in the list of listeners is occupied.

ATB_TIME (i)indicates the total blocking time due to all trunks busy during which the announcementgroup was blocked.

NUMBER_OF_ATB (i)indicates the number of occurrences on which ATB time was recorded for the announce-ment group.

CCU_ANGRP_BLOCKED (i)indicates the number of calls rejected due to (semipermanent or transient) blocking ofthe announcement group.

CCU_TECHN_IRREGULAR (i)indicates how often attempts to seize the announcement group are rejected due to atechnical fault when entering the announcement line busy status (entry in the list of lis-teners) or due to SN blocking (no access to outgoing line).

CCS_TECHN_IRREGULAR (e)indicates the number of calls released after seizure of the announcement group (enteredin the list of listeners) due to technical irregularities.

13.8 PBX Traffic MeasurementFor the measurement of traffic flows through private (automatic) branch exchangesP(A)BXs,

service-related data andservice-independent data


Therefore, event and holding time counters are implemented in the CP database onwhich relies PBX traffic measurement. This measurement can be started by enteringcommand REC PBX with a specific object group. Up to 255 PBXs, with or without directinward dialing, can be measured simultaneously. Alternatively, it is possible to startmeasurement of 255 PBXs via 8 commands, each with 32 individual objects. The resultsare stored on CP disk from where they can be retrieved.

136 A50016-D1109-G801-6-7618


Exclusively for PBX measurement, the traffic types “incoming” (I) and “outgoing” (O)handled by PBX trunk groups, are consistently looked at from the point of the view of thenetwork node. So, a call originated from a PBX user is incoming for the MSC.– Incoming traffic is handled by trunk groups being accessible either exclusively in-

coming or bothway.– Outgoing traffic is handled by trunk groups being accessible either exclusively out-

going or bothway.

The service number, index, LAC, DN and operating mode are additional constants beinginserted when the counter results are displayed at the OMT of the network node or re-corded in the OMC in order to allow the measured data to be allocated.– Service number

The incorporation of private ISDN exchanges into the MSC provides a lot of appro-priate services the data of which can be counted. Such service-related data is iden-tified by an internal service number (1 to 32) in the CP. An output only applies if theproper service has been used during the measurement interval.General data of the PBX (of any type) is counted seperately. Such service-indepen-dent data is indicated by the service number 0 (zero). This data always has an outputafter the measurement interval (of 15-minutes).

– Index is only used at the tape interface for data control.Index 1 or 2 for service-related dataIndices 1 up to 4 for service-independent data

– LACThis local area code is only relevant if the CP serves more than one local network.It is specified when entering the command and is displayed in the header at theOMT.

– DNEither the directory number of the measured PBX being used to accessan incoming or bothway PBX line,or the extension number of the calling party being served by the PBX.

– OPMODEThe folowing codes represent the operation mode that can be created for a PBXgroup.

13.8.1 Service-related dataThe following data is output per service as identified by the service number. The nameof each service is country-specific and varies according to the signaling protocol(EDSS1, 1TR6).

CC:I (O)indicates how many incoming (outgoing) calls for the respective service have been ac-cepted by the CP and how often the service has changed.

traffic type: analog ISDN(EDSS1) ISDN(1TR6)

outgoing A_OG I_OG R_OG

incoming A_IC I_IC R_IC

bothway A_BW I_BW R_BW

mixed M_BW

A50016-D1109-G801-6-7618 137


Traffic Measurement

TV:Iindicates the sum of holding times (traffic volume) for the respective service through in-coming calls towards the CP that have been accepted by the latter.

TV:Oindicates the sum of holding times (traffic volume) for the respective service through out-going calls towards the called party over B channels that have been accepted by the CP.

CCS_ANSWER:I (O)indicates how often incoming (outgoing) calls at the PBX trunk group have successfullybeen answered on the called station (terminal).

TV_ANSWER:I (O)indicates the volume of incoming (outgoing) traffic at the PBX trunk group that is an-swered on the called station (terminal).

13.8.2 Service-independent dataCounters as described for service-related data are also implemented for service-inde-pendent data; they register the same kind of data. In addition, the following counters areimplemented. The output of these counters after measurement is identified by digit 0.

CCU:Oindicates the number of unsuccessful attempts in the CP to seize the trunk group. Theseare lost calls for the outgoing trunk group (from CP to called subscriber) per line and forbothway trunk group.

ATB TIMETotal blocking time (due to all trunks busy) for OG or in bothway trunks for both IC andOG.

NO OF ATBindicates the number of occurrences of ATB; i.e. how often all available lines in thegroup were busy.

CONNECTED CHANNELSindicates how many channels are available for connection. With respect to bothwaytrunk groups, this represents the total number of trunks both for IC and OG.

SEMI BLOCKED CHANNELSindicates the number of trunks blocked for O&M purposes. The counter indicates a cur-rent value at the end of each quarter-hour.

TRANS BLOCKED CHANNELSindicates the number of trunks blocked transiently. The counter indicates a current valueat the end of each quarter hour.

138 A50016-D1109-G801-6-7618


14 MP Load MeasurementsIn order to operate the signaling network, the GSN is realized by means of main proces-sors, a main-processor system. A main processor (MP) can handle several softwareprocesses, such as packet processing, protocol handling, performance measurement,GPRS accounting and OA&M functions.

Because the CPU of the main processor is split into several virtual central processorunits (VCPUs), each of them is also involved in these processes during a budgeted time.

In order to get a realistic time budget, a number of counters capable of measuring theMP load are implemented. The load situation for the various processes on a given MPcan be derived by retrieving their data during the measurement time period.

The maximum load and average load per VCPU and message handler are recordedwith the MP load measurements. They provide the operator with an overview of the loadsituation regarding selectable MPs during the measurement time period. The operatorcan start a measurement job in the GSN via a Q3 task (see Tab. 14.1).

14.1 Measurement Object for VCPUFor this measurement object the main and average loads of the different VCPUs are re-corded by the following counters. A separate VCPU is provided in order to guarantee aruntime budget for GPRS accounting according to the model.

vcpu mpTotalAverageLoad

indicates the mean load (in mErl) of all VCPUs of a given MP.

vcpu mpTotalMaximumLoad

indicates the maximum load (in mErl) of all VCPUs of a given MP.

vcpu SystemIntegrityAverageLoad

indicates the mean load (in mErl) of the VCPU being provided with an unlimited runtimebudget for system integrity.

vcpu SystemIntegrityMaximumLoad

indicates the maximum load (in mErl) of the VCPU being provided with an unlimited runt-ime budget for system integrity.

vcpu sltPrhAverageLoad

indicates the mean load (in mErl) of a VCPU protocol handler.

Measurement object(Object class)

Section Q3 command

a measurement object for VCPU(vcpuCurrentData)

14.1 CR MPLDME

a measurement object for MH(mhCurrentdata)

14.2

Tab. 14.1 Object classes for MP load measurements

A50016-D1109-G801-6-7618 139


Traffic Measurement

vcpu sltPrhMaximumLoad

indicates the maximum load (in mErl) of a VCPU protocol handler.

vcpu oamAverageLoad

indicates the mean load (in mErl) of a VCPU being provided with operation, administra-tion and maintenance functionality.

vcpu oamMaximumLoad

indicates the maximum load (in mErl) of a VCPU being provided with operation, admin-istration and maintenance functionality.

vcpu callpAverageLoad

This counter value is not relevant.

vcpu callpMaximumLoad


vcpu SystemUpgradeAverageLoad

indicates the mean load (in mErl) of a VCPU being provided with system upgrade.

vcpu SystemUpgradeMaximumLoad

indicates the maximum load (in mErl) of a VCPU being provided with system upgrade.

vcpu ccs7NmAverageLoad

indicates the mean load (in mErl) of a VCPU being provided with SS7-related function-ality.

vcpu ccs7NmMaximumLoad

indicates the maximum load (in mErl) of a VCPU being provided with SS7-related func-tionality.

vcpu Spare07NmAverageLoad


vcpu Spare07NmMaximumLoad


vcpu Spare08NmAverageLoad

indicates the mean load (in mErl) of the VCPU being provided with a runtime budget forGPRS accounting.

vcpu Spare08NmMaximumLoad

indicates the maximum load (in mErl) of the VCPU being provided with a runtime budgetfor GPRS accounting.

vcpu backgroundAverageLoad

indicates the mean load (in mErl) of a VCPU due to background processes.

140 A50016-D1109-G801-6-7618


vcpu backgroundMaximumLoad

indicates the maximum load (in mErl) of a VCPU due to background processes.

vcpu auditAverageLoad

indicates the mean load (in mErl) of a VCPU due to audit processes.

vcpu auditMaximumLoad

indicates the maximum load (in mErl) of a VCPU due to audit processes.

vcpu idleAverageLoad

indicates the mean load (in mErl) of a VCPU due to idle processes.

vcpu idleMaximumLoad

indicates the maximum load (in mErl) of a VCPU due to idle processes.

vcpu SystemBaseLoadAverageLoad

This is the mean base load (in mErl) as a result of the calculation: total load (= 1000mErl) - sum of the average loads of all measured VCPUs.

vcpu SystemBaseLoadMaximumLoad

This is the maximum base load (in mErl) as a result of the calculation: total load (= 1000mErl) - sum of the maximum loads of all measured VCPUs.

14.2 Measurement Object for MHFor this measurement object the main and average loads of message handlers are re-corded by the following counters. A separate message handler is also provided for theGPRS support node.

ccs7MgrAverageLoad

indicates the mean load (in mErl) of the SS7-related functionality.

ccs7MgrMaximumLoad

indicates the maximum load (in mErl) of the SS7-related functionality.

mhSpare04AverageLoad


mhSpare04MaximumLoad



indicates the mean load (in mErl) of the GSN message handler.


indicates the maximum load (in mErl) of the GSN message handler.



A50016-D1109-G801-6-7618 141


Traffic Measurement











prhMgrBaseLoadAverageLoad

indicates the mean load (in mErl) of the protocol handler managers.

prhMgrBaseLoadMaximumLoad

indicates the maximum load (in mErl) of the protocol handler managers.

sgtrMgrAverageLoad

indicates the mean load (in mErl) of the protocol handler manager for SCCP global titlerouting.

sgtrMgrMaximumLoad

indicates the maximum load (in mErl) of the protocol handler manager for SCCP globaltitle routing.

uniMgrAverageLoad

This counter value is not relevant for the GSN.

uniMgrMaximumLoad

This counter value is not relevant for the GSN.

142 A50016-D1109-G801-6-7618


15 SS7-specific Traffic MeasurementSignaling on common channels for internetwork node communication in theD900/D1800/D1900 system takes place according to signaling system number 7 (SS7)protocols. Signaling traffic control in the different nodes is realized by:– either the signaling system network control (SSNC), an SS7 platform based on the

ATM technology with uniform data rate;– or the common channel network control (CCNC) based on PCM spans of 2 Mbit/s.

Signaling system no. 7

The signaling system number 7 (SS7) is an International Telecommunication Union(ITU-T) level-structured signaling system whereby each level defines a set of rules andprocedures performing specific tasks with repect to the exchange of signaling informa-tion. SS7 is composed of different parts each characterized by their functions which arerealized by means of protocols.

The following SS7 parts are used between the network nodes:– message transfer part (MTP)– signaling connection control part (SCCP)– transaction capabilities application part (TCAP)

Measurement process

Because the data for SS7 signaling includes data for MTP, SCCP and TCAP, the follow-ing types of measurements apply:– MTP measurement (SSNC), or– CCS7-specific measurement (CCNC);– SCCP measurement

- with SSNC, or- with CCNC;

– TCAP measurement (applies to both SSNC and CCNC)

SCCP/TCAP traffic measurement is performed in accordance with RecommendationQ.752 of the ITU-T White Book. This involves the registration of SCCP/TCAP events us-ing software counters in the entities of a node. These events are the SS7-based signal-ing or information messages exchanged between nodes of a mobile network or theservice control points of the intelligent network during normal system operation.

The event counters are supervised by a process for measurements in the signaling net-work. This process controls the execution of the measurements and outputs the databuffered in the processor at 15-minute intervals to the output device specified in thecommand. They are activated at the start of each measurement and continually updat-ed.

15.1 MTP Measurement (SSNC)The MTP measurements provide details on the quality and volume of the signaling per-formance. The operator can start a measurement job via a Q3 task (see Tab. 15.1). Themeasurement results are emitted as report notifications containing the value of each at-tribute (counter) being observed during the reporting. The counters, whose values arereported, are described further on in this chapter in the same order as they appear in thereport notification.

A50016-D1109-G801-6-7618 143


Traffic Measurement

Output of the measured values

The log files for the measured values of SS7 measurements are created on the hard diskof the MP. Therefore, they cannot be processed with the commands of CP file manage-ment in the same way as the measurement files of the general traffic measurements.

The NetManager is provided with the application “Performance Data Collector” speciallyfor the traffic measurement files. This collector transfers the measured values from thehard disk of the MP to the disks of the Netmanager. The measurement data is read fromthe log file of the MP, converted into ASCII format and stored in the transmission files inthe common file store of the Netmanager network. If the transmission of data was con-cluded successfully, the application “Performance Data Collector” deletes the data in theMP log files.


Section Q3 command

Net element measurement(switchingElementMeasurement)

15.1.1 CR SIGNEME

Signaling point utilization measurement(allSignalingPointUtilisationData)

15.1.2 CR SIGPTME

Obligatory signaling point utilization measurement(oblSignalingPointUtilisationData)

15.1.3

Network MSU measurement(perNetCounterMSU)

15.1.4

Signaling point measurement(signalingPointData)

15.1.5

Link set duration measurement(signalingLinkSetDurationData)

15.1.6 CR SIGLSME

Destination point measurement(routeSetInformationData)

15.1.7 CR SIGDPME

Obligatory link duration measurement(oblSignalingLinkDurationData)

15.1.8 CR SIGLME

Link duration measurement(all30MinSignalingLinkDurationData)

15.1.9

Obligatory link utilization measurement(oblSignalingLinkUtilisationData)

15.1.10

Link utilization measurement(allSignalingLinkUtilisationData)

15.1.11

Link congestion measurement(signalingLinkCongestionData)

15.1.12

Tab. 15.1 Object classes for MTP measurements

144 A50016-D1109-G801-6-7618


15.1.1 Net element measurementFor this measurement object the incoming, outgoing, discarded and transit messagesignaling units (MSUs) are recorded at the network node level by means of the followingcounters.

numInMSUindicates the number of incoming MSUs per network node.

NumLostMSURoutErrindicates the number of discarded MSUs per network node because of routing errors asdefined in ITU-T Rec. Q.752, § 5.5.Discarded MSUs can refer to major SS7-related routing errors and require an MTP routeverification test. They occur because of the following reasons:– Circular routing: the OPC of the incoming MSU is identical to its own special signal-

ing point code.– The incoming MSU contains an unknown user in the service indicator, which may be

due to an incorrect encoding in the respective signaling information octet (SIO) ofthe MSU.

– The incoming MSUs contain an unknown message type.– The incoming MSUs contain an unknown circuit identification code.– The incoming MSUs have an invalid DPC (unknown in its own database of the net-

work node).– Ping-pong effect: the incoming and the outgoing link set are the same for MSU.– The incoming MSUs have an invalid OPC (unknown in the database of the network

node).– The incoming MSU contains an invalid point code. For example, a 14-bit point code

is invalid in a network, which supports 24-bit point codes.– The outgoing MSU is routed to a link, which does not exist in the corresponding da-

tabase.– The MSU arriving from the network contains an invalid SCP. This takes place if an

adjacent STP sends the following message: TFP (transfer prohibited), TFA (transferallowed) or RST (route set test).

– The incoming MSU contains an invalid signaling link code.– The incoming MSU was received from a non-adjacent DPC.

numOutMSUindicates the number of outgoing MSUs per network.

numTransitMSUindicates the number of transit MSUs per network.

mSUsThroughSwitchedOctetsrepresents the sum of all switched through octets counted on a link basis over a com-plete switch.

mSUsOriginatedOctetsrepresents the sum of all originated octets counted on a link basis over a completeswitch.

mSUsTerminatedOctetsrepresents the sum of all terminated octets counted on a link basis over a completeswitch.

nodeIsolationForAnyReasonrepresents the sum of route set failures for each DPC of the complete network node.

A50016-D1109-G801-6-7618 145


Traffic Measurement

nodeIsolationDurationrepresents the sum of durations of route set failures for each DPC of the complete net-work node.

15.1.2 Signaling point utilization measurementFor this measurement object the unavailability data for all signaling points in the network(adjacent DPCs) is recorded as defined in ITU-T Rec. Q.752 by means of the followingcounters.

adjacentInaccessibleDurationindicates the duration during which each adjacent signaling point in the complete net-work was inaccessible (§ 5.2).

adjacentInaccessibleEventsindicates how often each adjacent signaling point was inaccessible; the number of fail-ures applies to all destinations in the complete network (§ 5.1). The counters for failurecauses are described in section 15.1.7.

15.1.3 Obligatory signaling point utilization measurementFor this measurement object the obligatory unavailability data for the signaling point isrecorded as defined in ITU-T Rec. Q.752, § 5.2 by means of the following counter.

adjacentInaccessibleDurationindicates the duration during which each adjacent signaling point in the complete net-work was inaccessible.

15.1.4 Network MSU measurementFor this measurement object the incoming, outgoing and transit MSUs per network arerecorded by means of the following counters.

numInMSUperNetindicates the number of incoming MSUs per network.

numOutMSUperNetindicates the number of outgoing MSUs per network.

numTransitMSUperNetindicates the number of transit MSUs per network.

15.1.5 Signaling point measurementFor this measurement object the number of discarded MSUs as defined in ITU-T Rec.Q.752, § 3.10 is recorded by means of the following counter.

discardedMSUsindicates the number of discarded MSUs per link because of blocking .

15.1.6 Link set duration measurementFor this measurement object the number of availability cases per link set and the un-availability duration per link set are recorded by means of the following counters.

numLinkSetNotAvailindicates how often a link set is unavailable during a measurement time period.

146 A50016-D1109-G801-6-7618


slsUnavailableindicates the time (in s) during a measurement time period the link set was un-available because of local blocking, foreign blocking, local and foreign blockingor failure of the remote processor (according ITU-T Rec. Q.752, § 4.2).The counter is started when the last link of this link set assumes the ‘inactive’mode and is stopped when the link set is active again.

15.1.7 Destination point measurementFor this measurement object the route set failures and their duration per signaling des-tination point as defined in ITU-T Rec. Q.752 are recorded by means of the followingcounters.

dpcIsAdjacentmarks the DPC of the route set as adjacent or non-adjacent (§ 5.1 and 5.2).

routeSetUnavailableindicates the number of route set failures per destination (§ 4.9 and 5.1).Reasons for route set failure:– The last link of a link set fails and there is no alternative route in the relevant set.– The TFP (transfer prohibited) message is received and there is no alternative route

in the relevant set.

routeSetUnavailableDurationindicates per destination the time (in s) during a measurement time period a routeset was unavailable (§ 4.10).The counter is started if layer 3 network control reports an unavailable route setand is stopped if it reports the route set to be available again.

15.1.8 Obligatory link duration measurementFor this measurement object the available obligatory signaling link duration (for narrow-band only) as defined in ITU-T Rec. Q.752 is recorded by means of the followingcounters.

slInServiceDurationindicates the duration (in s) of the link (§ 1.1).This counter is started if the link is in the “active” mode (the link is active and thelink test ran successfully).

slUnavailabilityDurationindicates the time (in s) during a measurement time period a link was unavailablebecause of local blocking, foreign blocking, local and foreign blocking or failureof the remote processor (§ 2.1).The counter is started if the link assumes the ‘inactive’ mode and is stopped if thelink is active again.

inhLinkDurUnavailindicates the time (in s) during a measurement time period that a local link re-mained unavailable because its state was set to “inhibited”.

A50016-D1109-G801-6-7618 147


Traffic Measurement

15.1.9 Link duration measurementFor this measurement object the unavailability duration and the availability duration ofthe signaling link as defined in ITU-T Rec. Q.752 are recorded by means of the followingcounters.

slFailedindicates the time (in s) during a measurement time period that a link stays in the ‘faulty’mode. I.e. no MSUs can be sent via the link because of an error related to MTP level 2,or the SAAL layer is unavailable, or there is a hardware fault (SLT).The counter is started if the link assumes the ‘faulty’ mode and is stopped if the link isactive again.

sIInServiceDurationindicates the duration (in s) during which the link is available (§ 1.1).The counter is started if the link is in the “active” mode (the link is active and the link testran successfully).

slRemoteProcOutageindicates the time (in s) during a measurement time period the signaling link was un-available because the remote processor failed (§ 2.9 and also Q.704, § 3.2.6). The linkis active in this mode, but not tested and MSUs cannot be sent via the link.The counter is started if the link changes to such ‘unavailable’ mode and is stopped ifthe link changes to a mode other than the one described above.

sIUnavailabilityDurationindicates the time (in s) during a measurement time period a link was unavailable be-cause of local blocking, foreign blocking, local and foreign blocking or failure of the re-mote processor.The counter is started if the link assumes the ‘inactive’ mode and is stopped if the link isactive again.

inhLinkDurUnavailindicates the time (in s) during a measurement time period that a local link re-mained unavailable because its state was set to “inhibited”.

15.1.10 Obligatory link utilization measurementFor this measurement object the obligatory signaling link utilization data (for narrowbandonly) as defined in ITU-T Rec. Q.752 are recorded by means of the following counters.

receivedOctetsSIFSIOindicates the number of received signaling information fields+octets (SIF + SIO) per link(§ 3.4).

signUnitsReceivedindicates the number of incoming faulty MSUs per link (§ 1.8) caused by:– checksum error,– signaling information fields+octets (SIF + SIO) exceeding 272 bytes.

transmittedOctetsSIFSIOindicates the number of transmitted signaling information fields+octets (SIF + SIO) perlink (§ 3.1).

discardedMSUsindicates the number of discarded MSUs because of overload (§ 3.10).Message transfer on layer 2 handles the administrative signaling link overload threshold

148 A50016-D1109-G801-6-7618


value. Once the threshold value is reached, MSUs are discarded and the counter will beincremented.

slLocalInhibitedindicates how often a local link was unavailable because its state was set to “inhibited”.This state can also be entered by administration causing the opposite link in the adja-cent network node to be set in a similar state. Both links are then no longer available forsignaling traffic

slRemoteInhibitedindicates how often a link in the adjacent network node was unavailable because itsstate was brought to “inhibited”. This state can also be caused by administration whensetting the local link as inhibited.

slLocalBlockedindicates how often a local link was unavailable because its state was set to “blocked”.

slRemoteBlockedindicates how often a link was unavailable because the state of the opposite link in theadjacent network node was blocked.

15.1.11 Link utilization measurementFor this measurement object signaling link utilization data (for narrowband only) as de-fined in ITU-T Rec. Q.752 are recorded by means of the following counters.

receivedMSUsindicates the number of received MSUs (§ 3.5).

receivedOctetsSIFSIOindicates the number of received signaling information fields+octets (SIF + SIO) (§ 3.4).

retransmittedOctetsindicates the number of retransmitted octets (§ 3.2).

signUnitsReceivedindicates the number of received faulty signaling units (§ 1.8).

transmittedMSUsindicates the number of transmitted MSUs (§ 3.3).

transmittedOctetsSIFSIOindicates the number of transmitted signaling information fields+octets (SIF + SIO); therepeated octets are not counted (§ 3.2).

slLocalInhibitedindicates how often a local link was unavailable because its state was set to “inhibited”.This state can also be entered by administration causing the opposite link in the adja-cent network node to be set in a similar state. Both links are then no longer available forsignaling traffic.

slRemoteInhibitedindicates how often a link in the adjacent network node was unavailable because itsstate was brought to “inhibited”. This state can also be caused by administration whensetting the local link as inhibited.

slLocalBlockedindicates how often a local link was unavailable because its state was set to “blocked”.

A50016-D1109-G801-6-7618 149


Traffic Measurement

slRemoteBlockedindicates how often a link was unavailable because the state of the opposite link in theadjacent network node was blocked.

15.1.12 Link congestion measurementFor this measurement object the overload data of the signaling links as defined in ITU-T Rec. Q.752 are recorded by means of the following counters.

slCongestedDurationindicates the overload duration (in s) of a signaling link (§ 3.7) in a measurement timeperiod; the individual blocking durations are added within a measurement time period.

slCongestedStartsindicates the number of times a link is unavailable during a measurement time period.The measured values are determined by layer 2 message management.

15.2 CCS7-specific Measurement (CCNC)The different measurement types have been implemented in the D900/D1800/D1900system in accordance with ITU-T Rec. Q.752 and Telekom specification 163TR77 asshown in Tab. 15.2. This table also denotes the respective paragraphs of the recom-mendations concerned.


The results of the measurement of CCS7 signaling data are stored on a disk in the CP.Upon retrieving them via a traffic file, some additional information on the outcome of themeasurement is inserted. Each result includes information on the data quality and avail-ability of the measurement, besides some other aspects that may differ from unit to unit.The aspects displayed at the OMT of the network node can differ from those recordedon tape in the OMC.

Measurement data(Q.752) - [163TR77]

Section MML command

Set data for CCS7 routes(§ 4.9, 4.10, 5.1, 5.2) - [§ 5.1, 5.2]

15.2.1 REC C7RSET

Set data for CCS7 links(§ 4.2) - [§ 4.2]

15.2.2 REC C7LSET

Grade of service data for CCS7(§ 1.1, 1.8, 2.1, 2.7, 2.8, 2.9) - [§ 2.7]

15.2.3 REC C7GOS

Load data for CCS7 links(§ 3.1, 3.2, 3.3, 3.4, 3.5, 3.7, 3.10) - [§ 3.2, 3.3, 3.5, 3.7]

15.2.4 REC C7LLOAD

CCS7 MSUs being discarded(§ 5.5)

15.2.5 REC C7DCDMSU

All CCS7 MSUs being received, transmitted, forwarded[§ 6a.1, 6a.2, 6a.3]

15.2.6 REC C7MSU

Tab. 15.2 Measurement for CCS7 signaling data

150 A50016-D1109-G801-6-7618


• Data qualityThe output indicates once per measurement interval (15 minutes) whether data cor-ruption has taken place.

• AvailabilityThe output at the end of the measurement interval indicates whether data for the re-spective object was available.

15.2.1 CCS7 Route Set MeasurementThis mandatory measurement records data on the availability of CCS7 routes per des-tination point code (DPC) or routing area. The CCNC contains route data per DPC andnetwork level. One measurement job can record data on 1024 DPCs (routes) at one net-work level (e.g. NAT0).

The measurement results for more than 16 object object ranges can only be output todisk; output at the OMT is also possible for less object ranges.

The result of this measurement can be used to obtain the:– time intervals (quarter hours, hours etc.) with the greatest duration of unavailability

for the route set of an adjacent or non-adjacent DPC– time intervals with the greatest duration of route set unavailability for a group of ad-

jacent and non-adjacent DPCs– time intervals in which the number of route data failures of an adjacent or non-adja-

cent DPC or group of DPCs was greatest– mean duration of unavailability of the route set for adjacent or non-adjacent DPCs

or DPC groups for each time interval– number of route set failures for an adjacent or non-adjacent DPC or DPC group in

each time interval– sum of durations of route set unavailability for adjacent or non-adjacent DPCs or

DPC groups in each time interval

Identification and adjacent signaling pointsare additional constants being inserted when the counter results are retrieved via a traf-fic file in order to allow the measured data to be allocated.

1/ SECURE data has not been corrupted2/ TIME_CORR system time has been corrected during interval3/ NO_INIT insecure data; counter initialization has failed due to

e.g. recovery or CP overload4/ INCOMPL measurement results are incomplete5/ OVERLOAD system was overloaded6/ NO HEAP heap was not available

<========> displayed after each line at the OMT<============> added to each record on tape

1/ SECURE data is secure2/ DEL data has been deleted during interval3/ NO DATA data has not been received4/ INSECURE data has been corrupted

<=======> displayed after each line at the OMT<===========> added to each record on tape

A50016-D1109-G801-6-7618 151


Traffic Measurement

– The object can be selected with either the name of the routing area (RANAM), orboth a DPC (0 to 16383) and a network indicator (NAT0 - NAT1 - INAT0 - INAT1).

– A value indicates the kind of DPC (0 = default, 1 = adjacent, 2 = non-adjacent).

UNAVAILABLE ROUTE SETindicates the number of route set failures.

DURATION UNAVAILABLE ROUTE SETindicates the sum of the durations in seconds of route set failures.

15.2.2 CCS7 Link Set MeasurementThis measurement records the number of unavailable signaling link sets and the dura-tion of unavailability of a link set. A link set is considered to be unavailable when the lastlink in the set goes into the state “inactive” as a result of:– a signaling link failure,– a signaling link blocked due to network management actions.


The results of this measurement can be used to obtain the:– time intervals (quarter hours, hours etc.) in which the number of out-of-service link

sets was greatest and lowest;– total duration of unavailability of a link set during a defined time interval (quarter

hour, hour etc.)

Link set nameThe name of the link set is an additional constant being inserted when the counter re-sults are retrieved via a traffic file in order to allow the measured data to be allocated.

UNAVAILABLE LINK SETSindicates the number of link sets out of service.

DURATION UNAVAILABLE LINK SETSindicates the duration for which link sets were out of service.

15.2.3 CCS7 Grade of Service MeasurementThis mandatory measurement records the grade of service of a CCS7 signaling link. Alllinks created in a D900/D1800/D1900 network node (max. 0-255) can be measured.


The results of this measurement can be used to obtain the:– time intervals (quarter hour, hour etc.) in which the signaling link was in service with-

out operation– total duration of signaling link unavailability in a defined time interval (quarter hour,

hour etc.)– duration of signaling line unavailability in a defined time interval (quarter hour, hour

etc.) due to a failure (link not available to user traffic), local blocking, remote blocking,both local and remote blocking

– time intervals (quarter hour, hour etc.) with the largest and/or smallest number of er-rored MSUs

– mean duration of blocking per time interval for all blocking types or individual block-ing types.

152 A50016-D1109-G801-6-7618


Index and link identificationsare additional constants being inserted when the counter results are retrieved via a traf-fic file in order to allow the measured data to be allocated.– Index 10 or 11 is used only at the tape interface for data control.– The link set can be selected in the output by a link number (0 to 255), or by the name

of the link set (LSNAM), or by a signaling link code (0 to 15).

DUR LINK IN SERVICEindicates the in-service duration in seconds of a link.

NUM SIG UNIT ERRORindicates the number of errored MSUs.

DUR UNA LINKindicates the duration in seconds of link unavailability. The link is not accessible by usertraffic.

DUR UNA LINK FAILUREindicates the duration in seconds of link unavailability due to failure.

DUR UNA LOCAL BLKindicates the duration in seconds of link unavailability due to local blocking.

DUR UNA REMOTE BLKindicates the duration in seconds of link unavailability due to remote blocking.

DUR UNA BOTH BLKindicates the duration in seconds of link unavailability due to local and remote blocking.

15.2.4 CCS7 Link load MeasurementThis mandatory measurement is activated in the CCNC and records the load on a CCS7signaling link. All links created in a D900/D1800/D1900 network node (max. 0-255) canbe measured.


These measurement results can be used to obtain:– the time of the busy hour for the link or LINK SET;– the traffic intensity in the busy hour for the link or LINK SET.

The results of measurements in the busy hour, or any other defined period can be usedto determine the:– number of information octets (fields included) transmitted in MSUs– number of retransmitted information octets in MSUs– percentage of retransmitted information octets– number of message signal units (MSUs) transmitted– number of information octets (fields included) received in MSUs– ratio of transmitted to received information octets– number of message signal units (MSUs) received– ratio of transmitted to received MSUs– number of MSUs discarded in the SILT due to link overload in the transmit direction– percentage of discarded MSUs in the transmit direction

Index and link identificationsare additional constants being inserted when the counter results are retrieved via a traf-fic file in order to allow the measured data to be allocated.

A50016-D1109-G801-6-7618 153


Traffic Measurement

– The index is used only at the tape interface for data control.– The link set can be selected in the output either by a link number (0 to 255), or by

the name of the link set (LSNAM), or by a signaling link code (0 to 15).

NUM MSU TRANSindicates the number of transmitted MSUs.

NUM SIF/SIO TRANSindicates the number of transmitted information octets + fields in the MSUs.

NUM MSU RECEIVEDindicates the number of received MSUs.

NUM SIF/SIO RECEIVEDindicates the number of received information octets + fields in the MSUs.

NUM OCTETS RETRANSindicates the number of retransmitted octets + fields in the MSUs.

NUM DCD MSU CONGESTindicates the number of MSUs discarded due to overload.

NUM LINK CONGESTIONindicates the number of links out of service due to overload.

DUR LINK CONGESTIONindicates the duration of link congestion.

15.2.5 CCS7 Discarded MSU MeasurementThis mandatory measurement records message signal units (MSUs) discarded in thePU:SIMP, MH:SIMP, and CPI because an implausible destination point code (DPC),originating point code (OPC), circuit identification code (CIC), network indicator (NI), oruser data was included, or due to errors in the routing/distribution tables.

The measurement results can be output to disk or at the OMT.

These measurement results can be used to obtain the:– time interval (quarter hour, hour etc.) in which the number of discarded MSUs was

the greatest ot the smallest;– number of MSUs discarded during a defined interval, e.g. the busy hour of the net-

work node.

TOTALindicates the total number of MSUs discarded due to routing data errors.

PU:SIMPindicates the number of MSUs discarded in the PU:SIMP (processing unit for signalingmanagement processor) due to routing data errors.

MH:SIMPindicates the number of MSUs discarded in the MH:SIMP (message handler for signal-ing management processor) due to routing data errors (discrimination errors).

CPIindicates the number of MSUs discarded in the CPI due to routing data errors (distribu-tion errors).

154 A50016-D1109-G801-6-7618


15.2.6 CCS7 Measurement of all MSUs Received, Transmitted, ForwardedIt records the total number of MSUs received, transmitted and forwarded by thePU:SIMP, MH:SIMP, and CPI in the CCNC.

The measurement results can be output to disk or at the OMT.

These measurement results can be used to obtain:– the time interval (quarter hour, hour etc.) in which the number of received, transmit-

ted and forwarded MSUs was greatest or smallest;– the number of MSUs received, transmitted and forwarded during a defined interval,

e.g. the exchange busy hour.

INCOMING_MESSAGE_SIGNAL_UNITSindicates the number of MSUs received by the signaling point (including those discard-ed).

OUTGOING_MESSAGE_SIGNAL_UNITSindicates the number of MSUs transmitted by the signaling point (including those dis-carded).

TRANSIT_MESSGE_SIGNAL_UNITSindicates the number of received and transmitted MSUs where the destination or originwas another signaling point. This includes the number of (discarded) MSUs which werenot forwarded, i.e., were received but not transmitted.

15.2.7 Measuring Statistics Data at SSP/SCP InterfaceCommand REC INSTAT activates the recording of the statistics events at the SSP/SCPinterface in the intelligent network (IN). Both the service switching point (SSP) and theservice control point (SCP) are IN system units and communicate via a CCS7 link.– The main functions of the SSP are the inclusion of the IN in the basic network, de-

tection of IN service requests, and the through connection of IN connections.– The SCP contains the appropriate data for controlling the services.

The IN statistics counters register the dialog traffic, overload controller events, and theerror frequency at the SSP/SCP interface enabling to diagnose its quality by means ofthe evaluated data from the counters.

The operator can start a maximum of two measurement jobs simultaneously at theOMT.

ATTEMPTED_DIALOG_INITIATIONSindicates the number of attempts by the SSP to open a dialog. The counter is increment-ed at the start of an attempt to set up a dialog.

BLOCKED_DIALOGSindicates the number of unsuccessful attempts to open a dialog. The dialog cannot beopened for internal SSP reasons.

PROCESSED_DIALOGS_(OVERALL)indicates the overall number of processed dialogs.

PROCESSED_DIALOGS_(SCF_INI)indicates the number of processed dialogs initiated by the service control function.

ERROR/REJECTION_MESSAGE_FROM_SSPindicates the number of error or rejection messages which were sent by the SSP.

A50016-D1109-G801-6-7618 155


Traffic Measurement

MESSG_FROM_TCAP_NOT_ACCEPTEDindicates the number of unsuccessful dialog attempts because the message was not ac-cepted by the TCAP.

TIME_FOR_ANSWER_EXPIREDindicates the number of unsuccessful dialog initiations due to time-out.

ABORTED_BY_SCP_OR_REMOTE_TCAPindicates the number of unsuccessful dialog attempts aborted by the SCP or the remoteTCAP.

LOCAL_ABORT_BY_SSPindicates the number of unsuccessful dialog attempts aborted locally by the SSP.

ERROR/REJECTION_MESSAGE_FROM_SCPindicates the number of error or rejection messages which were sent by the SCP.

15.3 SCCP Measurement

SCCP functions

The signaling connection control part (SCCP) is a user part of signaling system no.7(SS7). The SCCP is used to expand the MTP function and to determine signaling infor-mation without reference to the user channel, i.e., information transfer takes place at thelogical level. The routing label consists of the OPC (originating point code), DPC (desti-nation point code), and SLS (signaling link selection).A logical (virtual) signaling connection (transaction) between two network nodes alwaysuses packet switching. Although no user channels are seized, the partners in the con-nection occupy physical and logical resources.

The SCCP recognizes various options for transaction control.– If the SCCP has only a bearer function and the transactions are controlled by the

transaction capabilities application part (TCAP), this means that these are connec-tionless services. Connectionless means that users in different exchanges can ex-change data with each other without having to establish a connection referencebeforehand. The messages do not contain a call reference parameter.

– If the SCCP is controlling the transactions itself this means that these are connec-tion-oriented services. Connection-oriented means that a virtual signaling connec-tion is first established between the services (users) involved. It corresponds to anend-to-end connection. The users determine the setup and cleardown of the con-nection. The messages are given a call reference parameter with which they can beassigned to a specific virtual connection.

Connectionless and connection-oriented services are differentiated by the individual ac-tivities of SCCP. A more precise subdivision of the individual uses or of the functionalscope is achieved by introducing four protocol classes (0,...,3), as defined by ITU-T.• Protocol classes 0 and 1 include the connectionless services and use four SCCP

messages:– “Unitdata” (UDT) and “Extended Unitdata” (XUDT) are used for connectionless

transmission of an entire information unit.– “Unitdata Service” (UDTS) and “Extended Unitdata Service” (XUDTS) are used

to return an information unit which cannot be assigned to the sender. They includeinformation about why the information unit has been returned.

• Protocol classes 2 and 3 include the connection-oriented services.Protocol class 2 uses the SCCP messages

156 A50016-D1109-G801-6-7618


– “Connect Request” (CR),– “Connect Confirm” (CC),– “Connect Refused” (CREF),– “Data Form 1” (DT1),– “Released” (RLSD),– “Release Complete” (RLC).Protocol class 3 uses further messages, such as:– “Data Form 2” (DT2),– “Data Acknowledgement” (AK),– “Reset Request” (RSR),– ”Reset Confirm” (RSC).

The SCCP transaction is set up by the initiating side using CR to notify the distant end.If the signaling connection cannot be setup for any reason then CREF is returned. Ifthere is a positive response (the distant end receives CR), CC is returned. This meansthat the two ends know about each other and the SCCP transaction is set up. While theSCCP transaction is in place, the two sides can exchange user information units withDT1. If one of the two partners wishes to release the SCCP transaction, he sends RLSDto the distant end, which then responds with RLC. User information units can also beexchanged during transaction setup (in CR and/or CC) and even during transactioncleardown (in RLSD).

15.3.1 SCCP Counters with SSNCThe SCCP measurement registers SCCP events being exchanged between networknodes in D900/D1800 during normal system operation. Therefore, a number of countersfor collecting information about capacity utilization and network resources availabilityare implemented. SCCP performance can be examined on the basis of the data ob-tained as defined in ITU-T Recommendation Q.752. As for MTP measurements, the op-erator can start an SCCP measurement job in the node via a Q3 task (see Tab. 15.3).The measurement results with counter values are emitted as report notifications. Thecounters, whose values are reported, are described further on in this chapter in thesame order as they appear in the report notification.

15.3.1.1 SCCP error performance measurementFor this measurement object the errors in the signaling traffic such as routing errors,overload situations or errors because of the unavailability of certain components are re-


Section Q3 command

SCCP error performance(sccpErrorPerformance)

15.3.1.1 CR SPME

SCCP utilization(sccpUtilisation)

15.3.1.2

SCCP quality of service(sccpQualityOfService)

15.3.1.3

Tab. 15.3 Object classes for SCCP measurements

A50016-D1109-G801-6-7618 157


Traffic Measurement

corded by means of the following counters. In order to uniquely define the correct mes-sage, please refer to the appropriate event mentioned in Table 7 of ITU-T Rec. Q.752.

segmentationNotSupportedindicates the number of segmentation errors because segmentation is not supported(Event 19).

providerInitiatedReleaseindicates how often a provider initiated release of an external connection (Event 18)takes place because:– an inactivity timer cannot be set,– internal resources are unavailable,– there is an audit error,– there is a backup error.

tiarExpiryindicates the number of errors during the inactivity check because– the inactivity receive timer expires,– the data in the received inactivity timer (IT) message does not correspond to the lo-

cally stored data.

(Event 16 for external messages)

noReassemblyResourcesindicates the number of reassembly errors because of a lack of resources for reassem-bly (Event 12).

reassemblyTimerExpiredindicates how often the timer for segmentation feedback expired in the case of externalXUDT and DT1 messages (Event 10).

unknownDestinationAddressindicates how often the destination address was unknown as defined in ITU-T Rec.Q.714, § 3.2.

providerInitiatedResetindicates how often a connection is reset by the provider (Event 17).

violationOfHopCounterindicates the number of hop counter violations by external XUDT and XUDTS messages(Event 13).

messageTooLargeindicates how often the message is too large for segmentation (Event 14).

subsystem Congestionindicates the number of routing errors because of an SCCP subsystem blocking (Event6).

failReleaseCompleteindicates how often the RLS monitoring has failed. This means that the interval timer ex-pires without having received an RLS (Event 15 for external messages).

noPointCodeAvailableindicates the number of routing errors because the SPC was unavailable after identifi-cation by the SPC status check (Event 3).

noTranslForSpecificAddressindicates the number of routing errors because no translation has taken place for this

158 A50016-D1109-G801-6-7618


specific address (Event 2). The global title translation failed because there was no trans-lation for the specified global title digits.

networkCongestionindicates the number of routing errors because the SPC was overloaded after identifica-tion by the SPC status check (Event 4).

subsystemFailureindicates the number of routing errors because the subsystem was unavailable (Event5). Therefore, the subsystem cannot send the external messages (CR, UDT, XUDT,UDTS or XUDTS).

userUnequippedindicates the number of routing errors because the subsystem was not provided in ad-vance (Event 7). Because the subsystem has not been created, the external messages(CR, UDT, XUDT, UDTS or XUDTS) cannot be sent.

sccpSyntaxErrorListindicates how often syntax errors are identified in incoming external messages (Event8).

unknownOrUnqualifiedRoutingFailureindicates the number of unknown routing errors as defined by ITU-T Rec. Q.714, § 3.2.

segmentReceivedOutOfSequenceindicates the number of reassembly errors because the received segment was not in se-quence (this also includes duplicates and receipt of other segments than first one forwhich no reassembly process is available) (Event 11).

noTranslForNatureAddressindicates the number of routing errors because unknown address types prevent addresstranslation (Event 1).

segmentationFailedindicates the number of Segmentation error - Segmentation failed occurrences(Event20).

15.3.1.2 SCCP utilization measurementFor this measurement object SCCP utilization data is recorded by means of the follow-ing counters. In order to uniquely define the correct message, please refer to the appro-priate event mentioned in Table 9 of ITU-T Rec. Q.752.

messagesHandledindicates how often all external messages from both local and remote systems are pro-cessed (Event 3). This concerns all incoming and outgoing external SCCP messages.

messagesRequiringGTTranslationindicates the number of all messages requiring global title translation (Event 5). Thenumber of messages depends on whether or not the global title could be translated.

messagesForLocalSubsystemsindicates the total number of all messages intended for local subsystems (Event 4).

numberOfTransitMessagesProcessedindicates the number of processed transit messages as defined in ITU-T Rec Q752.

A50016-D1109-G801-6-7618 159


Traffic Measurement

15.3.1.3 SCCP quality of service measurementFor this measurement object the quality of service data on the network layer is recordedby means of the following counters. In order to uniquely define the correct message,please refer to the appropriate events mentioned in Table 9bis of ITU-T Rec. Q.752.

errMessagesReceivedindicates the number of PROTOCOL DATA UNIT ERROR messages being receivedfrom the MTP (Event 2).

xudtsMessagesSentindicates the number of outgoing external XUDTS messages being sent (Event 14).

udtsMessagesReceivedindicates the number of UDTS messages being received (Event 4).

udtMessagesReceivedindicates the number of UDT messages being received (Event 3).

crMessagesReceivedindicates the number of CR messages being received from the MTP as well as ISDN-UP embedded CR messages (Event 7).

crMessagesSentindicates the number of CR messages being sent to the MTP as well as ISDN-UP em-bedded CR messages (Event 5); i.e. all outgoing external CR messages.

xudtMessagesReceivedindicates the number of XUDT messages (including the messages with syntax/protocoland addressing errors) being received (Event 15).

crefMessagesReceivedindicates the number of CREF messages being received from the MTP (Event 8).

udtMessagesSentindicates the number of UDT messages being sent (Event 1).

xudtsMessagesReceivedindicates the number of XUDTS messages (including the messages with syntax/proto-col and addressing errors) being received (Event 16).

errMessagesSentindicates the number of outgoing external PROTOCOL DATA UNIT ERROR messagesbeing sent (Event 11).

crefMessagesSentindicates the number of CREF messages being sent (Event 6).

xudtMessagesSentindicates the number of outgoing external XUDT messages being sent (Event 13).

udtsMessagesSentindicates the number of UDTS messages being sent (Event 2).

ludtsMessagesReceivedindicates the number of long UNITDATA SERVICE message received (Event 20).

ludtsMessageSentindicates the number of long UNITDATA SERVICE message sent (Event 18).

ludtMessageSentindicates the number of ng UNITDATA message sent (Event 17).

160 A50016-D1109-G801-6-7618


ludtMessagesReceivedindicates the number of long UNITDATA message received (Event 16).

15.3.2 SCCP Counters with CCNCThe SCCP measurement registers SCCP events being exchanged between networknodes in D900/D1800 during normal system operation. Therefore, a number of countersfor collecting information about capacity utilization and network resources availabilityare implemented. SCCP performance can be examined on the basis of the data ob-tained as defined in ITU-T Recommendation Q.752.

15.3.2.1 SCCP utilization measurementThe measurement of SCCP utilization data is supported by the following counters. In or-der to uniquely define the correct SCCP message, reference is made to the appropriateevent mentioned in Table 9 of ITU-T Rec. Q.752.

SCTINTMH INTERNAL MESS. HANDLEDindicates the total number of internal messages received from each LTG or CP, exceptfor CP short circuit messages.

SCTIMLSS INTERNAL MESSAGE F. LOCAL SSindicates the total number of internal SCCP messages received from a local subsystem(CP or LTG), regardless of whether processed successfully or not, except for CP shortcircuit messages.

SCTEXTMH EXTERNAL MESS. HANDLEDindicates the total number of externally handled SCCP messages from local or remotesystems (Event 3).

SCUDTMR1 UNIDATA CL 1 MESS. F. SS RECV.indicates how often UDT/XUDT messages (transfer messages between CCNC and CPexcluded) have been received in sequence (Event 7).

SCDT1MRC DT1 MESS. F. SS RECEIVED.indicates how often incoming external DATA1 (DT1) messages are received by the sub-system (Event 9).

SCDT1MSE DT1- MESS. F.SS SENTindicates how often outgoing external DATA1 (DT1) messages are sent by the sub-system (Event 10).

SCDT2MRC DT2- MESS. F. SS RECEIVEDindicates how often incoming external DATA2 (DT2) messages are received by the sub-system (Event 11).

SCDT2MSE DT2- MESS. SENT BY SSindicates all outgoing external DATA2 (DT2) messages sent by the subsystem (Event12).

SCSHORTM SHORTCIRCUIT MESSAGEindicates how often the CP has processed short circuit messages; such message con-sists of an event pair (Request/Indication) indicating an SCCP short circuit event.

SCSHORTM MLD F. GLOBAL TITLE TRANSL.indicates the total number of global title translations (Event 5).

A50016-D1109-G801-6-7618 161


Traffic Measurement

SCMSBUSS MESS. SENT TO SAFEG. SUBSYSTEM.indicates all external messages sent to the safeguarding system of a subsystem servicegroup (Event 8).

SCTEMLSS EXTERNAL MESS. F. LOCAL SSindicates how often the CCNC has received an external SCCP message that was in-tended for the CP or an LTG, regardless of whether processing was successful or not(Event 4).

SCUDTMS0 UNITDATA CL 0 MESS. F. SS SENTindicates how often UDT/XUDTclass 0 messages (transfer messages between CCNCand CP excluded) have been sent out of sequence (Event 6).

SCUDTMS1 UNIDATA CL 1 MESS. F. SS SENTindicates how often UDT/XUDT class 1 messages (transfer messages between CCNCand CP excluded) have been received out of sequence (Event 6).

SCUDTMR0 UNITDATA CL 0 MESS. F. SS RECV.indicates how often UDT/XUDT messages (transfer messages between CCNC and CPexcluded) have been received out of sequence (Event 7).

15.3.2.2 SCCP quality of service measurementThe measurement of SCCP quality of service data is supported by the followingcounters. In order to uniquely define the correct SCCP message, reference is made tothe appropriate event mentioned in Table 9bis of ITU-T Rec. Q.752.

SCUDTMSE UNITDATA- MESS. SENTindicates the number of UTD messages (including the relayed ones from CCNC or LTG)being sent (Event 1).

SCUDTSSE UNITDATA SERV.- MESS. SENTindicates the number of UDTS messages (including the relayed ones from CCNC orLTG) being sent (Event 2).

SCUDTMRC UNITDATA- MESS. RECEIVEDindicates the number of UTD messages (including the ones with syntax, protocol andaddressing errrors) being received from the CCNC (Event 3).

SCUDTSRC UNITDATA SERV.- MESS. RECEIVEDindicates the number of UDTS messages (including the ones with syntax, protocol andaddressing errors) being received from the CCNC (Event 4).

SCCRMSSE CR MESSAGE SENTindicates the CR messages (including the relayed ones from CCNC and LTG) beingsent to the MTP (Event 5).

SCCREFMS CREF MESSAGE SENTindicates all outgoing external CREF messages sent to the MTP (Event 6).

SCCRMSRC CR MESSAGE RECEIVEDindicates the CR messages received (Event 7).

SCCREFMR CREF MESSAGE RECEIVEDindicates all external CREF messages received by the CCNC (Event 8).

SCRSRMSE RSR MESSAGE SENTindicates all RSR messages sent by the SCCP to the MTP (Event 9).

SCRSRMRC RSR MESSAGE RECEIVEDindicates all RSR messages received from the CCNC (Event 10).

162 A50016-D1109-G801-6-7618


SCERRMSE ERROR MESSAGE SENTindicates all PROTOCOL-DATA-UNIT-ERROR messages sent to the CCNC (Event 11).

SCERRMRC ERROR MESSAGE RECEIVEDindicates all PROTOCOL-DATA-UNIT-ERROR messages received by the CCNC(Event 12).

SCXUTMSE XUNIT DATA- MESS. SENTindicates the XUDT messages (including the relayed ones from CCNC and LTG) beingsent (Event 13).

SCXUSMSE XUNIT DATA SERV. MESS. SENTindicates the XUDTS messages (including the relayed ones from CCNC and LTG) beingsent (Event 14).

SCXUTMRC XUNIT DATA- MESS. RECEIVEDindicates the XUDT messages (including the relayed ones from CCNC and LTG) beingreceived by the CCNC (Event 15).

SCXUSMRC XUNIT DATA SERV.- MESS. RECV.indicates the XUDTS messages (including the relayed ones from CCNC and LTG) beingreceived by the CCNC (Event 16).

15.3.2.3 SCCP error performance measurementThe measurement of SCCP error performance data is supported by the followingcounters. In order to uniquely define the correct SCCP message, reference is made tothe appropriate event mentioned in Table 7 of ITU-T Rec. Q.752.

SCTIMSER INTERNAL MESSAGE ERRORindicates the total number of internal messages that cannot be forwarded to a sub-system due to:– a failure in internal messages to/from LTG/CP or within the CP;– a routing error in short circuit messages within the CP.

SCSSUNAV SUBSYSTEM NOT AVAILABLEindicates the number of external messages (CR, UDT, XUDT, UDTS or XUDTS) thatcannot be sent since the subsystem is not available (Event 5).

SCSSNEQD SUBSYSTEM NOT EQUIPPEDindicates the number of external messages (CR, UDT, XUDT, UDTS or XUDTS) thatcannot be sent since the subsystem is not created (Event 7).

SCSYNERR SYNTAX ERRORindicates syntax error detected in incoming external messages (Event 8).

SCRFRUNK UNKNOWN ROUTING ERRORindicates routing error for which the reason is unknown (Event 9).

SCRETITO REASSEMBLY TIMER. REDindicates how often timer for segment reassembly expired (for external XUDT and DT1messages).

SCINCOFA ERROR INACTIVITY CHECKindicates error on inactivity check with external messages because the inactivity receivetimer expires or the data in the received inactivity timer (IT) message does not corre-spond to the local stored data.

SCRLCSFA FAILURE OF RLS CMPL-SUPERVISIONindicates how often the interval timer has expired without receiving the RLC message.

A50016-D1109-G801-6-7618 163


Traffic Measurement

SCUDESAD UNKNOWN DEST ADDRESSindicates how often a destination address was unknown for external messages to an un-known remote SPC or for an incoming CREF message with ”destination address un-known”.

SCPICORL CONN RELS BY PROVIDERindicates how often the provider has released the external connection because of a fail-ure to set up the inactivity timer, a lack of internal resources, or errors during audit orsafeguarding.

SCOLDPBB DATA F. BLUEB.CL- MESS.TOO LONGindicates that the data length for external SCCP message acc. to the Blue Book hasbeen exceeded; the data does not fit in a single UDT message in one network, in whichCL segmentation/re-assembly is not possible.

SCNTRASN NO TRANSLAT. ADDRESS NATUREindicates how often global title translation fails since no translation is available for thespecified address nature (Event 1).

SCNTRSPA NO TRANSLATION-SPECIF. ADDRESSindicates how often global title translation fails since no translation available for thespecified global title digits (Event 2).

SCSPCUNA SPC NOT AVAILABLEindicates unavailable signaling point code detected by SPC status check (Event 3).

SCSPCCON SPC OVERLOADEDindicates overloaded signaling point code detected by SPC status check (Event 4).

SCHOPCVI HOP COUNTER OVERFLOWindicates that hop counter of a received CR, XUDT or XUDTS message, which is to beforwarded, reaches the zero value after global title translation.

15.4 TCAP Measurement

TCAP functions

The transaction capabilities application part (TCAP) controls and provides the connec-tionless edge-to-edge exchange of information between users. It contains general user-neutral procedures which can be used to allow simple setup, sending, reception, andanalysis of information units for bidirectional communication. TCAP extends the connec-tionless services from the SCCP and the MTP for the transport of an information unit byenveloping it in UDT or XUDT.

The TCAP has the tasks of transaction control (setup and cleardown of signaling con-nections and, also, identifying such connections) and operational control over a giventransaction. It therefore consists of two parts, the transaction part and the componentpart.

The transaction part has five message types:– “Unidirectional” for transmission of components without a transaction– “Begin” to set up a transaction– “End” for regular cleardown of a transaction– “Continue” for component transmission over a regular transaction– “Abort” to abort a transaction because of irregularities which have occurred.

A transaction between nodes A and B is set up as follows.– A sends “Begin” to B, thereby transferring its transaction identity.

164 A50016-D1109-G801-6-7618


– B can answer by “Continue” thereby transferring its transaction identity as well.– From this point on, both sides can exchange “Continue” messages in any order.– The transaction is cleared down by one of the two ends sending “End” or “Abort”. No

answer is given.

For the shortest possible transaction, A sends “Begin” and B immediately clears downthe transaction again with “End” or “Abort”.


Traffic measurement regarding TCAP is started using MML command REC SCTC, tak-ing into account that:– only one measurement job of this type can be started;– a measurement in progress is stopped by the specified interval time (parameter IV);– the measurement process is stopped by specifying the end date;– the measurement data is called every 15 minutes, output periodically on an output

device and optionally stored in individual or day files.

The operating personnel can use the MML command CAN JOB to cancel the processand GET TRAFILE to display the contents of the disk file at the OMT.

TCAP counters

In order to uniquely define the correct TCAP message, reference is made to the appro-priate event mentioned in Table 13 of ITU-T Recommendation Q.752.

.

TCUMSGSB BEGIN - MESSAGE SENTindicates the number of “Begin” messages sent (Event 1).

TCUMSGSC CONTINUE MESSAGE SENTindicates the number of “Continue” messages sent (Event 1).

TCUMSGSE END MESSAGE SENTindicates the number of “End” messages sent (Event 1).

TCUMSGSA ABORT MESSAGE SENTindicates the number of “Abort” messages sent (Event 1).

TCUMSGSU UNIDIRECTIONAL MESS. SENTindicates the number of “Unidirectional” messages sent (Event 1).

TCUMSGRB BEGIN MESSAGE RECEIVEDindicates the number of “Begin” messages received (Event 2).

TCUMSGRC CONTINUE MESS. RECEIVEDindicates the number of “Continue” messages received (Event 2).

TCUMSGRE END MESSAGE RECEIVEDindicates the number of “End” messages received (Event 2).

TCUMSGRA ABORT MESSAGE RECEIVEDindicates the number of “Abort” messages received (Event 2).

TCUMSGRU UNIDIRECTIONAL MESS. RECEIVEDindicates the number of “Unidirectional” messages received (Event 2).

TCUCMPSN COMPONENTS SENTindicates the number of components sent over the node (Event 3).

TCUCMPRN COMPONENTS RECEIVEDindicates the number of components received over the node (Event 4).

A50016-D1109-G801-6-7618 165


Traffic Measurement

TCUSCSRB SHORT CIRCUIT BEGIN MESS.indicates the number of interactions with “Begin” messages due to a TCAP short circuitevent between 2 network units being assigned to each other or integrated into the samesignaling point.

TCUSCSRC SHORT CIRCUIT CONTINUE MESS.indicates the number of interactions with “Continue” messages due to a TCAP short cir-cuit event between 2 network units being assigned to each other or integrated into thesame signaling point.

TCUSCSRE SHORT CIRCUIT END MESS.indicates the number of interactions with “End” messages due to a TCAP short circuitevent between 2 network units being assigned to each other or integrated into the samesignaling point.

TCUSCSRA SHORT CIRCUIT ABORT MESS.indicates the number of interactions with “Abort” messages due to a TCAP short circuitevent between 2 network units being assigned to each other or integrated into the samesignaling point.

TCUSCSRU SHORT-CIRCUIT UNIDIRECTIONALindicates the number of interactions with “Unidirectional” messages due to a TCAP shortcircuit event between 2 network units being assigned to each other or integrated into thesame signaling point.

166 A50016-D1109-G801-6-7618


16 Mobile-Specific Traffic SupervisionThe counter functions allow the PLMN operator to monitor certain mobile-specific trafficcounters or counter calculations (counter ratios, sum or differences of counters, etc...),indicating the success rate of certain mobile-specific functions in the network elements.The mobile-specific traffic counters used within the counter functions are mentioned inthe preceding chapters.

Activating the monitoring feature implies that the system will calculate the counter mea-surements and compare them with operator defined threshold values. Should thesethreshold values be exceeded, alarms will be generated. In this way, the operator willreceive on-line information about the quality of service and the current load condition atany time.

Mobile-specific traffic monitoring can be performed in two different ways:– monitoring by the switching subsystem: MSC/VLR, HLR/AC, EIR.– monitoring by the OMC.

Monitoring by the switching subsystem

Counter functions can be monitored by the network elements themselves. Every 15 min-utes, the monitoring function compares the counter functions with the predefined thresh-olds. When a threshold is exceeded, the operator will be informed at the OMT and byan audible/visible alarm on the system panel (SYP).

The PLMN operator can activate the mobile user monitoring for 1 specific counter func-tion using MML command ACT MUSMON; up to 38 counter functions can be activatedin parallel. Deactivating via DACT MUSMON can be done for a single counter functionor for all monitoring jobs currently active. Prior to activation, the PLMN operator has toassociate to each control function at least 1 out of 3 threshold ranges indicating a sever-ity level:– a minor level– a major level– a critical level.

Each level is defined by a pair of threshold values:– a lower value at which an alarm will be generated– an upper value at which the alarm will be cleared

A threshold range is associated or canceled via ENTR/CAN MUSMON.

All possible traffic counter functions which can be monitored by the PLMN operator areenumerated in Tab. 16.1 further on. It gives the network node to which the proper func-tion applies as well as the formulas according to which the mounting function has beenimplemented.

A50016-D1109-G801-6-7618 167


Traffic Measurement

HOTRFS =

MSC/VLR

100 % x

Handover traffic flow structure success rate (per cell)HO_OLD_CELL--------------------------------------------------------HANDOVER_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCA

MOCSETUP=

MSC/VLR

100 % x

MOC setup rateGEN_TRAFF_CHAN_REQ for MORTR-------------------------------------------------------------CALL_ATTEMPTS for MORTR– CALL_END_CALL_FORW for MORTR

MOCANSW =

MSC/VLR

100% x

MOC answer rateSPEECH_CALLS_WITH_ANSWER for MOUT PLMN+ SPEECH_CALLS_WITH_ANSWER for MOUT NOT PLMN+ DATA_CDA_ANA_WITH ANSWER for MOUT PLMN+ DATA_CDA_ANA_WITH ANSWER for MOUT NOT PLMN+ DATA_CDA_DIG_WITH ANSWER for MOUT PLMN+ DATA_CDA_DIG_WITH ANSWER for MOUT NOT PLMN+ ALTFAXSP_WITH_ANSWER for MOUT PLMN+ ALTFAXSP_WITH_ANSWER for MOUT NOT PLMN+ FAX3_WITH_ANSWER for MOUT PLMN+ FAX3_WITH_ANSWER for MOUT NOT PLMN+ DED_PAD_WITH_ANSWER for MOUT NOT PLMN+ DATACDS_ANA_WITH_ANSWER for MOUT PLMN+ DATACDS_ANA_WITH_ANSWER for MOUT NOT PLMN+ DATACDS_DIG_WITH_ANSWER for MOUT PLMN+ DATACDS_DIG_WITH_ANSWER for MOUT NOT PLMN+ ALT_SPEECH_DATA_ANSWER for MOUT PLMN+ ALT_SPEECH_DATA_ANSWER for MOUT NOT PLMN+ BS_REL_WITH_ANSWER for MOUT PLMN+ BS_REL_WITH_ANSWER for MOUT NOT PLMN--------------------------------------------------------------------------------CALL_ATTEMPTS for MORTR– CALL_INT_MS_OWN_MSC for MORTR– CA_MOB_DISPATCH_VGCS_VBS– CA_FIX_DISPATCH_VGCS_VBS

MTCSETUP=

MSC/VLR

100 % x

MTC setup rateGEN_TRAFF_CHAN_REQUEST for MTER-------------------------------------------------------------------RECEIVED_PAGING_RESPONSE for MTER

Tab. 16.1 Traffic counter functions

168 A50016-D1109-G801-6-7618


MTCANSW =

MSC/VLR

100 % x

MTC answer rateSPEECH_CALLS_WITH_ANSWER for MTER+ DATACDA_ANA_WITH_ANSWER for MTER+ DATACDA_DIG_WITH_ANSWER for MTER+ ALTFAXSP_WITH_ANSWER for MTER+ FAX3_WITH_ANSWER for MTER+ DATACDS_ANA_WITH_ANSWER for MTER+ DATACDS_DIG_WITH_ANSWER for MTER+ ALT_SPEECH_DATA_ANSWER for MTER+ BS_REL_WITH_ANSWER for MTER------------------------------------------------------------------------CALL_ATTEMPTS for MTER

EMERSUCC=

MSC/VLR

100 % x

Emergency call success rateTS12_EMERG_CALL_TCH_ALLOC for MORTR----------------------------------------------------------------------------EMERGENCY_TS12_ATTEMPTS for MORTR

EMERANSW=

MSC/VLR

100 % x

Emergency call answer rateTS12_EMERG_WITH_ANSWER-----------------------------------------------------EMERGENCY_TS12_ATTEMPTS

CIPHCTRL =

MSC/VLR

100 % x

Ciphering mode control procedure success rateSUCC_CIPH_MODE_CTRL_PROC--------------------------------------------------------CIPHERING_REQ

HLRINTER =

MSC/VLR

100 % x

HLR interrogation succes rate for interrogation by VLRINTERROG_TO_HLR– INTERROG_UNSUCC_SUBSCR– INTERROG_UNSUCC_SYSTEM-------------------------------------------------------INTERROG_TO_HLR

MOSMSUCC=

MSC/VLR

100 % x

MO SMS success rateSUCC_SMS_OTG--------------------------------------SMS_OTG_ATTEMPTS

MTSMSUCC=

MSC/VLR

100 % x

MT SMS success rateSUCC_SMS_INC------------------------------------SMS_INC_ATTEMPTS

HONOTALO=

MSC/VLR

100 –

Handover not allowedHO_CONFERENCE------------------------------------------------------- x 100 %HANDOVER_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCA– SUBSEQ_MSC_MSC_HO_MSCB

TMSIREAL =

MSC/VLR

100 % x

TMSI reallocation success rateSUCCESSFUL_TMSI_REALLOC---------------------------------------------------–---------ATTEMPTED_TMSI_REALLOCATIONS


A50016-D1109-G801-6-7618 169


Traffic Measurement

INTRAMSC =

MSC/VLR

100 % x

Incoming external intra-MSC handover success rateSUCC_COMPLETED_HO+ SUCC_HO_SEC_MSC_MSC_HO_MSCB---------------------------------------------------------------------HANDOVER_ATTEMPTS– HANDOVER_MSC_MSC_OG_ATTEMPTS– SUBSEQ_MSC_MSC_HO_MSCB

HOFAIL =

MSC/VLR

100 –

Outgoing external intra-MSC handover success rateSUCC_COMPLETED_HO+ SUCC_MSC_MSC_HO_MSCA+ SUCC_HO_SEC_MSC_MSC_HO_MSCB------------------------------------------------------------------- x 100 %HANDOVER_CONFERENCE

INTMSCB =

MSC/VLR

100 % x

Incoming inter-MSC handover success rateSUCC_MSC_MSC_HO_MSCB+ SUCC_SUBSEQ_MSC_MSC_HO_MSCB--------------------------------------------------------------------HANDOVER_MSC_MSC_IC_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCB

INTMSCA =

MSC/VLR

100 % x

Outgoing inter-MSC handover success rateSUCC_MSC_MSC_HO_MSCA------------------------------------------------------------------HANDOVER_MSC_MSC_OG_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCA

SUBMSCA =

MSC/VLR

100 % x

Subsequent inter-MSC handover (MSC-A) success rateSUCC_MSC_MSC_HO_MSCA+ SUCC_DATA_MSC_MSC_HO_MSCA------------------------------------------------------------------HANDOVER_MSC_MSC_OG_ATTEMPTS+ HANDOVER_MSC_MSC_OG_DAT_ATT+ SUBSEQ_MSC_MSC_HO_MSCA

SUBMSCC =

MSC/VLR

100 % x

Subsequent inter-MSC handover (MSC-C) success rateSUCC_SUBSEQ_MSC_MSC_HO_MSCB-----------------------------------------------------------------SUBSEQ_MSC_MSC_HO_MSCB

HOSUCC =

MSC/VLR

100 % x

Unsuccessful external handover rateSUCC_COMPLETED_HO+ SUCC_MSC_MSC_HO_MSCA+ SUCC_MSC_MSC_HO_MSB+ SUCC_SUBSEQ_MSC_MSC_HO_MSCB+ SUCC_HO_SEC_MSC_MSC_HO_MSCB-------------------------------------------------------------------HANDOVER_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCA+ HANDOVER_MSC_MSC_IC_ATTEMPTS


170 A50016-D1109-G801-6-7618


REQAUTH =

HLR/AC

100 % x

Request for authentication set success rateRECVD_SEND_PARAM_AR– UNS_SND_PARAM_AR---------------------------------------------RECVD_SEND_PARAM_AR

INSSUBDA =

HLR/AC

100 % x

Insert subscriber data service success rateSND_INS_SUBDT_MSG_SUB_ADMIN+ SND_INS_SUBDT_MSG+ SENT_INSERT_MS_DATA_AFTER_SCI– UNS_INS_SUBDT_MSG_SUB_ADMIN– UNS_INS_SUBDT_MSG– UNS_RESP_INS_SUBDT_SS------------------------------------------------------------------SND_INS_SUBDT_MSG_SUB_ADMIN+ SND_INS_SUBDT_MSG+ SENT_INSERT_MS_DATA_AFTER_SCI

LUPSUCC

MSC/VLR

100 % x

Location update success rateSUCC_LOCUPD_WITH_IMSI_ATTACH+ SUCC_REQUESTS_LOCUPD--------------------------------------------------------------REQUESTS_LOCUPD

REQSMROU=

HLR/AC

100 % x

Request for SM routing information success rateRECVD_SND_ROUTING_INFO_SM– UNS_ADBLCKD_OR_CALLBARR– UNS_SUBSCRIPTION_ERROR– UNS_GMSC_BEHAVIOUR– UNS_SUB_BEHAVIOUR– UNS_SECONDARY_CAUSES– UNS_LOST_LOCATION– UNS_SMS_OVL----------------------------------------------------------RECVD_SND_ROUTING_INFO_SM

SMDELIV =

MSC/VLR

100 % x

SM delivery status report procedure success rateSMS_INC_ATTEMPTS+ SMS_OTG_ATTEMPTS– UNS_SMS_INC_DELIVERY_FAIL– UNS_SMS_OTG_DELIVERY_FAIL----------------------------------------------------------SMS_INC_ATTEMPTS+ SMS_OTG_ATTEMPTS

SENDAL =

HLR/AC

100 % x

Send alert for SMS success rateSUCC_ALERT_SERVICE_CENTER--------------------------------------------------------SND_ALERT_SERVICE_CENTE

REQMSRN =

HLR/AC

100 % x

Request for SMS success rateRECVD_MSRN------------------------------SND_PROV_MSRN


A50016-D1109-G801-6-7618 171


Traffic Measurement

IDREQVLR=

MSC/VLR

100 % x

Identification requests to PVLR success rateIDENTITY_REQUESTS– IDENT_REQ_CORR_FAILURE– IDENT_REQ_INTW_PVLR_FAILURE– IDENT_REQ_AUTH_FAILURE-------------------------------------------------------------IDENTITY_REQUESTS

PAGEREQ =

MSC/VLR

100 % x

Page request success rateSUCC_PAG------------------------PAG_PROC+ RETRY_PAG

AUTHPROC=

MSC/VLR

100 % x

Authentication procedure success rateAUTH_REQ– AUTH_WITH_ILLEGAL_SUB------------------------------------------------AUTH_REQ

INTRAVLR =

MSC/VLR

100 % x

Intra-VLR location update success rateSUCC_REQUESTS_LOCUPD+SUCC_LOCUPD_WITH_IMSI_ATTACH-LOCUPD_LAI_NULL-LA_CHANGES_AFTER_RECOV-VLR_CHANGES_PVLR_KNOWN-VLR_CHANGES_PVLR_UNKNOWN-----------------------------------------------------------REQUESTS_LOCUPD_INTRA_VLR

INTERVLR =

MSC/VLR

100 % x

Inter-VLR location update success rateVLR_CHANGES_PVLR_KNOWN+VLR_CHANGES_PVLR_UNKNOWN--------------------------------------------------------REQUESTS_LOCUPD_INTER_VLR

UNIMEI =

EIR

100 % x

Unknown IMEI answer rateNO_OF_UNKNOWN_EQUIPMENT------------------------------------------------------NO_OF_IMEI_CHECK_MESSAGE

MOSMS =

MSC/VLR

100 % x

MO SMS forwarding success rateSUCC_SMS_SEND_RP_ACK------------------------------------------------SMS_SER_REQ_ATTEMPTS

MTSMS =

MSC/VLR

100 % x

MT SMS forwarding success rateSUCC_SMS_INC------------------------------------SMS_INC_ATTEMPTS

EMPRESPA=

integrat.

100 % x

Empty response on authentication set request rateRECVD_SEND_PARAM_AR-----------------------------------------------------------EMPTY_RESPONSE_TO_AUTH_SET


172 A50016-D1109-G801-6-7618


Moreover, some particular results can be calculated from the counter values or dis-played at the OMT by means of the respective formules in Tab. 16.2. This table alsostates the MML commands by which traffic data is measured via the respectivecounters.

1. The average time of a call setup can be derived from the duration of each call setupservice divided by the number of call setups.

2. A similar formula applies to the average time of a location updating.

SSRELOP =

HLR/AC

100 % x

SS related operations in HLR success rateRECVD_MSG_REGISTER_SS+ RECVD_MSG_ERASE_SS+ RECVD_MSG_ACT_SS+ RECVD_MSG_DEACT_SS+ RECVD_MSG_INTERROG_SS+ SENT_FORW_CHECK_SS_INDIC+ RECVD_MSG_UNSTRUCTURED_SS_DATA– UNS_RESP_REGISTER_SS_SUB_BEH– UNS_RESP_REGISTER_SS_SYS_BEH– UNS_RESP_ERASE_SS_SUB_BEH– UNS_RESP_ERASE_SS_SYS_BEH– UNS_RESP_ACT_SS_SUB_BEH– UNS_RESP_ACT_SS_SYS_BEH– UNS_RESP_DEACT_SS_SUB_BEH– UNS_RESP_DEACT_SS_SYS_BEH– UNS_RECVD_INTERROG_SS_SUB_BEH– UNS_RECVD_INTERROG_SS_SYS_BEH– UNS_RESP_UNSTRUCTURED_SS_DATA----------------------------------------------------------------------RECVD_MSG_REGISTER_SS+ RECVD_MSG_ERASE_SS+ RECVD_MSG_ACT_SS+ RECVD_MSG_DEACT_SS+ RECVD_MSG_INTERROG_SS+ SENT_FORW_CHECK_SS_INDIC+ RECVD_MSG_UNSTRUCTERED_SS_DATA

ACDCSUCC

MSC/VLR

100 % x

Answered call - dropped call rate (applies to all cells of the MSC)REL_ANSW_CALL_BS_REASON---------------------------------------------------ANSW_ORIG_CALL+ ANSW_INCOM_CALLS+ REL_ANSW_CALL_BS_REASON

CSDCSUCC

MSC/VLR

100 % x

Call setup - dropped call rate (applies to all cells of the MSC)REL_CALL_BS_REASON-----------------------------------------ORIG_CALL_ATTEMPTS+ INCOM_CALL_ATTEMPTS

MSMEMAV

MSC/VLR

100 % x

MS memory available notification success rateSUCCESS_MS_MEMORY_AVAIL--------------------------------------------------MS_MEMORY_AVAIL_TO_HLR


A50016-D1109-G801-6-7618 173


Traffic Measurement

3. A lot of counters for IWE exists from which the mean holding time of a particular IWEcircuit can be derived. E.g. the total time during which an IWE for Fax Gr3 T at a cer-tain rate has been connected, divided by the number of attempts to interconnect thisIWE circuit delivers its mean holding time.

4. The operational load on a GP can be calculated by subtracting the load caused byroutine tests during an interval of 900 seconds.

5. With respect to an announcement group the number of seizures can be displayedon the OMT output.

6. Even the number of accepted seizures can be displayed there.7. Moreover, the normalized traffic (i.e. the capacity rate without taking the specific line

broadcasting into account) can be displayed. It is based on the value of carried traffic(TC) that relies on the count of traffic volume.

8. A plausibility check can be made with the in-service time of a CCS7 signaling linkand its duration of unavailability during the measurement period.

9. The total duration of unavailability of a CCS7 signaling link is composed with 4counter results.

10. The total number of overload messages sent by the MSC can be calculated in post-procesing by taking the number of BSCs into account.

item formula MML

1 average call setup time (s)=

TIME_CALL_SET_U_SERV--------------------------------------------------NUM_CALL_SET_UP_CONTRIB

REC MSC

2 average location updatetime (s) =

TIME_LUP_SERV---------------------------------NUM_LUP_CONTRIB

REC MSC

3 mean IWE holding time (s)=

traffic volume (e.g.TV_IWE_FAX3_TP)------------------------------------------------------------call attempts (e.g. IWE_FAX3_TP)

REC IWE

4 GP load (milliErl) = 1000 –GP_IDR x GP_MEA ( s)-------------------------------------900,000 (ms)

REC LTG

5 TOTAL_CALLS = CC+ CCU_ATB+ CCU_TECHN_IRREGULAR+ CCU_ANGRP_BLOCKED

REC AN-GRP

6 SUCCESSFUL_CALLS = CC– CCS_TECHN_IRREGULAR

REC AN-GRP

Tab. 16.2 Particular calculations with OMT output

174 A50016-D1109-G801-6-7618


7 TC_N (deciErl) =

TC (deciErl) =

TC x 10.000--------------------------------------900 x SEIZE_MAXIMUM

(TV x 4 x 10) + 450------------------------------900

REC AN-GRP

8 plausibility check: 900 s = DUR_LINK_IN_SERVICE+ DUR_UNA_LINK

RECC7GOS

9 DUR_UNA_LINK = DUR_UNA_LINK_FAILURE+ DUR_UNA_LOCAL_BLK+ DUR_UNA_REMOTE_BLK+ DUR_UNA_BOTH_BLK

RECC7GOS

10

total overload messages = (n BSCs) xNUM_SEND_OVERLOAD

REC MSC

item formula MML

Tab. 16.2 Particular calculations with OMT output

A50016-D1109-G801-6-7618 175


Traffic Measurement

Monitoring by the OMC

Although monitoring can be fully supported by the network elements, a customized mon-itoring outside the switching subsystem, i.e., by an OMC, is also provided. The operationand maintenance center can collect traffic measurement data from e.g. severalMSC/VLRs in order to centralize all traffic handling results. Each network element onlyhas to provide the OMC with the data measured by its traffic counters. Therefore thePLMN operator can activate the mobile traffic data collection via ACT MTDRCOL. Thetransfer of the counter results towards the OMC will then be started every 15 minutes.The actual monitoring, the administration of thresholds, and the generation of alarms arecompletely covered by applications in the OMC which are manufacturer-dependent andtherefore not described within this document.

176 A50016-D1109-G801-6-7618


17 AbbreviationsAC authentication center

ASCI Advanced Speech Call Items

ASCI advanced speech call items

ATM asynchronous transfer mode

BAP base processor

BHCA busy hour call attempts

BS bearer service

BSC base station controller

BSS base station system

BSSAP base station system application part

CAMEL Customized Application for Mobile networkEnhanced Logic

CAP call processor

CCBS completion of calls to a busy subscriber

CCNC common channel network control

CCNC common channel signaling network control

CCS7 common channel signaling system no 7

CDA circuit duplex asynchronous

CDMA Code Division Multiple Access

CDS circuit duplex synchronous

CI cell identity

CKSN cipher key sequence number

CLIP calling line identification presentation

CLIR calling line identification restriction

COLP connected line identification presentation

COLR connected line identification restriction

CP coordination processor

CPI coordination processor interface

CUG closed user group

DLU digital line unit

DPC destination point code

DTMF dual tone multifrequency

EIR equipment identity register

eMLLP enhanced multi-level precedence and pre-emption

GCR group call register

GMSC gateway MSC

GP group processor

GPRS General Packet Radio Service

GSM Global System for Mobile communication

A50016-D1109-G801-6-7618 177


Traffic Measurement

GSMSCF GSM service control function

HLR home location register

HPLMN home PLMN

HSCSD high-speed circuit-switched data

IMEI international mobile equipment identity

IMSI international mobile subscriber identity

IN intelligent network

ISDN Integrated Services Digital Network

ITU International Telecommunication Union

IWE interworking equipment

LACOD location area code

LAI location area identity

LNR location routing number

LTG line/trunk group

MAP mobile application part

MICTR mobile incoming traffic

MML man-machine language

MOC mobile originating call

MORTR mobile originating traffic

MOUT_NOT_PLMNmobile originating outgoing traffic to aparty from the PSTN or another PLMN

MOUT_PLMNmobile originating outgoing traffic to a mo-bile party who is subscribed in the homePLMN

MS mobile station

MSC mobile-services switching center

MSISDN mobile subscriber ISDN number

MSRN mobile station roaming number

MSU message signaling unit

MTC mobile terminating call

MTER mobile terminating traffic

MTP message transfer part

MTRAN mobile transit traffic

NP number portability

O&M operation and maintenance

OACSU off-air call setup

ODB operator determined barring

OMC operation and maintenance center

OMP O&M processor

OMT O&M terminal

OPC originating point code

PAD packet assembler/disassembler

178 A50016-D1109-G801-6-7618


PBX private branch exchange

PCM pulse code modulation

PCS Personal Communication System (at 1900MHz)

PLMN Public Land Mobile Network

PSTN Public Switched Telephone Network

PVLR previous VLR

RCF reason for call failure

RCT reason for call termination

SC service center

SCCP signaling connection control part

SCI subscriber controlled input

SCP service control point

SILT signaling link terminal

SLS signaling link selection

SMS short message service

SN switching network

SS supplementary service

SS7 signaling system number 7

SSNC signaling system network control

SSP service switching point

SSS switching subsystem

SW software

TCAP transaction capabilities application part

TCH traffic channel

TMSI temporary mobile subscriber identity

TS teleservice

USSD unstructured SS data

VBS voice broadcasting service

VGCS voice group call service

VLR visitor location register

VMSC visited MSC

A50016-D1109-G801-6-7618 179


Traffic Measurement

18 IndexSymbols*All counters marked with * are explained with call

flows in a separate document . 13*CC:I(O) 122*CCS CCS7 CALL FAIL 126*CCS CONGESTION 124*CCS EXT TECHN IRREG 125*CCS INT TECHN IRREG 124*CCS UNANSWERED 125*CCS_ANSWER:I (O) 123*CCU CCS7 CCNC OLOAD 126*CCU LOST CALLS 125*CCU SUM OFL/LOSS 125*CCU TECHN IRREGULAR 125*CONNECTED LINES 123*HANDOVER_MSC_MSC_IC_ATTEMPTS 48*INCOM_CALL_ATTEMPTS 62*INCOM_CALL_SUCC_TCH_ALLOC 63*NUMBER OF ATB 124*ORIG_CALL_ATTEMPTS 62*ORIG_CALL_SUCC_TCH_ALLOC 62*REL_ANSW_CALL_BS_REASON 63*REL_BEFORE_ACM 35*REL_CALL_BS_REASON 63*SEMI BLOCKED LINES 123*SUBSEQ_MSC_MSC_HO_MSCB 48*SUCC_HO_SEC_MSC_MSC_HO_MSCB 49*SUCC_MSC_MSC_HO_MSCB 49*SUCC_SUBSEQ_MSC_MSC_HO_MSCB 49*TRANS BLOCKED LINES 123*TV:I(O) 123*UNS_BS_REASON 37*UNS_CONGESTION 36*UNS_LACK_IWE 37*UNS_LINK_FAIL 37*UNS_MS_BLOCKED 36*UNS_MS_BUSY 36*UNS_NETW_MANAGEMENT 37*UNS_OVERLOAD 37*UNS_PAGING 35*UNS_PROTO_ERROR 37*UNS_REQ_DEST_ERR 35*UNS_SECURITY_FAIL 37*UNS_SERV_CHECK 36*UNS_SN_CONGESTION 36*UNS_TECHN_FAULT 35

AABORTED_BY_SCP_OR_REMOTE_TCAP 155ACT_SS_TO_HLR 86ACT_TRACEMODE_FROM_HLR 85ACTIVE_QUEUING 29

adjacentInaccessibleDuration 145adjacentInaccessibleEvents 145ADMIN_ACT_TRACEMODE 102ADMIN_DEACT_TRACEMODE 102ALT_SPEECH_DATA_ANSWER 45ALT_SPEECH_DATA_ATTEMPTS 28ALTERN_SPEECH_DATA 94ALTFAXSP_CALL_ATTEMPTS 27ALTFAXSP_WITH_ANSWER 45ANGRP_BLO_TIME 134ANN_ERROR 43ANN_NO_ERROR 42ANSW_INCOM_CALLS 63ANSW_ORIG_CALL 63AOC_CHARGING_LEVEL 96AOC_INFORM_LEVEL 96ASCI_EMLPP 100ASCI_VBS 99ASCI_VGCS 99ATB TIME 124, 137ATB_TIME 135ATTEMPTED_DIALOG_INITIATIONS 154ATTEMPTED_TMSI_REALLOCATIONS 84AUTH_REQ 82AUTH_WITH_ILLEGAL_SUB 83AUTHENTICATION

REQUEST_CKSN_MISMATCH 82

BBLOCKED_CHANNELS 133BLOCKED_DIALOGS 154BLOCKED_SUB_REGISTERED_IN_HLR 92BS_REL_WITH_ANSWER 46BSSAP_PL_DECODING_ERR 88BSSAP_PL_UNKNOWN 88

CCA_COM_PAGING 32CA_COM_PAGING_RETRY 32CA_DATA_FR 31CA_FIX_DISPATCH_VGCS_VBS 54CA_HANDOVER_SDCCH 47CA_HSCSD_2FR 32CA_MOB_DISPATCH_VGCS_VBS 54CA_MOB_SERV_SUB_IN_RMSC 57CA_PTP_EMLPP_0 57CA_SERV_SUB_VBS 54CA_SERV_SUB_VGCS 53CA_SPEECH 31CA_VGCS_VBS_EMLPP_A 57CA_VGCS_VBS_TERM 56CALL_ATTEMPTS 26

180 A50016-D1109-G801-6-7618


CALL_BACK 96CALL_BARR_INC_CALLS 95CALL_BARR_INC_ROAM_OUT_HPLMN 95CALL_BARR_OUTG_CALLS 95CALL_BARR_OUTG_INT_CALL_HPLMN 95CALL_BARR_OUTG_INT_CALLS 95CALL_CCBS 44CALL_END_CALL_FORW 42CALL_FORW_DEF 98CALL_FORW_ON_MS_BUSY 94CALL_FORW_ON_MS_NOT_REACH 95CALL_FORW_ON_NO_REPLY 94CALL_FORW_UNCONDITIONAL 94CALL_GREY_LIST 42CALL_HOLD 97CALL_INT_MS_OWN_MSC 41CALL_LINE_IDENT_PRESENT 95CALL_LINE_IDENT_RESTR 96CALL_REL_A_ALERT 41CALL_REL_ALERT 41CALL_REL_BEF_A_ALERT 41CALL_REL_BEF_ALERT 41CALL_REL_EXCHANGE 41CALL_TCH_ALLOCATION 40CALL_TIOUT_ALERT 42CALL_TRANSFER 43, 97CALL_WAITING 97CALL_WHITE_LIST 42CALL_WITH_UNIDENT_SUB 77CALLS_COMPL_BUSY_SUB 97CALLS_WITH_ANSWER 44CAMEL_PSI 81CAMEL_USSD 99CC 128, 135CC NH ALT1 REROUTING 127CC: NH ALT2: O 127CC: NH DIRECT: O 126CC:I (O) 136CC:I(O) 133CC:NH ALT1: O 127CC_ANSW_VGCS_VBS 55CC_SCI_D_CHANNEL 133CCBS 30CCBS_RECALL 30CCS CCS7 CALL FAIL 128CCS CONGESTION 128CCS EXT TECHN IRREG 129CCS INCMP DIAL 124, 128CCS INT TECHN IRREG 129CCS LINK FAILURE 124, 128CCS NH ALT1 ANSW: O 127CCS NH DIRECT ANSW: O 126CCS OPERATOR RELEASE 129CCS RELORIG ENDTOEND 124, 129CCS SUB BUSY 124, 129

CCS UNALL NUM 124, 129CCS UNANSWERED 129CCS WITH ANSWER 129CCS_ANSWER:I (O) 137CCS_COM_PAGING_RES 33CCS_DISPATCH_RECONN_VGCS_VBS 54CCS_SDCCH_ALLOC 48CCS_TECHN_IRREGULAR 135CCS7 DPC OLOAD 126CCU ALL TRUNKS BUSY 125CCU CCS7 DPC OL ACC 126CCU CCS7 DPC OLOAD 126CCU CONGESTION 129CCU NH ALT1 LOST 127CCU NH ALT2 127CCU NH DIRECT OFL 127CCU NM CODE BLOCKING 129CCU NM TGRP BLOCKING 125, 129CCU TECHN IRREGULAR 130CCU TGRP BLOCKED 125CCU TRUNK RESERVATION 125CCU:INTERNAL 133CCU:O 137CCU:TERMINATING 133CCU_ANGRP_BLOCKED 135CCU_ATB 135CCU_COM_PAGING 33CCU_DATA_FR 39CCU_HSCSD_2FR 39CCU_LACK_CONF_UNIT 55CCU_OVERLOAD_INIT_VGCS_VBS 54CCU_OVERLOAD_SETUP_VGCS_VBS 55CCU_SERV_SUB_BUSY_VGCS_VBS 54CCU_SPEECH 39CCU_TECHN_IRREGULAR 135CHECK_SS_FROM_HLR 86CIPHERING_REQ 82CLOSED_USER_GROUP 97COM_LUP_IMSI_ATTACH_REQ 87COM_LUP_LAI_NULL 87COM_LUP_REQ 87COMPL_INTERROGATIONS 40COMPL_INTERROGATIONS_SC 40COMPL_SCI_CALL_REL 40COMPL_SCI_INDEPENDENT 40CONN_LINE_IDENT_PRESENT 96CONN_LINE_IDENT_RESTR 96CONNECTED CHANNELS 137CONNECTED_CHANNELS 133CONNECTED_LINES 134CPI 153crefMessagesReceived 159crefMessagesSent 159CRM/CRP

ACCEPTED CALLS 132

A50016-D1109-G801-6-7618 181


Traffic Measurement

DELTHR EXCEEDED 132NUMB OF BLOCKED 132NUMB OF CONNECT 132NUMBER OF DELAYS 132SUM DELAYS 132SUMMARY EFFECTS 131TC 131

crMessagesReceived 159crMessagesSent 159

DDATA_CDA 93DATA_CDA_GBS 98DATA_CDS 94DATA_CDS_GBS 98DATACDA_ANA_ATTEMPTS 27DATACDA_ANA_WITH_ANSWER 44DATACDA_DIG_ATTEMPTS 27DATACDA_DIG_WITH_ANSWER 45DATACDS_ANA_ATTEMPTS 28DATACDS_ANA_WITH_ANSWER 45DATACDS_DIG_ATTEMPTS 28DATACDS_DIG_WITH_ANSWER 45DEACT_SS_TO_HLR 86DEACT_TRACEMODE_FROM_HLR 85DED_PAD_ATTEMPTS 28DED_PAD_WITH_ANSWER 45DELETE_FROM_HLR 84DETACH_MSG_TMSI_NO_IMSI_CORR 75discardedMSUs 145, 147DOWNGRADING_NETWORK_INIT 73DOWNGRADING_USER_INIT 73dpcIsAdjacent 146DUR LINK CONGESTION 153DUR LINK IN SERVICE 152DUR UNA BOTH BLK 152DUR UNA LINK 152DUR UNA LINK FAILURE 152DUR UNA LOCAL BLK 152DUR UNA REMOTE BLK 152DUR_ALT_SPEECH_DATA 26DUR_OF_CONV_ALTFAXSP 25DUR_OF_CONV_DATACDA_ANA 25DUR_OF_CONV_DATACDA_DIG 25DUR_OF_CONV_DATACDS_ANA 26DUR_OF_CONV_DATACDS_DIG 26DUR_OF_CONV_DED_PAD 26DUR_OF_CONV_FAX3 25DUR_OF_CONV_SPEECH_SERV 25DUR_OF_CONVERSATION 25DURATION UNAVAILABLE LINK SETS 151DURATION UNAVAILABLE ROUTE SET 151

EEMERGENCY_TS12_ATTEMPTS 28EMPTY_RESPONSE_TO_AUTH_SET 84ENTRY_OP_BARR 75ENTRY_SS_ACT 75ENTRY_USED_DETACH 75ENTRY_USED_FOREIGN 75ENTRY_USED_OWN 75ERA_SS_TO_HLR 86errMessagesReceived 159errMessagesSent 159ERROR/REJECTION_MESSAGE_FROM_SCP 155ERROR/REJECTION_MESSAGE_FROM_SSP 154ESRK_ALLOC_ATT 33EXPLICIT_IMSI_DETACH 76

FFACSIMILE_SERVICES 93failReleaseComplete 157FAX3_CALL_ATTEMPTS 27FAX3_WITH_ANSWER 45FOLLOW_ME 98FRC_IWE_ANACDS_NTP 71FRC_IWE_ANALOG_NTP 70FRC_IWE_ANALOG_TP 69FRC_IWE_DIGCDS_NTP 71FRC_IWE_DIGITAL_NTP 70FRC_IWE_DIGITAL_TP 70FRC_IWE_FAX3_TP 70FRC_IWE_SP_FAX3_TP 74

GGEN_TRAFF_CHAN_REQ 29GP_IDR 132GP_MEA 132

HHANDOVER_ATTEMPTS 46, 65HANDOVER_BETTER_CELL 47HANDOVER_DATA_CALL_ATTEMPTS 47HANDOVER_DIRECTED_RETRY 47HANDOVER_DISTANCE 47HANDOVER_DOWNLINK_QUALITY 47HANDOVER_DOWNLINK_STRENGTH 47HANDOVER_MSC_MSC_OG_ATTEMPTS 48HANDOVER_MSC_MSC_OG_DAT_ATT 48HANDOVER_OP_MAINT_INT 47HANDOVER_RESP_TO_MSC 47HANDOVER_UPLINK_QUALITY 47HANDOVER_UPLINK_STRENGTH 47HO_CONFERENCE 48HO_OLD_CELL 48HO_PERFORMED 48HO_REQUIRED 63

182 A50016-D1109-G801-6-7618


HOT_BILLING 97

IIDENT_REQ_AUTH_FAILURE 82IDENT_REQ_CORR_FAILURE 82IDENT_REQ_INTW_PVLR_FAILURE 82IDENTITY_REQUESTS 82IMEI_CHECKS 30IMPLICIT_IMSI_DETACH 76IN_ATTEMPTS 30IN_ERROR_DEST 39IN_ERROR_SCP 39IN_NO_ANSW_SCP 38IN_OVERLOAD 38IN_REROUTE 42IN_SERV_CHECK 39IN_SERVICE_CLASS_MARK_MOC 97IN_SERVICE_CLASS_MARK_MTC 97IN_TRANS 30INCOM_CALL_ATT_QUEUING 62INCOM_CALL_ATT_TCH_REQ 62INCOM_CALL_QUEUE_TCH_ALLOC 63INCOMING_MESSAGE_SIGNAL_UNITS 154INSERT_FROM_HLR_LOCUPD 84INSERT_FROM_HLR_OCI_SCI 84INTERCELL_HO_INC 64INTERCELL_HO_OUTG 64INTERROG_HANDLED_BY_VLR 86INTERROG_TO_HLR 86INTERROG_UNSUCC_SUBSCR 86INTERROG_UNSUCC_SYSTEM 86INTRACELL_HO_BSC 64INTRACELL_HO_MSC 63INTW_BSS_ILLEGAL_ME 81INTW_BSS_ILLEGAL_SUB 80INTW_BSS_IMSI_UNKNOWN_IN_HLR 80INTW_BSS_LAI_UNKNOWN 81INTW_BSS_LOCAREA_NOT_ALLOWED 80INTW_BSS_NETWORK_FAILURE 80INTW_BSS_OTHER_REASONS 81INTW_BSS_PLMN_NOT_ALLOWED 80INTW_BSS_RADIO_REASONS1 81INTW_BSS_RADIO_REASONS2 81INTW_BSS_SECOND_TRANS_LOCUPD 81INTW_HLR_DEST_OUT_OF_SERVICE 79INTW_HLR_OTHER_REASONS 79INTW_HLR_PROTOCOL_ERRORS 79INTW_HLR_RESTOR_HLR 78INTW_HLR_ROAMING_NOT_ALLOWED 78INTW_HLR_SYSTEM_FAILURE 79INTW_HLR_TCAP_ABORT 79INTW_HLR_TCAP_TIMER_EXPIRY 79INTW_HLR_UNKNOWN_SUB 78INTW_PVLR_DEST_OUT_OF_SERVICE 80INTW_PVLR_OTHER_REASONS 80

INTW_PVLR_PROTOCOL_ERRORS 80INTW_PVLR_TCAP_ABORT 80INTW_PVLR_TCAP_TIMER_EXPIRY 79INTW_PVLR_UNIDENT_SUB 79INVOC_SERV_AOC_CHARGE 59INVOC_SERV_AOC_INFO 59INVOC_SERV_CALL_BACK 59INVOC_SERV_CALL_FORWARD 58INVOC_SERV_CALL_TRANSFER 59INVOC_SERV_CCBS_MORTR 60INVOC_SERV_CCBS_MTER 60INVOC_SERV_CLIP 59INVOC_SERV_CLIR 59INVOC_SERV_MULTIPARTY 59INVOC_SERV_PUT_HOLD 59INVOC_SERV_RETRIEVE_HOLD 59INVOC_SERV_UUS 60INVOKE_SS_BAOC 86INVOKE_SS_BOIC 87IWE_ANACDS_NTP 67IWE_ANALOG_NTP 66IWE_ANALOG_TP 66IWE_DIGCDS_NTP 67IWE_DIGITAL_NTP 67IWE_DIGITAL_TP 67IWE_FAX3_TP 67IWE_SP_FAX3_TP 74

LLA_CHANGES_AFTER_RECOV 77LA_CHANGES_FOREIGN_PLMN 76LA_CHANGES_OWN_PLMN 76LINKED_SUB_REGISTERED_IN_HLR 91LNP_MISROUTED_CALL 23LNP_QUERIES_LRN 23LNP_UNALLOC_NUM_MICTR 23LNP_VACANT_CODE 23LOC_UPD 89LOCAL_ABORT_BY_SSP 155LOCATION_ATTEMPTS 33LOCUPD_LAI_NULL 77ludtMessageSent 159ludtMessagesReceived 160ludtsMessageSent 159ludtsMessagesReceived 159

MmessagesForLocalSubsystems 158messagesHandled 158messagesRequiringGTTranslation 158messageTooLarge 157MESSG_FROM_TCAP_NOT_ACCEPTED 155MH:SIMP 153MORE_THAN_ONE_MSRN_ALLOC 84

A50016-D1109-G801-6-7618 183


Traffic Measurement

MS_MEMORY_AVAIL_TO_HLR 85MSC_MSC_HO_CALL_ATTEMPTS 28MSRN_TIMER_EXPIRES 85MSUB _REGISTERED_GPRS 98MSUB _ROAM_FOREIGN_GPRS_PLMN 99mSUsOriginatedOctets 144mSUsTerminatedOctets 144mSUsThroughSwitchedOctets 144MULTI_PARTY_SERVICE 96

NNATIONAL_FEATURE_1 99networkCongestion 158nhLinkDurUnavail 146, 147NO OF ATB 137NO OF BLO LINES 123NO_OF_AMS 89NO_OF_BLACK_EQUIPMENT 120NO_OF_BLACK_IMEI 119NO_OF_GREY_EQUIPMENT 120NO_OF_GREY_IMEI 119NO_OF_IMEI_CHECK_MESSAGES 119NO_OF_LMU 100NO_OF_MS 89NO_OF_TAC_FAC 119NO_OF_UNKNOWN_EQUIPMENT 120NO_OF_UNSUCC_MESSAGES 119NO_OF_WHITE_EQUIPMENT 120NO_OF_WHITE_IMEI 119nodeIsilationForAnyReason 144nodeIsolationDuration 145noPointCodeAvailable 157noReassemblyResources 157noTranslForNatureAddress 158noTranslForSpecificAddress 157NUM DCD MSU CONGEST 153NUM LINK CONGESTION 153NUM MSU RECEIVED 153NUM MSU TRANS 153NUM OCTETS RETRANS 153NUM SIF/SIO RECEIVED 153NUM SIF/SIO TRANS 153NUM SIG UNIT ERROR 152NUM_ALLOC_GCNR 56NUM_ASCI_CALL_SETUP_RECVD_RMSC 56NUM_ASCI_CALL_SETUP_TO_RMSC 56NUM_ATRIB_REQ_GCR 54NUM_ATRIB_RESPONSE_GCR 54NUM_ATT_SCP_DIALOGS_LNP 22NUM_ATT_SCP_DIALOGS_SMS 23NUM_ATT_SCP_DIALOGS_USSD 23NUM_CALL_SET_UP_CONTRIB 24NUM_CALLS_REL_BS 21NUM_CELL_SETUP_RESP_GCR 54NUM_COM_LUP_CONTRIB 32

NUM_COM_PAGING_RET_A 32NUM_DISPATCH_SETUP_RESP_GCR 54NUM_IMEI_CHECK_BLACK 22NUM_IMEI_CHECK_GREY 22NUM_IMEI_CHECK_LUP 22NUM_IMEI_CHECK_PER_LUP 22NUM_IMEI_CHECK_UNKNOWN 22NUM_LUP_CONTRIB 24NUM_MSUB _GPRS_CSI 99NUM_MSUB _SS_CSI 99NUM_NO_SPCH_BSSAP_LTG 22NUM_RECEIVED_CIP 21NUM_RECEIVED_CLASSM_UPD 22NUM_RECEIVED_GCP 21NUM_RECEIVED_OVERLOAD 21NUM_RECVD_GCNR_IN_AMSC 56NUM_REQ_GCNR 56NUM_RESET 21NUM_RESET_CIRCUIT 21NUM_SEND_GCNR_TO_AMSC 56NUM_SEND_OVERLOAD 21NUM_SIGN_POINT_PROHIB 21NUM_SSP_BSSAP 21NUM_SUCC_SCP_DIALOGS_LNP 23NUM_SUCC_SETUP_DISP_VGCS_VBS 55NUM_SWITCH_LTGPOOL 23NUM_TONES_DTMF 22NUM_TOTAL_START_IMEI_CHECK 22NUM_VGCS_TALK_ACK 56NUM_VGCS_TALK_CONFIRM 56NUM_VGCS_TALK_REJECT 56NUM_VGCS_TALK_REL 55NUM_VGCS_TALK_REQ 55NUM_VGCS_VBS_SETUP_BSC_ACK 55NUM_VGCS_VBS_SETUP_BSC_REQ 55NUM_VGCS_VBS_TCH_ALLOC_ACK 55NUM_VGCS_VBS_TCH_ALLOC_REQ 55NUMB CCS7 DPC OLOAD 126NUMBER_OF_ATB 135numberOfTransitMessagesProcessed 158numInMSU 144numInMSUperNet 145numLinkSetNotAvail 145NumLostMSURoutErr 144numOutMSU 144numOutMSUperNet 145numTransitMSU 144numTransitMSUperNet 145

OOACSU_ATTEMPTS 30OACSU_RELSUB 44OACSU_TCH_ALLOC 44OACSU_WITH_ANSWER 46ORIG_CALL_ATT_QUEUING 62

184 A50016-D1109-G801-6-7618


ORIG_CALL_ATT_TCH_REQ 62ORIG_CALL_QUEUE_TCH_ALLOC 63OUTGOING_MESSAGE_SIGNAL_UNITS 154OWN_SUB_ROAM_IN_FOREIGN_PLMN 93

PPAD_CDA 94PAD_CDA_GBS 98PAG_PROC 89POS_SEND_TO_GMLC 34PROCESSED_DIALOGS_(OVERALL) 154PROCESSED_DIALOGS_(SCF_INI) 154PROVIDE_MSRN_RECEIVED 84providerInitiatedRelease 157providerInitiatedReset 157PU:SIMP 153

RreassemblyTimerExpired 157RECEIVE_RP DATA_ATTEMPTS 50RECEIVED_DETACH_NO_VLR_ENTRY 78RECEIVED_DETACH_WITH_IMSI 78RECEIVED_DETACH_WITH_TMSI 78RECEIVED_PAG_RESP 40receivedMSUs 148receivedOctetsSIFSIO 147, 148RECVD_ACT_FOLLOW_ME 102RECVD_ATI 103RECVD_AUTH_INF_TRIPLES_HLR 83RECVD_AUTH_INF_TRIPLES_PVLR 83RECVD_CAMEL_USSD_BY_GSMSCF 112RECVD_CAMEL_USSD_TO_GSMSCF 110RECVD_CCBS_REQ_IN_HLR_A 103RECVD_CCBS_REQ_IN_HLR_B 103RECVD_DEACT_FOLLOW_ME 102RECVD_LOCUPD_HPLMN 114RECVD_LOCUPD_VPLMN 114RECVD_MSG_ACT_CALLBACK 109RECVD_MSG_ACT_SS 109RECVD_MSG_DEACT_CALLBACK 109RECVD_MSG_DEACT_SS 109RECVD_MSG_ERASE_CALLBACK 109RECVD_MSG_ERASE_SS 108RECVD_MSG_INTERROG_CALLBACK 110RECVD_MSG_INTERROG_SS 109RECVD_MSG_REGISTER_CALLBACK 109RECVD_MSG_REGISTER_PW 108RECVD_MSG_REGISTER_SS 108RECVD_MSG_UNSTRUCTURED_SS_DATA 109RECVD_MSRN 105RECVD_NOTE_MS_PRESENT 113RECVD_POS_ACK_FROM_GSMSCF 31RECVD_RESET_VLR 101RECVD_RESTORE_DATA 101

RECVD_SEND_PARAM_AR 101RECVD_SEND_PARAM_AR_PR 101RECVD_SEND_PARAM_PR 101RECVD_SEND_ROUT_INFO_MSG_GMSC 101RECVD_SEND_ROUT_INFO_MSG_SCODE 101RECVD_SET_MWD 113RECVD_SND_ROUTING_INFO_SM 113RECVD_UPD_LOC_MSG_VLR_HPLMN 100RECVD_UPD_LOC_MSG_VLR_VPLMN 100REG_SS_TO_HLR 85REQ_COM_LUP_TO_HLR 87REQ_COM_PAG 89REQUEST_LOCUPD_INTER_VLR 77REQUEST_LOCUPD_INTRA_VLR 76REQUESTS_LOCUPD 76REQUESTS_LOCUPD_TO_HLR 78REQUESTS_LOCUPD_WITH_IMSI_ATT 77REQUESTS_PERIODIC_LOCUPD 77REROUTE_AFTER_SN 43REROUTE_BEFORE_SN 43REROUTE_NEW_DEST 46RES_COM_LUP_FROM_HLR 88RES_COM_LUP_FROM_PVLR 88RESETS_RECEIVED_FROM_HLR 85RESTORE_DATA_TO_HLR 85RESTR_SUB_1_NAT_ALL_VPLMN 91RESTR_SUB_ALL_GSM_PLMN 91RESTR_SUB_HOME_PLMN_ONLY 92RESULTS_LOCUPD_FROM_HLR 78RESULTS_LOCUPD_FROM_PVLR 78retransmittedOctets 148RETRY_PAG 89REUSED_TRIPLES 83, 102, 118routeSetUnavailable 146routeSetUnavailableDuration 146

SsccpSyntaxErrorList 158SCCREFMR 161SCCREFMS 161SCCRMSRC 161SCCRMSSE 161SCDT1MRC 160SCDT1MSE 160SCDT2MRC 160SCDT2MSE 160SCERRMRC 162SCERRMSE 162SCHOPCVI 163SCINCOFA 162SCMSBUSS 161SCNTRASN 163SCNTRSPA 163SCOLDPBB 163SCPICORL 163

A50016-D1109-G801-6-7618 185


Traffic Measurement

SCRETITO 162SCRFRUNK 162SCRLCSFA 162SCRSRMRC 161SCRSRMSE 161SCSHORTM 160SCSPCCON 163SCSPCUNA 163SCSSNEQD 162SCSSUNAV 162SCSYNERR 162SCTEMLSS 161SCTEXTMH 160SCTIMLSS 160SCTIMSER 162SCTINTMH 160SCUDESAD 163SCUDTMR0 161SCUDTMR1 160SCUDTMRC 161SCUDTMS0 161SCUDTMS1 161SCUDTMSE 161SCUDTSRC 161SCUDTSSE 161SCXUSMRC 162SCXUSMSE 162SCXUTMRC 162SCXUTMSE 162SEC_COM_PAG 89segmentationFailed 158segmentationNotSupported 157segmentReceivedOutOfSequence 158SEIZE_MAXIMUM 134SEMI BLOCKED CHANNELS 137SEMI_BLOCKED_LINES 134SEND_PAR_RECVD_FROM_OTHER_VLR 83SEND_PARAM_REQ_SUBDAT_TO_HLR 83SEND_PARAM_REQ_TRIPLES_TO_HLR 82SEND_PARAM_REQ_TRIPLES_TO_PVLR 83SEND_RP DATA_ATTEMPTS 50SEND_TRIPLES_TO_VLR 83SENT_CAN_LOC_MSG_ AFTER_SCI 109SENT_CAN_LOC_SGSN_CHANGE 115SENT_CAN_LOC_SUB_ADMIN 115SENT_FORW_CHECK_SS_INDIC 109SENT_FORW_TO_NO_TO_GMSC 105SENT_INS_DEL_SUB_DATA 115SENT_INSERT_MS_DATA_AFTER_SCI 109SENT_MI_USSD_TO_HLR 87SENT_MSRN_TO_GMSC 105SENT_NI_USSD_TO_MS 87SENT_NI_USSD_TO_VLR 103SENT_NOTIF_SS_INV_TO_GSMSCF 31SENT_PSI 102

SENT_PURGE_MS_MSG_TO_HLR 85SENT_RESET_HLR 101SENT_RESET_TO_SGSN 115SERV_SUB_VBS_ATTEMPTS_IN_RMSC 57SERV_SUB_VGCS_ATTEMPTS_IN_RMSC 57SERVICE_REQ_COM_LUP 32SERVICE_REQ_LOC_UPD 31SERVICE_REQ_SCI_CALL_REL 31SERVICE_REQ_SCI_INDEPENDENT 30SET_UP_SERV_CODE 29SHORT_MSG_SERVICE_MO 93SHORT_MSG_SERVICE_MT 93signUnitsReceived 147, 148sIInServiceDuration 147sIUnavailabilityDuration 147SLC:ACC CALLS GP 131SLC:OFF CALLS 131SLC:REJ CALLS OL 131slCongestedDuration 149slCongestedStarts 149slFailed 147slInServiceDuration 146slLocalBlocked 148slLocalInhibited 148slRemoteBlocked 148, 149slRemoteInhibited 148slRemoteProcOutage 147slsUnavailablel 146slUnavailabilityDuration 146SMS_INC_ATTEMPTS 50SMS_INC_PARALLEL 50SMS_INC_PARALLEL_MEM_AV_INV 50SMS_OTG_ATTEMPTS 50SMS_OTG_PARALLEL 50SMS_SER_REQ_ATTEMPTS 50SN_REROUTE_CALL 43SN_THROUGH_CONNECTIONS 41SND_ACT_TRACEMODE 102SND_ALERT_SERVICE_CENTER 113SND_CAN_LOC_MSG_LOC_UPD 100SND_CAN_LOC_MSG_SUB_ADMIN 100SND_DEL_SUBDT_MSG_SUB_ADMIN 101SND_INS_SUBDT_MSG 100SND_INS_SUBDT_MSG_SUB_ADMIN 100SND_PROV_MSRN 105SPEECH_CALLS_WITH_ANSWER 44SPEECH_FOLLOWED_BY_DATA 94SPEECH_TRANSMISSION 93STARTED_INT_SER_CODE_DIG 29STARTED_INTERROGATIONS 29STARTED_PAG_RETRY_PROC 29STARTED_PAGING_PROC 29SUB_IDENTIFIED_WITH_IMSI 82SUB_IDENTIFIED_WITH_TMSI 81SUB_REGISTERED_IN_HLR 91

186 A50016-D1109-G801-6-7618


SUB_WITH_IMSI_TRACE_ACTIVE 92SUB_WITH_ODB_INCOMING 92SUB_WITH_ODB_OUTGOING 92SUB_WITH_ODB_PREMIUM_RATE 92SUB_WITH_ODB_ROAM 92SUB_WITH_ODB_SPECIFIC_HPLMN 92SUB_WITH_ODB_SS_MANAGEMENT 92SUBSEQ_MSC_MSC_HO_MSCA 48subsystemCongestion 157subsystemFailure 158SUCC_ALERT_SERVICE_CENTER 113SUCC_CIPH_MODE_CTRL_PROC 84SUCC_COM_LUP 87SUCC_COM_LUP_IMSI_ATTACH 87SUCC_COM_PAG 90SUCC_COMPL_HO_DATA_CALLS 49SUCC_COMPL_HO_SDCCH 49SUCC_COMPLETED_HO 49SUCC_DATA_MSC_MSC_HO_MSCA 49SUCC_ESRK_ALLOC_ATT 33SUCC_INVOC_AOC_CHARGE 60SUCC_INVOC_AOC_INFO 60SUCC_INVOC_CALL_BACK 60SUCC_INVOC_CALL_TRANSFER 61SUCC_INVOC_CCBS_MORTR 61SUCC_INVOC_CCBS_MTER 61SUCC_INVOC_MULTIPARTY 60SUCC_INVOC_PUT_HOLD 60SUCC_INVOC_RETRIEVE_HOLD 60SUCC_INVOC_SERV_CALL_BARRING 59SUCC_INVOC_SERV_CALL_FORWARD 58SUCC_LINK_SETUP_TO_RMSC 57SUCC_LOC_ATT 33SUCC_LOC_ATT_CONV_GPS 34SUCC_LOC_ATT_MOB_ASSIST_E_OTD 34SUCC_LOC_ATT_MOB_ASSIST_GPS 34SUCC_LOC_ATT_MOB_BASED_E_OTD 34SUCC_LOC_ATT_MOB_BASED_GPS 34SUCC_LOC_ATT_TA 33SUCC_LOC_ATT_TOA 34SUCC_LOC_ATT_UNKNOWN_POS 34SUCC_LOCUPD_WITH_IMSI_ATTACH 77SUCC_MSC_MSC_HO_MSCA 49SUCC_MULT_SMS_INC 51SUCC_MULT_SMS_OTG 51SUCC_PAG 89SUCC_POS_SEND_TO_GMLC 35SUCC_REQUESTS_LOCUPD 77SUCC_SMS_INC 50SUCC_SMS_OTG 51SUCC_SMS_RECEIVE_RP_ACK 51SUCC_SMS_SEND_RP_ACK 51SUCCESS_MS_MEMORY_AVAIL 85SUCCESSFUL_HANDOVERS 65SUCCESSFUL_TMSI_REALLOC 84

SUM_CH_BLO_TIME 133SWITCHES_TO_LINKED_MS 102

TTC 128, 135TC WITH ANSWER 128TC:I(O) 133TC_SEMI_BLOLI 134TC_TRANS_BLOLI 134TCUCMPRN 164TCUCMPSN 164TCUMSGRA 164TCUMSGRB 164TCUMSGRC 164TCUMSGRE 164TCUMSGRU 164TCUMSGSA 164TCUMSGSB 164TCUMSGSC 164TCUMSGSE 164TCUMSGSU 164TCUSCSRA 165TCUSCSRB 165TCUSCSRC 165TCUSCSRE 165TCUSCSRU 165TGRP BLO TIME: O 124tiarExpiry 157TIME_CALL_SET_U_SERV 24TIME_COM_LUP_SERV 32TIME_FOR_ANSWER_EXPIRED 155TIME_LUP_SERV 24TMSI_REALLOC_NOT_ANSWERED 84TOTAL 153TR CIRC:ACC CALLS GP 131TR CIRC:OFF CALLS 131TR CIRC:REJ CALLS OL 131TRAFF_VOL_SUCC_PAGING 24TRAFFIC_VOLUME 24TRANS BLOCKED CHANNELS 137TRANS_BLOCKED_LINES 134TRANSIT_MESSGE_SIGNAL_UNITS 154transmittedMSUs 148transmittedOctetsSIFSIO 147, 148TRIPLES_REQUESTED_BY_HLR 118TRIPLES_RETURNED_TO_HLR 118TS11_EMERG_CALL_TCH_ALL 40TS11_EMERG_WITH_ANSWER 44TS12_EMERG_CALL_TCH_ALL 40TS12_EMERG_WITH_ANSWER 44TV NH ALT1: O 127TV SEMI BLOLI 123TV TRANS BLOLI 123TV: NH DIRECT: O 126TV:I 137

A50016-D1109-G801-6-7618 187


Traffic Measurement

TV:O 137TV_ANSWER:I (O) 123, 137TV_IWE_ANACDS_NTP 72TV_IWE_ANALOG_NTP 71TV_IWE_ANALOG_TP 71TV_IWE_DIGCDS_NTP 72TV_IWE_DIGITAL_NTP 72TV_IWE_DIGITAL_TP 72TV_IWE_FAX3_TP 72TV_SP_FAX3_TP 74TV_SUCC_COM_PAGING 32TV_VBS 53TV_VGCS 53

UudtMessagesReceived 159udtMessagesSent 159udtsMessagesReceived 159udtsMessagesSent 159UNAVAILABLE LINK SETS 151UNAVAILABLE ROUTE SET 151unknownDestinationAddress 157unknownOrUnqualifiedRoutingFailure 158UNRELDIR 102UNS_ACT_FOLLOW_ME_MS_BEH 104UNS_ACT_FOLLOW_ME_SYS_BEH 105UNS_ACT_TRACEMODE 104UNS_ACT_TRACEMODE_SUB_ADMIN 108UNS_ADMBLCKD_OR_CALLBARR 113UNS_BLACK_LIST 38UNS_CALL_SS_BIC 106UNS_CALL_SS_BICROAM 107UNS_CAMEL_USSD_BY_HLR 112UNS_CAN_LOC_SGSN_CHANGE 116UNS_CAN_LOC_SUB_ADMIN 116UNS_CANLOC_ANY_OTHER_SS 111UNS_CANLOC_UNIDENT_SUB_SS 111UNS_CANLOCMSG_ANY_OTHER 104UNS_CANLOCMSG_UNIDENT_SUB 104UNS_CCBS_REQ_OTHER 107UNS_CCBS_REQ_SUB_BEH 107UNS_CUG_REJECT 38UNS_DEACT_FOLLOW_ME_MS_BEH 105UNS_DEACT_FOLLOW_ME_SYS_BEH 105UNS_DEACT_TRACEMODE_SUB_ADMIN 108UNS_DEL_SUBDT_MSG_SUB_ADMIN 107UNS_DOWNGRADING_USER_INIT 73UNS_GMSC_BEHAVIOR 113UNS_IMEI_UNKNOWN 38UNS_INS_DEL_SUB_DATA 116UNS_INS_SUBDT_MSG 104UNS_INS_SUBDT_MSG_SUB_ADMIN 107UNS_IWE_ DIGCDS_NTP 69UNS_IWE_ANACDS_NTP 69UNS_IWE_ANALOG_NTP 68

UNS_IWE_ANALOG_TP 68UNS_IWE_DIGITAL_NTP 68UNS_IWE_DIGITAL_TP 68UNS_IWE_FAX3_TP 69UNS_IWE_SP_FAX3_TP 74UNS_LOC_ATT_CONGESTION 33UNS_LOC_UPD_HPLMN_OTHER 115UNS_LOC_UPD_HPLMN_SUB_BEH 115UNS_LOC_UPD_OVL 116UNS_LOC_UPD_VPLMN_OTHER 115UNS_LOC_UPD_VPLMN_SUB_BEH 115UNS_LOST_LOCATION 114UNS_MS_DETACH 38UNS_MTC_OVL 116UNS_MULT_SMS_INC 53UNS_MULT_SMS_OTG 53UNS_RECVD_PSI 105UNS_RECVD_SET_MWD 114UNS_RESP_ACT_CALLBACK 112UNS_RESP_ACT_SS_SUB_BEH 111UNS_RESP_ACT_SS_SYS_BEH 111UNS_RESP_DEACT_CALLBACK 112UNS_RESP_DEACT_SS_SUB_BEH 111UNS_RESP_DEACT_SS_SYS_BEH 111UNS_RESP_ERASE_CALLBACK 112UNS_RESP_ERASE_SS_SUB_BEH 110UNS_RESP_ERASE_SS_SYS_BEH 110UNS_RESP_INS_SUBDT_SS 111UNS_RESP_INTERROG_CALLBACK 112UNS_RESP_INTERROG_SS_SUB_BEH 111UNS_RESP_INTERROG_SS_SYS_BEH 111UNS_RESP_REGISTER_CALLBACK 112UNS_RESP_REGISTER_PW_SUB_BEH 110UNS_RESP_REGISTER_PW_SYS_BEH 110UNS_RESP_REGISTER_SS_SUB_BEH 110UNS_RESP_REGISTER_SS_SYS_BEH 110UNS_RESP_UNSTRUCTURED_SS_DATA 112UNS_RESTORE_DATA 106UNS_SECONDARY_CAUSES 114UNS_SMS_INC_ABSENT_MS 51UNS_SMS_INC_DELIVERY_FAIL 52UNS_SMS_INC_PARALLEL_MS_STATE 52UNS_SMS_OTG_DELIVERY_FAIL 52UNS_SMS_OTG_NO_FACILITY 51UNS_SMS_OTG_UNIDENT_MS 51UNS_SMS_OVL 117UNS_SMS_REC_RP_MEMORY 52UNS_SMS_REC_RP_PROT_ERR 52UNS_SMS_SEND_RP_FAC_CHECK_ERR 52UNS_SMS_SEND_RP_PROT_ERR 52UNS_SMS_SEND_RP_SUB_ERR 52UNS_SMS_SEND_RP_UNASSIGN_NUM 52UNS_SND_PARAM_AR 108UNS_SND_PARAM_AR_PR 108UNS_SND_PARAM_OVL 116

188 A50016-D1109-G801-6-7618


UNS_SND_PARAM_PR 108UNS_SNDROUTINFMSG_BLCKD_BARR 105UNS_SNDROUTINFMSG_CF_VIOL 105UNS_SNDROUTINFMSG_GMSC_BEH 106UNS_SNDROUTINFMSG_LOST_LOC 106UNS_SNDROUTINFMSG_MS_BEH 106UNS_SNDROUTINFMSG_SEC_CAUSES 106UNS_SNDROUTINFMSG_SUB_ERROR 106UNS_SS_OVL 116UNS_SUB_ BEHAVIOR 114UNS_SUB_ADMIN_CANLOC_ANY_OTHER 107UNS_SUB_ADMIN_CANLOC_UNIDENT_MS 107UNS_SUBSCRIPTION_ERROR 113UNS_UPGRADING_USER_INIT 73UNS_UPLOCMSG_VLR_HPLMN_IRR_SYS 103UNS_UPLOCMSG_VLR_HPLMN_IRR_VLR 103UNS_UPLOCMSG_VLR_HPLMN_SUB_BEH 103UNS_UPLOCMSG_VLR_VPLMN_IRR_SYS 104UNS_UPLOCMSG_VLR_VPLMN_IRR_VLR 104UNS_UPLOCMSG_VLR_VPLMN_SUB_BEH 104UNSTRUC_SS_DATA_TO_HLR 86UPGRADING_NETWORK_INIT 73UPGRADING_USER_INIT 73USER_SIG1 98userUnequipped 158

VviolationOfHopCounter 157VLR_AREA_LEAVES_FOREIGN_PLMN 76VLR_AREA_LEAVES_OWN_PLMN 76VLR_CHANGES_PVLR_KNOWN 77VLR_CHANGES_PVLR_UNKNOWN 78

WWLL_SUB_REGISTERED_IN_HLR 91WRITTEN_MISMATCH_RECORDS 83

XxudtMessagesReceived 159xudtMessagesSent 159xudtsMessagesReceived 159xudtsMessagesSent 159