08-Chapter 8 Total Traffic of The Office

Technical Manual Performance Measurement Entities
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents

Huawei Technologies Proprietary
i
Table of Contents
Chapter 8 Total Traffic of the Office ............................................................................................ 8-1
8.1 Overview of Measurement Set .......................................................................................... 8-1
8.2 MS-Originated Outgoing Traffic......................................................................................... 8-2
8.2.1 Overview of MS_OFFICE_2G_ORGOUT_TRAF ................................................... 8-2
8.2.2 Count of Call Attempts ............................................................................................ 8-2
8.2.3 Count of Wrongly Dialed Numbers.......................................................................... 8-3
8.2.4 Count of Releases Before Ringing.......................................................................... 8-5
8.2.5 Count of Terminal Application Failures ................................................................... 8-6
8.2.6 Count of Common Resource Application Failures.................................................. 8-7
8.2.7 Count of Last-Choice Route Overflow .................................................................... 8-8
8.2.8 Count of Peer Office Congestions........................................................................... 8-9
8.2.9 Count of Callee Busy ............................................................................................ 8-10
8.2.10 Count of Connected Calls ................................................................................... 8-11
8.2.11 Count of Releases Before the Pickup................................................................. 8-12
8.2.12 Count of Long Time No Reply............................................................................. 8-13
8.2.13 Count of Answered Calls..................................................................................... 8-14
8.2.14 Seizure Traffic ..................................................................................................... 8-15
8.2.15 Connected Traffic................................................................................................ 8-16
8.2.16 Answered Traffic ................................................................................................. 8-17
8.2.17 Call Completion Rate .......................................................................................... 8-18
8.2.18 Answer Rate........................................................................................................ 8-18
8.3 MS-Originated Traffic....................................................................................................... 8-19
8.3.1 Overview of MS_OFFICE_2G_ORG_TRAF......................................................... 8-19
8.3.2 Count of Call Attempts .......................................................................................... 8-19
8.3.3 Count of Mobile Caller Authentication Failures..................................................... 8-20
8.3.4 Count of Mobile Caller Ciphering Mode Setting Failures...................................... 8-20
8.3.5 Count of Mobile Caller Barring.............................................................................. 8-21
8.3.6 Count of Mobile Caller Trunk Resource Overflow................................................. 8-21
8.3.7 Count of Mobile Caller Traffic Channel allocations Failures ................................. 8-22
8.3.8 Count of Wrongly Dialed Numbers........................................................................ 8-23
8.3.9 Count of Releases Before Ringing........................................................................ 8-24
8.3.10 Count of Terminal Application Failures............................................................... 8-24
8.3.11 Count of Common Resource Application Failures.............................................. 8-25
8.3.14 Seizure Traffic ..................................................................................................... 8-28

ii
8.3.18 Answer Rate........................................................................................................ 8-30
8.3.19 Count of Callee Power-Off .................................................................................. 8-30
8.4 MS-Terminated Incoming Traffic ..................................................................................... 8-30
8.4.1 Overview of MS_OFFICE_2G_INCTRM_TRAF ................................................... 8-30
8.4.4 Count of Terminal Application Failures ................................................................. 8-33
8.4.5 Count of Common Resource Application Failures................................................ 8-34
8.4.7 Count of Mobile Callee Trunk Resource Overflow................................................ 8-36
8.4.8 Count of Mobile Callee Traffic Channel allocations Failures ................................ 8-37
8.4.9 Count of MS Unavailable ...................................................................................... 8-38
8.4.13 Count of Mobile Callee Determined Busy........................................................... 8-43
8.4.15 Seizure Traffic ..................................................................................................... 8-44
8.4.19 Answer Rate........................................................................................................ 8-47
8.5 MS-Terminated Traffic ..................................................................................................... 8-48
8.5.1 Overview of MS_OFFICE_2G_TRM_TRAF ......................................................... 8-48
8.5.6 Count of Mobile Callee Trunk Resource Overflow................................................ 8-52
8.5.7 Count of Mobile Callee Traffic Channel allocations Failures ................................ 8-53
8.5.8 Count of MS Unavailable ...................................................................................... 8-54
8.5.9 Count of Connected Calls ..................................................................................... 8-55
8.5.12 Count of Mobile Callee Determined Busy........................................................... 8-58
8.5.14 Seizure Traffic ..................................................................................................... 8-60

iii
8.5.18 Answer Rate........................................................................................................ 8-63
8.6 3G VP Subscriber Originated Traffic ............................................................................... 8-64
8.6.1 Overview of MS_VP_3G_ORG_TRAF ................................................................. 8-64
8.6.2 Count of VP Call Attempts .................................................................................... 8-64
8.6.3 Count of VP Connected Calls ............................................................................... 8-65
8.6.4 Count of VP Answered Calls................................................................................. 8-66
8.6.5 Count of Failures Due to Bearer Capability .......................................................... 8-67
8.6.6 Seizure Traffic ....................................................................................................... 8-68
8.6.7 VP Connected Traffic............................................................................................ 8-68
8.6.8 VP Answered Traffic ............................................................................................. 8-68
8.6.9 VP Call Completion Rate ...................................................................................... 8-69
8.6.10 VP Answer Rate.................................................................................................. 8-69
8.7 3G VP Subscriber Terminated Traffic.............................................................................. 8-69
8.7.1 Overview of MS_VP_3G_TRM_TRAF.................................................................. 8-69
8.7.2 Count of VP Call Attempts .................................................................................... 8-70
8.7.3 Count of VP Connected Calls ............................................................................... 8-71
8.7.4 Count of VP Answered Calls................................................................................. 8-72
8.7.5 Count of Failures Due to Bearer Capability .......................................................... 8-73
8.7.6 Seizure Traffic ....................................................................................................... 8-74
8.7.7 VP Connected Traffic............................................................................................ 8-74
8.7.8 VP Answered Traffic ............................................................................................. 8-74
8.7.9 VP Call Completion Rate ...................................................................................... 8-75
8.7.10 VP Answer Rate.................................................................................................. 8-75
8.8 UE-Originated Outgoing Traffic ....................................................................................... 8-75
8.8.1 Overview of MS_OFFICE_3G_ORGOUT_TRAF ................................................. 8-75
8.8.7 Count of Outgoing Trunk Overflow........................................................................ 8-82
8.8.8 Count of Peer Office Congestions......................................................................... 8-83
8.8.14 Seizure Traffic ..................................................................................................... 8-89
8.8.18 Answer Rate........................................................................................................ 8-92

iv
8.9 UE-Originated Traffic ....................................................................................................... 8-93
8.9.1 Overview of MS_OFFICE_3G_ORG_TRAF......................................................... 8-93
8.9.3 Count of Mobile Caller Authentication Failures..................................................... 8-94
8.9.4 Count of Mobile Caller Ciphering Mode Setting Failures...................................... 8-94
8.9.5 Count of Mobile Caller Barring.............................................................................. 8-95
8.9.6 Count of Mobile Caller Trunk Resource Overflow................................................. 8-95
8.9.7 Count of Mobile Caller Traffic Channel allocations Failures ................................. 8-96
8.9.10 Count of Terminal Application Failures............................................................... 8-98
8.9.11 Count of Common Resource Application Failures.............................................. 8-99
8.9.13 Count of Answered Calls................................................................................... 8-100
8.9.14 Seizure Traffic ................................................................................................... 8-101
8.9.15 Connected Traffic.............................................................................................. 8-101
8.9.16 Answered Traffic ............................................................................................... 8-102
8.9.17 Call Completion Rate ........................................................................................ 8-102
8.9.18 Answer Rate...................................................................................................... 8-103
8.9.19 Count of Callee Power-Off ................................................................................ 8-103
8.10 UE-Terminated Incoming Traffic.................................................................................. 8-103
8.10.1 Overview of MS_OFFICE_3G_INCTRM_TRAF............................................... 8-103
8.10.2 Count of Call Attempts ...................................................................................... 8-104
8.10.3 Count of Releases Before Ringing.................................................................... 8-105
8.10.4 Count of Terminal Application Failures............................................................. 8-106
8.10.5 Count of Common Resource Application Failures............................................ 8-107
8.10.6 Count of Callee Busy ........................................................................................ 8-108
8.10.7 Count of Mobile Callee Traffic Channel allocations Failures ............................ 8-109
8.10.8 Count of MS Unavailable .................................................................................. 8-110
8.10.9 Count of Connected Calls ................................................................................. 8-111
8.10.10 Count of Releases Before the Pickup............................................................. 8-112
8.10.11 Count of Long Time No Reply......................................................................... 8-113
8.10.12 Count of Mobile Callee Determined Busy....................................................... 8-114
8.10.13 Count of Answered Calls................................................................................. 8-115
8.10.14 Seizure Traffic ................................................................................................. 8-116
8.10.15 Connected Traffic............................................................................................ 8-117
8.10.16 Answered Traffic ............................................................................................. 8-118
8.10.17 Call Completion Rate ...................................................................................... 8-119
8.10.18 Answer Rate.................................................................................................... 8-119
8.11 UE-Terminated Traffic ................................................................................................. 8-120
8.11.1 Overview of MS_OFFICE_3G_TRM_TRAF ..................................................... 8-120

v
8.11.6 Count of Mobile Callee Trunk Resource Overflow............................................ 8-124
8.11.14 Seizure Traffic ................................................................................................. 8-132
8.11.18 Answer Rate.................................................................................................... 8-135
8.12 Outgoing Traffic ........................................................................................................... 8-136
8.12.1 Overview of MS_OFFICE_OUT_TRAF ............................................................ 8-136
8.12.2 Count of Seizure Attempts ................................................................................ 8-137
8.12.3 Count of Seizure ............................................................................................... 8-137
8.12.6 Count of Not Answered Calls............................................................................ 8-140
8.12.8 Count of Call Failures Due to Overload ............................................................ 8-142
8.12.9 Count of Call Failures Due to Network Management........................................ 8-144
8.12.10 Count of Outgoing Trunk Overflow ................................................................. 8-146
8.12.11 Count of Callee Busy ...................................................................................... 8-147
8.12.12 Count of Callee Busy in Toll Calls................................................................... 8-148
8.12.13 Count of Callee Busy in Local Calls................................................................ 8-149
8.12.14 Seizure Traffic ................................................................................................. 8-149
8.12.16 Count of Blocked Circuits................................................................................ 8-151
8.12.18 Answer Rate.................................................................................................... 8-152
8.12.19 Count of Call Attempts .................................................................................... 8-152
8.12.20 Count of Failed Call Attempts Due to Common Resource Application Failure8-153
8.12.21 Count of Failed Call Attempts Due to Peer Office Congestion ....................... 8-154
8.12.23 Count of Incomplete Addresses Received...................................................... 8-157
8.13 Connection Type.......................................................................................................... 8-160
8.13.1 Overview of MS_OFFICE_CALLNATURE_TRAF............................................ 8-160

vi
8.13.5 Count of Barred Calls Due to Caller Service Restriction .................................. 8-163
8.13.7 Count of Outgoing Trunk Overflow ................................................................... 8-164
8.13.9 Count of Releases Before the Pickup............................................................... 8-166
8.13.11 Seizure Traffic ................................................................................................. 8-168
8.13.15 Answer Rate.................................................................................................... 8-171
8.13.16 Count of MS Unavailable ................................................................................ 8-172
8.13.17 Count of Failed Call Attempts Due to Inter-Trunk Failure............................... 8-172
8.13.18 Count of Failed Call Attempts Due to Inter-Trunk Failure............................... 8-173
8.13.19 Count of Failed Call Attempts Due to Peer Office Congestion ....................... 8-174
8.14 Intra-Office Traffic ........................................................................................................ 8-176
8.14.1 Overview of MS_OFFICE_INT_MTM_TRAF.................................................... 8-176
8.14.7 Count of Mobile Callee Trunk Resource Overflow............................................ 8-182
8.14.10 Count of Connected Calls ............................................................................... 8-185
8.14.15 Seizure Traffic ................................................................................................. 8-190
8.14.19 Answer Rate.................................................................................................... 8-193
8.15 Call Forwarding Traffic................................................................................................. 8-194
8.15.1 Overview of MS_FORWARD_TRAF................................................................. 8-194
8.15.2 Count of Call Forwarding Attempts ................................................................... 8-194

vii
8.15.3 Count of Forwarded Calls ................................................................................. 8-195
8.15.4 Count of Answered Forwarded Calls ................................................................ 8-196
8.15.5 Count of Call Forwarding Seizure Traffic.......................................................... 8-197
8.15.6 Count of Call Forwarding Connected Traffic..................................................... 8-198
8.15.7 Call Forwarding Answered Traffic..................................................................... 8-199
8.16 Forwarded Subscriber Count....................................................................................... 8-200
8.16.1 Overview of MS_FORWARD_USER................................................................ 8-200
8.16.2 Count of Subscribers Forwarded to Destination ............................................... 8-200
8.17 Failure Causes of the Office ........................................................................................ 8-204
8.17.1 Overview of MS_FAULT_REASON_TRAF....................................................... 8-204
8.17.2 Count of Supplementary Service Setting Conflict ............................................. 8-208
8.17.3 Count of Supplementary Service Setting Successes ....................................... 8-208
8.17.4 Count of Supplementary Service Setting Failures ............................................ 8-209
8.17.5 Count of Supplementary Service Deregistration Successes ............................ 8-209
8.17.6 Count of Supplementary Service Deregistration Failures................................. 8-209
8.17.7 Count of Supplementary Service Authentication Successes............................ 8-210
8.17.8 Count of Supplementary Service Authentication Failures ................................ 8-210
8.17.9 Count of Supplementary Service Application Successes................................. 8-210
8.17.10 Count of Supplementary Service Application Failures.................................... 8-211
8.17.11 Count of Successes in Probing Malicious Calls.............................................. 8-211
8.17.12 Count of Failures in Probing Malicious Calls .................................................. 8-211
8.17.13 Count of MSC Congestions............................................................................. 8-212
8.17.14 Count of Long Time No Dialing....................................................................... 8-212
8.17.16 Count of Temporary Failures .......................................................................... 8-213
8.17.17 Count of Self-Test Successes......................................................................... 8-213
8.17.18 Count of Long Time No Messages ................................................................. 8-214
8.17.19 Count of Long Time No Ringing...................................................................... 8-214
8.17.20 Count of Long Time No Release..................................................................... 8-214
8.17.21 Count of Inband Signals.................................................................................. 8-215
8.17.22 Count of Continuity Check Failures ................................................................ 8-215
8.17.23 Count of Exceeding Max. Call Attempts ......................................................... 8-215
8.17.24 Count of Releases Before Ringing.................................................................. 8-216
8.17.26 Count of Call Restrictions................................................................................ 8-216
8.17.27 Count of MSC Failures.................................................................................... 8-217
8.17.28 Count of Toll Calls to Busy Callee .................................................................. 8-217
8.17.29 Count of Local Calls to Busy Callee................................................................ 8-217
8.17.30 Count of Peer Office Congestion .................................................................... 8-218
8.17.31 Count of Call Failures...................................................................................... 8-218
8.17.32 Count of Contentions ...................................................................................... 8-219
8.17.33 Count of Invalid Numbers................................................................................ 8-219

viii
8.17.34 Count of Network Management Barring.......................................................... 8-219
8.17.35 Count of CPU Congestions and Overload ...................................................... 8-220
8.17.36 Count of No CR Resources............................................................................. 8-220
8.17.37 Count of No CCB Resources .......................................................................... 8-220
8.17.38 Count of Incoming Office CF Barring.............................................................. 8-221
8.17.39 Count of Dialing Time Out............................................................................... 8-221
8.17.40 Count of Signaling Failures............................................................................. 8-221
8.17.41 Count of Black List Calls Barred ..................................................................... 8-222
8.17.42 Count of Caller Number Identification Failures ............................................... 8-222
8.17.43 Count of No A Interface Resource for A Bearer Service ................................ 8-222
8.17.44 Count of No A Interface Resources ................................................................ 8-223
8.17.45 Count of CUG Service Incompatible............................................................... 8-223
8.17.46 Count of Unknown CUG.................................................................................. 8-223
8.17.47 Count of CUG Unselected............................................................................... 8-224
8.17.48 Count of CUG Outgoing Calls Barred............................................................. 8-224
8.17.49 Count of CUG Incoming Calls Barred............................................................. 8-224
8.17.50 Count of CUG Supplementary Service Failures ............................................. 8-225
8.17.51 Count of CUG Destination Incompatible......................................................... 8-225
8.17.52 Count of Released Calls ................................................................................. 8-225
8.17.53 Count of Switchover Successes...................................................................... 8-226
8.17.54 Count of Switchover Failures .......................................................................... 8-226
8.17.55 Count of Call Restriction Duration Timeout..................................................... 8-226
8.17.56 Count of Termination Resource Application Failures...................................... 8-227
8.17.57 Count of Callee Number Not Exist (Excluding Fixed-Line Numbers) ............. 8-227
8.17.58 Count of Mobile Callee No Reply.................................................................... 8-228
8.17.59 Count of Mobile Callee Incoming Call Restricted............................................ 8-228
8.17.60 Count of Call out Restrictions.......................................................................... 8-228
8.17.61 Count of Callee Unreachable.......................................................................... 8-229
8.17.62 Count of Calling Local Subscriber Without Area Code................................... 8-229
8.17.63 Count of Mobile Callee Busy........................................................................... 8-229
8.17.64 Count of Mobile Callee Power-Off................................................................... 8-230
8.17.65 Count of Required Function Not Applied ........................................................ 8-230
8.17.66 Count of Toll Calls Without 0 ........................................................................ 8-230
8.17.67 Count of CF Conflict ........................................................................................ 8-231
8.17.68 Count of Failures in HLR Obtaining Route Information .................................. 8-231
8.17.69 Count of All Outgoing Calls Barred by Operators ........................................... 8-232
8.17.70 Count of All Outgoing International Calls Barred by Operators ...................... 8-232
8.17.71 Count of All Outgoing International Calls Barred by Subscribers ................... 8-232
8.17.72 Count of BOIC-exHC Barred by Subscribers.................................................. 8-233
8.17.73 Count of BOIC-exHC Barred by Operators..................................................... 8-233
8.17.74 Count of All Incoming Calls Barred by Operators ........................................... 8-233
8.17.75 Count of Operators Barring Entertainment Console....................................... 8-234

ix
8.17.76 Count of Operators Barring Announcement Console ..................................... 8-234
8.17.77 Count of Subscriber Roaming Out .................................................................. 8-234
8.17.78 Count of All National Toll Calls Barred by Operators...................................... 8-235
8.17.79 Count of Cause Unknown Failures ................................................................. 8-235
8.17.80 Count of Unallocated Numbers....................................................................... 8-235
8.17.81 Count of No Route to Specified Transit Network ............................................ 8-236
8.17.82 Count of No Route to Destination ................................................................... 8-236
8.17.83 Count of Sending Private Tone....................................................................... 8-237
8.17.84 Count of Wrongly Dialed Numbers of Toll Call Prefix ..................................... 8-237
8.17.85 Count of Unacceptable Paths ......................................................................... 8-237
8.17.86 Count of Calls Connected and Delivered on Established Route .................... 8-238
8.17.87 Count of Calls Barred by Operators................................................................ 8-238
8.17.88 Count of Circuits Reserved for Reusing.......................................................... 8-238
8.17.89 Count of Normally cleared Calls...................................................................... 8-239
8.17.90 Count of Callee Determined Busy................................................................... 8-239
8.17.91 Count of No Reply........................................................................................... 8-239
8.17.92 Count of No Response.................................................................................... 8-240
8.17.93 Count of Callee Absent ................................................................................... 8-240
8.17.94 Count of Calls Rejected .................................................................................. 8-240
8.17.95 Count of Number Changed ............................................................................. 8-241
8.17.96 Count of No Idle Circuits ................................................................................. 8-241
8.17.97 Count of RAB Pre-Empted.............................................................................. 8-241
8.17.98 Count of Callee Failures.................................................................................. 8-242
8.17.99 Count of Invalid Number Formats ................................................................... 8-242
8.17.100 Count of Facilities Rejected .......................................................................... 8-242
8.17.101 Count of Responses to STATUS ENQUIRY................................................. 8-243
8.17.102 Count of Normally cleared Calls.................................................................... 8-243
8.17.103 Count of Unavailable Circuits........................................................................ 8-243
8.17.104 Count of Network Failures............................................................................. 8-244
8.17.105 Count of Contemporary Failures................................................................... 8-244
8.17.106 Count of MSC Failures.................................................................................. 8-245
8.17.107 Count of Accessed Messages Discarded ..................................................... 8-245
8.17.108 Count of Unavailable Routes ........................................................................ 8-245
8.17.109 Count of Unavailable Paths........................................................................... 8-246
8.17.110 Count of Unavailable Resources .................................................................. 8-246
8.17.111 Count of No Suitable Service Quality............................................................ 8-246
8.17.112 Counts of Facility Applied Not Preserved Before.......................................... 8-247
8.17.113 Count of CUG Outgoing Call Restriction....................................................... 8-247
8.17.114 Count of CUG Incoming Call Restriction....................................................... 8-247
8.17.115 Count of Bearer Capability Authorized.......................................................... 8-248
8.17.116 Count of No Available Bearer Capability....................................................... 8-248
8.17.117 Count of No Suitable Service or Optional Project ......................................... 8-248

