Information, Traffic and Performance Data, Counter Description, Siemens

Information

Traffic and Performance Data

Counter Description

A50016-D1112-G802-1-7618

2 A50016-D1112-G802-1-7618

Counter Description InformationTraffic and Performance Data

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 2005.

Issued by the Communications GroupHofmannstraß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-D1112-G802-1-7618 3

InformationTraffic and Performance Data

Counter Description

Reason for UpdateSummary:A new version of this document.

Issue HistoryIssue

Number

Date of issue Reason for Update

1 05/2005 New software release

4 A50016-D1112-G802-1-7618


A50016-D1112-G802-1-7618 5


Counter Description

This document consists of a total of 241 pages. All pages are issue 1.

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 About the Use of Traffic and Performance Data . . . . . . . . . . . . . . . . . . . . . 141.2 Types of Collected Traffic and Performance Data . . . . . . . . . . . . . . . . . . . 141.3 Traffic and Performance Measurement on the CP Platform . . . . . . . . . . . . 151.3.1 Data Collection and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.3.2 Data Transfer and Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.3.3 Measurement Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.4 Traffic and Performance Measurement on the MP Platform. . . . . . . . . . . . 181.4.1 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.4.2 Data Storage, Transfer, and Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.4.3 Measurement Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2 Traffic Measurement in the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.1 Basic Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.1.1 Miscellaneous Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.1.2 Time/Duration Counters: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1.3 Time/Duration Counters: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.1.4 Load and Demand Counters: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.1.5 Load and Demand Counters: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352.1.6 Load and Demand Counters: LTG Pooling. . . . . . . . . . . . . . . . . . . . . . . . . 362.1.7 Load and Demand Counters: Gs Interface . . . . . . . . . . . . . . . . . . . . . . . . . 372.1.8 Load and Demand Counters: Location Services . . . . . . . . . . . . . . . . . . . . 382.1.9 Location Service Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.1.10 Grade of Service Counters: Unsuccessful Calls . . . . . . . . . . . . . . . . . . . . . 422.1.11 Grade of Service Counters: Unsuccessful LTG Pooling . . . . . . . . . . . . . . . 462.1.12 Grade of Service Counters: Successful Call Establishment . . . . . . . . . . . . 472.1.13 Grade of Service Counters: Answered Calls . . . . . . . . . . . . . . . . . . . . . . . 512.2 Handover Data Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.2.1 Load and Demand Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.2.2 Grade of Service Counters: Handover Establishment . . . . . . . . . . . . . . . . 562.2.3 Grade of Service Counters: Successful Completed Handovers . . . . . . . . . 562.2.4 Counters for Inter System Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.3 Short Message Service Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . 582.3.1 Load and Demand Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.3.2 Grade of Service Counters: Successful Services . . . . . . . . . . . . . . . . . . . . 592.3.3 Grade of Service Counters: Unsuccessful Services . . . . . . . . . . . . . . . . . . 602.4 ASCI Service Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

3 UMTS Traffic Measurement in a 3G MSC . . . . . . . . . . . . . . . . . . . . . . . . . 703.1 Basic Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.1.1 Time/Duration Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.1.2 Load and Demand Counters: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1.3 Load and Demand Counters: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.1.4 Grade of Service Counters: Unsuccessful Calls . . . . . . . . . . . . . . . . . . . . . 723.1.5 Grade of Service Counters: Successful Call Establishment . . . . . . . . . . . . 72

6 A50016-D1112-G802-1-7618


3.1.6 Grade of Service Counters: Answered Calls . . . . . . . . . . . . . . . . . . . . . . . . 743.2 Handover Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.2.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.2.2 Grade of Service Counters: Successful Completed Handovers . . . . . . . . . 763.3 Short Message Service Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . 773.3.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.3.2 Grade of Service Counters: Successful Services . . . . . . . . . . . . . . . . . . . . 78

4 Traffic Measurement of Special and Supplementary Services . . . . . . . . . . 814.1 Supplementary Service Counters: Call Forwarding . . . . . . . . . . . . . . . . . . . 814.2 Supplementary Service Counters: Call Barring . . . . . . . . . . . . . . . . . . . . . . 824.3 Special Services Counters: Invocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.4 Special Services Counters: Successfully Completed Invocations . . . . . . . . 83

5 Traffic Measurement in IWE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.2 Grade of Service Counters: Unsuccessful Attempts . . . . . . . . . . . . . . . . . . 875.3 Grade of Service Counters: Forced Released Calls . . . . . . . . . . . . . . . . . . 895.4 Grade of Service Counters: Holding Times . . . . . . . . . . . . . . . . . . . . . . . . . 905.5 Grade of Service Counters: Upgrading and Downgrading. . . . . . . . . . . . . . 925.6 Alternate Speech Fax 3 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

6 Traffic Measurement in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.1 Installation-related Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966.2 Load and Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976.3 Security Function Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046.4 External Interworking Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086.5 Combined Paging and Combined Location Update Counters . . . . . . . . . . 112

7 Traffic Measurement in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147.1 Structure- and Installation-related Counters: Part 1. . . . . . . . . . . . . . . . . . 1147.2 Structure- and Installation-related Counters: Part 2. . . . . . . . . . . . . . . . . . 1167.3 Structure- and Installation-related Counters: Part 3. . . . . . . . . . . . . . . . . . 1237.4 Mobility Management/Call Handling/Authentication. . . . . . . . . . . . . . . . . . 1247.4.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247.4.2 Grade of Service Counters: Mobility Management . . . . . . . . . . . . . . . . . . 1297.4.3 Grade of Service Counters: Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . 1317.4.4 Grade of Service Counters: Subscriber Data. . . . . . . . . . . . . . . . . . . . . . . 1327.5 Subscriber Controlled Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347.5.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1347.5.2 Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1367.6 Short Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.6.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397.6.2 Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1407.7 Overload Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1417.8 Data Service with GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427.8.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1427.8.2 Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

A50016-D1112-G802-1-7618 7


Counter Description

8 Traffic Measurement in AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

9 Traffic Measurement in EIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1469.1 Structure- and Installation-related Counters . . . . . . . . . . . . . . . . . . . . . . . 1469.2 Grade of Service Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

10 Traffic Measurement Related to Location Area . . . . . . . . . . . . . . . . . . . . 148

11 Traffic Measurement Related to Cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15011.1 Load and Demand Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15011.2 Handover Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

12 Counter Calculations for Traffic Monitoring. . . . . . . . . . . . . . . . . . . . . . . . 153

13 General CN Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16113.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16113.2 Trunk Group Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16213.2.1 Index 1: Seizure and Traffic Volume Counters . . . . . . . . . . . . . . . . . . . . . 16313.2.2 Index 2: Additional Trunk Group Counters . . . . . . . . . . . . . . . . . . . . . . . . 16313.2.3 Index 3: Counters for Successful Calls not Reaching Destination . . . . . . 16413.2.4 Index 4: Counters for Refused Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16513.2.5 Index 5: Counters for Refused Calls at CCS7 Trunk Groups . . . . . . . . . . 16613.2.6 Index 6 and 7: Counters for Non-hierarchical Trunk Groups . . . . . . . . . . 16613.2.7 Index 8: Enhanced Multilevel Precedence and Preemption Counters . . . 16713.3 Destination Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16813.4 CP Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17013.5 LTG Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17113.5.1 LTG Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17113.5.2 Code Receiver Group Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17313.5.3 Group Processor Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17313.6 GP Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17313.7 DLU Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17513.8 Announcement Group Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . 17713.9 GSM MGW Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

14 CSC-specific Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18214.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18214.1.1 Data Quality and Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18214.1.2 Plausibility Checking of Traffic Measurement Results . . . . . . . . . . . . . . . 18314.2 PBX Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18314.2.1 Service-related Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18414.2.2 Service-independent Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

15 SS7-specific Traffic Measurement (SSNC). . . . . . . . . . . . . . . . . . . . . . . . 18615.1 MTP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18615.1.1 Net Element Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18615.1.2 Signaling Point Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18715.1.2.1 Signaling Point Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18815.1.2.2 Obligatory Signaling Point Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18815.1.2.3 Network MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18815.1.2.4 Signaling Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

8 A50016-D1112-G802-1-7618


15.1.3 Signaling Link Set Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18915.1.3.1 Link Set Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18915.1.3.2 Link Set Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18915.1.4 Destination Point Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19015.1.5 Signaling Link Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19015.1.5.1 Obligatory Link Duration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19015.1.5.2 Link Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19115.1.5.3 Obligatory Link Utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19215.1.5.4 Link Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19215.1.5.5 Link Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19315.1.5.6 High-Speed Link Utilization Measurement . . . . . . . . . . . . . . . . . . . . . . . . . 19415.1.5.7 Obligatory High-Speed Link Utilization Measurement . . . . . . . . . . . . . . . . 19415.1.6 Signaling Linkset IP Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19415.1.7 SCTP Association Utilization and Duration Measurement . . . . . . . . . . . . . 19515.1.7.1 Obligatory Association Utilization Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 19515.1.7.2 All Association Utilization Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19515.1.7.3 All Association Duration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19615.2 SCCP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19715.2.1 SCCP Measurements with Specific Criteria. . . . . . . . . . . . . . . . . . . . . . . . 19815.2.1.1 SCCP Error Performance Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 19815.2.1.2 SCCP Utilization Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20015.2.1.3 SCCP Quality of Service Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 20115.2.2 SCCP Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20315.2.2.1 SCCP Screening Success Measurement . . . . . . . . . . . . . . . . . . . . . . . . . 20315.2.2.2 SCCP Screening Failure Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 20415.2.3 Signaling Link Set IP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20515.3 TCAP Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

16 MP Load Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20816.1 VCPU Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20816.2 Message Handler Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

17 Traffic Measurement Related to Iu Interface . . . . . . . . . . . . . . . . . . . . . . . 21217.1 CIC Group Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21217.1.1 AAL2 Overrun Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21217.1.2 AMR Underrun Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21317.1.3 SSCS Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21317.1.4 Data Underrun Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21317.1.5 Iu User Plane Protocol Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21317.1.6 Rate Control Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21417.1.7 AMR Mode Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21417.2 AAL2 Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21417.2.1 AAL2 NNI Access Control Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 21517.2.2 AAL2 NNI Access Protocol Measurement . . . . . . . . . . . . . . . . . . . . . . . . . 21717.2.3 AAL2 Carrier Access Control Measurement . . . . . . . . . . . . . . . . . . . . . . . 21917.2.4 CPS Protocol Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21917.2.5 PDU14 Protocol Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22017.2.6 AAL2 Destination Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

A50016-D1112-G802-1-7618 9


Counter Description

17.3 RANAP Destination Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22117.3.1 RANAP Protocol Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22117.3.2 CAM Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22217.4 ATM Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22317.4.1 ATM Traffic Load Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22417.4.2 Cell Level Protocol Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22417.4.3 Virtual Path and Virtual Channel Measurements . . . . . . . . . . . . . . . . . . . 224

18 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

19 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

10 A50016-D1112-G802-1-7618


IllustrationsFig. 1.1 Storage of traffic data into Q3 log file or SAMAR on the MP . . . . . . . . . 19

Fig. 2.1 Traffic types in scope of the observed MSC . . . . . . . . . . . . . . . . . . . . . . 25

Fig. 13.1 RSU overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

A50016-D1112-G802-1-7618 11


Counter Description

TablesTab. 1.1 Traffic measurement commands on the CP . . . . . . . . . . . . . . . . . . . . . 17

Tab. 1.2 Traffic measurement tasks and objects on the MP . . . . . . . . . . . . . . . . 20

Tab. 12.1 Options for counter-based calculations . . . . . . . . . . . . . . . . . . . . . . . . 154

Tab. 12.2 Calculations with OMC output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Tab. 14.1 Data quality and availability of measurement data . . . . . . . . . . . . . . . 182

12 A50016-D1112-G802-1-7618


A50016-D1112-G802-1-7618 13


Counter Description

1 IntroductionThis Counter Description gives information about the traffic and performance counterdata that is collected within the circuit-switched domain of the PLMN core network. Fol-lowing a general introduction about traffic and performance data in the core network, alltraffic counters that are implemented within the different parts of the system are listedand described.

The Counter Description is intended for use by network operators, developers, and sys-tem operators who need an overview or interpretation of the various counters which areimplemented in the circuit-switched domain of the core network. Furthermore, it ad-dresses users of the Element Management System which makes measurement resultsavailable.

iFor dimensioning the whole PLMN, traffic measurement data related to manufacturer-specific subunits and auxiliary units (e.g., use of conference modules) must also be reg-istered. This manual does not include information about this data.

14 A50016-D1112-G802-1-7618


1.1 About the Use of Traffic and Performance DataThe purpose of traffic and performance data collection is to serve the process of networkplanning and observation. Traffic data collection and evaluation is of decisive impor-tance for telecommunications carriers regarding network planning and traffic forecastsand network traffic management:• Network planning and traffic forecasts

Analysis of traffic measurement data is the basis for planning new networks and ex-panding the existing network to meet future demands. Long-term traffic measure-ments (e.g., over several months) help to identify trends in traffic and make trafficforecasts. Measurement data also reveals extreme load situations and unused re-sources. This information can be taken into consideration when planning new net-work components.

• Network traffic managementTraffic measurement data provides an accurate overview of the traffic situation in thenetwork and detects overload situations, unused network resources, and faults inthe network. The network operator can respond with appropriate network manage-ment measures and make full use of the network resources.

The core network does not require any special equipment for traffic data acquisition be-cause a wide range of intra-system functions is available. These functions collect andprocess traffic data in every functional system element and for every main unit or logicalconfiguration (e.g., entire MSC, trunk groups, location area or cells).

All kinds of traffic data are collected from the traffic flows between and within the differ-ent network elements and registered in measurement counters. The counters are con-tinuously updated by the call-processing software. However, traffic data is stored only ifa measurement job has been set up for the required data. The results are stored on themagnetic disk of the coordination processor (CP) or are sent to a network element man-ager, such as Switch Commander.

1.2 Types of Collected Traffic and Performance DataBased on counter measurements, the following types of traffic and performance dataare provided on the CP and MP platforms:• Traffic measurement data

Traffic measurements are recorded by means of counters which are implemented inthe system. Traffic data measurements provide the network operator with informa-tion related to the traffic and performance of network elements. This information in-cludes data about the system load, the processor load, and the protocol load.

• Traffic monitoring dataTraffic monitoring refers to objects with definable thresholds. By continuously com-paring counts of monitored variables with defined thresholds, the system generatesdata and messages which can be called up directly at the operating system. At theend of each measurement interval, the data is backed up automatically in monitoringfiles on the CP magnetic disk, from where it can be output to a printer or operatingsystem. Monitoring functions have been created for selected monitoring objects todetect such bottlenecks and overload situations.

iThis manual does not make a clear distinction between the terms “traffic” and “perfor-mance” because this is only possible with respect to a special counter. The term “traffic”covers a larger concept, and is therefore often used to refer to traffic and performancedata.

A50016-D1112-G802-1-7618 15


Counter Description

1.3 Traffic and Performance Measurement on the CP PlatformTraffic measurement on the CP platform supplies and outputs counters registering:– Occurrence and duration of specific events during call processing– Total load and the call processing load of the NE– Grade of service– Usage of features and services– Usage and states of equipment (e.g.: LTG, DLU)

The counters are implemented on the CP platform according to the recommendationsof the ITU-T and the 3GPP standard.

1.3.1 Data Collection and StorageTraffic measurement data on the CP platform is taken continuously but is processedonly after the operator has entered an MML command. MML commands are used to de-fine on which network element or logical component the measurement has to be taken,the time scheduler for the measurement, and the file type of the measurement file (seechapter 1.3.2 "Data Transfer and Retrieval").

All measured values are assigned two areas of traffic data memory: a passive part andan active part. The counters are updated in the active part under the control of call-pro-cessing software. The passive traffic data memory is read by the relevant measurementprocess and edited for output. The two parts are switched over every 15 minutes: Theactive traffic data memory becomes passive and vice versa. The passive traffic datamemory is only read if a measurement job is present in the system. After each read op-eration from the passive traffic data memory, the counters are initialized.

Implementation of the individual measurements, as well as the collection and output ofthe measurement data, is controlled by separate traffic measurement processes. Whenthe recording jobs are entered, an operational process (traffic measurement process) istriggered in the CP. These processes collect the measured values and output them onthe administered output medium. One measurement process is used to control each re-cording command for general measurements, except for the recording jobs REC LTGand REC GP, which are implemented in a joint measurement process. For mobile spe-cific maeasurements, there is one process for all commands.

The CP main memory reads the data of the respective counters and outputs it to spec-ified devices. This takes place every fifteen minutes during the active traffic measure-ment intervals, irrespective of the file type.

Three methods are used for collecting and storing traffic data in output files:• Time-controlled measurement with output to individual files.

All traffic measurement data that is generated during the defined time is recorded inthis file. One file is created per traffic measurement job.

• Continuous measurement with output to daily files.Up to seven files, one for each day of the week, can exist simultaneously for eachjob. If the operator does not delete the file after it has been evaluated, it is overwrittenon the same day of the following week.

• Continuous measurement job with output to cyclic files.Data related to each measurement period of 15 minutes is collected and the resultsare written into a separate cyclic file for each started measurement type every 15minutes. Such files can be assigned to any traffic measurement job listed inTab. 1.1.

16 A50016-D1112-G802-1-7618


The files are stored in ASN.1 format on the magnetic disk of the CP. The contents of thedisk file can be displayed at the OMC using the GET TRAFILE command.

1.3.2 Data Transfer and RetrievalAt the end of the measurement job or period, the measurement data can be transferredfrom the CP’s magnetic disk to a magnetic optical disk or a tape. Alternatively, the col-lected data can be transferred via FTAM to an operating system, e.g., Switch Com-mander equipped with the Performance Data Collector (PDC) application. The minimumupload frequency for cyclic files on PDC amounts to 15 minutes. Data is converted toASCII format on the PDC and made available for postprocessing. Siemens offers theSPOTS traffic analysis system, which provides a series of reports that are used to ana-lyze the measurement data and achieve more effective network operation and planning.

1.3.3 Measurement CommandsVarious measurement commands have been designed to specify the groups of mea-surement types and counters to be observed. These commands are used to set up time-dependent traffic data measurements and restrict the amount of data to be measured,which subsequently reduces performance requirements.

Tab. 1.1 gives an overview of the traffic measurement commands integrated in the sys-tem and the references to the chapters in this manual that deal with the respective mea-surement command and describe the provided counters. The measurements areclassified as follows:• Mobile-specific traffic measurement s

These measurements are performed for mobile-specific units, such as MSC, VLR,HLR, AC, IWE, EIR or mobile-specific functions or procedures, such as location up-date, authentication, paging, roaming, and handover.

• General traffic measurementsGeneral traffic measurements register data related to user traffic or signaling trafficin network nodes of the PLMN and of the PSTN/ISDN. In this context, the MSC han-dles user traffic and, consequently, these traffic measurements are relevant in thePLMN. Examples of such events are the start of call setup in a GMSC or a connec-tion with announcement groups.

• CSC-specific measurementsCSC-specific measurements are performed on a combined switching center (CSC),only. They refer to the fixed subscribers and PBX connected to the CSC.

A50016-D1112-G802-1-7618 17


Counter Description

MML command Measurement Chapter

Mobile-specific traffic measurement and monitoring

REC MSC MSC traffic measurement 2 and 3

REC SSERV Traffic measurement for Supplementary Services(SS)

4

REC IWE Traffic measurement in IWE 5

REC VLR VLR traffic measurement 6

REC HLR HLR traffic measurement 7

REC AC AC traffic measurement 8

REC EIR EIR traffic measurement 9

REC LOCAREA Location-area-related traffic measurement 10

REC INTCELL Cell-related traffic measurement 11

ENTR MUSMON Mobile-specific traffic monitoring 12

General traffic measurements

REC TGRP Trunk group traffic measurement 13.2

REC DEST Destination traffic measurement 13.3

REC CP CP traffic measurement 13.4

REC LTG LTG traffic measurement 13.5

REC GP GP traffic measurement 13.6

REC DLU DLU traffic measurement 13.7

REC ANGRP Announcement group traffic measurement 13.8

REC RSU GSM MGW traffic measurements 13.9

REC SCTC SCCP/TCAP traffic measurement 15

CSC-specific traffic measurements

REC PBX PBX traffic measurement 14.2

Tab. 1.1 Traffic measurement commands on the CP

18 A50016-D1112-G802-1-7618


1.4 Traffic and Performance Measurement on the MP PlatformTraffic measurement on the MP platform supplies and outputs counters that register:– Quality of Service, e.g., delays during call set-up, packet throughput, etc.– Traffic levels within the network, including the level of both user traffic and signaling

traffic– Verification of the network configuration and traffic models– Resource access and availability, e.g., begin and end times of service unavailability– Grade of Service, i.e., measurement of successful and unsuccessful events includ-

ing failure causes

The counters are implemented on the MP platform according to the recommendationsof the ITU-T and the 3GPP standard.

1.4.1 Data CollectionOn the MP platform, counters are modeled as attributes of current data subclasses. Acurrent data subclass consists of up to 26 counters and refers to specified measurementobjects (also designated as measurement type or current data object).

Traffic measurement data on the MP platform is processed after the operator has en-tered the respective task to specify one or several measurement objects, define ascheduler and, in case of storage such as a Q3 log file (see chapter 1.4.2), create a Q3output file.

The respective counter values are collected in measurement time periods of 5, 15 or 30minutes for general measurements and 15 minutes for mobile-specific measurementsand are stored on the hard disk of the MP. The measurement results are emitted as re-ports which contain the value of all counters (attributes) being observed during report-ing.

Traffic monitoring on the MP is performed with First and Interval measurements. Thesame measurement objects and counters are used for traffic monitoring and traffic mea-surement. The collected data is, however, handled in a different manner. Every time anymonitored event reaches the threshold value “1”, an alarm notification is generated. Inother words, when the monitored event occurs for the first time during the measurementperiod, an alarm notification is produced and written into the alarm report. This notifica-tion indicates severity, time and further attributes, which enables the alarm to be ana-lyzed. At the end of a monitoring period, an interval report is emitted.

1.4.2 Data Storage, Transfer, and RetrievalMeasurement reports and alarm reports are output on the hard disks of the MP andstored using one of two methods:– SAM file array to be transferred via the FTP interface– Q3 log files to be transferred via the Q3 interface

The storage method used depends on how the collected data is further processed:– If the Performance Data Collector (PDC) is to be used for data transfer and conver-

sion into ASCII, an SAM file array has be used for data storage on the MP. For thispurpose, the pmStorageOnSamar feature has to be activated. This feature enablesperformance gains by saving ASN.1 coded traffic data on the MP hard disk andtransferring it via FTP to a Network Manager, i.e., to Switch Commander equippedwith PDC. The SAM file array is created during system installation. The minimum up-load frequency on PDC amounts to 15 minutes.

A50016-D1112-G802-1-7618 19


Counter Description

– If the Performance Data Collector (PDC) is not to be used or data transfer and con-version Q3 log files can be used for data storage. In this case, the further processingof data depends on project-specific solutions.

Fig. 1.1 gives an overview of the methods to store and transfer traffic data from the MP’shard disk to Switch Commander with or without using the pmStorageOnSamar feature.

Fig. 1.1 Storage of traffic data into Q3 log file or SAMAR on the MP

1.4.3 Measurement TasksOn the MP platform, measurements are administered by means of Q3 tasks. For everymeasurement job, the measured object has to be created and the measurement timehas to be defined in a separate measurement scheduler.

Various measurement tasks have been designed to specify the groups of traffic mea-surement and monitoring objects containing the counters to be observed. Additionaltasks are used to set up the scheduler and – in the case of Q3 logfile storage – definethe output file.

Tab. 1.2 gives an overview of all the traffic measurement commands integrated in thesystem and refers to the chapters of this manual dealing with this measurement and de-scribing the provided counters. The measurements are classified as follows:• SS7 traffic measurement and monitoring (SSNC)

Signaling data traffic applies to SS7 routes to destination point codes, the load onsignaling links, the transfer of message signaling units, and the availability of routingareas. The traffic measurements for this signaling data is relevant for both the PLMNand the PSTN/ISDN.

• MP load measurementMP load measurements are general measurements and register data on user trafficor signaling traffic in network nodes of the PLMN and of the PSTN/ISDN.

• Measurement related to the Iu interfaceMeasurements of the Iu interface are performed for a 2G/3G MSC and 3G MSC.Data concerning the connection to the RNC are registered.

Collection Storage File transfer Retrieval

SAMAR

Common Q3 Log File

Specific Q3 Log File

Scan Reports

QoS Alarms

Scan Reports

QoS Alarms

Scan Reports

QoS Alarms

Raw Data

PerformanceData Collector

Project-specificsolutions

Q3 PresentationService

FTP

Q3

Q3

Q3

Q3

legend: withpmStorageOnSamar feature

FTP

20 A50016-D1112-G802-1-7618


Q3 task Measurement object(current data object)

IDgroup

Chapter

SS7 traffic measurement (SSNC)

CR SIGNEME Net element measurement(switchingElementMeasurement)

202 15.1.1

CR SIGPTME Signaling point utilization measurement(allSignalingPointUtilisationData)

204 15.1.2.1

Obligatory signaling point utilizationmeasurement(oblSignalingPointUtilisationData)

206 15.1.2.2

Network MSU measurement(perNetCounterMSU)

208 15.1.2.3

Signaling point measurement(signalingPointData)

210 15.1.2.4

CR SIGLSME Link set duration measurement(signalingLinkSetDurationData)

212 15.1.3.1

Link set utilization measurement(signalingLinkSetUtilisationData)

234 15.1.3.2

CR SIGDPME Destination point measurement(routeSetInformationData)

214 15.1.4

CR SIGLME Obligatory link duration measurement(oblSignalingLinkDurationData)

216 15.1.5.1

Link duration measurement(all30MinSignalingLinkDurationData)

218 15.1.5.2

Obligatory link utilization measurement(oblSignalingLinkUtilisationData)

220 15.1.5.3

Link utilization measurement(allSignalingLinkUtilisationData)

222 15.1.5.4

Link congestion measurement(signalingLinkCongestionData)

224 15.1.5.5

Obligatory HSLink utilization measurement(saalOblSignallingLinkUtilisationData)

228 15.1.5.6

HSLink utilization measurement(saalAllSignallingLinkUtilisationData)

226 15.1.5.7

CRSIGLSETIPME Signaling linkset IP measurement(ipLinkSetInformationData)

15.1.6

Tab. 1.2 Traffic measurement tasks and objects on the MP

A50016-D1112-G802-1-7618 21


Counter Description

CR SCTPASSOC-ME

SCTP obligatory association utilization mea-surement(oblAssociationUtilizationData)

15.1.7.1

SCTP association utilization measurement(allAssociationUtilizationData)

15.1.7.2

SCTP association duration measurement(allAssociationDurationData)

15.1.7.3

CR SPME SCCP error performance, network-indepen-dent(sccpErrorPerformance)

310 15.2.1.1

SCCP utilization, network-independent(sccpUtilisation)

330 15.2.1.2

SCCP quality of service, network-independent(sccpQualityOfService)

320 15.2.1.3

CR SPMEN SCCP error performance per network(sccpErrorPerformance)

310 15.2.1.1

SCCP utilization per network(sccpUtilization)

330 15.2.1.2

SCCP quality of service per network(sccpQualityOfService)

320 15.2.1.3

CR SPMESSN SCCP error performance per SSN(sccpErrorPerformance)

340 15.2.1.1

CR SPSME SCCP Screening traffic measurement(sccpScreeningTrafficMeas)

370 15.2.2.1

SCCP Screening failures(sccpScreeeningFailures)

360 15.2.2.2

SS7 traffic monitoring (SSNC)

CR SIGFAIME Signaling point measurement(signalingPointData)

15.1.2.4

Link congestion measurement(signalingLinkCongestionData)

15.1.5.5

CR SPMEFAI SCCP error performance per SSN(sccpErrorPerformance)

15.2.1.1

SCCP screening failures(sccpScreeningFailures))

15.2.2.2

CR SPMENFAI SCCP error performance per network(sccpErrorPerformance)

15.2.1.1

MP load measurement


IDgroup

Chapter


22 A50016-D1112-G802-1-7618


CR MPLDME Measurement object for VCPU(vcpuCurrentData)

16.1

Measurement object for MH(mhCurrentData)

16.2

Traffic measurement related to the Iu interface

CR CICGRPME AAL2 overrun error measurement(aal2OverrunCurrentData)

604 17.1.1

AMR underrun error measurement(amrUnderrunCurrentData)

605 17.1.2

SSCS error measurement(sscsErrorCurrentData)

611 17.1.3

Data underrun error measurement(dataUnderrunErrorCurrentData)

608 17.1.4

Iu user plane protocol error measurement(iuUPPProtocolErrorCurrentData)

609 17.1.5

Rate control measurement(rateControlCurrentData)

17.1.6

AMR mode measurement(amrModeCurrentData)

17.1.7

CR AAL2NNIAME AAL2 NNI access control measurement(aal2ControlCurrentData)

603 17.2.1

AAL2 NNI access protocol measurement(aal2ProtocolCurrentData)

612 17.2.2

AAL2 carrier access control measurement(aal2CACurrentData)

17.2.3

CR AAL2VCCME CPS protocol error measurement(cpsProtocolErrorCurrentData)

607 17.2.4

PDU protocol error measurement(PDU14ProtocolErrrorCurrentData)

17.2.5

CR DAAL2SEPME AAL2 destination measurement(aal2DestCurrentData)

17.2.5

CR RANAPDME RANAP destination measurements(ranapProtocolCurrentData)

610 17.3.1

CAM control measurements(camControlCurrentData)

606 17.3.2

CR TCSUBLME ATM Traffic load measurements(atmTrafficLoadCurrentDataExt)

701 17.4.1

Cell level protocol measurement(cellLevelProtocolCurrentData)

601 17.4.2


IDgroup

Chapter


A50016-D1112-G802-1-7618 23


Counter Description

CR VPATHME ATM traffic load measurements(atmTrafficLoadCurrentDataExt)

701 17.4.1

Virtual path and virtual channel performancemeasurements(vpVcPMCurrentData)

602 17.4.3

CR VCHANME ATM traffic load measurements(atmTrafficLoadCurrentDataExt)

701 17.4.1

Virtual path and virtual channel performancemeasurements(vpVcPMCurrentData)

602 17.4.3


IDgroup

Chapter


24 A50016-D1112-G802-1-7618


2 Traffic Measurement in the MSCIn order to measure the traffic in the entire MSC, data can be recorded by counters con-cerning the traffic load, the grade of service, and features. This data is collected duringthe main tasks controlled by the MSC, such as call setup for speech and data, handover,and short message service.

A traffic measurement job in the MSC is started by entering the REC MSC command. Inthis command the following groups of counters can be specified in order to reduce theamount of data collected:• Basic counters (see chapter 2.1)• Handover counters (see chapter 2.2)• Short message service (SMS) counters (see chapter 2.3)• Advanced speech call items (ASCI) counters (see chapter 2.4)

2.1 Basic Data MeasurementBasic counters collect the call setup data for both speech and data calls. This data ap-plies to standard and mobile-specific functions. The measurement job is started by se-lecting the data type GENERAL DATA in the REC MSC command .

This chapter lists all mobile-specific counters that are registered. Because there is alarge number of different counters, they have been grouped on the following pages ac-cording to their distinctive purposes:• Miscellaneous (see chapter 2.1.1)• Time/duration (see chapters 2.1.2 and 2.1.3)• Load and demand (see chapters 2.1.4 and 2.1.5) focussing furthermore on: LTG

pooling (see chapter 2.1.6), Gs interface (see chapter 2.1.7), location services (seechapter 2.1.8)

• Location service counters (see chapter 2.1.9)• Grade of service, focussing on: unsuccessful calls (see chapter 2.1.10), unsuccess-

ful LTG pooling (see chapter 2.1.11), successful call establishments (see chapter2.1.12), answered calls (see chapter 2.1.13)

Traffic types

Most basic counters can be differentiated by traffic type. The different types occur withinthe observed MSC and provide information about the origin and destination of the call.Because different traffic types cause different call handling, there are variations with re-spect to the trigger points for special counters. These differences are considered in thecounter description.

The observed MSC detects whether a call originated in its own area or was transmittedby another exchange. The following traffic types exist:

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:

MORTR: Mobile originating traffic: traffic initiated by a mobile station in thearea of the observed MSC, irrespective of where the destinationis

MICTR: Mobile incoming traffic: mobile traffic that has been directed to theobserved MSC by another exchange

A50016-D1112-G802-1-7618 25


Counter Description

Fig. 2.1 shows the different traffic types within the scope of the observed MSC.

Fig. 2.1 Traffic types in scope of the observed MSC

MTER: Mobile terminating traffic: traffic directed to each mobile stationin the area of the observed MSC

MOUT_PLMN: Mobile originating traffic outgoing to a mobile station of thehome PLMN, wherever the subscriber is roaming

MOUT_NOT_PLMN: Mobile originating traffic outgoing to the PSTN or anotherPLMN

MTRAN: Mobile transit traffic: traffic that has neither been initiated in norwill terminate at the observed MSC

iThese 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).

MICTR

MIC

TR

MO

UT

NO

T P

LMN

MTRAN

MORTR

MORTR

MTER

MTER

BSS

BSS

observed MSC

PSTN PLMN

PLMN

MICTR

MSC

MT

RA

N

MOUT PLMN

MIC

TR

MO

UT

NO

T P

LMN

MO

UT

PLM

N

MORTR: Mobile originating trafficMICTR: Mobile incoming trafficMTER: Mobile terminating trafficMTRAN: Mobile transit traffic

MOUT_PLMN: Mobile (originating) outgoing traffic to home PLMNMOUT_NOT_PLMN: Mobile (originating) outgoing traffic to PSTN or

another PLMN

AccessNetwork

AccessNetwork

26 A50016-D1112-G802-1-7618


2.1.1 Miscellaneous Counters

NUM_RESET

Indicates how many RESET messages have been received.

Trigger: each time RESET is received from the BSC.

NUM_RESET_CIRCUIT

Indicates how many RESET CIRCUIT messages have been received.

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

NUM_SSP_BSSAP

Indicates how many SUBSYSTEM PROHIBITED messages for subsystem BSSAPhave been received.

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

NUM_SIGN_POINT_PROHIB

Indicates how many SIGNALING POINT PROHIBITED messages have been received.

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

NUM_CALLS_REL_BS

Number of calls released because one of the messages referred to in “trigger” has beenreceived.

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

NUM_RECEIVED_OVERLOAD

Indicates how many overload messages have been 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 general congestion primitives (GCP) have been received.

Trigger: each time a GCP is received from the CCS7 link system or message buffer.

NUM_RECEIVED_CIP

Indicates how many congestion indication primitives (CIP) have been received.

Trigger: each time a CIP is received from the CCS7 link.

NUM_RECEIVED_CLASSM_UPD

Indicates how many CLASSMARK UPDATE messages have been received.

Trigger: each time CLASSMARK UPDATE is received.

NUM_TOTAL_START_IMEI_CHECK

Indicates how often IMEI check procedures have been started.

A50016-D1112-G802-1-7618 27


Counter Description

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

NUM_IMEI_CHECK_WHITE

Indicates how often the IMEI check procedure detects white-listed equipment.

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 detects grey-listed equipment.

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 detects black-listed equipment.

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 detects unknown equipment.

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

NUM_IMEI_CHECK_LUP

Indicates how often IMEI checks have been started due to location update.

Trigger: each time CHECK IMEI is sent due to a location update because of an IMSI at-tach or a normal location update.

NUM_IMEI_CHECK_PER_LUP

Indicates how often IMEI checks have been started by a periodic location update.

Trigger: each time CHECK IMEI is sent due to a location update because of a periodiclocation update.

NUM_TONES_DTMF

Indicates how many DTMF tones have been sent by the MS.

Trigger: each time START DTMF is received.

NUM_NO_SPCH_BSSAP_LTG

Indicates how often no free speech channel has been found in the BSSAP LTG.

Trigger: each time an attempt to seize a BSSAP-LTG fails (internal condition; reason:no free speech channel available in this LTG).

NUM_ATT_SCP_DIALOGS_LNP

Indicates how many queries have been initiated to the number portability (NP) databasein the service control point (SCP).

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

NUM_SUCC_SCP_DIALOGS_LNP

Indicates how often the NP database has been successfully queried.

Trigger: each time the SCP sends CONNECT in response to an NP database query con-taining either a location routing number (LRN) or the same number as the one beingsent.

28 A50016-D1112-G802-1-7618


LNP_QUERIES_LRN

Indicates how many LRNs the NP database in the SCP has returned after being queried;i.e., the investigated subscriber number is a ported number.

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 has returned “unknown subscriber” after being interrogatedwith an 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 notbeen created 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., no code point for the LRN concerned exists.

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

NUM_ATT_SCP_DIALOGS_SMS

Indicates how often an attempt to send a short message has successfully invoked an INfunction.

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 INfunction.

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 an LTG other than the one involved in this servicerequest.

CA_VGCS_VBS_EMLPP

Indicates 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.

A50016-D1112-G802-1-7618 29


Counter Description

2.1.2 Time/Duration Counters: Part 1

TIME_CALL_SET_U_SERV

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

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 a 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

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

Duration of the paging procedure (unit 50ms). Only successful paging procedures areincluded, but no timeout cases.

Trigger:– Starts each time PAGING is sent;– Stops each time PAGING RESPONSE is received.

2.1.3 Time/Duration Counters: Part 2

TRAFFIC_VOLUME

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 timeout.– MOUT_NOT_PLMN / MOUT_PLMN: starts with proper result of digit analysis after

interrogation; stops when RELEASE COMPLETE is sent or received, or with an un-successful call attempt before IAM is sent.

– MTRAN: starts with proper result of the digit analysis; stops when RELEASE COM-PLETE is received.

30 A50016-D1112-G802-1-7618


D_CONV_SPEECH_SERV

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 a call is released.– MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops

each time a call is released.

D_CONVERSATION

Duration of conversation for MTRAN.

Trigger:– Starts each time ANSWER is received;– Stops each time a call is released.

D_CONV_DATACDA_ANA

Duration of conversation for data CDA (circuit duplex asynchronous) analog services.

D_CONV_DATACDS_ANA

Duration of conversation for data CDS (circuit duplex synchronous) analog services.

Trigger: start and stop depend on the message of the respective traffic type:– MTER: starts each time CONNECT is received; stops each time the call is released.– MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops

each time the call is released.

D_CONV_DATACDA_DIG

Duration of conversation for data CDA digital services.



D_CONV_ALTFAXSP

Duration of conversation for alternate speech/facsimile services.

Trigger: start and stop depend on the message of the respective traffic type:– MTER: starts each time CONNECT is received; stops each time a call is released.– MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; starts

each time ANSWER is received;

D_CONV_FAX3

Duration of conversation for the automatic facsimile group 3 service.



D_CONV_DED_PAD

Duration of conversation for dedicated PAD (packet assembler/disassembler) accessfor MOUT_NOT_PLMN.

A50016-D1112-G802-1-7618 31


Counter Description

Trigger:– Starts each time ANSWER is received;– Stops each time a call is released.

D_CONV_DATACDS_DIG

Duration of conversation for data CDS digital services.



D_ALT_SPEECH_DATA

Duration of conversation for alternate speech/data or speech followed by data services.



2.1.4 Load and Demand Counters: Part 1

CALL_ATTEMPTS

Indicates how many call attempts have taken place, independently of the received BSor TS (except for MOUT_PLMN, MOUT_NOT_PLMN).

Trigger: each time the respective message is involved:– MORTR: on receipt of each CM SERVICE REQUEST with SERVICE TYPE = mobile

originating call or establishment of all emergency call attempts. Short message ser-vice and SS activation are not included.

– MICTR: each time IAM is received (all call attempts).– MTER: each time PAGING is sent. The exact trigger condition is the detection of an

MSRN of the home MSC by digit processing; this usually causes a paging messageto be sent (all call attempts). The following cases are exceptions: busy MS, invoca-tion of service call wait and overload related to the A interface.

– MOUT_PLMN, MOUT_NOT_PLMN: Receipt of SET UP and digit analysis results inthis traffic type (speech call attempts only).

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

CALL_ATT_MS_OWN_MSC_NO

Number of incoming call attempts leading MS in own MSC to MTER without performinginterrogation for MICTR.

Trigger: each time IAM (includes MSRN) is received and call leads directly (without in-terrogation) to an MTER call attempt.

CALL_ATT_PURE_TRANSIT

Number of incoming call attempts leading to transit without performing interrogation forMICTR.

Trigger: each time IAM is received and call leads directly (without interrogation) to anMTRANS call attempt.

32 A50016-D1112-G802-1-7618


DATACDA_ANA_ATTEMPTS

Number of call attempts 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 an MSRN of the home MSC

by digit processing; this usually causes a paging message to be sent. The followingcases are exceptions: busy MS, invocation of service call wait and overload relatedto the A interface.

– MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter includetraffic without interrogation unless international interrogation is applied.

DATACDA_DIG_ATTEMPTS

Number of call attempts for data CDA digital services.



– MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter includetraffic without interrogation unless international interrogation is applied.

ALTFAXSP_CALL_ATTEMPTS

Number of call attempts for alternate speech/facsimile services.




FAX3_CALL_ATTEMPTS

Number of call attempts for the automatic facsimile group 3 service for MTER,MOUT_PLMN, MOUT_NOT_PLMN.

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

DED_PAD_ATTEMPTS

Indicates 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_ATTEMPTS

Number of call attempts for data CDS analog services.



A50016-D1112-G802-1-7618 33


Counter Description


DATACDS_DIG_ATTEMPTS

Number of call attempts for data CDS digital services.




ALT_SPEECH_DATA_ATTEMPTS

Number of call attempts for alternate speech/data or speech followed by data services.




EMERGENCY_TS12_ATTEMPTS

Number of emergency call attempts (TS12) for MORTR.

Trigger: each time CM SERVICE REQUEST indicating an emergency call is received.

MSC_MSC_HO_CALL_ATTEMPTS

Number of call attempts caused by inter MSC handover for MTER (MSC-B is the homeMSC).

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

STARTED_PAGING_PROC

Number of initial paging procedures that have been started for MTER.

Trigger: each time PAGING is sent.

STARTED_PAG_RETRY_PROC

Number of paging retry procedures that have been started for MTER.

Trigger: each time PAGING is sent after the first expiry of the paging timer.

STARTED_INTERROGATIONS

Number of interrogations to another MS and MICTR. that have been started for MORTR.

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

STARTED_INT_SER_CODE_DIG

Number of interrogations including service code digits to another MS and MICTR thathave been started for MORTR.

34 A50016-D1112-G802-1-7618


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.

SET_UP_SERV_CODE

Number of received setup messages containing short code digits or service codes forMORTR.

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_REQ

Number of generated traffic channel requests.

Trigger: each time ASSIGNMENT REQUEST is sent to the BSC for:– MORTR: after the previous receipt of CM SERVICE REQUEST.– MTER: after previous paging.– MOUT_PLMN / MOUT_NOT_PLMN: the counter is only incremented in the case of

rerouting, e.g., COC failure.

ACTIVE_QUEUING

Number of calls where queuing was active for MORTR, MTER, MOUT_PLMN,MOUT_NOT_PLMN.

Trigger: each time QUEUING INDICATION is received from the BSC. The counter is up-dated when ASSIGNMENT COMPLETE or RELEASE COMPLETE is received for thecall.

IMEI_CHECKS

Number of IMEI checks caused by call setup for MORTR, MTER.

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

IN_ATTEMPTS

Number of call attempts invoking IN functions for MORTR, MICTR.

Trigger: each time interworking to an IN service control point (SCP) is started as a resultof digit evaluation (e.g., dial an IN directory number) being part of a call setup.

IN_TRANS

Number of transaction attempts invoking IN functionality, whereby no interworking withthe IN SCP is started (e.g., televoting with service filtering so that precounting is done inthe SSP), for MORTR and MICTR.

Trigger: each time interworking to IN SCP is started for a non call-related transaction.

OACSU_ATTEMPTS

Number of attempted calls with OACSU for MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time SET UP is received and OACSU treatment is initiated for the propertraffic type.

CCBS

The 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.

A50016-D1112-G802-1-7618 35


Counter Description

Trigger: each time a CCBS REQUEST activating CCBS for:– MORTR: is sent by the MSC-A.– MTER: is received from the MSC-A

CCBS_RECALL

Once 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 for:– MORTR: is received from the MSC-A.– MTER: is sent by the MSC-B.

SUCC_ORMMC

Number of successful optimal routing mobile-to-mobile attempts.

Trigger: each time an SRI with interrogation type basic and OR interrogation is sent toHLR, and “Roaming number” is included in the SRI ack.

SUCC_ORECF

Number of successful optimal routing early call forwarding attempts.

Trigger: each time an SRI with interrogation type basic and OR interrogation indicator issent to the HLR, and the “Forwarded-to-number” is included in SRI ack, and the flagATD_MOBILE_DATA.OR_INDICATION is set directly before sending SEIZURE_CBT.


SERVICE_REQ_SCI_INDEPENDENT

Number of call-independent services requested via SCI.

Trigger: each time CM SERVICE REQUEST is received for SS activation without beinginvolved in a call.

SERVICE_REQ_SCI_CALL_REL

Number of services requested via SCI during a parallel call.

Trigger: each time CM SERVICE REQUEST is received for SS during a call.

SERVICE_REQ_LOC_UPD

Number of received service requests for a location update.

Trigger: each time COMPLETE L3 INFO with LOCATION UPDATE REQUEST is re-ceived.

RECVD_POS_ACK_FROM_GSMSCF

Number of positive acknowledgements sent by the GSM service control function.

Trigger: each time a message containing a positive acknowledgement is received.

SENT_NOTIF_SS_INV_TO_GSMSCF

Indicates how often the GSM service control function has been requested to invoke asupplementary service.

Trigger: each time SS INVOCATION NOTIFY is sent to the GSM service control func-tion.

36 A50016-D1112-G802-1-7618


2.1.6 Load and Demand Counters: LTG PoolingThe following counters collect data concerning the use of LTG pools. LTG pooling pro-vides 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:– 6 kbit/s results from channel coding TCH/F4.8– 12 kbit/s results from channel coding TCH/F9.6– 14.5 kbit/s results from channel coding TCH/F14.4

• The high-speed circuit-switched data (HSCSD) facility enables data to be transport-ed by the PLMN using 2 traffic channels on the radio interface for the same data call.This facility only applies to 9.6 and 14.4 user data rates for BS20. The correspondingrates at the radio interface are 12 kbit/s,14.5 kbit/s, and 14.5 kbit/s only.

CA_SPEECH_HR

Number of attempts for speech calls for which a trunk providing the proper channel at-tributes has been seized.

Trigger: each time SET UP C containing the channel attributes required to seize theproper trunk is sent for HR (V1 or V3).

CA_SPEECH_FR

Number of attempts for speech calls for which a trunk providing the proper channel at-tributes has been seized.

Trigger: each time SET UP C containing the channel attributes required to seize theproper trunk is sent for FR (V1 or V2 or V3).

CA_DATA_FR

Number of attempts for data calls for which a trunk providing the proper channel at-tributes for specific rates on the radio interface has been seized.

Trigger: each time SET UP C containing the channel attributes required to seize theproper LTG is sent for 12 kbit/s, 14.5 kbit/s, and 14.5 kbit/s only.

CA_DATA_HR

Number of attempts for data calls for which a trunk providing the proper channel at-tributes for specific half rates on the radio interface has been seized.

Trigger: each time SET UP C containing the channel attributes required to seize theproper LTG is sent for 6 kbit/s or 3.6 kbit/s.

CA_HSCSD_2FR

Number of attempts for high-speed data calls for which a trunk providing 2 channels withthe proper attributes is seized.

Trigger: each time SET UP C containing the channel attributes required to seize theproper LTG is sent for 12 kbit/s, 14.5 kbit/s, and 14.5 kbit/s only.

A50016-D1112-G802-1-7618 37


Counter Description

2.1.7 Load and Demand Counters: Gs Interface

TIME_COM_LUP_SERV

Accumulated time to provide service combined location update being handled via theGs interface.

Trigger:– Starts each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received;– Stops each time LOCATION UPDATE RESPONSE or REJECT is sent.

SERVICE_REQ_COM_LUP

Number of received service requests for a combined location update.

Trigger: each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received viathe Gs interface.

NUM_COM_LUP_CONTRIB

Number of combined location updates which caused the “combined location update ser-vice time”.

TV_SUCC_COM_PAGING

Duration of successfully completed paging procedures (in 50 ms units).

Trigger:– Starts each time PAGING is sent;– Stops each time PAGING RESPONSE is received.

CA_COM_PAGING

Number of started combined paging procedures.

Trigger: each time PAGING is sent on both the A interface and the Gs interface.

CA_COM_PAGING_RETRY

Indicates 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_A

Number of started paging procedures on the A interface after an unsuccessful attempton the Gs interface.

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

CCU_COM_PAGING

Number of calls terminated because the combined paging procedure was unsuccessful.

Trigger: each time the connection is released because the paging timer expired for thesecond time.

CCS_COM_PAGING_RES

Number of successfully completed combined paging procedures.

38 A50016-D1112-G802-1-7618


Trigger: each time PAGING RESPONSE is received from the BSC.

2.1.8 Load and Demand Counters: 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 a call triggers 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_ATT

Number of attempts for allocating an ESRK.

Trigger: each time the digit evaluation results into an emergency call.

SUCC_ESRK_ALLOC_ATT

Number of successful attempts allocating an ESRK.

Trigger: each time an ESRK is found after the digit evaluation.

LOCATION_ATTEMPTS

Number of location attempts.

Trigger: each time DT1:PERFORM LCS is sent to the LTG.

UNS_LOC_ATT_CONGESTION

Number of unsuccessful location attempts due to congestion.

Trigger: each time DT1:PERFORM LCS RESP is received indicating unsuccessful po-sitioning.

SUCC_LOC_ATT

Total number of successful location attempts.

Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning.

SUCC_LOC_ATT_TA

Number of successful location attempts as a result of using the “time advance” position-ing method.


SUCC_LOC_ATT_TOA

Number of successful location attempts as a result of using the “time of arrival” position-ing method.


SUCC_LOC_ATT_MOB_ASSIST_E_OTD

Number of successful location attempts as a result of using the “enhanced observedtime difference” positioning method (MS-assisted calculation).

A50016-D1112-G802-1-7618 39


Counter Description


SUCC_LOC_ATT_MOB_BASED_E_OTD

Number of successful location attempts as a result of using the “enhanced observedtime difference” positioning method (MS-based calculation).


SUCC_LOC_ATT_MOB_ASSIST_GPS

Number of successful location attempts as a result of using the “global positioning sys-tem” (MS-assisted calculation).


SUCC_LOC_ATT_MOB_BASED_GPS

Number of successful location attempts as a result of using the “global positioning sys-tem” (MS-based calculation).


SUCC_LOC_ATT_CONV_GPS

Number of successful location attempts as a result of using the conventional “global po-sitioning system”.


SUCC_LOC_ATT_UNKNOWN_POS

Number of successful location attempts as a result of using an unknown positioningmethod.


POS_SEND_TO_GMLC

Number of attempts for transferring both MS position estimate and emergency call orig-ination to the gateway mobile location center.

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

SUCC_POS_SEND_TO_GMLC

Number of successful transfers of the MS position estimate and the emergency call orig-ination to the gateway mobile location center.

Trigger: each time SUBSCRIBER LOCATION REPORT ACK is received after the reportis sent.

2.1.9 Location Service CountersLocation Services (LCS) may be considered as a network provided enabling technologythat is used by various possible location applications, so-called LCS clients, to enable

40 A50016-D1112-G802-1-7618


the position of an MS or an UE in a PLMN. It can be used, for example, for regional reg-ulatory requirements or for commercial purposes. Therefore, the LCS feature is a net-work feature and not a supplementary service. The LCS applications or LCS clients maybe service provider specific.

A MT-LR (Mobile Terminating Location Request) enables an external LCS client (e.g.,fleet management center) to request the location of a specific identified MS or UE.

Location Service Counters are recorded if a measurement of the complete MSC data isperformed. The following counters are provided.

TOTAL_NUM_MT_LR

Indicates how many MT-LRs have been requested by LCS client.

Trigger: each time a Provide Subscriber Location Report message is received by the CPfrom the GMLC for an MT-LR.

MT_LR_ATT

Indicates how many MT-LR attempts (request sent to the BSC or RNC) have been per-formed.

Trigger: each time CP sends PERFORM_LCS to LTG when GMLC has requested a anMT-LR.

SUCC_MT_LR

Indicates how many successful MT-LRs (location returned to GMLC) have been per-formed.

Trigger: each time CP receives successful PERFORM_LCS_RESPONSE from the LTGand Provide Subscriber Location Report Acknowledgement is sent to the GMLC for anMT-LR.

NUM_MT_LR_BLOCK_PRIV

Indicates how many MT-LRs have been blocked by privacy checks prior to any MS no-tification.

Trigger: each time MT_LR requested by GMLC to MSC is blocked because of MS sub-scriber’s privacy. This does not include MT-LR rejected by an MS having notification andverification.

NUM_MT_LR_OVRD_ATT

Indicates how many MT-LR, with location attempt due to LCS client override, have beenperformed.

Trigger: each time a GMLC sends a Provide Subscriber Location Report to the MSC withthe override indication set, and the GMLC is in the same country as the VMSC, and theLCS client type is either emergency services or lawful interception and the override in-dicator is enabled as a PLMN option.

NUM_MT_LR_NO_PAG_RESP

Indicates how many MT-LR attempt have been rejected because the MS target is un-known or there is no paging response.

Trigger: each time, during an MT_LR, a paging response is received with a failure or ifno paging response is received.

A50016-D1112-G802-1-7618 41


Counter Description

CA_ORMMC_OR_ORECF

Number of optimal routing mobile-to-mobile calls or optimal routing early call forwardingattempts.

Trigger: each time SEND ROUTING INFO with interrogation type basic and OR interro-gation indicator is sent to the HLR.

NUM_MT_LR_BLOCK_REJ

Number of MT-LRs blocked due to MS notification and verification.

Trigger: each time a GMLC requests an MT-LR from the MSC, and the MT-LR is blockeddue to MS notification and verification (MT-LR is rejected by the MS).

MO_LR_SELF_LOC

Number of MO-LR requests by location request.

Trigger: each time an MS requests an MO-LR by location request.

MO_LR_ASSIST_DATA

Number of MO-LR requests by assistance data request.

Trigger: each time an MS requests an MO-LR by assistance data request.

MO_LR_DEC_KEYS

Number of MO-LR requests by deciphering keys request.

Trigger: each time an MS requests an MO-LR by deciphering keys request.

MO_LR_SELF_LOC_ATT

Number of MO-LR attempts by location request.

Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MShas requested an MO-LR by location request.

MO_LR_ASSIST_DATA_ATT

Number of MO-LR attempts by assistance data request.

Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MShas requested an MO-LR by assistance data request.

MO_LR_DEC_KEYS_ATT

Number of MO-LR attempts by deciphering keys request.

Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MShas requested an MO-LR by deciphering keys request.

SUCC_MO_LR_SELF_LOC

Number of successful MO-LRs by location request.

Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in theCP from the GP for an MO-LR by location request.

SUCC_MO_LR_ASSIST_DATA

Number of successful MO-LRs by assistance data request.

Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in theCP from the GP for an MO-LR by assistance data request.

42 A50016-D1112-G802-1-7618


SUCC_MO_LR_DEC_KEYS

Number of successful MO-LRs by deciphering keys request.

Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in theCP from the GP for an MO-LR by deciphering keys request.

NI_LR

Indicates the total number of NI-LR requests.

Trigger: each time a NI-LR is detected in the MSC for an emergency call.

NI_LR_ATT

Number of NI-LR attempts.

Trigger: each time the DT1:PERFORM_LCS message is sent to the GP for an emergen-cy call.

SUCC_NI_LR

Number of successful NI-LRs.

Trigger: each time a successful MAP Subscriber Location Report or MAP Provide Sub-scriber Location Report is sent to the GMLC for an emergency call.

MO_LR_TTTP

Indicates the total number of MO-LR requests by category (location request, assistancedata request, deciphering keys request, and transfer to third party).

Trigger: each time an MS has requested an MO-LR with transfer to third party viaDT1:BEGIN_LCS.

MO_LR_TTTP_ATT

Number of MO-LR attempts (request send to the BSC or RNC) by category (location re-quest, assistance data request, deciphering keys request, and transfer to third party).

Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MShas requested an MO-LR with transfer to third party.

MO_LR_TTTP_GMLC_ATT

Indicates the total number of MO-LR attempts sent to GMLC with transfer to third party.

Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in theCP from the GP, and the MAP: Subscriber Location Report is sent to the GMLC for anMO-LR request with transfer to third party.

SUCC_MO_LR_TTTP

Number of successful MO-LR by category (location request, assistance data request,deciphering keys request, and transfer to third party).

Trigger: each time successful Subscriber_Location_Report_Ack is received in the CPfrom the GMLC for an MO-LR request with transfer to third party.

2.1.10 Grade of Service Counters: Unsuccessful Calls

REL_BEFORE_ACM_MICTR

Number of calls released in the forward direction before ACM is sent for MICTR.

A50016-D1112-G802-1-7618 43


Counter Description

Trigger: each time a call is released in the 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 be-

fore PAGING after receipt of IAM).

UNS_PAGING

Number of incoming calls terminated due to an unsuccessful paging procedure.

Trigger: each time a connection is released by the second expiry of the paging timer.

UNS_REQ_DEST_ERROR

Number of calls terminated because the requested destination was unknown, blockedor could not be charged.

Trigger: each time the respective message is involved:– MORTR: on receipt of internal release (CP) after digit analysis failed.– MTER: on receipt of RELEASE COMPLETE (cause: destination is unknown,

blocked or could not be zoned).– MOUT_PLMN, MOUT_NOT_PLMN: on receipt of ISUP message RELEASE COM-

PLETE / UNSUCCESSFUL BACKWARD MESSAGE after digit analysis (cause:destination is unknown, blocked or could not be zoned).

– MTRAN: on receipt of RELEASE COMPLETE/UBM (cause: destination is unknown,blocked or could not be zoned).

UNS_TECHN_FAULT

Number of calls terminated due to technical faults in the home MSC. For MORTR, MIC-TR, MTER, MOUT_PLMN, MOUT_NOT_PLMN, MTRAN.

Trigger: each time the MSC causes a technical fault (e.g., software fault, plausibilitycheck, hardware fault).

UNS_SERV_CHECK

Number of calls terminated due to negative service facility checks or negative compati-bility checks.

Trigger: each time the relevant message with the proper cause, for:– MORTR: RELEASE COMPLETE (e.g., service not implemented) is sent to the BSS.– MICTR: TC-U-ERROR (BS or TS not provisioned, facility not supported, forwarding

violation) is received from the HLR in response to SEND ROUTING INFO.– MTER: RELEASE COMPLETE (e.g., service not implemented) is sent to the previ-

ous exchange or the BSS.– MOUT_PLMN / MOUT_NOT_PLMN: RELEASE COMPLETE (e.g., service not im-

plemented) is sent to the BSS.

UNS_MS_BLOCKED

Number of calls terminated because the subscriber was blocked by operator determinedbarring, by administration, or by SS. Because there are unblockable destinations, thedestination must be determined if the described barring conditions are fulfilled.

Trigger: each time a call is released for:– MORTR: due to barring of outgoing calls (calling subscriber) or of incoming calls

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

44 A50016-D1112-G802-1-7618


UNS_MS_BUSY

Number of calls terminated because the requested subscriber was busy.

Trigger: each time the relevant message (including RELEASE messages) with reason“subscriber busy”:– MTER: UBM is sent to the previous exchange.– MOUT_PLMN, MOUT_NOT_PLMN: RELEASE UBM is received from the following

exchange.

UNS_CONGESTION

Number of calls terminated due to (trunk) congestion in the home MSC.

Trigger: each time trunk seizure is not successful due to congestion. For example for:– MORTR: BSS trunk– MTER: BSS trunk on the B side.– MOUT_PLMN / MOUT_NOT_PLMN: trunk on the B side.– MTRAN: trunk on the B side.

UNS_SN_CONGESTION

Number of calls terminated due to switching network (SN) congestion. For MTER,MTRAN, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time a failure during SN through-connection occurs.

UNS_LACK_IWE

Number of calls terminated due to lack of IWEs. For MORTR, MTER, MOUT_PLMN,MOUT_NOT_PLMN.

Trigger: each time the seizure of IWE is not successful due to unavailable IWE.

UNS_SECURITY_FAIL

Number of calls terminated due to authentication/security failure for MORTR and MTER.

Trigger: each time AUTHENTICATION REJECT is sent to the BSS.

UNS_LINK_FAIL

Number of calls terminated due to failure/congestion/overload on associated CCS7 sig-naling system links. For MORTR, MICTR, MTER, MOUT_PLMN, MOUT_NOT_PLMN,MTRAN.

Trigger: each time a call is released due to CCS7 failure (e.g., on receipt of ”STOPTRAFFIC”).

UNS_PROTO_ERROR

Number of calls terminated due to protocol errors. For MORTR, MICTR MTER,MOUT_PLMN, MOUT_NOT_PLMN, MTRAN.

Trigger: each time a protocol error is detected but the call cannot be identified.

UNS_NETW_MANAGEMENT

Number of calls terminated due to network management activities for MOUT_PLMN,MOUT_NOT_PLMN, MTRAN.

Trigger: each time trunk resource management detects a network management event.

A50016-D1112-G802-1-7618 45


Counter Description

UNS_OVERLOAD

Number of calls terminated due to overload prevention for MORTR, MICTR, MTER.

Trigger: each time a call is internally released due to an overload situation.

UNS_BS_REASON

Number of calls terminated during setup due to BSS/radio-related reasons.

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

UNS_BLACK_LIST

Number of calls terminated because the IMEI check indicates black-listed equipment.For MTER, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time a result indicating “black list” is received from the EIR in response toCHECK IMEI.

UNS_IMEI_UNKNOWN

Number of calls terminated because the IMEI check indicates unknown equipment, forMTER, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time a result indicating “IMEI unknown” is received from the EIR in re-sponse to CHECK IMEI.

UNS_MS_DETACH

Number of calls terminated because the called MS was detached/absent.

Trigger: each time a detached or absent subscriber is detected for:– 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_REJECT

Number of calls terminated because the CUG has been rejected.

Trigger: the proper CUG error cause is reported by– MORTR: sending RELEASE COMPLETE to the BSS.– MICTR: sending RELEASE to the previous MSC.– MOUT_PLMN, MOUT_NOT_PLMN: receiving RELEASE/UBM from subsequent

MSC.

UNS_INTERROGATION

Number of pure interrogation failures, such as “no answer from HLR” for MORTR orMICTR.

Trigger: each time a dialog error cause is received from the HLR for interrogation or theHLR does not respond to SEND_ROUTING_INFO.

IN_OVERLOAD

Number of IN calls that have been released due to SCP overload or automatic call gap-ping initiated by SCP for MORTR and MICTR.

46 A50016-D1112-G802-1-7618


Trigger: each time call setup with prompted call handling is released due to IN overloadprevention measures.

IN_NO_ANSW_SCP

Number of IN calls that are released due to missing answer from SCP for MORTR andMICTR.

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.

IN_ERROR_SCP

Number of IN calls that have been released because SCP sent unsuitable information(e.g., new call numbers sent from the SCP cannot be recognized in the MSC, data isunreadable). For MORTR and MICTR.

Trigger: each time a connection is released because the IN SCP data received is insuf-ficient to establish the call.

IN_SERV_CHECK

Number of IN calls that have been released because the required IN service is not ac-tive, e.g., not allowed for the subscriber or not supported by SCP. For MORTR and MIC-TR.

Trigger: each time the SCP releases a call due to service/facility checks.

IN_ERROR_DEST

Number of IN calls that have been released because the called IN number is unknown.For MORTR and MICTR.

Trigger: each time the SCP releases a call because the called number is unknown.

CCU_DATA_HR_6K

Number of failed call establishments for a traffic channel with HR data (6, 3.6 kbit/s).

2.1.11 Grade of Service Counters: Unsuccessful LTG Pooling

CCU_SPEECH_HR

Indicates how many attempts for speech calls have been terminated because a trunkproviding the proper channel attributes could not be seized.

Trigger: each time the trunk cannot be seized on sending SET UP C with channel at-tributes for HR (V1 or V3)

CCU_SPEECH_FR

Indicates how many attempts for speech calls have been terminated because a trunkproviding the proper channel attributes could not be seized.

Trigger: each time the trunk cannot be seized on sending SET UP C with channel at-tributes for:– HR (V1 or V3)– FR (V1 or V2 or V3)

A50016-D1112-G802-1-7618 47


Counter Description

CCU_DATA_FR

Indicates how many attempts for data calls have been terminated because a trunk pro-viding the proper channel attributes for specific rates on the radio interface could not beseized.

Trigger: each time the LTG cannot be seized on sending SET UP C with channel at-tributes for:– 12K– 14.5K– 14.5K only

CCU_HSCSD_2FR

Indicates 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 cannot be seized on sending SET UP C with channel at-tributes for:– 12 only– 14.5K– 14.5K only

2.1.12 Grade of Service Counters: Successful Call Establishment

RECEIVED_PAG_RESP

Number of paging response messages received for MTER.

Trigger: each time PAGING RESPONSE is received from the BSC.

CALL_TCH_ALLOCATION

Number of calls with successfully completed traffic channel (TCH) allocation for MOR-TR, MTERMOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time ASSIGNMENT COMPLETE is received.

TS11_EMERG_CALL_TCH_ALL

Number of outgoing emergency calls with successfully completed traffic channel alloca-tion for emergency calling (TS11).

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

TS12_EMERG_CALL_TCH_ALL

Number of outgoing emergency calls with successfully completed traffic channel alloca-tion for emergency calling (TS12).

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

COMPL_SCI_INDEPENDENT

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.

48 A50016-D1112-G802-1-7618


COMPL_SCI_CALL_REL

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_INTERROGATIONS

Number of calls with successfully completed interrogations for MORTR and MICTR.

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

COMPL_INTERROGATIONS_SC

Number of calls with successfully completed interrogations containing service codes forMORTR and MICTR.

Trigger: each time TC-RESULT is received in response to SEND ROUTING INFO con-taining short-codes or short-service-codes.

CALL_INT_MS_OWN_MSC

Number of calls with successfully completed interrogations leading to MS in the homeMSC for MORTR and MICTR.

Trigger: each time a positive result of SEND ROUTING INFO is received from the HLRand the MSRN evaluation results in paging.

CALL_INT_MS_FOREIGN_MSC

Number of call attempts for which no paging is performed after evaluating the MSRN forMORTR and MICTR.

Trigger: each time a positive result of SEND ROUTING INFO is received from the HLRand the MSRN evaluation does not result in paging.

SN_THROUGH_CONNECTIONS

Number of successful call attempts.

Trigger: each time– MTER: CALL CONFIRMED is received for:– MOUT_PLMN, MOUT_NOT_PLMN: IAM is sent to the next exchange.– MTRAN: IAM is sent to the next exchange.

CALL_REL_EXCHANGE

Number of calls terminated by the previous exchange for MTER, and by the followingexchange for MOUT_PLMN, MOUT_NOT_PLMN, and by the previous/following ex-change for MTRAN.

Trigger: each time RELEASE is received:– MTER: indicating clear forward.– MOUT_PLMN, 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_ALERT

Number of calls released before alerting the destination.

A50016-D1112-G802-1-7618 49


Counter Description

Trigger: each time, on receipt of:– MTER: RELEASE COMPLETE before alerting signal is received.– MTRAN: RELEASE (clear backward or clear forward) before alert signal is received.– MORTR, MICTR, MOUT_PLMN, MOUT_NOT_PLMN.

CALL_REL_ALERT

Number of calls released before CONNECT is received for MTER and during alertingfor MTRAN.

Trigger: each time, on receipt of:– MTER: RELEASE COMPLETE after alerting is sent and before CONNECT is re-

ceived.– MTRAN: RELEASE (clear backward or clear forward) before receipt of ANSWER

and after receipt of ACM.

CALL_TIOUT_ALERT

Number of calls released by alert supervision timeout for MOUT_PLMN,MOUT_NOT_PLMN.

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

CALL_WHITE_LIST

Number of successful calls with white-listed equipment for MORTR and MTER.

Trigger: each time TC-RESULT (white list IMEI) is received from the EIR in response tocheck IMEI at call setup.

CALL_GREY_LIST

Number of successful calls with grey-listed equipment for MORTR and MTER.

Trigger: each time TC-RESULT (grey list IMEI) is received from the EIR in response tocheck IMEI at call setup.

CALL_END_CALL_FORW

Number of calls ended due to start of call forwarding for MORTR, MICTR, MTER,MOUT_PLMN, MOUT_NOT_PLMN, and MTRAN.

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

CALL_END_CF_NOT_REACH

Number of calls that have been ended because call forwarding (CF) is not available forMTER.

Trigger: each time “CF for MTER not reachable” is invoked and the previous call setupis ended.

CALL_END_CF_MS_BUSY

Number of calls that have been ended because the MS busy and call forwarding is notpossible for MTER.

Trigger: each time “CF for MS busy” is invoked and the previous call setup is ended.

50 A50016-D1112-G802-1-7618


CALL_END_CF_NO_REPLY

Number of calls that have been ended because there is no reply and call forwarding isnot possible for MTER.

Trigger: each time “CF for No Reply” is invoked and the previous call setup is ended.

CALL_END_CALL_FORW_OR

Number of calls ended due to start of optimal routing late call forwarding for MORTR,MICTR, MTER, MOUT_PLMN, MOUT_NOT_PLMN, and MTRAN.

Trigger: each time an optimal routing late call forwarding is performed successfully.

IN_REROUTE

Number of calls ended due to rerouting by IN for MORTR and MICTR.

Trigger: each time an answer from SCP is received and the call is rerouted to a new des-tination included in the SCP response.

ANN_NO_ERROR

Indicates how many calls have been intercepted to an announcement without a knowncall release reason for MORTR, MICTR, and MTER.

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).

ANN_ERROR

Indicates how many calls have been intercepted to an announcement after a call releas-ing error for MORTR, MICTR, and MTER.

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).

REROUTE_BEFORE_SN

Number of calls rerouted before SN through-connection. For MORTR, MICTR, MTER,MOUT_PLMN, MOUT_NOT_PLMN, and MTRAN.

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 set-up.

REROUTE_AFTER_SN

Number of calls rerouted after SN through-connection For MTER, MOUT_PLMN,MOUT_NOT_PLMN, and MTRAN.

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.

SN_REROUTE_CALL

Number of through-connections in the switching network (SN) for rerouted calls. ForMTER, MOUT_PLMN, MOUT_NOT_PLMN, and MTRAN.

Trigger: each time a through-connection of the routed call setup is successful. Analog:SN THROUGH CONNECTIONS for routed connections changed to a new destination.

A50016-D1112-G802-1-7618 51


Counter Description

CALL_TRANSFER

Indicates how many call transfers have been completed by new resource configurationestablishing for MTER and MTRAN.

Trigger: each time RELEASE or FACILITY with return-result is sent to the BSS in re-sponse to INVOKE SS.

OACSU_RELSUB

Number of calls released by subscribers during OACSU treatment for MOUT_PLMN,MOUT_NOT_PLMN.

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.

OACSU_TCH_ALLOC

Number of call attempts with OACSU and successful traffic channel allocation forMOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time ASSIGNMENT COMPLETE is received for a MOC with OACSUtreatment.

CALL_CCBS

Number of successful CCBS call attempts.

Trigger: each time IAM for:– MORTR: is sent to destination MSC (MSC-B) after previous receipt of REMOTE

USER FREE.– MTER: is received from the originating MSC (MSC-A) after previously sent RE-

MOTE USER FREE.

2.1.13 Grade of Service Counters: Answered Calls

SPEECH_CALLS_WITH_ANSWER

Indicates how many speech calls have been answered.

Trigger: each time the connection is released in response to the receipt of the respectivemessage:– MTER: CONNECT– MOUT_PLMN, MOUT_NOT_PLMN: ANM

CALLS_WITH_ANSWER

Number of answered calls for MTRAN.

Trigger: each time the connection is released in response to the receipt of ANM.

TS11_EMERG_WITH_ANSWER

Number of answered emergency calls (TS11).

Trigger: each time the connection has actually been released in response to the receiptof ANM.

TS12_EMERG_WITH_ANSWER

Number of answered emergency calls (TS12).

52 A50016-D1112-G802-1-7618



DATACDA_ANA_WITH_ANSWER

Number of answered data calls for CDA analog services.


DATACDA_DIG_WITH_ANSWER

Number of answered data calls for CDA digital services.


ALTFAXSP_WITH_ANSWER

Number of answered data calls with alternation from speech to facsimile.

Trigger: each time the connection has actually been released in response to the receiptof the respective message:– MTER: CONNECT– MOUT_PLMN, MOUT_NOT_PLMN: ANM

FAX3_WITH_ANSWER

Number of answered data calls for automatic facsimile group 3.


DED_PAD_WITH_ANSWER

Number of answered calls for dedicated PAD CDA services.


DATACDS_ANA_WITH_ANSWER

Number of answered data calls for CDS analog services.


DATACDS_DIG_WITH_ANSWER

Number of answered data calls for CDS digital services.


A50016-D1112-G802-1-7618 53


Counter Description

ALT_SPEECH_DATA_ANSWER

Number of answered alternate speech/data or speech followed by data calls.


BS_REL_WITH_ANSWER

Number of answered calls terminated due to BSS/radio-related reasons (e.g., loss ofconnection) for MTER, MOUT_PLMN, MOUT_NOT_PLMN.

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

REROUTE_NEW_DEST

Number of answered calls that have been rerouted to a new call destination (e.g., by INSCP Interworking). For MTER, MOUT_PLMN, MOUT_NOT_PLMN, MTRAN.

Trigger: each time ANSWER/CONNECT are received.

OACSU_WITH_ANSWER

Number of answered calls with OACSU for MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time ANM is received for a MOC with OACSU treatment:

INC_HO_WITH_ANSWER

Number of answered signals related to the number of incoming handover for MTER(MSC-B is the home MSC).

Trigger: each time RELEASE is received if an MSC_MSC HO has been performed, ifthe current MSC is the MSC-B, and if the call disposition indicates that the call was an-swered.

TOTAL_CALLS_WITH_ANSWER

Total number of calls that have been answered. For MTER, MOUT_PLMN,MOUT_NOT_PLMN, MORTR, MICTR.

54 A50016-D1112-G802-1-7618


2.2 Handover Data MeasurementHandover counters have been implemented to measure handover traffic in the MSC.Note that these counters only apply to handovers controlled by the MSC. Counters forBSC-controlled handover are defined in the BSC. Because the MSC has no knowledgeabout BSC-controlled handover attempts (only successful handovers are reported), theinclusion of HANDOVER PERFORMED increases the handover success rate. Becausethe receipt of this message indicates a BSC-controlled handover, it is not used to triggerthe HO_PERFORMED counter (see chapter 2.2.2.)

The measurement job is started by selecting the HANDOVER data type in the RECMSC command.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Load and demand (see chapter 2.2.1)• Grade of service, focussing on:

– Handover establishments (see chapter 2.2.2)– Successfully completed handovers (see chapter 2.2.3).

• Inter System Handover from GSM to UMTS (see chapter 2.2.4)

2.2.1 Load and Demand Counters

HANDOVER_ATTEMPTS

Number of handover requests.

Trigger: each time HANDOVER REQUIRED is received without SDCCH indication.

CA_HANDOVER_SDCCH

Number of handover attempts using a stand alone dedicated control channel (applies toSMS, SCI and USSD).

Trigger: each time HANDOVER REQUIRED with SDCCH indication.

HANDOVER_DATA_CALL_ATTEMPTS

Number of handover requests for data calls.

Trigger: each time HANDOVER REQUIRED is received, data call active.

HANDOVER_UPLINK_QUALITY

Number of handover requests due to uplink quality.

Trigger: each time HANDOVER REQUIRED is received, uplink quality.

HANDOVER_UPLINK_STRENGTH

Number of handover requests due to uplink strength.

Trigger: each time HANDOVER REQUIRED is received, uplink strength.

HANDOVER_DOWNLINK_QUALITY

Number of handover requests due to downlink quality.

Trigger: each time HANDOVER REQUIRED is received, downlink quality.

HANDOVER_DOWNLINK_STRENGTH

Number of handover requests due to downlink strength.

A50016-D1112-G802-1-7618 55


Counter Description

Trigger: each time HANDOVER REQUIRED is received, downlink strength.

HANDOVER_DISTANCE

Number of handover requests due to distance.

Trigger: each time HANDOVER REQUIRED is received, distance.

HANDOVER_BETTER_CELL

Number of handover requests due to better cell.

Trigger: each time HANDOVER REQUIRED is received, better cell.

HANDOVER_RESP_TO_MSC

Number of handover requests due to response to MSC invocation.

Trigger: each time HANDOVER REQUIRED, response to MSC invocation.

HANDOVER_OP_MAINT_INT

Number of handover requests caused by O&M intervention.

Trigger: each time HANDOVER REQUIRED is received, O&M intervention.

HANDOVER_DIRECTED_RETRY

Number of handover requests due to directed retry.

Trigger: each time HANDOVER REQUIRED is received, directed retry.

HANDOVER_MSC_MSC_OG_ATTEMPTS

Number of outgoing requests for inter-MSC handover (home MSC = MSC-A).

Trigger: each time PERFORM HANDOVER is sent to the MSC-B.

HANDOVER_MSC_MSC_OG_DAT_ATT

Number of outgoing requests for inter-MSC handover for data calls (home MSC = MSC-A).

Trigger: each time PERFORM HANDOVER is sent to the MSC-B during active data call.

HANDOVER_MSC_MSC_IC_ATTEMPTS

Number of incoming requests for inter-MSC handover (home MSC = MSC-B).

Trigger: each time HANDOVER REQUIRED is received from the MSC-A.

SUBSEQ_MSC_MSC_HO_MSCB

Number of requests for subsequent inter-MSC handover (home MSC = MSC-B).

Trigger: each time PERFORM SUBSEQUENT HANDOVER is sent to the MSC-A.

SUBSEQ_MSC_MSC_HO_MSCA

Number of requests for subsequent inter-MSC handover (home MSC = MSC-A).

Trigger: each time PERFORM SUBSEQUENT HANDOVER is received from the MSC-B.

56 A50016-D1112-G802-1-7618


2.2.2 Grade of Service Counters: Handover Establishment

HO_PERFORMED

Number of handovers autonomously performed by the BSS.

Trigger: each time the MSC-A receives HANDOVER PERFORMED from the BSS.

HO_CONFERENCE

Number of conferences built up during all handover attempts.

Trigger: each time a handover for a speech call is performed, as follows:– for intra-MSC handover: MSC sends HANDOVER COMMAND to BSC– for inter-MSC handover: MSC-A sends IAM to MSC-B/MSC-B’– for inter-MSC handover back to the MSC-A: result (PREPARE SUBSEQUENT HAN-

DOVER) is sent to the MSC-B.

HO_OLD_CELL

Number of handovers completed in the old cell.

Trigger: each time HANDOVER COMMAND is sent to the BSS by the MSC-A.

CCS_SDCCH_ALLOC

Number of successful allocations of stand alone dedicated control channels.

Trigger: each time SEIZ FOR HO ACK is received.

2.2.3 Grade of Service Counters: Successful Completed Handovers

SUCC_COMPLETED_HO

Number of successfully completed intra-MSC handovers.

Trigger: each time the MSC receives HANDOVER COMPLETE from the BSS.

SUCC_COMPL_HO_SDCCH

Number of successfully completed intra-MSC handovers using stand alone dedicatedcontrol channels.

Trigger: each time HO EXECUTED is received.

SUCC_COMPL_HO_DATA_CALLS

Number of successfully completed intra-MSC controlled handovers for data calls.

Trigger: each time the MSC-B receives HANDOVER COMPLETE from the BSS duringactive data call.

SUCC_MSC_MSC_HO_MSCA

Number of successful inter-MSC handovers where the home MSC acts as the MSC-A.

Trigger: each time HANDOVER COMPLETE is received for handover back to the MSC-A, and each time SEND END SIGNAL is received from the MSC-B for handover to theMSC-B.

SUCC_DATA_MSC_MSC_HO_MSCA

Number of successful inter-MSC handovers for data calls where the home MSC acts asthe MSC-A.

A50016-D1112-G802-1-7618 57


Counter Description

Trigger: each time SEND END SIGNAL is received from the MSC-B during active datacall.

SUCC_MSC_MSC_HO_MSCB

Number of successful inter-MSC handovers where the home MSC acts as the MSC-B/MSC-B'.

Trigger: each time SEND END SIGNAL is sent to the MSC-A.

SUCC_SUBSEQ_MSC_MSC_HO_MSCB

Number of successful subsequent inter-MSC handovers.

Trigger: each time END SIGNAL is received in response to the handover command.

SUCC_HO_SEC_MSC_MSC_HO_MSCB

Number of intra-MSC handovers after previous inter-MSC handover (home MSC =MSC-B).

Trigger: each time HANDOVER COMPLETE is received from the BSS for intra-MSChandover in the MSC-B.

2.2.4 Counters for Inter System HandoverIn the circuit-switched domain a number of counters have been defined in order to mea-sure the activity of inter system handover from GSM to UMTS. Some of these countersare measured in the 2G MSC, and others in the 3G MSC, as described in this chapter.

U_INTER_MSC_MSC_HO_ATT_GSM_UMTS_OG

Number of inter MSC inter system handover OG attempts from GSM to UMTS (mea-sured in the 2G MSC).

U_INTRA_HANDOVER_GSM_TO_UMTS

Number of successful intra MSC inter system handovers from GSM to UMTS.

U_INTER_HANDOVER_GSM_TO_UMTS

Number of successful inter MSC inter system handovers from GSM to UMTS (measuredin the 2G MSCA).

U_SUCC_INTER_MSC_HO_GSM_UMTS_MSCB

Number of successful inter MSC inter system handovers from GSM to UMTS (measuredin the 3G MSCB).

U_SUCC_INTER_MSC_HO_UMTS_GSM_MSCB

Number of successful inter MSC inter system handovers from UMTS to GSM (measuredin the 3G MSCB).

U_INTER_HO_ATT_UMTS_TO_GSM

Number of inter system handover attempts from UMTS to GSM.

U_INTER_MSC_MSC_HO_ATT_UMTS_GSM_IC

Number of inter MSC inter system handover IC attempts from UMTS to GSM (measuredin the 3G MSC). In MSC-A the A interface is used, in MSC-B the Iu interface.

58 A50016-D1112-G802-1-7618


U_INTER_MSC_MSC_HO_ATT_UMTS_GSM_OG

Number of inter MSC inter system handover OG attempts from UMTS to GSM (mea-sured in the 2G MSC).

2.3 Short Message Service Data MeasurementFor the measurement of traffic related to the short message service (SMS), a number ofSMS counters are implemented in the MSC. The measurement job is started by select-ing the SMS data type in the REC MSC command.

Because there is a large number of various counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Load and demand (see chapter 2.3.1)• Grade of service, focussing on:

– Successful short message services (see chapter 2.3.2),– Unsuccessful short message services (see chapter 2.3.2).


SMS_INC_ATTEMPTS

Number of short messages received from the SMS gateway (home MSC = servingMSC).

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

SMS_OTG_ATTEMPTS

Number of short messages sent to the SMS gateway (home MSC=serving MSC).

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

SMS_INC_PARALLEL

Number of parallel SMS-MT invocations.

Trigger: each time FORWARD SHORT MESSAGE is received from the SMS gateway.The setup of SMS-MT is a parallel transaction (e.g., to a call).

SMS_OTG_PARALLEL

Number of parallel SMS-MO invocations.

Trigger: each time FORWARD SHORT MESSAGE is sent to the SMS gateway.The set-up of SMS-MO is a parallel transaction.

SMS_INC_PARALLEL_MEM_AV_INV

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_ATTEMPTS

Number of received CM SERVICE REQUEST messages for SMS.

Trigger: each time CM SERVICE REQUEST including service type SMS is receivedfrom the MS.

A50016-D1112-G802-1-7618 59


Counter Description

RECEIVE_RP_DATA_ATTEMPTS

Number of short messages that have been received from the MS.

Trigger: each time RP DATA is received from the MS.

SEND_RP_DATA_ATTEMPTS

Number of SMS messages that are sent to the MS.

Trigger: each time RP DATA is sent to the MS.

RECEIVE_RP_SMMA_ATTEMPTS

Number of SMS-MA delivery attempts received from mobile stations.

Trigger: each time CP_DATA (RP_ERROR) is received from the MS.

SMS_OTG_FALLBACK

Number of SMS-MO fallbacks from MAP V3/V2 to MAP V2/V1.

Trigger: each time an ABORT message is received from the SMSC in response to anSMS-MO delivery attempt that results in fallback.

2.3.2 Grade of Service Counters: Successful Services

SUCC_SMS_INC

Number of successfully acknowledged short messages that have been received fromthe SMS gateway (home MSC = serving MSC).

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

SUCC_SMS_OTG

Number of successfully acknowledged short messages that are sent to the SMS gate-way (home MSC = serving MSC).

Trigger: each time FORWARD SHORT MESSAGE ACK is received by the SMS gate-way.

SUCC_SMS_OTG_IN

Number of short messages with CAMEL phase 3 treatment delivered successfully to theSMSC.

Trigger: each time there is a successful CAMEL Phase 3 MO SMS IN.

SUCC_SMS_RECEIVE_RP_ACK

Number of mobile terminated short messages acknowledged by the MS.

Trigger: each time RP ACK is received by the MS.

SUCC_SMS_SEND_RP_ACKS

Number of sent mobile originated short messages acknowledged by the MS.

Trigger: each time RP ACK is sent to the MS.

SUCC_MULT_SMS_OTG

Number of successfully acknowledged sent multiple short messages.

60 A50016-D1112-G802-1-7618


Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is received asacknowledgement from the SMS gateway for multiple short message transfer. Note: thefirst short message is acknowledged as SUCCESSFUL SHORT MESSAGE OUTGO-ING.

SUCC_MULT_SMS_INC

Number of successfully acknowledged received multiple short messages.

Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is sent as ac-knowledgement to the SMS gateway for multiple short message transfer. Note: lastshort message is acknowledged as SUCCESSFUL SHORT MESSAGE OUTGOING.

SUCC_SMS_SEND_SMSMA_RP_ACK

Number of SMS-MA acknowledgments sent to the mobile station.

Trigger: each time ACK is sent to the MS with SMS-MA.

2.3.3 Grade of Service Counters: Unsuccessful Services

UNS_SMS_INC_ABSENT_MS

Number of short messages that is received from the SMS gateway due to absent sub-scriber (home MSC = serving MSC).

Trigger: each time FORWARD SHORT MESSAGE ERROR indicating “absent subscrib-er” is sent to the SMS gateway.

UNS_SMS_OTG_UNIDENT_MS

Number of short messages that is sent to the SMS gateway due to unidentified subscrib-er (home MSC = serving MSC).

Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating “unidentifiedsubscriber” is received from the SMS gateway.

UNS_SMS_OTG_NO_FACILITY

Number of short messages that is sent to the SMS gateway due to facility not being sup-ported (home MSC = serving MSC).

Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating “facility not sup-ported” is received from the SMS gateway.

UNS_SMS_INC_NO_FACILITY

Number of short messages that is received from the SMS gateway due to facility not be-ing supported (home MSC = serving MSC).

Trigger: each time FORWARD SHORT MESSAGE ERROR indicating “facility not sup-ported” is received from the SMS gateway.

UNS_SMS_INC_DELIVERY_FAIL

Number of short messages that is received from the SMS gateway due to short mes-sage delivery failure (home MSC = serving MSC).

Trigger: each time FORWARD SHORT MESSAGE ERROR is sent to the SMS gatewaywith either of the following error codes: unknown SC, SC congestion, invalid SMS ad-dress, subscriber not SC subscriber.

A50016-D1112-G802-1-7618 61


Counter Description

UNS_SMS_OTG_DELIVERY_FAIL

Number of short messages that has been sent to the SMS gateway due to SM deliveryfailure (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_MEMORY

Number of mobile terminated short messages that has been refused due to memory ca-pacity exceeded.

Trigger: each time an RP ERROR is received from the MS for this reason.

UNS_SMS_SEND_RP_UNASSIGN_NUM

Number of mobile originated short messages that has been refused due to unassignednumber.

Trigger: each time an RP ERROR indicating unassigned number is sent to the MS.

UNS_SMS_SEND_RP_SUB_ERR

Number of mobile originated short messages that has been refused due to subscriberdata (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_ERR

Number of mobile originated short messages that has been refused due to facility errors(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_ERR

Number of mobile terminated short messages that has been refused due to protocol ormessage-related errors.

Trigger: each time RP ERROR with the proper reason is received from the MS.

UNS_SMS_SEND_RP_PROT_ERR

Number of mobile originated short messages that has been refused due to protocol ormessage-related errors.

Trigger: each time RP ERROR with the proper reason is sent to the MS.

UNS_SMS_INC_PARALLEL_MS_STATE

Number of unsuccessful parallel SMS MT message transfers due to MS transactionstate.

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_OTG

Number of multiple short messages sent that were handled unsuccessfully.

62 A50016-D1112-G802-1-7618


Trigger: each time a FORWARD SHORT MESSAGE ERROR is received from the SMSgateway or an RP ERROR is sent to the MS for multiple short messages.

UNS_MULT_SMS_INC

Number of multiple SMS messages received that were handled unsuccessfully.

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 short messages.

UNS_SMS_SEND_NET_OUT_OF_ORDER

Number of SMS-MO delivery attempts that failed due to “network problems”.

Trigger: each time CP_DATA(RP_ERROR) is sent to the MS with RP_CAUSE=38.

UNS_SMS_SEND_SMSC_CONGESTION

Number of SMS-MO delivery attempts that failed due to SMSC congestion.


UNS_SMS_SEND_MES_TRAN_REJ_SMSC

Number of SMS-MO delivery attempts that failed due to “short message transfer reject-ed by the SMSC”.


UNS_SMS_SEND_SMSMA_RP_ERROR

Number of CP_DATA(RP_ERROR) messages sent to mobile stations during SMS-MA.

Trigger: each time CP_DATA (RP_ERROR) is sent to the MS during SMS-MA with anyRP_CAUSE value.

SMS_OTG_ABORTED_BY_SMSC

Number of unsuccessful SMS-MO attempts aborted by the SMSC.

Trigger: each time an ABORT message is received from the SMSC in response to aMAP V2 SMS-MO delivery attempt that does not result in fallback.

SMS_OTG_ERROR

Number of unsuccessful SMS-MO attempts due to returnError sent by the SMSC.

Trigger: each time a Return Error component is received from the SMSC.

UNS_SMS_INC_DEREGISTERED_MS

Number of returnError components with errorCode="absentSubscriber” due to IMSI-de-tached sent to the SMSC.

Trigger: each time the error code “absent Subscriber” due to IMSI-detached is sent tothe SMSC.

UNS_SMS_INC_SUBBUSY_FAIL

Number of returnError components with errorCode="subscriberBusyForSMSMT" sentto the SMSC.

Trigger: each time errorCode="subscriberBusyForSMSMT" is sent to the SMSC.

A50016-D1112-G802-1-7618 63


Counter Description

2.4 ASCI Service Data MeasurementAdvanced speech call items (ASCI) provides for services to a GSM subscriber to estab-lish voice group calls (VGCs) and to use voice broadcasting (VB). By just calling a singlenumber, particular subscribers from a given geographical area can be grouped in a par-allel connection.– VGC is initiated by a dispatcher for a speech conversation between one talking and

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

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 preemption of ongoing calls. With respect to these services, a group callregister (GCR) is implemented where the relevant attributes are assigned by registra-tion, 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.

The measurement job is started by selecting the ASCI data type in the REC MSC com-mand. The following counters are provided.

TV_VGCS

Sum of holding times (i.e., traffic volume in sec.) as a result of voice group calls.

Trigger: each time a CM SERVICE REQUEST with service type VGCS is received.

TV_VBS

Sum of holding times (i.e., traffic volume in sec.) as a result of broadcasting.

Trigger: each time CM SERVICE REQUEST with service type VBS is received.

CA_SERV_SUB_VGCS

Indicates how often a service subscriber has attempted to originate a voice group call.

Trigger: each time CM SERVICE REQUEST with service type VGCS is received.

CA_SERV_SUB_VBS

Indicates how often a service subscriber has attempted to originate a voice broadcast.

Trigger: each time CM SERVICE REQUEST with service type VBS is received.

CCU_OVERLOAD_INIT_VGCS_VBS

Indicates how many attempts for the VGCS or the VBS were rejected due to MSC over-load.

Trigger: each time CM SERVICE REJECT is sent on receiving a request for VGC or VBservice.

CA_MOB_DISPATCH_VGCS_VBS

Indicates how many attempts have been initiated by a mobile dispatcher for a VG or VBcall.

64 A50016-D1112-G802-1-7618


Trigger: each time digit translation detects a VG or VB call on receiving SETUP.

CA_FIX_DISPATCH_VGCS_VBS

Indicates how many attempts have been initiated by a dispatcher from the fixed networkfor a VG or VB call.

Trigger: each time digit translation detects a VG or VB call on receiving DIGIT BLOCK C.

NUM_ATRIB_REQ_GCR

Number of requests to the GCR for retrieval of the appropriate attributes.

Trigger: each time VGCS ATR REQ is sent to the GCR on receiving SETUP.

NUM_ATRIB_RESPONSE_GCR

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_VBS

Indicates how often a dispatcher, on originating a group call, has been reconnected toa recently created group connection (included in the group again).

Trigger: each time VGCS ATR RES with busy indication is received.

CCU_SERV_SUB_BUSY_VGCS_VBS

Indicates how often a group call from a service subscriber has been terminated unsuc-cessfully because the group was already involved in a call.

Trigger: each time TERMINATION indicating busy is sent to the service subscriber onreceiving VGCS ATR RES.

NUM_CELL_SETUP_RESP_GCR

Number of radio cells involved in the group call setup.

Trigger: each time a setup request is received for each cell indicated in VGCS ATR RE-SPONSE from the GCR.

NUM_DISPATCH_SETUP_RESP_GCR

Number of dispatchers involved in the group call setup.

Trigger: each time a setup request is received for each dispatcher indicated in VGCSATR RESPONSE from the GCR.

NUM_VGCS_VBS_SETUP_BSC_REQ

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_REQ

Number of traffic channel requests to the cells intended for VG calls or broadcasting.

Trigger: each time VGCS/VBS ASS REQ is sent.

NUM_VGCS_VBS_SETUP_BSC_ACK

Number of acknowledgements received from the BSCs to establish a group call.

A50016-D1112-G802-1-7618 65


Counter Description

Trigger: each time VGCS/VBS SETUP ACK is received.

NUM_VGCS_VBS_TCH_ALLOC_ACK

Number of acknowledgements received from the cells to establish a group call.

Trigger: each time VGCS/VBS ASS COM is received.

NUM_SUCC_SETUP_DISPVGCS_VBS

Indicates how often a group call to a dispatcher has been 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_VBS

Number of group call attempts being terminated unsuccessfully due to overload aftertraffic attributes have been retrieved from GCR.

Trigger: each time the ASCI configuration is released due to an MSC internal overload.

CCU_LACK_CONF_UNIT

Number of group call attempts being terminated unsuccessfully due to lack of ASCI con-ference resources in the MSC.

Trigger: each time the ASCI configuration is released due to a lack of resources in theMSC.

CC_ANSW_VGCS_VBS

Indicates how many voice group calls and voice broadcasting events have been an-swered.

Trigger: each time ASCI CONNECT is sent to the conference LTG.

NUM_VGCS_TALK_REL

Indicates 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_REQ

Indicates how often the MSC has been requested for a talker function.

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

NUM_VGCS_TALK_ACK

Indicates how often a request for a talker function has been allocated to the new speak-er.

Trigger: each time the MSC sends UPLINK REQUEST ACK.

NUM_VGCS_TALK_REJECT

Indicates how many requests for a talker function have been rejected because the newspeaker has already been selected in another BSC.

Trigger: each time the MSC sends UPLINK REJECT COMMAND.

66 A50016-D1112-G802-1-7618


NUM_VGCS_TALK_CONFIRM

Indicates 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_RMSC

Indicates 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_RMSC

Indicates 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_GCNR

Indicates how often a group call number has been requested.

Trigger: each time an internal procedure for allocating a GC NR is invoked on receivingPREPARE GROUP CALL.

NUM_ALLOC_GCNR

Indicates how often a group call number has been allocated.

Trigger: each time the relay MSC successfully allocates a GC NR on receiving PRE-PARE GROUP CALL.

NUM_SEND_GCNR_TO_AMSC

Indicates how often a group call number has been sent to the anchor MSC.

Trigger: each time the relay MSC sends PREPARE GROUP CALL ACK.

NUM_RECVD_GCNR_IN_AMSC

Indicates 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_TERM

Indicates 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 on receiving DIGITBLOCK C.

SUCC_LINK_SETUP_TO_RMSC

Indicates how often links have been successfully set up to a relay MSC.

Trigger: each time the anchor MSC receives SENT GROUP CALL END SIGNAL.

SERV_SUB_VGCS_ATTEMPTS_IN_RMSC

Indicates how often service subscribers have initiated voice group calls in the relayMSC.

Trigger: each time ROUTE TO AMSC is received from the group call register.

A50016-D1112-G802-1-7618 67


Counter Description

SERV_SUB_VBS_ATTEMPTS_IN_RMSC

Indicates how often service subscribers have initiated voice broadcasting in the relayMSC.

Trigger: each time ROUTE TO AMSC is received from the group call register.

CA_MOB_SERV_SUB_IN_RMSC

Indicates how often the anchor MSC has received call attempts initiated by service sub-scribers in the relay MSC.

Trigger: each time digit analysis triggers a group call setup on receiving DIGIT BLOCKC.

CA_PTP_EMLPP

Indicates 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 re-

ceived.– MTC: PAGING is sent.

ATTEMPTS_TRFO_BICC

Number of calls where the TrFO is attempted at the BICC side.

Trigger:– MOC: after O:APM when the TrFO Check is done (first AddReq from BICC side).– MTC: after R: AppTransp when the TrFO Check is done (first AddReq from BICC

side).

ATTEMPTS_TRFO_RANAP

Number of calls where the TrFO is attempted at the RANAP side.

Trigger:– MOC: after R: AppTransp when the TrFO Check is done (first AddReq from RANAP

side).– MTC: after R: Continuity when the TrFO Check is done (first AddReq from RANAP

side).

SUCC_TRFO_BICC

Number of successful calls with TrFO at the BICC side

Trigger:– MOC: after O:APM and TrFO Check in case that TrFO possible or in case it is known

that TrFO was possible just after receiving AddResp from the MGW– MTC: after R: AppTransp and TrFO Check in case that TrFO was possible, after re-

ceiving AddResp from the MGW Idem.

SUCC_TRFO_RANAP

Number of successful calls with TrFO at RANAP side.

Trigger:– MOC: after R: AppTransp and TrFO Check in case that TrFO possible or eventually

just after receiving DT1:RABAssRsp if it is possible to know that TrFO was possible.

68 A50016-D1112-G802-1-7618


For a MOC call in R: Continuity there will be a plausibility check so BICC may knowthe status of RANAP LTG (Bearer Up and TrFO not possible or Bearer down andTrFO possible)

– MTC: after R: Continuity and TrFO Check in case that TrFO possible. idem.

CODEC_MODIFICATION_ATTEMPTS

Number of Codec Modification attempts.

Trigger: When APM (Modify Codec) is received (respectively sent if more than one MSCis involved in the call).

SUCCESSFUL_CODEC_MODIFICATIONS

Number of successful Codec modifications

Trigger: When APM (Codec Modified) is sent (respectively received if more than oneMSC is involved in the call).

CCU_CONGESTION_ATM

Calls released due to Bearer initiated release with Mc General Cause 2 or 3.

CCU_PROTOCOL_ERROR_BCF

Calls released because of protocol errors detected in the BCF (e.g. error codes400,401,422,442,443,444,445,446,447).

CCU_PROTOCOL_ERROR_CSF

Calls released because of protocol errors in the CSF.

CCU_TECHN_ERROR_BCF

Calls released due to bearer initiated release with Mc General Cause other than 1, 2, 3and 6.

CCU_UNSUPPORTED_BCF

Calls released due to Bearer initiated release with Mc General Cause 6.

RESERVE_COUNTER

RESERVE_COUNTER_2 to RESERVE_COUNTER_5

A50016-D1112-G802-1-7618 69


Counter Description

70 A50016-D1112-G802-1-7618


3 UMTS Traffic Measurement in a 3G MSCThe traffic measurements for circuit-switched calls in an MSC are expanded for UMTSin order to have an overview of the total performance of the switch.

The concept for traffic measurement as it exists in the GSM network is not changed forthe UMTS network. This means that all existing (global) MSC counters are updated aswell for GSM as for UMTS-calls.

In addition to the existing set of counters, a new set of counters (= variants of the globalcounters) is defined for UMTS specific calls.

When an UMTS circuit-switched call is setup, the global counters and the UMTScounters are both updated for this call.

For each call, an internal indication allows to distinguish if the call is an UMTS or a GSMone.

Traffic measurement is started in the 3G MSC by entering the REC MSC command . Inthis command the following groups of counters to be recorded can be specified in orderto reduce the amount of collected data:• Basic counters (see chapter 3.1)• Handover counters (see chapter 3.2)• Short message service (SMS) counters (see chapter 3.3)

3.1 Basic Data MeasurementThis chapter lists all mobile-specific counters that are registered in addition to the GSMcounters (see chapter 2.1).

The description of the UMTS basic data is divided into the same parts as the descriptionof GSM basic data.

The measurement job is started by selecting the GENERAL data type in the REC MSCcommand . Because there is a large number of different counters, they have beengrouped on the following pages according to their distinctive purposes:• Load and demand (see chapters 3.1.2 and 3.1.3)• Grade of service, focussing on: unsuccessful calls (see chapter 3.1.4), successful

call establishments (see chapter 3.1.5), answered calls (see chapter 3.1.6)

Traffic types

UMTS counters are only provided for the traffic types: MORTR, MOUT_PLMN,MOUT_NOT_PLMN and MTER. The traffic types and the relation between them is ex-plained in chapter 2.1 and presented in Fig. 4.1.

3.1.1 Time/Duration Counters

U_TRAFFIC_VOLUME

Indicates the sum of all holding times for UMTS calls.

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.– MTER: starts each time PAGING is sent; stops each time RELEASE COMPLETE is

received, or at paging timeout.

A50016-D1112-G802-1-7618 71


Counter Description

– MOUT_PLMN, MOUT_NOT_PLMN: starts with proper result of digit analysis afterinterrogation; stops when RELEASE COMPLETE is sent or received, or with an un-successful call attempt before IAM is sent.

U_D_CONV_SPEECH_SERV

Indicates duration of conversation for speech services for UMTS.

Trigger: start and stop depend on the message of the respective UMTS traffic type:– MTER: starts each time CONNECT is received; stops each time a call is released.– MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops



U_CALL_ATTEMPTS

Indicates how many UMTS call attempts have taken place, independently of the re-ceived BS or TS (except for MOUT_PLMN, MOUT_NOT_PLMN).

Trigger: each time the respective message is involved, this for UMTS call:– MORTR: each time CM SERVICE REQUEST with SERVICE TYPE = mobile origi-

nating call or establishment of all emergency call attempts is received. Short mes-sage service and SS activation are not included.

– MTER: each time PAGING is sent. The exact trigger condition is the detection of aMSRN of the home MSC by digit processing; this usually causes a paging messageto be sent). The following cases are exceptions: busy UE, invocation of service callwait and overload related to Iu interface.

– MOUT_PLMN, MOUT_NOT_PLMN: each time SET UP is received and digit analy-sis results in this traffic type (speech call attempts only).

U_EMERGENCY_TS12_ATTEMPTS

Number of emergency call attempts (TS12) for UMTS MORTR.

Trigger: each time CM SERVICE REQUEST indicating an emergency UMTS call is re-ceived.

U_GEN_TRAFF_CHAN_REQ

Number of generated traffic channel requests for UMTS call.

Trigger: each time ASSIGNMENT REQUEST is sent to the RNC for:– MORTR: after the previous receipt of CM SERVICE REQUEST.– MTER: after previous paging.– MOUT_PLMN, MOUT_NOT_PLMN: the counter is only incremented in the case of

rerouting, e.g., COC failure.


U_NUM_LUP_CONTRIB

Number of location updates contributing to “location update service time” for UE.

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

72 A50016-D1112-G802-1-7618


U_SERVICE_REQ_LOC_UPD

Indicates how often service requests for location update have been received for UE.

Trigger: each time COMPLETE L3 INFO with LOCATION UPDATE REQUEST is re-ceived for UE.

3.1.4 Grade of Service Counters: Unsuccessful Calls

U_UNS_MS_BUSY

Indicates how many UMTS calls are terminated because the requested subscriber is al-ready busy.

Trigger: each time the relevant message (including RELEASE messages) with reason“subscriber busy” for:– MTER: UBM is sent to the previous exchange for UMTS call.– MOUT_PLMN, MOUT_NOT_PLMN: RELEASE UBM is received from the following

exchange for UMTS call.

U_UNS_UTRAN_REASON

Number of UMTS calls terminated because of a radio resources problem.

Trigger:– MORTR– MTER– MOUT_PLMN, MOUT_NOT_PLMN

U_UNS_CONGESTION

Indicates how many UMTS calls are terminated due to (trunk) congestion in the homeUMSC.

Trigger: each time trunk seizure is not successful for UMTS call due to congestion:– MORTR: UTRAN trunk– MTER: UTRAN trunk at B side.– MOUT_PLMN, MOUT_NOT_PLMN: trunk at B side.

U_UNS_RNC_REASON

Number of calls terminated during setup due to UTRAN/radio-related reasons.

Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PRO-HIBITED, RESET, RESET CIRCUIT is received for UMTS call– MORTR: from the UTRAN before digit analysis is performed.– MTER: before digit analysis is performed.– MOUT_PLMN, MOUT_NOT_PLMN: after digit analysis has been performed.

3.1.5 Grade of Service Counters: Successful Call Establishment

U_RECEIVED_PAG_RESP

Number of received paging response messages for MTER.

Trigger: each time PAGING RESPONSE is received from the RNC.

A50016-D1112-G802-1-7618 73


Counter Description

U_CALL_TCH_ALLOCATION

Number of UMTS calls with successfully completed traffic channel (TCH) allocation. ForMORTR, MTER, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time ASSIGNMENT COMPLETE is received.

U_TS11_EMERG_CALL_TCH_ALL

Number of UMTS outgoing emergency calls with successfully completed traffic channelallocation for emergency calling (TS11).

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

U_TS12_EMERG_CALL_TCH_ALL

Number of UMTS outgoing emergency calls with successfully completed traffic channelallocation for emergency calling (TS12).

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

U_SN_THROUGH_CONNECTIONS

Number of successful UMTS call attempts.

Trigger: each time– MTER: CALL CONFIRMED is received for UMTS call.– MOUT_PLMN, MOUT_NOT_PLMN: IAM is sent to the next exchange for UMTS call.

U_CALL_REL_BEF_ALERT

Indicates how many UMTS calls have been released before alerting the destination forMTER, MORTR, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time RELEASE COMPLETE is received for a UMTS call before the alert-ing signal is received.

U_CALL_REL_ALERT

Indicates how many UMTS calls have been released before CONNECT is received forMTER, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time RELEASE COMPLETE is received after the alert signal is sent andbefore CONNECT is received, for a UMTS call.

U_CALL_TI_OUT_ALERT

Indicates how many UMTS calls have been released by alert supervision timeout forMOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time RELEASE COMPLETE is received due to alert supervision timeout(internal event in MSC), for UMTS call:

U_CALL_END_CALL_FORW

Indicates how many UMTS calls are ended due to start of call forwarding. For MORTR,MTER, MOUT_PLMN, MOUT_NOT_PLMN.

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

U_CALL_END_CF_MS_BUSY

Number of UMTS calls that are ended due to start of CF on MS busy. For MTER.

74 A50016-D1112-G802-1-7618


Trigger: each time CF for MS busy is invoked and old call setup is thereby ended.

U_CALL_END_CF_NO_REPLY

Number of UMTS calls that are ended due to start of CF No Reply. For MTER.

Trigger: each time CF for No Reply is invoked and old call setup is thereby ended.

U_CALL_END_CALL_FORW_OR

Indicates how many UMTS calls are ended due to start of optimal routing of late call for-warding. For MORTR, MTERMOUT_PLMN, MTERMOUT_NOT_PLMN

Trigger: each time an optimal routing late call forwarding is performed successfully.

3.1.6 Grade of Service Counters: Answered Calls

U_SPEECH_CALLS_WITH_ANSWER

Indicates how many UMTS speech calls are answered.

Trigger: each time the connection has actually been released in response to the receiptof the respective message for:– MTER: CONNECT– MOUT_PLMN, MOUT_NOT_PLMN: ANM

U_TS11_EMERG_WITH_ANSWER

Number of answered UMTS emergency calls (TS11) for MOUT_NOT_PLMN.

Trigger: each time the connection has actually been released in response to the receiptof ANM for UMTS call.

U_TS12_EMERG_WITH_ANSWER

Number of answered UMTS emergency calls (TS12) or MOUT_NOT_PLMN.

Trigger: each time the connection has actually been released in response to the receiptof ANM for UMTS call.

U_RNC_REL_WITH_ANSWER

Number of answered UMTS calls terminated due to UTRAN/radio-related reasons (e.g.,loss of connection). For MTER, MOUT_PLMN, MOUT_NOT_PLMN.

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

CCS_TO_FROM_ATM_NETW

Number of calls routed to another MSC of the same network over an ATM Core Network.For MICTR, MTRAN, MOUT_PLMN, MOUT_NOT_PLMN.

Trigger: each time an outgoing trunk is selected to rout the call over an ATM Core Net-work.

NUM_PAG_PERF_DUE_CL_RET

Number of pagings/searches performed due to current location retrieval in the MSC.

Trigger: each time paging is performed in order to retrieve the current location via theGs interface or the A/Iu interface.

A50016-D1112-G802-1-7618 75


Counter Description

NUM_LOC_REP_CTL_MAP_PSI

Number of location reporting controls sent due to MAP:PSI from the MSC.

Trigger: each time PROVIDE SUBSCRIBER INFORMAMATION HANDLING is sent(prerequisite: the subscriber has a 3G connection).

NUM_UND_LOC_RNC

Indicates the number of undetermined locations in RNC which is also counted in theMSC.

Trigger: each time an unsuccessful location reporting procedure is sent due to MAP:PSI.

3.2 Handover Data MeasurementFor circuit-switched calls, a number of handover counters has been introduced in orderto measure the activity of inter system handover from UMTS towards GSM, and the re-location inside the UMTS system. It should be underlined that these counters only applyto UMSC controlled handover/relocation.

The description of the UMTS handover data is divided into the same parts as the de-scription of GSM handover data.

The measurement job is started by selecting the HANDOVER data type in the RECMSC command .

Following distinction is made for UMTS traffic measurements concerning the han-dover/relocation part:• Intra MSC handover:

– handover from an UMTS cell to a GSM cell,– handover from one UMTS cell to another.

• Inter MSC handover:– handover from an UMTS cell to a GSM cell,– handover from one UMTS cell to another.

For inter system handover from a GSM cell to an UMTS cell, refer to chapter 2.2.4.

The distinction between hard and soft handover is not relevant for traffic measurement,so the traffic measurement counters are not subdivided into hard and soft.

The description of the UMTS basic data is divided into the same parts as the descriptionof GSM basic data. Because there is a large number of different counters, they havebeen grouped on the following pages according to their distinctive purposes:• Load and demand counters (see chapter 3.2.1)• Grade of service counters, focussing successful completed handovers (see chapter

3.2.2)


U_HANDOVER_ATTEMPTS

Number of relocations or handovers from UMTS to GSM.

Trigger: when HANDOVER REQUIRED is received without SDCCH indication, and withradio source indicator set to UMTS.

76 A50016-D1112-G802-1-7618


U_HANDOVER_MSC_MSC_OG_ATTEMPTS

Number of outgoing requests for inter-MSC relocation or inter-MSC handover fromUMTS to GSM (home MSC = MSC-A).

Trigger: each time PERFORM HANDOVER is sent to the MSC-B, with radio source in-dicator set to UMTS.

U_HANDOVER_MSC_MSC_IC_ATTEMPTS

Number of incoming requests for inter-MSC relocation (home MSC = MSC-B).

Trigger: each time HANDOVER REQUIRED is received from the MSC-A, with radio tar-get indicator set to UMTS.

U_SUBSEQ_MSC_MSC_HO_MSCB

Number of requests for subsequent inter-MSC relocation or inter-MSC handover fromUMTS to GSM (home MSC = MSC-B).

Trigger: each time PERFORM SUBSEQUENT HANDOVER is sent to the MSC-A, withradio source indicator set to UMTS

U_SUBSEQ_MSC_MSC_HO_MSCA

Number of requests for subsequent inter-MSC relocation (home MSC = MSC-A).

Trigger: each time PERFORM SUBSEQUENT HANDOVER is received from the MSC-B, with target source indicator set to UMTS.

U_INTER_MSC_MSC_HO_ATT_GSM_UMTS_IC

Number of inter MSC inter system handover IC attempts from GSM to UMTS (measuredin the 3G MSC). In MSC-A the A interface is used, in MSC-B the Iu interface.

Trigger: each time HANDOVER REQUIRED is received from MSC-A.

3.2.2 Grade of Service Counters: Successful Completed Handovers

U_INTRA_HANDOVER_UMTS_TO_GSM

Number of successful completed intra MSC handover from UMTS to GSM.

Trigger: each time MSC receives HANDOVER COMPLETE from the BSS, with radiosource indicator set to UMTS and target source indicator set to GSM.

U_INTER_HANDOVER_UMTS_TO_GSM

Number of successful inter-MSC handovers from UMTS to GSM, where the home MSCacts as the MSC-A.

Trigger: each time HANDOVER COMPLETE is received for handover back to the MSC-A, or each time SEND END SIGNAL is received from the MSC-B for handover to MSC-B, both with radio source indicator set to UMTS and target source indicator set to GSM.

U_SUCC_COMPLETED_HO

Number of successfully completed intra-UMSC relocations or handovers from UMTS toGSM.

Trigger: each time MSC receives HANDOVER COMPLETE from the BSS, or each timeMSC receives RELOCATION COMPLETE from the UTRAN, both with radio source in-dicator set to UMTS.

A50016-D1112-G802-1-7618 77


Counter Description

U_SUCC_MSC_MSC_HO_MSCA

Number of successful inter-UMSC relocations or inter-MSC handovers from UMTS toGSM, where the home MSC acts as the MSC-A.

Trigger: each time HANDOVER COMPLETE is received for handover back to the MSC-A, and each time SEND END SIGNAL is received from the MSC-B for handover to theMSC-B, both with radio source indicator set to UMTS.

U_SUCC_MSC_MSC_HO_MSCB

Number of successful inter-MSC relocation where the home MSC acts as the MSC-B/MSC-B'.

Trigger: each time SEND END SIGNAL is sent to the MSC-A, with target source indica-tor set to UMTS.

U_SUCC_SUBSEQ_MSC_MSC_HO_MSCB

Number of successful subsequent inter-MSC relocation.

Trigger: each time END SIGNAL is received in response to the handover command, forUMTS call.

U_SUCC_HO_SEC_MSC_MSC_HO_MSCB

Number of intra-MSC relocation after previous inter-MSC relocation (home MSC =MSC-B).

Trigger: each time RELOCATION COMPLETE is received from the UTRAN for intra-MSC relocation in the MSC-B.

U_RELOCATION_CANCEL

Number of relocation canceled by the serving RNC.

Trigger: each time RELOCATION CANCEL is received from the serving RNC.

3.3 Short Message Service Data MeasurementFor the measurement of the traffic related to the short message service (SMS) overUMTS via the Iu interface, a number of SMS counters are implemented in the UMSC.

The description of the UMTS SMS data is divided into the same parts as the descriptionof GSM SMS data.

The measurement job is started by selecting the data type SMS in command REC MSC.

The description of the UMTS SMS data is divided into the same parts as for GSM. Be-cause there is a large number of different counters, they have been grouped on the fol-lowing pages according to their distinctive purposes:– Load and demand (see chapter 3.3.1)– Grade of service, focussing on successful short message services (see chapter

3.3.2).

The traffic types do not affect SMS traffic measurement.

78 A50016-D1112-G802-1-7618



U_SMS_INC_ATTEMPTS

Number of SMS messages over UMTS received from the SMS gateway (home MSC =serving MSC).

Trigger: each time the CP executes the delivery of an SMS-MT (e.g., after successfulpaging of a single standalone SMS-MT transaction) when the radio source indicator isset to UMTS .

U_SMS_OTG_ATTEMPTS

Number of SMS messages over UMTS sent to the SMS gateway (home MSC=servingMSC).

Trigger: each time the FORWARD SHORT MESSAGE is sent to the SMS gatewaywhen radio source indicator is set to UMTS.

U_SMS_INC_PARALLEL

Number of parallel UMTS SMS-MT invocations.

Trigger: each time the FORWARD SHORT MESSAGE is received from the SMS gate-way when radio source indicator is set to UMTS.The setup of SMS-MT is a paralleltransaction (e.g., to a call).

U_SMS_OTG_PARALLEL

Number of parallel UMTS SMS-MO invocations.

Trigger: each time the FORWARD SHORT MESSAGE is sent to the SMS gatewaywhen radio source indicator is set to UMTS.The setup of SMS-MO is a parallel transac-tion.

U_SMS_SER_REQ_ATTEMPTS

Number of received CM SERVICE REQUEST messages for service SMS over UMTS.

Trigger: each time the CM SERVICE REQUEST including service type SMS is receivedfrom the UE.

3.3.2 Grade of Service Counters: Successful Services

U_SUCC_SMS_INC

Number of successfully acknowledged SMS messages over UMTS that have been re-ceived from the SMS gateway (home MSC = serving MSC).

Trigger: each time FORWARD SHORT MESSAGE ACK is sent to the SMS gatewaywhen radio source indicator is set to UMTS.

U_SUCC_SMS_OTG

Number of successfully acknowledged SMS messages over UMTS that are sent to theSMS gateway (home MSC = serving MSC).

Trigger: each time FORWARD SHORT MESSAGE ACK is received by the SMS gate-way when radio source indicator is set to UMTS.

A50016-D1112-G802-1-7618 79


Counter Description

U_SUCC_MULT_SMS_OTG

Number of successfully acknowledged sent multiple SMS messages over UMTS.

Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is received asacknowledgement from the SMS gateway for multiple short message transfer, when ra-dio source indicator is set to UMTS. Note: first short message is acknowledged as SUC-CESSFUL SHORT MESSAGE OUTGOING.

U_SUCC_MULT_SMS_INC

Number of successfully acknowledged received multiple SMS messages over UMTS.

Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is sent as ac-knowledgement to the SMS gateway for multiple short message transfer, when radiosource indicator is set to UMTS. Note: last short message is acknowledged as SUC-CESSFUL SHORT MESSAGE OUTGOING.

80 A50016-D1112-G802-1-7618


A50016-D1112-G802-1-7618 81


Counter Description

4 Traffic Measurement of Special andSupplementary ServicesA 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 groups (telephony, fac-simile transmission, bearer service) the service may be associated with. Since the MSCis involved each time an SS is called in, the measurement of the resulting traffic is car-ried out in the MSC.

The measurement job is started by entering the REC SSERV command.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• call forwarding data (see chapter 4.1)• call barring data (see chapter 4.2)• special services for which can be registered:

– the number of all invocations (see chapter 4.3)– the number of successfully completed invocations (see chapter 4.4)

4.1 Supplementary Service Counters: Call Forwarding

INVOC_SERV_CALL_FORWARD

Number of invocations for call forwarding with respect to the proper 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: in a GMSC each time an interrogation of the HLR has delivered a forward-

ed-to-number for a detached subscriber.in a VMSC each time an MTC has been forwarded due to either no paging responseor to radio congestion.

SUCC_INVOC_SERV_CALL_FORWARD

Number of successful 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: in a GMSC each time an interrogation of the HLR has delivered a forward-

ed-to-number for a detached subscriber.in a VMSC each time an MTC has been forwarded due to either no paging responseor to radio congestion.

82 A50016-D1112-G802-1-7618


4.2 Supplementary Service Counters: Call Barring

SUCC_INVOC_SERV_CALL_BARRING

Indicates 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 Counters: Invocations

INVOC_SERV_AOC_CHARGE

Number of invocations for advice of charge, charging level.

Trigger: each time this service is invoked.

INVOC_SERV_SPLIT_MPTY

Number of invocations for split multiparty service.

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

INVOC_AOC_CHARGE_INFO

Number of invocations for advice of charge, information level.

Trigger: each time this service is invoked.

INVOC_SERV_MULTIPARTY

Number of invocations for multiparty service.


INVOC_SERV_PUT_HOLD

Indicates 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_HOLD

Indicates 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_CLIP

Number of invocations for calling line identification presentation.


INVOC_SERV_CLIR

Number of invocations for calling line identification restriction.


INVOC_SERV_CALL_BACK

Number of invocations for call back.

A50016-D1112-G802-1-7618 83


Counter Description


INVOC_SERV_CALL_TRANSFER

Number of invocations for call transfer.

Trigger: each time this service is invoked and call transfer condition is recognized duringdatabase access.

INVOC_SERV_UUS

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_MORTR

Number of invocations for the service completion of calls to busy subscriber for MORTR.

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

INVOC_SERV_CCBS_MTER

Number of invocations for the service completion of calls to busy subscriber for MTER.

Trigger: each time CCBS REQUEST is received in the MSC-B.

4.4 Special Services Counters: Successfully CompletedInvocations

SUCC_INVOC_AOC_CHARGE

Indicates 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_INFO

Indicates how many invocations are completed successfully for advice of charge, infor-mation level.


SUCC_INVOC_MULTIPARTY

Indicates how many invocations are completed successfully for multiparty service.


SUCC_INVOC_PUT_HOLD

Indicates 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_HOLD

Indicates how often a held call is successfully retrieved.

84 A50016-D1112-G802-1-7618


Trigger: each time the call on hold is released and successfully processed in the homeexchange.

SUCC_INVOC_CALL_BACK

Indicates how many invocations are completed successfully for call back.


SUCC_INVOC_SPLIT_MPTY

Number of successfully completed invocations for service split multiparty.

SUCC_INVOC_CALL_TRANSFER

Indicates 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_MORTR

Indicates 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_MTER

Indicates 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.

A50016-D1112-G802-1-7618 85


Counter Description

5 Traffic Measurement in IWEIn order to handle data services, it is necessary to introduce functionally different typesof interworking equipment (IWE) that carry out, for example, rate adaptations towardsthe BSS, and modem and codec functions towards the external network. For this pur-pose it is important 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 REC IWE command.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Load and demand (see chapter 5.1)• Grade of service, focussing on:

– Unsuccessful attempts (see chapter 5.2)– Forced released calls (see chapter 5.3)– Holding times (see chapter 5.4)– Upgrading and downgrading (see chapter 5.5)

• Alternate speech fax 3 (see chapter 5.6)

5.1 Load and Demand Counters

IWE_ANALOG_TP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S– 14400 B/S– 19200 B/S– 28800 B/S

IWE_ANALOG_NTP

Indicates 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:– 300 B/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S– 14400 B/S

86 A50016-D1112-G802-1-7618


– 19200 B/S– 28800 B/S

IWE_DIGITAL_TP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 19200 B/S

IWE_DIGITAL_NTP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 14400 B/S– 19200 B/S– 28800 B/S– 38400 B/S

IWE_FAX3_TP

Indicates 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/S– 4800 B/S– 9600 B/S

IWE_ANACDS_NTP

Indicates 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/S– 2400 B/S– 4800 B/S– 9600 B/S

A50016-D1112-G802-1-7618 87


Counter Description

IWE_DIGCDS_NTP

Indicates 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.


5.2 Grade of Service Counters: Unsuccessful Attempts

UNS_IWE_ANALOG_TP

Indicates 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.


UNS_IWE_ANALOG_NTP

Indicates 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.


UNS_IWE_DIGITAL_TP

Indicates 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/S– 1200 B/S– 2400 B/S

88 A50016-D1112-G802-1-7618


– 4800 B/S– 9600 B/S– 19200 B/S

UNS_IWE_DIGITAL_NTP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 14400 B/S– 19200 B/S– 28800 B/S– 38400 B/S

UNS_IWE_FAX3_TP

Indicates 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/S– 4800 B/S– 9600 B/S

UNS_IWE_ANACDS_NTP

Indicates how many attempts were unsuccessful - due to a lack of resources - to inter-connect an IWE for the transfer of analog data for the transfer of digital data at a givenuser rate in CDS and non-transparent mode.


UNS_IWE_DIGCDS_NTP

Indicates 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.


A50016-D1112-G802-1-7618 89


Counter Description

5.3 Grade of Service Counters: Forced Released Calls

FRC_IWE_ANALOG_TP

Indicates 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, or at a 30seconds timeout for IWE synchronization for the respective bearer service of:– 300 B/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S– 14400 B/S– 19200 B/S– 28800 B/S

FRC_IWE_ANALOG_NTP

Indicates 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 timeout for IWE synchronization for the respective bearer service of:– 300 B/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S– 14400 B/S– 19200 B/S– 28800 B/S

FRC_IWE_DIGITAL_TP

Indicates 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, or at a 30seconds timeout for IWE synchronization for the respective bearer service of:– 300 B/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 19200 B/S

FRC_IWE_DIGITAL_NTP

Indicates how many calls are forced released by the IWE for digital data at a given userrate in CDA and non-transparent mode.

90 A50016-D1112-G802-1-7618


Trigger: each time a forced release due to an IWE malfunction takes place, or at a 30seconds timeout for IWE synchronization for the respective bearer service of:– 300 B/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 14400 B/S– 19200 B/S– 28800 B/S– 38400 B/S

FRC_IWE_FAX3_TP

Indicates 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, or at a 30seconds timeout for IWE synchronization for teleservice 61 at a user rate of:– 2400 B/S– 4800 B/S– 9600 B/S

FRC_IWE_ANACDS_NTP

Indicates 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, or at a 30seconds timeout for IWE synchronization for the respective bearer service of:– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S

FRC_IWE_DIGCDS_NTP

Indicates 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, or at a 30seconds timeout for IWE synchronization for the respective bearer service of:– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S

5.4 Grade of Service Counters: Holding Times

TV_IWE_ANALOG_TP

Indicates 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.

A50016-D1112-G802-1-7618 91


Counter Description

Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:– 300 B/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S– 14400 B/S– 19200 B/S– 28800 B/S

TV_IWE_ANALOG_NTP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S– 14400 B/S– 19200 B/S– 28800 B/S

TV_IWE_DIGITAL_TP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 19200 B/S

TV_IWE_DIGITAL_NTP

Indicates 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 14400 B/S

92 A50016-D1112-G802-1-7618


– 19200 B/S– 28800 B/S– 38400 B/S

TV_IWE_FAX3_TP

Indicates 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/S– 4800 B/S– 9600 B/S

TV_IWE_ANACDS_NTP

Indicates 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/S– 2400 B/S– 4800 B/S– 9600 B/S

TV_IWE_DIGCDS_NTP

Indicates 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.

Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease) for the respective bearer service of:– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S

5.5 Grade of Service Counters: Upgrading and Downgrading

UPGRADING_USER_INIT

Indicates how many level upgrades were initiated by the user; i.e., when the user hasrequested 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_INIT

Indicates how many level upgrades were initiated by the network.

Trigger: each time UPDATE CHANNEL for upgrading during handover is sent toBSSAP-LTG.

DOWNGRADING_USER_INIT

Indicates how many level downgrades were initiated by the user; i.e., when the user hasrequested a lower user rate at the air interface than the actual one.

A50016-D1112-G802-1-7618 93


Counter Description

Trigger: each time MODIFY RESULT for successful downgrading is sent to BSSAP-LTG.

DOWNGRADING_NETWORK_INIT

Indicates how many level downgrades were initiated by the network.

Trigger: each time UPDATE CHANNEL for downgrading during handover is sent toBSSAP-LTG.

UNS_UPGRADING_USER_INIT

Indicates how many level upgrades were initiated by the user unsuccessfully. In thatcase, the old configuration is restored.

Trigger: each time MODIFY RESULT indicating an unsuccessful upgrading is sent toBSSAP-LTG.

UNS_DOWNGRADING_USER_INIT

Indicates how many level downgrades were initiated by the user unsuccessfully. In thatcase, the old configuration is restored.

Trigger: each time MODIFY RESULT indicating an unsuccessful downgrading is sent toBSSAP-LTG.

94 A50016-D1112-G802-1-7618


5.6 Alternate Speech Fax 3 Counters

IWE_SP_FAX3_TP

Indicates 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.

IWE_SP_FAX3_NTP

Indicates how many attempts are made to interconnect an IWE for alternate speech/fac-simile group 3, non transparent mode for fax transmission only.

Trigger: each time the IWE device is selected for teleservice 61 in non transparentmode.

UNS_IWE_SP_FAX3_TP

Indicates 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.

UNS_IWE_SP_FAX3_NTP

Indicates how many unsuccessful attempts are made to interconnect an IWE for alter-nate speech/facsimile group 3, non transparent mode, due to lack of IWE.

Trigger: upon each failure to seize an IWE device for teleservice 61 in non transparentmode.

FRC_IWE_SP_FAX3_TP

Indicates 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.

FRC_IWE_SP_FAX3_NTP

Indicates how many calls are forced released by IWE for alternate speech/facsimilegroup 3, non 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_TP

Indicates 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).

TV_SP_FAX3_NTP

Indicates the total holding time to interconnect an IWE for alternate speech/facsimilegroup 3, non transparent mode for fax transmission only.

Trigger: starts when IWE is selected and stops when IWE is released (including a forcedrelease).

A50016-D1112-G802-1-7618 95


Counter Description

NUM_IWE_CREATED_IN_DB

Number of IWEs created in the database.

Trigger: every 15 minutes this number is retrieved from the database.

NUM_IWE_AVAILABLE

Number of IWEs that are available.


NUM_IWE_BUSY

Number of IWEs that are busy.


NUM_IWE_IDLE

Number of IWEs that are idle


NUM_IWE_BLOCKED

Number of IWEs that are blocked.


96 A50016-D1112-G802-1-7618


6 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 to retrieve information from the previous VLR and the HLR.

A traffic measurement job is started by entering the REC VLR command.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Installation-related, focussing on non-static data, e.g., numbers of registered sub-

scribers in the VLR database (see chapter 6.1)• Load and grade of service (see chapter 6.2)• Security functions (see chapter 6.3)• External interworking (see chapter 6.4)• Combined paging and combined location update (see chapter 6.5)

6.1 Installation-related Counters

ENTRY_USED_OWN

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_FOREIGN

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_ACT

Total number of SS activated, for all subscribers registered in the VLR.

Trigger: for each existing VLR entry (home and foreign MS), the counter is incrementedby the number of SS that the MS has active.

ENTRY_OP_BARR

Indicates 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_DETACH

Number of detached subscribers in the VLR.

Trigger: each time VLR entry exists and entry is implicitly or explicitly marked as de-tached.

A50016-D1112-G802-1-7618 97


Counter Description

DETACH_MSG_TMSI_NO_IMSI_CORR

Number of received DETACH messages with TMSI and no IMSI correlation is found.

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

VLR_AREA_LEAVES_OWN_PLMN

Number of location updates at which the subscriber of the home PLMN leaves the VLRarea.

Trigger: each time CANCEL LOCATION for a home MS is received in PVLR.

VLR_AREA_LEAVES_FOREIGN_PLMN

Number of location updates at which the subscriber of a foreign PLMN leaves the VLRarea.

Trigger: each time CANCEL LOCATION for a foreign MS is received in PVLR.

LA_CHANGES_OWN_PLMN

Number of location area changes at which the subscriber of the home PLMN stays inthe VLR area.

Trigger: each time Location Update REQUEST for home MS is received, whereby newLAI belongs to home (old) VLR area.

LA_CHANGES_FOREIGN_PLMN

Number of location area changes at which the subscriber of a foreign PLMN stays in theVLR area.

Trigger: each time Location Update REQUEST is received, whereby the new LAI be-longs to home (old) VLR area.

EXPLICIT_IMSI_DETACH

Number of handled procedures for an explicit IMSI detach.

Trigger: each time COMPLETE LAYER 3 with IMSI detach indication is received.

IMPLICIT_IMSI_DETACH

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.

6.2 Load and Grade of Service Counters

REQUESTS_LOCUPD

Number of requests for location updating (normal, periodic, IMSI attach).

Trigger: each time LOCATION UPDATE REQUEST is received.

REQUESTS_LOCUPD_INTRA_VLR

Number of attempted location updates (normal, periodic, IMSI attach) within the VLR.

Trigger: each time LOCATION UPDATE REQUEST for an intra VLR location is re-ceived.

98 A50016-D1112-G802-1-7618


REQUESTS_LOCUPD_INTER_VLR

Number of attempted normal location updates between VLRs.

Trigger: each time LOCATION UPDATE REQUEST is received and LAC translation In-dicates VLR area change.

REQUESTS_PERIODIC_LOCUPD

Number of requests for periodic location updating.

Trigger: each time LOCATION UPDATE REQUEST containing type “periodic” is re-ceived.

REQUESTS_LOCUPD_WITH_IMSI_ATT

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_LOCUPD

Number of successfully handled requests for location updating (normal, periodic).

Trigger: each time LOCATION UPDATE ACCEPT is received.

SUCC_LOCUPD_WITH_IMSI_ATTACH

Number of successfully handled location update requests for an IMSI attach.

Trigger: each time LOCATION UPDATE ACCEPT containing “IMSI attach” is sent to theBSS.

LOCUPD_LAI_NULL

Number of location updates with old LAI = 0 (e.g., at registration with MS recovery).

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

CALL_WITH_UNIDENT_SUB

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_RECOV

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_KNOWN

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.

VLR_CHANGES_PVLR_UNKNOWN

Number of VLR area changes where the PVLR is unknown.

A50016-D1112-G802-1-7618 99


Counter Description

Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS and the PVLR isunknown.

REQUESTS_LOCUPD_TO_HLR

Number of requests for location updating sent to the HLR.

Trigger: each time LOCATION UPDATE ACCEPT is sent to the HLR.

RESULTS_LOCUPD_FROM_HLR

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_HLR

Number of additional location update interworkings between VLR and HLR caused byHLR restoration.

Trigger: each time TC-BEGIN invoke UPDATE LOCATION is sent to HLR after previousHLR restoration.

RESULTS_LOCUPD_FROM_PVLR

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_IMSI

Number of received detach messages with IMSI.

Trigger: each time IMSI DETACH including MS identification by IMSI is received.

RECEIVED_DETACH_WITH_TMSI

Number of received detach messages with TMSI.

Trigger: each time IMSI DETACH including the MS identification by TMSI is received.

RECEIVED_DETACH_NO_VLR_ENTRY

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_SUB

Number of unsuccessful HLR interworkings because the subscriber was not 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_ALLOWED

Number of unsuccessful HLR interworkings because roaming is not allowed.

Trigger: each time TC-END U-Error due to roaming not allowed is received from HLR inresponse to TC-BEGIN invoke UPDATE LOCATION.

INTW_HLR_TCAP_TIMER_EXPIRY

Number of unsuccessful HLR interworkings because TCAP timer expired.

Trigger: each time T-LU expires (no HLR response).

100 A50016-D1112-G802-1-7618


INTW_HLR_DEST_OUT_OF_SERVICE

Number of unsuccessful HLR interworkings because the destination was out of service.

Trigger: each time TC-NOTICE is received due to destination out of service.

INTW_HLR_SYSTEM_FAILURE

Number of unsuccessful HLR interworkings because the HLR system failed.

Trigger: each time TC-END U-ERROR is received from the HLR due to system failure.

INTW_HLR_TCAP_ABORT

Number of unsuccessful HLR interworkings because the TCAP aborted.

Trigger: each time TC-ABORT is received.

INTW_HLR_PROTOCOL_ERRORS

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_REASONS

Number of unsuccessful HLR interworkings due to reasons different from those coveredby 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 SUBSCRIBERDATA, missing resources in the VLR, subscriber cancelled in the meantime.

INTW_PVLR_UNIDENT_SUB

Number of unsuccessful PVLR interworkings because the subscriber cannot be identi-fied.

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_EXPIRY

Number of unsuccessful PVLR interworkings because the TCAP timer expired.

Trigger: each time timer expires.– Ph1: T-par– Ph2: T-si

INTW_PVLR_DEST_OUT_OF_SERVICE

Number of unsuccessful PVLR interworkings because the destination was out of ser-vice.

Trigger: each time TC-NOTICE is received due to destination out of service.

INTW_PVLR_TCAP_ABORT

Number of unsuccessful PVLR interworkings due to TCAP abort.

A50016-D1112-G802-1-7618 101


Counter Description

Trigger: each time TC-ABORT is received from TCAP.

INTW_PVLR_PROTOCOL_ERRORS

Number of unsuccessful PVLR interworkings due to protocol errors (invoke, 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_REASONS

Number of unsuccessful PVLR interworkings because of reasons different from thosecovered 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_HLR

Number of unsuccessful BSS interworkings because the IMSI is not known in the HLR.

Trigger: each time LOCATION UPDATE REJECT indicating IMSI unknown is sent to theMS.

INTW_BSS_ILLEGAL_SUB

Number of unsuccessful BSS interworkings because the subscriber was illegal.

Trigger: each time LOCATION UPDATE REJECT indicating illegal MS is sent to the MS.

INTW_BSS_PLMN_NOT_ALLOWED

Number of UNSUCCESSFUL BSS interworkings because the PLMN was not allowed.

Trigger: each time LOCATION UPDATE REJECT indicating PLMN not allowed is sentto the MS.

INTW_BSS_LOCAREA_NOT_ALLOWED

Number of unsuccessful BSS interworkings because the location area was not allowed.

Trigger: each time LOCATION UPDATE REJECT indicating location area not allowedis sent to the MS.

INTW_BSS_NETWORK_FAILURE

Number of unsuccessful BSS interworkings because the network has failed.

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

INTW_BSS_RADIO_REASONS1

Number of unsuccessful BSS interworkings due to radio/BSS-related reasons concern-ing BSS/MSC connection failures.

Trigger: the receipt of CLEAR REQUEST.

INTW_BSS_RADIO_REASONS2

Number of unsuccessful BSS interworkings because the radio/BSS-related reasonsconcerning protocol errors - (new) LAI unknown (database inconsistency).

102 A50016-D1112-G802-1-7618


Trigger: each time LOCATION UPDATE REJECT is sent to the MS due to unspecifiedprotocol error.

INTW_BSS_LAI_UNKNOWN

Number of unsuccessful BSS interworkings because the (new) LAI is not known.

Trigger: each time LOCATION UPDATE REQUEST is received and the new LAI doesnot exist in the VLR.

INTW_BSS_SECOND_TRANS_LOCUPD

Number of unsuccessful BSS interworkings due to second transaction for location up-dating (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_REASONS

Number of unsuccessful BSS interworkings for reasons that are not covered by the pre-vious 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_ME

Number of unsuccessful BSS interworkings because the mobile equipment (ME) is fromthe black list or unknown.

Trigger: each time message Location Update Reject indicating “Illegal ME” is sent to theBSC/MS.

CAMEL_PSI

Number of information requests received from the HLR in order to retrieve the subscrib-er’s location intended for CAMEL services.

Trigger: each time PROVIDE SUBSCRIBER INFO is received from the HLR.

INTW_BSS_ROAMING_NOT_ALLOWED

Number of unsuccessful BSS interworkings because roaming is not allowed.

Trigger: each time when the LUP is rejected because of cause #13 (Roaming not al-lowed in this Location Area).

INTW_BSS_NO_SUIT_CELL_IN_LOCAREA

Number of unsuccessful BSS interworkings because there is no suitable cell in the lo-cation area.

Trigger: each time when the LUP is rejected because of cause #15 (No suitable cells inLocation Area).

BSSAP_PL_UNKNOWN

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_ERR

Number of decoding errors with respect to BSSAP+.

A50016-D1112-G802-1-7618 103


Counter Description

Trigger: each time a UDT message with a decoding error is received from the BSSAP-LTG.

NUM_MAP_NOTEMM_OWN_MSUB

Number of MAP:NoteMM-Events sent for own subscribers.

Trigger: each time an IMSI attach/detach or Location Update is performed (Prerequisite:subscriber has an M-CSI).

NUM_MAP_NOTEMM_SUCC_OWN_MSUB

Number of MAP:NoteMM-Events successfully sent for own subscribers.

Trigger: each time an acknowledge message is received from the SCP (ATIRes ack).

NUM_MAP_NOTEMM_FRN_MSUB

Number of MAP:NoteMM-Events sent for foreign subscribers.

Trigger: each time an IMSI attach/detach or Location Update is performed (Prerequisite:subscriber has an M-CSI)

NUM_MAP_NOTEMM_SUCC_FRN_MSUB

Number of MAP:NoteMM-Events successfully sent for foreign subscribers.

Trigger: each time an acknowledge message is received from the SCP.

NUM_MAP_PSI_CL_OWN_MSUB_REC

Number of MAP:PSIs with current location for own subscribers received in the VLR.

Trigger: each time MAP:PSI with Current Location for own subscribers is sent from theHLR.

NUM_MAP_PSI_CL_FRN_MSUB_REC

Number of MAP:PSIs with current location for foreign subscribers received in the VLR.

Trigger: each time MAP:PSI with Current Location for foreign subscribers is sent fromthe HLR.

NUM_NOT_ALLOW_MAP_PSI_REC

Number of not allowed MAP:PSIs with and without current location received in the VLR.

Trigger: each time the check against RST fails

NUM_BSSAP_MS_INF_REQ_SNT_DU_CL

Number of BSSAP+Ms-Information-Requests sent due to location info from the VLR.

Trigger: each time PSI-handling is performed (Prerequisite: the subscriber has com-bined attach, the Gs interface is active).

NUM_BSSAP_MS_INF_RESP_W_CL_REC

Number of BSSAP+Ms-Information-Responses including the current location receivedin the VLR

Trigger: each time PSI-handling is performed (Prerequisite: the subscriber has com-bined attach, the Gs interface is active).

104 A50016-D1112-G802-1-7618


MM_INFO_SENT

Number of MM_INFORMATION sent over the A interface.

Trigger: each time MM INFORMATION (NITZ info) is sent to the BSSAP LTG for A in-terface.

RANAP_MM_INFO_SENT

Number of MM_INFORMATION sent over the Iu interface.

Trigger: each time MM INFORMATION (NITZ info) is sent to the BSSAP LTG for Iu in-terface.

6.3 Security Function Counters

SUB_IDENTIFIED_WITH_TMSI

Number of handled transactions (e.g., MOC, MTC, SCI) where the subscriber was iden-tified with TMSI.

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

SUB_IDENTIFIED_WITH_IMSI

Number of handled transactions (e.g., MOC, MTC, SCI) where subscriber was identifiedwith IMSI.

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

IDENTITY_REQUESTS

Indicates the total number of identity requests sent on the A interface.

Trigger: each time IDENTITY REQUEST is sent on the A interface.

IDENT_REQ_CORR_FAILURE

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_FAILURE

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_FAILURE

Number of identity requests caused by authentication failure when subscriber was pre-viously identified with TMSI.

Trigger: each time IDENTITY REQUEST is sent on the A interface after detection of au-thentication failure.

AUTH_REQ

Number of authentication requests.

Trigger: each time AUTHENTICATION REQUEST is sent to the MS.

A50016-D1112-G802-1-7618 105


Counter Description

AUTH_REQ_CKSN_MISMATCH

Number of authentication requests initiated by a mismatch of the cipher key sequencenumber (CKSN).

Trigger: each time AUTHENTICATION REQUEST is sent to the MS after detection ofCKSN mismatch.

CIPHERING_REQ

Number of ciphering requests.

Trigger: each time CIPHERING COMMAND is sent to the MS.

SEND_PAR_REQ_AUTH_VEC_TO_HLR

Indicates how often a request for authentication vector is sent to the HLR.

Trigger: upon sending the appropriate message to the HLR.– Ph1: SEND PARAMETERS– Ph2: SEND AUTHENTICATION INFO

SEND_PARAM_REQ_SUBDAT_TO_HLR

Indicates 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_HLR

Number of acknowledgments containing triples that have been received from the HLR.

Trigger: each time TC-END Return Result-L is received from the HLR in response to– Ph1: SEND PARAMETERS– Ph2: SEND AUTHENTICATION INFO

SEND_PAR_REQ_AUTH_VEC_TO_PVLR

Indicates how often a request for authentication vector is sent to the PVLR.

Trigger: each time SEND IDENTIFICATION is sent to the PVLR.

RECVD_AUTH_INF_TRIPLES_PVLR

Number of acknowledgments containing triples received from the PVLR.

Trigger: each time TC-END Return Result-L is received from PVLR in response to– Ph1: SEND PARAMETERS– Ph2: SEND IDENTIFICATION

SEND_PAR_RECVD_FROM_OTHER_VLR

Number of messages received from other VLRs requesting triples.

Trigger: each time SEND IDENTIFICATION is received.

SEND_TRIPLES_TO_VLR

Number of successful authentication sets that have been received and sent to other VL-Rs.

Trigger: each time TC-END Return Result-L is sent to other VLR in response to– Ph1: SEND PARAMETERS

106 A50016-D1112-G802-1-7618


– Ph2: SEND IDENTIFICATION

AUTH_WITH_ILLEGAL_SUB

Number of authentications with outcome ”illegal subscriber”.

Trigger: each time AUTHENTICATION REJECT indicating illegal MS is sent to theBSC/MS.

WRITTEN_MISMATCH_RECORDS

Number of written mismatch records.

Trigger: each time AUTHENTICATION REJECT indicating illegal MS was sent anddataset was saved successfully.

REUSED_TRIPLES

Number of reused triples.

Trigger: each time AUTHENTICATION REQUEST containing an old triple is sent to theMS.

ATTEMPTED_TMSI_REALLOCATIONS

Number of attempted TMSI reallocations.

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

TMSI_REALLOC_NOT_ANSWERED

Number of VLR database requests achieving two (old/new) allocated TMSIs (missingMS 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_REALLOC

Number of successful TMSI reallocations.

Trigger: each time TMSI REALLOCATION COMPLETE is received from the MS/BSC.

EMPTY_RESPONSE_TO_AUTH_SET

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_PROC

Number of successful ciphering mode control procedures.

Trigger: each time CIPHERING MODE COMPLETE is received from the MS/BSC.

RECVD_AUTH_INF_QUINTETS_HLR

Number of acknowledgments containing quintets that have been received from the HLR.

Trigger: each time TC-END Return Result-L is received from the HLR in response toSEND AUTHENTICATION INFO.

A50016-D1112-G802-1-7618 107


Counter Description

RECVD_AUTH_INF_QUINTETS_PVLR

Number of acknowledgments containing quintets received from the PVLR.

Trigger: each time TC-END Return Result-L is received from PVLR in response toSEND IDENTIFICATION.

SEND_QUINTETS_TO_VLR

Number of successful authentication vectors that are sent to other VLRs.

Trigger: each time TC-END Return Result-L is sent to other VLR in response to SENDIDENTIFICATION.

RECVD_RESYNCHRON_INFO

Total number of completed re-synchronizations.

Trigger: each time TC-END Return Result-L is received from the HLR in response toSEND AUTHENTICATION INFO, sent after a synchronization failure.

IDENTITY_REQUESTS_UMTS

Total number of identity requests sent on the Iu interface.

Trigger: each time IDENTITY REQUEST is sent on the Iu interface.

AUTH_REQ_WITH_AUTN

Number of authentication requests sent on A and Iu interface containing the parameterAUTN.

Trigger: each time AUTHENTICATION REQUEST containing AUTN is sent to theUMTS subscriber.

AUTH_SYNCHRON_FAIL_RECEIVED

Number of authentication failure messages received on A and Iu interfaces indicatingsynchronization failure.

Trigger: each time AUTHENTICATION FAILURE with synchronization failure indicationis received from the UMTS subscriber.

AUTH_MAC_FAIL_RECEIVED

Number of authentication failure messages received on A and Iu interface indicatingMessage Authentication Code failure.

Trigger: each time AUTHENTICATION FAILURE with Message Authentication Codefailure indication is received from the UMTS subscriber.

AUTH_AUTH_FAIL_REP_REQ

Number of authentication failure reports sent to the HLR/AC.

Trigger: each time AUTHENTICATION FAILURE REPORT is sent to the HLR/AC.

AUTH_AUTH_FAIL_REP_SUCC

Number of authentication failure report responses received from the HLR/AC.

Trigger: each time AUTHENTICATION FAILURE REPORT response is received fromthe HLR/AC.

108 A50016-D1112-G802-1-7618


ACCESSED_EPLMN_LISTS

Number of access with sent lists at all.

Trigger: each time an access is made in the EPLMN Selection List.

ACCESSED_EPLMN_DEFAULT_LIST

Number of access with sent default list.

Trigger: each time an access is made in the EPLMN Selection List and the result is thedefault one.

RNC_SECURITY_REQ

Number of security mode procedures for UMTS subscriber started by the MSC/VLR.

Trigger: each time SECURITY MODE COMMAND message is sent to the UE with the“ciphering” parameter and/or “integrity” parameter.

RNC_SECURITY_SUCC

Number of successful security mode procedures for UMTS subscriber.

Trigger: each time SECURITY MODE COMPLETE confirmation message is received bythe MSC/VLR from the UE.

RNC_INTEGRITY_REQ

Number of integrity mode procedures for UMTS subscriber started by the MSC/VLR.

Trigger: each time SECURITY MODE COMMAND message is sent to the UE with the“integrity” parameter.

RNC_INTEGRITY_SUCC

Number of successful integrity mode procedures for UMTS subscriber.

Trigger: each time SECURITY MODE COMPLETE confirmation message or SECURI-TY MODE REJECT message with “integrity performed successfully” is received by theMSC/VLR from the UE.

RNC_CIPHERING_REQ

Number of ciphering mode procedures for UMTS subscriber started by the MSC/VLR.

Trigger: each time SECURITY MODE COMMAND message is sent to the UE with the“ciphering” parameter.

RNC_CIPHERING_SUCC

Number of successful ciphering mode procedures for UMTS subscriber.

Trigger: each time SECURITY MODE COMPLETE confirmation message or SECURI-TY MODE REJECT message with “ciphering performed successfully” is received by theMSC/VLR from the UE.

6.4 External Interworking Counters

INSERT_FROM_HLR_LOCUPD

Number of messages containing subscriber data that is received from the HLR duringlocation update.

A50016-D1112-G802-1-7618 109


Counter Description

Trigger: each time INSERT SUBSCRIBER DATA is received from the HLR in responseto UPDATE LOCATION.

INSERT_FROM_HLR_OCI_SCI

Number of messages containing subscriber data that is received from the HLR duringsubscriber or operator controlled input.

Trigger: each time INSERT SUBSCRIBER DATA is received from HLR due to operatoror subscriber controlled input.

DELETE_FROM_HLR

Number of relevant messages received from the HLR.

Trigger: each time DELETE SUBSCRIBER DATA is received from the HLR.

PROVIDE_MSRN_RECEIVED

Number of relevant messages received from the HLR.

Trigger: each time PROVIDE ROAMING NUMBER is received.

MSRN_SENT

Number of MSRN sent to the HLR.

Trigger: each time a roaming number is sent to a HLR as response to PROVIDE ROAM-ING NUMBER.

MORE_THAN_ONE_MSRN_ALLOC

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

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_EXPIRES

Indicates 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_HLR

Indicates how often a reset message is received from the HLR.

Trigger: each time RESET is received.

ACT_TRACEMODE_FROM_HLR

Indicates how often the relevant message is received from the HLR.

Trigger: each time ACTIVATE TRACEMODE is received.

DEACT_TRACEMODE_FROM_HLR

Indicates how often the relevant message is received from the HLR.

Trigger: each time DEACTIVATE TRACEMODE is received.

RESTORE_DATA_TO_HLR

Indicates how often the relevant message is sent to the HLR.

110 A50016-D1112-G802-1-7618


Trigger: each time RESTORE DATA is sent.

MS_MEMORY_AVAIL_TO_HLR

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_AVAIL

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_HLR

Indicates 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 informs the HLR.

Trigger: each time GENERATE ENTRY is sent provided the proper conditions are met.

REG_SS_TO_HLR

Indicates how many registrations for all SS are sent to the HLR.

Trigger: each time REGISTER SS is sent.

ERA_SS_TO_HLR

Indicates how many erasures for all SS are sent to the HLR.

Trigger: each time ERASURE SS is sent.

ACT_SS_TO_HLR

Indicates how many activations for all SS are sent to the HLR.

Trigger: each time ACTIVATE SS is sent.

DEACT_SS_TO_HLR

Indicates how many deactivations for all SS are sent to the HLR.

Trigger: each time DEACTIVATE SS is sent.

CHECK_SS_FROM_HLR

Indicates how many messages for SS checks have been received from the HLR.

Trigger: each time REGISTER SS, ACTIVATE SS, etc. for SS is sent and the SS checkresult is received.

INTERROG_TO_HLR

Indicates how many SS interrogations the VLR sends to the HLR.

Trigger: each time INTERROGATE SS is sent.

A50016-D1112-G802-1-7618 111


Counter Description

INTERROG_HANDLED_BY_VLR

Indicates 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_SUBSCR

Indicates 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_SYSTEM

Indicates 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_HLR

Indicates how many messages for unstructured SS are sent.

Trigger: each time PROCESS UNSTRUCTURED SS REQUEST is sent to the HLR.

INVOKE_SS_BAOC

Number of successful invocations of all outgoing barring services.

Trigger: each time that, during MOC or SMS-MO establishment, data base accessrecognizes that the SS “barring of all outgoing calls” is active for the subscriber.

INVOKE_SS_BOIC

Number of successful invocations of all outgoing international barring services.

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_MS

Indicates 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_HLR

Indicates 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.

MS_PRESENT_TO_HLR

Number of times the VLR informs the HLR that the MS is ready to receive short mes-sages.

Trigger: each time readyForSM is sent to the HLR with alertReason=ms-present (MAPV2) or noteSubscriberMSPresent (MAP V1).

112 A50016-D1112-G802-1-7618


SUCCESS_MS_PRESENT_TO_HLR

Number of times the VLR receives acknowledgment by the HLR to ms-present.

Trigger: each time ReturnResult component is received from HLR as acknowledgmentto ms-present.

6.5 Combined Paging and Combined Location UpdateCounters

COM_LUP_REQ

Number of location update requests in all (normal and combined).

Trigger: each time UDT(LOCATION UPDATE REQUEST) is received from the BSSAP-LTG.

SUCC_COM_LUP

Number of all successfully handled combined location update requests.

Trigger: each time LOCATION UPDATE ACCEPT is received via the Gs interface.

COM_LUP_PERIODIC

Number of successfully handled periodic location updates via the Gs interface.

Trigger: each time LOCATION UPDATE ACCEPT containing “periodic” is sent to theBSS via the Gs interface.

COM_LUP_LAI_NULL

Number of combined location updates with old LAI = 0 (e.g., upon registration with MSrecovery).

Trigger: each time LOCATION UPDATE ACCEPT is sent to the BSS via the Gs inter-face.

REQ_COM_LUP_TO_HLR

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.

RES_COM_LUP_FROM_HLR

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_PVLR

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.

COM_LUP_TMSI_REQ

Number of started TMSI reallocation procedures via the Gs interface when sendingBSSAP+ LOCATION-UPDATE-ACCEPT.

A50016-D1112-G802-1-7618 113


Counter Description

Trigger: send lr_request with TMSI reallocation in Gs state G_LA_UPDATE_PRESENT.

COM_LUP_TMSI_COM

Number of received BSSAP+ TMSI-REALLOCATION-COMPLETE messages.

Trigger: each time a BSSAP+ TMSI-REALLOCATION-COMPLETE message is re-ceived.

GS_IF_MS_INFO_ERR

Number of received erroneous BSSAP+ MS-INFORMATION-RESPONSE messagesbased upon the mobile station state parameter.

Trigger: each time an erroneous BSSAP+ MS-INFORMATION-RESPONSE message isreceived.

114 A50016-D1112-G802-1-7618


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

A traffic measurement job is started in the HLR by entering REC HLR command.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Structure- and installation-related, such as

– Number of subscribers registered in the HLR database (see chapter 7.1),– Number of subscribers provided with specific services (see chapter 7.2),– Number of subscribers provided with ASCI service and LMU (see chapter 7.3)

• Load and demand and grade of service for mobility management/call handling/au-thentication (see chapter 7.4)

• Load and demand and grade of service for subscriber controlled input (see chapter7.5)

• Load and demand and grade of service for short message service (see chapter 7.6)• GPRS data service (see chapter 7.8)• Overload (see chapter 7.7)

7.1 Structure- and Installation-related Counters: Part 1

SUB_REGISTERED_IN_HLR

Indicates 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_HLR

Indicates 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, or– decreased by CAN MSUB

LINKED_SUB_REGISTERED_IN_HLR

Indicates how many linked subscribers are registered in the HLR.

Trigger: after a successful MML command:– increased by CR MSUBLINK, or– decreased by CAN MSUBLINK

RESTR_SUB_ALL_GSM_PLMN

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_VPLMN

Number of subscribers with the subscription restriction ”one national and all internationalGSM PLMNs”.

A50016-D1112-G802-1-7618 115


Counter Description


RESTR_SUB_HOME_PLMN_ONLY

Number of subscribers with the subscription restriction ”home PLMN only”.


BLOCKED_SUB_REGISTERED_IN_HLR

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_OUTGOING

Number of subscribers with operator determined barring for outgoing calls.


SUB_WITH_ODB_INCOMING

Number of subscribers with operator determined barring for incoming calls.


SUB_WITH_ODB_ROAM

Number of subscribers with operator determined barring for roaming.


SUB_WITH_ODB_PREMIUM_RATE

Number of subscribers with operator determined barring for premium rate calls.


SUB_WITH_ODB_SPECIFIC_HPLMN

Number of subscribers with operator determined barring for specific HPLMN.


SUB_WITH_ODB_SS_MANAGEMENT

Number of subscribers with operator determined barring for SS management.


SUB_WITH_IMSI_TRACE_ACTIVE

Number of subscribers for whom IMSI tracing is active.

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

116 A50016-D1112-G802-1-7618


– decreased by DACT IMSITRAC

OWN_SUB_ROAM_IN_FOREIGN_PLMN

Number of subscribers roaming in a foreign PLMN.

Trigger:– increased upon each location update from the VLR of foreign PLMN and a VLR num-

ber 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.


SPEECH_TRANSMISSION

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_MT

Number of subscribers with the provision for short message services, mobile terminat-ed.


SHORT_MSG_SERVICE_MO

Number of subscribers with the provision for short message services, mobile originated.


FACSIMILE_SERVICES

Number of subscribers with the provision for facsimile services.


DATA_CDA

Number of subscribers being provisioned with the bearer service to transfer analog dataat 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S– 1200/75 B/S

A50016-D1112-G802-1-7618 117


Counter Description

DATA_CDS

Number of subscribers being provisioned with the bearer service to transfer analog dataat 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/S– 2400 B/S– 4800 B/S– 9600 B/S

ALTERN_SPEECH_DATA

Number of subscribers with the provision alternate speech/data services.


SPEECH_FOLLOWED_BY_DATA

Number of subscribers with the provision speech followed by data services.


PAD_CDA

Number of subscribers with the provision for PAD (packet assembler/disassembler) ac-cess 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/S– 1200 B/S– 2400 B/S– 4800 B/S– 9600 B/S

CALL_FORW_UNCONDITIONAL

Number of mobile subscribers with the provision ”call forwarding unconditional”.

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_BUSY

Number of mobile subscribers with the provision ”call forwarding on mobile subscriberbusy”.

Trigger: after a successful MML command for the specified SS of a subscriber.– increased by ENTR CFSERV;– decreased by CAN CFSERV.

CALL_FORW_ON_NO_REPLY

Number of mobile subscribers with the provision ”call forwarding on no reply”.

Trigger: after a successful MML command for the specified SS of a subscriber.– increased by ENTR CFSERV;

118 A50016-D1112-G802-1-7618


– decreased by CAN CFSERV.

CALL_FORW_ON_MS_NOT_REACH

Number of mobile subscribers with the provision ”call forwarding on MS not reachable”.


CALL_BARR_OUTG_CALLS

Number of mobile subscribers with the provision ”barring of all outgoing calls”.

Trigger: after a successful MML command for the specified SS of a subscriber.– increased by ENTR CBSERV;– decreased by CAN CBSERV.

CALL_BARR_OUTG_INT_CALLS

Number of mobile subscribers with the provision ”barring of all outgoing internationalcalls”.


CALL_BARR_OUTG_INT_CALL_HPLMN

Number of mobile subscribers with the provision ”barring of all outgoing internationalcalls except those directed to the home PLMN country”.


CALL_BARR_INC_CALLS

Number of mobile subscribers with the provision ”barring of all incoming calls”.


CALL_BARR_INC_ROAM_OUT_HPLMN

Number of mobile subscribers with the provision ”barring of all incoming calls whenroaming outside the HPLMN”.


CALL_LINE_IDENT_PRESENT

Number of mobile subscribers with the provision “calling line identification presentation”(CLIP).

Trigger: after a successful MML command for the specified SS of a subscriber.– increased by ENTR GCSERV;– decreased by CAN GCSERV.

A50016-D1112-G802-1-7618 119


Counter Description

CALL_LINE_IDENT_RESTR

Number of mobile subscribers with the provision “calling line identification restriction”(CLIR).


CONN_LINE_IDENT_PRESENT

Number of mobile subscribers with the provision “connected line identification presenta-tion” (COLP).


CONN_LINE_IDENT_RESTR

Number of mobile subscribers with the provision “connected line identification restric-tion” (COLR).


AOC_CHARGING_LEVEL

Number of mobile subscribers with the provision “advice of charge, charging level”.


AOC_INFORM_LEVEL

Number of mobile subscribers with the provision “advice of charge, information level”.


MULTI_PARTY_SERVICE

Number of mobile subscribers with the provision “multi party service”.


CALL_BACK

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 CALLBACK;– decreased by CAN CALLBACK.

CLOSED_USER_GROUP

Number of mobile subscribers with the provision “closed user group”.

120 A50016-D1112-G802-1-7618


Trigger: after a successful MML command for the specified SS of a subscriber.– increased by ENTR CUGSERV;– decreased by CAN CUGSERV.

HOT_BILLING

Number of mobile subscribers with the provision “hot billing”.


CALL_HOLD

Number of mobile subscribers with the provision “call hold”.


CALL_WAITING

Number of mobile subscribers with the provision “call waiting”.


NATIONAL_CALLTRANS

Number of mobile subscribers with the provision of “call transfer”.


CALLS_COMPL_BUSY_SUB

Number of mobile subscribers with the provision “call completion to busy subscriber”.


IN_SERVICE_CLASS_MARK_MTC

Number of mobile subscribers with the provision “class mark MTC for IN services”.

Trigger: after a successful MML command for the specified service.– increased by ENTR OPRSERV;– decreased by CAN OPRSERV.

IN_SERVICE_CLASS_MARK_MOC

Number of mobile subscribers with the provision “class mark MOC for IN services”.


USER_SIG1

Number of mobile subscribers with the provision “user-to-user signaling service 1”.

A50016-D1112-G802-1-7618 121


Counter Description


FOLLOW_ME

Number of mobile subscribers with the provision “follow me”.


CALL_FORW_DEF

In addition to the other call forwarding services, this service too has its own counter thatNumber of mobile subscribers with the provision “call forwarding by default”


DATA_CDA_GBS

Number of mobile subscribers being provisioned with the general bearer service totransfer 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_GBS

Number of mobile subscribers being provisioned with the general bearer service totransfer analog data at an appropriate user rate in CDS.


PAD_CDA_GBS

Number of subscribers with the provision for PAD (packet assembler/disassembler) ac-cess at a user rate from the general bearer service via modem circuit duplex asynchro-nous.


MSUB_REGISTERED_GPRS

Indicates 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.

MSUB_ROAM_FOREIGN_GPRS_PLMN

Number of mobile subscribers currently roaming in a foreign GPRS PLMN

Trigger:– increased upon each location update from the SGSN of foreign GPRS PLMN the

number of which differs from the SGSN number in the HLR, or recovery with dataloss for this MS since last location update;

122 A50016-D1112-G802-1-7618


– 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_USSD

Indicates how many mobile subscribers with the provision unstructured supplementaryservice data for 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_CSI

Indicates 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_CSI

Indicates 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).

NUM_MSUB_D_CSI

Indicates how many mobile subscribers with the provision Dialled Service CSI are reg-istered in the HLR.


NUM_MSUB_M_CSI

Indicates how many mobile subscribers with the provision Mobility Management Notifi-cation CSI are registered in the HLR.


NUM_MSUB_SMS_CSI

Indicates how many mobile subscribers with the provision SMS CSI are registered in theHLR.


NUM_MSUB_VT_CSI

Indicates how many mobile subscribers with the provision VMSC Terminating CSI areregistered in the HLR.


NUM_MSUB_UCSI

Indicates how many mobile subscribers with the provision USSD CSI are registered inthe HLR.


A50016-D1112-G802-1-7618 123


Counter Description

NUM_MSUB_MSP

Indicates how many mobile subscribers with the provision Multiple Subscriber Profileare registered in the HLR.


NUM_MSUB_TIF_CSI

Indicates how many mobile subscribers with the provision Translation Information FlagCSI are registered in the HLR.


NUM_MSUB_IN

Indicates how many mobile subscribers with the provision IN are registered in the HLR.


NUM_MSUB_TWC

Number of twin card subscribers.

Trigger: increased if a twin card chain is created and decreased if the last slave is re-moved from a chain.

NATIONAL_FEATURE

Number of mobile subscribers with the provision of national features. Up to 15 of thesecounters are provided.

Trigger: after a successful MML command for the specified feature.– increased by ENTR MBSUFT– decreased by CAN MBSUFT


ASCI_VBS

Indicates 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_VGCS

Indicates 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.

ASCI_EMLPP

Indicates 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.

124 A50016-D1112-G802-1-7618


NO_OF_LMU

Indicates 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).

7.4 Mobility Management/Call Handling/Authentication


RECVD_UPD_LOC_MSG_VLR_HPLMN

Indicates 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_VPLMN

Indicates 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_UPD

Indicates 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_ADMIN

Indicates 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_MSG

Indicates 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_ADMIN

Indicates 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.

SND_DEL_SUBDT_MSG_SUB_ADMIN

Indicates how often a message for deleting subscriber data is sent to the VLR due tosubscriber administration.

A50016-D1112-G802-1-7618 125


Counter Description

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_GMSC

Indicates 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_SCODE

Indicates how often a request for routing information containing service codes is re-ceived.

Trigger: each time SEND ROUTING INFO containing service codes is received.

SND_PROV_MSRN

Indicates how often the relevant message is sent to the VLR.

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

RECVD_MSRN

Indicates 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_GMSC

Indicates 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_GMSC

Indicates how often many forwarded-to-numbers are sent to GMSC.

Trigger: each time SEND ROUTING INFO RESULT containing forwarding data is sentto GMSC.

RECVD_SEND_PARAM_PR

Indicates how often messages for parameter request (e.g., IMSI) have been received.

Trigger: each time the proper message is received.– Ph1: SEND PARAMETERS including authentication triples– Ph2: RESTORE DATA

RECVD_SEND_PARAM_AR

Indicates how often messages requesting authentication data is received.The imple-mented counter measures the number of triplets the HLR requests from the AC.

Trigger: each time the proper message is received.– Ph1: SEND PARAMETERS– Ph2: SEND AUTHENTICATION INFO

RECVD_SEND_PARAM_AR_PR

Indicates how often messages requesting parameter and authentication data have beenreceived.

126 A50016-D1112-G802-1-7618


Trigger: each time SEND PARAMETERS is received, including authentication triplesand subscriber data (Ph1).

SENT_RESET_HLR

Indicates how often a reset message is sent to the HLR.

Trigger: each time RESET is sent to the HLR.

RECVD_RESET_VLR

Indicates how often a reset message is received from a VLR.

Trigger: each time RESET is received from the HLR.

RECVD_RESTORE_DATA

Indicates how often the relevant message is received from a VLR.

Trigger: each time RESTORE DATA is received from the VLR.

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_MS

Number of switches to linked MS.

Trigger: each time an MTC is made to a double IMSI subscriber and the MSUB_2 mo-bility data was inactive.

SND_ACT_TRACEMODE

Indicates how often tracing is activated after a location update.

Trigger: each time ACTIVATE TRACEMODE is sent after a location update.

ADMIN_ACT_TRACEMODE

Indicates 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_TRACEMODE

Indicates how often tracing is deactivated due to subscriber administration.

Trigger: each time DEACTIVATE TRACEMODE is sent upon the MML command DACTIMSITRAC.

RECVD_ACT_FOLLOW_ME

Indicates how often follow me is activated.

Trigger: each time ACTIVATE FOLLOW ME is received from the MS.

RECVD_DEACT_FOLLOW_ME

Indicates how often follow me is deactivated.

Trigger: each time DEACTIVATE FOLLOW ME is received from the MS.

A50016-D1112-G802-1-7618 127


Counter Description

UNRELDIR

When 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_PSI

The 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. It Number of MAPmessages PROVIDE SUBSCRIBER INFO (contains either the last radio cell being af-fected by the subscriber or his status) that the HLR has sent to the VLR.

Trigger: each time the HLR receives– SEND ROUTING INFO from the gateway GMSC, or– ANY TIME INTERROGATION from the GSM service control function.

RECVD_ATI

Another 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. It Indicates how often the HLR has receivedan interrogation message directly from the CAMEL server (its address is included in ATIinvoke). This message drives the HLR for a dialog with the VLR.

Trigger: each time ANY TIME INTERROGATION is received from the GSM service con-trol function.

NUM_MAP_ATI_WITH_CL_REC

Number of all MAP:ATIs with current location that have been received in the HLR.

Trigger: each time the SCP sends MAP:ATI with Current Location flag.

NUM_NOT_ALLOW_MAP_ATI_REC

Number of not allowed MAP:ATIs with and without current location that have been re-ceived in the HLR.

Trigger: each time the check against RST fails.

NUM_MAP_PSI_WITH_CL_SEND

Number of MAP:PSIs with current location that are sent from the HLR.

Trigger: each time MPHCSG7_PSI_CREATE is called by SRI or ATI with Current Loca-tion.

NUM_MAP_SRI_REC_HLR_WITH_CL

Number of MAP:SRIs with current location received in the HLR.

Trigger: each time the SCP sends a MAP:SRI with Current Location flag.

NUM_NOT_ALLOW_MAP_SRI_REC_HLR

Number of not allowed MAP:ATIs with current location received in the HLR.

128 A50016-D1112-G802-1-7618


Trigger: each time the check against RST fails for SRI with Current Location.CSE

RECVD_CAMEL_ATSI

Indicates how many any time subscription interrogation requests have been received.

Trigger: each time an ATSI request is received from a gsmSCF.

RECVD_CAMEL_ATM

Indicates how many any time modification requests have been received.

Trigger: each time an ATM request is received from a gsmSCF.

SEND_CAMEL_NSDC

Indicates how many Notification of Subscriber Data Change messages have been sentto gsmSCF

Trigger: each time a sequence of NSDC messages is sent to the gsmSCF.

RECVD_POS_ACK_NSDC_FROM_GSMSCF

Indicates how many positive acknowledgements to NSDC have been received fromgsmSCF.

Trigger: each time a successful result message is received from the gsmSCF.

SENT_NI_USSD_TO_VLR

Indicates 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_A

Indicates how often the HLR of the calling side (A) receives a request from the MSC-Afor the 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_B

Indicates 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.

ORMMC_ALLOWED_IN_HLR

Indicates how many optimal routing calls for basic mobile to mobile calls are allowed inthe HLR.

Trigger: each time SRI with interrogation type basic and OR interrogation indicator is re-ceived and if “Roaming number” is included in SRI ack.

ORECF_ALLOWED_IN_HLR

Indicates how many optimal routing calls for early call forwarding are allowed in the HLR.

A50016-D1112-G802-1-7618 129


Counter Description

Trigger: each time SRI with interrogation type basic and OR interrogation indicator is re-ceived and if “Forwarded-to number” is included in SRI ack.

RECVD_AUTH_INF_REQUESTS

Indicates how many authentication requests has been received on MAP V3.

Trigger: each time SendAuthenticationInfo V3 request is received by the HLR from theVLR.

RECVD_RESYNCHRON_REQUESTS

Indicates how many resynchronization requests has been received on MAP V3.

Trigger: each time SendAuthenticationInfo V3 request for resynchronization is receivedby the HLR from the VLR.

RECVD_AUTH_FAIL_REP_REQ

Indicates how many authentication failure reports has been received on MAP V3.

Trigger: each time AuthenticationFailureReport V3 message is received by the HLRfrom the VLR.

7.4.2 Grade of Service Counters: Mobility Management

UNS_UPLOCMSG_VLR_HPLMN_SUB_BEH

Indicates 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 theVLR due to location update with an old SIM card, ODB of roaming, roaming not allowed,AOC not supported in the VLR.

UNS_UPLOCMSG_VLR_HPLMN_IRR_VLR

Indicates 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_SYS

Indicates 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 internalfailure in HLR) is sent to the VLR upon receipt of UPDATE LOCATION.

UNS_UPLOCMSG_VLR_VPLMN_SUB_BEH

Indicates 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 location update with old SIM card, ODB of roaming, roaming not allowed, AOCnot supported in the VLR.

130 A50016-D1112-G802-1-7618


UNS_UPLOCMSG_VLR_VPLMN_IRR_VLR

Indicates 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_SYS

Indicates 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_SUB

Indicates 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_OTHER

Indicates 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_MSG

Indicates 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_TRACEMODE

Indicates 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_BEH

Indicates how often follow me was activated unsuccessfully due to subscriber behavior.

Trigger: each time TC-END U-ERROR is sent on ACTIVATE FOLLOW ME.

UNS_ACT_FOLLOW_ME_SYS_BEH

Indicates 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_BEH

Indicates how often follow me was activated unsuccessfully due to subscriber behavior.

A50016-D1112-G802-1-7618 131


Counter Description

Trigger: each time TC-END U-ERROR is sent upon DEACTIVATE FOLLOW ME.

UNS_DEACT_FOLLOW_ME_SYS_BEH

Indicates 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_RCVD_PSI

Number of negative responses that the VLR returns to the PROVIDE SUBSCRIBERINFO requests (CAMEL service) from the HLR sent beforehand.

Trigger: each time the VLR sends a message to indicate an abort, a timeout, a rejectionor a user error in response to PROVIDE SUBSCRIBER INFO.

7.4.3 Grade of Service Counters: Call Handling

UNS_SNDROUTINFMSG_BLCKD_BARR

Indicates 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_VIOL

Indicates how often requests for routing information to the HLR are unsuccessfully han-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_ERROR

Indicates 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_BEH

Indicates 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_BEH

Indicates 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.

132 A50016-D1112-G802-1-7618


UNS_SNDROUTINFMSG_SEC_CAUSES

Indicates 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_LOC

Indicates 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 address isstored in the HLR.

UNS_RESTORE_DATA

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_BIC

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.

UNS_CALL_SS_BICROAM

Number of successful invocations of barring of all incoming calls when roaming outsidethe 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_BEH

Number of unsuccessful CCBS requests due to subscriber behavior (e.g., no CCBS re-call, timer expiry at calling side or at called side).

Trigger: each time the HLR receives a message indicating a CCBS cancel (timeout ofthe CCBS service timer or call supervision timer).

UNS_CCBS_REQ_OTHER

Number of unsuccessful CCBS requests due to system behavior (e.g., MAP errors, sys-tem failure).

Trigger: each time the HLR receives an error message after CCBS REQUEST, or whensuspend handling is concerned.

7.4.4 Grade of Service Counters: Subscriber Data

UNS_INS_SUBDT_MSG_SUB_ADMIN

Indicates how often the VLR has unsuccessfully handled a message with subscriberdata being initiated via subscriber administration.

A50016-D1112-G802-1-7618 133


Counter Description

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_ADMIN

Indicates 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_MS

Indicates how often the VLR has unsuccessfully handled a request to cancel locationbeing 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_OTHER

Indicates 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.

UNS_ACT_TRACEMODE_SUB_ADMIN

Indicates 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_ADMIN

Indicates 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_PR

Indicates 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_AR

Indicates 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:– Ph1: SEND PARAMETERS

134 A50016-D1112-G802-1-7618


– Ph2: SEND AUTHENTICATION INFO

UNS_SND_PARAM_AR_PR

Indicates 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.

UNS_AUTH_INF_REQ_UNAVAIL_AV

Indicates number of unsuccessful authentication requests on MAP V3 due to not avail-able authentication vector.

Trigger: each time HLR supervision timer for authentication calculation expires. No cal-culation result is coming back from AC.

UNS_AUTH_INF_REQ_OTHER

Indicates number of unsuccessful authentication requests on MAP V3 due to reasonother than not available authentication vector.

Trigger: each time authentication is rejected for a reason different than expiration of cal-culation supervision timer in HLR.

UNSUCC_RESYNCHRONISATION

Indicates number of unsuccessful resynchronization requests on MAP V3.

Trigger: each time HLR supervision timer for resynchronization calculation expires. Nocalculation result is coming back from AC.

UNS_CAMEL_ATSI

Number of unsuccessful ATSI requests.

Trigger: each time there is an error in the processing of the ATSI request.

UNS_CAMEL_ATM

Number of unsuccessful ATM requests.

Trigger: each time there is an error in the processing of the ATM request.

7.5 Subscriber Controlled Input


RECVD_MSG_REGISTER_SS

Indicates how often an SS is registered by SCI.

Trigger: each time REGISTER SS is received from the VLR.

RECVD_MSG_REGISTER_PW

Indicates how often an SS for password is registered by SCI.

Trigger: each time REGISTER PW is received from the VLR.

A50016-D1112-G802-1-7618 135


Counter Description

RECVD_MSG_ERASE_SS

Indicates how often an SS is erased by SCI.

Trigger: each time ERASE SS is received from the VLR.

RECVD_MSG_ACT_SS

Indicates how often an SS call wait is activated by SCI.

Trigger: each time ACTIVATE SS is received.

RECVD_MSG_DEACT_SS

Indicates how often an SS for call wait is deactivated by SCI.

Trigger: each time DEACTIVATE SS is received from the VLR.

RECVD_MSG_INTERROG_SS

Indicates how often each SS is interrogated by SCI.

Trigger: each time INTERROGATE SS is received from the HLR.

SENT_INSERT_MS_DATA_AFTER_SCI

Indicates 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_SCI

Indicates 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_INDIC

Indicates 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_DATA

Indicates how often an unstructured SS is requested.

Trigger: each time PROCESS UNSTRUCTURED SS REQUEST is received.

RECVD_MSG_REGISTER_CALLBACK

Indicates how often call back is registered.

Trigger: each time REGISTER SS (type “call back”) is received.

RECVD_MSG_ERASE_CALLBACK

Indicates how often call back is erased.

Trigger: each time ERASE SS (type “call back”) is erased.

RECVD_MSG_ACT_CALLBACK

Indicates how often call back is activated.

Trigger: each time ACTIVATE SS (type “call back”) is received.

136 A50016-D1112-G802-1-7618


RECVD_MSG_DEACT_CALLBACK

Indicates how often call back is deactivated.

Trigger: each time DEACTIVATE SS (“call back”) is received.

RECVD_MSG_INTERROG_CALLBACK

Indicates how often call back is interrogated.

Trigger: each time INTERROGATE SS (type “call back”) is received.

RECVD_CAMEL_USSD_TO_GSMSCF

Indicates 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.

SENT_SS_INV_NOTIF_TO_SCP

Indicates how many sent SS invocations are sent from the HLR to the SCP.

Trigger: each time the MAP message SSInvocationNotification is sent to the SCP.

RECVD_POS_ACK_FROM_SCP

Number of positive acknowledged SS invocations.

Trigger: each time the SSInvocationNotificationRes MAP message is received.

7.5.2 Grade of Service CountersSubscriber controlled inputs (SCI) can be handled successfully thanks to:– subscriber behavior: SCI may be affected by statements or restrictions, such as ille-

gal SS operation, SS error status, SS not available, SS specific error, BS or TS notprovisioned, SS subscription violation, SS incompatibility, bad password or invalidformat.

– irregular system behavior: The system may then not be able to reply to an SCI be-cause unknown subscriber, unexpected data value, data missing, system failure, orany other unsuccessful outcome is sent to the VLR.

UNS_RESP_REGISTER_SS_SUB_BEH

Indicates 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_BEH

Indicates 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_BEH

Indicates how many SCIs for REGISTER PW are unsuccessfully handled due to sub-scriber behavior.


A50016-D1112-G802-1-7618 137


Counter Description

UNS_RESP_REGISTER_PW_SYS_BEH

Indicates how many SCIs for REGISTER PW are unsuccessfully handled due to irreg-ular system behavior.


UNS_RESP_ERASE_SS_SUB_BEH

Indicates how many SCIs for ERASE SS are unsuccessfully handled due to subscriberbehavior.


UNS_RESP_ERASE_SS_SYS_BEH

Indicates how many SCIs for ERASE SS are unsuccessfully handled due to irregularsystem behavior.


UNS_RESP_ACT_SS_SUB_BEH

Indicates how many SCIs for ACTIVATE SS are unsuccessfully handled due to sub-scriber behavior.


UNS_RESP_ACT_SS_SYS_BEH

Indicates how many SCIs for ACTIVATE SS are unsuccessfully handled due to irregularsystem behavior.


UNS_RESP_DEACT_SS_SUB_BEH

Indicates how many SCIs for DEACTIVATE SS are unsuccessfully handled due to sub-scriber behavior.


UNS_RESP_DEACT_SS_SYS_BEH

Indicates how many SCIs for DEACTIVATE SS are unsuccessfully handled due to irreg-ular system behavior.


UNS_RESP_INTERROG_SS_SUB_BEH

Indicates how many SCIs for INTERROGATE SS are unsuccessfully handled due tosubscriber behavior.


UNS_RESP_INTERROG_SS_SYS_BEH

Indicates how many SCIs for INTERROGATE SS are unsuccessfully handled due to ir-regular system behavior.


138 A50016-D1112-G802-1-7618


UNS_RESP_INS_SUBDT_SS

Indicates 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_SS

Indicates 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_SS

Indicates how often a request to cancel a location is unsuccessfully handled due to anyother reason.

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_DATA

Indicates 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_CALLBACK

Indicates how many SCIs 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_CALLBACK

Indicates how many SCIs for ERASE CALLBACK are handled unsuccessfully.


UNS_RESP_ACT_CALLBACK

Indicates how many SCIs for ACTIVATE CALLBACK are handled unsuccessfully.


UNS_RESP_DEACT_CALLBACK

Indicates how many SCIs for DEACTIVATE CALLBACK are handled unsuccessfully.


UNS_RESP_INTERROG_CALLBACK

Indicates how many SCIs for INTERROGATE CALLBACK are handled unsuccessfully.


A50016-D1112-G802-1-7618 139


Counter Description

UNS_CAMEL_USSD_BY_HLR

Indicates 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.

UNS_CAMEL_USSD_BY_GSMSCF

Indicates 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).

RECVD_READY_FOR_SM

Number of times the HLR is informed that MS is ready to receive short messages.

Trigger: each time READY FOR SM is received in MAP Version >1.

7.6 Short Message Service


RECVD_SND_ROUTING_INFO_SM

Indicates how often routing info is requested for a short message.

Trigger: each time SEND ROUTING INFORMATION FOR SM is received.

RECVD_SET_MWD

Indicates how many messages delivering short message data have been received fromthe gateway 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_PRESENT

Indicates 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_CENTER

Indicates how often the service center for SMS is alerted.

Trigger: each time the HLR receives the respective message.– Ph1: NOTE SM PRESENT

140 A50016-D1112-G802-1-7618


– Ph2: READY FOR SM

SUCC_ALERT_SERVICE_CENTER

Number of successful alert messages to the service center.

Trigger: each time the HLR receives a successful ALERT SERVICE CENTER ACK(Ph 2).

SND_ALERT_SMSC_NO_RESULT

Number of times the HLR alerts the SMSC that the MS is ready to receive short mes-sages.

Trigger: each time SND_ALERT_SMSC_NO_RESULT: Number of Invoke componentalertServiceCentrewithoutResult (MAP V1) is sent by the HLR.

7.6.2 Grade of Service Counters

UNS_ADMBLCKD_OR_CALLBARR

Indicates 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_ERROR

Indicates 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_BEHAVIOR

Indicates how often a routing info request for an SM is handled unsuccessfully due toGMSC behavior.

Trigger: each time TC-U-ERROR is sent to GMSC in response to this request.

UNS_SUB_BEHAVIOUR

Indicates 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 response toSEND ROUTING INFO FOR SMS.

UNS_SECONDARY_CAUSES

Indicates 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_LOCATION

Indicates how often a routing info request for an SM is handled unsuccessfully due tolost location.

A50016-D1112-G802-1-7618 141


Counter Description

Trigger: each time TC-U-ERROR is received from the VLR in response to ProvideRoaming Number for SMS.

UNS_RECVD_SET_MWD

Indicates 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)

UNS_MS_PRESENT_TO_VLR

Number of times the HLR returns a returnError in response to readyForSM invoke com-ponent.

Trigger: each time ReturnError component is sent by the HLR in response to ready-ForSM.

7.7 Overload CountersThe 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_OVL

Indicates 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_OVL

Indicates 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_OVL

Indicates how many requests for parameters were handled unsuccessfully due to over-load.

Trigger: each time the respective message is rejected due to HLR overload.– Ph1: SEND PARAMETERS– Ph2: SEND AUTHENTICATION INFO

UNS_SS_OVL

Indicates how many SCIs were handled unsuccessfully due to overload.

Trigger: each time Register SS, Activate SS, Deactivate SS, ERASE SS are rejecteddue to HLR overload.

UNS_SMS_OVL

Indicates how often a routing info request for SM is lost due to HLR overload.

142 A50016-D1112-G802-1-7618


Trigger: each time SEND ROUTING INFORMATION for SMS is discarded (rejected)due to HLR overload.

7.8 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.


RECVD_LOCUPD_HPLMN

Indicates 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_VPLMN

Indicates 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.

SENT_CAN_LOC_SGSN_CHANGE

Indicates 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_ADMIN

Indicates 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_DATA

Indicates 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 or ENTR/CAN GPRSERV.

SENT_RESET_TO_SGSN

Indicates 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.

A50016-D1112-G802-1-7618 143


Counter Description

7.8.2 Grade of Service Counters

UNS_LOC_UPD_HPLMN_SUB_BEH

Indicates 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_BEH

Indicates how often a GPRS location update from the SGSN of the VPLMN was unsuc-cessfully handled by the VLR due to irregular subscriber behavior.

Trigger: 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_OTHER

Indicates 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_OTHER

Indicates 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.

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_CHANGE

Indicates 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_ADMIN

Indicates 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_DATA

Indicates 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.

144 A50016-D1112-G802-1-7618


8 Traffic Measurement in ACThe authentication center (AC) contains several security boxes that store the keys andalgorithms required for the creation of the authentication vectors: triples for 2G subscrib-ers and quintets for 3G subscribers.

A record of authentication vectors is generated for each mobile subscriber, usually be-fore entering the network. This record is filled up with new vectors each time the previ-ous ones have been used (replenish mechanism).

These vectors are used by the VLR for authentication tests, i.e., to prove whether a mo-bile subscriber is authorized to enter the network and to set up calls.

So, counters related to triple and quintet data are implemented in the AC on which trafficmeasurement relies.

A traffic measurement job is started by entering the REC AC command. The followingcounters are provided.

TRIPLES_REQUESTED_BY_HLR

Number of triples requested by the HLR.

Trigger: each time SEND PARAMETERS is received.

TRIPLES_RETURNED_TO_HLR

Number of triples returned to the HLR.

Trigger: each time SEND PARAMETERS RESULT is sent to the VLR.

REUSED_TRIPLES


Trigger: each time the request for triples from the HLR is unsuccessful due to an internalevent in AC.

QUINTETS_REQ_BY_HLR_IMM

Number of quintets requested by HLR for immediate requests.

Trigger: each time immediate authentication request is received from HLR.

QUINTETS_REQ_BY_HLR_NON_IMM

Number of quintets requested by HLR for non immediate requests.

Trigger: each time non immediate authentication request is received from HLR.

QUINTETS_REQ_BY_HLR_RESYNC

Number of quintets requested by HLR for resynchronization.

Trigger: each time resynchronization request is received from HLR.

QUINTETS_RET_TO_HLR_IMM

Number of quintets returned to HLR for immediate requests.

Trigger: each time AC returns quintets to HLR for immediate authentication.

QUINTETS_RET_TO_HLR_NON_IMM

Number of quintets returned to HLR for non immediate requests.

A50016-D1112-G802-1-7618 145


Counter Description

Trigger: each time AC returns quintets to HLR for non immediate authentication.

QUINTETS_RET_TO_HLR_RESYNC

Number of quintets returned to HLR for resynchronizations.

Trigger: each time AC returns quintets to HLR for resynchronization.

RECVD_AUTH_FAIL_REPORT_IN_AC

Number of authentication failure reports received by AC.

Trigger: each time authentication failure report is received from HLR.

QUINTETS_RET_TO_HLR_SUB_CREA

Number of quintets returned to HLR during subscriber creation.

Trigger: each time AC sends quintets to HLR during subscriber creation in AC database.

146 A50016-D1112-G802-1-7618


9 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 achieved by classifying each station in one of the following three lists.– White list for allowed mobile stations– Grey list for mobile stations to be observed– 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.It then replies to the MSC whether the IMEI is unknown or on the white, grey or blacklist. The counters implemented in the EIR are related to these lists

A traffic measurement job is started by entering the REC EIR command.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Structure- and installation-related• Grade of service

9.1 Structure- and Installation-related Counters

NO_OF_BLACK_IMEI

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_IMEI

Number of IMEIs in grey list of the EIR database.


NO_OF_WHITE_IMEI

Number of IMEIs in white list of the EIR database.


NO_OF_TAC_FAC

Number of areas (defined by the codes TAC and FAC) created in the EIR database.

Trigger: each time a new area entry in the white list is created by administration.

9.2 Grade of Service Counters

NO_OF_IMEI_CHECK_MESSAGES

Number of IMEI check messages received in the EIR.

Trigger: each time CHECK IMEI is received from MSC.

NO_OF_UNSUCC_MESSAGES

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.

A50016-D1112-G802-1-7618 147


Counter Description

NO_OF_BLACK_EQUIPMENT

Number of IMEI checks that directs to a black list.

Trigger: each time the EIR returns TC-RESULT indicating a black list status in responseto a CHECK IMEI.

NO_OF_GREY_EQUIPMENT

Number of IMEI checks that directs to a grey list.

Trigger: each time the EIR returns TC-RESULT indicating a grey list status in responseto a CHECK IMEI.

NO_OF_WHITE_EQUIPMENT

Number of IMEI checks that directs to a white list.

Trigger: each time the EIR returns TC-RESULT indicating a white list status in responseto a CHECK IMEI.

NO_OF_UNKNOWN_EQUIPMENT

Number of IMEI checks resulting in unknown equipment.

Trigger: each time TC-U-ERROR indicating “unknown equipment” is returned to MSC inresponse to CHECK IMEI.

148 A50016-D1112-G802-1-7618


10 Traffic Measurement Related to LocationAreaA number of counters are implemented for the measurement of traffic between locationareas. Since the sizing of location areas versus MSC/ VLR areas has a strong impacton the load caused by location update and paging procedures, data within this respectis 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.

A traffic measurement job is started by entering the REC LOCAREA command. The fol-lowing counters are provided.

PAG_PROC

Indicates how many paging procedures started for MTER.

Trigger:each time PAGING is sent.

RETRY_PAG

Indicates how many paging retry procedures started for MTER.

Trigger: each time PAGING is sent after expiry of the paging timer.

SUCC_PAG

Number of successfully completed paging procedures.

Trigger: each time PAGING RESPONSE is received.

LOC_UPD

Number of received requests for location updating.

Trigger: each time COMPLETE LAYER 3 containing LOCATION UPDATE REQUESTis received.

NO_OF_MS

Indicates how many mobile subscribers registered in the location area.

Trigger: increases upon creation of entry, decreases upon deletion of entry.

NO_OF_AMS

Number of attached mobile subscribers in the location area.

Trigger: upon set/reset of detach state in the VLR.

REQ_COM_PAG

Indicates 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).

A50016-D1112-G802-1-7618 149


Counter Description

SEC_COM_PAG

Indicates 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.

SUCC_COM_PAG

Indicates 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).

150 A50016-D1112-G802-1-7618


11 Traffic Measurement Related to CellsA number of cell-related counters is implemented for measuring the traffic on each indi-vidual radio cell and its associated resources. The measurements retrieve data on theradio interface in order to plan and to dimension the entire radio service area. This cell-related traffic measurement is started by entering the REC INTCELL command and se-lecting the INTCREL parameter.

For 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. The measurementof such cell-related traffic data is started by entering the REC INTCELL command andselecting the HOTRFS parameter causing the handover counters to run for all cells.

Each output matrix contains two fields: a LACOD field and a cell identifier (CI) field. For2G traffic the latter is filled with the CI (Cell Identity), whereas for 3G traffic it is filled withthe SAC (Service Area Code). There are two matrices:– 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.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:• Load and demand (see chapter 11.1),• Handover (see chapter 11.2),

11.1 Load and Demand Counters

ORIG_CALL_ATTEMPTS

Number of attempted calls for mobile originating traffic.

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_ATTEMPTS

Number of attempted calls for mobile terminating traffic.

Trigger: each time PAGING RESPONSE is received.

ORIG_CALL_ATT_TCH_REQ

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_REQ

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_QUEUING

Number of attempted originating calls where queuing was active for mobile originatingtraffic.

A50016-D1112-G802-1-7618 151


Counter Description

Trigger: each time the QUEUING INDICATION is received.

INCOM_CALL_ATT_QUEUING

Number of attempted incoming calls where queuing was active for mobile terminatingtraffic.

Trigger: each time the QUEUING INDICATION is received.

ORIG_CALL_SUCC_TCH_ALLOC

Number of mobile originating calls with successful traffic channel allocation.

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).

INCOM_CALL_SUCC_TCH_ALLOC

Number of mobile terminating calls with successful traffic channel allocation.

Trigger: upon each receipt of ASSIGNMENT COMPLETE without previous queuing. Itcan also be (internally) triggered in the same way as described for originating calls.

ORIG_CALL_QUEUE_TCH_ALLOC

Number of attempted originating calls for which queuing is active and a traffic channelwas successfully allocated for mobile originating traffic.

Trigger: each time ASSIGNMENT COMPLETE is received after receipt of QUEUING IN-DICATION.

INCOM_CALL_QUEUE_TCH_ALLOC

Number of attempted incoming calls for which queuing was active and a traffic channelwas allocated successfully for mobile originating traffic.

Trigger: each time ASSIGNMENT COMPLETE is received and queuing is active.

REL_CALL_BS_REASON

Number of calls that were terminated during setup for base station/radio-related rea-sons.

Trigger: during call setup, prior to CONNECT, each time SUBSYSTEM PROHIBITED,RESET, RESET CIRCUIT, RELEASE COMMAND/CLEAR REQUEST are received.

REL_ANSW_CALL_BS_REASON

Number of answered calls that are terminated for base station/radio-related reasons.

Trigger: after CONNECT ACK, each time SUBSYSTEM PROHIBITED, RESET, RESETCIRCUIT, RELEASE COMMAND/CLEAR REQUEST are received.

ANSW_ORIG_CALL

Number of answered calls for mobile originating traffic.

Trigger: release of call when previous CONNECT ACK is received.

ANSW_INCOM_CALLS

Number of answered calls for mobile terminating traffic.

152 A50016-D1112-G802-1-7618


Trigger: release of call when previous CONNECT ACK is received.

11.2 Handover Counters

HO_REQUIRED

Indicates how many handover requests have been received.

Trigger: each time HANDOVER REQUIRED is received.

INTRACELL_HO_MSC

Number of successfully performed MSC controlled intra-cell handovers.

Trigger: each time HANDOVER COMPLETE is received.

INTRACELL_HO_BSC

Number of successfully performed BSS controlled intra-cell handovers.

Trigger: each time HANDOVER PERFORMED is received.

INTERCELL_HO_OUTG

Number of successfully performed outgoing inter-cell handovers.


INTERCELL_HO_INC

Number of successfully performed incoming inter-cell handovers.


SUCCESSFUL_HANDOVERS

Indicates for each origin/target cell the respective handovers being completed success-fully.


CA_HO

Number of handover requests.

CC_HO

Number of successful handover requests.

A50016-D1112-G802-1-7618 153


Counter Description

12 Counter Calculations for Traffic MonitoringMonitoring functions enable the PLMN operator to monitor mobile-specific traffic countercalculations (such as counter ratios and sum or differences of counters), indicating thesuccess rate of certain functions in the network elements. This chapter indicates thefunctions to be monitored and the counters used, together with the calculation on whicha certain value is based. (The traffic counters are described in this manual.)

Mobile-specific traffic can be monitored in two different ways:– By the OMC– By the network nodes: MSC/VLR, HLR/AC, EIR

Monitoring by the OMC

Monitoring can be fully supported by the network elements. However, the OMC. alsoprovides customized monitoring. The OMC collects traffic measurement data from thenetwork elements in order to centralize all traffic handling results. Each NE has only toprovide the OMC with the measured traffic counters. Therefore, the PLMN operator hasto activate the mobile traffic data collection using the ACT MTRDCOL command. Thetransfer of the measured values to the OMC then starts every 15 minutes. The actualmonitoring, the administration of thresholds, and the generation of alarms is completelycovered by applications in the OMC. This applications are manufacturer-dependent andare therefore not described in this manual.

Monitoring by the network nodes

Activating a monitoring function implies that the system calculates the counter measure-ments and compares the results with operator-defined threshold values. Every 15 min-utes, the monitoring function compares the counter functions with the operator-definedthreshold values. If these threshold values are exceeded, alarms are generated by theOMC. In this way, on-line information about the quality of service and the current loadcondition is received at any time.

The PLMN operator can activate mobile user monitoring for one specific option usingthe ACT MUSMON command; up to 38 options can be activated in parallel. Prior to ac-tivation, the PLMN operator has to associate at least 1 of 3 possible threshold ranges toeach control function, indicating the severity level: minor, major or critical. This is doneusing the ENTR MUSMON command.

Each level is defined by a pair of threshold values:– A lower value at which an alarm is to be generated– An upper value at which the alarm is to be cleared

Tab. 12.1 summarizes all possible traffic counter functions that can be monitored by thePLMN operator. It also shows the network node to which the function applies and theformulas used to implement the mounting function. The options are listed in alphabeticalorder:

154 A50016-D1112-G802-1-7618


Option NE Calculation

ACDCSUCC(Answered call – droppedcall rate)

MSC/VLR100% x

REL_ANSW_CALL_BS_REASON————————————————ANSW_ORIG_CALL+ ANSW_INCOM_CALLS+ REL_ANSW_CALL_BS_REASON

AUTHPROC(Authenticationproceduresuccess rate)

MSC/VLR

100% x

AUTH_REQ+ AUTH_REQ_WITH_AUTN– AUTH_WITH_ILLEGAL_SUB– AUTH_SYNCHRON_FAIL_RECEIVED———————————————————AUTH_REQ+ AUTH_REQ_WITH_AUTN– AUTH_WITH_ILLEGAL_SUB

CIPHCTRL(Ciphering mode controlprocedure success rate)

MSC/VLR

100% x

SUCC_CIPH_MODE_CTRL_PROC+ RNC_CIPHERING_SUCC—————————————————CIPHERING_REQ+ RNC_CIPHERING_REQ

CSDCSUCC(Call setup – dropped callrate)

MSC/VLR100% x

REL_CALL_BS_REASON————————————ORIG_CALL_ATTEMPTS+ INCOM_CALL_ATTEMPTS

EMERANSW(Emergency call answerrate)

MSC/VLR .100% x

TS12_EMERG_WITH_ANSWER————————————————EMERGENCY_TS12_ATTEMPTS

EMERSUCC(Emergency call successrate)

MSC/VLR100% x

TS12_EMERG_CALL_TCH_ALLOC for MORTR———————————————————————EMERGENCY_TS12_ATTEMPTS for MORTR

EMPRESPA(Empty response on au-thentication set requestrate)

MSC/VLR100% x

RECVD_SEND_PARAM_AR+ RECVD_AUTH_INF_REQUESTS——————————————————EMPTY_RESPONSE_TO_AUTH_SET

HLRINTER(HLR interrogation suc-cess rate for interrogationby VLR)

MSC/VLR

100% x

INTERROG_TO_HLR– INTERROG_UNSUCC_SUBSCR– INTERROG_UNSUCC_SYSTEM—————————————————INTERROG_TO_HLR

HOFAIL(Outgoing external intra-MSC handover successrate)

MSC/VLR

100 –

SUCC_COMPLETED_HO+ SUCC_MSC_MSC_HO_MSCA+ SUCC_HO_SEC_MSC_MSC_HO_MSCB——————————————————————x 100%HANDOVER_CONFERENCE

Tab. 12.1 Options for counter-based calculations

A50016-D1112-G802-1-7618 155


Counter Description

HONOTALO(Handover not allowed)

MSC/VLR100 –

HO_CONFERENCE——————————————————————x 100%HANDOVER_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCA– SUBSEQ_MSC_MSC_HO_MSCB

HOSUCC(Unsuccessful externalhandover rate)

MSC/VLR

100% x

SUCC_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

HOTRFS(Handover traffic flowstructure success rate percell)

MSC/VLR .100% x

HO_OLD_CELL————————————————HANDOVER_ATTEMPTS

IDREQVLR(Identification requests toPVLR success rate)

MSC/VLR

100% x

IDENTITY_REQUESTS+ IDENTITY_REQUESTS_UMTS– IDENT_REQ_CORR_FAILURE– IDENT_REQ_INTW_PVLR_FAILURE– IDENT_REQ_AUTH_FAILURE——————————————————IDENTITY_REQUESTS+ IDENTITY_REQUESTS_UMTS

INSSUBDA(Insert subscriber dataservice success rate)

HLR/AC

100% x

SND_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

INTERVLR(Inter–VLR location up-date success rate)

MSC/VLR .

100% x

VLR_CHANGES_PVLR_KNOWN+ VLR_CHANGES_PVLR_UNKNOWN———————————————————REQUESTS_LOCUPD_INTER_VLR

INTMSCA(Outgoing inter-MSC han-dover success rate)

MSC/VLR .100% x

SUCC_MSC_MSC_HO_MSCA————————————————————HANDOVER_MSC_MSC_OG_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCA



156 A50016-D1112-G802-1-7618


INTMSCB(Incoming inter-MSC han-dover success rate)

MSC/VLR

100% x

SUCC_MSC_MSC_HO_MSCB+ SUCC_SUBSEQ_MSC_MSC_HO_MSCB—————————————————————HANDOVER_MSC_MSC_IC_ATTEMPTS+ SUBSEQ_MSC_MSC_HO_MSCB

INTRAMSC(Incoming external intra-MSC handover successrate)

MSC/VLR

100% x

SUCC_COMPLETED_HO+ SUCC_HO_SEC_MSC_MSC_HO_MSCB————————————————————HANDOVER_ATTEMPTS– HANDOVER_MSC_MSC_OG_ATTEMPTS– SUBSEQ_MSC_MSC_HO_MSCB

INTRAVLR(Intra–VLR location up-date success rate)

MSC/VLR

100% x

SUCC_REQUESTS_LOCUPD+ SUCC_LOCUPD_WITH_IMSI_ATTACH– LOCUPD_LAI_NULL– VLR_CHANGES_PVLR_KNOWN– VLR_CHANGES_PVLR_UNKNOWN——————————————————REQUESTS_LOCUPD_INTRA_VLR

LUPSUCC(Location update successrate)

MSC/VLR

100% x

SUCC_LOCUPD_WITH_IMSI_ATTACH+ SUCC_REQUESTS_LOCUPD——————————————————REQUESTS_LOCUPD

MOCANSW(MOC answer rate)

MSC/VLR

100% x

SPEECH_CALLS_WITH_ANSWER for MOUT PLMN+ SPEECH_CALLS_WITH_ANSWER for MOUT NOT PLMN+ DATACDA_ANA_WITH ANSWER for MOUT PLMN+ DATACDA_ANA_WITH ANSWER for MOUT NOT PLMN+ DATACDA_DIG_WITH ANSWER for MOUT PLMN+ DATACDA_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



A50016-D1112-G802-1-7618 157


Counter Description

MOCSETUP(MOC setup rate)

MSC/VLR100% x

GEN_TRAFF_CHAN_REQ for MORTR——————————————————CALL_ATTEMPTS for MORTR– CALL_END_CALL_FORW for MORTR

MOSMS(MO SMS forwarding suc-cess rate)

MSC/VLR100% x

SUCC_SMS_SEND_RP_ACK——————————————SMS_SER_REQ_ATTEMPTS

MOSMSUCC(MO SMS success rate)

MSC/VLR100% x

SUCC_SMS_OTG———————————SMS_OTG_ATTEMPTS

MSMEMAV(MS memory availablenotification success rate)

MSC/VLR100% x

SUCCESS_MS_MEMORY_AVAIL————————————————MS_MEMORY_AVAIL_TO_HLR

MTCANSW(MTC answer rate)

MSC/VLR

100% x

SPEECH_CALLS_WITH_ANSWER for MTER+ DATACDA_ANA_WITH_ANSWER for MTER+ DATACDA_DIG_WITH_ANSWER for MTER+ ALTFAXSP_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+ INC_HO_WITH_ANSWER—————————————————————CALL_ATTEMPTS for MTER+ MSC_MSC_HO_CALL_ATTEMTS for MTER

MTCSETUP(MTC setup rate)

MSC/VLR100% x

GEN_TRAFF_CHAN_REQUEST for MTER—————————————————————RECEIVED_PAGING_RESPONSE for MTER

MTSMS(MT SMS forwarding suc-cess rate)

MSC/VLR100% x

SUCC_SMS_INC———————————SMS_INC_ATTEMPTS

MTSMSUCC(MT SMS success rate)

MSC/VLR100% x

SUCC_SMS_INC———————————SMS_INC_ATTEMPTS

PAGEREQ(Page request successrate)

MSC/VLR100% x

SUCC_PAG————————PAG_PROC+ RETRY_PAG

REQAUTH(Request for authentica-tion set success rate)

HLR/AC

100% x

RECVD_SEND_PARAM_AR+ RECVD_AUTH_INF_REQUESTS– UNS_SND_PARAM_AR– UNS_AUTH_INF_REQ_UNAVAILABLE_AV– UNS_AUTH_INF_REQ_OTHER—————————————————————RECVD_SEND_PARAM_AR+ RECVD_AUTH_INF_REQUESTS



158 A50016-D1112-G802-1-7618


REQMSRN(Request for SMS suc-cess rate)

HLR/AC .100% x

RECVD_MSRN——————————SND_PROV_MSRN

REQSMROU(Request for SM routinginformation success rate)

HLR/AC

100% x

RECVD_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

SENDAL(Send alert for SMS suc-cess rate)

HLR/AC100% x

SUCC_ALERT_SERVICE_CENTER—————————————————SND_ALERT_SERVICE_CENTE

SMDELIV(SM delivery status reportprocedure success rate)

MSC/VLR

100% x

SMS_INC_ATTEMPTS+ SMS_OTG_ATTEMPTS– UNS_SMS_INC_DELIVERY_FAIL– UNS_SMS_OTG_DELIVERY_FAIL—————————————————SMS_INC_ATTEMPTS+ SMS_OTG_ATTEMPTS

SSRELOP(SS-related operations inHLR success rate)

HLR/AC

100% x

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_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



A50016-D1112-G802-1-7618 159


Counter Description

Moreover, particular results can be calculated from the delivered counter values or dis-played at an OMC by means of the formulas in Tab. 12.2. This table also states theMML commands to collect the respective counters.

SUBMSCA(Subsequent inter-MSChandover (MSC-A) suc-cess rate)

MSC/VLR

100% x

SUCC_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(Subsequent inter-MSChandover (MSC-C) suc-cess rate)

MSC/VLR100% x

SUCC_SUBSEQ_MSC_MSC_HO_MSCB———————————————————SUBSEQ_MSC_MSC_HO_MSCB

TMSIREAL(TMSI reallocation suc-cess rate)

MSC/VLR100% x

SUCCESSFUL_TMSI_REALLOC——————————————————ATTEMPTED_TMSI_REALLOCATIONS

UNIMEI(Unknown IMEI answerrate)

MSC/VLR100% x

NO_OF_UNKNOWN_EQUIPMENT————————————————NO_OF_IMEI_CHECK_MESSAGE



Result Formula Description MMLcommand

average call setup time(s)

TIME_CALL_SET_U_SERV———————————————NUM_CALL_SET_UP_CONTRIB

The average time of a call setupcan be derived from the durationof each call setup service dividedby the number of call setups

REC MSC

average location updatetime (s)

TIME_LUP_SERV——————————NUM_LUP_CONTRIB

A similar formula applies to theaverage time of a location updat-ing

REC MSC

mean IWE holding time(s)

traffic volume(e.g.TV_IWE_FAX3_TP)———————————————call attempts (e.g.,IWE_FAX3_TP)

Various counters deliver themean holding time of IWE circuit.E.g., the total time an IWE for FaxGr3 T at a certain rate has beenconnected, divided by the numberof attempts to interconnect thisIWE circuit

REC IWE

GP load (milliErl)1000 –

GP_IDR x GP_MEA ( s) ———————————900,000 (ms)

The operational load on a GP canbe calculated by subtracting theload caused by routine tests dur-ing an interval of 900 seconds

REC LTG

Tab. 12.2 Calculations with OMC output

160 A50016-D1112-G802-1-7618


TOTAL CALLS CC+ CCU ATB+ CCU TECHN IRREGULAR+ CCU ANGRP BLOCKED

With respect to an announcementgroup the number of seizures canbe displayed on an OMC

REC ANGRP

SUCCESSFUL CALLS CC– CCS_TECHN_IRREGULAR

The number of accepted seizurescan be displayed

REC ANGRP

TC_N (deciErl)

TC (deciErl)

TC x 10.000———————————900 x SEIZE_MAXIMUM

(TV x 4 x 10) + 450—————————900

The normalized traffic (i.e., thecapacity rate without the specificline broadcasting into account)can be displayed. It is based onthe value of carried traffic (TC)that relies on the count of trafficvolume

REC ANGRP

plausibility check: 900 s DUR_LINK_IN_SERVICE+ DUR_UNA_LINK

A plausibility check can be madewith the in–service time of aCCS7 signaling link and its dura-tion of unavailability

RECC7GOS

DUR_UNA_LINK DUR_UNA_LINK_FAILURE+ DUR_UNA_LOCAL_BLK+ DUR_UNA_REMOTE_BLK+ DUR_UNA_BOTH_BLK

The total duration of unavailabilityof a CCS7 signaling link is com-posed with 4 counter results

RECC7GOS

total overload messages (n BSCs) x NUM_SEND_OVERLOAD

The total number of overloadmessages sent by the MSC is cal-culated in postprocessing by tak-ing the number of BSCs intoaccount

REC MSC

Result Formula Description MMLcommand

Tab. 12.2 Calculations with OMC output

A50016-D1112-G802-1-7618 161


Counter Description

13 General CN Traffic MeasurementTraffic measurement also provides counters for data about the general units of the corenetwork (CN) suited for planning and configuration purposes. The general units areused for the PLMN traffic as well as for PSTN traffic. The traffic counters for generalmeasurements are described in this chapter for the following network components:• trunk groups (see chapter 13.2)• destinations (see chapter 13.3)• coordination processor (see chapter 13.4)• line/trunk groups (see chapter 13.5)• group processor in the LTG (see chapter 13.6)• digital line unit (see chapter 13.7)• announcement groups (see chapter 13.8)

13.1 General InformationInformation on the quality and availability of the recorded data is contained in differentCN measurements and explained for all of them in this chapter.

Upon retrieving the measurement results via a traffic file, some additional information onthe outcome of the measurement is inserted. Each result includes information on thedata quality and availability of the measurement, besides some other aspects thatmay differ from unit to unit. The aspects displayed at the OMC differ from those recordedon tape.• Data quality

The output indicates once per measurement interval (15 minutes) whether data cor-ruption has taken place. On the OMC the state is displayed at the end of each linewhile number and state are recorded on tape as follows:

• AvailabilityThe output at the end of the measurement interval indicates whether data for the re-spective unit was available. On the OMC, the state is displayed at the end of eachline while number and state are recorded on tape as follows:

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 OMC

<============> 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 OMC

<=======> added to each record on tape

162 A50016-D1112-G802-1-7618


13.2 Trunk Group Traffic MeasurementThe assignment and utilization of trunk groups in PLMN is the same as in PSTN and therelevant traffic data apply to nodes from both networks. Therefore, the traffic measure-ment functions can be used by the MSC operator without any mobile-specific alter-ations.

The new, additional procedures used during call setup at the radio interface (e.g., pag-ing procedure, authentication, ciphering) are executed via a signaling connection (SC-CP). These procedures do not use trunk-group-related resources and have no influenceon the grade of service of the trunk groups.

This traffic measurement is started by entering the REC TGRP command.

Constants inserted during file transfer

Index and operation mode are additional constants being inserted when the counterresults are retrieved via a traffic file at the OMC in order to allow the measured data tobe allocated.• Index

All data about trunk groups is sorted by a control index when transferred to the CPhard disk. As far as the type of trunk group has been implemented, the relevantcounter data is transferred. Otherwise, some indices may not be indicated duringmeasurement. The following indices (1– 8) refer to counters for specific kind of data:

• Operation modeEach trunk group is identified by its number, and has one of the following codes in-dicating the operation mode:

1. seizure and traffic volume data2. additional trunk group data3. data on successful calls without reaching their destination4. data on refused calls5. data on refused calls at CCS7 trunk groups6. data on non-hierarchical trunk groups (not mobile-specific)7. data on non-hierarchical trunk groups (not mobile-specific)8. data on enhanced multilevel precedence and preemption

IC: incoming trafficOG: outgoing trafficBW: bothway traffic

A50016-D1112-G802-1-7618 163


Counter Description

13.2.1 Index 1: Seizure and Traffic Volume Counters

CC:I (O)

Indicates how often a trunk group was seized, i.e., carried calls (CC) in CP database, byincoming (outgoing) traffic in ERLS.

Trigger: start and stop depend on the message of the respective trunk type:– starts at receipt (sending) of IAM: for ISDN trunks, and

at sending of ASSIGNMENT REQ or HO REQ: for BSSAP trunks.– stops at release of trunk, e.g., REL COM.

TC:I (O)

Indicates the sum of holding times, i.e., traffic volume (TV), for seizures of a trunk groupthrough incoming (outgoing) traffic in ERLS.

Trigger: start and stop depend on the message of the respective trunk type:– starts at receipt (sending) of IAM: for ISDN trunks, and

at 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.

TC_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) in ERLS.

13.2.2 Index 2: Additional Trunk Group Counters

CONNECTED LINES

Number of connected trunks. With respect to a bothway trunk group, this represents thetotal number of trunks set up for IC and OG.

NO OF BLO LINES

Traffic load in ERLS which has not been handled because a number of trunks in thegroup were blocked during the measurement interval.

SEMI BLOCKED LINES

Number of trunks blocked semipermanently for O&M reasons. The counter indicates thecurrent value at the end of each quarter hour.

TRANS BLOCKED LINES

Number of trunks blocked transiently (i.e., blocking status is not caused by any O&Mreason in the home exchange). The value is updated at the end of each quarter hourand applies to IC and OG.

Trigger: actual number of transiently blocked trunks at the end of the measured interval.

164 A50016-D1112-G802-1-7618


TC SEMI BLOLI

Sum of blocking durations (traffic volume) due to maintenance caused by semiperma-nent trunk blocking in ERLS.

TC TRANS BLOLI

Volume counter for transiently blocked trunks in the group in ERLS; see also “TRANSBLOCKED LINES”.

TGRP BLO TIME: O

Indicates 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 TIME

Total 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 ATB

Number of occurrences of ATB, i.e., the number of times that all available trunks in thegroup were busy.

Trigger: each time the last free trunk in the group is seized.

13.2.3 Index 3: Counters for Successful Calls not Reaching Destination

CCS CONGESTION

Number of calls released after trunk group seizure (CC:O) because the backward signalfor “congestion” (all trunks busy) was received in the subsequent MSC.

CCS INCMP DIAL

Number of calls released after trunk group seizure (CC:O) because calling party goeson-hook after incomplete dialing or interdigit timeout in the own MSC.

CCS LINK FAILURE

Number of calls released after trunk group seizure (CC:O) because access to the out-going trunk was not possible. Call release is initiated by the LTG at the called end.

CCS UNALL NUM

Number of calls released after trunk group seizure (CC:O) because the dialed directorynumber was not created or because the calling party is not authorized to make calls tothis destination (CUG, service).

CCS RELORIG ENDTOEND

Number of calls released after trunk group seizure (CC:O) due to “clear forward” fromthe previous MSC without knowledge of the reason for release.

A50016-D1112-G802-1-7618 165


Counter Description

CCS SUB BUSY

Number of calls released after trunk group seizure (CC:O) because the backward signal“subscriber terminal busy” was received.

CCS INT TECHN IRREG

Number of calls released after trunk group seizure (CC:O) due to technical fault (e.g.,LTG failure on A- or B-side) in the own MSC.

CCS EXT TECHN IRREG

Number of calls released after seizure of the outgoing trunk group (CC:O) due to a tech-nical fault in the subsequent MSC after SN through-connection.

CCS UNANSWERED

Number of calls released after trunk group seizure (CC:O) because the called partydoes not answer (timeout of ringing time supervision) or because the calling party of theown MSC or the incoming call goes on-hook during ringing.

13.2.4 Index 4: Counters for Refused Calls

CCU SUM OFL/LOSS

Number of unsuccessful attempts to seize the trunk group. This represents the sum ofoverflow calls and lost calls. For trunk groups in the high-usage route or final route, itrepresents the sum of lost calls.

CCU LOST CALLS

Number of calls offered to the trunk group as first-choice route which then overflowedbut were unsuccessful in all alternative routes. This also includes calls rejected after be-ing offered to the final trunk group as first-choice route.

CCU NM TGRP BLOCKING

Number of attempts to seize the trunk group rejected due to network management ac-tions (e.g.: cancel, skip) in the trunk group (lost calls).

Trigger: at each attempt to seize a trunk group blocked by network management.

CCU TECHN IRREGULAR

Number of attempts to seize the trunk group rejected due to a technical fault when en-tering the trunk busy status or due to SN blocking (no access to outgoing trunk) (lostcalls).

CCU TGRP BLOCKED

Number of calls offered to a trunk group which overflowed (high-usage circuit group) orwere rejected (final circuit group or only-choice circuit group) because the trunk groupwas blocked for administration or maintenance.

CCU TRUNK RESERVATION

Number of calls offered to trunk group which overflowed (high-usage circuit group) orwere rejected (final circuit group or only-choice circuit group) because the trunks in thegroup were reserved.

166 A50016-D1112-G802-1-7618


CCU ALL TRUNKS BUSY

Number of calls offered to a trunk group which overflowed (high-usage circuit group) orwere rejected (final circuit group or only-choice circuit group) because all the trunks inthe group were marked busy in the CP.

13.2.5 Index 5: Counters for Refused Calls at CCS7 Trunk Groups

NUMB CCS7 DPC OLOAD

Number of occurrences on which destination point code (DPC) overload was recordedfor the CCS7 trunk group.

CCS7 DPC OLOAD

Indicates the overload duration (in seconds) due to DPC overload in the CCS7 trunkgroup.

CCS CCS7 CALL FAIL

Number of calls released after trunk group seizure (CC:O) because the line signal CALLFAILURE (for TUP) was received, or because certain line signals (IUC for ISUP) inCCS7 messages were received, from which RCF CALL FAILURE was derived..

CCU CCS7 CCNC OLOAD

Number of calls offered to a circuit group with CCS7 signaling which overflowed (high-usage circuit group) or were rejected (final circuit group or only-choice circuit group) dueto CCNC overload in the own MSC.

CCU CCS7 DPC OLOAD

Number of calls offered to a circuit group with CCS7 signaling which overflowed (highusage circuit group) or were rejected (final circuit group or only-choice circuit group) dueto DPC overload in the subsequent MSC.

CCU CCS7 DPC OL ACC

Number of calls offered to a circuit group with CCS7 signaling which overflowed (high-usage circuit group) or were rejected (final circuit group or only-choice group) becausethe transmission buffer of the links for the selected outgoing server was full.

13.2.6 Index 6 and 7: Counters for 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: O

Number of calls carried at the direct trunk group by successful outgoing seizures (con-nection is switched through SN).

TC: NH DIRECT: O

Indicates the traffic volume handled at the direct trunk group on successful outgoing sei-zures.

A50016-D1112-G802-1-7618 167


Counter Description

CCS NH DIRECT ANSW: O

Number of outgoing calls being successfully seized in the direct trunk group, and an-swered on the called terminal.

CCU NH DIRECT OFL

Number of those unsuccessful attempts for seizing in a direct trunk group, that result intoan overflow to an alternative trunk group.

CC:NH ALT1: O

Number of calls carried at the alternative trunk group (first-choice) because of success-ful outgoing seizures (connection is switched through the SN).

TC NH ALT1: O

Indicates the traffic volume handled by the alternative trunk group because of successfuloutgoing seizures.

CCS NH ALT1 ANSW: O

Number of outgoing calls being successfully handled in the alternative trunk group, andanswered on the called terminal.

CC NH ALT1 REROUTING

Number of events for outgoing seizures of an alternative trunk group which have beenrerouted to another trunk group; for example, because the next exchange finds no freetrunk.

CCU NH ALT1 LOST

Number of unsuccessful attempts to seize an alternative trunk group which cannot bererouted any longer to search for a free trunk.

CC: NH ALT2: O / CCS NH ALT2 ANSW: O

These 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 ALT2

Number of unsuccessful attempts to seize an alternative trunk group (second-choice).

13.2.7 Index 8: Enhanced Multilevel Precedence and Preemption Counters

CC PRECEDENCE:O

All outgoing seizures which have a precedence level (exceeding the routine). Note thatthe counter is incremented on releasing the trunk and not when it is seized.

CC PREEMPTED:O

All outgoing seizures which were released forcibly because of a precedence seizure (ora seizure for precedence traffic).

CC PRECEDENCE:I

All incoming seizures which have a precedence level (exceeding the routine). Note thatthe counter is incremented on releasing the trunk and not when it is seized.

168 A50016-D1112-G802-1-7618


CC PREEMPTED:I

Incoming seizures which were released forcibly because of a precedence seizure (or aseizure for precedence traffic).

13.3 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.

This measurement can be started by the REC DEST command by specifying the desti-nation group as an object group. A maximum of 512 internal and external destinationssimultaneously 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 OMC in order to allow the mea-sured data to be allocated:• Index

Index 50 or 51 is used only at the tape interface for data control.• DESTLAC

The 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.

CC

Indicates 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, for example, C:SETUP C and C:SEI-ZURE C BT have been sent from the CP to the LTGs.

TC

Total holding time (traffic carried in dErl).

TC WITH ANSWER

Sum 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, for example, 1800 seconds isadded. This intermediate time can be administered in the CP.

A50016-D1112-G802-1-7618 169


Counter Description

CCS CCS7 CALL FAIL

Number of calls that, after being connected by the SN of the home MSC, are rejectedupon receiving line signal CALL FAILURE.

CCS CONGESTION

Number of calls that, after being connected by the SN of the home MSC, are rejectedupon receiving line signal “congestion”.

CCS INCMP DIAL

Number of calls that, after being connected by the SN of the home MSC, are releasedbecause the calling party went on-hook after incomplete dialing or because interdigittime supervision timed out in the home MSC.

CCS LINK FAILURE

Number of calls released by the LTG after connection through the SN because at the B-side the group switch could not be set in the LTG or DIU, or because no free time slotcould be seized.

CCS UNALL NUM

Number of calls that, after being connected by the SN of the home MSC, are releaseddue to “number unobtainable” in the subsequent MSC.

CCS OPERATOR RELEASE

Number of calls released by the operator after connection through the SN; for example,because an audible “busy” tone was received. (only for outgoing operator traffic.

CCS RELORIG ENDTOEND

Number of calls that, after being connected by the SN of the home MSC, are releaseddue to a CLEAR FORWARD from the home MSC, without indicating the actual reasonfor call failure, e.g., “congestion”.

CCS SUB BUSY

Number of calls that, after being connected by the SN of the home MSC, are releaseddue to “subscriber busy”.

CCS INT TECHN IRREG

Number of calls that, after being connected by the SN of the home MSC, are releaseddue to technical irregularities and radio subsystem faults.

CCS EXT TECHN IRREG

Number of calls released after connection through the SN due to technical faults in thefollowing MSC.

CCS UNANSWERED

Indicates 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 ANSWER

Number of calls answered at the called station. This event is not counted until the endof the call.

170 A50016-D1112-G802-1-7618


CCU CONGESTION

Number of calls with untimely end before being trough connected by the SN of the homeMSC upon receiving line signal “congestion”, “subscriber busy” or CCNC overload in thehome MSC or due to overload in the subsequent MSC.

CCU NM CODE BLOCKING

Number of calls rejected in the home MSC before being connected through the SN dueto network management action. Such action reduces in stages or completely blocks traf-fic to specific destinations.

CCU NM TGRP BLOCKING

Number of calls rejected in the home MSC prior to connection through the SN becausethey were not authorized to access the outgoing trunk group (e.g., trunk reservation).

CCU TECHN IRREGULAR

Number of calls prematurely terminated in the home MSC prior to connection throughthe SN due to internal blocking in the SN, number unobtainable or internal or externalirregularities from the originating MSC.

CC LNP QUERY ATTEMPT

Number of calls with queries to an LNP server (local number portability server). Thecounter records the number of calls for which a query to an internal or external LNP serv-er was made. Queries according to the Query on Release procedure and according tothe Query on digit analysis procedure are counted. The counter is only incrementedonce, even if several queries are made to the server for one call. The counter is incre-mented for the original number (the dialed number).

CC LNP QUERY SUCCESS

Number of successful queries to an LNP server (local number portability server), i.e., anew routing number was received from the LNP server. Successful queries accordingto the Query on Release procedure and according to the Query on digit analysis proce-dure are counted. The counter is only incremented once, even if several queries aremade to the server for one call. The counter is incremented for the original number (thedialed number).

13.4 CP Traffic MeasurementFor the measurement of traffic in the CP of each network unit (MSC, VLR and HLR) datacan be recorded by counters concerning call processing load and total load. Therefore,holding time counters are implemented on which relies CP traffic measurement.

A measurement job is started by entering the REC CP command


Integration time and output are additional constants being inserted when the counterresults are retrieved via a traffic file at the OMC in order to allow the measured data tobe allocated.• Integration time

A 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

A50016-D1112-G802-1-7618 171


Counter Description

interval, an integration time is introduced. By specifying this time at command input,the results can be output each multiple (from 1 up to 255) of 4 seconds, instead ofjust at the end of the interval.

• OutputThe output at the end of the measurement interval Indicates whether the processor– has been active: specific load value– was not active: *– has not been created: blank.

CARRIED_TRAFFIC

Call processing load in miliErlang. For processors: BAPM, BAPS, CAP0, CAP1– CAP9.

TOTAL_INTENSITY

Total load in miliErlang. For processors: BAPM, BAPS, CAP0, CAP1– CAP9.

13.5 LTG Traffic MeasurementIn order to determine the busy period for the network node and the code receiver groups,a lot of data is recorded in counters concerning:– Calls offered to the exchange– Not accepted calls due to a lack of resources in the LTG– Traffic offered to the code receiver groups

Therefore, counters are implemented on which relies LTG traffic measurement: eventcounters, holding time and waiting time counters. All these counters are continuouslyupdated by the call-processing software in the line/trunk groups (LTGs) and their datais collected at measurement intervals of 15 minutes.

A traffic measurement job is started by entering the REC LTG command. It can be spec-ified whether or not code receiver measurement data have to be output. The LTG mea-surement is used only in the MSC as the LTG in the VLR and HLR just offer channelsfor CCS7 signaling and not for user traffic.

Because there is a large number of different counters, they have been grouped on thefollowing pages according to their distinctive purposes:– LTG Counters (see chapter 13.5.1)– Code Receiver Group Counters (see chapter 13.5.2)– Group Processor Counters (see chapter 13.5.3)


The LTG number is a number or a name by which each LTG is identified. This numberis inserted when the counter results are retrieved via a traffic file at the OMC in order toallow the measurement data to be allocated.

13.5.1 LTG CountersThe following data is recorded for each LTG:

CC LOST SC: TERM INC

Number of calls (incoming from the transit network) rejected because of a lack of speechchannels (B-side), i.e., there are no free speech channels available between SN andLTG or the free speech channels are reserved and the call does not have the necessaryauthorization.

172 A50016-D1112-G802-1-7618


CC LOST SC: TERM INT

Number of calls (from the own network node) rejected because of a lack of speech chan-nels (B-side), i.e., there are no free speech channels between SN and LTG or the freespeech channels are reserved and the call does not have the necessary authorization.

CC LOST SC: ORIG

Number of calls rejected because of a lack of speech channels (A-side), i.e., there areno free speech channels between LTG and SN or the free speech channels are re-served and the call does not have the necessary authorization.

CC ON SC: TERM

Number of successful speech channel occupations in terminating traffic.

CC ON SC: ORIG

Number of successful speech channel occupations in originating traffic.

MIN NUM FREE SC

The minimum number of free speech channels (including the speech channels reservedfor preferenced traffic) during the measurement interval.

NUM ALL SC OCCUPIED

The number of times that all speech channels are occupied during a measurement in-terval. This does not take into account the speech channels reserved for preferencedtraffic. The counter is incremented each time the last free speech channel is occupiedsuccessfully.

SUM ALL SC OCCU(SEC)

Occupation level of the speech channels between LTG and SN, total duration of the sta-tus “all speech channels occupied” during the measurement interval. The counter isstarted when the counter NUM ALL SC OCCUPIED is incremented. When a speechchannel becomes free, the counter is stopped.

SLC:OFF CALLS

Number of calls offered by subscriber line circuits SLC (lines).

SLC:ACC CALLS GP

Number of calls accepted by the LTG from subscriber line circuits for incoming subscrib-er traffic (originating traffic).

SLC:REJ CALLS OL

Number of calls from subscriber line circuits rejected by the GP. Possible reasons forrejection: LTG/CP CPU overload, SEIZURE A calling rate too high, lack of GP resourcessuch as lack of heap or threshold exceeded in task or available queue. Calls rejecteddue to lack of code receivers are not counted.

TR CIRC:OFF CALLS

Number of calls offered by incoming trunk circuits.

TR CIRC:ACC CALLS GP

Number of calls accepted by the LTG from trunk circuits for incoming traffic.

A50016-D1112-G802-1-7618 173


Counter Description

TR CIRC:REJ CALLS OL

Number of calls from trunk circuits rejected by the GP. Possible reasons for rejection:LTG/CP CPU overload, SEIZURE A calling rate too high, lack of GP resources, for ex-ample lack of heap or threshold exceeded in task queue or available queue. Calls re-jected due to lack of code receivers are not counted.

13.5.2 Code Receiver Group CountersThe following data is recorded for each code receiver group:

CRM/CRP:TC

Sum of holding times (traffic carried in mErl).

CRM/CRP:SUMMARY EFFECTS

Number of calls offered.

CRM/CRP:ACCEPTED CALLS

Number of calls accepted.

CRM/CRP:SUM DELAYS

Sum of delay times.

CRM/CRP:NUMBER OF DELAYS

Number of calls which had to wait for a code receiver.

CRM/CRP:DELTHR EXCEEDED

Number of calls which had to wait more than a defined time (default 3 seconds, selectionrange 1 to 20 seconds) for a code receiver.

CRM/CRP:NUMB OF CONNECT

Number of connected code receivers.

CRM/CRP:NUMB OF BLOCKED

Number of blocked code receivers (current value at the end of the integration period).

13.5.3 Group Processor CountersThe following data is recorded for each group processor (GPP):

GP_IDR

Indicates for each GP the number of routine tests that have run.

GP_MEANT

Indicates for each GP the average time (in microseconds) for the execution of the test.

13.6 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.

174 A50016-D1112-G802-1-7618


The measurement relying on these counters can be started by entering the REC GPcommand. For the provided counters see chapter 13.5.3.

A50016-D1112-G802-1-7618 175


Counter Description

13.7 DLU Traffic MeasurementFor traffic measurement in the LTG concerning the digital line unit (DLU), data to deter-mine the time at which the busy hour occurs for subscribers served by this DLU can berecorded by counters. With respect to mobile equipment, the DLU that incorporates theinterworking equipment (called data service unit) is involved in this measurement.

Therefore, counters are implemented on which relies traffic measurement of each DLU:event counters, holding time and blocking time counters.

The measurement job is started by entering the REC DLU command for each DIU.


The DLU and DIU number are additional constants being inserted when the counter re-sults are retrieved via a traffic file at the OMC in order to allow the measurement data tobe allocated.– An external DLU number .– The DIU number is composed of a TSG, a GP and a DIU number.

NUMBER OF DIUS

Number of DIUs of the measured DLU.

SIGNALLING CHANNELS

Number of the connected common signaling channels.

BEARER CHANNELS

Number of the connected bearer channels.

BLOCKED BEARER CHNS

Number of the blocked bearer channels.

SUM CH BLO TIME

Total blocking time of all channels per DIU (in seconds).

CC ON TS: TERM

Calls carried on time slots. Terminating.

CC ON TS: ORIG

Calls carried on time slots. Originating.

TC ON TS: TERM

Traffic carried on time slots. Terminating in mErl.

TC ON TS: ORIG

Traffic carried on time slots. Originating in mErl.

CC: SCI D-CHANNEL

Number of subscriber-controlled D-channels inputs per DIU.

CC LOST: TERM INC

Sum of the TERM_INC counters CC LOST DA, CC LOST TS and CC LOST SC.

176 A50016-D1112-G802-1-7618


CC LOST: TERM INT

Sum of the TERM_INT counters CC LOST DA, CC LOST TS and CC LOST SC.

CC LOST: ORIG

Sum of the ORIG counters CC LOST TS and CC LOST SC.

CC LOST DA: TERM INC

Number of lost calls due to "DLU not available."

CC LOST DA: TERM INT

Number of lost calls due to "DLU not available."

CC LOST TS: TERM INC

Number of lost calls due to lack of time slots.

CC LOST TS: TERM INT


CC LOST TS: ORIG


CC LOST SC: TERM INC

Number of lost calls due to lack of speech channels.

CC LOST SC: TERM INT


CC LOST SC: ORIG


MIN NUM FREE TS

Minimum number of free time slots.

NUM ALL TS OCCUPIED

Number of cases "all time slots occupied."

A50016-D1112-G802-1-7618 177


Counter Description

13.8 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.

The counters are updated either implicitly (i) or explicitly (e) as marked further on foreach counter.– (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.

The measurement job is started by entering the REC ANGRP command. The followingcounters are provided.


Index and TGNO are additional constants being inserted when the counter results areretrieved via a traffic file at the OMC in order to allow the measurement data to be allo-cated. 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)

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)

Number of semipermanently blocked lines. The counter Indicates a current value at theend of each quarter hour.

TC_SEMI_BLOLI (i)

Sum of blocking times of semipermanently blocked lines (traffic carried in dErl); broad-casting is left aside.

TRANS_BLOCKED_LINES (i)

Number of transiently blocked lines. The value is updated at the end of each quarterhour.

TC_TRANS_BLOLI (i)

Sum of blocking times (traffic carried) in dErl of the transiently blocked lines.

ANGRP_BLO_TIME (i)

Sum of the maintenance-related blocking times of the announcement group in seconds.

178 A50016-D1112-G802-1-7618


TC N

Sum of holding times (traffic carried in dErl) for calls accepted by the announcementgroup, i.e., for broadcast announcement group, this is the number of accepted 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)

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)

Total blocking time due to all trunks busy during which the announcement group wasblocked.

NUMBER OF ATB (i)

Number of occurrences on which ATB time was recorded for the announcement group.

CCU_ANGRP_BLOCKED (i)

Number of calls rejected due to (semipermanent or transient) blocking of the announce-ment 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

Number of calls released after seizure of the announcement group (entered in the list oflisteners) due to technical irregularities.

TOTAL_SEIZE_TIME_IFU

Indicates the total seizure time for announcement type IFU.

A50016-D1112-G802-1-7618 179


Counter Description

13.9 GSM MGW MeasurementThe GSM Media Gateway (GSM MGW) is a product based on the Remote SwitchingUnit (RSU). It is physically separated from the MSC. Local switching can be introduced,thus benefitting the operator with a separated architecture.

The GSM MGW requires the following hardware within the remote entity:– Remote Timeslot Interchange (RTI)– LTGs– DLUs

The GSM MGW needs a controlling entity to work. This task is performed by an MSCwith one additional hardware component, the Host Timeslot Interchange (HTI). The con-trolling MSC, which is called the GSM MSC Server has the same functionality as an or-dinary MSC.

GSM MGW measurements determine the processor load values and blocks for theGSM MGW and the associated MHs (message handlers) located in RTI/HTI. In addition,the measurements record the internal GSM MGW traffic. In this way the operator canobtain information on the usage and operation of the GSM MGW. The measured valuesalso serve to achieve optimal usage of the GSM MGW and are a basis for the dimen-sioning of extensions.

Fig. 13.1 RSU overview

GSM MGW

GSM MSC Server

SN

HTI

DLU LTG RTIsidedoor trunks

GSM MGW

RTI LTG DLUDLU

DLU LTG

CP

interfacetrunks

interfacetrunks

BSC BSC

A interfaceA interface

PSTN or anotherMSC

180 A50016-D1112-G802-1-7618



RSU and TYPE are additional constants being inserted when the counter results are re-trieved via a traffic file at the OMC in order to allow the measurement data to be allocat-ed.• RSU

Number of the RSU (max. 286 RSUs are possible of which 254 RTIs AND 32 HTIs)• RSU ID

Name of the RSU• TYPE

RSU type: HTI or RTI

The following measured values are recorded for all the GSM MGWs, which are connect-ed to the GSM MSC server during the measuring interval:

PROCESSOR LOAD (%) RSUC, MH0...MH6

Average load of the RSU controller and message handlers 0..6 in the measuring intervalin percent.

NUMBER OF CONGESTIONS RSUC, MH0...MH6

Number of congestion cases in the measuring interval. Congestion occurs if the numberof free message buffers in the processor drops below a defined value. The congestionsituation is cleared if the number of message buffers increases to twice the value de-fined for the congestion.

TIME IN CONGESTION (SEC) RSUC, MH0...MH6

Time a processor (RSUC, MH0...MH6) was in the congestion status during a measuringinterval. The output is in seconds.

CC: INTRA-RSU

Number of internal RSU calls. For an internal RSU call, the A and B port use the sameRSU.

TV INTRA RSU

Traffic volume of internal RSU connections in Erls.

A50016-D1112-G802-1-7618 181


Counter Description

182 A50016-D1112-G802-1-7618


14 CSC-specific MeasurementThe measurements described in this chapter are performed on a Combined SwitchingCenter (CSC) and apply only to wireline subscribers and PBXs.

The following CSC-specific measurements are described in this chapter:• PBX Traffic Measurement (see chapter 14.2)

14.1 General InformationInformation on the quality, availability and plausibility of the recorded data is containedin different CSC-specific measurements and explained for all of them in the followingchapters:• Data Quality and Availability (see chapter 14.1.1)• Plausibility Checking of Traffic Measurement Results (see chapter 14.1.2)

14.1.1 Data Quality and AvailabilityThe validity of the measured values is characterized by two factors: data quality andavailability. Data quality describes the validity of all the measurement data output perintegration period. Availability refers to the validity of the data per measurement object.

Tab. 14.1 shows which data quality/availability is relevant for individual measurements.

In the following lists, the figures before the slash denote the values in the output datarecord. The information behind the slash is shown if the data is output on the OMC.

Data quality 1

Availability 1

Traffic measurement Data quality Availability

REC PBX 1 1

Tab. 14.1 Data quality and availability of measurement data

blank default value1/ SECURE - data is secure2/ TIME CORR - time correction in the integration period3/ NO INIT - Traffic meters could not be initialized in the integration peri-

od (not applicable for REC DN)4/ INCOMPL SUM - Only for REC SAF:

Incomplete summation of data, e.g., if LTG recovery per-formedOnly for REC DN:Incomplete summation of data, i.e., due to a day-changeover the integration interval does not have the de-fined integration length

1/ blank - object data is available

A50016-D1112-G802-1-7618 183


Counter Description

14.1.2 Plausibility Checking of Traffic Measurement ResultsThe plausibility of the values obtained from a specific measurement or from severalmeasurements can only be checked through single calls or through the traffic from au-tomatic subscribers (outgoing originating traffic → incoming terminating traffic). It is im-portant to ensure that the calls begin and end inside a time interval (quarter hour) orinside a defined period (n quarter hours). In ongoing traffic, a complete plausibility checkis only possible over a 24-hour period, for example, in which the subscriber traffic mustbe zero at the beginning and end of observation. Moreover, it must be noted that the callprocessing events may occur in different quarter-hour periods, meaning that the eventcounters are updated in different intervals, e.g., start of seizure of the B side in the homeexchange (CCS:INT) and end of call (CCS_WITH_ANSWER:INT in the REC GOS mea-surement).

14.2 PBX Traffic MeasurementFor the measurement of traffic flows through private (automatic) branch exchangesP(A)BXs, the following data can be recorded by counters:• Service-related data (see chapter 14.2.1)

which are always output per integration interval.• Service-independent data (see chapter 14.2.2)

which are only output if the service has been used in the integration period

Therefore, event and holding time counters are implemented in the CP database onwhich relies PBX traffic measurement. The measurement job is started by entering theREC PBX command for 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.

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.


Service Number , Index , LAC , DN and Operating Mode are additional constants beinginserted when the counter results are recorded in the OMC in order to allow the mea-sured data to be allocated.• Service number

The incorporation of private ISDN exchanges into the MSC provides for a lot of ap-propriate services the data which can be counted. Such service-related data is iden-tified by an internal service number (1 to 32) in the CP. Data is output only if theproper service has been used during the measurement interval. General data of the

2/ DEL - the object was canceled during the measurement period3/ NONE - no data received, i.e., the data could not be read owing to re-

covery or CP overload in the recording period.4/ UNA - DIU is unavailable (only for DLU measurement)

184 A50016-D1112-G802-1-7618


PBX (of any type) is counted separately. Such service-independent data is indicatedby the service number 0 (zero). This data always is output after the measurementinterval (of 15-minutes).

• IndexIndex is only used at the tape interface for data control. Index 1 or 2 for service-re-lated data. Index 1 – 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.

• DNor the extension number of the calling party being served by the PBX.

• OPMODEThe following codes represent the operation mode that can be created for a PBXgroup:

14.2.1 Service-related CountersThe counters are provided per service as identified by the service number. The name ofeach service is country-specific and varies according to the signaling protocol (EDSS1,1TR6).

CC:I (O)

Indicates how many incoming or outgoing calls (calls carried) for the respective servicehave been accepted by the CP and how often the service has changed.

TC:I

Sum of holding times (traffic volume) for the respective service through incoming callstowards the CP that have been accepted by the latter.

TC:O

Sum of holding times (traffic volume) for the respective service through outgoing callstowards the called party over B channels that have been accepted by the CP.

CCS WITH ANSWER:I (O)

Indicates how often incoming or outgoing calls (calls carried) at the PBX trunk grouphave successfully been answered on the called station (terminal).

TC ANSWER:I (O)

Volume of incoming or outgoing traffic at the PBX trunk group that is answered on thecalled station (terminal).

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-D1112-G802-1-7618 185


Counter Description

14.2.2 Service-independent CountersService-related counters are also implemented and register the same kind of data (seechapter 14.2.2). In addition, the following counters are implemented. The output of thesecounters after measurement is identified by digit 0.

CCU:O

Number of unsuccessful attempts in the CP to seize the trunk group, i.e., lost calls forthe outgoing trunk group (from CP to called subscriber) per line and for bothway trunkgroup.

CCU PDN:O

Number of rejected or forwarded PDN calls (pilot directory number calls). The counteris incremented if the search for free lines was not successful for all the hunting groupsof a private branch exchange, i.e., if all the lines are busy (ATB).

ATB TIME

Total blocking time (due to all trunks busy) for OG or in bothway trunks for IC and OG.

NUMBER OF ATB

Number of occurrences of ATB; i.e., how often all available lines in the group were busy.

CONNECTED CHANNELS

Indicates 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 CHAN

Number of trunks blocked for O&M purposes. The counter indicates a current value atthe end of each quarter-hour.

TRANS BLOCKED CHAN

Number of trunks blocked transiently. The counter indicates a current value at the endof each quarter hour.

186 A50016-D1112-G802-1-7618


15 SS7-specific Traffic Measurement (SSNC)Signaling on common channels for inter network node communication takes place ac-cording to signaling system number 7 (SS7) protocols. On the MP platform signalingtraffic control in the different nodes is implemented by the signaling system network con-trol (SSNC), an SS7 platform based on the ATM technology with uniform data rate.

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 respect to the exchange of signaling informa-tion. SS7 is composed of different parts each characterized by their functions which areimplemented by means of protocols.

The following SS7 parts are used between the network nodes:• Message transfer (see chapter 15.1)• Signaling connection control (see chapter 15.2)• Transaction capabilities application (see chapter 15.3)

15.1 MTP MeasurementThe MTP measurements provide details on the quality and volume of the signaling per-formance. The counters, whose values are reported, are described further on in thischapter in the same order as they appear in the report notification.• Net Element Measurement (see chapter 15.1.1)• Signaling Point Measurement (see chapter 15.1.2)• Signaling Link Set Measurement (see chapter 15.1.3)• Destination Point Measurement (see chapter 15.1.4)• Signaling Link Measurement (see chapter 15.1.5)• Signaling Linkset IP Measurement(see chapter 15.1.6)• SCTP Association Utilization and Duration Measurement (see chapter 15.1.7)

15.1.1 Net Element MeasurementThe traffic measurement is entered with the CR SIGNEME task. For the measurementobject the incoming, outgoing, discarded and transit message signaling units (MSUs)are recorded at the network node level by means of the following counters.

numInMSU

Number of incoming MSUs per network node.

NumLostMSURoutErr

Number of discarded MSUs per network node because of routing errors.

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.

A50016-D1112-G802-1-7618 187


Counter Description

– 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.

numOutMSU

Number of outgoing MSUs per network.

numTransitMSU

Number of transit MSUs per network.

mSUsThroughSwitchedOctets

represents the sum of all switched through octets counted on a link basis over a com-plete switch.

mSUsOriginatedOctets

represents the sum of all originated octets counted on a link basis over a completeswitch.

mSUsTerminatedOctets

represents the sum of all terminated octets counted on a link basis over a completeswitch.

nodeIsolationForAnyReason

represents the sum of route set failures for each DPC of the complete network node.

nodeIsolationDuration

represents the sum of durations of route set failures for each DPC of the complete net-work node.

15.1.2 Signaling Point MeasurementSignaling point measurement are entered with the CR SIGPTME task by selecting oneor all of the following measurement types:• Signaling Point Utilization (section 15.1.2.1)• Obligatory Signaling Point Utilization (section 15.1.2.2)• Network MSU (section 15.1.2.3)• Signaling Point (section 15.1.2.4)

188 A50016-D1112-G802-1-7618


15.1.2.1 Signaling Point UtilizationFor 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.

adjacentInaccessibleDuration

Duration during which each adjacent signaling point in the complete network was inac-cessible (§ 5.2).

adjacentInaccessibleEvents

Indicates 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.4.

15.1.2.2 Obligatory Signaling Point UtilizationFor 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.

adjacentInaccessibleDuration

Duration during which each adjacent signaling point in the complete network was inac-cessible.

15.1.2.3 Network MSUFor this measurement object the incoming, outgoing and transit MSUs per network arerecorded by means of the following counters.

numInMSUperNet

Number of incoming MSUs per network.

numOutMSUperNet

Number of outgoing MSUs per network.

numTransitMSUperNet

Number of transit MSUs per network.

15.1.2.4 Signaling PointFor 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 counters.

discardedMSUs

Number of discarded MSUs per link because of blocking.

A50016-D1112-G802-1-7618 189


Counter Description

15.1.3 Signaling Link Set MeasurementSignaling link set measurement are entered with the CR SIGLSME command by select-ing one or all of the following measurement types:• Link Set Duration (see chapter 15.1.3.1)• Link Set Utilization (see chapter 15.1.3.2)

15.1.3.1 Link Set DurationFor 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.

numLinkSetNotAvail

Indicates how often a link set is unavailable during a measurement time period.

slsUnavailable

Indicates the time (in s) during a measurement time period the link set was unavailablebecause of local blocking, foreign blocking, local and foreign blocking or failure of theremote processor.

The counter is started when the last link of this link set assumes the “inactive” mode andis stopped when the link set is active again.

15.1.3.2 Link Set UtilizationFor this measurement object the utilization of link sets is recorded by means of the fol-lowing counters.

receivedMSUs

Number of received message signal units.

transmittedMSUs

Number of transmitted MSUs.

receivedOctets

Number of received octets.

transmittedOctets

Number of transmitted octets.

retransmittedOctets

Number of retransmitted octets.

lostMSUsBufferOverflow

Indicates the sum of measurements concerning local buffer overflow. In networks with3 congestion levels the value is always “0”.

lostMSUCongestionEventThreshold-1

Number of MSUs being rejected because of exceeding congestion threshold 1. In net-works with only one congestion level this value is always “0”.

190 A50016-D1112-G802-1-7618






15.1.4 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. Destination point measurement are en-tered with the CR SIGDPME command and are recorded by means of the followingcounters.

dpcIsAdjacent

marks the DPC of the route set as adjacent or non-adjacent (§ 5.1).

routeSetUnavailable

Number of route set failures per destination (§ 4.9).

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.

routeSetUnavailableDuration

Indicates per destination the time (in s) during a measurement time period a route setwas unavailable (§ 4.10).

The counter is started if layer 3 network control reports an unavailable route set and isstopped if it reports the route set to be available again.

15.1.5 Signaling Link MeasurementSignaling link measurement are entered with the CR SIGLME task by selecting one orall of the following measurement types:• Obligatory Link Duration (see chapter 15.1.5.1)• Link Duration (see chapter 15.1.5.2)• Obligatory Link Utilization (see chapter 15.1.5.3)• Link Utilization (see chapter 15.1.5.4)• Link Congestion (see chapter 15.1.5.5)• High-Speed Link Utilization Measurement (see chapter 15.1.5.6)• Obligatory High-Speed Link Utilization Measurement (see chapter 15.1.5.7)

15.1.5.1 Obligatory Link DurationFor 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.

A50016-D1112-G802-1-7618 191


Counter Description

slInServiceDuration

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 the link testran successfully).

slUnavailabilityDuration

Indicates 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 (§ 2.1).

The counter is started if the link assumes the “inactive” mode and is stopped if the linkis active again.

inhLinkDurUnavail

Indicates the time (in s) during a measurement time period that a local link remained un-available because its state was set to “inhibited”.

15.1.5.2 Link DurationFor 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.

slFailed

Indicates 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 MTPlevel 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.

sIInServiceDuration

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).

slRemoteProcOutage

Indicates 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.

sIUnavailabilityDuration

Indicates 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 linkis active again.

192 A50016-D1112-G802-1-7618


inhLinkDurUnavail

Indicates the time (in s) during a measurement time period that a local link remained un-available because its state was set to “inhibited”.

15.1.5.3 Obligatory Link UtilizationFor 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.

receivedOctetsSIFSIO

Number of received signaling information fields+octets (SIF + SIO) per link (§ 3.4).

signUnitsReceived

Number of incoming faulty MSUs per link (§ 1.8) caused by:– checksum error,– signaling information fields+octets (SIF + SIO) exceeding 272 bytes.

transmittedOctetsSIFSIO

Number of transmitted signaling information fields+octets (SIF + SIO) per link (§ 3.1).

discardedMSUs

Number of discarded MSUs because of overload (§ 3.10).

Message transfer on layer 2 handles the administrative signaling link overload thresholdvalue. Once the threshold value is reached, MSUs are discarded and the counter is in-cremented.

slLocalInhibited

Indicates 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.

slRemoteInhibited

Indicates 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.

slLocalBlocked

Indicates how often a local link was unavailable because its state was set to “blocked”.

slRemoteBlocked

Indicates how often a link was unavailable because the state of the opposite link in theadjacent network node was blocked.

15.1.5.4 Link UtilizationFor 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.

A50016-D1112-G802-1-7618 193


Counter Description

receivedMSUs

Number of received MSUs (§ 3.5).

receivedOctetsSIFSIO

Number of received signaling information fields+octets (SIF + SIO) (§ 3.4).

retransmittedOctets

Number of retransmitted octets (§ 3.2).

signUnitsReceived

Number of received faulty signaling units (§ 1.8).

transmittedMSUs

Number of transmitted MSUs (§ 3.3).

transmittedOctetsSIFSIO

Number of transmitted signaling information fields+octets (SIF + SIO); the repeated oc-tets are not counted (§ 3.2).

slLocalInhibited

Indicates 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.

slRemoteInhibited

Indicates 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.

slLocalBlocked

Indicates how often a local link was unavailable because its state was set to “blocked”.

slRemoteBlocked

Indicates how often a link was unavailable because the state of the opposite link in theadjacent network node was blocked.

15.1.5.5 Link CongestionFor 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.

slCongestedDuration

Indicates 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.

slCongestedStarts

Number of times a link is unavailable during a measurement time period. The measuredvalues are determined by layer 2 message management.

194 A50016-D1112-G802-1-7618


15.1.5.6 High-Speed Link Utilization MeasurementFor this measurement object the utilization data is recorded for high-speed links bymeans of the following counters.

discardedSD-PDUs

Number of discarded sequenced data protocol data units (PDUs) due to overload.

receivedSD-PDUs

Number of received sequenced data PDUs.

sduReceivedOctets

Number of received service data unit octets.

sduRetransmittedOctets

Indicates how many sequenced service data unit octets are retransmitted.

sduTransmittedOctets

Number of transmitted service data unit octets.

transmittedSD-PDUs

Number of transmitted sequenced data PDUs.

15.1.5.7 Obligatory High-Speed Link Utilization MeasurementFor this measurement object the obligatory data is recorded for high-speed links bymeans of the following counters.

discardedSD-PDUs

Number of discarded sequenced data PDUs due to overload.

sduReceivedOctets

Number of received service data unit octets.

sduTransmittedOctets

Number of transmitted service data unit octets.

15.1.6 Signaling Linkset IP MeasurementThis measurement records IP link set information data. The counters register the num-ber of unavailable cases per IP link set and the unavailable duration per IP link set.

For this measurement object the data is recorded with the CR SIGLSETIPME task bymeans of the following counters:

numIpLinkSetUnavailable

The counter records in M3UA (MTP3 user adaption layer) Management the cases, whenthe IP linkset is not available during a measurement time period.

A50016-D1112-G802-1-7618 195


Counter Description

ipLinkSetUnavailableDuration

This counter records the total time in seconds for an IP link set unavailable within a mea-surement time period. The counter is started when M3UA Management announces anIP linkset is unavailable. The counter is stopped when M3UA Management announcesIP link set is available. The counter is reincremented for each measurement time period.

15.1.7 SCTP Association Utilization and Duration MeasurementSCTP association utilisation and duration measurements are entered with the CR SCT-PASSOCME task by selecting one or all of the following measurement types:• Obligatory Association Utilization Data (see chapter 15.1.7.1)• All Association Utilization Data (see chapter 15.1.7.2)• All Association Duration Data (see chapter 15.1.7.3)

15.1.7.1 Obligatory Association Utilization DataThis measurement records the obligatory SCTP association utilization data.

For this measurement object the data is recorded by means of the following counters:

numM3UA-MsgSent

This counter records the number of M3UA (MTP3 user adaption layer) messages sentto the peers per association.

numM3UA-MsgReceived

This counter records the number of M3UA messages per association received from thepeers.

numSCTP-PacketsSent

This counter records the number of SCTP (Stream Control Transmission Protocol)packets per association sent to the peers.

numSCTP-PacketsReceived

This counter records the number of SCTP packets per association received from thepeers.

numOctetsSentPerAssoc

This counter records the number of transmitted octets per association (inclusive SCTPcontrol chunks and SACK chunks).

numM3UA-MsgDiscarded

This counter records the number of discarded M3UA messages per association due tocongestion.

15.1.7.2 All Association Utilization DataThis measurement records all SCTP association utilization data.

For this measurement object the obligatory association utilzation data listed in section15.1.7.1 plus the following counters are recorded.

196 A50016-D1112-G802-1-7618


numOctetsSentPerAssocNoCtrl

This counter records the number of transmitted octets per association without SCTPcontrol chunks.

numOctetsReceivedPerAssocNoCtrl

This counter records the number of received octets per association without SCTP con-trol chunks.

numOctetsRetransPerAssocNoCtrl

This counter records the number of retransmitted octets per association without SCTPcontrol chunks.

15.1.7.3 All Association Duration DataThis measurement records all SCTP association duration data.

For this measurement object the data is recorded by means of the following counters:

assocUnavailable

The counter records the duration of unavailability for an required association. The dura-tion counter is restarted for each measurement time period.

assocAvailable

The counter records the duration of availability for an required association. The durationcounter is restarted for each measurement time period.

sctpPathUnavailable

The counter records the duration of SCTP path unavailability within an association. Theduration counter is restarted for each measurement time period.

sctpAssocCongestion

The counter records the cumulative duration of congestion per association. The durationcounter is restarted for each measurement time period.

numCongestionLevel1

Number of the congestions events of an association, i.e. the counter is implementedwhen the threshold level 1 is crossed.

numCongestionLevel2


numCongestionLevel3


numPerAssocUnavailable

The number of unavailability events of an association.

A50016-D1112-G802-1-7618 197


Counter Description

15.2 SCCP MeasurementThe 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– “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 with

198 A50016-D1112-G802-1-7618


DT1. 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).

The SCCP measurement registers SCCP events being exchanged between networknodes during normal system operation. Therefore, a number of counters for collectinginformation about capacity utilization and network resources availability are implement-ed. SCCP performance can be examined on the basis of the data obtained as definedin ITU-T Recommendation Q.752.• SCCP Measurements with Specific Criteria (see chapter 15.2.1)• SCCP Screening (see chapter 15.2.2)

15.2.1 SCCP Measurements with Specific CriteriaSSCP measurements can be performed for a special network with the CR SPME task,network independently with the CR SPMEN task or for a special subsystem with the CRSPMESSN task. The appropriate selection criteria (NetID or SSN) have to be enteredwhile creating a measurement. For a specified subsystem only error performance mea-surements can be performed. For network-dependent and network-independent SSCPmeasurement tasks the same measurement types are available and one or all of the fol-lowing measurement types can be selected:

One or both of the following measurement types can be selected:• SCCP Error Performance Measurement• SCCP Utilization Measurement• SCCP Quality of Service Measurement

15.2.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-corded by means of the following counters.

In order to uniquely define the correct message, please refer to the appropriate eventmentioned in Table 7 of ITU-T Rec. Q.752.

segmentationNotSupported

Number of segmentation errors because segmentation is not supported (Event 19).

providerInitiatedRelease

Indicates 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.

tiarExpiry

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.

A50016-D1112-G802-1-7618 199


Counter Description

(Event 16 for external messages)

noReassemblyResources

Number of reassembly errors because of a lack of resources for reassembly (Event 12).

reassemblyTimerExpired

Indicates how often the timer for segmentation feedback expired in the case of externalXUDT and DT1 messages (Event 10).

reassemblyFailed

Indicates how often failed reassembly occured (Event 21).

unknownDestinationAddress

Indicates how often the destination address was unknown as defined in ITU-T Rec.Q.714, § 3.2.

providerInitiatedReset

Indicates how often a connection is reset by the provider (Event 17).

violationOfHopCounter

Number of hop counter violations by external XUDT and XUDTS messages (Event 13).

messageTooLarge

Indicates how often the message is too large for segmentation (Event 14).

subsystemCongestion

Number of routing errors because of an SCCP subsystem blocking (Event 6).

failReleaseComplete

Indicates 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).

noPointCodeAvailable

Number of routing errors because the SPC was unavailable after identification by theSPC status check (Event 3).

noTranslForSpecificAddress

Number of routing errors because no translation has taken place for this specific ad-dress (Event 2). The global title translation failed because there was no translation forthe specified global title digits.

networkCongestion

Number of routing errors because the SPC was overloaded after identification by theSPC status check (Event 4).

subsystemFailure

Number of routing errors because the subsystem was unavailable (Event 5). Therefore,the subsystem cannot send the external messages (CR, UDT, XUDT, UDTS orXUDTS).

200 A50016-D1112-G802-1-7618


userUnequipped

Number of routing errors because the subsystem was not provided in advance (Event7). Because the subsystem has not been created, the external messages (CR, UDT,XUDT, UDTS or XUDTS) cannot be sent.

sccpSyntaxErrorList

Indicates how often syntax errors are identified in incoming external messages (Event8).

unknownOrUnqualifiedRoutingFailure

Number of unknown routing errors (Event 9).

segmentReceivedOutOfSequence

Number of reassembly errors because the received segment was not in sequence (thisalso includes duplicates and receipt of other segments than first one for which no reas-sembly process is available) (Event 11).

noTranslForNatureAddress

Number of routing errors because unknown address types prevent address translation(Event 1).

segmentationFailed

Number of Segmentation error - Segmentation failed occurrences (Event 20).

15.2.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.

messagesHandled

Indicates 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.

messagesRequiringGTTranslation

Number of all messages requiring global title translation (Event 5). The number of mes-sages depends on whether or not the global title could be translated.

messagesForLocalSubsystems

Indicates the total number of all messages intended for local subsystems (Event 4).

numberOfTransitMessagesProcessed

Number of processed transit messages as defined in ITU-T Rec Q752.

dt2MessagesToSinkSSN

Number of sent DT2 messages for a specific subsystem resulting from a request of thatlocal subsystems.

A50016-D1112-G802-1-7618 201


Counter Description

messagesOriginatedPerSsnSpcCl0

Number of sent UDT/XUDT messages of class 0 for a specific subsystem resulting froma request of that local subsystems.

dt1MessagesToSinkSSN

Number of sent DT1 message for a specific subsystems resulting from a request of thatlocal subsystems.

messagesToBackupSsn

Number of messages sent to a back-up system of a subsystems service group.

messagesReceivedOrTerminatedPerSsnSpcCl1

Number of events for a local subsystems caused by an incoming external UDT/XUDTmessage of class 1 and generated by routing control.

messagesReceivedOrTerminatedPerSsnSpcCl0

Number of events for a local subsystems caused by an incoming external UDT/XUDTmessage of class 0 and generated by routing control.

messagesOriginatedPerSsnSpcCl1

Number of sent UDT/XUDT message of class 1 for a specific subsystems resulting froma request of that local subsystem.

dt1MessagesFromSourceSSN

Number of events for a local subsystems caused by an incoming external DT1 messageand generated by routing control.

edMessagesToSinkSSN

Number of sent ed messages resulting from a request of that local subsystems.

edMessagesFromSourceSSN

Number of events for a local subsystems caused by an incoming external ed messageand generated by routing control.

dt2MessagesFromSourceSSN

Number of events for a local subsystems caused by an incoming external DT2 messageand generated by routing control.

15.2.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.

errMessagesReceived

Number of PROTOCOL DATA UNIT ERROR messages being received from the MTP(Event 12).

xudtsMessagesSent

Number of outgoing external XUDTS messages being sent (Event 14).

202 A50016-D1112-G802-1-7618


udtsMessagesReceived

Number of UDTS messages being received (Event 4).

udtMessagesReceived

Number of UDT messages being received (Event 3).

crMessagesReceived

Number of CR messages being received from the MTP as well as ISDN-UP embeddedCR messages (Event 7).

crMessagesSent

Number of CR messages being sent to the MTP as well as ISDN-UP embedded CRmessages (Event 5); i.e., all outgoing external CR messages.

xudtMessagesReceived

Number of XUDT messages (including the messages with syntax/protocol and address-ing errors) being received (Event 15).

crefMessagesReceived

Number of CREF messages being received from the MTP (Event 8).

udtMessagesSent

Number of UDT messages being sent (Event 1).

xudtsMessagesReceived

Number of XUDTS messages (including the messages with syntax/protocol and ad-dressing errors) being received (Event 16).

errMessagesSent

Number of outgoing external PROTOCOL DATA UNIT ERROR messages being sent(Event 11).

crefMessagesSent

Number of CREF messages being sent (Event 6).

xudtMessagesSent

Number of outgoing external XUDT messages being sent (Event 13).

udtsMessagesSent

Number of UDTS messages being sent (Event 2).

ludtsMessagesReceived

Number of long UNITDATA SERVICE message received (Event 20).

ludtsMessageSent

Number of long UNITDATA SERVICE message sent (Event 18).

ludtMessageSent

Number of UNITDATA message sent (Event 17).

A50016-D1112-G802-1-7618 203


Counter Description

ludtMessagesReceived

Number of long UNITDATA message received (Event 19).

rsrMessagesSent

Number of reset request messages sent (Event 9).

rsrMessagesReceived

Number of reset request messages received (Event 10).

15.2.2 SCCP ScreeningSS7 screening ensures that only authorized signaling traffic is forwarded. Unauthorizedtraffic is rejected and can be registered.

SCCP screening measurements are entered with the CR SPSME task for the followingmeasurement types:• SCCP Screening Success Measurement (see chapter 15.2.2.1)• SCCP Screening Failure Measurement (see chapter 15.2.2.2)

15.2.2.1 SCCP Screening Success MeasurementThe SCCP screening traffic measurement monitors the traffic by means of the followingcounters.

nrOfGtTranslationsToOrigDomain

Indicates how many global title translations are performed that result in a destinationpoint code belonging to the original operator.

nrOfGtTranslations

Indicates how many messages of global title translations have been received from theinterconnecting operator.

nrOfSSTMessagesReceived

Number of subsystem status test messages (SCMG messages) which are received bythe SSNC These messages are only counted if screening of subsystem status testmessages should be done (discarded and passed).

nrOfSSPMessagesReceived

Number of subsystem tatus prohibited messages (SCMG messages) which are re-ceived by the SSNC These messages are only counted if screening of SSP messagesshould be done (discarded and passed).

nrOfSSAMessagesReceived

Number of subsystem allowed messages (SCMG messages) which are received fromthe interconnecting operator.

nrOfSSCMessagesReceived

Number of SSC messages (SCCP management messages) which are received to theinterconnecting operator.

204 A50016-D1112-G802-1-7618


15.2.2.2 SCCP Screening Failure MeasurementThe SCCP screening feature ensures that unauthorized traffic is rejected and attemptscan be registered.

disallowedCgpaTranslator

Indicates that the translator info of the calling party address (CGPA) is not allowed formessages received from the interconnecting operator.

disallowedCdpa

Indicates that the called party address (CDPA) is not allowed for messages receivedfrom the interconnecting operator.

disallowedCdpaTranslator

Indicates that the translator info of the called party address is not allowed for messagesreceived from the interconnecting operator.

disallowedCgpa

Indicates that the calling party address is not allowed for messages received from theinterconnecting operator.

failedGtTransNoAddressOfSuchNature

Indicates how many global title translations cannot be performed due to lack of a trans-lation table for this translator.

disallowedCdpaAfterTranslation

Indicates that the called party address after global title translation is not allowed for mes-sages received from the interconnecting operator.

disallowedMsgType

Indicates that the message type is not allowed for messages received from the intercon-necting operator.

failedGtTransNoRuleForSpecAddress

Indicates how many global title translations cannot be performed because no rule canbe selected matching the global digits.

disallowedScreeningDomain

Indicates that the level 3 MTP sap address is not allowed for messages received fromthe interconnecting operator.

disallowedSSTmessages

Invalid Point code/Subsystem number in subsystem status test messages (SCMG mes-sages) which are received from the interconnecting operator

disallowedSSCmessages

Invalid Point code/Subsystem number in Ssc messages (SCMG messages) which arereceived from the interconnecting operator.

A50016-D1112-G802-1-7618 205


Counter Description

disallowedCdpaDig

Global Digits of Called Party Address not allowed for messages received from the inter-connecting operator.

disallowedSSAMessages

Invalid Point code in subsystem-allowed messages (SCMG messages) which are re-ceived from the interconnecting operator.

disallowedSSPMessages

Invalid Point code in subsystem-prohibited messages (SCMG messages) which are re-ceived from the interconnecting operator.

disallowedCgpaDig

Global Digits of Called Party Address not allowed for messages received from the inter-connecting operator.

disallowedOperationContext

Application context or operation code not allowed for the messages received form theinterconnecting operator

15.2.3 Signaling Link Set IP Measurement

15.3 TCAP MeasurementTCAP traffic measurement is performed in accordance with Recommendation Q.752 ofthe ITU-T White Book. This involves the registration of TCAP events using softwarecounters in the entities of a node. These events are the SS7-based signaling or infor-mation messages exchanged between nodes of a mobile network or the service controlpoints of the intelligent network during normal system operation.

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.– B can answer by “Continue” thereby transferring its transaction identity as well.

206 A50016-D1112-G802-1-7618


– 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”.

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 SENT)

Number of “Begin” messages sent (Event 1).

TCUMSGSC (CONTINUE MESSAGE SENT

Number of “Continue” messages sent (Event 1).

TCUMSGSE (END MESSAGE SENT)

Number of “End” messages sent (Event 1).

TCUMSGSA (ABORT MESSAGE SENT)

Number of “Abort” messages sent (Event 1).

TCUMSGSU (UNIDIRECTIONAL MESS. SENT)

Number of “Unidirectional” messages sent (Event 1).

TCUMSGRB (BEGIN MESSAGE RECEIVED)

Number of “Begin” messages received (Event 2).

TCUMSGRC (CONTINUE MESS. RECEIVED)

Number of “Continue” messages received (Event 2).

TCUMSGRE (END MESSAGE RECEIVED)

Number of “End” messages received (Event 2).

TCUMSGRA ABORT MESSAGE RECEIVED

Number of “Abort” messages received (Event 2).

TCUMSGRU (UNIDIRECTIONAL MESS. RECEIVED)

Number of “Unidirectional” messages received (Event 2).

TCUCMPSN (COMPONENTS SENT)

Number of components sent over the node (Event 3).

TCUCMPRN (COMPONENTS RECEIVED)

Number of components received over the node (Event 4).

A50016-D1112-G802-1-7618 207


Counter Description

208 A50016-D1112-G802-1-7618


16 MP Load MeasurementsIn 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.

Traffic MP load measurement are entered with task CR MPLDME. One or both of thefollowing measurement types can be selected:• VCPU Measurement (see chapter 16.1)• Message Handler Measurement (see chapter 16.2)

16.1 VCPU MeasurementFor the VCPU measurement object the main and average loads of the different VCPUsare recorded by means of the following counters:

vcpu00mpTotalAverageLoad

Indicates the mean load (in mErl) of all VCPUs of a given MP.

vcpu00mpTotalMaximumLoad

Indicates the maximum load (in mErl) of all VCPUs of a given MP.

vcpu01SystemIntegrityAverageLoad

Indicates the mean load (in mErl) of the VCPU being provided with an unlimited runtimebudget for system integrity.

vcpu01SystemIntegrityMaximumLoad

Indicates the maximum load (in mErl) of the VCPU being provided with an unlimited runt-ime budget for system integrity.

vcpu02sltPrhAverageLoad

Indicates the mean load (in mErl) of a VCPU protocol handler.

vcpu02sltPrhMaximumLoad

Indicates the maximum load (in mErl) of a VCPU protocol handler.

vcpu03oamAverageLoad

Indicates the maximum load (in mErl) of a VCPU being provided with operation, admin-istration and maintenance functionality.

vcpu03oamMaximumLoad

Indicates the maximum load (in mErl) of a VCPU being provided with operation, admin-istration and maintenance functionality.

vcpu04callpAverageLoad

This counter value is not relevant.

A50016-D1112-G802-1-7618 209


Counter Description

vcpu04callpMaximumLoad


vcpu05SystemUpgradeAverageLoad

Indicates the mean load (in mErl) of a VCPU being provided with system upgrade.

vcpu05SystemUpgradeMaximumLoad

Indicates the maximum load (in mErl) of a VCPU being provided with system upgrade.

vcpu06ccs7NmAverageLoad

Indicates the mean load (in mErl) of a VCPU being provided with SS7-related function-ality.

vcpu06ccs7NmMaximumLoad

Indicates the maximum load (in mErl) of a VCPU being provided with SS7-related func-tionality.

vcpu07Spare07AverageLoad

The value of this spare counter is not relevant.

vcpu07Spare07MaximumLoad


vcpu08Spare08AverageLoad


vcpu08Spare08MaximumLoad


vcpu14backgroundAverageLoad

Indicates the mean load (in mErl) of a VCPU due to background processes.

vcpu14backgroundMaximumLoad

Indicates the maximum load (in mErl) of a VCPU due to background processes.

vcpu15auditAverageLoad

Indicates the mean load (in mErl) of a VCPU due to audit processes.

vcpu15auditMaximumLoad

Indicates the maximum load (in mErl) of a VCPU due to audit processes.

vcpu16idleAverageLoad

Indicates the mean load (in mErl) of a VCPU due to idle processes.

vcpu16idleMaximumLoad

Indicates the maximum load (in mErl) of a VCPU due to idle processes.

vcpu17SystemBaseLoadAverageLoad

This is the mean base load (in mErl) as a result of the calculation:

210 A50016-D1112-G802-1-7618


total load (=1000 mErl) – sum of the average loads of all measured VCPUs.

vcpu17SystemBaseLoadMaximumLoad

This is the maximum base load (in mErl) as a result of the calculation:

total load (=1000 mErl) – sum of the loads of all measured VCPUs.

16.2 Message Handler MeasurementFor this measurement object the main and average loads of message handlers are re-corded by means of the following counters.

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


















prhMgrBaseLoadAverageLoad

Indicates the mean load (in mErl) of the protocol handler managers.

A50016-D1112-G802-1-7618 211


Counter Description

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


uniMgrMaximumLoad


212 A50016-D1112-G802-1-7618


17 Traffic Measurement Related to Iu InterfaceThis chapter describes the traffic measurements in the circuit-switched domain that areperformed on the TSC (TRAU Server Card), the AAL2 server card (A2SC) and the Iuinterface. The TSC performs the voice transcoding on the circuit-switched path in direc-tion to the Iu interface together with the A2SC. The Iu interface connects the NE withany (vendor-independent) RNC. The traffic measurements on the TSC and Iu interfacedeliver information about the operating performance of the system, such as the systemload, the number of successful and unsuccessful calls, and the grade of service. Themeasurement results can be used for internal evaluation of the system, enhanced net-work configuration, and for statistical purposes.

The SS7 measurements and monitoring functions are implemented in accordance withthe ITU-T Rec. Q822.

The following measurements can be performed in the Iu interface connecting the 2G/3GMSC with the RNC:• CIC group measurements (see chapter 17.1)• AAL2 measurements (see chapter 17.2)• RANAP measurements (see chapter 17.3)• ATM measurements (see chapter 17.4)

17.1 CIC Group MeasurementsCircuit Identification Code (CIC) group measurements are performed on the TSC. TheTSC is responsible for the transcoding and the rate adaptation of the circuit-switchedvoice data and the PCM/ATM conversion. A CIC group consists of several channels,which are used on the ATM side of the TSC.

CIC group measurement are entered with the CR CICGRPME command by selectingone or all of the following measurement types:• AAL2 overrun measurements (see chapter 17.1.1)• AMR underrun error measurements (see chapter 17.1.2)• SSCS error measurements (see chapter 17.1.3)• Data underrun error measurements (see chapter 17.1.4)• Iu user plane protocol error measurements (see chapter 17.1.5)• Rate control measurements (see chapter 17.1.6)• AMR mode measurements (see chapter 17.1.7)

17.1.1 AAL2 Overrun Measurement

aal2-overrun-counter

Indicates that the connection sent more AAL2 packets than are permitted.

Trigger: The counter is incremented each time the number of received packets exceedsa threshold.

A50016-D1112-G802-1-7618 213


Counter Description

17.1.2 AMR Underrun Error Measurement

aal2-underrun-counter

Indicates errors occurring when a Digital Signal Processor (DSP) does not receive a suf-ficient number of AAL2 packets for a Vocoder Identifier (VID) from the AAL2 TerminationElement (ATE). In this case, speech muting is applied.

Trigger: The counter is incremented each time an expected packet is not received fromRNC.

17.1.3 SSCS Error Measurement

sscs-error-counter

Indicates SSCS (Service Specific Convergence Sublayer) protocol errors, like “lengthexceeded”, for each VID on each DSP of the TSC.

Trigger: The counter is incremented each time the received packet exceeds the maxi-mum allowed length.

17.1.4 Data Underrun Error Measurement

mcsd-data-underrun-counter

Indicates that no data is available for the DSP to fill an A-TRAU' frame.

Trigger: The counter is incremented each time an expected packet is not received.

17.1.5 Iu User Plane Protocol MeasurementIu User Plane protocol error measurements are provided for each VID. Counters aresplit into the groups Semantical_Protocol_Errors, Syntactical_Protocol_Errors andOther_Errors. In order to uniquely define the error type, please refer to 3GPP 25.415 ta-ble 4.

Other_Errors_Counter_Remote

This counter represents the sum of the User Plane error type “Other Error” signaled bythe remote termination.

Trigger: The counter is incremented each time an error event frame is received with rea-son “other” from RNC.

Sema_IuUP_Errors_Counter_Local

This counter represents the sum of the User Plane error type “Semantical” detected bythe local termination.

Trigger: The counter is incremented each time a semantical error is detected on a re-ceived PDU from RNC.

Sema_IuUP_Errors_Counter_Remote

This counter represents the sum of the User Plane error type “Semantical” signaled bythe remote termination.

Trigger: The counter is incremented each time an error event frame is received with rea-son “Semantically error” from RNC.

214 A50016-D1112-G802-1-7618


Synt_IuUP_Errors_Counter_Local

This counter represents the sum of the User Plane error type “Syntactical” detected bythe local termination.

Trigger: The counter is incremented each time a syntactical error is detected on a re-ceived PDU from RNC.

Synt_IuUP_Errors_Counter_Remote

This counter represents the sum of the User Plane error type “Syntactical” signaled bythe remote termination.

Trigger: The counter is incremented each time an error event frame is received with rea-son “syntactical error” from RNC.

17.1.6 Rate Control Measurement

rate-control-frame-counter

Number of received rate control frames per VDI.

17.1.7 AMR Mode Measurement

amr-mode475

Number of received and sent rate control frames for the 12.2 kbit/s amr mode.

amr-mode515


amr-mode590


amr-mode670


amr-mode740


amr-mode795


amr-mode102


amr-mode122-counter


17.2 AAL2 MeasurementThe AAL2 protocol level is the part of the Iu interface which performs traffic control forthe AAL2 messages which are exchanged between the adjacent node (e.g.: RNC) andthe UMSC.

A50016-D1112-G802-1-7618 215


Counter Description

AAL2 NNI and protocol access measurements are entered with the CR AAL2NNIAMEcommand by selecting one or all of the following measurement types:• AAL2 NNI Access Control Measurement (see chapter 17.2.1)• AAL2 NNI Access Protocol Measurement (see chapter 17.2.2)• AAL2 Carrier Access Control Measurement (see chapter 17.2.3)

AAL2 CPS protocol error measurements are entered with the CR AAL2VCCME com-mand by selecting the following measurement type:• CPS Protocol Error Measurement (see chapter 17.2.4)• PDU14 Protocol Error Measurement (see chapter 17.2.5)

AAL2 destination measurements are entered with the CR DAAL2SEPME command.

17.2.1 AAL2 NNI Access Control MeasurementThe AAL2 network to network interface (AAL2 NNI) access bundles a group of VirtualChannel Connections (VCC) that extend between two signaling points (AAL2 serviceendpoints) and is controlled by the same signaling protocol. AAL2 NNI access measure-ments perform signaling traffic control for external AAL2 messages.

accBLOCK-Incoming

Number of BLOCK messages received from adjacent node.

accBLOCK-Outgoing

Number of BLOCK messages sent to adjacent node.

accCONFUSION-Incoming

Number of CONFUSION messages received from adjacent node.

accCONFUSION-Outgoing

Number of CONFUSION messages sent to adjacent node.

accERQ-Attempt

Number of ERQ messages received from and sent to adjacent node.

accERQ-Failed-Attempt-Overload-Error

Number of failed ERQ messages received from and sent to adjacent node due to over-load type error.

accERQ-Failed-Attempt-Protocol-Error

Number of failed ERQ messages received from and sent to adjacent node due to pro-tocol type error.

accERQ-Failed-Attempt-Resource-Error

Number of failed ERQ messages received from and sent to adjacent node due to re-source type error.

accERQ-Failed-Attempt-Unspecified-Error

Number of failed ERQ messages received from and sent to adjacent node due to un-known type error.

216 A50016-D1112-G802-1-7618


accMOD-Attempt

Number of MOD messagesreceived from and sent to adjacent node.

accMOD-Failed-Attempt-Overload-Error

Number of MOD messages rreceived from and sent to adjacent node due to overloadtype error.

accMOD-Failed-Attempt-Protocol-Error

Number of MOD messages received from and sent to adjacent node due to protocoltype error.

accMOD-Failed-Attempt-Resource-Error

Number of MOD messages received from and sent to adjacent node due to resourcetype error.

accMOD-Failed-Attempt-Unknown-Error

Number of MOD messages received from and sent to adjacent node due to unknowntype error.

accREL-Attempt

Number of REL messages received from and sent to adjacent node.

accREL-Failed-Attempt

Number of failed REL messages (so end result is that connection is not released) re-ceived/sent from/to adjacent node due to protocol type error.

accRESET-Access-Incoming

Number of RESET messages received from adjacent node that resets for access.

accRESET-Access-Outgoing

Number of RESET messages sent to adjacent node that resets for access.

accRESET-CID-Incoming

Number of RESET messages received from adjacent node that resets for one ChannelIdentifier (CID).

accRESET-CID-Outgoing

Number of RESET messages sent to adjacent node that resets for one CID.

accRESET-Path-Incoming

Number of RESET messages received from from adjacent node that resets for one path.

accRESET-Path-Outgoing

Number of RESET messages sent to adjacent node that resets for one path.

accUNBLOCK-Incoming

Number of UNBLOCK messages received from adjacent node.

A50016-D1112-G802-1-7618 217


Counter Description

accUNBLOCK-Outgoing

Number of UNBLOCK messages sent to adjacent node.

accUNKNOWN-MESSAGE

Number of UNKNOWN messages.

17.2.2 AAL2 NNI Access Protocol Measurement

protBLC-Missing

Number of times the incoming BLC message is missing after timer expiry for sent outBLO message.

protBLC-with-cause-value

Number of incoming BLC messages containing the parameter CAUSE received fromadjacent node.

protBLO-Missing-Mand-Parameter

Number of incoming BLO messages without one of the parameters CEID or OSAID re-ceived from adjacent node.

protCNF-Missing-Mand-Parameter

Number of incoming CNF messages without parameter CAUSE received from adjacentnode.

protECF-Missing-Mand-Parameter

Number of incoming ECF messages without parameter OSAID received from adjacentnode.

protERQ-Missing-Mand-Parameter

Number of incoming ERQ messages without one of the parameters CEID, OSAID,NSEA, LC or SUGR received from adjacent node.

protERQ-On-Not-Avail-Path-Access

Number of incoming ERQ messages received on a locally blocked AAL2 path or AAL2path not available or AAL2 NNI Access not available.

protInvalid-CEID-CALLP

Number of incoming ERQ messages with invalid parameter CEID received from adja-cent node.

protInvalid-CEID-MAINT

Number of incoming RES, BLO or UBL messages with invalid parameter CEID receivedfrom adjacent node.

protInvalid-OSAID-CALLP

Number of incoming ERQ messages with invalid parameter OSAID (OSAID = 0) re-ceived from adjacent node.

218 A50016-D1112-G802-1-7618


protInvalid-OSAID-MAINT

Number of incoming RES, BLO or UBL messages with invalid parameter OSAID(OSAID = 0) received from adjacent node.

protMOD-Missing-Mand-Parameter

Number of incoming MOD messages without parameter LC received from adjacentnode.

protMOR-Missing-Mand-Parameter

Number of incoming MOR messages without parameter CAUSE received from adjacentnode.

protOSAID-Allocation-Failed

Number of times the OSAID allocation for outgoing ERQ messages failed.

protREL-Missing-Mand-Parameter

Number of incoming REL messages without parameter CAUSE received from adjacentnode.

protRES-Missing-Mand-Parameter

Number of incoming RES messages without one of the parameters CEID or OSAID re-ceived from adjacent node.

protRLC-with-cause-value

Number of incoming RLC messages containing the parameter CAUSE received fromadjacent node.

protRSC-with-cause-value

Number of incoming RSC messages containing the parameter CAUSE received fromadjacent node.

protUBC-Missing

Number of times the incoming UBC message is missing after timer expiry for sent outUBL message.

protUBC-with-cause-value

Number of incoming UBC messages containing the parameter CAUSE received fromadjacent node.

protUBL-Missing-Mand-Parameter

Number of incoming UBL messages without one of the parameters CEID or OSAID re-ceived from adjacent node.

protUnexpected-Message

Number of unexpected messages or ECF, REL, RLC, CFN, MOD, MOA, MOR, RSC,BLC, UBC with invalid DSAID.

protUnrecognized-Parameter

Number of incoming ERQ, REL, MOD, RES, BLO or UBL messages with wrong param-eter or message length.

A50016-D1112-G802-1-7618 219


Counter Description

17.2.3 AAL2 Carrier Access Control Measurement

cacBearerMod-incoming-Lack-BW

Counts how often CACrejected an incoming bearer modification due to lack of band-width.

cacBearerMod-outgoing-Lack-BW

Counts how often CAC could not send an outgoing bearer modification due to lack ofbandwidth on the outgoing AAL2 path.

cacERQ-incoming-Lack-BW

Counts how often CAC rejected an incoming ERQ due to lack of bandwidth.

cacERQ-outgoing-Lack-BW

Counts how often an outgoing ERQ could not be sent due to lack of bandwidth on theoutgoing AAL2 path.

cacERQ-outgoing-Lack-CID

Counts how often an outgoing ERQ could not be sent for this AAL2 access because oflack of CID.

17.2.4 CPS Protocol Error MeasurementCommon part sublayer (CPS) measurements are performed on the AAL2 Server Card(A2SC). Protocol errors on one of the up to 256 AAL2 path can be detected per singlepath. AAL2 CPS errors resulting from an incorrect ATM header are not counted as CPSprotocol error.

AAL2 measurements are entered with the CR AAL2VCCME command by means of thefollowing counters.

cpsParityError0

Number of transmission errors detected via the parity of the Start Field (STF); the com-plete CPS-PDU was discarded.

cpsSTFSeqError1

Number of wrong sequence number in the STF; if the Offset Field (OSF) is less than 47,processing starts at the octet pointed to by the OSF, otherwise the complete CPS-Pro-tocol Data Unit (CPS-PDU) is discarded.

cpsOctetsError2

Number of error due to a number of octets expected for a CPS-Packet overlapping intothis CPS-PDU, which does not match the information contained in the STF; if the valueof the OSF is less than 47, processing starts at the octet pointed to by the OSF.

cpsValueOSFError3

Number of error due to OSF of the STF containing a value 48 or greater; the completeCPS-PDU is discarded.

220 A50016-D1112-G802-1-7618


cpsXmitError4

Number of transmission errors detected in CPS-Packet header via the Header ErrorControl (HEC) Code; the unprocessed information in the CPS-PDU is discarded.

cpsSDULenghtError5

Number of errors due to a length of the received CPS-Packet Payload (CPS-SDU) ex-ceeding the maximum length indicated in 'Max_SDU_Deliver_Length'.

cpsCPSPacketError6

Number of errors due to partial CPS-Packet received previously and discarded due toerrors detected before the completion of the reassembly of the CPS-Packet.

cpsHeaderXmitError7

Number of transmission errors in the CPS-Packet header, detected by Header ErrorControl (HEC) Code of a CPS-Packet header overlapping a CPS-PDU boundary; if thevalue of the OSF is less than 47, processing starts at the octet pointed to by the OSF.

cpsUUIError8

Number of error due to User to User Indication (UUI) field in the received CPS-Packetheader containing a value ('28' or '29') that is reserved for future standardization.

17.2.5 PDU14 Protocol Error Measurement

synt-IuUP-Errors-Counter-Local

Counts error causes leading to discarded frames on the Iu User Plane protocol forPDU14 , according to table 4 of 3GPP-25.415: Syntactical errors in uplink direction: er-ror range 0-15.

sema-IuUP-Errors-Counter-Local

Counts error causes leading to discarded frames on the Iu User Plane protocol forPDU14 , according to table 4 of 3GPP-25.415: Semantical errors in uplink direction : er-ror range 0-15.

synt-IuUP-Errors-Counter-Remote

Counts error causes leading to discarded frames on the Iu User Plane protocol forPDU14 , according to table 4 of 3GPP-25.415: Syntatical errors in downlink path : errorrange 16-41.

sema-IuUP-Errors-Counter-Remote

Counts error causes leading to discarded frames on the Iu User Plane protocol forPDU14 , according to table 4 of 3GPP-25.415: Semantical errors in downlink path : errorrange 16-41.

other-Errors-Counter-Remote

Counts error causes leading to discarded frames on the Iu User Plane protocol forPDU14 , according totable 4 of 3GPP-25.415: Other protocol errors in downlink path :error range 42-63.

A50016-D1112-G802-1-7618 221


Counter Description

17.2.6 AAL2 Destination Measurement

cacDest -Lack-BW

counts how often a destination could not be reached because lack of available band-width in any of the possible accesses to this destination.

cacDest -Lack-CID

counts how often a destination could not be reached because of Lack of CID

17.3 RANAP Destination MeasurementThe Radio Access Network Application Part (RANAP) destination defines the types ofsignaling that are supported on the radio network controller. RANAP destination mea-surements are performed on the MP:RANAP for a specific RANAP destination, a spe-cific signaling point or for all RANAP destinations. The measurements can be performedfor two object groups:

RANAP measurements are entered with the CR RANAPDME command by selectingone or both of the following measurement types:• RANAP protocol measurements (see chapter 17.3.1)• CAM measurements (see chapter 17.3.2)

17.3.1 RANAP Protocol MeasurementThe RANAP protocol measurements count error messages occurring during the setupof an SCCP connection for RANAP, and lead to a refusal of this connection. The errorsare detected before the messages are forwarded to the circuit-switched or packet-switched specific part of the system with the counters indicated in the following.

RANAP counters with the “PS” suffix are not incremented in a circuit-switched systembut output with value “0”.

ranapBlocked-RNC-CS

Number of errors occurring because of a blocked RNC in the CS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but the RNC ismarked as BLOCKED in the CS domain.

ranapBlocked-RNC-PO

Number of errors occurring because of a blocked RNC in the PS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but the RNC ismarked as BLOCKED in the PS domain.

ranapLack-Of-Resources-CS

Number of errors occurring because of lack of resources in the CS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but there is noresource available on the MP:RANAP in the CS domain.

ranapLack-Of-Resources-PO

Number of errors occurring because of lack of resources in the PS domain.

222 A50016-D1112-G802-1-7618


Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but there is noresource available on the MP:RANAP in the PS domain.

ranapOverload-CS

Number of errors occurring because of overload in the CS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but theMP:RANAP is overloaded in the CS domain.

ranapOverload-PO

Number of errors occurring because of overload in the PS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but theMP:RANAP is overloaded in the PS domain.

ranapProtocol-Error-CS

Number of errors occurring because of a protocol error in the CS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but the initialmessage contains a protocol error in the CS domain.

ranapProtocol-Error-PO

Number of errors occurring because of a protocol error in the PS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but the initialmessage contains a protocol error in the PS domain.

ranapProtocol-Error-Unknown

Number of protocol errors in an unknown domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but the initialmessage contains a protocol error so that the domain cannot be determined.

ranapTechnical-Fault-CS

Number of errors occurring because of a technical fault in the CS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but a technicalfault occurs in the CS domain.

ranapTechnical-Fault-PO

Number of errors occurring because of a technical fault in the PS domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but a technicalfault occurs in the PS domain.

ranapTechnical-Fault-Unknown

Number of technical faults in an unknown domain.

Trigger: Each time the RNC tries to set up a RANAP SCCP connection, but a technicalfault occurs before the domain can be determined.

17.3.2 CAM MeasurementsThe call processing maintenance (CAM) on the MP is responsible to register possiblefailures of external and internal entities and, if possible, to repair them or to neutralizethe effects. CAM measurements count the maintenance messages on the RANAP pro-

A50016-D1112-G802-1-7618 223


Counter Description

tocol. The RANAP counters with the “CS” suffix are not incremented in a pure packet-switched system.

camOVERLOAD-from-RNC

Number of overload messages received from the RNC.

Trigger: Each time an overload situation in an RNC occurs.

camOVERLOAD-to-RNC

Number of overload messages sent to the RNC.

Trigger: Each time an overload situation in the core network occurs.

camRESET-from-RNC-CS

Number of RESET messages from the CS-domain in an RNC.

Trigger: Each time a RANAP RESET message for the CS-domain is received.

camRESET-from-RNC-PO

Number of RESET messages from the PS-domain in an RNC.

Trigger: Each time a RANAP RESET message for the PS-domain is received.

camRESET-RESOURCE-from-RNC-CS

Number of RESET RESOURCE messages from the CS-domain in an RNC.

Trigger: Each time an RNC requests the release of resources and references to Iu sig-naling connection identifiers of the CS-domain.

camRESET-RESOURCE-from-RNC-PO

Number of RESET RESOURCE messages from the PS-domain in an RNC.

Trigger: Each time an RNC requests the release of resources and references to Iu sig-naling connection identifiers of the PS-domain.

camSSP-from-SCMG-CS

Number of times the signaling link for the CS-domain is lost.

Trigger: Each time a SUBSYSTEM PROHIBITED is received from the SCCP managerfor the CS-domain.

camSSP-from-SCMG-PO

Number of times the signaling link for the PS domain is lost.

Trigger: Each time a SUBSYSTEM PROHIBITED is received from the SCCP managerfor the PS-domain.

17.4 ATM MeasurementsATM measurements are performed on the ATM-LIC. They provide data concerning theATM traffic load, protocol errors and the virtual paths and channels.

ATM traffic load measurements are performed on port level with the task CR TCSUB-LME, on virtual path (VP) level with the task CR VPATHME and on virtual channel (VC)level with the task CR VCHANME.

224 A50016-D1112-G802-1-7618


The same counter groups are provided for the following measurement types:• ATM traffic load measurement (see chapter 17.4.1)• Cell level protocol measurement (see chapter 17.4.2)• Virtual path and virtual channel performance measurement (see chapter 17.4.3)

17.4.1 ATM Traffic Load Measurements

pcr

Peak cell rate of the incoming cell stream multipied by 900 to get a quarter based value.It may be used for policing, necessary for calculating the utilization percentage of thecorresponding connection. The PCR is asserted at the creation of a connection and isconstant for its life time.

incomingCells

Number of incoming cells.

Trigger: Each time a valid ATM cell is coming in from the line.

outgoingCells

Number of outgoing cells.

Trigger: Each time an ATM cell is going out to the line.

17.4.2 Cell Level Protocol MeasurementsCell level protocol measurements count the number of arriving cells discarded due tothe detection of ATM layer protocol violations (invalid header pattern, not assignedVPI/VCI value or out-of-range VPI/VCI value).

discardedCellsInvalidHeader

Number of ATM cells discarded due to header content errors.

Trigger: Each time an incoming ATM cell with an invalid header is discarded, the counteris incremented.

17.4.3 Virtual Path and Virtual Channel MeasurementsThe virtual path (VP) measurements refer to the objects VP connection termination point(CTP) and VP trail termination point (TTP). The VP CTP object delimits virtual path links.When a VP failure is detected, the VP CTP object generates an alarm notification withthe probable cause parameter value. The VP TTP object delimits virtual path connec-tions. These VP/VC measurements require a measurement in a peer unit (e.g., RNC),which responds.

The virtual channel (VC) measurement refers to the object VC connection terminationpoint (CTP). The VC CTP object delimits virtual channel links.

userCells

Number of transmitted user information cells processed on the termination point beingmonitored.

A50016-D1112-G802-1-7618 225


Counter Description

Trigger: Each time a forward monitoring (FM) cell arrives the counter is increased. Thedifference of the TUC-fields (transmitted user cell) of the current and the last FM cell isadded to this counter.

lostCells

Number of detected lost cells.

Trigger: Each time a forward monitoring (FM) cell arrives and the difference of the TUC-fields is greater than the number of the received user cells between the last two incom-ing FM cells, the counter is increased.

misinsertedCells

Number of detected misinserted cells.

Trigger: Each time a forward monitoring (FM) cell arrives and the difference of the TUC-fields is smaller than the number of the received user cells between the last FM cells,the counter is increased.

feUserCells

Number of transmitted user information cells processed on the termination point beingmonitored by the far-end terminal.

Trigger: Each time a backward reporting (BR) cell arrives, the counter is increased. Thedifference of the TUC-fields of the current and the last BR cell is added to this counter.

feLostCells

Number of lost cells that were detected by the far end terminal.

Trigger: Each time a BR cell arrives and the number of transmitted far end user cells(derived from the TUC fields) is greater than the difference of the TRCC-fields (total re-ceived cell count) of the current and the last incoming BR cell, the counter is increased.

feMisinsertedCells

Number of misinserted cells that were detected by the far end terminal.

Trigger: Each time a BR cell arrives and the difference of the TUC fields is smaller thanthe difference of the TRCC-fields of the last two BR cells, the counter is increased.

226 A50016-D1112-G802-1-7618


18 AbbreviationsA2SC AAL2 server card

AAL2 NNI AAL2 network to network interface

ASCI advanced speech call items

ATE AAL2 termination element

ATM asynchronous transfer mode

BAP base processor

BR backward reporting

BS bearer service

BSC base station controller

BSS base station system

BSSAP base station system application part

CAM call processing maintenance

CAMEL customized application for mobile networkenhanced logic

CAP call processor

CCBS completion of calls to a busy subscriber

CCNC common channel signaling network control

CDA circuit duplex asynchronous

CDMA code division multiple access

CDPA called party address

CDS circuit duplex synchronous

CGPA calling party address

CI cell identity

CIC circuit identification code

CID channel identifier

CKSN cipher key sequence number

CLIP calling line identification presentation

CLIR calling line identification restriction

CN core network

COLP connected line identification presentation

COLR connected line identification restriction

CP coordination processor

CPS common part sublayer

CPS-PDU CPS-protocol data unit

CSC combined switching center

CUG closed user group

DLU digital line unit

DSP digital signal processor

DTMF dual tone multifrequency

EIR equipment identity register

A50016-D1112-G802-1-7618 227


Counter Description

eMLLP enhanced multi-level precedence and pre-emption

FM forward monitoring

FTP file transfer protocol

GCR group call register

GMSC gateway MSC

GP group processor

GPRS general packet radio service

GSM global system for mobile communication

GSMSCF GSM service control function

HEC header error control

HPLMN home PLMN

HSCSD high-speed circuit-switched data

IMEI international mobile equipment identity

IMSI international mobile subscriber identity

IN intelligent network

INT internal traffic

ITU international telecommunication union

LACOD location area code

LAI location area identity

LNR location routing number

LTG line/trunk group

MML man-machine language

MOC mobile originating call

MP main processor

MS mobile station

MSISDN mobile subscriber ISDN number

MSRN mobile station roaming number

MSU message signaling unit

MTC mobile terminating call

MTP message transfer part

NP number portability

O&M operation and maintenance

OACSU off-air call setup

ODB operator determined barring

OMC operation and maintenance center

OMC Operation and Maintenance Center

OSF offset field

PAD packet assembler/disassembler

PCS personal communication system (at 1900MHz)

PVLR previous VLR

228 A50016-D1112-G802-1-7618


RANAP radio access network application part

RNC radio network controller

SAM sequential access method

SC service center

SCCP signaling connection control part

SCI subscriber controlled input

SCP service control point

SLS signaling link selection

SMS short message service

SS supplementary service

SS7 signaling system number 7

SSNC signaling system network control

SSP service switching point

STF start field

TCH traffic channel

TMSI temporary mobile subscriber identity

TRCC total received cell count

TS teleservice

TSC TRAU server card

TUC transmitted user cell

USSD unstructured SS data

UUI user to user indication

VBS voice broadcasting service

VC virtual channel

VCC virtual channel connection

VGCS voice group call service

VMSC visited MSC

VP virtual path

A50016-D1112-G802-1-7618 229


Counter Description

19 IndexAaal2-overrun-counter 212aal2-underrun-counter 213accBLOCK-Incoming 215accBLOCK-Outgoing 215accCONFUSION-Incoming 215accCONFUSION-Outgoing 215accERQ-Attempt 215accERQ-Failed-Attempt-Overload-Error 215accERQ-Failed-Attempt-Protocol-Error 215accERQ-Failed-Attempt-Resource-Error 215accERQ-Failed-Attempt-Unspecified-Error 215ACCESSED_EPLMN_DEFAULT_LIST 108ACCESSED_EPLMN_LISTS 108AccMOD-Attempt 216AccMOD-Failed-Attempt-Overload-Error 216AccMOD-Failed-Attempt-Protocol-Error 216AccMOD-Failed-Attempt-Resource-Error 216AccMOD-Failed-Attempt-Unknown-Error 216accREL-Attempt 216accREL-Failed-Attempt 216accRESET-Access-Incoming 216accRESET-Access-Outgoing 216accRESET-CID-Incoming 216accRESET-CID-Outgoing 216accRESET-Path-Incoming 216accRESET-Path-Outgoing 216accUNBLOCK-Incoming 216accUNBLOCK-Outgoing 217accUNKNOWN-MESSAGE 217ACT_SS_TO_HLR 110ACT_TRACEMODE_FROM_HLR 109ACTIVE_QUEUING 34adjacentInaccessibleDuration 188adjacentInaccessibleEvents 188ADMIN_ACT_TRACEMODE 126ADMIN_DEACT_TRACEMODE 126ALT_SPEECH_DATA_ANSWER 53ALT_SPEECH_DATA_ATTEMPTS 33ALTERN_SPEECH_DATA 117ALTFAXSP_CALL_ATTEMPTS 32ALTFAXSP_WITH_ANSWER 52ANGRP_BLO_TIME 177ANN_ERROR 50ANN_NO_ERROR 50ANSW_INCOM_CALLS 151ANSW_ORIG_CALL 151AOC_CHARGING_LEVEL 119AOC_INFORM_LEVEL 119ASCI_EMLPP 123ASCI_VBS 123ASCI_VGCS 123

assocAvailable 196assocUnavailable 196ATB TIME 164, 178, 185ATTEMPTED_TMSI_REALLOCATIONS 106ATTEMPTS_TRFO_BICC 67ATTEMPTS_TRFO_RANAP 67AUTH_AUTH_FAIL_REP_REQ 107AUTH_AUTH_FAIL_REP_SUCC 107AUTH_MAC_FAIL_RECEIVED 107AUTH_REQ 104AUTH_REQ_CKSN_MISMATCH 105AUTH_REQ_WITH_AUTN 107AUTH_SYNCHRON_FAIL_RECEIVED 107AUTH_WITH_ILLEGAL_SUB 106

BBEARER CHANNELS 175BLOCKED BEARER CHNS 175BLOCKED_SUB_REGISTERED_IN_HLR 115BS_REL_WITH_ANSWER 53BSSAP_PL_DECODING_ERR 102BSSAP_PL_UNKNOWN 102

CCA_COM_PAGING 37CA_COM_PAGING_RETRY 37CA_DATA_FR 36CA_DATA_HR 36CA_FIX_DISPATCH_VGCS_VBS 64CA_HANDOVER_SDCCH 54CA_HO 152CA_HSCSD_2FR 36CA_MOB_DISPATCH_VGCS_VBS 63CA_MOB_SERV_SUB_IN_RMSC 67CA_ORMMC_OR_ORECF 41CA_PTP_EMLPP 67CA_SERV_SUB_VBS 63CA_SERV_SUB_VGCS 63CA_SPEECH_FR 36CA_SPEECH_HR 36CA_VGCS_VBS_EMLPP 28CA_VGCS_VBS_TERM 66CALL_ATT_MS_OWN_MSC_NO 31CALL_ATT_PURE_TRANSIT 31CALL_ATTEMPTS 31CALL_BACK 119CALL_BARR_INC_CALLS 118CALL_BARR_INC_ROAM_OUT_HPLMN 118CALL_BARR_OUTG_CALLS 118CALL_BARR_OUTG_INT_CALL_HPLMN 118CALL_BARR_OUTG_INT_CALLS 118CALL_CCBS 51

230 A50016-D1112-G802-1-7618


CALL_END_CALL_FORW 49CALL_END_CALL_FORW_OR 50CALL_END_CF_MS_BUSY 49CALL_END_CF_NO_REPLY 50CALL_END_CF_NOT_REACH 49CALL_FORW_DEF 121CALL_FORW_ON_MS_BUSY 117CALL_FORW_ON_MS_NOT_REACH 118CALL_FORW_ON_NO_REPLY 117CALL_FORW_UNCONDITIONAL 117CALL_GREY_LIST 49CALL_HOLD 120CALL_INT_MS_FOREIGN_MSC 48CALL_INT_MS_OWN_MSC 48CALL_LINE_IDENT_PRESENT 118CALL_LINE_IDENT_RESTR 119CALL_REL_ALERT 49CALL_REL_BEF_ALERT 48CALL_REL_EXCHANGE 48CALL_TCH_ALLOCATION 47CALL_TIOUT_ALERT 49CALL_TRANSFER 51CALL_WAITING 120CALL_WHITE_LIST 49CALL_WITH_UNIDENT_SUB 98CALLS_COMPL_BUSY_SUB 120CALLS_WITH_ANSWER 51CAMEL_PSI 102CAMEL_USSD 122camOVERLOAD-from-RNC 223camOVERLOAD-to-RNC 223camRESET-from-RNC-CS 223camRESET-from-RNC-PO 223camRESET-RESOURCE-from-RNC-CS 223camRESET-RESOURCE-from-RNC-PO 223camSSP-from-SCMG-CS 223camSSP-from-SCMG-PO 223CARRIED_TRAFFIC 171CC 168, 178CC LNP QUERY ATTEMPT 170CC LNP QUERY SUCCESS 170CC LOST DA:TERM INC 176CC LOST DA:TERM INT 176CC LOST SC:ORIG 172, 176CC LOST SC:TERM INC 171, 176CC LOST SC:TERM INT 172, 176CC LOST TS:ORIG 176CC LOST TS:TERM INC 176CC LOST TS:TERM INT 176CC LOST:ORIG 176CC LOST:TERM INC 175CC LOST:TERM INT 176CC NH ALT1 REROUTING 167CC ON SC:ORIG 172CC ON SC:TERM 172

CC ON TS:ORIG 175CC ON TS:TERM 175CC PRECEDENCE:I 167CC PRECEDENCE:O 167CC PREEMPTED:I 168CC PREEMPTED:O 167CC:I (O) 163, 184CC:INTRA-RSU 180CC:NH ALT1:O 167CC:NH ALT2

O.....CCS NH ALT2 ANSW:O 167CC:NH DIRECT:O 166CC:SCI D-CHANNEL 175CC_ANSW_VGCS_VBS 65CC_HO 152CCBS 34CCBS_RECALL 35CCS CCS7 CALL FAIL 169CCS CCS7 CALL FAILURE 166CCS CONGESTION 164CCS EXT TECHN IRREG 165, 169CCS INCMP DIAL 164, 169CCS INT TECHN IRREG 165, 169CCS LINK FAILURE 164, 169CCS NH ALT1 ANSW:O 167CCS NH ALT2 ANSW

O 167CCS NH DIRECT ANSW:O 167CCS OPERATOR RELEASE 169CCS RELORIG ENDTOEND 164, 169CCS SUB BUSY 165, 169CCS TECHN IRREGULAR 178CCS UNALL NUM 164, 169CCS UNANSWERED 165, 169CCS WITH ANSWER 169CCS_ANSWER:I (O) 163, 184CCS_COM_PAGING_RES 37CCS_DISPATCH_RECONN_VGCS_VBS 64CCS_SDCCH_ALLOC 56CCS_TO_FROM_ATM_NETW 74CCS7 DPC OLOAD 166ccs7MgrAverageLoad 210ccs7MgrMaximumLoad 210CCU ALL TRUNKS BUSY 166CCU CCS7 CCNC OLOAD 166CCU CCS7 DPC OL ACC 166CCU CCS7 DPC OLOAD 166CCU CONGESTION 170CCU LOST CALLS 165CCU NH ALT1 LOST 167CCU NH ALT2 167CCU NH DIRECT OFL 167CCU NM CODE BLOCKING 170CCU NM TGRP BLOCKING 165, 170CCU PDN:O 185

A50016-D1112-G802-1-7618 231


Counter Description

CCU SUM OFL/LOSS 165CCU TECHN IRREGULAR 165, 170CCU TGRP BLOCKED 165CCU TRUNKRESERVATION 165CCU:O 185CCU_ANGRP_BLOCKED 178CCU_ATB 178CCU_COM_PAGING 37CCU_CONGESTION_ATM 68CCU_DATA_FR 47CCU_DATA_HR_6K 46CCU_HSCSD_2FR 47CCU_LACK_CONF_UNIT 65CCU_OVERLOAD_INIT_VGCS_VBS 63CCU_OVERLOAD_SETUP_VGCS_VBS 65CCU_PROTOCOL_ERROR_BCF 68CCU_PROTOCOL_ERROR_CSF 68CCU_SERV_SUB_BUSY_VGCS_VBS 64CCU_SPEECH_FR 46CCU_SPEECH_HR 46CCU_TECHN_ERROR_BCF 68CCU_TECHN_IRREGULAR 178CCU_UNSUPPORTED_BCF 68CHECK_SS_FROM_HLR 110CIPHERING_REQ 105CLOSED_USER_GROUP 119CODEC_MODIFICATION_ATTEMPTS 68COM_LUP_LAI_NULL 112COM_LUP_PERIODIC 112COM_LUP_REQ 112COM_LUP_TMSI_COM 113COM_LUP_TMSI_REQ 112COMPL_INTERROGATIONS 48COMPL_INTERROGATIONS_SC 48COMPL_SCI_CALL_REL 48COMPL_SCI_INDEPENDENT 47CONN_LINE_IDENT_PRESENT 119CONN_LINE_IDENT_RESTR 119CONNECTED CHANNELS 185CONNECTED LINES 163, 177cpsCPSPacketError6 220cpsHeaderXmitError7 220cpsOctetsError2 219cpsParityError0 219cpsSDULenghtError5 220cpsSTFSeqError1 219cpsUUIError8 220cpsValueOSFError3 219cpsXmitError4 220crefMessagesReceived 202crefMessagesSent 202CRM/CR:SUM DELAYS 173CRM/CRP:ACCEPTED CALLS 173CRM/CRP:DELTHR EXCEEDED 173CRM/CRP:NUMB OF BLOCKED 173

CRM/CRP:NUMB OF CONNECT 173CRM/CRP:NUMBER OF DELAYS 173CRM/CRP:SUMMARY EFFECTS 173CRM/CRP:TC 173crMessagesReceived 202crMessagesSent 202

DD_ALT_SPEECH_DATA 31D_CONV_ALTFAXSP 30D_CONV_DATACDA_ANA 30D_CONV_DATACDA_DIG 30D_CONV_DATACDS_ANA 30D_CONV_DATACDS_DIG 31D_CONV_DED_PAD 30D_CONV_FAX3 30D_CONV_SPEECH_SERV 30D_CONVERSATION 30DATA_CDA 116DATA_CDS 117DATA_CDS_GBS 121DATACDA_ANA_ATTEMPTS 32DATACDA_ANA_WITH_ANSWER 52DATACDA_DIG_ATTEMPTS 32DATACDA_DIG_WITH_ANSWER 52DATACDS_ANA_ATTEMPTS 32DATACDS_ANA_WITH_ANSWER 52DATACDS_DIG_ATTEMPTS 33DATACDS_DIG_WITH_ANSWER 52DEACT_SS_TO_HLR 110DEACT_TRACEMODE_FROM_HLR 109DED_PAD_ATTEMPTS 32DED_PAD_WITH_ANSWER 52DELETE_FROM_HLR 109DETACH_MSG_TMSI_NO_IMSI_CORR 97disallowedCdpa 204disallowedCdpaAfterTranslation 204disallowedCdpaDig 205disallowedCdpaTranslator 204disallowedCgpa 204disallowedCgpaDig 205disallowedCgpaTranslator 204disallowedMsgType 204disallowedOperationContext 205disallowedScreeningDomain 204disallowedSSAMessages 205disallowedSSCmessages 204disallowedSSPMessages 205disallowedSSTmessages 204discardedCellsInvalidHeader 224discardedMSUs 188, 192discardedSD-PDUs 194DOWNGRADING_NETWORK_INIT 93DOWNGRADING_USER_INIT 92dpcIsAdjacent 190

232 A50016-D1112-G802-1-7618


dt1MessagesFromSourceSSN 201dt1MessagesToSinkSSN 201dt2MessagesFromSourceSSN 201dt2MessagesToSinkSSN 200

EedMessagesFromSourceSSN 201edMessagesToSinkSSN 201EMERGENCY_TS12_ATTEMPTS 33EMPTY_RESPONSE_TO_AUTH_SET 106ENTRY_OP_BARR 96ENTRY_SS_ACT 96ENTRY_USED_DETACH 96ENTRY_USED_FOREIGN 96ENTRY_USED_OWN 96ERA_SS_TO_HLR 110errMessagesReceived 201errMessagesSent 202ESRK_ALLOC_ATT 38EXPLICIT_IMSI_DETACH 97

FFACSIMILE_SERVICES 116failedGtTransNoAddressOfSuchNature 204failedGtTransNoRuleForSpecAddress 204failReleaseComplete 199FAX3_CALL_ATTEMPTS 32FAX3_WITH_ANSWER 52feLostCells 225feMisinsertedCells 225feUserCells 225FOLLOW_ME 121FRC_IWE_ANACDS_NTP 90FRC_IWE_ANALOG_NTP 89FRC_IWE_ANALOG_TP 89FRC_IWE_DIGCDS_NTP 90FRC_IWE_DIGITAL_NTP 89FRC_IWE_DIGITAL_TP 89FRC_IWE_FAX3_TP 90FRC_IWE_SP_FAX3_NTP 94FRC_IWE_SP_FAX3_TP 94

GGEN_TRAFF_CHAN_REQ 34GP_IDR 173GP_MEANT 173GS_IF_MS_INFO_ERR 113

HHANDOVER_ATTEMPTS 54HANDOVER_BETTER_CELL 55HANDOVER_DATA_CALL_ATTEMPTS 54HANDOVER_DIRECTED_RETRY 55HANDOVER_DISTANCE 55

HANDOVER_DOWNLINK_QUALITY 54HANDOVER_DOWNLINK_STRENGTH 54HANDOVER_MSC_MSC_IC_ATTEMPTS 55HANDOVER_MSC_MSC_OG_ATTEMPTS 55HANDOVER_MSC_MSC_OG_DAT_ATT 55HANDOVER_OP_MAINT_INT 55HANDOVER_RESP_TO_MSC 55HANDOVER_UPLINK_QUALITY 54HANDOVER_UPLINK_STRENGTH 54HO_CONFERENCE 56HO_OLD_CELL 56HO_PERFORMED 56HO_REQUIRED 152HOT_BILLING 120

IIDENT_REQ_AUTH_FAILURE 104IDENT_REQ_CORR_FAILURE 104IDENT_REQ_INTW_PVLR_FAILURE 104IDENTITY_REQUESTS 104IDENTITY_REQUESTS_UMTS 107IMEI_CHECKS 34IMPLICIT_IMSI_DETACH 97IN_ATTEMPTS 34IN_ERROR_DEST 46IN_ERROR_SCP 46IN_NO_ANSW_SCP 46IN_OVERLOAD 45IN_REROUTE 50IN_SERV_CHECK 46IN_SERVICE_CLASS_MARK_MOC 120IN_SERVICE_CLASS_MARK_MTC 120IN_TRANS 34INC_HO_WITH_ANSWER 53INCOM_CALL_ATT_QUEUING 150, 151INCOM_CALL_ATTEMPTS 150INCOM_CALL_QUEUE_TCH_ALLOC 151INCOM_CALL_SUCC_TCH_ALLOC 151incomingCells 224inhLinkDurUnavail 191, 192INSERT_FROM_HLR_LOCUPD 108INSERT_FROM_HLR_OCI_SCI 109INTERCELL_HO_INC 152INTERCELL_HO_OUTG 152INTERROG_HANDLED_BY_VLR 111INTERROG_TO_HLR 110INTERROG_UNSUCC_SUBSCR 111INTERROG_UNSUCC_SYSTEM 111INTRACELL_HO_BSC 152INTRACELL_HO_MSC 152INTW_BSS_ILLEGAL_ME 102INTW_BSS_ILLEGAL_SUB 101INTW_BSS_IMSI_UNKNOWN_IN_HLR 101INTW_BSS_LAI_UNKNOWN 102INTW_BSS_LOCAREA_NOT_ALLOWED 101

A50016-D1112-G802-1-7618 233


Counter Description

INTW_BSS_NETWORK_FAILURE 101INTW_BSS_NO_SUIT_CELL_IN_LOCAREA 102INTW_BSS_OTHER_REASONS 102INTW_BSS_PLMN_NOT_ALLOWED 101INTW_BSS_RADIO_REASONS1 101INTW_BSS_RADIO_REASONS2 101INTW_BSS_ROAMING_NOT_ALLOWED 102INTW_BSS_SECOND_TRANS_LOCUPD 102INTW_HLR_DEST_OUT_OF_SERVICE 100INTW_HLR_OTHER_REASONS 100INTW_HLR_PROTOCOL_ERRORS 100INTW_HLR_RESTOR_HLR 99INTW_HLR_ROAMING_NOT_ALLOWED 99INTW_HLR_SYSTEM_FAILURE 100INTW_HLR_TCAP_ABORT 100INTW_HLR_TCAP_TIMER_EXPIRY 99INTW_HLR_UNKNOWN_SUB 99INTW_PVLR_DEST_OUT_OF_SERVICE 100INTW_PVLR_OTHER_REASONS 101INTW_PVLR_PROTOCOL_ERRORS 101INTW_PVLR_TCAP_ABORT 100INTW_PVLR_TCAP_TIMER_EXPIRY 100INTW_PVLR_UNIDENT_SUB 100INVOC_AOC_CHARGE_INFO 82INVOC_SERV_AOC_CHARGE 82INVOC_SERV_CALL_BACK 82INVOC_SERV_CALL_FORWARD 81INVOC_SERV_CALL_TRANSFER 83INVOC_SERV_CCBS_MORTR 83INVOC_SERV_CCBS_MTER 83INVOC_SERV_CLIP 82INVOC_SERV_CLIR 82INVOC_SERV_MULTIPARTY 82INVOC_SERV_PUT_HOLD 82INVOC_SERV_RETRIEVE_HOLD 82INVOC_SERV_UUS 83INVOKE_SS_BAOC 111INVOKE_SS_BOIC 111ipLinkSetUnavailableDuration 195IWE_ANACDS_NTP 86IWE_ANALOG_NTP 85IWE_ANALOG_TP 85IWE_DIGCDS_NTP 87IWE_DIGITAL_NTP 86IWE_DIGITAL_TP 86IWE_FAX3_TP 86IWE_SP_FAX3_NTP 94IWE_SP_FAX3_TP 94

LLA_CHANGES_AFTER_RECOV 98LA_CHANGES_FOREIGN_PLMN 97LA_CHANGES_OWN_PLMN 97LINKED_SUB_REGISTERED_IN_HLR 114LNP_MISROUTED_CALL 28

LNP_QUERIES_LRN 28LNP_UNALLOC_NUM_MICTR 28LNP_VACANT_CODE 28LOC_UPD_COUNTER 148LOCATION_ATTEMPTS 38LOCUPD_LAI_NULL 98lostCells 225lostMSUCongestionEventThreshold-1 189lostMSUCongestionEventThreshold-2 190lostMSUCongestionEventThreshold-3 190lostMSUsBufferOverflow 189ludtMessageSent 202ludtMessagesReceived 203ludtsMessageSent 202ludtsMessagesReceived 202

Mmcsd-data-underrun-counter 213messagesForLocalSubsystems 200messagesHandled 200messagesOriginatedPerSsnSpcCl0 201messagesOriginatedPerSsnSpcCl1 201messagesReceivedOrTerminatedPerSsnSpcCl0 201messagesReceivedOrTerminatedPerSsnSpcCl1 201messagesRequiringGTTranslation 200messagesToBackupSsn 201messageTooLarge 199mhSpare04AverageLoad 210mhSpare04MaximumLoad 210mhSpare05AverageLoad 210mhSpare05MaximumLoad 210mhSpare06AverageLoad 210mhSpare06MaximumLoad 210mhSpare07AverageLoad 210mhSpare07MaximumLoad 210mhSpare08AverageLoad 210mhSpare08MaximumLoad 210MIN NUM FREE SC 172MIN NUM FREE TS 176misinsertedCells 225MM_INFO_SENT 104MO_LR_ASSIST_DATA 41MO_LR_ASSIST_DATA_ATT 41MO_LR_DEC_KEYS 41MO_LR_DEC_KEYS_ATT 41MO_LR_SELF_LOC 41MO_LR_SELF_LOC_ATT 41MO_LR_TTTP 42MO_LR_TTTP_ATT 42MO_LR_TTTP_GMLC_ATT 42MORE_THAN_ONE_MSRN_ALLOC 109MS_MEMORY_AVAIL_TO_HLR 110MS_PRESENT_TO_HLR 111MSC_MSC_HO_CALL_ATTEMPTS 33MSRN_SENT 109

234 A50016-D1112-G802-1-7618


MSRN_TIMER_EXPIRES 109MSUB_REGISTERED_GPRS 121MSUB_ROAM_FOREIGN_GPRS_PLMN 121mSUsOriginatedOctets 187mSUsTerminatedOctets 187mSUsThroughSwitchedOctets 187MT_LR_ATT 40MULTI_PARTY_SERVICE 119

NNATIONAL_CALLTRANS 120NATIONAL_FEATURE_1 123networkCongestion 199NI_LR_ATT 42NI_LT 42NO OF BLO LINES 163NO_OF_AMS 148NO_OF_BLACK_EQUIPMENT 147NO_OF_BLACK_IMEI 146NO_OF_GREY_EQUIPMENT 147NO_OF_GREY_IMEI 146NO_OF_IMEI_CHECK_MESSAGES 146NO_OF_LMU 124NO_OF_MS 148NO_OF_TAC_FAC 146NO_OF_UNKNOWN_EQUIPMENT 147NO_OF_UNSUCC_MESSAGES 146NO_OF_WHITE_EQUIPMENT 147NO_OF_WHITE_IMEI 146nodeIsolationDuration 187nodeIsolationForAnyReason 187noPointCodeAvailable 199noReassemblyResources 199noTranslForNatureAddress 200noTranslForSpecificAddress 199nrOfGtTranslations 203nrOfGtTranslationsToOrigDomain 203nrOfSSAMessagesReceived 203nrOfSSCMessagesReceived 203nrOfSSPMessagesReceived 203nrOfSSTMessagesReceived 203NUM ALL SC OCCUPIED 172NUM ALL TS OCCUPIED 176NUM_ALLOC_GCNR 66NUM_ASCI_CALL_SETUP_RECVD_RMSC 66NUM_ASCI_CALL_SETUP_TO_RMSC 66NUM_ATRIB_REQ_GCR 64NUM_ATRIB_RESPONSE_GCR 64NUM_ATT_SCP_DIALOGS_LNP 27NUM_ATT_SCP_DIALOGS_SMS 28NUM_ATT_SCP_DIALOGS_USSD 28NUM_BSSAP_MS_INF_REQ_SNT_DU_CL 103NUM_BSSAP_MS_INF_RESP_W_CL_REC 103NUM_CALL_SET_UP_CONTRIB 29NUM_CALLS_REL_BS 26

NUM_CELL_SETUP_RESP_GCR 64NUM_COM_LUP_CONTRIB 37NUM_COM_PAGING_RET_A 37NUM_DISPATCH_SETUP_RESP_GCR 64NUM_IMEI_CHECK_BLACK 27NUM_IMEI_CHECK_GREY 27NUM_IMEI_CHECK_LUP 27NUM_IMEI_CHECK_PER_LUP 27NUM_IMEI_CHECK_UNKNOWN 27NUM_IMEI_CHECK_WHITE 27NUM_IWE_AVAILABLE 95NUM_IWE_BLOCKED 95NUM_IWE_BUSY 95NUM_IWE_CREATED_IN_DB 95NUM_IWE_IDLE 95NUM_LOC_REP_CTL_MAP_PSI 75NUM_LUP_CONTRIB 29NUM_MAP_ATI_WITH_CL_REC 127NUM_MAP_NOTEMM_FRN_MSUB 103NUM_MAP_NOTEMM_OWN_MSUB 103NUM_MAP_NOTEMM_SUCC_FRN_MSUB 103NUM_MAP_NOTEMM_SUCC_OWN_MSUB 103NUM_MAP_PSI_CL_FRN_MSUB_REC 103NUM_MAP_PSI_CL_OWN_MSUB_REC 103NUM_MAP_PSI_WITH_CL_SEND 127NUM_MAP_SRI_REC_HLR_WITH_CL 127NUM_MSUB_D_CSI 122NUM_MSUB_GPRS_CSI 122NUM_MSUB_IN 123NUM_MSUB_M_CSI 122NUM_MSUB_MSP 123NUM_MSUB_SMS_CSI 122NUM_MSUB_SS_CSI 122NUM_MSUB_TIF_CSI 123NUM_MSUB_TWC 123NUM_MSUB_UCSI 122NUM_MSUB_VT_CSI 122NUM_MT_LR_BLOCK_PRIV 40NUM_MT_LR_BLOCK_REJ 41NUM_MT_LR_NO_PAG_RESP 40NUM_MT_LR_OVRD_ATT 40NUM_NO_SPCH_BSSAP_LTG 27NUM_NOT_ALLOW_MAP_ATI_REC 127NUM_NOT_ALLOW_MAP_PSI_REC 103NUM_NOT_ALLOW_MAP_SRI_REC_HLR 127NUM_PAG_PERF_DUE_CL_RET 74NUM_RECEIVED_CIP 26NUM_RECEIVED_CLASSM_UPD 26NUM_RECEIVED_GCP 26NUM_RECEIVED_OVERLOAD 26NUM_RECVD_GCNR_IN_AMSC 66NUM_REQ_GCNR 66NUM_RESET 26NUM_RESET_CIRCUIT 26NUM_SEND_GCNR_TO_AMSC 66

A50016-D1112-G802-1-7618 235


Counter Description

NUM_SEND_OVERLOAD 26NUM_SIGN_POINT_PROHIB 26NUM_SSP_BSSAP 26NUM_SUCC_SCP_DIALOGS_LNP 27NUM_SUCC_SETUP_DISP_VGCSVBS 65NUM_SWITCH_LTGPOOL 28NUM_TONES_DTMF 27NUM_TOTAL_START_IMEI_CHECK 26NUM_UND_LOC_RNC 75NUM_VGCS_TALK_ACK 65NUM_VGCS_TALK_CONFIRM 66NUM_VGCS_TALK_REJECT 65NUM_VGCS_TALK_REL 65NUM_VGCS_TALK_REQ 65NUM_VGCS_VBS_SETUP_BSC_ACK 64NUM_VGCS_VBS_SETUP_BSC_REQ 64NUM_VGCS_VBS_TCH_ALLOC_ACK 65NUM_VGCS_VBS_TCH_ALLOC_REQ 64NUMB CCS7 DPC OLOAD 166NUMBER OF ATB 164, 178, 185NUMBER OF CONGESTIONS RSUC 180NUMBER OF DIUS 175numberOfTransitMessagesProcessed 200numCongestionLevel1 196numCongestionLevel2 196numCongestionLevel3 196numInMSU 186numInMSUperNet 188numIpLinkSetUnavailable 194numLinkSetNotAvail 189NumLostMSURoutErr 186numM3UA-MsgDiscarded 195numM3UA-MsgReceived 195numM3UA-MsgSent 195numOctetsReceivedPerAssocNoCtrl 196numOctetsRetransPerAssocNoCtrl 196numOctetsSentPerAssoc 195numOctetsSentPerAssocNoCtrl 196numOutMSU 187numOutMSUperNet 188numPerAssocUnavailable 196numSCTP-PacketsReceived 195numSCTP-PacketsSent 195numTransitMSU 187numTransitMSUperNet 188

OOACSU_ATTEMPTS 34OACSU_RELSUB 51OACSU_TCH_ALLOC 51OACSU_WITH_ANSWER 53ORECF_ALLOWED_IN_HLR 128ORIG_CALL_ATT_QUEUING 150ORIG_CALL_ATT_TCH_REQ 150ORIG_CALL_ATTEMPTS 150

ORIG_CALL_QUEUE_TCH_ALLOC 151ORIG_CALL_SUCC_TCH_ALLOC 151ORMMC_ALLOWED_IN_HLR 128Other_Errors_Counter_Remote 213outgoingCells 224OWN_SUB_ROAM_IN_FOREIGN_PLMN 116

PPAD_CDA 117PAG_PROC 148pcr 224POS_SEND_TO_GMLC 39prhMgrBaseLoadAverageLoad 210prhMgrBaseLoadMaximumLoad 211PROCESSOR LOAD RSUC 180protBLC-Missing 217protBLC-with-cause-value 217protBLO-Missing-Mand-Parameter 217protCNF-Missing-Mand-Parameter 217protECF-Missing-Mand-Parameter 217protERQ-Missing-Mand-Parameter 217protERQ-On-Not-Avail-Path-Access 217protInvalid-CEID-CALLP 217protInvalid-CEID-MAINT 217protInvalid-OSAID-CALLP 217protInvalid-OSAID-MAINT 218protMOD-Missing-Mand-Parameter 218protMOR-Missing-Mand-Parameter 218protOSAID-Allocation-Failed 218protREL-Missing-Mand-Parameter 218protRES-Missing-Mand-Parameter 218protRLC-with-cause-value 218protRSC-with-cause-value 218protUBC-Missing 218protUBC-with-cause-value 218protUBL-Missing-Mand-Parameter 218protUnexpected-Message 218protUnrecognized-Parameter 218PROVIDE_MSRN_RECEIVED 109providerInitiatedRelease 198providerInitiatedReset 199

QQUINTETS_REQ_BY_HLR_IMM 144QUINTETS_REQ_BY_HLR_NON_IMM 144QUINTETS_REQ_BY_HLR_RESYNC 144QUINTETS_RET_TO_HLR_IMM 144QUINTETS_RET_TO_HLR_NON_IMM 144QUINTETS_RET_TO_HLR_RESYNC 145QUINTETS_RET_TO_HLR_SUB_CREA 145

RRANAP_MM_INFO_SENT 104ranapBlocked-RNC-CS 221

236 A50016-D1112-G802-1-7618


ranapBlocked-RNC-PO 221ranapLack-Of-Resources-CS 221ranapLack-Of-Resources-PO 221ranapOverload-CS 222ranapOverload-PO 222ranapProtocol-Error-CS 222ranapProtocol-Error-PO 222ranapProtocol-Error-Unknown 222ranapTechnical-Fault-CS 222ranapTechnical-Fault-PO 222ranapTechnical-Fault-Unknown 222reassemblyTimerExpired 199RECEIVE_RP_DATA_ATTEMPTS 59RECEIVE_RP_SMMA_ATTEMPTS 59RECEIVED_DETACH_NO_VLR_ENTRY 99RECEIVED_DETACH_WITH_IMSI 99RECEIVED_DETACH_WITH_TMSI 99RECEIVED_PAG_RESP 47receivedMSUs 189, 193receivedOctets 189receivedOctetsSIFSIO 192, 193receivedSD-PDUs 194RECVD_ACT_FOLLOW_ME 126RECVD_ATI 127RECVD_AUTH_FAIL_REP_REQ 129RECVD_AUTH_FAIL_REPORT_IN_AC 145RECVD_AUTH_INF_QUINTETS_HLR 106RECVD_AUTH_INF_QUINTETS_PVLR 107RECVD_AUTH_INF_REQUESTS 129RECVD_AUTH_INF_TRIPLES_HLR 105RECVD_AUTH_INF_TRIPLES_PVLR 105RECVD_CAMEL_ATM 128RECVD_CAMEL_ATSI 128RECVD_CAMEL_USSD_TO_GSMSCF 136RECVD_CCBS_REQ_IN_HLR_A 128RECVD_CCBS_REQ_IN_HLR_B 128RECVD_DEACT_FOLLOW_ME 126RECVD_LOCUPD_HPLMN 142RECVD_LOCUPD_VPLMN 142RECVD_MSG_ACT_CALLBACK 135RECVD_MSG_ACT_SS 135RECVD_MSG_DEACT_CALLBACK 136RECVD_MSG_DEACT_SS 135RECVD_MSG_ERASE_CALLBACK 135RECVD_MSG_ERASE_SS 135RECVD_MSG_INTERROG_CALLBACK 136RECVD_MSG_INTERROG_SS 135RECVD_MSG_REGISTER_CALLBACK 135RECVD_MSG_REGISTER_PW 134RECVD_MSG_REGISTER_SS 134RECVD_MSG_UNSTRUCTURED_SS_DATA 135RECVD_MSRN 125RECVD_NOTE_MS_PRESENT 139RECVD_POS_ACK_FROM_GSMSCF 35RECVD_POS_ACK_FROM_SCP 136

RECVD_POS_ACK_NSDC_FROM_GSMSCF 128RECVD_READY_FOR_SM 139RECVD_RESET_VLR 126RECVD_RESTORE_DATA 126RECVD_RESYNCHRON_INFO 107RECVD_RESYNCHRON_REQUESTS 129RECVD_SEND_PARAM_AR 125RECVD_SEND_PARAM_AR_PR 125RECVD_SEND_PARAM_PR 125RECVD_SEND_ROUT_INFO_MSG_GMSC 125RECVD_SEND_ROUT_INFO_MSG_SCODE 125RECVD_SET_MWD 139RECVD_SND_ROUTING_INFO_SM 139RECVD_UPD_LOC_MSG_VLR_HPLMN 124RECVD_UPD_LOC_MSG_VLR_VPLMN 124REG_SS_TO_HLR 110REL_ANSW_CALL_BS_REASON 151REL_BEFORE_ACM_MICTR 42REL_CALL_BS_REASON 151REQ_COM_LUP_TO_HLR 112REQ_COM_PAG 148REQUESTS_LOCUPD 97REQUESTS_LOCUPD_INTER_VLR 98REQUESTS_LOCUPD_INTRA_VLR 97REQUESTS_LOCUPD_TO_HLR 99REQUESTS_LOCUPD_WITH_IMSI_ATT 98REQUESTS_PERIODIC_LOCUPD 98REROUTE_AFTER_SN 50REROUTE_BEFORE_SN 50REROUTE_NEW_DEST 53RES_COM_LUP_FROM_HLR 112RES_COM_LUP_FROM_PVLR 112RESERVE_COUNTER 68RESETS_RECEIVED_FROM_HLR 109RESTORE_DATA_TO_HLR 109RESTR_SUB_1_NAT_ALL_VPLMN 114RESTR_SUB_ALL_GSM_PLMN 114RESTR_SUB_HOME_PLMN_ONLY 115RESULTS_LOCUPD_FROM_HLR 99RESULTS_LOCUPD_FROM_PVLR 99retransmittedOctets 189, 193RETRY_PAG 148REUSED_TRIPLES 106, 126, 144RNC_CIPHERING_REQ 108RNC_CIPHERING_SUCC 108RNC_INTEGRITY_REQ 108RNC_INTEGRITY_SUCC 108RNC_SECURITY_REQ 108RNC_SECURITY_SUCC 108routeSetUnavailable 190routeSetUnavailableDuration 190rsrMessagesReceived 203rsrMessagesSent 203

A50016-D1112-G802-1-7618 237


Counter Description

SsccpSyntaxErrorList 200sctpAssocCongestion 196sctpPathUnavailable 196sduReceivedOctets 194sduRetransmittedOctets 194sduTransmittedOctets 194SEC_COM_PAG 149segmentationFailed 200segmentationNotSupported 198segmentReceivedOutOfSequence 200SEIZE_MAXIMUM 177Sema_IuUP_Errors_Counter_Local 213Sema_IuUP_Errors_Counter_Remote 213SEMI BLOCKED CHAN 185SEMI BLOCKED LINES 163, 177SEND_CAMEL_NSDC 128SEND_PAR_RECVD_FROM_OTHER_VLR 105SEND_PAR_REQ_AUTH_VEC_TO_HLR 105SEND_PAR_REQ_AUTH_VEC_TO_PVLR 105SEND_PARAM_REQ_SUBDAT_TO_HLR 105SEND_QUINTETS_TO_VLR 107SEND_RP_DATA_ATTEMPTS 59SEND_TRIPLES_TO_VLR 105SENT_CAN_LOC_MSG_AFTER_SCI 135SENT_CAN_LOC_SGSN_CHANGE 142SENT_CAN_LOC_SUB_ADMIN 142SENT_FORW_CHECK_SS_INDIC 135SENT_FORW_TO_NO_TO_GMSC 125SENT_INS_DEL_SUB_DATA 142SENT_INSERT_MS_DATA_AFTER_SCI 135SENT_MI_USSD_TO_HLR 111SENT_MSRN_TO_GMSC 125SENT_NI_USSD_TO_MS 111SENT_NI_USSD_TO_VLR 128SENT_NOTIF_SS_INV_TO_GSMSCF 35SENT_PSI 127SENT_PURGE_MS_MSG_TO_HLR 110SENT_RESET_HLR 126SENT_RESET_TO_SGSN 142SENT_SS_INV_NOTIF_TO_SCP 136SERV_SUB_VBS_ATTEMPTS_IN_RMSC 67SERV_SUB_VGCS_ATTEMPTS_IN_RMSC 66SERVICE_REQ_COM_LUP 37SERVICE_REQ_LOC_UPD 35SERVICE_REQ_SCI_CALL_REL 35SERVICE_REQ_SCI_INDEPENDENT 35SET_UP_SERV_CODE 34sgtrMgrAverageLoad 211sgtrMgrMaximumLoad 211SHORT_MSG_SERVICE_MO 116SHORT_MSG_SERVICE_MT 116SIGNALLING CHANNELS 175signUnitsReceived 192, 193sIInServiceDuration 191

sIUnavailabilityDuration 191SLC:ACC CALLS GP 172SLC:OFF CALLS 172SLC:REJ CALLS OL 172slCongestedDuration 193slCongestedStarts 193slFailed 191slInServiceDuration 191slLocalBlocked 192, 193slLocalInhibited 192, 193slRemoteBlocked 192, 193slRemoteInhibited 192, 193slRemoteProcOutage 191slsUnavailable 189slUnavailabilityDuration 191SMS_INC_ATTEMPTS 58SMS_INC_PARALLEL 58SMS_INC_PARALLEL_MEM_AV_INV 58SMS_OTG_ABORTED_BY_SMSC 62SMS_OTG_ATTEMPTS 58SMS_OTG_ERROR 62SMS_OTG_FALLBACK 59SMS_OTG_PARALLEL 58SMS_SER_REQ_ATTEMPTS 58SN_REROUTE_CALL 50SN_THROUGH_CONNECTIONS 48SND_ACT_TRACEMODE 126SND_ALERT_SERVICE_CENTER 139SND_ALERT_SMSC_NO_RESULT 140SND_CAN_LOC_MSG_LOC_UPD 124SND_CAN_LOC_MSG_SUB_ADMIN 124SND_DEL_SUBDT_MSG_SUB_ADMIN 124SND_INS_SUBDT_MSG 124SND_INS_SUBDT_MSG_SUB_ADMIN 124SND_PROV_MSRN 125SPEECH_CALLS_WITH_ANSWER 51SPEECH_FOLLOWED_BY_DATA 117SPEECH_TRANSMISSION 116sscs-error-counter 213STARTED_INT_SER_CODE_DIG 33STARTED_INTERROGATIONS 33STARTED_PAG_RETRY_PROC 33STARTED_PAGING_PROC 33SUB_IDENTIFIED_WITH_IMSI 104SUB_IDENTIFIED_WITH_TMSI 104SUB_REGISTERED_IN_HLR 114SUB_WITH_IMSI_TRACE_ACTIVE 115SUB_WITH_ODB_INCOMING 115SUB_WITH_ODB_OUTGOING 115SUB_WITH_ODB_PREMIUM_RATE 115SUB_WITH_ODB_ROAM 115SUB_WITH_ODB_SPECIFIC_HPLMN 115SUB_WITH_ODB_SS_MANAGEMENT 115SUBSEQ_MSC_MSC_HO_MSCA 55SUBSEQ_MSC_MSC_HO_MSCB 55

238 A50016-D1112-G802-1-7618


subsystemCongestion 199subsystemFailure 199SUCC_ALERT_SERVICE_CENTER 140SUCC_CIPH_MODE_CTRL_PROC 106SUCC_COM_LUP 112SUCC_COM_PAG 149SUCC_COMPL_HO_DATA_CALLS 56SUCC_COMPL_HO_SDCCH 56SUCC_COMPLETED_HO 56SUCC_DATA_MSC_MSC_HO_MSCA 56SUCC_ESRK_ALLOC_ATT 38SUCC_HO_SEC_MSC_MSC_HO_MSCB 57SUCC_INVOC_AOC_CHARGE 83SUCC_INVOC_AOC_INFO 83SUCC_INVOC_CALL_BACK 84SUCC_INVOC_CALL_TRANSFER 84SUCC_INVOC_CCBS_MORTR 84SUCC_INVOC_CCBS_MTER 84SUCC_INVOC_MULTIPARTY 83SUCC_INVOC_PUT_HOLD 83SUCC_INVOC_RETRIEVE_HOLD 83SUCC_INVOC_SERV_CALL_BARRING 82SUCC_INVOC_SERV_CALL_FORWARD 81SUCC_LINK_SETUP_TO_RMSC 66SUCC_LOC_ATT 38SUCC_LOC_ATT_CONV_GPS 39SUCC_LOC_ATT_MOB_ASSIST_E_OTD 38SUCC_LOC_ATT_MOB_ASSIST_GPS 39SUCC_LOC_ATT_MOB_BASED_E_OTD 39SUCC_LOC_ATT_MOB_BASED_GPS 39SUCC_LOC_ATT_TA 38SUCC_LOC_ATT_TOA 38SUCC_LOC_ATT_UNKNOWN_POS 39SUCC_LOCUPD_WITH_IMSI_ATTACH 98SUCC_MO_LR_ASSIST_DATA 41SUCC_MO_LR_DEC_KEYS 42SUCC_MO_LR_SELF_LOC 41SUCC_MO_LR_TTTP 42SUCC_MSC_MSC_HO_MSCA 56SUCC_MSC_MSC_HO_MSCB 57SUCC_MT_LR 40SUCC_MULT_SMS_INC 60SUCC_MULT_SMS_OTG 59SUCC_NI_LR 42SUCC_ORECF 35SUCC_ORMMC 35SUCC_PAG 148SUCC_POS_SEND_TO_GMLC 39SUCC_REQUESTS_LOCUPD 98SUCC_SMS_INC 59SUCC_SMS_OTG 59SUCC_SMS_OTG_IN 59SUCC_SMS_RECEIVE_RP_ACK 59SUCC_SMS_SEND_RP_ACKS 59SUCC_SMS_SEND_SMSMA_RP_ACK 60

SUCC_SUBSEQ_MSC_MSC_HO_MSCB 57SUCC_TRFO_BICC 67SUCC_TRFO_RANAP 67SUCCESS_MS_MEMORY_AVAIL 110SUCCESS_MS_PRESENT_TO_HLR 112SUCCESSFUL_CODEC_MODIFICATIONS 68SUCCESSFUL_HANDOVERS 152SUCCESSFUL_TMSI_REALLOC 106SUM ALL SC OCCU 172SUM CH BLO TIME 175SWITCHES_TO_LINKED_MS 126Synt_IuUP_Errors_Counter_Local 214Synt_IuUP_Errors_Counter_Remote 214

TTC 168TC N 178TC NH ALT1:O 167TC ON TS:ORIG 175TC ON TS:TERM 175TC SEMI BLOLI 164TC TRANS BLOLI 164TC WITH ANSWER 168TC: NH DIRECT: O 166TC:I 184TC:I (O) 163TC:O 184TC_ANSWER:I (O) 163TC_SEMI_BLOLI 177TC_TRANS_BLOLI 177TCUCMPRN 206TCUCMPSN 206TCUMSGRA 206TCUMSGRB 206TCUMSGRC 206TCUMSGRE 206TCUMSGRU 206TCUMSGSA 206TCUMSGSB 206TCUMSGSC 206TCUMSGSE 206TCUMSGSU 206TGRP BLO TIME:O 164tiarExpiry 198TIME IN CONGESTION RSUC 180TIME_CALL_SET_U_SERV 29TIME_COM_LUP_SERV 37TIME_LUP_SERV 29TMSI_REALLOC_NOT_ANSWERED 106TOTAL_CALLS_WITH_ANSWER 53TOTAL_INTENSITY 171TOTAL_NUM_MT_LR 40TOTAL_SEIZE_TIME_IFU 178TR CIRC:ACC CALLS GP 172TR CIRC:OFF CALLS 172

A50016-D1112-G802-1-7618 239


Counter Description

TR CIRC:REJ CALLS OL 173TRAFF_VOL_SUCC_PAGING 29TRAFFIC_VOLUME 29TRANS BLOCKED CHAN 185TRANS BLOCKED LINES 163TRANS_BLOCKED_LINES 177transmittedMSUs 189, 193transmittedOctets 189transmittedOctetsSIFSIO 192, 193transmittedSD-PDUs 194TRIPLES_REQUESTED_BY_HLR 144TRIPLES_RETURNED_TO_HLR 144TS11_EMERG_CALL_TCH_ALL 47TS11_EMERG_WITH_ANSWER 51TS12_EMERG_CALL_TCH_ALL 47TS12_EMERG_WITH_ANSWER 51TV INTRA RSU 180TV_ANSWER:I (O) 184TV_IWE_ANACDS_NTP 92TV_IWE_ANALOG_NTP 91TV_IWE_ANALOG_TP 90TV_IWE_DIGCDS_NTP 92TV_IWE_DIGITAL_NTP 91TV_IWE_DIGITAL_TP 91TV_IWE_FAX3_TP 92TV_SP_FAX3_NTP 94TV_SP_FAX3_TP 94TV_SUCC_COM_PAGING 37TV_VBS 63TV_VGCS 63

UU_CALL_ATTEMPTS 71U_CALL_END_CALL_FORW 73U_CALL_END_CALL_FORW_OR 74U_CALL_END_CF_MS_BUSY 74U_CALL_END_CF_NO_REPLY 74U_CALL_REL_ALERT 73U_CALL_REL_BEF_ALERT 73U_CALL_TCH_ALLOCATION 73U_CALL_TI_OUT_ALERT 73U_D_CONV_SPEECH_SERV 71U_EMERGENCY_TS12_ATTEMPTS 71U_GEN_TRAFF_CHAN_REQ 71U_HANDOVER_ATTEMPTS 75U_HANDOVER_MSC_MSC_IC_ATTEMPTS 76U_HANDOVER_MSC_MSC_OG_ATTEMPTS 76U_INTER_HANDOVER_GSM_TO_UMTS 57U_INTER_HANDOVER_UMTS_TO_GSM 76U_INTER_HO_ATT_UMTS_TO_GSM 57U_INTER_MSC_MSC_HO_ATT_GSM_UMTS_IC 7

6U_INTER_MSC_MSC_HO_ATT_GSM_UMTS_OG

57U_INTER_MSC_MSC_HO_ATT_UMTS_GSM_IC 5

7U_INTER_MSC_MSC_HO_ATT_UMTS_GSM_OG

58U_INTRA_HANDOVER_GSM_TO_UMTS 57U_INTRA_HANDOVER_UMTS_TO_GSM 76U_NUM_LUP_CONTRIB 71U_RECEIVED_PAG_RESP 72U_RELOCATION_CANCEL 77U_RNC_REL_WITH_ANSWER 74U_SERVICE_REQ_LOC_UPD 72U_SMS_INC_ATTEMPTS 78U_SMS_INC_PARALLEL 78U_SMS_OTG_ATTEMPTS 78U_SMS_OTG_PARALLEL 78U_SMS_SER_REQ_ATTEMPTS 78U_SN_THROUGH_CONNECTIONS 73U_SPEECH_CALLS_WITH_ANSWER 74U_SUBSEQ_MSC_MSC_HO_MSCA 76U_SUBSEQ_MSC_MSC_HO_MSCB 76U_SUCC_COMPLETED_HO 76U_SUCC_HO_SEC_MSC_MSC_HO_MSCB 77U_SUCC_INTER_MSC_HO_GSM_UMTS_MSCB 5

7U_SUCC_INTER_MSC_HO_UMTS_GSM_MSCB 5

7U_SUCC_MSC_MSC_HO_MSCA 77U_SUCC_MSC_MSC_HO_MSCB 77U_SUCC_MULT_SMS_INC 79U_SUCC_MULT_SMS_OTG 79U_SUCC_SMS_INC 78U_SUCC_SMS_OTG 78U_SUCC_SUBSEQ_MSC_MSC_HO_MSCB 77U_TRAFFIC_VOLUME 70U_TS11_EMERG_CALL_TCH_ALL 73U_TS11_EMERG_WITH_ANSWER 74U_TS12_EMERG_CALL_TCH_ALL 73U_TS12_EMERG_WITH_ANSWER 74U_UNS_CONGESTION 72U_UNS_MS_BUSY 72U_UNS_RNC_REASON 72U_UNS_UTRAN_REASON 72udtMessagesReceived 202udtMessagesSent 202udtsMessagesReceived 202udtsMessagesSent 202uniMgrAverageLoad 211uniMgrMaximumLoad 211unknownDestinationAddress 199unknownOrUnqualifiedRoutingFailure 200UNRELDIR 127UNS_ACT_FOLLOW_ME_MS_BEH 130UNS_ACT_FOLLOW_ME_SYS_BEH 130UNS_ACT_TRACEMODE 130UNS_ACT_TRACEMODE_SUB_ADMIN 133UNS_ADMBLCKD_OR_CALLBARR 140

240 A50016-D1112-G802-1-7618


UNS_AUTH_INF_REQ_OTHER 134UNS_AUTH_INF_REQ_UNAVAIL_AV 134UNS_BLACK_LIST 45UNS_BS_REASON 45UNS_CALL_SS_BIC 132UNS_CALL_SS_BICROAM 132UNS_CAMEL_ATM 134UNS_CAMEL_ATSI 134UNS_CAMEL_USSD_BY_GSMSCF 139UNS_CAMEL_USSD_BY_HLR 139UNS_CAN_LOC_SGSN_CHANGE 143UNS_CAN_LOC_SUB_ADMIN 143UNS_CANLOC_ANY_OTHER_SS 138UNS_CANLOC_UNIDENT_SUB_SS 138UNS_CANLOCMSG_ANY_OTHER 130UNS_CANLOCMSG_UNIDENT_SUB 130UNS_CCBS_REQ_OTHER 132UNS_CCBS_REQ_SUB_BEH 132UNS_CONGESTION 44UNS_CUG_REJECT 45UNS_DEACT_FOLLOW_ME_MS_BEH 130UNS_DEACT_FOLLOW_ME_SYS_BEH 131UNS_DEACT_TRACEMODE_SUB_ADMIN 133UNS_DEL_SUBDT_MSG_SUB_ADMIN 133UNS_DOWNGRADING_USER_INIT 93UNS_GMSC_BEHAVIOR 140UNS_IMEI_UNKNOWN 45UNS_INS_DEL_SUB_DATA 143UNS_INS_SUBDT_MSG 130UNS_INS_SUBDT_MSG_SUB_ADMIN 132UNS_INTERROGATION 45UNS_IWE_ANACDS_NTP 88UNS_IWE_ANALOG_NTP 87UNS_IWE_ANALOG_TP 87UNS_IWE_DIGCDS_NTP 88UNS_IWE_DIGITAL_NTP 88UNS_IWE_DIGITAL_TP 87UNS_IWE_FAX3_TP 88UNS_IWE_SP_FAX3_TP 94UNS_LACK_IWE 44UNS_LINK_FAIL 44UNS_LOC_ATT_CONGESTION 38UNS_LOC_UPD_HPLMN_OTHER 143UNS_LOC_UPD_HPLMN_SUB_BEH 143UNS_LOC_UPD_OVL 141UNS_LOC_UPD_VPLMN_OTHER 143UNS_LOC_UPD_VPLMN_SUB_BEH 143UNS_LOST_LOCATION 140UNS_MS_BLOCKED 43UNS_MS_BUSY 44UNS_MS_DETACH 45UNS_MS_PRESENT_TO_VLR 141UNS_MTC_OVL 141UNS_MULT_SMS_INC 62UNS_MULT_SMS_OTG 61

UNS_NETW_MANAGEMENT 44UNS_OVERLOAD 45UNS_PAGING 43UNS_PROTO_ERROR 44UNS_RCVD_PSI 131UNS_RECVD_SET_MWD 141UNS_REQ_DEST_ERROR 43UNS_RESP_ACT_CALLBACK 138UNS_RESP_ACT_SS_SUB_BEH 137UNS_RESP_ACT_SS_SYS_BEH 137UNS_RESP_DEACT_CALLBACK 138UNS_RESP_DEACT_SS_SUB_BEH 137UNS_RESP_DEACT_SS_SYS_BEH 137UNS_RESP_ERASE_CALLBACK 138UNS_RESP_ERASE_SS_SUB_BEH 137UNS_RESP_ERASE_SS_SYS_BEH 137UNS_RESP_INS_SUBDT_SS 138UNS_RESP_INTERROG_CALLBACK 138UNS_RESP_INTERROG_SS_SUB_BEH 137UNS_RESP_INTERROG_SS_SYS_BEH 137UNS_RESP_REGISTER_CALLBACK 138UNS_RESP_REGISTER_PW_SUB_BEH 136UNS_RESP_REGISTER_PW_SYS_BEH 137UNS_RESP_REGISTER_SS_SUB_BEH 136UNS_RESP_REGISTER_SS_SYS_BEH 136UNS_RESP_UNSTRUCTURED_SS_DATA 138UNS_RESTORE_DATA 132UNS_SECONDARY_CAUSES 140UNS_SECURITY_FAIL 44UNS_SERV_CHECK 43UNS_SMS_INC_ABSENT_MS 60UNS_SMS_INC_DELIVERY_FAIL 60UNS_SMS_INC_DEREGISTERED_MS 62UNS_SMS_INC_NO_FACILITY 60UNS_SMS_INC_PARALLEL_MS_STATE 61UNS_SMS_INC_SUBBUSY_FAIL 62UNS_SMS_OTG_DELIVERY_FAIL 61UNS_SMS_OTG_NO_FACILITY 60UNS_SMS_OTG_UNIDENT_MS 60UNS_SMS_OVL 141UNS_SMS_REC_RP_MEMORY 61UNS_SMS_REC_RP_PROT_ERR 61UNS_SMS_SEND_MES_TRAN_REJ_SMSC 62UNS_SMS_SEND_NET_OUT_OF_ORDER 62UNS_SMS_SEND_RP_FAC_CHECK_ERR 61UNS_SMS_SEND_RP_PROT_ERR 61UNS_SMS_SEND_RP_SUB_ERR 61UNS_SMS_SEND_RP_UNASSIGN_NUM 61UNS_SMS_SEND_SMSC_CONGESTION 62UNS_SMS_SEND_SMSMA_RP_ERROR 62UNS_SN_CONGESTION 44UNS_SND_PARAM_AR 133UNS_SND_PARAM_AR_PR 134UNS_SND_PARAM_OVL 141UNS_SND_PARAM_PR 133

A50016-D1112-G802-1-7618 241


Counter Description

UNS_SNDROUTINFMSG_BLCKD_BARR 131UNS_SNDROUTINFMSG_CF_VIOL 131UNS_SNDROUTINFMSG_GMSC_BEH 131UNS_SNDROUTINFMSG_LOST_LOC 132UNS_SNDROUTINFMSG_MS_BEH 131UNS_SNDROUTINFMSG_SEC_CAUSES 132UNS_SNDROUTINFMSG_SUB_ERROR 131UNS_SS_OVL 141UNS_SUB_ADMIN_CANLOC_ANY_OTHER 133UNS_SUB_ADMIN_CANLOC_UNIDENT_MS 133UNS_SUB_BEHAVIOUR 140UNS_SUBSCRIPTION_ERROR 140UNS_TECHN_FAULT 43UNS_UPGRADING_USER_INIT 93UNS_UPLOCMSG_VLR_HPLMN_IRR_SYS 129UNS_UPLOCMSG_VLR_HPLMN_IRR_VLR 129UNS_UPLOCMSG_VLR_HPLMN_SUB_BEH 129UNS_UPLOCMSG_VLR_VPLMN_IRR_SYS 130UNS_UPLOCMSG_VLR_VPLMN_IRR_VLR 130UNS_UPLOCMSG_VLR_VPLMN_SUB_BEH 129UNSTRUC_SS_DATA_TO_HLR 111UNSUCC_RESYNCHRONISATION 134UPGRADING_NETWORK_INIT 92UPGRADING_USER_INIT 92USER_SIG1 120userCells 224userUnequipped 200

Vvcpu auditAverageLoad 209vcpu auditMaximumLoad 209vcpu backgroundAverageLoad 209vcpu backgroundMaximumLoad 209vcpu callpAverageLoad 208vcpu callpMaximumLoad 209vcpu ccs7NmAverageLoad 209vcpu ccs7NmMaximumLoad 209vcpu idleAverageLoad 209vcpu idleMaximumLoad 209vcpu mpTotalAverageLoad 208vcpu mpTotalMaximumLoad 208vcpu oamAverageLoad 208vcpu sltPrhAverageLoad 208vcpu sltPrhMaximumLoad 208vcpu Spare07AverageLoad 209vcpu Spare07MaximumLoad 209vcpu Spare08AverageLoad 209vcpu Spare08MaximumLoad 209vcpu SystemBaseLoadAverageLoad 209vcpu SystemBaseLoadMaximumLoad 210vcpu SystemIntegrityAverageLoad 208vcpu SystemIntegrityMaximumLoad 208vcpu SystemUpgradeAverageLoad 209vcpu SystemUpgradeMaximumLoad 209vcpu03oamMaximumLoad 208

violationOfHopCounter 199VLR_AREA_LEAVES_FOREIGN_PLMN 97VLR_AREA_LEAVES_OWN_PLMN 97VLR_CHANGES_PVLR_KNOWN 98VLR_CHANGES_PVLR_UNKNOWN 98

WWLL_SUB_REGISTERED_IN_HLR 114WRITTEN_MISMATCH_RECORDS 106

XxudtMessagesReceived 202xudtMessagesSent 202xudtsMessagesReceived 202xudtsMessagesSent 201

Information, Traffic and Performance Data, Counter Description, Siemens

Mobile

Transcript of Information, Traffic and Performance Data, Counter Description, Siemens