Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Information, Traffic Data Administration, Traffic Measurement, Siemens

594 views

Published on

Information, Traffic Data Administration, Traffic Measurement, Siemens

Published in: Mobile
  • Be the first to comment

  • Be the first to like this

Information, Traffic Data Administration, Traffic Measurement, Siemens

  1. 1. Information Traffic Data Administration Traffic Measurement A50016-D1109-G801-6-7618
  2. 2. Traffic Measurement Information Traffic Data Administration f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts 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 comply with 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 Teile können auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen und Sachschäden führen. Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet. Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen. Trademarks: All designations used in this document can be trademarks, the use of which by third parties for their own purposes could violate the rights of their owners. Copyright (C) Siemens AG 2002. Issued by Information and Communication Mobile Hofmannstraße 51 D-81359 München Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract. 2 A50016-D1109-G801-6-7618
  3. 3. Information Traffic Data Administration Traffic Measurement Reason for Update Summary: This document is updated with counters missing in chapter 15. Details: Chapter/Section Reason for Update Chapter 15.3.1 Counters missing from previous issue: number- OfTransitMessagesProcessed; all ludts - parame-ters; segmentationFailed. Issue History Issue Number Date of issue Reason for Update 1 10/2000 New version. 2 2/2001 Specific MTP and SCCP counters. 3 10/2001 Fault Report CLO 178 5 02/2002 Missing MP counters 6 02/2002 Missing SS7-specific Traffic Measurement Counters A50016-D1109-G801-6-7618 3
  4. 4. Traffic Measurement Information Traffic Data Administration 4 A50016-D1109-G801-6-7618
  5. 5. Information Traffic Data Administration Traffic Measurement This document consists of a total of 188 pages. All pages are issue 6. Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.1 Methods of Determining Grade of Service Data . . . . . . . . . . . . . . . . . . . . . 14 2.2 Collection of Mobile-specific Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.3 Traffic Measurement Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 3 Traffic Measurement in the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 3.1 Basic counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3.1.1 Miscellaneous part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.2 Time/duration related part (1) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.1.3 Time/duration related part (2) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.1.4 Load and demand related part (1) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3.1.5 Load and demand related part (2) of (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.1.6 Load and demand related part: LTG pooling . . . . . . . . . . . . . . . . . . . . . . . 31 3.1.7 Load and demand related part: Gs interface . . . . . . . . . . . . . . . . . . . . . . . 32 3.1.8 Load and demand related part: Location services . . . . . . . . . . . . . . . . . . . 33 3.1.9 Grade of service related part: unsuccessful calls . . . . . . . . . . . . . . . . . . . . 35 3.1.10 Grade of service related part: unsuccessful LTG pooling . . . . . . . . . . . . . . 39 3.1.11 Grade of service related part: successful call establishment . . . . . . . . . . . 40 3.1.12 Grade of service related part: answered calls. . . . . . . . . . . . . . . . . . . . . . . 44 3.2 Handover Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.2.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 3.2.2 Grade of service related part: handover establishment . . . . . . . . . . . . . . . 48 3.2.3 Grade of service related part: successful completed handovers . . . . . . . . 49 3.3 Short Message Service Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3.3.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 3.3.2 Grade of service related part: successful services . . . . . . . . . . . . . . . . . . . 50 3.3.3 Grade of service related part: unsuccessful services . . . . . . . . . . . . . . . . . 51 3.4 ASCI Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 4 Traffic Measurement for SS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.1 Supplementary Service: Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 58 4.2 Supplementary Service: Call Barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 4.3 Special Services: number of invocations . . . . . . . . . . . . . . . . . . . . . . . . . . 59 4.4 Special Services: number of successfully completed invocations . . . . . . . 60 5 Cell-related Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 5.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 5.2 Handover part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 6 Traffic-structure Measurement for HO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 7 Traffic Measurement in IWE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 7.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 7.2 Grade of service related part: unsuccessful attempts. . . . . . . . . . . . . . . . . 68 7.3 Grade of service related part: forced released calls . . . . . . . . . . . . . . . . . . 69 A50016-D1109-G801-6-7618 5
  6. 6. Traffic Measurement Information Traffic Data Administration 7.4 Grade of service related part: holding times . . . . . . . . . . . . . . . . . . . . . . . . 71 7.5 Grade of service related part: upgrading and downgrading . . . . . . . . . . . . . 73 7.6 Alternate speech fax 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 8 Traffic Measurement in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 8.1 Installation related part. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 8.2 Load and grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 8.3 Security functions related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 8.4 External interworking related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8.5 Combined paging and combined location update part. . . . . . . . . . . . . . . . . 87 9 Location-area Related Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . 89 10 Traffic Measurement in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 10.1 Structure and Installation Related Part (1) of (3) . . . . . . . . . . . . . . . . . . . . . 91 10.2 Structure and Installation Related Part (2) of (3) . . . . . . . . . . . . . . . . . . . . . 93 10.3 Structure and Installation Related Part (3) of (3) . . . . . . . . . . . . . . . . . . . . . 99 10.4 Mobility Management/Call Handling/Authentication. . . . . . . . . . . . . . . . . . 100 10.4.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 10.4.2 Grade of service related part for mobility management . . . . . . . . . . . . . . . 103 10.4.3 Grade of service related part for call handling . . . . . . . . . . . . . . . . . . . . . . 105 10.4.4 Grade of service related part for subscriber data. . . . . . . . . . . . . . . . . . . . 107 10.5 Subscriber Controlled Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 10.5.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 10.5.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 10.6 Short Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 10.6.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 10.6.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 10.7 Data Service with GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 10.7.1 Load and demand related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 10.7.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 10.8 Overload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 11 Traffic Measurement in AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 12 Traffic Measurement in EIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 12.1 Structure and installation related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 12.2 Grade of service related part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 13 Conventional SSS Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 121 13.1 Trunk Group Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 13.1.1 Index 1: seizure and traffic volume data . . . . . . . . . . . . . . . . . . . . . . . . . . 122 13.1.2 Index 2: additional trunk group data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 13.1.3 Index 3: data on successful calls without reaching their destination . . . . . 124 13.1.4 Index 4: data on refused calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 13.1.5 Index 5: data on refused calls at CCS7 trunk groups. . . . . . . . . . . . . . . . . 126 13.1.6 Index 6,7: data of non-hierarchical trunk groups . . . . . . . . . . . . . . . . . . . . 126 13.2 Destination Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 13.3 CP Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 13.4 LTG Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 13.5 GP Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 6 A50016-D1109-G801-6-7618
  7. 7. Information Traffic Data Administration Traffic Measurement 13.6 DLU Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 13.7 Announcement Group Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . 134 13.8 PBX Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 13.8.1 Service-related data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 13.8.2 Service-independent data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 14 MP Load Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 14.1 Measurement Object for VCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 14.2 Measurement Object for MH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 15 SS7-specific Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 15.1 MTP Measurement (SSNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 15.1.1 Net element measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 15.1.2 Signaling point utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 145 15.1.3 Obligatory signaling point utilization measurement. . . . . . . . . . . . . . . . . . 145 15.1.4 Network MSU measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 15.1.5 Signaling point measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 15.1.6 Link set duration measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 15.1.7 Destination point measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 15.1.8 Obligatory link duration measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 15.1.9 Link duration measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 15.1.10 Obligatory link utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 147 15.1.11 Link utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 15.1.12 Link congestion measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 15.2 CCS7-specific Measurement (CCNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 15.2.1 CCS7 Route Set Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 15.2.2 CCS7 Link Set Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 15.2.3 CCS7 Grade of Service Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 15.2.4 CCS7 Link load Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 15.2.5 CCS7 Discarded MSU Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 15.2.6 CCS7 Measurement of all MSUs Received, Transmitted, Forwarded . . . 154 15.2.7 Measuring Statistics Data at SSP/SCP Interface . . . . . . . . . . . . . . . . . . . 154 15.3 SCCP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 15.3.1 SCCP Counters with SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 15.3.1.1 SCCP error performance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 156 15.3.1.2 SCCP utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 15.3.1.3 SCCP quality of service measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 15.3.2 SCCP Counters with CCNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 15.3.2.1 SCCP utilization measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 15.3.2.2 SCCP quality of service measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 15.3.2.3 SCCP error performance measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 162 15.4 TCAP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 16 Mobile-Specific Traffic Supervision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 17 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 18 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 A50016-D1109-G801-6-7618 7
  8. 8. Traffic Measurement Information Traffic Data Administration Illustrations Fig. 2.1 Grade of service model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Fig. 3.1 Traffic types in scope of the observed MSC . . . . . . . . . . . . . . . . . . . . . . 20 8 A50016-D1109-G801-6-7618
  9. 9. Information Traffic Data Administration Traffic Measurement Tables Tab. 2.1 Traffic measurement jobs in D900/D1800/D1900 . . . . . . . . . . . . . . . . . 17 Tab. 14.1 Object classes for MP load measurements . . . . . . . . . . . . . . . . . . . . . 138 Tab. 15.1 Object classes for MTP measurements . . . . . . . . . . . . . . . . . . . . . . . . 143 Tab. 15.2 Measurement for CCS7 signaling data . . . . . . . . . . . . . . . . . . . . . . . . 149 Tab. 15.3 Object classes for SCCP measurements. . . . . . . . . . . . . . . . . . . . . . . 156 Tab. 16.1 Traffic counter functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Tab. 16.2 Particular calculations with OMT output. . . . . . . . . . . . . . . . . . . . . . . . 173 A50016-D1109-G801-6-7618 9
  10. 10. Traffic Measurement Information Traffic Data Administration 10 A50016-D1109-G801-6-7618
  11. 11. Information Traffic Data Administration Traffic Measurement 1 Introduction Optimum traffic conditions can be achieved in the Public Land Mobile Network (PLMN) thanks to an increasingly sophisticated range of variations in network design and traffic routing. This involves the increased intermeshing of the network nodes and thus a great-er planning effort. Careful, future-oriented planning makes it possible, in the majority of cases, to avoid traffic bottlenecks and overload situations, even in the face of major traf-fic fluctuations. Traffic data acquisition is therefore of decisive importance for the telecommunications carriers with respect to · traffic handling Traffic bottlenecks can be detected as early as possible. A consistently high quality of service can be ensured, resulting from the grade of ser-vice, call processing performance and transmission quality. · traffic forecasting Network nodes can be composed for the long-term, demand-oriented expansion of the networks. Contrary to the systems of older technology, the D900/D1800/D1900 system does not require any special equipment for traffic data acquisition. A broad range of intra-system functions is available for the tasks at hand. These functions collect and process traffic data from all parts of the network nodes and trunk groups. For instance, the call process-ing programs include traffic data registration and specific programs record traffic mea-surement data. The numerous tasks in traffic data acquisition are subdivided into two areas for the pur-pose of more convenient management and handling: – traffic supervision – traffic measurement Traffic supervision Traffic supervision implies that traffic flows, losses in the trunk network, and other vari-ables which affect the quality of service must be determined. To provide the required quality of service, the telecommunications equipment in operation at any time must therefore be supervised, continuously or periodically. Therefore, traffic data for the op-eration is recorded and call processing traffic of the network nodes and the switching network is analyzed. The grade of service is affected by the modes of operation (e.g. a delay or a loss ) as-sociated with the dimensioning of the serving trunk groups. To ensure an adequate grade of service for switching operations in the individual network nodes, software counts are periodically compared with predefined threshold values. Should these threshold values be exceeded, messages and data indicating any irregularities in call processing are output. A result is, for instance, that faulty trunks (transmission paths) can be blocked at short notice, or traffic overloads can be anticipated and prevented, e.g. by traffic management measures. A50016-D1109-G801-6-7618 11
  12. 12. Traffic Measurement Information Traffic Data Administration Traffic measurement Traffic data acquisition is also used to verify whether the traffic data taken as a planning basis is still correct. Therefore, the dimensioning of trunk groups is an important plan-ning task. To ensure sufficient traffic handling capacity, the grade of service in the busy hour is prespecified when trunk groups have to be expanded or added. Traffic has to be processed not only by trunk groups and switching networks, but also by all the control devices associated with them. It is essential to know how often the de-vices will be used within a given time. A gauge of this demand is the mean number of calls offered per unit of time, the number of call attempts during the busy hour (i.e., the BHCA value), the number of successful switching network (SN) through-connections. Measurements of these traffic variables indicate the call load on the call processors and on the control devices, and the requirements for the switching network. Traffic measurement registers events and duration of states in the system or system parts. Hence, basic data for the long-term expansion of call-processing equipment is available to meet a growth in telecommunications traffic over time. Since the traffic data from the peak traffic periods must be used as the basis for planning work, traffic mea-surements must be carried out during these periods. Traffic measurement in D900/D1800/D1900 Traffic data acquisition creates the necessary conditions for reliable traffic planning, such as – a prediction of the traffic development, which forms the basis for expansion of the call-processing equipment and the network. – the assessment and supervision of past or future investments. – the monitoring of current traffic in order to ensure switching operation and constant quality of service. This means: recognition of traffic bottlenecks during the switching operation and also of insufficiently used or unused capacity. Various types of data are collected independently of each other in the D900/D1800/D1900 system. They are collected in and by every system element and for every main unit or logical/functional configuration (e.g. entire MSC), trunk groups, loca-tion area or cells). Therefore, a number of counters for the registration of events in the network elements are implemented. So, all kinds of traffic data are collected from the traffic flows between these elements, i.e. specific messages being exchanged within the network are counted. The counters are continuously updated by the call-processing SW. As soon as a traffic measurement job is started, the results wil be processed to the mag-netic disk. They can then be used to calculate the load, the utilization and the grade of service of the system. Traffic measurement jobs in the D900/D1800/D1900 system are subdivided into mobile-specific, conventional, and CCS7-specific traffic measurement jobs. 12 A50016-D1109-G801-6-7618
  13. 13. Information Traffic Data Administration Traffic Measurement · Mobile-specific traffic measurement Unlike the PSTN, ISDN, a PLMN consists of additional, mobile-specific units such as VLR, HLR, AC, IWE, EIR. The traffic measurement data of these units must be registered. Because a PLMN deals with call processing and transmission in a different way than a PSTN/ISDN does, datamust be recorded for modified or additional mobile-specific functions or procedures. Examples of mobility events are: – location update, – authentication, – paging, – roaming, – handover. · Conventional traffic measurement Conventional traffic measurement prepares jobs that register data on user traffic or signaling traffic. Some of the functions measured in the course of such jobs are han-dled as the PLMN; within this respect, only the MSC takes part in user traffic. Con-sequently, some of these traffic measurement jobs are relevant in the PLMN. Examples of such events are: – start of call setup in a GMSC, – connection with announcement groups. Measurements that effect the PBXs are typical for a combined switching center. · CCS7-specific traffic measurement AS for the PSTN/ISDN, signaling data traffic applies to CCS7 routes to destination point codes (DPCs), the load on signaling links, the transfer of message signaling units, the availability of routing areas. The traffic measurement that prepares jobs to register these signaling data is relevant in the PLMN too. For dimensioning the whole PLMN, traffic measurement data on manufacturer-specific subunits and auxiliary units (e.g. use of conference modules) must also be registered. Nevertheless, this data is not dealt with in the document The counters from this document marked with * are described by means of a call flow in a separate document “Traffic Counter Description”. In this way it is possible to exactly show the point in the call flow where the counter is triggered by a specific message. A50016-D1109-G801-6-7618 13
  14. 14. Traffic Measurement Information Traffic Data Administration 2 Implementation Traffic data acquisition in all parts of the PLMN nodes and trunk groups is important to ensure a consistently high quality of service in traffic handling. This encompasses: – the grade of service – the call processing performance – the transmission quality A broad range of intra-system functions is available for the tasks at hand. To this end, the call processing programs from all units integrate traffic data registration by which it is possible to continuously count traffic-affecting messages being exchanged within the network. This data is registered in measurement counters. The Traffic Measurement document describes all possible counters being provided for the registration of events all over the D900/D1800/D1900 system. By carrying out the appropriate traffic measurement jobs, relevant data will be collected. The document Monitoring of Traffic Counters contains information and commands for traffic supervision. In this way the operator is able to get knowledge of: – traffic flows between the network nodes; – losses in the trunk network; – variables affecting the quality of service. 2.1 Methods of Determining Grade of Service Data The model in Fig. 2.1 is used for obtaining the data for grade of service measurement. According to this model, requests and attempts for certain services and system func-tions are offered to or generated by the PLMN and its units. These requests and at-tempts can be generated either by the mobile subscriber (e.g. by raising the handset) or by the system (e.g. by starting a handover or location update). requests attempts successfully completed Fig. 2.1 Grade of service model unsuccessfully terminated behavior of mobile subscriber system behavior reasons relating to the user/the network 14 A50016-D1109-G801-6-7618
  15. 15. Information Traffic Data Administration Traffic Measurement The requests and attempts bring about activities in the system which are carried out with a certain grade of service. Some attempts are completed successfully, others are termi-nated without success (loss, abandonment or rejection). · Successfully completed actions can lead to further activities (e.g. successful inter-rogation leads to call setup to the visited MSC). · Unsuccessful attempts can be offered again or automatically repeated by the sys-tem. A distinction can be made between the following groups of unsuccessfully ter-minated attempts. – mobile subscriber behavior (e.g. replacing handset during call setup, incorrect dialing) – system behavior (e.g. lack of resources, overload, technical faults) – user or network related reasons (e.g. certain features or options are blocked or not provided, subscriber blocked by the operating company) Certain errors within the grade of service measurement jobs are derived from the error causes within the messages of the protocols used (e.g. MAP, BSSAP error causes). Since these causes are very detailed, they are often summarized in a number of counters. Two release events can be distinguished. – The release event detected by the call processing software of the LTG’s group pro-cessor is sent as a reason for call failure (RCF) in the release message from the LTGs to the CP. – The release event detected by the call processing software of the coordination pro-cessor (CP) is sent as a reason for call termination (RCT) in a command (e.g.) to the LTGs. Some of the data recorded via load and seizure-related traffic measurement jobs is also necessary for grade of service measurement (e.g. the number of calls offered is neces-sary for traffic load and, together with successfully completed calls, for grade of service measurements). Load and seizure-related traffic measurement and grade of service measurement can thus be carried out in one measurement job. 2.2 Collection of Mobile-specific Data To collect mobile-specific traffic data, the operator has to activate a measurement job by an MML command (see ). Appropriate commands exist to collect the relevant data for the measurement of the traffic load and grade of service in the different D900/D1800/D1900 units. – in the MSC – in the IWE – in the VLR – in the HLR – in the AC – in the EIR There are also commands to collect data regarding the traffic in the radio cells and the location areas. Even the data collection regarding invocations of call forwarding and call barring can be started with an MML command. The operator has to specify within the command – the objects to be measured, A50016-D1109-G801-6-7618 15
  16. 16. Traffic Measurement Information Traffic Data Administration – the recording period, and – the output device. There are three types (with the same format) to output files onto magnetic disk. The file format is fully described in an appropriate document that will be delivered with the sys-tem SW load. It describes the output of the measured data such that it is possible to cre-ate postprocessing programs for this data. · A time-controlled measurement job with output to individual files being created and assigned to the measurement job. Such file can record all the data arising during traffic measurement (one file per job, one traffic measurement type). · Continuous measurement job with output to day files collecting only the data relating to one measurement day. Such file is assigned to only one specific measurement job, i.e., only one traffic mea-surement type per file. Up to seven files can exist simultaneously for each job. If the operator does not delete the file after it is evaluated, it is overwritten on the same day of the following week. · Continuous measurement job with output to cyclic files, collecting only data related to each measurement period of 15 minutes. The operator can optionally assign such file to any created traffic measurement job from Tab. 2.1, except for REC INSTAT for which no output to a cyclic file can be se-lected. For each started measurement type, the proper results are then written into a separate cyclic file on disk every 15 minutes. Usually the measurement data is taken continuously but is processed only after the op-erator has entered an MML command. The CP main memory reads the data of the re-spective counters and outputs it to specified devices. This takes place every fifteen minutes during the active traffic measurement intervals, irrespective of the file type. Subsequently, MML command TRANS FILE allows to activate the transfer of the mea-surement data from magnetic disk to tape, either locally at the CP or centrally at the O&M processor (OMP). – Individual files can only be transferred at the end of a measurement job or if the job is aborted. – Day files can be transferred after the day concerned. – Cyclic files can be transferred at any moment of the day. To avoid losing measure-ment data, it may be kept on disk for a maximum of 2 days only before being trans-ferred to tape. 16 A50016-D1109-G801-6-7618
  17. 17. Information Traffic Data Administration Traffic Measurement 2.3 Traffic Measurement Jobs Tab. 2.1 gives an overview of the traffic measurement jobs integrated in the D900/D1800/D1900 system and refers to the sections with a detailed explanation. Recording job Measurement designation Chapter Mobile-specific traffic measurement: REC MSC MSC Traffic Measurement 3 REC SSERV Traffic Measurement for Supplementary Services (SS) 4 REC INTCELL (IN-TCREL) Cell-related Traffic Measurement 5 REC INTCELL (HOTRFS) Traffic-Structure Measurement for Handover 6 REC IWE Traffic Measurement in IWE 7 REC VLR VLR Traffic Measurement 8 REC LOCAREA Location-Area related Traffic Measurement 9 REC HLR HLR Traffic Measurement 10 REC AC AC Traffic Measurement 11 REC EIR EIR Traffic Measurement 12 Conventional SSS traffic measurement REC TGRP Trunk Group Traffic Measurement 13.1 REC DEST Destination Traffic Measurement 13.2 REC CP CP Traffic Measurement 13.3 REC LTG LTG Traffic Measurement 13.4 REC GP GP Traffic Measurement 13.5 REC DLU DLU Traffic Measurement 13.6 REC ANGRP Announcement Group Traffic Measurement 13.7 REC PBX PBX Traffic Measurement 13.8 CR MPLDME MP Load Measurements 14 CCS7-specific traffic measurement REC C7RSET CCS7 Route Set Measurement 15.2.1 REC C7LSET CCS7 Link Set Measurement 15.2.2 REC C7GOS CCS7 Grade of service Measurement 15.2.3 REC C7LLOAD CCS7 Link Load Measurement 15.2.4 REC C7DCDMSU CCS7 Discarded MSU Measurement 15.2.5 REC C7MSU CCS7 Measurement of all MSUs Received, Transmit-ted, Forwarded 15.2.6 Tab. 2.1 Traffic measurement jobs in D900/D1800/D1900 A50016-D1109-G801-6-7618 17
  18. 18. Traffic Measurement Information Traffic Data Administration Recording job Measurement designation Chapter REC INSTAT Measuring Statistics Data at SSP/SCP Interface 15.2.7 REC SCTC SCCP/TCAP Traffic Measurement 15.3.2 /15.4 Tab. 2.1 Traffic measurement jobs in D900/D1800/D1900 18 A50016-D1109-G801-6-7618
  19. 19. Information Traffic Data Administration Traffic Measurement 3 Traffic Measurement in the MSC In order to measure traffic in the entire MSC, a lot of data concerning the – traffic load, – traffic grade of service, – features can be recorded by counters. This data is collected during the main tasks controlled by the MSC, such as: – call setup for speech and data, – handover, – short message service. Traffic measurement can be started in the MSC by entering the command REC MSC in which one can additionally specify: – the basic counters – the handover counters – the short message service (SMS) counters – the advanced speech call items (ASCI) counters Traffic types Within the MSC basic traffic measurement part, most of the counters can be differenti-ated by several traffic types. The traffic types are within scope of the observed MSC (see Fig. 3.1) and inform about the origin and the destination of the call. The observed MSC detects whether the call to be handled has been either originated in its own area, or transmitted by another exchange. From this point of view one can dis-tinguish: · mobile originating traffic (MORTR) All traffic being initiated by a mobile subscriber in the area of the observed MSC, whatever the destination will be. · mobile incoming traffic (MICTR) Mobile traffic that has been directed to the observed MSC by another exchange. From digit translation, possibly followed by an interrogation process, the observed MSC knows where to find the destination of the call. This changes the original traffic type into one of the following types: · mobile terminating traffic (MTER) This applies to the traffic directed towards each mobile station in the area of the ob-served MSC. · mobile originating outgoing traffic to a mobile party who is subscribed in the home PLMN (MOUT_PLMN), wherever he is actually roaming. · mobile originating outgoing traffic to a party from the PSTN or another PLMN (MOUT_NOT_PLMN). · mobile transit traffic (MTRAN) Traffic that has neither been initiated in nor will terminate at the observed MS. These traffic types differ from those proposed in the GSM Recommendation 12.04 be-cause it is not always possible to distinguish between the traffic types as a result of the routing strategy used between networks. – PLMN ® PLMN – PSTN ® PLMN – PLMN ® PSTN A50016-D1109-G801-6-7618 19
  20. 20. Traffic Measurement Information Traffic Data Administration PLMN BSS MTER BSS observed MSC MICTR MOUT NOT PLMN MTER MORTR MORTR MICTR MSC MTRAN MOUT PLMN MICTR MOUT NOT PLMN MOUT PLMN PSTN PLMN Fig. 3.1 Traffic types in scope of the observed MSC 3.1 Basic counters MICTR MTRAN BSS BSS Basic counters are to collect the call setup data for both speech and data calls. This data applies to standard and mobile-specific functions. This description enumerates all the mobile-specific counters that are registered by the MSC basic traffic measurement. Due to the abundance of these counters, the descrip-tion is further divided into several parts in order to give a better summary and meaning of the counters offered: · a miscellaneous part · a time/duration related part · a load and demand related part focussing on: – LTG pooling, – Gs interface, – location services. · a grade of service related part focussing on: – unsuccessful calls, – unsuccessful LTG pooling, 20 A50016-D1109-G801-6-7618
  21. 21. Information Traffic Data Administration Traffic Measurement – successful call establishments, – answered calls. 3.1.1 Miscellaneous part NUM_RESET indicates how many RESET messages are received. Trigger: each time RESET is received from the BSC. NUM_RESET_CIRCUIT indicates how many RESET CIRCUIT messages are received Trigger: each time RESET CIRCUIT is received from the BSC. NUM_SSP_BSSAP indicates how many SUBSYSTEM PROHIBITED messages for subsystem BSSAP are received Trigger: each time SUBSYSTEM PROHIBITED is received from the BSC. NUM_SIGN_POINT_PROHIB indicates how many SIGNALING POINT PROHIBITED messages are received. Trigger: each time SIGNALING POINT PROHIBITED is received from the BSC. NUM_CALLS_REL_BS indicates how many calls are released because one of the messages referred to in “trig-ger” is received. Trigger: each time RESET, RESET CIRCUIT, SUBSYSTEM PROHIBITED (subsystem = BSSAP) or SIGNALING POINT PROHIBITED is received. NUM_RECEIVED_OVERLOAD indicates how many overload messages are received. Trigger: each time OVERLOAD is received from the BSC. NUM_SEND_OVERLOAD indicates how many overload events have occurred. Trigger: each time the MSC sends OVERLOAD messages to all connected BSCs. NUM_RECEIVED_GCP indicates how many GCP primitives are received. Trigger: each time GCP (general congestion primitive) is received from the CCS7 link system. NUM_RECEIVED_CIP indicates how many CIP primitives are received. Trigger: each time CIP (congestion indication primitive) is received from the CCS7 link. A50016-D1109-G801-6-7618 21
  22. 22. Traffic Measurement Information Traffic Data Administration NUM_RECEIVED_CLASSM_UPD indicates how many CLASSMARK UPDATE messages are received. Trigger: each time CLASSMARK UPDATE is received. NUM_TOTAL_START_IMEI_CHECK indicates how often IMEI check procedures are started. Trigger: each time CHECK IMEI is sent to the EIR. NUM_IMEI_CHECK_WHITE indicates how often the IMEI check procedure leading to a white list equipment is started Trigger: each time the EIR sends a white list after having performed an IMEI check. NUM_IMEI_CHECK_GREY indicates how often the IMEI check procedure leading to a grey list equipment is started. Trigger: each time the EIR sends a grey list after having performed an IMEI check. NUM_IMEI_CHECK_BLACK indicates how often the IMEI check procedure leading to a black list equipment is started Trigger: each time the EIR sends a black list after having performed an IMEI check. NUM_IMEI_CHECK_UNKNOWN indicates how often the IMEI check procedure leading to unknown equipment is started. Trigger: each time the EIR sends IMEI unknown after having performed an IMEI check. NUM_IMEI_CHECK_LUP indicates how often IMEI checks are started by a location update. Trigger: each time CHECK IMEI is sent with reason location update because of IMSI at-tach or normal location update. NUM_IMEI_CHECK_PER_LUP indicates how often IMEI checks are started by a periodic location update. Trigger: each time CHECK IMEI is sent with reason location update because of periodic location update. NUM_TONES_DTMF indicates how many DTMF tones are sent by the MS. Trigger: each time START DTMF is received. NUM_NO_SPCH_BSSAP_LTG indicates how often no free speech channel was found in the BSSAP LTG. Trigger: upon each failure to seize a BSSAP-LTG (internal condition; reason: no free speech channel available in this LTG). NUM_ATT_SCP_DIALOGS_LNP indicates how many queries are initiated to the number portability (NP) database in the service control point (SCP). 22 A50016-D1109-G801-6-7618
  23. 23. Information Traffic Data Administration Traffic Measurement Trigger: each time the MSC sends an IDP message to the SCP. NUM_SUCC_SCP_DIALOGS_LNP indicates how often the NP database is successfully queried. Trigger: each time the SCP sends CONNECT in reply to an NP database query contain-ing either a location routing number (LRN) or the same number as the one being sent. LNP_QUERIES_LRN indicates how many LRNs the NP database in the SCP returns after being queried; i.e. the investigated subscriber number is a ported one. Trigger: each time the NP returns a local roaming number. LNP_MISROUTED_CALL. indicates how many calls were released because they were misrouted to a ported num-ber; applies to PCS1900 networks only. Trigger: each time a release message of this type is received. LNP_UNALLOC_NUM_MICTR indicates how often the HLR returns “unknown subscriber” after being interrogated with an LRN. Trigger: each time the HLR returns ‘unknown subscriber’ after being interrogated with an LRN; also each time in the case of incoming calls with an LRN of a ported in fixed subscriber for which no code point exists; i.e. the ported in fixed subscriber has not been created in the MSC database. LNP_VACANT_CODE indicates how often the digit translation of an LRN of either a ported out subscriber or a ported in mobile subscriber fails; i.e. there exists no code point for the LRN concerned. Trigger: each time that the digit translation of an LRN of either a ported out subscriber or a ported in mobile subscriber fails. NUM_ATT_SCP_DIALOGS_SMS indicates how often an attempt for a short message has successfully invoked an IN func-tionality. Trigger: each time IN TRIGGER to start an IN function is received. NUM_ATT_SCP_DIALOGS_USSD. indicates how often an attempt for unstructured SS data has successfully invoked an IN functionality. Trigger: each time INTR USSD to start an IN function is received. NUM_SWITCH_LTGPOOL indicates how often an initial LTG has switched over to another one to continue call es-tablishment. Trigger: each time NRELAY contains another LTG than the one involved in this service request. A50016-D1109-G801-6-7618 23
  24. 24. Traffic Measurement Information Traffic Data Administration 3.1.2 Time/duration related part (1) of (2) TIME_CALL_SET_U_SERV is the average time to provide the “call setup” service. Trigger: – starts each time SET UP is received (MOC) or sent (MTC) – stops each time ASSIGNMENT COMPLETE is received NUM_CALL_SET_UP_CONTRIB indicates the number of calls contributing to “call setup time” Trigger: each time ASSIGNMENT COMPLETE is received (for the calculation of the av-erage setup time). TIME_LUP_SERV Accumulated time to provide service location update Trigger: – starts each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received – stops each time LOCATION UPDATE ACCEPT is sent NUM_LUP_CONTRIB indicates the number of location updates contributing to “location update service time”. Trigger: each time a location update contributing to TIME LUP SERV is received (for the calculation of the mean holding time). TRAFF_VOL_SUCC_PAGING indicates the duration of the paging procedure (unit 50ms). Only successful paging pro-cedures are included, but no timeout cases Trigger: – starts each time PAGING is sent – stops each time PAGING RESPONSE is received 3.1.3 Time/duration related part (2) of (2) TRAFFIC_VOLUME indicates the sum of all holding times. Trigger: start and stop depend on the message of the respective traffic type: MORTR:starts each time CM SERVICE REQUEST is received; stops each time RELEASE COMPLETE is received. MICTR: starts each time IAM is received; stops each time RELEASE COMPLETE is received. MTER: starts each time PAGING is sent; stops each time RELEASE COMPLETE is received, or at paging time-out. MOUT_(NOT)_PLMN:starts with proper result of digit analysis after interrogation; stops when RELEASE COMPLETE is sent or received, or with an unsuccessful call attempt before IAM is sent. MTRAN:starts with proper result of the digit analysis; 24 A50016-D1109-G801-6-7618
  25. 25. Information Traffic Data Administration Traffic Measurement stops when RELEASE COMPLETE is received. DUR_OF_CONV_SPEECH_SERV indicates duration of conversation for speech services. Trigger: start and stop depend on the message of the respective traffic type: MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_OF_CONVERSATION indicates duration of conversation for MTRAN. Trigger: starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_DATACDA_ANA indicates the duration of conversation for data CDA (circuit duplex asynchronous) ana-log services. Trigger: start and stop depend on the message of the respective traffic type: MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_DATACDA_DIG indicates the duration of conversation for data CDA digital services. Trigger: start and stop depend on the message of the respective traffic type: MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_ALTFAXSP indicates the duration of conversation for alternate speech/facsimile services. Trigger: start and stop depend on the message of the respective traffic type: MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_FAX3 indicates the duration of conversation for the automatic facsimile group 3 service. Trigger: start and stop depend on the message of the respective traffic type: A50016-D1109-G801-6-7618 25
  26. 26. Traffic Measurement Information Traffic Data Administration MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_DED_PAD indicates the duration of conversation for dedicated PAD (packet assembler/disassem-bler) access for MOUT_NOT_PLMN. Trigger: starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_DATACDS_ANA indicates the duration of conversation for data CDS (circuit duplex synchronous) 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 call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_OF_CONV_DATACDS_DIG indicates the duration of conversation for data CDS digital services. Trigger: start and stop depend on the message of the respective traffic type: MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. DUR_ALT_SPEECH_DATA indicates the duration of conversation for alternate speech/data or speech followed by data services. Trigger: start and stop depend on the message of the respective traffic type: MTER: starts each time CONNECT is received; stops each time call is released. MOUT_(NOT)_PLMN:starts each time ANSWER is received; stops each time call is released. 3.1.4 Load and demand related part (1) of (2) CALL_ATTEMPTS .indicates how many call attempts have taken place, independently of the received BS or TS (except for MOUT_(NOT)_PLMN). Trigger: each time the respective message is involved: MORTR:upon receipt of each CM SERVICE REQUEST with SERVICE TYPE = mobile originating call ... or establishment of all emergency call attempts. Short message service and SS activation are not included. 26 A50016-D1109-G801-6-7618
  27. 27. Information Traffic Data Administration Traffic Measurement MICTR: each time IAM is received (all call attempts). MTER: each time PAGING is sent. The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent (all call attempts). The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_(NOT)_PLMN:upon receipt of SET UP and digit analysis results in this traffic type (speech call attempts only). MTRAN:each time IAM is received and digit analysis results in outgoing traffic (all call attempts). DATACDA_ANA_ATTEMPTS indicates how many call attemps have taken place for data CDA analog services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: MTER: The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_PLMN: MOUT_NOT_PLMN: In general, the values of this counter will include traffic without interrogation unless international interrogation is applied. DATACDA_DIG_ATTEMPTS indicates how many call attempts have taken place for data CDA digital services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: MTER: The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_PLMN MOUT_NOT_PLMN: In general, the values of this counter will include traffic without interrogation unless international interrogation is applied. ALTFAXSP_CALL_ATTEMPTS indicates how many call attempts for alternate speech/facsimile services have taken place. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: MTER: The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_PLMN MOUT_NOT_PLMN: In general, the values of this counter will include traffic without interrogation unless international interrogation is applied. FAX3_CALL_ATTEMPTS indicates how many call attempts for the automatic facsimile group 3 service have taken place. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: A50016-D1109-G801-6-7618 27
  28. 28. Traffic Measurement Information Traffic Data Administration MTER: each time SET UP is sent MOUT_(NOT)_PLMN 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 indicates the number of call attempts for data CDS analog services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: MTER: The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_PLMN MOUT_NOT_PLMN: In general, the values of this counter will include traffic without interrogation unless international interrogation is applied. DATACDS_DIG_ATTEMPTS indicates the number of call attempts for data CDS digital services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: MTER: The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_PLMN MOUT_NOT_PLMN: In general, the values of this counter will include traffic without interrogation unless international interrogation is applied. ALT_SPEECH_DATA_ATTEMPTS indicates the number of call attempts for alternate speech/data or speech followed by data services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: MTER: The exact trigger condition is the detection of a MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to A-interface. MOUT_PLMN MOUT_NOT_PLMN: In general, the values of this counter will include traffic without interrogation unless international interrogation is applied. EMERGENCY_TS12_ATTEMPTS indicates the number of emergency call attempts (TS12) for MORTR. Trigger: each time CM SERVICE REQUEST indicating an emergency call is received. MSC_MSC_HO_CALL_ATTEMPTS indicates the number of call attempts caused by inter MSC handover for MTER; (MSC-B is the home MSC). 28 A50016-D1109-G801-6-7618
  29. 29. Information Traffic Data Administration Traffic Measurement Trigger: each time IAM is received from MSC-A and digit processing detects a handover number. STARTED_PAGING_PROC indicates the number of started initial paging procedures for MTER. Trigger: each time PAGING is sent. STARTED_PAG_RETRY_PROC indicates the number of started paging retry procedures for MTER. Trigger: each time PAGING is sent after the first expiry of the paging timer. STARTED_INTERROGATIONS indicates the number of started interrogations. Trigger: each time SEND ROUTING INFO is sent upon receipt of SETUP MORTR:to another MS MICTR STARTED_INT_SER_CODE_DIG indicates the number of started interrogations including service code digits. Trigger: each time SEND ROUTING INFO is sent to the HLR and digit analysis reveals that the MSISDN is a short code or a service code directory number. MORTR:to another MS MICTR SET_UP_SERV_CODE indicates the number of received setup messages containing short code digits or service codes for MORTR. Trigger: each time SET UP is received from the MS and digit analysis reveals that the MSISDN is a short code or a service code directory number. GEN_TRAFF_CHAN_REQ indicates the number of generated traffic channel requests. Trigger: each time ASSIGNMENT REQUEST is sent to the BSC MORTR:after the previous receipt of CM SERVICE REQUEST. MTER: after previous paging. MOUT_(NOT)_PLMN:the counter is only incremented in the case of rerouting, e.g. COC failure. ACTIVE_QUEUING indicates the number of calls where queuing was active. Trigger: each time QUEUING INDICATION is received from the BSC. The counter will be actualized when ASSIGNMENT COMPLETE or RELEASE COMPLETE is received for the call. MORTR MTER MOUT_(NOT)_PLMN A50016-D1109-G801-6-7618 29
  30. 30. Traffic Measurement Information Traffic Data Administration IMEI_CHECKS indicates the number of IMEI checks caused by call setup. Trigger: each time CHECK IMEI is sent to the EIR. MORTR MTER IN_ATTEMPTS indicates the number of call attempts invoking IN functions. Trigger: each time an interworking to an IN service control point (SCP) is started as a result of digit evaluation (e.g. dial an IN directory number) being part of a call setup. MORTR MICTR IN_TRANS indicates the number of call attempts invoking IN functionality, whereby no interworking with the IN SCP is started (e.g. televoting with service filtering so that precounting is done in the SSP). Trigger: each time an interworking to IN SCP is started for a non call-related transaction. MORTR MICTR OACSU_ATTEMPTS indicates the number of attempted calls with OACSU for MOUT_(NOT)_PLMN. Trigger: each time SET UP is received and OACSU treatment is initiated for the proper traffic type. CCBS The CCBS service is activated by a mobile subscriber at the MSC-A. This CCBS request is sent to the MSC-B of the called subscriber where it initiates an activation as well. This counter indicates the number of activation attempts. Trigger: each time a CCBS REQUEST activating CCBS MORTR: is sent by the MSC-A. MTER: is received from the MSC-A CCBS_RECALL Once the busy subscriber at the MSC-B is released he can recall the subscriber at the MSC-A. This counter indicates the number of CCBS recall attempts. Trigger: each time REMOTE USER FREE MORTR:is received from the MSC-A. MTER: is sent by the MSC-B 3.1.5 Load and demand related part (2) of (2) SERVICE_REQ_SCI_INDEPENDENT indicates how often call-independent services were requested via SCI. Trigger: each time CM SERVICE REQUEST is received for SS activation without being involved in a call. 30 A50016-D1109-G801-6-7618
  31. 31. Information Traffic Data Administration Traffic Measurement SERVICE_REQ_SCI_CALL_REL indicates how often services were requested via SCI during a parallel call. Trigger: each time CM SERVICE REQUEST is received for SS during a call. SERVICE_REQ_LOC_UPD indicates how often service requests for location update are received. Trigger: each time COMPLETE L3 INFO with LOCATION UPDATE REQUEST is re-ceived. RECVD_POS_ACK_FROM_GSMSCF indicates how often the GSM service control function has sent a positve acknowledge-ment. Trigger: each time a message containing a positive acknowledgement is received. SENT_NOTIF_SS_INV_TO_GSMSCF indicates how often the GSM service control function is requested to invoke a supple-mentary service. Trigger: each time SS INVOCATION NOTIFY is sent to the GSM service control func-tion. 3.1.6 Load and demand related part: LTG pooling These counters are intended to collect data about the use of LTG pools. LTG pooling provides a group of circuits that support the same channel types. – a specific speech transcoder is provided to transmit speech on the radio interface, allowing speech transmission via half rate channels (HR) or full rate channels (FR). – circuit switched user data is handled by the channel coding for transmission via FR channels on the radio interface at specific rates: a rate of 6 kbit/s results from channel coding TCH/F4.8 a rate of 12 kbit/s results from channel coding TCH/F9.6 a rate of 14.5 kbit/s results from channel coding TCH/F14.4 – the high-speed circuit-switched data (HSCSD) facility enables data to be transported by the PLMN using 2 traffic channels at the radio interface for the same data call. This facility just applies to 9.6 and 14.4 user data rates for BS20. The corresponding rates at the radio interface are 12 and 14.5 kbits/s. CA_SPEECH indicates the number of attempts for speech calls for which a trunk providing the proper channel attributes is seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper trunk is sent for HR (V1 or V3) FR (V1 or V2 or V3) CA_DATA_FR indicates the number of attempts for data calls for which a trunk providing the proper channel attributes for specific rates on the radio interface is seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper LTG is sent for 12K A50016-D1109-G801-6-7618 31
  32. 32. Traffic Measurement Information Traffic Data Administration 14.5K 14.5K only CA_HSCSD_2FR indicates the number of attempts for high-speed data calls for which a trunk providing 2 channels with the proper attributes is seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper LTG is sent for 12 only 14.5K 14.5K only 3.1.7 Load and demand related part: Gs interface TIME_COM_LUP_SERV Accumulated time to provide service combined location update being handled via the Gs 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 indicates how often service requests for a combined location update are received. Trigger: each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received via the Gs interface. NUM_COM_LUP_CONTRIB indicates how many combined location updates have caused the ‘combined location up-date service time’. TV_SUCC_COM_PAGING indicates the 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 indicates the number of started combined paging procedures. Trigger: each time PAGING is sent on both the A interface and the Gs interface. CA_COM_PAGING_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 after PAGING REJECT on the latter has been received. NUM_COM_PAGING_RET_A indicates the number of started paging procedures on the A interface after an unsuc-cessful attempt on the Gs interface. 32 A50016-D1109-G801-6-7618
  33. 33. Information Traffic Data Administration Traffic Measurement Trigger: each time PAGING is sent on the A interface upon PAGING REJECT on the Gs interface has been received. CCU_COM_PAGING indicates the number of calls terminated because the combined paging procedure did not succeed. Trigger: each time the connection is released because the paging timer expired for the second time. CCS_COM_PAGING_RES indicates the number of successfully completed combined paging procedures. Trigger: each time PAGING RESPONSE is received from the BSC. 3.1.8 Load and demand related part: Location services The initial position of any mobile station from which the subscriber makes an emergency call must be delivered to a public safety answering point, as required for PCS1900 net-works. Such call will trigger location measurement equipment in the MSC that interfaces with the gateway mobile location center. The latter manages the overall coordination of resources required to perform the positioning of the calling MS. Within this respect an emergency services routing key (ESRK) can be allocated for call and MS identification. ESRK_ALLOC_ATT indicates the number of attempts for allocating an ESRK. Trigger: each time the digit evaluation results into an emergency call. SUCC_ESRK_ALLOC_ATT indicates the number of successful attempts allocating an ESRK. Trigger: each time such key is found after the digit evaluation. LOCATION_ATTEMPTS indicates the number of location attempts. Trigger: each time DT1:PERFORM LCS is sent to the LTG. UNS_LOC_ATT_CONGESTION indicates the number of unsuccessful location attempts due to congestion. Trigger: each time DT1:PERFORM LCS RESP is received indicating unsuccessful po-sitioning. SUCC_LOC_ATT indicates the total number of successful location attempts. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_TA indicates the number of successful location attempts as a result of using the ’time ad-vance’ positioning method. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi- A50016-D1109-G801-6-7618 33
  34. 34. Traffic Measurement Information Traffic Data Administration tioning. SUCC_LOC_ATT_TOA indicates the number of successful location attempts as a result of using the ’time of ar-rival’ positioning method. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_ASSIST_E_OTD indicates the number of successful location attempts as a result of using the ’enhanced observed time difference’ positioning method (MS assisted calculation). Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_BASED_E_OTD indicates the number of successful location attempts as a result of using the ’enhanced observed time difference’ positioning method (MS based calculation). Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_ASSIST_GPS indicates the number of successful location attempts as a result of using the ’global po-sitioning system’ (MS assisted calculation). Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_BASED_GPS indicates the number of successful location attempts as a result of using the ’global po-sitioning system’ (MS based calculation). Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_CONV_GPS indicates the number of successful location attempts as a result of using the convention-al ’global positioning system’. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_UNKNOWN_POS indicates the number of successful location attempts as a result of using an unknown positioning method. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. POS_SEND_TO_GMLC indicates the number of attempts for transferring both MS position estimate and emer-gency call origination to the gateway mobile location center 34 A50016-D1109-G801-6-7618
  35. 35. Information Traffic Data Administration Traffic Measurement Trigger: each time the first SUBSCRIBER LOCATION REPORT is successfully sent. SUCC_POS_SEND_TO_GMLC indicates the number of successful transfers of the MS position estimate and the emer-gency call origination to the gateway mobile location center Trigger: each time SUBSCRIBER LOCATION REPORT ACK is received upon sending the report. 3.1.9 Grade of service related part: unsuccessful calls *REL_BEFORE_ACM indicates how many calls are released in the forward direction before ACM is sent for MICTR. Trigger: upon each release in forward direction in GMSC: before ACM is sent and after receipt of IAM. in VMSC: before address-complete condition and after receipt of IAM (release before PAGING after receipt of IAM). *UNS_PAGING indicates how many incoming calls are terminated due to an unsuccessful paging pro-cedure . Trigger: upon each release of the connection by the second expiry of the paging timer. *UNS_REQ_DEST_ERR indicates how many calls are terminated because the requested destination was un-known, blocked or could not be charged. Trigger: each time the respective message is involved: *MORTR:upon receipt of internal release (CP) after digit analysis failed. *MTER: upon receipt of RELEASE COMPLETE (cause: destination is unknown, blocked or could not be zoned). *MOUT_(NOT)_PLMN:upon rECEIPT of ISUP message RELEASE COMPLETE / UNSUCCESSFUL BACKWARD MESSAGE after digit analysis (cause: destination is unknown, blocked or could not be zoned). *MTRAN:upon receipt of RELEASE COMPLETE/UBM (cause: destination is unknown, blocked or could not be zoned). *UNS_TECHN_FAULT indicates how many calls are terminated due to technical faults in the home MSC. Trigger: each time the MSC causes a technical fault (e.g. software fault, plausibility check, hardware fault). *MORTR *MICTR *MTER *MOUT_(NOT)_PLMN *MTRAN A50016-D1109-G801-6-7618 35
  36. 36. Traffic Measurement Information Traffic Data Administration *UNS_SERV_CHECK indicates how many calls are terminated due to negative service facility checks or neg-ative compatibility checks. Trigger: each time the relevant message with the proper cause: *MORTR:RELEASE COMPLETE (e.g. service not implemented) is sent to the BSS. *MICTR:TC-U-ERROR (BS or TS not provisioned, facility not supported, forwarding violation) is received from the HLR in reply to SEND ROUTING INFO. *MTER: RELEASE COMPLETE (e.g. service not implemented) is sent to the previous exchange or the BSS. *MOUT_(NOT)_PLMN:RELEASE COMPLETE (e.g. service not implemented) is sent to the BSS. *UNS_MS_BLOCKED indicates how many calls are terminated because the subscriber was blocked by oper-ator determined barring, by administration, or by SS. Because there are unblockable destinations, the destination must be determined if the described barring conditions are fulfilled. Trigger: each time a call is released due to: *MORTR:barring of outgoing calls (calling subscriber) or of incoming calls (called subscriber). *MICTR:due to the interrogation result “CALL BARRED”. *MTER: the interrogation result “CALL BARRED” for the called subscriber. *UNS_MS_BUSY indicates how many calls are terminated because the requested subscriber is already busy. Trigger: each time the relevant message (including RELEASE messages) with reason “subscriber busy”: *MTER: UBM is sent to the previous exchange. *MOUT_(NOT)_PLMN:RELEASE UBM is received from the following exchange. *UNS_CONGESTION indicates how many calls are terminated due to (trunk) congestion in the home MSC. Trigger: each time trunk seizure is not successful due to congestion: *MORTR:BSS trunk *MTER: BSS trunk at B side. *MOUT_(NOT)_PLMN:trunk at B side. *MTRAN: trunk at B side. *UNS_SN_CONGESTION indicates how many calls are terminated due to switching network (SN) congestion. Trigger: each time a failure during SN through-connection occurs. *MORTR *MTER *MOUT_(NOT)_PLMN 36 A50016-D1109-G801-6-7618
  37. 37. Information Traffic Data Administration Traffic Measurement *UNS_LACK_IWE indicates how many calls are terminated due to lack of IWEs. Trigger: each time the seizure of IWE was not successful due to unavailable IWE. *MORTR *MTER *MOUT_(NOT)_PLMN *UNS_SECURITY_FAIL indicates how many calls are terminated due to authentication/security failure. Trigger: each time AUTHENTICATION REJECT is sent to the BSS. *MORTR *MTER *UNS_LINK_FAIL indicates how many calls are terminated due to failure/congestion/overload on associ-ated CCS7 signaling system links. Trigger: each time a call is released due to CCS7 failure (e.g. upon receipt of ”STOP TRAFFIC”). *MORTR *MICTR *MTER *MOUT_(NOT)_PLMN *MTRAN *UNS_PROTO_ERROR indicates how many calls are terminated due to protocol errors. Trigger: each time a protocol error was detected but the call could be identified. *MORTR *MICTR *MTER *MOUT_(NOT)_PLMN *MTRAN *UNS_NETW_MANAGEMENT indicates how many calls are terminated due to network management activities. Trigger: each time trunk resource management detects a network management event . *MOUT_(NOT)_PLMN *MTRAN *UNS_OVERLOAD indicates how many calls/transactions are terminated due to overload prevention. Trigger: each time a call is internally released due to an overload situation. *MORTR *MICTR *MTER *UNS_BS_REASON indicates how many calls are terminated during setup due to BSS/radio-related reasons Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PRO- A50016-D1109-G801-6-7618 37
  38. 38. Traffic Measurement Information Traffic Data Administration HIBITED, RESET, RESET CIRCUIT is received *MORTR:from the BSS before digit analysis is performed. *MTER: before digit analysis is performed. *MOUT_(NOT)_PLMN:after digit analysis has been performed. UNS_BLACK_LIST indicates how many calls are terminated because the IMEI check indicates black list equipment. Trigger: each time a result indicating ‘black list’ is received from the EIR in reply to CHECK IMEI. MTER MOUT_(NOT)_PLMN UNS_IMEI_UNKNOWN indicates how many calls are terminated because IMEI check indicates unknown equip-ment. Trigger: each time a result indicating ‘IMEI unknown’ is received from the EIR in reply to CHECK IMEI. MTER MOUT_(NOT)_PLMN UNS_MS_DETACH indicates how many calls are terminated because the called MS was detached/absent. Trigger: each time a detached or absent subscriber is detected MORTR:by a negative reply by the HLR to SEND ROUTING INFO. MICTR: by a negative reply by the HLR to SEND ROUTING INFO. MTER: in the VLR database causing the call to be released. UNS_CUG_REJECT indicates how many calls are terminated due to CUG reject. Trigger: the proper CUG error cause is reported by MORTR:sending RELEASE COMPLETE to the BSS. MICTR: sending RELEASE to the previous MSC. MOUT_(NOT)_PLMN:receiving RELEASE/UBM from the subsequent MSC. IN_OVERLOAD indicates the number of IN calls that are released due to SCP overload or automatic call gapping initiated by SCP. Trigger: each time call setup with prompted call handling is released due to IN overload prevention measures. MORTR MICTR IN_NO_ANSW_SCP indicates the number of IN calls that are released due to missing answer from SCP. Trigger: each time an IN dialog to the SCP is started and no answer is received within a timer schedule. The call setup is then released. MORTR 38 A50016-D1109-G801-6-7618
  39. 39. Information Traffic Data Administration Traffic Measurement MICTR IN_ERROR_SCP indicates the number of IN calls that are released because SCP sends unsuitable infor-mation (e.g. (new) call numbers sent from the SCP cannot be recognized/connected in the MSC, data is unreadable). Trigger: each time a connection is released because the IN SCP data received is insuf-ficient to establish it. MORTR MICTR IN_SERV_CHECK indicates the number of IN calls that are released because the required IN service is not active, e.g. not allowed for subscriber or not supported by SCP. Trigger: each time the SCP releases a call due to service/facility checks. MORTR MICTR IN_ERROR_DEST indicates the number of IN calls that are released because the called IN number is un-known. Trigger: each time the SCP releases a call because the called number is unknown. MORTR MICTR 3.1.10 Grade of service related part: unsuccessful LTG pooling CCU_SPEECH indicates how many attempts for speech calls are terminated because a trunk providing the proper channel attributes could not be seized. Trigger: each time the trunk could not be seized upon sending SET UP C with channel attributes for HR (V1 or V3) FR (V1 or V2 or V3) CCU_DATA_FR indicates how many attempts for data calls are terminated because a trunk providing the proper channel attributes for specific rates on the radio interface could not be seized. Trigger: each time the LTG could not be seized upon sending SET UP C with channel attributes for 12K 14.5K 14.5K only CCU_HSCSD_2FR indicates how many attempts for high-speed data calls are terminated because a trunk providing 2 channels containing the proper attributes could not be seized. Trigger: each time the LTG could not be seized upon sending SET UP C with channel attributes for A50016-D1109-G801-6-7618 39
  40. 40. Traffic Measurement Information Traffic Data Administration 12 only 14.5K 14.5K only 3.1.11 Grade of service related part: successful call establishment RECEIVED_PAG_RESP indicates the number of received paging response messages for MTER. Trigger: each time PAGING RESPONSE is received from the BSC. CALL_TCH_ALLOCATION indicates the number of calls with successfully completed traffic channel (TCH) alloca-tion. Trigger: each time ASSIGNMENT COMPLETE is received. MORTR MTER TS11_EMERG_CALL_TCH_ALL indicates the number of outgoing emergency calls with successfully completed traffic channel allocation for emergency calling (TS11). Trigger: each time ASSIGNMENT COMPLETE is received for TS11 calls. TS12_EMERG_CALL_TCH_ALL indicates the number of outgoing emergency calls with successfully completed traffic channel allocation for emergency calling (TS12). Trigger: each time ASSIGNMENT COMPLETE is received for TS12 calls. COMPL_SCI_INDEPENDENT indicates the number of successfully performed call-independent SCIs for MORTR. Trigger: each time RELEASE COMPLETE with facility information element (return-re-sult) is received in response to operate SS, i.e. activate/deactivate/register/erase/inter-rogate SS, register PW or process unstructured SS data. COMPL_SCI_CALL_REL indicates the number of successfully performed call-related SCIs for MORTR. Trigger: each time RELEASE COMPLETE with facility information element (return-re-sult) is received in response to operate SS. COMPL_INTERROGATIONS indicates the number of calls with successfully completed interrogations. Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR. MORTR MICTR COMPL_INTERROGATIONS_SC indicates the number of calls with successfully completed interrogations containing ser-vice codes. Trigger: each time TC-RESULT is received in response to SEND ROUTING INFO con-taining short-codes or short-service-codes. 40 A50016-D1109-G801-6-7618
  41. 41. Information Traffic Data Administration Traffic Measurement MORTR MICTR CALL_INT_MS_OWN_MSC indicates the number of calls with successfully completed interrogations leading to MS in home MSC. Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR and the MSRN evaluation results in paging. MORTR MICTR SN_THROUGH_CONNECTIONS indicates the number of successful call attempts. Trigger: each time MTER: CALL CONFIRMED is received. MOUT_(NOT)_PLMN:IAM is sent to the next exchange. MTRAN:IAM is sent to the next exchange. CALL_REL_EXCHANGE indicates how many calls are terminated by the previous exchange for MTER, and by the following exchange for MOUT_(NOT)_PLMN, and by the previous/following exchange for MTRAN. Trigger: each time RELEASE is received MTER: indicating clear forward. MOUT_(NOT)_PLMN:indicating clear backward) or UBM with causes different from busy, CUG reject, destination error. MTRAN:indicating clear forward or clear backward. CALL_REL_BEF_A_ALERT indicates how many calls are released by the A-subscriber before alerting. Trigger: each time RELEASE COMPLETE is received before alert with relevant rea-son( s), for: MOUT_(NOT)_PLMN CALL_REL_A_ALERT indicates how many calls are released by the A-subscriber during alerting. Trigger: each time RELEASE COMPLETE is received after alert and before CONNECT with relevant reason(s), for: MOUT_(NOT)_PLMN CALL_REL_BEF_ALERT indicates how many calls are released before alerting the destination. Trigger: each time upon receipt of MTER: RELEASE COMPLETE before alerting signal is received. MTRAN:RELEASE (clear backward or clear forward) before alert signal is received. CALL_REL_ALERT indicates how many calls are released before connect is received for MTER and during A50016-D1109-G801-6-7618 41
  42. 42. Traffic Measurement Information Traffic Data Administration alerting for MTRAN. Trigger: each time upon receipt of MTER: RELEASE COMPLETE after alerting is sent and before CONNECT is received. MTRAN:RELEASE (clear backward or clear forward) before receipt of ANSWER and after receipt of ACM. CALL_TIOUT_ALERT indicates how many calls are released by alert supervision time-out. Trigger: each time RELEASE COMPLETE is received due to alert supervision time-out (internal event in MSC), for: MOUT_(NOT)_PLMN CALL_WHITE_LIST indicates the number of successful calls with white listed equipment. Trigger: each time TC-RESULT (white list IMEI) is received from the EIR in response to check IMEI at call setup. MORTR MTER CALL_GREY_LIST indicates the number of successful calls with grey listed equipment. Trigger: each time TC-RESULT (grey list IMEI) is received from the EIR in response to check IMEI at call setup. MORTR MTER CALL_END_CALL_FORW indicates how many calls are ended due to start of call forwarding. Trigger: each time call forwarding treatment (e.g. busy, unconditional no paging re-sponse) is invoked and old call setup is thereby ended. MORTR MICTR MTER IN_REROUTE indicates how many calls are ended due to rerouting by IN. Trigger: each time an answer from SCP is received and call is rerouted to a new desti-nation included in the SCP response. MORTR MICTR ANN_NO_ERROR indicates how many calls are intercepted to an announcement without a known call re-lease reason. Trigger: each time a call is intercepted to an announcement by digit processing, call rout-ing without previous error (e.g. recorded announcements in call setup for queuing). MORTR MICTR 42 A50016-D1109-G801-6-7618
  43. 43. Information Traffic Data Administration Traffic Measurement MTER ANN_ERROR indicates how many calls are intercepted to an announcement after a call releasing er-ror. Trigger: each time call setup encounters an error that terminates further call handling and the call is intercepted to an announcement (e.g. announcement: subscriber cannot be reached by deactivated subscribers). MORTR MICTR MTER REROUTE_BEFORE_SN indicates how many calls are rerouted before SN through-connection. Trigger: each time a connection is rerouted to new directory numbers by digit evaluation (e.g. installation of code processing) before through-connection of the original call setup. MORTR MICTR MTER MOUT_(NOT)_PLMN MTRAN REROUTE_AFTER_SN indicates how many calls are rerouted after SN through-connection. Trigger: each time a connection is rerouted to new directory numbers by digit evaluation (e.g. installation of code processing) after SN through-connection in the home MSC; it can be caused by backward messages (UBM/Release) of the subsequent MSC. MTER MOUT_(NOT)_PLMN MTRAN SN_REROUTE_CALL indicates the number of through-connections in the switching network (SN) for rerouted calls. Trigger: each time time a through-connection of the routed call setup is successful. An-alog: SN THROUGH CONNECTIONS for routed connections changed to a new desti-nation. MTER MOUT_(NOT)_PLMN MTRAN CALL_TRANSFER indicates how many call transfers are completed by new resource configuration estab-lishing. Trigger: each time Release or Facility with return-result is sent to the BSS in response to INVOKE SS. MTER MTRAN A50016-D1109-G801-6-7618 43
  44. 44. Traffic Measurement Information Traffic Data Administration OACSU_RELSUB indicates how many calls are released by subscribers during OACSU treatment. Trigger: each time RELEASE COMPLETE during OACSU handling is received due to: a) release of the B-subscriber before a traffic channel is allocated on the A-interface; b) release of the A-subscriber before an answer of the B-subscriber is received, for: MOUT_(NOT)_PLMN OACSU_TCH_ALLOC indicates the number of call attempts with OACSU and successful traffic channel alloca-tion. Trigger: each time time ASSIGNMENT COMPLETE is received for a MOC with OACSU treatment, for: MOUT_(NOT)_PLMN CALL_CCBS indicates the number of successful CCBS call attempts. Trigger: each time IAM MORTR:is sent to destination MSC (MSC-B) after previous receipt of REMOTE USER FREE. MTER: is received from originating MSC (MSC-A) after previously sent REMOTE USER FREE. 3.1.12 Grade of service related part: answered calls SPEECH_CALLS_WITH_ANSWER indicates how many speech calls are answered. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM CALLS_WITH_ANSWER indicates the number of answered calls for MTRAN. Trigger:each time the connection has actually been released in reply to the receipt of ANM. TS11_EMERG_WITH_ANSWER indicates the number of answered emergency calls (TS11). Trigger: each time the connection has actually been released in reply to the receipt of ANM. TS12_EMERG_WITH_ANSWER .indicates the number of answered emergency calls (TS12) Trigger: each time the connection has actually been released in reply to the receipt of ANM. DATACDA_ANA_WITH_ANSWER indicates the number of answered data calls for CDA analog services. Trigger: each time the connection has actually been released in reply to the receipt of 44 A50016-D1109-G801-6-7618
  45. 45. Information Traffic Data Administration Traffic Measurement the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM DATACDA_DIG_WITH_ANSWER indicates the number of answered data calls for CDA digital services. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM ALTFAXSP_WITH_ANSWER indicates the number of answered data calls with alternation from speech to facsimile. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM FAX3_WITH_ANSWER indicates the number of answered data calls for automatic facsimile group 3. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM DED_PAD_WITH_ANSWER indicates the number of answered calls for dedicated PAD CDA services. Trigger: each time the connection has actually been released in reply to the receipt of ANM. DATACDS_ANA_WITH_ANSWER indicates the number of answered data calls for CDS analog services. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM DATACDS_DIG_WITH_ANSWER indicates the number of answered data calls for CDS digital services. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. MTER: CONNECT MOUT_(NOT)_PLMN: ANM ALT_SPEECH_DATA_ANSWER indicates the number of answered alternate speech/data or speech followed by data calls. Trigger: each time the connection has actually been released in reply to the receipt of the respective message. A50016-D1109-G801-6-7618 45
  46. 46. Traffic Measurement Information Traffic Data Administration MTER: CONNECT MOUT_(NOT)_PLMN: ANM BS_REL_WITH_ANSWER indicates the number of answered calls terminated due to BSS/radio-related reasons (e.g. loss of connection). Trigger: upon each receipt of CONNECT ACK when SUBSYSTEM PROHIBITED, RE-SET, RESET CIRCUIT, RELEASE COMPLETE/CLEAR REQ for particular reason(s) were received. MTER MOUT_(NOT)_PLMN REROUTE_NEW_DEST indicates the number of answered calls that were rerouted to a new call destination (e.g. by IN SCP Interworking). Trigger: each time ANSWER/CONNECT are received. MTER MOUT_(NOT)_PLMN MTRAN OACSU_WITH_ANSWER indicates the number of answered calls with OACSU. Trigger: each time ANM is received for a MOC with OACSU treatment, for: MOUT_(NOT)_PLMN 3.2 Handover Counters For the measurement of handover traffic in the MSC, a number of handover counters has been implemented. It should be underlined that these counters only apply to MSC controlled handovers. Counters for BSC controlled handover are defined in the BSC. Since the MSC has no knowledge about BSC-controlled handover attempts (only suc-cessful handovers are reported), the inclusion of HANDOVER PERFORMED would in-crease the handover success rate. Because the receipt of this message will indicate a BSC-controlled handover, it will not be used to trigger the counter HO_PERFORMED. The traffic types do not affect the handover traffic measurement. The handover traffic measurement relies on counters that make up – a load and demand related part and – a grade of service related part focussing: handover establishments, successful completed handovers. To be able to exactly know when the counter is triggered, the proper call flows for some handover counters are presented in “Description of Measurement Counters”. 3.2.1 Load and demand related part HANDOVER_ATTEMPTS indicates the number of handover requests. 46 A50016-D1109-G801-6-7618
  47. 47. Information Traffic Data Administration Traffic Measurement Trigger: upon receipt of HANDOVER REQUIRED without SDCCH indication. CA_HANDOVER_SDCCH indicates the number of handover attempts using a stand alone dedicated control chan-nel (applies to SMS, SCI and USSD). Trigger: upon receipt of HANDOVER REQUIRED with SDCCH indication. HANDOVER_DATA_CALL_ATTEMPTS indicates the number of handover requests for data calls. Trigger: upon each receipt of HANDOVER REQUIRED, data call active. HANDOVER_UPLINK_QUALITY indicates the number of handover requests due to uplink quality. Trigger: upon each receipt of HANDOVER REQUIRED, uplink quality. HANDOVER_UPLINK_STRENGTH indicates the number of handover requests due to uplink strength. Trigger: upon each receipt of HANDOVER REQUIRED, uplink strength. HANDOVER_DOWNLINK_QUALITY indicates the number of handover requests due to downlink quality. Trigger: upon each receipt of HANDOVER REQUIRED, downlink quality. HANDOVER_DOWNLINK_STRENGTH indicates the number of handover requests due to downlink strength. Trigger: upon each receipt of HANDOVER REQUIRED, downlink strength. HANDOVER_DISTANCE indicates the number of handover requests due to distance. Trigger: upon each receipt of HANDOVER REQUIRED, distance. HANDOVER_BETTER_CELL indicates the number of handover requests due to better cell. Trigger: upon each receipt of HANDOVER REQUIRED, better cell. HANDOVER_RESP_TO_MSC indicates the number of handover requests due to response to MSC invocation. Trigger: upon each receipt of HANDOVER REQUIRED, response to MSC invocation. HANDOVER_OP_MAINT_INT indicates the number of handover requests caused by O&M intervention. Trigger: upon each receipt of HANDOVER REQUIRED, O&M intervention. HANDOVER_DIRECTED_RETRY indicates the number of handover requests due to directed retry. Trigger: upon each receipt of HANDOVER REQUIRED, directed retry. A50016-D1109-G801-6-7618 47
  48. 48. Traffic Measurement Information Traffic Data Administration HANDOVER_MSC_MSC_OG_ATTEMPTS indicates the number of outgoing requests for inter-MSC handover (home MSC = MSC-A). Trigger: each time PERFORM HANDOVER is sent to MSC-B. HANDOVER_MSC_MSC_OG_DAT_ATT indicates the number of outgoing requests for inter-MSC handover for data calls (home MSC = MSC-A). Trigger: each time PERFORM HANDOVER is sent to MSC-B during active data call. *HANDOVER_MSC_MSC_IC_ATTEMPTS indicates the number of incoming requests for inter-MSC handover (home MSC = MSC-B). Trigger: each time HANDOVER REQUIRED is received from MSC-A. *SUBSEQ_MSC_MSC_HO_MSCB indicates the number of requests for subsequent inter-MSC handover (home MSC = MSC-B). Trigger: each time PERFORM SUBSEQUENT HANDOVER is sent to MSC-A. SUBSEQ_MSC_MSC_HO_MSCA indicates the number of requests for subsequent inter-MSC handover (home MSC = MSC-A). Trigger: each time PERFORM SUBSEQUENT HANDOVER is received from MSC-B. 3.2.2 Grade of service related part: handover establishment HO_PERFORMED indicates the number of handovers autonomously performed by the BSS. Trigger: each time the MSC-A receives HANDOVER PERFORMED from the BSS. HO_CONFERENCE indicates the number of conferences built up during all handover attempts. Trigger: upon each handover for speech call, as follows: for intra-MSC handover: MSC sends HANDOVER COMMAND to BSC for inter-MSC handover: MSC-A sends IAM to MSC-B/MSC-B’ for inter-MSC handover back to MSC-A: result (PREPARE SUBSEQUENT HANDOVER) is sent to MSC-B. HO_OLD_CELL indicates the number of handovers completed in the old cell. Trigger: each time the HANDOVER COMMAND is sent to the BSS by MSC-A. CCS_SDCCH_ALLOC indicates the number of succesful allocations of stand alone dedicated control channels. Trigger: each time upon receipt of SEIZ FOR HO ACK. 48 A50016-D1109-G801-6-7618
  49. 49. Information Traffic Data Administration Traffic Measurement 3.2.3 Grade of service related part: successful completed handovers SUCC_COMPLETED_HO indicates the number of successfully completed intra-MSC handovers. Trigger: each time MSC receives HANDOVER COMPLETE from the BSS. SUCC_COMPL_HO_SDCCH indicates the number of successfully completed intra-MSC handovers using stand alone dedicated control channels. Trigger: each time upon receipt of HO EXECUTED. SUCC_COMPL_HO_DATA_CALLS indicates the number of successfully completed intra-MSC controlled handovers for data calls. Trigger: each time MSC-B receives HANDOVER COMPLETE from the BSS during ac-tive data call. SUCC_MSC_MSC_HO_MSCA indicates the number of successful inter-MSC handovers where the home MSC acts as MSC-A. Trigger: each time HANDOVER COMPLETE is received for handover back to MSC-A, and each time SEND END SIGNAL is received from MSC-B for handover to MSC-B. SUCC_DATA_MSC_MSC_HO_MSCA indicates the number of successful inter-MSC handovers for data calls where the home MSC acts as MSC-A. Trigger: each time SEND END SIGNAL is received from MSC-B during active data call. *SUCC_MSC_MSC_HO_MSCB indicates the number of successful inter-MSC handovers where the home MSC acts as MSC-B/MSC-B'. Trigger: each time the SEND END SIGNAL is sent to MSC-A. *SUCC_SUBSEQ_MSC_MSC_HO_MSCB indicates the number of successful subsequent inter-MSC handovers. Trigger: each time the END SIGNAL is received in response to the handover command. *SUCC_HO_SEC_MSC_MSC_HO_MSCB indicates the number of intra-MSC handovers after previous inter-MSC handover (home MSC = MSC-B). Trigger: each time the HANDOVER COMPLETE is received from the BSS for intra-MSC handover in MSC-B. 3.3 Short Message Service Counters For the measurement of the traffic related to the short message service (SMS), a num-ber of SMS counters are implemented in the MSC. The traffic types do not affect SMS traffic measurement. The SMS traffic measurement relies on counters that make up: – a load and demand related part A50016-D1109-G801-6-7618 49
  50. 50. Traffic Measurement Information Traffic Data Administration – a grade of service related part focussing: successful short message services, and unsuccessful short message services. 3.3.1 Load and demand related part SMS_INC_ATTEMPTS indicates the number of SMS messages received from the SMS gateway (home MSC = serving MSC). Trigger: each time the FORWARD SHORT MESSAGE is received from the SMS gate-way. SMS_OTG_ATTEMPTS indicates the number of SMS messages sent to the SMS gateway (home MSC=serving MSC). Trigger: each time the FORWARD SHORT MESSAGE is sent to the SMS gateway. SMS_INC_PARALLEL indicates the number of parallel SMS-MT invocations. Trigger: each time the FORWARD SHORT MESSAGE is received from the SMS gate-way. The setup of SMS-MT is a parallel transaction (e.g. to a call). SMS_OTG_PARALLEL indicates the number of parallel SMS-MO invocations. Trigger: each time the FORWARD SHORT MESSAGE is sent to the SMS gateway.The setup of SMS-MO is a parallel transaction. SMS_INC_PARALLEL_MEM_AV_INV indicates the number of parallel SMS memory available invocations. Trigger: each time READY FOR SM (GSM phase 2) is sent to the HLR. SM is a parallel transaction to a call/other transaction. SMS_SER_REQ_ATTEMPTS indicates the number of received CM SERVICE REQUEST messages for service SMS. Trigger: each time the CM SERVICE REQUEST including service type SMS is received from the MS. RECEIVE_RP DATA_ATTEMPTS indicates the number of SMS messages that are received from the MS. Trigger: each time RP DATA is received from the MS. SEND_RP DATA_ATTEMPTS indicates the number of SMS messages that are sent to the MS. Trigger: each time RP DATA is sent to the MS. 3.3.2 Grade of service related part: successful services SUCC_SMS_INC indicates the number of successfully acknowledged SMS messages that are received from the SMS gateway (home MSC = serving MSC). 50 A50016-D1109-G801-6-7618
  51. 51. Information Traffic Data Administration Traffic Measurement Trigger: each time FORWARD SHORT MESSAGE ACK is sent to the SMS gateway. SUCC_SMS_OTG indicates the number of successfully acknowledged SMS messages that are sent to the SMS gateway (home MSC = serving MSC). Trigger: each time FORWARD SHORT MESSAGE ACK is received by the SMS gate-way. SUCC_SMS_RECEIVE_RP_ACK indicates the number of mobile terminated SMS messages acknowledged by the MS. Trigger: each time RP ACK is received by the MS. SUCC_SMS_SEND_RP_ACK indicates the number of sent mobile originated SMS messages acknowledged by the MS. Trigger: each time RP ACK is sent to the MS. SUCC_MULT_SMS_OTG indicates the number of successfully acknowledged sent multiple SMS messages. Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is received as acknowledgement from the SMS gateway for multiple short message transfer. Note: first short message is acknowledged as SUCCESSFUL SHORT MESSAGE OUTGOING. SUCC_MULT_SMS_INC indicates the number of successfully acknowledged received multiple SMS messages. Trigger: each time the FORWARD SHORT MESSAGE ACKNOWLEDGE is sent as ac-knowledgement to the SMS gateway for multiple short message transfer. Note: last short message is acknowledged as SUCCESSFUL SHORT MESSAGE OUTGOING. 3.3.3 Grade of service related part: unsuccessful services UNS_SMS_INC_ABSENT_MS indicates the number of SMS messages that is received from the SMS gateway due to absent subscriber (home MSC = serving MSC). Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating ‘absent sub-scriber’ is sent to the SMS gateway. UNS_SMS_OTG_UNIDENT_MS indicates the number of SMS messages that is sent to the SMS gateway due to uniden-tified subscriber (home MSC = serving MSC). Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating ‘unidentified subscriber’ is received from the SMS gateway. UNS_SMS_OTG_NO_FACILITY indicates the number of SMS messages that is sent to the SMS gateway due to facility not supported (home MSC = serving MSC). Trigger: each time a FORWARD SHORT MESSAGE ERROR indicating ‘facility not sup- A50016-D1109-G801-6-7618 51

×