x
8.17.118 Count of Bearer Capability Not Implemented ............................................... 8-249
8.17.119 Count of Path Type Not Implemented........................................................... 8-249
8.17.120 Count of AOC Service Request Failures ...................................................... 8-250
8.17.121 Count of ACM Equaling or Greater Than ACM max..................................... 8-250
8.17.122 Count of Requested Equipment Not Implemented ....................................... 8-250
8.17.123 Count of Restricted Bearer Capability........................................................... 8-251
8.17.124 Count of IWF Resource Unavailable............................................................. 8-251
8.17.125 Count of Service or Optional Project Not Implemented................................ 8-251
8.17.126 Count of Invalid Call Reference Values ........................................................ 8-252
8.17.127 Count of Identified Route Not Exist ............................................................... 8-252
8.17.128 Count of Callee not CUG Subscriber ............................................................ 8-252
8.17.129 Count of Incompatible Terminals .................................................................. 8-253
8.17.130 Count of CUG Not Exist ................................................................................ 8-253
8.17.131 Count of Invalid Transit Network Selection................................................... 8-253
8.17.132 Count of Invalid Messages............................................................................ 8-254
8.17.133 Count of Non-Existent or Not Implemented Message Types........................ 8-254
8.17.134 Count of Non-Existent or Not Implemented Message Units ......................... 8-255
8.17.135 Count of Timeout Recoveries........................................................................ 8-255
8.17.136 Count of Non-Existent or Not Implemented Parameters .............................. 8-255
8.17.137 Count of Messages Carrying Unidentified Parameters................................. 8-256
8.17.138 Count of Protocol errors................................................................................ 8-256
8.17.139 Count of Interworking.................................................................................... 8-256
8.18 Incoming Traffic ........................................................................................................... 8-257
8.18.1 Overview of MS_OFFICE_INC_TRAF.............................................................. 8-257
8.18.2 Count of Seizure ............................................................................................... 8-257
8.18.4 Count of Incomplete Numbers .......................................................................... 8-259
8.18.5 Count of Invalid Addresses ............................................................................... 8-261
8.18.6 Count of Failed Calls Due to Internal Failure.................................................... 8-263
8.18.7 Count of Call Failures Due to Overload ............................................................ 8-265
8.18.8 Count of Call Failures Due to Network Management........................................ 8-266
8.18.9 Seizure Traffic ................................................................................................... 8-268
8.18.11 Count of Circuits in Maintenance.................................................................... 8-269
8.18.12 Answer Rate.................................................................................................... 8-269
8.18.13 Count of Connected Calls ............................................................................... 8-270
8.18.16 Count of Callee Power-Off .............................................................................. 8-272
8.19 Source TMG Destination Route Traffic........................................................................ 8-273
8.19.1 Overview of MS_MGWID_ROUTE_TRAF........................................................ 8-273
8.19.2 Count of Seizure Attempts ................................................................................ 8-274

xi
8.19.3 Count of Seizure ............................................................................................... 8-275
8.19.4 Count of Ringings Received.............................................................................. 8-276
8.19.6 Call Completion Rate ........................................................................................ 8-278
8.19.7 Answer Rate...................................................................................................... 8-278
8.19.8 Seizure Traffic ................................................................................................... 8-279
8.19.9 Connected Traffic.............................................................................................. 8-280
8.19.11 Count of Outgoing Trunk Overflow ................................................................. 8-281
8.19.12 Count of Releases Before Ringing.................................................................. 8-282
8.19.14 Count of Callee No Reply................................................................................ 8-284
8.19.15 Count of Callee Determined Busy................................................................... 8-285
8.19.16 Count of Callee Busy ...................................................................................... 8-286
8.19.17 Count of Invalid Addresses ............................................................................. 8-287
8.19.18 Count of Paging No Reply............................................................................... 8-288
8.19.19 Count of Subscriber Absence ......................................................................... 8-289
8.19.20 Count of Subscriber Service Restricted.......................................................... 8-290
8.19.21 Count of Special Tones................................................................................... 8-291
8.19.22 Count of Peer Office Congestions .................................................................. 8-292
8.19.23 Count of Interworking Failures ........................................................................ 8-293
8.19.24 Count of Other Failures................................................................................... 8-294
8.19.25 Count of Re-Routing ....................................................................................... 8-294
8.19.26 Count of Re-Routing Failures.......................................................................... 8-296
8.19.27 Count of UMG Failures ................................................................................... 8-297
8.19.28 Count of Circuit All Busy ................................................................................. 8-298
8.20 Transit Traffic............................................................................................................... 8-300
8.20.1 Overview of MS_OFFICE_TRN_TRAF............................................................. 8-300
8.20.2 Count of Outgoing Trunk Seizure Attempts ...................................................... 8-300
8.20.3 Count of Outgoing Trunk Seizure...................................................................... 8-301
8.20.7 Count of Outgoing Trunk Overflow ................................................................... 8-305
8.20.9 Seizure Traffic ................................................................................................... 8-307
8.20.13 Answer Rate.................................................................................................... 8-310
8.20.14 Count of Call Attempts .................................................................................... 8-311
8.20.15 Count of Wrongly Dialed Numbers.................................................................. 8-311

xii
8.20.16 Count of Failed Call Attempts Due to Common Resource Application Failures8-312
8.20.17 Count of Peer Office Congestions .................................................................. 8-313

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Total Traffic of the Office

8-1
Chapter 8 Total Traffic of the Office
8.1 Overview of Measurement Set
This measurement set specifies the total traffic of the office. According to the
measurement of the total traffic of the office, all information including calling status,
calling service quality, and network quality in all directions can be obtained. This
information facilitates network optimization and upgrade.
The names and meanings are listed in the following table.
Name Description
MS_OFFICE_2G_ORGOUT_TRAF MS-originated outgoing traffic
MS_OFFICE_2G_ORG_TRAF MS-originated traffic
MS_OFFICE_2G_INCTRM_TRAF MS-terminated incoming traffic
MS_OFFICE_2G_TRM_TRAF MS-terminated traffic
MS_VP_3G_ORG_TRAF 3G VP subscriber originated traffic
MS_VP_3G_TRM_TRAF 3G VP subscriber terminated traffic
MS_OFFICE_3G_ORGOUT_TRAF UE-originated outgoing traffic
MS_OFFICE_3G_ORG_TRAF UE-originated traffic
MS_OFFICE_3G_INCTRM_TRAF UE-terminated incoming traffic
MS_OFFICE_3G_TRM_TRAF UE-terminated traffic
MS_OFFICE_OUT_TRAF Outgoing traffic
MS_OFFICE_CALLNATURE_TRAF Connection type
MS_OFFICE_INT_MTM_TRAF Intra-office traffic
MS_FORWARD_TRAF Call forwarding traffic
MS_FORWARD_USER Forwarded subscriber count
MS_FAULT_REASON_TRAF Failure causes of the office
MS_OFFICE_INC_TRAF Incoming traffic
MS_MGWID_ROUTE_TRAF Source TMG destination route traffic
MS_OFFICE_TRN_TRAF Transit traffic


8-2
8.2 MS-Originated Outgoing Traffic
8.2.1 Overview of MS_OFFICE_2G_ORGOUT_TRAF
Name Description
CA10 Count of call attempts
WDN10 Count of wrongly dialed numbers
ABR10 Count of releases before ringing
TAF10 Count of terminal application failures
CRU10 Count of common resource application failures
TO10 Count of last-choice route overflow
EC10 Count of peer office congestions
CB10 Count of callee busy
ALT10 Count of connected calls
AAR10 Count of releases before the pickup
RNA10 Count of long time no reply
ANS10 Count of answered calls
SU10 Seizure traffic
ALTU10 Connected traffic
ANSU10 Answered traffic
ALTR10 Call completion rate
ANSR10 Answer rate

8.2.2 Count of Call Attempts
I. Entity Name
CA10
II. Description
It is the count of call attempts initiated by the RNS and found to be outgoing ones
through DN analysis.
III. Measurement Point
It is measured when the MSC finds out a call originated by the BSS to be an outgoing
one according to the called number analysis.

8-3
See point A in the following figure.
MSC Server MSC Server
BSC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
DTAP Connect Ack
ANM/ANC
REL

IV. Formula
None
8.2.3 Count of Wrongly Dialed Numbers
I. Entity Name
WDN10
II. Description
It is the count of call connection failures due to wrong numbers dialed by mobile callers.
It is measured when the MSC receives the ADI or UNN message (TUP signaling).
See point B in the following figure.

8-4
ACM
DTAP SETUP
IAM
B
REL
RLC
RNC

It is measured when the number dialing time exceeds the time set on the internal
timer of the MSC. See point B in the following figure.
ACM
DTAP SETUP
IAM
B
REL
RLC
RNC

It is measured when the MSC receives the REL message from the terminating
office. The cause value in the message is 129 (unallocated number) or 156
(incomplete number). See point B in the following figure.

8-5
ACM
DTAP SETUP
IAM
B
REL
RLC
RNC

IV. Formula
None
8.2.4 Count of Releases Before Ringing
I. Entity Name
ABR10
II. Description
It is the count of mobile caller releases before the callees' phones ring (the callee may
be either a non-local PSTN or mobile subscriber).
It is measured when the MSC receives the DTAP Disconnect message from a mobile
caller before the call is connected. See point A in the following figure.

8-6
RNC/BSC
ACM
DTAP SETUP
IAM
A REL
RLC
DTAP
Disconnect

IV. Formula
None
8.2.5 Count of Terminal Application Failures
I. Entity Name
TAF10
II. Description
It is the count of call failures caused by Prepare Bearer failures on the MGW.
It is measured when the MSC receives the Prepare Bearer Rsp message from the
MGW. The message contains failure information. See point A in the following figure.

8-7
MSC Server
MSC Server
BSC
ACM
DTAP SETUP
IAM
A
REL
DTAP Disconnect

IV. Formula
None
8.2.6 Count of Common Resource Application Failures
I. Entity Name
CRU10
II. Description
It is the count of call failures caused by common resources unavailable on the MSC,
including the IWF, bill pool, control table, and announcement resources.
It is measured when the MSC fails to apply and use internal common resources. See
point A in the following figure.

8-8
MSC Server
MSC Server
BSC
ACM
DTAP SETUP
IAM
A
REL
DTAP Disconnect

IV. Formula
None
8.2.7 Count of Last-Choice Route Overflow
I. Entity Name
TO10
II. Description
It is the count of failures when the MSC tries to seize the outgoing trunk for outgoing
calls.
It is measured when the MSC fails to select a trunk in an outgoing call. See point A in
the following figure.

8-9
MSC Server
MSC Server
BSC
DTAP SETUP
IAM
A

IV. Formula
None
8.2.8 Count of Peer Office Congestions
I. Entity Name
EC10
II. Description
After the MSC sends the IAM or IAI to the peer office according to the routing
information in an outgoing call, the peer office or the terminating office returns an
unexpected backward message (excluding callee busy, invalid address) to indicate that
the call cannot be connected. This entity is the count of call connection failures in such
situation.
It is measured in one of the following cases:
After sending the IAM, the MSC releases the call due to no response from the peer
office in a valid period.
The callee line is faulty.
The call connection fails.
The circuit group of the peer office is congested.
The switch of the peer office is congested.

8-10
BSC
ACM
DTAP SETUP
IAM
A
DTAP Disconnect

IV. Formula
None
8.2.9 Count of Callee Busy
I. Entity Name
CB10
II. Description
It is the count of call connections failed because callees are busy (in local or toll calls) in
the outgoing calls.
It is measured when the MSC receives the STB, SLB (TUP), or REL (ISUP) message
from the terminating office in an outgoing call. See point A in the following figure.

8-11
BSC
ACM
DTAP SETUP
IAM
A
REL
RLC
DTAP
Disconnect

IV. Formula
None
8.2.10 Count of Connected Calls
I. Entity Name
ALT10
II. Description
It is the count of DTAP Alerting messages sent to the callers in the outgoing calls.
It is measured when the MSC sends the DTAP Alerting message to the mobile caller
after receiving the ACM. See point B in the following figure.

8-12
BSC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
8.2.11 Count of Releases Before the Pickup
I. Entity Name
AAR10
II. Description
It is the count of active releases by mobile callers before the pickup.
caller before the callee picks up the phone. See point A in the following figure.

8-13
BSC
ACM
DTAP SETUP
IAM
A
REL
DTAP
Disconnect
DTAP ALERTING
ANM/ANC

IV. Formula
None
8.2.12 Count of Long Time No Reply
I. Entity Name
RNA10
II. Description
It is the count of outgoing calls that are released because the callees do not answer till
timeout.
It is measured when the MSC releases the call due to no ANM/ANC message
received from the callee in a valid period after the ACM. See point A in the
following figure.

8-14
BSC
ACM
DTAP SETUP
IAM
A
REL
DTAP ALERTING
RLC
ANM/ANC

It is measured when the MSC releases the call after receiving the ACM and REL
messages from the callee. The cause value in REL message is 146
(CV_NO_RESPOND) or 147 (CV_NO_ACKNOWLEGE). See point A in the
following figure.
BSC
ACM
DTAP SETUP
IAM
A
REL
DTAP ALERTING
RLC
ANM/ANC

IV. Formula
None
8.2.13 Count of Answered Calls
I. Entity Name
ANS10
II. Description
It is the count of outgoing calls answered.

8-15
It is measured when the MSC receives the DTAP Connect Ack message sent by an
mobile caller. See point C in the following figure. When receiving the ANC or ANN
message, the MSC sends the DTAP Connect message to the mobile caller. And then
the caller sends the DTAP Connect Ack to the MSC.
BSC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
8.2.14 Seizure Traffic
I. Entity Name
SU10
II. Description
It is the traffic generated during the outgoing call attempts.
It is measured from the moment the IAM or IAI message is sent to the destination MSC
to that the REL message is sent. The final result is indicated in Erlang. Point A in the
following figure is the start point of the measurement and call release is the end point.

8-16
BSC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
8.2.15 Connected Traffic
I. Entity Name
ALTU10
II. Description
It is the traffic generated when outgoing calls are in the connected status.
It is measured from the moment the ACM is received from the destination MSC to that
the REL message is sent. The final result is indicated in Erlang. Point B in the following
figure is the start point of the measurement and call release is the end point.

8-17
BSC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
8.2.16 Answered Traffic
I. Entity Name
ANSU10
II. Description
It is the traffic generated when outgoing calls are in the answered status.
It is measured from the moment the Answer signal is received from the destination
MSC to that the REL message is sent. The final result is indicated in Erlang. Point C in
the following figure is the start point of the measurement and call release is the end
point.

8-18
BSC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
8.2.17 Call Completion Rate
I. Entity Name
ALTR10
II. Description
Answer rate = Count of connected calls/Count of call attempts
It is a calculated value.
IV. Formula
ALTR10 = ALT10/CA10
8.2.18 Answer Rate
I. Entity Name
ANSR10
II. Description
Answer rate = Count of answered calls/Count of call attempts

8-19
IV. Formula
ANSR10 = ANS10/CA10
8.3 MS-Originated Traffic
8.3.1 Overview of MS_OFFICE_2G_ORG_TRAF
Name Description
MAF3 Count of mobile caller authentication failures
MSCF3 Count of mobile caller ciphering mode setting failures
MB3 Count of mobile caller barring
MBTO3 Count of mobile caller trunk resource overflow
MASF3 Count of mobile caller traffic channel allocations failures
SNB3 Count of terminal application failures
SU3 Seizure traffic
AU3 Connected traffic
ANU3 Answered traffic
AR3 Call completion rate
ANR3 Answer rate
ID3 Count of callee power-off

I. Entity Name
CA3

8-20
II. Description
It is the count of call attempts originated by the MSs in the local MSC, regardless of the
terminating MSCs.
It is measured when the MSC receives the layer-3 CM Service Request message.
IV. Formula
None
8.3.3 Count of Mobile Caller Authentication Failures
I. Entity Name
MAF3
II. Description
It is the count of failed calls originated by the MSs in the local MSC due to
authentication failures.
When receiving the AUTHENTICATION_RESPONSE message from the MS, the
MSC checks whether the XRES or SRES (for GSM network) is correct. If not, the
MSC returns a CM Service Reject message and begins the measurement.
It is measured when the MSC does not receive the
AUTHENTICATION_RESPONSE message from the MS in a valid period.
IV. Formula
None
8.3.4 Count of Mobile Caller Ciphering Mode Setting Failures
I. Entity Name
MSCF3
II. Description
It is the count of failed calls originated by MSs due to ciphering mode setting failures.
It is measured when the MSC receives the CIPHER MODE REJECT message from the
BSS after sending the CIPHER MODE COMMAND message to the BSS of the MS.

8-21
IV. Formula
None
8.3.5 Count of Mobile Caller Barring
I. Entity Name
MB3
II. Description
It is the count of failed calls due to the bearer capability or originating MS service
restriction, such as Bearer service not provisioned, Teleservice not provisioned, or
BAOC.
It is measured when the call is released due to the restriction subscribed by the caller.
SETUP
O_MS MSC Server
A
RELEASE
VLR
ObtainSubscriberParaOutgoingCall
RELEASE COMPLETE

IV. Formula
None
8.3.6 Count of Mobile Caller Trunk Resource Overflow
I. Entity Name
MBTO3
II. Description
It is the count of failed calls originated by MSs due to all trunks busy on the interface A,
which makes the MSC fail to send the PREPARE BEARER REQ message to the MGW.
It is measured when the MSC fails to allocate terrestrial channels before sending the
BSSMAP ASSIGN REQUEST message to the BSS of the mobile caller.

8-22
SETUP
O_BSS MSC Server MGW
A
PREPARE BEARER REQ
PREPARE BEARER RSP
A1

IV. Formula
None
8.3.7 Count of Mobile Caller Traffic Channel allocations Failures
I. Entity Name
MASF3
II. Description
It is the count of failed call attempts caused by unsuccessful voice channel allocations
from the MSC to the BSC for the mobile callers.
It is measured when the MSC receives the ASSIGN FAILURE message from the BSC
of the mobile caller after sending the BSSMAP ASSIGNMENT REQUEST message to
this BSC. The allocation includes advanced allocation and delayed allocation.

8-23
BSSMAP ASSIGNMENT REQUEST
O_BSS MSC Server
BSSMAP ASSIGNMENT FAILURE
A

IV. Formula
None
I. Entity Name
WDN3
II. Description
It is the count of wrong numbers dialed by local MSs, including the following three
cases.
The MSC fails to analyze the called number because the number is incomplete
and cannot be determined.
After confirming that the called number is MSISDN, the MSC fails to obtain the
routing information from the HLR. The callee location is unknown.
The MSC obtains the outgoing routing from the HLR, however, the terminating
office returns the ADI (invalid address), UNN (unallocated number, TUP), or REL
(unallocated number, incomplete number, ISUP) message.
It is measured in one of the following cases.
The MSC fails to analyze the called number and the destination is unknown.
The MSC receives the Routing Failure message from the MAP.
The calling side is CM, and the call is released due to unavailable called number,
unallocated called number, invalid number format, or long time no dialing.
IV. Formula
None

8-24
I. Entity Name
ABR3
II. Description
It is the count of mobile caller releases before the callees' phones ring.
It is measured when the MSC receives the DTAP Disconnect, DTAP RELEASE, or
DTAP_RELEASE_CMP message from a mobile caller before the call is connected.
O_MS MSC Server
A
DISCONNECT / RELEASE
/ RELEASE COMPLETE
SETUP
Before ALERTING

IV. Formula
None
I. Entity Name
SNB3
II. Description
It is the count of failed calls originated by the local MSs. The calls fail because the MSC
fails to request the MGW for the Termination resources.
It is measured when the MSC fails to request the Reserve circuit from the MGW. See
point A1 in the following figure.

8-25
SETUP
O_BSS MSC Server MGW
A
PREPARE BEARER REQ
PREPARE BEARER RSP
A1

IV. Formula
None
I. Entity Name
CRU3
II. Description
It is measured when the MSC fails to apply and use internal common resources.

8-26
SETUP
O_MS MSC Server
A
REALEASE COMPLETE

IV. Formula
None
I. Entity Name
ALT3
II. Description
It is the count of DTAP Alerting messages sent to the MSs.
after receiving the ACM from the terminating office in an inter-office call.

8-27
ALERTING
O_UE MSC Server
A
CONNECT
B
CONNECT ACK
ACM
ANM

after receiving the DTAP Alerting message from the mobile callee in an intra-office call.
IV. Formula
None
I. Entity Name
ANS3
II. Description
It is the count of MS-originated calls answered.
In an outgoing call, when receiving the ANC/ANN (TUP) or ANM (ISUP) message from
the terminating office, the MSC sends the DTAP Connect message to the mobile caller.
After receiving the DTAP Connect ACK message from the mobile caller, the MSC
begins the measurement.
In an incoming call, when receiving the DTAP Connect message from the mobile callee,
the MSC sends the DTAP Connect message to the mobile caller and begins the
measurement.

8-28
ALERTING
O_UE MSC Server
A
CONNECT
B
CONNECT ACK
ACM
ANM

IV. Formula
None
I. Entity Name
SU3
II. Description
It is the traffic generated from originating MS starting call attempt to call release.
It measures the interval between relevant messages in a measurement period. It is
measured from the moment the DTAP Setup message is sent to that the CLEAR
COMMAND is sent. The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
AU3
II. Description
It is the traffic generated when incoming calls initiated by the MSs are in the connected
status. The measurement begins from the moment the phone rings to that the call is
released.

8-29
It is measured from the moment the DTAP Alerting message is received to that the
CLEAR COMMAND message is received. The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
ANU3
II. Description
It is the traffic generated when VP calls initiated by the local MSs are in the answered
status.
It is measured from the moment the CONNECT ACKNOWLEDGE message is received
to that the CLEAR COMMAND message is received. The final result is indicated in
Erlang.
IV. Formula
None
I. Entity Name
AR3
II. Description
IV. Formula
AR3 = ALT3/CA3

