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 and Performance Data 
Counter Description 
A50016-D1112-G802-1-7618
Counter Description Information 
Traffic and Performance Data 
f Important Notice on Product Safety 
Elevated voltages are...
Information 
Traffic and Performance Data 
Counter Description 
Reason for Update 
Summary: 
A new version of this documen...
Counter Description Information 
Traffic and Performance Data 
4 A50016-D1112-G802-1-7618
Information 
Traffic and Performance Data 
Counter Description 
This document consists of a total of 241 pages. All pages ...
Counter Description Information 
Traffic and Performance Data 
3.1.6 Grade of Service Counters: Answered Calls . . . . . ....
Information 
Traffic and Performance Data 
Counter Description 
8 Traffic Measurement in AC . . . . . . . . . . . . . . . ...
Counter Description Information 
Traffic and Performance Data 
15.1.3 Signaling Link Set Measurement . . . . . . . . . . ....
Information 
Traffic and Performance Data 
Counter Description 
17.3 RANAP Destination Measurement . . . . . . . . . . . ....
Counter Description Information 
Traffic and Performance Data 
Illustrations 
Fig. 1.1 Storage of traffic data into Q3 log...
Information 
Traffic and Performance Data 
Counter Description 
Tables 
Tab. 1.1 Traffic measurement commands on the CP . ...
Counter Description Information 
Traffic and Performance Data 
12 A50016-D1112-G802-1-7618
Information 
Traffic and Performance Data 
Counter Description 
1 Introduction 
This Counter Description gives information...
Counter Description Information 
Traffic and Performance Data 
1.1 About the Use of Traffic and Performance Data 
The purp...
Information 
Traffic and Performance Data 
Counter Description 
1.3 Traffic and Performance Measurement on the CP Platform...
Counter Description Information 
Traffic and Performance Data 
The files are stored in ASN.1 format on the magnetic disk o...
Information 
Traffic and Performance Data 
Counter Description 
MML command Measurement Chapter 
Mobile-specific traffic m...
Counter Description Information 
Traffic and Performance Data 
1.4 Traffic and Performance Measurement on the MP Platform ...
Information 
Traffic and Performance Data 
Counter Description 
– If the Performance Data Collector (PDC) is not to be use...
Counter Description Information 
Traffic and Performance Data 
Q3 task Measurement object 
(current data object) 
ID 
grou...
Information 
Traffic and Performance Data 
Counter Description 
Q3 task Measurement object 
(current data object) 
CR SCTP...
Counter Description Information 
Traffic and Performance Data 
Q3 task Measurement object 
(current data object) 
CR MPLDM...
Information 
Traffic and Performance Data 
Counter Description 
Q3 task Measurement object 
(current data object) 
CR VPAT...
Counter Description Information 
Traffic and Performance Data 
2 Traffic Measurement in the MSC 
In order to measure the t...
Information 
Traffic and Performance Data 
Counter Description 
MTER: Mobile terminating traffic: traffic directed to each...
Counter Description Information 
Traffic and Performance Data 
2.1.1 Miscellaneous Counters 
NUM_RESET 
Indicates how many...
Information 
Traffic and Performance Data 
Counter Description 
Trigger: each time CHECK IMEI is sent to the EIR. 
NUM_IME...
Counter Description Information 
Traffic and Performance Data 
LNP_QUERIES_LRN 
Indicates how many LRNs the NP database in...
Information 
Traffic and Performance Data 
Counter Description 
2.1.2 Time/Duration Counters: Part 1 
TIME_CALL_SET_U_SERV...
Counter Description Information 
Traffic and Performance Data 
D_CONV_SPEECH_SERV 
Duration of conversation for speech ser...
Information 
Traffic and Performance Data 
Counter Description 
Trigger: 
– Starts each time ANSWER is received; 
– Stops ...
Counter Description Information 
Traffic and Performance Data 
DATACDA_ANA_ATTEMPTS 
Number of call attempts for data CDA ...
Information 
Traffic and Performance Data 
Counter Description 
– MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of thi...
Counter Description Information 
Traffic and Performance Data 
Trigger: each time SEND ROUTING INFO is sent to the HLR and...
Information 
Traffic and Performance Data 
Counter Description 
Trigger: each time a CCBS REQUEST activating CCBS for: 
– ...
Counter Description Information 
Traffic and Performance Data 
2.1.6 Load and Demand Counters: LTG Pooling 
The following ...
Information 
Traffic and Performance Data 
Counter Description 
2.1.7 Load and Demand Counters: Gs Interface 
TIME_COM_LUP...
Counter Description Information 
Traffic and Performance Data 
Trigger: each time PAGING RESPONSE is received from the BSC...
Information 
Traffic and Performance Data 
Counter Description 
Trigger: each time DT1:PERFORM LCS RESP is received indica...
Counter Description Information 
Traffic and Performance Data 
the position of an MS or an UE in a PLMN. It can be used, f...
Information 
Traffic and Performance Data 
Counter Description 
CA_ORMMC_OR_ORECF 
Number of optimal routing mobile-to-mob...
Counter Description Information 
Traffic and Performance Data 
SUCC_MO_LR_DEC_KEYS 
Number of successful MO-LRs by deciphe...
Information 
Traffic and Performance Data 
Counter Description 
Trigger: each time a call is released in the forward direc...
Counter Description Information 
Traffic and Performance Data 
UNS_MS_BUSY 
Number of calls terminated because the request...
Information 
Traffic and Performance Data 
Counter Description 
UNS_OVERLOAD 
Number of calls terminated due to overload p...
Counter Description Information 
Traffic and Performance Data 
Trigger: each time call setup with prompted call handling i...
Information 
Traffic and Performance Data 
Counter Description 
CCU_DATA_FR 
Indicates how many attempts for data calls ha...
Counter Description Information 
Traffic and Performance Data 
COMPL_SCI_CALL_REL 
Number of successfully performed call-r...
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Information, Traffic and Performance Data, Counter Description, Siemens
Upcoming SlideShare
Loading in …5
×

Information, Traffic and Performance Data, Counter Description, Siemens

765 views

Published on

Information, Traffic and Performance Data, Counter Description, Siemens

Published in: Mobile
  • Be the first to comment

  • Be the first to like this