8-30
8.3.18 Answer Rate
I. Entity Name
ANR3
II. Description
IV. Formula
ANR3 = ANS3/CA3
8.3.19 Count of Callee Power-Off
I. Entity Name
ID3
II. Description
It is the count of failed call connections (during called number analysis in MSC) due to
callees power-off.
When the MSC analyzes the called number and queries the MSRN of the callee from
the HLR. The HLR returns an indication of callee power-off. The call connection fails
and the measurement begins.
IV. Formula
None
8.4 MS-Terminated Incoming Traffic
8.4.1 Overview of MS_OFFICE_2G_INCTRM_TRAF
Name Description

8-31
Name Description
MBTO14 Count of mobile callee trunk resource overflow
MAF14 Count of mobile callee traffic channel allocations failures
MNR14 Count of MS unavailable
MDB14 Count of mobile callee determined busy
ANSR14 Answer rate

I. Entity Name
CA14
II. Description
It is the count of incoming trunk call attempts in which the callees are found out to be the
local MSs.
It is measured when the MSC confirms the callee is an MS according to the MSRN of
the callee. See point A in the following figure.

8-32
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ABR14
II. Description
It is the count of active releases by the callers before calls are connected.
It is measured when the MSC receives the call release message from a mobile caller
before the call is connected. See point A in the following figure.

8-33
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
REL

IV. Formula
None
I. Entity Name
TAF14
II. Description

8-34
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
REL
DTAP Disconnect

IV. Formula
None
I. Entity Name
CRU14
II. Description

8-35
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
REL
DTAP Disconnect

IV. Formula
None
I. Entity Name
CB14
II. Description
It is the count of incoming call connections failed because the mobile callees are busy
(in session).
After getting the MSRN from the HLR, the MSC sends the message send info for
incoming/outgoing call to the VLR. The VLR returns a message to indicate that the
callee is busy, and then the MSC begins the measurement. See point A in the following
figure.

8-36
A
BSC
IAM
DTAP SETUP
When the MSC obtains the
MSRN, and the VLR returns a
message indicating callee busy.

IV. Formula
None
8.4.7 Count of Mobile Callee Trunk Resource Overflow
I. Entity Name
MBTO14
II. Description
It is the count of times when resources are unavailable for the incoming calls.
It is measured when the MSC fails to allocate an A interface circuit for the callee. See

8-37
A
BSC
IAM
DTAP SETUP
A interface circuits
allocation failure
DTAP ALERTING
A

IV. Formula
None
8.4.8 Count of Mobile Callee Traffic Channel allocations Failures
I. Entity Name
MAF14
II. Description
for the mobile callees in the incoming calls.
It is measured when the MSC receives the BSSMAP ASSIGN FAILURE from the BSC.
Or it is measured at the timeout of the assignment timer. See point A in the following
figure.

8-38
A
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
Called traffic channels
allocation failure

IV. Formula
None
8.4.9 Count of MS Unavailable
I. Entity Name
MNR14
II. Description
It is the count of failed incoming call connections due to the paging failures.
It is measured when the MSC does not receive the Paging Response message from
the BSC of the mobile callee after sending the BSSMAP Paging message to the BSC in
an incoming call. See point A in the following figure.

8-39
A
A
BSC
Mobile subscriber
unreachable
DTAP SETUP
DTAP PAGING
DTAP PAGING_RSP

IV. Formula
None
I. Entity Name
ALT14
II. Description
It is the count of messages indicating that the calls are connected.
It is measured when the MSC receives the DTAP Alerting message in an incoming call.

8-40
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
AAR14
II. Description
It is the count of active releases by the fixed-line callers before the mobile callees
pickup the phones in the incoming calls.
After receiving the DTAP Alerting message from the mobile callee, the MSC sends
ringback tone to the caller. Before receiving the Connect message from the mobile
callee, the MSC receives the REL message from the caller. The measurement begins.

8-41
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
REL
DTAP PAGING_RSP
ACM
DTAP CONNECT

IV. Formula
None
I. Entity Name
RNA14
II. Description
timeout.
It is measured when the MSC releases the call due to no DTAP Alerting message
received from the callee in a valid period after the DTAP Alerting message. See

8-42
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
DTAP PAGING_RSP
ACM
DTAP CONNECT
DTAP DISCONNECT

It is measured when the MSC releases the call after receiving the DTAP Connect
and DTAP Disconnect messages from the callee. The cause value in DTAP
Disconnect message is 146 (CV_NO_RESPOND) or 147
(CV_NO_ACKNOWLEGE). See point A in the following figure.
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
DTAP PAGING_RSP
ACM
DTAP CONNECT
DTAP DISCONNECT
ANM/ANC

IV. Formula
None

8-43
8.4.13 Count of Mobile Callee Determined Busy
I. Entity Name
MDB14
II. Description
It is the count of incoming calls directly rejected by the mobile callees after the ringing.
It is measured when the MSC receives the DTAP Disconnect message from the callee
after the ringing. See point A in the following figure.
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
DTAP PAGING_RSP
ACM
DTAP CONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
ANS14
II. Description
It is the count of incoming calls answered by the mobile callees.
It is measured when the MSC sends the ANM to the originating office after receiving the
DTAP Connect message from the mobile callee. See point C in the following figure.

8-44
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
SU14
II. Description
It is the traffic generated during the incoming call attempts.
It is measured from the moment the IAM or IAI message is received to that the REL
message is received. The final result is indicated in Erlang. (ITU-T Rec. Q.722). Point A
in the following figure is the start point of the measurement and call release is the end
point.

8-45
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ALTU14
II. Description
It is the traffic generated when incoming calls are in the connected status.
It is measured from the moment the DTAP Alerting message is received from the callee
to that the REL message is received. The final result is indicated in Erlang (ITU-T Rec.
Q.722). Point B in the following figure is the start point of the measurement and call
release is the end point.

8-46
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ANSU14
II. Description
It is the traffic generated when incoming calls are in the answered status.
It is measured from the moment the Answer signal message is received from the callee
Q.722). Point C in the following figure is the start point of the measurement and call

8-47
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ALTR14
II. Description
It is calculated on the BAM.
IV. Formula
ALTR14 = ALT14/CA14
8.4.19 Answer Rate
I. Entity Name
ANSR14
II. Description

8-48
IV. Formula
ANSR14 = ANS14/CA14
8.5 MS-Terminated Traffic
8.5.1 Overview of MS_OFFICE_2G_TRM_TRAF
Name Description
ANSR19 Answer rate

I. Entity Name
CA19

8-49
II. Description
It is the count of call attempts in which the callees are local MSs.
It is measured after the VDB checks whether the number carried in the message is a
MSRN and before the Paging message is sent. At the same time, the MSC resets the
indicator. The callee may be in the local MSC or in another one. See point A in the
following figure.
BSC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
Incoming IAM or local SETUP
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
TAF19
II. Description
It is the count of Termination preparation failures on the MGW in 2G mobile terminated
calls.
It is measured when the MSC fails to apply for the internal common resources in an 2G
mobile terminated call. The callee may be in the local MSC or in another one. See point
A in the following figure.

8-50
BSC MSC Server
DTAP ALERTING
A
XXX
REL / DTAP DISCONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
CRU19
II. Description
including the IWF, bill pool, and control table resources.
It is measured when the MSC fails to apply and use internal common resources. The
callee may be in the local MSC or in another one. See point A in the following figure.

8-51
BSC MSC Server
DTAP ALERTING
A
XXX
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
CB19
II. Description
It is the count of call connections failed because 2G callees are busy.
The callee may be in the local MSC or in another one. See point A in the following
figure.

8-52
BSC MSC Server
A
XXX
DTAP SETUP
The MSC obtains the MSRN, and
the VLR returns a message
indicating callee busy.

IV. Formula
None
I. Entity Name
MBTO19
II. Description
It is the count of failed local MSs terminated calls due to all trunks busy on the interface
A.
BSSMAP ASSIGN REQUEST message to the BSS of the mobile callee. The callee
may be in the local MSC or in another one. See point A in the following figure.

8-53
BSC MSC Server
A
XXX
DTAP SETUP
Trunk resource overflow
DTAP ALERTING

IV. Formula
None
I. Entity Name
MAF19
II. Description
for the mobile callees.
It is measured when the MSC receives the ASSIGN FAILURE message from the BSC
of the mobile callee after sending the BSSMAP ASSIGN REQUEST message to this
BSC. The allocation includes advanced allocation and delayed allocation. Or it is
measured at the timeout of the assignment timer. The callee may be in the local MSC or
in another one. See point A in the following figure.

8-54
BSC MSC Server
A
XXX
DTAP SETUP
allocation failure
DTAP ALERTING

IV. Formula
None
I. Entity Name
MNR19
II. Description
It is measured when the MSC does not receive the Paging Response message after
sending the Paging message to the RNC or BSC of the mobile callee in an incoming
call. The callee may be in the local MSC or in another one. See point A in the following
figure.

8-55
BSC MSC Server
A
XXX
DTAP PAGING
DTAP PAGING_RSP
Mobile subscriber
unreachable

IV. Formula
None
I. Entity Name
ALT19
II. Description
It is the count of DTAP Alerting messages received from the callees in the incoming 2G
calls.
It is measured when the MSC receives the DTAP ALERTING message from the mobile
callee. The callee may be in the local MSC or in another one. See point B in the
following figure.

8-56
BSC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
AAR19
II. Description
It is the count of active releases by the callers before the mobile callees pickup the
phones in the 2G incoming calls.
It is measured when the caller hooks on after the MSC receives the DTAP Altering
message but not the Connect message from the mobile callee. The callee may be in
the local MSC or in another one. See point A in the following figure.

8-57
BSC MSC Server
DTAP ALERTING
DTAP SETUP
XXX
ACM / DTAP ALERTING
A
DTAP CONNECT
RLC / DTAP RELEASE

IV. Formula
None
I. Entity Name
RNA19
II. Description
It is the count of incoming calls not answered by the 2G mobile callees till timeout.
It is measured when the MSC releases the call due to no DTAP Connect message
received from the callee in a valid period after the DTAP Alerting message. The callee
may be in the local MSC or in another one. See point A in the following figure.

8-58
BSC MSC Server
DTAP ALERTING
DTAP SETUP
XXX
ACM / DTAP ALERTING
A
DTAP CONNECT
DTAP DISCONNECT
DTAP RELEASE
Long time no reply

IV. Formula
None
I. Entity Name
MDB19
II. Description
It is the count of incoming calls directly rejected by the 2G mobile callees after the
ringing.
after the ringing. The callee may be in the local MSC or in another one. See point A in

8-59
BSC MSC Server
DTAP ALERTING
DTAP SETUP
XXX
ACM / DTAP ALERTING
A
DTAP CONNECT
DTAP DISCONNECT(CV_BUSY/
CV_USR_BUSY)
DTAP RELEASE

IV. Formula
None
I. Entity Name
ANS19
II. Description
It is the count of incoming calls answered by the 2G mobile callees.
It is measured when the MSC receives the DTAP Connect message from the mobile
callee. The callee may be in the local MSC or in another one. See point C in the
following figure.

8-60
BSC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
SU19
II. Description
It is the traffic generated during the incoming call attempts in which the callees are MSs.
It measures the interval between relevant messages in a measurement period. In
internal MSC call connection, if the CM in the NSS is in the call originated status
(CM_MM_CONNECTION), the MSC begins the measurement. The measurement
stops when the CM shifts to idle state after the call is released. The final result is
indicated in Erlang (3GPP TS 25.413, GSM 08.08).
The callee may be in the local MSC or in another one. Point A in the following figure is
the start point of the measurement and call release is the end point.

8-61
BSC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
ALTU19
II. Description
It is the traffic generated when incoming calls terminated by MSs are in the connected
released.
It measures the interval between relevant messages in a measurement period. For
GSM system, the MSC begins the measurement from the moment the MSC receives
the DTAP Alerting message to that the CLEAR COMMAND message is received. The
final result is indicated in Erlang (3GPP TS 24.008, 3GPP TS25.413, GSM08.08).
The callee may be in the local MSC or in another one. Point B in the following figure is

8-62
BSC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
ANSU19
II. Description
It is the traffic generated when incoming calls terminated by MSs are in the connected
status. The measurement begins from the moment the call is answered to that the call
is released.
GSM system, the MSC begins the measurement from the moment the MSC receives
the CONNECT ACKNOWLEDGE message to that the CLEAR COMMAND message is
received. The final result is indicated in Erlang (3GPP TS 24.008, 3GPP TS25.413,
GSM08.08).
The callee may be in the local MSC or in another one. Point C in the following figure is

8-63
BSC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
ALTR19
II. Description
IV. Formula
ALTR19 = ALT19/CA19
8.5.18 Answer Rate
I. Entity Name
ANSR19
II. Description

8-64
IV. Formula
ANSR19 = ANS19/CA19
8.6 3G VP Subscriber Originated Traffic
8.6.1 Overview of MS_VP_3G_ORG_TRAF
This section includes the following entities: UE VP calls, call attempts, connected calls,
answered calls, and traffic. The parameter protocols include 3GPP TS26110 and 3GPP
TS 26111.
Name Description
CA196 Count of VP call attempts
ALT196 Count of VP connected calls
ANS196 Count of VP answered calls
BNS196 Count of failures due to bearer capability
AU196 VP connected traffic
ANU196 VP answered traffic
AR196 VP call completion rate
ANR196 VP answer rate

8.6.2 Count of VP Call Attempts
I. Entity Name
CA196
II. Description
It is the count of VP call attempts originated by the local MSs.
It is measured when the MSC finds that the BC in the caller data received is multimedia
BC. See point A in the following figure.

8-65
SETUP
O_UE MSC Server
A
SubscriberPara
VLR
B
CONNECT
C
CONNECT ACK
ALERTING
CALL PROCEEDING

IV. Formula
None
8.6.3 Count of VP Connected Calls
I. Entity Name
ALT196
II. Description
It is the count of connected VP calls originated by the local MSs.
It is measured when the call switches to the CM_CALL_DELIVERED state after the
O_UE receives the ALERTING/ACM message in an outgoing mobile caller VP call. See
point B in the following figure.

8-66
SETUP
O_UE MSC Server
A
SubscriberPara
VLR
B
CONNECT
C
CONNECT ACK
ALERTING
CALL PROCEEDING

IV. Formula
None
8.6.4 Count of VP Answered Calls
I. Entity Name
ANS196
II. Description
It is the count of answered VP calls originated by the local MSs.
It is measured when the call switches to the CALL CONNECT IND state after the O_UE
receives the CONNECT/ANM message in an outgoing mobile caller VP call. See point
C in the following figure.

8-67
SETUP
O_UE MSC Server
A
SubscriberPara
VLR
B
CONNECT
C
CONNECT ACK
ALERTING
CALL PROCEEDING

IV. Formula
None
8.6.5 Count of Failures Due to Bearer Capability
I. Entity Name
BNS196
II. Description
It is the count of failed outgoing mobile caller VP calls due to no bearer services
registered.
It is measured when the MSC receives the REL message from the MAP for a call
started by a local MS with the release reason of no bearer capability.
SETUP
O_UE MSC Server
A
RELEASE
VLR

IV. Formula
None

8-68
I. Entity Name
SU196
II. Description
It is the traffic generated from the start of outgoing VP call attempts initiated by local
MSs to the releases.
It is measured from when the MSC finds that the BC in the caller data received is
multimedia BC until the call is released. The unit is Erlang.
IV. Formula
None
8.6.7 VP Connected Traffic
I. Entity Name
AU196
II. Description
It is the traffic generated when VP calls initiated by the local MSs are in the connected
status.
The MSC begins the measurement from the moment it receives the DTAP Alerting or
ACM message to that the call is released. The unit is Erlang.
IV. Formula
None
8.6.8 VP Answered Traffic
I. Entity Name
ANU196
II. Description
It is the traffic generated when VP calls initiated by local MSs are in the answered
status.

8-69
The MSC begins the measurement from the moment it receives the DTAP Connect or
ANM message to that the call is released. The unit is Erlang.
IV. Formula
None
8.6.9 VP Call Completion Rate
I. Entity Name
AR196
II. Description
VP call completion rate = Count of VP connected calls/Count of VP call attempts
IV. Formula
AR196 = ALT196/CA196.
8.6.10 VP Answer Rate
I. Entity Name
ANR196
II. Description
VP answer rate = Count of VP answered calls/Count of VP call attempts
IV. Formula
ANR196 = ANS196/CA196
8.7 3G VP Subscriber Terminated Traffic
8.7.1 Overview of MS_VP_3G_TRM_TRAF
This section includes the following entities: UE VP calls, call attempts, connected calls,
answered calls, and traffic. The parameter protocols include 3GPP TS26110 and 3GPP
TS 26111.

8-70
Name Description
CA197 Count of VP call attempts
ALT197 Count of VP connected calls
ANS197 Count of VP answered calls
BNS197 Count of failures due to bearer capability
AU197 VP connected traffic
ANU197 VP answered traffic
AR197 VP call completion rate
ANR197 VP answer rate

8.7.2 Count of VP Call Attempts
I. Entity Name
CA197
II. Description
It is the count of incoming VP call attempts.
It is measured when the MSC finds that the BC in the caller data or the
CALL-CONFIRM message received is multimedia BC. See point A in the following
figure.

8-71
SETUP
T_UE MSC Server
A
B
CONNECT
C
CONNECT ACK
ALERTING
CALL CONFIRMED

IV. Formula
None
8.7.3 Count of VP Connected Calls
I. Entity Name
ALT197
II. Description
It is the count of connected incoming VP calls.
It is measured when the MSC receives the ALERTING message from the MS in an
incoming VP call. See point B in the following figure.

8-72
SETUP
T_UE MSC Server
A
B
CONNECT
C
CONNECT ACK
ALERTING
CALL CONFIRMED

IV. Formula
None
8.7.4 Count of VP Answered Calls
I. Entity Name
ANS197
II. Description
It is the count of answered incoming VP calls.
It is measured when the MSC receives the CONNECT message from the MS in an
incoming VP call. See point C in the following figure.

8-73
SETUP
T_UE MSC Server
A
B
CONNECT
C
CONNECT ACK
ALERTING
CALL CONFIRMED

IV. Formula
None
8.7.5 Count of Failures Due to Bearer Capability
I. Entity Name
BNS197
II. Description
It is the count of failed incoming VP calls due to no bearer services registered.
It is measured when the MSC receives the REL message from the MAP or the caller
with the release reason of no bearer capability.
PAGE RESPONSE
T_UE MSC Server
A
RELEASE
VLR/O_UE

IV. Formula
None

8-74
I. Entity Name
SU197
II. Description
It is the traffic generated during the incoming VP call attempts.
It is measured from when the MSC finds that the BC in the caller data or the
CALL-CONFIRM message received is multimedia BC until the call is released. The unit
is Erlang.
IV. Formula
None
8.7.7 VP Connected Traffic
I. Entity Name
AU197
II. Description
It is the traffic generated when incoming VP calls are in the connected status.
The MSC begins the measurement from the moment it receives the DTAP Alerting
message from the MS to that the call is released. The unit is Erlang.
IV. Formula
None
8.7.8 VP Answered Traffic
I. Entity Name
ANU197
II. Description
It is the traffic generated when incoming VP calls are in the answered status.
The MSC begins the measurement from the moment it receives the DTAP Connect
message from the MS to that the call is released. The unit is Erlang.

8-75
IV. Formula
None
8.7.9 VP Call Completion Rate
I. Entity Name
AR197
II. Description
VP call completion rate = Count of VP connected calls/Count of VP call attempts
IV. Formula
AR197 = ALT197/CA197.
8.7.10 VP Answer Rate
I. Entity Name
ANR197
II. Description
VP answer rate = Count of VP answered calls/Count of VP call attempts
IV. Formula
ANR197 = ANS197/CA197
8.8 UE-Originated Outgoing Traffic
8.8.1 Overview of MS_OFFICE_3G_ORGOUT_TRAF
Name Description

8-76
Name Description
TO11 Count of outgoing trunk overflow
EC11 Count of peer office congestions
ANSR11 Answer rate

I. Entity Name
CA11
II. Description
It is the count of call attempts initiated by the RNS and found to be outgoing ones
After the RNC initiates a call, the MSC analyzes the called number. After confirming the
call is an outgoing one, the MSC begins the measurement. See point A in the following
figure.

8-77
RNC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
I. Entity Name
WDN11
II. Description
It is the count of call connection failures due to wrong numbers dialed by mobile callers.
It is measured when the MSC receives the ADI or UNN message (TUP). See point

8-78
ACM
DTAP SETUP
IAM
A
REL
RLC
RNC

It is measured when the number dialing time exceeds the time set on the internal
timer of the MSC. See point A in the following figure.
RNC
ACM
DTAP SETUP
IAM
A
REL
RLC

It is measured when the MSC receives the REL message from the terminating
office. The cause value in the message is 129 (unallocated number) or 156
(incomplete number). See point A in the following figure.

8-79
ACM
DTAP SETUP
IAM
A
REL
RLC
RNC

IV. Formula
None
I. Entity Name
ABR11
II. Description
It is the count of mobile caller releases before the callees' phones ring (the callee may
be either a non-local PSTN or mobile subscriber).

8-80
RNC
ACM
DTAP SETUP
IAM
A REL
RLC
DTAP
Disconnect

IV. Formula
None
I. Entity Name
TAF11
II. Description

8-81
MSC Server
MSC Server
RNC
ACM
DTAP SETUP
IAM
A
REL
DTAP Disconnect

IV. Formula
None
I. Entity Name
CRU11
II. Description

8-82
MSC Server
MSC Server
RNC
ACM
DTAP SETUP
IAM
A
REL
DTAP Disconnect

IV. Formula
None
8.8.7 Count of Outgoing Trunk Overflow
I. Entity Name
TO11
II. Description
calls.

8-83
MSC Server
MSC Server
RNC
DTAP SETUP
IAM
A
Outgoing trunk
overflow

IV. Formula
None
I. Entity Name
EC11
II. Description
situation.
The peer office is congested.

8-84
RNC
ACM
DTAP SETUP
IAM
A
DTAP Disconnect

IV. Formula
None
I. Entity Name
CB11
II. Description
It is the count of call connections failed because callees are busy in the outgoing calls.
It is measured when the MSC receives the STB, SLB (TUP), or REL (ISUP) message
from the terminating office in an outgoing call. See point A in the following figure.

8-85
RNC
ACM
DTAP SETUP
IAM
A
REL
RLC
DTAP Disconnect

IV. Formula
None
I. Entity Name
ALT11
II. Description
It is the count of DTAP Alerting messages sent to the callers in the outgoing calls.
It is measured when the MSC sends the DTAP Alerting message to a mobile caller after
receiving the ACM. See point B in the following figure.

8-86
RNC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
I. Entity Name
AAR11
II. Description
It is the count of active releases by mobile callers before the pickup.
caller before the callee picks up the phone. See point A in the following figure.

8-87
RNC
ACM
DTAP SETUP
IAM
A
REL
DTAP Disconnect
DTAP ALERTING
ANM/ANC

IV. Formula
None
I. Entity Name
RNA11
II. Description
timeout.
1) It is measured when the MSC releases the call due to no DTAP Connect message
received from the callee in a valid period after the ACM.

8-88
RNC
ACM
DTAP SETUP
IAM
A
REL
DTAP ALERTING
RLC
ANM/ANC

2) It is measured when the MSC releases the call after receiving the ACM and REL
messages from the callee. The cause value in REL message is 146
(CV_NO_RESPOND) or 147 (CV_NO_ACKNOWLEGE).
RNC
ACM
DTAP SETUP
IAM
A
REL
DTAP ALERTING
RLC
ANM/ANC

IV. Formula
None
I. Entity Name
ANS11

8-89
II. Description
When receiving the ANC or ANN message, the MSC sends the DTAP Connect
message to the mobile caller. After receiving the DTAP Connect ACK message from
the mobile caller, the MSC begins the measurement. See point C in the following figure.
RNC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
I. Entity Name
SU11
II. Description
to the moment the REL message is sent. The final result is indicated in Erlang (ITU-T
Rec. Q.722). Point A in the following figure is the start point of the measurement and
call release is the end point.

8-90
RNC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
I. Entity Name
ALTU11
II. Description
the REL message is sent. The final result is indicated in Erlang (ITU-T Rec. Q.722).
Point B in the following figure is the start point of the measurement and call release is
the end point.

8-91
RNC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
I. Entity Name
ANSU11
II. Description
It is the traffic generated when outgoing calls are in answered status.
MSC to that the REL message is sent. The final result is indicated in Erlang (ITU-T Rec.
Q.722). Point C in the following figure is the start point of the measurement and call

8-92
RNC
ACM
DTAP SETUP
IAM
DTAP ALERTING
DTAP CONNECT
A
B
C
REL
REL
DTAP Connect Ack
ANM/ANC

IV. Formula
None
I. Entity Name
ALTR11
II. Description
IV. Formula
ALTR11 = ALT11/CA11
8.8.18 Answer Rate
I. Entity Name
ANSR11
II. Description

8-93
IV. Formula
ANSR11 = ANS11/CA11
8.9 UE-Originated Traffic
8.9.1 Overview of MS_OFFICE_3G_ORG_TRAF
Name Description
MAF4 Count of mobile caller authentication failures
MSCF4 Count of mobile caller ciphering mode setting failures
MB4 Count of mobile caller barring
MBTO4 Count of mobile caller trunk resource overflow
MASF4 Count of mobile caller traffic channel allocations failures
SNB4 Count of terminal application failures
SU4 Seizure traffic
AU4 Connected traffic
ANU4 Answered traffic
AR4 Call completion rate
ANR4 Answer rate
ID4 Count of callee power-off

I. Entity Name
CA4
II. Description
It is the count of call attempts originated by UEs, regardless of the terminating MSCs.

8-94
It is measured when the MSC confirms that it is a mobile originating call or an
emergency call after receiving a layer-3 CM Service Request message.
IV. Formula
None
8.9.3 Count of Mobile Caller Authentication Failures
I. Entity Name
MAF4
II. Description
It is the count of failed calls originated by the UEs in the local MSC due to
authentication failures.
1) When receiving the AUTHENTICATION_RESPONSE message from the MS, the
MSC checks whether the XRES or SRES (for GSM network) is correct. If not, the
MSC returns a CM Service Reject message, and the measurement begins.
2) It is measured when the MSC does not receive the
AUTHENTICATION_RESPONSE message from the MS in a valid period.
3) It is measured when the MS returns the respond message which carries MAC
failure or synchronization failure.
IV. Formula
None
8.9.4 Count of Mobile Caller Ciphering Mode Setting Failures
I. Entity Name
MSCF4
II. Description
It is the count of failed calls originated by UEs due to ciphering mode setting failures.
It is measured when the MSC receives the SECURITY MODE REJECT message from
the RNC after sending the SECURITY MODE COMMAND message to the RNC.
IV. Formula
None

8-95
8.9.5 Count of Mobile Caller Barring
I. Entity Name
MB4
II. Description
It is the count of failed calls due to the bearer capability or originating UE service
restriction, such as Bearer service not provisioned, Teleservice not provisioned, or
BAOC.
It is measured when the call is released due to the restriction of the service subscribed
by the caller.
SETUP
O_UE MSC Server
A
RELEASE
VLR
RELEASE COMPLETE

IV. Formula
None
8.9.6 Count of Mobile Caller Trunk Resource Overflow
I. Entity Name
MBTO4
II. Description
It is the count of failed calls originated by UEs due to Prepare Bearer failures on the
MGW.
RAB ASSIGN REQUEST message to the RNC of the mobile caller. See point A in the
following figure.

8-96
SETUP
O_RNC MSC Server MGW
A
PREPARE BEARER REQ
PREPARE BEARER RSP
A1

IV. Formula
None
8.9.7 Count of Mobile Caller Traffic Channel allocations Failures
I. Entity Name
MASF4
II. Description
for originating UEs in the incoming calls.
It is measured when the MSC receives the ASSIGN FAILURE message from the RNC
of the mobile caller after sending the RAB ASSIGN REQUEST message to this RNC.
The allocation includes advanced allocation and delayed allocation.

8-97
RAB ASSIGNMENT REQUEST
O_RNC MSC Server
RAB ASSIGNMENT RESPONSE
A

IV. Formula
None
I. Entity Name
WDN4
II. Description
It is the count of wrong numbers dialed by UEs, including the following three cases.
The MSC fails to analyze the called number because the number is incomplete
and cannot be determined.
After confirming that the called number is MSISDN, the MSC fails to obtain the
routing information from the HLR. The callee location is unknown.
The MSC obtains the outgoing routing from the HLR, however, the terminating
office returns the ADI (invalid address), UNN (unallocated number, TUP), or REL
(unallocated number, incomplete number, ISUP) message.
The MSC fails to analyze the called number and the destination is unknown.
The MSC receives the Routing Failure message from the MAP.
The MSC receives the ADI, UNN (TUP) or REL (ISUP) message from the
terminating office in an outgoing call.
IV. Formula
None

8-98
I. Entity Name
ABR4
II. Description
It is the count of active releases by the local UEs before the callees phones ring.
It is measured when the MSC receives the DTAP Disconnect, DTAP RELEASE, or
DTAP RELEASE COMPLETE message from a mobile caller before the call is
connected.
O_UE MSC Server
A
DISCONNECT / RELEASE
/ RELEASE COMPLETE
SETUP
Before ALERTING

IV. Formula
None
I. Entity Name
SNB4
II. Description
It is the count of failed calls originated by the UEs. The calls fail due to the Prepare
Bearer failures on the MGW.
MGW. The message contains failure information. See point A1 in the following figure.

8-99
SETUP
O_RNC MSC Server MGW
A
PREPARE BEARER REQ
PREPARE BEARER RSP
A1

IV. Formula
None
I. Entity Name
CRU4
II. Description
It is measured when the MSC fails to apply and use internal common resources.
IV. Formula
None
I. Entity Name
ALT4
II. Description
It is the count of DTAP Alerting messages sent to the O_UEs in the outgoing calls.
after receiving the ACM from the terminating office in an inter-office call. It is measured

8-100
when the MSC sends the DTAP Alerting message to the mobile caller after receiving
the DTAP Alerting message from the mobile callee in an intra-office call.
ALERTING
O_UE MSC Server
A
CONNECT
B
CONNECT ACK
ACM
ANM

IV. Formula
None
I. Entity Name
ANS4
II. Description
It is the count of incoming UE-originated calls answered.
In an outgoing call, when receiving the ANC/ANN (TUP) or ANM (ISUP) message from
the terminating office, the MSC sends the DTAP Connect message to the mobile caller
and begins the measurement. See point B in the following figure.

8-101
ALERTING
O_UE MSC Server
A
CONNECT
B
CONNECT ACK
ACM
ANM

IV. Formula
None
I. Entity Name
SU4
II. Description
It is the traffic generated from originating UE starting call attempt to call release.
In internal MSC call connection, if the CM is in the call originated status
(CM_CALL_ORIGINATED), the MSC begins the measurement. The measurement
stops when the CM shifts to idle state after the call is released.
IV. Formula
None
I. Entity Name
AU4
II. Description
It is the traffic generated when incoming calls initiated by the UEs are in the connected
released.

8-102
It is measured from the moment the DTAP Alerting message is received to that the IU
RELEASE COMMAND message is received. The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
ANU4
II. Description
It is the traffic generated when incoming calls initiated by UEs are in the connected
status. The measurement begins from the moment the call is answered to that the call
is released.
It measures the interval between relevant messages in a measurement period. The
MSC begins the measurement from the moment the message CONNECT
ACKNOWLEDGE is received to that the message IU RELEASE COMMAND is sent.
The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
AR4
II. Description
Call completion rate = Count of connected calls/Count of call attempts
IV. Formula
AR4 = ALT4/CA4

8-103
8.9.18 Answer Rate
I. Entity Name
ANR4
II. Description
IV. Formula
ANR4 = ANS4/CA4
I. Entity Name
ID4
II. Description
callees power-off.
IV. Formula
None
8.10 UE-Terminated Incoming Traffic
8.10.1 Overview of MS_OFFICE_3G_INCTRM_TRAF
Name Description

8-104
Name Description
ANSR15 Answer rate

I. Entity Name
CA15
II. Description
It is the count of incoming call attempts in which the callees are found to be local UEs
during called number analysis stage in MSC.
It is measured when the MSC confirms the callee is a UE according to the MSRN of the
callee. See point A in the following figure.

8-105
A
RNC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ABR15
II. Description
It is the count of active releases by the callers before calls are connected.
It is measured when the MSC receives the call release message from a caller before
the call is connected. See point A in the following figure.

8-106
A
RNC
IAM
DTAP SETUP
DTAP ALERTING
REL

IV. Formula
None
I. Entity Name
TAF15
II. Description

8-107
A
RNC
IAM
DTAP SETUP
DTAP ALERTING
REL
DTAP Disconnect

IV. Formula
None
I. Entity Name
CRU15
II. Description

8-108
A
RNC
IAM
DTAP SETUP
DTAP ALERTING
REL
DTAP Disconnect

IV. Formula
None
I. Entity Name
CB15
II. Description
It is the count of incoming calls failed because mobile callees are busy (in session).
incoming call to the VLR. The VLR returns a message to indicate that the callee is busy,
and then the MSC begins the measurement. See point A in the following figure.

8-109
A
RNC
IAM
DTAP SETUP
The MSC obtains the MSRN,
and the VLR returns a message

IV. Formula
None
I. Entity Name
MAF15
II. Description
for mobile callees in the incoming calls.
It is measured when the MSC receives the RAB ASSIGNMENT RESP (assignment
failure) message from the RNC. Or it is measured at the timeout of the assignment
timer. See point A in the following figure.

8-110
A
A
RNC
IAM
DTAP SETUP
DTAP
ALERTING
allocation failure

IV. Formula
None
I. Entity Name
MNR15
II. Description
sending the Paging message to the RNC of the mobile callee in an incoming call. See

8-111
A
A
RNC
Mobile subscriber
unreachable
DTAP SETUP
DTAP PAGING
DTAP PAGING_RSP

IV. Formula
None
I. Entity Name
ALT15
II. Description
It is the count of messages indicating that the calls are connected.
It is measured when the MSC receives the DTAP Alerting message in an incoming call.

8-112
A
RNC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
AAR15
II. Description
It is the count of active releases by fixed-line callers before the mobile callees pickup
the phones in the incoming calls.
After receiving the DTAP Alerting message from the mobile callee, the MSC sends the
ringback tone to the fixed-line caller. Before the mobile callee sends the Connect
message, the originating office sends the REL message. The MSC begins the
measurement. See point A in the following figure.

8-113
A
RNC
IAM
DTAP SETUP
DTAP ALERTING
REL
DTAP PAGING_RSP
ACM
DTAP CONNECT

IV. Formula
None
I. Entity Name
RNA15
II. Description
It is the count of incoming calls not answered by the mobile callees till timeout.
received from the callee in a valid period after the DTAP Alerting message. See point A
in the following figure.

8-114
A
RNC
IAM
DTAP SETUP
DTAP ALERTING
DTAP PAGING_RSP
ACM
DTAP CONNECT
DTAP DISCONNECT

It is measured when the MSC releases the call after receiving the DTAP Connect and
DTAP Disconnect messages from the callee. The cause value in DTAP Disconnect
message is 146 (CV_NO_RESPOND) or 147 (CV_NO_ACKNOWLEGE). See point A
A
BSC
IAM
DTAP SETUP
DTAP ALERTING
DTAP PAGING_RSP
ACM
DTAP CONNECT
DTAP DISCONNECT
ANM/ANC

IV. Formula
None
I. Entity Name
MDB15

8-115
II. Description
A
RNC
IAM
DTAP SETUP
DTAP ALERTING
DTAP PAGING_RSP
ACM
DTAP CONNECT
DTAP DISCONNECT

after the ringing. See point A in the following figure. The value of the message is
CV_USER_BUSY or CV_BUSY.
IV. Formula
None
I. Entity Name
ANS15
II. Description
It is the count of incoming calls answered by the mobile callees.
It is measured when the MSC sends the ANM to the originating office after receiving the
DTAP Connect message from the mobile callee. See point C in the following figure.

8-116
A
RNC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
SU15
II. Description
message is received. The final result is indicated in Erlang (ITU-T Rec. Q.722).
Point A in the following figure is the start point of the measurement and call release is
the end point.

8-117
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ALTU15
II. Description
It is the traffic generated when incoming calls are in the connected status.
It is measured from the moment the DTAP Alerting message is received from the callee
Q.722).
the end point.

8-118
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ANSU15
II. Description
It is the traffic generated when incoming calls are in answered status.
Q.722).
Point C in the following figure is the start point of the measurement and call release is
the end point.

8-119
A
BSC
c
IAM
DTAP SETUP
DTAP ALERTING
DTAP CONNECT
B ACM
ANM/ANC

IV. Formula
None
I. Entity Name
ALTR15
II. Description
IV. Formula
ALTR15 = ALT15/CA15
8.10.18 Answer Rate
I. Entity Name
ANSR15
II. Description

8-120
IV. Formula
ANSR15 = ANS15/CA15
8.11 UE-Terminated Traffic
8.11.1 Overview of MS_OFFICE_3G_TRM_TRAF
Name Description
ANSR20 Answer rate

I. Entity Name
CA20

8-121
II. Description
It is the count of call attempts in which the callees are found out to be the local UEs.
It is measured when the MSC receives the DTAP PAGING RSP message. At the same
time, the MSC resets the indicator. The callee may be in the local MSC or in another
one. See point A in the following figure.
RNC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
TAF20
II. Description
It is measured when the MGW prepares the trunk resource after receiving the
BEARER_INFO message in a 3G terminated call. The callee may be in the local MSC
or in another one. See point A in the following figure.

8-122
RNC MSC Server
DTAP ALERTING
A
XXX
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
CRU20
II. Description
It is measured when the MSC fails to apply and use internal common resources. The

8-123
RNC MSC Server
DTAP ALERTING
A
XXX
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
CB20
II. Description
It is the count of call connections failed because callees are busy.
incoming/outgoing call setup to the VLR. The VLR returns a message to indicate that
the callee (no CF service) is busy, and then the MSC begins the measurement. The

8-124
RNC MSC Server
A
XXX
DTAP SETUP
The MSC obtains the MSRN,
and the VLR returns a message

IV. Formula
None
I. Entity Name
MBTO20
II. Description
It is the count of times of failed terrestrial channel allocations for terminating UEs.
RAB ASSIGN REQUEST message to the RNC of the mobile callee. The callee may be
in the local MSC or in another one. See point A in the following figure.

8-125
RNC MSC Server
A
XXX
DTAP SETUP
allocation failure
DTAP ALERTING

IV. Formula
None
I. Entity Name
MAF20
II. Description
for the UEs.
It is measured when the MSC receives the ASSIGN FAILURE message from the RNC
of the mobile callee after sending the RAB ASSIGN REQUEST message to this RNC.
The allocation includes advanced allocation and delayed allocation. Or it is measured
at the timeout of the assignment timer. The callee may be in the local MSC or in another
one. See point A in the following figure.

8-126
RNC MSC Server
A
XXX
DTAP SETUP
allocation failure
DTAP ALERTING

IV. Formula
None
I. Entity Name
MNR20
II. Description
It is the count of failed call connections due to the MSs unavailable.
sending the Paging message to the RNC or BSC of the mobile callee in a call. The

8-127
RNC MSC Server
A
XXX
DTAP PAGING
DTAP PAGING_RSP
Mobile subscriber
unreachable

IV. Formula
None
I. Entity Name
ALT20
II. Description
It is the count of DTAP Alerting messages received from the 3G callees in the incoming
calls.
It is measured when the MSC receives the DTAP Alerting message. It is measured
when the status of the CM is CM_CALL_RECEIVED. The callee may be in the local
MSC or in another one. See point B in the following figure.

8-128
RNC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
AAR20
II. Description
It is the count of active releases by non-local callers before the mobile callees pickup in
3G incoming calls.
It is measured when the caller hooks on after the MSC receives the DTAP Altering
message but not the Connect message from the mobile callee. The callee may be in
the local MSC or in another one. See point B in the following figure.

8-129
RNC MSC Server
DTAP ALERTING
DTAP SETUP
XXX
ACM / DTAP ALERTING
A
DTAP CONNECT
RLC / DTAP RELEASE

IV. Formula
None
I. Entity Name
RNA20
II. Description
It is the count of incoming calls not answered by the 3G mobile callees till timeout.
It is measured when the MSC receives the DISCONNECT message from the mobile
caller due to no DTAP Connect message received from the callee in a valid period after
the DTAP Alerting message. Or it is measured when the MSC releases the call due to
connection timeout. The callee may be in the local MSC or in another one. See point A

8-130
RNC MSC Server
DTAP ALERTING
DTAP SETUP
XXX
ACM / DTAP ALERTING
A
DTAP CONNECT
DTAP DISCONNECT
DTAP RELEASE
Long time no reply

IV. Formula
None
I. Entity Name
MDB20
II. Description
It is the count of incoming calls directly rejected by mobile callees after the ringing.
after the ringing. The callee may be in the local MSC or in another one. See point A in

8-131
RNC MSC Server
DTAP ALERTING
DTAP SETUP
XXX
ACM / DTAP ALERTING
A
DTAP CONNECT
CV_USR_BUSY)
DTAP RELEASE

IV. Formula
None
I. Entity Name
ANS20
II. Description
It is the count of incoming calls answered by the 3G mobile callees.
It is measured when the MSC receives the DTAP Connect message from the mobile
callee. The callee may be in the local MSC or in another one. See point C in the
following figure.

8-132
RNC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
SU20
II. Description
It is the traffic generated during the incoming call attempts in which the callees are UEs.
It measures the interval between relevant messages in a measurement period. In
internal MSC call connection, if the CM is in the call originated status
(CM_MM_CONNECTION), the MSC begins the measurement. The measurement
indicated in Erlang (3GPP TS 25.413, GSM 08.08). The callee may be in the local MSC
or in another one. Point A in the following figure is the start point of the measurement
and call release is the end point.

8-133
RNC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
ALTU20
II. Description
It is the traffic generated when incoming UE calls are in the connected status.
It measures the interval between relevant messages in a measurement period. When
the MSC receives the DTAP Alerting message and the CM is in the status of
CM_CALL_RECIEVED, the MSC begins the measurement. The measurement stops
when the CM shifts to idle state after the call is released. The final result is indicated in
Erlang (3GPP TS 24.008, 3GPP TS25.413, GSM08.08). The callee may be in the local
MSC or in another one. Point B in the following figure is the start point of the
measurement and call release is the end point.