Information, Traffic and Performance Data, Counter Description, Siemens

  1. 1. Information Traffic and Performance Data Counter Description A50016-D1112-G802-1-7618
  2. 2. Counter Description Information Traffic and Performance Data 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 2005. Issued by the Communications Group 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-D1112-G802-1-7618
  3. 3. Information Traffic and Performance Data Counter Description Reason for Update Summary: A new version of this document. Issue History Issue Number Date of issue Reason for Update 1 05/2005 New software release A50016-D1112-G802-1-7618 3
  4. 4. Counter Description Information Traffic and Performance Data 4 A50016-D1112-G802-1-7618
  5. 5. Information Traffic and Performance Data Counter Description This document consists of a total of 241 pages. All pages are issue 1. Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.1 About the Use of Traffic and Performance Data . . . . . . . . . . . . . . . . . . . . . 14 1.2 Types of Collected Traffic and Performance Data . . . . . . . . . . . . . . . . . . . 14 1.3 Traffic and Performance Measurement on the CP Platform . . . . . . . . . . . . 15 1.3.1 Data Collection and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1.3.2 Data Transfer and Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 1.3.3 Measurement Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 1.4 Traffic and Performance Measurement on the MP Platform. . . . . . . . . . . . 18 1.4.1 Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1.4.2 Data Storage, Transfer, and Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1.4.3 Measurement Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2 Traffic Measurement in the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.1 Basic Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.1.1 Miscellaneous Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 2.1.2 Time/Duration Counters: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1.3 Time/Duration Counters: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1.4 Load and Demand Counters: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.1.5 Load and Demand Counters: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.1.6 Load and Demand Counters: LTG Pooling. . . . . . . . . . . . . . . . . . . . . . . . . 36 2.1.7 Load and Demand Counters: Gs Interface . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.1.8 Load and Demand Counters: Location Services . . . . . . . . . . . . . . . . . . . . 38 2.1.9 Location Service Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 2.1.10 Grade of Service Counters: Unsuccessful Calls . . . . . . . . . . . . . . . . . . . . . 42 2.1.11 Grade of Service Counters: Unsuccessful LTG Pooling . . . . . . . . . . . . . . . 46 2.1.12 Grade of Service Counters: Successful Call Establishment . . . . . . . . . . . . 47 2.1.13 Grade of Service Counters: Answered Calls . . . . . . . . . . . . . . . . . . . . . . . 51 2.2 Handover Data Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2.2.1 Load and Demand Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 2.2.2 Grade of Service Counters: Handover Establishment . . . . . . . . . . . . . . . . 56 2.2.3 Grade of Service Counters: Successful Completed Handovers . . . . . . . . . 56 2.2.4 Counters for Inter System Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 2.3 Short Message Service Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . 58 2.3.1 Load and Demand Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 2.3.2 Grade of Service Counters: Successful Services . . . . . . . . . . . . . . . . . . . . 59 2.3.3 Grade of Service Counters: Unsuccessful Services . . . . . . . . . . . . . . . . . . 60 2.4 ASCI Service Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 3 UMTS Traffic Measurement in a 3G MSC . . . . . . . . . . . . . . . . . . . . . . . . . 70 3.1 Basic Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 3.1.1 Time/Duration Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 3.1.2 Load and Demand Counters: Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 3.1.3 Load and Demand Counters: Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 3.1.4 Grade of Service Counters: Unsuccessful Calls . . . . . . . . . . . . . . . . . . . . . 72 3.1.5 Grade of Service Counters: Successful Call Establishment . . . . . . . . . . . . 72 A50016-D1112-G802-1-7618 5
  6. 6. Counter Description Information Traffic and Performance Data 3.1.6 Grade of Service Counters: Answered Calls . . . . . . . . . . . . . . . . . . . . . . . . 74 3.2 Handover Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.2.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 3.2.2 Grade of Service Counters: Successful Completed Handovers . . . . . . . . . 76 3.3 Short Message Service Data Measurement . . . . . . . . . . . . . . . . . . . . . . . . 77 3.3.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 3.3.2 Grade of Service Counters: Successful Services . . . . . . . . . . . . . . . . . . . . 78 4 Traffic Measurement of Special and Supplementary Services . . . . . . . . . . 81 4.1 Supplementary Service Counters: Call Forwarding . . . . . . . . . . . . . . . . . . . 81 4.2 Supplementary Service Counters: Call Barring . . . . . . . . . . . . . . . . . . . . . . 82 4.3 Special Services Counters: Invocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 4.4 Special Services Counters: Successfully Completed Invocations . . . . . . . . 83 5 Traffic Measurement in IWE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 5.2 Grade of Service Counters: Unsuccessful Attempts . . . . . . . . . . . . . . . . . . 87 5.3 Grade of Service Counters: Forced Released Calls . . . . . . . . . . . . . . . . . . 89 5.4 Grade of Service Counters: Holding Times . . . . . . . . . . . . . . . . . . . . . . . . . 90 5.5 Grade of Service Counters: Upgrading and Downgrading. . . . . . . . . . . . . . 92 5.6 Alternate Speech Fax 3 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 6 Traffic Measurement in the VLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 6.1 Installation-related Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 6.2 Load and Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 6.3 Security Function Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 6.4 External Interworking Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 6.5 Combined Paging and Combined Location Update Counters . . . . . . . . . . 112 7 Traffic Measurement in the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 7.1 Structure- and Installation-related Counters: Part 1. . . . . . . . . . . . . . . . . . 114 7.2 Structure- and Installation-related Counters: Part 2. . . . . . . . . . . . . . . . . . 116 7.3 Structure- and Installation-related Counters: Part 3. . . . . . . . . . . . . . . . . . 123 7.4 Mobility Management/Call Handling/Authentication. . . . . . . . . . . . . . . . . . 124 7.4.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 7.4.2 Grade of Service Counters: Mobility Management . . . . . . . . . . . . . . . . . . 129 7.4.3 Grade of Service Counters: Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . 131 7.4.4 Grade of Service Counters: Subscriber Data. . . . . . . . . . . . . . . . . . . . . . . 132 7.5 Subscriber Controlled Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.5.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 7.5.2 Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 7.6 Short Message Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 7.6.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 7.6.2 Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 7.7 Overload Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 7.8 Data Service with GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 7.8.1 Load and Demand Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 7.8.2 Grade of Service Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 6 A50016-D1112-G802-1-7618
  7. 7. Information Traffic and Performance Data Counter Description 8 Traffic Measurement in AC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 9 Traffic Measurement in EIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 9.1 Structure- and Installation-related Counters . . . . . . . . . . . . . . . . . . . . . . . 146 9.2 Grade of Service Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 10 Traffic Measurement Related to Location Area . . . . . . . . . . . . . . . . . . . . 148 11 Traffic Measurement Related to Cells. . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 11.1 Load and Demand Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 11.2 Handover Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 12 Counter Calculations for Traffic Monitoring. . . . . . . . . . . . . . . . . . . . . . . . 153 13 General CN Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 13.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 13.2 Trunk Group Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 13.2.1 Index 1: Seizure and Traffic Volume Counters . . . . . . . . . . . . . . . . . . . . . 163 13.2.2 Index 2: Additional Trunk Group Counters . . . . . . . . . . . . . . . . . . . . . . . . 163 13.2.3 Index 3: Counters for Successful Calls not Reaching Destination . . . . . . 164 13.2.4 Index 4: Counters for Refused Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 13.2.5 Index 5: Counters for Refused Calls at CCS7 Trunk Groups . . . . . . . . . . 166 13.2.6 Index 6 and 7: Counters for Non-hierarchical Trunk Groups . . . . . . . . . . 166 13.2.7 Index 8: Enhanced Multilevel Precedence and Preemption Counters . . . 167 13.3 Destination Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 13.4 CP Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 13.5 LTG Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 13.5.1 LTG Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 13.5.2 Code Receiver Group Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 13.5.3 Group Processor Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 13.6 GP Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 13.7 DLU Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 13.8 Announcement Group Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . 177 13.9 GSM MGW Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 14 CSC-specific Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 14.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 14.1.1 Data Quality and Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 14.1.2 Plausibility Checking of Traffic Measurement Results . . . . . . . . . . . . . . . 183 14.2 PBX Traffic Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 14.2.1 Service-related Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 14.2.2 Service-independent Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 15 SS7-specific Traffic Measurement (SSNC). . . . . . . . . . . . . . . . . . . . . . . . 186 15.1 MTP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 15.1.1 Net Element Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 15.1.2 Signaling Point Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 15.1.2.1 Signaling Point Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 15.1.2.2 Obligatory Signaling Point Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 15.1.2.3 Network MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 15.1.2.4 Signaling Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 A50016-D1112-G802-1-7618 7
  8. 8. Counter Description Information Traffic and Performance Data 15.1.3 Signaling Link Set Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 15.1.3.1 Link Set Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 15.1.3.2 Link Set Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 15.1.4 Destination Point Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 15.1.5 Signaling Link Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 15.1.5.1 Obligatory Link Duration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 15.1.5.2 Link Duration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 15.1.5.3 Obligatory Link Utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 15.1.5.4 Link Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 15.1.5.5 Link Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 15.1.5.6 High-Speed Link Utilization Measurement . . . . . . . . . . . . . . . . . . . . . . . . . 194 15.1.5.7 Obligatory High-Speed Link Utilization Measurement . . . . . . . . . . . . . . . . 194 15.1.6 Signaling Linkset IP Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 15.1.7 SCTP Association Utilization and Duration Measurement . . . . . . . . . . . . . 195 15.1.7.1 Obligatory Association Utilization Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 15.1.7.2 All Association Utilization Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 15.1.7.3 All Association Duration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 15.2 SCCP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 15.2.1 SCCP Measurements with Specific Criteria. . . . . . . . . . . . . . . . . . . . . . . . 198 15.2.1.1 SCCP Error Performance Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . 198 15.2.1.2 SCCP Utilization Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 15.2.1.3 SCCP Quality of Service Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 15.2.2 SCCP Screening . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 15.2.2.1 SCCP Screening Success Measurement . . . . . . . . . . . . . . . . . . . . . . . . . 203 15.2.2.2 SCCP Screening Failure Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . 204 15.2.3 Signaling Link Set IP Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 15.3 TCAP Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 16 MP Load Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 16.1 VCPU Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 16.2 Message Handler Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 17 Traffic Measurement Related to Iu Interface . . . . . . . . . . . . . . . . . . . . . . . 212 17.1 CIC Group Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 17.1.1 AAL2 Overrun Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 17.1.2 AMR Underrun Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17.1.3 SSCS Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17.1.4 Data Underrun Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17.1.5 Iu User Plane Protocol Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 17.1.6 Rate Control Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 17.1.7 AMR Mode Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 17.2 AAL2 Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 17.2.1 AAL2 NNI Access Control Measurement. . . . . . . . . . . . . . . . . . . . . . . . . . 215 17.2.2 AAL2 NNI Access Protocol Measurement . . . . . . . . . . . . . . . . . . . . . . . . . 217 17.2.3 AAL2 Carrier Access Control Measurement . . . . . . . . . . . . . . . . . . . . . . . 219 17.2.4 CPS Protocol Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 17.2.5 PDU14 Protocol Error Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 17.2.6 AAL2 Destination Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 8 A50016-D1112-G802-1-7618
  9. 9. Information Traffic and Performance Data Counter Description 17.3 RANAP Destination Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 17.3.1 RANAP Protocol Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 17.3.2 CAM Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 17.4 ATM Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 17.4.1 ATM Traffic Load Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 17.4.2 Cell Level Protocol Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 17.4.3 Virtual Path and Virtual Channel Measurements . . . . . . . . . . . . . . . . . . . 224 18 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 19 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 A50016-D1112-G802-1-7618 9
  10. 10. Counter Description Information Traffic and Performance Data Illustrations Fig. 1.1 Storage of traffic data into Q3 log file or SAMAR on the MP . . . . . . . . . 19 Fig. 2.1 Traffic types in scope of the observed MSC . . . . . . . . . . . . . . . . . . . . . . 25 Fig. 13.1 RSU overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 10 A50016-D1112-G802-1-7618
  11. 11. Information Traffic and Performance Data Counter Description Tables Tab. 1.1 Traffic measurement commands on the CP . . . . . . . . . . . . . . . . . . . . . 17 Tab. 1.2 Traffic measurement tasks and objects on the MP . . . . . . . . . . . . . . . . 20 Tab. 12.1 Options for counter-based calculations . . . . . . . . . . . . . . . . . . . . . . . . 154 Tab. 12.2 Calculations with OMC output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Tab. 14.1 Data quality and availability of measurement data . . . . . . . . . . . . . . . 182 A50016-D1112-G802-1-7618 11
  12. 12. Counter Description Information Traffic and Performance Data 12 A50016-D1112-G802-1-7618
  13. 13. Information Traffic and Performance Data Counter Description 1 Introduction This Counter Description gives information about the traffic and performance counter data that is collected within the circuit-switched domain of the PLMN core network. Fol-lowing a general introduction about traffic and performance data in the core network, all traffic counters that are implemented within the different parts of the system are listed and described. The Counter Description is intended for use by network operators, developers, and sys-tem operators who need an overview or interpretation of the various counters which are implemented in the circuit-switched domain of the core network. Furthermore, it ad-dresses users of the Element Management System which makes measurement results available. i For dimensioning the whole PLMN, traffic measurement data related to manufacturer-specific subunits and auxiliary units (e.g., use of conference modules) must also be reg-istered. This manual does not include information about this data. A50016-D1112-G802-1-7618 13
  14. 14. Counter Description Information Traffic and Performance Data 1.1 About the Use of Traffic and Performance Data The purpose of traffic and performance data collection is to serve the process of network planning and observation. Traffic data collection and evaluation is of decisive impor-tance for telecommunications carriers regarding network planning and traffic forecasts and network traffic management: · Network planning and traffic forecasts Analysis of traffic measurement data is the basis for planning new networks and ex-panding the existing network to meet future demands. Long-term traffic measure-ments (e.g., over several months) help to identify trends in traffic and make traffic forecasts. Measurement data also reveals extreme load situations and unused re-sources. This information can be taken into consideration when planning new net-work components. · Network traffic management Traffic measurement data provides an accurate overview of the traffic situation in the network and detects overload situations, unused network resources, and faults in the network. The network operator can respond with appropriate network manage-ment measures and make full use of the network resources. The core network does not require any special equipment for traffic data acquisition be-cause a wide range of intra-system functions is available. These functions collect and process traffic data in every functional system element and for every main unit or logical configuration (e.g., entire MSC, trunk groups, location area or cells). All kinds of traffic data are collected from the traffic flows between and within the differ-ent network elements and registered in measurement counters. The counters are con-tinuously updated by the call-processing software. However, traffic data is stored only if a measurement job has been set up for the required data. The results are stored on the magnetic disk of the coordination processor (CP) or are sent to a network element man-ager, such as Switch Commander. i This manual does not make a clear distinction between the terms “traffic” and “perfor-mance” because this is only possible with respect to a special counter. The term “traffic” covers a larger concept, and is therefore often used to refer to traffic and performance data. 1.2 Types of Collected Traffic and Performance Data Based on counter measurements, the following types of traffic and performance data are provided on the CP and MP platforms: · Traffic measurement data Traffic measurements are recorded by means of counters which are implemented in the system. Traffic data measurements provide the network operator with informa-tion related to the traffic and performance of network elements. This information in-cludes data about the system load, the processor load, and the protocol load. · Traffic monitoring data Traffic monitoring refers to objects with definable thresholds. By continuously com-paring counts of monitored variables with defined thresholds, the system generates data and messages which can be called up directly at the operating system. At the end of each measurement interval, the data is backed up automatically in monitoring files on the CP magnetic disk, from where it can be output to a printer or operating system. Monitoring functions have been created for selected monitoring objects to detect such bottlenecks and overload situations. 14 A50016-D1112-G802-1-7618
  15. 15. Information Traffic and Performance Data Counter Description 1.3 Traffic and Performance Measurement on the CP Platform Traffic measurement on the CP platform supplies and outputs counters registering: – Occurrence and duration of specific events during call processing – Total load and the call processing load of the NE – Grade of service – Usage of features and services – Usage and states of equipment (e.g.: LTG, DLU) The counters are implemented on the CP platform according to the recommendations of the ITU-T and the 3GPP standard. 1.3.1 Data Collection and Storage Traffic measurement data on the CP platform is taken continuously but is processed only after the operator has entered an MML command. MML commands are used to de-fine on which network element or logical component the measurement has to be taken, the time scheduler for the measurement, and the file type of the measurement file (see chapter 1.3.2 "Data Transfer and Retrieval"). All measured values are assigned two areas of traffic data memory: a passive part and an active part. The counters are updated in the active part under the control of call-pro-cessing software. The passive traffic data memory is read by the relevant measurement process and edited for output. The two parts are switched over every 15 minutes: The active traffic data memory becomes passive and vice versa. The passive traffic data memory is only read if a measurement job is present in the system. After each read op-eration from the passive traffic data memory, the counters are initialized. Implementation of the individual measurements, as well as the collection and output of the measurement data, is controlled by separate traffic measurement processes. When the recording jobs are entered, an operational process (traffic measurement process) is triggered in the CP. These processes collect the measured values and output them on the administered output medium. One measurement process is used to control each re-cording command for general measurements, except for the recording jobs REC LTG and REC GP, which are implemented in a joint measurement process. For mobile spe-cific maeasurements, there is one process for all commands. The CP main memory reads the data of the respective counters and outputs it to spec-ified devices. This takes place every fifteen minutes during the active traffic measure-ment intervals, irrespective of the file type. Three methods are used for collecting and storing traffic data in output files: · Time-controlled measurement with output to individual files. All traffic measurement data that is generated during the defined time is recorded in this file. One file is created per traffic measurement job. · Continuous measurement with output to daily files. Up to seven files, one for each day of the week, can exist simultaneously for each job. If the operator does not delete the file after it has been evaluated, it is overwritten on the same day of the following week. · Continuous measurement job with output to cyclic files. Data related to each measurement period of 15 minutes is collected and the results are written into a separate cyclic file for each started measurement type every 15 minutes. Such files can be assigned to any traffic measurement job listed in Tab. 1.1. A50016-D1112-G802-1-7618 15
  16. 16. Counter Description Information Traffic and Performance Data The files are stored in ASN.1 format on the magnetic disk of the CP. The contents of the disk file can be displayed at the OMC using the GET TRAFILE command. 1.3.2 Data Transfer and Retrieval At the end of the measurement job or period, the measurement data can be transferred from the CP’s magnetic disk to a magnetic optical disk or a tape. Alternatively, the col-lected data can be transferred via FTAM to an operating system, e.g., Switch Com-mander equipped with the Performance Data Collector (PDC) application. The minimum upload frequency for cyclic files on PDC amounts to 15 minutes. Data is converted to ASCII format on the PDC and made available for postprocessing. Siemens offers the SPOTS traffic analysis system, which provides a series of reports that are used to ana-lyze the measurement data and achieve more effective network operation and planning. 1.3.3 Measurement Commands Various measurement commands have been designed to specify the groups of mea-surement types and counters to be observed. These commands are used to set up time-dependent traffic data measurements and restrict the amount of data to be measured, which subsequently reduces performance requirements. Tab. 1.1 gives an overview of the traffic measurement commands integrated in the sys-tem and the references to the chapters in this manual that deal with the respective mea-surement command and describe the provided counters. The measurements are classified as follows: · Mobile-specific traffic measurements These measurements are performed for mobile-specific units, such as MSC, VLR, HLR, AC, IWE, EIR or mobile-specific functions or procedures, such as location up-date, authentication, paging, roaming, and handover. · General traffic measurements General traffic measurements register data related to user traffic or signaling traffic in network nodes of the PLMN and of the PSTN/ISDN. In this context, the MSC han-dles user traffic and, consequently, these traffic measurements are relevant in the PLMN. Examples of such events are the start of call setup in a GMSC or a connec-tion with announcement groups. · CSC-specific measurements CSC-specific measurements are performed on a combined switching center (CSC), only. They refer to the fixed subscribers and PBX connected to the CSC. 16 A50016-D1112-G802-1-7618
  17. 17. Information Traffic and Performance Data Counter Description MML command Measurement Chapter Mobile-specific traffic measurement and monitoring REC MSC MSC traffic measurement 2 and 3 REC SSERV Traffic measurement for Supplementary Services (SS) 4 REC IWE Traffic measurement in IWE 5 REC VLR VLR traffic measurement 6 REC HLR HLR traffic measurement 7 REC AC AC traffic measurement 8 REC EIR EIR traffic measurement 9 REC LOCAREA Location-area-related traffic measurement 10 REC INTCELL Cell-related traffic measurement 11 ENTR MUSMON Mobile-specific traffic monitoring 12 General traffic measurements REC TGRP Trunk group traffic measurement 13.2 REC DEST Destination traffic measurement 13.3 REC CP CP traffic measurement 13.4 REC LTG LTG traffic measurement 13.5 REC GP GP traffic measurement 13.6 REC DLU DLU traffic measurement 13.7 REC ANGRP Announcement group traffic measurement 13.8 REC RSU GSM MGW traffic measurements 13.9 REC SCTC SCCP/TCAP traffic measurement 15 CSC-specific traffic measurements REC PBX PBX traffic measurement 14.2 Tab. 1.1 Traffic measurement commands on the CP A50016-D1112-G802-1-7618 17
  18. 18. Counter Description Information Traffic and Performance Data 1.4 Traffic and Performance Measurement on the MP Platform Traffic measurement on the MP platform supplies and outputs counters that register: – Quality of Service, e.g., delays during call set-up, packet throughput, etc. – Traffic levels within the network, including the level of both user traffic and signaling traffic – Verification of the network configuration and traffic models – Resource access and availability, e.g., begin and end times of service unavailability – Grade of Service, i.e., measurement of successful and unsuccessful events includ-ing failure causes The counters are implemented on the MP platform according to the recommendations of the ITU-T and the 3GPP standard. 1.4.1 Data Collection On the MP platform, counters are modeled as attributes of current data subclasses. A current data subclass consists of up to 26 counters and refers to specified measurement objects (also designated as measurement type or current data object). Traffic measurement data on the MP platform is processed after the operator has en-tered the respective task to specify one or several measurement objects, define a scheduler and, in case of storage such as a Q3 log file (see chapter 1.4.2), create a Q3 output file. The respective counter values are collected in measurement time periods of 5, 15 or 30 minutes for general measurements and 15 minutes for mobile-specific measurements and are stored on the hard disk of the MP. The measurement results are emitted as re-ports which contain the value of all counters (attributes) being observed during report-ing. Traffic monitoring on the MP is performed with First and Interval measurements. The same measurement objects and counters are used for traffic monitoring and traffic mea-surement. The collected data is, however, handled in a different manner. Every time any monitored event reaches the threshold value “1”, an alarm notification is generated. In other words, when the monitored event occurs for the first time during the measurement period, an alarm notification is produced and written into the alarm report. This notifica-tion indicates severity, time and further attributes, which enables the alarm to be ana-lyzed. At the end of a monitoring period, an interval report is emitted. 1.4.2 Data Storage, Transfer, and Retrieval Measurement reports and alarm reports are output on the hard disks of the MP and stored using one of two methods: – SAM file array to be transferred via the FTP interface – Q3 log files to be transferred via the Q3 interface The storage method used depends on how the collected data is further processed: – If the Performance Data Collector (PDC) is to be used for data transfer and conver-sion into ASCII, an SAM file array has be used for data storage on the MP. For this purpose, the pmStorageOnSamar feature has to be activated. This feature enables performance gains by saving ASN.1 coded traffic data on the MP hard disk and transferring it via FTP to a Network Manager, i.e., to Switch Commander equipped with PDC. The SAM file array is created during system installation. The minimum up-load frequency on PDC amounts to 15 minutes. 18 A50016-D1112-G802-1-7618
  19. 19. Information Traffic and Performance Data Counter Description – If the Performance Data Collector (PDC) is not to be used or data transfer and con-version Q3 log files can be used for data storage. In this case, the further processing of data depends on project-specific solutions. Fig. 1.1 gives an overview of the methods to store and transfer traffic data from the MP’s hard disk to Switch Commander with or without using the pmStorageOnSamar feature. Collection Storage File transfer Retrieval SAMAR Scan Reports QoS Alarms Common Q3 Log File Scan Reports QoS Alarms Specific Q3 Log File Scan Reports QoS Alarms Raw Data FTP FTP Q3 Q3 Q3 Q3 legend: with pmStorageOnSamar feature Fig. 1.1 Storage of traffic data into Q3 log file or SAMAR on the MP 1.4.3 Measurement Tasks Performance Data Collector Project-specific solutions Q3 Presentation Service On the MP platform, measurements are administered by means of Q3 tasks. For every measurement job, the measured object has to be created and the measurement time has to be defined in a separate measurement scheduler. Various measurement tasks have been designed to specify the groups of traffic mea-surement and monitoring objects containing the counters to be observed. Additional tasks are used to set up the scheduler and – in the case of Q3 logfile storage – define the output file. Tab. 1.2 gives an overview of all the traffic measurement commands integrated in the system and refers to the chapters of this manual dealing with this measurement and de-scribing the provided counters. The measurements are classified as follows: · SS7 traffic measurement and monitoring (SSNC) Signaling data traffic applies to SS7 routes to destination point codes, the load on signaling links, the transfer of message signaling units, and the availability of routing areas. The traffic measurements for this signaling data is relevant for both the PLMN and the PSTN/ISDN. · MP load measurement MP load measurements are general measurements and register data on user traffic or signaling traffic in network nodes of the PLMN and of the PSTN/ISDN. · Measurement related to the Iu interface Measurements of the Iu interface are performed for a 2G/3G MSC and 3G MSC. Data concerning the connection to the RNC are registered. A50016-D1112-G802-1-7618 19
  20. 20. Counter Description Information Traffic and Performance Data Q3 task Measurement object (current data object) ID group Chapter SS7 traffic measurement (SSNC) CR SIGNEME Net element measurement (switchingElementMeasurement) 202 15.1.1 CR SIGPTME Signaling point utilization measurement (allSignalingPointUtilisationData) 204 15.1.2.1 Obligatory signaling point utilization measurement (oblSignalingPointUtilisationData) 206 15.1.2.2 Network MSU measurement (perNetCounterMSU) 208 15.1.2.3 Signaling point measurement (signalingPointData) 210 15.1.2.4 CR SIGLSME Link set duration measurement (signalingLinkSetDurationData) 212 15.1.3.1 Link set utilization measurement (signalingLinkSetUtilisationData) 234 15.1.3.2 CR SIGDPME Destination point measurement (routeSetInformationData) 214 15.1.4 CR SIGLME Obligatory link duration measurement (oblSignalingLinkDurationData) 216 15.1.5.1 Link duration measurement (all30MinSignalingLinkDurationData) 218 15.1.5.2 Obligatory link utilization measurement (oblSignalingLinkUtilisationData) 220 15.1.5.3 Link utilization measurement (allSignalingLinkUtilisationData) 222 15.1.5.4 Link congestion measurement (signalingLinkCongestionData) 224 15.1.5.5 Obligatory HSLink utilization measurement (saalOblSignallingLinkUtilisationData) 228 15.1.5.6 HSLink utilization measurement (saalAllSignallingLinkUtilisationData) 226 15.1.5.7 CRSIGLSETIPME Signaling linkset IP measurement (ipLinkSetInformationData) 15.1.6 Tab. 1.2 Traffic measurement tasks and objects on the MP 20 A50016-D1112-G802-1-7618
  21. 21. Information Traffic and Performance Data Counter Description Q3 task Measurement object (current data object) CR SCTPASSOC-ME SCTP obligatory association utilization mea-surement (oblAssociationUtilizationData) Chapter 15.1.7.1 SCTP association utilization measurement (allAssociationUtilizationData) 15.1.7.2 SCTP association duration measurement (allAssociationDurationData) 15.1.7.3 CR SPME SCCP error performance, network-indepen-dent (sccpErrorPerformance) ID group 310 15.2.1.1 SCCP utilization, network-independent (sccpUtilisation) 330 15.2.1.2 SCCP quality of service, network-independent (sccpQualityOfService) 320 15.2.1.3 CR SPMEN SCCP error performance per network (sccpErrorPerformance) 310 15.2.1.1 SCCP utilization per network (sccpUtilization) 330 15.2.1.2 SCCP quality of service per network (sccpQualityOfService) 320 15.2.1.3 CR SPMESSN SCCP error performance per SSN (sccpErrorPerformance) 340 15.2.1.1 CR SPSME SCCP Screening traffic measurement (sccpScreeningTrafficMeas) 370 15.2.2.1 SCCP Screening failures (sccpScreeeningFailures) 360 15.2.2.2 SS7 traffic monitoring (SSNC) CR SIGFAIME Signaling point measurement (signalingPointData) 15.1.2.4 Link congestion measurement (signalingLinkCongestionData) 15.1.5.5 CR SPMEFAI SCCP error performance per SSN (sccpErrorPerformance) 15.2.1.1 SCCP screening failures (sccpScreeningFailures)) 15.2.2.2 CR SPMENFAI SCCP error performance per network (sccpErrorPerformance) 15.2.1.1 MP load measurement Tab. 1.2 Traffic measurement tasks and objects on the MP A50016-D1112-G802-1-7618 21
  22. 22. Counter Description Information Traffic and Performance Data Q3 task Measurement object (current data object) CR MPLDME Measurement object for VCPU (vcpuCurrentData) Chapter 16.1 Measurement object for MH (mhCurrentData) 16.2 Traffic measurement related to the Iu interface CR CICGRPME AAL2 overrun error measurement (aal2OverrunCurrentData) ID group 604 17.1.1 AMR underrun error measurement (amrUnderrunCurrentData) 605 17.1.2 SSCS error measurement (sscsErrorCurrentData) 611 17.1.3 Data underrun error measurement (dataUnderrunErrorCurrentData) 608 17.1.4 Iu user plane protocol error measurement (iuUPPProtocolErrorCurrentData) 609 17.1.5 Rate control measurement (rateControlCurrentData) 17.1.6 AMR mode measurement (amrModeCurrentData) 17.1.7 CR AAL2NNIAME AAL2 NNI access control measurement (aal2ControlCurrentData) 603 17.2.1 AAL2 NNI access protocol measurement (aal2ProtocolCurrentData) 612 17.2.2 AAL2 carrier access control measurement (aal2CACurrentData) 17.2.3 CR AAL2VCCME CPS protocol error measurement (cpsProtocolErrorCurrentData) 607 17.2.4 PDU protocol error measurement (PDU14ProtocolErrrorCurrentData) 17.2.5 CR DAAL2SEPME AAL2 destination measurement (aal2DestCurrentData) 17.2.5 CR RANAPDME RANAP destination measurements (ranapProtocolCurrentData) 610 17.3.1 CAM control measurements (camControlCurrentData) 606 17.3.2 CR TCSUBLME ATM Traffic load measurements (atmTrafficLoadCurrentDataExt) 701 17.4.1 Cell level protocol measurement (cellLevelProtocolCurrentData) 601 17.4.2 Tab. 1.2 Traffic measurement tasks and objects on the MP 22 A50016-D1112-G802-1-7618
  23. 23. Information Traffic and Performance Data Counter Description Q3 task Measurement object (current data object) CR VPATHME ATM traffic load measurements (atmTrafficLoadCurrentDataExt) ID group Chapter 701 17.4.1 Virtual path and virtual channel performance measurements (vpVcPMCurrentData) 602 17.4.3 CR VCHANME ATM traffic load measurements (atmTrafficLoadCurrentDataExt) 701 17.4.1 Virtual path and virtual channel performance measurements (vpVcPMCurrentData) 602 17.4.3 Tab. 1.2 Traffic measurement tasks and objects on the MP A50016-D1112-G802-1-7618 23
  24. 24. Counter Description Information Traffic and Performance Data 2 Traffic Measurement in the MSC In order to measure the traffic in the entire MSC, data can be recorded by counters con-cerning the traffic load, the grade of service, and features. This data is collected during the main tasks controlled by the MSC, such as call setup for speech and data, handover, and short message service. A traffic measurement job in the MSC is started by entering the REC MSC command. In this command the following groups of counters can be specified in order to reduce the amount of data collected: · Basic counters (see chapter 2.1) · Handover counters (see chapter 2.2) · Short message service (SMS) counters (see chapter 2.3) · Advanced speech call items (ASCI) counters (see chapter 2.4) 2.1 Basic Data Measurement Basic counters collect the call setup data for both speech and data calls. This data ap-plies to standard and mobile-specific functions. The measurement job is started by se-lecting the data type GENERAL DATA in the REC MSC command. This chapter lists all mobile-specific counters that are registered. Because there is a large number of different counters, they have been grouped on the following pages ac-cording to their distinctive purposes: · Miscellaneous (see chapter 2.1.1) · Time/duration (see chapters 2.1.2 and 2.1.3) · Load and demand (see chapters 2.1.4 and 2.1.5) focussing furthermore on: LTG pooling (see chapter 2.1.6), Gs interface (see chapter 2.1.7), location services (see chapter 2.1.8) · Location service counters (see chapter 2.1.9) · Grade of service, focussing on: unsuccessful calls (see chapter 2.1.10), unsuccess-ful LTG pooling (see chapter 2.1.11), successful call establishments (see chapter 2.1.12), answered calls (see chapter 2.1.13) Traffic types Most basic counters can be differentiated by traffic type. The different types occur within the observed MSC and provide information about the origin and destination of the call. Because different traffic types cause different call handling, there are variations with re-spect to the trigger points for special counters. These differences are considered in the counter description. The observed MSC detects whether a call originated in its own area or was transmitted by another exchange. The following traffic types exist: MORTR: Mobile originating traffic: traffic initiated by a mobile station in the area of the observed MSC, irrespective of where the destination is MICTR: Mobile incoming traffic: 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: 24 A50016-D1112-G802-1-7618
  25. 25. Information Traffic and Performance Data Counter Description MTER: Mobile terminating traffic: traffic directed to each mobile station in the area of the observed MSC MOUT_PLMN: Mobile originating traffic outgoing to a mobile station of the home PLMN, wherever the subscriber is roaming MOUT_NOT_PLMN: Mobile originating traffic outgoing to the PSTN or another PLMN MTRAN: Mobile transit traffic: traffic that has neither been initiated in nor will terminate at the observed MSC Fig. 2.1 shows the different traffic types within the scope of the observed MSC. observed MSC MICTR MOUT NOT PLMN MTER MTER MORTR MORTR PLMN MICTR MSC MTRAN MOUT PLMN MICTR MOUT NOT PLMN MOUT PLMN Access Network Access Network PSTN PLMN MORTR: Mobile originating traffic MICTR: Mobile incoming traffic MTER: Mobile terminating traffic MTRAN: Mobile transit traffic MOUT_PLMN: Mobile (originating) outgoing traffic to home PLMN MOUT_NOT_PLMN: Mobile (originating) outgoing traffic to PSTN or Fig. 2.1 Traffic types in scope of the observed MSC MICTR MTRAN BSS BSS another PLMN i 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-D1112-G802-1-7618 25
  26. 26. Counter Description Information Traffic and Performance Data 2.1.1 Miscellaneous Counters NUM_RESET Indicates how many RESET messages have been received. Trigger: each time RESET is received from the BSC. NUM_RESET_CIRCUIT Indicates how many RESET CIRCUIT messages have been received. Trigger: each time RESET CIRCUIT is received from the BSC. NUM_SSP_BSSAP Indicates how many SUBSYSTEM PROHIBITED messages for subsystem BSSAP have been received. Trigger: each time SUBSYSTEM PROHIBITED is received from the BSC. NUM_SIGN_POINT_PROHIB Indicates how many SIGNALING POINT PROHIBITED messages have been received. Trigger: each time SIGNALING POINT PROHIBITED is received from the BSC. NUM_CALLS_REL_BS Number of calls released because one of the messages referred to in “trigger” has been 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 have been received. Trigger: each time OVERLOAD is received from the BSC. NUM_SEND_OVERLOAD Indicates how many overload events have occurred. Trigger: each time the MSC sends OVERLOAD messages to all connected BSCs. NUM_RECEIVED_GCP Indicates how many general congestion primitives (GCP) have been received. Trigger: each time a GCP is received from the CCS7 link system or message buffer. NUM_RECEIVED_CIP Indicates how many congestion indication primitives (CIP) have been received. Trigger: each time a CIP is received from the CCS7 link. NUM_RECEIVED_CLASSM_UPD Indicates how many CLASSMARK UPDATE messages have been received. Trigger: each time CLASSMARK UPDATE is received. NUM_TOTAL_START_IMEI_CHECK Indicates how often IMEI check procedures have been started. 26 A50016-D1112-G802-1-7618
  27. 27. Information Traffic and Performance Data Counter Description Trigger: each time CHECK IMEI is sent to the EIR. NUM_IMEI_CHECK_WHITE Indicates how often the IMEI check procedure detects white-listed equipment. Trigger: each time the EIR sends a white list after having performed an IMEI check. NUM_IMEI_CHECK_GREY Indicates how often the IMEI check procedure detects grey-listed equipment. Trigger: each time the EIR sends a grey list after having performed an IMEI check. NUM_IMEI_CHECK_BLACK Indicates how often the IMEI check procedure detects black-listed equipment. Trigger: each time the EIR sends a black list after having performed an IMEI check. NUM_IMEI_CHECK_UNKNOWN Indicates how often the IMEI check procedure detects unknown equipment. Trigger: each time the EIR sends IMEI unknown after having performed an IMEI check. NUM_IMEI_CHECK_LUP Indicates how often IMEI checks have been started due to location update. Trigger: each time CHECK IMEI is sent due to a location update because of an IMSI at-tach or a normal location update. NUM_IMEI_CHECK_PER_LUP Indicates how often IMEI checks have been started by a periodic location update. Trigger: each time CHECK IMEI is sent due to a location update because of a periodic location update. NUM_TONES_DTMF Indicates how many DTMF tones have been sent by the MS. Trigger: each time START DTMF is received. NUM_NO_SPCH_BSSAP_LTG Indicates how often no free speech channel has been found in the BSSAP LTG. Trigger: each time an attempt to seize a BSSAP-LTG fails (internal condition; reason: no free speech channel available in this LTG). NUM_ATT_SCP_DIALOGS_LNP Indicates how many queries have been initiated to the number portability (NP) database in the service control point (SCP). Trigger: each time the MSC sends an IDP message to the SCP. NUM_SUCC_SCP_DIALOGS_LNP Indicates how often the NP database has been successfully queried. Trigger: each time the SCP sends CONNECT in response to an NP database query con-taining either a location routing number (LRN) or the same number as the one being sent. A50016-D1112-G802-1-7618 27
  28. 28. Counter Description Information Traffic and Performance Data LNP_QUERIES_LRN Indicates how many LRNs the NP database in the SCP has returned after being queried; i.e., the investigated subscriber number is a ported number. Trigger: each time the NP returns a local roaming number. LNP_MISROUTED_CALL Indicates how many calls were released because they were misrouted to a ported num-ber; applies to PCS1900 networks only. Trigger: each time a release message of this type is received. LNP_UNALLOC_NUM_MICTR Indicates how often the HLR has returned “unknown subscriber” after being 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., no code point for the LRN concerned exists. Trigger: each time 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 to send a short message has successfully invoked an IN function. 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 function. Trigger: each time INTR USSD to start an IN function is received. NUM_SWITCH_LTGPOOL Indicates how often an initial LTG has switched over to another one to continue call es-tablishment. Trigger: each time NRELAY contains an LTG other than the one involved in this service request. CA_VGCS_VBS_EMLPP Indicates how often group calls have been set up with a given priority level. A counter is provided for each level; i.e., from level A (high) up to level 4 (low). Trigger: each time the GCR sends VGCS ATR RESPONSE containing the attributes and the eMLLP priority. 28 A50016-D1112-G802-1-7618
  29. 29. Information Traffic and Performance Data Counter Description 2.1.2 Time/Duration Counters: Part 1 TIME_CALL_SET_U_SERV Average time to provide the “call setup” service. Trigger: – Starts each time SET UP is received (MOC) or sent (MTC); – Stops each time ASSIGNMENT COMPLETE is received. NUM_CALL_SET_UP_CONTRIB Number of calls contributing to “call setup time”. Trigger: each time ASSIGNMENT COMPLETE is received (for the calculation of the av-erage setup time). TIME_LUP_SERV Accumulated time to provide a service location update. Trigger: – Starts each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received; – Stops each time LOCATION UPDATE ACCEPT is sent. NUM_LUP_CONTRIB Number of location updates contributing to “location update service time”. Trigger: each time a location update contributing to TIME LUP SERV is received (for the calculation of the mean holding time). TRAFF_VOL_SUCC_PAGING Duration of the paging procedure (unit 50ms). Only successful paging procedures are included, but no timeout cases. Trigger: – Starts each time PAGING is sent; – Stops each time PAGING RESPONSE is received. 2.1.3 Time/Duration Counters: Part 2 TRAFFIC_VOLUME Sum of all holding times. Trigger: start and stop depend on the message of the respective traffic type. – MORTR: starts each time CM SERVICE REQUEST is received; stops each time RELEASE COMPLETE is received. – MICTR: starts each time IAM is received; stops each time RELEASE COMPLETE is received. – MTER: starts each time PAGING is sent; stops each time RELEASE COMPLETE is received, or at paging timeout. – MOUT_NOT_PLMN / MOUT_PLMN: starts with proper result of digit analysis after interrogation; stops when RELEASE COMPLETE is sent or received, or with an un-successful call attempt before IAM is sent. – MTRAN: starts with proper result of the digit analysis; stops when RELEASE COM-PLETE is received. A50016-D1112-G802-1-7618 29
  30. 30. Counter Description Information Traffic and Performance Data D_CONV_SPEECH_SERV Duration of conversation for speech services. Trigger: start and stop depend on the message of the respective traffic type: – MTER: starts each time CONNECT is received; stops each time a call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops each time a call is released. D_CONVERSATION Duration of conversation for MTRAN. Trigger: – Starts each time ANSWER is received; – Stops each time a call is released. D_CONV_DATACDA_ANA Duration of conversation for data CDA (circuit duplex asynchronous) analog services. D_CONV_DATACDS_ANA Duration of conversation for data CDS (circuit duplex synchronous) analog services. Trigger: start and stop depend on the message of the respective traffic type: – MTER: starts each time CONNECT is received; stops each time the call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops each time the call is released. D_CONV_DATACDA_DIG Duration of conversation for data CDA digital services. Trigger: start and stop depend on the message of the respective traffic type: – MTER: starts each time CONNECT is received; stops each time a call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops each time a call is released. D_CONV_ALTFAXSP Duration of conversation for alternate speech/facsimile services. Trigger: start and stop depend on the message of the respective traffic type: – MTER: starts each time CONNECT is received; stops each time a call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; starts each time ANSWER is received; D_CONV_FAX3 Duration of conversation for the automatic facsimile group 3 service. Trigger: start and stop depend on the message of the respective traffic type: – MTER: starts each time CONNECT is received; stops each time a call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops each time a call is released. D_CONV_DED_PAD Duration of conversation for dedicated PAD (packet assembler/disassembler) access for MOUT_NOT_PLMN. 30 A50016-D1112-G802-1-7618
  31. 31. Information Traffic and Performance Data Counter Description Trigger: – Starts each time ANSWER is received; – Stops each time a call is released. D_CONV_DATACDS_DIG Duration of conversation for data CDS digital services. Trigger: start and stop depend on the message of the respective traffic type: – MTER: starts each time CONNECT is received; stops each time the call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops each time the call is released. D_ALT_SPEECH_DATA 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 the call is released. – MOUT_PLMN, MOUT_NOT_PLMN: starts each time ANSWER is received; stops each time the call is released. 2.1.4 Load and Demand Counters: Part 1 CALL_ATTEMPTS Indicates how many call attempts have taken place, independently of the received BS or TS (except for MOUT_PLMN, MOUT_NOT_PLMN). Trigger: each time the respective message is involved: – MORTR: on receipt of each CM SERVICE REQUEST with SERVICE TYPE = mobile originating call or establishment of all emergency call attempts. Short message ser-vice and SS activation are not included. – MICTR: each time IAM is received (all call attempts). – MTER: each time PAGING is sent. The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent (all call attempts). The following cases are exceptions: busy MS, invoca-tion of service call wait and overload related to the A interface. – MOUT_PLMN, MOUT_NOT_PLMN: Receipt of SET UP and digit analysis results in this traffic type (speech call attempts only). – MTRAN: each time IAM is received and digit analysis results in outgoing traffic (all call attempts). CALL_ATT_MS_OWN_MSC_NO Number of incoming call attempts leading MS in own MSC to MTER without performing interrogation for MICTR. Trigger: each time IAM (includes MSRN) is received and call leads directly (without in-terrogation) to an MTER call attempt. CALL_ATT_PURE_TRANSIT Number of incoming call attempts leading to transit without performing interrogation for MICTR. Trigger: each time IAM is received and call leads directly (without interrogation) to an MTRANS call attempt. A50016-D1112-G802-1-7618 31
  32. 32. Counter Description Information Traffic and Performance Data DATACDA_ANA_ATTEMPTS Number of call attempts for data CDA analog services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. – MOUT_PLMN/ MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied. DATACDA_DIG_ATTEMPTS Number of call attempts 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 an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied. ALTFAXSP_CALL_ATTEMPTS Number of call attempts for alternate speech/facsimile services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied. FAX3_CALL_ATTEMPTS Number of call attempts for the automatic facsimile group 3 service for MTER, MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time the digit analysis after interrogation results in the relevant traffic type and SET UP is sent. DED_PAD_ATTEMPTS Indicates how many call attempts to a foreign network for dedicated PAD access servic-es have taken place for MOUT_NOT_PLMN. Trigger: each time the digit analysis after interrogation results in this traffic type. DATACDS_ANA_ATTEMPTS Number of call attempts for data CDS analog services. Trigger: each time the digit analysis after interrogation results in the relevant traffic type: – MTER: The exact trigger condition is the detection of an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. 32 A50016-D1112-G802-1-7618
  33. 33. Information Traffic and Performance Data Counter Description – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied. DATACDS_DIG_ATTEMPTS 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 an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied. ALT_SPEECH_DATA_ATTEMPTS 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 an MSRN of the home MSC by digit processing; this usually causes a paging message to be sent. The following cases are exceptions: busy MS, invocation of service call wait and overload related to the A interface. – MOUT_PLMN / MOUT_NOT_PLMN: In general, the values of this counter include traffic without interrogation unless international interrogation is applied. EMERGENCY_TS12_ATTEMPTS Number of emergency call attempts (TS12) for MORTR. Trigger: each time CM SERVICE REQUEST indicating an emergency call is received. MSC_MSC_HO_CALL_ATTEMPTS Number of call attempts caused by inter MSC handover for MTER (MSC-B is the home MSC). Trigger: each time IAM is received from MSC-A and digit processing detects a handover number. STARTED_PAGING_PROC Number of initial paging procedures that have been started for MTER. Trigger: each time PAGING is sent. STARTED_PAG_RETRY_PROC Number of paging retry procedures that have been started for MTER. Trigger: each time PAGING is sent after the first expiry of the paging timer. STARTED_INTERROGATIONS Number of interrogations to another MS and MICTR. that have been started for MORTR. Trigger: each time SEND ROUTING INFO is sent on receipt of SETUP STARTED_INT_SER_CODE_DIG Number of interrogations including service code digits to another MS and MICTR that have been started for MORTR. A50016-D1112-G802-1-7618 33
  34. 34. Counter Description Information Traffic and Performance Data 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. SET_UP_SERV_CODE 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 Number of generated traffic channel requests. Trigger: each time ASSIGNMENT REQUEST is sent to the BSC for: – MORTR: after the previous receipt of CM SERVICE REQUEST. – MTER: after previous paging. – MOUT_PLMN / MOUT_NOT_PLMN: the counter is only incremented in the case of rerouting, e.g., COC failure. ACTIVE_QUEUING Number of calls where queuing was active for MORTR, MTER, MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time QUEUING INDICATION is received from the BSC. The counter is up-dated when ASSIGNMENT COMPLETE or RELEASE COMPLETE is received for the call. IMEI_CHECKS Number of IMEI checks caused by call setup for MORTR, MTER. Trigger: each time CHECK IMEI is sent to the EIR. IN_ATTEMPTS Number of call attempts invoking IN functions for MORTR, MICTR. Trigger: each time interworking to an IN service control point (SCP) is started as a result of digit evaluation (e.g., dial an IN directory number) being part of a call setup. IN_TRANS Number of transaction attempts invoking IN functionality, whereby no interworking with the IN SCP is started (e.g., televoting with service filtering so that precounting is done in the SSP), for MORTR and MICTR. Trigger: each time interworking to IN SCP is started for a non call-related transaction. OACSU_ATTEMPTS Number of attempted calls with OACSU for MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time SET UP is received and OACSU treatment is initiated for the 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. 34 A50016-D1112-G802-1-7618
  35. 35. Information Traffic and Performance Data Counter Description Trigger: each time a CCBS REQUEST activating CCBS for: – MORTR: is sent by the MSC-A. – MTER: is received from the MSC-A CCBS_RECALL Once the busy subscriber at the MSC-B is released he can recall the subscriber at the MSC-A. This counter indicates the number of CCBS recall attempts. Trigger: each time REMOTE USER FREE for: – MORTR: is received from the MSC-A. – MTER: is sent by the MSC-B. SUCC_ORMMC Number of successful optimal routing mobile-to-mobile attempts. Trigger: each time an SRI with interrogation type basic and OR interrogation is sent to HLR, and “Roaming number” is included in the SRI ack. SUCC_ORECF Number of successful optimal routing early call forwarding attempts. Trigger: each time an SRI with interrogation type basic and OR interrogation indicator is sent to the HLR, and the “Forwarded-to-number” is included in SRI ack, and the flag ATD_MOBILE_DATA.OR_INDICATION is set directly before sending SEIZURE_CBT. 2.1.5 Load and Demand Counters: Part 2 SERVICE_REQ_SCI_INDEPENDENT Number of call-independent services requested via SCI. Trigger: each time CM SERVICE REQUEST is received for SS activation without being involved in a call. SERVICE_REQ_SCI_CALL_REL Number of services requested via SCI during a parallel call. Trigger: each time CM SERVICE REQUEST is received for SS during a call. SERVICE_REQ_LOC_UPD Number of received service requests for a location update. Trigger: each time COMPLETE L3 INFO with LOCATION UPDATE REQUEST is re-ceived. RECVD_POS_ACK_FROM_GSMSCF Number of positive acknowledgements sent by the GSM service control function. Trigger: each time a message containing a positive acknowledgement is received. SENT_NOTIF_SS_INV_TO_GSMSCF Indicates how often the GSM service control function has been requested to invoke a supplementary service. Trigger: each time SS INVOCATION NOTIFY is sent to the GSM service control func-tion. A50016-D1112-G802-1-7618 35
  36. 36. Counter Description Information Traffic and Performance Data 2.1.6 Load and Demand Counters: LTG Pooling The following counters collect data concerning the use of LTG pools. LTG pooling pro-vides a group of circuits that support the same channel types. · A specific speech transcoder is provided to transmit speech on the radio interface, allowing speech transmission via half rate channels (HR) or full rate channels (FR). · Circuit-switched user data is handled by the channel coding for transmission via FR channels on the radio interface at specific rates: – 6 kbit/s results from channel coding TCH/F4.8 – 12 kbit/s results from channel coding TCH/F9.6 – 14.5 kbit/s results from channel coding TCH/F14.4 · The high-speed circuit-switched data (HSCSD) facility enables data to be transport-ed by the PLMN using 2 traffic channels on the radio interface for the same data call. This facility only applies to 9.6 and 14.4 user data rates for BS20. The corresponding rates at the radio interface are 12 kbit/s,14.5 kbit/s, and 14.5 kbit/s only. CA_SPEECH_HR Number of attempts for speech calls for which a trunk providing the proper channel at-tributes has been seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper trunk is sent for HR (V1 or V3). CA_SPEECH_FR Number of attempts for speech calls for which a trunk providing the proper channel at-tributes has been seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper trunk is sent for FR (V1 or V2 or V3). CA_DATA_FR Number of attempts for data calls for which a trunk providing the proper channel at-tributes for specific rates on the radio interface has been seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper LTG is sent for 12 kbit/s, 14.5 kbit/s, and 14.5 kbit/s only. CA_DATA_HR Number of attempts for data calls for which a trunk providing the proper channel at-tributes for specific half rates on the radio interface has been seized. Trigger: each time SET UP C containing the channel attributes required to seize the proper LTG is sent for 6 kbit/s or 3.6 kbit/s. CA_HSCSD_2FR Number of attempts for high-speed data calls for which a trunk providing 2 channels 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 kbit/s, 14.5 kbit/s, and 14.5 kbit/s only. 36 A50016-D1112-G802-1-7618
  37. 37. Information Traffic and Performance Data Counter Description 2.1.7 Load and Demand Counters: Gs Interface TIME_COM_LUP_SERV Accumulated time to provide service combined location update being handled via 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 Number of received service requests for a combined location update. Trigger: each time COMPL L3 INFO (LOCATION UPDATE REQUEST) is received via the Gs interface. NUM_COM_LUP_CONTRIB Number of combined location updates which caused the “combined location update ser-vice time”. TV_SUCC_COM_PAGING Duration of successfully completed paging procedures (in 50 ms units). Trigger: – Starts each time PAGING is sent; – Stops each time PAGING RESPONSE is received. CA_COM_PAGING Number of started combined paging procedures. Trigger: each time PAGING is sent on both the A interface and the Gs interface. CA_COM_PAGING_RETRY Indicates how often a combined paging procedure is retried after rejection on the Gs in-terface. Trigger: each time PAGING is sent on both the A interface and the Gs interface after PAGING REJECT on the latter has been received. NUM_COM_PAGING_RET_A Number of started paging procedures on the A interface after an unsuccessful attempt on the Gs interface. Trigger: each time PAGING is sent on the A interface after PAGING REJECT on the Gs interface has been received. CCU_COM_PAGING Number of calls terminated because the combined paging procedure was unsuccessful. Trigger: each time the connection is released because the paging timer expired for the second time. CCS_COM_PAGING_RES Number of successfully completed combined paging procedures. A50016-D1112-G802-1-7618 37
  38. 38. Counter Description Information Traffic and Performance Data Trigger: each time PAGING RESPONSE is received from the BSC. 2.1.8 Load and Demand Counters: 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 a call triggers 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 Number of attempts for allocating an ESRK. Trigger: each time the digit evaluation results into an emergency call. SUCC_ESRK_ALLOC_ATT Number of successful attempts allocating an ESRK. Trigger: each time an ESRK is found after the digit evaluation. LOCATION_ATTEMPTS Number of location attempts. Trigger: each time DT1:PERFORM LCS is sent to the LTG. UNS_LOC_ATT_CONGESTION Number of unsuccessful location attempts due to congestion. Trigger: each time DT1:PERFORM LCS RESP is received indicating unsuccessful po-sitioning. SUCC_LOC_ATT Total number of successful location attempts. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_TA Number of successful location attempts as a result of using the “time advance” position-ing method. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_TOA Number of successful location attempts as a result of using the “time of arrival” position-ing method. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_ASSIST_E_OTD Number of successful location attempts as a result of using the “enhanced observed time difference” positioning method (MS-assisted calculation). 38 A50016-D1112-G802-1-7618
  39. 39. Information Traffic and Performance Data Counter Description Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_BASED_E_OTD 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 Number of successful location attempts as a result of using the “global positioning sys-tem” (MS-assisted calculation). Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_MOB_BASED_GPS Number of successful location attempts as a result of using the “global positioning sys-tem” (MS-based calculation). Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_CONV_GPS Number of successful location attempts as a result of using the conventional “global po-sitioning system”. Trigger: each time DT1:PERFORM LCS RESP is received indicating successful posi-tioning. SUCC_LOC_ATT_UNKNOWN_POS 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 Number of attempts for transferring both MS position estimate and emergency call orig-ination to the gateway mobile location center. Trigger: each time the first SUBSCRIBER LOCATION REPORT is successfully sent. SUCC_POS_SEND_TO_GMLC Number of successful transfers of the MS position estimate and the emergency call orig-ination to the gateway mobile location center. Trigger: each time SUBSCRIBER LOCATION REPORT ACK is received after the report is sent. 2.1.9 Location Service Counters Location Services (LCS) may be considered as a network provided enabling technology that is used by various possible location applications, so-called LCS clients, to enable A50016-D1112-G802-1-7618 39
  40. 40. Counter Description Information Traffic and Performance Data the position of an MS or an UE in a PLMN. It can be used, for example, for regional reg-ulatory requirements or for commercial purposes. Therefore, the LCS feature is a net-work feature and not a supplementary service. The LCS applications or LCS clients may be service provider specific. A MT-LR (Mobile Terminating Location Request) enables an external LCS client (e.g., fleet management center) to request the location of a specific identified MS or UE. Location Service Counters are recorded if a measurement of the complete MSC data is performed. The following counters are provided. TOTAL_NUM_MT_LR Indicates how many MT-LRs have been requested by LCS client. Trigger: each time a Provide Subscriber Location Report message is received by the CP from the GMLC for an MT-LR. MT_LR_ATT Indicates how many MT-LR attempts (request sent to the BSC or RNC) have been per-formed. Trigger: each time CP sends PERFORM_LCS to LTG when GMLC has requested a an MT-LR. SUCC_MT_LR Indicates how many successful MT-LRs (location returned to GMLC) have been per-formed. Trigger: each time CP receives successful PERFORM_LCS_RESPONSE from the LTG and Provide Subscriber Location Report Acknowledgement is sent to the GMLC for an MT-LR. NUM_MT_LR_BLOCK_PRIV Indicates how many MT-LRs have been blocked by privacy checks prior to any MS no-tification. Trigger: each time MT_LR requested by GMLC to MSC is blocked because of MS sub-scriber’s privacy. This does not include MT-LR rejected by an MS having notification and verification. NUM_MT_LR_OVRD_ATT Indicates how many MT-LR, with location attempt due to LCS client override, have been performed. Trigger: each time a GMLC sends a Provide Subscriber Location Report to the MSC with the override indication set, and the GMLC is in the same country as the VMSC, and the LCS client type is either emergency services or lawful interception and the override in-dicator is enabled as a PLMN option. NUM_MT_LR_NO_PAG_RESP Indicates how many MT-LR attempt have been rejected because the MS target is un-known or there is no paging response. Trigger: each time, during an MT_LR, a paging response is received with a failure or if no paging response is received. 40 A50016-D1112-G802-1-7618
  41. 41. Information Traffic and Performance Data Counter Description CA_ORMMC_OR_ORECF Number of optimal routing mobile-to-mobile calls or optimal routing early call forwarding attempts. Trigger: each time SEND ROUTING INFO with interrogation type basic and OR interro-gation indicator is sent to the HLR. NUM_MT_LR_BLOCK_REJ Number of MT-LRs blocked due to MS notification and verification. Trigger: each time a GMLC requests an MT-LR from the MSC, and the MT-LR is blocked due to MS notification and verification (MT-LR is rejected by the MS). MO_LR_SELF_LOC Number of MO-LR requests by location request. Trigger: each time an MS requests an MO-LR by location request. MO_LR_ASSIST_DATA Number of MO-LR requests by assistance data request. Trigger: each time an MS requests an MO-LR by assistance data request. MO_LR_DEC_KEYS Number of MO-LR requests by deciphering keys request. Trigger: each time an MS requests an MO-LR by deciphering keys request. MO_LR_SELF_LOC_ATT Number of MO-LR attempts by location request. Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MS has requested an MO-LR by location request. MO_LR_ASSIST_DATA_ATT Number of MO-LR attempts by assistance data request. Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MS has requested an MO-LR by assistance data request. MO_LR_DEC_KEYS_ATT Number of MO-LR attempts by deciphering keys request. Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MS has requested an MO-LR by deciphering keys request. SUCC_MO_LR_SELF_LOC Number of successful MO-LRs by location request. Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in the CP from the GP for an MO-LR by location request. SUCC_MO_LR_ASSIST_DATA Number of successful MO-LRs by assistance data request. Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in the CP from the GP for an MO-LR by assistance data request. A50016-D1112-G802-1-7618 41
  42. 42. Counter Description Information Traffic and Performance Data SUCC_MO_LR_DEC_KEYS Number of successful MO-LRs by deciphering keys request. Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in the CP from the GP for an MO-LR by deciphering keys request. NI_LR Indicates the total number of NI-LR requests. Trigger: each time a NI-LR is detected in the MSC for an emergency call. NI_LR_ATT Number of NI-LR attempts. Trigger: each time the DT1:PERFORM_LCS message is sent to the GP for an emergen-cy call. SUCC_NI_LR Number of successful NI-LRs. Trigger: each time a successful MAP Subscriber Location Report or MAP Provide Sub-scriber Location Report is sent to the GMLC for an emergency call. MO_LR_TTTP Indicates the total number of MO-LR requests by category (location request, assistance data request, deciphering keys request, and transfer to third party). Trigger: each time an MS has requested an MO-LR with transfer to third party via DT1:BEGIN_LCS. MO_LR_TTTP_ATT Number of MO-LR attempts (request send to the BSC or RNC) by category (location re-quest, assistance data request, deciphering keys request, and transfer to third party). Trigger: each time the DT1:PERFORM_LCS message is sent to the GP when the MS has requested an MO-LR with transfer to third party. MO_LR_TTTP_GMLC_ATT Indicates the total number of MO-LR attempts sent to GMLC with transfer to third party. Trigger: each time a successful DT1:PERFORM_LCS_RESPONSE is received in the CP from the GP, and the MAP: Subscriber Location Report is sent to the GMLC for an MO-LR request with transfer to third party. SUCC_MO_LR_TTTP Number of successful MO-LR by category (location request, assistance data request, deciphering keys request, and transfer to third party). Trigger: each time successful Subscriber_Location_Report_Ack is received in the CP from the GMLC for an MO-LR request with transfer to third party. 2.1.10 Grade of Service Counters: Unsuccessful Calls REL_BEFORE_ACM_MICTR Number of calls released in the forward direction before ACM is sent for MICTR. 42 A50016-D1112-G802-1-7618
  43. 43. Information Traffic and Performance Data Counter Description Trigger: each time a call is released in the forward direction – in GMSC: before ACM is sent and after receipt of IAM. – in VMSC: before address-complete condition and after receipt of IAM (release be-fore PAGING after receipt of IAM). UNS_PAGING Number of incoming calls terminated due to an unsuccessful paging procedure. Trigger: each time a connection is released by the second expiry of the paging timer. UNS_REQ_DEST_ERROR Number of calls terminated because the requested destination was unknown, blocked or could not be charged. Trigger: each time the respective message is involved: – MORTR: on receipt of internal release (CP) after digit analysis failed. – MTER: on receipt of RELEASE COMPLETE (cause: destination is unknown, blocked or could not be zoned). – MOUT_PLMN, MOUT_NOT_PLMN: on receipt of ISUP message RELEASE COM-PLETE / UNSUCCESSFUL BACKWARD MESSAGE after digit analysis (cause: destination is unknown, blocked or could not be zoned). – MTRAN: on receipt of RELEASE COMPLETE/UBM (cause: destination is unknown, blocked or could not be zoned). UNS_TECHN_FAULT Number of calls terminated due to technical faults in the home MSC. For MORTR, MIC-TR, MTER, MOUT_PLMN, MOUT_NOT_PLMN, MTRAN. Trigger: each time the MSC causes a technical fault (e.g., software fault, plausibility check, hardware fault). UNS_SERV_CHECK Number of calls terminated due to negative service facility checks or negative compati-bility checks. Trigger: each time the relevant message with the proper cause, for: – MORTR: RELEASE COMPLETE (e.g., service not implemented) is sent to the BSS. – MICTR: TC-U-ERROR (BS or TS not provisioned, facility not supported, forwarding violation) is received from the HLR in response to SEND ROUTING INFO. – MTER: RELEASE COMPLETE (e.g., service not implemented) is sent to the previ-ous exchange or the BSS. – MOUT_PLMN / MOUT_NOT_PLMN: RELEASE COMPLETE (e.g., service not im-plemented) is sent to the BSS. UNS_MS_BLOCKED Number of calls terminated because the subscriber was blocked by operator 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 for: – MORTR: due to barring of outgoing calls (calling subscriber) or of incoming calls (called subscriber). – MICTR: due to the interrogation result “CALL BARRED”. – MTER: due to the interrogation result “CALL BARRED” for the called subscriber. A50016-D1112-G802-1-7618 43
  44. 44. Counter Description Information Traffic and Performance Data UNS_MS_BUSY Number of calls terminated because the requested subscriber was busy. Trigger: each time the relevant message (including RELEASE messages) with reason “subscriber busy”: – MTER: UBM is sent to the previous exchange. – MOUT_PLMN, MOUT_NOT_PLMN: RELEASE UBM is received from the following exchange. UNS_CONGESTION Number of calls terminated due to (trunk) congestion in the home MSC. Trigger: each time trunk seizure is not successful due to congestion. For example for: – MORTR: BSS trunk – MTER: BSS trunk on the B side. – MOUT_PLMN / MOUT_NOT_PLMN: trunk on the B side. – MTRAN: trunk on the B side. UNS_SN_CONGESTION Number of calls terminated due to switching network (SN) congestion. For MTER, MTRAN, MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time a failure during SN through-connection occurs. UNS_LACK_IWE Number of calls terminated due to lack of IWEs. For MORTR, MTER, MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time the seizure of IWE is not successful due to unavailable IWE. UNS_SECURITY_FAIL Number of calls terminated due to authentication/security failure for MORTR and MTER. Trigger: each time AUTHENTICATION REJECT is sent to the BSS. UNS_LINK_FAIL Number of calls terminated due to failure/congestion/overload on associated CCS7 sig-naling system links. For MORTR, MICTR, MTER, MOUT_PLMN, MOUT_NOT_PLMN, MTRAN. Trigger: each time a call is released due to CCS7 failure (e.g., on receipt of ”STOP TRAFFIC”). UNS_PROTO_ERROR Number of calls terminated due to protocol errors. For MORTR, MICTR MTER, MOUT_PLMN, MOUT_NOT_PLMN, MTRAN. Trigger: each time a protocol error is detected but the call cannot be identified. UNS_NETW_MANAGEMENT Number of calls terminated due to network management activities for MOUT_PLMN, MOUT_NOT_PLMN, MTRAN. Trigger: each time trunk resource management detects a network management event. 44 A50016-D1112-G802-1-7618
  45. 45. Information Traffic and Performance Data Counter Description UNS_OVERLOAD Number of calls terminated due to overload prevention for MORTR, MICTR, MTER. Trigger: each time a call is internally released due to an overload situation. UNS_BS_REASON Number of calls terminated during setup due to BSS/radio-related reasons. Trigger: each time RELEASE COMPLETE/CLEAR REQUEST or SUBSYSTEM PRO-HIBITED, RESET, RESET CIRCUIT is received. – MORTR: from the BSS before digit analysis is performed. – MTER: before digit analysis is performed. – MOUT_PLMN, MOUT_NOT_PLMN: after digit analysis has been performed. UNS_BLACK_LIST Number of calls terminated because the IMEI check indicates black-listed equipment. For MTER, MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time a result indicating “black list” is received from the EIR in response to CHECK IMEI. UNS_IMEI_UNKNOWN Number of calls terminated because the IMEI check indicates unknown equipment, for MTER, MOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time a result indicating “IMEI unknown” is received from the EIR in re-sponse to CHECK IMEI. UNS_MS_DETACH Number of calls terminated because the called MS was detached/absent. Trigger: each time a detached or absent subscriber is detected for: – MORTR: by a negative reply by the HLR to SEND ROUTING INFO. – MICTR: by a negative reply by the HLR to SEND ROUTING INFO. – MTER: in the VLR database causing the call to be released. UNS_CUG_REJECT Number of calls terminated because the CUG has been rejected. Trigger: the proper CUG error cause is reported by – MORTR: sending RELEASE COMPLETE to the BSS. – MICTR: sending RELEASE to the previous MSC. – MOUT_PLMN, MOUT_NOT_PLMN: receiving RELEASE/UBM from subsequent MSC. UNS_INTERROGATION Number of pure interrogation failures, such as “no answer from HLR” for MORTR or MICTR. Trigger: each time a dialog error cause is received from the HLR for interrogation or the HLR does not respond to SEND_ROUTING_INFO. IN_OVERLOAD Number of IN calls that have been released due to SCP overload or automatic call gap-ping initiated by SCP for MORTR and MICTR. A50016-D1112-G802-1-7618 45
  46. 46. Counter Description Information Traffic and Performance Data Trigger: each time call setup with prompted call handling is released due to IN overload prevention measures. IN_NO_ANSW_SCP Number of IN calls that are released due to missing answer from SCP for MORTR and MICTR. Trigger: each time an IN dialog to the SCP is started and no answer is received within a timer schedule. The call setup is then released. IN_ERROR_SCP Number of IN calls that have been released because SCP sent unsuitable information (e.g., new call numbers sent from the SCP cannot be recognized in the MSC, data is unreadable). For MORTR and MICTR. Trigger: each time a connection is released because the IN SCP data received is insuf-ficient to establish the call. IN_SERV_CHECK Number of IN calls that have been released because the required IN service is not ac-tive, e.g., not allowed for the subscriber or not supported by SCP. For MORTR and MIC-TR. Trigger: each time the SCP releases a call due to service/facility checks. IN_ERROR_DEST Number of IN calls that have been released because the called IN number is unknown. For MORTR and MICTR. Trigger: each time the SCP releases a call because the called number is unknown. CCU_DATA_HR_6K Number of failed call establishments for a traffic channel with HR data (6, 3.6 kbit/s). 2.1.11 Grade of Service Counters: Unsuccessful LTG Pooling CCU_SPEECH_HR Indicates how many attempts for speech calls have been terminated because a trunk providing the proper channel attributes could not be seized. Trigger: each time the trunk cannot be seized on sending SET UP C with channel at-tributes for HR (V1 or V3) CCU_SPEECH_FR Indicates how many attempts for speech calls have been terminated because a trunk providing the proper channel attributes could not be seized. Trigger: each time the trunk cannot be seized on sending SET UP C with channel at-tributes for: – HR (V1 or V3) – FR (V1 or V2 or V3) 46 A50016-D1112-G802-1-7618
  47. 47. Information Traffic and Performance Data Counter Description CCU_DATA_FR Indicates how many attempts for data calls have been terminated because a trunk pro-viding the proper channel attributes for specific rates on the radio interface could not be seized. Trigger: each time the LTG cannot be seized on sending SET UP C with channel at-tributes for: – 12K – 14.5K – 14.5K only CCU_HSCSD_2FR Indicates how many attempts for high-speed data calls are terminated because a trunk providing 2 channels containing the proper attributes could not be seized. Trigger: each time the LTG cannot be seized on sending SET UP C with channel at-tributes for: – 12 only – 14.5K – 14.5K only 2.1.12 Grade of Service Counters: Successful Call Establishment RECEIVED_PAG_RESP Number of paging response messages received for MTER. Trigger: each time PAGING RESPONSE is received from the BSC. CALL_TCH_ALLOCATION Number of calls with successfully completed traffic channel (TCH) allocation for MOR-TR, MTERMOUT_PLMN, MOUT_NOT_PLMN. Trigger: each time ASSIGNMENT COMPLETE is received. TS11_EMERG_CALL_TCH_ALL Number of outgoing emergency calls with successfully completed traffic channel alloca-tion for emergency calling (TS11). Trigger: each time ASSIGNMENT COMPLETE is received for TS11 calls. TS12_EMERG_CALL_TCH_ALL Number of outgoing emergency calls with successfully completed traffic channel alloca-tion for emergency calling (TS12). Trigger: each time ASSIGNMENT COMPLETE is received for TS12 calls. COMPL_SCI_INDEPENDENT Number of successfully performed call-independent SCIs for MORTR. Trigger: each time RELEASE COMPLETE with facility information element (return-re-sult) is received in response to operate SS, i.e., activate/deactivate/register/erase/inter-rogate SS, register PW or process unstructured SS data. A50016-D1112-G802-1-7618 47
  48. 48. Counter Description Information Traffic and Performance Data COMPL_SCI_CALL_REL Number of successfully performed call-related SCIs for MORTR. Trigger: each time RELEASE COMPLETE with facility information element (return-re-sult) is received in response to operate SS. COMPL_INTERROGATIONS Number of calls with successfully completed interrogations for MORTR and MICTR. Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR. COMPL_INTERROGATIONS_SC Number of calls with successfully completed interrogations containing service codes for MORTR and MICTR. Trigger: each time TC-RESULT is received in response to SEND ROUTING INFO con-taining short-codes or short-service-codes. CALL_INT_MS_OWN_MSC Number of calls with successfully completed interrogations leading to MS in the home MSC for MORTR and MICTR. Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR and the MSRN evaluation results in paging. CALL_INT_MS_FOREIGN_MSC Number of call attempts for which no paging is performed after evaluating the MSRN for MORTR and MICTR. Trigger: each time a positive result of SEND ROUTING INFO is received from the HLR and the MSRN evaluation does not result in paging. SN_THROUGH_CONNECTIONS Number of successful call attempts. Trigger: each time – MTER: CALL CONFIRMED is received for: – MOUT_PLMN, MOUT_NOT_PLMN: IAM is sent to the next exchange. – MTRAN: IAM is sent to the next exchange. CALL_REL_EXCHANGE Number of calls terminated by the previous exchange for MTER, and by the following exchange for MOUT_PLMN, MOUT_NOT_PLMN, and by the previous/following ex-change for MTRAN. Trigger: each time RELEASE is received: – MTER: indicating clear forward. – MOUT_PLMN, MOUT_NOT_PLMN: indicating clear backward or UBM with causes different from busy, CUG reject, destination error. – MTRAN: indicating clear forward or clear backward. CALL_REL_BEF_ALERT Number of calls released before alerting the destination. 48 A50016-D1112-G802-1-7618

×