8-134
RNC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
ANSU20
II. Description
It is the traffic generated when incoming UE calls are in the answered status.
It measures the interval between relevant messages in a measurement period. When
the MSC receives the DTAP Connect message and the CM is in the status of
CM_CONNECT_REQUEST, the MSC begins the measurement. The measurement
indicated in Erlang (3GPP TS 24.008, 3GPP TS25.413, GSM08.08). The callee may be
in the local MSC or in another one. Point C in the following figure is the start point of the
measurement and call release is the end point.

8-135
RNC MSC Server
DTAP ALERTING
DTAP SETUP
ACM / DTAP ALERTING
B
DTAP CONNECT
ANM / DTAP CONNECT
C
XXX
DTAP PAGING
DTAP PAGING_RSP
A

IV. Formula
None
I. Entity Name
ALTR20
II. Description
IV. Formula
ALTR20 = ALT20/CA20
8.11.18 Answer Rate
I. Entity Name
ANSR20
II. Description

8-136
IV. Formula
ANSR20 = ANS20/CA20
8.12 Outgoing Traffic
8.12.1 Overview of MS_OFFICE_OUT_TRAF
Name Description
BID Count of call attempts
SEIZ Count of seizure
CNT Count of connected calls
ANS Count of answered calls
NANS Count of not answered calls
BRGABN Count of releases before ringing
ALBLCL Count of call failures due to overload
FWCTLCL Count of call failures due to network management
LRUOFL Count of outgoing trunk overflow
CBSY Count of callee busy
CTB Count of callee busy in toll calls
CLB Count of callee busy in local calls
SERL Seizure traffic
RERL Answered traffic
MNTCIR Count of blocked circuits
CNTR Call completion rate
ANSR Answer rate
CATS Count of call attempts
CRFS
Count of failed call attempts due to common resource
application failure
PCFS Count of failed call attempts due to peer office congestion
ATTR Connected traffic
RADI Count of incomplete addresses received


8-137
8.12.2 Count of Seizure Attempts
I. Entity Name
BID
II. Description
It is the count of outgoing seizure attempts (without considering the caller attributes).
It is measured when the MSC tries to seize a trunk circuit or BICC CIC for a call. It is
measured when the ISUP receives the Setup message. See point A in the following
figure.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None
8.12.3 Count of Seizure
I. Entity Name
SEIZ
II. Description
It is the count of successful seizures of the outgoing (bidirectional) trunk circuits or
BICC CIC. For SS7, It is the count of seizure ACK messages. For SS1, it is the count of
Setup messages. For BICC, It is the count of CIC seizure.

8-138
It is measured when the call successfully seizes the outgoing trunk circuit or BICC CIC.
It is measured when the ISUP receives the Setup message. See point A in the following
figure.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of ACMs received from the peer office of the callees (PSTN or GSM
subscribers) in the outgoing calls.
It is measured when the ISUP receives the ACM (ITU-T Rec. Q.722) from the peer
office.
It is measured when the ISUP receives the ACM. See point A in the following table.

8-139
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None
I. Entity Name
ANS
II. Description
It is measured after the MSC receives the ANC, ANN, or ANM message.
It is measured when the ISUP receives the ANM.

8-140
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None
8.12.6 Count of Not Answered Calls
I. Entity Name
NANS
II. Description
It is the count of failed call attempts due to no replies from the callees, releases by the
callers, or other reasons. The preceding reasons are classified into one because the
callees are in other offices where the signaling cannot be distinguished. You can
calculate the calls by the following formula:
Count of not answered calls = Count of connected calls Count of answered calls.
It is measured when the MSC releases the call due to no ANM received from the callee
in a valid period after the ACM.
1) Not answered calls (case 1)
The cause value of the REL message might be one of the following:
CV_NO_ACKNOWLEGE
CV_LONG_TIME_NO_ANSWER
CV_GSM_CLD_USER_NO_ACKNOWLEGE

8-141
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
REL
A
REL
Release
Release

2) Not answered calls (case 2)
The cause value of the REL message might be one of the following:
CV_RECOVERY_OF_TIME_OUT
CV_NO_ACKNOWLEGE
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL

IV. Formula
None

8-142
I. Entity Name
BRGABN
II. Description
Before receiving the ACM, the MSC sends the CLF or REL message.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
REL
A
REL
Release
Release

IV. Formula
None
8.12.8 Count of Call Failures Due to Overload
I. Entity Name
ALBLCL
II. Description
It is the count of failed calls due to CPU overload.
It is measured when the call is released due to CPU overload.

8-143
1) Call failures due to overload (case 1)
The cause value of the REL message is CV_CPU_OVERLAP.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
A
REL
Release

ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL
Release


8-144
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL
Release
ANM
Connect
Connect
ANM

IV. Formula
None
8.12.9 Count of Call Failures Due to Network Management
I. Entity Name
FWCTLCL
II. Description
It is the count of failed calls due to network management.
It is measured when the call is released due to the network management.
1) Call failure due to network management (case 1)
The cause value of the REL message is CV_NET_MANAGE_BARRING.

8-145
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
A
REL
Release

ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL
Release


8-146
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL
Release
ANM
Connect
Connect
ANM

IV. Formula
None
I. Entity Name
LRUOFL
II. Description
It is the count of failures of trunk or BICC CIC seizure attempts originated by the MSC in
the outgoing calls.
It is measured when the MSC fails to select an outgoing trunk or BICC CIC in an
outgoing call. See point A in the following figure.

8-147
IAM
MSC Server
A
MSC Server
Outgoing trunk
overflow

IV. Formula
None
I. Entity Name
CBSY
II. Description
It is measured when the MSC receives the REL message from the peer office to
indicate that the callee is busy in an outgoing call. It includes the following cases.
1) Callee busy (case 1)
The cause value of the REL message is CV_BUSY.

8-148
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
A
REL

2) Callee busy (case 2)
The cause value of the REL message is CV_BUSY.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL

IV. Formula
None
8.12.12 Count of Callee Busy in Toll Calls
I. Entity Name
CTB

8-149
II. Description
It is the count of calls failed because the callees are in toll calls..
It is measured when the TUP receives the STB message from the peer office in an
outgoing call.
IV. Formula
None
8.12.13 Count of Callee Busy in Local Calls
I. Entity Name
CLB
II. Description
It is the count of failed calls due to callees in local call sessions.
It is measured when the TUP receives the SLB message from the peer office in an
outgoing call.
IV. Formula
None
I. Entity Name
SERL
II. Description
It is measured from the moment the IAM or IAI message is sent to that the REL, CLF or
CBK message is received. The final result is indicated in Erlang (ITU-T Rec. Q.722).

8-150
IAM
MSC Server
MSC Server
REL
A
IAM
MSC Server
MSC Server
REL
A

IV. Formula
None
I. Entity Name
RERL
II. Description
It is the traffic generated when outgoing calls are in the answered status.
MSC to that the REL, CLF or CBK message is sent. The final result is indicated in
Erlang (ITU-T Rec. Q.722).

8-151
IAM
MSC Server
MSC Server
REL
A
ANM
REL
B
IAM
MSC Server
MSC Server
REL
A
ANM
REL
B

IV. Formula
None
8.12.16 Count of Blocked Circuits
I. Entity Name
MNTCIR
II. Description
It is the count of circuits that are in maintenance state on the outgoing (bidirectional)
trunk.
It is measured when a circuit is in maintenance state.
IV. Formula
None
I. Entity Name
CNTR
II. Description

8-152
IV. Formula
CNTR = CNT/CATS
8.12.18 Answer Rate
I. Entity Name
ANSR
II. Description
IV. Formula
ANSR = ANS/CATS
I. Entity Name
CATS
II. Description
It is the count of outgoing call attempts.
After the caller initiates a call, the MSC analyzes the called number. After confirming the
call is an outgoing one, the MSC begins the measurement.

8-153
IAM
MSC Server
MSC Server
A
IAM
MSC Server
MSC Server
A

IV. Formula
None
8.12.20 Count of Failed Call Attempts Due to Common Resource Application
Failure
I. Entity Name
CRFS
II. Description
including the IWF, DTR, bill pool, and control table resources.

8-154
IAM
A
REL
RLC
ACM

IV. Formula
None
8.12.21 Count of Failed Call Attempts Due to Peer Office Congestion
I. Entity Name
PCFS
II. Description
situation.
Long time no reply.
Called line faulty.
Call connection failure.
Peer office circuit group congestion.
Dedicated signal tone sending failure.
Peer office congestion. See point A in the following figure.
The cause value of the REL message may be one of the following:
CV_EXCHANGE_FACILITY_SURGE
CV_NO_RESOURCE_AVAILABLE

8-155
CV_NO_ROUTE_TO_TERMINAL
CV_NO_ROUTE_AVAILABLE
CV_NO_ROUTE_OR_CIRCUIT_APPLIED_AVAILABLE
CV_REOUTE_IDENTEFIED_NOT_EXIST
CV_INVALID_TRANSMIT_NETWORK_SELECTION
1) Call failure due to peer office congestion (case 1)
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
A
REL

2) Call failure due to peer office congestion (case 2)

8-156
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL

IV. Formula
None
I. Entity Name
ATTR
II. Description
the REL, CLF, or CBK message is sent. The final result is indicated in Erlang (ITU-T
Rec. Q.722). Point A in the following figure is the start point of the measurement and B
or C is the end point.

8-157
IAM
MSC Server
MSC Server
REL
B
ACM
C
REL
A
IAM
MSC Server
MSC Server
REL
B
ACM
C
REL
A

IV. Formula
None
8.12.23 Count of Incomplete Addresses Received
I. Entity Name
RADI
II. Description
It is the count of failed calls due to incomplete numbers.
It is measured when the MSC receives the REL message with the cause value address
incomplete (0011100) from the peer office.
1) Call failure due to incomplete number (case 1)
The cause value of the REL message is
CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOUGH.

8-158
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
A
REL

The cause value of the REL message is
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL

The value of the Release message is

8-159
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
MSC ISUP(inc)
A
REL
Release
Release
REL

The value of the Release message is
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
MSC ISUP(inc)
A
REL
Release
Release
REL

IV. Formula
None

8-160
8.13 Connection Type
8.13.1 Overview of MS_OFFICE_CALLNATURE_TRAF
Name Description
PEGS Count of call attempts
BAR Count of barred calls due to caller service restriction
ARGABN Count of releases before the pickup
LTNANS Count of long time no reply
CERL Connected traffic
ANSR Answer rate
CEUR Count of MS unavailable
CFITB Count of failed call attempts due to inter-trunk failure
CFBTB Count of failed call attempts due to inter-trunk failure
CFPOB Count of failed call attempts due to peer office congestion
CDBT Count of mobile callee determined busy

I. Entity Name
PEGS
II. Description
It is the count of call attempts in which the connection types are defined.

8-161
After receiving the IAM or DTAP SETUP message, the MSC analyzes the called
number. After confirming the connection type, the MSC begins the measurement.
The callee may be in the local MSC or in another one. If the callee is in another office,
see point A in the following figure. If the callee is a local MS, see point D in the following
figure.
ACM
RNC/BSC
DTAP CONNECT
D
DTAP ALERTING
IAM
ANM/ANC/ANN
C
A
B
E
F
DTAP SETUP
XXX

IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of DTAP Alerting messages or ACMs received from the peer office.
It is measured when the MSC receives the ACM or the DTAP Alerting message from
the peer office.
see point B in the following figure. If the callee is a local MS, see point E in the following
figure.

8-162
ACM
RNC/BSC
DTAP CONNECT
D
DTAP ALERTING
IAM
ANM/ANC/ANN
C
A
B
E
F
DTAP SETUP
XXX

IV. Formula
None
I. Entity Name
ANS
II. Description
For an outgoing call, it is measured when the MSC receives the ANC, ANN, or ANM
message. For an incoming call, it is measured when the MSC receives the DTAP
Connect message from the mobile callee.
see point C in the following figure. If the callee is a local MS, see point F in the following
figure.

8-163
ACM
RNC/BSC
DTAP CONNECT
D
DTAP ALERTING
IAM
ANM/ANC/ANN
C
A
B
E
F
DTAP SETUP
XXX

IV. Formula
None
8.13.5 Count of Barred Calls Due to Caller Service Restriction
I. Entity Name
BAR
II. Description
It is the count of barred calls due to the caller service restrictions, such as Bearer
service not provisioned, Teleservice not provisioned, or BAOC.
It is measured when the MSC receives the abnormal cause value of the release
message.
IV. Formula
None
I. Entity Name
BRGABN

8-164
II. Description
It is measured when the MSC receives the REL or DTAP Disconnect message from a
caller before the call is connected.
see point A in the following figure. If the callee is a local MS, see point B in the following
figure.
ACM
RNC/BSC
B
DTAP ALERTING
XXX
A
Incoming REL or local DTAP DISCONNECT

IV. Formula
None
I. Entity Name
LRUOFL
II. Description
calls.

8-165
IAM
A
XXX
Outgoing trunk overflow

IV. Formula
None
I. Entity Name
CBSY
II. Description
It is measured when the MSC receives the REL message from the terminating office or
from the mobile callee due to user busy.
figure.

8-166
REL
RNC/BSC
DTAP ALERTING
B
IAM
A
XXX
ACM
MT busy

IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of active releases by the incoming trunk before the pickup.
It is measured when the callee receives the REL message from the incoming trunk
(including the RNC and BSC).
figure.

8-167
ACM
RNC/BSC
B
DTAP ALERTING
XXX
A
IAM
ANM
DTAP CONNECT
DTAP SETUP

IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of calls that are released because the callees do not answer till timeout.
received from the callee in a valid period.
The callee may be in the local MSC or in another one. For an incoming call, point A in
the following figure is the start point of the measurement. For an outgoing call from the
local MSC, point B in the following figure is the start point of the measurement.

8-168
ACM
RNC/BSC
B
DTAP ALERTING
XXX
A
ACM / DTAP ALERTING
IAM
ANM
DTAP CONNECT
DTAP SETUP
ACM / DTAP ALERTING
REL
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
SERL
II. Description
It is the traffic generated during the call attempts.
It is measured from the moment the MSC defines the call attribute to that the REL
message is received. The final result is indicated in Erlang.
see point A in the following figure. If the callee is a local MS, see point D in the following
figure.

8-169
ACM
RNC/BSC
DTAP CONNECT
D
DTAP ALERTING
IAM
ANM/ANC/ANN
C
A
B
E
F
DTAP SETUP
XXX

IV. Formula
None
I. Entity Name
CERL
II. Description
It is the traffic generated during the call connections. The measurement begins from the
moment the phone rings to that the call is released.
It is measured from the moment the ACM or DTAP Alerting message is received from
the destination MSC to that the REL message is received. The final result is indicated in
Erlang.
see point B in the following figure. If the callee is a local MS, see point E in the following
figure.

8-170
ACM
RNC/BSC
DTAP CONNECT
D
DTAP ALERTING
IAM
ANM/ANC/ANN
C
A
B
E
F
DTAP SETUP
XXX

IV. Formula
None
I. Entity Name
RERL
II. Description
It is the traffic generated when the callees answer the calls. The measurement begins
from the moment the call is answered to that the call is released.
It is measured from the moment the Answer signal or CONNECT ACK message is
received to that the REL message is received. The final result is indicated in Erlang.
see point C in the following figure. If the callee is a local MS, see point F in the following
figure.

8-171
ACM
RNC/BSC
DTAP CONNECT
D
DTAP ALERTING
IAM
ANM/ANC/ANN
C
A
B
E
F
DTAP SETUP
XXX

IV. Formula
None
I. Entity Name
CNTR
II. Description
IV. Formula
CNTR = CNT/PEGS
8.13.15 Answer Rate
I. Entity Name
ANSR
II. Description

8-172
IV. Formula
ANSR = ANS/PEGS
I. Entity Name
CEUR
II. Description
call. See point A in the following figure.
RNC/BSC MSC Server
DTAP PAGING_RSP
XXX
DTAP PAGING
Mobile subscriber
unreachable
A

IV. Formula
None
8.13.17 Count of Failed Call Attempts Due to Inter-Trunk Failure
I. Entity Name
CFITB

8-173
II. Description
It is the count of failed calls due to all outgoing (bidirectional) trunks busy. And the call
connection type is the selected type. That is, the software invokes the database to
select an outgoing (bidirectional) trunk, but it fails. And the call connection type is the
selected type.
It is measured when the MSC software fails to choose an outgoing (bidirectional) trunk
circuit. See point A in the following figure.
IAM
A
XXX
Outgoing trunk
overflow

IV. Formula
None
8.13.18 Count of Failed Call Attempts Due to Inter-Trunk Failure
I. Entity Name
CFBTB
II. Description
It is the count of failed calls due to terrestrial channels unavailable. In an incoming call,
if the MSC fails to seize the terrestrial channels of the BSS before sending the
ASSIGNMENT REQUEST message to this BSS, the call connection fails.
Before sending the ASSIGNMENT REQUEST message to this BSS in an incoming call,
if the MSC fails to seize the terrestrial channels of the BSS which the MS belongs to,

8-174
the measurement begins. It is measured only when the MS accesses from the interface
A. See point A in the following figure.
BSC MSC Server
DTAP ALERTING
XXX
DTAP SETUP
BSS trunk busy
A

IV. Formula
None
8.13.19 Count of Failed Call Attempts Due to Peer Office Congestion
I. Entity Name
CFPOB
II. Description
situation.
The sending of the dedicated signal tone fails.
The peer office is congested.

8-175
IAM
A
XXX
REL
ACM

IV. Formula
None
I. Entity Name
CDBT
II. Description
It is the count of calls rejected because callees are busy.
It is measured when the MSC receives the REL or DTAP Disconnect message from the
terminating office or callee. The value of the message is USER BUSY.
The call may be an incoming call or an outgoing one from the local MSC If the callee is
in another office, see point A in the following figure. If the callee is a local MS, see point
B in the following figure.

8-176
ACM
RNC/BSC
B
DTAP ALERTING
IAM
DTAP PAGING_RSP
A
XXX
DTAP SETUP
REL(CV_ST_BUSY/CV_SL_BUSY/CV_BUSY)
DTAP DISCONNECT(CV_BUSY)
DTAP ALERTING / ACM
ANM/ANC
DTAP CONNECT
DTAP ALERTING / ACM

IV. Formula
None
8.14 Intra-Office Traffic
8.14.1 Overview of MS_OFFICE_INT_MTM_TRAF
Name Description

8-177
Name Description
SU7 Seizure traffic
ANSR7 Answer rate

I. Entity Name
CA7
II. Description
It is the count of call attempts initiated by the RNS and found to be intra-office ones
After receiving the DTAP Setup message from the mobile caller, the MSC obtains
routing information from the HLR. After defining the call is an incoming one according to
the mobile station roaming number (MSRN), the MSC begins the measurement. See

8-178
RNC/BSC MSC Server
DTAP ALERTING
DTAP SETUP
A
RNC/BSC
DTAP SETUP
DTAP ALERTING
B
DTAP CONNECT
DTAP CONNECT
C

IV. Formula
None
I. Entity Name
ABR7
II. Description
It is the count of active releases by the local mobile callers before calls are connected.

8-179
RNC/BSC MSC Server
DTAP ALERTING
A
RNC/BSC
DTAP SETUP
DTAP DISCONNECT
DTAP RELEASE

IV. Formula
None
I. Entity Name
TAF7
II. Description

8-180
RNC/BSC MSC Server
DTAP ALERTING
A
RNC/BSC
DTAP SETUP
DTAP DISCONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
CRU7
II. Description
including the IWF, DTR, bill pool, control table, and announcement resources.

8-181
RNC/BSC MSC Server
DTAP ALERTING
A
RNC/BSC
DTAP SETUP
DTAP DISCONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
CB7
II. Description
It is the count of call connections failed because mobile callees are busy in intra-office
calls.
incoming/outgoing call setup to the VLR. The VLR returns a message to indicate that
the callee (no CF service) is busy, and then the MSC begins the measurement. See

8-182
RNC/BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP SETUP
The MSC obtains the MSRN, and
the VLR returns a message

IV. Formula
None
I. Entity Name
MBTO7
II. Description
It is the count of failed incoming calls due to the trunk resources unavailability on the
lu_CS interface.
It is measured when the MSC queries the idle circuits before the allocation. In WCDMA
mode, the RNC establishes the AAL2, so there is no overflow measurement. See point

8-183
BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP SETUP
allocation failure
DTAP ALERTING

IV. Formula
None
I. Entity Name
MAF7
II. Description
for the mobile callees in the incoming calls.
It is measured when the MS receives the RAB ASSIGNMENT RESP message from the
RNC of the mobile callee, or receives the BSSMAP ASSIGN FAILURE from the BSC of
the mobile callee. See point A in the following figure.

8-184
RNC/BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP SETUP
allocation failure
DTAP ALERTING

IV. Formula
None
I. Entity Name
MNR7
II. Description
It is the count of failed incoming call connections due to paging failures.
call. See point A in the following figure.

8-185
RNC/BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP PAGING
DTAP PAGING_RSP
Mobile subscriber
unreachable

IV. Formula
None
I. Entity Name
ALT7
II. Description
It is the count of DTAP Alerting messages sent to mobile callers in the intra-office calls.
It is measured when the MSC sends the DTAP Alerting message to the local mobile
caller after receiving the DTAP Alerting message from the mobile callee. See point B in

8-186
RNC/BSC MSC Server
DTAP ALERTING
DTAP SETUP
A
RNC/BSC
DTAP SETUP
DTAP ALERTING
B
DTAP CONNECT
DTAP CONNECT
C

IV. Formula
None
I. Entity Name
AAR7
II. Description
It is the count of active releases by mobile callers before the mobile callees pickup the
phones.
It is measured when the mobile caller releases the call after receiving the DTAP Alerting
message but before the DTAP Connect message. See point A in the following figure.

8-187
RNC/BSC MSC Server
DTAP ALERTING
DTAP SETUP
RNC/BSC
DTAP SETUP
DTAP ALERTING
A
DTAP CONNECT
DTAP DISCONNECT
DTAP RELEASE

IV. Formula
None
I. Entity Name
RNA7
II. Description
received from the callee in a valid period after the DTAP Alerting message. See point A

8-188
RNC/BSC MSC Server
DTAP ALERTING
DTAP SETUP
RNC/BSC
DTAP SETUP
DTAP ALERTING
A
DTAP CONNECT
DTAP DISCONNECT
DTAP RELEASE
Long time no reply

IV. Formula
None
I. Entity Name
MDB7
II. Description
after the ringing. The value of the message is CV_USER_BUSY or CV_BUSY. See

8-189
RNC/BSC MSC Server
DTAP ALERTING
DTAP SETUP
RNC/BSC
DTAP SETUP
DTAP ALERTING
A
DTAP CONNECT
CV_USR_BUSY)
DTAP RELEASE

IV. Formula
None
I. Entity Name
ANS7
II. Description
It is the count of mobile incoming calls answered by the mobile callees.
When receiving the DTAP Connect message from the mobile callee, the MSC sends
the DTAP Connect message to the mobile caller. After receiving the DTAP Connect
ACK message from the mobile caller, the MSC begins the measurement. See point C in

8-190
RNC/BSC MSC Server
DTAP ALERTING
DTAP SETUP
A
RNC/BSC
DTAP SETUP
DTAP ALERTING
B
DTAP CONNECT
DTAP CONNECT
C

IV. Formula
None
I. Entity Name
SU7
II. Description
It is the traffic generated during the intra-office call attempts.
WCDMA system, the MSC begins the measurement from the moment the message
MAP_SEND_ROUTING_INFORMATION is received to that the message IU RELEASE
COMMAND is sent. For GSM system, the MSC begins the measurement from the
moment the message MAP_SEND_ROUTING_INFORMATION is received to that the
message CLEAR COMMAND is sent. The final result is indicated in Erlang.
The release of the call is the measurement point. See point A in the following figure.

8-191
RNC/BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP DISCONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
ALTU7
II. Description
It is the traffic generated when intra-office calls are in the connected status.
It measures the interval between relevant messages in a measurement period.
For WCDMA system, the MSC begins the measurement from the moment the
message DTAP Alerting is received to that the message IU RELEASE
COMMAND is sent.
For GSM system, the MSC begins the measurement from the moment the
message DTAP Alerting is received to that the message CLEAR COMMAND is
sent. The final result is indicated in Erlang.
The release of the call is the measurement point. See point A in the following figure.

8-192
RNC/BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP DISCONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
ANSU7
II. Description
It is the traffic generated when intra-office calls are in the answered status.
It measures the interval between relevant messages in a measurement period.
For WCDMA system, the MSC begins the measurement from the moment the
message CONNECT ACKNOWLEDGE is received to that the message IU
RELEASE COMMAND is sent.
For GSM system, the MSC begins the measurement from the moment the
message CONNECT ACKNOWLEDGE is received to that the message CLEAR
COMMAND is sent.
The final result is indicated in Erlang. The release of the call is the measurement point.

8-193
RNC/BSC MSC Server
A
RNC/BSC
DTAP SETUP
DTAP DISCONNECT
DTAP DISCONNECT

IV. Formula
None
I. Entity Name
ALTR7
II. Description
IV. Formula
ALTR7 = ALT7/CA7
8.14.19 Answer Rate
I. Entity Name
ANSR7
II. Description

8-194
IV. Formula
ANSR7 = ANS7/CA7
8.15 Call Forwarding Traffic
8.15.1 Overview of MS_FORWARD_TRAF
Name Description
FORCAM Count of call forwarding attempts
FORCCN Count of forwarded calls
FORCAN Count of answered forwarded calls
FORST Count of call forwarding seizure traffic
FORCT Count of call forwarding connected traffic
FORAT Call forwarding answered traffic

8.15.2 Count of Call Forwarding Attempts
I. Entity Name
FORCAM
II. Description
It is the count of analyzed numbers in forwarding calls.
It is measured when the MSC finishes analyzing the called number in a forwarding call.
If the callee is in another office, see point A in the following figure. If the callee is a local
MS, see point D in the following figure.

8-195
ACM
RNC/BSC
DTAP CONNECT
F
DTAP ALERTING
IAM
ANM/ANC
C
SETUP
A
B
D
E

IV. Formula
None
8.15.3 Count of Forwarded Calls
I. Entity Name
FORCCN
II. Description
It is the count of ACM received by the MSC in the forwarding call connections.
It is measured when the MSC receives the ACM from the forwarded party. If the callee
is in another office, see point B in the following figure. If the callee is a local MS, see
point E in the following figure.

8-196
ACM
RNC/BSC
DTAP CONNECT
F
DTAP ALERTING
IAM
ANM/ANC
C
SETUP
A
B
D
E

IV. Formula
None
8.15.4 Count of Answered Forwarded Calls
I. Entity Name
FORCAN
II. Description
It is the count of answered forwarding calls.
In an outgoing call, it is measured when the MSC receives the ANC or ANN message
from the forwarded party. In an incoming call, if the call is originated from the local MSC,
it is measured when the MSC receives the DTAP Connect message from the forwarded
party.
If the callee is in another office, see point C in the following figure. If the callee is a local
MS, see point F in the following figure.

8-197
ACM
RNC/BSC
DTAP CONNECT
F
DTAP ALERTING
IAM
ANM/ANC
C
SETUP
A
B
D
E

IV. Formula
None
8.15.5 Count of Call Forwarding Seizure Traffic
I. Entity Name
FORST
II. Description
It is the traffic generated during the forwarding call attempts.
It is measured from the moment the call forwarding begins to that the REL message is
received. The final result is indicated in Erlang (ITU-T Rec. Q.722).
If the callee is in another office, see point A in the following figure. If the callee is a local
MS, see point D in the following figure.

8-198
ACM
RNC/BSC
DTAP CONNECT
F
DTAP ALERTING
IAM
ANM/ANC
C
SETUP
A
B
D
E

IV. Formula
None
8.15.6 Count of Call Forwarding Connected Traffic
I. Entity Name
FORCT
II. Description
It is the traffic generated when forwarding calls are in the connected status.
It is measured from the moment the ACM or DTAP Alerting message is received to that
the REL message is received. The final result is indicated in Erlang (ITU-T Rec. Q.722).
If the callee is in another office, see point B in the following figure. If the callee is a local
MS, see point E in the following figure.

8-199
ACM
RNC/BSC
DTAP CONNECT
F
DTAP ALERTING
IAM
ANM/ANC
C
SETUP
A
B
D
E

IV. Formula
None
8.15.7 Call Forwarding Answered Traffic
I. Entity Name
FORAT
II. Description
It is the traffic generated when forwarded calls are in the answered status.
It is measured from the moment the ANM or ANC or DTAP Connect message is
received to that the REL message is received. The final result is indicated in Erlang
(ITU-T Rec. Q.722).
If the callee is in another office, see point C in the following figure. If the callee is a local
MS, see point F in the following figure.

8-200
ACM
RNC/BSC
DTAP CONNECT
F
DTAP ALERTING
IAM
ANM/ANC
C
SETUP
A
B
D
E

IV. Formula
None
8.16 Forwarded Subscriber Count
8.16.1 Overview of MS_FORWARD_USER
The name and meaning are listed in the following table.
Name Description
FORUN Count of subscribers forwarded to destination

8.16.2 Count of Subscribers Forwarded to Destination
I. Entity Name
FORUN
II. Description
It is the count of subscribers moved into the local area.
It is measured when the subscriber data is inserted or modified.
1) The location update concerns two measurement points (B and C in the following
figure). The detailed procedures of inter-office location update are as follows.
The HLR sends CANCEL_LOCATION message to the previous VLR (PVLR).

8-201
The PVLR deletes the subscriber who has moved into another location area.
The PVLR checks the office of the forwarded-to number in the service subscription
information and updates the subscriber data.
See point B.
The HLR sends the INSERT_SUBSCRIBER_DATA message to the VLR.
The VLR checks the destination of the forwarded-to number in the service
subscription information and updates the subscriber data.
See point C.
MAP-UPDATE-LOCATION-
AREA
MAP-UPDATE-LOCATION
MAP-VDB-INSERT-SUBSCRIVER-DATA
MAP-VDB-INSERT-SUBSCRIVER-DATA-ACK
MAP-PROVIDE-IMSI
MAP-PROVIDE-IMSI-ACK
MAP-CANCEL-LOCTION
MAP-CANCEL-LOCTION-ACK
MSC VLR PVLR HLR
MAP-UPDATE-LOCATION-ACK
MAP-UPDATE-LOCATION-
AREA-ACK
B
C
D
A

2) The subscriber data operation of the HLR concerns two measurement points (A
and B in the following figure). The detailed procedures are as follows.
For removing the subscriber, the HLR sends the CANCEL_LOCATION message
to the current VLR.
The VLR deletes the subscriber moved into another location area.
The VLR checks the destination of the forwarded number in the service
subscription information of the subscriber data and updates the subscriber data.
See point A.

8-202
MAP-CANCEL-LOCTION
MAP-CANCEL-LOCTION-ACK
VLR HLR OMC
Delete subscriber
Subscriber deleted
A

For modifying the supplementary service data of the subscriber, the HLR sends a
MAP-INSERT-SUB-DATA or MAP-DELETE-SUB-DATA message to the current
VLR.
The VLR updates the subscriber data of supplementary services.
The VLR checks the destination of the forwarded number in the service
subscription information of the subscriber data and updates the subscriber data.
MAP-INSERT-SUB-DATA or
MAP-DELETE-SUB-DATA
MAP-INSERT-SUB-DATA-ACK or
MAP-DELETE-SUB-DATA-ACK
VLR HLR OMC
Modify user data
Subscriber data
modified
B

3) The procedures of functionalizing the supplementary services concerns one
measurement point. See point A in the following figure.
When the MS initiates a supplementary service data operation, the HLR initiates a
flow of inserting subscriber data to the current VLR.
The VLR compares the supplementary service subscription information in local
VLR with that in the message.
If it requires to add or remove the number, the VLR checks the destination of the
forwarded number in the service subscription information of the subscriber data
and updates the subscriber data.
See point A.

8-203
MAP-REG / ERASE / ACT /
DEA-SS
DEA-SS-ACK
MSC VLR HLR
A
DEA-SS
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA

4) The internal VLR periodical subscriber management concerns one measurement
point. See point B in the following figure.
if there is no message interaction between a subscriber and the VLR during a period
specified in the VLR configuration table, the VLR directly removes the subscriber data
and notifies the HLR. At the same time, the VLR checks the destination of the
forwarded number in the service subscription information of the subscriber data and
updates the subscriber data.
MAP-PURGY-MS
MSC HLR VLR
MAP-PURGY-MS
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
B

IV. Formula
None

8-204
8.17 Failure Causes of the Office
8.17.1 Overview of MS_FAULT_REASON_TRAF
Name Description
NSSETCFT Count of supplementary service setting conflict
NSSETOK Count of supplementary service setting successes
NSSETFL Count of supplementary service setting failures
NSCANOK Count of supplementary service deregistration successes
NSCANFL Count of supplementary service deregistration failures
NSTSTOK Count of supplementary service authentication successes
NSTSTFL Count of supplementary service authentication failures
NSUSOK Count of supplementary service application successes
NSUSFL Count of supplementary service application failures
MCTOK Count of successes in probing malicious calls
MCTFL Count of failures in probing malicious calls
SEC Count of MSC congestions
LTNDG Count of long time no dialing
LTNANS Count of long time no reply
SYSFL Count of temporary failures
RTSTOK Count of self-test successes
LTNINF Count of long time no messages
LTNRG Count of long time no ringing
LTNRLS Count of long time no release
INBSIG Count of inband signals
COCFL Count of continuity check failures
EXREATP Count of exceeding max. call attempts
ARGABN Count of releases before the pickup
BAR Count of call restrictions
SEFL Count of MSC failures
SEFL1 Count of toll calls to busy callee

8-205
Name Description
SEFL2 Count of local calls to busy callee
REPMCG Count of peer office congestion
CLFL Count of call failures
DSEIZ Count of contentions
INVCD Count of invalid numbers
NMNBAR Count of network management barring
CPUOL Count of CPU congestions and overload
NCR Count of no CR resources
NCCB Count of no CCB resources
IFCR Count of incoming office CF barring
DIALTO Count of dialing time out
SIGER Count of signaling failures
BWLBAR Count of black list calls barred
BWLBAR1 Count of caller number identification failures
NACFBS Count of no A interface resource for a bearer service
NAC Count of no A interface resources
ICUGS Count of CUG service incompatible
UCUG Count of unknown CUG
NSCUG Count of CUG unselected
BOCUG Count of CUG outgoing calls barred
BICUG Count of CUG incoming calls barred
CUGSSI Count of CUG supplementary service failures
ICUGD Count of CUG destination incompatible
CL Count of released calls
HOC Count of Switchover successes
HOF Count of Switchover failures
TECLT Count of call restriction duration timeout
TF Count of termination resource application failures
CDNE Count of callee number not exist (excluding fixed-line numbers)
NAFCD Count of mobile callee no reply
CDBAIC Count of mobile callee incoming call restricted
CRBOAC Count of call out restrictions

8-206
Name Description
CDUR Count of callee unreachable
NACP Count of calling local subscriber without area code
CDB Count of mobile callee busy
CDPO Count of mobile callee power-off
SNA Count of required function not applied
DZ Count of toll calls without 0
CFV Count of CF conflict
ESRI Count of failures in HLR obtaining route information
ODBAOC Count of all outgoing calls barred by operators
ODBOIC Count of all outgoing international calls barred by operators
UBOICE Count of all outgoing international calls barred by subscriber
UBOICENH Count of BOIC-exHC barred by subscribers
ODBOICE Count of BOIC-exHC barred by operators
ODBAIC Count of all incoming calls barred by operators
ODBEC Count of operators barring entertainment console
ODBMC Count of operators barring announcement console
SROP Count of subscriber roaming out
ODBT Count of all national toll calls barred by operators
UN Count of cause unknown failures
UALCCD Count of unallocated numbers
NRUTOSI Count of no route to specified transit network
NRUTOTE Count of no route to destination
SPRVTONE Count of sending private tone
ERLNGPFX Count of wrongly dialed numbers of toll call prefix
RUUAPT Count of unacceptable paths
CALLEST Count of calls connected and delivered on established route
ODB Count of calls barred by operators
RFREUSE Count of circuits reserved for reusing
NORCLR Count of normally cleared calls
UDB Count of callee determined busy
NRSP Count of no reply
NACK Count of no response

8-207
Name Description
AS Count of callee absent
REJ Count of calls rejected
CDCHD Count of number changed
NFC Count of no idle circuits
RABPE Count of rab pre-empted
TEER Count of callee failures
INVCDFMT Count of invalid number formats
FACREJ Count of facilities rejected
RSPSE Count of responses to STATUS ENQUIRY
NOR Count of normally cleared calls
NCIR Count of unavailable circuits
NETER Count of network failures
TMPER Count of contemporary failures
EPMCG Count of MSC failures
AIL Count of accessed messages discarded
NRUCIR Count of unavailable routes
PCALLBLK Count of unavailable paths
NRSC Count of unavailable resources
NSSQUA Count of no suitable service quality
FACNPV Counts of facility applied not preserved before
CUGBC Count of CUG outgoing call restriction
CUGUALW Count of CUG incoming call restriction
BCUNP Count of bearer capability authorized
NBC Count of no available bearer capability
NSSOOP Count of no suitable service or optional project
BCNLO Count of bearer capability not implemented
RTNLO Count of path type not implemented
AOCRF Count of AOC service request failures
ACMEG Count of ACM equaling or greater than ACMmax
FACNLO Count of requested equipment not implemented
LTDDIBC Count of restricted bearer capability
IWFRU Count of IWF resource unavailable

8-208
Name Description
SOPNLO Count of service or optional project not implemented
INVCR Count of invalid call reference values
RUNEXT Count of identified route not exist
CLDNOCUG Count of callee not CUG subscriber
TEUCPT Count of incompatible terminals
NECUG Count of CUGs not exist
INVTNL Count of invalid transit network selection
INVMSG Count of invalid messages
MSGNOEXT Count of Non-Existent or Not Implemented message types
IENOEXT Count of Non-Existent or Not Implemented message units
TOUT Count of timeout recoveries
PARANOEXT Count of Non-Existent or Not Implemented parameters
UNRECPARA Count of messages carrying unidentified parameters
PROERR Count of protocol errors
INTWORK Count of interworking

8.17.2 Count of Supplementary Service Setting Conflict
I. Entity Name
NSSETCFT
II. Description
It is the count of setting failures of supplementary services.
It is measured when the MSC releases the call.
IV. Formula
None
8.17.3 Count of Supplementary Service Setting Successes
I. Entity Name
NSSETOK

8-209
II. Description
It is the count of successful settings of the supplementary services
IV. Formula
None
8.17.4 Count of Supplementary Service Setting Failures
I. Entity Name
NSSETFL
II. Description
It is the count of setting failures of supplementary services.
IV. Formula
None
8.17.5 Count of Supplementary Service Deregistration Successes
I. Entity Name
NSCANOK
II. Description
It is the count of successful deregistration of supplementary services.
IV. Formula
None
8.17.6 Count of Supplementary Service Deregistration Failures
I. Entity Name
NSCANFL

8-210
II. Description
It is the count of deregistration failures of supplementary services.
IV. Formula
None
8.17.7 Count of Supplementary Service Authentication Successes
I. Entity Name
NSTSTOK
II. Description
It is the count of successful authentication of supplementary services.
IV. Formula
None
8.17.8 Count of Supplementary Service Authentication Failures
I. Entity Name
NSTSTFL
II. Description
It is the count of authentication failures of supplementary services.
IV. Formula
None
8.17.9 Count of Supplementary Service Application Successes
I. Entity Name
NSUSOK

8-211
II. Description
It is the count of successful application of supplementary services.
IV. Formula
None
8.17.10 Count of Supplementary Service Application Failures
I. Entity Name
NSUSFL
II. Description
It is the count of application failures of supplementary services.
IV. Formula
None
8.17.11 Count of Successes in Probing Malicious Calls
I. Entity Name
MCTOK
II. Description
It is the count of successes in probing malicious calls.
IV. Formula
None
8.17.12 Count of Failures in Probing Malicious Calls
I. Entity Name
MCTFL

8-212
II. Description
It is the count of failures in probing malicious calls.
IV. Formula
None
8.17.13 Count of MSC Congestions
I. Entity Name
SEC
II. Description
It is the count of internal MSC congestions.
IV. Formula
None
8.17.14 Count of Long Time No Dialing
I. Entity Name
LTNDG
II. Description
It is the count of long time no dialing after the callers hook off.
IV. Formula
None
I. Entity Name
LTNANS

8-213
II. Description
IV. Formula
None
8.17.16 Count of Temporary Failures
I. Entity Name
SYSFL
II. Description
It is the count of call releases because the system performance declines due to
message losses, internal errors, or message combination failures.
IV. Formula
None
8.17.17 Count of Self-Test Successes
I. Entity Name
RTSTOK
II. Description
It is the count of self-test successes.
IV. Formula
None

8-214
8.17.18 Count of Long Time No Messages
I. Entity Name
LTNINF
II. Description
It is the count that the subscribers do not receive the messages in a specified period.
IV. Formula
None
8.17.19 Count of Long Time No Ringing
I. Entity Name
LTNRG
II. Description
It is the count of connection failures due to timeout when the caller does not receive the
message DTAP Alerting after receiving the message PAGING ACK from the callee.
IV. Formula
None
8.17.20 Count of Long Time No Release
I. Entity Name
LTNRLS
II. Description
It is the count of calls disconnected in specified periods after the DISCONNECT
messages are received.

8-215
IV. Formula
None
8.17.21 Count of Inband Signals
I. Entity Name
INBSIG
II. Description
It is the count of inband signals.
IV. Formula
None
8.17.22 Count of Continuity Check Failures
I. Entity Name
COCFL
II. Description
It is the count of continuity check failures in the peer office.
IV. Formula
None
8.17.23 Count of Exceeding Max. Call Attempts
I. Entity Name
EXREATP
II. Description
It is the count of call attempts that exceed the maximum number in the call connections
due to the contention.

8-216
IV. Formula
None
I. Entity Name
BRGABN
II. Description
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of active releases by the callers before the pickup.
IV. Formula
None
8.17.26 Count of Call Restrictions
I. Entity Name
BAR
II. Description
It is the count of calls barred due to subscriber service restrictions.

8-217
IV. Formula
None
8.17.27 Count of MSC Failures
I. Entity Name
SEFL
II. Description
It is the count of MSC failures in processing the IN services and iPath.
IV. Formula
None
8.17.28 Count of Toll Calls to Busy Callee
I. Entity Name
SEFL1
II. Description
It is the count of messages indicating the callees are busy in fixed toll calls.
IV. Formula
None
8.17.29 Count of Local Calls to Busy Callee
I. Entity Name
SEFL2
II. Description
It is the count of messages indicating callees busy in local fixed calls.

8-218
IV. Formula
None
8.17.30 Count of Peer Office Congestion
I. Entity Name
REPMCG
II. Description
It is the count of calls failed due to congestions in the peer office.
IV. Formula
None
8.17.31 Count of Call Failures
I. Entity Name
CLFL
II. Description
It is caused by the following reasons:
The peer office is congested and the MSC cannot obtain the addressing message
after receiving the SETUP message.
The peer office DSP is unavailable and the TUP releases the call due to timeout.
The called number is less than that requested when the MSC receives the IAM.
The MSC receives the RLG message abnormally.
The channel is blocked due to TUP circuit busy.
The circuit group is blocked.
The internal timer is timeout when the TUP is in the ringing state.
The MSC fails to receive the GSM message.
The TUP fails to receive the SETUP message.
The CFL message is received.

8-219
IV. Formula
None
8.17.32 Count of Contentions
I. Entity Name
DSEIZ
II. Description
It is the count of trunk busy due to contentions.
IV. Formula
None
8.17.33 Count of Invalid Numbers
I. Entity Name
INVCD
II. Description
It is the count of invalid numbers due to called number analysis failures.
IV. Formula
None
8.17.34 Count of Network Management Barring
I. Entity Name
NMNBAR
II. Description
It is the count of calls barred by the NMS.

8-220
IV. Formula
None
8.17.35 Count of CPU Congestions and Overload
I. Entity Name
CPUOL
II. Description
It is the count of CPU congestions and overload.
IV. Formula
None
8.17.36 Count of No CR Resources
I. Entity Name
NCR
II. Description
It is the count of insufficient CR resources which are used by the subscriber side (CCB
at network side) when originating or terminating calls.
IV. Formula
None
8.17.37 Count of No CCB Resources
I. Entity Name
NCCB
II. Description
It is the count of insufficient CCB resources which are used by the network side when
originating or terminating calls.

8-221
IV. Formula
None
8.17.38 Count of Incoming Office CF Barring
I. Entity Name
IFCR
II. Description
It is the count of forwarding calls barred by the peer office.
IV. Formula
None
8.17.39 Count of Dialing Time Out
I. Entity Name
DIALTO
II. Description
It is the count of timeout in dialing.
IV. Formula
None
8.17.40 Count of Signaling Failures
I. Entity Name
SIGER
II. Description
It is the count of signaling cooperation failures between SS7 and SS1.

8-222
IV. Formula
None
8.17.41 Count of Black List Calls Barred
I. Entity Name
BWLBAR
II. Description
It is the count of calls barred because the callers or callees are in the black list.
IV. Formula
None
8.17.42 Count of Caller Number Identification Failures
I. Entity Name
BWLBAR1
II. Description
It is the count of failures in identifying the caller numbers.
IV. Formula
None
8.17.43 Count of No A Interface Resource for A Bearer Service
I. Entity Name
NACFBS
II. Description
It is the count of no A interface resources for bearing the services.

8-223
IV. Formula
None
8.17.44 Count of No A Interface Resources
I. Entity Name
NAC
II. Description
It is the count of no A interface circuits.
IV. Formula
None
8.17.45 Count of CUG Service Incompatible
I. Entity Name
ICUGS
II. Description
It is the count of supplementary service failures due to CUG service incompatible.
IV. Formula
None
8.17.46 Count of Unknown CUG
I. Entity Name
UCUG
II. Description
It is the count of supplementary service failures due to CUG unknown.

8-224
IV. Formula
None
8.17.47 Count of CUG Unselected
I. Entity Name
NSCUG
II. Description
It is the count of supplementary service failures due to CUG unselected.
IV. Formula
None
8.17.48 Count of CUG Outgoing Calls Barred
I. Entity Name
BOCUG
II. Description
It is the count of calls barred due to CUG outgoing restrictions.
IV. Formula
None
8.17.49 Count of CUG Incoming Calls Barred
I. Entity Name
BICUG
II. Description
It is the count of calls barred due to CUG incoming restrictions.

8-225
IV. Formula
None
8.17.50 Count of CUG Supplementary Service Failures
I. Entity Name
CUGSSI
II. Description
It is the count of supplementary service failures due to CUG supplementary service
failures.
IV. Formula
None
8.17.51 Count of CUG Destination Incompatible
I. Entity Name
ICUGD
II. Description
It is the count of supplementary service failures due to CUG destination incompatible.
IV. Formula
None
8.17.52 Count of Released Calls
I. Entity Name
CL

8-226
II. Description
It is the count of released calls.
IV. Formula
None
8.17.53 Count of Switchover Successes
I. Entity Name
HOC
II. Description
It is the count of successful switchovers.
IV. Formula
None
8.17.54 Count of Switchover Failures
I. Entity Name
HOF
II. Description
It is the count of switchover failures.
IV. Formula
None
8.17.55 Count of Call Restriction Duration Timeout
I. Entity Name
TECLT

8-227
II. Description
It is the count of calls released because the session durations exceed the threshold.
IV. Formula
None
8.17.56 Count of Termination Resource Application Failures
I. Entity Name
TF
II. Description
It is the count of application failures of the Termination resources.
IV. Formula
None
8.17.57 Count of Callee Number Not Exist (Excluding Fixed-Line Numbers)
I. Entity Name
CDNE
II. Description
It is the count of messages indicating the HLR has no information about the callees
number.
IV. Formula
None

8-228
8.17.58 Count of Mobile Callee No Reply
I. Entity Name
NAFCD
II. Description
It is the count of mobile callees no reply after ringing.
IV. Formula
None
8.17.59 Count of Mobile Callee Incoming Call Restricted
I. Entity Name
CDBAIC
II. Description
It is the count of calls failed because the mobile callees have set incoming call
restrictions.
IV. Formula
None
8.17.60 Count of Call out Restrictions
I. Entity Name
CRBOAC
II. Description
It is the count of calls failed because the mobile callers have set outgoing call
restrictions.

8-229
IV. Formula
None
8.17.61 Count of Callee Unreachable
I. Entity Name
CDUR
II. Description
It is the count of calls of which the mobile callees are unreachable, power-off, or
abnormal.
IV. Formula
None
8.17.62 Count of Calling Local Subscriber Without Area Code
I. Entity Name
NACP
II. Description
It is the count of callee numbers without area codes when the MSs make local fixed-line
calls.
IV. Formula
None
8.17.63 Count of Mobile Callee Busy
I. Entity Name
CDB
II. Description
It is the count of calls restricted because mobile callees are busy.

8-230
IV. Formula
None
8.17.64 Count of Mobile Callee Power-Off
I. Entity Name
CDPO
II. Description
callees power-off.
IV. Formula
None
8.17.65 Count of Required Function Not Applied
I. Entity Name
SNA
II. Description
It is the count of required service functions that are not applied.
IV. Formula
None
8.17.66 Count of Toll Calls Without 0
I. Entity Name
DZ

8-231
II. Description
It is the count of unallocated numbers generated when the callers make non-local calls
without adding "0".
IV. Formula
None
8.17.67 Count of CF Conflict
I. Entity Name
CFV
II. Description
It is the count of calls released due to CF conflicts resulted from the forwarding time
restriction for the same reason.
IV. Formula
None
8.17.68 Count of Failures in HLR Obtaining Route Information
I. Entity Name
ESRI
II. Description
It is the count of routing selection and protocol errors.
IV. Formula
None

8-232
8.17.69 Count of All Outgoing Calls Barred by Operators
I. Entity Name
ODBAOC
II. Description
It is the count of outgoing calls barred by operators.
IV. Formula
None
8.17.70 Count of All Outgoing International Calls Barred by Operators
I. Entity Name
ODBOIC
II. Description
It is the count of outgoing international calls barred by operators.
IV. Formula
None
8.17.71 Count of All Outgoing International Calls Barred by Subscribers
I. Entity Name
UBOICE
II. Description
It is the count of outgoing international calls barred by subscribers.
IV. Formula
None

8-233
8.17.72 Count of BOIC-exHC Barred by Subscribers
I. Entity Name
UBOICENH
II. Description
It is the count of outgoing international calls barred by subscribers except those
directed to the home PLMN country.
IV. Formula
None
8.17.73 Count of BOIC-exHC Barred by Operators
I. Entity Name
ODBOICE
II. Description
It is the count of outgoing international calls barred by operators except those directed
to the home PLMN country.
IV. Formula
None
8.17.74 Count of All Incoming Calls Barred by Operators
I. Entity Name
ODBAIC
II. Description
It is the count of all incoming calls barred by operators.

8-234
IV. Formula
None
8.17.75 Count of Operators Barring Entertainment Console
I. Entity Name
ODBEC
II. Description
It is the count of messages indicating that the operators bar the entertainment
consoles.
IV. Formula
None
8.17.76 Count of Operators Barring Announcement Console
I. Entity Name
ODBMC
II. Description
It is the count of messages indicating that the operators bar the announcement
consoles.
IV. Formula
None
8.17.77 Count of Subscriber Roaming Out
I. Entity Name
SROP
II. Description
It is the count of calls failed because subscribers not in the service area.

8-235
IV. Formula
None
8.17.78 Count of All National Toll Calls Barred by Operators
I. Entity Name
ODBT
II. Description
It is the count of national toll calls barred by operators.
IV. Formula
None
8.17.79 Count of Cause Unknown Failures
I. Entity Name
UN
II. Description
It is the count of failed calls due to unknown causes.
IV. Formula
None
8.17.80 Count of Unallocated Numbers
I. Entity Name
UALCCD
II. Description
It is the count of unallocated numbers due to the following reasons:

8-236
The route selection source code or the route selection code is empty.
The bsn of the circuit in the table is empty.
The called number analysis fails according to the data configuration table.
The MAP fails to return the called number to the calling module.
The calling module fails to obtain the MSISDN or IMSI in the caller data.
The MSC receives the UNN message from the TUP of the callee side.
IV. Formula
None
8.17.81 Count of No Route to Specified Transit Network
I. Entity Name
NRUTOSI
II. Description
It is the count of calls that have no routes to the specified transit network due to the
following causes. The equipment receives an alternative calling request from the
specified but unknown transit network. The equipment cannot recognize this transit
network because the network does not exist or does not provide any service to the
equipment. The network determines whether to support this cause value.
IV. Formula
None
8.17.82 Count of No Route to Destination
I. Entity Name
NRUTOTE
II. Description
It is the count of calls that have no routes to the destinations due to terrestrial circuits
allocation failures and MM_CC_REL_IND from the bottom layer.

8-237
IV. Formula
None
8.17.83 Count of Sending Private Tone
I. Entity Name
SPRVTONE
II. Description
It is the count of private tones sent due to peer office congestions.
IV. Formula
None
8.17.84 Count of Wrongly Dialed Numbers of Toll Call Prefix
I. Entity Name
ERLNGPFX
II. Description
It is the count of faulty prefixes of the called numbers.
IV. Formula
None
8.17.85 Count of Unacceptable Paths
I. Entity Name
RUUAPT
II. Description
It is the count of calls rejected due to unacceptable paths.

8-238
IV. Formula
None
8.17.86 Count of Calls Connected and Delivered on Established Route
I. Entity Name
CALLEST
II. Description
It is the count of calls connected and delivered on the established paths.
IV. Formula
None
8.17.87 Count of Calls Barred by Operators
I. Entity Name
ODB
II. Description
It is the count of calls barred by operators.
It is the count of calls barred by operators.
IV. Formula
None
8.17.88 Count of Circuits Reserved for Reusing
I. Entity Name
RFREUSE
II. Description
It is the count of circuits reserved for reusing.

8-239
IV. Formula
None
8.17.89 Count of Normally cleared Calls
I. Entity Name
NORCLR
II. Description
It is the count of normally cleared calls.
IV. Formula
None
8.17.90 Count of Callee Determined Busy
I. Entity Name
UDB
II. Description
It is the count of calls failed because callees are busy.
IV. Formula
None
8.17.91 Count of No Reply
I. Entity Name
NRSP
II. Description
It is the count of calls not replied for a long time till timeout.

8-240
IV. Formula
None
8.17.92 Count of No Response
I. Entity Name
NACK
II. Description
This cause value is used when there is no response from the callee in a specified
period or when the link indication responds that the call is connected.
IV. Formula
None
8.17.93 Count of Callee Absent
I. Entity Name
AS
II. Description
It is the count of calls of which the callees are absent.
IV. Formula
None
8.17.94 Count of Calls Rejected
I. Entity Name
REJ
II. Description
It is the count of rejected calls.

8-241
IV. Formula
None
8.17.95 Count of Number Changed
I. Entity Name
CDCHD
II. Description
It is the count of invalid numbers due to changes of called numbers.
IV. Formula
None
8.17.96 Count of No Idle Circuits
I. Entity Name
NFC
II. Description
It is the count of failed calls due to no idle circuits.
IV. Formula
None
8.17.97 Count of RAB Pre-Empted
I. Entity Name
RABPE
II. Description
It is the count of calls released due to RAB resources seizure conflicts.

8-242
IV. Formula
None
8.17.98 Count of Callee Failures
I. Entity Name
TEER
II. Description
It is the count of calls of which the callees are abnormal.
IV. Formula
None
8.17.99 Count of Invalid Number Formats
I. Entity Name
INVCDFMT
II. Description
It is the count of calls cannot reach the callees due to invalid called numbers format or
incomplete called numbers. This cause value is used in this case.
IV. Formula
None
8.17.100 Count of Facilities Rejected
I. Entity Name
FACREJ

8-243
II. Description
It is the count of facilities rejected.
IV. Formula
None
8.17.101 Count of Responses to STATUS ENQUIRY
I. Entity Name
RSPSE
II. Description
It is the count of responses to the STATUS_ENQUIRY messages.
IV. Formula
None
8.17.102 Count of Normally cleared Calls
I. Entity Name
NOR
II. Description
It is the count of normally cleared calls.
IV. Formula
None
8.17.103 Count of Unavailable Circuits
I. Entity Name
NCIR

8-244
II. Description
It is the count of unavailable circuits. The circuits may be unavailable in:
querying the TUP circuits.
allocating the territorial circuits after the switch.
allocating the territorial circuits.
indication empty of the internal HW networks.
receiving the CGC message.
IV. Formula
None
8.17.104 Count of Network Failures
I. Entity Name
NETER
II. Description
It is the count of CC internal processing failures.
IV. Formula
None
8.17.105 Count of Contemporary Failures
I. Entity Name
TMPER
II. Description
It is the count of internal failures.
IV. Formula
None

8-245
8.17.106 Count of MSC Failures
I. Entity Name
EPMCG
II. Description
It is the count of MSC failures. The equipment sends this cause value to indicate the
MSC is in the high traffic stage.
IV. Formula
None
8.17.107 Count of Accessed Messages Discarded
I. Entity Name
AIL
II. Description
It is the count of accessed messages discarded. This cause value indicates the
network cannot deliver the access information to the remote subscribers. That is,
subscriber-subscriber information, lower-layer compatibility, higher-layer compatibility,
or sub-address indicated in the diagnosis.
IV. Formula
None
8.17.108 Count of Unavailable Routes
I. Entity Name
NRUCIR
II. Description
It is the count of failures in querying or allocating trunk resources.

8-246
IV. Formula
None
8.17.109 Count of Unavailable Paths
I. Entity Name
PCALLBLK
II. Description
It is the count of unavailable paths.
IV. Formula
None
8.17.110 Count of Unavailable Resources
I. Entity Name
NRSC
II. Description
It is the count of failures in allocating resources including the calling module control
table and paths.
IV. Formula
None
8.17.111 Count of No Suitable Service Quality
I. Entity Name
NSSQUA
II. Description
It is the count of calls with no suitable service qualities. This cause value reports the
service quality defined in the X.213 cannot be provided (for example, throughput and
transfer delay).

8-247
IV. Formula
None
8.17.112 Counts of Facility Applied Not Preserved Before
I. Entity Name
FACNPV
II. Description
It is the count of services or optional projects not preserved before.
IV. Formula
None
8.17.113 Count of CUG Outgoing Call Restriction
I. Entity Name
CUGBC
II. Description
It is the count of calls barred due to CUG call-out restrictions.
IV. Formula
None
8.17.114 Count of CUG Incoming Call Restriction
I. Entity Name
CUGUALW
II. Description
It is the count of CUG incoming calls barred due to CUG call-in restrictions.

8-248
IV. Formula
None
8.17.115 Count of Bearer Capability Authorized
I. Entity Name
BCUNP
II. Description
It is the count of calls released due to no bearer services registered.
IV. Formula
None
8.17.116 Count of No Available Bearer Capability
I. Entity Name
NBC
II. Description
It is the count of messages indicating the MSC has no bearer resources, including the
trunk and software resources.
IV. Formula
None
8.17.117 Count of No Suitable Service or Optional Project
I. Entity Name
NSSOOP

8-249
II. Description
It is the count of no suitable services or optional projects.
IV. Formula
None
8.17.118 Count of Bearer Capability Not Implemented
I. Entity Name
BCNLO
II. Description
It is the count of calls released due to no implemented bearer services.
IV. Formula
None
8.17.119 Count of Path Type Not Implemented
I. Entity Name
RTNLO
II. Description
It is the count of calls with the path type not implemented. In this case, the equipment
sends this cause value.
IV. Formula
None

8-250
8.17.120 Count of AOC Service Request Failures
I. Entity Name
AOCRF
II. Description
It is the count of AOC service request failures.
IV. Formula
None
8.17.121 Count of ACM Equaling or Greater Than ACM max
I. Entity Name
ACMEG
II. Description
It is the count of ACMs equaling or greater than the ACM max.
IV. Formula
None
8.17.122 Count of Requested Equipment Not Implemented
I. Entity Name
FACNLO
II. Description
It is the count of requested equipment not implemented.
IV. Formula
None

8-251
8.17.123 Count of Restricted Bearer Capability
I. Entity Name
LTDDIBC
II. Description
It is the count of calls released due to restricted bearer capability. The callers have
registered the non-restricted services, but the equipment sending the cause value only
supports the restricted services.
IV. Formula
None
8.17.124 Count of IWF Resource Unavailable
I. Entity Name
IWFRU
II. Description
It is the count of unavailable IWF resources.
IV. Formula
None
8.17.125 Count of Service or Optional Project Not Implemented
I. Entity Name
SOPNLO
II. Description
It is the count of services or optional projects not implemented.

8-252
IV. Formula
None
8.17.126 Count of Invalid Call Reference Values
I. Entity Name
INVCR
II. Description
The equipment sends this cause value because it receives the message carrying the
calling reference value that is not used on the current subscriber-network interface.
IV. Formula
None
8.17.127 Count of Identified Route Not Exist
I. Entity Name
RUNEXT
II. Description
It is the count of identified routes that do not exist.
IV. Formula
None
8.17.128 Count of Callee not CUG Subscriber
I. Entity Name
CLDNOCUG
II. Description
It is the count of messages indicating the callees are not CUG subscribers.

8-253
IV. Formula
None
8.17.129 Count of Incompatible Terminals
I. Entity Name
TEUCPT
II. Description
It is the count of incompatible terminals. The caller bearer capability specifies the
non-voice service, but the callee does not support the ISUP interface or other interfaces
that support the data services. The TUP supports non-restricted services if the ACB
(access barred) is not received.
IV. Formula
None
8.17.130 Count of CUG Not Exist
I. Entity Name
NECUG
II. Description
It is the count of supplementary service failures due to the non-existence of CUGs.
IV. Formula
None
8.17.131 Count of Invalid Transit Network Selection
I. Entity Name
INVTNL

8-254
II. Description
The received transit network identifier is not the correct format as defined in the
Appendix C.
IV. Formula
None
8.17.132 Count of Invalid Messages
I. Entity Name
INVMSG
II. Description
It is the count of invalid messages.
IV. Formula
None
8.17.133 Count of Non-Existent or Not Implemented Message Types
I. Entity Name
MSGNOEXT
II. Description
It is the count of message types that do not exist or are not implemented.
IV. Formula
None

8-255
8.17.134 Count of Non-Existent or Not Implemented Message Units
I. Entity Name
IENOEXT
II. Description
It is the count of message units that do not exist or are not implemented.
IV. Formula
None
8.17.135 Count of Timeout Recoveries
I. Entity Name
TOUT
II. Description
It is the count of timeout recoveries of timers.
IV. Formula
None
8.17.136 Count of Non-Existent or Not Implemented Parameters
I. Entity Name
PARANOEXT
II. Description
It is the count of parameters that do not exist or are not implemented.
IV. Formula
None

8-256
8.17.137 Count of Messages Carrying Unidentified Parameters
I. Entity Name
UNRECPARA
II. Description
It is the count of messages carrying the unidentified parameters.
IV. Formula
None
8.17.138 Count of Protocol errors
I. Entity Name
PROERR
II. Description
It is the count of protocol errors.
IV. Formula
None
8.17.139 Count of Interworking
I. Entity Name
INTWORK
II. Description
It is the count of interworking.
IV. Formula
None

8-257
8.18 Incoming Traffic
8.18.1 Overview of MS_OFFICE_INC_TRAF
Name Description
SEIZ Count of seizure
PDIMP Count of incomplete numbers
INVADR Count of invalid addresses
SYSFLCL Count of failed calls due to internal failure
ALBLCL Count of call failures due to overload
FWCTLCL Count of call failures due to network management
MNTCIR Count of circuits in maintenance
ANSR Answer rate
ALTN Count of connected calls
ALTT Connected traffic
ALTR Call completion rate
UPOT Count of callee power-off

I. Entity Name
SEIZ
II. Description
It is the count of seizure of incoming trunk circuits or BICC CIC.
It is measured when a call seizes an incoming trunk circuit or BICC CIC.
It is measured when the ISUP receives the IAM. See point A in the following figure.

8-258
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
CCB ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of calls answered, no matter whether the calls are in supplementary
services (CFU, CFB, or CFNR).
It is measured when the Connect message is received.
It is measured when the ISUP receives the Connect message. See point C in the
following figure.

8-259
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
CCB ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None
8.18.4 Count of Incomplete Numbers
I. Entity Name
PDIMP
II. Description
The incoming (bidirectional) trunk cannot define whether the call is a terminating call or
tandem call due to incomplete number. It includes the following cases:
The trunk does not send number.
The number is discarded during the dialing.
The interval of dialing is timeout.
The incoming trunk releases the call.
It is measured when the incoming trunk stops collecting the numbers due to abnormity.
The cause value of the REL message may be one of the following.
CV_NORMAL
CV_NORMAL_CALL_CLEAR
CV_RELEASE_BEFORE_ANSWER
CV_RELEASE_BEFORE_RING

8-260
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
REL
CCB ISUP(inc)
A

The cause value of the Release message may be one of the following.
CV_LONG_TIME_NO_DIALING
CV_PARTIAL_DIAL_TIMEOUT
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
REL
Release
Release
REL

CV_LONG_TIME_NO_DIALING
CV_PARTIAL_DIAL_TIMEOUT

8-261
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
ACM
Alerting
Alerting
ACM
REL
Release
Release
REL

IV. Formula
None
8.18.5 Count of Invalid Addresses
I. Entity Name
INVADR
II. Description
The numbers received by the incoming trunk are not consistent with the existing
destination address or the confirmed address numbers. The call is processed by
intercepting (sending signal tone, announcement, or operator speech). The numbers
include the invalid number and the number by which the callee cannot be found.
It is measured when the complete number is wrong.
1) Invalid address (case 1)
CV_NUMBER_CHANGED
CV_DIAL_NO_RESERED
CV_UNALOC_CODE
CV_INVALID_CODE_FORM
CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOUGH
CV_ERROR_INCLUDE_LONG_DISTANCE

8-262
CV_GSM_CLD_DN_NO_EXIST
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
REL
Release
Release
REL

2) Invalid address (case 2)
CV_NUMBER_CHANGED
CV_DIAL_NO_RESERED
CV_UNALOC_CODE
CV_INVALID_CODE_FORM
CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOUGH
CV_ERROR_INCLUDE_LONG_DISTANCE
CV_GSM_CLD_DN_NO_EXIST

8-263
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
ACM
Alerting
Alerting
ACM
REL
Release
Release
REL

IV. Formula
None
8.18.6 Count of Failed Calls Due to Internal Failure
I. Entity Name
SYSFLCL
II. Description
For the requested destination address, the outgoing circuit is available, but the transit
network cannot implement the connection. In addition, there are no other paths
available. The resources cannot be obtained for intra- or inter-module calls.
It is measured when the MSC applies for the internal resources.
1) Call failures due to internal failures (case 1)
CV_TEMPORARY_FAILURE
CV_ERROR_FOR_THE_TIME_BEING

8-264
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
REL
Release
Release
REL

2) Call failures due to internal failures (case 1)
CV_TEMPORARY_FAILURE
CV_ERROR_FOR_THE_TIME_BEING
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
ACM
Alerting
Alerting
ACM
REL
Release
Release
REL

IV. Formula
None

8-265
8.18.7 Count of Call Failures Due to Overload
I. Entity Name
ALBLCL
II. Description
It is the count of failed calls due to CPU overload.
It is measured when the call is released due to CPU overload (cause#60).
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
REL
Release
Release
REL


8-266
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
ACM
Alerting
Alerting
ACM
REL
Release
Release
REL

IV. Formula
None
8.18.8 Count of Call Failures Due to Network Management
I. Entity Name
FWCTLCL
II. Description
It is the count of failed calls due to network management.
It is measured when the call is released due to the network management.

8-267
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
REL
Release
Release
REL

ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
ACM
Alerting
Alerting
ACM
REL
Release
Release
REL

IV. Formula
None

8-268
I. Entity Name
SERL
II. Description
message is received. The final result is indicated in Erlang (ITU-T Rec. Q.722). Point A
in the following figure is the start point of the measurement and B or C is the end point.
IAM
MSC Server
MSC Server
REL
B
REL
C
A
IAM
MSC Server
MSC Server
REL
B
REL
C
A

IV. Formula
None
I. Entity Name
RERL
II. Description
It is the traffic generated when incoming calls are in the answered status.
to that the REL, CLF or CBK message is received. The final result is indicated in Erlang

8-269
(ITU-T Rec. Q.722). Point A in the following figure is the start point of the measurement
and B or C is the end point.
IAM
MSC Server
MSC Server
REL
B
REL
C
ANM
A
IAM
MSC Server
MSC Server
REL
B
REL
C
ANM
A

IV. Formula
None
8.18.11 Count of Circuits in Maintenance
I. Entity Name
MNTCIR
II. Description
It is the count of circuits that are in maintenance state on the outgoing (bidirectional)
trunk.
It is measured when a circuit is in maintenance status.
IV. Formula
None
8.18.12 Answer Rate
I. Entity Name
ANSR
II. Description

8-270
IV. Formula
ANSR = ANS/ SEIZ
I. Entity Name
ALTN
II. Description
It is the count of connected calls on the incoming trunk.
It is measured when the MSC sends the ACM to the originating office.
It is measured when the ISUP receives the Alerting message. See point B in the
following figure.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
ACM
Alerting
IAM
Setup
Setup Ack
Alerting
ACM
CCB ISUP(inc)
B
ANM
Connect
Connect Ack
ANM
Connect
Connect Ack
C
A

IV. Formula
None

8-271
I. Entity Name
ALTT
II. Description
the REL, CLF, or CBK message is sent. The final result is indicated in Erlang (ITU-T
Rec. Q.722). Point A in the following figure is the start point of the measurement and B
or C is the end point.
IAM
MSC Server
MSC Server
ACM
A
REL
REL
B
C
IAM
MSC Server
MSC Server
ACM
A
REL
REL
B
C

IV. Formula
None
I. Entity Name
ALTR
II. Description

8-272
IV. Formula
ALTR = ALTN/SEIZ
I. Entity Name
UPOT
II. Description
callees power-off.
1) Count of Callee Power-Off (case 2)
The cause value of the REL message is CV_GSM_CLD_USER_NOT_ACTIVE.
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
REL
Release
Release
REL

2) Count of Callee Power-Off (case 2)
The cause value of the REL message is CV_GSM_CLD_USER_NOT_ACTIVE.

8-273
ISUP(out) MTP MTP
Setup
Setup Ack
IAM
IAM
Setup
Setup Ack
CCB ISUP(inc)
A
ACM
Alerting
Alerting
ACM
REL
Release
Release
REL

IV. Formula
None
8.19 Source TMG Destination Route Traffic
8.19.1 Overview of MS_MGWID_ROUTE_TRAF
Name Description
TMGRTBID Count of seizure attempts
TMGRTSZ Count of seizure
TMGRTACM Count of ringings received
TMGRTANS Count of answered calls
TMGRTCNTR Call completion rate
TMGRTANSR Answer rate
TMGRTSERL Seizure traffic
TMGRTCERL Connected traffic
TMGRTAERL Answered traffic
TMGRTLCR Count of outgoing trunk overflow
TMGRTABR Count of releases before ringing
TMGRTAAR Count of releases before the pickup

8-274
Name Description
TMGRTRNA Count of callee no reply
TMGRTUDB Count of callee determined busy
TMGRTUB Count of callee busy
TMGRTIVA Count of invalid addresses
TMGRTPNR Count of paging no reply
TMGRTAS Count of subscriber absence
TMGRTSSR Count of subscriber service restricted
TMGRTSPT Count of special tones
TMGRTCG Count of peer office congestions
TMGRTIWK Count of interworking failures
TMGRTOTH Count of other failures
TMGRTRES Count of re-routing
TMGRTRESF Count of re-routing failures
TMGRTUMGEF Count of UMG failures
TMGRTNOFRF Count of circuit all busy

8.19.2 Count of Seizure Attempts
I. Entity Name
TMGRTBID
II. Description
It is the count of seizure attempts on the source TMG destination route.
It is measured when the following situations are met:
The MSC finds out the call is a tandem call according to the called number
analysis.
The source TMG number and the destination area index are not null. See point A

8-275
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
TMGRTSZ
II. Description
It is the count of seizures on the source TMG destination route. It is measured after the
successful routing.
The MSC finds out the call is a tandem call according to the called number
analysis.
The source TMG number and the destination area index are not null.
The route is successfully selected. See point A in the following figure.

8-276
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
8.19.4 Count of Ringings Received
I. Entity Name
TMGRTACM
II. Description
It is the count of alerting on the source TMG destination route. It is measured when the
ACM is received from the backward office.
The MSC finds out the call is a tandem call.
The source TMG number and the destination area index are not null.
The ACM is received from the backward office. See point B in the following figure.

8-277
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
TMGRTANS
II. Description
It is the count of ANMs received from the terminating office on the source TMG
destination route.
It is measured when the MSC receives the ANM from the terminating office in a
forwarding call, under the situation that the source TMG number and the destination
area index are not null. See point C in the following figure.

8-278
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
TMGRTCNTR
II. Description
It is the completion rate of the source TMG destination route. It is calculated on the
BAM with the formula (Count of answered calls + Count of subscriber determined call
failures)/Count of call attempts.
It is calculated on the BAM. The formula is: (Count of answered calls + Count of
releases before ringing + Count of callee no reply + Count of callee determined busy +
Count of callee busy + Count of invalid addresses + Count of callee absent + Count of
subscriber service restrictions + Count of special tones)/Count of seizure attempts.
IV. Formula
TMGRTCNTR = (TMGRTANS + TMGRTABR + TMGRTRNA + TMGRTUDB +
TMGRTUB + TMGRTIVA + TMGRTAS + TMGRTSSR + TMGRTSPT)/TMGRTBID
8.19.7 Answer Rate
I. Entity Name
TMGRTANSR

8-279
II. Description
It is the count of answer rate on the source TMG destination route.
IV. Formula
TMGRTANSR = TMGRTANS/TMGRTBID
I. Entity Name
TMGRTSERL
II. Description
It is the traffic generated during the call attempts on the source TMG destination route.
It is measured from the start of the call attempt to the end of the attempt. Point A in the
following figure is the start point of the measurement.
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None

8-280
I. Entity Name
TMGRTCERL
II. Description
It is the traffic generated when calls on the source TMG destination route are in the
connected status. The measurement begins from the moment the phone rings to that
the call is released.
It is measured from the moment the phone rings to that the call is released. See point B
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
TMGRTAERL
II. Description
It is the traffic generated when calls on the source TMG destination route are in
answered status. The measurement begins from the moment the call is answered to
that the call is released.

8-281
It is measured from the moment the call is answered to that the call is released. See
point C in the following figure.
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
TMGRTLCR
II. Description
It is the count of outgoing trunk overflow on the source TMG destination route.
It is measured when the MSC sends the REL message before the call is connected due
to the outgoing trunk selection timeout or failure. See point A in the following figure.

8-282
ANM/ANC
A
MSC Server
IAM
RLC
REL

IV. Formula
None
I. Entity Name
TMGRTABR
II. Description
It is the count of active releases by the callers before calls are connected on the source
TMG destination route.
It is measured when the MSC receives the call release message from a caller before

8-283
ACM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
I. Entity Name
TMGRTAAR
II. Description
It is the count of active releases on the source TMG destination route by the callers
before the pickup.
It is measured when the MSC receives the REL message from a caller before the callee
picks up the phone. See point A in the following figure.

8-284
ACM
IAM
A
MSC Server
IAM
REL
ACM
ANM/ANC
RLC

IV. Formula
None
8.19.14 Count of Callee No Reply
I. Entity Name
TMGRTRNA
II. Description
It is the count of messages indicating that the calls are not replied on the source TMG
destination route because no backward ANM is received.
It is measured when the MSC does not receive the ANM from the terminating office for
a long time. See point A in the following figure.

8-285
RLC
IAM
A
MSC Server
IAM
REL
ACM
ANM/ANC
ACM

IV. Formula
None
8.19.15 Count of Callee Determined Busy
I. Entity Name
TMGRTUDB
II. Description
It is the count of incoming calls directly rejected by the mobile callees after the ringing
on the source TMG destination route.
It is measured when the MSC receives the REL message from the callee after the
ringing.

8-286
ACM
IAM
A
MSC Server
IAM
REL
ACM
ANM/ANC
RLC

IV. Formula
None
I. Entity Name
TMGRTUB
II. Description
It is the count of call connections failed because callees are busy on the source TMG
destination route.
It is measured when the MSC receives the REL message before the call is connected.

8-287
ACM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.17 Count of Invalid Addresses
I. Entity Name
TMGRTIVA
II. Description
It is the count of invalid addresses on the source TMG destination route. The calls are
released before they are connected due to invalid addresses.
It is measured when the call is released due to the invalid address. See point A in the
following figure.

8-288
ANM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.18 Count of Paging No Reply
I. Entity Name
TMGRTPNR
II. Description
It is the count of paging no reply on the source TMG destination route. The calls are
released before they are connected due to paging no reply.
It is measured when the call is released due to paging no reply. See point A in the
following figure.

8-289
ANM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.19 Count of Subscriber Absence
I. Entity Name
TMGRTAS
II. Description
It is the count of subscribers absent on the source TMG destination route. The calls are
released before they are connected due to subscribers absent.
It is measured when the call is released because the subscriber is absent. See point A

8-290
ANM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.20 Count of Subscriber Service Restricted
I. Entity Name
TMGRTSSR
II. Description
It is the count of subscriber service restricted on the source TMG destination route. The
calls are released before they are connected due to service restrictions.
It is measured when the call is released because the subscriber service is restricted.

8-291
ANM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.21 Count of Special Tones
I. Entity Name
TMGRTSPT
II. Description
It is the count of special tones on the source TMG destination route.
It is measured when the ACM is received from the backward office, and the message
carries the cause value CV_SEND_PRIVATE_TONE (132). See point A in the following
figure.

8-292
IAM
A
MSC Server
IAM
ACM(CV_SEND_PRIVATE_TONE)

IV. Formula
None
I. Entity Name
TMGRTCG
II. Description
It is the count of peer office congestions on the source TMG destination route.
It is measured when the MSC receives the REL message due to peer office congestion.

8-293
ANM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.23 Count of Interworking Failures
I. Entity Name
TMGRTIWK
II. Description
It is the count of interworking failures on the source TMG destination route. The calls
are released before they are connected due to interworking failures.
It is measured when the call is released due to interworking failure. See point A in the
following figure.

8-294
ANM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.19.24 Count of Other Failures
I. Entity Name
TMGRTOTH
II. Description
It is the count of other failures without specified cause values on the source TMG
destination route.
The failures are those not specified in this document.
IV. Formula
None
8.19.25 Count of Re-Routing
I. Entity Name
TMGRTRES
II. Description
It is the count of re-routing after the failure on the TMG destination route.

8-295
It is measured when the MSC reselect the route after the source TMG destination route
failure.
If it occurs in the local MSC, see point A in the following figure.
IAM
A
MSC Server
IAM

If the route is reselected in the originating office after the routing failure in the backward
office, point A in the following figure is the measurement point.
IAM
A
MSC Server
IAM
REL

IV. Formula
None

8-296
8.19.26 Count of Re-Routing Failures
I. Entity Name
TMGRTRESF
II. Description
It is the count of re-routing failures after the source TMG destination routing failure.
It is measured when the MSC releases the call due to the re-routing failure.
If it occurs in the local MSC, point A in the following figure is the measurement point.
IAM
A
MSC Server
IAM

If the route is reselected in the originating office after the routing failure in the backward
office, point A in the following figure is the measurement point.

8-297
IAM
A
MSC Server
IAM
REL

IV. Formula
None
8.19.27 Count of UMG Failures
I. Entity Name
TMGRTUMGEF
II. Description
It is the count of source TMG destination route failures because the UMG is faulty.
It is measured when the MSC releases the call due to UMG failure. If it is the local UMG
failure, point A in the following figure is the measurement point.

8-298
A
MSC Server
IAM

If it is the backward office UMG failure, point A in the following figure is the
measurement point.
IAM
A
MSC Server
IAM
REL

IV. Formula
None
8.19.28 Count of Circuit All Busy
I. Entity Name
TMGRTNOFRF
II. Description
It is the count of all circuits busy which result in the source TMG destination route
failures.

8-299
It is measured when the MSC releases the call due to all circuits busy.
If all local circuits are busy, see point A in the following figure.
A
MSC Server
IAM

If all backward office circuits are busy, see point A in the following figure.
IAM
A
MSC Server
IAM
REL

IV. Formula
None

8-300
8.20 Transit Traffic
8.20.1 Overview of MS_OFFICE_TRN_TRAF
Name Description
OTKBID Count of outgoing trunk seizure attempts
OTKSEIZ Count of outgoing trunk seizure
ALTT Connected traffic
ANSR Answer rate
TRNSEIZ Count of call attempts
DWNT Count of wrongly dialed numbers
CFCR
Count of failed call attempts due to common resource
application failure
POCT Count of peer office congestions
CRAR Count of releases before the pickup

8.20.2 Count of Outgoing Trunk Seizure Attempts
I. Entity Name
OTKBID
II. Description
It is the count of seizure attempts on outgoing trunk circuits in the forwarding calls.

8-301
It is measured when the MSC selects the route for the callee after the number analysis.
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
8.20.3 Count of Outgoing Trunk Seizure
I. Entity Name
OTKSEIZ
II. Description
It is the count of successful seizures on outgoing trunk circuits in the forwarding calls.
It is measured when the MSC receives the ACM which indicates the call successfully
seizes the trunk circuit.

8-302
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of ACMs sent to the originating office in the forwarding calls.
It is measured when the MSC sends the ACM to the originating office after receiving the
ACM from the terminating office. See point B in the following figure.

8-303
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of forwarding calls answered.
It is measured when the MSC receives the ANM. See point C in the following figure.

8-304
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
BRGABN
II. Description
It is the count of active releases by the callers before the fixed-line callees' phones ring
in the forwarding calls.
It is measured when the MSC receives the REL or CLF message from a caller before

8-305
ACM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
I. Entity Name
LRUOFL
II. Description
It is the count of failures of outgoing (bidirectional) trunk seizure attempts originated by
the MSC in the forwarding calls.
It is measured when the MSC fails to select an internal outgoing trunk (bidirectional) in
a forwarding call. See point A in the following figure.

8-306
MSC Server
IAM
A
Outgoing trunk
overflow
MSC Server
MSC Server
IAM

IV. Formula
None
I. Entity Name
CBSY
II. Description
It is the count of call connections failed because callees are busy in the forwarding
calls.
The MSC receives the REL message. If the cause value in the message is
CV_SL_BUSY or CV_ST_BUSY, or CV_BUSY in an outgoing call, the measurement
begins. See point A in the following figure.

8-307
ACM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
I. Entity Name
SERL
II. Description
It is the traffic generated during the forwarding call attempts.
Q.722).
Point A in the following figure is the start point of the measurement and call release is
the end point.

8-308
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
ALTT
II. Description
It is the traffic generated when forwarding calls are connection status.
It is measured from the moment the ACM message is sent to the source MSC to that
the REL message is sent to the destination MSC. The final result is indicated in Erlang
(ITU-T Rec. Q.722).
the end point.

8-309
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
RERL
II. Description
It is the traffic generated when forwarded calls are in the answered status.
It is measured from the moment the Answer signal is sent to the source MSC to that the
REL message is sent to the destination MSC. The final result is indicated in Erlang
(ITU-T Rec. Q.722).
Point C in the following figure is the start point of the measurement and call release is
the end point.

8-310
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
CNTR
II. Description
IV. Formula
CNTR = CNT/TRNSEIZ
8.20.13 Answer Rate
I. Entity Name
ANSR
II. Description

8-311
IV. Formula
ANSR = ANS/TRNSEIZ
I. Entity Name
TRNSEIZ
II. Description
It is the count of incoming trunk call attempts in which the calls are found out to be the
tandem ones by analyzing the called numbers.
After receiving the IAI or IAM message from the originating office, the MSC analyzes
the called number. It is measured when the MSC finds that the call is a tandem one.
ACM
IAM
ANM/ANC
C
A
B
MSC Server
ACM
ANM/ANC
IAM

IV. Formula
None
I. Entity Name
DWNT
II. Description
It is the count of wrong numbers dialed in the forwarding calls, which result in call
connection failures.

8-312
It is measured when the MSC sends the REL (unallocated number or incomplete
address) message to the originating office after receiving the same message from the
terminating office. See point A in the following figure.
ACM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
8.20.16 Count of Failed Call Attempts Due to Common Resource Application
Failures
I. Entity Name
CFCR
II. Description
It is measured when the MSC fails to allocate the internal common resources. See

8-313
ACM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
I. Entity Name
POCT
II. Description
situation.
The MSC fails to select an internal outgoing (bidirectional) trunk in a forwarding
call.

8-314
ACM
IAM
A
MSC Server
IAM
REL
RLC

IV. Formula
None
I. Entity Name
CRAR
II. Description
It is the count of active releases by the callers before the pickup in the forwarding calls.
It is measured when the MSC receives the REL message from a mobile caller before
the callee picks up the phone. See point A in the following figure.

8-315
ACM
IAM
A
MSC Server
IAM
REL
ACM
ANM/ANC
RLC

IV. Formula
None

08-Chapter 8 Total Traffic of The Office

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

08-Chapter 8 Total Traffic of The Office

Hochgeladen von

Copyright:

Verfügbare Formate

Technical Manual Performance Measurement Entities

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents

Das könnte Ihnen auch gefallen