MSOFTX3000 Technical Manual-Performance Measurement Entities

Chapter 1 Overview .........................................................................................
1-1
1.1 Measurement Set ................................................................................... 1-1
1.2 Measurement Unit .................................................................................. 1-1
1.3 Relationship Between Measurement Object and Measurement Unit ..... 1-2
1.4 Measurement Entity ............................................................................... 1-2
Chapter 2 MSC Basic Functions .................................................................... 2-1
2.1 Overview of Measurement Set ............................................................... 2-1
2.2 MSC Basic Table.................................................................................... 2-1
2.2.1 Overview of MS_BASIC_TABLE_TRAF ........................................ 2-1
2.2.2 Count of Level Updates ................................................................. 2-2
2.2.3 Count of Ciphering Mode Setting Requests ................................... 2-3
2.2.4 Count of Ciphering Mode Setting Successes ................................ 2-4
2.2.5 Count of Routing Information Requests ......................................... 2-5
2.2.6 Count of Successes in Receiving Roaming Numbers ................... 2-6
2.2.7 Count of Successes in Receiving Forwarded-to Numbers ............ 2-7
2.2.8 Count of Sent MO Short Messages ............................................... 2-8
2.2.9 Count of Successful MO Short Messages (Sent) .......................... 2-8
2.2.10 Count of Received MT Short Messages ...................................... 2-10
2.2.11 Count of Successful MT Short Messages (Received) ................. 2-11
2.2.12 Count of Use of TMSI at MM Layer ............................................. 2-11
2.2.13 Count of Use of IMSI at MM Layer ............................................... 2-21
2.2.14 Count of TMSI Reallocation Requests ......................................... 2-30
2.2.15 Count of TMSI Reallocation Successes....................................... 2-32
2.2.16 Count of IMSI Detachments ......................................................... 2-34
2.2.17 Count of IMSI Attachments .......................................................... 2-35
2.2.18 Count of Pagings ......................................................................... 2-37
2.2.19 Count of Paging Responses ........................................................ 2-37
2.2.20 Count of SOR Basic Call Requests ............................................. 2-38
2.2.21 Count of Successes of Basic SOR Call ....................................... 2-39
2.2.22 Count of SOR Early Forward Call Requests ................................ 2-40
2.2.23 Count of Successes of SOR Early Forward Call .......................... 2-41
2.2.24 Count of SOR Late Forward Call Requests ................................. 2-42
2.2.25 Count of Successes of SOR Late Forward Call ........................... 2-43
2.2.26 Count of SOR Requests for Routing ............................................ 2-44
2.2.27 Count of SOR Requests for MSRN .............................................. 2-45
2.2.28 Count of Receiving MSRN During SOR Routing ......................... 2-46
2.2.29 Count of Successes of SOR for MSRN ....................................... 2-47
2.3 Authentication ......................................................................................... 2-48
2.3.1 Overview of MS_TYPE_AUTH ...................................................... 2-48
2.3.2 Count of Authentication Set Requests to HLR ............................... 2-49
2.3.3 Count of Authentication Set Receipts from HLR ............................ 2-49
2.3.4 Count of Empty Authentication Set Receipts from HLR ................. 2-50
2.3.5 Count of Authentication Set Requests to PVLR ............................. 2-51
2.3.6 Count of Authentication Set Receipts from PVLR .......................... 2-52
2.3.7 Count of Authentication Requests ................................................. 2-52
2.3.8 Count of Successful Authentications ............................................. 2-53
2.3.9 Count of Authentication Failures Due to Illegal SRES ................... 2-54
2.3.10 Count of Authentication Requests with TMSI .............................. 2-55
2.3.11 Count of Authentication Failures Due to Illegal SRES (with
TMSI) ...................................................................................................... 2-55
2.3.12 Count of Successful Authentications After IMSI Being
Identified ................................................................................................. 2-56
2.3.13 Count of Failures in Responding to Authentication Requests...... 2-57
2.3.14 Count of Failure Responses to Authenication Requests ............. 2-58
2.4 Location Update ..................................................................................... 2-59
2.4.1 Overview of MS_TYPE_LOC_UP .................................................. 2-59
2.4.2 Count of Location Update Requests .............................................. 2-60
2.4.3 Count of Location Update Rejections ............................................ 2-60
2.4.4 Count of IMSI Detachments ........................................................... 2-61
2.4.5 Count of IMSI Attachments ............................................................ 2-62
2.4.6 Count of Location Update Requests in VLR .................................. 2-62
2.4.7 Count of Location Update Successes in VLR ................................ 2-63
2.4.8 Count of Location Update Requests Due to Subsriber Roaming... 2-63
2.4.9 Count of Location Update Successes Due to Subsriber
Roaming .................................................................................................. 2-64
2.4.10 Count of Location Update Successes Due to National
Roaming .................................................................................................. 2-65
2.4.11 Count of Location Update Successes Due to International
Roaming .................................................................................................. 2-65
2.4.12 Count of Location Update Failures Due to Unknown User in
HLR ......................................................................................................... 2-66
2.4.13 Count of Location Update Failures Due to Illegal MS .................. 2-67
2.4.14 Count of Location Update Failures Due to IMEI Check Failure ... 2-67
2.4.15 Count of Location Update Failures Due to PLMN Denying
Access .................................................................................................... 2-68
2.4.16 Count of Location Update Failures Due to Prohibition of
Location Area .......................................................................................... 2-69
2.4.17 Count of Location Update Failures Due to Roaming
Prohibition ............................................................................................... 2-69
2.4.18 Count of Location Update Failures Due to Protocol Failure......... 2-70
2.4.19 Count of Location Update Failures Due to Network Failure......... 2-71
Location Area in PLMN ........................................................................... 2-71
Location Area Cell ................................................................................... 2-72
2.4.22 Count of Location Update Failures Due to Other Causes............ 2-73
2.4.23 Count of Attempts to Insert User Data ......................................... 2-74
2.4.24 Count of Sucesses in Inserting User Data ................................... 2-74
2.4.25 Count of Location Update Failures Due to ARD .......................... 2-75
Chapter 3 MSC Basic Services ....................................................................... 3-1
3.2 Handover Between Two PLMNs ............................................................ 3-1
3.2.1 Overview of MS_HO_2PLMN ........................................................ 3-1
3.2.2 Count of Ultrashort Inter-MSC Handovers Between Two
PLMNs .................................................................................................... 3-2
3.2.3 Duration of Ultrashort Inter-MSC Handovers Between Two
PLMNs .................................................................................................... 3-2
3.2.4 Count of Ultrashort Intra-MSCb Handovers Between Two
PLMNs .................................................................................................... 3-3
3.2.5 Duration of Ultrashort Intra-MSCb Handovers Between Two
PLMNs .................................................................................................... 3-4
3.2.6 Count of Ultrashort Inter-BSC Handovers Between Two
PLMNs .................................................................................................... 3-5
3.2.7 Duration of Ultrashort Inter-BSC Handovers Between Two
PLMNs .................................................................................................... 3-6
3.2.8 Count of Ultrashort Intra-BSC Handovers Between Two
PLMNs .................................................................................................... 3-7
3.2.9 Duration of Ultrashort Intra-BSC Handovers Between Two
PLMNs .................................................................................................... 3-8
3.3 GSM Assignment ................................................................................... 3-9
3.3.1 Overview of MS_S_ASSIGN_TRAF .............................................. 3-9
3.3.2 Count of Requests for Traffic Channel Assignments ..................... 3-10
3.3.3 Count of Successful Traffic Channel Assignments ........................ 3-11
3.3.4 Count of Traffic Channel Assignment Failures Due to Radio
Interface Message Failure ...................................................................... 3-11
3.3.5 Count of Traffic Channel Assignment Failures Due to O&M
Intervention ............................................................................................. 3-12
3.3.6 Count of Traffic Channel Assignment Failures Due to
Equipment Failure ................................................................................... 3-13
Resource Unavailable ............................................................................. 3-14
Requested Terrestrial Resource Unavailable ......................................... 3-14
Requested Transcoding/ Rate Adaptation Unavailable .......................... 3-15
Terrestrial Resource Already Allocated .................................................. 3-16
3.3.11 Count of Traffic Channel Assignment Failures Due to Invalid
Message Content .................................................................................... 3-17
Interface Failure - Reversion to Old Channel.......................................... 3-17
Directed Retry ......................................................................................... 3-18
3.3.14 Count of Traffic Channel Assignment Failures Due to Circuit
Pool Mismatch ........................................................................................ 3-19
3.3.15 Count of Traffic Channel Assignment Failures Due to Change
of Circuit Group ....................................................................................... 3-19
3.3.16 Count of Traffic Channel Assignment Failures Due to Other
Causes .................................................................................................... 3-20
3.4 MSC Handover ....................................................................................... 3-21
3.4.1 Overview of MS_S_MSC_HO ........................................................ 3-21
3.4.2 Count of Handovers Controlled by MSC ........................................ 3-21
3.4.3 Count of Link Disconnections Due to Handover Failure ................ 3-22
3.4.4 Count of Calls Returned to Original Channels Due to Handover
Failure ..................................................................................................... 3-23
3.4.5 Count of Requests for Intra-MSC Handovers ................................ 3-24
3.4.6 Count of Successful Intra-MSC Handovers ................................... 3-24
3.4.7 Count of Requests for Basic Outgoing Handovers ........................ 3-25
3.4.8 Count of Successful Basic Outgoing Handovers ........................... 3-26
3.4.9 Count of Requests for Basic Incoming Handovers ........................ 3-26
3.4.10 Count of Successful Basic Incoming Handovers ......................... 3-27
3.4.11 Count of Requests for Subsequent Handovers Back to Local
MSC ( MSCa).......................................................................................... 3-28
3.4.12 Count of Successful Subsequent Handovers Back to Local
MSC ( MSCa).......................................................................................... 3-29
3.4.13 Count of Requests for Subsequent Handovers to MSCc
(Local MSC Is MSCa) ............................................................................. 3-30
3.4.14 Count of Successful Subsequent Handovers to MSCc (Local
MSC Is MSCa) ........................................................................................ 3-31
3.4.15 Count of Requests for Subsequent Handovers (Local MSC Is
MSCb) ..................................................................................................... 3-32
3.4.16 Count of Successful Subsequent Handovers (Local MSC Is
MSCb) ..................................................................................................... 3-33
3.5 TMSI Reallocation .................................................................................. 3-34
3.5.1 Overview of MS_S_TMSI_REALLOC_TRAF ................................ 3-34
3.5.2 Count of TMSI Reallocation Requests During Location Update .... 3-34
3.5.3 Count of Successful TMSI Reallocations During Location
Update .................................................................................................... 3-36
3.5.4 Count of TMSI Reallocation Requests During Service Access...... 3-37
3.5.5 Count of Successful TMSI Reallocations During Service
Access .................................................................................................... 3-38
3.6 WCDMA Assignment.............................................................................. 3-40
3.6.1 Overview of MS_S_ASSIGN_3G_TRAF ....................................... 3-40
3.6.2 Count of Requests for Traffic Channel Assignments ..................... 3-41
3.6.3 Count of Successful Traffic Channel Assignments ........................ 3-41
3.6.4 Count of Assignment Failures Due to RAB Preempted ................. 3-42
3.6.5 Count of Assignment Failures Due to Timeout of Establishing
RAB or Modifying Request on RNC Side................................................ 3-43
3.6.6 Count of Assignment Failures Due to Handover ............................ 3-44
3.6.7 Count of Assignment Failures Due to Requested Traffic Class
Unavailable ............................................................................................. 3-44
3.6.8 Count of Assignment Failures Due to Invalid RAB Parameter
Value ....................................................................................................... 3-45
3.6.9 Count of Assignment Failures Due to Requested Maximum Bit
Rate Unavailable ..................................................................................... 3-46
3.6.10 Count of Assignment Failures Due to Requested Guaranteed
Bit Rate Unavailable ............................................................................... 3-46
3.6.11 Count of Assignment Failures Due to Requested Transfer
Delay Unavailable ................................................................................... 3-47
Combination ............................................................................................ 3-48
3.6.13 Count of Assignment Failures Due to Violation of SDU
Parameter Conditions ............................................................................. 3-48
3.6.14 Count of Assignment Failures Due to Violation of Traffic
Handling Priority Conditions .................................................................... 3-49
3.6.15 Count of Assignment Failures Due to Violation of Guaranteed
Bit Rate Conditions ................................................................................. 3-50
3.6.16 Count of Assignment Failures Due to User Plane Version Not
Supported ............................................................................................... 3-50
3.6.17 Count of Assignment Failures Due to Iu UP Failure .................... 3-51
3.6.18 Count of Assignment Failures Due to Invalid RAB ID .................. 3-52
3.6.19 Count of Assignment Failures Due to No Remaining RAB .......... 3-52
3.6.20 Count of Assignment Failures Due to Request Superseded ....... 3-53
3.6.21 Count of Assignment Failures Due to Signaling Transport
Resource Failure ..................................................................................... 3-54
3.6.22 Count of Assignment Failures Due to O&M Intervention ............. 3-54
3.6.23 Count of Assignment Failures Due to No Resource Available ..... 3-55
3.6.24 Count of Assignment Failures Due to Unspecified Failure .......... 3-56
3.6.25 Count of Assignment Failures Due to Directed Retry .................. 3-56
3.6.26 Count of Assignment Failures Due to Iu Transport Connection
Setup Failure ........................................................................................... 3-57
3.6.27 Count of Assignment Failures Due to Other Causes ................... 3-58
3.7 Short Message Service .......................................................................... 3-58
3.7.1 Overview of MS_TYPE_SMS ........................................................ 3-58
3.7.2 Count of Attempt MO Short Messages .......................................... 3-59
3.7.3 Count of Successful MO Short Messages ..................................... 3-60
3.7.4 Count of Failures to Send MO Short Messages Due to
Authentication Failure ............................................................................. 3-62
3.7.5 Count of Failures to Send MO Short Messages Due to Setting
Ciphering Mode Failure........................................................................... 3-62
3.7.6 Count of Failures to Send MO Short Messages Due to Service
Restriction ............................................................................................... 3-63
Unknown Subscriber ............................................................................... 3-64
Equipment Not Supported ....................................................................... 3-65
3.7.9 Count of Failures to Send MO Short Messages Due to System
Failure ..................................................................................................... 3-68
3.7.10 Count of Failures to Send MO Short Messages Due to SM
Delivery Failure ....................................................................................... 3-70
Protocol Data Error ................................................................................. 3-71
3.7.12 Count of Attempt MT Short Messages ......................................... 3-73
3.7.13 Count of Successful MT Short Messages .................................... 3-73
3.7.14 Count of Failures to Send MT Short Messages Due to
Unidentified Subscriber ........................................................................... 3-74
3.7.15 Count of Failures to Send MT Short Messages Due to Absent
Subscriber ............................................................................................... 3-75
Equipment Not Supported ....................................................................... 3-76
3.7.17 Count of Failures to Send MT Short Messages Due to Illegal
Subscriber ............................................................................................... 3-76
Equipment ............................................................................................... 3-77
System Failure ........................................................................................ 3-78
3.7.20 Count of Failures to Send MT Short Messages Due to SM
Delivery Failure ....................................................................................... 3-79
3.8 GSM Cell Handover ............................................................................... 3-79
3.8.1 Overview of MS_S_CELL_HO_TRAF ........................................... 3-79
3.8.2 Count of Requests for Intra-MSC Incoming Handovers to Cell ..... 3-81
3.8.3 Count of Successful Intra-MSC Incoming Handovers to Cell ........ 3-82
3.8.4 Count of Requests for Intra-MSC Outgoing Handovers from
Cell .......................................................................................................... 3-82
3.8.5 Count of Successful Intra-MSC Outgoing Handovers from Cell .... 3-83
3.8.6 Count of Requests for Inter-MSC Incoming Handovers to Cell ..... 3-84
3.8.7 Count of Successful Inter-MSC Incoming Handovers to Cell ........ 3-85
3.8.8 Count of Requests for Inter-MSC Outgoing Handovers from
Cell .......................................................................................................... 3-87
3.8.9 Count of Successful Inter-MSC Outgoing Handovers from Cell .... 3-88
3.8.10 Count of Outgoing Handovers from Cell Due to Uplink Quality ... 3-90
3.8.11 Count of Outgoing Handovers from Cell Due to Uplink
Strength .................................................................................................. 3-90
3.8.12 Count of Outgoing Handovers from Cell Due to Downlink
Quality ..................................................................................................... 3-91
3.8.13 Count of Outgoing Handovers from Cell Due to Downlink
Strength .................................................................................................. 3-92
3.8.14 Count of Outgoing Handovers from Cell Due to Distance ........... 3-93
3.8.15 Count of Outgoing Handovers from Cell Due to Existence of
Better Cell ............................................................................................... 3-94
3.8.16 Count of Outgoing Handovers from Cell Due to Response to
MSC Request.......................................................................................... 3-95
3.8.17 Count of Outgoing Handovers from Cell Due to O&M
Intervention ............................................................................................. 3-96
3.8.18 Count of Outgoing Handovers from Cell Due to Directed
Retry ....................................................................................................... 3-97
3.8.19 Count of Outgoing Handovers from Cell Due to Change of
Circuit Group ........................................................................................... 3-98
3.8.20 Count of Outgoing Handovers from Cell Due to Other Causes ... 3-99
3.8.21 Count of Handover Failures Due to Radio Interface Message
Failure ..................................................................................................... 3-100
3.8.22 Count of Handover Failures Due to O&M Intervention ................ 3-101
3.8.23 Count of Handover Failures Due to Equipment Failure ............... 3-102
3.8.24 Count of Handover Failures Due to No Radio Resource
Available ................................................................................................. 3-103
3.8.25 Count of Handover Failures Due to Requested Terrestrial
3.8.26 Count of Handover Failures Due to Transcoding/Rate
Adaptation Unavailable ........................................................................... 3-105
3.8.27 Count of Handover Failures Due to Requested Terrestrial
Resource Already Allocated .................................................................... 3-106
3.8.28 Count of Handover Failures Due to Invalid Message Content ..... 3-107
3.8.29 Count of Handover Failures Due to Radio Interface Failure -
Reversion to Old Channel ....................................................................... 3-108
3.8.30 Count of Handover Failures Due to Ciphering Algorithm Not
Supported ............................................................................................... 3-109
3.8.31 Count of Handover Failures Due to Circuit Pool Mismatch .......... 3-110
3.8.32 Count of Handover Failures Due to Change of Circuit Group
Number ................................................................................................... 3-111
3.8.33 Count of Handover Failures Due to Requested Speech
Version Unavailable ................................................................................ 3-112
3.8.34 Count of Handover Failures Due to Protocol Error ...................... 3-113
3.8.35 Count of Handover Failures Due to Preemption .......................... 3-114
3.8.36 Count of Handover Failures Due to Other Causes ...................... 3-115
3.9 WCDMA RNC Handover ........................................................................ 3-116
3.9.1 Overview of MS_S_RNC_RELOCATION ...................................... 3-116
3.9.2 Count of Requests for Intra-MSC Incoming Handovers to RNC .... 3-119
3.9.3 Count of Successful Intra-MSC Incoming Handovers to RNC ....... 3-119
3.9.4 Count of Requests for Intra-MSC Outgoing Handovers from
RNC ........................................................................................................ 3-120
3.9.5 Count of Successful Intra-MSC Outgoing Handovers from RNC... 3-121
3.9.6 Count of Requests for Inter-MSC Incoming Handovers to RNC .... 3-122
3.9.7 Count of Successful Inter-MSC Incoming Handovers to RNC ....... 3-123
3.9.8 Count of Requests for Inter-MSC Outgoing Handovers from
RNC ........................................................................................................ 3-125
3.9.9 Count of Successful Inter-MSC Outgoing Handovers from RNC... 3-127
3.9.10 Count of Outgoing Handovers from RNC Due to Time Critical .... 3-128
3.9.11 Count of Outgoing Handovers from RNC Due to Resource
Optimization ............................................................................................ 3-129
3.9.12 Count of Outgoing Handovers from RNC Due to Radio
Resource ................................................................................................. 3-130
3.9.13 Count of Outgoing Handovers from RNC Due to Directed
Retry ....................................................................................................... 3-131
3.9.14 Count of Outgoing Handovers from RNC Due to O&M
Intervention ............................................................................................. 3-132
3.9.15 Count of Outgoing Handovers from RNC Due to Network
Optimization ............................................................................................ 3-133
3.9.16 Count of Outgoing Handovers from RNC Due to Other
Causes .................................................................................................... 3-134
3.9.17 Count of Handover Failures Due to RAB Preempted .................. 3-135
3.9.18 Count of Handover Failures Due to Handover Timeout ............... 3-136
3.9.19 Count of Handover Failures Due to Timeout of Preparing
Handover ................................................................................................ 3-137
3.9.20 Count of Handover Failures Due to Timeout of Waiting for
Relocation Complete Message ............................................................... 3-138
3.9.21 Count of Handover Failures Due to Timeout of Queuing
Radio Interface ........................................................................................ 3-139
3.9.22 Count of Handover Failures Due to Timeout of Allocating
Resource ................................................................................................. 3-140
3.9.23 Count of Handover Failures Due to Establishing Radio
Interface Unsuccessfully ......................................................................... 3-141
3.9.24 Count of Handover Failures Due to Unknown Target Cell ........... 3-142
3.9.25 Count of Handover Failures Due to Handover Cancelled ............ 3-143
3.9.26 Count of Handover Failures Due to Requested Ciphering
Algorithm Not Supported ......................................................................... 3-144
3.9.27 Count of Handover Failures Due to Change of Ciphering
Algorithm ................................................................................................. 3-145
3.9.28 Count of Handover Failures Due to Radio Interface Failure ........ 3-146
3.9.29 Count of Handover Failures Due to UTRAN ................................ 3-147
3.9.30 Count of Handover Failures Due to Requested Traffic Class
Unavailable ............................................................................................. 3-148
3.9.31 Count of Handover Failures Due to Invalid RAB Parameter
Value ....................................................................................................... 3-149
3.9.32 Count of Handover Failures Due to Requested Maximum Bit
Rate Unavailable ..................................................................................... 3-150
3.9.33 Count of Handover Failures Due to Requested Guaranteed
Bit Rate Unavailable ............................................................................... 3-151
3.9.34 Count of Handover Failures Due to Requested Transfer
Delay Unachievable ................................................................................ 3-152
Combination ............................................................................................ 3-153
3.9.36 Count of Handover Failures Due to Violation of SDU
Parameter Conditions ............................................................................. 3-154
3.9.37 Count of Handover Failures Due to Violation of Traffic
Handling Priority Conditions .................................................................... 3-155
3.9.38 Count of Handover Failures Due to Violation of Requested
Guaranteed Bit Rate Conditions ............................................................. 3-156
3.9.39 Count of Handover Failures Due to User Plane Version Not
Supported ............................................................................................... 3-157
3.9.40 Count of Handover Failures Due to Iu UP Negotiation Failure .... 3-158
3.9.41 Count of Handover Failures Due to Target System Failure ......... 3-159
3.9.42 Count of Handover Failures Due to Invalid RAB ID ..................... 3-160
3.9.43 Count of Handover Failures Due to No Remaining RAB ............. 3-161
3.9.44 Count of Handover Failures Due to Interaction with Other
Procedures .............................................................................................. 3-162
Rate for Downlink Unavailable ................................................................ 3-163
Rate for Uplink Unavailable .................................................................... 3-164
Bit Rate for Downlink Unavailable ........................................................... 3-165
Bit Rate for Uplink Unavailable ............................................................... 3-166
3.9.49 Count of Handover Failures Due to Repeated Consistency
Check Failure .......................................................................................... 3-167
3.9.50 Count of Handover Failures Due to UE Generated Signaling
Connection Released.............................................................................. 3-168
3.9.51 Count of Handover Failures Due to Requested Information
Unavailable ............................................................................................. 3-169
3.9.52 Count of Handover Failures Due to Target System Not
Supported ............................................................................................... 3-170
3.9.53 Count of Handover Failures Due to Radio Connection with
UE Lost ................................................................................................... 3-171
3.9.54 Count of Handover Failures Due to RNC Unable to Establish
All RFCs .................................................................................................. 3-172
3.9.55 Count of Handover Failures Due to Target Not Allowed .............. 3-173
3.9.56 Count of Handover Failures Due to Signaling Transport
Resource Failure ..................................................................................... 3-174
3.9.57 Count of Handover Failures Due to Iu Transport Connection
Setup Failure ........................................................................................... 3-175
3.9.58 Count of Handover Failures Due to Protocol Failure ................... 3-176
3.9.59 Count of Handover Failures Due to No Resource Available ........ 3-177
3.9.60 Count of Handover Failures Due to Unspecified Cause .............. 3-178
3.10 Ciphering Mode Setting ........................................................................ 3-179
3.10.1 Overview of MS_S_CIPHER_TRAF ............................................ 3-179
3.10.2 Count of Requests for Setting Ciphering Mode During
Location Update ...................................................................................... 3-179
3.10.3 Count of Successes in Setting Ciphering Mode During
Location Update ...................................................................................... 3-181
3.10.4 Count of Requests for Setting Ciphering Mode During Service
Access .................................................................................................... 3-182
3.10.5 Count of Successes in Setting Ciphering Mode During
Service Access ....................................................................................... 3-183
3.11 Paging .................................................................................................. 3-185
3.11.1 Overview of MS_S_PAGING_TRAF ............................................ 3-185
3.11.2 Count of PAGING Messages First Sent Through A-Interface...... 3-185
3.11.3 Count of Responses for PAGING Messages First Sent
Through A- Interface ............................................................................... 3-186
3.11.4 Count of PAGING Messages Repeatedly Sent Through
A-Interface .............................................................................................. 3-187
3.11.5 Count of Responses for PAGING Messages Repeatedly Sent
Through A- Interface ............................................................................... 3-188
3.11.6 Count of PAGING Messages First Sent Through Iu-Interface ..... 3-189
Through Iu- Interface .............................................................................. 3-190
Iu-Interface .............................................................................................. 3-191
Through Iu- Interface .............................................................................. 3-192
3.11.10 Count of PAGING Messages First Sent Through
Gs-Interface ............................................................................................ 3-193
Through Gs- Interface ............................................................................. 3-194
Gs-Interface ............................................................................................ 3-195
3.11.13 Count of Responses for PAGING Messages Repeatedly
Sent Through Gs- Interface .................................................................... 3-196
Chapter 4 MSC Special Services .................................................................... 4-1
4.2 Location Service ..................................................................................... 4-1
4.2.1 Overview of MS_LCS_SRV ........................................................... 4-1
4.2.2 Count of Location Requests (Emergency Services) ...................... 4-1
4.2.3 Count of Location Successes (Emergency Services) .................... 4-2
4.2.4 Count of Location Requests (Value-Added Services) .................... 4-3
4.2.5 Count of Location Successes (Value-Added Services) ................. 4-4
4.2.6 Count of Location Requests (PLMN Operator Services) ............... 4-5
4.2.7 Count of Location Successes (PLMN Operator Services) ............. 4-6
4.2.8 Count of Location Requests (Lawful Interception Services) .......... 4-7
4.2.9 Count of Location Successes (Lawful Interception Services) ........ 4-8
4.3 Bearer Services ...................................................................................... 4-9
4.3.1 Overview of MS_DIG_TRAF .......................................................... 4-9
4.3.2 Count of Use of Asynchronous Digital Service BS2X .................... 4-10
4.3.3 Traffic of Asynchronous Digital Service BS2X ............................... 4-10
4.3.4 Count of Use of Dedicated Digital Service BS4X........................... 4-11
4.3.5 Traffic of Dedicated Digital Service BS4X ...................................... 4-11
4.3.6 Count of Use of Synchronous Digital Service BS3X ...................... 4-12
4.3.7 Traffic of Synchronous Digital Service BS3X ................................. 4-13
4.3.8 Count of Use of Dedicated Packet Service BS5X .......................... 4-13
4.3.9 Traffic of Dedicated Packet Service BS5X ..................................... 4-14
4.3.10 Count of Use of Fax Digital Service ............................................. 4-14
4.3.11 Traffic of Fax Digital Service ........................................................ 4-15
4.3.12 Count of Use of Alternate Speech/Data Synchronous Digital
Service .................................................................................................... 4-15
4.3.13 Traffic of Alternate Speech/Data Synchronous Digital Service .... 4-16
4.3.14 Count of Use of Asynchronous Digital Service BS20 .................. 4-16
4.3.15 Traffic of Asynchronous Data Service BS20 ................................ 4-17
4.3.16 Count of Use of Basic Packet Service BS30 ............................... 4-17
4.3.17 Traffic of Basic Packet Service BS30 .......................................... 4-18
4.4 NI_LR Location....................................................................................... 4-18
4.4.1 Overview of MS_LCS_NI_LR ........................................................ 4-18
4.4.2 Count of NI_LRs ............................................................................ 4-19
4.4.3 Count of NI_LR Successes ............................................................ 4-20
4.4.4 Count of NI_LR Failures Due to System Failure ............................ 4-21
4.4.5 Count of NI_LR Failures Due to Unqualified Data ......................... 4-22
4.4.6 Count of NI_LR Failures Due to Lack of Data ................................ 4-23
4.4.7 Count of NI_LR Failures Due to Resource Limitation .................... 4-24
4.4.8 Count of Location Failures Due to Timeout in Waiting for
Report_CNF from GMLC ........................................................................ 4-25
4.4.9 Count of Location Failures Due to Timeout in Waiting for UE
Location Report Message ....................................................................... 4-26
4.5 Mobile-Originated Location Service ....................................................... 4-27
4.5.1 Overview MS_LCS_MO_LR .......................................................... 4-27
4.5.2 Count of MO Location Requests .................................................... 4-28
4.5.3 Count of MO Location Successes .................................................. 4-29
4.5.4 Count of MO Location Failures Due to MSC Failure ...................... 4-29
4.5.5 Count of MO Location Failures Due to Unqualified Data from
MSC ........................................................................................................ 4-30
4.5.6 Count of MO Location Failures Due to Lack of Data at MSC ........ 4-31
4.5.7 Count of MO Location Failures Due to Inconsistent Information
Format at MSC ........................................................................................ 4-32
4.5.8 Count of MO Location Failures Due to Unauthorized Data at
VLR ......................................................................................................... 4-33
4.5.9 Count of MO Location Failures Due to Location Method Failure
at MSC .................................................................................................... 4-34
4.5.10 Count of MO Location Failures Due to GMLC Failure ................. 4-35
4.5.11 Count of MO Location Failures Due to Lack of Data at GMLC .... 4-36
4.5.12 Count MO Location Failures Due to Resource Limitation at
GMLC...................................................................................................... 4-37
4.5.13 Count of MO Location Failures Due to Unqualified Data from
GMLC...................................................................................................... 4-38
4.5.14 Count of MO Location Failures Due to Unknown Subscriber
at GMLC .................................................................................................. 4-39
4.5.15 Count of MO Location Failures Due to Unauthorized Network
at GMLC .................................................................................................. 4-40
4.5.16 Count of MO Location Failures Due to Unknown/Unreachable
LCS Client at GMLC ............................................................................... 4-41
4.5.17 Count of MO Location Failures Due to Timeout in Waiting for
Report_ CNF Message from GMLC ........................................................ 4-42
UE Location Report Response from RNC .............................................. 4-43
4.6 Mobile-Terminated Location Service ...................................................... 4-44
4.6.1 Overview of MS_LCS_MT_LR ....................................................... 4-44
4.6.2 Count of MT Location Requests .................................................... 4-45
4.6.3 Count of MT Location Successes .................................................. 4-45
4.6.4 Count of MT Location Failures Due to System Failure .................. 4-46
4.6.5 Count of MT Location Failures Due to Lack of Data ...................... 4-47
4.6.6 Count of MT Location Failures Due to Unqualified Data ................ 4-48
4.6.7 Count of MT Location Failures Due to Inconsistent Information
Format ..................................................................................................... 4-49
4.6.8 Count of MT Location Failures Due to Unknown Subscriber ......... 4-50
4.6.9 Count of MT Location Failures Due to Absent Subscriber ............. 4-51
4.6.10 Count of MT Location Failures Due to Unauthorized Network ..... 4-52
4.6.11 Count of MT Location Failures Due to Unauthorized LCS
Client ....................................................................................................... 4-53
4.6.12 Count of MT Location Failures Due to Location Method
Failure from RNC .................................................................................... 4-54
4.6.13 Count of MT Location Failures Due to Timeout in Waiting for
UE Location Report Response from RNC .............................................. 4-55
Chapter 5 Bearer Traffic .................................................................................. 5-1
5.2 Traffic Between BICC MGs .................................................................... 5-2
5.2.1 Overview of MS_MGW_DEST_TRAF ........................................... 5-2
5.2.2 Count of Seizures .......................................................................... 5-2
5.2.3 Count of Connected Calls .............................................................. 5-3
5.2.4 Count of Answered Calls ............................................................... 5-4
5.2.5 Count of Callee Busy ..................................................................... 5-5
5.2.6 Count of Release Before Offhook .................................................. 5-6
5.2.7 Count of No Reply .......................................................................... 5-7
5.2.8 Seizure Traffic ................................................................................ 5-8
5.2.9 Traffic of Connected Calls .............................................................. 5-9
5.2.10 Traffic of Answered Calls ............................................................. 5-10
5.2.11 Call Completion Rate ................................................................... 5-11
5.2.12 Call Answer Rate ......................................................................... 5-11
5.3 Intra-Office Path Across MG .................................................................. 5-12
5.3.1 Overview of MS_INTERMGW_TRAF ............................................ 5-12
5.3.2 Count of Path Seizure Attempts ..................................................... 5-12
5.3.3 Count of Path Seizures .................................................................. 5-12
5.3.4 Count of Same MG Path Seizures ................................................. 5-13
5.3.5 Count of Direct Path Seizures ........................................................ 5-13
5.3.6 Count of Path Seizures Across One MG ....................................... 5-13
5.3.7 Count of Path Seizures Across Two MGs ...................................... 5-14
5.3.8 Count of Path Seizures Across Three MGs ................................... 5-14
5.3.9 Count of Path Overflow .................................................................. 5-15
5.4 Office Direction Outgoing Traffic ............................................................ 5-15
5.4.1 Overview of MS_OFFICEDIR_OUT_TRAF ................................... 5-15
5.4.2 Count of Seizure Attempts ............................................................. 5-16
5.4.6 Count of Overflow .......................................................................... 5-20
5.4.7 Count of Dual Seizures .................................................................. 5-20
5.4.8 Count of Trunk Retry ...................................................................... 5-21
5.4.9 Count of Peer End Congestion ...................................................... 5-22
5.4.10 Count of Callee Busy ................................................................... 5-24
5.4.11 Count of Release Before Offhook ................................................ 5-26
5.4.12 Count of No Reply........................................................................ 5-26
5.4.13 Count of Installed Bidirectional Circuits ....................................... 5-28
5.4.14 Count of Available Bidirectional Circuits ...................................... 5-29
5.4.15 Count of Blocked Bidirectional Circuits ........................................ 5-29
5.4.16 Availability of outgoing trunks ...................................................... 5-29
5.4.17 Seizure Rate ................................................................................ 5-30
5.4.19 Call Answer Rate ......................................................................... 5-30
5.4.20 Rate of Blocked Bidirectional Circuits .......................................... 5-31
5.4.21 Traffic of Bidirectional Trunk Seizures ......................................... 5-31
5.4.22 Seizure Traffic .............................................................................. 5-31
5.4.23 Traffic of Connected Calls............................................................ 5-32
5.4.25 Average Seizure Duration ............................................................ 5-33
5.4.26 Count of First Sub-Route Overflow .............................................. 5-33
5.4.27 Count of Second Sub-Route Overflow ......................................... 5-33
5.4.28 Count of Third Sub-Route Overflow ............................................. 5-34
5.4.29 Count of Fourth Sub-Route Overflow ........................................... 5-34
5.4.30 Count of Fifth Sub-Route Overflow .............................................. 5-35
5.4.31 Count of Sixth Sub-Route Overflow ............................................. 5-35
5.4.32 Count of Seventh Sub-Route Overflow ........................................ 5-35
5.4.33 Count of Eighth Sub-Route Overflow ........................................... 5-36
5.4.34 Count of Ninth Sub-Route Overflow............................................. 5-36
5.4.35 Count of Tenth Sub-Route Overflow ............................................ 5-37
5.4.36 Count of Eleventh Sub-Route Overflow ....................................... 5-37
5.4.37 Count of Twelfth Sub-Route Overflow ......................................... 5-37
5.4.38 Count of Outgoing Trunk Receiving Called Subscriber Line
Failure ..................................................................................................... 5-38
5.4.39 Count of Outgoing Trunk Calling Peer Office No Reply ............... 5-39
5.4.40 Count of Caller Release Before Ringing ...................................... 5-39
5.4.41 Average Seizure Traffic Per Line ................................................. 5-40
5.5 Office Direction Incoming Traffic ............................................................ 5-41
5.5.1 Overview of MS_OFFICEDIR_INC_TRAF ..................................... 5-41
5.5.3 Count of Terminating Call Attempts ............................................... 5-43
5.5.4 Count of Transfer Call Attempts ..................................................... 5-43
5.5.7 Count of Terminating Answers ....................................................... 5-45
5.5.8 Count of Transfer Answers ............................................................ 5-45
5.5.9 Count of Call Loss Because of Intra-Office Congestion ................. 5-46
5.5.12 Count of No Reply........................................................................ 5-48
5.5.13 Count of Installed Circuits ............................................................ 5-49
5.5.14 Count of Available Circuits ........................................................... 5-50
5.5.15 Count of Blocked Circuits ............................................................. 5-50
5.5.16 Count of Installed Bidirectional Circuits ....................................... 5-50
5.5.17 Count of Available Bidirectional Circuits ...................................... 5-51
5.5.18 Count of Blocked Bidirectional Circuits ........................................ 5-51
5.5.19 Availability of Incoming Trunk ...................................................... 5-51
5.5.21 Call Answer Rate ......................................................................... 5-52
5.5.22 Rate of Blocked Circuits............................................................... 5-53
5.5.23 Rate of Blocked Bidirectional Circuits .......................................... 5-53
5.5.24 Traffic of Bidirectional Trunk Seizures ......................................... 5-53
5.5.25 Seizure Traffic .............................................................................. 5-54
5.5.29 Average Seizure Traffic Per Line ................................................. 5-56
5.6 Destination Code Traffic ......................................................................... 5-57
5.6.1 Overview of MS_DESTCODE_TRAF ............................................ 5-57
5.6.2 Count of Call Attempt ..................................................................... 5-58
5.6.3 Count of Outgoing Trunk Seizure .................................................. 5-58
5.6.4 Count of Ringing ............................................................................ 5-58
5.6.5 Count of Answered Call ................................................................. 5-59
5.6.6 Call Completion Rate ..................................................................... 5-60
5.6.7 Call Answer Rate ........................................................................... 5-60
5.6.8 Seizure Traffic ................................................................................ 5-61
5.6.9 Traffic of Connected Call ............................................................... 5-61
5.6.10 Traffic of Answered Call ............................................................... 5-62
5.6.11 Count of Last-Choice Route Overflow ......................................... 5-62
5.6.12 Count of Early Release Before Ringing ....................................... 5-62
5.6.13 Count of Early Release Before Offhook ....................................... 5-63
5.6.14 Count of Callee No Answer .......................................................... 5-63
5.6.15 Count of Callee Rejection ............................................................ 5-64
5.6.17 Count of Invalid Address .............................................................. 5-64
5.6.18 Count of Paging Not Replied ....................................................... 5-65
5.6.19 Count of Callee Absence ............................................................. 5-65
5.6.20 Count of Restriction of Subscriber Service .................................. 5-65
5.6.21 Count of Private Tone .................................................................. 5-66
5.6.22 Count of Peer End Congestion .................................................... 5-66
5.6.23 Count of Connection Failure ........................................................ 5-67
5.6.24 Count of Callee No Reply ............................................................ 5-67
5.6.25 Count of Other Failure Reason .................................................... 5-68
5.7 Destination Traffic Distribution ............................................................... 5-68
5.7.1 Overview of MS_OFFICE_DEST_DISTRIB_TRAF ....................... 5-68
5.7.6 Seizure Traffic ................................................................................ 5-72
5.7.7 Traffic of Answered Calls ............................................................... 5-73
5.7.8 Count of Available Circuits ............................................................. 5-74
5.7.9 Count of Installed Circuits .............................................................. 5-74
5.8 Supplementary Service Traffic ............................................................... 5-76
5.8.1 Overview of MS_SS_INVOKE ....................................................... 5-76
5.8.2 Count of Supplementary Service Invoke ........................................ 5-76
5.9 Trunk Office Direction Outgoing Traffic .................................................. 5-76
5.9.1 Overview of MS_TK_OFC_OUT_TRAF ........................................ 5-76
5.9.4 Count of Received Ringing Messages ........................................... 5-79
5.9.6 Call Completion Rate ..................................................................... 5-81
5.9.7 Call Answer Rate ........................................................................... 5-81
5.9.8 Count of Overflow .......................................................................... 5-82
5.9.9 Count of Main Control Circuit Contention ...................................... 5-82
5.9.10 Count of Non¤CMain Control Circuit Contention ......................... 5-83
5.9.11 Count of Trunk Retry .................................................................... 5-84
5.9.12 Seizure Traffic .............................................................................. 5-86
5.9.15 Count of Installed Circuits ............................................................ 5-87
5.9.16 Count of Available Circuits ........................................................... 5-88
5.9.17 Count of Blocked Circuits ............................................................. 5-88
5.9.18 Count of Caller Release Before Offhook ...................................... 5-88
5.9.20 Count of Local Office Failure ....................................................... 5-90
5.9.21 Count of Callee No Answer .......................................................... 5-91
5.9.22 Count of Callee Rejection ............................................................ 5-93
5.9.24 Count of Invalid Addresses .......................................................... 5-94
5.9.25 Count of Callee Absent ................................................................ 5-94
5.9.26 Count of Restricted Subscriber Service ....................................... 5-95
5.9.27 Count of Special Signal Tone ...................................................... 5-95
5.9.28 Count of Congestion .................................................................... 5-95
5.9.29 Count of Paging No Reply ........................................................... 5-96
5.9.30 Count of Connection Failure ........................................................ 5-96
5.9.31 Count of Callee No Reply ............................................................ 5-96
5.9.32 Count of UMG Failure .................................................................. 5-98
5.9.33 Count of All Circuits Busy ............................................................ 5-98
5.9.34 Count of Other Failure Reasons .................................................. 5-99
5.9.35 Count of First Sub-Route Overflow .............................................. 5-99
5.9.36 Count of Second Sub-Route Overflow ......................................... 5-100
5.9.37 Count of Third Sub-Route Overflow ............................................. 5-100
5.9.38 Count of Fourth Sub-Route Overflow ........................................... 5-100
5.9.39 Count of Fifth Sub-Route Overflow .............................................. 5-101
5.9.40 Count of Sixth Sub-Route Overflow ............................................. 5-101
5.9.41 Count of Seventh Sub-Route Overflow ........................................ 5-102
5.9.42 Count of Eighth Sub-Route Overflow ........................................... 5-102
5.9.43 Count of Ninth Sub-Route Overflow............................................. 5-102
5.9.44 Count of Tenth Sub-Route Overflow ............................................ 5-103
5.9.45 Count of Eleventh Sub-Route Overflow ....................................... 5-103
5.9.46 Count of Twelfth Sub-Route Overflow ......................................... 5-104
5.10 Trunk Office Direction Incoming Traffic ................................................ 5-104
5.10.1 Overview of MS_TK_OFC_INC_TRAF ........................................ 5-104
5.10.2 Count of Seizures ........................................................................ 5-105
5.10.3 Count of Received Ringing Messages ......................................... 5-106
5.10.4 Count of Answered Calls ............................................................. 5-107
5.10.6 Call Answer Rate ......................................................................... 5-108
5.10.7 Seizure Traffic .............................................................................. 5-109
5.10.10 Count of Installed Circuits .......................................................... 5-110
5.10.11 Count of Available Circuits ......................................................... 5-110
5.10.12 Count of Blocked Circuits ........................................................... 5-111
5.10.13 Count of Caller Release Before Offhook.................................... 5-111
5.10.14 Count of Release Before Offhook .............................................. 5-112
5.10.15 Count of Local Office Failure ..................................................... 5-113
5.10.16 Count of Callee No Answer ........................................................ 5-114
5.10.17 Count of Callee Rejection .......................................................... 5-116
5.10.18 Count of Callee Busy ................................................................. 5-116
5.10.19 Count of Invalid Addresses ........................................................ 5-117
5.10.20 Count of Callee Absent .............................................................. 5-117
5.10.21 Count of Restricted Subscriber Service ..................................... 5-118
5.10.22 Count of Special Signal Tone .................................................... 5-118
5.10.23 Count of Congestion .................................................................. 5-118
5.10.24 Count of Paging No Reply ......................................................... 5-119
5.10.25 Count of Connection Failure ...................................................... 5-119
5.10.26 Count of Callee No Reply .......................................................... 5-119
5.10.27 Count of UMG Failure ................................................................ 5-121
5.10.28 Count of All Circuits Busy .......................................................... 5-121
5.10.29 Count of Other Failure Reasons ................................................ 5-122
5.11 Trunk Group Outgoing Traffic............................................................... 5-122
5.11.1 Overview of MS_TKGRP_OUT_TRAF ........................................ 5-122
5.11.2 Count of Seizure Attempts ........................................................... 5-124
5.11.4 Count of Connected Calls ............................................................ 5-125
5.11.6 Count of Overflow ........................................................................ 5-127
5.11.7 Count of Trunk Circuit Type Mismatch ......................................... 5-127
5.11.8 Count of Bearer Capability and Mode Mismatch ......................... 5-128
5.11.9 Count of Dual Seizures ................................................................ 5-128
5.11.10 Count of Trunk Retry.................................................................. 5-129
5.11.11 Count of Peer End Congestion .................................................. 5-130
5.11.12 Congestion Duration .................................................................. 5-132
5.11.14 Count of Callee Toll Busy .......................................................... 5-134
5.11.15 Count of Callee Local Busy ........................................................ 5-134
5.11.17 Count of No Reply ...................................................................... 5-135
5.11.21 Count of Installed Bidirectional Circuits ..................................... 5-138
5.11.22 Count of available bidirectional circuits ...................................... 5-139
5.11.23 Count of blocked bidirectional circuits ........................................ 5-139
5.11.24 Availability of outgoing trunks .................................................... 5-139
5.11.25 Seizure Rate .............................................................................. 5-140
5.11.26 Call Completion Rate ................................................................. 5-140
5.11.27 Call Answer Rate ....................................................................... 5-140
5.11.28 Rate of Blocked Circuits ............................................................. 5-141
5.11.29 Rate of Blocked Bidirectional Circuits ........................................ 5-141
5.11.30 Traffic of Bidirectional Trunk Seizures ....................................... 5-141
5.11.31 Seizure Traffic ............................................................................ 5-142
5.11.32 Traffic of Connected Calls .......................................................... 5-142
5.11.33 Traffic of Answered Calls ........................................................... 5-142
5.11.34 Average Seizure Duration .......................................................... 5-143
5.11.35 Count of Outgoing Trunk Receiving Called Subscriber Line
Failure ..................................................................................................... 5-143
5.11.36 Count of Outgoing Trunk Calling Peer Office No Reply ............. 5-144
5.11.37 Count of Caller Release Before Ringing .................................... 5-145
5.11.38 Average Seizure Traffic Per Line ............................................... 5-146
5.12 Trunk Group Incoming Traffic............................................................... 5-147
5.12.1 Overview of MS_TKGRP_INC_TRAF.......................................... 5-147
5.12.5 Count of Call Loss Because of Intra-Office Congestion............... 5-150
5.12.6 Congestion Duration .................................................................... 5-151
5.12.9 Count of No Reply........................................................................ 5-153
5.12.14 Count of available bidirectional circuits ...................................... 5-156
5.12.15 Count of blocked bidirectional circuits ........................................ 5-156
5.12.16 Availability of Incoming Trunk .................................................... 5-156
5.12.18 Call Answer Rate ....................................................................... 5-157
5.12.19 Rate of Blocked Circuits ............................................................. 5-158
5.12.22 Seizure Traffic ............................................................................ 5-159
5.12.26 Average Seizure Traffic Per Line ............................................... 5-160
5.13 VP Office Direction Incoming Traffic .................................................... 5-161
5.13.1 Overview of MS_VP_OFFICEDIR_INC_TRAF ............................ 5-161
5.13.2 Count of Seizure .......................................................................... 5-161
5.13.3 Count of Connected Call .............................................................. 5-162
5.13.4 Count of Answered Call ............................................................... 5-163
5.13.6 Call Answer Rate ......................................................................... 5-164
5.13.7 Seizure Traffic .............................................................................. 5-165
5.13.8 Traffic of Connected Call ............................................................. 5-165
5.13.10 Count of Callee Determined Busy .............................................. 5-166
5.13.11 Count of Release After Ringing ................................................. 5-167
5.13.12 Count of No Reply ...................................................................... 5-168
5.13.13 Count of Rejection of Handover from 3G to 2G ......................... 5-169
5.13.14 Count of Call Drop on RAN Side................................................ 5-169
5.13.15 Call Drop Rate on RAN Side...................................................... 5-170
5.14 VP Office Direction Outgoing Traffic .................................................... 5-171
5.14.1 Overview of MS_VP_OFFICEDIR_OUT_TRAF .......................... 5-171
5.14.2 Count of Seizure Attempt ............................................................. 5-171
5.14.3 Count of Seizure .......................................................................... 5-172
5.14.7 Call Answer Rate ......................................................................... 5-175
5.14.8 Seizure Traffic .............................................................................. 5-176
5.14.10 Traffic of Answered Call ............................................................. 5-177
5.14.13 Count of No Reply ...................................................................... 5-179
5.14.14 Count of Rejection of Handover from 3G to 2G ......................... 5-180
5.14.15 Count of Call Drop on RAN Side................................................ 5-180
5.14.16 Call Drop Rate on RAN Side...................................................... 5-181
5.15 VP Destination Traffic........................................................................... 5-182
5.15.1 Overview of MS_VP_DEST_TRAF .............................................. 5-182
5.15.2 Count of Call Attempt ................................................................... 5-182
5.15.5 Seizure Traffic .............................................................................. 5-185
5.15.8 Average Call Duration .................................................................. 5-186
5.15.10 Call Answer Rate ....................................................................... 5-187
5.15.11 Count of Abandon Before Alerting ............................................. 5-187
5.15.12 Count of Incomplete Address ..................................................... 5-188
5.15.15 Count of No Reply ...................................................................... 5-191
5.15.16 Count of Mobile Subscriber Unreachable .................................. 5-192
5.15.17 Count of Inter-Office Trunk Overflow ......................................... 5-193
5.16 VP Trunk Office Direction Incoming Traffic .......................................... 5-193
5.16.1 Overview of MS_TK_VP_OFC_INC_TRAF ................................. 5-193
5.16.2 Count of Seizure .......................................................................... 5-194
5.16.3 Count of Ringing .......................................................................... 5-195
5.16.6 Call Answer Rate ......................................................................... 5-197
5.16.7 Seizure Traffic .............................................................................. 5-198
5.16.12 Count of No Reply ...................................................................... 5-200
5.17 VP Trunk Office Direction Outgoing Traffic .......................................... 5-203
5.17.1 Overview of MS_TK_VP_OFC_OUT_TRAF ................................ 5-203
5.17.2 Count of Seizure Attempt ............................................................. 5-203
5.17.3 Count of Seizure .......................................................................... 5-204
5.17.4 Count of Ringing .......................................................................... 5-204
5.17.7 Call Answer Rate ......................................................................... 5-206
5.17.8 Seizure Traffic .............................................................................. 5-207
5.17.10 Traffic of Answered Call ............................................................. 5-207
5.17.11 Count of Overflow ...................................................................... 5-208
5.17.14 Count of No Reply ...................................................................... 5-209
Chapter 6 Call Processing .............................................................................. 6-1
6.2 GSM Call Drop Rate ............................................................................... 6-1
6.2.1 Overview of MS_2G_CALL_DROP_RATE_TRAP ........................ 6-1
6.2.3 Count of Connected MO Calls ....................................................... 6-2
6.2.4 Count of Connected MT Calls ........................................................ 6-2
6.2.5 Count of Dropped Calls.................................................................. 6-3
6.2.6 Count of Dropped MO Calls ........................................................... 6-3
6.2.7 Count of Dropped MT Calls ........................................................... 6-3
6.2.8 Count of Dropped Calls Due to Handover Failure ......................... 6-4
6.2.9 Call Drop Rate ............................................................................... 6-4
6.3 MTC Success Rate ................................................................................ 6-5
6.3.1 Overview of MS_MTC_SUCC_RATE_TRAF................................. 6-5
6.3.2 Count of Pagings ........................................................................... 6-5
6.3.3 Count of Paging Responses .......................................................... 6-6
6.3.4 Paging Success Rate..................................................................... 6-7
6.3.6 Count of Connected Intra-Office Calls ........................................... 6-8
6.3.7 Count of Connected Incoming Calls .............................................. 6-8
6.3.8 MT Call Completion Rate ............................................................... 6-8
6.4 WCDMA Call Drop Rate ......................................................................... 6-9
6.4.1 Overview of MS_3G_CALL_DROP_RATE_TRAP ........................ 6-9
6.4.3 Count of Connected MO Calls ....................................................... 6-10
6.4.4 Count of Connected MT Calls ........................................................ 6-10
6.4.5 Count of Dropped Calls.................................................................. 6-11
6.4.6 Count of Dropped MO Calls ........................................................... 6-11
6.4.7 Count of Dropped MT Calls ........................................................... 6-12
6.4.8 Count of Dropped Calls Due to Handover Failure ......................... 6-13
6.4.9 Call Drop Rate ............................................................................... 6-14
6.5 Call Setup Rate ...................................................................................... 6-14
6.5.1 Overview of MS_DELIVERY_SUCC_RATE_TRAF ....................... 6-14
6.5.2 Count of Call Setup Attempts......................................................... 6-15
6.5.3 Count of Call Setup Attempts from Mobile Subscriber to Mobile
Subscriber ............................................................................................... 6-15
6.5.4 Count of Call Setup Attempts from Mobile Subscriber to Fixed
Subscriber ............................................................................................... 6-16
6.5.5 Count of Call Setup Attempts from Fixed Subscriber to Mobile
Subscriber ............................................................................................... 6-17
6.5.6 Count of Call Setup Attempts from Fixed Subscriber to Fixed
Subscriber ............................................................................................... 6-18
6.5.7 Count of Successful Call Setups .................................................... 6-19
6.5.8 Count of Successful Call Setups from Mobile Subscriber to
Mobile Subscriber ................................................................................... 6-19
6.5.9 Count of Successful Call Setups from Mobile Subscriber to
Fixed Subscriber ..................................................................................... 6-20
6.5.10 Count of Successful Call Setups from Fixed Subscriber to
6.5.11 Count of Successful Call Setups from Fixed Subscriber to
6.5.12 Call Setup Success Rate ............................................................. 6-23
6.6 Answer Rate ........................................................................................... 6-23
6.6.1 Overview of MS_CALL_SUCC_RATE_TRAF ............................... 6-23
6.6.2 Count of Call Attempts ................................................................... 6-24
6.6.3 Count of MO Call Attempts ............................................................ 6-24
6.6.4 Count of Incoming Call Attempts by Fixed Subscriber ................... 6-25
6.6.6 Count of Answers to MO Calls ....................................................... 6-26
6.6.7 Count of Answers to Incoming Calls by Fixed Subscriber ............. 6-27
6.6.8 Answer Rate .................................................................................. 6-28
Chapter 7 Call Record ..................................................................................... 7-1
7.2 Combined Object Conditions Traffic ....................................................... 7-1
7.2.1 Overview of MS_TKGRP_INC_TRAF ............................................ 7-1
7.2.6 Seizure Traffic ................................................................................ 7-7
7.2.7 Traffic of Answered Calls ............................................................... 7-7
7.2.8 Total Seizure Duration ................................................................... 7-8
7.2.9 Total Answer Duration ................................................................... 7-8
7.2.10 Rate of Connected Calls .............................................................. 7-8
7.2.12 Average Answer Duration ............................................................ 7-9
7.2.13 Count of Malicious Call Identification Successes ......................... 7-9
7.2.14 Count of Malicious Call Identification Failures ............................. 7-10
7.2.15 Count of Switch Congestions ....................................................... 7-10
7.2.16 Count of Long Time No Dialing .................................................... 7-10
7.2.17 Count of Long Time No Reply...................................................... 7-11
7.2.18 Count of Temporary Failures ....................................................... 7-11
7.2.19 Count of Self-Test Successes...................................................... 7-11
7.2.20 Count of No Messages ................................................................ 7-12
7.2.21 Count of No Ringing..................................................................... 7-12
7.2.22 Count of No Releases .................................................................. 7-12
7.2.23 Count of Inband Signals............................................................... 7-13
7.2.24 Count of Continuity Check Failures ............................................. 7-13
7.2.25 Count of Exceed Maximum Retries ............................................. 7-13
7.2.26 Count of Subscriber Releases Before Ringing ............................ 7-14
7.2.27 Count of Releases Before Answers ............................................. 7-14
7.2.28 Count of Call Barrings .................................................................. 7-14
7.2.29 Count of Switch Failures .............................................................. 7-15
7.2.30 Count of Callee Toll Busy ............................................................ 7-15
7.2.31 Count of Callee Local Busy .......................................................... 7-15
7.2.32 Count of Peer Equipment Congestions ........................................ 7-16
7.2.33 Count of Call Failures .................................................................. 7-16
7.2.34 Count of Circuit Contentions ........................................................ 7-17
7.2.35 Count of Invalid Numbers ............................................................ 7-17
7.2.36 Count of Call Restrictions by NMS ............................................... 7-17
7.2.37 Count of CPU Congestions and Overload ................................... 7-18
7.2.38 Count of No CR Resources ......................................................... 7-18
7.2.39 Count of No CCB Resources ....................................................... 7-18
7.2.40 Count of Incoming Forwarded Call Restrictions........................... 7-19
7.2.41 Count of Dialing Interval Timeout ................................................. 7-19
7.2.42 Count of Signaling Fault............................................................... 7-19
7.2.43 Count of Black and White List Restrictions .................................. 7-20
7.2.44 Count of Caller Number Discrimination Failures .......................... 7-20
7.2.45 Count of No A Interface Circuits for Bearer Service .................... 7-20
7.2.46 Count of Circuits Without A Interface ........................................... 7-21
7.2.47 Count of CUG Service Incompatible ............................................ 7-21
7.2.48 Count of Unknown CUG .............................................................. 7-21
7.2.49 Count of Unselected CUG ........................................................... 7-22
7.2.50 Count of CUG Outgoing Call Barring ........................................... 7-22
7.2.51 Count of CUG Incoming Call Barring ........................................... 7-22
7.2.52 Count of CUG Supplementary Service Failures .......................... 7-23
7.2.53 Count of CUG Destination Incompatible ...................................... 7-23
7.2.54 Count of Call Releases ................................................................ 7-23
7.2.55 Count of Switchover Successes .................................................. 7-24
7.2.56 Count of Switchover Failures ....................................................... 7-24
7.2.57 Count of Duration Limit Timeout .................................................. 7-24
7.2.58 Count of Termination Resource Application Failures ................... 7-25
7.2.59 Count of Non-Existent Called Numbers ....................................... 7-25
7.2.60 Count of No Answer from Called Mobile Subscribers .................. 7-25
7.2.61 Count of Called Mobile Subscriber Barring of Incoming Calls ..... 7-26
7.2.62 Count of Caller Barring of Outgoing Calls .................................... 7-26
7.2.63 Count of Callees Unreachable or Switched off ............................ 7-27
7.2.64 Count of Calling Local Subscriber Without Dialing Area Code .... 7-27
7.2.65 Count of Called Mobile Subscriber Busy ..................................... 7-27
7.2.66 Count of Called Mobile Subscriber Switched off .......................... 7-28
7.2.67 Count of Needed Function Not Applied ....................................... 7-28
7.2.68 Count of Calling Mobile Subscriber in Other Area Without
Dialing 0 .................................................................................................. 7-28
7.2.69 Count of Call Forwarding Conflicts .............................................. 7-29
7.2.70 Count of Errors Found When Getting Routing Information
Through HLR .......................................................................................... 7-29
7.2.71 Count of Carrier Barring of All Outgoing Calls ............................. 7-29
7.2.72 Count of Carrier Barring of All Outgoing International Calls ........ 7-30
7.2.73 Count of Subscriber Barring of All Outgoing International
Calls ........................................................................................................ 7-30
7.2.74 Count of BOIC-exHC Barred by Subscribers ............................... 7-30
7.2.75 Count of BOIC-exHC Barred by Operators .................................. 7-31
7.2.76 Count of Carrier Barring of All Incoming Calls ............................. 7-31
7.2.77 Count of Carrier Barring of Entertainment Consoles ................... 7-31
7.2.78 Count of Carrier Barring of Consoles ........................................... 7-32
7.2.79 Count of Subscribers Out of Service Area ................................... 7-32
7.2.80 Count of Carrier Barring of National Toll ...................................... 7-33
7.2.81 Count of Call Failures Because of Unknown Reason .................. 7-33
7.2.82 Count of Unallocated Numbers .................................................... 7-33
7.2.83 Count of No Routes to Transit Network ....................................... 7-34
7.2.84 Count of No Routes to Destination .............................................. 7-34
7.2.85 Count of Sending Special Signal Tones ...................................... 7-35
7.2.86 Count of Dialing Wrong Toll Prefix ............................................... 7-35
7.2.87 Count of Unaccepted Paths ......................................................... 7-35
7.2.88 Count of Calls Established and Delivered on Path Established... 7-36
7.2.89 Count of Call Barring Decided by Carrier ..................................... 7-36
7.2.90 Count of Circuits Reserved for Reuse ......................................... 7-36
7.2.91 Count of Normal Cleared Calls .................................................... 7-37
7.2.93 Count of No Responses from Callee ........................................... 7-37
7.2.94 Count of No Answer from Callee ................................................. 7-38
7.2.95 Count of Callee Absent ................................................................ 7-38
7.2.96 Count of Call Rejected ................................................................. 7-38
7.2.97 Count of Called Numbers Changed ............................................. 7-39
7.2.98 Count of No Idle Circuits .............................................................. 7-39
7.2.99 Count of RAB Resources Pre-Used............................................. 7-39
7.2.100 Count of Destination Fault ......................................................... 7-40
7.2.101 Count of Invalid Number Format ................................................ 7-40
7.2.102 Count of Facility Rejected .......................................................... 7-40
7.2.103 Count of Responses to STATUS ENQUIRY .............................. 7-41
7.2.104 Count of Normal Cleared Calls .................................................. 7-41
7.2.105 Count of No Available Circuits ................................................... 7-41
7.2.106 Count of Network Failures ......................................................... 7-42
7.2.107 Count of Temporary Failures ..................................................... 7-42
7.2.108 Count of Switch Congestions ..................................................... 7-42
7.2.109 Count of Access Information Lost .............................................. 7-43
7.2.110 Count of Circuits Unavailable ..................................................... 7-43
7.2.111 Count of Prior Calls Blocked ...................................................... 7-43
7.2.112 Count of No Available Resources .............................................. 7-44
7.2.113 Count of No Suitable Service Quality ......................................... 7-44
7.2.114 Count of Required Facility Not Booked ...................................... 7-45
7.2.115 Count of CUG Barring Out-Group Calls ..................................... 7-45
7.2.116 Count of CUG Incoming Calls Not Allowed ................................ 7-45
7.2.117 Count of Bearer Capability Not Registered ................................ 7-46
7.2.118 Count of No Available Bearer Capability.................................... 7-46
7.2.119 Count of No Suitable Services or Optional Projects .................. 7-46
7.2.120 Count of Bearer Capability Not Carried Out ............................... 7-47
7.2.121 Count of Route Type Not Supported.......................................... 7-47
7.2.122 Count of AOC Service Request Failures ................................... 7-47
7.2.123 Count of ACMs Greater or Equal to ACMmax ........................... 7-48
7.2.124 Count of Requested Facility Not Supported ............................... 7-48
7.2.125 Count of Only Having Restricted Bearer Capability ................... 7-48
7.2.126 Count of IWF Resources Unavailable ........................................ 7-49
7.2.127 Count of Services or Optional Projects Not Supported .............. 7-49
7.2.128 Count of Invalid Call Reference ................................................. 7-49
7.2.129 Count of Identified Paths Do Not Exist....................................... 7-50
7.2.130 Count of Callees Not in CUG ..................................................... 7-50
7.2.131 Count of Incompatible Destinations ........................................... 7-50
7.2.132 Count of Non-Existent CUGs ..................................................... 7-51
7.2.133 Count of Invalid Transit Network Selections .............................. 7-51
7.2.134 Count of Invalid Messages......................................................... 7-51
7.2.135 Count of Non-Existent or Not Supported Message Types ......... 7-52
7.2.136 Count of Non-Existent or Not Supported Information
Elements ................................................................................................. 7-52
7.2.137 Count of Recoveries of Timer Timeout ...................................... 7-52
7.2.138 Count of Non-Existent or Not Invoked Parameters .................... 7-53
7.2.139 Count of Messages with Unrecognized Parameters .................. 7-53
7.2.140 Count of Protocol Errors ............................................................ 7-53
7.2.141 Count of Interworking ................................................................. 7-54
7.3 Traffic Distribution and Duration ............................................................. 7-54
7.3.1 Overview of MS_TKGRP_INC_TRAF ............................................ 7-54
7.3.2 Count of Call Source Inlet Information ........................................... 7-55
7.3.3 Count of Call Source Outlet Information ........................................ 7-55
7.3.4 Count of Caller Numbers ............................................................... 7-55
7.3.5 Count of Dialed Numbers............................................................... 7-56
7.3.6 Caller Service Request Time ......................................................... 7-57
7.3.7 Callee Service Setup Time ............................................................ 7-57
7.3.8 Ringing Time .................................................................................. 7-58
7.3.9 Answer Time .................................................................................. 7-58
7.3.10 Release Time ............................................................................... 7-58
Chapter 8 Total Traffic of the Office............................................................... 8-1
8.2 MS-Originated Outgoing Traffic .............................................................. 8-2
8.2.1 Overview of MS_OFFICE_2G_ORGOUT_TRAF .......................... 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-7
8.2.8 Count of Peer Office Congestions ................................................. 8-8
8.2.11 Count of Releases Before the Pickup .......................................... 8-11
8.2.14 Seizure Traffic .............................................................................. 8-14
8.2.15 Connected Traffic ......................................................................... 8-15
8.2.16 Answered Traffic .......................................................................... 8-16
8.2.18 Answer Rate ................................................................................ 8-17
8.3 MS-Originated Traffic ............................................................................. 8-18
8.3.1 Overview of MS_OFFICE_2G_ORG_TRAF .................................. 8-18
8.3.3 Count of Mobile Caller Authentication Failures .............................. 8-19
8.3.4 Count of Mobile Caller Ciphering Mode Setting Failures ............... 8-19
8.3.5 Count of Mobile Caller Barring ....................................................... 8-20
8.3.6 Count of Mobile Caller Trunk Resource Overflow .......................... 8-20
8.3.7 Count of Mobile Caller Traffic Channel allocations Failures .......... 8-21
8.3.10 Count of Terminal Application Failures ........................................ 8-23
8.3.11 Count of Common Resource Application Failures ....................... 8-24
8.3.14 Seizure Traffic .............................................................................. 8-27
8.3.18 Answer Rate ................................................................................ 8-28
8.3.19 Count of Callee Power-Off ........................................................... 8-29
8.4 MS-Terminated Incoming Traffic ............................................................ 8-29
8.4.1 Overview of MS_OFFICE_2G_INCTRM_TRAF ............................ 8-29
8.4.7 Count of Mobile Callee Trunk Resource Overflow ......................... 8-35
8.4.8 Count of Mobile Callee Traffic Channel allocations Failures ......... 8-36
8.4.9 Count of MS Unavailable ............................................................... 8-37
8.4.13 Count of Mobile Callee Determined Busy .................................... 8-41
8.4.15 Seizure Traffic .............................................................................. 8-43
8.4.19 Answer Rate ................................................................................ 8-46
8.5 MS-Terminated Traffic ............................................................................ 8-47
8.5.1 Overview of MS_OFFICE_2G_TRM_TRAF .................................. 8-47
8.5.6 Count of Mobile Callee Trunk Resource Overflow ......................... 8-51
8.5.7 Count of Mobile Callee Traffic Channel allocations Failures ......... 8-52
8.5.8 Count of MS Unavailable ............................................................... 8-53
8.5.12 Count of Mobile Callee Determined Busy .................................... 8-57
8.5.14 Seizure Traffic .............................................................................. 8-59
8.5.18 Answer Rate ................................................................................ 8-62
8.6 3G VP Subscriber Originated Traffic ...................................................... 8-63
8.6.1 Overview of MS_VP_3G_ORG_TRAF .......................................... 8-63
8.6.2 Count of VP Call Attempts ............................................................. 8-63
8.6.3 Count of VP Connected Calls ........................................................ 8-64
8.6.4 Count of VP Answered Calls .......................................................... 8-65
8.6.5 Count of Failures Due to Bearer Capability ................................... 8-66
8.6.6 Seizure Traffic ................................................................................ 8-67
8.6.7 VP Connected Traffic ..................................................................... 8-67
8.6.8 VP Answered Traffic ...................................................................... 8-67
8.6.9 VP Call Completion Rate ............................................................... 8-68
8.6.10 VP Answer Rate........................................................................... 8-68
8.7 3G VP Subscriber Terminated Traffic .................................................... 8-68
8.7.1 Overview of MS_VP_3G_TRM_TRAF ........................................... 8-68
8.7.2 Count of VP Call Attempts ............................................................. 8-69
8.7.3 Count of VP Connected Calls ........................................................ 8-70
8.7.4 Count of VP Answered Calls .......................................................... 8-71
8.7.5 Count of Failures Due to Bearer Capability ................................... 8-72
8.7.6 Seizure Traffic ................................................................................ 8-73
8.7.7 VP Connected Traffic ..................................................................... 8-73
8.7.8 VP Answered Traffic ...................................................................... 8-73
8.7.9 VP Call Completion Rate ............................................................... 8-74
8.7.10 VP Answer Rate........................................................................... 8-74
8.8 UE-Originated Outgoing Traffic .............................................................. 8-74
8.8.1 Overview of MS_OFFICE_3G_ORGOUT_TRAF .......................... 8-74
8.8.7 Count of Outgoing Trunk Overflow ................................................ 8-81
8.8.8 Count of Peer Office Congestions ................................................. 8-82
8.8.14 Seizure Traffic .............................................................................. 8-88
8.8.18 Answer Rate ................................................................................ 8-91
8.9 UE-Originated Traffic.............................................................................. 8-92
8.9.1 Overview of MS_OFFICE_3G_ORG_TRAF .................................. 8-92
8.9.3 Count of Mobile Caller Authentication Failures .............................. 8-93
8.9.4 Count of Mobile Caller Ciphering Mode Setting Failures ............... 8-93
8.9.5 Count of Mobile Caller Barring ....................................................... 8-94
8.9.6 Count of Mobile Caller Trunk Resource Overflow .......................... 8-94
8.9.7 Count of Mobile Caller Traffic Channel allocations Failures .......... 8-95
8.9.14 Seizure Traffic .............................................................................. 8-100
8.9.18 Answer Rate ................................................................................ 8-102
8.9.19 Count of Callee Power-Off ........................................................... 8-102
8.10 UE-Terminated Incoming Traffic .......................................................... 8-102
8.10.1 Overview of MS_OFFICE_3G_INCTRM_TRAF .......................... 8-102
8.10.2 Count of Call Attempts ................................................................. 8-103
8.10.3 Count of Releases Before Ringing ............................................... 8-104
8.10.7 Count of Mobile Callee Traffic Channel allocations Failures ....... 8-108
8.10.8 Count of MS Unavailable ............................................................. 8-109
8.10.10 Count of Releases Before the Pickup ........................................ 8-111
8.10.11 Count of Long Time No Reply .................................................... 8-112
8.10.12 Count of Mobile Callee Determined Busy .................................. 8-113
8.10.13 Count of Answered Calls ........................................................... 8-114
8.10.14 Seizure Traffic ............................................................................ 8-115
8.10.15 Connected Traffic ....................................................................... 8-116
8.10.16 Answered Traffic ........................................................................ 8-117
8.10.18 Answer Rate .............................................................................. 8-118
8.11 UE-Terminated Traffic .......................................................................... 8-119
8.11.1 Overview of MS_OFFICE_3G_TRM_TRAF ................................ 8-119
8.11.6 Count of Mobile Callee Trunk Resource Overflow ....................... 8-123
8.11.14 Seizure Traffic ............................................................................ 8-131
8.11.18 Answer Rate .............................................................................. 8-134
8.12 Outgoing Traffic .................................................................................... 8-135
8.12.1 Overview of MS_OFFICE_OUT_TRAF ....................................... 8-135
8.12.3 Count of Seizure .......................................................................... 8-136
8.12.6 Count of Not Answered Calls ....................................................... 8-139
8.12.8 Count of Call Failures Due to Overload ....................................... 8-141
8.12.9 Count of Call Failures Due to Network Management ................... 8-143
8.12.10 Count of Outgoing Trunk Overflow ............................................ 8-145
8.12.12 Count of Callee Busy in Toll Calls .............................................. 8-147
8.12.13 Count of Callee Busy in Local Calls ........................................... 8-148
8.12.14 Seizure Traffic ............................................................................ 8-148
8.12.18 Answer Rate .............................................................................. 8-151
8.12.19 Count of Call Attempts ............................................................... 8-151
8.12.20 Count of Failed Call Attempts Due to Common Resource
Application Failure .................................................................................. 8-152
8.12.21 Count of Failed Call Attempts Due to Peer Office
Congestion .............................................................................................. 8-153
8.12.23 Count of Incomplete Addresses Received ................................. 8-155
8.13 Connection Type .................................................................................. 8-158
8.13.1 Overview of MS_OFFICE_CALLNATURE_TRAF ....................... 8-158
8.13.5 Count of Barred Calls Due to Caller Service Restriction .............. 8-161
8.13.7 Count of Outgoing Trunk Overflow .............................................. 8-162
8.13.11 Seizure Traffic ............................................................................ 8-166
8.13.15 Answer Rate .............................................................................. 8-169
8.13.16 Count of MS Unavailable ........................................................... 8-170
8.13.17 Count of Failed Call Attempts Due to Inter-Trunk Failure .......... 8-170
8.13.18 Count of Failed Call Attempts Due to Inter-Trunk Failure .......... 8-171
Congestion .............................................................................................. 8-172
8.14 Intra-Office Traffic................................................................................. 8-174
8.14.1 Overview of MS_OFFICE_INT_MTM_TRAF ............................... 8-174
8.14.7 Count of Mobile Callee Trunk Resource Overflow ....................... 8-180
8.14.10 Count of Connected Calls .......................................................... 8-183
8.14.15 Seizure Traffic ............................................................................ 8-188
8.14.19 Answer Rate .............................................................................. 8-191
8.15 Call Forwarding Traffic ......................................................................... 8-192
8.15.1 Overview of MS_FORWARD_TRAF ............................................ 8-192
8.15.2 Count of Call Forwarding Attempts .............................................. 8-192
8.15.3 Count of Forwarded Calls ............................................................ 8-193
8.15.4 Count of Answered Forwarded Calls ........................................... 8-194
8.15.5 Count of Call Forwarding Seizure Traffic ..................................... 8-195
8.15.6 Count of Call Forwarding Connected Traffic ................................ 8-196
8.15.7 Call Forwarding Answered Traffic ................................................ 8-197
8.16 Forwarded Subscriber Count ............................................................... 8-198
8.16.1 Overview of MS_FORWARD_USER ........................................... 8-198
8.16.2 Count of Subscribers Forwarded to Destination .......................... 8-198
8.17 Failure Causes of the Office ................................................................. 8-202
8.17.1 Overview of MS_FAULT_REASON_TRAF .................................. 8-202
8.17.2 Count of Supplementary Service Setting Conflict ........................ 8-206
8.17.3 Count of Supplementary Service Setting Successes ................... 8-206
8.17.4 Count of Supplementary Service Setting Failures ....................... 8-207
8.17.5 Count of Supplementary Service Deregistration Successes ....... 8-207
8.17.6 Count of Supplementary Service Deregistration Failures ............ 8-207
8.17.7 Count of Supplementary Service Authentication Successes ....... 8-208
8.17.8 Count of Supplementary Service Authentication Failures............ 8-208
8.17.9 Count of Supplementary Service Application Successes ............ 8-208
8.17.10 Count of Supplementary Service Application Failures ............... 8-209
8.17.11 Count of Successes in Probing Malicious Calls ......................... 8-209
8.17.12 Count of Failures in Probing Malicious Calls ............................. 8-209
8.17.13 Count of MSC Congestions ....................................................... 8-210
8.17.14 Count of Long Time No Dialing .................................................. 8-210
8.17.16 Count of Temporary Failures ..................................................... 8-211
8.17.17 Count of Self-Test Successes .................................................... 8-211
8.17.18 Count of Long Time No Messages ............................................ 8-211
8.17.19 Count of Long Time No Ringing ................................................. 8-212
8.17.20 Count of Long Time No Release................................................ 8-212
8.17.21 Count of Inband Signals ............................................................. 8-212
8.17.22 Count of Continuity Check Failures ........................................... 8-213
8.17.23 Count of Exceeding Max. Call Attempts .................................... 8-213
8.17.24 Count of Releases Before Ringing............................................. 8-213
8.17.26 Count of Call Restrictions .......................................................... 8-214
8.17.27 Count of MSC Failures............................................................... 8-214
8.17.28 Count of Toll Calls to Busy Callee ............................................. 8-215
8.17.29 Count of Local Calls to Busy Callee ........................................... 8-215
8.17.30 Count of Peer Office Congestion ............................................... 8-215
8.17.31 Count of Call Failures ................................................................ 8-216
8.17.32 Count of Contentions ................................................................. 8-216
8.17.33 Count of Invalid Numbers .......................................................... 8-217
8.17.34 Count of Network Management Barring ..................................... 8-217
8.17.35 Count of CPU Congestions and Overload ................................. 8-217
8.17.36 Count of No CR Resources ....................................................... 8-218
8.17.37 Count of No CCB Resources ..................................................... 8-218
8.17.38 Count of Incoming Office CF Barring ......................................... 8-218
8.17.39 Count of Dialing Time Out .......................................................... 8-219
8.17.40 Count of Signaling Failures ........................................................ 8-219
8.17.41 Count of Black List Calls Barred ................................................ 8-219
8.17.42 Count of Caller Number Identification Failures .......................... 8-220
8.17.43 Count of No A Interface Resource for A Bearer Service............ 8-220
8.17.44 Count of No A Interface Resources ........................................... 8-220
8.17.45 Count of CUG Service Incompatible .......................................... 8-221
8.17.46 Count of Unknown CUG ............................................................ 8-221
8.17.47 Count of CUG Unselected ......................................................... 8-221
8.17.48 Count of CUG Outgoing Calls Barred ........................................ 8-222
8.17.49 Count of CUG Incoming Calls Barred ........................................ 8-222
8.17.50 Count of CUG Supplementary Service Failures ........................ 8-222
8.17.51 Count of CUG Destination Incompatible .................................... 8-223
8.17.52 Count of Released Calls ............................................................ 8-223
8.17.53 Count of Switchover Successes ................................................ 8-223
8.17.54 Count of Switchover Failures ..................................................... 8-224
8.17.55 Count of Call Restriction Duration Timeout ................................ 8-224
8.17.56 Count of Termination Resource Application Failures ................. 8-224
8.17.57 Count of Callee Number Not Exist (Excluding Fixed-Line
Numbers) ................................................................................................ 8-225
8.17.58 Count of Mobile Callee No Reply ............................................... 8-225
8.17.59 Count of Mobile Callee Incoming Call Restricted ....................... 8-225
8.17.60 Count of Call out Restrictions .................................................... 8-226
8.17.61 Count of Callee Unreachable ..................................................... 8-226
8.17.62 Count of Calling Local Subscriber Without Area Code .............. 8-227
8.17.63 Count of Mobile Callee Busy...................................................... 8-227
8.17.64 Count of Mobile Callee Power-Off ............................................. 8-227
8.17.65 Count of Required Function Not Applied ................................... 8-228
8.17.66 Count of Toll Calls Without "0" ................................................ 8-228
8.17.67 Count of CF Conflict ................................................................... 8-228
8.17.68 Count of Failures in HLR Obtaining Route Information .............. 8-229
8.17.69 Count of All Outgoing Calls Barred by Operators ...................... 8-229
8.17.70 Count of All Outgoing International Calls Barred by
Operators ................................................................................................ 8-229
8.17.71 Count of All Outgoing International Calls Barred by
Subscribers ............................................................................................. 8-230
8.17.72 Count of BOIC-exHC Barred by Subscribers ............................. 8-230
8.17.73 Count of BOIC-exHC Barred by Operators ................................ 8-230
8.17.74 Count of All Incoming Calls Barred by Operators ...................... 8-231
8.17.75 Count of Operators Barring Entertainment Console .................. 8-231
8.17.76 Count of Operators Barring Announcement Console ................ 8-232
8.17.77 Count of Subscriber Roaming Out ............................................. 8-232
8.17.78 Count of All National Toll Calls Barred by Operators ................. 8-232
8.17.79 Count of Cause Unknown Failures ............................................ 8-233
8.17.80 Count of Unallocated Numbers .................................................. 8-233
8.17.81 Count of No Route to Specified Transit Network ....................... 8-233
8.17.82 Count of No Route to Destination .............................................. 8-234
8.17.83 Count of Sending Private Tone .................................................. 8-234
8.17.84 Count of Wrongly Dialed Numbers of Toll Call Prefix ................ 8-235
8.17.85 Count of Unacceptable Paths .................................................... 8-235
8.17.86 Count of Calls Connected and Delivered on Established
Route ...................................................................................................... 8-235
8.17.87 Count of Calls Barred by Operators ........................................... 8-236
8.17.88 Count of Circuits Reserved for Reusing ..................................... 8-236
8.17.89 Count of Normally cleared Calls ................................................ 8-236
8.17.91 Count of No Reply ...................................................................... 8-237
8.17.92 Count of No Response............................................................... 8-237
8.17.93 Count of Callee Absent .............................................................. 8-238
8.17.94 Count of Calls Rejected ............................................................. 8-238
8.17.95 Count of Number Changed ........................................................ 8-238
8.17.96 Count of No Idle Circuits ............................................................ 8-239
8.17.97 Count of RAB Pre-Empted ......................................................... 8-239
8.17.98 Count of Callee Failures ............................................................ 8-239
8.17.99 Count of Invalid Number Formats .............................................. 8-240
8.17.100 Count of Facilities Rejected ..................................................... 8-240
8.17.101 Count of Responses to STATUS ENQUIRY ............................ 8-240
8.17.102 Count of Normally cleared Calls .............................................. 8-241
8.17.103 Count of Unavailable Circuits................................................... 8-241
8.17.104 Count of Network Failures ....................................................... 8-241
8.17.105 Count of Contemporary Failures .............................................. 8-242
8.17.106 Count of MSC Failures ............................................................. 8-242
8.17.107 Count of Accessed Messages Discarded ................................ 8-242
8.17.108 Count of Unavailable Routes ................................................... 8-243
8.17.109 Count of Unavailable Paths ..................................................... 8-243
8.17.110 Count of Unavailable Resources ............................................. 8-244
8.17.111 Count of No Suitable Service Quality....................................... 8-244
8.17.112 Counts of Facility Applied Not Preserved Before ..................... 8-244
8.17.113 Count of CUG Outgoing Call Restriction .................................. 8-245
8.17.114 Count of CUG Incoming Call Restriction .................................. 8-245
8.17.115 Count of Bearer Capability Authorized ..................................... 8-245
8.17.116 Count of No Available Bearer Capability .................................. 8-246
8.17.117 Count of No Suitable Service or Optional Project .................... 8-246
8.17.118 Count of Bearer Capability Not Implemented .......................... 8-246
8.17.119 Count of Path Type Not Implemented ...................................... 8-247
8.17.120 Count of AOC Service Request Failures ................................. 8-247
8.17.121 Count of ACM Equaling or Greater Than ACM max ................ 8-247
8.17.122 Count of Requested Equipment Not Implemented .................. 8-248
8.17.123 Count of Restricted Bearer Capability ...................................... 8-248
8.17.124 Count of IWF Resource Unavailable ........................................ 8-248
8.17.125 Count of Service or Optional Project Not Implemented ........... 8-249
8.17.126 Count of Invalid Call Reference Values ................................... 8-249
8.17.127 Count of Identified Route Not Exist .......................................... 8-249
8.17.128 Count of Callee not CUG Subscriber ....................................... 8-250
8.17.129 Count of Incompatible Terminals ............................................. 8-250
8.17.130 Count of CUG Not Exist ........................................................... 8-250
8.17.131 Count of Invalid Transit Network Selection .............................. 8-251
8.17.132 Count of Invalid Messages ....................................................... 8-251
8.17.133 Count of Non-Existent or Not Implemented Message Types ... 8-251
8.17.134 Count of Non-Existent or Not Implemented Message Units .... 8-252
8.17.135 Count of Timeout Recoveries .................................................. 8-252
8.17.136 Count of Non-Existent or Not Implemented Parameters .......... 8-252
8.17.137 Count of Messages Carrying Unidentified Parameters ............ 8-253
8.17.138 Count of Protocol errors ........................................................... 8-253
8.17.139 Count of Interworking ............................................................... 8-253
8.18 Incoming Traffic .................................................................................... 8-254
8.18.1 Overview of MS_OFFICE_INC_TRAF ......................................... 8-254
8.18.2 Count of Seizure .......................................................................... 8-254
8.18.4 Count of Incomplete Numbers ..................................................... 8-256
8.18.5 Count of Invalid Addresses .......................................................... 8-258
8.18.6 Count of Failed Calls Due to Internal Failure ............................... 8-260
8.18.7 Count of Call Failures Due to Overload ....................................... 8-262
8.18.8 Count of Call Failures Due to Network Management ................... 8-263
8.18.9 Seizure Traffic .............................................................................. 8-265
8.18.11 Count of Circuits in Maintenance ............................................... 8-266
8.18.12 Answer Rate .............................................................................. 8-266
8.18.13 Count of Connected Calls .......................................................... 8-267
8.18.16 Count of Callee Power-Off ......................................................... 8-269
8.19 Source TMG Destination Route Traffic ................................................ 8-270
8.19.1 Overview of MS_MGWID_ROUTE_TRAF ................................... 8-270
8.19.3 Count of Seizure .......................................................................... 8-272
8.19.4 Count of Ringings Received ........................................................ 8-273
8.19.7 Answer Rate ................................................................................ 8-275
8.19.8 Seizure Traffic .............................................................................. 8-276
8.19.11 Count of Outgoing Trunk Overflow ............................................ 8-278
8.19.12 Count of Releases Before Ringing............................................. 8-279
8.19.14 Count of Callee No Reply .......................................................... 8-281
8.19.17 Count of Invalid Addresses ........................................................ 8-284
8.19.18 Count of Paging No Reply ......................................................... 8-285
8.19.19 Count of Subscriber Absence .................................................... 8-286
8.19.20 Count of Subscriber Service Restricted ..................................... 8-287
8.19.21 Count of Special Tones .............................................................. 8-288
8.19.22 Count of Peer Office Congestions ............................................. 8-289
8.19.23 Count of Interworking Failures ................................................... 8-290
8.19.24 Count of Other Failures .............................................................. 8-291
8.19.25 Count of Re-Routing .................................................................. 8-291
8.19.26 Count of Re-Routing Failures .................................................... 8-293
8.19.27 Count of UMG Failures .............................................................. 8-294
8.19.28 Count of Circuit All Busy ............................................................ 8-295
8.20 Transit Traffic ....................................................................................... 8-297
8.20.1 Overview of MS_OFFICE_TRN_TRAF ........................................ 8-297
8.20.2 Count of Outgoing Trunk Seizure Attempts ................................. 8-297
8.20.3 Count of Outgoing Trunk Seizure ................................................ 8-298
8.20.7 Count of Outgoing Trunk Overflow .............................................. 8-302
8.20.9 Seizure Traffic .............................................................................. 8-304
8.20.13 Answer Rate .............................................................................. 8-307
8.20.15 Count of Wrongly Dialed Numbers ............................................ 8-308
Application Failures................................................................................. 8-309
8.20.17 Count of Peer Office Congestions ............................................. 8-310
Chapter 9 Global Components ....................................................................... 9-1
9.2 CPU Seizure Rate .................................................................................. 9-1
9.2.1 Overview of MS-CPU-OCCUP-TRAF ............................................ 9-1
9.2.2 Average Seizure Rate .................................................................... 9-2
9.2.3 Count of Congestion ...................................................................... 9-2
9.2.4 Congestion Duration ...................................................................... 9-2
9.2.5 Count of Overload .......................................................................... 9-3
9.2.6 Overload Duration .......................................................................... 9-3
9.2.7 Count of Originating and Incoming Calls ....................................... 9-3
9.2.8 Count of Incoming and Outgoing Calls .......................................... 9-4
9.2.9 Peak Seizure Rate ......................................................................... 9-4
9.2.10 Peak Seizure Time ....................................................................... 9-4
9.2.11 Peak Seizure Duration ................................................................. 9-5
9.3 Count of VLR Subscribers ...................................................................... 9-5
9.3.1 Overview of MS-VDB-MSG-SUB-STAT ......................................... 9-5
9.3.2 VLR Local Subscribers .................................................................. 9-7
9.3.3 VLR Roaming Subscribers ............................................................. 9-9
9.3.4 Subscribers with CLIP .................................................................... 9-12
9.3.5 Subscribers with CLIR ................................................................... 9-16
9.3.6 Subscribers with COLP .................................................................. 9-19
9.3.7 Subscribers with COLR.................................................................. 9-22
9.3.8 Subscribers with CFU .................................................................... 9-26
9.3.9 Subscribers with CFB .................................................................... 9-29
9.3.10 Subscribers with CFNRy .............................................................. 9-33
9.3.11 Subscribers with CFNRc .............................................................. 9-36
9.3.12 Subscribers with Call Waiting ...................................................... 9-39
9.3.13 Subscribers with Call Hold ........................................................... 9-43
9.3.14 Subscribers with Three-Party Service.......................................... 9-46
9.3.15 Subscribers with CUG.................................................................. 9-49
9.3.16 Subscribers with AoCI.................................................................. 9-53
9.3.17 Subscribers with AoCC ................................................................ 9-53
9.3.18 Subscribers with BAOC ............................................................... 9-56
9.3.19 Subscribers with BOIC ................................................................. 9-59
9.3.20 Subscribers with BOIC Except Home Country ............................. 9-62
9.3.21 Subscriber with ODB .................................................................... 9-65
9.3.22 Subscribers with ODB BAOC ....................................................... 9-68
9.3.23 Subscribers with ODB BOIC ........................................................ 9-71
9.3.24 Subscribers with ODB BOIC Except Home Country .................... 9-74
9.3.25 Subscribers with IMSI Detached .................................................. 9-77
9.3.26 IN Subscribers ............................................................................. 9-80
9.3.27 GPRS Subscribers ....................................................................... 9-83
9.3.28 Local Network Subscribers .......................................................... 9-87
9.3.29 Other Network Subscribers .......................................................... 9-89
9.3.30 Subscribers with Data Service ..................................................... 9-91
9.3.31 Subscribers with Hot Billing ......................................................... 9-94
9.3.32 Subscribers with LCS ................................................................... 9-97
9.3.33 Subscribers with PPS Triggered by Number Segment ................ 9-100
9.3.34 MO CAMEL Subscribers .............................................................. 9-103
9.3.35 CAMEL Subscribers with Dialing Service .................................... 9-106
9.3.36 MT CAMEL Subscribers in VMSC ............................................... 9-109
9.3.37 CAMEL Subscribers Invoked by Supplementary Service ............ 9-112
9.3.38 SMS CAMEL Subscribers ............................................................ 9-115
9.3.39 CAMEL Subscribers with Mobile Management ............................ 9-118
9.3.40 ALS Subscribers .......................................................................... 9-121
9.3.41 Subscribers with VP Dual Number ............................................... 9-124
9.4 Location Area Traffic Distribution ........................................................... 9-127
9.4.1 Overview of MS_LAI_STAT ........................................................... 9-127
9.4.2 Count of Local Subscribers ............................................................ 9-128
9.4.3 Count of Roaming Subscribers ...................................................... 9-130
9.4.4 Count of Switch-off Subscribers ..................................................... 9-133
9.4.5 Count of Requesting Location Update ........................................... 9-136
9.4.6 Count of Failed Location Update due to Roaming Restriction ....... 9-137
9.4.7 Count of Rejected Location Update ............................................... 9-138
9.4.8 Count of IMSI Attach ...................................................................... 9-139
9.4.9 Count of IMSI Detach..................................................................... 9-140
9.4.10 Count of MO Call Attempts .......................................................... 9-141
9.4.11 Count of MO Subscriber Release Before Connection ................. 9-142
9.4.12 Count of MO Subscriber Release Before Pickup ......................... 9-142
9.4.13 MO Call_Count of Absent Callee ................................................. 9-143
9.4.14 MO Call_Count of Busy Callee .................................................... 9-143
9.4.15 MO Call_Count of Call Completion .............................................. 9-144
9.4.16 MO Call_Count of Call Answer .................................................... 9-144
9.4.17 MO Call_Traffic of Call Completion .............................................. 9-144
9.4.18 MO Call_Traffic of Call Answer .................................................... 9-145
9.4.19 Count of Paging ........................................................................... 9-145
9.4.20 Count of Paging Response .......................................................... 9-146
9.4.21 MT Call_Count of Release Before Ringing .................................. 9-147
9.4.22 MT Call_Count of Release During Ringing .................................. 9-147
9.4.23 MT Call_Count of Call Completion ............................................... 9-148
9.4.24 MT Call_Count of Call Answer ..................................................... 9-148
9.4.25 MT Call_Traffic of Call Completion .............................................. 9-148
9.4.26 MT Call_Traffic of Call Answer .................................................... 9-149
9.4.27 Count of Move-out of Location Area ............................................ 9-149
9.4.28 Count of Successful Move-out of Location Area .......................... 9-150
9.4.29 Count of Move-in to Location Area .............................................. 9-150
9.4.30 Count of Successful Move-in to Location Area ............................ 9-151
9.4.31 Count of Call Drop by Mobile Caller............................................. 9-152
9.4.32 Count of Call Drop by Mobile Callee ............................................ 9-153
9.5 Cell Traffic Distribution ........................................................................... 9-154
9.5.1 Overview of MS_GCI_STAT .......................................................... 9-154
9.5.2 Count of Local Subscribers ............................................................ 9-155
9.5.3 Count of Roaming Subscribers ...................................................... 9-157
9.5.4 Count of Switch-off Subscribers ..................................................... 9-160
9.5.5 Count of Requesting Location Update ........................................... 9-163
9.5.6 Count of Rejected Location Update ............................................... 9-164
9.5.7 Count of IMSI Attach ...................................................................... 9-165
9.5.8 Count of IMSI Detach..................................................................... 9-166
9.5.9 Count of MO Call Attempts ............................................................ 9-167
9.5.10 Count of MO Subscriber Release Before Connection ................. 9-168
9.5.11 Count of MO Subscriber Release Before Pickup ......................... 9-168
9.5.12 MO Call_Count of Absent Callee ................................................. 9-169
9.5.13 MO Call_Count of Busy Callee .................................................... 9-169
9.5.14 MO Call_Count of Call Completion .............................................. 9-170
9.5.15 MO Call_Count of Call Answer .................................................... 9-170
9.5.16 MO Call_Traffic of Call Completion .............................................. 9-170
9.5.17 MO Call_Traffic of Call Answer .................................................... 9-171
9.5.18 MT Call_Count of Release Before Ringing .................................. 9-171
9.5.19 MT Call_Count of Release During Ringing .................................. 9-171
9.5.20 MT Call_Count of Call Completion ............................................... 9-172
9.5.21 MT Call_Count of Call Answer ..................................................... 9-172
9.5.22 MT Call_Traffic of Call Completion .............................................. 9-172
9.5.23 MT Call_Traffic of Call Answer .................................................... 9-173
9.5.24 Count of Move-out of Cell ............................................................ 9-173
9.5.25 Count of Successful Move-out of Cell .......................................... 9-174
9.5.26 Count of Move-in to Cell .............................................................. 9-174
9.5.27 Count of Successful Move-in to Cell ............................................ 9-175
9.5.28 Count of Call Drop by Mobile Caller............................................. 9-176
9.5.29 Count of Call Drop by Mobile Callee ............................................ 9-176
9.6 Count of MVNO Subscribers .................................................................. 9-177
9.6.1 Overview of MS_VDB_MVNO_SUB .............................................. 9-177
9.6.2 Count of MVNO Subscribers .......................................................... 9-177
Chapter 10 Signaling and Interfaces .............................................................. 10-1
10.1 Overview of Measurement Set ............................................................. 10-1
10.2 A-Interface Signaling Procedure Error ................................................. 10-3
10.2.1 Overview of MS_TYPE_A_PROTOCOL_ERR ............................ 10-3
10.2.2 Count of Received Messages with Cause of Radio Interface
Message Failure ..................................................................................... 10-4
10.2.3 Count of Sent Messages with Cause of Radio Interface
Message Failure ..................................................................................... 10-4
10.2.4 Count of Received Messages with Cause of Radio Interface
Failure ..................................................................................................... 10-5
10.2.5 Count of Sent Messages with Cause of Radio Interface
Failure ..................................................................................................... 10-6
10.2.6 Count of Received Messages with Cause of Invalid Message
Content ................................................................................................... 10-7
10.2.7 Count of Sent Messages with Cause of Invalid Message
Content ................................................................................................... 10-8
10.2.8 Count of Received Messages with Cause of Information
Element or Field Missing ......................................................................... 10-9
10.2.9 Count of Sent Messages with Cause of Information Element
or Field Missing ....................................................................................... 10-10
10.2.10 Count of Received Messages with Cause of Incorrect Value .... 10-10
10.2.11 Count of Sent Messages with Cause of Incorrect Value............ 10-11
10.2.12 Count of Received Messages with Cause of Unknown
Message Type ........................................................................................ 10-12
10.2.13 Count of Sent Messages with Cause of Unknown Message
Type ........................................................................................................ 10-12
10.2.14 Count of Received Messages with Cause of Unknown
Information Element ................................................................................ 10-13
10.2.15 Count of Sent Messages with Cause of Unknown
10.2.16 Count of Received Messages with Cause of Protocol Error ...... 10-14
10.2.17 Count of Sent Messages with Cause of Protocol Error .............. 10-15
10.2.18 Count of Received Messages with Cause of Terrestrial
Circuit Already Allocated ......................................................................... 10-16
10.2.19 Count of Sent Messages with Cause of Terrestrial Circuit
Already Allocated .................................................................................... 10-16
10.3 BICC SCTP Link ................................................................................... 10-17
10.3.1 Overview of MS_BICCMSG ......................................................... 10-17
10.3.2 Count of Link Disconnections ...................................................... 10-18
10.3.3 Duration of Link Disconnections .................................................. 10-18
10.3.4 Count of Link Congestion ............................................................. 10-18
10.3.5 Duration of Link Congestion......................................................... 10-19
10.3.6 Count of Messages Sent .............................................................. 10-19
10.3.7 Count of Bytes in Messages Sent ................................................ 10-19
10.3.8 Count of Messages Received ...................................................... 10-20
10.3.9 Count of Bytes in Messages Received ........................................ 10-20
10.3.10 Count of Messages Sent per Second ........................................ 10-20
10.3.11 Count of Messages Received per Second................................. 10-21
10.3.12 Count of Bits Sent per Second................................................... 10-21
10.3.13 Count of Bits Received per Second ........................................... 10-21
10.4 BICC Node Capability .......................................................................... 10-22
10.4.1 Overview of MS_BICC_NODE_CAPABILITY .............................. 10-22
10.4.2 Count of Incoming Call Attempts ................................................. 10-22
10.4.3 Count of Call Failures Due to Switching Equipment
Congestion .............................................................................................. 10-23
10.4.4 Count of Call Failures Due to No Valid Circuit ............................. 10-24
10.4.5 Count of Call Failures Due to Address Incomplete ...................... 10-25
10.4.6 Count of Call Failures Due to Temporary Failure ........................ 10-26
10.4.7 Count of Call Failures Due to Unallocated Number ..................... 10-27
10.4.8 Count of Call Failures Due to Callee Busy ................................... 10-28
10.4.9 Count of Call Failures Due to Destination Fault ........................... 10-29
10.4.10 Count of Call Failures Due to Other Causes.............................. 10-30
10.5 Base Station Controller ........................................................................ 10-31
10.5.1 Overview of MS_TYPE_BSC ....................................................... 10-31
10.5.2 Count of Reset Messages from BSC ........................................... 10-32
10.5.3 Count of Circuit Reset Messages from MSC ............................... 10-32
10.5.4 Count of Circuit Reset Messages from BSC ................................ 10-33
10.5.5 Count of Circuit Blocking Messages from BSC ............................ 10-33
10.5.6 Count of Circuit Unblocking Messages from BSC ....................... 10-34
10.5.7 Count of Circuit Group Blocking Messages from BSC ................. 10-35
10.5.8 Count of Circuit Group Unblocking Messages from BSC ............ 10-36
10.5.9 Count of Overload Messages from BSC ...................................... 10-36
10.5.10 Count of Unequipped Circuit Messages from MSC ................... 10-37
10.5.11 Count of Unequipped Circuit Messages from BSC .................... 10-37
10.5.12 Count of SAPI "N" Rejection Messages ..................................... 10-38
10.5.13 Count of Confusion Messages from BSC .................................. 10-39
10.5.14 Count of Confusion Messages from MSC .................................. 10-39
10.6 GPRS Timeout ..................................................................................... 10-40
10.6.1 Overview of MS_TYPE_GPRS_TIMEOUT .................................. 10-40
10.6.2 Count of Timeouts for Non-GPRS Service Indications ................ 10-40
10.6.3 Count of Timeouts for Getting Subscriber Information ................. 10-41
10.7 Gs-Interface Operation ......................................................................... 10-42
10.7.1 Overview of MS_TYPE_GS_OPER ............................................. 10-42
10.7.2 Count of Paging Messages on Gs-Interface ................................ 10-43
10.7.3 Count of Paging Rejection Messages on Gs-Interface ................ 10-44
10.7.4 Count of MS Unreachable Messages from SGSN ....................... 10-45
10.7.5 Count of Messages of Location Update Request ........................ 10-46
10.7.6 Count of Messages of Location Update Acceptance ................... 10-47
10.7.7 Count of Messages of Location Update Rejection ....................... 10-48
10.7.8 Count of Messages of TMSI Reallocation.................................... 10-49
10.7.9 Count of Messages of Non-GPRS Indication Request ................ 10-50
10.7.10 Count of Messages of Non-GPRS Indication Rejection ............. 10-51
10.7.11 Count of Messages of Non-GPRS Indication
Acknowledgement ................................................................................... 10-52
10.7.12 Count of Messages of MS Activity Indication ............................. 10-53
10.7.13 Count of Messages of GPRS Detachment Indication ................ 10-54
10.7.14 Count of Messages of GPRS Detachment
Acknowledgement ................................................................................... 10-55
10.7.15 Count of Messages of IMSI Detachment Indication ................... 10-56
10.7.16 Count of Messages of IMSI Detachment Acknowledgement ..... 10-57
10.7.17 Count of Messages of VLR Reset Indication ............................. 10-58
10.7.18 Count of Messages of VLR Reset Acknowledgement ............... 10-59
10.7.19 Count of Messages of SGSN Reset Indication .......................... 10-60
10.7.20 Count of Messages of SGSN Reset Acknowledgement ............ 10-61
10.7.21 Count of Messages of MS Information Request ........................ 10-62
10.7.22 Count of Messages of MS Information Response ..................... 10-63
10.7.23 Count of Messages of Mobile Management Information
Request................................................................................................... 10-64
10.7.24 Count of MS Status Abnormal Messages Received .................. 10-65
10.7.25 Count of MS Status Abnormal Messages Sent .......................... 10-66
10.8 Gs-Interface Error Cause ..................................................................... 10-67
10.8.1 Overview of MS_TYPE_GS_ERR ............................................... 10-67
10.8.2 Count of Messages with Cause of IMSI Detached for GPRS
Service .................................................................................................... 10-68
10.8.3 Count of Messages with Cause of IMSI Detached for GPRS
and Non- GPRS Services ....................................................................... 10-69
10.8.4 Count of Messages with Cause of IMSI Unknown ....................... 10-69
10.8.5 Count of Messages with Cause of IMSI Explicitly Detached
for Non- GPRS Services ......................................................................... 10-70
10.8.6 Count of Messages with Cause of IMSI Implicitly Detached
for Non- GPRS Services ......................................................................... 10-71
10.8.7 Count of Messages with Cause of MS Unreachable ................... 10-72
10.8.8 Count of Messages with Cause of Message Not Compatible
with Protocol State .................................................................................. 10-73
10.8.9 Count of Messages with Cause of Missing Mandatory
10.8.10 Count of Messages with Cause of Invalid Mandatory
Information .............................................................................................. 10-75
10.8.11 Count of Messages with Cause of Conditional IE Error ............. 10-76
10.8.12 Count of Messages with Cause of Semantically Incorrect
Message ................................................................................................. 10-77
10.8.13 Count of Messages with Cause of Message Unknown .............. 10-78
10.8.14 Count of Messages with Cause of Address Error ...................... 10-79
10.9 H.248 MGW.......................................................................................... 10-80
10.9.1 Overview of MS_H.248_MGW_TRAFIC ...................................... 10-80
10.9.2 Count of Unavailable States ........................................................ 10-81
10.9.3 Duration of Unavailable State ...................................................... 10-81
10.9.4 Count of Messages Sent .............................................................. 10-82
10.9.5 Count of Bytes in Messages Sent ................................................ 10-82
10.9.6 Count of Messages Received ...................................................... 10-82
10.9.7 Count of Bytes in Messages Received ........................................ 10-83
10.9.8 Count of Messages Unsuccessfully Sent ..................................... 10-83
10.9.9 Count of Messages Unsuccessfully Received ............................. 10-83
10.9.10 Count of Binary Encoded Messages.......................................... 10-84
10.9.11 Count of Binary Decoded Messages ......................................... 10-84
10.9.12 Count of Text Encoded Messages ............................................. 10-84
10.9.13 Count of Text Decoded Messages............................................. 10-85
10.9.14 Count of Messages Failed in Security Information
Application .............................................................................................. 10-85
10.9.15 Count of Messages Failed in Security Information
Verification .............................................................................................. 10-85
10.9.16 Count of Messages Failed in Encoding ..................................... 10-86
10.9.17 Count of Messages with Error in Decoding ................................ 10-86
10.9.18 Count of Messages Sent per Second ........................................ 10-86
10.9.19 Count of Messages Received per Second................................. 10-87
10.9.20 Count of Bits Sent per Second................................................... 10-87
10.9.21 Count of Bits Received per Second ........................................... 10-87
10.10 H.248 SCTP Link ................................................................................ 10-88
10.10.1 Overview of MS_H.248_SCTPLNK_TRAFIC ............................ 10-88
10.10.2 Count of Unavailable States ...................................................... 10-88
10.10.3 Duration of Unavailable State .................................................... 10-88
10.10.4 Count of Link Congestion ........................................................... 10-89
10.10.5 Duration of Link Congestion ....................................................... 10-89
10.10.6 Count of Messages Sent............................................................ 10-89
10.10.7 Count of Bytes in Messages Sent .............................................. 10-90
10.10.8 Count of Messages Received .................................................... 10-90
10.10.9 Count of Bytes in Messages Received ...................................... 10-91
10.10.10 Count of Messages Sent per Second ...................................... 10-91
10.10.11 Count of Messages Received per Second ............................... 10-91
10.10.12 Count of Bits Sent per Second ................................................. 10-92
10.10.13 Count of Bits Received per Second ......................................... 10-92
10.11 IP Port Traffic ..................................................................................... 10-92
10.11.1 Overview of MS_IFM_IPFLOW_TRAF ...................................... 10-92
10.11.2 Count of Packets Sent ............................................................... 10-93
10.11.3 Count of Packets Received ........................................................ 10-93
10.11.4 Count of Bytes Sent ................................................................... 10-94
10.11.5 Count of Bytes Received ........................................................... 10-94
10.11.6 Speed of Sending Packet .......................................................... 10-94
10.11.7 Speed of Receiving Packet ........................................................ 10-95
10.11.8 Bit Rate of Sending Packet ........................................................ 10-95
10.11.9 Bit Rate of Receiving Packet ..................................................... 10-95
10.11.10 Bandwidth Utilization of IP Port When Sending Packet ........... 10-96
10.11.11 Bandwidth Utilization of IP Port When Receiving Packet ........ 10-96
10.11.12 Count of Discarded Packets Received .................................... 10-96
10.11.13 Count of Packets with Invalid IP Address ................................ 10-97
10.11.14 Count of Rejected Packets for Access ..................................... 10-97
10.11.15 Count of Restricted ICMP Packets .......................................... 10-97
10.11.16 Count of Unknown IP Packets ................................................. 10-98
10.11.17 Count of Packets That IFM Fails to Transfer ........................... 10-98
10.11.18 Count of Packets That IFM Fails to Send ................................ 10-98
10.12 ISUP Circuit Group ............................................................................. 10-99
10.12.1 Overview of MS_ISUP_TKGRP_PERFORM_TRAF ................. 10-99
10.12.2 Count of Incoming Call Attempts ............................................... 10-100
10.12.3 Count of REL Messages Sent with Cause of Switching
Equipment Congestion ............................................................................ 10-101
10.12.4 Count of Messages of Circuit Group Congestion ....................... 10-103
10.12.6 Count of REL Messages Sent with Cause of Address
Incomplete .............................................................................................. 10-105
10.12.7 Count of REL Messages Sent with Cause of Temporary
Failure ..................................................................................................... 10-107
10.12.8 Count of REL Messages Sent with Cause of Unallocated
Number ................................................................................................... 10-108
10.12.9 Count of REL Messages Sent with Cause of Subscriber
Busy ........................................................................................................ 10-110
10.12.10 Count of REL Messages Sent with Cause of Destination
Fault ........................................................................................................ 10-111
10.12.11 Count of REL Messages Sent with Other Causes ................... 10-113
10.12.12 Count of Outgoing Call Attempts ............................................. 10-114
10.12.13 Count of REL Messages Received with Cause of Switching
10.12.14 Count of REL Messages Received with Cause of No Valid
Circuit ...................................................................................................... 10-117
10.12.15 Count of REL Messages Received with Cause of Address
Incomplete .............................................................................................. 10-118
10.12.16 Count of REL Messages Received with Cause of
Temporary Failure ................................................................................... 10-120
Unallocated Number ............................................................................... 10-121
10.12.18 Count of REL Messages Received with Cause of No Route
to Destination .......................................................................................... 10-123
Subscriber Busy ...................................................................................... 10-124
Destination Fault ..................................................................................... 10-126
10.12.21 Count of REL Messages Received with Other Causes ........... 10-127
10.12.22 Count of Answers Without Charging ........................................ 10-129
10.12.23 Count of Maintenance-Oriented CGB Messages..................... 10-131
10.12.24 Count of Hardware-Oriented CGB Messages .......................... 10-131
10.12.25 Count of Circuit Group Reset Messages ................................. 10-132
10.12.26 Count of Circuit Reset Messages ............................................ 10-133
10.12.27 Count of Answers..................................................................... 10-134
10.12.28 Count of Messages Received .................................................. 10-136
10.12.29 Count of Messages Sent .......................................................... 10-136
10.12.30 Count of Messages Both Received and Sent .......................... 10-137
10.12.31 Length of Messages Received ................................................. 10-138
10.12.32 Length of Messages Sent ........................................................ 10-138
10.12.33 Length of Messages Both Received and Sent ......................... 10-139
10.12.34 Count of Calls .......................................................................... 10-139
10.12.35 Length of Messages per Call ................................................... 10-140
10.12.36 Average Message Length ........................................................ 10-140
10.13 ISUP Node ......................................................................................... 10-141
10.13.1 Overview of MS_ISUP_NODE_PERFORM_TRAF ................... 10-141
10.13.3 Count of REL Messages Sent with Cause of Switching
10.13.4 Count of REL Messages Sent with Cause of No Valid Circuit ... 10-144
10.13.5 Count of REL Messages Sent with Cause of Address
Incomplete .............................................................................................. 10-146
10.13.6 Count of REL Messages Sent with Cause of Temporary
Failure ..................................................................................................... 10-147
10.13.7 Count of REL Messages Sent with Cause of Unallocated
Number ................................................................................................... 10-149
10.13.8 Count of REL Messages Sent with Cause of Subscriber
Busy ........................................................................................................ 10-150
10.13.9 Count of REL Messages Sent with Cause of Destination
Fault ........................................................................................................ 10-152
10.13.10 Count of REL Messages Sent with Other Causes ................... 10-153
10.14 ISUP Network ..................................................................................... 10-155
10.14.1 Overview of MS_ISUP_NET_PERFORM_TRAF ....................... 10-155
10.14.2 Count of Outgoing Call Attempts ............................................... 10-156
10.14.4 Count of REL Messages Received with Cause of No Valid
Circuit ...................................................................................................... 10-158
Incomplete .............................................................................................. 10-160
10.14.6 Count of REL Messages Received with Cause of Temporary
Failure ..................................................................................................... 10-161
Unallocated Number ............................................................................... 10-163
10.14.8 Count of REL Messages Received with Cause of No Route
to Destination .......................................................................................... 10-164
10.14.9 Count of REL Messages Received with Cause of Subscriber
Busy ........................................................................................................ 10-166
Destination Fault ..................................................................................... 10-167
10.14.11 Count of REL Messages Received with Other Causes ........... 10-169
10.15 ISUP Message Usage ........................................................................ 10-170
10.15.1 Overview of MS_ISUP_MSG_USING_TRAF ............................ 10-170
10.15.2 Count of Certain Messages Sent ............................................... 10-170
10.15.3 Count of Certain Messages Received ....................................... 10-171
10.16 Count of ISUP Messages ................................................................... 10-172
10.16.1 Overview of MS_ISUP_TOTAL_MSU_TRAF ............................ 10-172
10.17 ISUP Abnormality ............................................................................... 10-174
10.17.1 Overview of MS_ISUP_UNUSUAL_TRAF................................. 10-174
10.17.2 Count of Responses to RSC Not Received by T17 ................... 10-175
10.17.3 Count of GRAs Not Received by T23 ........................................ 10-176
10.17.4 Count of RLCs Not Received by T5 ........................................... 10-177
10.17.5 Count of Circuit Remote Blocking Messages ............................. 10-177
10.17.6 Count of Failures to Assign CGBA on Some Circuits ................ 10-178
10.17.7 Count of Failures to Assign CGUA on Some Circuits ................ 10-179
10.17.8 Count of Assignments of Too Many CGBAs on Some
Circuits .................................................................................................... 10-179
10.17.9 Count of Assignments of Too Many CGUAs on Some
Circuits .................................................................................................... 10-180
10.17.10 Count of Unexpected CGBAs Received .................................. 10-181
10.17.11 Count of Unexpected CGUAs Received .................................. 10-181
10.17.12 Count of Unexpected BLAs Received ...................................... 10-182
10.17.13 Count of Unexpected UBAs Received ..................................... 10-183
10.17.14 Count of BLAs Not Received by T13 ....................................... 10-183
10.17.15 Count of UBAs Not Received by T15....................................... 10-184
10.17.16 Count of CGBAs Not Received by T19 .................................... 10-185
10.17.17 Count of CGUAs Not Received by T21.................................... 10-185
10.17.18 Count of Messages with Error Format ..................................... 10-186
10.17.19 Count of Unexpected Messages Received .............................. 10-186
10.17.20 Count of Unknown Messages Received .................................. 10-187
10.18 IUA Link Set ....................................................................................... 10-187
10.18.1 Overview of MS_IUA_LS_TRAF ................................................ 10-187
10.18.4 Count of Control Messages Sent ............................................... 10-189
10.18.5 Count of Control Messages Received ....................................... 10-189
10.18.6 Count of QPTM Messages Sent ................................................ 10-190
10.18.7 Count of QPTM Messages Received ......................................... 10-191
10.18.8 Count of ERROR Messages Received ...................................... 10-192
10.18.9 Count of Bytes in Control Messages Sent ................................. 10-192
10.18.10 Count of Bytes in Control Messages Received........................ 10-193
10.18.11 Count of Bytes in QPTM Messages Sent ................................ 10-194
10.18.12 Count of Bytes in QPTM Messages Received ......................... 10-194
10.19 IUA Signaling Link .............................................................................. 10-196
10.19.1 Overview of MS_IUA_LINK_TRAF ............................................ 10-196
10.19.5 Duration of Congestion .............................................................. 10-198
10.19.8 Count of QPTM Messages Sent ................................................ 10-200
10.19.9 Count of QPTM Messages Received ......................................... 10-201
10.19.10 Count of ERROR Messages Received .................................... 10-201
10.19.11 Count of Bytes in Control Messages Sent ............................... 10-202
10.19.13 Count of Bytes in QPTM Messages Sent ................................ 10-203
10.19.14 Count of Bytes in QPTM Messages Received ......................... 10-204
10.20 M2UA Link Set ................................................................................... 10-206
10.20.1 Overview of MS_M2UA_LS_TRAF ............................................ 10-206
10.20.4 Count of MAUP Messages Sent ................................................ 10-208
10.20.5 Count of MAUP Messages Received ......................................... 10-208
10.20.6 Count of ERROR Messages Received ...................................... 10-209
10.20.8 Count of Bytes in Control Messages Received .......................... 10-211
10.20.9 Count of Bytes in MAUP Messages Sent .................................. 10-211
10.20.10 Count of Bytes in MAUP Messages Received ......................... 10-212
10.21 M2UA Link .......................................................................................... 10-214
10.21.1 Overview of MS_M2UA_LINK_TRAF ........................................ 10-214
10.21.8 Count of MAUP Messages Sent ................................................ 10-217
10.21.9 Count of MAUP Messages Received ......................................... 10-218
10.21.10 Count of ERROR Messages Received .................................... 10-218
10.21.11 Count of Bytes in Control Messages Sent ............................... 10-219
10.21.13 Count of Bytes in MAUP Messages Sent ................................ 10-221
10.21.14 Count of Bytes in MAUP Messages Received ......................... 10-221
10.22 M3UA Destination Entity .................................................................... 10-223
10.22.1 Overview of MS_M3UA_DEST_ENTITY_TRAF ........................ 10-223
10.22.2 Count of Failed Accesses .......................................................... 10-224
10.22.3 Duration of Failed Access .......................................................... 10-224
10.23 M3UA Signaling Link .......................................................................... 10-224
10.23.1 Overview of MS_M3UA_LINK_TRAF ........................................ 10-224
10.23.10 Count of Data Messages Sent ................................................. 10-230
10.23.11 Count of Data Messages Received ......................................... 10-230
10.23.12 Count of Bytes in Data Messages Sent ................................... 10-231
10.23.13 Count of Bytes in Data Messages Received ............................ 10-231
10.23.14 Count of SCCP Messages Sent ............................................... 10-232
10.23.15 Count of SCCP Messages Received ....................................... 10-233
10.23.16 Count of Bytes in SCCP Messages Sent ................................. 10-233
10.23.17 Count of Bytes in SCCP Messages Received ......................... 10-234
10.23.18 Count of TUP Messages Sent ................................................. 10-235
10.23.19 Count of TUP Messages Received .......................................... 10-235
10.23.20 Count of Bytes in TUP Messages Sent.................................... 10-236
10.23.21 Count of Bytes in TUP Messages Received ............................ 10-237
10.23.22 Count of ISUP Messages Sent ................................................ 10-237
10.23.23 Count of ISUP Messages Received ......................................... 10-238
10.23.24 Count of Bytes in ISUP Messages Sent .................................. 10-239
10.23.25 Count of Bytes in ISUP Messages Received ........................... 10-239
10.23.28 Count of Bytes in Messages Sent ............................................ 10-241
10.23.29 Count of Bytes in Messages Received .................................... 10-242
10.24 M3UA Signaling Link Set .................................................................... 10-244
10.24.1 Overview of MS_M3UA_LS_TRAF ............................................ 10-244
10.24.8 Count of Data Messages Sent ................................................... 10-249
10.24.9 Count of Data Messages Received ........................................... 10-249
10.24.10 Count of Bytes in Data Messages Sent ................................... 10-250
10.24.11 Count of Bytes in Data Messages Received ............................ 10-251
10.25 MAP Public Service Procedure Error ................................................. 10-264
10.25.1 Overview of MS_TYPE_MAP_PUBLIC_SERVICE .................... 10-264
10.25.2 Count of Session Rejections at Local MAP (OPEN_RSP) ........ 10-265
10.25.3 Count of Session Rejections at Remote MAP (OPEN_CNF) .... 10-266
10.25.4 Count of Session Aborts at Local MAP (U_ABORT_REQ) ........ 10-267
10.25.5 Count of Session Aborts at Remote MAP (U_ABORT_IND) ..... 10-268
10.25.6 Count of Provider Aborts (P_ABORT) ....................................... 10-269
10.25.7 Count of Notice Indications (NOTICE) ....................................... 10-270
10.25.8 Count of MAP_OPEN_RSP Session Rejections Due to
Other Causes .......................................................................................... 10-271
Invalid Destination Reference ................................................................. 10-272
Invalid Origination Reference.................................................................. 10-273
Application Context Not Supported ......................................................... 10-274
Potential Version Incompatibility ............................................................. 10-275
10.25.13 Count of MAP_OPEN_CNF Session Rejections Due to
Other Causes .......................................................................................... 10-276
Invalid Destination Reference ................................................................. 10-277
Invalid Origination Reference.................................................................. 10-278
Application Context Not Supported ......................................................... 10-279
Potential Version Incompatibility ............................................................. 10-280
10.25.18 Count of MAP_U_ABORT_REQ Messages Due to
Application Program Error ....................................................................... 10-281
Subscriber Resource Limited .................................................................. 10-282
Application Program Cancelled............................................................... 10-284
10.25.22 Count of MAP_U_ABORT_IND Messages Due to
Application Program Error ....................................................................... 10-285
Subscriber Resource Limited .................................................................. 10-286
Application Program Cancelled............................................................... 10-288
10.25.26 Count of MAP_P_ABORT_IND Messages Due to Provider
Failure ..................................................................................................... 10-289
10.25.27 Count of MAP_P_ABORT_IND Messages Due to
Supported Call Released ........................................................................ 10-290
10.25.28 Count of MAP_P_ABORT_IND Messages Due to Provider
Resource Limited .................................................................................... 10-291
Maintenance ........................................................................................... 10-292
10.25.30 Count of MAP_P_ABORT_IND Messages Due to Potential
Version Incompatibility ............................................................................ 10-293
Abnormal Call ......................................................................................... 10-294
10.25.32 Count of MAP_NOTICE_IND Messages Due to Abnormal
Event Detected by Remote MAP ............................................................ 10-295
10.25.33 Count of MAP_NOTICE_IND Messages Due to Response
Rejected by Remote MAP ....................................................................... 10-296
10.25.34 Count of MAP_NOTICE_IND Messages Due to Abnormal
Event Received from Remote MAP ........................................................ 10-297
10.26 MAP Operation ................................................................................... 10-298
10.26.1 Overview of MS_TYPE_MAP_OPERATION ............................. 10-298
10.26.2 Count of Messages Indicating Subscriber Unknown ................. 10-300
10.26.3 Count of Messages Indicating Base Station Unknown .............. 10-301
10.26.4 Count of Messages Indicating MSC Unknown........................... 10-302
10.26.5 Count of Messages Indicating Subscriber Unidentified ............. 10-303
10.26.6 Count of Messages Indicating SMS Subscriber Absent ............ 10-304
10.26.7 Count of Messages Indicating Equipment Unknown ................. 10-305
10.26.8 Count of Messages Indicating Roaming Not Allowed ................ 10-306
10.26.9 Count of Messages Indicating Subscriber Illegal ....................... 10-307
10.26.10 Count of Messages Indicating Bearer Services Not
Supported ............................................................................................... 10-308
10.26.11 Count of Messages Indicating Teleservices Not Supported .... 10-309
10.26.12 Count of Messages Indicating Equipment Illegal ..................... 10-310
10.26.13 Count of Messages Indicating Call Restricted ......................... 10-311
10.26.14 Count of Messages Indicating Forwarding Violation ................ 10-312
10.26.15 Count of Messages Indicating CUG Rejection ......................... 10-313
10.26.16 Count of Messages Indicating Operation on Supplementary
Services Illegal ........................................................................................ 10-314
10.26.17 Count of Messages Indicating Status Error of
Supplementary Services ......................................................................... 10-315
10.26.18 Count of Messages Indicating Supplementary Services
Unavailable ............................................................................................. 10-316
10.26.19 Count of Messages Indicating Subscription Violation of
Supplementary Services ......................................................................... 10-317
Incompatible ............................................................................................ 10-318
10.26.21 Count of Messages Indicating Function Not Supported ........... 10-319
10.26.22 Count of Messages Indicating Target Base Station Invalid ..... 10-320
10.26.23 Count of Messages Indicating Radio Resource Unavailable ... 10-321
10.26.24 Count of Messages Indicating Handover Number
Unavailable ............................................................................................. 10-322
10.26.25 Count of Messages Indicating Subsequent Handover
Failure ..................................................................................................... 10-323
10.26.26 Count of Messages Indicating Subscriber Absent ................... 10-324
10.26.27 Count of Messages Indicating Terminal Incompatible ............. 10-325
10.26.28 Count of Messages Indicating Short Term Rejection............... 10-326
10.26.29 Count of Messages Indicating Long Term Rejection ............... 10-327
10.26.30 Count of Messages Indicating MT SMS Subscriber Busy ....... 10-328
10.26.31 Count of Messages Indicating Short Message Delivery
Failure ..................................................................................................... 10-329
10.26.32 Count of Messages Indicating Message Waiting Queue
Full .......................................................................................................... 10-330
10.26.33 Count of Messages Indicating System Error ............................ 10-331
10.26.34 Count of Messages Indicating Data Loss ................................ 10-332
10.26.35 Count of Messages Indicating Data Unexpected ..................... 10-333
10.26.36 Count of Messages Indicating Registration Failure Due to
Password Invalid ..................................................................................... 10-334
10.26.37 Count of Messages Indicating Password Check Failure .......... 10-335
10.26.38 Count of Messages Indicating MSRN Unavailable .................. 10-336
10.26.39 Count of Messages Indicating Trace Buffer Full ...................... 10-337
10.26.40 Count of Messages Indicating Target Cell Outside Group
Call Area ................................................................................................. 10-338
10.26.41 Count of Messages Indicating Password Attempt Violation ..... 10-339
10.26.42 Count of Messages Indicating Number Changed .................... 10-340
10.26.43 Count of Messages Indicating Subscriber Busy ...................... 10-341
10.26.44 Count of Messages Indicating No Answer ............................... 10-342
10.26.45 Count of Messages Indicating Forwarding Failure ................... 10-343
10.26.46 Count of Messages Indicating Optimized Routing Not
Allowed ................................................................................................... 10-344
10.26.47 Count of Messages Indicating Group Call Number
Unavailable ............................................................................................. 10-345
10.26.48 Count of Messages Indicating Resource Limitation ................. 10-346
10.26.49 Count of Messages Indicating Requested Network
Unauthorized ........................................................................................... 10-347
10.26.50 Count of Messages Indicating LCS Client Unauthorized ......... 10-348
10.26.51 Count of Messages Indicating Location Method Failure .......... 10-349
10.26.52 Count of Messages Indicating LCS Client Unknown or
Unreachable ............................................................................................ 10-350
10.26.53 Count of Messages Indicating Mobility Management Event
Not Supported ......................................................................................... 10-351
10.26.54 Count of Messages Indicating Character Set Unknown .......... 10-352
10.26.55 Count of Messages Indicating USSD Subscriber Busy ........... 10-353
10.26.56 Count of Messages Indicating Operation Request .................. 10-354
10.26.57 Count of Messages Indicating Normal Response to
Operation ................................................................................................ 10-355
10.26.58 Count of Messages Indicating Operation Termination Not
Due to Timeout ....................................................................................... 10-356
10.26.59 Count of Messages Indicating Operation Timeout ................... 10-357
10.26.60 Duration of Operation............................................................... 10-358
10.27 MTP3B Signaling Link ........................................................................ 10-359
10.27.1 Overview of MS_MTP3B_LINK_TRAF ...................................... 10-359
10.27.2 Duration of Signaling Link in In-Service State ............................ 10-360
10.27.3 Count of Signaling Link Failures (All Causes) ............................ 10-360
10.27.4 Duration of Signaling Link Failure .............................................. 10-360
10.27.5 Count of Local Management Inhibition Operations .................... 10-361
10.27.6 Duration of Local Management Inhibition Operation.................. 10-361
10.27.7 Count of Remote Management Inhibition Operations ................ 10-362
10.27.8 Duration of Remote Management Inhibition Operation .............. 10-362
10.27.9 Count of Local Automatic Switchovers ...................................... 10-363
10.27.12 Count of Octets of SIF and SIO Sent ....................................... 10-364
10.27.13 Count of Octets of SIF and SIO Received ............................... 10-365
10.27.14 Count of Signaling Link Congestion ......................................... 10-366
10.27.15 Duration of Signaling Link Congestion ..................................... 10-366
10.27.16 Percentage of Signaling Link Bandwidth Used for Sending
Signaling Information .............................................................................. 10-366
10.27.17 Percentage of Signaling Link Bandwidth Used for
Receiving Signaling Information ............................................................. 10-367
10.28 MTP3B Signaling Link Set.................................................................. 10-367
10.28.1 Overview of MS_MTP3B_LINKSET_TRAF ............................... 10-367
10.29 MTP3B Destination Signaling Point ................................................... 10-368
10.29.1 Overview of MS_MTP3B_DSP_TRAF ....................................... 10-368
10.29.4 Count of Transfer Prohibited Messages Received .................... 10-369
10.30 MTP Destination Signaling Point ........................................................ 10-370
10.30.1 Overview of MS_MTP_DSP_TRAF ........................................... 10-370
10.31 MTP Signaling Link ............................................................................ 10-371
10.31.1 Overview of MS_MTP_LINK_TRAF ........................................... 10-371
10.31.3 Count of Failures........................................................................ 10-372
10.31.4 Duration of Failure ..................................................................... 10-372
10.31.7 Count of Messages Discarded Due to Congestion .................... 10-373
10.31.8 Count of Transfer Prohibited Signals Received ......................... 10-374
10.31.9 Count of Local Automatic Switchovers ...................................... 10-374
10.31.10 Count of Local Management Inhibition Operations .................. 10-375
10.31.11 Duration of Local Management Inhibition Operations .............. 10-375
10.31.12 Count of Remote Management Inhibition Operations .............. 10-376
10.31.13 Duration of Remote Management Inhibition Operations .......... 10-376
10.31.14 Count of Remote Processor Failures ....................................... 10-377
10.31.15 Duration of Remote Processor Failure ..................................... 10-377
Signaling Information .............................................................................. 10-387
10.31.33 Percentage of Signaling Link Bandwidth Used for
Receiving Signaling Information ............................................................. 10-387
10.32 MTP Signaling Link Set ...................................................................... 10-388
10.32.1 Overview of MS_MTP_LINKSET_TRAF.................................... 10-388
10.32.2 Count of Unavailability ............................................................... 10-388
10.32.3 Duration of Unavailability ........................................................... 10-389
10.32.4 Count of SCCP Messages Sent ................................................. 10-389
10.32.5 Count of SCCP Messages Received ......................................... 10-390
10.32.6 Count of Bytes in SCCP Messages Sent ................................... 10-390
10.32.7 Count of Bytes in SCCP Messages Received ........................... 10-391
10.32.8 Count of TUP Messages Sent ................................................... 10-392
10.32.9 Count of TUP Messages Received ............................................ 10-392
10.33 SAAL Signaling Link ........................................................................... 10-399
10.33.1 Overview of MS_SAAL_LINK_TRAF ......................................... 10-399
10.33.2 Duration of SAAL Signaling Link in Service ............................... 10-399
10.33.3 Count of SAAL Signaling Link Failures Due to Other Causes ... 10-400
10.33.4 Count of SAAL Signaling Link Failures Due to Timeout of No
Response Timer ...................................................................................... 10-400
10.33.5 Count of SAAL Signaling Link Failures Due to Too High Bit
Error Rate ............................................................................................... 10-400
10.33.6 Count of SAAL Signaling Link Failures Due to Congestion
Timeout ................................................................................................... 10-401
10.33.7 Count of Location Failures of SAAL Signaling Link ................... 10-401
10.33.8 Count of MAA-ERROR Indications Due to SD Loss .................. 10-401
10.33.9 Count of Unexpected Packets Received ................................... 10-402
10.33.10 Count of SSCOP Sending Error Report to LM Due to Other
Causes .................................................................................................... 10-402
10.33.11 Count of Failed Retransmission ............................................... 10-403
10.34 SCCP Availability ............................................................................... 10-403
10.34.1 Overview of MS_SCCP_AVAILABILITY .................................... 10-403
10.34.2 Count of Local SCCP Failures Due to Fault .............................. 10-403
10.34.3 Count of Local SCCP Failures Due to Maintenance .................. 10-404
10.34.4 Count of Local SCCP Failures Due to Congestion .................... 10-404
10.34.5 Duration of Unavailability of Local SCCP Due to All Causes ..... 10-404
10.34.6 Count of Local SCCP Recovery Due to All Causes ................... 10-405
10.35 SCCP Usage ...................................................................................... 10-405
10.35.1 Overview of MS_SCCP_UTILIZATION ...................................... 10-405
10.35.2 Count of UDTS Messages Sent ................................................. 10-405
10.35.3 Count of UDTS Messages Received ......................................... 10-406
10.35.4 Count of Processed Messages (from Local or Remote
Subsystem) ............................................................................................. 10-407
10.35.5 Count of Messages Used by Local Subsystem ......................... 10-407
10.35.6 Count of Messages Needing GT Translation ............................. 10-408
10.35.7 Count of Connectionless Messages Sent .................................. 10-409
10.35.8 Count of Connectionless Messages Received .......................... 10-409
10.35.9 Count of Messages Sent to a Standby Subsystem .................... 10-410
10.36 SCCP Traffic ...................................................................................... 10-411
10.36.1 Overview of MS_SCCP_FLUX_TRAFFIC ................................. 10-411
10.36.2 Count of Messages Sent to a DSP ............................................ 10-411
10.36.3 Count of Messages Received from a DSP ................................ 10-411
10.36.4 Count of Bytes Sent to a DSP .................................................... 10-412
10.36.5 Count of Bytes Received from a DSP ........................................ 10-413
10.37 SCCP Performance ............................................................................ 10-413
10.37.1 Overview of MS_SCCP_PERFORMANCE ................................ 10-413
10.37.2 Count of Route Failures Due to Invalid Addressing
Information .............................................................................................. 10-414
10.37.3 Count of Route Failures Due to Translation Failure of Valid
Address ................................................................................................... 10-414
10.37.4 Count of Route Failures Due to Unavailable Signaling Point ..... 10-414
10.37.5 Count of Route Failures Due to Network Congestion ................ 10-415
10.37.6 Count of Route Failures Due to Subsystem Failure ................... 10-415
10.37.7 Count of Route Failures Due to Subsystem Congestion ........... 10-415
10.37.8 Count of Route Failures Due to Subsystem Not Installed .......... 10-416
10.37.9 Count of Route Failures Due to Unknown Reason .................... 10-416
10.37.10 Count of Route Failures Due to Syntax Error .......................... 10-416
10.38 TCAP CSL .......................................................................................... 10-417
10.38.1 Overview of MS_TCAP_CSL_PERFORMANCE ....................... 10-417
10.38.2 Count of Unrecognized Components ......................................... 10-417
10.38.3 Count of Components of Wrong Type ....................................... 10-418
10.38.4 Count of Wrong Component Structures ..................................... 10-418
10.38.5 Count of Unrecognized Link IDs ................................................ 10-418
10.38.6 Count of Unexpected Results .................................................... 10-419
10.38.7 Count of Unrecognized Operation IDs in Results ...................... 10-419
10.38.8 Count of Unexpected Errors ...................................................... 10-419
10.38.9 Count of Unrecognized Operation IDs in Errors ........................ 10-420
10.39 TCAP Transport Sublayer .................................................................. 10-420
10.39.1 Overview of MS_TCAP_TSL_PERFORMANCE ....................... 10-420
10.39.2 Count of P_ABORT Messages with Cause of Unrecognized
Message Type ........................................................................................ 10-420
10.39.3 Count of P_ABORT Messages with Cause of Wrong
Transaction Portion ................................................................................. 10-421
10.39.4 Count of P_ABORT Messages with Cause of Wrong Format
of Transaction Portion ............................................................................. 10-422
Transaction ID ......................................................................................... 10-423
10.39.6 Count of P_ABORT Messages with Cause of Resource
Limitation on Transaction Sublayer......................................................... 10-423
10.40 TCAP Availability ................................................................................ 10-424
10.40.1 Overview of MS_TCAP_AVAILABILITY .................................... 10-424
10.40.2 Count of Local TCAP Failures Due to Fault ............................... 10-424
10.40.3 Count of Local TCAP Failures Due to Maintenance .................. 10-425
10.40.4 Count of Local TCAP Failures Due to Congestion..................... 10-425
10.40.5 Duration of Unavailability of Local TCAP Due to All Causes ..... 10-425
10.41 Count of TCAP Messages .................................................................. 10-426
10.41.1 Overview of MS_TCAP_MSG_UTILIZATION ............................ 10-426
10.41.2 Count of Invoke Messages Sent ................................................ 10-426
10.41.3 Count of Invoke Messages Received ........................................ 10-427
10.41.4 Count of Last Result Messages Sent (Returned Result) ........... 10-427
10.41.5 Count of Last Result Messages Received (Returned Result) .... 10-428
10.41.6 Count of Not Last Result Messages Sent (Returned Result) ..... 10-429
10.41.7 Count of Not Last Result Messages Received (Returned
Result) ..................................................................................................... 10-429
10.41.8 Count of Returned Error Messages Sent ................................... 10-430
10.41.9 Count of Returned Error Messages Received ........................... 10-430
10.41.10 Count of Reject Messages Sent .............................................. 10-431
10.41.11 Count of Reject Messages Received ....................................... 10-432
10.42 TCAP Component Utilization .............................................................. 10-432
10.42.1 Overview of MS_TCAP_CMP_UTILIZATION ............................ 10-432
10.42.2 Count of Invoke Components Sent ............................................ 10-433
10.42.3 Count of Invoke Components Received .................................... 10-433
10.42.4 Count of Last Result Components Sent (Returned Result) ....... 10-434
10.42.5 Count of Last Result Components Received (Returned
Result) ..................................................................................................... 10-434
10.42.6 Count of Not Last Result Components Sent (Returned
Result) ..................................................................................................... 10-435
10.42.7 Count of Not Last Result Components Received (Returned
Result) ..................................................................................................... 10-436
10.42.8 Count of Return Error Components Sent ................................... 10-436
10.42.9 Count of Return Error Components Received ........................... 10-437
10.42.10 Count of Reject Components Sent .......................................... 10-437
10.42.11 Count of Reject Components Received ................................... 10-438
10.43 TUP Circuit Group .............................................................................. 10-439
10.43.1 Overview of MS_TUP_TKGRP_PERFORM_TRAF ................... 10-439
10.43.3 Count of Messages with Cause of Switching Equipment
Congestion .............................................................................................. 10-441
10.43.4 Count of Messages with Cause of Circuit Group Congestion .... 10-442
10.43.5 Count of Messages with Cause of National Network
Congestion .............................................................................................. 10-442
10.43.7 Count of Messages with Cause of Incomplete Address ............ 10-443
10.43.8 Count of Messages with Cause of Call Failure .......................... 10-444
10.43.9 Count of Messages with Cause of Callee Busy ......................... 10-445
10.43.10 Count of Messages with Cause of Unallocated Number ......... 10-446
10.43.11 Count of Messages with Cause of Line out of Service ............ 10-447
10.43.12 Count of Messages with Cause of Sending Special Signal
Tone ........................................................................................................ 10-448
10.43.13 Count of Messages with Cause of Rejected Access ............... 10-449
10.43.14 Count of Messages with Cause of Digital Path Not
Provided .................................................................................................. 10-450
10.43.15 Count of Messages with Cause of Trunk Prefix Wrongly
Dialed ...................................................................................................... 10-451
10.43.16 Count of Outgoing Call Attempts ............................................. 10-451
10.43.17 Count of SEC Messages Received.......................................... 10-452
10.43.18 Count of CGC Messages Received ......................................... 10-453
10.43.19 Count of NNC Messages Received ......................................... 10-454
10.43.20 Count of ADI Messages Received ........................................... 10-455
10.43.21 Count of CFL Messages Received .......................................... 10-456
10.43.22 Count of Messages Received with Cause of Callee Busy ....... 10-457
10.43.23 Count of UNN Messages Received ......................................... 10-458
10.43.24 Count of LOS Messages Received .......................................... 10-459
10.43.25 Count of SST Messages Received .......................................... 10-460
10.43.26 Count of ACB Messages Received.......................................... 10-461
10.43.27 Count of DPN Messages Received ......................................... 10-462
10.43.28 Count of Messages Received with Cause of Trunk Prefix
Wrongly Dialed ........................................................................................ 10-463
10.43.29 Count of Answers Without Charging ........................................ 10-463
10.43.30 Count of Maintenance-Oriented CGB Messages..................... 10-464
10.43.31 Count of Hardware-Oriented CGB Messages .......................... 10-465
10.43.32 Count of Circuit Group Reset Messages ................................. 10-466
10.43.33 Count of Circuit Reset Messages ............................................ 10-467
10.43.34 Count of Answers..................................................................... 10-468
10.43.37 Count of Messages Both Received and Sent .......................... 10-470
10.43.38 Length of Messages Received ................................................. 10-470
10.43.39 Length of Messages Sent ........................................................ 10-471
10.43.40 Length of Messages Both Received and Sent ......................... 10-471
10.43.41 Count of Calls .......................................................................... 10-471
10.43.42 Length of Messages per Call ................................................... 10-472
10.43.43 Average Message Length ........................................................ 10-472
10.44 TUP Node ........................................................................................... 10-473
10.44.1 Overview of MS_TUP_NODE_PERFORM_TRAF..................... 10-473
10.44.3 Count of Messages with Cause of Switch Congestion .............. 10-474
10.44.4 Count of Messages with Cause of Circuit Group Congestion .... 10-475
10.44.5 Count of Messages with Cause of National Network
Congestion .............................................................................................. 10-476
10.44.6 Count of Messages with Cause of Incomplete Address ............ 10-476
10.44.7 Count of Messages with Cause of Call Failure .......................... 10-477
10.44.8 Count of Messages with Cause of Callee Busy ......................... 10-478
10.44.9 Count of Messages with Cause of Unallocated Number ........... 10-479
10.44.10 Count of Messages with Cause of Line out of Service ............ 10-480
10.44.11 Count of Messages with Cause of Sending Special Tone ....... 10-481
10.44.12 Count of Messages with Cause of Rejected Access ............... 10-482
10.44.13 Count of Messages with Cause of Digital Path Not
Provided .................................................................................................. 10-483
10.44.14 Count of Messages with Cause of Trunk Prefix Wrongly
Dialed ...................................................................................................... 10-484
10.45 TUP Network ...................................................................................... 10-485
10.45.1 Overview of MS_TUP_NET_PERFORM_TRAF ........................ 10-485
10.45.2 Count of Outgoing Call Attempts ............................................... 10-485
10.45.3 Count of SEC Messages Received ............................................ 10-486
10.45.4 Count of CGC Messages Received ........................................... 10-487
10.45.5 Count of NNC Messages Received ........................................... 10-488
10.45.6 Count of ADI Messages Received ............................................. 10-489
10.45.7 Count of CFL Messages Received ............................................ 10-490
10.45.8 Count of Messages Received with Cause of Callee Busy ......... 10-491
10.45.9 Count of UNN Messages Received ........................................... 10-492
10.45.10 Count of LOS Messages Received .......................................... 10-493
10.45.11 Count of SST Messages Received .......................................... 10-494
10.45.12 Count of ACB Messages Received.......................................... 10-495
10.45.13 Count of DPN Messages Received ......................................... 10-496
10.45.14 Count of Messages Received with Cause of Trunk Prefix
Wrongly Dialed ........................................................................................ 10-497
10.46 TUP Message Application .................................................................. 10-498
10.46.1 Overview of MS_TUP_MSG_USING_TRAF ............................. 10-498
10.46.2 Count of Certain Messages Sent ............................................... 10-498
10.46.3 Count of Certain Messages Received ....................................... 10-498
10.47 Count of TUP Messages .................................................................... 10-499
10.47.1 Overview of MS_TUP_TOTAL_MSU_TRAF ............................. 10-499
10.48 TUP Abnormity ................................................................................... 10-500
10.48.1 Overview of MS_TUP_UNUSUAL_TRAF .................................. 10-500
10.48.2 Count of Responses to RSC Not Received by T19 ................... 10-501
10.48.3 Count of GRAs Not Received by T22 ........................................ 10-501
10.48.4 Count CLFs Not Received by T5 ............................................... 10-501
10.48.5 Count of RLGs Not Received by T7 ........................................... 10-502
10.48.6 Count of Abnormal Release Messages ..................................... 10-502
10.48.7 Count of Circuit Blocking Messages .......................................... 10-502
10.48.8 Count of Failures to Assign MHBA on Some Circuits ................ 10-503
10.48.9 Count of Failures to Assign MHUA on Some Circuits ................ 10-503
10.48.10 Count of Assignments of Too Many MHBAs on Some
Circuits .................................................................................................... 10-503
10.48.11 Count of Assignments of Too Many MHUAs on Some
Circuits .................................................................................................... 10-504
10.48.12 Count of Unexpected MHBAs Received .................................. 10-504
10.48.13 Count of Unexpected MHUAs Received .................................. 10-504
10.48.14 Count of Unexpected BLAs Received ...................................... 10-505
10.48.15 Count of Unexpected UBAs Received ..................................... 10-505
10.48.16 Count of BLAs Not Received by T13 ....................................... 10-505
10.48.17 Count of UBAs Not Received by T16....................................... 10-506
10.48.18 Count of Second Group Messages Not Received by T25 ....... 10-506
10.48.19 Count of MBAs Not Received by T27 ...................................... 10-506
10.48.20 Count of MUAs Not Received by T29 ...................................... 10-507
10.48.21 Count of HBAs Not Received by T33....................................... 10-507
10.48.22 Count of HUAs Not Received by T35 ...................................... 10-507
10.48.23 Count of Wrong Format Messages .......................................... 10-508
10.48.24 Count of Unexpected Messages Received .............................. 10-508
10.48.25 Count of Unknown Messages Received .................................. 10-508
10.49 Union Location Update Rejected Cause ............................................ 10-509
10.49.1 Overview of MS_TYPE_UNION_LOC_UP ................................ 10-509
10.49.2 Count of Messages Indicating Unknown Subscriber ................. 10-509
10.49.3 Count of Messages Indicating Roaming Not Allowed ................ 10-510
10.49.4 Count of Messages Indicating PLMN Roaming Not Allowed ..... 10-511
10.49.5 Count of Messages Indicating System Failure........................... 10-512
10.49.6 Count of Messages Indicating Data Lost ................................... 10-513
Chapter 11 IN Services .................................................................................... 11-1
11.2 CAP Operations ................................................................................... 11-1
11.2.1 Overview of MS_TYPE_CAP_OPER ........................................... 11-1
11.2.2 Count of Received Activity Test Messages .................................. 11-3
11.2.3 Count of Sent Activity Test Messages ......................................... 11-4
11.2.4 Count of Apply Charging Messages ............................................ 11-5
11.2.5 Count of Apply Charging Report Messages................................. 11-6
11.2.6 Count of Assist Request Instructions Messages .......................... 11-7
11.2.7 Count of Call Gap Messages ....................................................... 11-8
11.2.8 Count of Call Information Report Messages ................................ 11-9
11.2.9 Count of Call Information Request Messages ............................. 11-10
11.2.10 Count of Cancel Messages ........................................................ 11-11
11.2.11 Count of Connect Messages...................................................... 11-12
11.2.12 Count of Connect To Resource Messages ................................ 11-13
11.2.13 Count of Continue Messages ..................................................... 11-14
11.2.14 Count of Disconnect Forward Connection Messages ................ 11-15
11.2.15 Count of Establish Temporary Connection Messages ............... 11-16
11.2.16 Count of Event Report BCSM Messages ................................... 11-17
11.2.17 Count of Received Furnish Charging Information ...................... 11-18
11.2.18 Count of Initial DP Messages ..................................................... 11-19
11.2.19 Count of Play Announcement Messages ................................... 11-20
11.2.20 Count of Prompt And Collect User Information Messages ........ 11-21
11.2.21 Count of Prompt and Collect User Information Results ............. 11-22
11.2.22 Count of Release Call Messages ............................................... 11-23
11.2.23 Count of Request Report BCSM Event Messages .................... 11-24
11.2.24 Count of Reset Timer Messages ............................................... 11-25
11.2.25 Count of Send Charging Information Messages ........................ 11-26
11.2.26 Count of Specialized Resource Report Messages .................... 11-27
11.2.27 Count of Received NULL Messages .......................................... 11-28
11.2.28 Count of Sent NULL Messages ................................................. 11-29
11.2.29 Count of Received Error Messages ........................................... 11-30
11.2.30 Count of Sent Error Messages................................................... 11-31
11.2.31 Count of Sent TC_ABORT Messages ....................................... 11-32
11.2.32 Count of Received TC_ABORT Messages ................................ 11-33
11.2.33 Count of Continue With Argument Messages ............................ 11-34
11.2.34 Count of Connect SMS Messages ............................................. 11-35
11.2.35 Count of Continue SMS Messages ............................................ 11-36
11.2.36 Count of Event Report SMS Messages ..................................... 11-37
11.2.37 Count of Furnish Charging Information SMS Messages............ 11-38
11.2.38 Count of Initial DP SMS Messages ............................................ 11-39
11.2.39 Count of Release SMS Messages ............................................. 11-40
11.2.40 Count of Request Report SMS Event Messages ....................... 11-41
11.2.41 Count of Reset Timer SMS Messages....................................... 11-42
11.2.42 Count of ICA Messages ............................................................. 11-43
11.2.43 Count of Provide Avail DN Messages (Received) ..................... 11-44
11.2.44 Count of Provide Avail DN Messages (Sent) ............................. 11-45
11.2.45 Count of Port Connected Messages (Received)........................ 11-46
11.2.46 Count of Port Connected Messages (Sent) ............................... 11-47
11.2.47 Count of Bridge Ports Messages (Received) ............................. 11-48
11.2.48 Count of Bridge Ports Messages ............................................... 11-49
11.3 Initial Call Attempts ............................................................................... 11-50
11.3.1 Overview of MS_IN_ICA .............................................................. 11-50
11.3.2 Count of ICA Call Attempts .......................................................... 11-51
11.3.3 Count of ICA Call Alertings .......................................................... 11-51
11.3.4 Count of ICA Call Answers .......................................................... 11-52
11.3.5 ICA Call Seizure Traffic ................................................................ 11-53
11.3.6 ICA Call Alerting Traffic ................................................................ 11-53
11.3.7 ICA Call Answer Traffic ................................................................ 11-54
11.3.8 ICA Call Alerting Rate .................................................................. 11-54
11.3.9 ICA Call Answer Rate .................................................................. 11-54
11.3.10 Count of ICA DNs ...................................................................... 11-55
11.3.11 Count of ICA DN Failures .......................................................... 11-55
11.3.12 Count of Received Bridge Ports ................................................. 11-56
11.3.13 Count of SSP Bridge Ports Failures ........................................... 11-57
11.4 MAP IN Services .................................................................................. 11-57
11.4.1 Overview of MS_TYPE_MAP_IN_SERVICE ............................... 11-57
11.4.2 Count of Providing CAMEL Subscriber Information ..................... 11-58
11.4.3 Success Count of Providing CAMEL Subscriber Information ...... 11-58
11.4.4 Count of Sending Routing Information for CAMEL Subscriber .... 11-59
11.5 SSF Calls ............................................................................................. 11-60
11.5.1 Overview of MS_TYPE_SSF_CALL_TRAF ................................. 11-60
11.5.2 Count of SSF Call Outs ................................................................ 11-60
11.5.3 Count of SSF Call Ins .................................................................. 11-61
11.6 Fixed Subscriber Calling IN Subscriber................................................ 11-62
11.6.1 Overview of MS_TYPE_IN_INC_TRAF ....................................... 11-62
11.6.2 Attempt Count of Fixed Subscriber Calling IN Subscriber ........... 11-63
11.6.3 Connect Count of Fixed Subscriber Calling IN Subscriber .......... 11-63
11.6.4 Answer Count of Fixed Subscriber Calling IN Subscriber............ 11-64
11.6.5 Abandon Before Alerting Count of Fixed Subscriber Calling IN
Subscriber ............................................................................................... 11-65
11.6.6 Abandon After Alerting Count of Fixed Subscriber Calling IN
Subscriber ............................................................................................... 11-66
11.6.7 Callee Busy Count of Fixed Subscriber Calling IN Subscriber .... 11-67
11.6.8 No Answer Count of Fixed Subscriber Calling IN Subscriber ...... 11-68
11.6.9 Callee Determined Busy Count of Fixed Subscriber Calling IN
Subscriber ............................................................................................... 11-69
11.6.10 Seizure Traffic of Fixed Subscriber Calling IN Subscriber ......... 11-70
11.6.11 Connected Traffic of Fixed Subscriber Calling IN Subscriber .... 11-71
11.6.12 Answer Traffic of Fixed Subscriber Calling IN Subscriber ......... 11-72
11.7 Mobile Subscriber Calling IN Subscriber .............................................. 11-73
11.7.1 Overview of MS_TYPE_IN_MT_INT_TRAF ................................ 11-73
11.7.2 Attempt Count of Mobile Subscriber Calling IN Subscriber ......... 11-74
11.7.3 Connect Count of Mobile Subscriber Calling IN Subscriber ........ 11-75
11.7.4 Answer Count of Mobile Subscriber Calling IN Subscriber .......... 11-76
11.7.5 Abandon Before Alerting Count of Mobile Subscriber Calling
IN Subscriber .......................................................................................... 11-77
11.7.6 Abandon After Alerting Count of Mobile Subscriber Calling IN
Subscriber ............................................................................................... 11-78
11.7.7 Callee Busy Count of Mobile Subscriber Calling IN Subscriber... 11-79
11.7.8 No Answer Count of Mobile Subscriber Calling IN Subscriber .... 11-80
11.7.9 Callee Determined Busy Count of Mobile Subscriber Calling
IN Subscriber .......................................................................................... 11-81
11.7.10 Seizure Traffic of Mobile Subscriber Calling IN Subscriber ....... 11-82
11.7.11 Connected Traffic of Mobile Subscriber Calling IN
Subscriber ............................................................................................... 11-83
11.7.12 Answer Traffic of Mobile Subscriber Calling IN Subscriber ....... 11-83
11.8 IN Components .................................................................................... 11-83
11.8.1 Overview of MS_TYPE_IN_COMPOMENT ................................. 11-83
11.8.2 Sent INVOKE ............................................................................... 11-84
11.8.3 Received INVOKE ....................................................................... 11-84
11.8.4 Count of RESULTs that Cannot be Coded .................................. 11-85
11.8.5 Count of RESULTs that Cannot be Decoded .............................. 11-86
11.8.6 Count of Sent TC_REJECT Messages ........................................ 11-86
11.8.7 Count of Received TC_REJECT Messages ................................ 11-87
11.9 IN Dialogue ........................................................................................... 11-88
11.9.1 Overview of MS_IN_DIALOGUE_TRAF ...................................... 11-88
11.9.2 Count of Sessions Sent by SSF................................................... 11-89
11.9.3 Count of Sessions Received by SSF ........................................... 11-89
11.9.4 Count of Sessions U-Abort Sent by SSP ..................................... 11-90
11.9.5 Count of Sessions P-Abort and U-Abort Sent by SSP ................. 11-91
11.9.6 Call Duration Between Received TC-BEGIN and TC-END ......... 11-92
11.9.7 Total Count of Sessions ............................................................... 11-92
11.9.8 Average Duration of Sessions ..................................................... 11-93
11.10 IN Calls of All Subscribers Calling Operator....................................... 11-93
11.10.1 Overview of MS_TYPE_IN_OPERATOR_TRAF ....................... 11-93
11.10.2 Attempt Count of IN Subscriber Calling Operator ...................... 11-94
11.10.3 Connect Count of IN Subscriber Calling Operator ..................... 11-95
11.10.4 Answer Count of IN Subscriber Calling Operator ...................... 11-97
11.10.5 Abandon Before Alerting Count of IN Subscriber Calling
Operator .................................................................................................. 11-99
11.10.6 Abandon After Alerting Count of IN Subscriber Calling
Operator .................................................................................................. 11-101
11.10.7 Callee Busy Count of IN Subscriber Calling Operator ............... 11-103
11.10.8 No Answer Count of IN Subscriber Calling Operator ................. 11-105
11.10.9 Callee Determined Busy Count of IN Subscriber Calling
Operator .................................................................................................. 11-106
11.10.10 Seizure Traffic of IN Subscriber Calling Operator .................... 11-107
11.10.11 Connect Traffic of IN Subscriber Calling Operator ................... 11-108
11.10.12 Answer Traffic of IN Subscriber Calling Operator .................... 11-108
11.11 IN Failures .......................................................................................... 11-109
11.11.1 Overview of MS_IN_FAILURE_TRAF ....................................... 11-109
11.11.2 Count of Overload Rejected Calls .............................................. 11-109
11.11.3 Count of Call Failures Before Initialization ................................. 11-109
11.11.4 Count of Call Failures After Initialization .................................... 11-110
11.11.5 Count of Sessions Reject Received by SSF .............................. 11-110
11.12 IN Events ............................................................................................ 11-111
11.12.2 Originating IN Call Initiates (DP2) .............................................. 11-112
11.12.3 Originating Route Selection Fails (EDP4) .................................. 11-113
11.12.4 Originating Callee Busy (DP5) ................................................... 11-113
11.12.5 Originating Callee Does Not Answer (DP6) ............................... 11-114
11.12.6 Originating Callee Answers (DP7) ............................................. 11-115
11.12.7 Originating Release Event (DP9) ............................................... 11-116
11.12.8 Originating Caller Abandons (DP10).......................................... 11-117
11.12.9 Terminating IN Call Initiates (DP12) .......................................... 11-118
11.12.10 Terminating Callee Busy (EDP13) ........................................... 11-119
11.12.11 Terminating Callee Does Not Answer (EDP14) ....................... 11-120
11.12.12 Terminating Callee Answers (DP15) ........................................ 11-121
11.12.13 Terminating Releases (DP17) .................................................. 11-122
11.12.14 Terminating Caller Abandons (DP18) ...................................... 11-123
11.12.15 Terminating Analyzes Information (DP3) ................................. 11-124
11.12.16 Originating Route Selection Fails (TDP4) ................................ 11-125
11.12.17 Terminating Callee Busy (TDP13) ........................................... 11-126
11.12.18 Terminating Callee Does Not Answer (TDP14) ....................... 11-127
11.12.19 Originating IN SMS Initiates ..................................................... 11-128
11.12.20 Originating SMS Fails .............................................................. 11-129
11.12.21 Originating SMS Submits ......................................................... 11-130
11.13 IN Subscriber Calling Fixed Subscriber .............................................. 11-131
11.13.1 Overview of MS_TYPE_IN_ORGOUT_TRAF ........................... 11-131
11.13.2 Attempt Count of IN Subscriber Calling Fixed Subscriber ......... 11-132
11.13.3 Connect Count of IN Subscriber Calling Fixed Subscriber ........ 11-132
11.13.4 Answer Count of IN Subscriber Calling Fixed Subscriber .......... 11-133
11.13.6 Abandon After Alerting Count of IN Subscriber Calling Fixed
Subscriber ............................................................................................... 11-135
11.13.7 Callee Busy Count of IN Subscriber Calling Fixed
Subscriber ............................................................................................... 11-136
11.13.8 No Answer Count of IN Subscriber Calling Fixed Subscriber .... 11-137
11.13.9 Seizure Traffic of IN Subscriber Calling Fixed Subscriber ......... 11-138
11.13.10 Connected Traffic of IN Subscriber Calling Fixed
Subscriber ............................................................................................... 11-139
11.13.11 Answer Traffic of IN Subscriber Calling Fixed Subscriber ....... 11-140
11.14 IN Subscriber Calling Mobile Subscriber ............................................ 11-141
11.14.1 Overview of MS_TYPE_IN_MO_INT_TRAF.............................. 11-141
11.14.2 Attempt Count of IN Subscriber Calling Mobile Subscriber ....... 11-142
11.14.3 Connect Count of IN Subscriber Calling Mobile Subscriber ...... 11-143
11.14.4 Answer Count of IN Subscriber Calling Mobile Subscriber ........ 11-144
11.14.6 Abandon After Alerting Count of IN Subscriber Calling
11.14.7 Callee Busy Count of IN Subscriber Calling Mobile
Subscriber ............................................................................................... 11-147
11.14.8 No Answer Count of IN Subscriber Calling Mobile
Subscriber ............................................................................................... 11-148
11.14.9 Callee Determined Busy Count of IN Subscriber Calling
11.14.10 Seizure Traffic of IN Subscriber Calling Mobile Subscriber ..... 11-150
11.14.11 Connected Traffic of IN Subscriber Calling Mobile
Subscriber ............................................................................................... 11-151
11.14.12 Answer Traffic of IN Subscriber Calling Mobile Subscriber ..... 11-152
11.15 IN Subscriber Calling IN Subscriber ................................................... 11-153
11.15.2 Count of Caller Attempts ............................................................ 11-154
11.15.3 Count of Caller Connections ...................................................... 11-156
11.15.4 Count of Caller Answers ............................................................ 11-158
11.15.5 Count of Caller Abandons Before Ringing ................................. 11-160
11.15.6 Count of Caller Abandons After Ringing .................................... 11-162
11.15.7 Count of No Answers ................................................................. 11-164
11.15.10 Caller Seizure Traffic ............................................................... 11-170
11.15.11 Caller Connected Traffic .......................................................... 11-171
11.15.12 Caller Answer Traffic ................................................................ 11-171
11.15.13 Count of Callee Attempts ......................................................... 11-171
11.15.14 Count of Callee Connections ................................................... 11-172
11.15.15 Count of Callee Answers ......................................................... 11-173
11.15.16 Callee Seizure Traffic............................................................... 11-173
11.15.17 Callee Connected Traffic ......................................................... 11-174
11.15.18 Callee Answer Traffic ............................................................... 11-174
Chapter 12 Lawful Interception ...................................................................... 12-1
12.2 Monitored Outgoing Traffic ................................................................... 12-1
12.2.1 Overview of MS_OFFICE_OUT_TRAF_LICI ............................... 12-1
12.2.6 Count of No Answer ..................................................................... 12-6
12.2.7 Count of Abandon Before Alerting ............................................... 12-8
12.2.8 Count of Lost Calls Due to Overload Control ............................... 12-8
12.2.9 Count of Lost Calls Due to NMS Control ..................................... 12-11
12.2.10 Count of Last-Choice Route Overflow ....................................... 12-13
12.2.14 Seizure Traffic ............................................................................ 12-15
12.2.16 Count of Circuits in Maintenance State ...................................... 12-17
12.2.18 Answer Rate .............................................................................. 12-18
Application Failure .................................................................................. 12-19
Congestion .............................................................................................. 12-20
12.2.22 Traffic of Completed Calls .......................................................... 12-22
12.3 Monitored Office Direction Outgoing Traffic ......................................... 12-23
12.3.1 Overview of MS_OFFICEDIR_OUT_TRAF_LICI ......................... 12-23
12.3.7 Count of Calls Through Indirect Sub-Routes ............................... 12-28
12.3.8 Count of No Command for Nested Calling ................................... 12-29
12.3.10 Count of Trunk Retry.................................................................. 12-30
12.3.14 Count of No Reply ...................................................................... 12-35
12.3.16 Count of Available Bidirectional Circuits .................................... 12-37
12.3.17 Count of Blocked Bidirectional Circuits ...................................... 12-38
12.3.18 Availability of Outgoing Trunks .................................................. 12-38
12.3.19 Seizure Rate .............................................................................. 12-39
12.3.21 Answer Rate .............................................................................. 12-39
12.3.22 Block Rate .................................................................................. 12-40
12.3.25 Seizure Traffic ............................................................................ 12-41
12.3.29 Count of First Sub-Route Overflow ............................................ 12-42
12.3.30 Count of Second Sub-Route Overflow ....................................... 12-43
12.3.31 Count of Third Sub-Route Overflow ........................................... 12-43
12.3.32 Count of Fourth Sub-Route Overflow ......................................... 12-43
12.3.33 Count of Fifth Sub-Route Overflow ............................................ 12-44
12.3.34 Count of Sixth Sub-Route Overflow ........................................... 12-44
12.3.35 Count of Seventh Sub-Route Overflow ...................................... 12-45
12.3.36 Count of Eighth Sub-Route Overflow ......................................... 12-45
12.3.37 Count of Ninth Sub-Route Overflow ........................................... 12-45
12.3.38 Count of Tenth Sub-Route Overflow .......................................... 12-46
12.3.39 Count of Eleventh Sub-Route Overflow ..................................... 12-46
12.3.40 Count of Twelfth Sub-Route Overflow ....................................... 12-46
12.4 Monitored Trunk Group Outgoing Traffic .............................................. 12-47
12.4.1 Overview of MS_TKGRP_OUT_TRAF_LICI ................................ 12-47
12.4.7 Count of Bearer Capability and Mode Mismatch ......................... 12-53
12.4.9 Count of Trunk Retry .................................................................... 12-54
12.4.11 Congestion Duration .................................................................. 12-57
12.4.12 Count of Effects Caused by NMS Control .................................. 12-57
12.4.17 Count of No Reply ...................................................................... 12-62
12.4.22 Count of Available Bidirectional Circuits .................................... 12-66
12.4.23 Count of Blocked Bidirectional Circuits ...................................... 12-66
12.4.24 Availability of Outgoing Trunks .................................................. 12-66
12.4.25 Seizure Rate .............................................................................. 12-67
12.4.27 Answer Rate .............................................................................. 12-67
12.4.28 Block Rate .................................................................................. 12-68
12.4.31 Seizure Traffic ............................................................................ 12-69
Index .................................................................................................................
HUAWEI
HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Technical Manual – Performance Measurement
Entities
V100R003
Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Mobile SoftSwitch Center
Technical Manual
Volume Performance Measurement Entities
Manual Version T2-030249-20051031-C-3.03
Product Version V100R003
BOM 31026949
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com

Copyright © 2005 Huawei Technologies Co., Ltd.
All Rights Reserved
No part of this manual may be reproduced or transmitted in any form or by any

means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA,
iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE,
OpenEye, Lansway, SmartAX, infoX, and TopEng are trademarks of Huawei
Technologies Co., Ltd.
All other trademarks and trade names mentioned in this manual are the property of
their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents,
but all statements, information, and recommendations in this manual do not
constitute the warranty of any kind, express or implied.

About This Manual
Release Notes
This manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R003.
Organization
The manual provides an overall introduction to HUAWEI MSOFTX3000 Mobile

SoftSwitch Center (hereinafter referred to as MSOFTX3000).
There are twelve chapters in the manual.

z Chapter 1 Overview profiles the definitions of the performance measurement,
measurement set, measurement unit, and measurement entity as well as the
relationship between measurement object and measurement unit,
z Chapter 2 MSC Basic Functions introduces the measurement set used to
measure the MSC mobility management, such as authentication and location
management.
z Chapter 3 MSC Basic Services presents the measurement set used to
measure the traffic of MSC basic services like handover and short message
service (SMS).
z Chapter 4 MSC Special Services introduces the measurement set used to
measure the traffic of some special services, such as data services.
z Chapter 5 Bearer Traffic presents the measurement units that are divided by
the objects carrying different traffic.
z Chapter 6 Call Processing details the measurement set used to measure the
traffic in different phases of call processing.
z Chapter 7 Call Record presents the measurement set used to test the
measurement point, average internal and external connection duration during
the connections.
z Chapter 8 Total Traffic of the Office describes the measurement set that
specifies the total traffic of the office, including calling status, calling service
quality, and network quality in all directions can be obtained.
z Chapter 9 Global Components presents the measurement set used to check
the status of the MSC such as CPU seizure rate and count of VLR subscribers.
z Chapter 10 Signaling and Interfaces details the measurement set used to
effectively manage, evaluate and utilize signaling network resources.
z Chapter 11 IN Services presents the measurement set used to measure the
traffic of IN calls.

z Chapter 12 Lawful Interception details the measurement set used to measure
the traffic of the lawful interception office direction.
Intended Audience
The manual is intended for the following readers:

z Mobile network engineering specialists
z Operation and Maintenance engineers
z Mobile network system engineers
Conventions
The manual uses the following conventions:
I. General conventions
Convention Description
Arial Normal paragraphs are in Arial.
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.
II. GUI conventions
Convention Description
Button names are inside angle brackets. For example, click

<>
the <OK> button.
Window names, menu items, data table and field names are
[] inside square brackets. For example, pop up the [New User]
window.
Multi-level menus are separated by forward slashes. For
/
example, [File/Create/Folder].
III. Keyboard operation
Format Description
Press the key with the key name inside angle brackets. For
<Key>
example, <Enter>, <Tab>, <Backspace>, or <A>.

Format Description
Press the keys concurrently. For example, <Ctrl+Alt+A>
<Key1+Key2>
means the three keys should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two
<Key1, Key2>
keys should be pressed in turn.
IV. Mouse operation
Action Description
Press the left button or right button quickly (left button by

Click
default).
Double Click Press the left button twice continuously and quickly.
Drag Press and hold the left button and drag it to a certain position.
V. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution Means reader be extremely careful during the operation.
Note: Means a complementary description.

Technical Manual – Performance Measurement Entity
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents
Table of Contents
Chapter 1 Overview ....................................................................................................................... 1-1

1.1 Measurement Set............................................................................................................... 1-1
1.2 Measurement Unit.............................................................................................................. 1-1
1.3 Relationship Between Measurement Object and Measurement Unit................................ 1-2
1.4 Measurement Entity ........................................................................................................... 1-2
Chapter 2 MSC Basic Functions .................................................................................................. 2-1

2.1 Overview of Measurement Set .......................................................................................... 2-1
2.2 MSC Basic Table ............................................................................................................... 2-1
2.2.1 Overview of MS_BASIC_TABLE_TRAF ................................................................. 2-1
2.2.2 Count of Level Updates........................................................................................... 2-2
2.2.3 Count of Ciphering Mode Setting Requests............................................................ 2-3
2.2.4 Count of Ciphering Mode Setting Successes ......................................................... 2-4
2.2.5 Count of Routing Information Requests.................................................................. 2-5
2.2.6 Count of Successes in Receiving Roaming Numbers ............................................ 2-6
2.2.7 Count of Successes in Receiving Forwarded-to Numbers ..................................... 2-7
2.2.8 Count of Sent MO Short Messages ........................................................................ 2-8
2.2.9 Count of Successful MO Short Messages (Sent) ................................................... 2-8
2.2.10 Count of Received MT Short Messages ............................................................. 2-10
2.2.11 Count of Successful MT Short Messages (Received) ........................................ 2-11
2.2.12 Count of Use of TMSI at MM Layer .................................................................... 2-11
2.2.13 Count of Use of IMSI at MM Layer...................................................................... 2-21
2.2.14 Count of TMSI Reallocation Requests................................................................ 2-30
2.2.15 Count of TMSI Reallocation Successes.............................................................. 2-32
2.2.16 Count of IMSI Detachments ................................................................................ 2-34
2.2.17 Count of IMSI Attachments ................................................................................. 2-35
2.2.18 Count of Pagings................................................................................................. 2-37
2.2.19 Count of Paging Responses ............................................................................... 2-37
2.2.20 Count of SOR Basic Call Requests..................................................................... 2-38
2.2.21 Count of Successes of Basic SOR Call .............................................................. 2-39
2.2.22 Count of SOR Early Forward Call Requests....................................................... 2-40
2.2.23 Count of Successes of SOR Early Forward Call................................................. 2-41
2.2.24 Count of SOR Late Forward Call Requests ........................................................ 2-42
2.2.25 Count of Successes of SOR Late Forward Call.................................................. 2-43
2.2.26 Count of SOR Requests for Routing................................................................... 2-44
2.2.27 Count of SOR Requests for MSRN..................................................................... 2-45
2.2.28 Count of Receiving MSRN During SOR Routing ................................................ 2-46
2.2.29 Count of Successes of SOR for MSRN .............................................................. 2-47
i
2.3 Authentication .................................................................................................................. 2-48

2.3.1 Overview of MS_TYPE_AUTH.............................................................................. 2-48
2.3.2 Count of Authentication Set Requests to HLR...................................................... 2-49
2.3.3 Count of Authentication Set Receipts from HLR................................................... 2-49
2.3.4 Count of Empty Authentication Set Receipts from HLR........................................ 2-50
2.3.5 Count of Authentication Set Requests to PVLR.................................................... 2-51
2.3.6 Count of Authentication Set Receipts from PVLR................................................. 2-52
2.3.7 Count of Authentication Requests......................................................................... 2-52
2.3.8 Count of Successful Authentications .................................................................... 2-53
2.3.9 Count of Authentication Failures Due to Illegal SRES .......................................... 2-54
2.3.10 Count of Authentication Requests with TMSI ..................................................... 2-55
2.3.11 Count of Authentication Failures Due to Illegal SRES (with TMSI) .................... 2-55
2.3.12 Count of Successful Authentications After IMSI Being Identified ....................... 2-56
2.3.13 Count of Failures in Responding to Authentication Requests ............................ 2-57
2.3.14 Count of Failure Responses to Authenication Requests .................................... 2-58
2.4 Location Update............................................................................................................... 2-59
2.4.1 Overview of MS_TYPE_LOC_UP ......................................................................... 2-59
2.4.2 Count of Location Update Requests ..................................................................... 2-60
2.4.3 Count of Location Update Rejections ................................................................... 2-60
2.4.4 Count of IMSI Detachments .................................................................................. 2-61
2.4.5 Count of IMSI Attachments ................................................................................... 2-62
2.4.6 Count of Location Update Requests in VLR ......................................................... 2-62
2.4.7 Count of Location Update Successes in VLR ....................................................... 2-63
2.4.8 Count of Location Update Requests Due to Subsriber Roaming ......................... 2-63
2.4.9 Count of Location Update Successes Due to Subsriber Roaming ....................... 2-64
2.4.10 Count of Location Update Successes Due to National Roaming ....................... 2-65
2.4.11 Count of Location Update Successes Due to International Roaming................ 2-65
2.4.12 Count of Location Update Failures Due to Unknown User in HLR ..................... 2-66
2.4.13 Count of Location Update Failures Due to Illegal MS......................................... 2-67
2.4.14 Count of Location Update Failures Due to IMEI Check Failure .......................... 2-67
2.4.15 Count of Location Update Failures Due to PLMN Denying Access.................... 2-68
2.4.16 Count of Location Update Failures Due to Prohibition of Location Area ............ 2-69
2.4.17 Count of Location Update Failures Due to Roaming Prohibition ........................ 2-69
2.4.18 Count of Location Update Failures Due to Protocol Failure ............................... 2-70
2.4.19 Count of Location Update Failures Due to Network Failure ............................... 2-71
2.4.20 Count of Location Update Failures Due to Prohibition of Location Area in PLMN2-71
2.4.21 Count of Location Update Failures Due to Prohibition of Location Area Cell ..... 2-72
2.4.22 Count of Location Update Failures Due to Other Causes .................................. 2-73
2.4.23 Count of Attempts to Insert User Data ................................................................ 2-74
2.4.24 Count of Sucesses in Inserting User Data .......................................................... 2-74
2.4.25 Count of Location Update Failures Due to ARD ................................................. 2-75
ii
Chapter 3 MSC Basic Services .................................................................................................... 3-1

3.2 Handover Between Two PLMNs........................................................................................ 3-1
3.2.1 Overview of MS_HO_2PLMN ................................................................................. 3-1
3.2.2 Count of Ultrashort Inter-MSC Handovers Between Two PLMNs .......................... 3-2
3.2.3 Duration of Ultrashort Inter-MSC Handovers Between Two PLMNs ...................... 3-2
3.2.4 Count of Ultrashort Intra-MSCb Handovers Between Two PLMNs ........................ 3-3
3.2.5 Duration of Ultrashort Intra-MSCb Handovers Between Two PLMNs .................... 3-4
3.2.6 Count of Ultrashort Inter-BSC Handovers Between Two PLMNs........................... 3-5
3.2.7 Duration of Ultrashort Inter-BSC Handovers Between Two PLMNs....................... 3-6
3.2.8 Count of Ultrashort Intra-BSC Handovers Between Two PLMNs........................... 3-7
3.2.9 Duration of Ultrashort Intra-BSC Handovers Between Two PLMNs....................... 3-8
3.3 GSM Assignment ............................................................................................................... 3-9
3.3.1 Overview of MS_S_ASSIGN_TRAF ....................................................................... 3-9
3.3.2 Count of Requests for Traffic Channel Assignments ............................................ 3-10
3.3.3 Count of Successful Traffic Channel Assignments ............................................... 3-11
3.3.4 Count of Traffic Channel Assignment Failures Due to Radio Interface Message
Failure ............................................................................................................................ 3-11
3.3.5 Count of Traffic Channel Assignment Failures Due to O&M Intervention............. 3-12
3.3.6 Count of Traffic Channel Assignment Failures Due to Equipment Failure ........... 3-13
3.3.7 Count of Traffic Channel Assignment Failures Due to Radio Resource Unavailable3-14
3.3.8 Count of Traffic Channel Assignment Failures Due to Requested Terrestrial
Resource Unavailable .................................................................................................... 3-14
3.3.9 Count of Traffic Channel Assignment Failures Due to Requested Transcoding/Rate
Adaptation Unavailable .................................................................................................. 3-15
3.3.10 Count of Traffic Channel Assignment Failures Due to Terrestrial Resource Already
Allocated......................................................................................................................... 3-16
3.3.11 Count of Traffic Channel Assignment Failures Due to Invalid Message Content3-17
3.3.12 Count of Traffic Channel Assignment Failures Due to Radio Interface Failure -
Reversion to Old Channel .............................................................................................. 3-17
3.3.13 Count of Traffic Channel Assignment Failures Due to Directed Retry................ 3-18
3.3.14 Count of Traffic Channel Assignment Failures Due to Circuit Pool Mismatch.... 3-19
3.3.15 Count of Traffic Channel Assignment Failures Due to Change of Circuit Group 3-19
3.3.16 Count of Traffic Channel Assignment Failures Due to Other Causes ................ 3-20
3.4 MSC Handover ................................................................................................................ 3-21
3.4.1 Overview of MS_S_MSC_HO ............................................................................... 3-21
3.4.2 Count of Handovers Controlled by MSC............................................................... 3-21
3.4.3 Count of Link Disconnections Due to Handover Failure ....................................... 3-22
3.4.4 Count of Calls Returned to Original Channels Due to Handover Failure.............. 3-23
3.4.5 Count of Requests for Intra-MSC Handovers ....................................................... 3-24
3.4.6 Count of Successful Intra-MSC Handovers .......................................................... 3-24
3.4.7 Count of Requests for Basic Outgoing Handovers ............................................... 3-25
iii
3.4.8 Count of Successful Basic Outgoing Handovers .................................................. 3-26

3.4.9 Count of Requests for Basic Incoming Handovers ............................................... 3-26
3.4.10 Count of Successful Basic Incoming Handovers ................................................ 3-27
3.4.11 Count of Requests for Subsequent Handovers Back to Local MSC (MSCa) ..... 3-28
3.4.12 Count of Successful Subsequent Handovers Back to Local MSC (MSCa) ........ 3-29
3.4.13 Count of Requests for Subsequent Handovers to MSCc (Local MSC Is MSCa) 3-30
3.4.14 Count of Successful Subsequent Handovers to MSCc (Local MSC Is MSCa) .. 3-31
3.4.15 Count of Requests for Subsequent Handovers (Local MSC Is MSCb) .............. 3-32
3.4.16 Count of Successful Subsequent Handovers (Local MSC Is MSCb) ................. 3-33
3.5 TMSI Reallocation............................................................................................................ 3-34
3.5.1 Overview of MS_S_TMSI_REALLOC_TRAF ....................................................... 3-34
3.5.2 Count of TMSI Reallocation Requests During Location Update........................... 3-34
3.5.3 Count of Successful TMSI Reallocations During Location Update....................... 3-36
3.5.4 Count of TMSI Reallocation Requests During Service Access ............................ 3-37
3.5.5 Count of Successful TMSI Reallocations During Service Access ........................ 3-38
3.6 WCDMA Assignment ....................................................................................................... 3-40
3.6.1 Overview of MS_S_ASSIGN_3G_TRAF .............................................................. 3-40
3.6.2 Count of Requests for Traffic Channel Assignments ............................................ 3-41
3.6.3 Count of Successful Traffic Channel Assignments ............................................... 3-41
3.6.4 Count of Assignment Failures Due to RAB Preempted ........................................ 3-42
3.6.5 Count of Assignment Failures Due to Timeout of Establishing RAB or Modifying
Request on RNC Side .................................................................................................... 3-43
3.6.6 Count of Assignment Failures Due to Handover................................................... 3-44
3.6.7 Count of Assignment Failures Due to Requested Traffic Class Unavailable........ 3-44
3.6.8 Count of Assignment Failures Due to Invalid RAB Parameter Value ................... 3-45
3.6.9 Count of Assignment Failures Due to Requested Maximum Bit Rate Unavailable3-46
3.6.10 Count of Assignment Failures Due to Requested Guaranteed Bit Rate Unavailable3-46
3.6.11 Count of Assignment Failures Due to Requested Transfer Delay Unavailable .. 3-47
3.6.12 Count of Assignment Failures Due to Invalid RAB Parameter Combination ...... 3-48
3.6.13 Count of Assignment Failures Due to Violation of SDU Parameter Conditions.. 3-48
3.6.14 Count of Assignment Failures Due to Violation of Traffic Handling Priority
Conditions ...................................................................................................................... 3-49
3.6.15 Count of Assignment Failures Due to Violation of Guaranteed Bit Rate Conditions3-50
3.6.16 Count of Assignment Failures Due to User Plane Version Not Supported......... 3-50
3.6.17 Count of Assignment Failures Due to Iu UP Failure ........................................... 3-51
3.6.18 Count of Assignment Failures Due to Invalid RAB ID......................................... 3-52
3.6.19 Count of Assignment Failures Due to No Remaining RAB................................. 3-52
3.6.20 Count of Assignment Failures Due to Request Superseded .............................. 3-53
3.6.21 Count of Assignment Failures Due to Signaling Transport Resource Failure .... 3-54
3.6.22 Count of Assignment Failures Due to O&M Intervention .................................... 3-54
3.6.23 Count of Assignment Failures Due to No Resource Available ........................... 3-55
3.6.24 Count of Assignment Failures Due to Unspecified Failure ................................. 3-56
iv
3.6.25 Count of Assignment Failures Due to Directed Retry ......................................... 3-56

3.6.26 Count of Assignment Failures Due to Iu Transport Connection Setup Failure... 3-57
3.6.27 Count of Assignment Failures Due to Other Causes .......................................... 3-58
3.7 Short Message Service.................................................................................................... 3-58
3.7.1 Overview of MS_TYPE_SMS................................................................................ 3-58
3.7.2 Count of Attempt MO Short Messages ................................................................. 3-59
3.7.3 Count of Successful MO Short Messages ............................................................ 3-60
3.7.4 Count of Failures to Send MO Short Messages Due to Authentication Failure.... 3-62
3.7.5 Count of Failures to Send MO Short Messages Due to Setting Ciphering Mode
Failure ............................................................................................................................ 3-62
3.7.6 Count of Failures to Send MO Short Messages Due to Service Restriction......... 3-63
3.7.7 Count of Failures to Send MO Short Messages Due to Unknown Subscriber ..... 3-64
3.7.8 Count of Failures to Send MO Short Messages Due to Equipment Not Supported3-65
3.7.9 Count of Failures to Send MO Short Messages Due to System Failure............... 3-68
3.7.10 Count of Failures to Send MO Short Messages Due to SM Delivery Failure ..... 3-70
3.7.11 Count of Failures to Send MO Short Messages Due to Protocol Data Error...... 3-71
3.7.12 Count of Attempt MT Short Messages................................................................ 3-73
3.7.13 Count of Successful MT Short Messages........................................................... 3-73
3.7.14 Count of Failures to Send MT Short Messages Due to Unidentified Subscriber 3-74
3.7.15 Count of Failures to Send MT Short Messages Due to Absent Subscriber........ 3-75
3.7.16 Count of Failures to Send MT Short Messages Due to Equipment Not Supported3-76
3.7.17 Count of Failures to Send MT Short Messages Due to Illegal Subscriber ......... 3-76
3.7.18 Count of Failures to Send MT Short Messages Due to Illegal Equipment ......... 3-77
3.7.19 Count of Failures to Send MT Short Messages Due to System Failure ............. 3-78
3.7.20 Count of Failures to Send MT Short Messages Due to SM Delivery Failure...... 3-79
3.8 GSM Cell Handover......................................................................................................... 3-79
3.8.1 Overview of MS_S_CELL_HO_TRAF .................................................................. 3-79
3.8.2 Count of Requests for Intra-MSC Incoming Handovers to Cell ............................ 3-81
3.8.3 Count of Successful Intra-MSC Incoming Handovers to Cell ............................... 3-82
3.8.4 Count of Requests for Intra-MSC Outgoing Handovers from Cell ........................ 3-82
3.8.5 Count of Successful Intra-MSC Outgoing Handovers from Cell ........................... 3-83
3.8.6 Count of Requests for Inter-MSC Incoming Handovers to Cell ............................ 3-84
3.8.7 Count of Successful Inter-MSC Incoming Handovers to Cell ............................... 3-85
3.8.8 Count of Requests for Inter-MSC Outgoing Handovers from Cell ........................ 3-87
3.8.9 Count of Successful Inter-MSC Outgoing Handovers from Cell ........................... 3-88
3.8.10 Count of Outgoing Handovers from Cell Due to Uplink Quality .......................... 3-90
3.8.11 Count of Outgoing Handovers from Cell Due to Uplink Strength........................ 3-90
3.8.12 Count of Outgoing Handovers from Cell Due to Downlink Quality ..................... 3-91
3.8.13 Count of Outgoing Handovers from Cell Due to Downlink Strength ................... 3-92
3.8.14 Count of Outgoing Handovers from Cell Due to Distance .................................. 3-93
3.8.15 Count of Outgoing Handovers from Cell Due to Existence of Better Cell........... 3-94
3.8.16 Count of Outgoing Handovers from Cell Due to Response to MSC Request .... 3-95
v
3.8.17 Count of Outgoing Handovers from Cell Due to O&M Intervention .................... 3-96
3.8.18 Count of Outgoing Handovers from Cell Due to Directed Retry ......................... 3-97
3.8.19 Count of Outgoing Handovers from Cell Due to Change of Circuit Group ......... 3-98
3.8.20 Count of Outgoing Handovers from Cell Due to Other Causes .......................... 3-99
3.8.21 Count of Handover Failures Due to Radio Interface Message Failure ............. 3-100
3.8.22 Count of Handover Failures Due to O&M Intervention ..................................... 3-101
3.8.23 Count of Handover Failures Due to Equipment Failure .................................... 3-102
3.8.24 Count of Handover Failures Due to No Radio Resource Available .................. 3-103
3.8.25 Count of Handover Failures Due to Requested Terrestrial Resource Unavailable3-104
3.8.26 Count of Handover Failures Due to Transcoding/Rate Adaptation Unavailable3-105
3.8.27 Count of Handover Failures Due to Requested Terrestrial Resource Already
Allocated....................................................................................................................... 3-106
3.8.28 Count of Handover Failures Due to Invalid Message Content.......................... 3-107
3.8.29 Count of Handover Failures Due to Radio Interface Failure - Reversion to Old
Channel ........................................................................................................................ 3-108
3.8.30 Count of Handover Failures Due to Ciphering Algorithm Not Supported ......... 3-109
3.8.31 Count of Handover Failures Due to Circuit Pool Mismatch .............................. 3-110
3.8.32 Count of Handover Failures Due to Change of Circuit Group Number............. 3-111
3.8.33 Count of Handover Failures Due to Requested Speech Version Unavailable . 3-112
3.8.34 Count of Handover Failures Due to Protocol Error ........................................... 3-113
3.8.35 Count of Handover Failures Due to Preemption ............................................... 3-114
3.8.36 Count of Handover Failures Due to Other Causes ........................................... 3-115
3.9 WCDMA RNC Handover ............................................................................................... 3-116
3.9.1 Overview of MS_S_RNC_RELOCATION ........................................................... 3-116
3.9.2 Count of Requests for Intra-MSC Incoming Handovers to RNC......................... 3-119
3.9.3 Count of Successful Intra-MSC Incoming Handovers to RNC............................ 3-119
3.9.4 Count of Requests for Intra-MSC Outgoing Handovers from RNC .................... 3-120
3.9.5 Count of Successful Intra-MSC Outgoing Handovers from RNC ....................... 3-121
3.9.6 Count of Requests for Inter-MSC Incoming Handovers to RNC......................... 3-122
3.9.7 Count of Successful Inter-MSC Incoming Handovers to RNC............................ 3-123
3.9.8 Count of Requests for Inter-MSC Outgoing Handovers from RNC .................... 3-125
3.9.9 Count of Successful Inter-MSC Outgoing Handovers from RNC ....................... 3-127
3.9.10 Count of Outgoing Handovers from RNC Due to Time Critical......................... 3-128
3.9.11 Count of Outgoing Handovers from RNC Due to Resource Optimization ........ 3-129
3.9.12 Count of Outgoing Handovers from RNC Due to Radio Resource................... 3-130
3.9.13 Count of Outgoing Handovers from RNC Due to Directed Retry...................... 3-131
3.9.14 Count of Outgoing Handovers from RNC Due to O&M Intervention................. 3-132
3.9.15 Count of Outgoing Handovers from RNC Due to Network Optimization .......... 3-133
3.9.16 Count of Outgoing Handovers from RNC Due to Other Causes ...................... 3-134
3.9.17 Count of Handover Failures Due to RAB Preempted ....................................... 3-135
3.9.18 Count of Handover Failures Due to Handover Timeout.................................... 3-136
3.9.19 Count of Handover Failures Due to Timeout of Preparing Handover ............... 3-137
vi
3.9.20 Count of Handover Failures Due to Timeout of Waiting for Relocation Complete
Message....................................................................................................................... 3-138
3.9.21 Count of Handover Failures Due to Timeout of Queuing Radio Interface ........ 3-139
3.9.22 Count of Handover Failures Due to Timeout of Allocating Resource ............... 3-140
3.9.23 Count of Handover Failures Due to Establishing Radio Interface Unsuccessfully3-141
3.9.24 Count of Handover Failures Due to Unknown Target Cell................................ 3-142
3.9.25 Count of Handover Failures Due to Handover Cancelled................................. 3-143
3.9.26 Count of Handover Failures Due to Requested Ciphering Algorithm Not Supported3-144
3.9.27 Count of Handover Failures Due to Change of Ciphering Algorithm ................ 3-145
3.9.28 Count of Handover Failures Due to Radio Interface Failure............................. 3-146
3.9.29 Count of Handover Failures Due to UTRAN ..................................................... 3-147
3.9.30 Count of Handover Failures Due to Requested Traffic Class Unavailable....... 3-148
3.9.31 Count of Handover Failures Due to Invalid RAB Parameter Value .................. 3-149
3.9.32 Count of Handover Failures Due to Requested Maximum Bit Rate Unavailable3-150
3.9.33 Count of Handover Failures Due to Requested Guaranteed Bit Rate Unavailable3-151
3.9.34 Count of Handover Failures Due to Requested Transfer Delay Unachievable 3-152
3.9.35 Count of Handover Failures Due to Invalid RAB Parameter Combination ....... 3-153
3.9.36 Count of Handover Failures Due to Violation of SDU Parameter Conditions... 3-154
3.9.37 Count of Handover Failures Due to Violation of Traffic Handling Priority Conditions3-155
3.9.38 Count of Handover Failures Due to Violation of Requested Guaranteed Bit Rate
Conditions .................................................................................................................... 3-156
3.9.39 Count of Handover Failures Due to User Plane Version Not Supported .......... 3-157
3.9.40 Count of Handover Failures Due to Iu UP Negotiation Failure ......................... 3-158
3.9.41 Count of Handover Failures Due to Target System Failure.............................. 3-159
3.9.42 Count of Handover Failures Due to Invalid RAB ID .......................................... 3-160
3.9.43 Count of Handover Failures Due to No Remaining RAB .................................. 3-161
3.9.44 Count of Handover Failures Due to Interaction with Other Procedures............ 3-162
3.9.45 Count of Handover Failures Due to Requested Maximum Bit Rate for Downlink
Unavailable................................................................................................................... 3-163
3.9.46 Count of Handover Failures Due to Requested Maximum Bit Rate for Uplink
Unavailable................................................................................................................... 3-164
3.9.47 Count of Handover Failures Due to Requested Guaranteed Bit Rate for Downlink
Unavailable................................................................................................................... 3-165
3.9.48 Count of Handover Failures Due to Requested Guaranteed Bit Rate for Uplink
Unavailable................................................................................................................... 3-166
3.9.49 Count of Handover Failures Due to Repeated Consistency Check Failure...... 3-167
3.9.50 Count of Handover Failures Due to UE Generated Signaling Connection Released3-168
3.9.51 Count of Handover Failures Due to Requested Information Unavailable ......... 3-169
3.9.52 Count of Handover Failures Due to Target System Not Supported.................. 3-170
3.9.53 Count of Handover Failures Due to Radio Connection with UE Lost ............... 3-171
3.9.54 Count of Handover Failures Due to RNC Unable to Establish All RFCs .......... 3-172
3.9.55 Count of Handover Failures Due to Target Not Allowed................................... 3-173
vii
3.9.56 Count of Handover Failures Due to Signaling Transport Resource Failure ..... 3-174
3.9.57 Count of Handover Failures Due to Iu Transport Connection Setup Failure .... 3-175
3.9.58 Count of Handover Failures Due to Protocol Failure ........................................ 3-176
3.9.59 Count of Handover Failures Due to No Resource Available............................. 3-177
3.9.60 Count of Handover Failures Due to Unspecified Cause ................................... 3-178
3.10 Ciphering Mode Setting ............................................................................................... 3-179
3.10.1 Overview of MS_S_CIPHER_TRAF ................................................................. 3-179
3.10.2 Count of Requests for Setting Ciphering Mode During Location Update ......... 3-179
3.10.3 Count of Successes in Setting Ciphering Mode During Location Update ........ 3-181
3.10.4 Count of Requests for Setting Ciphering Mode During Service Access ........... 3-182
3.10.5 Count of Successes in Setting Ciphering Mode During Service Access .......... 3-183
3.11 Paging.......................................................................................................................... 3-185
3.11.1 Overview of MS_S_PAGING_TRAF ................................................................. 3-185
3.11.2 Count of PAGING Messages First Sent Through A-Interface .......................... 3-185
3.11.3 Count of Responses for PAGING Messages First Sent Through A-Interface .. 3-186
3.11.4 Count of PAGING Messages Repeatedly Sent Through A-Interface ............... 3-187
3.11.5 Count of Responses for PAGING Messages Repeatedly Sent Through A-Interface3-188
3.11.6 Count of PAGING Messages First Sent Through Iu-Interface.......................... 3-189
3.11.7 Count of Responses for PAGING Messages First Sent Through Iu-Interface . 3-190
3.11.8 Count of PAGING Messages Repeatedly Sent Through Iu-Interface............... 3-191
3.11.9 Count of Responses for PAGING Messages Repeatedly Sent Through Iu-Interface
...................................................................................................................................... 3-192
3.11.10 Count of PAGING Messages First Sent Through Gs-Interface ...................... 3-193
3.11.11 Count of Responses for PAGING Messages First Sent Through Gs-Interface3-194
3.11.12 Count of PAGING Messages Repeatedly Sent Through Gs-Interface ........... 3-195
3.11.13 Count of Responses for PAGING Messages Repeatedly Sent Through
Gs-Interface.................................................................................................................. 3-196
Chapter 4 MSC Special Services ................................................................................................. 4-1

4.2 Location Service ................................................................................................................ 4-1
4.2.1 Overview of MS_LCS_SRV .................................................................................... 4-1
4.2.2 Count of Location Requests (Emergency Services) ............................................... 4-1
4.2.3 Count of Location Successes (Emergency Services) ............................................. 4-2
4.2.4 Count of Location Requests (Value-Added Services)............................................. 4-3
4.2.5 Count of Location Successes (Value-Added Services) .......................................... 4-4
4.2.6 Count of Location Requests (PLMN Operator Services) ........................................ 4-5
4.2.7 Count of Location Successes (PLMN Operator Services)...................................... 4-6
4.2.8 Count of Location Requests (Lawful Interception Services) ................................... 4-7
4.2.9 Count of Location Successes (Lawful Interception Services)................................. 4-8
4.3 Bearer Services ................................................................................................................. 4-9
4.3.1 Overview of MS_DIG_TRAF ................................................................................... 4-9
4.3.2 Count of Use of Asynchronous Digital Service BS2X ........................................... 4-10
viii
4.3.3 Traffic of Asynchronous Digital Service BS2X ...................................................... 4-10

4.3.4 Count of Use of Dedicated Digital Service BS4X.................................................. 4-11
4.3.5 Traffic of Dedicated Digital Service BS4X............................................................. 4-11
4.3.6 Count of Use of Synchronous Digital Service BS3X............................................. 4-12
4.3.7 Traffic of Synchronous Digital Service BS3X........................................................ 4-13
4.3.8 Count of Use of Dedicated Packet Service BS5X................................................. 4-13
4.3.9 Traffic of Dedicated Packet Service BS5X............................................................ 4-14
4.3.10 Count of Use of Fax Digital Service .................................................................... 4-14
4.3.11 Traffic of Fax Digital Service ............................................................................... 4-15
4.3.12 Count of Use of Alternate Speech/Data Synchronous Digital Service................ 4-15
4.3.13 Traffic of Alternate Speech/Data Synchronous Digital Service........................... 4-16
4.3.14 Count of Use of Asynchronous Digital Service BS20 ......................................... 4-16
4.3.15 Traffic of Asynchronous Data Service BS20....................................................... 4-17
4.3.16 Count of Use of Basic Packet Service BS30 ...................................................... 4-17
4.3.17 Traffic of Basic Packet Service BS30 ................................................................. 4-18
4.4 NI_LR Location ................................................................................................................ 4-18
4.4.1 Overview of MS_LCS_NI_LR................................................................................ 4-18
4.4.2 Count of NI_LRs.................................................................................................... 4-19
4.4.3 Count of NI_LR Successes ................................................................................... 4-20
4.4.4 Count of NI_LR Failures Due to System Failure................................................... 4-21
4.4.5 Count of NI_LR Failures Due to Unqualified Data ................................................ 4-22
4.4.6 Count of NI_LR Failures Due to Lack of Data....................................................... 4-23
4.4.7 Count of NI_LR Failures Due to Resource Limitation ........................................... 4-24
4.4.8 Count of Location Failures Due to Timeout in Waiting for Report_CNF from GMLC4-25
4.4.9 Count of Location Failures Due to Timeout in Waiting for UE Location Report
Message......................................................................................................................... 4-26
4.5 Mobile-Originated Location Service................................................................................. 4-27
4.5.1 Overview MS_LCS_MO_LR ................................................................................. 4-27
4.5.2 Count of MO Location Requests ........................................................................... 4-28
4.5.3 Count of MO Location Successes......................................................................... 4-29
4.5.4 Count of MO Location Failures Due to MSC Failure............................................. 4-29
4.5.5 Count of MO Location Failures Due to Unqualified Data from MSC..................... 4-30
4.5.6 Count of MO Location Failures Due to Lack of Data at MSC ............................... 4-31
4.5.7 Count of MO Location Failures Due to Inconsistent Information Format at MSC. 4-32
4.5.8 Count of MO Location Failures Due to Unauthorized Data at VLR ...................... 4-33
4.5.9 Count of MO Location Failures Due to Location Method Failure at MSC............. 4-34
4.5.10 Count of MO Location Failures Due to GMLC Failure ........................................ 4-35
4.5.11 Count of MO Location Failures Due to Lack of Data at GMLC........................... 4-36
4.5.12 Count MO Location Failures Due to Resource Limitation at GMLC ................... 4-37
4.5.13 Count of MO Location Failures Due to Unqualified Data from GMLC ................ 4-38
4.5.14 Count of MO Location Failures Due to Unknown Subscriber at GMLC.............. 4-39
4.5.15 Count of MO Location Failures Due to Unauthorized Network at GMLC ........... 4-40
ix
4.5.16 Count of MO Location Failures Due to Unknown/Unreachable LCS Client at GMLC

........................................................................................................................................ 4-41
4.5.17 Count of MO Location Failures Due to Timeout in Waiting for Report_CNF Message
from GMLC..................................................................................................................... 4-42
4.5.18 Count of MO Location Failures Due to Timeout in Waiting for UE Location Report
Response from RNC ...................................................................................................... 4-43
4.6 Mobile-Terminated Location Service ............................................................................... 4-44
4.6.1 Overview of MS_LCS_MT_LR .............................................................................. 4-44
4.6.2 Count of MT Location Requests............................................................................ 4-45
4.6.3 Count of MT Location Successes ......................................................................... 4-45
4.6.4 Count of MT Location Failures Due to System Failure ......................................... 4-46
4.6.5 Count of MT Location Failures Due to Lack of Data ............................................. 4-47
4.6.6 Count of MT Location Failures Due to Unqualified Data ...................................... 4-48
4.6.7 Count of MT Location Failures Due to Inconsistent Information Format .............. 4-49
4.6.8 Count of MT Location Failures Due to Unknown Subscriber................................ 4-50
4.6.9 Count of MT Location Failures Due to Absent Subscriber.................................... 4-51
4.6.10 Count of MT Location Failures Due to Unauthorized Network ........................... 4-52
4.6.11 Count of MT Location Failures Due to Unauthorized LCS Client ....................... 4-53
4.6.12 Count of MT Location Failures Due to Location Method Failure from RNC ....... 4-54
4.6.13 Count of MT Location Failures Due to Timeout in Waiting for UE Location Report
Response from RNC ...................................................................................................... 4-55
Chapter 5 Bearer Traffic ............................................................................................................... 5-1

5.2 Traffic Between BICC MGs................................................................................................ 5-2
5.2.1 Overview of MS_MGW_DEST_TRAF..................................................................... 5-2
5.2.2 Count of Seizures.................................................................................................... 5-2
5.2.3 Count of Connected Calls ....................................................................................... 5-3
5.2.4 Count of Answered Calls......................................................................................... 5-4
5.2.5 Count of Callee Busy .............................................................................................. 5-5
5.2.6 Count of Release Before Offhook ........................................................................... 5-6
5.2.7 Count of No Reply................................................................................................... 5-7
5.2.8 Seizure Traffic ......................................................................................................... 5-8
5.2.9 Traffic of Connected Calls....................................................................................... 5-9
5.2.10 Traffic of Answered Calls .................................................................................... 5-10
5.2.11 Call Completion Rate .......................................................................................... 5-11
5.2.12 Call Answer Rate ................................................................................................ 5-11
5.3 Intra-Office Path Across MG............................................................................................ 5-12
5.3.1 Overview of MS_INTERMGW_TRAF ................................................................... 5-12
5.3.2 Count of Path Seizure Attempts............................................................................ 5-12
5.3.3 Count of Path Seizures ......................................................................................... 5-12
5.3.4 Count of Same MG Path Seizures ........................................................................ 5-13
5.3.5 Count of Direct Path Seizures............................................................................... 5-13
x
5.3.6 Count of Path Seizures Across One MG .............................................................. 5-13

5.3.7 Count of Path Seizures Across Two MGs............................................................. 5-14
5.3.8 Count of Path Seizures Across Three MGs .......................................................... 5-14
5.3.9 Count of Path Overflow ......................................................................................... 5-15
5.4 Office Direction Outgoing Traffic...................................................................................... 5-15
5.4.1 Overview of MS_OFFICEDIR_OUT_TRAF .......................................................... 5-15
5.4.2 Count of Seizure Attempts .................................................................................... 5-16
5.4.3 Count of Seizures.................................................................................................. 5-17
5.4.4 Count of Connected Calls ..................................................................................... 5-18
5.4.5 Count of Answered Calls....................................................................................... 5-19
5.4.6 Count of Overflow ................................................................................................. 5-20
5.4.7 Count of Dual Seizures ......................................................................................... 5-20
5.4.8 Count of Trunk Retry............................................................................................. 5-21
5.4.9 Count of Peer End Congestion ............................................................................. 5-22
5.4.10 Count of Callee Busy .......................................................................................... 5-24
5.4.11 Count of Release Before Offhook ....................................................................... 5-26
5.4.12 Count of No Reply............................................................................................... 5-26
5.4.13 Count of Installed Bidirectional Circuits .............................................................. 5-28
5.4.14 Count of Available Bidirectional Circuits ............................................................. 5-29
5.4.15 Count of Blocked Bidirectional Circuits ............................................................... 5-29
5.4.16 Availability of outgoing trunks.............................................................................. 5-29
5.4.17 Seizure Rate........................................................................................................ 5-30
5.4.19 Call Answer Rate ................................................................................................ 5-30
5.4.20 Rate of Blocked Bidirectional Circuits ................................................................. 5-31
5.4.21 Traffic of Bidirectional Trunk Seizures ................................................................ 5-31
5.4.22 Seizure Traffic ..................................................................................................... 5-31
5.4.23 Traffic of Connected Calls................................................................................... 5-32
5.4.25 Average Seizure Duration ................................................................................... 5-33
5.4.26 Count of First Sub-Route Overflow ..................................................................... 5-33
5.4.27 Count of Second Sub-Route Overflow................................................................ 5-33
5.4.28 Count of Third Sub-Route Overflow .................................................................... 5-34
5.4.29 Count of Fourth Sub-Route Overflow.................................................................. 5-34
5.4.30 Count of Fifth Sub-Route Overflow ..................................................................... 5-35
5.4.31 Count of Sixth Sub-Route Overflow .................................................................... 5-35
5.4.32 Count of Seventh Sub-Route Overflow............................................................... 5-35
5.4.33 Count of Eighth Sub-Route Overflow.................................................................. 5-36
5.4.34 Count of Ninth Sub-Route Overflow.................................................................... 5-36
5.4.35 Count of Tenth Sub-Route Overflow................................................................... 5-37
5.4.36 Count of Eleventh Sub-Route Overflow .............................................................. 5-37
5.4.37 Count of Twelfth Sub-Route Overflow ................................................................ 5-37
xi
5.4.38 Count of Outgoing Trunk Receiving Called Subscriber Line Failure .................. 5-38
5.4.39 Count of Outgoing Trunk Calling Peer Office No Reply...................................... 5-39
5.4.40 Count of Caller Release Before Ringing ............................................................. 5-39
5.4.41 Average Seizure Traffic Per Line ........................................................................ 5-40
5.5 Office Direction Incoming Traffic...................................................................................... 5-41
5.5.1 Overview of MS_OFFICEDIR_INC_TRAF............................................................ 5-41
5.5.3 Count of Terminating Call Attempts ...................................................................... 5-43
5.5.4 Count of Transfer Call Attempts............................................................................ 5-43
5.5.7 Count of Terminating Answers.............................................................................. 5-45
5.5.8 Count of Transfer Answers ................................................................................... 5-45
5.5.9 Count of Call Loss Because of Intra-Office Congestion........................................ 5-46
5.5.12 Count of No Reply............................................................................................... 5-48
5.5.13 Count of Installed Circuits ................................................................................... 5-49
5.5.14 Count of Available Circuits .................................................................................. 5-50
5.5.15 Count of Blocked Circuits.................................................................................... 5-50
5.5.16 Count of Installed Bidirectional Circuits .............................................................. 5-50
5.5.17 Count of Available Bidirectional Circuits ............................................................. 5-51
5.5.18 Count of Blocked Bidirectional Circuits ............................................................... 5-51
5.5.19 Availability of Incoming Trunk ............................................................................. 5-51
5.5.21 Call Answer Rate ................................................................................................ 5-52
5.5.22 Rate of Blocked Circuits...................................................................................... 5-53
5.5.23 Rate of Blocked Bidirectional Circuits ................................................................. 5-53
5.5.24 Traffic of Bidirectional Trunk Seizures ................................................................ 5-53
5.5.25 Seizure Traffic ..................................................................................................... 5-54
5.5.28 Average Seizure Duration ................................................................................... 5-56
5.5.29 Average Seizure Traffic Per Line ........................................................................ 5-56
5.6 Destination Code Traffic .................................................................................................. 5-57
5.6.1 Overview of MS_DESTCODE_TRAF ................................................................... 5-57
5.6.2 Count of Call Attempt ............................................................................................ 5-58
5.6.3 Count of Outgoing Trunk Seizure.......................................................................... 5-58
5.6.4 Count of Ringing ................................................................................................... 5-58
5.6.5 Count of Answered Call ........................................................................................ 5-59
5.6.6 Call Completion Rate ............................................................................................ 5-60
5.6.7 Call Answer Rate................................................................................................... 5-60
xii
5.6.8 Seizure Traffic ....................................................................................................... 5-61

5.6.9 Traffic of Connected Call....................................................................................... 5-61
5.6.10 Traffic of Answered Call ...................................................................................... 5-62
5.6.11 Count of Last-Choice Route Overflow ................................................................ 5-62
5.6.12 Count of Early Release Before Ringing .............................................................. 5-62
5.6.13 Count of Early Release Before Offhook.............................................................. 5-63
5.6.14 Count of Callee No Answer................................................................................. 5-63
5.6.15 Count of Callee Rejection ................................................................................... 5-64
5.6.17 Count of Invalid Address ..................................................................................... 5-64
5.6.18 Count of Paging Not Replied............................................................................... 5-65
5.6.19 Count of Callee Absence .................................................................................... 5-65
5.6.20 Count of Restriction of Subscriber Service ......................................................... 5-65
5.6.21 Count of Private Tone ......................................................................................... 5-66
5.6.22 Count of Peer End Congestion ........................................................................... 5-66
5.6.23 Count of Connection Failure ............................................................................... 5-67
5.6.24 Count of Callee No Reply.................................................................................... 5-67
5.6.25 Count of Other Failure Reason ........................................................................... 5-68
5.7 Destination Traffic Distribution......................................................................................... 5-68
5.7.1 Overview of MS_OFFICE_DEST_DISTRIB_TRAF .............................................. 5-68
5.7.6 Seizure Traffic ....................................................................................................... 5-72
5.7.7 Traffic of Answered Calls ...................................................................................... 5-73
5.7.8 Count of Available Circuits .................................................................................... 5-74
5.7.9 Count of Installed Circuits ..................................................................................... 5-74
5.8 Supplementary Service Traffic......................................................................................... 5-76
5.8.1 Overview of MS_SS_INVOKE .............................................................................. 5-76
5.8.2 Count of Supplementary Service Invoke............................................................... 5-76
5.9 Trunk Office Direction Outgoing Traffic ........................................................................... 5-76
5.9.1 Overview of MS_TK_OFC_OUT_TRAF ............................................................... 5-76
5.9.4 Count of Received Ringing Messages.................................................................. 5-79
5.9.6 Call Completion Rate ............................................................................................ 5-81
5.9.7 Call Answer Rate................................................................................................... 5-81
5.9.8 Count of Overflow ................................................................................................. 5-82
5.9.9 Count of Main Control Circuit Contention ............................................................. 5-82
xiii
5.9.10 Count of Non–Main Control Circuit Contention................................................... 5-83

5.9.11 Count of Trunk Retry........................................................................................... 5-84
5.9.12 Seizure Traffic ..................................................................................................... 5-86
5.9.15 Count of Installed Circuits ................................................................................... 5-87
5.9.16 Count of Available Circuits .................................................................................. 5-88
5.9.17 Count of Blocked Circuits.................................................................................... 5-88
5.9.18 Count of Caller Release Before Offhook............................................................. 5-88
5.9.20 Count of Local Office Failure............................................................................... 5-90
5.9.21 Count of Callee No Answer................................................................................. 5-91
5.9.22 Count of Callee Rejection ................................................................................... 5-93
5.9.24 Count of Invalid Addresses ................................................................................. 5-94
5.9.25 Count of Callee Absent ....................................................................................... 5-94
5.9.26 Count of Restricted Subscriber Service .............................................................. 5-95
5.9.27 Count of Special Signal Tone.............................................................................. 5-95
5.9.28 Count of Congestion ........................................................................................... 5-95
5.9.29 Count of Paging No Reply................................................................................... 5-96
5.9.30 Count of Connection Failure ............................................................................... 5-96
5.9.31 Count of Callee No Reply.................................................................................... 5-96
5.9.32 Count of UMG Failure ......................................................................................... 5-98
5.9.33 Count of All Circuits Busy.................................................................................... 5-98
5.9.34 Count of Other Failure Reasons ......................................................................... 5-99
5.9.35 Count of First Sub-Route Overflow ..................................................................... 5-99
5.9.36 Count of Second Sub-Route Overflow.............................................................. 5-100
5.9.37 Count of Third Sub-Route Overflow .................................................................. 5-100
5.9.38 Count of Fourth Sub-Route Overflow................................................................ 5-100
5.9.39 Count of Fifth Sub-Route Overflow ................................................................... 5-101
5.9.40 Count of Sixth Sub-Route Overflow .................................................................. 5-101
5.9.41 Count of Seventh Sub-Route Overflow............................................................. 5-102
5.9.42 Count of Eighth Sub-Route Overflow................................................................ 5-102
5.9.43 Count of Ninth Sub-Route Overflow.................................................................. 5-102
5.9.44 Count of Tenth Sub-Route Overflow................................................................. 5-103
5.9.45 Count of Eleventh Sub-Route Overflow ............................................................ 5-103
5.9.46 Count of Twelfth Sub-Route Overflow .............................................................. 5-104
5.10 Trunk Office Direction Incoming Traffic ....................................................................... 5-104
5.10.1 Overview of MS_TK_OFC_INC_TRAF............................................................. 5-104
5.10.2 Count of Seizures.............................................................................................. 5-105
5.10.3 Count of Received Ringing Messages.............................................................. 5-106
5.10.4 Count of Answered Calls................................................................................... 5-107
xiv
5.10.5 Call Completion Rate ........................................................................................ 5-108

5.10.6 Call Answer Rate .............................................................................................. 5-108
5.10.7 Seizure Traffic ................................................................................................... 5-109
5.10.8 Traffic of Connected Calls................................................................................. 5-109
5.10.9 Traffic of Answered Calls .................................................................................. 5-110
5.10.10 Count of Installed Circuits ............................................................................... 5-110
5.10.11 Count of Available Circuits .............................................................................. 5-110
5.10.12 Count of Blocked Circuits................................................................................ 5-111
5.10.13 Count of Caller Release Before Offhook......................................................... 5-111
5.10.14 Count of Release Before Offhook ................................................................... 5-112
5.10.15 Count of Local Office Failure........................................................................... 5-113
5.10.16 Count of Callee No Answer............................................................................. 5-114
5.10.17 Count of Callee Rejection ............................................................................... 5-116
5.10.18 Count of Callee Busy ...................................................................................... 5-116
5.10.19 Count of Invalid Addresses ............................................................................. 5-117
5.10.20 Count of Callee Absent ................................................................................... 5-117
5.10.21 Count of Restricted Subscriber Service .......................................................... 5-118
5.10.22 Count of Special Signal Tone.......................................................................... 5-118
5.10.23 Count of Congestion ....................................................................................... 5-118
5.10.24 Count of Paging No Reply............................................................................... 5-119
5.10.25 Count of Connection Failure ........................................................................... 5-119
5.10.26 Count of Callee No Reply................................................................................ 5-119
5.10.27 Count of UMG Failure ..................................................................................... 5-121
5.10.28 Count of All Circuits Busy................................................................................ 5-121
5.10.29 Count of Other Failure Reasons ..................................................................... 5-122
5.11 Trunk Group Outgoing Traffic ...................................................................................... 5-122
5.11.1 Overview of MS_TKGRP_OUT_TRAF ............................................................. 5-122
5.11.2 Count of Seizure Attempts ................................................................................ 5-124
5.11.4 Count of Connected Calls ................................................................................. 5-125
5.11.6 Count of Overflow ............................................................................................. 5-127
5.11.7 Count of Trunk Circuit Type Mismatch.............................................................. 5-127
5.11.8 Count of Bearer Capability and Mode Mismatch .............................................. 5-128
5.11.9 Count of Dual Seizures ..................................................................................... 5-128
5.11.10 Count of Trunk Retry....................................................................................... 5-129
5.11.11 Count of Peer End Congestion ....................................................................... 5-130
5.11.12 Congestion Duration ....................................................................................... 5-132
5.11.14 Count of Callee Toll Busy................................................................................ 5-134
5.11.15 Count of Callee Local Busy............................................................................. 5-134
xv
5.11.17 Count of No Reply........................................................................................... 5-135

5.11.21 Count of Installed Bidirectional Circuits .......................................................... 5-138
5.11.22 Count of available bidirectional circuits........................................................... 5-139
5.11.23 Count of blocked bidirectional circuits............................................................. 5-139
5.11.24 Availability of outgoing trunks.......................................................................... 5-139
5.11.25 Seizure Rate.................................................................................................... 5-140
5.11.26 Call Completion Rate ...................................................................................... 5-140
5.11.27 Call Answer Rate ............................................................................................ 5-140
5.11.28 Rate of Blocked Circuits.................................................................................. 5-141
5.11.29 Rate of Blocked Bidirectional Circuits ............................................................. 5-141
5.11.30 Traffic of Bidirectional Trunk Seizures ............................................................ 5-141
5.11.31 Seizure Traffic ................................................................................................. 5-142
5.11.32 Traffic of Connected Calls............................................................................... 5-142
5.11.33 Traffic of Answered Calls ................................................................................ 5-142
5.11.34 Average Seizure Duration ............................................................................... 5-143
5.11.35 Count of Outgoing Trunk Receiving Called Subscriber Line Failure .............. 5-143
5.11.36 Count of Outgoing Trunk Calling Peer Office No Reply.................................. 5-144
5.11.37 Count of Caller Release Before Ringing ......................................................... 5-145
5.11.38 Average Seizure Traffic Per Line .................................................................... 5-146
5.12 Trunk Group Incoming Traffic ...................................................................................... 5-147
5.12.1 Overview of MS_TKGRP_INC_TRAF............................................................... 5-147
5.12.5 Count of Call Loss Because of Intra-Office Congestion ................................... 5-150
5.12.6 Congestion Duration ......................................................................................... 5-151
5.12.7 Count of Callee Busy ........................................................................................ 5-151
5.12.8 Count of Release Before Offhook ..................................................................... 5-152
5.12.9 Count of No Reply............................................................................................. 5-153
5.12.14 Count of available bidirectional circuits........................................................... 5-156
5.12.15 Count of blocked bidirectional circuits............................................................. 5-156
5.12.16 Availability of Incoming Trunk ......................................................................... 5-156
5.12.18 Call Answer Rate ............................................................................................ 5-157
5.12.19 Rate of Blocked Circuits.................................................................................. 5-158
xvi

5.12.22 Seizure Traffic ................................................................................................. 5-159
5.12.26 Average Seizure Traffic Per Line .................................................................... 5-160
5.13 VP Office Direction Incoming Traffic............................................................................ 5-161
5.13.1 Overview of MS_VP_OFFICEDIR_INC_TRAF................................................. 5-161
5.13.2 Count of Seizure ............................................................................................... 5-161
5.13.3 Count of Connected Call ................................................................................... 5-162
5.13.4 Count of Answered Call .................................................................................... 5-163
5.13.6 Call Answer Rate .............................................................................................. 5-164
5.13.7 Seizure Traffic ................................................................................................... 5-165
5.13.8 Traffic of Connected Call................................................................................... 5-165
5.13.9 Traffic of Answered Call .................................................................................... 5-165
5.13.10 Count of Callee Determined Busy................................................................... 5-166
5.13.11 Count of Release After Ringing....................................................................... 5-167
5.13.12 Count of No Reply........................................................................................... 5-168
5.13.13 Count of Rejection of Handover from 3G to 2G .............................................. 5-169
5.13.14 Count of Call Drop on RAN Side..................................................................... 5-169
5.13.15 Call Drop Rate on RAN Side........................................................................... 5-170
5.14 VP Office Direction Outgoing Traffic............................................................................ 5-171
5.14.1 Overview of MS_VP_OFFICEDIR_OUT_TRAF ............................................... 5-171
5.14.2 Count of Seizure Attempt .................................................................................. 5-171
5.14.3 Count of Seizure ............................................................................................... 5-172
5.14.7 Call Answer Rate .............................................................................................. 5-175
5.14.8 Seizure Traffic ................................................................................................... 5-176
5.14.10 Traffic of Answered Call .................................................................................. 5-177
5.14.13 Count of No Reply........................................................................................... 5-179
5.14.14 Count of Rejection of Handover from 3G to 2G .............................................. 5-180
5.14.15 Count of Call Drop on RAN Side..................................................................... 5-180
5.14.16 Call Drop Rate on RAN Side........................................................................... 5-181
5.15 VP Destination Traffic .................................................................................................. 5-182
5.15.1 Overview of MS_VP_DEST_TRAF ................................................................... 5-182
xvii
5.15.2 Count of Call Attempt ........................................................................................ 5-182

5.15.5 Seizure Traffic ................................................................................................... 5-185
5.15.8 Average Call Duration ....................................................................................... 5-186
5.15.10 Call Answer Rate ............................................................................................ 5-187
5.15.11 Count of Abandon Before Alerting .................................................................. 5-187
5.15.12 Count of Incomplete Address.......................................................................... 5-188
5.15.15 Count of No Reply........................................................................................... 5-191
5.15.16 Count of Mobile Subscriber Unreachable ....................................................... 5-192
5.15.17 Count of Inter-Office Trunk Overflow .............................................................. 5-193
5.16 VP Trunk Office Direction Incoming Traffic ................................................................. 5-193
5.16.1 Overview of MS_TK_VP_OFC_INC_TRAF ...................................................... 5-193
5.16.2 Count of Seizure ............................................................................................... 5-194
5.16.3 Count of Ringing ............................................................................................... 5-195
5.16.6 Call Answer Rate .............................................................................................. 5-197
5.16.7 Seizure Traffic ................................................................................................... 5-198
5.16.12 Count of No Reply........................................................................................... 5-200
5.16.13 Count of Congestion ....................................................................................... 5-202
5.17 VP Trunk Office Direction Outgoing Traffic ................................................................. 5-203
5.17.1 Overview of MS_TK_VP_OFC_OUT_TRAF..................................................... 5-203
5.17.2 Count of Seizure Attempt .................................................................................. 5-203
5.17.3 Count of Seizure ............................................................................................... 5-204
5.17.4 Count of Ringing ............................................................................................... 5-204
5.17.7 Call Answer Rate .............................................................................................. 5-206
5.17.8 Seizure Traffic ................................................................................................... 5-207
5.17.10 Traffic of Answered Call .................................................................................. 5-207
5.17.11 Count of Overflow ........................................................................................... 5-208
xviii

5.17.14 Count of No Reply........................................................................................... 5-209
Chapter 6 Call Processing............................................................................................................ 6-1

6.2 GSM Call Drop Rate .......................................................................................................... 6-1
6.2.1 Overview of MS_2G_CALL_DROP_RATE_TRAP ................................................. 6-1
6.2.3 Count of Connected MO Calls ................................................................................ 6-2
6.2.4 Count of Connected MT Calls ................................................................................. 6-2
6.2.5 Count of Dropped Calls........................................................................................... 6-3
6.2.6 Count of Dropped MO Calls .................................................................................... 6-3
6.2.7 Count of Dropped MT Calls..................................................................................... 6-3
6.2.8 Count of Dropped Calls Due to Handover Failure .................................................. 6-4
6.2.9 Call Drop Rate......................................................................................................... 6-4
6.3 MTC Success Rate ............................................................................................................ 6-5
6.3.1 Overview of MS_MTC_SUCC_RATE_TRAF.......................................................... 6-5
6.3.2 Count of Pagings..................................................................................................... 6-5
6.3.3 Count of Paging Responses ................................................................................... 6-6
6.3.4 Paging Success Rate.............................................................................................. 6-7
6.3.6 Count of Connected Intra-Office Calls .................................................................... 6-8
6.3.7 Count of Connected Incoming Calls........................................................................ 6-8
6.3.8 MT Call Completion Rate ........................................................................................ 6-8
6.4 WCDMA Call Drop Rate .................................................................................................... 6-9
6.4.1 Overview of MS_3G_CALL_DROP_RATE_TRAP ................................................. 6-9
6.4.3 Count of Connected MO Calls .............................................................................. 6-10
6.4.4 Count of Connected MT Calls ............................................................................... 6-10
6.4.5 Count of Dropped Calls......................................................................................... 6-11
6.4.6 Count of Dropped MO Calls .................................................................................. 6-11
6.4.7 Count of Dropped MT Calls................................................................................... 6-12
6.4.8 Count of Dropped Calls Due to Handover Failure ................................................ 6-13
6.4.9 Call Drop Rate....................................................................................................... 6-14
6.5 Call Setup Rate................................................................................................................ 6-14
6.5.1 Overview of MS_DELIVERY_SUCC_RATE_TRAF.............................................. 6-14
6.5.2 Count of Call Setup Attempts................................................................................ 6-15
6.5.3 Count of Call Setup Attempts from Mobile Subscriber to Mobile Subscriber........ 6-15
6.5.4 Count of Call Setup Attempts from Mobile Subscriber to Fixed Subscriber ......... 6-16
6.5.5 Count of Call Setup Attempts from Fixed Subscriber to Mobile Subscriber ......... 6-17
6.5.6 Count of Call Setup Attempts from Fixed Subscriber to Fixed Subscriber ........... 6-18
6.5.7 Count of Successful Call Setups........................................................................... 6-19
xix
6.5.8 Count of Successful Call Setups from Mobile Subscriber to Mobile Subscriber .. 6-19
6.5.9 Count of Successful Call Setups from Mobile Subscriber to Fixed Subscriber .... 6-20
6.5.10 Count of Successful Call Setups from Fixed Subscriber to Mobile Subscriber .. 6-21
6.5.11 Count of Successful Call Setups from Fixed Subscriber to Fixed Subscriber .... 6-22
6.5.12 Call Setup Success Rate .................................................................................... 6-23
6.6 Answer Rate .................................................................................................................... 6-23
6.6.1 Overview of MS_CALL_SUCC_RATE_TRAF ...................................................... 6-23
6.6.2 Count of Call Attempts .......................................................................................... 6-24
6.6.3 Count of MO Call Attempts ................................................................................... 6-24
6.6.4 Count of Incoming Call Attempts by Fixed Subscriber.......................................... 6-25
6.6.6 Count of Answers to MO Calls .............................................................................. 6-26
6.6.7 Count of Answers to Incoming Calls by Fixed Subscriber .................................... 6-27
6.6.8 Answer Rate.......................................................................................................... 6-28
Chapter 7 Call Record ................................................................................................................... 7-1

7.2 Combined Object Conditions Traffic .................................................................................. 7-1
7.2.1 Overview of MS_TKGRP_INC_TRAF..................................................................... 7-1
7.2.2 Count of Call Attempts ............................................................................................ 7-6
7.2.3 Count of Seizures.................................................................................................... 7-6
7.2.5 Count of Answered Calls......................................................................................... 7-7
7.2.6 Seizure Traffic ......................................................................................................... 7-7
7.2.7 Traffic of Answered Calls ........................................................................................ 7-7
7.2.8 Total Seizure Duration ............................................................................................ 7-8
7.2.9 Total Answer Duration............................................................................................. 7-8
7.2.10 Rate of Connected Calls ....................................................................................... 7-8
7.2.11 Average Seizure Duration ..................................................................................... 7-9
7.2.12 Average Answer Duration ..................................................................................... 7-9
7.2.13 Count of Malicious Call Identification Successes.................................................. 7-9
7.2.14 Count of Malicious Call Identification Failures .................................................... 7-10
7.2.15 Count of Switch Congestions .............................................................................. 7-10
7.2.16 Count of Long Time No Dialing ........................................................................... 7-10
7.2.17 Count of Long Time No Reply............................................................................. 7-11
7.2.18 Count of Temporary Failures .............................................................................. 7-11
7.2.19 Count of Self-Test Successes............................................................................. 7-11
7.2.20 Count of No Messages........................................................................................ 7-12
7.2.21 Count of No Ringing............................................................................................ 7-12
7.2.22 Count of No Releases ......................................................................................... 7-12
7.2.23 Count of Inband Signals...................................................................................... 7-13
7.2.24 Count of Continuity Check Failures .................................................................... 7-13
7.2.25 Count of Exceed Maximum Retries..................................................................... 7-13
xx
7.2.26 Count of Subscriber Releases Before Ringing ................................................... 7-14

7.2.27 Count of Releases Before Answers .................................................................... 7-14
7.2.28 Count of Call Barrings ......................................................................................... 7-14
7.2.29 Count of Switch Failures ..................................................................................... 7-15
7.2.30 Count of Callee Toll Busy.................................................................................... 7-15
7.2.31 Count of Callee Local Busy................................................................................. 7-15
7.2.32 Count of Peer Equipment Congestions............................................................... 7-16
7.2.33 Count of Call Failures.......................................................................................... 7-16
7.2.34 Count of Circuit Contentions ............................................................................... 7-17
7.2.35 Count of Invalid Numbers.................................................................................... 7-17
7.2.36 Count of Call Restrictions by NMS...................................................................... 7-17
7.2.37 Count of CPU Congestions and Overload .......................................................... 7-18
7.2.38 Count of No CR Resources................................................................................. 7-18
7.2.39 Count of No CCB Resources .............................................................................. 7-18
7.2.40 Count of Incoming Forwarded Call Restrictions.................................................. 7-19
7.2.41 Count of Dialing Interval Timeout........................................................................ 7-19
7.2.42 Count of Signaling Fault...................................................................................... 7-19
7.2.43 Count of Black and White List Restrictions ......................................................... 7-20
7.2.44 Count of Caller Number Discrimination Failures................................................. 7-20
7.2.45 Count of No A Interface Circuits for Bearer Service ........................................... 7-20
7.2.46 Count of Circuits Without A Interface.................................................................. 7-21
7.2.47 Count of CUG Service Incompatible ................................................................... 7-21
7.2.48 Count of Unknown CUG...................................................................................... 7-21
7.2.49 Count of Unselected CUG................................................................................... 7-22
7.2.50 Count of CUG Outgoing Call Barring .................................................................. 7-22
7.2.51 Count of CUG Incoming Call Barring .................................................................. 7-22
7.2.52 Count of CUG Supplementary Service Failures ................................................. 7-23
7.2.53 Count of CUG Destination Incompatible ............................................................. 7-23
7.2.54 Count of Call Releases ....................................................................................... 7-23
7.2.55 Count of Switchover Successes.......................................................................... 7-24
7.2.56 Count of Switchover Failures .............................................................................. 7-24
7.2.57 Count of Duration Limit Timeout ......................................................................... 7-24
7.2.58 Count of Termination Resource Application Failures.......................................... 7-25
7.2.59 Count of Non-Existent Called Numbers .............................................................. 7-25
7.2.60 Count of No Answer from Called Mobile Subscribers......................................... 7-25
7.2.61 Count of Called Mobile Subscriber Barring of Incoming Calls ............................ 7-26
7.2.62 Count of Caller Barring of Outgoing Calls........................................................... 7-26
7.2.63 Count of Callees Unreachable or Switched off ................................................... 7-27
7.2.64 Count of Calling Local Subscriber Without Dialing Area Code ........................... 7-27
7.2.65 Count of Called Mobile Subscriber Busy ............................................................ 7-27
7.2.66 Count of Called Mobile Subscriber Switched off................................................. 7-28
7.2.67 Count of Needed Function Not Applied .............................................................. 7-28
xxi
7.2.68 Count of Calling Mobile Subscriber in Other Area Without Dialing 0.................. 7-28
7.2.69 Count of Call Forwarding Conflicts...................................................................... 7-29
7.2.70 Count of Errors Found When Getting Routing Information Through HLR .......... 7-29
7.2.71 Count of Carrier Barring of All Outgoing Calls .................................................... 7-29
7.2.72 Count of Carrier Barring of All Outgoing International Calls ............................... 7-30
7.2.73 Count of Subscriber Barring of All Outgoing International Calls ......................... 7-30
7.2.74 Count of BOIC-exHC Barred by Subscribers...................................................... 7-30
7.2.75 Count of BOIC-exHC Barred by Operators......................................................... 7-31
7.2.76 Count of Carrier Barring of All Incoming Calls .................................................... 7-31
7.2.77 Count of Carrier Barring of Entertainment Consoles .......................................... 7-31
7.2.78 Count of Carrier Barring of Consoles.................................................................. 7-32
7.2.79 Count of Subscribers Out of Service Area .......................................................... 7-32
7.2.80 Count of Carrier Barring of National Toll............................................................. 7-33
7.2.81 Count of Call Failures Because of Unknown Reason ......................................... 7-33
7.2.82 Count of Unallocated Numbers ........................................................................... 7-33
7.2.83 Count of No Routes to Transit Network .............................................................. 7-34
7.2.84 Count of No Routes to Destination ..................................................................... 7-34
7.2.85 Count of Sending Special Signal Tones ............................................................. 7-35
7.2.86 Count of Dialing Wrong Toll Prefix ...................................................................... 7-35
7.2.87 Count of Unaccepted Paths ................................................................................ 7-35
7.2.88 Count of Calls Established and Delivered on Path Established ......................... 7-36
7.2.89 Count of Call Barring Decided by Carrier............................................................ 7-36
7.2.90 Count of Circuits Reserved for Reuse ................................................................ 7-36
7.2.91 Count of Normal Cleared Calls ........................................................................... 7-37
7.2.93 Count of No Responses from Callee .................................................................. 7-37
7.2.94 Count of No Answer from Callee......................................................................... 7-38
7.2.95 Count of Callee Absent ....................................................................................... 7-38
7.2.96 Count of Call Rejected ........................................................................................ 7-38
7.2.97 Count of Called Numbers Changed .................................................................... 7-39
7.2.98 Count of No Idle Circuits ..................................................................................... 7-39
7.2.99 Count of RAB Resources Pre-Used.................................................................... 7-39
7.2.100 Count of Destination Fault................................................................................. 7-40
7.2.101 Count of Invalid Number Format ....................................................................... 7-40
7.2.102 Count of Facility Rejected ................................................................................. 7-40
7.2.103 Count of Responses to STATUS ENQUIRY..................................................... 7-41
7.2.104 Count of Normal Cleared Calls ......................................................................... 7-41
7.2.105 Count of No Available Circuits .......................................................................... 7-41
7.2.106 Count of Network Failures................................................................................. 7-42
7.2.107 Count of Temporary Failures ............................................................................ 7-42
7.2.108 Count of Switch Congestions ............................................................................ 7-42
7.2.109 Count of Access Information Lost ..................................................................... 7-43
xxii
7.2.110 Count of Circuits Unavailable............................................................................ 7-43

7.2.111 Count of Prior Calls Blocked ............................................................................. 7-43
7.2.112 Count of No Available Resources ..................................................................... 7-44
7.2.113 Count of No Suitable Service Quality................................................................ 7-44
7.2.114 Count of Required Facility Not Booked............................................................. 7-45
7.2.115 Count of CUG Barring Out-Group Calls............................................................ 7-45
7.2.116 Count of CUG Incoming Calls Not Allowed....................................................... 7-45
7.2.117 Count of Bearer Capability Not Registered....................................................... 7-46
7.2.118 Count of No Available Bearer Capability........................................................... 7-46
7.2.119 Count of No Suitable Services or Optional Projects ......................................... 7-46
7.2.120 Count of Bearer Capability Not Carried Out...................................................... 7-47
7.2.121 Count of Route Type Not Supported................................................................. 7-47
7.2.122 Count of AOC Service Request Failures .......................................................... 7-47
7.2.123 Count of ACMs Greater or Equal to ACMmax .................................................. 7-48
7.2.124 Count of Requested Facility Not Supported...................................................... 7-48
7.2.125 Count of Only Having Restricted Bearer Capability .......................................... 7-48
7.2.126 Count of IWF Resources Unavailable............................................................... 7-49
7.2.127 Count of Services or Optional Projects Not Supported..................................... 7-49
7.2.128 Count of Invalid Call Reference ........................................................................ 7-49
7.2.129 Count of Identified Paths Do Not Exist.............................................................. 7-50
7.2.130 Count of Callees Not in CUG ............................................................................ 7-50
7.2.131 Count of Incompatible Destinations .................................................................. 7-50
7.2.132 Count of Non-Existent CUGs ............................................................................ 7-51
7.2.133 Count of Invalid Transit Network Selections ..................................................... 7-51
7.2.134 Count of Invalid Messages................................................................................ 7-51
7.2.135 Count of Non-Existent or Not Supported Message Types................................ 7-52
7.2.136 Count of Non-Existent or Not Supported Information Elements ....................... 7-52
7.2.137 Count of Recoveries of Timer Timeout ............................................................. 7-52
7.2.138 Count of Non-Existent or Not Invoked Parameters........................................... 7-53
7.2.139 Count of Messages with Unrecognized Parameters......................................... 7-53
7.2.140 Count of Protocol Errors.................................................................................... 7-53
7.2.141 Count of Interworking ........................................................................................ 7-54
7.3 Traffic Distribution and Duration ...................................................................................... 7-54
7.3.1 Overview of MS_TKGRP_INC_TRAF................................................................... 7-54
7.3.2 Count of Call Source Inlet Information .................................................................. 7-55
7.3.3 Count of Call Source Outlet Information ............................................................... 7-55
7.3.4 Count of Caller Numbers....................................................................................... 7-55
7.3.5 Count of Dialed Numbers...................................................................................... 7-56
7.3.6 Caller Service Request Time ................................................................................ 7-57
7.3.7 Callee Service Setup Time.................................................................................... 7-57
7.3.8 Ringing Time ......................................................................................................... 7-58
7.3.9 Answer Time ......................................................................................................... 7-58
xxiii
7.3.10 Release Time ...................................................................................................... 7-58
Chapter 8 Total Traffic of the Office ............................................................................................ 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-7
8.2.8 Count of Peer Office Congestions........................................................................... 8-8
8.2.9 Count of Callee Busy .............................................................................................. 8-9
8.2.10 Count of Connected Calls ................................................................................... 8-10
8.2.11 Count of Releases Before the Pickup ................................................................. 8-11
8.2.13 Count of Answered Calls..................................................................................... 8-13
8.2.14 Seizure Traffic ..................................................................................................... 8-14
8.2.15 Connected Traffic................................................................................................ 8-15
8.2.16 Answered Traffic ................................................................................................. 8-16
8.2.18 Answer Rate........................................................................................................ 8-17
8.3 MS-Originated Traffic....................................................................................................... 8-18
8.3.1 Overview of MS_OFFICE_2G_ORG_TRAF ......................................................... 8-18
8.3.3 Count of Mobile Caller Authentication Failures..................................................... 8-19
8.3.4 Count of Mobile Caller Ciphering Mode Setting Failures ...................................... 8-19
8.3.5 Count of Mobile Caller Barring .............................................................................. 8-20
8.3.6 Count of Mobile Caller Trunk Resource Overflow................................................. 8-20
8.3.7 Count of Mobile Caller Traffic Channel allocations Failures ................................. 8-21
8.3.8 Count of Wrongly Dialed Numbers........................................................................ 8-22
8.3.9 Count of Releases Before Ringing........................................................................ 8-23
8.3.10 Count of Terminal Application Failures ............................................................... 8-23
8.3.11 Count of Common Resource Application Failures .............................................. 8-24
8.3.14 Seizure Traffic ..................................................................................................... 8-27
8.3.18 Answer Rate........................................................................................................ 8-28
8.3.19 Count of Callee Power-Off .................................................................................. 8-29
xxiv
8.4 MS-Terminated Incoming Traffic ..................................................................................... 8-29

8.4.1 Overview of MS_OFFICE_2G_INCTRM_TRAF ................................................... 8-29
8.4.4 Count of Terminal Application Failures ................................................................. 8-32
8.4.5 Count of Common Resource Application Failures ................................................ 8-33
8.4.6 Count of Callee Busy ............................................................................................ 8-34
8.4.7 Count of Mobile Callee Trunk Resource Overflow................................................ 8-35
8.4.8 Count of Mobile Callee Traffic Channel allocations Failures ................................ 8-36
8.4.9 Count of MS Unavailable ...................................................................................... 8-37
8.4.13 Count of Mobile Callee Determined Busy ........................................................... 8-41
8.4.15 Seizure Traffic ..................................................................................................... 8-43
8.4.19 Answer Rate........................................................................................................ 8-46
8.5 MS-Terminated Traffic ..................................................................................................... 8-47
8.5.1 Overview of MS_OFFICE_2G_TRM_TRAF ......................................................... 8-47
8.5.6 Count of Mobile Callee Trunk Resource Overflow................................................ 8-51
8.5.7 Count of Mobile Callee Traffic Channel allocations Failures ................................ 8-52
8.5.8 Count of MS Unavailable ...................................................................................... 8-53
8.5.12 Count of Mobile Callee Determined Busy ........................................................... 8-57
8.5.14 Seizure Traffic ..................................................................................................... 8-59
8.5.18 Answer Rate........................................................................................................ 8-62
8.6 3G VP Subscriber Originated Traffic ............................................................................... 8-63
8.6.1 Overview of MS_VP_3G_ORG_TRAF ................................................................. 8-63
8.6.2 Count of VP Call Attempts .................................................................................... 8-63
xxv
8.6.3 Count of VP Connected Calls ............................................................................... 8-64

8.6.4 Count of VP Answered Calls................................................................................. 8-65
8.6.5 Count of Failures Due to Bearer Capability .......................................................... 8-66
8.6.6 Seizure Traffic ....................................................................................................... 8-67
8.6.7 VP Connected Traffic ............................................................................................ 8-67
8.6.8 VP Answered Traffic ............................................................................................. 8-67
8.6.9 VP Call Completion Rate ...................................................................................... 8-68
8.6.10 VP Answer Rate .................................................................................................. 8-68
8.7 3G VP Subscriber Terminated Traffic.............................................................................. 8-68
8.7.1 Overview of MS_VP_3G_TRM_TRAF .................................................................. 8-68
8.7.2 Count of VP Call Attempts .................................................................................... 8-69
8.7.3 Count of VP Connected Calls ............................................................................... 8-70
8.7.4 Count of VP Answered Calls................................................................................. 8-71
8.7.5 Count of Failures Due to Bearer Capability .......................................................... 8-72
8.7.6 Seizure Traffic ....................................................................................................... 8-73
8.7.7 VP Connected Traffic ............................................................................................ 8-73
8.7.8 VP Answered Traffic ............................................................................................. 8-73
8.7.9 VP Call Completion Rate ...................................................................................... 8-74
8.7.10 VP Answer Rate .................................................................................................. 8-74
8.8 UE-Originated Outgoing Traffic ....................................................................................... 8-74
8.8.1 Overview of MS_OFFICE_3G_ORGOUT_TRAF ................................................. 8-74
8.8.7 Count of Outgoing Trunk Overflow........................................................................ 8-81
8.8.8 Count of Peer Office Congestions......................................................................... 8-82
8.8.14 Seizure Traffic ..................................................................................................... 8-88
8.8.18 Answer Rate........................................................................................................ 8-91
8.9 UE-Originated Traffic ....................................................................................................... 8-92
8.9.1 Overview of MS_OFFICE_3G_ORG_TRAF ......................................................... 8-92
8.9.3 Count of Mobile Caller Authentication Failures..................................................... 8-93
xxvi
8.9.4 Count of Mobile Caller Ciphering Mode Setting Failures ...................................... 8-93
8.9.5 Count of Mobile Caller Barring .............................................................................. 8-94
8.9.6 Count of Mobile Caller Trunk Resource Overflow................................................. 8-94
8.9.7 Count of Mobile Caller Traffic Channel allocations Failures ................................. 8-95
8.9.10 Count of Terminal Application Failures ............................................................... 8-97
8.9.11 Count of Common Resource Application Failures .............................................. 8-98
8.9.14 Seizure Traffic ................................................................................................... 8-100
8.9.15 Connected Traffic.............................................................................................. 8-100
8.9.16 Answered Traffic ............................................................................................... 8-101
8.9.18 Answer Rate...................................................................................................... 8-102
8.9.19 Count of Callee Power-Off ................................................................................ 8-102
8.10 UE-Terminated Incoming Traffic.................................................................................. 8-102
8.10.1 Overview of MS_OFFICE_3G_INCTRM_TRAF ............................................... 8-102
8.10.2 Count of Call Attempts ...................................................................................... 8-103
8.10.3 Count of Releases Before Ringing.................................................................... 8-104
8.10.4 Count of Terminal Application Failures ............................................................. 8-105
8.10.5 Count of Common Resource Application Failures ............................................ 8-106
8.10.7 Count of Mobile Callee Traffic Channel allocations Failures ............................ 8-108
8.10.8 Count of MS Unavailable .................................................................................. 8-109
8.10.10 Count of Releases Before the Pickup ............................................................. 8-111
8.10.11 Count of Long Time No Reply......................................................................... 8-112
8.10.12 Count of Mobile Callee Determined Busy ....................................................... 8-113
8.10.13 Count of Answered Calls................................................................................. 8-114
8.10.14 Seizure Traffic ................................................................................................. 8-115
8.10.15 Connected Traffic............................................................................................ 8-116
8.10.16 Answered Traffic ............................................................................................. 8-117
8.10.18 Answer Rate.................................................................................................... 8-118
8.11 UE-Terminated Traffic ................................................................................................. 8-119
8.11.1 Overview of MS_OFFICE_3G_TRM_TRAF ..................................................... 8-119
8.11.6 Count of Mobile Callee Trunk Resource Overflow............................................ 8-123
xxvii
8.11.14 Seizure Traffic ................................................................................................. 8-131
8.11.18 Answer Rate.................................................................................................... 8-134
8.12 Outgoing Traffic ........................................................................................................... 8-135
8.12.1 Overview of MS_OFFICE_OUT_TRAF ............................................................ 8-135
8.12.3 Count of Seizure ............................................................................................... 8-136
8.12.6 Count of Not Answered Calls ............................................................................ 8-139
8.12.8 Count of Call Failures Due to Overload ............................................................ 8-141
8.12.9 Count of Call Failures Due to Network Management........................................ 8-143
8.12.10 Count of Outgoing Trunk Overflow ................................................................. 8-145
8.12.12 Count of Callee Busy in Toll Calls................................................................... 8-147
8.12.13 Count of Callee Busy in Local Calls................................................................ 8-148
8.12.14 Seizure Traffic ................................................................................................. 8-148
8.12.18 Answer Rate.................................................................................................... 8-151
8.12.19 Count of Call Attempts .................................................................................... 8-151
8.12.20 Count of Failed Call Attempts Due to Common Resource Application Failure8-152
8.12.21 Count of Failed Call Attempts Due to Peer Office Congestion ....................... 8-153
8.12.23 Count of Incomplete Addresses Received...................................................... 8-155
8.13 Connection Type.......................................................................................................... 8-158
8.13.1 Overview of MS_OFFICE_CALLNATURE_TRAF ............................................ 8-158
8.13.5 Count of Barred Calls Due to Caller Service Restriction .................................. 8-161
xxviii

8.13.7 Count of Outgoing Trunk Overflow ................................................................... 8-162
8.13.9 Count of Releases Before the Pickup ............................................................... 8-164
8.13.11 Seizure Traffic ................................................................................................. 8-166
8.13.15 Answer Rate.................................................................................................... 8-169
8.13.16 Count of MS Unavailable ................................................................................ 8-170
8.13.17 Count of Failed Call Attempts Due to Inter-Trunk Failure............................... 8-170
8.13.18 Count of Failed Call Attempts Due to Inter-Trunk Failure............................... 8-171
8.14 Intra-Office Traffic ........................................................................................................ 8-174
8.14.1 Overview of MS_OFFICE_INT_MTM_TRAF .................................................... 8-174
8.14.7 Count of Mobile Callee Trunk Resource Overflow............................................ 8-180
8.14.10 Count of Connected Calls ............................................................................... 8-183
8.14.15 Seizure Traffic ................................................................................................. 8-188
8.14.19 Answer Rate.................................................................................................... 8-191
8.15 Call Forwarding Traffic................................................................................................. 8-192
8.15.1 Overview of MS_FORWARD_TRAF................................................................. 8-192
8.15.2 Count of Call Forwarding Attempts ................................................................... 8-192
8.15.3 Count of Forwarded Calls ................................................................................. 8-193
8.15.4 Count of Answered Forwarded Calls ................................................................ 8-194
8.15.5 Count of Call Forwarding Seizure Traffic .......................................................... 8-195
8.15.6 Count of Call Forwarding Connected Traffic..................................................... 8-196
xxix
8.15.7 Call Forwarding Answered Traffic ..................................................................... 8-197

8.16 Forwarded Subscriber Count....................................................................................... 8-198
8.16.1 Overview of MS_FORWARD_USER ................................................................ 8-198
8.16.2 Count of Subscribers Forwarded to Destination ............................................... 8-198
8.17 Failure Causes of the Office ........................................................................................ 8-202
8.17.1 Overview of MS_FAULT_REASON_TRAF....................................................... 8-202
8.17.2 Count of Supplementary Service Setting Conflict ............................................. 8-206
8.17.3 Count of Supplementary Service Setting Successes ....................................... 8-206
8.17.4 Count of Supplementary Service Setting Failures ............................................ 8-207
8.17.5 Count of Supplementary Service Deregistration Successes ............................ 8-207
8.17.6 Count of Supplementary Service Deregistration Failures................................. 8-207
8.17.7 Count of Supplementary Service Authentication Successes............................ 8-208
8.17.8 Count of Supplementary Service Authentication Failures ................................ 8-208
8.17.9 Count of Supplementary Service Application Successes ................................. 8-208
8.17.10 Count of Supplementary Service Application Failures.................................... 8-209
8.17.11 Count of Successes in Probing Malicious Calls.............................................. 8-209
8.17.12 Count of Failures in Probing Malicious Calls .................................................. 8-209
8.17.13 Count of MSC Congestions............................................................................. 8-210
8.17.14 Count of Long Time No Dialing ....................................................................... 8-210
8.17.16 Count of Temporary Failures .......................................................................... 8-211
8.17.17 Count of Self-Test Successes......................................................................... 8-211
8.17.18 Count of Long Time No Messages ................................................................. 8-211
8.17.19 Count of Long Time No Ringing...................................................................... 8-212
8.17.20 Count of Long Time No Release..................................................................... 8-212
8.17.21 Count of Inband Signals.................................................................................. 8-212
8.17.22 Count of Continuity Check Failures ................................................................ 8-213
8.17.23 Count of Exceeding Max. Call Attempts ......................................................... 8-213
8.17.24 Count of Releases Before Ringing.................................................................. 8-213
8.17.26 Count of Call Restrictions................................................................................ 8-214
8.17.27 Count of MSC Failures.................................................................................... 8-214
8.17.28 Count of Toll Calls to Busy Callee .................................................................. 8-215
8.17.29 Count of Local Calls to Busy Callee................................................................ 8-215
8.17.30 Count of Peer Office Congestion .................................................................... 8-215
8.17.31 Count of Call Failures...................................................................................... 8-216
8.17.32 Count of Contentions ...................................................................................... 8-216
8.17.33 Count of Invalid Numbers................................................................................ 8-217
8.17.34 Count of Network Management Barring.......................................................... 8-217
8.17.35 Count of CPU Congestions and Overload ...................................................... 8-217
8.17.36 Count of No CR Resources............................................................................. 8-218
8.17.37 Count of No CCB Resources .......................................................................... 8-218
xxx
8.17.38 Count of Incoming Office CF Barring .............................................................. 8-218

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

8.17.81 Count of No Route to Specified Transit Network ............................................ 8-233
8.17.82 Count of No Route to Destination ................................................................... 8-234
8.17.83 Count of Sending Private Tone ....................................................................... 8-234
8.17.84 Count of Wrongly Dialed Numbers of Toll Call Prefix ..................................... 8-235
8.17.85 Count of Unacceptable Paths ......................................................................... 8-235
8.17.86 Count of Calls Connected and Delivered on Established Route .................... 8-235
8.17.87 Count of Calls Barred by Operators ................................................................ 8-236
8.17.88 Count of Circuits Reserved for Reusing.......................................................... 8-236
8.17.89 Count of Normally cleared Calls...................................................................... 8-236
8.17.91 Count of No Reply........................................................................................... 8-237
8.17.92 Count of No Response.................................................................................... 8-237
8.17.93 Count of Callee Absent ................................................................................... 8-238
8.17.94 Count of Calls Rejected .................................................................................. 8-238
8.17.95 Count of Number Changed ............................................................................. 8-238
8.17.96 Count of No Idle Circuits ................................................................................. 8-239
8.17.97 Count of RAB Pre-Empted .............................................................................. 8-239
8.17.98 Count of Callee Failures.................................................................................. 8-239
8.17.99 Count of Invalid Number Formats ................................................................... 8-240
8.17.100 Count of Facilities Rejected .......................................................................... 8-240
8.17.101 Count of Responses to STATUS ENQUIRY................................................. 8-240
8.17.102 Count of Normally cleared Calls.................................................................... 8-241
8.17.103 Count of Unavailable Circuits........................................................................ 8-241
8.17.104 Count of Network Failures............................................................................. 8-241
8.17.105 Count of Contemporary Failures ................................................................... 8-242
8.17.106 Count of MSC Failures.................................................................................. 8-242
8.17.107 Count of Accessed Messages Discarded ..................................................... 8-242
8.17.108 Count of Unavailable Routes ........................................................................ 8-243
8.17.109 Count of Unavailable Paths........................................................................... 8-243
8.17.110 Count of Unavailable Resources .................................................................. 8-244
8.17.111 Count of No Suitable Service Quality............................................................ 8-244
8.17.112 Counts of Facility Applied Not Preserved Before.......................................... 8-244
8.17.113 Count of CUG Outgoing Call Restriction....................................................... 8-245
8.17.114 Count of CUG Incoming Call Restriction....................................................... 8-245
8.17.115 Count of Bearer Capability Authorized.......................................................... 8-245
8.17.116 Count of No Available Bearer Capability....................................................... 8-246
8.17.117 Count of No Suitable Service or Optional Project......................................... 8-246
8.17.118 Count of Bearer Capability Not Implemented ............................................... 8-246
8.17.119 Count of Path Type Not Implemented........................................................... 8-247
8.17.120 Count of AOC Service Request Failures ...................................................... 8-247
8.17.121 Count of ACM Equaling or Greater Than ACM max ..................................... 8-247
xxxii
8.17.122 Count of Requested Equipment Not Implemented ....................................... 8-248

8.17.123 Count of Restricted Bearer Capability........................................................... 8-248
8.17.124 Count of IWF Resource Unavailable............................................................. 8-248
8.17.125 Count of Service or Optional Project Not Implemented ................................ 8-249
8.17.126 Count of Invalid Call Reference Values ........................................................ 8-249
8.17.127 Count of Identified Route Not Exist............................................................... 8-249
8.17.128 Count of Callee not CUG Subscriber ............................................................ 8-250
8.17.129 Count of Incompatible Terminals .................................................................. 8-250
8.17.130 Count of CUG Not Exist ................................................................................ 8-250
8.17.131 Count of Invalid Transit Network Selection ................................................... 8-251
8.17.132 Count of Invalid Messages............................................................................ 8-251
8.17.133 Count of Non-Existent or Not Implemented Message Types........................ 8-251
8.17.134 Count of Non-Existent or Not Implemented Message Units ......................... 8-252
8.17.135 Count of Timeout Recoveries........................................................................ 8-252
8.17.136 Count of Non-Existent or Not Implemented Parameters .............................. 8-252
8.17.137 Count of Messages Carrying Unidentified Parameters................................. 8-253
8.17.138 Count of Protocol errors ................................................................................ 8-253
8.17.139 Count of Interworking .................................................................................... 8-253
8.18 Incoming Traffic ........................................................................................................... 8-254
8.18.1 Overview of MS_OFFICE_INC_TRAF.............................................................. 8-254
8.18.2 Count of Seizure ............................................................................................... 8-254
8.18.4 Count of Incomplete Numbers .......................................................................... 8-256
8.18.5 Count of Invalid Addresses ............................................................................... 8-258
8.18.6 Count of Failed Calls Due to Internal Failure .................................................... 8-260
8.18.7 Count of Call Failures Due to Overload ............................................................ 8-262
8.18.8 Count of Call Failures Due to Network Management........................................ 8-263
8.18.9 Seizure Traffic ................................................................................................... 8-265
8.18.11 Count of Circuits in Maintenance .................................................................... 8-266
8.18.12 Answer Rate.................................................................................................... 8-266
8.18.13 Count of Connected Calls ............................................................................... 8-267
8.18.16 Count of Callee Power-Off .............................................................................. 8-269
8.19 Source TMG Destination Route Traffic........................................................................ 8-270
8.19.1 Overview of MS_MGWID_ROUTE_TRAF........................................................ 8-270
8.19.3 Count of Seizure ............................................................................................... 8-272
8.19.4 Count of Ringings Received.............................................................................. 8-273
xxxiii
8.19.7 Answer Rate...................................................................................................... 8-275

8.19.8 Seizure Traffic ................................................................................................... 8-276
8.19.9 Connected Traffic.............................................................................................. 8-277
8.19.11 Count of Outgoing Trunk Overflow ................................................................. 8-278
8.19.12 Count of Releases Before Ringing.................................................................. 8-279
8.19.14 Count of Callee No Reply................................................................................ 8-281
8.19.17 Count of Invalid Addresses ............................................................................. 8-284
8.19.18 Count of Paging No Reply............................................................................... 8-285
8.19.19 Count of Subscriber Absence ......................................................................... 8-286
8.19.20 Count of Subscriber Service Restricted .......................................................... 8-287
8.19.21 Count of Special Tones................................................................................... 8-288
8.19.22 Count of Peer Office Congestions .................................................................. 8-289
8.19.23 Count of Interworking Failures ........................................................................ 8-290
8.19.24 Count of Other Failures................................................................................... 8-291
8.19.25 Count of Re-Routing ....................................................................................... 8-291
8.19.26 Count of Re-Routing Failures.......................................................................... 8-293
8.19.27 Count of UMG Failures ................................................................................... 8-294
8.19.28 Count of Circuit All Busy ................................................................................. 8-295
8.20 Transit Traffic ............................................................................................................... 8-297
8.20.1 Overview of MS_OFFICE_TRN_TRAF............................................................. 8-297
8.20.2 Count of Outgoing Trunk Seizure Attempts ...................................................... 8-297
8.20.3 Count of Outgoing Trunk Seizure...................................................................... 8-298
8.20.7 Count of Outgoing Trunk Overflow ................................................................... 8-302
8.20.9 Seizure Traffic ................................................................................................... 8-304
8.20.13 Answer Rate.................................................................................................... 8-307
8.20.15 Count of Wrongly Dialed Numbers.................................................................. 8-308
8.20.16 Count of Failed Call Attempts Due to Common Resource Application Failures8-309
8.20.17 Count of Peer Office Congestions .................................................................. 8-310
xxxiv
Chapter 9 Global Components..................................................................................................... 9-1

9.2 CPU Seizure Rate.............................................................................................................. 9-1
9.2.1 Overview of MS-CPU-OCCUP-TRAF ..................................................................... 9-1
9.2.2 Average Seizure Rate ............................................................................................. 9-2
9.2.3 Count of Congestion ............................................................................................... 9-2
9.2.4 Congestion Duration ............................................................................................... 9-2
9.2.5 Count of Overload ................................................................................................... 9-3
9.2.6 Overload Duration ................................................................................................... 9-3
9.2.7 Count of Originating and Incoming Calls ................................................................ 9-3
9.2.8 Count of Incoming and Outgoing Calls ................................................................... 9-4
9.2.9 Peak Seizure Rate .................................................................................................. 9-4
9.2.10 Peak Seizure Time................................................................................................ 9-4
9.2.11 Peak Seizure Duration .......................................................................................... 9-5
9.3 Count of VLR Subscribers ................................................................................................. 9-5
9.3.1 Overview of MS-VDB-MSG-SUB-STAT.................................................................. 9-5
9.3.2 VLR Local Subscribers............................................................................................ 9-7
9.3.3 VLR Roaming Subscribers...................................................................................... 9-9
9.3.4 Subscribers with CLIP........................................................................................... 9-12
9.3.5 Subscribers with CLIR........................................................................................... 9-16
9.3.6 Subscribers with COLP ......................................................................................... 9-19
9.3.7 Subscribers with COLR......................................................................................... 9-22
9.3.8 Subscribers with CFU ........................................................................................... 9-26
9.3.9 Subscribers with CFB............................................................................................ 9-29
9.3.10 Subscribers with CFNRy ..................................................................................... 9-33
9.3.11 Subscribers with CFNRc ..................................................................................... 9-36
9.3.12 Subscribers with Call Waiting.............................................................................. 9-39
9.3.13 Subscribers with Call Hold .................................................................................. 9-43
9.3.14 Subscribers with Three-Party Service................................................................. 9-46
9.3.15 Subscribers with CUG......................................................................................... 9-49
9.3.16 Subscribers with AoCI......................................................................................... 9-53
9.3.17 Subscribers with AoCC ....................................................................................... 9-53
9.3.18 Subscribers with BAOC....................................................................................... 9-56
9.3.19 Subscribers with BOIC ........................................................................................ 9-59
9.3.20 Subscribers with BOIC Except Home Country.................................................... 9-62
9.3.21 Subscriber with ODB........................................................................................... 9-65
9.3.22 Subscribers with ODB BAOC.............................................................................. 9-68
9.3.23 Subscribers with ODB BOIC ............................................................................... 9-71
9.3.24 Subscribers with ODB BOIC Except Home Country........................................... 9-74
9.3.25 Subscribers with IMSI Detached ......................................................................... 9-77
9.3.26 IN Subscribers..................................................................................................... 9-80
9.3.27 GPRS Subscribers .............................................................................................. 9-83
xxxv
9.3.28 Local Network Subscribers ................................................................................. 9-87

9.3.29 Other Network Subscribers ................................................................................. 9-89
9.3.30 Subscribers with Data Service ............................................................................ 9-91
9.3.31 Subscribers with Hot Billing................................................................................. 9-94
9.3.32 Subscribers with LCS.......................................................................................... 9-97
9.3.33 Subscribers with PPS Triggered by Number Segment..................................... 9-100
9.3.34 MO CAMEL Subscribers ................................................................................... 9-103
9.3.35 CAMEL Subscribers with Dialing Service ......................................................... 9-106
9.3.36 MT CAMEL Subscribers in VMSC .................................................................... 9-109
9.3.37 CAMEL Subscribers Invoked by Supplementary Service................................. 9-112
9.3.38 SMS CAMEL Subscribers ................................................................................. 9-115
9.3.39 CAMEL Subscribers with Mobile Management................................................. 9-118
9.3.40 ALS Subscribers ............................................................................................... 9-121
9.3.41 Subscribers with VP Dual Number.................................................................... 9-124
9.4 Location Area Traffic Distribution................................................................................... 9-127
9.4.1 Overview of MS_LAI_STAT ................................................................................ 9-127
9.4.2 Count of Local Subscribers ................................................................................. 9-128
9.4.3 Count of Roaming Subscribers ........................................................................... 9-130
9.4.4 Count of Switch-off Subscribers.......................................................................... 9-133
9.4.5 Count of Requesting Location Update ................................................................ 9-136
9.4.6 Count of Failed Location Update due to Roaming Restriction............................ 9-137
9.4.7 Count of Rejected Location Update .................................................................... 9-138
9.4.8 Count of IMSI Attach ........................................................................................... 9-139
9.4.9 Count of IMSI Detach.......................................................................................... 9-140
9.4.10 Count of MO Call Attempts ............................................................................... 9-141
9.4.11 Count of MO Subscriber Release Before Connection ...................................... 9-142
9.4.12 Count of MO Subscriber Release Before Pickup.............................................. 9-142
9.4.13 MO Call_Count of Absent Callee ...................................................................... 9-143
9.4.14 MO Call_Count of Busy Callee ......................................................................... 9-143
9.4.15 MO Call_Count of Call Completion ................................................................... 9-144
9.4.16 MO Call_Count of Call Answer ......................................................................... 9-144
9.4.17 MO Call_Traffic of Call Completion................................................................... 9-144
9.4.18 MO Call_Traffic of Call Answer ......................................................................... 9-145
9.4.19 Count of Paging ................................................................................................ 9-145
9.4.20 Count of Paging Response ............................................................................... 9-146
9.4.21 MT Call_Count of Release Before Ringing ....................................................... 9-147
9.4.22 MT Call_Count of Release During Ringing ....................................................... 9-147
9.4.23 MT Call_Count of Call Completion.................................................................... 9-148
9.4.24 MT Call_Count of Call Answer .......................................................................... 9-148
9.4.25 MT Call_Traffic of Call Completion ................................................................... 9-148
9.4.26 MT Call_Traffic of Call Answer.......................................................................... 9-149
9.4.27 Count of Move-out of Location Area ................................................................. 9-149
xxxvi
9.4.28 Count of Successful Move-out of Location Area............................................... 9-150

9.4.29 Count of Move-in to Location Area ................................................................... 9-150
9.4.30 Count of Successful Move-in to Location Area ................................................. 9-151
9.4.31 Count of Call Drop by Mobile Caller.................................................................. 9-152
9.4.32 Count of Call Drop by Mobile Callee................................................................. 9-153
9.5 Cell Traffic Distribution................................................................................................... 9-154
9.5.1 Overview of MS_GCI_STAT ............................................................................... 9-154
9.5.2 Count of Local Subscribers ................................................................................. 9-155
9.5.3 Count of Roaming Subscribers ........................................................................... 9-157
9.5.4 Count of Switch-off Subscribers.......................................................................... 9-160
9.5.5 Count of Requesting Location Update ................................................................ 9-163
9.5.6 Count of Rejected Location Update .................................................................... 9-164
9.5.7 Count of IMSI Attach ........................................................................................... 9-165
9.5.8 Count of IMSI Detach.......................................................................................... 9-166
9.5.9 Count of MO Call Attempts ................................................................................. 9-167
9.5.10 Count of MO Subscriber Release Before Connection ...................................... 9-168
9.5.11 Count of MO Subscriber Release Before Pickup.............................................. 9-168
9.5.12 MO Call_Count of Absent Callee ...................................................................... 9-169
9.5.13 MO Call_Count of Busy Callee ......................................................................... 9-169
9.5.14 MO Call_Count of Call Completion ................................................................... 9-170
9.5.15 MO Call_Count of Call Answer ......................................................................... 9-170
9.5.16 MO Call_Traffic of Call Completion................................................................... 9-170
9.5.17 MO Call_Traffic of Call Answer ......................................................................... 9-171
9.5.18 MT Call_Count of Release Before Ringing ....................................................... 9-171
9.5.19 MT Call_Count of Release During Ringing ....................................................... 9-171
9.5.20 MT Call_Count of Call Completion.................................................................... 9-172
9.5.21 MT Call_Count of Call Answer .......................................................................... 9-172
9.5.22 MT Call_Traffic of Call Completion ................................................................... 9-173
9.5.23 MT Call_Traffic of Call Answer.......................................................................... 9-173
9.5.24 Count of Move-out of Cell ................................................................................. 9-173
9.5.25 Count of Successful Move-out of Cell............................................................... 9-174
9.5.26 Count of Move-in to Cell.................................................................................... 9-175
9.5.27 Count of Successful Move-in to Cell ................................................................. 9-175
9.5.28 Count of Call Drop by Mobile Caller.................................................................. 9-176
9.5.29 Count of Call Drop by Mobile Callee................................................................. 9-177
9.6 Count of MVNO Subscribers ......................................................................................... 9-177
9.6.1 Overview of MS_VDB_MVNO_SUB ................................................................... 9-177
9.6.2 Count of MVNO Subscribers............................................................................... 9-178
Chapter 10 Signaling and Interfaces ......................................................................................... 10-1

10.1 Overview of Measurement Set ...................................................................................... 10-1
10.2 A-Interface Signaling Procedure Error........................................................................... 10-3
10.2.1 Overview of MS_TYPE_A_PROTOCOL_ERR ................................................... 10-3
xxxvii
10.2.2 Count of Received Messages with Cause of Radio Interface Message Failure. 10-4
10.2.3 Count of Sent Messages with Cause of Radio Interface Message Failure ........ 10-4
10.2.4 Count of Received Messages with Cause of Radio Interface Failure................. 10-5
10.2.5 Count of Sent Messages with Cause of Radio Interface Failure ........................ 10-6
10.2.6 Count of Received Messages with Cause of Invalid Message Content ............. 10-7
10.2.7 Count of Sent Messages with Cause of Invalid Message Content ..................... 10-8
10.2.8 Count of Received Messages with Cause of Information Element or Field Missing10-9
10.2.9 Count of Sent Messages with Cause of Information Element or Field Missing 10-10
10.2.10 Count of Received Messages with Cause of Incorrect Value......................... 10-10
10.2.11 Count of Sent Messages with Cause of Incorrect Value ................................ 10-11
10.2.12 Count of Received Messages with Cause of Unknown Message Type ......... 10-12
10.2.13 Count of Sent Messages with Cause of Unknown Message Type ................. 10-12
10.2.14 Count of Received Messages with Cause of Unknown Information Element. 10-13
10.2.15 Count of Sent Messages with Cause of Unknown Information Element ........ 10-14
10.2.16 Count of Received Messages with Cause of Protocol Error........................... 10-14
10.2.17 Count of Sent Messages with Cause of Protocol Error .................................. 10-15
10.2.18 Count of Received Messages with Cause of Terrestrial Circuit Already Allocated10-16
10.2.19 Count of Sent Messages with Cause of Terrestrial Circuit Already Allocated 10-16
10.3 BICC SCTP Link .......................................................................................................... 10-17
10.3.1 Overview of MS_BICCMSG .............................................................................. 10-17
10.3.2 Count of Link Disconnections............................................................................ 10-18
10.3.3 Duration of Link Disconnections........................................................................ 10-18
10.3.4 Count of Link Congestion.................................................................................. 10-18
10.3.5 Duration of Link Congestion.............................................................................. 10-19
10.3.6 Count of Messages Sent................................................................................... 10-19
10.3.7 Count of Bytes in Messages Sent ..................................................................... 10-19
10.3.8 Count of Messages Received ........................................................................... 10-20
10.3.9 Count of Bytes in Messages Received ............................................................. 10-20
10.3.10 Count of Messages Sent per Second ............................................................. 10-20
10.3.11 Count of Messages Received per Second...................................................... 10-21
10.3.12 Count of Bits Sent per Second........................................................................ 10-21
10.3.13 Count of Bits Received per Second ................................................................ 10-21
10.4 BICC Node Capability.................................................................................................. 10-22
10.4.1 Overview of MS_BICC_NODE_CAPABILITY................................................... 10-22
10.4.2 Count of Incoming Call Attempts....................................................................... 10-22
10.4.3 Count of Call Failures Due to Switching Equipment Congestion...................... 10-23
10.4.4 Count of Call Failures Due to No Valid Circuit .................................................. 10-24
10.4.5 Count of Call Failures Due to Address Incomplete ........................................... 10-25
10.4.6 Count of Call Failures Due to Temporary Failure ............................................. 10-26
10.4.7 Count of Call Failures Due to Unallocated Number .......................................... 10-27
10.4.8 Count of Call Failures Due to Callee Busy........................................................ 10-28
10.4.9 Count of Call Failures Due to Destination Fault................................................ 10-29
xxxviii
10.4.10 Count of Call Failures Due to Other Causes................................................... 10-30

10.5 Base Station Controller................................................................................................ 10-31
10.5.1 Overview of MS_TYPE_BSC ............................................................................ 10-31
10.5.2 Count of Reset Messages from BSC ................................................................ 10-32
10.5.3 Count of Circuit Reset Messages from MSC .................................................... 10-32
10.5.4 Count of Circuit Reset Messages from BSC..................................................... 10-33
10.5.5 Count of Circuit Blocking Messages from BSC................................................. 10-33
10.5.6 Count of Circuit Unblocking Messages from BSC ............................................ 10-34
10.5.7 Count of Circuit Group Blocking Messages from BSC ..................................... 10-35
10.5.8 Count of Circuit Group Unblocking Messages from BSC ................................. 10-36
10.5.9 Count of Overload Messages from BSC........................................................... 10-36
10.5.10 Count of Unequipped Circuit Messages from MSC ........................................ 10-37
10.5.11 Count of Unequipped Circuit Messages from BSC......................................... 10-37
10.5.12 Count of SAPI “N” Rejection Messages.......................................................... 10-38
10.5.13 Count of Confusion Messages from BSC ....................................................... 10-39
10.5.14 Count of Confusion Messages from MSC....................................................... 10-39
10.6 GPRS Timeout............................................................................................................. 10-40
10.6.1 Overview of MS_TYPE_GPRS_TIMEOUT....................................................... 10-40
10.6.2 Count of Timeouts for Non-GPRS Service Indications ..................................... 10-40
10.6.3 Count of Timeouts for Getting Subscriber Information...................................... 10-41
10.7 Gs-Interface Operation ................................................................................................ 10-42
10.7.1 Overview of MS_TYPE_GS_OPER .................................................................. 10-42
10.7.2 Count of Paging Messages on Gs-Interface ..................................................... 10-43
10.7.3 Count of Paging Rejection Messages on Gs-Interface ..................................... 10-44
10.7.4 Count of MS Unreachable Messages from SGSN............................................ 10-45
10.7.5 Count of Messages of Location Update Request ............................................. 10-46
10.7.6 Count of Messages of Location Update Acceptance ........................................ 10-47
10.7.7 Count of Messages of Location Update Rejection............................................ 10-48
10.7.8 Count of Messages of TMSI Reallocation......................................................... 10-49
10.7.9 Count of Messages of Non-GPRS Indication Request ..................................... 10-50
10.7.10 Count of Messages of Non-GPRS Indication Rejection ................................. 10-51
10.7.11 Count of Messages of Non-GPRS Indication Acknowledgement ................... 10-52
10.7.12 Count of Messages of MS Activity Indication.................................................. 10-53
10.7.13 Count of Messages of GPRS Detachment Indication ..................................... 10-54
10.7.14 Count of Messages of GPRS Detachment Acknowledgement....................... 10-55
10.7.15 Count of Messages of IMSI Detachment Indication........................................ 10-56
10.7.16 Count of Messages of IMSI Detachment Acknowledgement.......................... 10-57
10.7.17 Count of Messages of VLR Reset Indication .................................................. 10-58
10.7.18 Count of Messages of VLR Reset Acknowledgement .................................... 10-59
10.7.19 Count of Messages of SGSN Reset Indication ............................................... 10-60
10.7.20 Count of Messages of SGSN Reset Acknowledgement................................. 10-61
10.7.21 Count of Messages of MS Information Request ............................................. 10-62
xxxix
10.7.22 Count of Messages of MS Information Response .......................................... 10-63

10.7.23 Count of Messages of Mobile Management Information Request.................. 10-64
10.7.24 Count of MS Status Abnormal Messages Received ....................................... 10-65
10.7.25 Count of MS Status Abnormal Messages Sent............................................... 10-66
10.8 Gs-Interface Error Cause............................................................................................. 10-67
10.8.1 Overview of MS_TYPE_GS_ERR..................................................................... 10-67
10.8.2 Count of Messages with Cause of IMSI Detached for GPRS Service.............. 10-68
10.8.3 Count of Messages with Cause of IMSI Detached for GPRS and Non-GPRS
Services........................................................................................................................ 10-69
10.8.4 Count of Messages with Cause of IMSI Unknown............................................ 10-69
10.8.5 Count of Messages with Cause of IMSI Explicitly Detached for Non-GPRS Services
...................................................................................................................................... 10-70
10.8.6 Count of Messages with Cause of IMSI Implicitly Detached for Non-GPRS Services
...................................................................................................................................... 10-71
10.8.7 Count of Messages with Cause of MS Unreachable ........................................ 10-72
10.8.8 Count of Messages with Cause of Message Not Compatible with Protocol State10-73
10.8.9 Count of Messages with Cause of Missing Mandatory Information Element ... 10-74
10.8.10 Count of Messages with Cause of Invalid Mandatory Information.................. 10-75
10.8.11 Count of Messages with Cause of Conditional IE Error.................................. 10-76
10.8.12 Count of Messages with Cause of Semantically Incorrect Message .............. 10-77
10.8.13 Count of Messages with Cause of Message Unknown .................................. 10-78
10.8.14 Count of Messages with Cause of Address Error ........................................... 10-79
10.9 H.248 MGW ................................................................................................................. 10-80
10.9.1 Overview of MS_H.248_MGW_TRAFIC........................................................... 10-80
10.9.2 Count of Unavailable States.............................................................................. 10-81
10.9.3 Duration of Unavailable State ........................................................................... 10-81
10.9.4 Count of Messages Sent................................................................................... 10-82
10.9.5 Count of Bytes in Messages Sent ..................................................................... 10-82
10.9.6 Count of Messages Received ........................................................................... 10-82
10.9.7 Count of Bytes in Messages Received ............................................................. 10-83
10.9.8 Count of Messages Unsuccessfully Sent.......................................................... 10-83
10.9.9 Count of Messages Unsuccessfully Received .................................................. 10-83
10.9.10 Count of Binary Encoded Messages............................................................... 10-84
10.9.11 Count of Binary Decoded Messages .............................................................. 10-84
10.9.12 Count of Text Encoded Messages.................................................................. 10-84
10.9.13 Count of Text Decoded Messages.................................................................. 10-85
10.9.14 Count of Messages Failed in Security Information Application....................... 10-85
10.9.15 Count of Messages Failed in Security Information Verification ...................... 10-85
10.9.16 Count of Messages Failed in Encoding .......................................................... 10-86
10.9.17 Count of Messages with Error in Decoding..................................................... 10-86
10.9.18 Count of Messages Sent per Second ............................................................. 10-86
10.9.19 Count of Messages Received per Second...................................................... 10-87
xl
10.9.20 Count of Bits Sent per Second........................................................................ 10-87

10.9.21 Count of Bits Received per Second ................................................................ 10-87
10.10 H.248 SCTP Link ....................................................................................................... 10-88
10.10.1 Overview of MS_H.248_SCTPLNK_TRAFIC ................................................. 10-88
10.10.2 Count of Unavailable States............................................................................ 10-88
10.10.3 Duration of Unavailable State ......................................................................... 10-88
10.10.4 Count of Link Congestion................................................................................ 10-89
10.10.5 Duration of Link Congestion............................................................................ 10-89
10.10.6 Count of Messages Sent................................................................................. 10-89
10.10.7 Count of Bytes in Messages Sent................................................................... 10-90
10.10.8 Count of Messages Received ......................................................................... 10-90
10.10.9 Count of Bytes in Messages Received ........................................................... 10-91
10.10.10 Count of Messages Sent per Second ........................................................... 10-91
10.10.11 Count of Messages Received per Second.................................................... 10-91
10.10.12 Count of Bits Sent per Second...................................................................... 10-92
10.10.13 Count of Bits Received per Second .............................................................. 10-92
10.11 IP Port Traffic ............................................................................................................. 10-92
10.11.1 Overview of MS_IFM_IPFLOW_TRAF ........................................................... 10-92
10.11.2 Count of Packets Sent .................................................................................... 10-93
10.11.3 Count of Packets Received............................................................................. 10-93
10.11.4 Count of Bytes Sent ........................................................................................ 10-94
10.11.5 Count of Bytes Received................................................................................. 10-94
10.11.6 Speed of Sending Packet................................................................................ 10-94
10.11.7 Speed of Receiving Packet ............................................................................. 10-95
10.11.8 Bit Rate of Sending Packet ............................................................................. 10-95
10.11.9 Bit Rate of Receiving Packet........................................................................... 10-95
10.11.10 Bandwidth Utilization of IP Port When Sending Packet................................ 10-96
10.11.11 Bandwidth Utilization of IP Port When Receiving Packet ............................. 10-96
10.11.12 Count of Discarded Packets Received ......................................................... 10-96
10.11.13 Count of Packets with Invalid IP Address ..................................................... 10-97
10.11.14 Count of Rejected Packets for Access.......................................................... 10-97
10.11.15 Count of Restricted ICMP Packets ............................................................... 10-97
10.11.16 Count of Unknown IP Packets ...................................................................... 10-98
10.11.17 Count of Packets That IFM Fails to Transfer ................................................ 10-98
10.11.18 Count of Packets That IFM Fails to Send ..................................................... 10-98
10.12 ISUP Circuit Group .................................................................................................... 10-99
10.12.1 Overview of MS_ISUP_TKGRP_PERFORM_TRAF ...................................... 10-99
10.12.2 Count of Incoming Call Attempts................................................................... 10-100
10.12.3 Count of REL Messages Sent with Cause of Switching Equipment Congestion10-101
10.12.4 Count of Messages of Circuit Group Congestion.......................................... 10-103
10.12.5 Count of Congestion ..................................................................................... 10-105
10.12.6 Count of REL Messages Sent with Cause of Address Incomplete............... 10-105
xli
10.12.7 Count of REL Messages Sent with Cause of Temporary Failure ................. 10-107
10.12.8 Count of REL Messages Sent with Cause of Unallocated Number.............. 10-108
10.12.9 Count of REL Messages Sent with Cause of Subscriber Busy .................... 10-110
10.12.10 Count of REL Messages Sent with Cause of Destination Fault.................. 10-111
10.12.11 Count of REL Messages Sent with Other Causes ...................................... 10-113
10.12.12 Count of Outgoing Call Attempts ................................................................ 10-114
10.12.13 Count of REL Messages Received with Cause of Switching Equipment
Congestion ................................................................................................................. 10-115
10.12.14 Count of REL Messages Received with Cause of No Valid Circuit ............ 10-117
10.12.15 Count of REL Messages Received with Cause of Address Incomplete ..... 10-118
10.12.16 Count of REL Messages Received with Cause of Temporary Failure........ 10-120
10.12.17 Count of REL Messages Received with Cause of Unallocated Number .... 10-121
10.12.18 Count of REL Messages Received with Cause of No Route to Destination10-123
10.12.19 Count of REL Messages Received with Cause of Subscriber Busy........... 10-124
10.12.20 Count of REL Messages Received with Cause of Destination Fault .......... 10-126
10.12.21 Count of REL Messages Received with Other Causes .............................. 10-127
10.12.22 Count of Answers Without Charging........................................................... 10-129
10.12.23 Count of Maintenance-Oriented CGB Messages........................................ 10-131
10.12.24 Count of Hardware-Oriented CGB Messages............................................. 10-131
10.12.25 Count of Circuit Group Reset Messages .................................................... 10-132
10.12.26 Count of Circuit Reset Messages ............................................................... 10-133
10.12.27 Count of Answers........................................................................................ 10-134
10.12.28 Count of Messages Received ..................................................................... 10-136
10.12.29 Count of Messages Sent............................................................................. 10-136
10.12.30 Count of Messages Both Received and Sent ............................................. 10-137
10.12.31 Length of Messages Received.................................................................... 10-138
10.12.32 Length of Messages Sent ........................................................................... 10-138
10.12.33 Length of Messages Both Received and Sent............................................ 10-139
10.12.34 Count of Calls.............................................................................................. 10-139
10.12.35 Length of Messages per Call ...................................................................... 10-140
10.12.36 Average Message Length ........................................................................... 10-140
10.13 ISUP Node ............................................................................................................... 10-141
10.13.1 Overview of MS_ISUP_NODE_PERFORM_TRAF ...................................... 10-141
10.13.3 Count of REL Messages Sent with Cause of Switching Equipment Congestion10-142
10.13.4 Count of REL Messages Sent with Cause of No Valid Circuit...................... 10-144
10.13.5 Count of REL Messages Sent with Cause of Address Incomplete............... 10-146
10.13.6 Count of REL Messages Sent with Cause of Temporary Failure ................. 10-147
10.13.7 Count of REL Messages Sent with Cause of Unallocated Number.............. 10-149
10.13.8 Count of REL Messages Sent with Cause of Subscriber Busy .................... 10-150
10.13.9 Count of REL Messages Sent with Cause of Destination Fault.................... 10-152
10.13.10 Count of REL Messages Sent with Other Causes ...................................... 10-153
xlii
10.14 ISUP Network .......................................................................................................... 10-155

10.14.1 Overview of MS_ISUP_NET_PERFORM_TRAF.......................................... 10-155
10.14.2 Count of Outgoing Call Attempts .................................................................. 10-156
10.14.3 Count of REL Messages Received with Cause of Switching Equipment
Congestion ................................................................................................................. 10-156
10.14.4 Count of REL Messages Received with Cause of No Valid Circuit .............. 10-158
10.14.5 Count of REL Messages Received with Cause of Address Incomplete ....... 10-160
10.14.6 Count of REL Messages Received with Cause of Temporary Failure.......... 10-161
10.14.7 Count of REL Messages Received with Cause of Unallocated Number ...... 10-163
10.14.8 Count of REL Messages Received with Cause of No Route to Destination. 10-164
10.14.9 Count of REL Messages Received with Cause of Subscriber Busy............. 10-166
10.14.10 Count of REL Messages Received with Cause of Destination Fault .......... 10-167
10.14.11 Count of REL Messages Received with Other Causes .............................. 10-169
10.15 ISUP Message Usage ............................................................................................. 10-170
10.15.1 Overview of MS_ISUP_MSG_USING_TRAF ............................................... 10-170
10.15.2 Count of Certain Messages Sent .................................................................. 10-170
10.15.3 Count of Certain Messages Received .......................................................... 10-171
10.16 Count of ISUP Messages ........................................................................................ 10-172
10.16.1 Overview of MS_ISUP_TOTAL_MSU_TRAF ............................................... 10-172
10.16.2 Count of Messages Sent............................................................................... 10-172
10.16.3 Count of Messages Received ....................................................................... 10-173
10.17 ISUP Abnormality .................................................................................................... 10-174
10.17.1 Overview of MS_ISUP_UNUSUAL_TRAF.................................................... 10-174
10.17.2 Count of Responses to RSC Not Received by T17 ...................................... 10-175
10.17.3 Count of GRAs Not Received by T23 ........................................................... 10-176
10.17.4 Count of RLCs Not Received by T5.............................................................. 10-177
10.17.5 Count of Circuit Remote Blocking Messages................................................ 10-177
10.17.6 Count of Failures to Assign CGBA on Some Circuits ................................... 10-178
10.17.7 Count of Failures to Assign CGUA on Some Circuits ................................... 10-179
10.17.8 Count of Assignments of Too Many CGBAs on Some Circuits .................... 10-179
10.17.9 Count of Assignments of Too Many CGUAs on Some Circuits .................... 10-180
10.17.10 Count of Unexpected CGBAs Received ..................................................... 10-181
10.17.11 Count of Unexpected CGUAs Received ..................................................... 10-181
10.17.12 Count of Unexpected BLAs Received......................................................... 10-182
10.17.13 Count of Unexpected UBAs Received ........................................................ 10-183
10.17.14 Count of BLAs Not Received by T13 .......................................................... 10-183
10.17.15 Count of UBAs Not Received by T15.......................................................... 10-184
10.17.16 Count of CGBAs Not Received by T19....................................................... 10-185
10.17.17 Count of CGUAs Not Received by T21....................................................... 10-185
10.17.18 Count of Messages with Error Format ........................................................ 10-186
10.17.19 Count of Unexpected Messages Received................................................. 10-186
10.17.20 Count of Unknown Messages Received ..................................................... 10-187
xliii
10.18 IUA Link Set ............................................................................................................. 10-187

10.18.1 Overview of MS_IUA_LS_TRAF ................................................................... 10-187
10.18.2 Count of Unavailable States.......................................................................... 10-188
10.18.3 Duration of Unavailable State ....................................................................... 10-188
10.18.4 Count of Control Messages Sent .................................................................. 10-189
10.18.5 Count of Control Messages Received .......................................................... 10-189
10.18.6 Count of QPTM Messages Sent ................................................................... 10-190
10.18.7 Count of QPTM Messages Received............................................................ 10-191
10.18.8 Count of ERROR Messages Received ......................................................... 10-192
10.18.9 Count of Bytes in Control Messages Sent .................................................... 10-192
10.18.10 Count of Bytes in Control Messages Received........................................... 10-193
10.18.11 Count of Bytes in QPTM Messages Sent ................................................... 10-194
10.18.12 Count of Bytes in QPTM Messages Received............................................ 10-194
10.18.13 Count of Messages Sent per Second ......................................................... 10-195
10.18.14 Count of Messages Received per Second.................................................. 10-195
10.18.15 Count of Bits Sent per Second.................................................................... 10-196
10.18.16 Count of Bits Received per Second ............................................................ 10-196
10.19 IUA Signaling Link ................................................................................................... 10-196
10.19.1 Overview of MS_IUA_LINK_TRAF ............................................................... 10-196
10.19.5 Duration of Congestion ................................................................................. 10-198
10.19.8 Count of QPTM Messages Sent ................................................................... 10-200
10.19.9 Count of QPTM Messages Received............................................................ 10-201
10.19.10 Count of ERROR Messages Received ....................................................... 10-201
10.19.11 Count of Bytes in Control Messages Sent .................................................. 10-202
10.19.13 Count of Bytes in QPTM Messages Sent ................................................... 10-203
10.19.14 Count of Bytes in QPTM Messages Received............................................ 10-204
10.20 M2UA Link Set......................................................................................................... 10-206
10.20.1 Overview of MS_M2UA_LS_TRAF ............................................................... 10-206
10.20.4 Count of MAUP Messages Sent ................................................................... 10-208
10.20.5 Count of MAUP Messages Received............................................................ 10-208
xliv
10.20.6 Count of ERROR Messages Received ......................................................... 10-209

10.20.8 Count of Bytes in Control Messages Received............................................. 10-211
10.20.9 Count of Bytes in MAUP Messages Sent ..................................................... 10-211
10.20.10 Count of Bytes in MAUP Messages Received............................................ 10-212
10.21 M2UA Link ............................................................................................................... 10-214
10.21.1 Overview of MS_M2UA_LINK_TRAF ........................................................... 10-214
10.21.8 Count of MAUP Messages Sent ................................................................... 10-217
10.21.9 Count of MAUP Messages Received............................................................ 10-218
10.21.10 Count of ERROR Messages Received ....................................................... 10-218
10.21.11 Count of Bytes in Control Messages Sent .................................................. 10-219
10.21.13 Count of Bytes in MAUP Messages Sent ................................................... 10-221
10.21.14 Count of Bytes in MAUP Messages Received............................................ 10-221
10.22 M3UA Destination Entity.......................................................................................... 10-223
10.22.1 Overview of MS_M3UA_DEST_ENTITY_TRAF........................................... 10-223
10.22.2 Count of Failed Accesses ............................................................................. 10-224
10.22.3 Duration of Failed Access ............................................................................. 10-224
10.23 M3UA Signaling Link ............................................................................................... 10-224
10.23.1 Overview of MS_M3UA_LINK_TRAF ........................................................... 10-224
xlv
10.23.10 Count of Data Messages Sent .................................................................... 10-230

10.23.11 Count of Data Messages Received ............................................................ 10-230
10.23.12 Count of Bytes in Data Messages Sent ...................................................... 10-231
10.23.13 Count of Bytes in Data Messages Received............................................... 10-231
10.23.14 Count of SCCP Messages Sent.................................................................. 10-232
10.23.15 Count of SCCP Messages Received .......................................................... 10-233
10.23.16 Count of Bytes in SCCP Messages Sent.................................................... 10-233
10.23.17 Count of Bytes in SCCP Messages Received ............................................ 10-234
10.23.18 Count of TUP Messages Sent..................................................................... 10-235
10.23.19 Count of TUP Messages Received............................................................. 10-235
10.23.20 Count of Bytes in TUP Messages Sent....................................................... 10-236
10.23.21 Count of Bytes in TUP Messages Received ............................................... 10-237
10.23.22 Count of ISUP Messages Sent ................................................................... 10-237
10.23.23 Count of ISUP Messages Received............................................................ 10-238
10.23.24 Count of Bytes in ISUP Messages Sent ..................................................... 10-239
10.23.25 Count of Bytes in ISUP Messages Received.............................................. 10-239
10.23.28 Count of Bytes in Messages Sent............................................................... 10-241
10.23.29 Count of Bytes in Messages Received ....................................................... 10-242
10.24 M3UA Signaling Link Set ......................................................................................... 10-244
10.24.1 Overview of MS_M3UA_LS_TRAF ............................................................... 10-244
10.24.8 Count of Data Messages Sent ...................................................................... 10-249
10.24.9 Count of Data Messages Received .............................................................. 10-249
10.24.10 Count of Bytes in Data Messages Sent ...................................................... 10-250
10.24.11 Count of Bytes in Data Messages Received............................................... 10-251
xlvi

10.25 MAP Public Service Procedure Error ...................................................................... 10-264
10.25.1 Overview of MS_TYPE_MAP_PUBLIC_SERVICE....................................... 10-264
10.25.2 Count of Session Rejections at Local MAP (OPEN_RSP) ........................... 10-265
10.25.3 Count of Session Rejections at Remote MAP (OPEN_CNF) ....................... 10-266
10.25.4 Count of Session Aborts at Local MAP (U_ABORT_REQ) .......................... 10-267
10.25.5 Count of Session Aborts at Remote MAP (U_ABORT_IND) ........................ 10-268
10.25.6 Count of Provider Aborts (P_ABORT) .......................................................... 10-269
10.25.7 Count of Notice Indications (NOTICE) .......................................................... 10-270
10.25.8 Count of MAP_OPEN_RSP Session Rejections Due to Other Causes ....... 10-271
10.25.9 Count of MAP_OPEN_RSP Session Rejections Due to Invalid Destination
Reference................................................................................................................... 10-272
10.25.10 Count of MAP_OPEN_RSP Session Rejections Due to Invalid Origination
Reference................................................................................................................... 10-273
10.25.11 Count of MAP_OPEN_RSP Session Rejections Due to Application Context Not
Supported................................................................................................................... 10-274
10.25.12 Count of MAP_OPEN_RSP Session Rejections Due to Potential Version
Incompatibility............................................................................................................. 10-275
10.25.13 Count of MAP_OPEN_CNF Session Rejections Due to Other Causes ..... 10-276
10.25.14 Count of MAP_OPEN_CNF Session Rejections Due to Invalid Destination
Reference................................................................................................................... 10-277
10.25.15 Count of MAP_OPEN_CNF Session Rejections Due to Invalid Origination
Reference................................................................................................................... 10-278
10.25.16 Count of MAP_OPEN_CNF Session Rejections Due to Application Context Not
Supported................................................................................................................... 10-279
10.25.17 Count of MAP_OPEN_CNF Session Rejections Due to Potential Version
10.25.18 Count of MAP_U_ABORT_REQ Messages Due to Application Program Error10-281
xlvii
10.25.19 Count of MAP_U_ABORT_REQ Messages Due to Subscriber Resource Limited

.................................................................................................................................... 10-282
10.25.20 Count of MAP_U_ABORT_REQ Messages Due to Resource Unavailable 10-283
10.25.21 Count of MAP_U_ABORT_REQ Messages Due to Application Program
Cancelled ................................................................................................................... 10-284
10.25.22 Count of MAP_U_ABORT_IND Messages Due to Application Program Error10-285
10.25.23 Count of MAP_U_ABORT_IND Messages Due to Subscriber Resource Limited10-286
10.25.24 Count of MAP_U_ABORT_IND Messages Due to Resource Unavailable. 10-287
10.25.25 Count of MAP_U_ABORT_IND Messages Due to Application Program
Cancelled ................................................................................................................... 10-288
10.25.26 Count of MAP_P_ABORT_IND Messages Due to Provider Failure ........... 10-289
10.25.27 Count of MAP_P_ABORT_IND Messages Due to Supported Call Released10-290
10.25.28 Count of MAP_P_ABORT_IND Messages Due to Provider Resource Limited10-291
10.25.29 Count of MAP_P_ABORT_IND Messages Due to Maintenance................ 10-292
10.25.30 Count of MAP_P_ABORT_IND Messages Due to Potential Version
10.25.31 Count of MAP_P_ABORT_IND Messages Due to Abnormal Call.............. 10-294
10.25.32 Count of MAP_NOTICE_IND Messages Due to Abnormal Event Detected by
Remote MAP .............................................................................................................. 10-295
10.25.33 Count of MAP_NOTICE_IND Messages Due to Response Rejected by Remote
MAP............................................................................................................................ 10-296
10.25.34 Count of MAP_NOTICE_IND Messages Due to Abnormal Event Received from
Remote MAP .............................................................................................................. 10-297
10.26 MAP Operation ........................................................................................................ 10-298
10.26.1 Overview of MS_TYPE_MAP_OPERATION ................................................ 10-298
10.26.2 Count of Messages Indicating Subscriber Unknown .................................... 10-300
10.26.3 Count of Messages Indicating Base Station Unknown ................................. 10-301
10.26.4 Count of Messages Indicating MSC Unknown.............................................. 10-302
10.26.5 Count of Messages Indicating Subscriber Unidentified ................................ 10-303
10.26.6 Count of Messages Indicating SMS Subscriber Absent ............................... 10-304
10.26.7 Count of Messages Indicating Equipment Unknown .................................... 10-305
10.26.8 Count of Messages Indicating Roaming Not Allowed................................... 10-306
10.26.9 Count of Messages Indicating Subscriber Illegal .......................................... 10-307
10.26.10 Count of Messages Indicating Bearer Services Not Supported.................. 10-308
10.26.11 Count of Messages Indicating Teleservices Not Supported ....................... 10-309
10.26.12 Count of Messages Indicating Equipment Illegal ........................................ 10-310
10.26.13 Count of Messages Indicating Call Restricted ............................................ 10-311
10.26.14 Count of Messages Indicating Forwarding Violation................................... 10-312
10.26.15 Count of Messages Indicating CUG Rejection............................................ 10-313
10.26.16 Count of Messages Indicating Operation on Supplementary Services Illegal10-314
10.26.17 Count of Messages Indicating Status Error of Supplementary Services .... 10-315
10.26.18 Count of Messages Indicating Supplementary Services Unavailable......... 10-316
xlviii
10.26.19 Count of Messages Indicating Subscription Violation of Supplementary Services

.................................................................................................................................... 10-317
10.26.20 Count of Messages Indicating Supplementary Services Incompatible ....... 10-318
10.26.21 Count of Messages Indicating Function Not Supported ............................. 10-319
10.26.22 Count of Messages Indicating Target Base Station Invalid ........................ 10-320
10.26.23 Count of Messages Indicating Radio Resource Unavailable...................... 10-321
10.26.24 Count of Messages Indicating Handover Number Unavailable .................. 10-322
10.26.25 Count of Messages Indicating Subsequent Handover Failure.................... 10-323
10.26.26 Count of Messages Indicating Subscriber Absent ...................................... 10-324
10.26.27 Count of Messages Indicating Terminal Incompatible ................................ 10-325
10.26.28 Count of Messages Indicating Short Term Rejection ................................. 10-326
10.26.29 Count of Messages Indicating Long Term Rejection .................................. 10-327
10.26.30 Count of Messages Indicating MT SMS Subscriber Busy .......................... 10-328
10.26.31 Count of Messages Indicating Short Message Delivery Failure ................. 10-329
10.26.32 Count of Messages Indicating Message Waiting Queue Full ..................... 10-330
10.26.33 Count of Messages Indicating System Error............................................... 10-331
10.26.34 Count of Messages Indicating Data Loss ................................................... 10-332
10.26.35 Count of Messages Indicating Data Unexpected........................................ 10-333
10.26.36 Count of Messages Indicating Registration Failure Due to Password Invalid10-334
10.26.37 Count of Messages Indicating Password Check Failure ............................ 10-335
10.26.38 Count of Messages Indicating MSRN Unavailable ..................................... 10-336
10.26.39 Count of Messages Indicating Trace Buffer Full ......................................... 10-337
10.26.40 Count of Messages Indicating Target Cell Outside Group Call Area.......... 10-338
10.26.41 Count of Messages Indicating Password Attempt Violation ....................... 10-339
10.26.42 Count of Messages Indicating Number Changed ....................................... 10-340
10.26.43 Count of Messages Indicating Subscriber Busy ......................................... 10-341
10.26.44 Count of Messages Indicating No Answer .................................................. 10-342
10.26.45 Count of Messages Indicating Forwarding Failure...................................... 10-343
10.26.46 Count of Messages Indicating Optimized Routing Not Allowed.................. 10-344
10.26.47 Count of Messages Indicating Group Call Number Unavailable................. 10-345
10.26.48 Count of Messages Indicating Resource Limitation.................................... 10-346
10.26.49 Count of Messages Indicating Requested Network Unauthorized ............. 10-347
10.26.50 Count of Messages Indicating LCS Client Unauthorized............................ 10-348
10.26.51 Count of Messages Indicating Location Method Failure............................. 10-349
10.26.52 Count of Messages Indicating LCS Client Unknown or Unreachable......... 10-350
10.26.53 Count of Messages Indicating Mobility Management Event Not Supported10-351
10.26.54 Count of Messages Indicating Character Set Unknown ............................. 10-352
10.26.55 Count of Messages Indicating USSD Subscriber Busy .............................. 10-353
10.26.56 Count of Messages Indicating Operation Request ..................................... 10-354
10.26.57 Count of Messages Indicating Normal Response to Operation.................. 10-355
10.26.58 Count of Messages Indicating Operation Termination Not Due to Timeout 10-356
10.26.59 Count of Messages Indicating Operation Timeout...................................... 10-357
xlix
10.26.60 Duration of Operation.................................................................................. 10-358

10.27 MTP3B Signaling Link ............................................................................................. 10-359
10.27.1 Overview of MS_MTP3B_LINK_TRAF ......................................................... 10-359
10.27.2 Duration of Signaling Link in In-Service State............................................... 10-360
10.27.3 Count of Signaling Link Failures (All Causes)............................................... 10-360
10.27.4 Duration of Signaling Link Failure ................................................................. 10-360
10.27.5 Count of Local Management Inhibition Operations....................................... 10-361
10.27.6 Duration of Local Management Inhibition Operation .................................... 10-361
10.27.7 Count of Remote Management Inhibition Operations................................... 10-362
10.27.8 Duration of Remote Management Inhibition Operation ................................ 10-362
10.27.9 Count of Local Automatic Switchovers ......................................................... 10-363
10.27.12 Count of Octets of SIF and SIO Sent.......................................................... 10-364
10.27.13 Count of Octets of SIF and SIO Received .................................................. 10-365
10.27.14 Count of Signaling Link Congestion............................................................ 10-366
10.27.15 Duration of Signaling Link Congestion........................................................ 10-366
10.27.16 Percentage of Signaling Link Bandwidth Used for Sending Signaling Information
.................................................................................................................................... 10-366
10.27.17 Percentage of Signaling Link Bandwidth Used for Receiving Signaling
Information ................................................................................................................. 10-367
10.28 MTP3B Signaling Link Set ....................................................................................... 10-367
10.28.1 Overview of MS_MTP3B_LINKSET_TRAF .................................................. 10-367
10.29 MTP3B Destination Signaling Point......................................................................... 10-368
10.29.1 Overview of MS_MTP3B_DSP_TRAF.......................................................... 10-368
10.29.4 Count of Transfer Prohibited Messages Received ....................................... 10-369
10.30 MTP Destination Signaling Point ............................................................................. 10-370
10.30.1 Overview of MS_MTP_DSP_TRAF .............................................................. 10-370
10.31 MTP Signaling Link.................................................................................................. 10-371
10.31.1 Overview of MS_MTP_LINK_TRAF.............................................................. 10-371
10.31.3 Count of Failures........................................................................................... 10-372
10.31.4 Duration of Failure......................................................................................... 10-372
10.31.7 Count of Messages Discarded Due to Congestion ....................................... 10-373
l
10.31.8 Count of Transfer Prohibited Signals Received ............................................ 10-374

10.31.9 Count of Local Automatic Switchovers ......................................................... 10-374
10.31.10 Count of Local Management Inhibition Operations..................................... 10-375
10.31.11 Duration of Local Management Inhibition Operations................................. 10-375
10.31.12 Count of Remote Management Inhibition Operations................................. 10-376
10.31.13 Duration of Remote Management Inhibition Operations............................. 10-376
10.31.14 Count of Remote Processor Failures.......................................................... 10-377
10.31.15 Duration of Remote Processor Failure........................................................ 10-377
10.31.32 Percentage of Signaling Link Bandwidth Used for Sending Signaling Information
.................................................................................................................................... 10-387
10.31.33 Percentage of Signaling Link Bandwidth Used for Receiving Signaling
Information ................................................................................................................. 10-387
10.32 MTP Signaling Link Set ........................................................................................... 10-388
10.32.1 Overview of MS_MTP_LINKSET_TRAF....................................................... 10-388
10.32.2 Count of Unavailability .................................................................................. 10-388
10.32.3 Duration of Unavailability .............................................................................. 10-389
10.32.4 Count of SCCP Messages Sent.................................................................... 10-389
10.32.5 Count of SCCP Messages Received ............................................................ 10-390
10.32.6 Count of Bytes in SCCP Messages Sent...................................................... 10-390
10.32.7 Count of Bytes in SCCP Messages Received .............................................. 10-391
10.32.8 Count of TUP Messages Sent....................................................................... 10-392
10.32.9 Count of TUP Messages Received ............................................................... 10-392
li

10.33 SAAL Signaling Link ................................................................................................ 10-399
10.33.1 Overview of MS_SAAL_LINK_TRAF ............................................................ 10-399
10.33.2 Duration of SAAL Signaling Link in Service .................................................. 10-399
10.33.3 Count of SAAL Signaling Link Failures Due to Other Causes ...................... 10-400
10.33.4 Count of SAAL Signaling Link Failures Due to Timeout of No Response Timer10-400
10.33.5 Count of SAAL Signaling Link Failures Due to Too High Bit Error Rate....... 10-400
10.33.6 Count of SAAL Signaling Link Failures Due to Congestion Timeout ............ 10-401
10.33.7 Count of Location Failures of SAAL Signaling Link ...................................... 10-401
10.33.8 Count of MAA-ERROR Indications Due to SD Loss ..................................... 10-401
10.33.9 Count of Unexpected Packets Received ...................................................... 10-402
10.33.10 Count of SSCOP Sending Error Report to LM Due to Other Causes......... 10-402
10.33.11 Count of Failed Retransmission .................................................................. 10-403
10.34 SCCP Availability..................................................................................................... 10-403
10.34.1 Overview of MS_SCCP_AVAILABILITY ....................................................... 10-403
10.34.2 Count of Local SCCP Failures Due to Fault ................................................. 10-403
10.34.3 Count of Local SCCP Failures Due to Maintenance..................................... 10-404
10.34.4 Count of Local SCCP Failures Due to Congestion ....................................... 10-404
10.34.5 Duration of Unavailability of Local SCCP Due to All Causes........................ 10-404
10.34.6 Count of Local SCCP Recovery Due to All Causes...................................... 10-405
10.35 SCCP Usage............................................................................................................ 10-405
10.35.1 Overview of MS_SCCP_UTILIZATION......................................................... 10-405
10.35.2 Count of UDTS Messages Sent .................................................................... 10-405
10.35.3 Count of UDTS Messages Received ............................................................ 10-406
10.35.4 Count of Processed Messages (from Local or Remote Subsystem) ............ 10-407
10.35.5 Count of Messages Used by Local Subsystem ............................................ 10-407
10.35.6 Count of Messages Needing GT Translation................................................ 10-408
10.35.7 Count of Connectionless Messages Sent ..................................................... 10-409
10.35.8 Count of Connectionless Messages Received ............................................. 10-409
10.35.9 Count of Messages Sent to a Standby Subsystem....................................... 10-410
10.36 SCCP Traffic ............................................................................................................ 10-411
10.36.1 Overview of MS_SCCP_FLUX_TRAFFIC .................................................... 10-411
10.36.2 Count of Messages Sent to a DSP ............................................................... 10-411
10.36.3 Count of Messages Received from a DSP ................................................... 10-411
10.36.4 Count of Bytes Sent to a DSP....................................................................... 10-412
10.36.5 Count of Bytes Received from a DSP........................................................... 10-413
10.37 SCCP Performance ................................................................................................. 10-413
lii
10.37.1 Overview of MS_SCCP_PERFORMANCE................................................... 10-413

10.37.2 Count of Route Failures Due to Invalid Addressing Information................... 10-414
10.37.3 Count of Route Failures Due to Translation Failure of Valid Address .......... 10-414
10.37.4 Count of Route Failures Due to Unavailable Signaling Point ....................... 10-414
10.37.5 Count of Route Failures Due to Network Congestion ................................... 10-415
10.37.6 Count of Route Failures Due to Subsystem Failure...................................... 10-415
10.37.7 Count of Route Failures Due to Subsystem Congestion .............................. 10-415
10.37.8 Count of Route Failures Due to Subsystem Not Installed ............................ 10-416
10.37.9 Count of Route Failures Due to Unknown Reason ....................................... 10-416
10.37.10 Count of Route Failures Due to Syntax Error ............................................. 10-416
10.38 TCAP CSL ............................................................................................................... 10-417
10.38.1 Overview of MS_TCAP_CSL_PERFORMANCE .......................................... 10-417
10.38.2 Count of Unrecognized Components............................................................ 10-417
10.38.3 Count of Components of Wrong Type .......................................................... 10-418
10.38.4 Count of Wrong Component Structures........................................................ 10-418
10.38.5 Count of Unrecognized Link IDs ................................................................... 10-418
10.38.6 Count of Unexpected Results ....................................................................... 10-419
10.38.7 Count of Unrecognized Operation IDs in Results ......................................... 10-419
10.38.8 Count of Unexpected Errors.......................................................................... 10-419
10.38.9 Count of Unrecognized Operation IDs in Errors ........................................... 10-420
10.39 TCAP Transport Sublayer........................................................................................ 10-420
10.39.1 Overview of MS_TCAP_TSL_PERFORMANCE .......................................... 10-420
10.39.2 Count of P_ABORT Messages with Cause of Unrecognized Message Type10-420
10.39.3 Count of P_ABORT Messages with Cause of Wrong Transaction Portion .. 10-421
10.39.4 Count of P_ABORT Messages with Cause of Wrong Format of Transaction
Portion ........................................................................................................................ 10-422
10.39.5 Count of P_ABORT Messages with Cause of Unrecognized Transaction ID10-423
10.39.6 Count of P_ABORT Messages with Cause of Resource Limitation on Transaction
Sublayer ..................................................................................................................... 10-423
10.40 TCAP Availability ..................................................................................................... 10-424
10.40.1 Overview of MS_TCAP_AVAILABILITY ....................................................... 10-424
10.40.2 Count of Local TCAP Failures Due to Fault.................................................. 10-424
10.40.3 Count of Local TCAP Failures Due to Maintenance ..................................... 10-425
10.40.4 Count of Local TCAP Failures Due to Congestion ....................................... 10-425
10.40.5 Duration of Unavailability of Local TCAP Due to All Causes ........................ 10-425
10.41 Count of TCAP Messages ....................................................................................... 10-426
10.41.1 Overview of MS_TCAP_MSG_UTILIZATION............................................... 10-426
10.41.2 Count of Invoke Messages Sent ................................................................... 10-426
10.41.3 Count of Invoke Messages Received ........................................................... 10-427
10.41.4 Count of Last Result Messages Sent (Returned Result) .............................. 10-427
10.41.5 Count of Last Result Messages Received (Returned Result) ...................... 10-428
10.41.6 Count of Not Last Result Messages Sent (Returned Result) ....................... 10-429
liii
10.41.7 Count of Not Last Result Messages Received (Returned Result)................ 10-429
10.41.8 Count of Returned Error Messages Sent...................................................... 10-430
10.41.9 Count of Returned Error Messages Received .............................................. 10-430
10.41.10 Count of Reject Messages Sent ................................................................. 10-431
10.41.11 Count of Reject Messages Received.......................................................... 10-432
10.42 TCAP Component Utilization ................................................................................... 10-432
10.42.1 Overview of MS_TCAP_CMP_UTILIZATION ............................................... 10-432
10.42.2 Count of Invoke Components Sent ............................................................... 10-433
10.42.3 Count of Invoke Components Received ....................................................... 10-433
10.42.4 Count of Last Result Components Sent (Returned Result) .......................... 10-434
10.42.5 Count of Last Result Components Received (Returned Result) .................. 10-434
10.42.6 Count of Not Last Result Components Sent (Returned Result) ................... 10-435
10.42.7 Count of Not Last Result Components Received (Returned Result)............ 10-436
10.42.8 Count of Return Error Components Sent...................................................... 10-436
10.42.9 Count of Return Error Components Received .............................................. 10-437
10.42.10 Count of Reject Components Sent ............................................................. 10-437
10.42.11 Count of Reject Components Received...................................................... 10-438
10.43 TUP Circuit Group ................................................................................................... 10-439
10.43.1 Overview of MS_TUP_TKGRP_PERFORM_TRAF...................................... 10-439
10.43.3 Count of Messages with Cause of Switching Equipment Congestion .......... 10-441
10.43.4 Count of Messages with Cause of Circuit Group Congestion....................... 10-442
10.43.5 Count of Messages with Cause of National Network Congestion ................ 10-442
10.43.7 Count of Messages with Cause of Incomplete Address ............................... 10-443
10.43.8 Count of Messages with Cause of Call Failure ............................................. 10-444
10.43.9 Count of Messages with Cause of Callee Busy ............................................ 10-445
10.43.10 Count of Messages with Cause of Unallocated Number ............................ 10-446
10.43.11 Count of Messages with Cause of Line out of Service ............................... 10-447
10.43.12 Count of Messages with Cause of Sending Special Signal Tone............... 10-448
10.43.13 Count of Messages with Cause of Rejected Access .................................. 10-449
10.43.14 Count of Messages with Cause of Digital Path Not Provided..................... 10-450
10.43.15 Count of Messages with Cause of Trunk Prefix Wrongly Dialed ................ 10-451
10.43.16 Count of Outgoing Call Attempts ................................................................ 10-451
10.43.17 Count of SEC Messages Received............................................................. 10-452
10.43.18 Count of CGC Messages Received ............................................................ 10-453
10.43.19 Count of NNC Messages Received ............................................................ 10-454
10.43.20 Count of ADI Messages Received .............................................................. 10-455
10.43.21 Count of CFL Messages Received ............................................................. 10-456
10.43.22 Count of Messages Received with Cause of Callee Busy.......................... 10-457
10.43.23 Count of UNN Messages Received ............................................................ 10-458
10.43.24 Count of LOS Messages Received............................................................. 10-459
liv
10.43.25 Count of SST Messages Received ............................................................. 10-460

10.43.26 Count of ACB Messages Received............................................................. 10-461
10.43.27 Count of DPN Messages Received ............................................................ 10-462
10.43.28 Count of Messages Received with Cause of Trunk Prefix Wrongly Dialed 10-463
10.43.29 Count of Answers Without Charging........................................................... 10-463
10.43.30 Count of Maintenance-Oriented CGB Messages........................................ 10-464
10.43.31 Count of Hardware-Oriented CGB Messages............................................. 10-465
10.43.32 Count of Circuit Group Reset Messages .................................................... 10-466
10.43.33 Count of Circuit Reset Messages ............................................................... 10-467
10.43.34 Count of Answers........................................................................................ 10-468
10.43.37 Count of Messages Both Received and Sent ............................................. 10-470
10.43.38 Length of Messages Received.................................................................... 10-470
10.43.39 Length of Messages Sent ........................................................................... 10-471
10.43.40 Length of Messages Both Received and Sent............................................ 10-471
10.43.41 Count of Calls.............................................................................................. 10-471
10.43.42 Length of Messages per Call ...................................................................... 10-472
10.43.43 Average Message Length ........................................................................... 10-472
10.44 TUP Node ................................................................................................................ 10-473
10.44.1 Overview of MS_TUP_NODE_PERFORM_TRAF........................................ 10-473
10.44.3 Count of Messages with Cause of Switch Congestion ................................. 10-474
10.44.4 Count of Messages with Cause of Circuit Group Congestion....................... 10-475
10.44.5 Count of Messages with Cause of National Network Congestion ................ 10-476
10.44.6 Count of Messages with Cause of Incomplete Address ............................... 10-476
10.44.7 Count of Messages with Cause of Call Failure ............................................. 10-477
10.44.8 Count of Messages with Cause of Callee Busy ............................................ 10-478
10.44.9 Count of Messages with Cause of Unallocated Number .............................. 10-479
10.44.10 Count of Messages with Cause of Line out of Service ............................... 10-480
10.44.11 Count of Messages with Cause of Sending Special Tone.......................... 10-481
10.44.12 Count of Messages with Cause of Rejected Access .................................. 10-482
10.44.13 Count of Messages with Cause of Digital Path Not Provided..................... 10-483
10.44.14 Count of Messages with Cause of Trunk Prefix Wrongly Dialed ................ 10-484
10.45 TUP Network............................................................................................................ 10-485
10.45.1 Overview of MS_TUP_NET_PERFORM_TRAF........................................... 10-485
10.45.2 Count of Outgoing Call Attempts .................................................................. 10-485
10.45.3 Count of SEC Messages Received............................................................... 10-486
10.45.4 Count of CGC Messages Received .............................................................. 10-487
10.45.5 Count of NNC Messages Received .............................................................. 10-488
10.45.6 Count of ADI Messages Received ................................................................ 10-489
10.45.7 Count of CFL Messages Received ............................................................... 10-490
lv
10.45.8 Count of Messages Received with Cause of Callee Busy............................ 10-491

10.45.9 Count of UNN Messages Received .............................................................. 10-492
10.45.10 Count of LOS Messages Received............................................................. 10-493
10.45.11 Count of SST Messages Received ............................................................. 10-494
10.45.12 Count of ACB Messages Received............................................................. 10-495
10.45.13 Count of DPN Messages Received ............................................................ 10-496
10.45.14 Count of Messages Received with Cause of Trunk Prefix Wrongly Dialed 10-497
10.46 TUP Message Application ....................................................................................... 10-498
10.46.1 Overview of MS_TUP_MSG_USING_TRAF ................................................ 10-498
10.46.2 Count of Certain Messages Sent .................................................................. 10-498
10.46.3 Count of Certain Messages Received .......................................................... 10-498
10.47 Count of TUP Messages.......................................................................................... 10-499
10.47.1 Overview of MS_TUP_TOTAL_MSU_TRAF ................................................ 10-499
10.47.2 Count of Messages Sent............................................................................... 10-499
10.47.3 Count of Messages Received ....................................................................... 10-499
10.48 TUP Abnormity......................................................................................................... 10-500
10.48.1 Overview of MS_TUP_UNUSUAL_TRAF..................................................... 10-500
10.48.2 Count of Responses to RSC Not Received by T19 ...................................... 10-501
10.48.3 Count of GRAs Not Received by T22 ........................................................... 10-501
10.48.4 Count CLFs Not Received by T5 .................................................................. 10-501
10.48.5 Count of RLGs Not Received by T7.............................................................. 10-502
10.48.6 Count of Abnormal Release Messages ........................................................ 10-502
10.48.7 Count of Circuit Blocking Messages ............................................................. 10-502
10.48.8 Count of Failures to Assign MHBA on Some Circuits ................................... 10-503
10.48.9 Count of Failures to Assign MHUA on Some Circuits................................... 10-503
10.48.10 Count of Assignments of Too Many MHBAs on Some Circuits .................. 10-503
10.48.11 Count of Assignments of Too Many MHUAs on Some Circuits.................. 10-504
10.48.12 Count of Unexpected MHBAs Received ..................................................... 10-504
10.48.13 Count of Unexpected MHUAs Received..................................................... 10-504
10.48.14 Count of Unexpected BLAs Received......................................................... 10-505
10.48.15 Count of Unexpected UBAs Received ........................................................ 10-505
10.48.16 Count of BLAs Not Received by T13 .......................................................... 10-505
10.48.17 Count of UBAs Not Received by T16.......................................................... 10-506
10.48.18 Count of Second Group Messages Not Received by T25 .......................... 10-506
10.48.19 Count of MBAs Not Received by T27 ......................................................... 10-506
10.48.20 Count of MUAs Not Received by T29 ......................................................... 10-507
10.48.21 Count of HBAs Not Received by T33.......................................................... 10-507
10.48.22 Count of HUAs Not Received by T35 ......................................................... 10-507
10.48.23 Count of Wrong Format Messages ............................................................. 10-508
10.48.24 Count of Unexpected Messages Received................................................. 10-508
10.48.25 Count of Unknown Messages Received ..................................................... 10-508
10.49 Union Location Update Rejected Cause ................................................................. 10-509
lvi
10.49.1 Overview of MS_TYPE_UNION_LOC_UP ................................................... 10-509

10.49.2 Count of Messages Indicating Unknown Subscriber .................................... 10-509
10.49.3 Count of Messages Indicating Roaming Not Allowed................................... 10-510
10.49.4 Count of Messages Indicating PLMN Roaming Not Allowed........................ 10-511
10.49.5 Count of Messages Indicating System Failure.............................................. 10-512
10.49.6 Count of Messages Indicating Data Lost ...................................................... 10-513
Chapter 11 IN Services ............................................................................................................... 11-1

11.2 CAP Operations ............................................................................................................. 11-1
11.2.1 Overview of MS_TYPE_CAP_OPER.................................................................. 11-1
11.2.2 Count of Received Activity Test Messages......................................................... 11-3
11.2.3 Count of Sent Activity Test Messages ................................................................ 11-4
11.2.4 Count of Apply Charging Messages ................................................................... 11-5
11.2.5 Count of Apply Charging Report Messages........................................................ 11-6
11.2.6 Count of Assist Request Instructions Messages................................................. 11-7
11.2.7 Count of Call Gap Messages .............................................................................. 11-8
11.2.8 Count of Call Information Report Messages ....................................................... 11-9
11.2.9 Count of Call Information Request Messages .................................................. 11-10
11.2.10 Count of Cancel Messages ............................................................................. 11-11
11.2.11 Count of Connect Messages........................................................................... 11-12
11.2.12 Count of Connect To Resource Messages ..................................................... 11-13
11.2.13 Count of Continue Messages.......................................................................... 11-14
11.2.14 Count of Disconnect Forward Connection Messages..................................... 11-15
11.2.15 Count of Establish Temporary Connection Messages.................................... 11-16
11.2.16 Count of Event Report BCSM Messages........................................................ 11-17
11.2.17 Count of Received Furnish Charging Information........................................... 11-18
11.2.18 Count of Initial DP Messages.......................................................................... 11-19
11.2.19 Count of Play Announcement Messages........................................................ 11-20
11.2.20 Count of Prompt And Collect User Information Messages ............................. 11-21
11.2.21 Count of Prompt and Collect User Information Results .................................. 11-22
11.2.22 Count of Release Call Messages.................................................................... 11-23
11.2.23 Count of Request Report BCSM Event Messages ......................................... 11-24
11.2.24 Count of Reset Timer Messages..................................................................... 11-25
11.2.25 Count of Send Charging Information Messages ............................................. 11-26
11.2.26 Count of Specialized Resource Report Messages ......................................... 11-27
11.2.27 Count of Received NULL Messages............................................................... 11-28
11.2.28 Count of Sent NULL Messages....................................................................... 11-29
11.2.29 Count of Received Error Messages ................................................................ 11-30
11.2.30 Count of Sent Error Messages........................................................................ 11-31
11.2.31 Count of Sent TC_ABORT Messages ............................................................ 11-32
11.2.32 Count of Received TC_ABORT Messages..................................................... 11-33
11.2.33 Count of Continue With Argument Messages................................................. 11-34
lvii
11.2.34 Count of Connect SMS Messages.................................................................. 11-35

11.2.35 Count of Continue SMS Messages................................................................. 11-36
11.2.36 Count of Event Report SMS Messages .......................................................... 11-37
11.2.37 Count of Furnish Charging Information SMS Messages ................................ 11-38
11.2.38 Count of Initial DP SMS Messages................................................................. 11-39
11.2.39 Count of Release SMS Messages .................................................................. 11-40
11.2.40 Count of Request Report SMS Event Messages............................................ 11-41
11.2.41 Count of Reset Timer SMS Messages............................................................ 11-42
11.2.42 Count of ICA Messages .................................................................................. 11-43
11.2.43 Count of Provide Avail DN Messages (Received) .......................................... 11-44
11.2.44 Count of Provide Avail DN Messages (Sent) .................................................. 11-45
11.2.45 Count of Port Connected Messages (Received)............................................. 11-46
11.2.46 Count of Port Connected Messages (Sent) .................................................... 11-47
11.2.47 Count of Bridge Ports Messages (Received).................................................. 11-48
11.2.48 Count of Bridge Ports Messages .................................................................... 11-49
11.3 Initial Call Attempts ...................................................................................................... 11-50
11.3.1 Overview of MS_IN_ICA ................................................................................... 11-50
11.3.2 Count of ICA Call Attempts ............................................................................... 11-51
11.3.3 Count of ICA Call Alertings ............................................................................... 11-51
11.3.4 Count of ICA Call Answers................................................................................ 11-52
11.3.5 ICA Call Seizure Traffic..................................................................................... 11-53
11.3.6 ICA Call Alerting Traffic..................................................................................... 11-53
11.3.7 ICA Call Answer Traffic ..................................................................................... 11-54
11.3.8 ICA Call Alerting Rate ....................................................................................... 11-54
11.3.9 ICA Call Answer Rate ....................................................................................... 11-54
11.3.10 Count of ICA DNs............................................................................................ 11-55
11.3.11 Count of ICA DN Failures................................................................................ 11-55
11.3.12 Count of Received Bridge Ports...................................................................... 11-56
11.3.13 Count of SSP Bridge Ports Failures................................................................ 11-57
11.4 MAP IN Services.......................................................................................................... 11-57
11.4.1 Overview of MS_TYPE_MAP_IN_SERVICE .................................................... 11-57
11.4.2 Count of Providing CAMEL Subscriber Information.......................................... 11-58
11.4.3 Success Count of Providing CAMEL Subscriber Information ........................... 11-58
11.4.4 Count of Sending Routing Information for CAMEL Subscriber......................... 11-59
11.5 SSF Calls ..................................................................................................................... 11-60
11.5.1 Overview of MS_TYPE_SSF_CALL_TRAF...................................................... 11-60
11.5.2 Count of SSF Call Outs..................................................................................... 11-60
11.5.3 Count of SSF Call Ins........................................................................................ 11-61
11.6 Fixed Subscriber Calling IN Subscriber....................................................................... 11-62
11.6.1 Overview of MS_TYPE_IN_INC_TRAF ............................................................ 11-62
11.6.2 Attempt Count of Fixed Subscriber Calling IN Subscriber ................................ 11-63
11.6.3 Connect Count of Fixed Subscriber Calling IN Subscriber ............................... 11-63
lviii
11.6.4 Answer Count of Fixed Subscriber Calling IN Subscriber ................................ 11-64

11.6.5 Abandon Before Alerting Count of Fixed Subscriber Calling IN Subscriber ..... 11-65
11.6.6 Abandon After Alerting Count of Fixed Subscriber Calling IN Subscriber ........ 11-66
11.6.7 Callee Busy Count of Fixed Subscriber Calling IN Subscriber ......................... 11-67
11.6.8 No Answer Count of Fixed Subscriber Calling IN Subscriber........................... 11-68
11.6.9 Callee Determined Busy Count of Fixed Subscriber Calling IN Subscriber ..... 11-69
11.6.10 Seizure Traffic of Fixed Subscriber Calling IN Subscriber.............................. 11-70
11.6.11 Connected Traffic of Fixed Subscriber Calling IN Subscriber......................... 11-71
11.6.12 Answer Traffic of Fixed Subscriber Calling IN Subscriber .............................. 11-72
11.7 Mobile Subscriber Calling IN Subscriber ..................................................................... 11-73
11.7.1 Overview of MS_TYPE_IN_MT_INT_TRAF ..................................................... 11-73
11.7.2 Attempt Count of Mobile Subscriber Calling IN Subscriber .............................. 11-74
11.7.3 Connect Count of Mobile Subscriber Calling IN Subscriber ............................. 11-75
11.7.4 Answer Count of Mobile Subscriber Calling IN Subscriber............................... 11-76
11.7.5 Abandon Before Alerting Count of Mobile Subscriber Calling IN Subscriber ... 11-77
11.7.6 Abandon After Alerting Count of Mobile Subscriber Calling IN Subscriber ...... 11-78
11.7.7 Callee Busy Count of Mobile Subscriber Calling IN Subscriber ....................... 11-79
11.7.8 No Answer Count of Mobile Subscriber Calling IN Subscriber ......................... 11-80
11.7.9 Callee Determined Busy Count of Mobile Subscriber Calling IN Subscriber.... 11-81
11.7.10 Seizure Traffic of Mobile Subscriber Calling IN Subscriber ............................ 11-82
11.7.11 Connected Traffic of Mobile Subscriber Calling IN Subscriber....................... 11-83
11.7.12 Answer Traffic of Mobile Subscriber Calling IN Subscriber ............................ 11-83
11.8 IN Components ............................................................................................................ 11-83
11.8.1 Overview of MS_TYPE_IN_COMPOMENT...................................................... 11-83
11.8.2 Sent INVOKE .................................................................................................... 11-84
11.8.3 Received INVOKE............................................................................................. 11-84
11.8.4 Count of RESULTs that Cannot be Coded ....................................................... 11-85
11.8.5 Count of RESULTs that Cannot be Decoded ................................................... 11-86
11.8.6 Count of Sent TC_REJECT Messages............................................................. 11-86
11.8.7 Count of Received TC_REJECT Messages ..................................................... 11-87
11.9 IN Dialogue .................................................................................................................. 11-88
11.9.1 Overview of MS_IN_DIALOGUE_TRAF ........................................................... 11-88
11.9.2 Count of Sessions Sent by SSF........................................................................ 11-89
11.9.3 Count of Sessions Received by SSF ................................................................ 11-89
11.9.4 Count of Sessions U-Abort Sent by SSP .......................................................... 11-90
11.9.5 Count of Sessions P-Abort and U-Abort Sent by SSP...................................... 11-91
11.9.6 Call Duration Between Received TC-BEGIN and TC-END .............................. 11-92
11.9.7 Total Count of Sessions .................................................................................... 11-92
11.9.8 Average Duration of Sessions........................................................................... 11-93
11.10 IN Calls of All Subscribers Calling Operator.............................................................. 11-93
11.10.1 Overview of MS_TYPE_IN_OPERATOR_TRAF ............................................ 11-93
11.10.2 Attempt Count of IN Subscriber Calling Operator ........................................... 11-94
lix
11.10.3 Connect Count of IN Subscriber Calling Operator .......................................... 11-95

11.10.4 Answer Count of IN Subscriber Calling Operator ........................................... 11-97
11.10.5 Abandon Before Alerting Count of IN Subscriber Calling Operator ................ 11-99
11.10.6 Abandon After Alerting Count of IN Subscriber Calling Operator ................. 11-101
11.10.7 Callee Busy Count of IN Subscriber Calling Operator .................................. 11-103
11.10.8 No Answer Count of IN Subscriber Calling Operator.................................... 11-105
11.10.9 Callee Determined Busy Count of IN Subscriber Calling Operator .............. 11-106
11.10.10 Seizure Traffic of IN Subscriber Calling Operator....................................... 11-107
11.10.11 Connect Traffic of IN Subscriber Calling Operator...................................... 11-108
11.10.12 Answer Traffic of IN Subscriber Calling Operator ....................................... 11-108
11.11 IN Failures................................................................................................................ 11-109
11.11.1 Overview of MS_IN_FAILURE_TRAF .......................................................... 11-109
11.11.2 Count of Overload Rejected Calls................................................................. 11-109
11.11.3 Count of Call Failures Before Initialization .................................................... 11-109
11.11.4 Count of Call Failures After Initialization ....................................................... 11-110
11.11.5 Count of Sessions Reject Received by SSF................................................. 11-110
11.12 IN Events ................................................................................................................. 11-111
11.12.1 Overview of MS_TYPE_IN_OPERATOR_TRAF .......................................... 11-111
11.12.2 Originating IN Call Initiates (DP2) ................................................................. 11-112
11.12.3 Originating Route Selection Fails (EDP4)..................................................... 11-113
11.12.4 Originating Callee Busy (DP5) ...................................................................... 11-113
11.12.5 Originating Callee Does Not Answer (DP6) .................................................. 11-114
11.12.6 Originating Callee Answers (DP7) ................................................................ 11-115
11.12.7 Originating Release Event (DP9) .................................................................. 11-116
11.12.8 Originating Caller Abandons (DP10)............................................................. 11-117
11.12.9 Terminating IN Call Initiates (DP12) ............................................................. 11-118
11.12.10 Terminating Callee Busy (EDP13) .............................................................. 11-119
11.12.11 Terminating Callee Does Not Answer (EDP14) .......................................... 11-120
11.12.12 Terminating Callee Answers (DP15)........................................................... 11-121
11.12.13 Terminating Releases (DP17)..................................................................... 11-122
11.12.14 Terminating Caller Abandons (DP18) ......................................................... 11-123
11.12.15 Terminating Analyzes Information (DP3) .................................................... 11-124
11.12.16 Originating Route Selection Fails (TDP4) ................................................... 11-125
11.12.17 Terminating Callee Busy (TDP13) .............................................................. 11-126
11.12.18 Terminating Callee Does Not Answer (TDP14) .......................................... 11-127
11.12.19 Originating IN SMS Initiates ........................................................................ 11-128
11.12.20 Originating SMS Fails ................................................................................. 11-129
11.12.21 Originating SMS Submits ............................................................................ 11-130
11.13 IN Subscriber Calling Fixed Subscriber................................................................... 11-131
11.13.1 Overview of MS_TYPE_IN_ORGOUT_TRAF .............................................. 11-131
11.13.2 Attempt Count of IN Subscriber Calling Fixed Subscriber ............................ 11-132
11.13.3 Connect Count of IN Subscriber Calling Fixed Subscriber ........................... 11-132
lx
11.13.4 Answer Count of IN Subscriber Calling Fixed Subscriber ............................ 11-133

11.13.5 Abandon Before Alerting Count of IN Subscriber Calling Fixed Subscriber . 11-134
11.13.6 Abandon After Alerting Count of IN Subscriber Calling Fixed Subscriber .... 11-135
11.13.7 Callee Busy Count of IN Subscriber Calling Fixed Subscriber ..................... 11-136
11.13.8 No Answer Count of IN Subscriber Calling Fixed Subscriber....................... 11-137
11.13.9 Seizure Traffic of IN Subscriber Calling Fixed Subscriber ............................ 11-138
11.13.10 Connected Traffic of IN Subscriber Calling Fixed Subscriber..................... 11-139
11.13.11 Answer Traffic of IN Subscriber Calling Fixed Subscriber .......................... 11-140
11.14 IN Subscriber Calling Mobile Subscriber ................................................................. 11-141
11.14.1 Overview of MS_TYPE_IN_MO_INT_TRAF................................................. 11-141
11.14.2 Attempt Count of IN Subscriber Calling Mobile Subscriber .......................... 11-142
11.14.3 Connect Count of IN Subscriber Calling Mobile Subscriber ......................... 11-143
11.14.4 Answer Count of IN Subscriber Calling Mobile Subscriber........................... 11-144
11.14.5 Abandon Before Alerting Count of IN Subscriber Calling Mobile Subscriber 11-145
11.14.6 Abandon After Alerting Count of IN Subscriber Calling Mobile Subscriber .. 11-146
11.14.7 Callee Busy Count of IN Subscriber Calling Mobile Subscriber ................... 11-147
11.14.8 No Answer Count of IN Subscriber Calling Mobile Subscriber ..................... 11-148
11.14.9 Callee Determined Busy Count of IN Subscriber Calling Mobile Subscriber 11-149
11.14.10 Seizure Traffic of IN Subscriber Calling Mobile Subscriber ........................ 11-150
11.14.11 Connected Traffic of IN Subscriber Calling Mobile Subscriber................... 11-151
11.14.12 Answer Traffic of IN Subscriber Calling Mobile Subscriber ........................ 11-152
11.15 IN Subscriber Calling IN Subscriber ........................................................................ 11-153
11.15.1 Overview of MS_TYPE_IN_OPERATOR_TRAF .......................................... 11-153
11.15.2 Count of Caller Attempts ............................................................................... 11-154
11.15.3 Count of Caller Connections ......................................................................... 11-156
11.15.4 Count of Caller Answers ............................................................................... 11-158
11.15.5 Count of Caller Abandons Before Ringing .................................................... 11-160
11.15.6 Count of Caller Abandons After Ringing ....................................................... 11-162
11.15.7 Count of No Answers .................................................................................... 11-164
11.15.8 Count of Callee Busy .................................................................................... 11-166
11.15.9 Count of Callee Determined Busy................................................................. 11-168
11.15.10 Caller Seizure Traffic................................................................................... 11-170
11.15.11 Caller Connected Traffic ............................................................................. 11-171
11.15.12 Caller Answer Traffic................................................................................... 11-171
11.15.13 Count of Callee Attempts ............................................................................ 11-171
11.15.14 Count of Callee Connections ...................................................................... 11-172
11.15.15 Count of Callee Answers............................................................................. 11-173
11.15.16 Callee Seizure Traffic.................................................................................. 11-173
11.15.17 Callee Connected Traffic............................................................................. 11-174
11.15.18 Callee Answer Traffic .................................................................................. 11-174
Chapter 12 Lawful Interception.................................................................................................. 12-1

lxi
12.2 Monitored Outgoing Traffic ............................................................................................ 12-1

12.2.1 Overview of MS_OFFICE_OUT_TRAF_LICI...................................................... 12-1
12.2.2 Count of Seizure Attempts .................................................................................. 12-2
12.2.3 Count of Seizures................................................................................................ 12-3
12.2.6 Count of No Answer ............................................................................................ 12-6
12.2.7 Count of Abandon Before Alerting ...................................................................... 12-8
12.2.8 Count of Lost Calls Due to Overload Control...................................................... 12-8
12.2.9 Count of Lost Calls Due to NMS Control .......................................................... 12-11
12.2.10 Count of Last-Choice Route Overflow ............................................................ 12-13
12.2.14 Seizure Traffic ................................................................................................. 12-15
12.2.16 Count of Circuits in Maintenance State........................................................... 12-17
12.2.18 Answer Rate.................................................................................................... 12-18
12.2.20 Count of Failed Call Attempts Due to Common Resource Application Failure12-19
12.2.22 Traffic of Completed Calls............................................................................... 12-22
12.3 Monitored Office Direction Outgoing Traffic ................................................................ 12-23
12.3.1 Overview of MS_OFFICEDIR_OUT_TRAF_LICI.............................................. 12-23
12.3.7 Count of Calls Through Indirect Sub-Routes .................................................... 12-28
12.3.8 Count of No Command for Nested Calling........................................................ 12-29
12.3.10 Count of Trunk Retry....................................................................................... 12-30
12.3.14 Count of No Reply........................................................................................... 12-35
12.3.16 Count of Available Bidirectional Circuits ......................................................... 12-37
12.3.17 Count of Blocked Bidirectional Circuits ........................................................... 12-38
12.3.18 Availability of Outgoing Trunks........................................................................ 12-38
lxii
12.3.19 Seizure Rate.................................................................................................... 12-39

12.3.21 Answer Rate.................................................................................................... 12-39
12.3.22 Block Rate ....................................................................................................... 12-40
12.3.25 Seizure Traffic ................................................................................................. 12-41
12.3.29 Count of First Sub-Route Overflow ................................................................. 12-42
12.3.30 Count of Second Sub-Route Overflow............................................................ 12-43
12.3.31 Count of Third Sub-Route Overflow................................................................ 12-43
12.3.32 Count of Fourth Sub-Route Overflow.............................................................. 12-43
12.3.33 Count of Fifth Sub-Route Overflow ................................................................. 12-44
12.3.34 Count of Sixth Sub-Route Overflow ................................................................ 12-44
12.3.35 Count of Seventh Sub-Route Overflow........................................................... 12-45
12.3.36 Count of Eighth Sub-Route Overflow.............................................................. 12-45
12.3.37 Count of Ninth Sub-Route Overflow................................................................ 12-45
12.3.38 Count of Tenth Sub-Route Overflow............................................................... 12-46
12.3.39 Count of Eleventh Sub-Route Overflow .......................................................... 12-46
12.3.40 Count of Twelfth Sub-Route Overflow ............................................................ 12-46
12.4 Monitored Trunk Group Outgoing Traffic..................................................................... 12-47
12.4.1 Overview of MS_TKGRP_OUT_TRAF_LICI..................................................... 12-47
12.4.7 Count of Bearer Capability and Mode Mismatch .............................................. 12-53
12.4.9 Count of Trunk Retry......................................................................................... 12-54
12.4.11 Congestion Duration ....................................................................................... 12-57
12.4.12 Count of Effects Caused by NMS Control....................................................... 12-57
12.4.17 Count of No Reply........................................................................................... 12-62
lxiii

12.4.22 Count of Available Bidirectional Circuits ......................................................... 12-66
12.4.23 Count of Blocked Bidirectional Circuits ........................................................... 12-66
12.4.24 Availability of Outgoing Trunks........................................................................ 12-66
12.4.25 Seizure Rate.................................................................................................... 12-67
12.4.27 Answer Rate.................................................................................................... 12-67
12.4.28 Block Rate ....................................................................................................... 12-68
12.4.31 Seizure Traffic ................................................................................................. 12-69
Index ................................................................................................................................................ i-1
lxiv
Technical Manual – Performance Measurement Entities
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 1 Overview
Chapter 1 Overview
Performance measurement (PM), also named traffic measurement or traffic statistics,

measures entities such as traffic and load in an office as well as its surrounding
networks, and provides the data displaying network operating conditions.
The PM offers the data of the measurement, formulation, running and management of
the telephony network, to optimize the network performance both in the reasonable
configuration of resources and the economy. In addition, the PM system measures
objects related to the traffic and equipment running, such as trunks, switching devices
and signaling system in an MSC.
The measurement covers the following objects:
z Count of calls
z Traffic
z Average seizure time
z Network state monitoring
z Equipment running
The PM consists of three basic factors:
z Measurement entity
z Measurement object
z Measurement time
The manual focuses on the descriptions of measurement entities and their
measurement points. The manual consists of multiple measurement sets, each of
which includes several measurement units. The measurement entities are detailed in
each section of measurement unit.
1.1 Measurement Set

A measurement set collects some units with certain attributes in common. For example,
the set call connection procedure measures answer rate, call setup rate and so on.
Usually, a type of PM task corresponds to a measurement set, and several
measurement sets can describe a PM system.
1.2 Measurement Unit

A measurement unit combines entities and objects effectively, and reflects the traffic
conditions of a type of measurement objects. For example, the unit Office Direction
Incoming Traffic details the traffic of an incoming call.
1-1
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 1 Overview
1.3 Relationship Between Measurement Object and

Measurement Unit
The measurement object is related to the measurement unit, which determines the type
of a measurement object. A measurement unit corresponds to one type or multiple
types of objects. For example, in the measurement unit Office Direction Outgoing Office
Traffic, the object type is outgoing office direction, including some object instances like
office direction 1, office direction 2 and office direction 3. Each object type can be
displayed by multiple object instances. As some measurement units are used to
measure the whole system, the objects need not to be chosen separately, like Outgoing
Traffic and Incoming Traffic.
1.4 Measurement Entity

The measurement entity, also named counter, refers to a certain amount (for example,
traffic, count of calls and average seizure time) to be collected in order to complete a
measurement.
It consists of original entity and customized entity.
z Original entity: refers to the entity defined by the system. For example, count of
call attempts and seizure traffic.
z Customized entity: refers to the entity customized through formula on the basis of
the original entity.
The customized entity covers two cases:
z It is a new entity defined by the user, that is, both the entity name and formula are
customized by the user.
z It uses the name of the original entity, while the new formula defined by the user
covers the result of the original entity. This kind of customized entity is also called
redefined entity.
1-2
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 2 MSC Basic Functions
Chapter 2 MSC Basic Functions
2.1 Overview of Measurement Set

The measurement set is used to measure the MSC mobility management, such as
authentication and location management.
The measurement units are listed in the following table.
Name Description
MS_BASIC_TABLE_TRAF MSC basic table
MS_TYPE_AUTH Authentication
MS_TYPE_LOC_UP Location update
2.2 MSC Basic Table

2.2.1 Overview of MS_BASIC_TABLE_TRAF
The names and meanings of the measurement entities are listed in the following table.
Name Description
NCU134 Count of level updates
ACMCP134 Count of ciphering mode setting requests
SCMCP134 Count of ciphering mode setting successes

AIHLRR134 Count of routing information requests
SIHLR134 Count of successes in receiving roaming numbers
Count of successes in receiving forwarded-to
SIHLRC134
numbers
AOMOPP134 Count of sent MO short messages

SOMOPP134 Count of successful MO short messages (sent)
AOMTPP134 Count of received MT short messages
SOMTPP134 Count of successful MT short messages (received)
TMMSIT134 Count of use of TMSI at MM layer
TMMSII134 Count of use of IMSI at MM layer
ATRA134 Count of TMSI reallocation requests
STRA134 Count of TMSI reallocation successes
2-1
Name Description
IDP134 Count of IMSI detachments
IAP134 Count of IMSI attachments
PG134 Count of pagings
PGRSP134 Count of paging responses
SORBQ Count of SOR basic call requests
SORBS Count of successes of SOR basic call
SOREFQ Count of SOR early forward call requests
SOREFS Count of successes of SOR early forward call
SORLFQ Count of SOR late forward call requests
SORLFS Count of successes of SOR late forward call
ISR134 Count of SOR requests for routing
AMSR134 Count of SOR requests for MSRN
ISM134 Count of receiving MSRN during SOR routing
AMSS134 Count of successes of SOR for MSRN
2.2.2 Count of Level Updates
I. Entity Name
NCU134
II. Description
It is the count of level updates initiated by MSs or the count of queries on MS level by
the MSC in the dedicated mode.
III. Measurement Point
It is measured when the MSC receives the message BSSMAP CLASSMARK_UPDATE

from the BSC. See point A in the following figure.
2-2
BSC MSC Server
BSSMAP
CLASSMARK_UPDATE
IV. Formula
None
2.2.3 Count of Ciphering Mode Setting Requests
I. Entity Name
ACMCP134
II. Description
It is the count of ciphering procedures enabled by the MSC/VLR.
It is measured when the MSC sends the message

RN_SECURITY_MODE_COMMAND or Cipher_Mode_Command. See point A in the
following figure.
In 2G networks:
2-3
BSC MSC Server
LOCATION_UPD_REQ/
CM_Service_Request
A
Cipher_Mode_Command
In 3G networks:
RNC MSC Server
RN_MM_LOCATION_UPD
ATION_REQUEST/
RN_MM_CM_SERVICE_R
EQUEST
A
RN_SECURITY_MODE_C
OMMAND
IV. Formula
None
2.2.4 Count of Ciphering Mode Setting Successes
I. Entity Name
SCMCP134
II. Description
It is the count of successes in implementing the ciphering procedures enabled by the

MSC/VLR.
2-4
It is measured when the MSC receives the message SECURITY_MODE_COMPLETE

or Cipher_Mode_Complete. See point A in the following figure.
In 2G networks:
BSC MSC Server
Cipher_Mode_Complete
A
Release/
CM_Service_Accept
In 3G networks:
RNC MSC Server
SECURITY_MODE_COM
PLETE
IU_RELEASE_COMMAND/
A
RN_MM_CM_SERVICE_A
CCEPT
IV. Formula
None
2.2.5 Count of Routing Information Requests
I. Entity Name
AIHLRR134
2-5
II. Description
It is the count of routing information requests sent by the MSC to the HLR.

SEND_ROUTING_INFORMATION_REQ to the HLR. See point A in the following
figure.
MSC Server HLR
SEND_ROUTING_INFORMATION_REQ
A
SEND_ROUTING_INFORMATION_RSP
IV. Formula
None
2.2.6 Count of Successes in Receiving Roaming Numbers
I. Entity Name
SIHLR134
II. Description
It is the count of receipts of MSRNs from the HLR after the MSC sends the message
SEND_ROUTING_INFORMATION_REQ.
It is measured when the MSC receives the message

SEND_ROUTING_INFORMATION_RSP (including MSRN) from the HLR. See point B
in the following figure.
2-6
MSC Server HLR
A
IV. Formula
None
2.2.7 Count of Successes in Receiving Forwarded-to Numbers
I. Entity Name
SIHLRC134
II. Description
It is the count of receipts of forwarded-to numbers from the HLR after the MSC sends
the message SEND_ROUTING_INFORMATION_REQ.

SEND_ROUTING_INFORMATION_RSP (including the forwarded-to number) from the
HLR. See point B in the following figure.
MSC Server HLR
A
IV. Formula
None
2-7
2.2.8 Count of Sent MO Short Messages
I. Entity Name
AOMOPP134
II. Description
It is the count of short messages originated by mobile callers.
It is measured when the MSC receives the message CM_SERVICE_REQUEST, and

confirms that the service type is short message service. See point A in the following
figure.
RNC MSCServer SMC
CM_SERVICE_REQUEST
A
Authentication/Ciphering
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA
B
CP_ACK
IV. Formula
None
2.2.9 Count of Successful MO Short Messages (Sent)
I. Entity Name
SOMOPP134
II. Description
It is the count of successful short messages originated by mobile callers.
2-8
z It is measured when the MSC receives the message MO_FORWARD_SM_RSP

from the IWMSC, and sends the message CP_DATA to a mobile caller. See point
B in the following figure.
RNC MSCServer SMC
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA
B
CP_ACK
z It is measured when the MSC sends the message READY_FORSM_REQ to the

HLR, and receives the correct message READY_FORSM_RSP. See point B in
the following figure.
2-9
RNC MSC Serv er HLR
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
READY_FORSM_REQ
READY_FORSM_RSP
CP_DATA
B
CP_ACK
IV. Formula
None
2.2.10 Count of Received MT Short Messages
I. Entity Name
AOMTPP134
II. Description
It is the count of short messages received by mobile terminating callees.
It is measured when the MSC sends the message CP_DATA to a mobile terminating
callee. See point A in the following figure.
2-10
RNC MSCServer SMC
MT_FORWARD_SM_IND
Access of paging
A
CP_DATA
CP_ACK
CP_DATA
MT_FORWARD_SM_RSP
B
CP_ACK
IV. Formula
None
2.2.11 Count of Successful MT Short Messages (Received)
I. Entity Name
SOMTPP134
II. Description
It is the count of successful short messages received by mobile terminating callees.
It is measured when the MSC receives the message CP_ACK returned from a mobile
terminating callee. See point B in the following figure.
IV. Formula
None
2.2.12 Count of Use of TMSI at MM Layer
I. Entity Name
TMMSIT134
II. Description
It is the count of TMSIs used in transaction processing at the MM layer.
2-11
The monitored service flows include:

z CM_Re-Establishment
z CM_Service Request
z Identity Response
z IMSI detach Indication
z Location Update Accept
z Location updating request
z TMSI re-allocation command
z PAGING RESPONSE
See point A in the following figures.
In 2G networks:
BSC MSC Server
CM_Reestablishment_
Request
Assignment_Request
In 3G networks:
2-12
RNC MSC Server
RN_MM_CM_RE_ESATABLI
SHMENT_REQUEST
A
RAB_ASSIGNMENT_REQUE
ST
In 2G networks:
BSC MSC Server
CM_Service_Request
Authentication_Request
In 3G networks:
2-13
RNC MSC Server
RN_MM_CM_SERVICE_REQ
UEST
A
RN_MM_AUTHENTICATION
_REQUEST
z Identity Response
In 2G networks:
BSC MSC Server
Identity_Response
A
Location_Updating_Ac
cept
In 3G networks:
2-14
RNC MSC Server
RN_MM_IDENTITY_RESPO
NSE
A
RN_MM_LOCATION_UPDATI
NG_ACCEPT

In 2G networks:
BSC MSC Server
Imsi_Detach_Indication
Clear_Command
In 3G networks:
2-15
RNC MSC Server
RN_MM_IMSI_DETACH_IND
ICATION
IU_RELEASE_COMMAND

In 2G networks:
BSC MSC Server
Location_Updating_Request
In 3G networks:
2-16
RNC MSC Server
RN_MM_LOCATION_UPDAT
ION_REQUEST
A
RN_MM_AUTHENTICATION_
REQUEST

In 2G networks:
BSC MSC Server
CM_Service_Request
A
Tmsi_Reallocation_Command
Tmsi_Reallocation_Complete
In 3G networks:
2-17
RNC MSC Server
UEST
A
RN_MM_TMSI_REALLOCATI
ON_COMMAND
ON_COMPLETE

In 2G networks:
BSC MSC Server
A
Location_Updating_Accept
In 3G networks:
2-18
RNC MSC Server
ION_REQUEST
A
NG_ACCEPT
ON_COMPLETE
z PAGING RESPONSE
In 2G networks:
BSC MSC Server
Paging_Response
Classmark_Request
In 3G networks:
2-19
RNC MSC Server
RN_RR_PAGING_RESPONS
E
A
REQUEST
z Cipher_Mode_Complete
In 2G networks:
BSC MSC Server
A
Release/
CM_Service_Accept
In 3G networks:
2-20
RNC MSC Server
RN_MM_SECURITY_MODE_
COMPLETE
IU_RELEASE_REQUEST/ A
RN_MM_CM_SERVICE_ACC
EPT
IV. Formula
None
2.2.13 Count of Use of IMSI at MM Layer
I. Entity Name
TMMSII134
II. Description
It is the count of IMSIs used in transaction processing at the MM layer.
The monitored service flows include:

z Identity Response
z Location Update Accept
z PAGING RESPONSE
In 2G networks:
2-21
BSC MSC Server
CM_Reestablishment_
Request
Assignment_Request
In 3G networks:
RNC MSC Server
RN_MM_CM_RE_ESATABLI
SHMENT_REQUEST
A
RAB_ASSIGNMENT_REQUE
ST
In 2G networks:
2-22
BSC MSC Server
CM_Service_Request
In 3G networks:
RNC MSC Server
UEST
A
RN_MM_AUTHENTICATION
_REQUEST
z Identity Response
In 2G networks:
2-23
BSC MSC Server
Identity_Response
A
cept
In 3G networks:
RNC MSC Server
RN_MM_IDENTITY_RESPO
NSE
A
NG_ACCEPT

In 2G networks:
2-24
BSC MSC Server
Clear_Command
In 3G networks:
RNC MSC Server
RN_MM_IMSI_DETACH_IND
ICATION
IU_RELEASE_COMMAND

In 2G networks:
2-25
BSC MSC Server
In 3G networks:
RNC MSC Server
ION_REQUEST
A
REQUEST

In 2G networks:
2-26
BSC MSC Server
CM_Service_Request
A
Tmsi_Reallocation_Command
In 3G networks:
RNC MSC Server
UEST
A
ON_COMMAND
ON_COMPLETE
2-27
BSC MSC Server
A
In 3G networks:
RNC MSC Server
ION_REQUEST
A
NG_ACCEPT
ON_COMPLETE
z PAGING RESPONSE
In 2G networks:
2-28
BSC MSC Server
Paging_Response
Classmark_Request
In 3G networks:
RNC MSC Server
RN_RR_PAGING_RESPONS
E
A
REQUEST
z Cipher_Mode_Complete
In 2G networks:
2-29
BSC MSC Server
A
Release/
CM_Service_Accept
In 3G networks:
RNC MSC Server
COMPLETE
IU_RELEASE_REQUEST/ A
EPT
IV. Formula
None
2.2.14 Count of TMSI Reallocation Requests
I. Entity Name
ATRA134
II. Description
It is the count of requests for TMSI reallocation initiated in the MM common procedure.
2-30
z It is measured when the MSC sends the message Location_Updating_Accept to

the MS, that is, the location update procedure contains TMSI reallocation. See
point A in the following figures.
In 2G networks:
BSC MSC Server
Location_Updating_Re
quest
A
cept
Tmsi_Reallocation_Co
mplete
In 3G networks:
RNC MSC Server
RN_MM_LOCATION_
UPDATION_REQUES
T
RN_MM_LOCATION_ A
UPDATING_ACCEPT
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
z It is measured when the MSC sends the message Tmsi_Reallocation_Command

to the MS. See point A in the following figures.
In 2G networks:
2-31
BSC MSC Server
CM_Service_Request
mmand
A
mplete
In 3G networks:
RNC MSC Server
RN_MM_CM_SERVIC
E_REQUEST
RN_MM_TMSI_REAL
LOCATION_COMMA
ND
A
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
IV. Formula
None
2.2.15 Count of TMSI Reallocation Successes
I. Entity Name
STRA134
II. Description
It is the count of successful TMSI reallocations initiated in the MM common procedure.
2-32
It is measured when the MSC receives the message Tmsi_Reallocation_Complete

from the MS. See point A in the following figures.
z During a location update
In 2G networks:
BSC MSC Server
mplete
Release
In 3G networks:
RNC MSC Server
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
IU_RELEASE_COMM A
AND
z During a service request

In 2G networks:
2-33
BSC MSC Server
mplete
A
CM_Service_Accept
In 3G networks:
RNC MSC Server
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
RN_MM_CM_SERVIC A
E_ACCEPT
IV. Formula
None
2.2.16 Count of IMSI Detachments
I. Entity Name
IDP134
II. Description
It is the count of IMSI detachments due to power-off.
2-34
It is measured when the MSC receives the message IMSI DETACH IND from the MS.
In 2G networks:
BSC MSC Server
Release
In 3G networks:
RNC MSC Server
RN_MM_IMSI_DETACH_
INDICATION
IU_RELEASE_COMMAND
IV. Formula
None
2.2.17 Count of IMSI Attachments
I. Entity Name
IAP134
2-35
II. Description
It is the count of IMSI attachments due to power-on, SIM card insertion, and access to
service coverage areas.
It is measured when the MSC receives from the MS the message

LOCATION_UPDATE_REQUEST, which indicates the IMSI is activated
(IMSI_ATTACH_UPDATE). See point A in the following figures.
In 2G networks:
BSC MSC Server
Location_Updating_Requ
est
In 3G networks:
RNC MSC Server
RN_MM_LOCATION_UP
DATION_REQUEST
A
RN_MM_AUTHENTICATI
ON_REQUEST
IV. Formula
None
2-36
2.2.18 Count of Pagings
I. Entity Name
PG134
II. Description
It is the count of pagings sent from the MSC, and it is measured once for multiple
pagings of a call.
It is measured when the MSC sends the PAGING message. See point A in the following
figure.
RNS MSC Server
PAGING
……
A
PAGING
PAGING RESPONSE
IV. Formula
None
2.2.19 Count of Paging Responses
I. Entity Name
PGRSP134
II. Description
It is the count of PAGING RESPONSE messages received by the MSC from callees
after the MSC sends the PAGING message.
2-37
It is measured when the MSC receives the message Paging Response. See point A in
RNS MSC Server
PAGING
PAGING RESPONSE
AUTHENTICATION REQUEST
IV. Formula
None
2.2.20 Count of SOR Basic Call Requests
I. Entity Name
SORBQ
II. Description
It is the count of roaming queries during basic SOR calls.
It is measured when the GMSCA initiates the SOR queries. See point A in the following
figure.
2-38
GMSCA HLRB
A SRI
IV. Formula
None
2.2.21 Count of Successes of Basic SOR Call
I. Entity Name
SORBS
II. Description
It is the count of successful basic SOR calls.
It is measured when MSRN is returned and the outgoing call is made during the SOR
query in the GMSCA. See point A in the following figure.
2-39
GMSCA HLRB VMSCB
SRI ack
IAM
IV. Formula
None
2.2.22 Count of SOR Early Forward Call Requests
I. Entity Name
SOREFQ
II. Description
It is the count of requests for SOR early forwarded calls.
It is measured in course of supplementary service call forwarding or call forwarding

controlled by SCP during the SOR query in the GMSCA. See point A in the following
figure.
2-40
GMSCA HLRB
A SRI
IV. Formula
None
2.2.23 Count of Successes of SOR Early Forward Call
I. Entity Name
SOREFS
II. Description
It is the count of successes in the early forwarded call.
It is measured when the supplementary service or the IN call is forwarded on the

condition that they satisfy the early forward charging principle during the SOR query in
the GMSCA. See point A in the following figure.
2-41
GMSCA HLRB LEC
SRI ack(FTN)
IAM
IV. Formula
None
2.2.24 Count of SOR Late Forward Call Requests
I. Entity Name
SORLFQ
II. Description
It is the count of SOR requests for late forwarded calls.
It is measured when the GMSCA receives resume call handling (RCH) requests from
the VMSCB. See point A in the following figure.
2-42
GMSCA VMSCB
RCH
IV. Formula
None
2.2.25 Count of Successes of SOR Late Forward Call
I. Entity Name
SORLFS
II. Description
It is the successes in the late forwarded call.
It is measured when the GMSCA returns the message RCH ACK to the VMSCB after
receiving the RCH request from the VMSCB and ensuring that the SOR late forwarded
conditions are satisfied. See point A in the following figure.
2-43
GMSCA VMSCB
RCH
RCH ACK
IV. Formula
None
2.2.26 Count of SOR Requests for Routing
I. Entity Name
ISR134
II. Description
It is the count of SOR requests for routing.
It is measured if the optimal routing (OR) indication is TRUE when the MSC sends the
routing request. See point A in the following figure.
2-44
GMSC HLR VLR
SRI Req
With OR flag bit PRN Req
A
With OR flag bit
B
PRN Rsp
SRI Rsp
C
D
IV. Formula
None
2.2.27 Count of SOR Requests for MSRN
I. Entity Name
AMSR134
II. Description
It is the count of SOR requests for MSRN.
It is measured if the OR indication is TRUE when the called MAP sends the request for
MSRN to the VDB. See point B in the following figure.
2-45
GMSC HLR VLR
SRI Req
A
With OR flag bit
B
PRN Rsp
SRI Rsp
C
D
IV. Formula
None
2.2.28 Count of Receiving MSRN During SOR Routing
I. Entity Name
ISM134
II. Description
It is the count of received messages containing MSRN during SOR routing.
It is measured if the routing response message contains MSRN when the OR indication
is TRUE. See point C in the following figure.
2-46
GMSC HLR VLR
SRI Req
A
With OR flag bit
B
PRN Rsp
SRI Rsp
C
D
IV. Formula
None
2.2.29 Count of Successes of SOR for MSRN
I. Entity Name
AMSS134
II. Description
It is the count of successes of SOR applying for MSRN.
It is measured when the OR indication is TRUE and the MAP succeeds in requesting
MSRN. See point D in the following figure.
2-47
GMSC HLR VLR
SRI Req
A
With OR flag bit
B
PRN Rsp
SRI Rsp
C
D
IV. Formula
None
2.3 Authentication
2.3.1 Overview of MS_TYPE_AUTH
Name Description
SAIHT20 Count of authentication set requests to HLR
SRASH20 Count of authentication set receipts from HLR
REASHT20 Count of empty authentication set receipts from HLR
SIPT20 Count of authentication set requests to PVLR
SRASPT20 Count of authentication set receipts from PVL
ART20 Count of authentication requests
ST20 Count of successful authentications
IST20 Count of authentication failures due to illegal SRES
ARTT20 Count of authentication requests with TMSI
Count of authentication failures due to illegal SRES (with
ISATT20
TMSI)
Count of successful authentications after IMSI being
SAIIT20
identified
ANRSP20 Count of failures in responding to authentication requests
2-48
Name Description
SRFDA20 Count of failure responses to authentication requests
2.3.2 Count of Authentication Set Requests to HLR
I. Entity Name
SAIHT20
II. Description
It is the count of requests for authentication sets sent by the VLR to the HLR.
It is measured when the MSC sends to the HLR the message

SEND_AUTHENTICATION_ INFO_REQ. See point A in the following figure.
MSC Server HLR
SEND_AUTHENTICATION_INFO_REQ
A
SEND_AUTHENTICATION_INFO_RSP
IV. Formula
None
2.3.3 Count of Authentication Set Receipts from HLR
I. Entity Name
SRASH20
II. Description
It is the count of authentication sets received by the VLR from the HLR.
2-49
It is measured when the MSC/VLR receives from the HLR the message
SEND_AUTHENTICATION_INFO_RSP (if an authenciation set is contained). See
point B in the following figure.
MSC Server HLR
A
IV. Formula
None
2.3.4 Count of Empty Authentication Set Receipts from HLR
I. Entity Name
REASHT20
II. Description
It is the count of empty authentication sets received by the VLR from the HLR.
It is measured when the MSC/VLR receives from the HLR the message
SEND_AUTHENTICATION_INFO_RSP (if an empty authentication set is contained).
See point B in the following figure.
2-50
MSC Server HLR
A
IV. Formula
None
2.3.5 Count of Authentication Set Requests to PVLR
I. Entity Name
SIPT20
II. Description
It is the count of requests for authentication sets from the VLR to the PVLR. When MSs
register in the new VLR with TMSIs allocated in the previous VLR (PVLR), the new VLR
receives the IMSIs and authentication parameter from PVLR before sending the update
requests to the HLR.
The VLR sends the message MAP/G MAP_SEND_IDENTIFICATION to the PVLR.

See point A in the following figure.
MSC Server PVLR
SEND_IDENTIFICATION_REQ
A
SEND_IDENTIFICATION_RSP
IV. Formula
None
2-51
2.3.6 Count of Authentication Set Receipts from PVLR
I. Entity Name
SRASPT20
II. Description
It is the count of successes in receiving authentication sets from the PVLR (that is, the
authentication sets received from the PVLR are not empty). When MSs register in the
new VLR with TMSIs allocated in the previous VLR (PVLR), the new VLR receives the
IMSIs and authentication parameter from PVLR before sending the update request to
the HLR.
It is measured when the VLR receives the message MAP/G

MAP_SEND_IDENTIFICATION ACK from the PVLR. See point B in the following
figure.
MSC Server PVLR
SEND_IDENTIFICATION_REQ
A
SEND_IDENTIFICATION_RSP
IV. Formula
None
2.3.7 Count of Authentication Requests
I. Entity Name
ART20
II. Description
It is the count of authentication requests from the VLR. Either TMSI or IMSI can be used
in the requests.
2-52
It is measured when the MSC sends the message AUTHENTICATION_REQUEST to

the UE (MS) after receiving the message MAP/B AUTHENTICATION_REQUEST from
the VLR. See point A in the following figure.
UE MSC Server
AUTHENTICATION_REQUEST
AUTHENTICATION_RESPONSE
IV. Formula
None
2.3.8 Count of Successful Authentications
I. Entity Name
ST20
II. Description
It is the count of successful XRES and SRES authentications in the VLR after the MSC
receives the message Authentication Response (including XRES and SRES) from the
MS and forwards it to the VLR. Either IMSI or TMSI can be used in the authentications.
It is measured when the MSC sends the message MAP/B

AUTHENTICATION_RESPONSE to the VLR, and the VLR returns the related MAP
message after it succeeds in SRES authentication. See point B in the following figure.
2-53
UE MSC Server
IV. Formula
None
2.3.9 Count of Authentication Failures Due to Illegal SRES
I. Entity Name
IST20
II. Description
It is the count of authentication failures due to the illegal message Authentication

Response from mobile subscribers.
It is measured when the MSC fails to check the message

AUTHENTICATION_RESPONSE after receiving it. See point B in the following figure.
UE MSC Server
IV. Formula
None
2-54
2.3.10 Count of Authentication Requests with TMSI
I. Entity Name
ARTT20
II. Description
It is the count of authentication requests by the VLR after MSs send the service
requests with TMSIs.
It is measured when the MSC sends the message Authentication Request to an MS

(using TMSI authentication) after receiving the message MAP/B
AUTHENTICATION_REQUEST from the VLR. See point A in the following figure.
UE MSC Server
IV. Formula
None
2.3.11 Count of Authentication Failures Due to Illegal SRES (with TMSI)
I. Entity Name
ISATT20
II. Description
It is the count of failures of SRES authentication in the VLR after the MSC receives the
message Authentication Response (including SRES) from MSs and sends it to the VLR.
TMSIs are used for the authentications.
It is measured when the VLR returns the message Provide IMSI to the MSC after
receiving the message MAP/B AUTHENTICATION_RESPONSE and detecting the
illegal SRES. See point B in the following figure.
2-55
UE MSC Server
IV. Formula
None
2.3.12 Count of Successful Authentications After IMSI Being Identified
I. Entity Name
SAIIT20
II. Description
It is the count of successful authentications with IMSIs after the TMSI authentication
fails.

message (for legal subscribers, service is accepted; for illegal subscribers, service is
rejected) after it succeeds in SRES authentication. The premise is that the
authentication is just performed.
It is measured when the message Authentication Response received by the MSC is
sent from a legal subscriber, that is, when the IMSI authentication succeeds. See point
2-56
UE MSC Server
IDENTITY_REQUEST
IDENTITY_RESPONSE
A
IV. Formula
None
2.3.13 Count of Failures in Responding to Authentication Requests
I. Entity Name
ANRSP20
II. Description
It is the count of failures in receiving the message Authentication Response from UEs
in the specified time.
It is measured when the MSC times out in waiting for the message Authentication
Response from a UE. See point A in the following figure.
2-57
UE MSC Server
IV. Formula
None
2.3.14 Count of Failure Responses to Authenication Requests
I. Entity Name
SRFDA20
II. Description
It is the count of the AUTHENTICATION_FAILURE messages returned from UEs

during authentication.
It is measured when a UE returns the message MAC Failure or Synch Failure. See
point A in the following figure.
UE MSC Server
AUTHENTICATION_FAILURE
IV. Formula
None
2-58
2.4 Location Update

2.4.1 Overview of MS_TYPE_LOC_UP
Name Description
NOLUREQ Count of location update requests
NOLUREJ Count of location update rejections
NOID Count of IMSI detachments

NOIA Count of IMSI attachments
LUIVRT19 Count of location update requests in VLR
SLUIVT19 Count of location update successes in VLR

Count of location update requests due to subscriber
STIVRT19
roaming
Count of location update successes due to subscriber
SSLUIVT19
roaming
Count of location update successes due to national

MSNRUR19
roaming
Count of location update successes due to

MSIRUR19
international roaming
Count of location update failures due to unknown user
HUUULF
in HLR
IUULF Count of location update failures due to illegal MS

Count of location update failures due to IMEI check
IEULF
failure
Count of location update failures due to PLMN
PPAULF
denying access
Count of location update failures due to prohibition of
LPULF
location area
Count of location update failures due to roaming
RPULF
prohibition
Count of location update failures due to protocol
PEULF
failure
Count of location update failures due to network
NFULF
failure
NLPULF
location area in network
NSCULF
cell in location area
2-59
Name Description
OCULF Count of location update failures due to other causes
ISDT19 Count of attempts to insert user data
SISDT19 Count of successes in inserting user data
ARD Count of location update failures due to ARD
2.4.2 Count of Location Update Requests
I. Entity Name
NOLUREQ
II. Description
It is the count of requests for location update initiated by mobile subscribers, including
general location update and periodic location update.
It is measured when the MSC receives the message LOCATION UPDATE REQUEST
from a mobile subscriber. See point A in the following figure.
UE MSC Server
LOCATION_UPDATING_REQUEST
A
LOCATION_UPDATING_ACCEPT
IV. Formula
None
2.4.3 Count of Location Update Rejections
I. Entity Name
NOLUREJ
II. Description
It is the count of rejections to location update requests by mobile subscribers.
2-60
It is measured when the MSC sends the message LOCATION UPDATE REJECT to a
mobile subscriber. See point B in the following figure.
UE MSC Server
A
LOCATION_UPDATING_REJECT
IV. Formula
None
2.4.4 Count of IMSI Detachments
I. Entity Name
NOID
II. Description
It is the count of IMSI detachments due to power-off by mobile subscribers.
It is measured when the MSC receives the message IMSI DETACH IND from a mobile
subscriber. See point A in the following figure.
UE MSC Server
IMSI_DETACH_IND
IV. Formula
None
2-61
2.4.5 Count of IMSI Attachments
I. Entity Name
NOIA
II. Description
It is the count of IMSI attachments due to power-on, SIM card insertion, and access to
service coverage areas.
It is measured when the MSC receives from a mobile subscriber the message
LOCATION UPDATE REQUEST, which indicates that the IMSI is activated (IMSI
ATTACH UPDATE). See point A in the following figure.
UE MSC Server
A
IV. Formula
None
2.4.6 Count of Location Update Requests in VLR
I. Entity Name
LUIVRT19
II. Description
It is the count of requests for location update after mobile subscribers register in the
local VLR.
It is measured when the MSC sends the message MAP_UPDATE_LOCATION_AREA

to the VLR, and receives the message LOCATION_UPDATING_REQ from a local
mobile subscriber. See point A in the following figure.
2-62
UE MSC Server
A
IV. Formula
None
2.4.7 Count of Location Update Successes in VLR
I. Entity Name
SLUIVT19
II. Description
It is the count of successful location updates in the VLR.

MAP_UPDATE_LOCATION_AREA ACK from the VLR, and the location of a roaming
subscriber is updated successfully. See point B in the following figure.
UE MSC Server
A
IV. Formula
None
2.4.8 Count of Location Update Requests Due to Subsriber Roaming
I. Entity Name
STIVRT19
2-63
II. Description
It is the count of requests for location updates when mobile subscribers roam to the
local VLR service area (they have not registered in the local VLR for location update).
It is measured when the MSC sends the message MAP_UPDATE_LOCATION_AREA

to the VLR, and receives the request for location update from a mobile subscriber, who
roams between VLRs. See point A in the following figure.
UE MSC Server
A
IV. Formula
None
2.4.9 Count of Location Update Successes Due to Subsriber Roaming
I. Entity Name
SSLUIVT19
II. Description
It is the count of successful location updates when mobile subscribers roam to the local
VLR service area.

MAP_UPDATE_LOCATION_AREA ACK from the VLR, and the location of a mobile
subscriber roaming between VLRS is updated successfully. See point B in the following
figure.
2-64
UE MSC Server
A
IV. Formula
None
2.4.10 Count of Location Update Successes Due to National Roaming
I. Entity Name
MSNRUR19
II. Description
It is the count of successful location updates when national mobile subscribers roam to
the local VLR.

subscriber (a national roaming subscriber in different PLMNs) is updated successfully.
UE MSC Server
A
IV. Formula
None
2.4.11 Count of Location Update Successes Due to International Roaming
I. Entity Name
MSIRUR19
2-65
II. Description
It is the count of location update successes when international mobile subscribers roam
to the local VLR.

subscriber (an international roaming subscriber in different PLMNs) is updated
successfully. See point B in the following figure.
UE MSC Server
A
IV. Formula
None
2.4.12 Count of Location Update Failures Due to Unknown User in HLR
I. Entity Name
HUUULF
II. Description
It is the count of location update failures caused when the HLR cannot identify mobile
subscribers.
It is measured when the MSC sends to a mobile subscriber the message LOCATION
UPDATE REJECT (it contains cause#2, IMSI Unknown In HLR). See point A in the
following figure.
2-66
UE MSC Server UE
LOCATION_UPDATION_REQUEST
UPDATE_LOCATION_REQ
UPDATE_LOCATION_RSP
A
IV. Formula
None
2.4.13 Count of Location Update Failures Due to Illegal MS
I. Entity Name
IUULF
II. Description
It is the count of location update failures due to illegal mobile subscribers.
UPDATE REJECT (it contains cause#3, Illegal MS). See point B in the following figure.
UE MSC Server
A
IV. Formula
None
2.4.14 Count of Location Update Failures Due to IMEI Check Failure
I. Entity Name
IEULF
2-67
II. Description
It is the count of location update failures due to failure in IMEI authentication.
UPDATE REJECT (it contains cause#6, Illegal IMEI). See point B in the following
figure.
UE MSC Server
A
IV. Formula
None
2.4.15 Count of Location Update Failures Due to PLMN Denying Access
I. Entity Name
PPAULF
II. Description
It is the count of location update failures caused when the local PLMN denies the
access of mobile subscribers.
UPDATE REJECT (it contains cause#11, PLMN not allow). See point B in the following
figure.
2-68
UE MSC Server
A
IV. Formula
None
2.4.16 Count of Location Update Failures Due to Prohibition of Location

Area
I. Entity Name
LPULF
II. Description
It is the count of location update failures due to the denial of the location areas.
UPDATE REJECT (it contains cause#12, Local Area not allowed). See point B in the
following figure.
UE MSC Server
A
IV. Formula
None
2.4.17 Count of Location Update Failures Due to Roaming Prohibition
I. Entity Name
RPULF
2-69
II. Description
It is the count of location update failures caused when roaming is restricted in the
location area.
UPDATE REJECT (it contains cause#13, Roaming not allowed in this location area).
UE MSC Server
A
IV. Formula
None
2.4.18 Count of Location Update Failures Due to Protocol Failure
I. Entity Name
PEULF
II. Description
It is the count of location update failures due to the protocol failure. The protocol failure
is caused by the follow reasons:
z #96: Mandatory information element error
z #99: Information element non-existent or not implemented
z #100: Conditional IE error
z #111: Protocol error, unspecified
UPDATE REJECT (it contains cause values that entail location update rejection). See
2-70
UE MSC Server
A
IV. Formula
None
2.4.19 Count of Location Update Failures Due to Network Failure
I. Entity Name
NFULF
II. Description
It is the count of location update failures due to the network failure.
UPDATE REJECT (it contains cause#11, Network failure). See point B in the following
figure.
UE MSC Server
A
IV. Formula
None

Area in PLMN
I. Entity Name
NLPULF
2-71
II. Description
It is the count of location update failures due to denial of the location areas in a PLMN.
UPDATE REJECT (it contains cause#13, nation roam not allow). See point B in the
following figure.
RNC MSC Server
LOCATION_UPDATE_REQUEST
LOCATION_UPDATE_REJECT
Cause:Nation Roam Not Allowed B
IV. Formula
None

Area Cell
I. Entity Name
NSCULF
II. Description
It is the count of location update failures due to denial of location area cells.
UPDATE REJECT (it contains cause#15, No suitable cells in location area). See point
2-72
RNC MSC Server
Cause:No Suitable Cells in B

Location Area
IV. Formula
None
2.4.22 Count of Location Update Failures Due to Other Causes
I. Entity Name
OCULF
II. Description
It is the count of location update failures due to other causes.
UPDATE REJECT (it contains other causes). See point B in the following figure.
UE MSC Server
A
IV. Formula
None
2-73
2.4.23 Count of Attempts to Insert User Data
I. Entity Name
ISDT19
II. Description
It is the count of attempts to insert user data to the VLR indicated by the HLR after the
locations of roaming subscribers are updated or the user data in the HLR is modified.
It is measured when the VLR receives the message MAP/D Insert Subscriber data from
the HLR, and the MSC sends the message INSERT_SUBSCRIBER_DATA_REQ after
receiving UPDATA_LOCATION_CNF from the HLR. See point A in the following figure.
UE MSC Server UE
UPDATE_LOCATION_REQ
INSERT_SUBSCRIBER_DATA_REQ
A
INSERT_SUBSCRIBER_DATA_RSP
B
UPDATE_LOCATION_RSP
IV. Formula
None
2.4.24 Count of Sucesses in Inserting User Data
I. Entity Name
SISDT19
II. Description
It is the count of successes in inserting user data to the VLR indicated by the HLR after
the locations of roaming subscribers are updated or the user data in the HLR is
modified.
2-74
z It is measured when the VLR receives the message MAP/D Insert Subscriber data
from the HLR, and returns MAP/D Insert Subscriber data ACK.
z It is measured when the MSC receives the message UPDATA_LOCATION_CNF
from the HLR and returns INSERT_SUBSCRIBER_DATA_REP.
UE MSC Server UE
UPDATE_LOCATION_REQ
INSERT_SUBSCRIBER_DATA_REQ
A
INSERT_SUBSCRIBER_DATA_RSP
B
UPDATE_LOCATION_RSP
IV. Formula
None
2.4.25 Count of Location Update Failures Due to ARD
I. Entity Name
ARD
II. Description
It is the count of location update failures due to the access restriction in updating
locations.
It is measured when the MSC sends the message LOCATION UPDATE REJECT to the
MS. See point A in the following figure.
Its cause value is determined by the "Cause value of location update reject due to ARD"
configured in the Data Configuration. The message contains any one of the following
cause values:
z Cause#11 Network failure
z Cause#12 Local Area not allowed
2-75
z Cause#13 Roaming not allowed in this location area

z Cause#15 No Suitable Cells In Location Area
RNC MSC Server
LOCATION_UPDATE_REQ
LOCATION_UPDATE_REJ
IV. Formula
None
2-76
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 MSC Basic Services
Chapter 3 MSC Basic Services

This measurement is used to measure the traffic of MSC basic services like handover
and short message service (SMS).
Name Description
MS_HO_2PLMN Handover between two PLMNs
MS_S_ASSIGN_TRAF GSM assignment
MS_S_MSC_HO MSC handover
MS_S_TMSI_REALLOC_TRAF TMSI reallocation

MS_S_ASSIGN_3G_TRAF WCDMA assignment
MS_TYPE_SMS Short message service
MS_S_CELL_HO_TRAF GSM cell handover
MS_S_RNC_RELOCATION WCDMA RNC handover
MS_S_CIPHER_TRAF Ciphering mode setting
MS_S_PAGING_TRAF Paging
3.2 Handover Between Two PLMNs

3.2.1 Overview of MS_HO_2PLMN
Name Description
INTMSC Count of ultrashort inter-MSC handovers between two PLMNs
DINTMSC Duration of ultrashort inter-MSC handovers between two PLMNs
INMSCB Count of ultrashort intra-MSCb handovers between two PLMNs
DINMSCB Duration of ultrashort intra-MSCb handovers between two PLMNs
INTBSC Count of ultrashort inter-BSC handovers between two PLMNs
DINTBSC Duration of ultrashort inter-BSC handovers between two PLMNs
INBSC Count of ultrashort intra-BSC handovers between two PLMNs
DINBSC Duration of ultrashort intra-BSC handovers between two PLMNs
3-1
3.2.2 Count of Ultrashort Inter-MSC Handovers Between Two PLMNs
I. Entity Name
INTMSC
II. Description
It is the count of ultrashort inter-MSC handovers between two PLMNs.
It is measured when the following conditions are met:

z Basic outgoing handover or subsequent handover back to MSCa or a third party
succeeds.
z The handover is judged as a cross-PLMN one.
z The resident duration in the last PLMN is shorter than the threshold preset in the
system.
MSC-A MSC-B MSC-C
MAP-Prep-Handover req
MAP-Prep-Handover resp
MAP-Send-End-Sig req
HO Duration
MAP-Prep-Sub-Handover req
A
IV. Formula
None
3.2.3 Duration of Ultrashort Inter-MSC Handovers Between Two PLMNs
I. Entity Name
DINTMSC
II. Description
It is the duration of ultrashort inter-MSC handovers between two PLMNs.
3-2

z Basic outgoing handover or subsequent handover back to MSCa or a third party
succeeds.
z The handover is judged as a cross-PLMN one.
system.
MSC-A MSC-B MSC-C
HO Duration
MAP-Prep-Sub-Handover req
A
IV. Formula
None
3.2.4 Count of Ultrashort Intra-MSCb Handovers Between Two PLMNs
I. Entity Name
INMSCB
II. Description
It is the count of ultrashort handovers between two PLMNs in a non main control MSC.

z The MSCa receives the message MAP-Process-Access-Sig req from MSCb and
judges the handover as a cross-PLMN one.
system.
3-3
MSC-A MSC-B
MAP-Process-Access-Sig req
IV. Formula
None
3.2.5 Duration of Ultrashort Intra-MSCb Handovers Between Two PLMNs
I. Entity Name
DINMSCB
II. Description
It is the duration of ultrashort handovers between two PLMNs in a non main control
MSC.

z The MSCa receives the message MAP-Process-Access-Sig req from MSCb and
system.
3-4
MSC-A MSC-B
MAP-Process-Access-Sig req
IV. Formula
None
3.2.6 Count of Ultrashort Inter-BSC Handovers Between Two PLMNs
I. Entity Name
INTBSC
II. Description
It is the count of ultrashort inter-BSC handovers between two PLMNs in a main control
MSC.

z The MSC receives the message A-HANDOVER-COMPLETE from the terminating
BSC and judges the handover as a cross-PLMN one.
system.
3-5
BSC MSC
A-Handover-Complete
IV. Formula
None
3.2.7 Duration of Ultrashort Inter-BSC Handovers Between Two PLMNs
I. Entity Name
DINTBSC
II. Description
It is the duration of ultrashort inter-BSC handovers between two PLMNs in a main

control MSC.

z The MSC receives the message A-HANDOVER-COMPLETE from the terminating
BSC and judges the handover as a cross-PLMN one.
z The resident duration in the last PLMN is shorter than the preset threshold in the
system.
3-6
BSC MSC
A-Handover-Complete
IV. Formula
None
3.2.8 Count of Ultrashort Intra-BSC Handovers Between Two PLMNs
I. Entity Name
INBSC
II. Description
It is the count of ultrashort intra-BSC handovers between two PLMNs in a main control
MSC.

z The MSC receives the message A-HANDOVER-PERFORMED from the BSC and
system.
3-7
BSC MSC
A-Handover-Performed
IV. Formula
None
3.2.9 Duration of Ultrashort Intra-BSC Handovers Between Two PLMNs
I. Entity Name
DINBSC
II. Description
It is the duration of ultrashort intra-BSC handovers between two PLMNs in a main

control MSC.

z The MSC receives the message A-HANDOVER-PERFORMED from the BSC and
system.
3-8
BSC MSC
A-Handover-Performed
IV. Formula
None
3.3 GSM Assignment

3.3.1 Overview of MS_S_ASSIGN_TRAF
Name Description
ACR119 Count of requests for traffic channel assignments
SSC119 Count of successful traffic channel assignments
Count of traffic channel assignment failures due to radio
FFRMF119
interface message failure
Count of traffic channel assignment failures due to O&M

FFOAM119
intervention
Count of traffic channel assignment failures due to

FFEF119
equipment failure
FFNR119
resource unavailable

FFTRU119
requested terrestrial resource unavailable
FFTRRU119
requested transcoding/rate adaptation unavailable

FFTRA119
terrestrial resource already allocated

FFIM119
invalid message content
3-9
Name Description
FFRIF119
interface failure - reversion to old channel
FFDR119
directed retry
FFCPM119
circuit pool mismatch
FFSCP119
change of circuit group
Count of traffic channel assignment failures due to other
FFBGH119
causes
3.3.2 Count of Requests for Traffic Channel Assignments
I. Entity Name
ACR119
II. Description
It is the count of requests made by MSC to BSS (where the MS is located) for assigning
radio resources for GSM calls.
It is measured when the MSC sends the message BSSMAP ASSIGNMENT REQUEST
to the BSS.
BSS MSC Server
BSSMAP ASSIGNMENT REQUEST
A
BSSMAP ASSIGNMENT COMPLETE
IV. Formula
None
3-10
3.3.3 Count of Successful Traffic Channel Assignments
I. Entity Name
SSC119
II. Description
It is the count of successful radio resource assignments made by the BSS (where the
MS is located) for GSM calls.
It is measured when the MSC receives the message BSSMAP ASSIGNMENT

COMPLETE from the BSS.
BSS MSC Server
A
BSSMAP ASSIGNMENT COMPLETE
IV. Formula
None
3.3.4 Count of Traffic Channel Assignment Failures Due to Radio Interface

Message Failure
I. Entity Name
FFRMF119
II. Description
It is the count of failures of the BSS (where the MS is located) assigning radio resource
requested by the MSC for GSM calls, with the cause of "radio interface message
failure".
3-11

FAILURE from the BSS, with the cause value as "radio interface message failure".
BSS MSC Server
A
BSSMAP ASSIGNMENT FAILURE
IV. Formula
None
3.3.5 Count of Traffic Channel Assignment Failures Due to O&M Intervention
I. Entity Name
FFOAM119
II. Description
requested by the MSC for GSM calls, with the cause of "O and M intervention".

FAILURE from the BSS, with the cause value as "O and M intervention".
3-12
BSS MSC Server
A
IV. Formula
None
3.3.6 Count of Traffic Channel Assignment Failures Due to Equipment

Failure
I. Entity Name
FFEF119
II. Description
requested by the MSC for GSM calls, with the cause of "equipment failure".

FAILURE from the BSS, with the cause value as "equipment failure".
BSS MSC Server
A
IV. Formula
None
3-13
3.3.7 Count of Traffic Channel Assignment Failures Due to Radio Resource

Unavailable
I. Entity Name
FFNR119
II. Description
requested by the MSC for GSM calls, with the cause of "no radio resource available".

FAILURE from the BSS, with the cause value as "no radio resource available".
BSS MSC Server
A
IV. Formula
None
3.3.8 Count of Traffic Channel Assignment Failures Due to Requested

Terrestrial Resource Unavailable
I. Entity Name
FFTRU119
II. Description
requested by the MSC for GSM calls, with the cause of "requested terrestrial resource
unavailable".
3-14

FAILURE from the BSS, with the cause value as "requested terrestrial resource
unavailable".
BSS MSC Server
A
IV. Formula
None
3.3.9 Count of Traffic Channel Assignment Failures Due to Requested

Transcoding/Rate Adaptation Unavailable
I. Entity Name
FFTRRU119
II. Description
requested by the MSC for GSM calls, with the cause of "requested transcoding/rate
adaptation unavailable".

FAILURE from the BSS, with the cause value as "requested transcoding/rate
adaptation unavailable".
3-15
BSS MSC Server
A
IV. Formula
None
3.3.10 Count of Traffic Channel Assignment Failures Due to Terrestrial

Resource Already Allocated
I. Entity Name
FFTRA119
II. Description
requested by the MSC for GSM calls, with the cause of "terrestrial resource already
allocated".

FAILURE from the BSS, with the cause value as "terrestrial resource already
allocated".
BSS MSC Server
A
IV. Formula
None
3-16
3.3.11 Count of Traffic Channel Assignment Failures Due to Invalid Message

Content
I. Entity Name
FFIM119
II. Description
requested by the MSC for GSM calls, with the cause of "invalid message contents".

FAILURE from the BSS, with the cause value as "invalid message contents".
BSS MSC Server
A
IV. Formula
None
3.3.12 Count of Traffic Channel Assignment Failures Due to Radio Interface

Failure - Reversion to Old Channel
I. Entity Name
FFRIF119
II. Description
It is the count of failures of the BSS assigning radio resource for GSM calls, with the
cause of "radio interface failure - reversion to old channel".

FAILURE from the BSS, with the cause value as "radio interface failure - reversion to
old channel".
3-17
BSS MSC Server
A
IV. Formula
None
3.3.13 Count of Traffic Channel Assignment Failures Due to Directed Retry
I. Entity Name
FFDR119
II. Description
requested by the MSC for GSM calls, with the cause of "directed retry".

FAILURE from the BSS, with the cause value as "directed retry".
BSS MSC Server
A
IV. Formula
None
3-18
3.3.14 Count of Traffic Channel Assignment Failures Due to Circuit Pool

Mismatch
I. Entity Name
FFCPM119
II. Description
requested by the MSC for GSM calls, with the cause of "circuit pool mismatch".

FAILURE from the BSS, with the cause value as "circuit pool mismatch".
BSS MSC Server
A
IV. Formula
None
3.3.15 Count of Traffic Channel Assignment Failures Due to Change of

Circuit Group
I. Entity Name
FFSCP119
II. Description
requested by the MSC for GSM calls, with the cause of "switch circuit pool".

FAILURE from the BSS, with the cause value as "switch circuit pool".
3-19
BSS MSC Server
A
IV. Formula
None
3.3.16 Count of Traffic Channel Assignment Failures Due to Other Causes
I. Entity Name
FFBGH119
II. Description
requested by the MSC for GSM calls due to other causes.

FAILURE from the BSS, with the cause value as not any one listed above.
BSS MSC Server
A
IV. Formula
None
3-20
3.4 MSC Handover

3.4.1 Overview of MS_S_MSC_HO
Name Description
TC122 Count of handovers controlled by MSC
FC122 Count of link disconnections due to handover failure
Count of calls returned to original channels due to handover
AS122
failure
TR122 Count of requests for intra-MSC handovers
TS122 Count of successful intra-MSC handovers

ROR123 Count of requests for basic outgoing handovers
ROS123 Count of successful basic outgoing handovers
HIR123 Count of requests for basic incoming handovers
HIS123 Count of successful basic incoming handovers
Count of requests for subsequent handovers back to local
RBR123
MSC (MSCa)
Count of successful subsequent handovers back to local MSC
RBS123
(MSCa)
Count of requests for subsequent handovers to MSCc (local
RCR123
MSC is MSCa)
Count of successful subsequent handovers to MSCc (local
RCS123
MSC is MSCa)
Count of requests for subsequent handovers (local MSC is
BRSR123
MSCb)
Count of successful subsequent handovers (local MSC is
BRSS123
MSCb)
3.4.2 Count of Handovers Controlled by MSC
I. Entity Name
TC122
II. Description
It is the count of requests for intra-MSC and inter-MSC handovers controlled by MSCa
and intra-MSC handovers controlled by MSCb.
3-21
It is measured when the MSC receives the message HANDOVER REQUIRED or

RELOCATION REQUIRED. (3GPP TS 25.413)
BSC\RNC MSOFTX3000
HANDOVER REQUIRED
RELOCATION REQUIRED
IV. Formula
None
3.4.3 Count of Link Disconnections Due to Handover Failure
I. Entity Name
FC122
II. Description
It is the count of link disconnections (call drops) due to during handover or relocation
procedure.
It is measured when the MSC receives the message A CLEAR REQUEST, IU

RELEASE REQUEST or RAB RELEASE REQUEST for the requested handover or
relocation. (3GPP TS 25.413)
3-22
BSC\RNC MSOFTX3000
CLEAR REQUEST
IV. Formula
None
3.4.4 Count of Calls Returned to Original Channels Due to Handover Failure
I. Entity Name
AS122
II. Description
It is the count of calls returned to original channels (TCH and SDCCH) due to handover
or relocation failures in the MSC.
It is measured when the MSC receives the message HANDOVER FAILURE,

RELOCATION FAILURE or RELOCATION CANCEL for the requested handovers or
relocations. (3GPP TS 25.413)
BSC\RNC MSOFTX3000
HANDOVER FAILURE
IV. Formula
None
3-23
3.4.5 Count of Requests for Intra-MSC Handovers
I. Entity Name
TR122
II. Description
It is the count of requests for intra-MSC (including inter-RNC and inter-BSC) handovers
or relocations.
For inter-RNC handover, it is measured when the MSC receives the message
RELOCATION REQUIRED from the originating RNC; for inter-BSC handover, it is
measured when the MSC receives the message HANDOVER REQUIRED from
BSS_A.
BSC\RNC MSOFTX3000
HANDOVER REQUIRED
RELOCATION REQUIRED
IV. Formula
None
3.4.6 Count of Successful Intra-MSC Handovers
I. Entity Name
TS122
II. Description
It is the count of successful intra-MSC (including inter-RNC and inter-BSC) handovers

or relocations.
For inter-RNC handover, it is measured when the MSC receives the message
RELOCATION COMPLETE from the terminating RNC; for inter-BSC handover, it is
3-24
measured when the MSC receives the message HANDOVER COMPLETE from
BSS_B.
BSC\RNC MSOFTX3000
HANDOVER COMPLETE
RELOCATION COMPLETE
IV. Formula
None
3.4.7 Count of Requests for Basic Outgoing Handovers
I. Entity Name
ROR123
II. Description
It is the count of requests for inter-MSC handovers from the cells controlled by the local
MSC to the cells controlled by the specific MSC.
It is measured when the serving MSC sends MAP_PREPARE_HANDOVER_REQ.

(3GPP TS 29.002)
BSC\RNC MSOFTX3000-A MSOFTX3000-B
HANDOVER REQUIRED
RELOCATION REQUIRED
A
MAP_PREPARE_HANDOVER_REQ
IV. Formula
None
3-25
3.4.8 Count of Successful Basic Outgoing Handovers
I. Entity Name
ROS123
II. Description
It is the count of successful inter-MSC handovers from the cells controlled by the local
MSC to the cells controlled by the specific MSC.
It is measured when the MSC receives the response to

MAP_SEND_END_SIGNAL_REQ. (3GPP TS 29.002)
BSC\RNC MSOFTX3000-A MSOFTX3000-B
HANDOVER REQUIRED
RELOCATION REQUIRED MAP_PREPARE_HANDOVER_REQ
MAP_PREPARE_HANDOVER_CNF
IAM
ACM
HANDOVER COMMAND
MAP_PROCESS_ACCESS_SIGNAL_IND
MAP_SEND_END_SIGNAL_IND
IV. Formula
None
3.4.9 Count of Requests for Basic Incoming Handovers
I. Entity Name
HIR123
II. Description
It is the count of requests for basic incoming handovers received by MSCb.
It is measured when MSCb receives the MAP_PREPARE_HANDOVER request from

the serving MSC. (3GPP TS 29.002)
3-26
MSOFTX3000-A MSOFTX3000-B T_BSC
MAP_PREPARE_HANDOVER_IND
A
HANDOVER REQUEST
HANDOVER REQUEST ACK
MAP_PREPARE_HANDOVER_RSP
HANDOVER DETECT
HANDOVER COMPLETE
MAP_SEND_END_SIGNAL_REQ
IV. Formula
None
3.4.10 Count of Successful Basic Incoming Handovers
I. Entity Name
HIS123
II. Description
It is the count of successful basic incoming handovers received by MSCb.
It is measured when the MSC sends the response to

MAP_SEND_END_SIGNAL_REQ to the serving MSC. (3GPP TS 29.002)
3-27
HANDOVER REQUEST
HANDOVER DETECT
MAP_PROCESS_ACCESS_SIGNAL_REQ
HANDOVER COMPLETE
A
MAP_SEND_END_SIGNAL_REQ
IV. Formula
None
3.4.11 Count of Requests for Subsequent Handovers Back to Local MSC

(MSCa)
I. Entity Name
RBR123
II. Description
It is the count of requests for subsequent handovers from the specified MSC back to the
local MSC (MSCa). For example, the MS is first handed over from MSCa to MSCb, and
then back to MSCa.
It is measured when the MSC receives

MAP_PREPARE_SUBSEQUENT_HANDOVER_IND, in which the terminating MSC is
MSCa. (3GPP TS 29.002)
3-28
MSOFTX3000-B MSOFTX3000-A T_BSC
MAP_PREPARE_SUBSEQUENT_HANDOVER_IND
A
HANDOVER REQUEST
MAP_PREPARE_SUBSEQUENT_HANDOVER_RSP
HANDOVER DETECT
HANDOVER COMPLETE
IV. Formula
None
3.4.12 Count of Successful Subsequent Handovers Back to Local MSC

(MSCa)
I. Entity Name
RBS123
II. Description
It is the count of successful subsequent handovers from the specified MSC back to the
local MSC (MSCa). For example, the MS is first handed over from MSCa to MSCb, and
then back to MSCa.
It is measured when the MSC sends the MAP_SEND_END_SIGNAL_RSP. (3GPP TS

29.002)
3-29
HANDOVER REQUEST
HANDOVER DETECT
HANDOVER COMPLETE
A
MAP_SEND_END_SIGNAL_RSP
IV. Formula
None
3.4.13 Count of Requests for Subsequent Handovers to MSCc (Local MSC Is

MSCa)
I. Entity Name
RCR123
II. Description
It is the count of requests for subsequent handovers from the specified MSC (MSCb) to
a third party MSC (MSCc) through the local MSC (MSCa). For example, the MS is first
handed over from MSCa to MSCb, and then to MSCc.
It is measured when the MSC receives

MAP_PREPARE_SUBSEQUENT_HANDOVER_IND, in which the terminating MSC is
MSCc. (3GPP TS 29.002)
3-30
MSOFTX3000-B MSOFTX3000-A MSOFTX3000-C
A
IAM
ACM
IV. Formula
None
3.4.14 Count of Successful Subsequent Handovers to MSCc (Local MSC Is

MSCa)
I. Entity Name
RCS123
II. Description
It is the count of successful subsequent handovers from the specified MSC (MSCb) to a
third party MSC (MSCc) through the local MSC (MSCa). For example, the MS is first
handed over from MSCa to MSCb, and then to MSCc.
It is measured when MSCa sends MSCb MAP_SEND_END_SIGNAL_RSP, indicating

the completion of handover to MSCc. (3GPP TS 29.002)
3-31
MSOFTX3000-B MSOFTX3000-A MSOFTX3000-C
IAM
ACM
A
IV. Formula
None
3.4.15 Count of Requests for Subsequent Handovers (Local MSC Is MSCb)
I. Entity Name
BRSR123
II. Description
It is the count of requests for subsequent handovers initiated by MSCb.
It is measured when the MSC sends the response to

MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ to the serving MSC. (3GPP TS
29.002)
3-32
BSC MSOFTX3000-B MSOFTX3000-A
Basic inter-MSC handover completed

HANDOVER REQUIRED
A
MAP_PREPARE_SUBSEQUENT_HANDOVER_REQ
MAP_PREPARE_HANDOVER_SUBSEQUENT_CNF
HANDOVER COMMAND
MAP_SEND_END_SIGNAL_CNF
IV. Formula
None
3.4.16 Count of Successful Subsequent Handovers (Local MSC Is MSCb)
I. Entity Name
BRSS123
II. Description
It is the count of successful subsequent handovers initiated by MSCb.
It is measured when the MSC receives the MAP_SEND_END_SIGNAL_RSP from the

serving MSC. (3GPP TS 29.002)
3-33

HANDOVER REQUIRED
HANDOVER COMMAND
IV. Formula
None
3.5 TMSI Reallocation

3.5.1 Overview of MS_S_TMSI_REALLOC_TRAF
Name Description
ULTRRN Count of TMSI reallocation requests during location update
ULTRSN Count of successful TMSI reallocations during location update
SATRRN Count of TMSI reallocation requests during service access
SATRSN Count of successful TMSI reallocations during service access
3.5.2 Count of TMSI Reallocation Requests During Location Update
I. Entity Name
ULTRRN
II. Description
It is the count of requests for TMSI reallocation during location update.
3-34
It is measured when the MSC sends the message LOCATION_UPDATE_ACCEPT

(which contains TMSI reallocation information during location update) or TMSI
_REALLOCATION_COMMAND to the MS.
See point A in the following two figures.
In 2G networks:
BSC MSC Server
Location_Updating_Re
quest
A
cept
mplete
In 3G networks:
RNC MSC Server
RN_MM_LOCATION_U
PDATION_REQUEST
RN_MM_LOCATION_ A
UPDATING_ACCEPT
RN_MM_TMSI_REALL
OCATION_COMPLETE
IV. Formula
None
3-35
3.5.3 Count of Successful TMSI Reallocations During Location Update
I. Entity Name
ULTRSN
II. Description
It is the count of successful TMSI reallocations during location update.
It is measured when the MSC sends the message LOCATION_UPDATE_ACCEPT

(which contains TMSI reallocation information during location update) to the MS, or
receives the message TMSI_REALLOCATION _COMPLETE from the MS.
In 2G networks:
BSC MSC Server
mplete
Release
In 3G networks:
3-36
RNC MSC Server
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
IU_RELEASE_COMM A
AND
IV. Formula
None
3.5.4 Count of TMSI Reallocation Requests During Service Access
I. Entity Name
SATRRN
II. Description
It is the count of requests for TMSI reallocation during service (including call,
supplementary service, and short message service) access and processing.

TMSI_REALLOCATION_COMMAND to the MS.
In 2G networks:
3-37
BSC MSC Server
CM_Service_Request
A
mmand
mplete
In 3G networks:
RNC MSC Server
RN_MM_CM_SERVIC
E_REQUEST
RN_MM_TMSI_REAL A
LOCATION_COMMA
ND
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
IV. Formula
None
3.5.5 Count of Successful TMSI Reallocations During Service Access
I. Entity Name
SATRSN
II. Description
It is the count of successful TMSI reallocations during service (including call,

supplementary service, and short message service) access and processing.
3-38

TMSI_REALLOCATION_COMPLETE from the MS.
In 2G networks:
BSC MSC Server
mplete
A
CM_Service_Accept
In 3G networks:
RNC MSC Server
RN_MM_TMSI_REAL
LOCATION_COMPLE
TE
RN_MM_CM_SERVIC A
E_ACCEPT
IV. Formula
None
3-39
3.6 WCDMA Assignment

3.6.1 Overview of MS_S_ASSIGN_3G_TRAF
Name Description
ACR121 Count of requests for traffic channel assignments
SAC121 Count of successful traffic channel assignments
RP121 Count of assignment failures due to RAB preempted
Count of assignment failures due to timeout of
RTE121
establishing RAB or modifying request on RNC side
RT121 Count of assignment failures due to handover

Count of assignment failures due to requested traffic
RTCNA121
class unavailable
Count of assignment failures due to invalid RAB

IRP121
parameter value
Count of assignment failures due to requested maximum

RMBRNA121
bit rate unavailable
Count of assignment failures due to requested

RGBRNA121
guaranteed bit rate unavailable
Count of assignment failures due to requested transfer

RTDNA121
delay unavailable
Count of assignment failures due to invalid RAB
IBPC121
parameter combination
Count of assignment failures due to violation of SDU

CVFS121
parameter conditions
Count of assignment failures due to violation of traffic
CVFTH121
handling priority conditions
Count of assignment failures due to violation of

CVFGBR121
guaranteed bit rate conditions
Count of assignment failures due to user plane version

UPVNS121
not supported
IUF121 Count of assignment failures due to Iu UP failure

IRI121 Count of assignment failures due to invalid RAB ID
NRR121 Count of assignment failures due to no remaining RAB

RS121 Count of assignment failures due to request superseded
Count of assignment failures due to signaling transport
STRF121
resource failure
OI121 Count of assignment failures due to O&M intervention
3-40
Name Description
Count of assignment failures due to no resource
NRA121
available
UF121 Count of assignment failures due to unspecified failure
DRF121 Count of assignment failures due to directed retry
Count of assignment failures due to Iu transport
ITCFTE121
connection setup failure
MTCHD121 Count of assignment failures due to other causes
3.6.2 Count of Requests for Traffic Channel Assignments
I. Entity Name
ACR121
II. Description
It is the count of channel assignment requests before they are sent.
It is measured when the CM at the network side sends the message RAB
ASSIGNMENT REQUEST or RAB RELEASE REQUEST to the RNC.
RNC MSC Server
RAB ASSIGNMENT REQUEST
A
RAB ASSIGNMENT RESPONSE
IV. Formula
None
3.6.3 Count of Successful Traffic Channel Assignments
I. Entity Name
SAC121
3-41
II. Description
It is the count of successful channel assignments.
It is measured when the CM at the network side receives the message RAB
ASSIGNMENT RESPONSE from the RNC.
RNC MSC Server
A
IV. Formula
None
3.6.4 Count of Assignment Failures Due to RAB Preempted
I. Entity Name
RP121
II. Description
It is the count of assignment failures due to RAB preempted.
It is measured when the network side receives the message RAB ASSIGNMENT
RESPONSE indicating assignment failure from the RNC, with the cause value as “RAB
pre-empted”.
3-42
RNC MSC Server
A
IV. Formula
None
3.6.5 Count of Assignment Failures Due to Timeout of Establishing RAB or

Modifying Request on RNC Side
I. Entity Name
RTE121
II. Description
It is the count of assignment failures due to queuing timeout on the RNC side.
RESPONSE indicating assignment failure from the RNC, with the cause value as
“Tqueuing expiry”.
RNC MSC Server
A
IV. Formula
None
3-43
3.6.6 Count of Assignment Failures Due to Handover
I. Entity Name
RT121
II. Description
It is the count of assignment failures due to handover.
“Relocation Triggered”.
RNC MSC Server
A
IV. Formula
None
3.6.7 Count of Assignment Failures Due to Requested Traffic Class

Unavailable
I. Entity Name
RTCNA121
II. Description
It is the count of assignment failures due to requested traffic class unavailable.
“Requested Traffic Class not Available”.
3-44
RNC MSC Server
A
IV. Formula
None
3.6.8 Count of Assignment Failures Due to Invalid RAB Parameter Value
I. Entity Name
IRP121
II. Description
It is the count of assignment failures due to invalid RAB parameter values.
“Invalid RAB Parameters Value”.
RNC MSC Server
A
IV. Formula
None
3-45
3.6.9 Count of Assignment Failures Due to Requested Maximum Bit Rate

Unavailable
I. Entity Name
RMBRNA121
II. Description
It is the count of assignment failures due to requested maximum bit rate unavailable.
“Requested Maximum Bit Rate not Available”.
RNC MSC Server
A
IV. Formula
None
3.6.10 Count of Assignment Failures Due to Requested Guaranteed Bit Rate

Unavailable
I. Entity Name
RGBRNA121
II. Description
It is the count of assignment failures due to requested guaranteed bit rate unavailable.
“Requested Guaranteed Bit Rate not Available”.
3-46
RNC MSC Server
A
IV. Formula
None
3.6.11 Count of Assignment Failures Due to Requested Transfer Delay

Unavailable
I. Entity Name
RTDNA121
II. Description
It is the count of assignment failures due to requested transfer delay unachievable.
“Requested Transfer Delay not Achievable”.
RNC MSC Server
A
IV. Formula
None
3-47

Combination
I. Entity Name
IBPC121
II. Description
It is the count of assignment failures due to invalid RAB parameter combination.
“Invalid RAB Parameters Combination”.
RNC MSC Server
A
IV. Formula
None
3.6.13 Count of Assignment Failures Due to Violation of SDU Parameter

Conditions
I. Entity Name
CVFS121
II. Description
It is the count of assignment failures due to violation of SDU parameter conditions.
“Condition Violation for SDU Parameters”.
3-48
RNC MSC Server
A
IV. Formula
None
3.6.14 Count of Assignment Failures Due to Violation of Traffic Handling

Priority Conditions
I. Entity Name
CVFTH121
II. Description
It is the count of assignment failures due to violation of traffic handling priority

conditions.
“Condition Violation for Traffic Handling Priority”.
RNC MSC Server
A
IV. Formula
None
3-49
3.6.15 Count of Assignment Failures Due to Violation of Guaranteed Bit Rate

Conditions
I. Entity Name
CVFGBR121
II. Description
It is the count of assignment failures due to violation of guaranteed bit rate conditions.
“Condition Violation for Guaranteed Bit Rate”.
RNC MSC Server
A
IV. Formula
None
3.6.16 Count of Assignment Failures Due to User Plane Version Not

Supported
I. Entity Name
UPVNS121
II. Description
It is the count of assignment failures due to user plane version not supported.
RESPONSE indicating assignment failure from the RNC, with the cause value as “User
Plane Versions not Supported”.
3-50
RNC MSC Server
A
IV. Formula
None
3.6.17 Count of Assignment Failures Due to Iu UP Failure
I. Entity Name
IUF121
II. Description
It is the count of assignment failures due to Iu UP failure.
RESPONSE indicating assignment failure from the RNC, with the cause value as “Iu
UP Failure”.
RNC MSC Server
A
IV. Formula
None
3-51
3.6.18 Count of Assignment Failures Due to Invalid RAB ID
I. Entity Name
IRI121
II. Description
It is the count of assignment failures due to invalid RAB ID.
“Invalid RAB ID”.
RNC MSC Server
A
IV. Formula
None
3.6.19 Count of Assignment Failures Due to No Remaining RAB
I. Entity Name
NRR121
II. Description
It is the count of assignment failures due to no remaining RAB.
RESPONSE indicating assignment failure from the RNC, with the cause value as “No
remaining RAB”.
3-52
RNC MSC Server
A
IV. Formula
None
3.6.20 Count of Assignment Failures Due to Request Superseded
I. Entity Name
RS121
II. Description
It is the count of assignment failures due to request superseded.
“Request superseded”.
RNC MSC Server
A
IV. Formula
None
3-53
3.6.21 Count of Assignment Failures Due to Signaling Transport Resource

Failure
I. Entity Name
STRF121
II. Description
It is the count of assignment failures due to signaling transport resource failure.
“Signaling Transport Resource Failure”.
RNC MSC Server
A
IV. Formula
None
3.6.22 Count of Assignment Failures Due to O&M Intervention
I. Entity Name
OI121
II. Description
It is the count of assignment failures due to O&M intervention.
“O&M Intervention”.
3-54
RNC MSC Server
A
IV. Formula
None
3.6.23 Count of Assignment Failures Due to No Resource Available
I. Entity Name
NRA121
II. Description
It is the count of assignment failures due to no resource available.
RESPONSE indicating assignment failure from the RNC, with the cause value as “No
Resource Available”.
RNC MSC Server
A
IV. Formula
None
3-55
3.6.24 Count of Assignment Failures Due to Unspecified Failure
I. Entity Name
UF121
II. Description
It is the count of assignment failures due to unspecified failure.
“Unspecified Failure”.
RNC MSC Server
A
IV. Formula
None
3.6.25 Count of Assignment Failures Due to Directed Retry
I. Entity Name
DRF121
II. Description
It is the count of assignment failures due to directed retry.
“Directed Retry”.
3-56
RNC MSC Server
A
IV. Formula
None
3.6.26 Count of Assignment Failures Due to Iu Transport Connection Setup

Failure
I. Entity Name
ITCFTE121
II. Description
It is the count of assignment failures due to failure of establishing the Iu transport

connection.
RESPONSE indicating assignment failure from the RNC, with the cause value as “Iu
Transport Connection Failed to Establish”.
RNC MSC Server
A
IV. Formula
None
3-57
3.6.27 Count of Assignment Failures Due to Other Causes
I. Entity Name
MTCHD121
II. Description
It is the count of assignment failures due to other causes.
RESPONSE indicating assignment failure from the RNC, with the cause value as not
any one listed above.
RNC MSC Server
A
IV. Formula
None
3.7 Short Message Service

3.7.1 Overview of MS_TYPE_SMS
Name Description
AMSF28 Count of attempt MO short messages
SMSF28 Count of successful MO short messages

Count of failures to send MO short messages due to
UMSFAF28
authentication failure
Count of failures to send MO short messages due to setting

UMSFSCMF28
ciphering mode failure
Count of failures to send MO short messages due to service

UMSFSMB28
restriction
3-58
Name Description
UMSFUS28
unknown subscriber
UMSFFNS28
equipment not supported
Count of failures to send MO short messages due to system
UMSFSF28
failure
Count of failures to send MO short messages due to SM
UMSFSDF28
delivery failure
Count of failures to send MO short messages due to protocol
UMSFPDE28
data error
AMSFD28 Count of attempt MT short messages
SMSFD28 Count of successful MT short messages
Count of failures to send MT short messages due to
UMSFUSB28
unidentified subscriber
Count of failures to send MT short messages due to absent
UMSFAS28
subscriber
Count of failures to send MT short messages due to

UMSFFNSP28
equipment not supported
Count of failures to send MT short messages due to illegal

UMSFUSS28
subscriber
Count of failures to send MT short messages due to illegal

UMSFICF28
equipment
Count of failures to send MT short messages due to system

UMSFSFL28
failure
Count of failures to send MT short messages due to SM

UMSFSDFL28
delivery failure
3.7.2 Count of Attempt MO Short Messages
I. Entity Name
AMSF28
II. Description
It is the count of short message service (SMS) requests that the MSC receives from
subscribers.
It is measured when the MSC receives the SMS message from the BSC.
3-59
RNC MSC Server SMC
CM_SERVICE_REQUEST
A
Authentication/Encryption
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA
B
CP_ACK
IV. Formula
None
3.7.3 Count of Successful MO Short Messages
I. Entity Name
SMSF28
II. Description
It is the count of successes that the MSC sends the CP_DATA message to the
originating subscriber, that is, the count of successful mobile originated (MO) short
messages.
It is measured in the following cases:

z The MSC receives the message MAP_FOWARD_SHORT_MESSAG ACK from
the IWMSC and then sends the CP_DATA message to the caller.
z The MSC sends the message Ready For SM to the HLR and then receives a
correct response.
z The MSC sends the message Memory Available to the HLR and then receives a
correct response.
See point B in the following two figures.
3-60
RNC MSC Server SMC
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA
B
CP_ACK
RNC MSC Server HLR
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
READY_FORSM_REQ
READY_FORSM_RSP
CP_DATA
B
CP_ACK
IV. Formula
None
3-61
3.7.4 Count of Failures to Send MO Short Messages Due to Authentication

Failure
I. Entity Name
UMSFAF28
II. Description
It is the count of failures to send MO short messages due to authentication failure.

message indicating service accepted for legal subscribers or service rejected for illegal
subscribers to the MSC after successfully checking SRES.
See point B in the following figure. During access, if the MSC receives the response
indicating illegal subscriber from the VLR, the entity is measured.
RNC MSC Server
CM_SERVICE_REQUEST
A
COMMON_ID
B
CM_SERVICE_REJECT
IV. Formula
None
3.7.5 Count of Failures to Send MO Short Messages Due to Setting Ciphering

Mode Failure
I. Entity Name
UMSFSCMF28
II. Description
It is the count of failures to send MO short messages due to setting ciphering mode
failure.
3-62
It is measured when the MSC receives the message SECURITY MODE REJECT or
CIPH MODE REJECT.
RNC MSC Server
CM_SERVICE_REQUEST
A
COMMON_ID
SECURITY_MODE_COMMAND
SECURITY_MODE_REJECT
B
CM_SERVICE_REJECT
IV. Formula
None
3.7.6 Count of Failures to Send MO Short Messages Due to Service

Restriction
I. Entity Name
UMSFSMB28
II. Description
It is the count of failures to send MO short messages due to service restriction of the
caller, like SMS not subscribed to and barring of corresponding supplementary
services.
It is measured when the MSC checks barring of services relevant to MO short

messages after receiving the message CP-DATA, or the mobile subscriber (MS) does
not subscribe the teleservice of SMMO.
3-63
RNC MSC Server
CM_SERVICE_REQUEST
A
COMMON_ID
B
CM_SERVICE_REJECT
IV. Formula
None
3.7.7 Count of Failures to Send MO Short Messages Due to Unknown

Subscriber
I. Entity Name
UMSFUS28
II. Description
It is the count of failures to send MO short messages due to caller unknown in the short
message center (SMC).

z A subscriber accesses to the network, the MSC fetches the access data of the
subscriber from the VLR and the VLR returns a message indicating unknown
subscriber.
z A short message is sent, and the authentication fails with the cause of unknown
subscriber.
z The MSC sends the message Ready For SM to the HLR, and the HLR returns an
error message with the cause of unknown subscriber.
z The MAP fetches the MO short message data from the VLR, and the VLR returns
a message indicating location subscriber.
3-64
RNC MSC Server HLR
CM_SERVICE_REQUEST
A
COMMON_ID
B
CM_SERVICE_REJECT
RNC MSC Server HLR
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
READY_FORSM_REQ
READY_FORSM_RSP
CP_DATA B
CP_ACK
IV. Formula
None
3.7.8 Count of Failures to Send MO Short Messages Due to Equipment Not

Supported
I. Entity Name
UMSFFNS28
II. Description
It is the count of failures to send MO short messages due to equipment (such as the
SMC) not supported.
3-65

z The MSC sends the message Ready For SM to the HLR, and the HLR returns an
error message with the cause of equipment not supported.
z The subscriber finishes accessing, and the MAP receives a request for MO short
messages from the SMS module but the configuration does not support MO short
messages.
z The MSC sends short messages to the SMS GMSC and then receives the
response containing the error cause of equipment not supported.
3-66
RNC MSC Server HLR
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
READY_FORSM_REQ
READY_FORSM_RSP
CP_DATA B
CP_ACK
RNC MSC Server SMC
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA B
CP_ACK
IV. Formula
None
3-67
3.7.9 Count of Failures to Send MO Short Messages Due to System Failure
I. Entity Name
UMSFSF28
II. Description
It is the count of failures to send MO short messages due to SMC failure.

z The MAP does not receive all the access data from the VDB during access of a
short message.
z The MSC obtains the subscriber identification in the process of sending a short
message, and receives the message IMSI Not Received or the response without
IMSI.
z The SMC does not allow the subscriber to access.
z TMSI reallocation fails in the process of sending a short message.
z Authentication fails in the process of sending a short message.
z IMEI check fails in the process of sending a short message.
z The MSC obtains subscriber data from the VLR but the time limit is exceeded in
the process of sending a short message.
z The MSC sends the message Ready For SM to the HLR, and the HLR returns a
response with the cause of system failure.
See points A and B in the following two figures. The measurement begins when system
failure occurs between A and B.
3-68
RNC MSC Server HLR
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
READY_FORSM_REQ
READY_FORSM_RSP
CP_DATA B
CP_ACK
RNC MSC Server SMC
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA B
CP_ACK
IV. Formula
None
3-69
3.7.10 Count of Failures to Send MO Short Messages Due to SM Delivery

Failure
I. Entity Name
UMSFSDF28
II. Description
It is the count of failures to send MO short messages due to the causes like unknown
service center address and service center congestion.

MAP_FORWARD_SHORT_MESSAGE RSP from the IWMSC, with the cause value as
“SM Delivery Failure”.
RNC MSC Server SMC
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA B
CP_ACK
IV. Formula
None
3-70
3.7.11 Count of Failures to Send MO Short Messages Due to Protocol Data

Error
I. Entity Name
UMSFPDE28
II. Description
It is the count of failures to send MO short messages due to protocol data error.

z The MSC receives the message MAP_MO_FORWARD_SHORT_MESSAGE
RSP from the IWMSC, with the cause value as “Unexpected data value" or “Data
missing”.
z The MSC sends the message Ready For SM to the HLR, and then receives the
response with the cause of protocol error.
z The MS originates a short message and the MSC finds the protocol cell lost.
See point B in the following figures.
3-71
RNC MSC Server HLR
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
READY_FORSM_REQ
READY_FORSM_RSP
CP_DATA B
CP_ACK
RNC MSC Server SMC
CM_SERVICE_REQUEST
A
CP_DATA
CP_ACK
MO_FORWARD_SM_REQ
MO_FORWARD_SM_RSP
CP_DATA B
CP_ACK
IV. Formula
None
3-72
3.7.12 Count of Attempt MT Short Messages
I. Entity Name
AMSFD28
II. Description
It is the count of MAP/E MAP_FORWARD_SHORT_MESSAGE messages received by

the MSC which controls the callee.
It is measured when the serving MSC where the MS (that is, the measurement entity) is
located receives the message MAP/E MAP_FORWARD_SHORT_MESSAGE from the
GMSC.
RNC MSC Server SMC
MT_FORWARD_SM_IND
A
Paging access
CP_DATA
CP_ACK
CP_DATA
MT_FORWARD_SM_RSP
B
CP_ACK
IV. Formula
None
3.7.13 Count of Successful MT Short Messages
I. Entity Name
SMSFD28
II. Description
It is the count of successful mobile terminated (MT) short messages.
3-73
It is measured when the GMSC sends the message MAP/E

MAP_FORWARD_SHORT_MESSAGE RSP without cause value.
RNC MSC Server SMC
MT_FORWARD_SM_IND
A
Paging access
CP_DATA
CP_ACK
CP_DATA
MT_FORWARD_SM_RSP
B
CP_ACK
IV. Formula
None
3.7.14 Count of Failures to Send MT Short Messages Due to Unidentified

Subscriber
I. Entity Name
UMSFUSB28
II. Description
It is the count of failures to send MT short messages due to unidentified subscriber.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “Unidentified
subscriber”.
3-74
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None
3.7.15 Count of Failures to Send MT Short Messages Due to Absent

Subscriber
I. Entity Name
UMSFAS28
II. Description
It is the count of failures to send MT short messages due to absent subscriber.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “Absent
Subscriber_SM”.
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None
3-75
3.7.16 Count of Failures to Send MT Short Messages Due to Equipment Not

Supported
I. Entity Name
UMSFFNSP28
II. Description
It is the count of failures to send MT short messages due to equipment not supported.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “Facility Not
Supported”.
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None

Subscriber
I. Entity Name
UMSFUSS28
II. Description
It is the count of failures to send MT short messages due to illegal subscriber.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “Illegal
3-76
Subscriber”, indicating that the delivery of the MT short message fails because
authentication of the mobile station fails.
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None

Equipment
I. Entity Name
UMSFICF28
II. Description
It is the count of failures to send MT short messages due to illegal equipment.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “Illegal
Equipment”, indicating that the delivery of the MT short message fails because an IMEI
check fails.
3-77
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None
3.7.19 Count of Failures to Send MT Short Messages Due to System Failure
I. Entity Name
UMSFSFL28
II. Description
It is the count of failures to send MT short messages due to system failure.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “System failure”.
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None
3-78
3.7.20 Count of Failures to Send MT Short Messages Due to SM Delivery

Failure
I. Entity Name
UMSFSDFL28
II. Description
It is the count of failures to send MT short messages due to SM delivery failure.

MAP_FORWARD_SHORT_MESSAGE RSP, with the cause value as “SM Delivery
failure”.
MSC Server SMC
MT_FORWARD_SM_IND
A
MT_FORWARD_SM_RSP
IV. Formula
None
3.8 GSM Cell Handover

3.8.1 Overview of MS_S_CELL_HO_TRAF
Name Description
IEIMHT116 Count of requests for intra-MSC incoming handovers to cell
SIEIMHT116 Count of successful intra-MSC incoming handovers to cell

OEIMHT116 Count of requests for intra-MSC outgoing handovers from cell
SOEIMHT116 Count of successful intra-MSC outgoing handovers from cell
IIMHT116 Count of requests for inter-MSC incoming handovers to cell
SIIMHT116 Count of successful inter-MSC incoming handovers to cell
3-79
Name Description
OIMHT116 Count of requests for inter-MSC outgoing handovers from cell
SOIMHT116 Count of successful inter-MSC outgoing handovers from cell
HRFQ116 Count of outgoing handovers from cell due to uplink quality
HRUS116 Count of outgoing handovers from cell due to uplink strength
HRDQ116 Count of outgoing handovers from cell due to downlink quality
HRDS116 Count of outgoing handovers from cell due to downlink strength
HRD116 Count of outgoing handovers from cell due to distance
Count of outgoing handovers from cell due to existence of better
HRBC116
cell
Count of outgoing handovers from cell due to response to MSC

HRIBM116
request
HROM116 Count of outgoing handovers from cell due to O&M intervention
HRDR116 Count of outgoing handovers from cell due to directed retry
Count of outgoing handovers from cell due to change of circuit
HRSCP116
group
HROC116 Count of outgoing handovers from cell due to other causes
Count of handover failures due to radio interface message
HFRMF116
failure
HFOM116 Count of handover failures due to O&M intervention

HFEF116 Count of handover failures due to equipment failure
HFNRR116 Count of handover failures due to no radio resource available
Count of handover failures due to requested terrestrial resource
HFTRU116
unavailable
Count of handover failures due to transcoding/rate adaptation

HFTRRU116
unavailable
Count of handover failures due to requested terrestrial resource
HFTRA116
already allocated
HFIMSG116 Count of handover failures due to invalid message content

Count of handover failures due to radio interface failure -
HFRIF116
reversion to old channel
Count of handover failures due to ciphering algorithm not

HFCAN116
supported
HFCPM116 Count of handover failures due to circuit pool mismatch

Count of handover failures due to change of circuit group
HFSCP116
number
Count of handover failures due to requested speech version
HFSVU116
unavailable
3-80
Name Description
HFPE116 Count of handover failures due to protocol error
HFPRE116 Count of handover failures due to preemption
HFOR116 Count of handover failures due to other causes
3.8.2 Count of Requests for Intra-MSC Incoming Handovers to Cell
I. Entity Name
IEIMHT116
II. Description
It is the count of requests for intra-MSC (including inter-BSC and intra-BSC) incoming
handovers to the observed GSM cell.
For inter-BSC handover, it is measured when the MSC sends the message
HANDOVER_REQUEST to BSSb; for intra-BSC handover, it is measured when the
MSC receives the HO PERFORMED message from the BSS.
S_BSC MSOFTX3000 T_BSC
HANDOVER REQUIRED
HANDOVER REQUEST
A
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
IV. Formula
None
3-81
3.8.3 Count of Successful Intra-MSC Incoming Handovers to Cell
I. Entity Name
SIEIMHT116
II. Description
It is the count of successful intra-MSC (including inter-BSC and intra-BSC) incoming

handovers to the observed GSM cell.
For inter-BSC handover, it is measured when the MSC receives the message
HANDOVER_COMPLETE from BSSb; for intra-BSC handover, it is measured when
the MSC receives the HO PERFORMED message from the BSS.
HANDOVER REQUIRED
HANDOVER REQUEST
A
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
IV. Formula
None
3.8.4 Count of Requests for Intra-MSC Outgoing Handovers from Cell
I. Entity Name
OEIMHT116
II. Description
It is the count of requests for intra-MSC (including inter-BSC and intra-BSC) outgoing
handovers from the observed GSM cell.
3-82
It is measured when the MSC receives the message HANDOVER REQUIRED from the
originating BSC for intra-MSC handover.
HANDOVER REQUIRED
A
HANDOVER REQUEST
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
IV. Formula
None
3.8.5 Count of Successful Intra-MSC Outgoing Handovers from Cell
I. Entity Name
SOEIMHT116
II. Description
It is the count of successful intra-MSC (including inter-BSC and intra-BSC) outgoing

handovers from the observed GSM cell.
It is measured when the MSC receives the message HANDOVER COMPLETE from
the terminating BSC for intra-MSC handover.
3-83
HANDOVER REQUIRED
A
HANDOVER REQUEST
HANDOVER COMMAND
HANDOVER DETECT
HANDOVER COMPLETE
IV. Formula
None
3.8.6 Count of Requests for Inter-MSC Incoming Handovers to Cell
I. Entity Name
IIMHT116
II. Description
It is the count of requests for inter-MSC incoming handovers to the observed GSM cell,
including basic handovers and subsequent handovers. For different types of handovers,
the counters work logically in different MSCs during measurement.

z Basic handover: MSCb receives the message MAP/E
MAP_PREPARE_HANDOVER_IND from MSCa, and sends the message
HANDOVER REQUEST to the terminating BSC. See point A’ in the following
figure. Both the observed cell GCI and the counter are located in MSCb.
z Subsequent handover back to MSCa: MSCa receives the message MAP/E
MAP_PREPARE_SUBSEQUENT_HANDOVER_IND from MSCb, and sends the
message HANDOVER REQUEST to the terminating BSC. See point A’’ in the
following figure. Both the observed cell and the counter are located in MSCa.
z Subsequent handover to a third party MSCc: MSCc receives the message MAP/E
HANDOVER REQUEST to the terminating BSC. See point A’’’ in the following
3-84
figure. MSCa sends this message after receiving the MAP/E

MAP_Prep_Sub_Handover_Ind message from MSCb. Both the observed cell and
the counter are located in MSCc.
MSOFTX3000-A MSOFTX3000-B/C T_BSC
A'/A'''
HANDOVER REQUEST
HANDOVER DETECT
HANDOVER COMPLETE
A''
HANDOVER REQUEST

HANDOVER DETECT
HANDOVER COMPLETE
IV. Formula
None
3.8.7 Count of Successful Inter-MSC Incoming Handovers to Cell
I. Entity Name
SIIMHT116
II. Description
It is the count of successful inter-MSC incoming handovers to the observed GSM cell,
3-85

z Inter-MSC incoming handover to MSCb: MSCb receives the message
HANDOVER COMPLETE from the terminating BSC. See point B in the following
figure. Both the observed cell GCI and the counter are located in MSCb.
z Subsequent handover back to MSCa: MSCa receives the message HANDOVER
COMPLETE from the terminating BSC. See point B’’ in the following figure. Both
the observed cell and the counter are located in MSCa.
A
HANDOVER REQUEST
HANDOVER DETECT
HANDOVER COMPLETE
A''
HANDOVER REQUEST

HANDOVER DETECT
HANDOVER COMPLETE
B''
IV. Formula
None
3-86
3.8.8 Count of Requests for Inter-MSC Outgoing Handovers from Cell
I. Entity Name
OIMHT116
II. Description
It is the count of requests for inter-MSC outgoing handovers from the observed GSM
cell, including basic handovers and subsequent handovers. For different types of
handovers, the counters work logically in different MSCs during measurement.

z Basic outgoing handover from MSCa: MSCa receives the message HANDOVER
REQUIRED from the originating BSC. See point A’ in the following figure. Both the
observed cell GCI and the counter are located in MSCa.
z Subsequent handover of MSCb: MSCb sends the request for subsequent
handover back to MSCa or a third party after the inter-MSC handover completes.
See point A’’ in the following figure. Both the observed cell and the counter are
located in MSCb.
3-87
S_BSC MSOFTX3000-A MSOFTX3000-B
HANDOVER REQUIRED
A'
IAM
ACM
HANDOVER COMMAND
PAS(HANDOVER DETECT)
SES(HANDOVER COMPLETE)
B'

HANDOVER REQUIRED
A''
HANDOVER COMMAND
B''
IV. Formula
None
3.8.9 Count of Successful Inter-MSC Outgoing Handovers from Cell
I. Entity Name
SOIMHT116
II. Description
It is the count of successful inter-MSC outgoing handovers from the observed GSM cell,
3-88

z Basic outgoing handover from MSCa: MSCa receives the message HANDOVER
COMPLETE from MSCb. See point B’ in the following figure. Both the observed
cell GCI and the counter are located in MSCa.
z Subsequent handover of MSCb: MSCb receives the message
MAP_SEND_END_SIGNAL_CNF from MSCa after the subsequent handover
completes. See point B’’ in the following figure. Both the observed cell and the
counter are located in MSCb.
S_BSC MSOFTX3000-A MSOFTX3000-B
HANDOVER REQUIRED
A'
IAM
ACM
HANDOVER COMMAND
PAS(HANDOVER DETECT)
SES(HANDOVER COMPLETE)
B'

HANDOVER REQUIRED
A''
HANDOVER COMMAND
B''
IV. Formula
None
3-89
3.8.10 Count of Outgoing Handovers from Cell Due to Uplink Quality
I. Entity Name
HRFQ116
II. Description
It is the count of outgoing handovers from the cell due to uplink quality.
It is measured when the MSC receives the message HANDOVER_REQUIRED and

analyzes the handover cause code.
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.11 Count of Outgoing Handovers from Cell Due to Uplink Strength
I. Entity Name
HRUS116
II. Description
It is the count of outgoing handovers from the cell due to uplink strength.

3-90
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.12 Count of Outgoing Handovers from Cell Due to Downlink Quality
I. Entity Name
HRDQ116
II. Description
It is the count of outgoing handovers from the cell due to downlink quality.

3-91
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.13 Count of Outgoing Handovers from Cell Due to Downlink Strength
I. Entity Name
HRDS116
II. Description
It is the count of outgoing handovers from the cell due to downlink strength.

3-92
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.14 Count of Outgoing Handovers from Cell Due to Distance
I. Entity Name
HRD116
II. Description
It is the count of outgoing handovers from the cell due to distance.
See point A in the following figure. It is measured when the MSC receives the message
HANDOVER_REQUIRED and analyzes the handover cause code.
3-93
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.15 Count of Outgoing Handovers from Cell Due to Existence of Better

Cell
I. Entity Name
HRBC116
II. Description
It is the count of outgoing handovers from the cell due to the existence of better cells.

3-94
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.16 Count of Outgoing Handovers from Cell Due to Response to MSC

Request
I. Entity Name
HRIBM116
II. Description
It is the count of outgoing handovers from the cell due to response to the MSC request.

3-95
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.17 Count of Outgoing Handovers from Cell Due to O&M Intervention
I. Entity Name
HROM116
II. Description
It is the count of outgoing handovers from the cell due to O&M intervention.

3-96
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.18 Count of Outgoing Handovers from Cell Due to Directed Retry
I. Entity Name
HRDR116
II. Description
It is the count of outgoing handovers from the cell due to directed retry.

3-97
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.19 Count of Outgoing Handovers from Cell Due to Change of Circuit

Group
I. Entity Name
HRSCP116
II. Description
It is the count of outgoing handovers from the cell due to change of the circuit group.

3-98
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.20 Count of Outgoing Handovers from Cell Due to Other Causes
I. Entity Name
HROC116
II. Description
It is the count of outgoing handovers from the cell due to other causes.
It is measured when the MSC receives the message HANDOVER_REQUIRED,

analyzes the handover cause code, and finds that it is not any cause as list above.
3-99
BSC MSC
A-Handover-Required
IV. Formula
None
3.8.21 Count of Handover Failures Due to Radio Interface Message Failure
I. Entity Name
HFRMF116
II. Description
It is the count of handover failures due to radio interface message failure.
It is measured when the MSC receives the message HANDOVER_FAILURE from

BSSa or BSSb, with the cause value as “radio interface message failure”.
3-100
RNC MSC Server
LOCATION_UPDATE_REQ
LOCATION_UPDATE_REJ
IV. Formula
None
3.8.22 Count of Handover Failures Due to O&M Intervention
I. Entity Name
HFOM116
II. Description
It is the count of handover failures due to O&M intervention.

BSSa or BSSb, with the cause value as “O and M intervention”.
3-101
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.23 Count of Handover Failures Due to Equipment Failure
I. Entity Name
HFEF116
II. Description
It is the count of handover failures due to equipment failure.

BSSa or BSSb, with the cause value as “equipment failure”.
3-102
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.24 Count of Handover Failures Due to No Radio Resource Available
I. Entity Name
HFNRR116
II. Description
It is the count of handover failures due to no radio resource available.

BSSa or BSSb, with the cause value as “no radio resource available”.
3-103
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.25 Count of Handover Failures Due to Requested Terrestrial Resource

Unavailable
I. Entity Name
HFTRU116
II. Description
It is the count of handover failures due to requested terrestrial resource unavailable.

BSSa or BSSb, with the cause value as “requested terrestrial resource unavailable”.
3-104
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.26 Count of Handover Failures Due to Transcoding/Rate Adaptation

Unavailable
I. Entity Name
HFTRRU116
II. Description
It is the count of handover failures due to transcoding/rate adaptation unavailable.

BSSa or BSSb, with the cause value as “requested transcoding/rate adaptation
unavailable”.
3-105
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.27 Count of Handover Failures Due to Requested Terrestrial Resource

Already Allocated
I. Entity Name
HFTRA116
II. Description
It is the count of handover failures due to requested terrestrial resource already

allocated.

BSSa or BSSb, with the cause value as “terrestrial resource already allocated”.
3-106
RNC MSC Server
LOCATION_UPDATE_REQ
LOCATION_UPDATE_REJ
IV. Formula
None
3.8.28 Count of Handover Failures Due to Invalid Message Content
I. Entity Name
HFIMSG116
II. Description
It is the count of handover failures due to invalid message contents.

BSSa or BSSb, with the cause value as “invalid message contents”.
3-107
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.29 Count of Handover Failures Due to Radio Interface Failure - Reversion

to Old Channel
I. Entity Name
HFRIF116
II. Description
It is the count of handover failures due to radio interface failure - reversion to old
channel.

BSSa or BSSb, with the cause value as “radio interface failure - reversion old channel”.
3-108
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.30 Count of Handover Failures Due to Ciphering Algorithm Not

Supported
I. Entity Name
HFCAN116
II. Description
It is the count of handover failures due to ciphering algorithm not supported.

BSSa or BSSb, with the cause value as “ciphering algorithm not supported”.
3-109
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.31 Count of Handover Failures Due to Circuit Pool Mismatch
I. Entity Name
HFCPM116
II. Description
It is the count of handover failures due to circuit pool mismatch.

BSSa or BSSb, with the cause value as “circuit pool mismatch”.
3-110
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.32 Count of Handover Failures Due to Change of Circuit Group Number
I. Entity Name
HFSCP116
II. Description
It is the count of handover failures due to the change of the circuit group number.

BSSa or BSSb, with the cause value as “switch circuit pool”.
3-111
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.33 Count of Handover Failures Due to Requested Speech Version

Unavailable
I. Entity Name
HFSVU116
II. Description
It is the count of handover failures due to requested speech version unavailable.

BSSa or BSSb, with the cause value as “requested speech version unavailable”.
3-112
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.34 Count of Handover Failures Due to Protocol Error
I. Entity Name
HFPE116
II. Description
It is the count of handover failures due to protocol errors.

BSSa or BSSb, with the cause value as “protocol error between MSC-BSC”.
3-113
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.35 Count of Handover Failures Due to Preemption
I. Entity Name
HFPRE116
II. Description
It is the count of handover failures due to preemption.

BSSa or BSSb, with the cause value as “Preemption”.
3-114
BSC MSC
A-Handover-Failure
IV. Formula
None
3.8.36 Count of Handover Failures Due to Other Causes
I. Entity Name
HFOR116
II. Description
It is the count of handover failures due to other causes.

BSSa or BSSb due to other .causes.
3-115
BSC MSC
A-Handover-Failure
IV. Formula
None
3.9 WCDMA RNC Handover

3.9.1 Overview of MS_S_RNC_RELOCATION
Name Description
IIRH120 Count of requests for intra-MSC incoming handovers to RNC
SIIRH120 Count of successful intra-MSC incoming handovers to RNC
IAORH120 Count of requests for intra-MSC outgoing handovers from RNC
SIAORH120 Count of successful intra-MSC outgoing handovers from RNC
ITRH120 Count of requests for inter-MSC incoming handovers to RNC
SITRH120 Count of successful inter-MSC incoming handovers to RNC
ITORH120 Count of requests for inter-MSC outgoing handovers from RNC
SITORH120 Count of successful inter-MSC outgoing handovers from RNC

FRU120 Count of outgoing handovers from RNC due to time critical
Count of outgoing handovers from RNC due to resource
FRNS120
optimization
FRF120 Count of outgoing handovers from RNC due to radio resource
FRTE120 Count of outgoing handovers from RNC due to directed retry

OFRR120 Count of outgoing handovers from RNC due to O&M intervention
3-116
Name Description
Count of outgoing handovers from RNC due to network
OFRO120
optimization
OFTC120 Count of outgoing handovers from RNC due to other causes
OFDR120 Count of handover failures due to RAB preempted
OFOR120 Count of handover failures due to handover timeout
ATDF120 Count of handover failures due to timeout of preparing handover
Count of handover failures due to timeout of waiting for relocation
IUYYT120
complete message
Count of handover failures due to timeout of queuing radio

ARHS120
interface
ASIH120 Count of handover failures due to timeout of allocating resource
Count of handover failures due to establishing radio interface
AIORH120
unsuccessfully
ASIOH120 Count of handover failures due to unknown target cell

AITRH120 Count of handover failures due to handover cancelled
Count of handover failures due to requested ciphering algorithm

ASITR120
not supported
ATORH120 Count of handover failures due to change of ciphering algorithm
ATRIH120 Count of handover failures due to radio interface failure
AFRU120 Count of handover failures due to UTRAN
Count of handover failures due to requested traffic class

AFRNS120
unavailable
AFRF120 Count of handover failures due to invalid RAB parameter value
Count of handover failures due to requested maximum bit rate
AFRTE120
unavailable
Count of handover failures due to requested guaranteed bit rate

AOFRR120
unavailable
Count of handover failures due to requested transfer delay
AOFRO120
unachievable
Count of handover failures due to invalid RAB parameter

AOFTC120
combination
Count of handover failures due to violation of SDU parameter

AOFDR120
conditions
Count of handover failures due to violation of traffic handling
AOFOR120
priority conditions
Count of handover failures due to violation of requested

ATDK120
guaranteed bit rate conditions
3-117
Name Description
Count of handover failures due to user plane version not
AIUYT120
supported
DRHS120 Count of handover failures due to Iu UP negotiation failure
DSIH120 Count of handover failures due to target system failure
DIORH120 Count of handover failures due to invalid RAB ID
DSIOH120 count of handover failures due to no remaining RAB
Count of handover failures due to interaction with other
DITRH120
procedures
Count of handover failures due to requested maximum bit rate for

DSITR120
downlink unavailable
Count of handover failures due to requested maximum bit rate for

DTORH120
uplink unavailable

DTRIH120
for downlink unavailable

DFRU120
for uplink unavailable
Count of handover failures due to requested consistency check
DFRNS120
failure
Count of handover failures due to UE generated signaling

DFRF120
connection released
Count of handover failures due to requested information

DFRTE120
unavailable
DOFRR120 Count of handover failures due to target system not supported

DOFRO120 Count of handover failures due to radio connection with UE lost
Count of handover failures due to RNC unable to establish all
DOFTC120
RFCs
DOFDR120 Count of handover failures due to target not allowed
Count of handover failures due to signaling transport resource
DOFOR120
failure
Count of handover failures due to Iu transport connection setup

DTDK120
failure
DIUYT120 Count of handover failures due to protocol failure

COFOR120 Count of handover failures due to no resource available
CTDK120 Count of handover failures due to unspecified cause
3-118
3.9.2 Count of Requests for Intra-MSC Incoming Handovers to RNC
I. Entity Name
IIRH120
II. Description
It is the count of requests for intra-MSC (including inter-RNC) incoming handovers to

the observed 3G cell.
It is measured when the MSC sends the message RELOCATION REQUEST to the
terminating RNC.
S_RNC MSOFTX3000 T_RNC
RELOCATION REQUIRED
RELOCATION REQUEST
A
REOCATION REQUEST ACK
RELOCATION COMMAND
RELOCATION DETECT
RELOCATION COMPLETE
IV. Formula
None
3.9.3 Count of Successful Intra-MSC Incoming Handovers to RNC
I. Entity Name
SIIRH120
II. Description
It is the count of successful intra-MSC (including inter-RNC) incoming handovers to the

observed 3G cell.
3-119
It is measured when the MSC receives the message RELOCATION COMPLETE from
the terminating RNC.
RELOCATION REQUIRED
RELOCATION REQUEST
A
RELOCATION REQUEST ACK
RELOCATION COMMAND
RELOCATION DETECT
RELOCATION COMPLETE
IV. Formula
None
3.9.4 Count of Requests for Intra-MSC Outgoing Handovers from RNC
I. Entity Name
IAORH120
II. Description
It is the count of requests for intra-MSC (including inter-RNC) outgoing handovers from
It is measured when the MSC receives the message RELOCATION REQUIRED from
the originating RNC for intra-MSC handover.
3-120
RELOCATION REQUIRED
A
RELOCATION REQUEST
RELOCATION COMMAND
RELOCATION DETECT
RELOCATION COMPLETE
IV. Formula
None
3.9.5 Count of Successful Intra-MSC Outgoing Handovers from RNC
I. Entity Name
SIAORH120
II. Description
It is the count of successful intra-MSC (including inter-RNC) outgoing handovers from

It is measured when the MSC receives the message RELOCATION COMPLETE from
the terminating RNC for intra-MSC handover.
3-121
RELOCATION REQUIRED
A
RELOCATION REQUEST

RELOCATION COMMAND
RELOCATION DETECT
RELOCATION COMPLETE
IV. Formula
None
3.9.6 Count of Requests for Inter-MSC Incoming Handovers to RNC
I. Entity Name
ITRH120
II. Description
It is the count of requests for inter-MSC incoming handovers to the observed 3G cell,

z Basic handover: MSCb receives the message MAP/E
RELOCATION REQUEST to the terminating RNC. See point A’ in the following
figure. Both the observed RNC and the counter are located in MSCb.
z Subsequent handover back to MSCa: MSCa receives the message MAP/E
MAP_PREPARE_SUBSEQUENT_HANDOVER_IND from MSCb, and sends the
message RELOCATION REQUEST to the terminating RNC. See point A’’ in the
following figure. Both the observed RNC and the counter are located in MSCa.
z Subsequent handover to a third party MSCc: MSCc receives the message MAP/E
RELOCATION REQUEST to the terminating RNC. See point A’’’ in the following
3-122
figure. MSCa sends this message after receiving the message MAP/E
MAP_PREPARE_SUBSEQUENT_HANDOVER_IND from MSCb. Both the
observed RNC and the counter are located in MSCc.
MSOFTX3000-A MSOFTX3000-B/C T_RNC
A'/A'''
RELOCATION REQUEST
RELOCATION REQUEST
ACK
RELOCATION DETECT
RELOCATION COMPLETE
MSOFTX3000-B MSOFTX3000-A T_RNC
A''
RELOCATION REQUEST
RELOCATION REQUEST
ACK
RELOCATION DETECT
RELOCATION COMPLETE
IV. Formula
None
3.9.7 Count of Successful Inter-MSC Incoming Handovers to RNC
I. Entity Name
SITRH120
3-123
II. Description
It is the count of successful inter-MSC incoming handovers to the observed 3G cell,


z Inter-MSC incoming handover to MSCb: MSCb receives the message
RELOCATION COMPLETE from the terminating RNC. See point B in the
following figure. Both the observed RNC and the counter are located in
MSCb.Subsequent handover back to MSCa: MSCa receives the message
HANDOVER COMPLETE from the terminating RNC. See point B’’ in the following
figure. Both the observed RNC and the counter are located in MSCa.
3-124
MSOFTX3000-A MSOFTX3000-B T_RNC
A
RELOCATION REQUEST
RELOCATION REQUEST
ACK
RELOCATION DETECT
RELOCATION COMPLETE
MSOFTX3000-B MSOFTX3000-A T_RNC
A''
RELOCATION REQUEST
RELOCATION REQUEST
ACK
RELOCATION DETECT
RELOCATION COMPLETE
B''
IV. Formula
None
3.9.8 Count of Requests for Inter-MSC Outgoing Handovers from RNC
I. Entity Name
ITORH120
II. Description
It is the count of requests for inter-MSC outgoing handovers from the observed 3G cell,
3-125

z Basic outgoing handover from MSCa: MSCa receives the message
RELOCATION REQUIRED from the originating RNC. See point A’ in the following
figure. Both the observed RNC and the counter are located in MSCa.
z Subsequent handover of MSCb: MSCb sends the request for subsequent
handover back to MSCa or a third party after inter-MSC handover completes. See
point A’’ in the following figure. Both the observed RNC and the counter are
located in MSCb.
S_RNC MSOFTX3000-A MSOFTX3000-B
RELOCATION REQUIRED
A'
IAM
ACM
RELOCATION COMMAND
PAS(RELOCATION DETECT)
SES(RELOCATIONCOMPLETE
)
B'
RNC MSOFTX3000-B MSOFTX3000-A

RELOCATION REQUIRED
A''
RELOCATION COMMAND
B''
IV. Formula
None
3-126
3.9.9 Count of Successful Inter-MSC Outgoing Handovers from RNC
I. Entity Name
SITORH120
II. Description
It is the count of successful inter-MSC outgoing handovers from the observed 3G cell,

z Basic outgoing handover from MSCa: MSCa receives the message
RELOCATION COMPLETE from MSCb. See point B’ in the following figure. Both
the observed RNC and the counter are located in MSCa.
z Subsequent handover of MSCb: MSCb receives the message
MAP_SEND_END_SIGNAL_CNF from MSCa after the subsequent handover
completes. See point B’’ in the following figure. Both the observed RNC and the
counter are located in MSCb.
3-127
S_RNC MSOFTX3000-A MSOFTX3000-B
RELOCATION REQUIRED
A'
IAM
ACM
RELOCATION COMMAND
PAS(RELOCATION DETECT)
SES(RELOCATION COMPLETE)
B'
RNC MSOFTX3000-B MSOFTX3000-A

RELOCATION REQUIRED
A''
RELOCATION COMMAND
B''
IV. Formula
None
3.9.10 Count of Outgoing Handovers from RNC Due to Time Critical
I. Entity Name
FRU120
II. Description
It is the count of outgoing handovers from the RNC due to time critical.
3-128
It is measured when the MSC receives the message IU_RELOCATION_REQUIRED,

with the cause value as “Time Critical Relocation”.
RNC MSC
Iu-Relocation-Required
IV. Formula
None
3.9.11 Count of Outgoing Handovers from RNC Due to Resource

Optimization
I. Entity Name
FRNS120
II. Description
It is the count of outgoing handovers from the RNC due to resource optimization.

with the cause value as “Resource Optimization”.
3-129
RNC MSC
IV. Formula
None
3.9.12 Count of Outgoing Handovers from RNC Due to Radio Resource
I. Entity Name
FRF120
II. Description
It is the count of outgoing handovers from the RNC due to radio resource.

with the cause value as “Relocation desirable for radio reasons”.
3-130
RNC MSC
IV. Formula
None
3.9.13 Count of Outgoing Handovers from RNC Due to Directed Retry
I. Entity Name
FRTE120
II. Description
It is the count of handovers from the RNC due to directed retry.

with the cause value as “Directed Retry”.
3-131
RNC MSC
IV. Formula
None
3.9.14 Count of Outgoing Handovers from RNC Due to O&M Intervention
I. Entity Name
OFRR120
II. Description
It is the count of outgoing handovers from the RNC due to O&M intervention.

with the cause value as “O&M Intervention”.
3-132
RNC MSC
IV. Formula
None
3.9.15 Count of Outgoing Handovers from RNC Due to Network Optimization
I. Entity Name
OFRO120
II. Description
It is the count of outgoing handovers from the RNC due to network optimization.

with the cause value as “Network Optimization”.
3-133
RNC MSC
IV. Formula
None
3.9.16 Count of Outgoing Handovers from RNC Due to Other Causes
I. Entity Name
OFTC120
II. Description
It is the count of outgoing handovers from the RNC due to other causes.
It is measured when the MSC receives the message IU_RELOCATION_REQUIRED

due to other causes.
3-134
RNC MSC
IV. Formula
None
3.9.17 Count of Handover Failures Due to RAB Preempted
I. Entity Name
OFDR120
II. Description
It is the count of handover failures due to RAB preempted.
It is measured when the MSC receives the message RELOCATION_FAILURE from

RNCa or RNCb, with the cause value as “rab preempted”.
3-135
RNC MSC
Handover-Failure
IV. Formula
None
3.9.18 Count of Handover Failures Due to Handover Timeout
I. Entity Name
OFOR120
II. Description
It is the count of handover failures due to handover timeout.

RNCa or RNCb, with the cause value as “relocation overall expiry”.
3-136
RNC MSC
Handover-Failure
IV. Formula
None
3.9.19 Count of Handover Failures Due to Timeout of Preparing Handover
I. Entity Name
ATDF120
II. Description
It is the count of handover failures due to timeout of resource preparation.

RNCa or RNCb, with the cause value as “Trelocprep_Expiry”.
3-137
RNC MSC
Handover-Failure
IV. Formula
None
3.9.20 Count of Handover Failures Due to Timeout of Waiting for Relocation

Complete Message
I. Entity Name
IUYYT120
II. Description
It is the count of handover failures due to timeout of waiting for the relocation complete
message.

RNCa or RNCb, with the cause value as “Treloccomplete_Expiry”.
3-138
RNC MSC
Handover-Failure
IV. Formula
None
3.9.21 Count of Handover Failures Due to Timeout of Queuing Radio

Interface
I. Entity Name
ARHS120
II. Description
It is the count of handover failures due to timeout of queuing the radio interface.

RNCa or RNCb, with the cause value as “queuing expiry”.
3-139
RNC MSC
Handover-Failure
IV. Formula
None
3.9.22 Count of Handover Failures Due to Timeout of Allocating Resource
I. Entity Name
ASIH120
II. Description
It is the count of handover failures due to timeout of allocating resources.

RNCa or RNCb, with the cause value as “relocation resource allocation expiry”.
3-140
RNC MSC
Handover-Failure
IV. Formula
None
3.9.23 Count of Handover Failures Due to Establishing Radio Interface

Unsuccessfully
I. Entity Name
AIORH120
II. Description
It is the count of handover failures due to establishing the radio interface

unsuccessfully.

RNCa or RNCb, with the cause value as “Unable to Establish During Relocation”.
3-141
RNC MSC
Handover-Failure
IV. Formula
None
3.9.24 Count of Handover Failures Due to Unknown Target Cell
I. Entity Name
ASIOH120
II. Description
It is the count of handover failures due to unknown target cell.

RNCa or RNCb, with the cause value as “rab preempted”.
3-142
RNC MSC
Handover-Failure
IV. Formula
None
3.9.25 Count of Handover Failures Due to Handover Cancelled
I. Entity Name
AITRH120
II. Description
It is the count of handover failures due to handover cancelled.

RNCa or RNCb, with the cause value as “Relocation Cancelled”.
3-143
RNC MSC
Handover-Failure
IV. Formula
None
3.9.26 Count of Handover Failures Due to Requested Ciphering Algorithm

Not Supported
I. Entity Name
ASITR120
II. Description
It is the count of handover failures due to requested ciphering algorithm not supported.

RNCa or RNCb, with the cause value as “Requested Ciphering and/or Integrity
Protection Algorithms not supported”.
3-144
RNC MSC
Handover-Failure
IV. Formula
None
3.9.27 Count of Handover Failures Due to Change of Ciphering Algorithm
I. Entity Name
ATORH120
II. Description
It is the count of handover failures due to requested ciphering and integrity algorithms
changed and not supported.

RNCa or RNCb, with the cause value as “Change of Ciphering and/or Integrity
Protection is not supported”.
3-145
RNC MSC
Handover-Failure
IV. Formula
None
3.9.28 Count of Handover Failures Due to Radio Interface Failure
I. Entity Name
ATRIH120
II. Description
It is the count of handover failures due to radio interface failure.

RNCa or RNCb, with the cause value as “Failure in the Radio Interface Procedure”.
3-146
RNC MSC
Handover-Failure
IV. Formula
None
3.9.29 Count of Handover Failures Due to UTRAN
I. Entity Name
AFRU120
II. Description
It is the count of handover failures due to UTRAN causes.

RNCa or RNCb, with the cause value as “Release due to UTRAN Generated Reason”.
3-147
RNC MSC
Handover-Failure
IV. Formula
None
3.9.30 Count of Handover Failures Due to Requested Traffic Class

Unavailable
I. Entity Name
AFRNS120
II. Description
It is the count of handover failures due to requested traffic class unavailable.

RNCa or RNCb, with the cause value as “Requested Traffic Class not Available”.
3-148
RNC MSC
Handover-Failure
IV. Formula
None
3.9.31 Count of Handover Failures Due to Invalid RAB Parameter Value
I. Entity Name
AFRF120
II. Description
It is the count of handover failures due to invalid RAB parameters.

RNCa or RNCb, with the cause value as “Invalid RAB Parameters Value”.
3-149
RNC MSC
Handover-Failure
IV. Formula
None
3.9.32 Count of Handover Failures Due to Requested Maximum Bit Rate

Unavailable
I. Entity Name
AFRTE120
II. Description
It is the count of handover failures due to requested maximum bit rate unavailable.

RNCa or RNCb, with the cause value as “Requested Maximum Bit Rate not Available”.
3-150
RNC MSC
Handover-Failure
IV. Formula
None
3.9.33 Count of Handover Failures Due to Requested Guaranteed Bit Rate

Unavailable
I. Entity Name
AOFRR120
II. Description
It is the count of handover failures due to requested guaranteed bit rate unavailable.

RNCa or RNCb, with the cause value as “Requested Guaranteed Bit Rate not
Available”.
3-151
RNC MSC
Handover-Failure
IV. Formula
None
3.9.34 Count of Handover Failures Due to Requested Transfer Delay

Unachievable
I. Entity Name
AOFRO120
II. Description
It is the count of handover failures due to requested transfer delay unachievable.

RNCa or RNCb, with the cause value as “Requested Transfer Delay not Achievable”.
3-152
RNC MSC
Handover-Failure
IV. Formula
None

Combination
I. Entity Name
AOFTC120
II. Description
It is the count of handover failures due to invalid RAB parameter combination.

RNCa or RNCb, with the cause value as “Invalid RAB Parameters Combination”.
3-153
RNC MSC
Handover-Failure
IV. Formula
None
3.9.36 Count of Handover Failures Due to Violation of SDU Parameter

Conditions
I. Entity Name
AOFDR120
II. Description
It is the count of handover failures due to violation of requested SDU parameter

conditions.

RNCa or RNCb, with the cause value as “Condition Violation for SDU Parameters”.
3-154
RNC MSC
Handover-Failure
IV. Formula
None
3.9.37 Count of Handover Failures Due to Violation of Traffic Handling

Priority Conditions
I. Entity Name
AOFOR120
II. Description
It is the count of handover failures due to violation of requested traffic handling priority
conditions.

RNCa or RNCb, with the cause value as “Condition Violation for Traffic Handling
Priority”.
3-155
RNC MSC
Handover-Failure
IV. Formula
None
3.9.38 Count of Handover Failures Due to Violation of Requested

Guaranteed Bit Rate Conditions
I. Entity Name
ATDK120
II. Description
It is the count of handover failures due to violation of requested guaranteed bit rate
conditions.

RNCa or RNCb, with the cause value as “Condition Violation for Guaranteed Bit Rate”.
3-156
RNC MSC
Handover-Failure
IV. Formula
None
3.9.39 Count of Handover Failures Due to User Plane Version Not Supported
I. Entity Name
AIUYT120
II. Description
It is the count of handover failures due to user plane version mismatch.

RNCa or RNCb, with the cause value as “User Plane Versions not Supported”.
3-157
RNC MSC
Handover-Failure
IV. Formula
None
3.9.40 Count of Handover Failures Due to Iu UP Negotiation Failure
I. Entity Name
DRHS120
II. Description
It is the count of handover failures due to Iu UP negotiation failure.

RNCa or RNCb, with the cause value as “Iu UP Failure”.
3-158
RNC MSC
Handover-Failure
IV. Formula
None
3.9.41 Count of Handover Failures Due to Target System Failure
I. Entity Name
DSIH120
II. Description
It is the count of handover failures due to target system failure.

RNCa or RNCb, with the cause value as “Relocation Failure in Target CN/RNC or
Target System”.
3-159
RNC MSC
Handover-Failure
IV. Formula
None
3.9.42 Count of Handover Failures Due to Invalid RAB ID
I. Entity Name
DIORH120
II. Description
It is the count of handover failures due to invalid RAB ID.

RNCa or RNCb, with the cause value as “Invalid RAB ID”.
3-160
RNC MSC
Handover-Failure
IV. Formula
None
3.9.43 Count of Handover Failures Due to No Remaining RAB
I. Entity Name
DSIOH120
II. Description
It is the count of handover failures due to no RAB available.

RNCa or RNCb, with the cause value as “No remaining RAB”.
3-161
RNC MSC
Handover-Failure
IV. Formula
None
3.9.44 Count of Handover Failures Due to Interaction with Other Procedures
I. Entity Name
DITRH120
II. Description
It is the count of handover failures due to interaction with other procedures.

RNCa or RNCb, with the cause value as “Interaction with other procedure”.
3-162
RNC MSC
Handover-Failure
IV. Formula
None
3.9.45 Count of Handover Failures Due to Requested Maximum Bit Rate for
Downlink Unavailable
I. Entity Name
DSITR120
II. Description
It is the count of handover failures due to requested maximum bit rate for downlink
unavailable.

RNCa or RNCb, with the cause value as “Requested Maximum Bit Rate for DL not
Available”.
3-163
RNC MSC
Handover-Failure
IV. Formula
None
3.9.46 Count of Handover Failures Due to Requested Maximum Bit Rate for
Uplink Unavailable
I. Entity Name
DTORH120
II. Description
It is the count of handover failures due to requested maximum bit rate for uplink
unavailable.

RNCa or RNCb, with the cause value as “Requested Maximum Bit Rate for UL not
Available”.
3-164
RNC MSC
Handover-Failure
IV. Formula
None
3.9.47 Count of Handover Failures Due to Requested Guaranteed Bit Rate for
Downlink Unavailable
I. Entity Name
DTRIH120
II. Description
It is the count of handover failures due to requested guaranteed bit rate for downlink
unavailable.

RNCa or RNCb, with the cause value as “Requested Guaranteed Bit Rate for DL not
Available”.
3-165
RNC MSC
Handover-Failure
IV. Formula
None
3.9.48 Count of Handover Failures Due to Requested Guaranteed Bit Rate for
Uplink Unavailable
I. Entity Name
DFRU120
II. Description
It is the count of handover failures due to requested guaranteed bit rate for uplink
unavailable.

RNCa or RNCb, with the cause value as “Requested Guaranteed Bit Rate for UL not
Available”.
3-166
RNC MSC
Handover-Failure
IV. Formula
None
3.9.49 Count of Handover Failures Due to Repeated Consistency Check

Failure
I. Entity Name
DFRNS120
II. Description
It is the count of handover failures due to repeated integrity check failure.

RNCa or RNCb, with the cause value as “Repeated Integrity Checking Failure”.
3-167
RNC MSC
Handover-Failure
IV. Formula
None
3.9.50 Count of Handover Failures Due to UE Generated Signaling

Connection Released
I. Entity Name
DFRF120
II. Description
It is the count of handover failures due to UE generated signaling connection released.

RNCa or RNCb, with the cause value as “Release due to UE generated signaling
connection release”.
3-168
RNC MSC
Handover-Failure
IV. Formula
None
3.9.51 Count of Handover Failures Due to Requested Information

Unavailable
I. Entity Name
DFRTE120
II. Description
It is the count of handover failures due to requested information unavailable.

RNCa or RNCb, with the cause value as “Requested Information Not Available”.
3-169
RNC MSC
Handover-Failure
IV. Formula
None
3.9.52 Count of Handover Failures Due to Target System Not Supported
I. Entity Name
DOFRR120
II. Description
It is the count of handover failures due to target system not supported.

RNCa or RNCb, with the cause value as “Relocation not supported in Target RNC or
Target system”.
3-170
RNC MSC
Handover-Failure
IV. Formula
None
3.9.53 Count of Handover Failures Due to Radio Connection with UE Lost
I. Entity Name
DOFRO120
II. Description
It is the count of handover failures due to radio connection with UE lost.

RNCa or RNCb, with the cause value as “Radio Connection With UE Lost”.
3-171
RNC MSC
Handover-Failure
IV. Formula
None
3.9.54 Count of Handover Failures Due to RNC Unable to Establish All RFCs
I. Entity Name
DOFTC120
II. Description
It is the count of handover failures due to RNC unable to establish all RFCs.

RNCa or RNCb, with the cause value as “Rnc unable to establish all RFCs”.
3-172
RNC MSC
Handover-Failure
IV. Formula
None
3.9.55 Count of Handover Failures Due to Target Not Allowed
I. Entity Name
DOFDR120
II. Description
It is the count of handover failures due to relocation target not allowed.

RNCa or RNCb, with the cause value as “Relocation target not allowed”.
3-173
RNC MSC
Handover-Failure
IV. Formula
None
3.9.56 Count of Handover Failures Due to Signaling Transport Resource

Failure
I. Entity Name
DOFOR120
II. Description
It is the count of handover failures due to signaling transport resource failure.

RNCa or RNCb, with the cause value as “Signaling Transport Resource Failure”.
3-174
RNC MSC
Handover-Failure
IV. Formula
None
3.9.57 Count of Handover Failures Due to Iu Transport Connection Setup

Failure
I. Entity Name
DTDK120
II. Description
It is the count of handover failures due to Iu transport connection setup failure.

RNCa or RNCb, with the cause value as “Iu Transport Connection Failed to Establish”.
3-175
RNC MSC
Handover-Failure
IV. Formula
None
3.9.58 Count of Handover Failures Due to Protocol Failure
I. Entity Name
CTDK120
II. Description
It is the count of handover failures due to protocol failure.

RNCa or RNCb, with the cause value as “Abstract Syntax Error”.
3-176
RNC MSC
Handover-Failure
IV. Formula
None
3.9.59 Count of Handover Failures Due to No Resource Available
I. Entity Name
DIUYT120
II. Description
It is the count of handover failures due to no resource available.

RNCa or RNCb, with the cause value as “No Resource Available”.
3-177
RNC MSC
Handover-Failure
IV. Formula
None
3.9.60 Count of Handover Failures Due to Unspecified Cause
I. Entity Name
COFOR120
II. Description
It is the count of handover failures due to unknown causes.

RNCa or RNCb, with the cause value as “Unspecified Failure”.
3-178
RNC MSC
Handover-Failure
IV. Formula
None
3.10 Ciphering Mode Setting

3.10.1 Overview of MS_S_CIPHER_TRAF
Name Description
ULCMSRN Count of requests for setting ciphering mode during location update
Count of successes in setting ciphering mode during location

ULCMSSN
update
SACMSRN Count of requests for setting ciphering mode during service access
SACMSSN Count of successes in setting ciphering mode during service access
3.10.2 Count of Requests for Setting Ciphering Mode During Location

Update
I. Entity Name
ULCMSRN
II. Description
It is the count of requests for setting the ciphering mode during location update.
3-179
It is measured when the MSC sends the message SECURITY MODE COMMAND to
the RNC or CIPHER MODE COMMAND to the BSC during location update.
In 2G networks:
BSC MSC Server
LOCATION_UPD_REQ
A
Cipher_Mode_Command
In 3G networks:
RNC MSC Server
ION_REQUEST
A
RN_SECURITY_MODE_CO
MMAND
IV. Formula
None
3-180
3.10.3 Count of Successes in Setting Ciphering Mode During Location

Update
I. Entity Name
ULCMSSN
II. Description
It is the count of successes in setting the ciphering mode during location update.
It is measured when the MSC receives the message SECURITY MODE COMPLETE
from the RNC or CIPHER MODE COMPLETE from the BSC during location
registration.
In 2G networks:
BSC MSC Server
A
In 3G networks:
3-181
RNC MSC Server
COMPLETE
A
ING_ACCEPT
IV. Formula
None
3.10.4 Count of Requests for Setting Ciphering Mode During Service Access
I. Entity Name
SACMSRN
II. Description
It is the count of requests for setting the ciphering mode during service (including calls,
supplementary services, and SMS) processing.
It is measured when the MSC sends the message SECURITY MODE COMMAND to
the RNC or CIPHER MODE COMMAND to the BSC during location update.
In 2G networks:
3-182
BSC MSC Server
CM_Service_Request
A
Cipher_Mode_Command
In 3G networks:
RNC MSC Server
ION_REQUEST
A
SECURITY_MODE_COMMA
ND
IV. Formula
None
3.10.5 Count of Successes in Setting Ciphering Mode During Service Access
I. Entity Name
SACMSSN
II. Description
It is the count of successes in setting the ciphering mode during service (including calls,
supplementary services, and SMS) processing.
3-183
It is measured when the MSC receives the message SECURITY MODE COMPLETE
from the RNC or CIPHER MODE COMPLETE from the BSC during location
registration.
In 2G networks:
BSC MSC Server
A
CM_Service_Accept
In 3G networks:
RNC MSC Server
SECURITY_MODE_COMPLE
TE
A
EPT
IV. Formula
None
3-184
3.11 Paging
3.11.1 Overview of MS_S_PAGING_TRAF
Name Description
AIFSPN Count of PAGING messages first sent through A-interface
Count of responses for PAGING messages first sent through
AIFPRN
A-interface
AIRSPN Count of PAGING messages repeatedly sent through A-interface

Count of responses for PAGING messages repeatedly sent
AIRPRN
through A-interface
IUIFSPN Count of PAGING messages first sent through Iu-interface
IUIFPRN
Iu-interface
IUIRSPN Count of PAGING messages repeatedly sent through Iu-interface

IUIRPRN
through Iu-interface
GIFSPN Count of PAGING messages first sent through Gs-interface

GIFPRN
Gs-interface
Count of PAGING messages repeatedly sent through
GIRSPN
Gs-interface
GIRPRN
through Gs-interface
3.11.2 Count of PAGING Messages First Sent Through A-Interface
I. Entity Name
AIFSPN
II. Description
It is the count of PAGING messages that the MSC sends to the A-interface for the first
time for each call.
It is measured when the MSC sends the PAGING message to the BSC.
3-185
BSC MSC Server
PAGING
……
A
PAGING
PAGING RESPONSE
IV. Formula
None
3.11.3 Count of Responses for PAGING Messages First Sent Through

A-Interface
I. Entity Name
AIFPRN
II. Description
It is the count of responses that the MSC receives from the MS after sending PAGING
messages to the A-interface for the first time.
It is measured when the MSC receives the message PAGING RESPONSE from the
callee after sending PAGING messages to the BSC for the first time.
3-186
BSC MSC Server
PAGING
PAGING RESPONSE
IV. Formula
None
3.11.4 Count of PAGING Messages Repeatedly Sent Through A-Interface
I. Entity Name
AIRSPN
II. Description
It is the count of PAGING messages that the MSC sends to the A-interface not for the
first time for each call.
It is measured when the MSC sends the message BSSMAP PAGING to the BSC not for
the first time.
See point A1 in the following figure.
3-187
BSC MSC Server
PAGING
PAGING
……
A1
PAGING
An
PAGING RESPONSE
IV. Formula
None

A-Interface
I. Entity Name
AIRPRN
II. Description
messages to the A-interface not for the first time for each call.
callee after sending PAGING messages to the BSC not for the first time.
3-188
BSC MSC Server
PAGING
……
PAGING
PAGING RESPONSE
IV. Formula
None
3.11.6 Count of PAGING Messages First Sent Through Iu-Interface
I. Entity Name
IUIFSPN
II. Description
It is the count of PAGING messages that the MSC sends to the Iu-interface for the first
time for each call.
It is measured when the MSC sends the PAGING message to the Iu-interface for the
3-189
RNC MSC Server
PAGING
……
A
PAGING
RN_RR_PAGING_RESPONSE
IV. Formula
None

Iu-Interface
I. Entity Name
IUIFPRN
II. Description
messages to the Iu-interface for the first time for each call.
callee after sending PAGING messages to the RNC for the first time.
3-190
RNC MSC Server
PAGING
PAGING RESPONSE
IV. Formula
None
3.11.8 Count of PAGING Messages Repeatedly Sent Through Iu-Interface
I. Entity Name
IUIRSPN
II. Description
It is the count of PAGING messages that the MSC sends to the Iu-interface not for the
It is measured when the MSC sends the message BSSMAP PAGING to the RNC not
for the first time.
3-191
RNC MSC Server
PAGING
PAGING
……
A1
PAGING
An
IV. Formula
None

Iu-Interface
I. Entity Name
IUIRPRN
II. Description
messages to the Iu-interface not for the first time for each call.
callee after sending PAGING messages to the RNC not for the first time.
3-192
RNC MSC Server
PAGING
……
PAGING
IV. Formula
None
3.11.10 Count of PAGING Messages First Sent Through Gs-Interface
I. Entity Name
GIFSPN
II. Description
It is the count of PAGING messages that the MSC sends to the Gs-interface for the first
time for each call.
It is measured when the MSC sends the PAGING message to the SGSN.
3-193
RNS SGSN MSC Server
PAGING_Req
……
A
PAGING_Req
PAGING RESPONSE
IV. Formula
None

Gs-Interface
I. Entity Name
GIFPRN
II. Description
It is the count of PAGING RESPONSE messages that the MSC sends to the
Gs-interface for the first time for each call.
It is measured when the MSC sends the message PAGING RESPONSE to the SGSN.
3-194
RNS SGSN MSC Server
PAGING_Req
PAGING RESPONSE
IV. Formula
None
3.11.12 Count of PAGING Messages Repeatedly Sent Through Gs-Interface
I. Entity Name
GIRSPN
II. Description
It is the count of PAGING messages that the MSC sends to the Gs-interface not for the
It is measured when the MSC sends the message BSSMAP PAGING to the SGSN not
for the first time.
3-195
RNS SGSN MSC Server
PAGING_Req
PAGING_Req
……
A1
PAGING_Req
An
PAGING RESPONSE
IV. Formula
None

Through Gs-Interface
I. Entity Name
GIRPRN
II. Description
It is the count of PAGING RESPONSE messages that the MSC sends to the
Gs-interface not for the first time for each call.
It is measured when the MSC sends the message BSSMAP PAGING RESPONSE to
the SGSN not for the first time.
3-196
RNS SGSN MSC Server
PAGING_Req
……
PAGING_Req
PAGING RESPONSE
IV. Formula
None
3-197
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 MSC Special Services
Chapter 4 MSC Special Services

The measurement set is used to measure the traffic of some special services, such as
data services. The measurement units are listed in the following table.
Name Description
MS_LCS_SRV Location services
MS_DIG_TRAF Bearer traffic
MS_LCS_NI_LR NI_LR location service

MS_LCS_MO_LR Mobile Originated location service
MS_LCS_MT_LR Mobile Terminated location service
4.2 Location Service

4.2.1 Overview of MS_LCS_SRV
Name Description
ELRN Count of location requests (emergency services)
ELSN Count of location successes (emergency services)
ISLRN Count of location requests (value-added services)
ISLSN Count of location successes (value-added services)
POLRN Count of location requests (PLMN operator services)
POLSN Count of location successes (PLMN operator services)
LILRN Count of location requests (lawful interception services)
LILSN Count of location successes (lawful interception services)
4.2.2 Count of Location Requests (Emergency Services)
I. Entity Name
ELRN
4-1
II. Description
It is the count of mobile terminating location requests (MT_LRs) when the service type
is EMERGENCY_SERVICES.

PROVIDE_SUBSCRIBER_LOCATION_REQ from the GMLC, with the service type as
EMERGENCY_SERVICES. See point A in the following figure.
GMLC MSC Server
PROVIDE_SUBSCRIBER_LOCATION_REQ
PROVIDE_SUBSCRIBER_LOCATION_RSP
IV. Formula
None
4.2.3 Count of Location Successes (Emergency Services)
I. Entity Name
ELSN
II. Description
It is the count of successful MT_LRs when the service type is

EMERGENCY_SERVICES.
It is measured after the MSC sends the message

PROVIDE_SUBSCRIBER_LOCATION_RSP to the GMLC, with the service type as
EMERGENCY_SERVICES. See point B in the following figure.
4-2
GMLC MSC Server
IV. Formula
None
4.2.4 Count of Location Requests (Value-Added Services)
I. Entity Name
ISLRN
II. Description
It is the count of MT_LRs when the service type is VALUE_ADDED_SERVICES.

VALUE_ADDED_SERVICES. See point A in the following figure.
4-3
GMLC MSC Server
IV. Formula
None
4.2.5 Count of Location Successes (Value-Added Services)
I. Entity Name
ISLSN
II. Description

VALUE_ADDED_SERVICES.

VALUE_ADDED_SERVICES. See point B in the following figure.
4-4
GMLC MSC Server
IV. Formula
None
4.2.6 Count of Location Requests (PLMN Operator Services)
I. Entity Name
POLRN
II. Description
It is the count of MT_LRs when the service type is PLMN_OPERTATOR_SERVICES.

4-5
PLMN_OPERTATOR_SERVICES.
GMLC MSC Server
IV. Formula
None
4.2.7 Count of Location Successes (PLMN Operator Services)
I. Entity Name
POLSN
II. Description

PLMN_OPERTATOR_SERVICES.
4-6

PLMN_OPERTATOR_SERVICES. See point B in the following figure.
GMLC MSC Server
IV. Formula
None
4.2.8 Count of Location Requests (Lawful Interception Services)
I. Entity Name
LILRN
II. Description
It is the count of MT_LRs when the service type is LAWFUL_INTERCEPT_SERVICES.

LAWFUL_INTERCEPT_SERVICES. See point A in the following figure.
4-7
GMLC MSC Server
IV. Formula
None
4.2.9 Count of Location Successes (Lawful Interception Services)
I. Entity Name
LILSN
II. Description
It is the count of MT_LRs when the service type is LAWFUL_INTERCEPT_SERVICES.

LAWFUL_INTERCEPT_SERVICES. See point B in the following figure.
4-8
GMLC MSC Server
IV. Formula
None
4.3 Bearer Services

4.3.1 Overview of MS_DIG_TRAF
Name Description
BS2X125 Count of use of asynchronous digital service BS2x
BS2XU125 Traffic of asynchronous digital service BS2x
BS4X125 Count of use of dedicated digital service BS4x

BS4XU125 Traffic of dedicated digital service BS4x
BS3X125 Count of use of bearer service BS3x
BS3XU125 Traffic of bearer service BS3x

BS5X125 Count of use of dedicated packet service BS5x
BS5XU125 Traffic of dedicated packet service BS5x
FAX125 Count of use of fax digital service

FAXU125 Traffic of fax digital service
Count of use of alternate voice/data synchronous digital
SD125
service
ADU125 Traffic of alternate voice/data synchronous digital service
BS20125 Count of use of asynchronous digital service BS20

BS20T125 Traffic of asynchronous digital service BS20
4-9
Name Description
BS30125 Count of use of basic packet service BS30
BS30T125 Traffic of basic packet service BS30
4.3.2 Count of Use of Asynchronous Digital Service BS2X
I. Entity Name
BS2X125
II. Description
It is the count of use of digital services with rates of 300 bit/s, 1.2 kbit/s, 4.8 kbit/s and
9.6 kbit/s, and asynchronous duplex circuit digital services.
It is measured according to different bearer service codes, when the BC is an

asynchronous data service after a call is connected. See point A in the following figure.
O_UE MSC Server T_UE
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4.3.3 Traffic of Asynchronous Digital Service BS2X
I. Entity Name
BS2XU125
II. Description
It is the traffic of digital services with rates of 300 bit/s, 1.2 kbit/s, 4.8 kbit/s and 9.6 kbit/s,
and asynchronous duplex circuit digital services.
4-10
It is measured in the duration of BS2X data calls. The final value is indicated in Erlang.
IV. Formula
None
4.3.4 Count of Use of Dedicated Digital Service BS4X
I. Entity Name
BS4X125
II. Description
It is the count of use of digital services with rates of 300 bit/s, 1.2 kbit/s, 2.4 kbit/s and
4.8 kbit/s, and dedicated PAD access circuit digital services
It is measured according to different bearer service codes after a call is set up. See
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4.3.5 Traffic of Dedicated Digital Service BS4X
I. Entity Name
BS4XU125
4-11
II. Description
It is the traffic of digital services with rates of 300 bit/s, 1.2 kbit/s, 2.4 kbit/s, 4.8 kbit/s
and 9.6 kbit/s, and dedicated PAD access circuit digital services
IV. Formula
None
4.3.6 Count of Use of Synchronous Digital Service BS3X
I. Entity Name
BS3X125
II. Description
It is the count of use of digital services with rates of 300 bit/s, 1.2 kbit/s, 2.4 kbit/s, 4.8
kbit/s and 9.6 kbit/s, and synchronous duplex circuit digital services
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4-12
4.3.7 Traffic of Synchronous Digital Service BS3X
I. Entity Name
BS3XU125
II. Description
It is the traffic of digital services with rates of 300 bit/s, 1.2 kbit/s, 4.8 kbit/s and 9.6 kbit/s,
and asynchronous duplex circuit digital services.
IV. Formula
None
4.3.8 Count of Use of Dedicated Packet Service BS5X
I. Entity Name
BS5X125
II. Description
It is the count of use of packet services with rates of 2.4 kbit/s, 4.8 kbit/s and 9.8 kbit/s,
and dedicated packet services.
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4-13
4.3.9 Traffic of Dedicated Packet Service BS5X
I. Entity Name
BS5XU125
II. Description
It is the traffic of packet services with rates of 2.4 kbit/s, 4.8 kbit/s and 9.8 kbit/s, and
dedicated packet services.
IV. Formula
None
4.3.10 Count of Use of Fax Digital Service
I. Entity Name
FAX125
II. Description
It is the count of use of automatic facsimile G3 digital services.
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4-14
4.3.11 Traffic of Fax Digital Service
I. Entity Name
FAXU125
II. Description
It is the traffic of automatic facsimile G3 digital services.
It is measured in the duration of automatic facsimile G3 calls. The final value is

indicated in Erlang.
IV. Formula
None
4.3.12 Count of Use of Alternate Speech/Data Synchronous Digital Service
I. Entity Name
SD125
II. Description
It is the count of use of alternate speech or facsimile G3 digital services, alternate

speech or data synchronous digital services, and alternate speech or data
asynchronous digital services.
4-15
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4.3.13 Traffic of Alternate Speech/Data Synchronous Digital Service
I. Entity Name
ADU125
II. Description
It is the traffic of alternate speech or facsimile G3 digital services, alternate speech or

data synchronous digital services, and alternate speech or data asynchronous digital
services.
It is measured in the duration of alternate speech or data digital calls. The final value is
IV. Formula
None
4.3.14 Count of Use of Asynchronous Digital Service BS20
I. Entity Name
BS20125
II. Description
It is the count of use of asynchronous circuit digital services (BS20).
4-16
It is measured when the BC is BS20 when a call is set up in the bearer service. See
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4.3.15 Traffic of Asynchronous Data Service BS20
I. Entity Name
BS20T125
II. Description
It is the traffic of asynchronous circuit digital services (BS20).
It is measured in the duration of BS20 data calls in a measurement period. The final
value is indicated in Erlang.
IV. Formula
None
4.3.16 Count of Use of Basic Packet Service BS30
I. Entity Name
BS30125
II. Description
It is the count of use of basic packet bearer services (BS30).
4-17
It is measured when the BC is BS30 when a call is set up. See point A in the following
figure.
CONNECT
CONNECT
CONNECT ACK
CONNECT ACK
IV. Formula
None
4.3.17 Traffic of Basic Packet Service BS30
I. Entity Name
BS30T125
II. Description
It is the traffic of basic packet bearer services (BS30).
It is measured in the duration of BS30 data calls in a measurement period. The final
value is indicated in Erlang.
IV. Formula
None
4.4 NI_LR Location

4.4.1 Overview of MS_LCS_NI_LR
Name Description
NILRT Count of NI_LRs
4-18
Name Description
NILST Count of NI_LR successes
NIFSF Count of NI_LR failures due to system failure
NIFUD Count of NI_LR failures due to unqualified data
NIFDM Count of NI_LR failures due to lack of data
NIFRL Count of NI_LR failures due to resource limitation
Count of location failures due to timeout in waiting for
NIFGRTO
Report_CNF from GMLC
Count of location failures due to timeout in waiting for UE

NIFURTO
location report message
4.4.2 Count of NI_LRs
I. Entity Name
NILRT
II. Description
It is the count of network induced location requests (NI_LRs) triggered by emergency

calls.
It is measured after the emergency call made by the destination UE is set up. See point
A in the following figure.
4-19
RNC MSC Server GMLC

SETUP
LOCATION_REPORTING A
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
B
IV. Formula
None
4.4.3 Count of NI_LR Successes
I. Entity Name
NILST
II. Description
It is the count of successful NI_LRs triggered by emergency calls.
It is measured when the MSC receives the message Subscriber Location Report RSP
after sending the message Subscriber Location Report to the GMLC. See point B in the
following figure.
4-20
RNC MSC Server GMLC

SETUP
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
B
IV. Formula
None
4.4.4 Count of NI_LR Failures Due to System Failure
I. Entity Name
NIFSF
II. Description
It is the count of NI_LR failures due to system failure.
It is measured when the system failure occurs between point A and point B during the
NI_LR, as shown in the following figure.
4-21
RNC MSC Server GMLC

SETUP
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
B
IV. Formula
None
4.4.5 Count of NI_LR Failures Due to Unqualified Data
I. Entity Name
NIFUD
II. Description
It is the count of NI_LR failures due to unqualified data.
It is measured when the unqualified data is received between point A and point B during
the NI_LR, as shown in the following figure.
4-22
RNC MSC Server GMLC

SETUP
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
B
IV. Formula
None
4.4.6 Count of NI_LR Failures Due to Lack of Data
I. Entity Name
NIFDM
II. Description
It is the count of NI_LR failures due to lack of data.
It is measured when there is lack of data between point A and point B during the NI_LR,
as shown in the following figure.
4-23
RNC MSC Server GMLC

SETUP
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
B
IV. Formula
None
4.4.7 Count of NI_LR Failures Due to Resource Limitation
I. Entity Name
NIFRL
II. Description
It is the count of NI_LR failures due to resource limitation.
It is measured when the resources are limited between point A and point B during the
NI_LR, as shown in the following figure.
4-24
RNC MSC Server GMLC

SETUP
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
B
IV. Formula
None
4.4.8 Count of Location Failures Due to Timeout in Waiting for Report_CNF

from GMLC
I. Entity Name
NIFGRTO
II. Description
It is the count of location failures due to timeout in waiting for the location report
response from the GMLC during the NI_LR.
It is measured when the MSC times out in waiting for the location report response from
the GMLC during the NI_LR. See point B in the following figure.
4-25
RNC MSC Server GMLC

SETUP
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
IV. Formula
None
4.4.9 Count of Location Failures Due to Timeout in Waiting for UE Location

Report Message
I. Entity Name
NIFURTO
II. Description
It is the count of location failures due to timeout in waiting for the UE location report
message during the NI_LR.
It is measured when the MSC times out in waiting for the location report response from
the RNC during the NI_LR. See point B in the following figure.
4-26
RNC MSC Server GMLC

SETUP
_CONTROL
IV. Formula
None
4.5 Mobile-Originated Location Service

4.5.1 Overview MS_LCS_MO_LR
Name Description
MOLRT Count of MO location requests
MOLST Count of MO location successes
MOFMSF Count of MO location failures due to MSC failure

MOFMUDV Count of MO location failures due to unqualified data from MSC
MOFMDM Count of MO location failures due to lack of data at MSC
Count of MO location failures due to inconsistent information

MOFMFNS
format at MSC
MOFMSSV Count of MO location failures due to unauthorized data at MSC
Count of MO location failures due to location method failure at
MOFMPMF
MSC
MOFGSF Count of MO location failures due to GMLC failure

MOFGDM Count of MO location failures due to lack of data at GMLC
Count of MO location failures due to resource limitation at

MOFGRL
GMLC
Count of MO location failures due to unqualified data from

MOFGUDV
GMLC
4-27
Name Description
Count of MO location failures due to unknown subscriber at
MOFGUS
GMLC
Count of MO location failures due to unauthorized network at
MOFGUARN
GMLC
Count of MO location failures due to unknown/unreachable
MOFGULC
LCS client at GMLC
Count of MO location failures due to timeout in waiting for
MOFGRCTO
REPORT_CNF message from GMLC
Count of MO location failures due to timeout in waiting for UE
MOFURTO
location report response from RNC
4.5.2 Count of MO Location Requests
I. Entity Name
MOLRT
II. Description
It is the count of MO location requests to the MSC.
It is measured when the MSC receives the MO location requests. See point A in the
following figure.
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
MOLR_RESULT _REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4-28
4.5.3 Count of MO Location Successes
I. Entity Name
MOLST
II. Description
It is the count of successes in locating mobile phones precisely, and sending it to the
mobile phones and the GMLC of the third party (if required).
It is measured in the function (if required) used to report location to the third party or
when the MSC sends the message SUBSCRIBER_LOCATION_REPORT_RSP to a
mobile subscriber. See point B in the following figure.
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.4 Count of MO Location Failures Due to MSC Failure
I. Entity Name
MOFMSF
II. Description
It is the count of MO location failures that are not caused by the flow.
It is measured when the system failure occurs between point A and point B.
4-29
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.5 Count of MO Location Failures Due to Unqualified Data from MSC
I. Entity Name
MOFMUDV
II. Description
It is the count of location failures due to unqualified data received by the GMLC of the
third party in the location result sent from the MSC.
It is measured when the MSC receives the message Location Report RSP from the
GMLC. See point B in the following figure.
4-30
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.6 Count of MO Location Failures Due to Lack of Data at MSC
I. Entity Name
MOFMDM
II. Description
It is the count of location failures due to lack of required cells in MO location requests.
It is measured when the required cell does not exist in a MO location request received
by the MSC. See point A in the following figure.
4-31
RNC MSC Server GMLC

MOLR_REQ
IV. Formula
None
4.5.7 Count of MO Location Failures Due to Inconsistent Information Format

at MSC
I. Entity Name
MOFMFNS
II. Description
It is the count of MO location failures due to inconsistent information formats in the

message Location Report and MO_LR Request.
It is measured when the MSC checks the format of the location information when
informing the third party of the location result. See point B in the following figure.
4-32
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
IV. Formula
None
4.5.8 Count of MO Location Failures Due to Unauthorized Data at VLR
I. Entity Name
MOFMSSV
II. Description
It is the count of MO location failures due to unauthorized subscription data in the VLR.
It is measured after the VLR responds to the subscription data. See point A in the
following figure.
4-33
RNC MSC Server GMLC

MOLR_REQ
IV. Formula
None
4.5.9 Count of MO Location Failures Due to Location Method Failure at MSC
I. Entity Name
MOFMPMF
II. Description
It is the count of messages with the cause value of location method failure returned
from the RNC.
It is measured when the RNC returns the location result. See point B in the following
figure.
4-34
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
IV. Formula
None
4.5.10 Count of MO Location Failures Due to GMLC Failure
I. Entity Name
MOFGSF
II. Description
It is the count of Location Report Response messages returned from the GMLC, with
the cause value as system failure.

SUBSCRIBER_LOCATION_REPORT_RSP from the GMLC. See point B in the
following figure.
4-35
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.11 Count of MO Location Failures Due to Lack of Data at GMLC
I. Entity Name
MOFGDM
II. Description
the cause value as lack of data.
4-36
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.12 Count MO Location Failures Due to Resource Limitation at GMLC
I. Entity Name
MOFGRL
II. Description
the cause value as resource limitation.
4-37
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.13 Count of MO Location Failures Due to Unqualified Data from GMLC
I. Entity Name
MOFGUDV
II. Description
the cause value as unexpected data.
4-38
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.14 Count of MO Location Failures Due to Unknown Subscriber at GMLC
I. Entity Name
MOFGUS
II. Description
the cause value as unknown subscriber.
4-39
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.15 Count of MO Location Failures Due to Unauthorized Network at GMLC
I. Entity Name
MOFGUARN
II. Description
the cause value as unauthorized network.
4-40
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None
4.5.16 Count of MO Location Failures Due to Unknown/Unreachable LCS

Client at GMLC
I. Entity Name
MOFGULC
II. Description
the cause value as unknown/unreachable LCS client.
4-41
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
SUBSCRIBER_LOCATION
_REPORT_RSP
IV. Formula
None

Report_CNF Message from GMLC
I. Entity Name
MOFGRCTO
II. Description
It is the count of timeout in waiting for the message Location Report Response from the
GMLC.
It is measured when the MSC times out in waiting for the message Location Report
from the GMLC. See point B in the following figure.
4-42
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
LOCATION_REPORT
SUBSCRIBER_LOCATION
_REPORT_REQ
IV. Formula
None
4.5.18 Count of MO Location Failures Due to Timeout in Waiting for UE

Location Report Response from RNC
I. Entity Name
MOFURTO
II. Description
It is the count of timeout in waiting for the message Location Report from the UE.
It is measured when the MSC times out in waiting for the message Location Report
Response from the RNC. See point B in the following figure.
4-43
RNC MSC Server GMLC

MOLR_REQ
_CONTROL
IV. Formula
None
4.6 Mobile-Terminated Location Service

4.6.1 Overview of MS_LCS_MT_LR
Name Description
MTLRT Count of MT location requests
MTLST Count of MT location successes
MTFMSF Count of MT location failures due to system failure

MTFMDM Count of MT location failures due to lack of data
MTFMUD Count of MT location failures due to unqualified data
Count of MT location failures due to inconsistent information

MTFMFNS
format
MTFMUS Count of MT location failures due to unknown subscriber
MTFMAS Count of MT location failures due to absent subscriber
MTFMNARN Count of MT location failures due to unauthorized network
MTFMUALC Count of MT location failures due to unauthorized LCS client

Count of MT location failures due to location method failure
MTFMPMF
from MC
Count of MT location failures due to timeout in waiting for UE

MTFURTO
location report response from MC
4-44
4.6.2 Count of MT Location Requests
I. Entity Name
MTLRT
II. Description
It is the count of MT location requests.

PROVIDE_SUBSCRIBER_LOCATION_REQ from the GMLC. See point A in the
following figure.
RNC MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
_CONTROL
LOCATION_REPORT
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.3 Count of MT Location Successes
I. Entity Name
MTLST
II. Description
It is the count of successes in receiving the location results after the external LCS
clients send the location requests through the GMLC.
4-45
It is measured in the function in the message

PROVIDE_SUBSCRIBER_LOCATION_RSP sent to the GMLC. See point B in the
following figure.
RNC MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
_CONTROL
LOCATION_REPORT
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.4 Count of MT Location Failures Due to System Failure
I. Entity Name
MTFMSF
II. Description
It is the count of MT location failures due to the system failure.
It is measured when the system failure occurs during the MT location (between point A
and point B), as shown in the following figure.
4-46
RNC MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
_CONTROL
LOCATION_REPORT
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.5 Count of MT Location Failures Due to Lack of Data
I. Entity Name
MTFMDM
II. Description
It is the count of MT location failures due to lack of data.
It is measured when some cells are missing in the message Location Request received
from the GMLC. See point A in the following figure.
4-47
MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.6 Count of MT Location Failures Due to Unqualified Data
I. Entity Name
MTFMUD
II. Description
It is the count of MT location failures due to unexpected data.
It is measured when the message Location Request received from the GMLC contains
unexpected data. See point A in the following figure.
4-48
MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.7 Count of MT Location Failures Due to Inconsistent Information Format
I. Entity Name
MTFMFNS
II. Description
It is the count of MT location failures due to inconsistent information formats in the

messages LOCATION_REPORT and
PROVIDE_SUBSCRIBER_LOCATION_REQUEST.
It is measured when the MSC checks the format of the location information when
informing the GMLC of the location result. See point B in the following figure.
4-49
RNC MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
_CONTROL
LOCATION_REPORT
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.8 Count of MT Location Failures Due to Unknown Subscriber
I. Entity Name
MTFMUS
II. Description
It is the count of MT location failures due to the unknown subscriber.
It is measured when the VLR does not contain the subscriber data. See point A in the
following figure.
4-50
MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.9 Count of MT Location Failures Due to Absent Subscriber
I. Entity Name
MTFMAS
II. Description
It is the count of MT location failures due to the absent subscriber.
It is measured when the VLR confirms that the located UE is in the state of IMSI
detachment or regional roaming limited. See point A in the following figure.
4-51
MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.10 Count of MT Location Failures Due to Unauthorized Network
I. Entity Name
MTFMNARN
II. Description
It is the count of MT location failures due to unauthorized GMLC.
It is measured when the GMLC authorization fails after the MSC checks the number
from the GMLC. See point A in the following figure.
4-52
MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.11 Count of MT Location Failures Due to Unauthorized LCS Client
I. Entity Name
MTFMUALC
II. Description
It is the count of MT location failures due to unauthorized LCS clients in MT-LRs from
the GMLC.
It is measured when the VLR responds to the subscription data. See point A in the
following figure.
4-53
MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.12 Count of MT Location Failures Due to Location Method Failure from

RNC
I. Entity Name
MTFMPMF
II. Description
It is the count of messages returned from the RNC in MT-LRs, with the cause value as
location method failure.
It is measured when the location result returned from the RNC does not contain the
location information. See point B in the following figure.
4-54
RNC MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
_CONTROL
LOCATION_REPORT
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4.6.13 Count of MT Location Failures Due to Timeout in Waiting for UE

Location Report Response from RNC
I. Entity Name
MTFURTO
II. Description
It is the count of timeout in waiting for the message Location_Report from the UEs in
MT-LRs.
It is measured when the MSC times out in waiting for the message Location_Report
from the RNC. See point B in the following figure.
4-55
RNC MSC Server GMLC
PROVIDE_SUBSCRIBER_
LOCATION_REQ
_CONTROL
PROVIDE_SUBSCRIBER_
LOCATION_RSP
IV. Formula
None
4-56
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Bearer Traffic
Chapter 5 Bearer Traffic

This measurement set contains measurement units that are divided by the objects
carrying different traffic. It is used to measure the traffic of all office directions.
Name Meaning
MS_MGW_DEST_TRAF Traffic between BICC MGs
MS_INTERMGW_TRAF Intra-Office path across MG
MS_OFFICEDIR_OUT_TRAF Office direction outgoing traffic
MS_OFFICEDIR_INC_TRAF Office direction incoming traffic
MS_DESTCODE_TRAF Destination code traffic
MS_OFFICE_DEST_DISTRIB_TRAF Destination traffic distribution

Traffic of supplementary services of
MS_SS_INVOKE
mobile subscribers
MS_TK_OFC_OUT_TRAF Trunk office direction outgoing traffic

MS_TK_OFC_INC_TRAF Trunk office direction incoming traffic
MS_TKGRP_OUT_TRAF Trunk group outgoing traffic

MS_TKGRP_INC_TRAF Trunk group incoming traffic
MS_VP_OFFICEDIR_INC_TRAF VP office direction incoming traffic
MS_VP_OFFICEDIR_OUT_TRAF VP office direction outgoing traffic
MS_VP_DEST_TRAF VP destination traffic
MS_TK_VP_OFC_INC_TRAF VP trunk office direction incoming traffic
MS_TK_VP_OFC_OUT_TRAF VP trunk office direction outgoing traffic
5-1
5.2 Traffic Between BICC MGs

5.2.1 Overview of MS_MGW_DEST_TRAF
Name Meaning
SEIZ Count of seizures
CNT Count of connected calls
ANS Count of answered calls
CBSY Count of callee busy
ARGABN Count of release before offhook

LTNANS Count of no reply
SERL Seizure traffic
CERL Traffic of connected calls

RERL Traffic of answered calls
CNTR Call completion rate
ANSR Call answer rate
5.2.2 Count of Seizures
I. Entity Name
SEIZ
II. Description
It is the count of received APMs indicating seizure of peer media gateways (MG).
It is measured when the mobile switching center (MSC) receives the APM with the BCU
ID of the peer MG. See point A in the following figure.
5-2
MSC Server MSC Server
IAM
APM
IV. Formula
None
5.2.3 Count of Connected Calls
I. Entity Name
CNT
II. Description
It is the count of messages indicating call connections.
It is measured when the MSC receives the Address Complete Message (ACM) from
the peer office. See point A in the following figure.
5-3
IAM
ACM
IV. Formula
None
5.2.4 Count of Answered Calls
I. Entity Name
ANS
II. Description
It is the count of messages indicating that call answers.
It is measured when the MSC receives the ANM from the peer office. See point A in the
following figure.
5-4
IAM
ACM
ANM
A
IV. Formula
None
5.2.5 Count of Callee Busy
I. Entity Name
CBSY
II. Description
It is the count of received messages indicating call loss because callees are busy.
It is measured when the MSC receives the release (REL) message from the peer office
and the cause value in the message indicates that the subscriber is busy. See point A in
5-5
IAM
REL
IV. Formula
None
5.2.6 Count of Release Before Offhook
I. Entity Name
ARGABN
II. Description
It is the count of messages indicating callers release before offhook of non-local callees
in outgoing calls.
After the MSC receives the ACM from the terminating office, the caller hears the ringing.
The entity is measured when the caller hooks on before the MSC receives the ACK
message sent by the terminating office. See point A in the following figure.
5-6
IAM
ACM
ACM
REL
IV. Formula
None
5.2.7 Count of No Reply
I. Entity Name
LTNANS
II. Description
Callees' phones ring and callees do not answer. It is the count of messages indicating
that the MSC releases calls because of timeout.
It is measured when the MSC releases a call due to ringing timeout. See point A in the
following figure.
5-7
IAM
ACM
REL
IV. Formula
None
5.2.8 Seizure Traffic
I. Entity Name
SERL
II. Description
It is measured from the time when the MSC receives the APMs with BCU ID from the
peer end to the time when the calls end.
As shown in the following figure, the measurement starts when the MSC receives the
APM with the BCU ID of the peer MG and stops when the call ends.
5-8
IAM
APM
REL
End point
of measurement
IV. Formula
None
5.2.9 Traffic of Connected Calls
I. Entity Name
CERL
II. Description
It is measured from the time when the MSC receives the ACMs from the peer end to the
time when calls end.
ACM from the peer office, and stops when the call ends.
5-9
IAM
ACM
REL
End point
of measurement
IV. Formula
None
5.2.10 Traffic of Answered Calls
I. Entity Name
RERL
II. Description
It is measured from the time when the MSC receives the ANMs from the peer end to the
ANM from the peer office, and stops when the call ends.
5-10
IAM
ANM
REL
End point
of measurement
IV. Formula
None
5.2.11 Call Completion Rate
I. Entity Name
CNTR
II. Description
Call completion rate = Count of connected calls/Count of seizures
It is measured on the BAM.
IV. Formula
CNTR = E1/E0
5.2.12 Call Answer Rate
I. Entity Name
ANSR
II. Description
Call answer rate = Count of answered calls/Count of seizures
5-11
IV. Formula
ANSR = E2/E0
5.3 Intra-Office Path Across MG

5.3.1 Overview of MS_INTERMGW_TRAF
Name Meaning
PATHBID Count of path seizure attempts
PATHSEIZ Count of path seizures
PATHSAME Count of same MG path seizures
PATHDIRECT Count of direct path seizures
PATHHOP1 Count of path seizures across one MG

PATHHOP2 Count of path seizures across two MGs
PATHHOP3 Count of path seizures across three MGs
PATHOF Count of path overflow
5.3.2 Count of Path Seizure Attempts
I. Entity Name
PATHBID
II. Description
It is the count of messages indicating seizure attempts of intra-office MG paths.
It is measured when the CDB receives the path selection message of an intra-office
MG.
IV. Formula
None
5.3.3 Count of Path Seizures
I. Entity Name
PATHSEIZ
5-12
II. Description
It is the count of messages indicating successful path seizures.
It is measured when the CDB successfully selects a path between intra-office MGs.
IV. Formula
None
5.3.4 Count of Same MG Path Seizures
I. Entity Name
PATHSAME
II. Description
It is the count of messages indicating seizures of a same MG path.
It is measured when the CDB successfully selects an intra-office MG path.
IV. Formula
None
5.3.5 Count of Direct Path Seizures
I. Entity Name
PATHDIRECT
II. Description
It is the count of messages indicating direct path seizures.
It is measured when the CDB successfully selects a path between two intra-office MGs.
IV. Formula
None
5.3.6 Count of Path Seizures Across One MG
I. Entity Name
PATHHOP1
5-13
II. Description
It is the count of messages indicating seizures of paths across one MG
It is measured when the CDB successfully selects a path between three intra-office
MGs.
IV. Formula
None
5.3.7 Count of Path Seizures Across Two MGs
I. Entity Name
PATHHOP2
II. Description
It is the count of messages indicating seizures of paths across two MGs.
It is measured when the CDB successfully selects a path between four intra-office
MGs.
IV. Formula
None
5.3.8 Count of Path Seizures Across Three MGs
I. Entity Name
PATHHOP3
II. Description
It is the count of messages indicating seizures of paths across three MGs.
It is measured when the CDB successfully selects a path between five intra-office MGs.
IV. Formula
None
5-14
5.3.9 Count of Path Overflow
I. Entity Name
PATHOF
II. Description
It is the count of messages indicating path overflow.
It is measured when the CDB fails to select the path between intra-office MGs.
IV. Formula
None
5.4 Office Direction Outgoing Traffic

5.4.1 Overview of MS_OFFICEDIR_OUT_TRAF
Name Meaning
BID Count of seizure attempts

OFL Count of overflow
DSEIZ Count of dual seizures
RETRY Count of trunk retry
POFCCG Count of peer end congestion

INSBICIR Count of installed bidirectional circuits
AVABICIR Count of available bidirectional circuits
BLKBICIR Count of blocked bidirectional circuits
OTKAVAR Availability of outgoing trunks
SEIZR Seizure rate
5-15
Name Meaning
BLKBIR Rate of blocked bidirectional circuits
BISERL Traffic of bidirectional trunk seizures


AST Average seizure duration
OFLFIRST Count of first sub-route overflow
OFLSECND Count of second sub-route overflow

OFLTHIRD Count of third sub-route overflow
OFLFOURTH Count of fourth sub-route overflow
OFLFIFTH Count of fifth sub-route overflow

OFLSIXTH Count of sixth sub-route overflow
OFLSEVENTH Count of seventh sub-route overflow
OFLEIGHTH Count of eighth sub-route overflow
OFLNINTH Count of ninth sub-route overflow
OFLTENTH Count of tenth sub-route overflow
OFLELEVENTH Count of eleventh sub-route overflow
OFLTWELFTH Count of twelfth sub-route overflow
Count of outgoing trunk receiving called subscriber line
CSLF
failure
NRPO Count of outgoing trunk calling peer office no reply
RCBA Count of caller release before ringing
ASTPL Average seizure traffic per line
5.4.2 Count of Seizure Attempts
I. Entity Name
BID
II. Description
It is the count of messages indicating assignments sent by the intra-office mobile

terminating subscriber over the office direction to the BSC/RNC side.
5-16
For the BSC/RNC side, it is measured when the callee sends the message RAB
ASSIGN REQ or BSSMAP ASSIGN REQ. For multiple connections, it is measured
multiple times. For the core network side, it is measured when the trunk receives the
SETUP message sent by the call control block (CCB).See point A in the following
figure.
MTP ISUP(inc) MSC ISUP(out) MTP
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
SEIZ
II. Description
It is the count of messages indicating assignments sent by the intra-office mobile

terminating subscriber over the office direction to the BSC/RNC side.
For the BSC/RNC side, it is measured when the callee sends the message RAB
ASSIGN REQ or BSSMAP ASSIGN REQ. For multiple connections, it is measured
multiple times. For the core network side, it is measured when the trunk receives the
SETUP message sent by the CCB. See point A in the following figure.
5-17
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of messages indicating call connections of intra-office mobile terminating

subscribers over the office direction on the BSC/RNC side. That is, it is the count of
messages indicating ringing of callees' phones.
For the BSC/RNC side, it is measured when the MSC receives the DTAP ALERTING
message sent by the mobile terminal (MT). For the core network side, it is measured
when the MSC receives the ACM from the peer office. See point B in the following
figure.
5-18
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating callee offhook in the intra-office mobile

terminating call over the office direction to the BSC/RNC side.
For the BSC/RNC side, it is measured when the MSC receives the DTAP CONNECT
message sent by the MT. For the core network side, it is measured when the MSC
receives the ACK message from the peer office. See point C in the following figure.
5-19
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
5.4.6 Count of Overflow
I. Entity Name
OFL
II. Description
It is the count of messages indicating outgoing call failure because all trunk circuits of
the office direction are busy. The trunk types include outgoing trunk and bidirectional
trunk.
It is measured when the MSC fails to select a circuit.
IV. Formula
None
5.4.7 Count of Dual Seizures
I. Entity Name
DSEIZ
5-20
II. Description
It is the count of messages indicating dual seizures on bidirectional circuits or Bearer

Independent Call Control Protocol (BICC) circuit identification codes (CICs).
It is measured when dual seizure occurs on a bidirectional circuit or a BICC CIC. There
is a gap between circuit selection and the time when the local office sends an Initial
Address Message (IAM). If the local office receives an IAM from the peer office in the
gap, dual seizure occurs.
The measurement starts when the local office receives an IAM on a same circuit from
the peer office after the ISUP trunk receives the SETUP message from the CCB. See
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
5.4.8 Count of Trunk Retry
I. Entity Name
RETRY
II. Description
It is the count of messages indicating call retry after the MSC fails to occupy outgoing
trunk circuits or BICC CICs.
5-21
It is measured during call retry after the MSC fails to occupy an outgoing trunk circuit or
a BICC CIC.
There are all types of reasons for trunk retry. For example, if there is a gap between
circuit selection and the time when the local office sends an IAM, the message sending
fails due to the status change of the circuit. Another case is as shown in the following
figure: After the local office sends an IAM, the peer office responds by sending a BLO
message.
The measurement starts when the ISUP receives the BLO from the peer office after
sending the IAM. See point A in the following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
BLO
IV. Formula
None
5.4.9 Count of Peer End Congestion
I. Entity Name
POFCCG
II. Description
It is the count of messages indicating failed call attempts due to congestion of the MSC
in the peer office or terminating office.
5-22
It is measured when the MSC receives the REL message from the peer office.
There are two cases as follows:
z The ISUP receives the REL message from the peer office before call connection.
z The ISUP receives the REL message from the peer office after call connection.
The measurement starts when the cause value in the REL message is one of the
following:
z CV_EXCHANGE_FACILITY_SURGE
z CV_NO_RESOURCE_AVAILABLE
z CV_NO_ROUTE_TO_TERMINAL
z CV_NO_ROUTE_AVAILABLE
z CV_NO_ROUTE_OR_CIRCUIT_APPLIED_AVAILABLE
z CV_REOUTE_IDENTEFIED_NOT_EXIST
z CV_INVALID_TRANSMIT_NETWORK_SELECTION
Case one:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
5-23
Case two:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
I. Entity Name
CBSY
II. Description
It is the count of messages indicating call loss because callees cancel the calls.
For the BSC/RNC side, it is measured when the MSC receives a message from the MT
with the cause value indicating that the subscriber is busy after receiving the DTAP
ALERTING message. For the core network side, it is measured when the MSC
receives the REL message from the peer office with the cause value indicating that the
subscriber is busy.
The measurement starts when the ISUP receives the REL message containing the
cause value CV-BUSY from the peer office. See point A in the following two figures.
5-24
Case one:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Case two:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
5-25
I. Entity Name
ARGABN
II. Description
in outgoing calls.
After the MSC receives the ACM/ALERTING message from the terminating office, the
caller hears the ringing. The entity is measured when the caller hooks on before the
MSC receives the ACK message sent by the terminating office. See point A in the
following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
IV. Formula
None
I. Entity Name
LTNANS
5-26
II. Description
It is the count of messages indicating timeout release of the MSC because non-local
callees do not answer the phones although the phones ring. For the BSC/RNC side, it
is the count of messages indicating call loss due to timeout release when callees on the
radio network controller (RNC) or base station controller (BSC) do not answer after
receiving the ALERTING.
It is measured when the MSC releases a call due to ringing timeout. For the BSC/RNC
side, the callee on the RNC or BSC does not answer after receiving the ALERTING.
The MSC performs status timeout statistics or mobile release. The cause values in the
messages indicate timer timeout statistics.
There are two cases as follows: Local office timeout release and peer office timeout
release.
1) Local office timeout release
As shown by point A in the following figure, the measurement starts when the ISUP
receives the Release message from the CCB and the cause value is one of the
following:
z CV_NO_ACKNOWLEGE
z CV_LONG_TIME_NO_ANSWER
z CV_GSM_CLD_USER_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
2) Peer office timeout release
5-27
receives the REL message from the peer office and the cause value is one of the
following.
z CV_RECOVERY_OF_TIME_OUT
z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
5.4.13 Count of Installed Bidirectional Circuits
I. Entity Name
INSBICIR
II. Description
It is the count of installed bidirectional trunk circuits in the office direction at the end of a
measurement period.
It is measured at the end of a measurement period.
IV. Formula
None
5-28
5.4.14 Count of Available Bidirectional Circuits
I. Entity Name
AVABICIR
II. Description
It is the average count (an integer) of available incoming trunk circuits including
bidirectional circuits in the office direction in the measurement period.
IV. Formula
None
5.4.15 Count of Blocked Bidirectional Circuits
I. Entity Name
BLKBICIR
II. Description
It is the count of blocked bidirectional trunk circuits in the office direction in the
measurement period.
IV. Formula
None
5.4.16 Availability of outgoing trunks
I. Entity Name
OTKAVAR
II. Description
Count of available circuits/Count of installed circuits (Circuits on all modules are

calculated on the BAM.)
It is a calculated value.
5-29
IV. Formula
OTKAVAR = E28/E27
5.4.17 Seizure Rate
I. Entity Name
SEIZR
II. Description
Count of seizures/Count of call attempts (Circuits on all modules are calculated on the
BAM.)
IV. Formula
SEIZR = E1/E0
I. Entity Name
CNTR
II. Description
Call completion rate = Count of completed calls/Count of call attempts
IV. Formula
CNTR = E2/E0
I. Entity Name
ANSR
II. Description
Call answer rate = Count of answered calls/Count of call attempts
5-30
IV. Formula
ANSR = E3/E0
5.4.20 Rate of Blocked Bidirectional Circuits
I. Entity Name
BLKBIR
II. Description
Count of blocked bidirectional circuits/Count of installed bidirectional circuits
IV. Formula
BLKBIR = E29/E27
5.4.21 Traffic of Bidirectional Trunk Seizures
I. Entity Name
BISERL
II. Description
It is measured from the time when outgoing calls occupy bidirectional trunks to the time
when calls are released.
IV. Formula
None
I. Entity Name
SERL
II. Description
For the BSC/RNC side, it is measured from the time when local terminating mobile
subscribers send assignment requests to the radio interface to the time when calls are
released.
5-31
For the BSC/RNC side, the measurement starts when the local office sends the
assignment request to the BSC/RNC, and stops when the call is released and the
status of the CM changes to idle in a measurement period. The final result is indicated
in Erlang.
IV. Formula
None
I. Entity Name
CERL
II. Description
For the BSC/RNC side, it is measured from ringing to call release for local terminating
mobile subscribers.
For the BSC/RNC side, the measurement starts when the MSC receives the Alerting
message, and stops when the call is released. The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
RERL
II. Description
For the BSC/RNC side, it is measured from callee offhook to call release for local
terminating mobile subscribers.
For the BSC/RNC side, the measurement starts when the MSC receives the
CONNECT message, and stops when the call is released. The final result is indicated
in Erlang.
IV. Formula
None
5-32
5.4.25 Average Seizure Duration
I. Entity Name
AST
II. Description
Average seizure duration (It is the intersection of the average duration from the time
when the call occupies the outgoing trunk to release of the outgoing trunk and the
measurement period) = Seizure traffic/Count of seizures; Calculation formula on the
BAM: Average seizure duration = Seizure traffic/Count of seizures; Calculation formula
on the host: Average seizure duration = Seizure traffic/100 × Measurement period
(second)/100
IV. Formula
AST = E44/(E0 × 100)
5.4.26 Count of First Sub-Route Overflow
I. Entity Name
OFLFIRST
II. Description
It is the count of messages indicating failure of circuit occupation of the first sub-route in
the office direction because all outgoing (bidirectional) trunks of the sub-route are busy.
It is measured when the MSC fails to choose outgoing trunks.
IV. Formula
None
5.4.27 Count of Second Sub-Route Overflow
I. Entity Name
OFLSECND
5-33
II. Description
the office direction because all outgoing (bidirectional) trunks of the second sub-route
are busy.
IV. Formula
None
5.4.28 Count of Third Sub-Route Overflow
I. Entity Name
OFLTHIRD
II. Description
the office direction because all outgoing (bidirectional) trunks of the third sub-route are
busy.
IV. Formula
None
5.4.29 Count of Fourth Sub-Route Overflow
I. Entity Name
OFLFOURTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the fourth sub-route are
busy.
IV. Formula
None
5-34
5.4.30 Count of Fifth Sub-Route Overflow
I. Entity Name
OFLFIFTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the fifth sub-route are
busy.
IV. Formula
None
5.4.31 Count of Sixth Sub-Route Overflow
I. Entity Name
OFLSIXTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the sixth sub-route are
busy.
IV. Formula
None
5.4.32 Count of Seventh Sub-Route Overflow
I. Entity Name
OFLSEVENTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the seventh sub-route
are busy.
5-35
IV. Formula
None
5.4.33 Count of Eighth Sub-Route Overflow
I. Entity Name
OFLEIGHTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the eighth sub-route
are busy.
IV. Formula
None
5.4.34 Count of Ninth Sub-Route Overflow
I. Entity Name
OFLNINTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the ninth sub-route are
busy.
IV. Formula
None
5-36
5.4.35 Count of Tenth Sub-Route Overflow
I. Entity Name
OFLTENTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the tenth sub-route are
busy.
IV. Formula
None
5.4.36 Count of Eleventh Sub-Route Overflow
I. Entity Name
OFLELEVENTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the eleventh sub-route
are busy.
IV. Formula
None
5.4.37 Count of Twelfth Sub-Route Overflow
I. Entity Name
OFLTWELFTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the twelfth sub-route
are busy.
5-37
IV. Formula
None
5.4.38 Count of Outgoing Trunk Receiving Called Subscriber Line Failure
I. Entity Name
CSLF
II. Description
It is the count of messages received by outgoing trunks indicating call loss because of
terminal failure.
It is measured when the outgoing trunk receives an REL message with the cause value
CV_TERMINAL_ERROR. See point A in the following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
IV. Formula
None
5-38
5.4.39 Count of Outgoing Trunk Calling Peer Office No Reply
I. Entity Name
NRPO
II. Description
It is the count of messages indicating that outgoing trunks wait for the ACMs until
timeout.
It is measured when the ISUP receives the Release message from the CCB. See point
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
IV. Formula
None
5.4.40 Count of Caller Release Before Ringing
I. Entity Name
RCBA
II. Description
It is the count of messages indicating caller onhook before ringing.
5-39
It is measured when the outgoing trunk waits for the ACM and the timer receives the
caller release ahead of time.
following:
z CV_NORMAL
z CV_NORMAL_CALL_CLEAR
z CV_RELEASE_BEFORE_ANSWER
z CV_RELEASE_BEFORE_RING
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
IV. Formula
None
5.4.41 Average Seizure Traffic Per Line
I. Entity Name
ASTPL
II. Description
Average seizure traffic per line = Seizure traffic/Count of installed bidirectional circuits
It is calculated on the BAM.
5-40
IV. Formula
ASTPL = E38/E25
5.5 Office Direction Incoming Traffic

5.5.1 Overview of MS_OFFICEDIR_INC_TRAF
Name Meaning
TEBID Count of terminating call attempts
TRNBID Count of transfer call attempts

TEANS Count of terminating answers
TRNANS Count of transfer answers
INTCGCL Count of call loss because of intra-office congestion


INSCIR Count of installed circuits
AVACIR Count of available circuits
BLKCIR Count of blocked circuits
ITKAVAR Availability of incoming trunk
BLKR Rate of blocked circuits
5-41
Name Meaning
I. Entity Name
SEIZ
II. Description
For the BSC/RNC side, it is the count of assignment messages sent to the radio
interface by callers who start calls from the RNC/BSC. For the core network side, it is
the count of messages indicating seizures of incoming (bidirectional) trunk circuits.
For the BSC/RNC side, it is measured when the mobile caller sends the assignment
request to the IU/A interface. For the core network side, it is measured when the MSC
receives the IAM/IAI message from the peer office. See point A in the following figure.
MTP ISUP(inc) CCB ISUP(out) MTP
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
5-42
5.5.3 Count of Terminating Call Attempts
I. Entity Name
TEBID
II. Description
It is the count of messages indicating that destinations of calls in the incoming office
direction are local subscribers.
It is measured when the caller is a subscriber in the local office. It is not measured for
the BSC/RNC side.
IV. Formula
None
5.5.4 Count of Transfer Call Attempts
I. Entity Name
TRNBID
II. Description
It is the count of messages indicating that calls are transferred by the local office in the
incoming office direction.
It is measured when the caller is not a subscriber in the local office. It is not measured
for the BSC/RNC side.
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of messages indicating callee ringing for incoming calls between offices.
That is, it is the count of messages indicating connection of calls started by subscribers
connected to the local RNC/BSC.
5-43
The entity is the count of Alerting messages sent by the peer sides to the callers. See
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating callee answers for incoming calls between offices.
That is, it is the count of answers of calls started by subscribers connected to the local
RNC/BSC.
It is the count of Connect messages received by the caller from the peer office. See
point C in the following figure.
5-44
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
5.5.7 Count of Terminating Answers
I. Entity Name
TEANS
II. Description
It is the count of messages indicating that callees in the local office answer the phones.
It is measured when the Answer signal sent by the peer office is received and the caller
is in the local office. It is not measured for the BSC/RNC side.
IV. Formula
None
5.5.8 Count of Transfer Answers
I. Entity Name
TRNANS
5-45
II. Description
It is the count of messages indicating that calls are transferred by the local office and
answered by the callees.
It is measured when the Answer signal sent by the peer office is received and the callee
is not in the local office. It is not measured for the BSC/RNC side.
IV. Formula
None
5.5.9 Count of Call Loss Because of Intra-Office Congestion
I. Entity Name
INTCGCL
II. Description
For incoming trunk calls, it is the count of messages indicating invalid incoming call
attempts due to congestion of the MSC in the terminating office.
It is measured when the MSC sends an REL message to the originating office. For the
BSC/RNC side, it is measured when the MSC sends a DISCONNECT message to the
UE. See point A in the following figure.
O_UE MSC Server
SETUP
A
DISCONNECT
IV. Formula
None
5-46
I. Entity Name
CBSY
II. Description
For inter-office incoming calls, it is the count of messages indicating call release
because callees are busy. For calls started by subscribers of the local RNC/BSC, it is
the count of messages indicating call loss because callees are busy.
It is measured when the Release message from the peer office or the BSC/RNC side is
received with the cause value indicating that the subscriber is busy.
following:
z CV_ST_BUSY
z CV_BUSY
z CV_SL_BUSY
z CV_GSM_CLD_USER_BUSY
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
REL A
IV. Formula
None
5-47
I. Entity Name
ARGABN
II. Description
Phones of callees ring but the callees do not answer. The entity is the count of
messages indicating that incoming trunks receive forward release signals.
For incoming inter-office calls, phones of callees ring but the callees do not answer. The
entity is measured when the MSC receives the REL message on the incoming trunk.
For calls started by subscribers of the local RNC/BSC, the mobile caller does not
answer after receiving the Alerting message. The entity is measured when the trunk
receives the Release message with the cause value indicating timeout. See point A in
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
IV. Formula
None
I. Entity Name
LTNANS
5-48
II. Description
It is the count of messages indicating timeout release of the MSC because of no

answers from callees. For calls started by subscribers connected to the local RNC/BSC,
it is the count of messages indicating call loss because of no reply from callees.
It is measured when the MSC releases a call due to ringing timeout. For the BSC/RNC
side, it is measured when the subscriber in the local RNC/BSC starts a call and
receives the Release message from the peer office with the cause value indicating no
answer from the callee. See point A in the following figure.
O_UE MSC Server
SETUP
DISCONNECT / RELEASE
/ RELEASE COMPLETE
IV. Formula
None
5.5.13 Count of Installed Circuits
I. Entity Name
INSCIR
II. Description
It is the count of installed incoming trunk circuits (including bidirectional trunks) in the
office direction at the end of a measurement period.
5-49
IV. Formula
None
5.5.14 Count of Available Circuits
I. Entity Name
AVACIR
II. Description
IV. Formula
None
5.5.15 Count of Blocked Circuits
I. Entity Name
BLKCIR
II. Description
It is the count of blocked incoming trunk circuits including bidirectional trunks in the
office direction in the measurement period.
IV. Formula
None
I. Entity Name
INSBICIR
II. Description
measurement period.
5-50
IV. Formula
None
I. Entity Name
AVABICIR
II. Description
IV. Formula
None
I. Entity Name
BLKBICIR
II. Description
measurement period.
IV. Formula
None
5.5.19 Availability of Incoming Trunk
I. Entity Name
ITKAVAR
5-51
II. Description
Count of available circuits/Count of installed circuits (All modules are calculated on the
BAM.)
IV. Formula
ITKAVAR = E15/E14
I. Entity Name
CNTR
II. Description
IV. Formula
CNTR = E3/E0
I. Entity Name
ANSR
II. Description
IV. Formula
ANSR = E4/E0
5-52
5.5.22 Rate of Blocked Circuits
I. Entity Name
BLKR
II. Description
Count of blocked circuits/Count of installed circuits
IV. Formula
BLKR = E16/E14
I. Entity Name
BLKBIR
II. Description
IV. Formula
BLKBIR = E19/E17
I. Entity Name
BISERL
II. Description
It is measured from the time when incoming calls occupy bidirectional trunks to the time
5-53
IV. Formula
None
I. Entity Name
SERL
II. Description
It is measured from the time when incoming calls in the office direction occupy incoming
trunks (including bidirectional trunks) to the time when calls are released normally or
abnormally.
For the BSC/RNC side, the measurement starts when the caller sends an assignment
message to the radio interface, as shown by point A in the following figure. The
measurement stops when the call is released in a measurement period, as shown by
point B in the following figure. The final result is indicated in Erlang.
O_BSS/RNC MSC Server

/RAB ASSIGNMENT REQUEST
DISCONNECT (call release)
IV. Formula
None
I. Entity Name
CERL
5-54
II. Description
It is measured from the time when incoming calls in the office direction are connected to
the time when calls are released.
For the BSC/RNC side, the measurement starts from the time when the caller receives
the Alerting message to the time when calls are released in a measurement period. The
final result is indicated in Erlang. See the interval between points A and B (active
release on the BSS/RNC side) in the following figure.
ALERT
IV. Formula
None
I. Entity Name
RERL
II. Description
It is measured from the time when incoming calls in the office direction are answered to
For the BSC/RNC side, the measurement starts from the time when the caller receives
the Connect message to the time when calls are released in a measurement period.
The final result is indicated in Erlang. See the interval between points A and B (active
release on the BSS/RNC side) in the following figure.
5-55
CONNECT
IV. Formula
None
I. Entity Name
AST
II. Description
IV. Formula
AST = E33/(E0 × 100)
I. Entity Name
ASTPL
II. Description
5-56
IV. Formula
ASTPL = E27/E15
5.6 Destination Code Traffic

5.6.1 Overview of MS_DESTCODE_TRAF
Name Meaning
DESTCAT Count of call attempt
DESTOTT Count of outgoing trunk seizure
DESTRRT Count of ringing
DESTATI Count of answered call
DESTCNR Call completion rate
DESTANR Call answer rate

DESTSEI Seizure traffic
DESTCON Traffic of connected call
DESTATR Traffic of answered call

DESTLCR Count of last-choice route overflow
DESTABR Count of caller release before ringing
DESTAAR Count of release before offhook
DESTRNA Count of callee no answer
DESTUDB Count of callee rejection
DESTUBT Count of callee busy
DESTIAT Count of invalid address
DESTANT Count of paging not replied
DESTPNR Count of callee absence

DESTSSR Count of restriction of subscriber service
DESTSPT Count of private tone
DESTPOC Count of peer end congestion
DESTIWK Count of connection failure
DESTTCNR Count of callee no reply
5-57
Name Meaning
DESTOTH Count of other failure reason
5.6.2 Count of Call Attempt
I. Entity Name
DESTCAT
II. Description
It is the count of messages indicating call attempts to destination codes.
It is measured when the destination code index is known to be set after the number
analysis.
IV. Formula
None
5.6.3 Count of Outgoing Trunk Seizure
I. Entity Name
DESTOTT
II. Description
It is the count of outgoing trunk seizures to destination codes.
It is measured when the destination code index is known to be set and the trunk is
successfully occupied after the number analysis.
IV. Formula
None
5.6.4 Count of Ringing
I. Entity Name
DESTRRT
II. Description
It is the count of ringings received by destination codes.
5-58
It is measured after receiving the ACM from the callee side when the destination code
index is set. See point A in the following figure.
MSC-A MSC-B
ACM
IV. Formula
None
5.6.5 Count of Answered Call
I. Entity Name
DESTATI
II. Description
It is the count of calls answered by destination codes.
It is measured after receiving the ANM or ANC from the callee side when the
destination code index is set. See point A in the following figure.
5-59
MSC-A MSC-B
ANM/ANC
IV. Formula
None
I. Entity Name
DESTCNR
II. Description
It is the call completion rate of destination codes.

It is calculated on the BAM. The formula is (count of answered calls + count of caller
release before offhook + count of callee no answer + count of callee rejection + count of
callee busy + count of invalid addresses + count of callee absent + count of restricted
subscriber service + count of special signal tone)/count of seizure attempts.
None
IV. Formula
(E3+E11+E12+E13+E14+E15+E16+E18+E19+E20)/E0
I. Entity Name
DESTANR
5-60
II. Description
It is the destination code answer rate.

It is calculated on the BAM. The formula is count of answered calls/count of seizure
attempts.
None
IV. Formula
E3/E0
I. Entity Name
DESTSEI
II. Description
It is the traffic seized by destination codes from the time when calls are made to the
time when the calls are released.
It is measured from the time when a call is made to the time when the call is released.
IV. Formula
None
5.6.9 Traffic of Connected Call
I. Entity Name
DESTCON
II. Description
It is the destination code completion traffic transmitted from the time when calls are
connected to the time when the calls are released.
It is measured from the time when a call is connected to the time when the call is
released.
IV. Formula
None
5-61
5.6.10 Traffic of Answered Call
I. Entity Name
DESTATR
II. Description
It is the transmitted traffic of destination codes from the time when calls are answered to
the time when the calls are released.
It is measured from the time when a call is answered to the time when the call is
released.
IV. Formula
None
5.6.11 Count of Last-Choice Route Overflow
I. Entity Name
DESTLCR
II. Description
It is the count of overflows of the last-choice route of destination codes.
It is measured when the call is released at the local office before the callee answers the
phone and the reason is that the MSC overruns the time or fails in selecting the
outgoing circuits.
IV. Formula
None
5.6.12 Count of Early Release Before Ringing
I. Entity Name
DESTABR
II. Description
It is the count of early releases by destination codes before the called phone rings.
5-62
It is measured when the MSC receives the Disconnect message from the caller side
before the called phone rings due to releases before ringins.
IV. Formula
None
5.6.13 Count of Early Release Before Offhook
I. Entity Name
DESTAAR
II. Description
It is the count of early releases by destination codes before callees answer the calls
after hearing the ringing.
It is measured when the MSC receives the Disconnect message from the caller side
before the callee answers the call after hearing the ringing and the reason is the early
release of ringing.
IV. Formula
None
5.6.14 Count of Callee No Answer
I. Entity Name
DESTRNA
II. Description
It is the count of calls not answered by callees of destination codes.
It is measured when the MSC does not receive the ANM from the callee side although
the called phone has rung for a long time and the reason is no answer to the ringing
call.
IV. Formula
None
5-63
5.6.15 Count of Callee Rejection
I. Entity Name
DESTUDB
II. Description
It is the count of calls rejected by callees of destination codes.
It is measured when the MSC receives the Disconnect message from the callee side
although the called phone has rung because the callee cancels the call.
IV. Formula
None
I. Entity Name
DESTUBT
II. Description
It is the count of calls not answered by callees of destination codes because the callees
are busy.
It is measure when the MSC receives the Disconnect message before the call is
answered because the callee is busy.
IV. Formula
None
5.6.17 Count of Invalid Address
I. Entity Name
DESTIAT
II. Description
It is the count of messages indicating invalid addresses of destination codes.
It is measured when the MSC receives the Disconnect message before the call is
answered due to invalid addresses.
5-64
IV. Formula
None
5.6.18 Count of Paging Not Replied
I. Entity Name
DESTPNR
II. Description
It is the count of pagings not replied by destination codes.
It is measured when the MSC receives the Disconnect message before the callee
answers the call because of no response to the pagings.
IV. Formula
None
5.6.19 Count of Callee Absence
I. Entity Name
DESTSAT
II. Description
It is the count of calls whose callees of destination codes are absent.
answered because the callee is absent.
IV. Formula
None
5.6.20 Count of Restriction of Subscriber Service
I. Entity Name
DESTSSR
II. Description
It is the count of service restrictions of destination codes.
5-65
answered because the subscriber has not subscribed to the services.
IV. Formula
None
5.6.21 Count of Private Tone
I. Entity Name
DESTSPT
II. Description
It is the count of private tones from destination codes.
It is measured when the MSC receives the ACM with the cause value as
CV_SEND_PRIVATE_TONE (132) from the callee side.
MSC-A MSC-B
ACM
IV. Formula
None
I. Entity Name
DESTPOC
5-66
II. Description
It is the count of congestions at the peer office.
It is measured when the MSC receives the Disconnect message because the peer
office is congested.
IV. Formula
None
5.6.23 Count of Connection Failure
I. Entity Name
DESTIWK
II. Description
It is the count of connection failures.
answered because of the connection failure.
IV. Formula
None
5.6.24 Count of Callee No Reply
I. Entity Name
DESTTCNR
II. Description
It is the count of calls not replied by callees of destination codes.
answered because of no reply to the call.
IV. Formula
None
5-67
5.6.25 Count of Other Failure Reason
I. Entity Name
DESTOTH
II. Description
It is the count of failures due to other reasons of destination codes except all the above
ones.
It is measured when a failure happens due to other reasons except the above one.
IV. Formula
E0-(E3+E9+E11+E12+E13+E14+E15+E16+E17+E18+E19+E20+E21+E22+E23)
5.7 Destination Traffic Distribution

5.7.1 Overview of MS_OFFICE_DEST_DISTRIB_TRAF
Name Meaning



ALTR Traffic of connected calls
I. Entity Name
BID
5-68
II. Description
It is the count of messages indicating that the software tries to occupy the outgoing
trunks in the office direction and the destinations are specified ones.
It is measured when the MSC chooses the outgoing trunk. The attempt is counted
whether the MSC successfully chooses an outgoing trunk or not. The measurement
point is as shown by point A in the following figure.
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
I. Entity Name
SEIZ
II. Description
It is the count of messages indicating that trunks are occupied.
It is measured when the trunk is occupied. See point A in the following figure.
5-69
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of messages indicating that destinations in the office direction are the
specified ones in connected calls.
It is measured when the MSC receives the ACM from the peer office. See point B in the
following figure.
5-70
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating that the destinations in the office direction are the
specified ones in answered calls.
It is measured when the MSC receives the ANM from the peer office. See point C in the
following figure.
5-71
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
I. Entity Name
SERL
II. Description
It is measured from the time when call destinations are identified as the specified ones
to the time when calls are released.
It is measured when the MSC chooses the outgoing trunk. Start point: See point A in the
following figure. End point: See point B in the following figure.
5-72
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
I. Entity Name
RERL
II. Description
It is measured from call answer to call release. Destinations of calls in the office
direction are specified ones.
It is measured when the MSC receives the ANM from the peer office. Start point: See
point C in the following figure. End point: See point D in the following figure.
5-73
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
I. Entity Name
AVACIR
II. Description
It is the count of available circuits in the outgoing traffic measurement of the office
direction or trunk group.
It is calculated by the ISUP.
IV. Formula
None
I. Entity Name
INSCIR
II. Description
It is the count of installed circuits in the outgoing traffic measurement of the office
direction or trunk group.
5-74
It is calculated by the ISUP.
IV. Formula
None
I. Entity Name
ALTR
II. Description
It is measured from the time when call destinations are identified as the specified ones
and calls are connected to the time when calls are released.
It is measured when the MSC receives the ACM from the peer office. Start point: See
point B in the following figure. End point: See point D in the following figure.
A
IAM
ACM
B
ANM
REL
D
RLC
IV. Formula
None
5-75
5.8 Supplementary Service Traffic

5.8.1 Overview of MS_SS_INVOKE
Name Meaning
SSINVOKE Count of Supplementary Service Invoke
5.8.2 Count of Supplementary Service Invoke
I. Entity Name
SSINVOKE
II. Description
It is the count of messages indicating that supplementary services are invoked.
It is measured when the following types of supplementary services are activated:

z Forwarding type
z Identifying type
z Completion type
z Call restriction type
IV. Formula
None
5.9 Trunk Office Direction Outgoing Traffic

5.9.1 Overview of MS_TK_OFC_OUT_TRAF
Name Meaning
CNT Count of received ringing messages

5-76
Name Meaning
DSEIZM Count of main control circuit contention
DSEIZS Count of non–main control circuit contention



BRGABN Count of caller release before offhook

LFAIL Count of local office failure
LTNANS Count of callee no answer
CDBSY Count of callee rejection
IAT Count of invalid addresses
ASUB Count of callee absent
SLMT Count of Restricted Subscriber Service
SSTONE Count of special signal tone
CONG Count of congestion

OPNR Count of paging no reply
INTF Count of connection failure
CLDINSP Count of callee no reply
OMGUAV Count of UMG failure
OCIRBUSY Count of all circuits busy
OTHF Count of other failure reasons
5-77
Name Meaning


I. Entity Name
BID
II. Description
It is the count of messages indicating that the software tries to occupy outgoing circuits
(including bidirectional circuits) in the office direction.
It is measured when the local office tries to start an outgoing call.
IV. Formula
None
I. Entity Name
SEIZ
II. Description
It is the count of messages indicating that incoming (bidirectional) trunk circuits are
occupied.
It is measured when an outgoing call is started and an outgoing circuit is occupied. As

shown by point C in the following figure, the measurement starts when the ISUP
receives the ANM from the peer office.
5-78
IAM
Setup
Setup
Setup Ack
A
Setup Ack
IAM
Alerting ACM
Alerting
ACM
B
ANM
Connect
Connect
Connect Ack
ANM
Connect Ack
C
IV. Formula
None
5.9.4 Count of Received Ringing Messages
I. Entity Name
CNT
II. Description
It is the count of messages indicating phones of callees ring.
It is measured when an outgoing call is started and the ringing message is received. As
shown by point B in the following figure, the measurement starts when the ISUP
receives the ACM from the peer office.
5-79
IAM
Setup
Setup
Setup Ack
A
Setup Ack
IAM
Alerting ACM
Alerting
ACM
B
ANM
Connect
Connect
Connect Ack
ANM
Connect Ack
C
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating that callees hook off to answer the phones.
It is measured when an outgoing call is started and the Connect message is received.
As shown by point C in the following figure, the measurement starts when the ISUP
receives the ANM from the peer office.
5-80
IAM
Setup
Setup
Setup Ack
A
Setup Ack
IAM
Alerting ACM
Alerting
ACM
B
ANM
Connect
Connect
Connect Ack
ANM
Connect Ack
C
IV. Formula
None
I. Entity Name
CNTR
II. Description
Count of connected calls/Count of seizures (All modules are calculated on the BAM.)
It is measured on the BAM at the end of a measurement period.
IV. Formula
(E3+E22+E23+E25+E26+E27+E28+E29+E30+E31)/(E1+E6+E9)
I. Entity Name
ANSR
II. Description
Count of answered calls/Count of seizures (All modules are calculated on the BAM.)
5-81
IV. Formula
E3/(E1+E6+E9)
I. Entity Name
OFL
II. Description
It is the count of messages indicating failure of circuit occupation in the office direction
because all outgoing (bidirectional) trunks in the office direction are busy.
It is measured when circuit selection fails in an outgoing call.
IV. Formula
None
5.9.9 Count of Main Control Circuit Contention
I. Entity Name
DSEIZM
II. Description
It is the count of messages indicating contention of main control bidirectional circuits.
It is measured when contention of main control circuits configured in the local office
occurs in an outgoing call.
There is a gap between circuit selection and the time when the local office sends an
IAM. If the local office receives an IAM from the peer office in the gap, circuit contention
occurs. The IAM from the peer office is discarded as a result of circuit contention.
The measurement starts when the ISUP receives the IAM from the peer office. See
5-82
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
5.9.10 Count of Non–Main Control Circuit Contention
I. Entity Name
DSEIZS
II. Description
It is the count of messages indicating contention of non–main control bidirectional

circuits.
It is measured when contention of non–main control circuits configured in the local

office occurs in an outgoing call.
occurs. As a result of circuit contention, the Setup message from the local office is
discarded and trunk circuits are reselected.
5-83
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
I. Entity Name
RETRY
II. Description
trunk circuits.
It is measured when circuit contention occurs in an outgoing call and the route is
reselected.
1) Count of trunk retry (case 1)
occurs. Trunk retry occurs because of contention of non–main control circuits. As a
result of circuit contention, the Setup message from the local office is discarded and
trunk circuits are reselected.
5-84
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
2) Count of trunk retry (case 2)

The reason of this trunk retry is also circuit contention. In this case, the peer office
sends an IAM to the local office. The local office chooses the same circuit in an
outgoing call because of the gap. Therefore, circuit contention occurs. As a result, the
Setup message from the local office is discarded and trunk circuits are reselected.
The measurement starts when the ISUP receives the Setup message from the CCB.
5-85
IAM
Setup IAM
Setup
Setup Ack
A
Setup Ack
IV. Formula
None
I. Entity Name
SERL
II. Description
It is measured from the time when incoming (bidirectional) trunks are occupied to the
time when trunks are released.
It is measured from circuit occupation to circuit release.
IV. Formula
None
I. Entity Name
CERL
5-86
II. Description
For calls set up in the whole network, it is measured from ringing of callees' phones to
call release.
It is measured from call connection (when the Connect message is received) to call
release.
IV. Formula
None
I. Entity Name
RERL
II. Description
It is measured from the time when calls borne over the trunk enter answer status to the
It is measured from call answer (when the ACM is received) to call release.
IV. Formula
None
I. Entity Name
INSCIR
II. Description
It is the average count of installed incoming trunk circuits (including bidirectional circuits)
in the office direction.
The host measures the count of installed circuits every 30 seconds, and calculates the
average value at the end of the period.
IV. Formula
None
5-87
I. Entity Name
AVACIR
II. Description
The host measures the count of available circuits every 30 seconds, and calculates the
IV. Formula
None
I. Entity Name
BLKCIR
II. Description
The host measures the count of blocked circuits every 30 seconds, and calculates the
IV. Formula
None
5.9.18 Count of Caller Release Before Offhook
I. Entity Name
BRGABN
II. Description
It is the count of messages indicating that callers release incoming trunk calls before
phones of callees ring.
5-88
After the caller starts a call, the entity is measured when the Release message from the
caller side is received before the phone of the callee rings. See point A in the following
figure.
IAM
Setup
Setup
Setup Ack
REL Release Release
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of messages indicating that callers release calls when phones of callees
ring.
After the caller starts a call and the phone of callee rings, the entity is measured when
the Release message from the caller side is received before the callee answers. See
5-89
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
IV. Formula
None
5.9.20 Count of Local Office Failure
I. Entity Name
LFAIL
II. Description
It is the count of messages indicating local office failure.
It is measured when the local office fails to bear services.

There are the following cases:
z Messages sent are lost or wrong messages are received because the traffic of the
local office is heavy.
z External interface such as H.248 interface returns failure messages.
z Some abnormal operations of the local office cause failure. For example, board
switchover results in call release.
The measurement starts when the ISUP sends the Release message. See point A in
5-90
IAM
Setup
Setup
Setup Ack
Setup Ack
Release
Release
REL
A
IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of messages indicating that callees do not answer and the MSC releases
the calls due to timeout.
After the call is connected, the entity is measured when the MSC releases the call
because the callee does not answer.
1) Callee no answer (case 1)
For caller side timeout, the cause value in the Release message is one of the following:
z CV_NO_ACKNOWLEGE
The measurement starts when the ISUP receives the Release message from the CCB.
5-91
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL

For callee side timeout, the cause value in the Release message is one of the following:
z CV_NO_ACKNOWLEGE
The measurement starts when the ISUP receives the REL message from the peer
office. See point A in the following figure.
5-92
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
IV. Formula
None
I. Entity Name
CDBSY
II. Description
It is the count of messages indicating that calls fail because destination callees cancel
the calls.
It is measured when the callee cancels the call after the call is connected.
IV. Formula
None
I. Entity Name
CBSY
5-93
II. Description
It is the count of messages indicating that calls fail because destination callees are
busy.
After the caller starts a call, the entity is measured when the caller side receives the
Release message because the callee is busy.
IV. Formula
None
5.9.24 Count of Invalid Addresses
I. Entity Name
IAT
II. Description
It is the count of messages indicating call failure because invalid callee numbers are
dialed.
callee side is received because the callee number is invalid.
IV. Formula
None
5.9.25 Count of Callee Absent
I. Entity Name
ASUB
II. Description
It is the count of messages indicating that callees are absent.
callee side is received because the callee is absent.
IV. Formula
None
5-94
5.9.26 Count of Restricted Subscriber Service
I. Entity Name
SLMT
II. Description
It is the count of messages indicating subscriber services are restricted.
callee side is received because the service is restricted.
IV. Formula
None
5.9.27 Count of Special Signal Tone
I. Entity Name
SSTONE
II. Description
It is the count of messages indicating sending of the special signal tones.
After the caller starts a call, the entity is measured when the MSC receives the Release
message from the callee side because the cause value returned indicates sending of
the special signal tone.
IV. Formula
None
5.9.28 Count of Congestion
I. Entity Name
CONG
II. Description
It is the count of messages indicating congestion.
callee side is received because of circuit congestion.
5-95
IV. Formula
None
5.9.29 Count of Paging No Reply
I. Entity Name
OPNR
II. Description
It is the count of messages indicating that callees respond with paging no reply in
outgoing trunk calls.
callee side is received because the callee responds with paging no reply.
IV. Formula
None
I. Entity Name
INTF
II. Description
It is the count of messages indicating connection failure.
After the caller starts a call, the entity is measured when a message with cause value
related to connection failure is received.
IV. Formula
None
I. Entity Name
CLDINSP
II. Description
It is the count of messages indicating no reply from callees.
5-96
After the caller starts a call, the IAM is sent and there is no response from the callee.
The entity is measured when the Release message is received because of timeout.
Callee no response (case 1)
z CV_NO_ACKNOWLEGE
The measurement starts when the ISUP receives the Release message from the CCB.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
Callee no response (case 2)

z CV_NO_ACKNOWLEGE
The entity is measured when the ISUP receives the REL message from the peer office.
5-97
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
IV. Formula
None
5.9.32 Count of UMG Failure
I. Entity Name
OMGUAV
II. Description
It is the count of messages indicating that UMGs are faulty.
After the caller starts a call, the UMG in the local office becomes faulty. The entity is
measured when the Release message is received.
IV. Formula
None
5.9.33 Count of All Circuits Busy
I. Entity Name
OCIRBUSY
5-98
II. Description
It is the count of messages indicating that all circuits are busy.
After the caller starts a call, all circuits in the local office are busy. The entity is
IV. Formula
None
5.9.34 Count of Other Failure Reasons
I. Entity Name
OTHF
II. Description
It is the count of messages indicating other failure reasons.
IV. Formula
E1-E3-E22-E23-E24-E25-E26-E27-E28-E29-E30-E31-E32-E33-E34-E35-E36-E37
I. Entity Name
OFLFIRST
II. Description
It is the count of messages indicating that calls fail to occupy circuits of the first
sub-route in the office direction because all outgoing (bidirectional) trunks of the
sub-route are busy.
After the caller starts a call, the entity is measured when the MSC fails to choose the
first sub-route.
IV. Formula
None
5-99
I. Entity Name
OFLSECND
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the second
sub-route are busy.
second sub-route.
IV. Formula
None
I. Entity Name
OFLTHIRD
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the third
sub-route are busy.
third sub-route.
IV. Formula
None
I. Entity Name
OFLFOURTH
5-100
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the fourth
sub-route are busy.
fourth sub-route.
IV. Formula
None
I. Entity Name
OFLFIFTH
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the fifth
sub-route are busy.
fifth sub-route.
IV. Formula
None
I. Entity Name
OFLSIXTH
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the sixth
sub-route are busy.
sixth sub-route.
5-101
IV. Formula
None
I. Entity Name
OFLSEVENTH
II. Description
seventh sub-route are busy.
seventh sub-route.
IV. Formula
None
I. Entity Name
OFLEIGHTH
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the eighth
sub-route are busy.
eighth sub-route.
IV. Formula
None
I. Entity Name
OFLNINTH
5-102
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the ninth
sub-route are busy.
ninth sub-route.
IV. Formula
None
I. Entity Name
OFLTENTH
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the tenth
sub-route are busy.
tenth sub-route.
IV. Formula
None
I. Entity Name
OFLELEVENTH
II. Description
eleventh sub-route are busy.
eleventh sub-route.
5-103
IV. Formula
None
I. Entity Name
OFLTWELFTH
II. Description
sub-route in the office direction because all outgoing (bidirectional) trunks of the twelfth
sub-route are busy.
twelfth sub-route.
IV. Formula
None
5.10 Trunk Office Direction Incoming Traffic

5.10.1 Overview of MS_TK_OFC_INC_TRAF
Name Meaning
CNT Count of received ringing messages

BRGABN Count of caller release before offhook
5-104
Name Meaning
LFAIL Count of local office failure
LTNANS Count of callee no answer

CDBSY Count of callee rejection
IAT Count of invalid addresses

ASUB Count of callee absent
SLMT Count of Restricted Subscriber Service
SSTONE Count of special signal tone

OPNR Count of paging no reply
INTF Count of connection failure

CLDONSP Count of callee no reply
IMGUAV Count of UMG failure
ICIRBUSY Count of all circuits busy
OTHF Count of other failure reasons
I. Entity Name
SEIZ
II. Description
occupied.
It is measured after the IAM is received and a circuit is occupied in an incoming call.
The measurement starts when the ISUP receives the Connect message from the CCB.
See point C in the following figure.
5-105
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
5.10.3 Count of Received Ringing Messages
I. Entity Name
CNT
II. Description
It is the count of messages indicating that phones of callees ring.
It is measured when the ringing message is received in an incoming call.

5-106
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating that callees hook off to answer the phones.
It is measured when the Connect message is received in an incoming call.

5-107
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
CNTR
II. Description
Count of connected calls/Count of seizures (Circuits on all modules are calculated on

the BAM.)
IV. Formula
CNTR = (E2+E17+E18+E20+E21+E22+E23+E24+E25+E26)/E0
I. Entity Name
ANSR
5-108
II. Description
Count of answered calls/Count of seizures (Circuits on all modules are calculated on

the BAM.)
IV. Formula
ANSR = E2/E0
I. Entity Name
SERL
II. Description
It is measured from the time when incoming (bidirectional) trunks are occupied to the
time when trunks are released.
It is measured from circuit occupation to circuit release.
IV. Formula
None
I. Entity Name
CERL
II. Description
For calls set up in the whole network, the entity is measured from ringing of callees'
phones to call release.
It is measured from call connection (when the ANM is received) to call release.
IV. Formula
None
5-109
I. Entity Name
RERL
II. Description
It is measured from the time when calls borne over the trunk enter answer status to the
IV. Formula
None
I. Entity Name
INSCIR
II. Description
The host measures the count of installed circuits every 30 seconds, and calculates the
IV. Formula
None
I. Entity Name
AVACIR
II. Description
The host measures the count of available circuits every 30 seconds, and calculates the
5-110
IV. Formula
None
I. Entity Name
BLKCIR
II. Description
The host measures the count of blocked circuits every 30 seconds, and calculates the
IV. Formula
None
5.10.13 Count of Caller Release Before Offhook
I. Entity Name
BRGABN
II. Description
It is the count of messages indicating that callers release incoming trunk calls before
phones of callees ring.
After the callee receives a call, the entity is measured when the REL message from the
caller side is received before the phone of the callee rings.
5-111
IAM
Setup
Setup
Setup Ack
REL
A
Release
Release
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of messages indicating that callers release calls when phones of callees
ring.
After the callee receives a call, the phone of the callee rings. The entity is measured
when the REL message from the caller side is received before the callee answers the
phone.
5-112
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
A
Release Release REL
IV. Formula
None
5.10.15 Count of Local Office Failure
I. Entity Name
LFAIL
II. Description
It is the count of messages indicating local office failure.
It is measured when the local office fails to bear services.

There are the following cases:
z Messages sent are lost or wrong messages are received because the traffic of the
local office is heavy.
z External interfaces such as H.248 interfaces return failure messages.
z Some abnormal operations of the local office cause failure. For example, board
switchover results in call release.
The measurement starts when the ISUP receives the Release message. See point A in
5-113
IAM
Setup
Setup
Setup Ack
Setup Ack
Release
Release
A
REL
IV. Formula
None
I. Entity Name
LTNANS
II. Description
After the call is connected, the entity is measured when the MSC releases the call
because the callee does not answer.
For caller side timeout, the cause value in the REL message is one of the following:
z CV_NO_ACKNOWLEGE
5-114
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
A
Release Release
REL

z CV_NO_ACKNOWLEGE
5-115
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
Release
Release
REL A
IV. Formula
None
I. Entity Name
CDBSY
II. Description
It is the count of messages indicating that calls fail because destination callees cancel
the calls.
It is measured when the callee cancels the call after the call is connected.
IV. Formula
None
I. Entity Name
CBSY
5-116
II. Description
busy.
After the callee receives a call, the entity is measured when the caller side receives the
Release message because the callee is busy.
IV. Formula
None
I. Entity Name
IAT
II. Description
It is the count of messages indicating call failure because of invalid callee numbers
dialed.
After the callee receives a call, the entity is measured when the Release message from
the callee side is received because the callee number is invalid.
IV. Formula
None
I. Entity Name
ASUB
II. Description
It is the count of messages indicating that callees are absent.
the callee side is received because the callee is absent.
IV. Formula
None
5-117
5.10.21 Count of Restricted Subscriber Service
I. Entity Name
SLMT
II. Description
It is the count of messages indicating that subscriber services are restricted.
the callee side is received because the callee is restricted to use the service.
IV. Formula
None
5.10.22 Count of Special Signal Tone
I. Entity Name
SSTONE
II. Description
It is the count of messages indicating special signal tones.
the callee side is received because the callee sends a message with the cause value
indicating sending of the special signal tone.
IV. Formula
None
I. Entity Name
CONG
II. Description
It is the count of messages indicating congestion.
the callee side is received because the circuits on the callee side are congested.
5-118
IV. Formula
None
I. Entity Name
OPNR
II. Description
It is the count of messages indicating that callees respond with paging no reply in
outgoing trunk calls.
the callee side is received because the callee side responds with paging no reply.
IV. Formula
None
I. Entity Name
INTF
II. Description
It is the count of messages indicating connection failure.
After the callee receives a call, the entity is measured when a message with cause
value related to connection failure is received.
IV. Formula
None
I. Entity Name
CLDONSP
II. Description
It is the count of messages indicating no reply from callee sides.
5-119
After the callee receives a call, the IAM is sent and there is no response from the callee.
The entity is measured when the Release message is received because of timeout.
1) Callee no response (case 1)
For caller side timeout, the cause value in the REL message is one of the following:
z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
A
Release Release
REL
2) Callee no response (case 2)

z CV_NO_ACKNOWLEGE
5-120
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A
IV. Formula
None
5.10.27 Count of UMG Failure
I. Entity Name
IMGUAV
II. Description
It is the count of messages indicating that UMGs are faulty.
When the callee receives a call, the UMG in the local office is faulty. The entity is
IV. Formula
None
5.10.28 Count of All Circuits Busy
I. Entity Name
ICIRBUSY
5-121
II. Description
It is the count of messages indicating that all circuits are busy.
When the callee receives a call, all circuits in the local office are busy. The entity is
IV. Formula
None
5.10.29 Count of Other Failure Reasons
I. Entity Name
OTHF
II. Description
It is the count of messages indicating other failure reasons.
IV. Formula
E0-E2-E17-E18-E19-E20-E21-E22-E23-E24-E25-E26-E27-E28-E29-E30-E31-E32
5.11 Trunk Group Outgoing Traffic

5.11.1 Overview of MS_TKGRP_OUT_TRAF
Name Meaning

DNMA Count of trunk circuit type mismatch
CNMA Count of bearer capability and mode mismatch
5-122
Name Meaning
CGT Congestion duration

CTB Count of Callee toll busy
CLB Count of Callee local busy



SEIZR Seizure rate

Count of outgoing trunk receiving called subscriber line
CSLF
failure
NRPO Count of outgoing trunk calling peer office no reply

RCBA Count of caller release before ringing
5-123
I. Entity Name
BID
II. Description
It is the count of messages indicating that outgoing calls to an observed office direction
try to occupy trunk circuits to the office direction.
It is measured when the MSC chooses an outgoing circuit.

The measurement starts when the ISUP receives the Setup message. See point A in
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
SEIZ
5-124
II. Description
It is the count of messages indicating that outgoing calls to an observed office direction
successfully occupy trunk circuits to the office direction.
It is measured when the IAM is sent (ITU-T Rec.Q.722).

IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of callee ringing after calls are set up in the whole network.
It is measured when the ACM (ITU-T Rec.Q.722) from the peer office is received.
The measurement starts when the ISUP receives the ACM message. See point B in the
following figure.
5-125
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating that outgoing calls to the office direction are
answered.
It is measured when the Answer Signal (ITU-T Rec.Q.722) is sent.

The measurement starts when the ISUP receives the ANM. See point C in the following
figure.
5-126
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
I. Entity Name
OFL
II. Description
trunk.
It is measured when the MSC fails to choose a circuit.
IV. Formula
None
5.11.7 Count of Trunk Circuit Type Mismatch
I. Entity Name
DNMA
5-127
II. Description
It is the count of messages indicating that the type of trunk circuits is wrong.
It is measured when a wrong type of trunk circuit is found.
IV. Formula
None
5.11.8 Count of Bearer Capability and Mode Mismatch
I. Entity Name
CNMA
II. Description
It is the count of messages indicating call failure because there is a mismatch between
the bearer capability and the bear mode.
It is measured when the call fails because there is a mismatch between the bearer
capability and the bear mode.
IV. Formula
None
I. Entity Name
DSEIZ
II. Description
It is the count of messages indicating dual seizures on bidirectional circuits.
It is measured when dual seizure occurs on bidirectional circuits.

There is a gap between the circuit selection and the time when the local office sends an
IAM. If the local office receives an IAM from the peer office during the gap, dual seizure
occurs.
The measurement starts when the ISUP receives the IAM message. See point A in the
following figure.
5-128
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
I. Entity Name
RETRY
II. Description
trunk circuits.
It is measured during call retry after the MSC fails to occupy an outgoing trunk circuit.
There are all types of reasons for call retry. For example, if there is a gap between the
circuit selections to the time when the local office sends an IAM, the message sending
fails due to the change of circuit status.
The following figure shows a case of call retry. After the local office sends the IAM, the
peer office responds with the BLO message, which causes call retry.
The measurement starts when the ISUP receives the BLO message. See point A in the
following figure.
5-129
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
BLO
IV. Formula
None
I. Entity Name
POFCCG
II. Description
It is the count of messages indicating failed call attempts due to congestion of switches
It is measured when the MSC receives the TUP SEC and ISUP REL (switch congestion)
messages from the peer office.
The cause value in the REL message is one of the following:
1) Count of peer end congestion (case 1)
5-130
The measurement starts when the ISUP receives the REL message. See point A in the
following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
5-131
IV. Formula
None
5.11.12 Congestion Duration
I. Entity Name
CGT
II. Description
It is the duration of congestion. When all resources are occupied, congestion starts.
When one device becomes idle, congestion ends.
IV. Formula
None
I. Entity Name
CBSY
II. Description
busy.
It is measured when the ISUP receives the REL message with the cause value
CV_BUSY (17 + 128) from the peer office. It is also measured by TUP. When queried,
the ISUP/TUP shows the sum of three parameters: callee busy, callee toll busy, and
callee local busy.
The cause value in the REL message is CV_BUSY.
1) Callee busy (case 1)
following figure.
5-132
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
5-133
5.11.14 Count of Callee Toll Busy
I. Entity Name
CTB
II. Description
It is the count of messages indicating that callees are busy because they are making
toll calls.
It is measured when the TUP outgoing trunk receives the subscriber toll busy signal
(STB).
IV. Formula
None
5.11.15 Count of Callee Local Busy
I. Entity Name
CLB
II. Description
local calls.
It is measured when the TUP outgoing trunk receives the subscriber local busy signal
(SLB).
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of messages indicating callers release before offhook of non-local

fixed-line callees in outgoing calls.
5-134
message sent by the terminating office.
z CV_NORMAL
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of messages indicating that the MSC releases calls because the waiting
for offhook of non-local fixed-line callees times out.
5-135
It is measured when the MSC releases a call due to ringing timeout.

1) Count of no reply (case 1)
z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL

z CV_NO_ACKNOWLEGE
following figure.
5-136
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
I. Entity Name
INSCIR
II. Description
It is the count of installed outgoing trunk circuits (including bidirectional trunks) in the
IV. Formula
None
I. Entity Name
AVACIR
5-137
II. Description
It is the average count (an integer) of available outgoing trunk circuits including
IV. Formula
None
I. Entity Name
BLKCIR
II. Description
It is the count of blocked outgoing trunk circuits including bidirectional trunks in the
IV. Formula
None
I. Entity Name
INSBICIR
II. Description
measurement period.
IV. Formula
None
5-138
5.11.22 Count of available bidirectional circuits
I. Entity Name
AVABICIR
II. Description
IV. Formula
None
5.11.23 Count of blocked bidirectional circuits
I. Entity Name
BLKBICIR
II. Description
measurement period.
IV. Formula
None
5.11.24 Availability of outgoing trunks
I. Entity Name
OTKAVAR
II. Description
BAM.)
5-139
IV. Formula
OTKAVAR = E25/E24
5.11.25 Seizure Rate
I. Entity Name
SEIZR
II. Description
Count of seizures/Count of call attempts (All modules are calculated on the BAM.)
IV. Formula
SEIZR = E1/E0
I. Entity Name
CNTR
II. Description
IV. Formula
CNTR = E2/E0
I. Entity Name
ANSR
II. Description
5-140
IV. Formula
ANSR = E3/E0
I. Entity Name
BLKR
II. Description
IV. Formula
BLKR = E26/E24
I. Entity Name
BLKBIR
II. Description
IV. Formula
BLKBIR = E29/E27
I. Entity Name
BISERL
II. Description
5-141
IV. Formula
None
I. Entity Name
SERL
II. Description
It is measured from the time when outgoing calls in the office direction occupy outgoing
abnormally.
It is measured from the time when the MSC sends the IAM to the time when it sends or
receives the UBM, Clear Forward, Clear Backward, or REL message in a measurement
period. The final result is indicated in Erlang (ITU-T Rec. Q.722).
IV. Formula
None
I. Entity Name
CERL
II. Description
It is measured from the time when outgoing calls in an office direction are connected to
It is measured from the time when the MSC receives the ACM to the time when it sends
or receives the Clear Forward, Clear Backward, or REL message in a measurement
IV. Formula
None
I. Entity Name
RERL
5-142
II. Description
It is measured from the time when incoming calls in an office direction are answered to
It is measured from the time when the MSC receives the Answer Signal to the time
when it sends the Clear Forward, Clear Backward, or REL message in a measurement
IV. Formula
None
I. Entity Name
AST
II. Description
It is the average seizure duration of outgoing calls in an office direction. It is calculated

by using seizure traffic of outgoing calls, seizure count of outgoing calls, and sampling
period.
IV. Formula
E44/E0
5.11.35 Count of Outgoing Trunk Receiving Called Subscriber Line Failure
I. Entity Name
CSLF
II. Description
It is the count of messages received by outgoing trunks indicating call loss because of
terminal failure.
It is measured when the outgoing trunk receives an REL message with the cause value
CV_TERMINAL_ERROR.
5-143
following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
IV. Formula
None
5.11.36 Count of Outgoing Trunk Calling Peer Office No Reply
I. Entity Name
NRPO
II. Description
It is the count of messages indicating that outgoing trunks wait for the ACMs until
timeout.
It is measured when timeout occurs as the outgoing trunk waits for the ACM.
The cause value in the REL message is CV_RECOVERY_OF_TIME_OUT.
5-144
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
IV. Formula
None
5.11.37 Count of Caller Release Before Ringing
I. Entity Name
RCBA
II. Description
It is the count of messages indicating caller onhook before ringing.
It is measured when the outgoing trunk waits for the ACM and the timer receives the
caller release ahead of time.
The cause value in the Release message is one of the following:
z CV_NORMAL
5-145
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
IV. Formula
None
I. Entity Name
ASTPL
II. Description
It is the average seizure traffic per line.
IV. Formula
E38/E25
5-146
5.12 Trunk Group Incoming Traffic

5.12.1 Overview of MS_TKGRP_INC_TRAF
Name Meaning
INTCGCL Count of call loss because of intra-office congestion




ITKAVAR Availability of incoming trunk


5-147
I. Entity Name
SEIZ
II. Description
occupied.
It is measured when the ISUP receives the IAM. See point A in the following figure.
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of messages indicating phones of callees ring in inter-office incoming

calls.
5-148
It is measured when the ISUP receives the Alerting message. See point B in the
following figure.
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of messages indicating local callees answer the phones in inter-office
incoming calls.
It is measured when the ISUP receives the Connect message. See point C in the
following figure.
5-149
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
5.12.5 Count of Call Loss Because of Intra-Office Congestion
I. Entity Name
INTCGCL
II. Description
For incoming trunk calls, it is the count of messages indicating invalid incoming call
attempts due to congestion of switches in the local office.
It is measured when the MSC sends the TUP SEC and ISUP REL (switch congestion)
messages to the originating office.
Insufficient internal resources cause switch congestion. Therefore, subsequent call
connection cannot be completed.
The measurement starts when the ISUP sends the REL message. See point A in the
following figure.
5-150
MTP ISUP
IAM
A
REL
IV. Formula
None
I. Entity Name
CGT
II. Description
The measurement starts when the congestion begins, and stops when the congestion
ends.
IV. Formula
None
I. Entity Name
CBSY
II. Description
For inter-office incoming calls, it is the count of messages indicating call release
because callees are busy. For calls started by subscribers of the local RNC/BSC, it is
the count of messages indicating call loss because the callees are busy.
5-151
It is measured when the Release message from the peer office or the BSC/RNC side is
received and the cause value indicates that the subscriber is busy.
The cause value in the Release message sent by the CCB is one of the following:
z CV_ST_BUSY
z CV_BUSY
z CV_SL_BUSY
z CV_GSM_CLD_USER_BUSY
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
REL A
IV. Formula
None
I. Entity Name
ARGABN
II. Description
Phones of callees ring but the callees do not answer. The entity is the count of
messages indicating that incoming trunks receive forward release signals.
5-152
For an inter-office incoming call, the phone of the callee rings but the callee does not
answer. The entity is measured when the MSC receives the CLF and REL messages
through incoming trunk circuits.
z CV_NORMAL
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
REL A
IV. Formula
None
I. Entity Name
LTNANS
II. Description
5-153

z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
REL A
IV. Formula
None
I. Entity Name
INSCIR
II. Description
It is the count of installed incoming trunk circuits (including bidirectional trunks) in the
5-154
IV. Formula
None
I. Entity Name
AVACIR
II. Description
IV. Formula
None
I. Entity Name
BLKCIR
II. Description
IV. Formula
None
I. Entity Name
INSBICIR
II. Description
measurement period.
5-155
IV. Formula
None
5.12.14 Count of available bidirectional circuits
I. Entity Name
AVABICIR
II. Description
IV. Formula
None
5.12.15 Count of blocked bidirectional circuits
I. Entity Name
BLKBICIR
II. Description
measurement period.
IV. Formula
None
5.12.16 Availability of Incoming Trunk
I. Entity Name
ITKAVAR
5-156
II. Description
BAM.)
IV. Formula
ITKAVAR = E10/E9
I. Entity Name
CNTR
II. Description
IV. Formula
CNTR = E1/E0
I. Entity Name
ANSR
II. Description
IV. Formula
ANSR = E2/E0
5-157
I. Entity Name
BLKR
II. Description
IV. Formula
BLKR = E11/E9
I. Entity Name
BLKBIR
II. Description
IV. Formula
BLKBIR = E14/E12
I. Entity Name
BISERL
II. Description
It is measured from the time when incoming calls occupy bidirectional trunks to the time
5-158
IV. Formula
None
I. Entity Name
SERL
II. Description
It is measured from the time when incoming calls in the office direction occupy incoming
abnormally.
It is measured from the time when the MSC receives the IAM to the time when it sends
or receives the UBM, Clear Forward, Clear Backward, or REL message in a
measurement period. The final result is indicated in Erlang (ITU-T Rec. Q.722).
IV. Formula
None
I. Entity Name
CERL
II. Description
It is measured from the time when incoming calls in the office direction are connected to
It is measured from the time when the MSC sends the ACM to the time when it sends or
receives the Clear Forward, Clear Backward, or REL message in a measurement
IV. Formula
None
I. Entity Name
RERL
5-159
II. Description
It is measured from the time when incoming calls in the office direction are answered to
It is measured from the time when the MSC sends the Answer Signal to the time when
it sends or receives the Clear Forward, Clear Backward, or REL message in a
measurement period. The final result is indicated in Erlang (ITU-T Rec. Q.722).
IV. Formula
None
I. Entity Name
AST
II. Description
It is the average seizure duration of incoming calls in an office direction. It is calculated

by using seizure traffic of incoming calls, seizure count of incoming calls, and sampling
period.
IV. Formula
E28/E0
I. Entity Name
ASTPL
II. Description
Average seizure traffic per line = Seizure traffic/(Count of installed bidirectional circuits
× 100)
IV. Formula
E22/(E10 × 100)
5-160
5.13 VP Office Direction Incoming Traffic

5.13.1 Overview of MS_VP_OFFICEDIR_INC_TRAF
Name Meaning
SEIZ Count of seizure
CNT Count of connected call
ANS Count of answered call

CERL Traffic of connected call
RERL Traffic of answered call
CBSY Count of callee determined busy

ARGABN Count of release after ringing
HORJ Count of Rejection of Handover from 3G to 2G

RAND Count of call drop on RAN side
RANDR Call drop rate on RAN side
5.13.2 Count of Seizure
I. Entity Name
SEIZ
II. Description
It is the count of messages containing the cause value RAB ASSIGN REQ to the RNC
when local mobile callers make VP calls.
It is measured when a mobile caller at the local office delivers the message RAB
ASSIGN REQ. See point A in the following figure.
5-161
MSC RNC
RAB ASSIGN REQ
IV. Formula
None
5.13.3 Count of Connected Call
I. Entity Name
CNT
II. Description
It is the count of connected VP calls made by mobile callers at the local office.
It is measured when a local mobile caller receives the ALERTING message from the
callee, who is in the local office or another one. See point A in the following figure.
5-162
MSC BSS/MSC'
Alerting
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of answered VP calls made by mobile callers at the local office.
It is measured when the mobile caller at the local office receives the CONNECT
message. See point A in the following figure.
5-163
MSC BSS/MSC'
Connect
IV. Formula
None
I. Entity Name
CNTR
II. Description
IV. Formula
E1/E0
I. Entity Name
ANSR
II. Description
5-164
IV. Formula
E2/E0
I. Entity Name
SERL
II. Description
It is the traffic transmitted from the time when mobile callers at the local office send the
assignment message to the air interface until the VP calls are released (normal release
and abnormal release).
In a measurement period, it is measured from the time when the caller sends the
assignment message to the air interface to the time when the VP call is released. The
final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
CERL
II. Description
It is the traffic transmitted from the time when mobile callers at the local office receive
the Alerting message to the time when the VP calls are released.
In a measurement period, it is measured from the time when the caller receives the
Alerting message to the time when the VP call is released. The final result is indicated
in Erlang.
IV. Formula
None
I. Entity Name
RERL
5-165
II. Description
It is the traffic transmitted from the time when mobile callers at the local office receive
the Connect message to the time when the VP calls are released.
In a measurement period, it is measured from the time when the caller receives the
Connect message to the time when the VP calls are released. The final result is
IV. Formula
None
5.13.10 Count of Callee Determined Busy
I. Entity Name
CBSY
II. Description
It is the count of losses of VP calls made by mobile callers at the local office due to
rejections of the callees.
It is measured when the mobile caller receives the REL message with the cause value
as Called determined busy from the peer office or the RNC side. See point A in the
following figure.
5-166
MSC BSS/MSC'
REL
IV. Formula
None
5.13.11 Count of Release After Ringing
I. Entity Name
ARGABN
II. Description
It is the count of VP calls released by mobile callers at the local office before the callees
answer the ringing VP calls.
It is measured when the caller hooks on after the mobile caller at the local office
receives the Alerting message before the callee answers. See point A in the following
figure.
5-167
MSC BSS/MSC'
Alerting
Release
A
IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of losses of VP calls made by mobile callers at the local office but not
answered for a long time.
It is measured when the mobile caller at the local office receives the Release message
with the cause value as Ringed no answer after receiving the Alerting message. See
5-168
MSC BSS/MSC'
Alerting
Release
A
IV. Formula
None
5.13.13 Count of Rejection of Handover from 3G to 2G
I. Entity Name
HORJ
II. Description
It is the count of rejections of handing over VP calls made by mobile callers at the local
office to the BSC after the callees answer the VP calls.
A mobile caller at the local office makes a VP call. After the callee answers, the caller
hands over the VP call to the 2G network. The entity is measured if the target network is
BSC after the RABM receives the message HANDOVER_START from the HO.
IV. Formula
None
5.13.14 Count of Call Drop on RAN Side
I. Entity Name
RAND
5-169
II. Description
It is the count of call drops at the local mobile caller side after the callees answer the VP
calls.
A mobile caller at the local office makes a VP call. It is measured when the MSC
receives the message IU_RELEASE _REQUEST/Abort from the RANAP after the
callee answers the VP call. See point A in the following figure.
RNC MSC
Iu-Release-Req/Abort
IV. Formula
None
5.13.15 Call Drop Rate on RAN Side
I. Entity Name
RANDR
II. Description
Call drop rate on RAN side = Count of call drops on RAN side/Count of answered calls
IV. Formula
E17/E2
5-170
5.14 VP Office Direction Outgoing Traffic

5.14.1 Overview of MS_VP_OFFICEDIR_OUT_TRAF
Name Meaning
BID Count of seizure attempt


CBSY Count of callee determined busy
ARGABN Count of release after ringing

HORJ Count of rejection of handover from 3G to 2G
RAND Count of call drop on RAN side
RANDR Call drop rate on RAN side
5.14.2 Count of Seizure Attempt
I. Entity Name
BID
II. Description
when local mobile callees answer VP calls.
It is measured when the callee side delivers the message RAB ASSIGN REQ. See
5-171
MSC RNC
RAB ASSIGN REQ
IV. Formula
None
I. Entity Name
SEIZ
II. Description
when local mobile callees answer VP calls.
It is measured when the callee side delivers the message RAB ASSIGN REQ. See
5-172
MSC RNC
RAB ASSIGN REQ
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of connections of VP calls to mobile callees at the local office.
5-173
It is measured when the MSC receives the message DTAP ALERTING from the MT.
MSC RNC
Alerting
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of VP calls answered by mobile callees at the local office.
5-174
It is measured when the MSC receives the message DTAP CONNECT from the MT.
MSC RNC
Connect
IV. Formula
None
I. Entity Name
CNTR
II. Description
IV. Formula
E2/E0
I. Entity Name
ANSR
5-175
II. Description
IV. Formula
E3/E0
I. Entity Name
SERL
II. Description
It is the traffic transmitted from the time when mobile callees at the local office send the
assignment messages to the air interface until the VP calls are released.
In a measurement period, it is measured from the time when the local office sends the
assignment message to the RNC to the time when the VP calls are released, that is, the
CM status becomes idle. The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
CERL
II. Description
It is the traffic transmitted from the time when a mobile callee at the local office hears
the ringing until the VP call is released.
It is measured from the time when the MSC receives the Alerting message until the call
is released. The final result is indicated in Erlang.
IV. Formula
None
5-176
I. Entity Name
RERL
II. Description
It is the traffic transmitted from the time when mobile callees at the local office answer
VP calls to the time when the VP calls are released.
It is measured from the time when the MSC receives the CONNECT message to the
time when the call is released. The final result is indicated in Erlang.
IV. Formula
None
I. Entity Name
CBSY
II. Description
It is the count of losses of VP calls rejected by mobile callees at the local office.
It is measured when the MSC receives the Disconnect message with the cause value
as Called determined busy from the RNC. See point A in the following figure.
5-177
MSC RNC
Disconnect
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of releases at the caller side before the local mobile callees answer the
ringing VP calls.
It is measured when the Release message with the cause value as Abandon after ring
is received before the callee answers the ringing call. See point A in the following figure.
5-178
MSC RNC
Alerting
Release
A
IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of call losses due to no answer from the local mobile callees to the ringing
VP calls.
It is measured when the MSC internally processes overtime. The local RNC mobile
callee does not answer after the ALERTING message is received. It is measured when
the MSC timer is overtime or the call is released with the cause value as Timer overtime.
5-179
MSC RNC
Alerting
Release
A
IV. Formula
None
5.14.14 Count of Rejection of Handover from 3G to 2G
I. Entity Name
HORJ
II. Description
It is the rejections of handovers from 3G to 2G after the local mobile callees answer the
VP calls.
A VP call is made to a mobile callee at the local office. After the callee answers, the call
is handed over to the 2G network. The entity is measured if the target network is BSC
after the RABM receives the message HANDOVER_START from the HO.
IV. Formula
None
5.14.15 Count of Call Drop on RAN Side
I. Entity Name
RAND
II. Description
It is the count of call losses after the local mobile callees answer the VP calls.
5-180
It is measured when the MSC receives the messages IU_RELEASE _REQUEST and
Abort from the RANAP after the callee answers the call. See point A in the following
figure.
RNC MSC
Iu-Release-Req/Abort
IV. Formula
None
5.14.16 Call Drop Rate on RAN Side
I. Entity Name
RANDR
II. Description
Call drop rate on RAN side = Count of call drops on RAN side/Count of answered calls
IV. Formula
E17/E3
5-181
5.15 VP Destination Traffic

5.15.1 Overview of MS_VP_DEST_TRAF
Name Meaning
PEGS Count of call attempt

ACVST Average call duration

BRGABN Count of abandon before alerting
ADI Count of incomplete address


CEUR Count of mobile subscriber unreachable
CFITB Count of inter-office trunk overflow
5.15.2 Count of Call Attempt
I. Entity Name
PEGS
II. Description
It is the count of VP call attempts to a certain destination (including the call originated
and transferred locally).
It is measured based on the destination code in the callee number analysis table after
the MSC receives the IAM (or DTAP SETUP) and completes the callee number
analysis.
5-182
BSS/MSC' MSC
Setup/IAM
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of alertings in VP calls.
If the callee is a mobile subscriber at the local office, it is measured when the MSC
receives the Alerting message from the callee side. If the callee is in another office, it is
measured when the MSC receives the ACM message from the callee side. See point A
5-183
BSS/MSC' MSC
Alerting/ACM
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of answered VP calls.
If the callee is a mobile subscriber at the local office, it is measured when the MSC
receives the Connect message. If the callee is in another office, it is measured when
the MSC receives the ANM message. See point A in the following figure.
5-184
BSS/MSC' MSC
Connect/ANM
IV. Formula
None
I. Entity Name
SERL
II. Description
It is the traffic transmitted from the time when VP calls are made to the time when the
VP calls are released.
In a measurement period, it is measured from the time when the IAM, IAI or DTAP
SETUP message is received to the time when the REL message is received. The final
result is indicated in Erlang.
IV. Formula
None
I. Entity Name
CERL
5-185
II. Description
It is the traffic transmitted from the time when VP calls are connected to the time when
the VP calls are released.
In a measurement period, it is measured from the time when the ACM (DTAP
ALERTING) message is received to the time when the REL message is received. The
IV. Formula
None
I. Entity Name
RERL
II. Description
It is the traffic transmitted from the time when the VP calls are answered to the time
when the calls are released.
In a measurement period, it is measured from the time when the ANM (DTAP
CONNECT) message is received to the time when the REL message is received. The
IV. Formula
None
5.15.8 Average Call Duration
I. Entity Name
ACVST
II. Description
Average call duration (average duration from the callee offhook to the onhook by one or
both sides) = Traffic of answered calls × Measurement period/Count of answered calls
5-186
IV. Formula
E9/E2
I. Entity Name
CNTR
II. Description
Call completion rate = Count of connected calls/Count of call attempts
IV. Formula
E1/E0
I. Entity Name
ANSR
II. Description
IV. Formula
E2/E0
5.15.11 Count of Abandon Before Alerting
I. Entity Name
BRGABN
II. Description
It is the count of VP calls released by callers after destinations are determined but
before the VP calls are connected.
5-187
It is measured when the MSC receives the REL message from the caller side before the
VP call is connected. See point A in the following figure.
MSC BSS/MSC'
Alerting
Release
A
IV. Formula
None
5.15.12 Count of Incomplete Address
I. Entity Name
ADI
II. Description
It is the count of failed VP calls due to incomplete numbers or addresses.
It is measured when the MSC receives the REL message from the peer office. See
5-188
MSC BSS/MSC'
REL
IV. Formula
None
I. Entity Name
CBSY
II. Description
It is the count of failed VP calls because callees are busy or refuse to answer.
It is measured when the MSC receives the REL message from the landing office if the
failure cause value is CV_SL_BUSY, CV_ST_BUSY or CV_BUSY. Or it is measured
when the MSC receives the DTAP DISCONNECT message from the MT before the
callee answers the ringing phone if the cause value is #17 "user busy" or #21 "call
rejected. See point A in the following figure.
5-189
MSC BSS/MSC'
REL
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of VP calls released by callers before callees answer the ringing VP call.
It is measured when the MSC receives the REL or DISCNNECT message during the
ringing. See point A in the following figure.
5-190
MSC BSS/MSC'
Alerting
Release
A
IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of forced releases due to timeout of the ringing VP calls not answered for
a long time.
It is measured when the VP call is disconnected because the MSC timer is overtime
during the ringing.
5-191
MSC BSS/MSC'
Alerting
Release
A
IV. Formula
None
5.15.16 Count of Mobile Subscriber Unreachable
I. Entity Name
CEUR
II. Description
It is the count of VP calls released by callers after destinations are determined but
before the VP calls are answered.
The MSC sends the Paging message to the RNC where the MT is located but does not
receive the message Paging Response. The entity is measured when the MSC
receives the forward REL message from the incoming trunk before the callee hears the
ringing. See point A in the following figure.
5-192
BSS/MSC' MSC
REL
IV. Formula
None
5.15.17 Count of Inter-Office Trunk Overflow
I. Entity Name
CFITB
II. Description
It is the count of routing failures due to the fully busy outgoing (bi-directional) trunk
when VP calls are made to destinations.
It is measured when the MSC fails in the trunk circuit selection (bi-directional).
IV. Formula
None
5.16 VP Trunk Office Direction Incoming Traffic

5.16.1 Overview of MS_TK_VP_OFC_INC_TRAF
Name Meaning
CNT Count of ringing
5-193
Name Meaning



I. Entity Name
SEIZ
II. Description
It is the count of the incoming trunk circuit (bi-directional) seizures when VP calls are
made.
It is measured when the ISUP receives the IAM message from the MTP. See point A in
5-194
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of ringings at the callee side when VP calls are made.
It is measured when the ISUP receives the Alerting message from the CCB. See point
5-195
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of VP calls answered by callees.
It is measured when the ISUP receives the Connect message from the CCB. See point
C in the following figure.
5-196
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
I. Entity Name
CNTR
II. Description
Call completion rate = Count of connected calls/Count of the seizures
It is calculated on the BAM at the end of a measurement period.
IV. Formula
CNTR = (E2+E17+E18+E20+E21+E22+E23+E24+E25+E26)/E0
I. Entity Name
ANSR
II. Description
5-197
IV. Formula
ANSR=E2/E0
I. Entity Name
SERL
II. Description
It is the traffic transmitted during the time from seizing of the incoming trunk
(bi-directional) to releasing of the trunk.
It is measured when the circuit is seized and released.
IV. Formula
None
I. Entity Name
CERL
II. Description
It is the traffic transmitted from the time when the callees hear the ringing to the time
when the VP calls are released after the VP calls have been established over the
network.
It is measured when the call is connected (that is, the ANM message is received) and
released.
IV. Formula
None
5-198
I. Entity Name
RERL
II. Description
It is the traffic transmitted from the time when the VP calls are answered to the time
when the VP calls are released.
It is measured when the VP call is answered (that is, the ACM message is received)
and released.
IV. Formula
None
I. Entity Name
CBSY
II. Description
It is the count of failed VP calls due to the busy callee failing to answer the connected
VP calls.
The callee is busy when receiving a new VP call. The entity is measured when the
caller receives the Disconnect message.
IV. Formula
None
I. Entity Name
ARGABN
II. Description
It is the count of VP calls released at the caller side during ringing.
5-199
It is measured when the ISUP receives the REL message from the peer office after the
callee hears the ringing but before answering. See point A in the following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
A Release
Release REL
IV. Formula
None
I. Entity Name
CLDONSP
II. Description
It is the count of force-released VP calls due to no reply for a long time.
It is measured when the REL message is received due to timeout after the ANM
message is sent but before the call is answered.
1) No reply at the callee side (Case one)
The caller side times out. The REL message contains one of the following cause
values:
z CV_NO_ACKNOWLEGE
5-200
See point A in the following figure. It is measured when the ISUP receives the REL
message from the peer office.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
A Release
Release
REL
2) No reply at the callee side (Case two)

The callee side times out. The REL message contains one of the following cause
values:
z CV_NO_ACKNOWLEGE
5-201
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A
IV. Formula
None
I. Entity Name
CONG
II. Description
It is the count of congestions when VP calls are made.
The callee returns the circuit congestion message after a new incoming VP call is
received. It is measured when the Disconnect message is received from the callee
side.
IV. Formula
None
5-202
5.17 VP Trunk Office Direction Outgoing Traffic

5.17.1 Overview of MS_TK_VP_OFC_OUT_TRAF
Name Meaning
BID Count of seizure attempt
CNT Count of ringing



5.17.2 Count of Seizure Attempt
I. Entity Name
BID
II. Description
It is the count of seizure attempts of the outgoing circuit (bi-directional) in the office
direction.
It is measured when the local office attempts to makes an outgoing VP call.
IV. Formula
None
5-203
I. Entity Name
SEIZ
II. Description
It is the count of the outgoing trunk circuit (bi-directional) seizures when VP calls are
made.
It is measured when the outgoing circuits are successfully seized after an outgoing VP
call is made.
See point A in the following figure. It is measured when the ISUP receives the Setup
message from the CCB.
IAM
Setup
Setup
Setup Ack
A
Setup Ack
IAM
Alerting ACM
Alerting
ACM
B
ANM
Connect
Connect
Connect Ack
ANM
Connect Ack
C
IV. Formula
None
I. Entity Name
CNT
5-204
II. Description
It is the count of ringings when VP calls are made.
It is measured when the ringing message is received after an outgoing VP call is made.
See point B in the following figure. It is measured when the ISUP receives the ACM
IAM
Setup
Setup
Setup Ack
A
Setup Ack
IAM
Alerting ACM
Alerting
ACM
B
ANM
Connect
Connect
Connect Ack
ANM
Connect Ack
C
IV. Formula
None
I. Entity Name
ANS
II. Description
It is the count of VP calls answered at the callee side.
It is measured when the Connect message is received after an outgoing VP call is

made. See point C in the following figure. It is measured when the ISUP receives the
ANM message from the peer office.
5-205
IAM
Setup
Setup
Setup Ack
A
Setup Ack
IAM
Alerting ACM
Alerting
ACM
B
ANM
Connect
Connect
Connect Ack
ANM
Connect Ack
C
IV. Formula
None
I. Entity Name
CNTR
II. Description
Call completion rate = Count of connected calls/Count of the seizures
IV. Formula
(E3+E22+E23+E25+E26+E27+E28+E29+E30+E31)/(E1+E6+E9)
I. Entity Name
ANSR
II. Description
5-206
IV. Formula
E3/(E1+E6+E9)
I. Entity Name
SERL
II. Description
It is the traffic transmitted during the time from seizing of the outgoing trunk
(bi-directional) to releasing of the trunk.
It is measured when the circuit is seized and released.
IV. Formula
None
I. Entity Name
CERL
II. Description
It is the traffic transmitted from the time when callees hear the ringing to the time when
the VP calls are released after VP calls have been established over the network.
It is measured when the VP call is connected (that is, the Connect message is received)
and released.
IV. Formula
None
I. Entity Name
RERL
5-207
II. Description
It is the traffic transmitted from the time when VP calls are answered to the time when
the VP calls are released.
It is measured when the VP call is answered (that is, the ACM message is received)
and released.
IV. Formula
None
I. Entity Name
OFL
II. Description
It is the count of routing failures due to the fully busy outgoing (bi-directional) trunk in
the office direction.
It is measured when the routing selection is failed.
IV. Formula
None
I. Entity Name
CBSY
II. Description
It is the count of VP calls not answered due to the busyness of callees.
It is measured when the caller side receives the Disconnect message due to the
busyness of the callee.
IV. Formula
None
5-208
I. Entity Name
ARGABN
II. Description
It is the count of VP calls released at the caller side during the ringing.
It is measured when the REL message is received from the caller side before the callee
answers the ringing call. See point A in the following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
IV. Formula
None
I. Entity Name
LTNANS
II. Description
It is the count of force-released VP calls due to no reply for a long time.
It is measured when the REL message is received due to no reply for a long time.
5-209
1) No reply at the callee side (Case one)

The caller side times out. The REL message contains one of the following cause
values:
z CV_NO_ACKNOWLEGE
message from the CCB.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
2) No reply at the callee side (Case two)

The callee side times out. The REL message contains one of the following cause
values:
z CV_NO_ACKNOWLEGE
5-210
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
IV. Formula
None
5-211
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Call Processing
Chapter 6 Call Processing

The measurement set is used to measure the traffic in different phases of call
processing. The measurement units are listed in the following table.
Name Description
MS_2G_CALL_DROP_RATE_TRAP GSM call drop rate
MS_MTC_SUCC_RATE_TRAF MTC success rate
MS_3G_CALL_DROP_RATE_TRAP WCDMA call drop rate

MS_DELIVERY_SUCC_RATE_TRAF Call setup rate
MS_CALL_SUCC_RATE_TRAF Answer rate
6.2 GSM Call Drop Rate

6.2.1 Overview of MS_2G_CALL_DROP_RATE_TRAP
Name Description
CT107 Count of connected calls
MCT107 Count of connected MO calls
TCT107 Count of connected MT calls
DT107 Count of dropped calls
MDT107 Count of dropped MO calls
TDT107 Count of dropped MT calls
HFDT107 Count of dropped calls due to handover failure
CDR107 Call drop rate
6-1
I. Entity Name
CT107
II. Description
It is the count of connected calls when either the callers or callees are local mobile
subscribers. The call attributes include intra-office call, outgoing call and incoming call.
Count of connected calls = Count of connected MO calls + Count of connected MT calls
IV. Formula
None
6.2.3 Count of Connected MO Calls
I. Entity Name
MCT107
II. Description
It is the count of connected MO calls.
z For an intra-office call, it is measured when the MSC sends the message DTAP
Connect to a mobile caller after receiving it from an MT callee.
z For an outgoing call, it is measured when the MSC sends the message DTAP
Connect to a mobile caller after receiving the ANC message from the terminating
office.
IV. Formula
None
6.2.4 Count of Connected MT Calls
I. Entity Name
TCT107
II. Description
It is the count of connected MT calls.
6-2
For an intra-office call or an incoming call, it is measured when the MSC receives the
message DTAP Connect from the MT callee.
IV. Formula
None
6.2.5 Count of Dropped Calls
I. Entity Name
DT107
II. Description
It is the count of dropped calls when either the callers or callees are mobile subscribers.
Count of dropped calls = Count of dropped MO calls + Count of dropped MT calls +

Count of dropped calls due to handover failure
IV. Formula
None
6.2.6 Count of Dropped MO Calls
I. Entity Name
MDT107
II. Description
It is the count of calls dropped due to the 2G mobile callers.
It is measured when the MSC receives the message BSSMAP Clear Request from the
BSC at the caller side during the talk.
IV. Formula
None
6.2.7 Count of Dropped MT Calls
I. Entity Name
TDT107
6-3
II. Description
It is the count of calls dropped due to the 2G mobile callees.
It is measured when the MSC receives the message BSSMAP Clear Request from the
BSC at the callee side during the talk.
IV. Formula
None
6.2.8 Count of Dropped Calls Due to Handover Failure
I. Entity Name
HFDT107
II. Description
It is the count of dropped calls due to errors in handover.
It is measured when the MSC receives BSSMAP Clear Request after sending the
message HO COMMAND to the source BSC during the handover.
IV. Formula
None
6.2.9 Call Drop Rate
I. Entity Name
CDR107
II. Description
Call drop rate = Count of dropped calls/Count of connected calls
IV. Formula
CDR107=DT107/CT107
6-4
6.3 MTC Success Rate

6.3.1 Overview of MS_MTC_SUCC_RATE_TRAF
Name Description
PAG109 Count of pagings
PAGRSP109 Count of paging responses

SPR109 Paging success rate
ALT109 Count of connected calls
MOALT109 Count of connected intra-office calls

LOALT109 Count of connected incoming calls
SR109 MT call completion rate
6.3.2 Count of Pagings
I. Entity Name
PAG109
II. Description
It is the count of PAGING messages sent to mobile callees (during the first paging). The
call attributes include intra-office call and incoming call.
It is measured when the MSC sends the PAGING message to a callee. See point A in
6-5
RNS MSC Server
PAGING
……
A
PAGING
PAGING RESPONSE
IV. Formula
None
6.3.3 Count of Paging Responses
I. Entity Name
PAGRSP109
II. Description
It is the count of responses to pagings of local mobile subscribers.
It is measured when the MSC receives the message PAGE_RESPONSE from the
callee side. See point A in the following figure.
6-6
MSC RNC
Page_Response
IV. Formula
None
6.3.4 Paging Success Rate
I. Entity Name
SPR109
II. Description
Paging success rate = Number of paging responses/Number of pagings
IV. Formula
E1/E0
I. Entity Name
ALT109
II. Description
It is the count of connected calls, including intra-office calls and incoming calls.
It is measured when the MSC receives the Alerting (Connect) message.
6-7
Count of connected calls = Count of connected intra-office calls + Count of connected

incoming calls.
IV. Formula
E4+E5
6.3.6 Count of Connected Intra-Office Calls
I. Entity Name
MOALT109
II. Description
It is the count of connected MT calls, including intra-office calls.
It is measured when the MSC receives the Alerting message.
IV. Formula
None
6.3.7 Count of Connected Incoming Calls
I. Entity Name
LOALT109
II. Description
It is the count of connected calls to fixed subscribers, including incoming calls.
It is measured when the MSC receives the Alerting message. Only one connection is
measured for a multiparty call.
IV. Formula
None
6.3.8 MT Call Completion Rate
I. Entity Name
SR109
II. Description
MT call completion rate = Count of connected calls/Count of pagings
6-8
IV. Formula
(E4+E5)/E0
6.4 WCDMA Call Drop Rate

6.4.1 Overview of MS_3G_CALL_DROP_RATE_TRAP
Name Description
CON111 Count of connected calls
MOCC111 Count of connected MO calls

MTCC111 Count of connected MT calls
DROP111 Count of dropped calls
MODRP111 Count of dropped MO calls
MTDRP111 Count of dropped MT calls
HODRP111 Count of dropped calls due to handover failure
DRATE111 Call drop rate
I. Entity Name
CON111
II. Description
It is the count of connected calls when either the callers or callees are in the local office,
that is, it is the count of connected calls except tandem calls.
Count of connected calls = Count of connected MO calls + Count of connected MT calls
IV. Formula
E1+E2
6-9
6.4.3 Count of Connected MO Calls
I. Entity Name
MOCC111
II. Description
It is the count of connected MO calls.
It is measured when the MSC sends the message DTAP CONNECT to the mobile caller.
RNC MSC
Connect
IV. Formula
None
6.4.4 Count of Connected MT Calls
I. Entity Name
MTCC111
II. Description
It is the count of connected MT calls.
It is measured when the MSC sends the message DTAP CONNECT to a mobile callee.
6-10
MSC RNC
Connect
IV. Formula
None
6.4.5 Count of Dropped Calls
I. Entity Name
DROP111
II. Description
It is the count of dropped calls in the local office.
Count of dropped calls = Count of dropped MO calls + Count of dropped MT calls +

Count of dropped calls due to handover failure
IV. Formula
E4+E5+E6
6.4.6 Count of Dropped MO Calls
I. Entity Name
MODRP111
II. Description
It is the count of calls dropped due to the 3G mobile callers.
6-11
It is measured when the MSC receives the message Iu Release Request from the RNC
at the caller side during a talk. See point A in the following figure.
RNC MSC
Iu_Release_Request
IV. Formula
None
6.4.7 Count of Dropped MT Calls
I. Entity Name
MTDRP111
II. Description
It is the count of calls dropped due to the 3G mobile callees.
It is measured when the MSC receives the message Iu Release Request from the RNC
at the callee side during a talk. See point A in the following figure.
6-12
MSC RNC
Iu_Release_Request
IV. Formula
None
6.4.8 Count of Dropped Calls Due to Handover Failure
I. Entity Name
HODRP111
II. Description
It is the count of dropped calls due to handover failure.
It is measured when the MSC receives the message Clear Request after sending
RELOCATION COMMAND to the source RNC during handover. See point A in the
following figure.
6-13
RNC MSC
Relocation_Command
Clear_Request
IV. Formula
None
6.4.9 Call Drop Rate
I. Entity Name
DRATE111
II. Description
Call drop rate = Count of dropped calls/Count of connected calls
IV. Formula
(E4+E5+E6)/(E1+E2)
6.5 Call Setup Rate

6.5.1 Overview of MS_DELIVERY_SUCC_RATE_TRAF
Name Description
MCDT110 Count of call setup attempts
Count of call setup attempts from mobile subscriber to

CDMM110
mobile subscriber
6-14
Name Description
Count of call setup attempts from mobile subscriber to
CDMF110
fixed subscriber
Count of call setup attempts from fixed subscriber to
CDFM110
mobile subscriber
Count of call setup attempts from fixed subscriber to fixed
CDFF110
subscriber
SMCDT110 Count of successful call setups
Count of successful call setups from mobile subscriber to

SCDMM110
mobile subscriber
Count of successful call setups from mobile subscriber to

SCDMF110
fixed subscriber
Count of successful call setups from fixed subscriber to

SCDFM110
mobile subscriber
Count of successful call setups from fixed subscriber to

SCDFF110
fixed subscriber
MCDSR110 Call setup success rate
6.5.2 Count of Call Setup Attempts
I. Entity Name
MCDT110
II. Description
It is the count of call attempts set up by the MSC.
Count of call setup attempts = Count of call setup attempts from mobile subscriber to
mobile subscriber + Count of call setup attempts from mobile subscriber to fixed
subscriber + Count of call setup attempts from fixed subscriber to mobile subscriber +
Count of call setup attempts from fixed subscriber to fixed subscriber
IV. Formula
None
6.5.3 Count of Call Setup Attempts from Mobile Subscriber to Mobile

Subscriber
I. Entity Name
CDMM110
6-15
II. Description
It is the count of call setup attempts from mobile subscribers to other mobile
subscribers when the MSC analyzes the callee numbers and notifies callers that the
calls are being connected.
It is measured when the MSC receives the message PAGING_RSP from the callee.
RNC/BSC MSC Server RNC/BSC
DTAP SETUP
DTAP PAGE_RSP
A
DTAP SETUP
DTAP ALERTING
B
DTAP ALERTING
IV. Formula
None
6.5.4 Count of Call Setup Attempts from Mobile Subscriber to Fixed

Subscriber
I. Entity Name
CDMF110
II. Description
It is the count of call setup attempts from mobile subscribers to fixed subscribers when
the MSC confirms that the callees are in the local office and notifies callers that the calls
are being connected.
It is measured when the outgoing circuits are occupied. See point A in the following
figure.
6-16
RNC/BSC MSC Server MSC Server
DTAP SETUP
A
IAM
ACM
B
DTAP ALERTING
IV. Formula
None
6.5.5 Count of Call Setup Attempts from Fixed Subscriber to Mobile

Subscriber
I. Entity Name
CDFM110
II. Description
It is the count of connection attempts after the MSC analyzes the callee numbers and
confirms that the calls are incoming calls.
It is measured when the MSC receives the message PAGING_RSP from the callee.
6-17
MSC Server MSC Server RNC/BSC
IAM
DTAP PAGE_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM
IV. Formula
None
6.5.6 Count of Call Setup Attempts from Fixed Subscriber to Fixed

Subscriber
I. Entity Name
CDFF110
II. Description
It is the count of connection attempts after the MSC analyzes the callee numbers and
confirms that the incoming calls are transferred calls.
It is measured when the outgoing circuits are occupied. See point A in the following
figure.
6-18
MSC Server MSC Server MSC Server

IAM
IAM
A
ACM
B
ACM
IV. Formula
None
6.5.7 Count of Successful Call Setups
I. Entity Name
SMCDT110
II. Description
It is the count of successful connections.
Count of successful call setups = Count of successful call setups from mobile
subscriber to mobile subscriber + Count of successful call setups from mobile
subscriber to fixed subscriber + Count of successful call setups from fixed subscriber to
mobile subscriber + Count of successful call setups from fixed subscriber to fixed
subscriber
IV. Formula
None
6.5.8 Count of Successful Call Setups from Mobile Subscriber to Mobile

Subscriber
I. Entity Name
SCDMM110
6-19
II. Description
It is the count of connected intra-office calls made by mobile callers.
It is measured when the MSC receives the message DTAP Alerting from a callee. See
DTAP SETUP
DTAP PAGE_RSP
A
DTAP SETUP
DTAP ALERTING
B
DTAP ALERTING
IV. Formula
None
6.5.9 Count of Successful Call Setups from Mobile Subscriber to Fixed

Subscriber
I. Entity Name
SCDMF110
II. Description
It is the count of connected outgoing calls made by mobile callers.
It is measured when the MSC receives the ACM from a callee. See point B in the
following figure.
6-20
DTAP SETUP
A
IAM
ACM
B
DTAP ALERTING
IV. Formula
None
6.5.10 Count of Successful Call Setups from Fixed Subscriber to Mobile

Subscriber
I. Entity Name
SCDFM110
II. Description
It is the count of connected incoming calls.
It is measured when the MSC receives the message DTAP ALERTING from a callee.
6-21
IAM
DTAP PAGE_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM
IV. Formula
None
6.5.11 Count of Successful Call Setups from Fixed Subscriber to Fixed

Subscriber
I. Entity Name
SCDFF110
II. Description
It is the count of successful connections of transferred calls.
It is measured when the MSC receives the ACM from a callee. See point B in the
following figure.
6-22

IAM
IAM
A
ACM
B
ACM
IV. Formula
None
6.5.12 Call Setup Success Rate
I. Entity Name
MCDSR110
II. Description
Call setup success rate = Count of successful call setups/Count of call setups
IV. Formula
MCDSR110=SMCDT110/MCDT110
6.6 Answer Rate

6.6.1 Overview of MS_CALL_SUCC_RATE_TRAF
Name Description
CA108 Count of call attempts
MCA108 Count of MO call attempts
6-23
Name Description
MCAT108 Count of incoming call attempts by fixed subscriber
CAT108 Count of answered calls
MCATM108 Count of answers to MO calls
MCTA108 Count of answers to incoming calls by fixed subscriber
CSR108 Answer rate
6.6.2 Count of Call Attempts
I. Entity Name
CA108
II. Description
It is the count of incoming call attempts made by mobile callers.
Count of call attempts = Count of MO call attempts + Count of incoming call attempts by
fixed subscriber
IV. Formula
None
6.6.3 Count of MO Call Attempts
I. Entity Name
MCA108
II. Description
It is the count of calls originated by mobile callers.
It is measured when the MSC receives the message CM Service Request from a
mobile caller. See point A in the following figure.
6-24
RNC/BSC MSC Server
DTAP SERVICE REQEST
DTAP ALERTING
DTAP CONNECT
IV. Formula
None
6.6.4 Count of Incoming Call Attempts by Fixed Subscriber
I. Entity Name
MCAT108
II. Description
It is the count of incoming calls originated by fixed subscribers.
It is measured when the MSC receives the IAM from the originating office. See point A
6-25
IAM
ACM
ANM/ANC
IV. Formula
None
I. Entity Name
CAT108
II. Description
It is the count of answers to incoming calls originated by mobile callers.
Count of answered calls = Count of answers to MO calls + Count of answers to

incoming calls by fixed subscriber
IV. Formula
None
6.6.6 Count of Answers to MO Calls
I. Entity Name
MCATM108
II. Description
It is the count of answered calls originated by mobile callers.
6-26
z For an intra-office call, it is measured when the MSC sends the message DTAP
Connect to a mobile caller after receiving it from an MT callee.
z For an outgoing call, it is measured when the MSC sends the message DTAP
Connect to a mobile caller after receiving the message ANC or ANM from the
terminating office.
If the callee is in another office, see point A in the following figure. If the callee is a local
mobile subscriber, see point B in the following figure.

DTAP SETUP
IAM
ACM
DTAP ALERTING
ANM/ANC
A RNC/BSC
DTAP CONNECT
DTAP SETUP DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP CONNECT
DTAP CONNECT B
IV. Formula
None
6.6.7 Count of Answers to Incoming Calls by Fixed Subscriber
I. Entity Name
MCTA108
II. Description
It is the count of answers to incoming calls originated by fixed subscribers (including the
PSTN subscribers and GSM subscribers in other regions).
z For an incoming call, it is measured when the MSC returns the messages ANC
and ANM to the originating office after receiving DTAP Connect from an MT callee.
z For a transferred call, it is measured when the MSC returns message ANC or ANM
to the originating office after receiving them from the terminating office.
mobile subscriber, see point B in the following figure.
6-27

IAM
IAM
ACM
ACM
ANM/ANC
A RNC/BSC
ANM/ANC
IAM DTAP SETUP
DTAP ALERTING
ACM
DTAP CONNECT
ANM/ANC B
IV. Formula
None
6.6.8 Answer Rate
I. Entity Name
CSR108
II. Description
Answer rate = Count of answered calls/Count of call attempts
IV. Formula
CSR108=CAT108/CA108
6-28
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 7 Call Record
Chapter 7 Call Record

This measurement set tests the measurement point, average internal and external
connection duration during the connections. It also performs the test based on
combined conditions.
Name Description
MS_MULTI_CONDITION_OBJECT_TRAF Combined Object Conditions Traffic
MS_DISPERSION_DURATION_TRAF Traffic Distribution and Duration
7.2 Combined Object Conditions Traffic

It is the measurement unit of task matching type. Every entity is tested when the MSC
releases the call.
The names and the meanings are listed in the following table.
Name Description
PEGS Count of call attempts
SEIZT Seizure traffic

ANST Call answer traffic
ASTAUX Total seizure duration
AANSTAUX Total answer duration
ALTR Rate of connected calls
AANST Average answer duration
MCTOK Count of malicious call identification successes
MCTFL Count of malicious call identification failures
7-1
Name Description
SEC Count of switch congestions
LTNDG Count of no dialing
SYSFL Count of temporary failures
RTSTOK Count of self-test successes
LTNINF Count of no messages
LTNRG Count of no ringing
LTNRLS Count of no release
INBSIG Count of inband signals
COCFL Count of continuity check failures
EXREATP Count of exceed maximum retries
BRGABN Count of subscriber release before ringing
ARGABN Count of release before answers
BAR Count of call barring

SEFL Count of switch failures
SEFL1 Count of callee toll busy
SEFL2 Count of callee local busy

REPMCG Count of peer equipment congestions
CLFL Count of call failures
DSEIZ Count of circuit contentions
INVCD Count of invalid numbers
NMNBAR Count of call restriction by NMS
CPUOL Count of CPU congestion and overload
NCR Count of no CR resources
NCCB Count of no CCB resources
IFCR Count of incoming forwarded call restrictions
DIALTO Count of dial interval timeout
SIGER Count of signaling fault
BWLBAR Count of black and white list restrictions
BWLBAR1 Count of caller number discrimination failures
NACFBS Count of no A interface circuit for bearer service
NAC Count of circuit without A interface
7-2
Name Description
ICUGS Count of CUG service incompatible
UCUG Count of known CUG
NSCUG Count of unselected CUG
BOCUG Count of CUG outgoing call barring
BICUG Count of CUG incoming call barring
CUGSSI Count of CUG supplementary service failures
ICUGD Count of CUG destination incompatible
CL Count of call releases
HOC Count of switchover successes
HOF Count of switchover failures
TECLT Count of duration limit timeout
TF Count of termination resource application failures
CDNE Count of non-existent called numbers
NAFCD Count of no answer from called mobile subscribers

Count of called mobile subscriber barring of incoming Count of
CDBAIC
calls
CRBOAC Count of caller barring of outgoing calls

CDUR Count of callee unreachable or switched off
NACP Count of calling local subscriber without dialing area code

CDB Count of called mobile subscriber busy
CDPO Count of called mobile subscriber switched off
SNA Count of needed function not applied

DZ Count of calling mobile subscriber in other area without dialing 0
CFV Count of call forwarding conflicts
Count of error found when getting routing information through
ESRI
HLR
ODBAOC Count of carrier barring of all outgoing calls

ODBOIC Count of carrier barring of all outgoing international calls
UBOICE Count of subscriber barring of all outgoing international calls
UBOICENH Count of BOIC-exHC barred by subscribers
ODBOICE Count of BOIC-exHC barred by operators
ODBAIC Count of carrier barring of all incoming calls
ODBEC Count of carrier barring of entertainment console
7-3
Name Description
ODBMC Count of carrier barring of console
SROP Count of subscriber out of service area
ODBT Count of carrier barring of national toll
UN Count of call failure because of unknown reason
UALCCD Count of unallocated numbers
NRUTOSI Count of no route to transit network
NRUTOTE Count of no route to destination
SPRVTONE Count of sending special signal tones
ERLNGPFX Count of dialing wrong toll prefix
RUUAPT Count of unaccepted paths
CALLEST Count of call established and delivered on path established
ODB Count of call barring decided by carrier
RFREUSE Count of circuit reserved for reuse
NORCLR Count of normal cleared calls

UDB Count of callee busy
NRSP Count of no response from callee
NACK Count of no answer from callee

AS Count of callee absent
REJ Count of call rejected
CDCHD Count of called number changed
NFC Count of no idle circuits
RABPE Count of RAB resource pre-used
TEER Count of destination fault
INVCDFMT Count of invalid number format
FACREJ Count of facility rejected
RSPSE Count of response to STATUS ENQUIRY
NOR Count of normal cleared calls
NCIR Count of no available circuits
NETER Count of network failures
TMPER Count of temporary failures
EPMCG Count of switch congestions
AIL Count of access information lost
7-4
Name Description
NRUCIR Count of circuits unavailable
PCALLBLK Count of prior calls blocked
NRSC Count of no available resource
NSSQUA Count of no suitable service quality
FACNPV Count of required facility not booked
CUGBC Count of CUG barring out-group calls
CUGUALW Count of CUG incoming call not allowed
BCUNP Count of bearer capability not registered
NBC Count of no available bearer capability
NSSOOP Count of no suitable service or optional projects
BCNLO Count of bearer capability not carried out
RTNLO Count of route type not supported
AOCRF Count of AOC service request failures
ACMEG Count of ACM greater or equal to ACMmax

FACNLO Count of requested facility not supported
LTDDIBC Count of only having restricted bearer capability
IWFRU Count of IWF resource unavailable

SOPNLO Count of service or optional project not supported
INVCR Count of invalid call reference
RUNEXT Count of identified path do not exist
CLDNOCUG Count of callee not in CUG
TEUCPT Count of incompatible destinations
NECUG Count of non-existent CUG
INVTNL Count of invalid transit network selections
INVMSG Count of invalid messages
MSGNOEXT Count of non-existent or not supported message types
IENOEXT Count of non-existent or not supported information elements
TOUT Count of recovery of timer timeout
PARANOEXT Count of non-existent or not invoked parameters
UNRECPARA Count of message with unrecognized parameters
PROERR Count of protocol errors
INTWORK Count of interworking
7-5
I. Entity Name
PEGS
II. Description
It is the count of call attempts on the calling directions specified under combined
conditions.
It is measured when the MSC succeeds in internal number analysis.
IV. Formula
None
I. Entity Name
SEIZ
II. Description
It is the count of circuits seizures by calls meeting the requirements.
It is measured when the MSC internally seizes a trunk circuit.
IV. Formula
None
I. Entity Name
CNT
II. Description
It is the count of DTAP alerting messages sent to the MSC.
It is measured when the MSC receives the ACM (DTAP ALERTING) from the callee.
IV. Formula
None
7-6
I. Entity Name
ANS
II. Description
It is the count of answered calls meeting the requirements.
It is measured when the MSC receives the ANM (DTAP CONNECT) from the callee.
IV. Formula
None
I. Entity Name
SEIZT
II. Description
It is the traffic generated from the moment the called trunk circuit is seized to that the
circuit is released.
It is measured when the MSC succeeds in number analysis.
IV. Formula
None
I. Entity Name
ANST
II. Description
It is the traffic generated from the moment the call is answered to that the call is
released.
It is measured when the MSC receives the ANM (DTAP CONNECT) from the callee.
7-7
IV. Formula
None
7.2.8 Total Seizure Duration
I. Entity Name
ASTAUX
II. Description
If Count of seizure is not 0, Total seizure duration = Seizure traffic × measurement

period.
IV. Formula
None
7.2.9 Total Answer Duration
I. Entity Name
AANSTAUX
II. Description
If Count of answered calls is not 0, Total answer duration = Traffic of answer calls ×
Measurement period.
IV. Formula
None
7.2.10 Rate of Connected Calls
I. Entity Name
ALTR
II. Description
Count of connected calls/Count of call attempts
7-8
IV. Formula
ALTR=CNT/PEGS
I. Entity Name
AST
II. Description
Seizure traffic × Measurement period/Count of seizure
IV. Formula
None
7.2.12 Average Answer Duration
I. Entity Name
AANST
II. Description
Traffic of answered calls × Measurement period/Count of answered calls
IV. Formula
None
7.2.13 Count of Malicious Call Identification Successes
I. Entity Name
MCTOK
II. Description
It is the count of successes in probing malicious calls.
7-9
It is measured when the MSC releases the call.
IV. Formula
None
7.2.14 Count of Malicious Call Identification Failures
I. Entity Name
MCTFL
II. Description
It is the count of failures in probing malicious calls.
IV. Formula
None
7.2.15 Count of Switch Congestions
I. Entity Name
SEC
II. Description
It is the count of internal MSC congestions.
IV. Formula
None
7.2.16 Count of Long Time No Dialing
I. Entity Name
LTNDG
II. Description
It is the count of long time no dialing after callers hook off.
7-10
IV. Formula
None
7.2.17 Count of Long Time No Reply
I. Entity Name
LTNANS
II. Description
It is the count of calls that are released because the callees do not answer till timeout.
IV. Formula
None
7.2.18 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
7.2.19 Count of Self-Test Successes
I. Entity Name
RTSTOK
II. Description
It is the count of self-test successes.
7-11
IV. Formula
None
7.2.20 Count of 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
7.2.21 Count of No Ringing
I. Entity Name
LTNRG
II. Description
It is the count of connection failures due to timeout when callers do not receive the
messages DTAP Alerting after receiving the messages PAGING ACK from callees.
IV. Formula
None
7.2.22 Count of No Releases
I. Entity Name
LTNRLS
7-12
II. Description
It is the count of calls disconnected in specified periods after the DISCONNECT

messages are received.
IV. Formula
None
7.2.23 Count of Inband Signals
I. Entity Name
INBSIG
II. Description
It is the count of inband signals.
IV. Formula
None
7.2.24 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
7.2.25 Count of Exceed Maximum Retries
I. Entity Name
EXREATP
7-13
II. Description
It is the count of call attempts that exceed the maximum number in the call connections
due to the contention.
IV. Formula
None
7.2.26 Count of Subscriber Releases Before Ringing
I. Entity Name
BRGABN
II. Description
It is the count of active releases by the callers before callees' phones ring.
IV. Formula
None
7.2.27 Count of Releases Before Answers
I. Entity Name
ARGABN
II. Description
It is the count of active releases by the callers before callees pick up their phones.
IV. Formula
None
7.2.28 Count of Call Barrings
I. Entity Name
BAR
7-14
II. Description
It is the count of calls barred due to subscriber service restrictions.
IV. Formula
None
7.2.29 Count of Switch Failures
I. Entity Name
SEFL
II. Description
It is the count of MSC failures in processing the IN services and iPath.
IV. Formula
None
I. Entity Name
SEFL1
II. Description
It is the count of fixed-line toll calls failed because callees are busy.
IV. Formula
None
I. Entity Name
SEFL2
7-15
II. Description
It is the count of fixed-line local calls failed because callees are busy.
IV. Formula
None
7.2.32 Count of Peer Equipment Congestions
I. Entity Name
REPMCG
II. Description
It is the count of calls failed due to peer office congestions.
IV. Formula
None
7.2.33 Count of Call Failures
I. Entity Name
CLFL
II. Description
It is caused by the following reasons:

z The peer office is congested and the MSC cannot obtain the addressing message
after receiving the SETUP message.
z The peer office DSP is unavailable and the TUP releases the call due to the timer
timeout.
z The called number is less than that requested when the MSC receives the IAM.
z The MSC receives the RLG message abnormally.
z The channel is blocked due to TUP circuit busy.
z The circuit group is blocked.
z The internal timer is timeout when the TUP is in the ringing state.
z The MSC fails to receive the GSM message.
z The TUP fails to receive the SETUP message.
7-16
z The CFL message is received.
IV. Formula
None
7.2.34 Count of Circuit Contentions
I. Entity Name
DSEIZ
II. Description
It is the count of trunk busy due to contentions.
IV. Formula
None
7.2.35 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
7.2.36 Count of Call Restrictions by NMS
I. Entity Name
NMNBAR
7-17
II. Description
It is the count of calls barred by the NMS.
IV. Formula
None
7.2.37 Count of CPU Congestions and Overload
I. Entity Name
CPUOL
II. Description
It is the count of messages indicating CPU congestions and overload.
IV. Formula
None
7.2.38 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
7.2.39 Count of No CCB Resources
I. Entity Name
NCCB
7-18
II. Description
It is the count of insufficient CCB resources which are used by the network side when
originating or terminating calls.
IV. Formula
None
7.2.40 Count of Incoming Forwarded Call Restrictions
I. Entity Name
IFCR
II. Description
It is the count of forwarded calls barred by the peer office.
IV. Formula
None
7.2.41 Count of Dialing Interval Timeout
I. Entity Name
DIALTO
II. Description
It is the count of timeout in dialing.
IV. Formula
None
7.2.42 Count of Signaling Fault
I. Entity Name
SIGER
7-19
II. Description
It is the count of signaling cooperation failures between SS7 and SS1.
IV. Formula
None
7.2.43 Count of Black and White List Restrictions
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
7.2.44 Count of Caller Number Discrimination Failures
I. Entity Name
BWLBAR1
II. Description
It is the count of failures in identifying the caller numbers.
IV. Formula
None
7.2.45 Count of No A Interface Circuits for Bearer Service
I. Entity Name
NACFBS
7-20
II. Description
It is the count of no A interface resources for bearing the services.
IV. Formula
None
7.2.46 Count of Circuits Without A Interface
I. Entity Name
NAC
II. Description
It is the count of no A interface circuits.
IV. Formula
None
7.2.47 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
7.2.48 Count of Unknown CUG
I. Entity Name
UCUG
7-21
II. Description
It is the count of supplementary service failures due to CUG unknown.
IV. Formula
None
7.2.49 Count of Unselected CUG
I. Entity Name
NSCUG
II. Description
It is the count of supplementary service failures due to CUG unselected.
IV. Formula
None
7.2.50 Count of CUG Outgoing Call Barring
I. Entity Name
BOCUG
II. Description
It is the count of calls barred due to CUG outgoing restrictions.
IV. Formula
None
7.2.51 Count of CUG Incoming Call Barring
I. Entity Name
BICUG
7-22
II. Description
It is the count of calls barred due to CUG incoming restrictions.
IV. Formula
None
7.2.52 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
7.2.53 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
7.2.54 Count of Call Releases
I. Entity Name
CL
7-23
II. Description
It is the count of call releases.
IV. Formula
None
7.2.55 Count of Switchover Successes
I. Entity Name
HOC
II. Description
It is the count of successful switchovers.
IV. Formula
None
7.2.56 Count of Switchover Failures
I. Entity Name
HOF
II. Description
It is the count of failed switchovers.
IV. Formula
None
7.2.57 Count of Duration Limit Timeout
I. Entity Name
TECLT
7-24
II. Description
It is the count of calls released because the session durations exceed the threshold.
IV. Formula
None
7.2.58 Count of Termination Resource Application Failures
I. Entity Name
TF
II. Description
It is the count of application failures of the Termination recourses.
IV. Formula
None
7.2.59 Count of Non-Existent Called 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
7.2.60 Count of No Answer from Called Mobile Subscribers
I. Entity Name
NAFCD
7-25
II. Description
It is the count of mobile callees no reply after ringing.
IV. Formula
None
7.2.61 Count of Called Mobile Subscriber Barring of Incoming Calls
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
7.2.62 Count of Caller Barring of Outgoing Calls
I. Entity Name
CRBOAC
II. Description
It is the count of calls failed because the mobile callers have set outgoing call
restrictions.
IV. Formula
None
7-26
7.2.63 Count of Callees Unreachable or Switched off
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
7.2.64 Count of Calling Local Subscriber Without Dialing 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
7.2.65 Count of Called Mobile Subscriber Busy
I. Entity Name
CDB
II. Description
It is the count of forwarding calls restricted because mobile callees are busy.
7-27
IV. Formula
None
7.2.66 Count of Called Mobile Subscriber Switched off
I. Entity Name
CDPO
II. Description
It is the count of messages indicating mobile callers are power-off or abnormal.
IV. Formula
None
7.2.67 Count of Needed Function Not Applied
I. Entity Name
SNA
II. Description
It is the count of required service functions that are not applied.
IV. Formula
None
7.2.68 Count of Calling Mobile Subscriber in Other Area Without Dialing 0
I. Entity Name
DZ
II. Description
It is the count of unallocated numbers generated when the callers make non-local calls
without adding "0".
7-28
IV. Formula
None
7.2.69 Count of Call Forwarding Conflicts
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
7.2.70 Count of Errors Found When Getting Routing Information Through

HLR
I. Entity Name
ESRI
II. Description
It is the count of routing selection and protocol errors.
IV. Formula
None
7.2.71 Count of Carrier Barring of All Outgoing Calls
I. Entity Name
ODBAOC
II. Description
It is the count of outgoing calls barred by operators.
7-29
IV. Formula
None
7.2.72 Count of Carrier Barring of All Outgoing International Calls
I. Entity Name
ODBOIC
II. Description
It is the count of outgoing international calls barred by operators.
IV. Formula
None
7.2.73 Count of Subscriber Barring of All Outgoing International Calls
I. Entity Name
UBOICE
II. Description
It is the count of outgoing international calls barred by subscribers.
IV. Formula
None
7.2.74 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.
7-30
IV. Formula
None
7.2.75 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
7.2.76 Count of Carrier Barring of All Incoming Calls
I. Entity Name
ODBAIC
II. Description
It is the count of all incoming calls barred by operators.
IV. Formula
None
7.2.77 Count of Carrier Barring of Entertainment Consoles
I. Entity Name
ODBEC
7-31
II. Description
It is the count of messages indicating that the operators bar the entertainment
consoles.
IV. Formula
None
7.2.78 Count of Carrier Barring of Consoles
I. Entity Name
ODBMC
II. Description
It is the count of messages indicating that the operators bar the announcement
consoles.
IV. Formula
None
7.2.79 Count of Subscribers Out of Service Area
I. Entity Name
SROP
II. Description
It is the count of calls failed because subscribers not in the service area.
IV. Formula
None
7-32
7.2.80 Count of Carrier Barring of National Toll
I. Entity Name
ODBT
II. Description
It is the count of national toll calls barred by operators.
IV. Formula
None
7.2.81 Count of Call Failures Because of Unknown Reason
I. Entity Name
UN
II. Description
It is the count of failed calls due to unknown causes.
IV. Formula
None
7.2.82 Count of Unallocated Numbers
I. Entity Name
UALCCD
II. Description
It is the count of unallocated numbers due to the following reasons:

z The route selection source code or the route selection code is empty.
z The bsn of the circuit in the table is empty.
z The called number analysis fails according to the data configuration table.
z The MAP fails to return the called number to the calling module.
z The calling module fails to obtain the MSISDN or IMSI in the caller data.
z The MSC receives the UNN message from the TUP of the callee side.
7-33
IV. Formula
None
7.2.83 Count of No Routes to 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 sends the cause value because 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
7.2.84 Count of No Routes 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.
IV. Formula
None
7-34
7.2.85 Count of Sending Special Signal Tones
I. Entity Name
SPRVTONE
II. Description
It is the count of private tones sent due to peer office congestions.
IV. Formula
None
7.2.86 Count of Dialing Wrong Toll Prefix
I. Entity Name
ERLNGPFX
II. Description
It is the count of faulty prefixes of the called numbers.
IV. Formula
None
7.2.87 Count of Unaccepted Paths
I. Entity Name
RUUAPT
II. Description
It is the count of calls rejected due to unacceptable paths.
IV. Formula
None
7-35
7.2.88 Count of Calls Established and Delivered on Path Established
I. Entity Name
CALLEST
II. Description
It is the count of calls connected and delivered on the established paths.
IV. Formula
None
7.2.89 Count of Call Barring Decided by Carrier
I. Entity Name
ODB
II. Description
It is the count of calls barred by operators.
IV. Formula
None
7.2.90 Count of Circuits Reserved for Reuse
I. Entity Name
RFREUSE
II. Description
It is the count of circuits reserved for reusing.
IV. Formula
None
7-36
7.2.91 Count of Normal Cleared Calls
I. Entity Name
NORCLR
II. Description
It is the count of normally cleared calls.
IV. Formula
None
I. Entity Name
UDB
II. Description
It is the count of calls failed because callees are busy.
IV. Formula
None
7.2.93 Count of No Responses from Callee
I. Entity Name
NRSP
II. Description
It is the count of messages indicating the calls long time no reply.
IV. Formula
None
7-37
7.2.94 Count of No Answer from Callee
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
I. Entity Name
AS
II. Description
It is the count of calls failed because callees are absent.
IV. Formula
None
7.2.96 Count of Call Rejected
I. Entity Name
REJ
II. Description
It is the count of rejected calls.
IV. Formula
None
7-38
7.2.97 Count of Called Numbers Changed
I. Entity Name
CDCHD
II. Description
It is the count of invalid numbers due to changes of called numbers.
IV. Formula
None
7.2.98 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
7.2.99 Count of RAB Resources Pre-Used
I. Entity Name
RABPE
II. Description
It is the count of calls released due to RAB resources seizure conflicts.
IV. Formula
None
7-39
7.2.100 Count of Destination Fault
I. Entity Name
TEER
II. Description
It is the count of calls of which the callees are abnormal.
IV. Formula
None
7.2.101 Count of Invalid Number Format
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
7.2.102 Count of Facility Rejected
I. Entity Name
FACREJ
II. Description
It is the count of facilities rejected.
IV. Formula
None
7-40
7.2.103 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
7.2.104 Count of Normal Cleared Calls
I. Entity Name
NOR
II. Description
IV. Formula
None
7.2.105 Count of No Available Circuits
I. Entity Name
NCIR
II. Description
It is the count of unavailable circuits. The circuits may be unavailable in:

z querying the TUP circuits;
z allocating the territorial circuits after the switch;
z allocating the territorial circuits;
z indication empty of the internal HW networks;
z receiving the CGC message.
7-41
IV. Formula
None
7.2.106 Count of Network Failures
I. Entity Name
NETER
II. Description
It is the count of CC internal processing failures.
IV. Formula
None
I. Entity Name
TMPER
II. Description
It is the count of internal failures.
IV. Formula
None
7.2.108 Count of Switch Congestions
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.
7-42
IV. Formula
None
7.2.109 Count of Access Information Lost
I. Entity Name
AIL
II. Description
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
7.2.110 Count of Circuits Unavailable
I. Entity Name
NRUCIR
II. Description
It is the count of failures in querying or allocating trunk resources.
IV. Formula
None
7.2.111 Count of Prior Calls Blocked
I. Entity Name
PCALLBLK
7-43
II. Description
It is the count of unavailable paths.
IV. Formula
None
7.2.112 Count of No Available 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
7.2.113 Count of No Suitable Service Quality
I. Entity Name
NSSQUA
II. Description
This cause value reports the service quality defined in the X.213 cannot be provided
(for example, throughput and transfer delay).
IV. Formula
None
7-44
7.2.114 Count of Required Facility Not Booked
I. Entity Name
FACNPV
II. Description
It is the count of no suitable services or optional projects.
IV. Formula
None
7.2.115 Count of CUG Barring Out-Group Calls
I. Entity Name
CUGBC
II. Description
It is the count of calls barred due to CUG call-out restrictions.
IV. Formula
None
7.2.116 Count of CUG Incoming Calls Not Allowed
I. Entity Name
CUGUALW
II. Description
It is the count of CUG incoming calls barred due to CUG call-in restrictions.
IV. Formula
None
7-45
7.2.117 Count of Bearer Capability Not Registered
I. Entity Name
BCUNP
II. Description
It is the count of calls released due to no bearer services registered.
IV. Formula
None
7.2.118 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
7.2.119 Count of No Suitable Services or Optional Projects
I. Entity Name
NSSOOP
II. Description
IV. Formula
None
7-46
7.2.120 Count of Bearer Capability Not Carried Out
I. Entity Name
BCNLO
II. Description
It is the count of calls released due to no bearer services implemented.
IV. Formula
None
7.2.121 Count of Route Type Not Supported
I. Entity Name
RTNLO
II. Description
It is the count of calls with the path type that is not implemented. In this case, the
equipment sends this cause value.
IV. Formula
None
7.2.122 Count of AOC Service Request Failures
I. Entity Name
AOCRF
II. Description
It is the count of AOC service request failures.
IV. Formula
None
7-47
7.2.123 Count of ACMs Greater or Equal to ACMmax
I. Entity Name
ACMEG
II. Description
It is the count of ACMs equaling or greater than the ACM max.
IV. Formula
None
7.2.124 Count of Requested Facility Not Supported
I. Entity Name
FACNLO
II. Description
It is the count of requested equipment that is not implemented.
IV. Formula
None
7.2.125 Count of Only Having 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.
7-48
IV. Formula
None
7.2.126 Count of IWF Resources Unavailable
I. Entity Name
IWFRU
II. Description
It is the count of unavailable IWF resources.
IV. Formula
None
7.2.127 Count of Services or Optional Projects Not Supported
I. Entity Name
SOPNLO
II. Description
IV. Formula
None
7.2.128 Count of Invalid Call Reference
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.
7-49
IV. Formula
None
7.2.129 Count of Identified Paths Do Not Exist
I. Entity Name
RUNEXT
II. Description
It is the count of identified routes that do not exist.
IV. Formula
None
7.2.130 Count of Callees Not in CUG
I. Entity Name
CLDNOCUG
II. Description
It is the count of messages indicating the callees are not CUG subscribers.
IV. Formula
None
7.2.131 Count of Incompatible Destinations
I. Entity Name
TEUCPT
II. Description
The caller bearer capability specifies the non-voice service, but the callee does not
support the ISUP interface or other interfaces those support the data services. The
TUP supports non-restricted services if the ACB (access barred) is not received.
7-50
IV. Formula
None
7.2.132 Count of Non-Existent CUGs
I. Entity Name
NECUG
II. Description
It is the count of supplementary service failures due to non-existent CUG.
IV. Formula
None
7.2.133 Count of Invalid Transit Network Selections
I. Entity Name
INVTNL
II. Description
The received transit network identifier is not the correct format as defined in the
Appendix C.
IV. Formula
None
7.2.134 Count of Invalid Messages
I. Entity Name
INVMSG
II. Description
It is the count of invalid messages.
7-51
IV. Formula
None
7.2.135 Count of Non-Existent or Not Supported Message Types
I. Entity Name
MSGNOEXT
II. Description
It is the count of non-existent or not implemented message types.
IV. Formula
None
7.2.136 Count of Non-Existent or Not Supported Information Elements
I. Entity Name
IENOEXT
II. Description
It is the count of non-existent or not implemented message units.
IV. Formula
None
7.2.137 Count of Recoveries of Timer Timeout
I. Entity Name
TOUT
II. Description
It is the count of timeout recoveries of timers.
7-52
IV. Formula
None
7.2.138 Count of Non-Existent or Not Invoked Parameters
I. Entity Name
PARANOEXT
II. Description
It is the count of non-existent or not implemented parameters.
IV. Formula
None
7.2.139 Count of Messages with Unrecognized Parameters
I. Entity Name
UNRECPARA
II. Description
It is the count of messages carrying the unidentified parameters.
IV. Formula
None
7.2.140 Count of Protocol Errors
I. Entity Name
PROERR
II. Description
It is the count of protocol errors.
7-53
IV. Formula
None
7.2.141 Count of Interworking
I. Entity Name
INTWORK
II. Description
Interworking.
IV. Formula
None
7.3 Traffic Distribution and Duration

This unit only measures the call attempts after ringing. The call attempts without ringing
cannot be measured here.
The names and the meanings are listed in the following table.
Name Description
CSINLET Count of call source inlet information
CSOUTLET Count of call source outlet information
CLRNUM Count of caller number
CLDNUM Count of dialed number

CLRSETUP Count of caller service request time
CLDSETUP Count of callee service setup time
ALTTIME Count of ringing time

ANSTIME Count of answer time
RELTIME Count of release time
7-54
7.3.2 Count of Call Source Inlet Information
I. Entity Name
CSINLET
II. Description
It is the count of messages indicating the call source inlet module numbers and office
direction information.
It is measured when the IAM or CM requires the services.
IV. Formula
None
7.3.3 Count of Call Source Outlet Information
I. Entity Name
CSOUTLET
II. Description
It is the count of messages indicating the call source outlet module numbers and office
direction information.
It is measured when the MSC sends the SETUP message to the trunk or CM.
IV. Formula
None
7.3.4 Count of Caller Numbers
I. Entity Name
CLRNUM
II. Description
It is the count of called numbers.
If the callee is in another office, it is measured when the MSC receives the ACM from
the callee side. If the callee is a local MS, it is measured when the MSC receives the
7-55
ALERTING message from the callee side. 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.
ACM
RNC/BSC
DTAP ALERTING
IV. Formula
None
7.3.5 Count of Dialed Numbers
I. Entity Name
CLDNUM
II. Description
It is the count of dialed numbers dialed by callers.
If the callee is in another office, it is measured when the MSC receives the ACM from
the callee side. If the callee is a local MS, it is measured when the MSC receives the
ALERTING message from the callee side. 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.
7-56
ACM
RNC/BSC
DTAP ALERTING
IV. Formula
None
7.3.6 Caller Service Request Time
I. Entity Name
CLRSETUP
II. Description
It is the time for the IAM or CM at the trunk side requesting services.
It is measured when the IAM or CM requires the services.
IV. Formula
None
7.3.7 Callee Service Setup Time
I. Entity Name
CLDSETUP
II. Description
It is the time for sending the SETUP message to the trunk or CM.
7-57
It is measured when the MSC sends the SETUP message to the trunk or CM.
IV. Formula
None
7.3.8 Ringing Time
I. Entity Name
ALTTIME
II. Description
It is the time for the calling ISUP or CM sending the ALERTING message.
It is measured when the ISUP or CM sends the ALERTING message to the caller.
IV. Formula
None
7.3.9 Answer Time
I. Entity Name
ANSTIME
II. Description
It is the time for the calling ISUP or CM sending the answer message.
It is measured when the ISUP or CM sends the answer message to the caller.
IV. Formula
None
7.3.10 Release Time
I. Entity Name
RELTIME
II. Description
It is the time for the calling ISUP or CM sending the Release message.
7-58
It is measured when the ISUP or CM sends the Release message to the caller.
IV. Formula
None
7-59
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 8 Total Traffic of the Office
Chapter 8 Total Traffic of the Office

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-1
8.2 MS-Originated Outgoing Traffic

8.2.1 Overview of MS_OFFICE_2G_ORGOUT_TRAF
Name Description
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
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
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.
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-2
BSC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C 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.
z It is measured when the MSC receives the ADI or UNN message (TUP signaling).
8-3
RNC MSC Server MSC Server
DTAP SETUP
IAM
ACM
REL
B
RLC
z 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.
DTAP SETUP
IAM
ACM
REL
B
RLC
z 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-4
DTAP SETUP
IAM
ACM
REL
B
RLC
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-5
RNC/BSC
DTAP SETUP
DTAP IAM
Disconnect
A REL
RLC
ACM
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.
BSC
DTAP SETUP
IAM
DTAP Disconnect
REL
A
ACM
IV. Formula
None
8-6
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
BSC
DTAP SETUP
IAM
DTAP Disconnect
REL
A
ACM
IV. Formula
None
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
8-7
BSC
DTAP SETUP
A
IAM
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:

z After sending the IAM, the MSC releases the call due to no response from the peer
office in a valid period.
z The callee line is faulty.
z The call connection fails.
z The circuit group of the peer office is congested.
z The switch of the peer office is congested.
8-8
BSC
DTAP SETUP
IAM
ACM
DTAP Disconnect
A
IV. Formula
None
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-9
BSC
DTAP SETUP
IAM
ACM
DTAP REL
Disconnect
A
RLC
IV. Formula
None
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-10
BSC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-11
BSC
DTAP SETUP
IAM
ACM
DTAP ALERTING
DTAP
Disconnect A
REL
ANM/ANC
IV. Formula
None
I. Entity Name
RNA10
II. Description
It is the count of outgoing calls that are released because the callees do not answer till
timeout.
z 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-12
BSC
DTAP SETUP
IAM
DTAP ALERTING ACM
REL
A
RLC
ANM/ANC
z 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
DTAP SETUP
IAM
DTAP ALERTING ACM
REL
A
RLC
ANM/ANC
IV. Formula
None
I. Entity Name
ANS10
II. Description
It is the count of outgoing calls answered.
8-13
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
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
IV. Formula
None
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-14
BSC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-15
BSC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-16
BSC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
IV. Formula
None
I. Entity Name
ALTR10
II. Description
Answer rate = Count of connected calls/Count of call attempts
IV. Formula
ALTR10 = ALT10/CA10
8.2.18 Answer Rate
I. Entity Name
ANSR10
II. Description
8-17
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
II. Description
It is the count of call attempts originated by the MSs in the local MSC, regardless of the
terminating MSCs.
8-18
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.
z 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.
z 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.
IV. Formula
None
8-19
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.
O_MS MSC Server VLR
SETUP
ObtainSubscriberParaOutgoingCall
RELEASE
RELEASE COMPLETE A
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-20
O_BSS MSC Server MGW
SETUP
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-21
O_BSS MSC Server
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.
z The MSC fails to analyze the called number because the number is incomplete
and cannot be determined.
z After confirming that the called number is MSISDN, the MSC fails to obtain the
routing information from the HLR. The callee location is unknown.
z 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.

z The MSC fails to analyze the called number and the destination is unknown.
z The MSC receives the Routing Failure message from the MAP.
z 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-22
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
SETUP
/ RELEASE COMPLETE
A
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-23
O_BSS MSC Server MGW
SETUP
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-24
O_MS MSC Server
SETUP
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-25
O_UE MSC Server
ACM
ALERTING
A ANM
CONNECT
B
CONNECT ACK
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-26
O_UE MSC Server
ACM
ALERTING
A ANM
CONNECT
B
CONNECT ACK
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-27
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.3.18 Answer Rate
I. Entity Name
ANR3
8-28
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

MBTO14 Count of mobile callee trunk resource overflow
MAF14 Count of mobile callee traffic channel allocations failures
8-29
Name Description
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-30
MSC Server MSC Server BSC
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-31
IAM
DTAP SETUP
REL A
DTAP ALERTING
IV. Formula
None
I. Entity Name
TAF14
II. Description
8-32
IAM
DTAP SETUP
REL A
DTAP Disconnect
DTAP ALERTING
IV. Formula
None
I. Entity Name
CRU14
II. Description
8-33
IAM
DTAP SETUP
REL A
DTAP Disconnect
DTAP ALERTING
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-34
IAM
When the MSC obtains the

MSRN, and the VLR returns a
message indicating callee busy.
A
DTAP SETUP
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-35
IAM
DTAP SETUP
A interface circuits
allocation failure
A
A
DTAP ALERTING
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-36
IAM
DTAP SETUP
Called traffic channels

allocation failure
A
A
DTAP ALERTING
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-37
DTAP SETUP
DTAP PAGING
Mobile subscriber
unreachable
A
A
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-38
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-39
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
REL
A
DTAP CONNECT
IV. Formula
None
I. Entity Name
RNA14
II. Description
timeout.
z 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-40
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
A
DTAP CONNECT
z 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.
IAM
DTAP PAGING_RSP
DTAP SETUP
ACM DTAP ALERTING
DTAP CONNECT
ANM/ANC
DTAP DISCONNECT
A
IV. Formula
None
8.4.13 Count of Mobile Callee Determined Busy
I. Entity Name
MDB14
8-41
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.
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
A
DTAP CONNECT
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-42
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-43
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-44
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-45
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
IV. Formula
None
I. Entity Name
ALTR14
II. Description
IV. Formula
ALTR14 = ALT14/CA14
8.4.19 Answer Rate
I. Entity Name
ANSR14
II. Description
8-46
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-47
II. Description
It is the count of call attempts in which the callees are local MSs.
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.
XXX MSC Server BSC
Incoming IAM or local SETUP

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
ANM / DTAP CONNECT C
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
8-48
XXX MSC Server BSC
REL / DTAP DISCONNECT
DTAP DISCONNECT
DTAP ALERTING
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-49
XXX MSC Server BSC
DTAP DISCONNECT
DTAP ALERTING
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-50
XXX MSC Server BSC
The MSC obtains the MSRN, and

the VLR returns a message
indicating callee busy.
A
DTAP SETUP
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-51
XXX MSC Server BSC
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-52
XXX MSC Server BSC
DTAP SETUP

allocation failure
A
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-53
XXX MSC Server BSC
DTAP PAGING
Mobile subscriber
unreachable
A
DTAP PAGING_RSP
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-54
XXX MSC Server BSC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-55
XXX MSC Server BSC

DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
A
RLC / DTAP RELEASE
DTAP CONNECT
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-56
XXX MSC Server BSC

DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
Long time no reply
DTAP DISCONNECT
A
DTAP RELEASE
DTAP CONNECT
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-57
XXX MSC Server BSC

DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
DTAP DISCONNECT(CV_BUSY/
CV_USR_BUSY)
A
DTAP RELEASE
DTAP CONNECT
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-58
XXX MSC Server BSC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-59
XXX MSC Server BSC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-60
XXX MSC Server BSC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-61
XXX MSC Server BSC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-62
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-63
O_UE MSC Server VLR
SETUP
CALL PROCEEDING SubscriberPara
ALERTING A
B
CONNECT
C
CONNECT ACK
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
8-64
O_UE MSC Server VLR
SETUP
ALERTING A
B
CONNECT
C
CONNECT ACK
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-65
O_UE MSC Server VLR
SETUP
ALERTING A
B
CONNECT
C
CONNECT ACK
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.
O_UE MSC Server VLR
SETUP
RELEASE
IV. Formula
None
8-66
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-67
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-68
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-69
T_UE MSC Server
SETUP
CALL CONFIRMED
ALERTING A
B
CONNECT
CONNECT ACK
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-70
T_UE MSC Server
SETUP
CALL CONFIRMED
ALERTING A
B
CONNECT
CONNECT ACK
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-71
T_UE MSC Server
SETUP
CALL CONFIRMED
ALERTING A
B
CONNECT
CONNECT ACK
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.
T_UE MSC Server VLR/O_UE
PAGE RESPONSE
RELEASE
IV. Formula
None
8-72
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-73
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-74
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-75
RNC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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.
z It is measured when the MSC receives the ADI or UNN message (TUP). See point
8-76
RNC
DTAP SETUP
IAM
REL
A
RLC
ACM
z 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
DTAP SETUP
IAM
REL
A
RLC
ACM
z 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-77
RNC
DTAP SETUP
IAM
REL
A
RLC
ACM
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-78
RNC
DTAP SETUP
DTAP IAM
Disconnect
A REL
RLC
ACM
IV. Formula
None
I. Entity Name
TAF11
II. Description
8-79
RNC
DTAP SETUP
IAM
DTAP Disconnect
REL
A
ACM
IV. Formula
None
I. Entity Name
CRU11
II. Description
8-80
RNC
DTAP SETUP
IAM
DTAP Disconnect
REL
A
ACM
IV. Formula
None
8.8.7 Count of Outgoing Trunk Overflow
I. Entity Name
TO11
II. Description
calls.
8-81
RNC
DTAP SETUP
Outgoing trunk
overflow
A
IAM
IV. Formula
None
I. Entity Name
EC11
II. Description
situation.

z The peer office is congested.
8-82
RNC
DTAP SETUP
IAM
ACM
DTAP Disconnect
A
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-83
RNC
DTAP SETUP
IAM
ACM
REL
DTAP Disconnect
A
RLC
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-84
RNC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-85
RNC
DTAP SETUP
IAM
ACM
DTAP ALERTING
DTAP Disconnect
A REL
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-86
RNC
DTAP SETUP
IAM
DTAP ALERTING ACM
REL
A
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
DTAP SETUP
IAM
DTAP ALERTING ACM
REL
A
RLC
ANM/ANC
IV. Formula
None
I. Entity Name
ANS11
II. Description
8-87
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
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-88
RNC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-89
RNC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-90
RNC
DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
DTAP CONNECT
DTAP Connect Ack

REL C REL
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-91
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-92
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-93
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.
O_UE MSC Server VLR
SETUP
RELEASE
RELEASE COMPLETE A
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-94
O_RNC MSC Server MGW
SETUP
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-95
O_RNC MSC Server
IV. Formula
None
I. Entity Name
WDN4
II. Description
It is the count of wrong numbers dialed by UEs, including the following three cases.
z The MSC fails to analyze the called number because the number is incomplete
and cannot be determined.
z After confirming that the called number is MSISDN, the MSC fails to obtain the
routing information from the HLR. The callee location is unknown.
z 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.

z The MSC fails to analyze the called number and the destination is unknown.
z The MSC receives the Routing Failure message from the MAP.
z The MSC receives the ADI, UNN (TUP) or REL (ISUP) message from the
terminating office in an outgoing call.
IV. Formula
None
8-96
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
SETUP
/ RELEASE COMPLETE
A
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-97
O_RNC MSC Server MGW
SETUP
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-98
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.
O_UE MSC Server
ACM
ALERTING
A ANM
CONNECT
B
CONNECT ACK
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-99
O_UE MSC Server
ACM
ALERTING
A ANM
CONNECT
B
CONNECT ACK
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-100
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
IV. Formula
AR4 = ALT4/CA4
8-101
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-102
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-103
MSC Server MSC Server RNC
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC
c
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-104
IAM
DTAP SETUP
REL A
DTAP ALERTING
IV. Formula
None
I. Entity Name
TAF15
II. Description
8-105
IAM
DTAP SETUP
REL A
DTAP Disconnect
DTAP ALERTING
IV. Formula
None
I. Entity Name
CRU15
II. Description
8-106
IAM
DTAP SETUP
REL A
DTAP Disconnect
DTAP ALERTING
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-107
IAM
The MSC obtains the MSRN,

and the VLR returns a message
DTAP SETUP
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-108
IAM
DTAP SETUP

allocation failure
A
A
DTAP
ALERTING
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-109
DTAP SETUP
DTAP PAGING
Mobile subscriber
unreachable
A
A
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-110
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-111
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
REL
A
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
8-112
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
A
DTAP CONNECT
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
IAM
DTAP PAGING_RSP
DTAP SETUP
ACM DTAP ALERTING
DTAP CONNECT
ANM/ANC
DTAP DISCONNECT
A
IV. Formula
None
I. Entity Name
MDB15
8-113
II. Description
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
A
DTAP CONNECT
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-114
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-115
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-116
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-117
IAM
DTAP SETUP
A
DTAP ALERTING
ACM B
DTAP CONNECT
ANM/ANC c
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-118
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-119
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
XXX MSC Server RNC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-120
XXX MSC Server RNC
DTAP DISCONNECT
DTAP ALERTING
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-121
XXX MSC Server RNC
DTAP DISCONNECT
DTAP ALERTING
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-122
XXX MSC Server RNC
The MSC obtains the MSRN,

and the VLR returns a message
A
DTAP SETUP
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-123
XXX MSC Server RNC
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
8-124
XXX MSC Server RNC
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-125
XXX MSC Server RNC
DTAP PAGING
Mobile subscriber
unreachable
A
DTAP PAGING_RSP
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-126
XXX MSC Server RNC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-127
XXX MSC Server RNC

DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
A
RLC / DTAP RELEASE
DTAP CONNECT
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-128
XXX MSC Server RNC

DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
Long time no reply
DTAP DISCONNECT
A
DTAP RELEASE
DTAP CONNECT
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-129
XXX MSC Server RNC
DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
CV_USR_BUSY)
A
DTAP RELEASE
DTAP CONNECT
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-130
XXX MSC Server RNC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-131
XXX MSC Server RNC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-132
XXX MSC Server RNC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-133
XXX MSC Server RNC

DTAP PAGING
DTAP PAGING_RSP
A
DTAP SETUP
DTAP ALERTING
B
ACM / DTAP ALERTING
DTAP CONNECT
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-134
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
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
CTB Count of callee busy in toll calls
CLB Count of callee busy in local calls
RERL Answered traffic
MNTCIR Count of blocked circuits
ANSR Answer rate
CATS Count of call attempts
Count of failed call attempts due to common resource
CRFS
application failure
PCFS Count of failed call attempts due to peer office congestion

ATTR Connected traffic
RADI Count of incomplete addresses received
8-135
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.
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
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-136
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.
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
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-137
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
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-138
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
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:
z CV_NO_ACKNOWLEGE
8-139
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
2) Not answered calls (case 2)

The cause value of the REL message might be one of the following:
z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
IV. Formula
None
8-140
I. Entity Name
BRGABN
II. Description
Before receiving the ACM, the MSC sends the CLF or REL message.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
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-141
1) Call failures due to overload (case 1)

The cause value of the REL message is CV_CPU_OVERLAP.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release
A
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release
A
REL

8-142
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Connect ANM
Connect
ANM Release
A
REL
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-143
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release
A
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release
A
REL

8-144
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Connect ANM
Connect
ANM Release
A
REL
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-145
Outgoing trunk
overflow
A IAM
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.
The cause value of the REL message is CV_BUSY.
8-146
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

The cause value of the REL message is CV_BUSY.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
8.12.12 Count of Callee Busy in Toll Calls
I. Entity Name
CTB
8-147
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-148
IAM
REL
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-149
IAM
ANM
REL
A
REL
IV. Formula
None
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-150
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-151
IAM
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-152
IAM
ACM
REL
RLC
IV. Formula
None
8.12.21 Count of Failed Call Attempts Due to Peer Office Congestion
I. Entity Name
PCFS
II. Description
situation.

z Long time no reply.
z Called line faulty.
z Call connection failure.
z Peer office circuit group congestion.
z Dedicated signal tone sending failure.
z Peer office congestion. See point A in the following figure.
The cause value of the REL message may be one of the following:
8-153
1) Call failure due to peer office congestion (case 1)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
8-154
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.
IAM
ACM
REL
B
C
REL
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.
8-155
1) Call failure due to incomplete number (case 1)

The cause value of the REL message is
CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOUGH.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

The cause value of the REL message is
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL

The value of the Release message is
8-156
IAM
Setup
Setup
Setup Ack
Setup Ack
REL
Release IAM
Release
A
REL

The value of the Release message is
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
Release
Release
A
REL
IV. Formula
None
8-157
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-158
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.
XXX MSC Server MSC Server

A
IAM
ACM
B
ANM/ANC/ANN
RNC/BSC
C
D DTAP SETUP
DTAP ALERTING
E
DTAP CONNECT
F
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-159

A
IAM
ACM
B
ANM/ANC/ANN
RNC/BSC
C
D DTAP SETUP
DTAP ALERTING
E
DTAP CONNECT
F
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-160

A
IAM
ACM
B
ANM/ANC/ANN
RNC/BSC
C
D DTAP SETUP
DTAP ALERTING
E
DTAP CONNECT
F
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-161
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.

Incoming REL or local DTAP DISCONNECT
RNC/BSC
ACM
B
DTAP ALERTING
IV. Formula
None
I. Entity Name
LRUOFL
II. Description
calls.
8-162
Outgoing trunk overflow
A
IAM
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-163

IAM
REL
A
ACM RNC/BSC
MT busy
DTAP ALERTING
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-164

IAM
ACM
A RNC/BSC
ANM

DTAP SETUP
DTAP ALERTING
DTAP CONNECT
IV. Formula
None
I. Entity Name
LTNANS
II. Description
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-165

IAM
ACM
ACM / DTAP ALERTING
REL
RNC/BSC
A
ANM

DTAP SETUP
DTAP ALERTING
ACM / DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
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-166

A
IAM
ACM
B
ANM/ANC/ANN
RNC/BSC
C
D DTAP SETUP
DTAP ALERTING
E
DTAP CONNECT
F
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-167

A
IAM
ACM
B
ANM/ANC/ANN
RNC/BSC
C
D DTAP SETUP
DTAP ALERTING
E
DTAP CONNECT
F
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-168
A
IAM
ACM
B
ANM/ANC/ANN
RNC/BSC
C
D DTAP SETUP
DTAP ALERTING
E
DTAP CONNECT
F
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-169
IV. Formula
ANSR = ANS/PEGS
I. Entity Name
CEUR
II. Description
call. See point A in the following figure.
XXX MSC Server RNC/BSC

DTAP PAGING
Mobile subscriber
unreachable
A
DTAP PAGING_RSP
IV. Formula
None
8.13.17 Count of Failed Call Attempts Due to Inter-Trunk Failure
I. Entity Name
CFITB
8-170
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.
Outgoing trunk
overflow
A
IAM
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,
the measurement begins. It is measured only when the MS accesses from the interface
A. See point A in the following figure.
8-171
XXX MSC Server BSC

DTAP SETUP
BSS trunk busy
DTAP ALERTING
IV. Formula
None
I. Entity Name
CFPOB
II. Description
situation.

z The sending of the dedicated signal tone fails.
z The peer office is congested.
8-172
IAM
REL
A
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
8-173

IAM
ACM
DTAP ALERTING / ACM
REL(CV_ST_BUSY/CV_SL_BUSY/CV_BUSY)
RNC/BSC
A
ANM/ANC
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING / ACM
DTAP DISCONNECT(CV_BUSY)
B
DTAP CONNECT
IV. Formula
None
8.14 Intra-Office Traffic

8.14.1 Overview of MS_OFFICE_INT_MTM_TRAF
Name Description



8-174
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-175
DTAP SETUP
A
DTAP SETUP
DTAP ALERTING
B
DTAP ALERTING
DTAP CONNECT
C
DTAP CONNECT
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-176
DTAP SETUP
DTAP DISCONNECT
A
DTAP RELEASE
DTAP ALERTING
IV. Formula
None
I. Entity Name
TAF7
II. Description
8-177
DTAP SETUP
DTAP DISCONNECT
A
DTAP DISCONNECT
DTAP ALERTING
IV. Formula
None
I. Entity Name
CRU7
II. Description
including the IWF, DTR, bill pool, control table, and announcement resources.
8-178
DTAP SETUP
DTAP DISCONNECT
A
DTAP DISCONNECT
DTAP ALERTING
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-179
DTAP SETUP
The MSC obtains the MSRN, and

the VLR returns a message
A
DTAP SETUP
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-180
RNC/BSC MSC Server 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-181
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-182
DTAP SETUP
DTAP PAGING
Mobile subscriber
unreachable
A
DTAP PAGING_RSP
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-183
DTAP SETUP
A
DTAP SETUP
DTAP ALERTING
B
DTAP ALERTING
DTAP CONNECT
C
DTAP CONNECT
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-184
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
A
DTAP RELEASE
DTAP CONNECT
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-185
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
Long time no reply
DTAP DISCONNECT
A
DTAP RELEASE
DTAP CONNECT
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-186
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
CV_USR_BUSY)
A
DTAP RELEASE
DTAP CONNECT
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-187
DTAP SETUP
A
DTAP SETUP
DTAP ALERTING
B
DTAP ALERTING
DTAP CONNECT
C
DTAP CONNECT
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-188
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.

z 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.
z 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-189
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.

z 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.
z 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-190
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-191
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.
MS, see point D in the following figure.
8-192
A IAM
ACM
B
ANM/ANC
RNC/BSC
C
D SETUP
DTAP ALERTING
E DTAP CONNECT
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-193
A IAM
ACM
B
ANM/ANC
RNC/BSC
C
D SETUP
DTAP ALERTING
E DTAP CONNECT
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-194
A IAM
ACM
B
ANM/ANC
RNC/BSC
C
D SETUP
DTAP ALERTING
E DTAP CONNECT
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).
MS, see point D in the following figure.
8-195
A IAM
ACM
B
ANM/ANC
RNC/BSC
C
D SETUP
DTAP ALERTING
E DTAP CONNECT
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-196
A IAM
ACM
B
ANM/ANC
RNC/BSC
C
D SETUP
DTAP ALERTING
E DTAP CONNECT
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-197
A IAM
ACM
B
ANM/ANC
RNC/BSC
C
D SETUP
DTAP ALERTING
E DTAP CONNECT
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.
z The HLR sends CANCEL_LOCATION message to the previous VLR (PVLR).
z The PVLR deletes the subscriber who has moved into another location area.
8-198
z The PVLR checks the office of the forwarded-to number in the service subscription
information and updates the subscriber data.
See point B.
z The HLR sends the INSERT_SUBSCRIBER_DATA message to the VLR.
z The VLR checks the destination of the forwarded-to number in the service
subscription information and updates the subscriber data.
See point C.
MSC VLR PVLR HLR
MAP-UPDATE-LOCATION-
AREA
MAP-PROVIDE-IMSI
MAP-PROVIDE-IMSI-ACK
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
MAP-CANCEL-LOCTION-ACK
MAP-VDB-INSERT-SUBSCRIVER-DATA
C
MAP-VDB-INSERT-SUBSCRIVER-DATA-ACK
MAP-UPDATE-LOCATION-ACK
AREA-ACK
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.
z For removing the subscriber, the HLR sends the CANCEL_LOCATION message
to the current VLR.
z The VLR deletes the subscriber moved into another location area.
z 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-199
VLR HLR OMC
Delete subscriber
MAP-CANCEL-LOCTION
A
Subscriber deleted
z 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.
z The VLR updates the subscriber data of supplementary services.
z The VLR checks the destination of the forwarded number in the service
subscription information of the subscriber data and updates the subscriber data.
VLR HLR OMC
Modify user data

MAP-INSERT-SUB-DATA or
MAP-DELETE-SUB-DATA
B
MAP-INSERT-SUB-DATA-ACK or Subscriber data
MAP-DELETE-SUB-DATA-ACK modified
3) The procedures of functionalizing the supplementary services concerns one

measurement point. See point A in the following figure.
z When the MS initiates a supplementary service data operation, the HLR initiates a
flow of inserting subscriber data to the current VLR.
z The VLR compares the supplementary service subscription information in local
VLR with that in the message.
z 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-200
MSC VLR HLR
MAP-REG / ERASE / ACT /

DEA-SS MAP-REG / ERASE / ACT /
DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
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.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
8-201
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

SEFL2 Count of local calls to busy callee
8-202
Name Description
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
CDUR Count of callee unreachable
8-203
Name Description
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
AS Count of callee absent
8-204
Name Description
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
SOPNLO Count of service or optional project not implemented
8-205
Name Description
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.
IV. Formula
None
8.17.3 Count of Supplementary Service Setting Successes
I. Entity Name
NSSETOK
II. Description
It is the count of successful settings of the supplementary services
8-206
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
II. Description
It is the count of deregistration failures of supplementary services.
8-207
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
II. Description
It is the count of successful application of supplementary services.
8-208
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
II. Description
It is the count of failures in probing malicious calls.
8-209
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
II. Description
8-210
IV. Formula
None
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.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.
8-211
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.
IV. Formula
None
8.17.21 Count of Inband Signals
I. Entity Name
INBSIG
8-212
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.
IV. Formula
None
I. Entity Name
BRGABN
8-213
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.
IV. Formula
None
8.17.27 Count of MSC Failures
I. Entity Name
SEFL
8-214
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.
IV. Formula
None
8.17.30 Count of Peer Office Congestion
I. Entity Name
REPMCG
8-215
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:

z The peer office is congested and the MSC cannot obtain the addressing message
after receiving the SETUP message.
z The peer office DSP is unavailable and the TUP releases the call due to timeout.
z The called number is less than that requested when the MSC receives the IAM.
z The MSC receives the RLG message abnormally.
z The channel is blocked due to TUP circuit busy.
z The circuit group is blocked.
z The internal timer is timeout when the TUP is in the ringing state.
z The MSC fails to receive the GSM message.
z The TUP fails to receive the SETUP message.
z The CFL message is received.
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.
8-216
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.
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.
8-217
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.
IV. Formula
None
8.17.38 Count of Incoming Office CF Barring
I. Entity Name
IFCR
8-218
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.
IV. Formula
None
8.17.41 Count of Black List Calls Barred
I. Entity Name
BWLBAR
8-219
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.
IV. Formula
None
8.17.44 Count of No A Interface Resources
I. Entity Name
NAC
8-220
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.
IV. Formula
None
8.17.47 Count of CUG Unselected
I. Entity Name
NSCUG
8-221
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.
IV. Formula
None
8.17.50 Count of CUG Supplementary Service Failures
I. Entity Name
CUGSSI
8-222
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
II. Description
It is the count of released calls.
IV. Formula
None
8.17.53 Count of Switchover Successes
I. Entity Name
HOC
8-223
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
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
8-224
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.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
8-225
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.
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-226
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.
IV. Formula
None
8.17.64 Count of Mobile Callee Power-Off
I. Entity Name
CDPO
II. Description
callees power-off.
8-227
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
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.
8-228
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.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.
8-229
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.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
8-230
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.
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-231
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.
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-232
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:

z The route selection source code or the route selection code is empty.
z The bsn of the circuit in the table is empty.
z The called number analysis fails according to the data configuration table.
z The MAP fails to return the called number to the calling module.
z The calling module fails to obtain the MSISDN or IMSI in the caller data.
z 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
8-233
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.
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-234
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.
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-235
8.17.87 Count of Calls Barred by Operators
I. Entity Name
ODB
II. Description
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.
IV. Formula
None
8.17.89 Count of Normally cleared Calls
I. Entity Name
NORCLR
II. Description
IV. Formula
None
8-236
I. Entity Name
UDB
II. Description
It is the count of calls failed because callees are busy.
IV. Formula
None
I. Entity Name
NRSP
II. Description
It is the count of calls not replied for a long time till timeout.
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-237
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.
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-238
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.
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-239
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
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-240
8.17.102 Count of Normally cleared Calls
I. Entity Name
NOR
II. Description
IV. Formula
None
8.17.103 Count of Unavailable Circuits
I. Entity Name
NCIR
II. Description
It is the count of unavailable circuits. The circuits may be unavailable in:

z querying the TUP circuits.
z allocating the territorial circuits after the switch.
z allocating the territorial circuits.
z indication empty of the internal HW networks.
z 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.
8-241
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.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
8-242
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.
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-243
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).
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.
8-244
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.
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.
8-245
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
II. Description
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.
8-246
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.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.
8-247
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.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.
8-248
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.
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.
8-249
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.
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
8-250
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
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
8-251
II. Description
It is the count of message types that do not exist or are not implemented.
IV. Formula
None
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
8-252
II. Description
It is the count of parameters that do not exist or are not implemented.
IV. Formula
None
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
8-253
II. Description
It is the count of interworking.
IV. Formula
None
8.18 Incoming Traffic

8.18.1 Overview of MS_OFFICE_INC_TRAF
Name Description
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
8-254
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.
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
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-255
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
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:
z The trunk does not send number.
z The number is discarded during the dialing.
z The interval of dialing is timeout.
z 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.
z CV_NORMAL
8-256
IAM
Setup
Setup
Setup Ack
Setup Ack
REL IAM

The cause value of the Release message may be one of the following.
z CV_LONG_TIME_NO_DIALING
z CV_PARTIAL_DIAL_TIMEOUT
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
A
REL

z CV_LONG_TIME_NO_DIALING
z CV_PARTIAL_DIAL_TIMEOUT
8-257
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release REL
Release
A
REL
IV. Formula
None
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)
z CV_NUMBER_CHANGED
z CV_DIAL_NO_RESERED
z CV_UNALOC_CODE
z CV_INVALID_CODE_FORM
z CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOUGH
z CV_ERROR_INCLUDE_LONG_DISTANCE
z CV_GSM_CLD_DN_NO_EXIST
8-258
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
A
REL
2) Invalid address (case 2)

z CV_NUMBER_CHANGED
z CV_DIAL_NO_RESERED
z CV_UNALOC_CODE
z CV_INVALID_CODE_FORM
z CV_ERROR_INCLUDE_LONG_DISTANCE
z CV_GSM_CLD_DN_NO_EXIST
8-259
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release REL
Release
A
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)
z CV_TEMPORARY_FAILURE
z CV_ERROR_FOR_THE_TIME_BEING
8-260
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
A
REL
2) Call failures due to internal failures (case 1)

z CV_TEMPORARY_FAILURE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release REL
Release
A
REL
IV. Formula
None
8-261
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).

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
A
REL

8-262
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release REL
Release
A
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-263
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
A
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release REL
Release
A
REL
IV. Formula
None
8-264
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
A
REL
B
REL
C
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-265
(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
ANM
A
REL
B
REL
C
IV. Formula
None
8.18.11 Count of Circuits in Maintenance
I. Entity Name
MNTCIR
II. Description
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-266
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.
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
B ANM
ACM Connect
Connect
Connect Ack
C
ANM
Connect Ack
IV. Formula
None
8-267
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
ACM
REL
B
REL
C
IV. Formula
None
I. Entity Name
ALTR
II. Description
8-268
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.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release REL
Release
A
REL
2) Count of Callee Power-Off (case 2)

The cause value of the REL message is CV_GSM_CLD_USER_NOT_ACTIVE.
8-269
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release REL
Release
A
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-270
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
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:

z The MSC finds out the call is a tandem call according to the called number
analysis.
z The source TMG number and the destination area index are not null. See point A
8-271

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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.

z The MSC finds out the call is a tandem call according to the called number
analysis.
z The source TMG number and the destination area index are not null.
z The route is successfully selected. See point A in the following figure.
8-272

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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.

z The MSC finds out the call is a tandem call.
z The source TMG number and the destination area index are not null.
z The ACM is received from the backward office. See point B in the following figure.
8-273

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-274

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-275
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.

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
IV. Formula
None
8-276
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

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-277
It is measured from the moment the call is answered to that the call is released. See

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-278

IAM
REL
RLC
ANM/ANC
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-279
IAM
REL
A
RLC
ACM
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-280
IAM
IAM
ACM
ACM
REL
A
RLC
ANM/ANC
IV. Formula
None
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-281
IAM
IAM
ACM
ACM
REL
A
RLC
ANM/ANC
IV. Formula
None
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-282
IAM
IAM
ACM
ACM
REL
A
RLC
ANM/ANC
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-283

IAM
IAM
REL
RLC
ACM
IV. Formula
None
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-284

IAM
IAM
REL
RLC
ANM
IV. Formula
None
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-285

IAM
IAM
REL
A
RLC
ANM
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-286

IAM
IAM
REL
A
RLC
ANM
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-287

IAM
IAM
REL
RLC
ANM
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-288

IAM
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-289

IAM
IAM
REL
A
RLC
ANM
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-290

IAM
IAM
REL
RLC
ANM
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-291
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
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
IAM
REL
IV. Formula
None
8-292
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
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-293

IAM
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-294

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

IAM
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-295
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.

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

IAM
IAM
REL
IV. Formula
None
8-296
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
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.
It is measured when the MSC selects the route for the callee after the number analysis.
8-297

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-298

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-299

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-300

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-301
IAM
REL
A
RLC
ACM
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-302
IAM
Outgoing trunk
overflow
A
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-303

IAM
IAM
REL
RLC
ACM
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-304

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-305

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-306

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-307
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.

IAM
A
IAM
ACM
ACM B
ANM/ANC
ANM/ANC C
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-308
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.

IAM
IAM
REL
A
RLC
ACM
IV. Formula
None

Failures
I. Entity Name
CFCR
II. Description
It is measured when the MSC fails to allocate the internal common resources. See
8-309

IAM
IAM
ACM
REL
A
RLC
IV. Formula
None
I. Entity Name
POCT
II. Description
situation.

z The MSC fails to select an internal outgoing (bidirectional) trunk in a forwarding
call.
8-310

IAM
IAM
ACM
REL A
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-311
IAM
IAM
ACM
ACM
REL
A
RLC
ANM/ANC
IV. Formula
None
8-312
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 Global Components
Chapter 9 Global Components

The measurement set is used to check the status of the MSC such as CPU seizure rate
and count of VLR subscribers.
Name Description
MS-CPU-OCCUP-TRAF CPU seizure rate
MS-VDB-MSG-SUB-STAT Count of VLR subscribers
MS-LAI-STAT Location area traffic distribution
MS-GCI-STAT Cell traffic distribution

MS_VDB_MVNO_SUB Count of MVNO subscribers
9.2 CPU Seizure Rate

9.2.1 Overview of MS-CPU-OCCUP-TRAF
Name Description
SEIZR Average seizure rate
CG Count of congestion
OL Overload count
OLT Overload duration
ORC Count of originating and incoming calls
TEC Count of terminating and outgoing calls
PEAKS Peak seizure rate
PEAKT Peak seizure time
PEAKD Peak seizure duration
9-1
9.2.2 Average Seizure Rate
I. Entity Name
SEIZR
II. Description
It is the average CPU seizure rate within a measurement period.
It is measured inside the MSC.
IV. Formula
None
I. Entity Name
CG
II. Description
It is the count of calls when the CPU seizure rate is above the highest level of overload.
IV. Formula
None
I. Entity Name
CGT
II. Description
It is the duration of congestion within a measurement period.
IV. Formula
None
9-2
9.2.5 Count of Overload
I. Entity Name
OL
II. Description
It is the count of calls when the CPU seizure rate is between the lowest level and the
highest level of overload.
IV. Formula
None
9.2.6 Overload Duration
I. Entity Name
OLT
II. Description
It is the duration of overload within a measurement period.
IV. Formula
None
9.2.7 Count of Originating and Incoming Calls
I. Entity Name
ORC
II. Description
It is the sum of the count of calls originated by a subscriber and the count of calls
through an incoming trunk.
It is measured when the MSC receives the message CM Service Request from layer 3,
or the IAM message and IAI message.
9-3
IV. Formula
None
9.2.8 Count of Incoming and Outgoing Calls
I. Entity Name
TEC
II. Description
It is the sum of the count of calls terminated to a subscriber and the count of calls
through an outgoing trunk.
It is measured when the MSC analyzes the called number and determines that it is an
incoming/outgoing call.
IV. Formula
None
9.2.9 Peak Seizure Rate
I. Entity Name
PEAKS
II. Description
It is the peak seizure rate within a measurement period.
It is measured when the peak occurs.
IV. Formula
None
9.2.10 Peak Seizure Time
I. Entity Name
PEAKT
II. Description
It is the time when the peak occurs for the first time within a measurement period.
9-4
It is measured when the peak occurs for the first time within a measurement period.
IV. Formula
None
9.2.11 Peak Seizure Duration
I. Entity Name
PEAKD
II. Description
It is the duration of peak seizure within a measurement period.
It is measured when the peak occurs.
IV. Formula
None
9.3 Count of VLR Subscribers

9.3.1 Overview of MS-VDB-MSG-SUB-STAT
Name Description
SPLMN VLR local subscribers
SR VLR roaming subscribers
SCLIP Subscribers with CLIP
SCLTR Subscribers with CLIR
SCOLP Subscribers with COLP
SCOLR Subscribers with COLR

SCFU Subscribers with CFU
SCFB Subscribers with CFB
SCFNRY Subscribers with CFNRy
SCFNRC Subscribers with CFNRc
SCW Subscribers with call waiting
SCH Subscribers with call hold
9-5
Name Description
SMPTY Subscribers with three-party service
SCUG Subscribers with CUG
AoCI Subscribers with AOCI
AoCC Subscribers with AOCC
SBAOC Subscribers with BAOC
SBOIC Subscribers with BOIC
SBE Subscribers with BOIC except home country
SFC Subscriber with ODB
ODBO Subscribers with ODB BAOC
ODBI Subscribers with ODB BOIC
ODBE Subscribers with ODB BOIC except home country
IMSID Subscribers with IMSI detached
SIN IN subscribers
GPRS GPRS subscribers

VLRLNU Local network subscribers
VLRONU Other network subscribers
RDSU Subscribers with data service

HPU Subscribers with hot billing
LCS Subscribers with LCS
PPS Subscribers with PPS triggered by number segment
OCSI Mobile originating CAMEL subscribers
DCSI CAMEL subscribers with dialing service
VTCSI Mobile terminating CAMEL subscribers in VMSC
SSCSI CAMEL subscribers invoked by supplementary service
SMSCSI SMS CAMEL subscribers
MCSI CAMEL subscribers with mobile management
ALS ALS subscribers
VPD Subscribers with VP dual number
9-6
9.3.2 VLR Local Subscribers
I. Entity Name
SPLMN
II. Description
It is the count of local subscribers in the VLR of the local office.
It is measured inside the VLR.

Three measurement points are involved in the flow of location updating. See point A,
point B and point D in the following figure.
z At point A, the VLR sets the subscriber type and inserts an unallocated record
after it obtains the IMSI information from a subscriber. At this moment, the VLR
checks that the subscriber is a local subscriber and updates the count of local
subscribers in itself.
z At point B, when the inter-office location updating happens, the message
CANCEL-LOCATION needs to be sent from the HLR to the PVLR where the
subscriber is located. After receiving the message, the PVLR deletes the
subscriber who has roamed to another VLR. At this moment, the PVLR checks
that the subscriber is a local subscriber and updates the count of local subscribers
in itself.
z At point D, after receiving the message UPDATE-LOCATION-ACK from the HLR,
the VLR updates the type of the subscriber through UpdateMMInfo. Then the VLR
checks that the subscriber is a local subscriber and updates the count of local
9-7
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
One measurement point is involved in the flow of operating subscriber data in the HLR.
z At point A, when subscriber data is deleted from the HLR, the message
CANCEL-LOCATION needs to be sent from the HLR to the VLR where the
subscriber is located. After receiving the message, the VLR deletes the subscriber
data in itself. At this moment, the VLR checks that the subscriber is a local
subscriber and updates the count of local subscribers in itself.
9-8
VLR HLR OMC
Delete subscriber data

MAP-CANCEL-LOCTION
A
Subscriber data is deleted
One measurement point is involved in the periodical management of the subscribers in

the VLR. See point B in the following figure.
z At point B, if there is no message interaction between a subscriber and the VLR
during a period specified in the VLR configuration table, the VLR deletes the
subscriber data and notifies the HLR. Then the VLR checks that the subscriber is a
local subscriber and updates the count of local subscribers in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.3 VLR Roaming Subscribers
I. Entity Name
SR
II. Description
It is the count of roaming subscribers in the VLR of the local office.
9-9

For the count of roaming subscribers and that of local subscribers, the measurement
objects are both subscriber type, so the measurement points are the same as those in
the measurement of local subscribers. Three measurement points are involved in the
flow of location updating. See point A, point B and point D in the following figure.
checks that the subscriber is a roaming subscriber and updates the count of
roaming subscribers in itself.
that the subscriber is a roaming subscriber and updates the count of roaming
the VLR updates the type of the subscriber through UpdateMMInfo. Then the VLR
checks that the subscriber is a roaming subscriber and updates the count of
roaming subscribers in itself.
9-10
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the subscriber is a roaming
subscriber and updates the count of roaming subscribers in itself.
9-11
VLR HLR OMC

MAP-CANCEL-LOCTION
A
One measurement point is involved in the periodical deletion of the subscribers in the
VLR. See point B in the following figure.
subscriber data and notifies the HLR. Then the VLR checks that the subscriber is a
roaming subscriber and updates the count of roaming subscribers in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.4 Subscribers with CLIP
I. Entity Name
SCLIP
II. Description
It is the count of subscribers with the calling line identification presentation (CLIP)
service in the VLR.
9-12

Two measurement points are involved in the flow of location updating. See point B and
that the CLIP service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CLIP in itself.
z At point C, after receiving the message INSERT-SUBSCRIBER-DATA from the
HLR, the VLR checks that the subscriber newly subscribes to the CLIP service,
and updates the count of subscribers with CLIP in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
Two measurement points are involved in the flow of operating subscriber data in the
HLR. See point A and point B in the following figures.
9-13
data in itself. At this moment, the VLR checks that the active CLIP service is in the
supplementary service subscription information of subscriber data and updates
the count of subscribers with CLIP in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
z At point B, when the subscriber supplementary service data is modified in the HLR,
the message MAP-INSERT-SUB-DATA or the message
MAP-DELETE-SUB-DATA needs to be sent to the VLR where the subscriber is
located. After receiving the message, the VLR updates the designated
supplementary service subscriber data. At this moment, the VLR checks that the
active CLIP service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CLIP in itself.
VLR HLR OMC
Modify subscriber data

MAP-DELETE-SUB-DATA
B
MAP-DELETE-SUB-DATA-ACK is modified
One measurement point is involved in the flow of operating supplementary services.

z At point A, when the MS initiates the supplementary service, the message
MAP-INSERT-SUBSCRIBER-DATA needs to be sent from the HLR to the VLR
where the subscriber is located. After receiving the message, the VLR compares
the supplementary service subscription information of the subscriber data in itself
and that in the message. If the CLIP service is changed from the active state to the
9-14
inactive state, the VLR decreases the count of subscribers with CLIP. Otherwise,
the VLR increases the count. Then the VLR updates the count of subscribers with
CLIP.
MSC VLR HLR

DEA -SS MAP-REG / ERASE / ACT /
DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
subscriber data and notifies the HLR. Then the VLR checks that the subscriber
newly subscribes to the CLIP service, and updates the count of subscribers with
CLIP in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9-15
9.3.5 Subscribers with CLIR
I. Entity Name
SCLTR
II. Description
It is the count of subscribers with the calling line identification restriction (CLIR) service
in the VLR.

that the CLIR service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CLIR in itself.
HLR, the VLR checks that the subscriber newly subscribes to the CLIR service,
and updates the count of subscribers with CLIR in itself.
9-16
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active CLIR service is in the
the count of subscribers with CLIR in itself.
9-17
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CLIR service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CLIR in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the CLIR service is changed from the active state to the
inactive state, the VLR decreases the count of subscribers with CLIR. Otherwise,
CLIR.
9-18
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CLIR service, and updates the count of subscribers with
CLIR in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.6 Subscribers with COLP
I. Entity Name
SCOLP
II. Description
It is the count of subscribers with the connected line identification presentation (COLP)
service in the VLR.
9-19

that the COLP service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with COLP in itself.
HLR, the VLR checks that the subscriber newly subscribes to the COLP service,
and updates the count of subscribers with COLP in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-20
data in itself. At this moment, the VLR checks that the active COLP service is in
the supplementary service subscription information of subscriber data and
updates the count of subscribers with COLP in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active COLP service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with COLP in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the COLP service is changed from the active state to
the inactive state, the VLR decreases the count of subscribers with COLP.
9-21
Otherwise, the VLR increases the count. Then the VLR updates the count of
subscribers with COLP.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the COLP service, and updates the count of subscribers with
COLP in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.7 Subscribers with COLR
I. Entity Name
SCOLR
9-22
II. Description
It is the count of subscribers with the connected line identification restriction (COLR)
service in the VLR.

that the COLR service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with COLR in itself.
HLR, the VLR checks that the subscriber newly subscribes to the COLR service,
and updates the count of subscribers with COLR in itself.
9-23
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active COLR service is in
updates the count of subscribers with COLR in itself.
9-24
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active COLR service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with COLR in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the COLR service is changed from the active state to
the inactive state, the VLR decreases the count of subscribers with COLR.
subscribers with COLR.
9-25
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the COLR service, and updates the count of subscribers with
COLR in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.8 Subscribers with CFU
I. Entity Name
SCFU
II. Description
It is the count of subscribers with the call forwarding unconditional (CFU) service in the
VLR.
9-26

that the CFU service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFU in itself.
HLR, the VLR checks that the subscriber newly subscribes to the CFU service,
and updates the count of subscribers with CFU in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-27
data in itself. At this moment, the VLR checks that the active CFU service is in the
the count of subscribers with CFU in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CFU service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFU in itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the CFU service is changed from the active state to the
inactive state, the VLR decreases the count of subscribers with CFU. Otherwise,
9-28
CFU.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CFU service, and updates the count of subscribers with
CFU in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.9 Subscribers with CFB
I. Entity Name
SCFB
9-29
II. Description
It is the count of subscribers with the call forwarding busy (CFB) service in the VLR.

that the CFB service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFB in itself
HLR, the VLR checks that the subscriber newly subscribes to the CFB service,
and updates the count of subscribers with CFB in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-30
data in itself. At this moment, the VLR checks that the active CFB service is in the
the count of subscribers with CFB in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CFB service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFB in itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

9-31
and that in the message. If the CFB service is changed from the active state to the
inactive state, the VLR decreases the count of subscribers with CFB. Otherwise,
CFB.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CFB service, and updates the count of subscribers with
CFB in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9-32
9.3.10 Subscribers with CFNRy
I. Entity Name
SCFNRY
II. Description
It is the count of subscribers with the call forwarding on no reply (CFNRy) service in the
VLR.

that the CFNRy service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFNRy in itself
HLR, the VLR checks that the subscriber newly subscribes to the CFNRy service,
and updates the count of subscribers with CFNRy in itself.
9-33
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active CFNRy service is in
updates the count of subscribers with CFNRy in itself.
9-34
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CFNRy service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFNRy in itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the CFNRy service is changed from the active state to
the inactive state, the VLR decreases the count of subscribers with CFNRy.
subscribers with CFNRy.
9-35
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CFNRy service, and updates the count of subscribers with
CFNRy in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.11 Subscribers with CFNRc
I. Entity Name
SCFNRC
II. Description
It is the count of subscribers with the call forwarding on mobile subscriber not reachable
(CFNRc) service in the VLR.
9-36

that the CFNRc service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFNRc in itself
HLR, the VLR checks that the subscriber newly subscribes to the CFNRc service,
and updates the count of subscribers with CFNRc in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-37
data in itself. At this moment, the VLR checks that the active CFNRc service is in
updates the count of subscribers with CFNRc in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CFNRc service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CFNRc in itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the CFNRc service is changed from the active state to
the inactive state, the VLR decreases the count of subscribers with CFNRc.
9-38
subscribers with CFNRc.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CFNRc service, and updates the count of subscribers with
CFNRc in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.12 Subscribers with Call Waiting
I. Entity Name
SCW
9-39
II. Description
It is the count of subscribers with the call waiting (CW) service in the VLR.

that the CW service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CW in itself
HLR, the VLR checks that the subscriber newly subscribes to the CW service, and
updates the count of subscribers with CW in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-40
data in itself. At this moment, the VLR checks that the active CW service is in the
the count of subscribers with CW in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CW service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CW in itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

9-41
and that in the message. If the CW service is changed from the active state to the
inactive state, the VLR decreases the count of subscribers with CW. Otherwise,
CW.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CW service, and updates the count of subscribers with
CW in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9-42
9.3.13 Subscribers with Call Hold
I. Entity Name
SCH
II. Description
It is the count of subscribers with the call hold service in the VLR.

that the call hold service is in the supplementary service subscription information
of subscriber data and updates the count of subscribers with the call hold service
in itself.
HLR, the VLR checks that the subscriber newly subscribes to the call hold service,
and updates the count of subscribers with the call hold service in itself.
9-43
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active call hold service is in
updates the count of subscribers with the call hold service in itself.
9-44
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active call hold service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with the call hold service in
itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the call hold service is changed from the active state to
the inactive state, the VLR decreases the count of subscribers with the call hold
service. Otherwise, the VLR increases the count. Then the VLR updates the count
of subscribers with the call hold service.
9-45
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the call hold service, and updates the count of subscribers
with the call hold service in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.14 Subscribers with Three-Party Service
I. Entity Name
SMPTY
II. Description
It is the count of subscribers with the three-party (3PTY) service in the VLR.
9-46

that the 3PTY service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with 3PTY in itself.
HLR, the VLR checks that the subscriber newly subscribes to the 3PTY service,
and updates the count of subscribers with 3PTY in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-47
data in itself. At this moment, the VLR checks that the active 3PTY service is in the
the count of subscribers with 3PTY in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active 3PTY service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with 3PTY in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the 3PTY service is changed from the active state to
the inactive state, the VLR decreases the count of subscribers with 3PTY.
9-48
subscribers with 3PTY.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the 3PTY service, and updates the count of subscribers with
3PTY in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.15 Subscribers with CUG
I. Entity Name
SCUG
9-49
II. Description
It is the count of subscribers with the closed user group (CUG) service in the VLR.

that the CUG service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CUG in itself.
HLR, the VLR checks that the subscriber newly subscribes to the CUG service,
and updates the count of subscribers with CUG in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-50
data in itself. At this moment, the VLR checks that the active CUG service is in the
the count of subscribers with CUG in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active CUG service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with CUG in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

9-51
and that in the message. If the CUG service is changed from the active state to the
inactive state, the VLR decreases the count of subscribers with CUG. Otherwise,
CUG.
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the CUG service, and updates the count of subscribers with
CUG in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9-52
9.3.16 Subscribers with AoCI
I. Entity Name
AoCI
II. Description
It is the count of subscribers with the advice of charge information (AoCI) service in the
VLR.
IV. Formula
None
9.3.17 Subscribers with AoCC
I. Entity Name
AoCC
II. Description
It is the count of subscribers with the advice of charge charging (AoCC) service in the
VLR.

that the AoCC service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with AoCC in itself.
HLR, the VLR checks that the subscriber newly subscribes to the AoCC service,
and updates the count of subscribers with AoCC in itself.
9-53
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active AoCC service is in the
the count of subscribers with AoCC in itself.
9-54
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active AoCC service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with AoCC in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the AoCC service, and updates the count of subscribers with
AoCC in itself.
9-55
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.18 Subscribers with BAOC
I. Entity Name
SBAOC
II. Description
It is the count of subscribers with the barring of all outgoing calls (BAOC) service in the
VLR.

that the BAOC service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with BAOC in itself.
HLR, the VLR checks that the subscriber newly subscribes to the BAOC service,
and updates the count of subscribers with BAOC in itself.
9-56
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the BAOC service is in the
the count of subscribers with BAOC in itself.
9-57
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active BAOC service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with BAOC in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the BAOC service, and updates the count of subscribers with
BAOC in itself.
9-58
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.19 Subscribers with BOIC
I. Entity Name
SBOIC
II. Description
It is the count of subscribers with the barring of outgoing international calls (BOIC)
service in the VLR.

that the BOIC service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with BOIC in itself.
HLR, the VLR checks that the subscriber newly subscribes to the BOIC service,
and updates the count of subscribers with BOIC in itself.
9-59
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active BOIC service is in the
the count of subscribers with BOIC in itself.
9-60
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active BOIC service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with BOIC in itself
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the BOIC service, and updates the count of subscribers with
BOIC in itself.
9-61
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.20 Subscribers with BOIC Except Home Country
I. Entity Name
SBE
II. Description
It is the count of subscribers with the BOIC except home country service in the VLR.

that the BOIC except home country service is in the supplementary service
subscription information of subscriber data and updates the count of subscribers
with the BOIC except home country service in itself.
HLR, the VLR checks that the subscriber newly subscribes to the BOIC except
home country service, and updates the count of subscribers with the BOIC except
home country service in itself.
9-62
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active BOIC except home
country service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with the BOIC except home
country service in itself.
9-63
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active BOIC except home country service is in the supplementary service
with the BOIC except home country service in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the BOIC except home country service, and updates the
count of subscribers with BOIC except home country service in itself.
9-64
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.21 Subscriber with ODB
I. Entity Name
SFC
II. Description
It is the count of subscribers with the operator terminated barring (ODB) service in the
VLR.

that the active ODB service is in the supplementary service subscription
information of subscriber data and updates the count of subscribers with ODB in
itself.
HLR, the VLR checks that the subscriber newly subscribes to the ODB service,
and updates the count of subscribers with ODB in itself.
9-65
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active ODB service is in the
the count of subscribers with ODB in itself.
9-66
VLR HLR OMC

MAP-CANCEL-LOCTION
A
active ODB service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with ODB in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B

and that in the message. If the ODB service is changed from the active state to the
inactive state, the VLR decreases the count of subscribers with ODB. Otherwise,
ODB.
9-67
MSC VLR HLR

DEA-SS
DEA-SS-ACK
DEA-SS-ACK
MAP-INSERT-
SUBSCRIBER-DATA
A
newly subscribes to the ODB service, and updates the count of subscribers with
ODB in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.22 Subscribers with ODB BAOC
I. Entity Name
ODBO
II. Description
It is the count of subscribers with ODB BAOC in the VLR.
9-68

that the ODB BAOC service is in the supplementary service subscription
information of subscriber data and updates the count of subscribers with ODB
BAOC in itself.
HLR, the VLR checks that the subscriber newly subscribes to the ODB BAOC
service, and updates the count of subscribers with ODB BAOC in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-69
data in itself. At this moment, the VLR checks that the active ODB BAOC service is
in the supplementary service subscription information of subscriber data and
updates the count of subscribers with ODB BAOC in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
MAP-DELETE-SUB-DATA needs to be sent from the HLR to the VLR where the
subscriber is located. After receiving the message, the VLR updates the
designated supplementary service subscriber data. At this moment, the VLR
checks that the active ODB BAOC service is in the supplementary service
with ODB BAOC in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the ODB BAOC service, and updates the count of subscribers
with ODB BAOC in itself.
9-70
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.23 Subscribers with ODB BOIC
I. Entity Name
ODBI
II. Description
It is the count of subscribers with ODB BOIC in the VLR.

that the ODB BOIC service is in the supplementary service subscription
information of subscriber data and updates the count of subscribers with ODB
BOIC in itself.
HLR, the VLR checks that the subscriber newly subscribes to the ODB BOIC
service, and updates the count of subscribers with ODB BOIC in itself.
9-71
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active ODB BOIC service is
in the supplementary service subscription information of subscriber data and
updates the count of subscribers with ODB BOIC in itself.
9-72
VLR HLR OMC

MAP-CANCEL-LOCTION
A
checks that the active ODB BOIC service is in the supplementary service
with ODB BOIC in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the ODB BOIC service, and updates the count of subscribers
with ODB BOIC in itself.
9-73
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.24 Subscribers with ODB BOIC Except Home Country
I. Entity Name
ODBE
II. Description
It is the count of subscribers with the ODB BOIC except home country service in the
VLR.

that the ODB BOIC except home country service is in the supplementary service
with the ODB BOIC except home country service in itself.
HLR, the VLR checks that the subscriber newly subscribes to the ODB BOIC
except home country service, and updates the count of subscribers with the ODB
BOIC except home country service in itself.
9-74
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the active ODB BOIC except
home country service is in the supplementary service subscription information of
subscriber data and updates the count of subscribers with the ODB BOIC except
home country service in itself.
9-75
VLR HLR OMC

MAP-CANCEL-LOCTION
A
checks that the active ODB BOIC except home country service is in the
the count of subscribers with the ODB BOIC except home country service in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the ODB BOIC except home country service, and updates the
count of subscribers with the ODB BOIC except home country service in itself.
9-76
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.25 Subscribers with IMSI Detached
I. Entity Name
IMSID
II. Description
It is the count of subscribers with IMSI detached in the VLR.

presets the subscriber with IMSI detached and updates the count of subscribers
with IMSI detached in itself.
that the subscriber is with IMSI detached and updates the count of subscribers
with IMSI detached in itself.
the VLR updates the state of the subscriber through IMSI Attached. Then the VLR
checks that the subscriber is with IMSI detached and updates the count of
subscribers with IMSI detached in itself.
9-77
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
Two measurement points are involved in the flow of power-off initiated by the MS. See
point A and point B in the following figures.
z At point A, when the MS sends a power-off request through the Iu interface in CS
domain, the MAP sets the subscriber to the IMSI detached state and measures the
count of subscribers in the VLR whose mobile phones are powered off.
9-78
Iu-CS
MS RNS MSC VLR
IMSI-DETACH-IND
MAP-SET-IMSI-DETACH
A
MAP-SET-IMSI-DETACH-ACK
z At point B, when the MS sends a power-off request through the Gs interface in

packet domain, the MAP transparently transfers the message
BSSAP-IMSI-DETACH-IND to the VLR in order to set the subscriber to the IMSI
detached state and measures the count of subscribers in the VLR whose mobile
phones are powered off.
Iu-PS
MS BSS/UTRAN SGSN MSC/VLR
IMSI-DETACH-IND
BSSAP-IMSI-DETACH-IND
Two measurement points are involved in the periodical deletion of the subscribers in
the VLR. See point A and point B in the following figures.
z At point A, if there is no message interaction between a subscriber and the VLR
during a period specified in the VLR configuration table, the VLR sets the
subscriber to the IMSI detached state by initiating an implicit IMSI detachment and
updates the inactive subscribers in itself.
9-79
VLR MSC
NOTIFY- GSMSCF
(IMPLICIT-IMSI-DETACH)
A

subscriber data and notifies the HLR. Then the VLR updates the count of inactive
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.26 IN Subscribers
I. Entity Name
SIN
II. Description
It is the count of subscribers with the CAMEL service in the VLR.

9-80
that the CAMEL service is in the CAMEL subscription information of subscriber
data and updates the count of subscribers with CAMEL in itself.
HLR, the VLR checks that the subscriber newly subscribes to the CAMEL service,
and updates the count of subscribers with CAMEL in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the CAMEL service is in the
CAMEL subscription information of subscriber data and updates the count of
subscribers with CAMEL in itself.
9-81
VLR HLR OMC

MAP-CANCEL-LOCTION
A
subscriber is located. After receiving the message, the VLR updates the CAMEL
subscription data of the subscriber. At this moment, the VLR checks that the
CAMEL service is in the CAMEL subscription information of subscriber data and
updates the count of subscribers with CAMEL in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the CAMEL service, and updates the count of subscribers
with CAMEL in itself.
9-82
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.27 GPRS Subscribers
I. Entity Name
GPRS
II. Description
It is the count of GPRS subscribers in the VLR.

z At point A, the location is updated periodically. After the VLR obtains the message
UPDATE-LOCATION, it sets the subscriber to the GPRS detached state. If the
original association of the subscriber is valid, the VLR updates the count of
subscribers with GPRS association in itself.
that the GPRS association of the subscriber is valid and updates the count of
GPRS subscribers in itself.
the VLR updates the GPRS association state of the subscriber by setting the
association state. Then it updates the count of subscribers with GPRS association
in itself.
9-83
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the GPRS association of the
subscriber is valid and updates the count of GPRS subscribers in itself.
9-84
VLR HLR OMC

MAP-CANCEL-LOCTION
A
Two measurement points are involved in the flow of power-off initiated by the MS. See
point A and point B in the following figures.
z At point A, when the MS sends a power-off request through the Iu interface in CS
domain, the MAP sets the subscriber to the IMSI detached state, and the GPRS
association state to invalid. If the original association of the subscriber is valid, the
VLR updates the count of subscribers with GPRS association in itself.
Iu-CS
MS RNS MSC VLR
IMSI-DETACH-IND
MAP-SET-IMSI-DETACH
A
MAP-SET-IMSI-DETACH-ACK
z At point A, when the MS sends a power-off request through the Gs interface in

packet domain, the MAP transparently transfers the message
BSSAP-IMSI-DETACH-IND to the VLR in order to set the subscriber to the IMSI
detached state and the GPRS association state to invalid. If the original
association of the subscriber is valid, the VLR updates the count of subscribers
with GPRS association in itself.
9-85
Iu-PS
IMSI-DETACH-IND
Two measurement points are involved in the flow of GPRS detachment initiated at the
network side. See point A and point B in the following figures.
z At point A, when the SGSN sends a GPRS detached request to the MS, it sends a
GPRS detached request to the MSC. The VLR sets the GPRS association of the
subscriber to invalid. If the original association of the subscriber is valid, the VLR
updates the count of subscribers with GPRS association in itself.
MS SGSN GGSN MSC/VLR
GPRS-DETACH-
REQUEST DELETE-PDP-
CONTEXT-REQ
DELETE-PDP-
CONTEXT-RSP
BSSAP_GPRS_DETACH_INDICATION
A
GPRS-DETACH-
ACCEPT
z At point B, the SGSN sends a restart notice to the MSC after the SGSN recovers
from failure. At this moment, the VLR sets the GPRS association of the
subscribers to invalid who are associated with the SGSN. If the original
association of the subscriber is valid, the VLR updates the count of subscribers
with GPRS association in itself.
9-86
SGSN MSC VLR
BSSAP-RESET-INDICATION
BSSAP-RESET-INDICATION
subscriber data and notifies the HLR. Then the VLR checks that the GPRS
association of the subscriber is valid and updates the count of GPRS subscribers
in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS
MAP-PURGY-MS
IV. Formula
None
9.3.28 Local Network Subscribers
I. Entity Name
VLRLNU
II. Description
It is the count of local network subscribers in the VLR.
9-87
Two measurement points are involved in the flow of location updating. See point A and
z At point A, the VLR inserts an unallocated record after it obtains the IMSI
information from a subscriber. At this moment, the VLR checks that the country
code and network number in the IMSI belong to the local network and updates the
count of local network subscribers in itself.
that the country code and network number in the IMSI belong to the local network
and updates the count of local network subscribers in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the country code and network
9-88
number in the IMSI belong to the local network and updates the count of local
network subscribers in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
subscriber data and notifies the HLR. Then the VLR checks that the country code
and network number in the IMSI belong to the local network and updates the count
of local network subscribers in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.29 Other Network Subscribers
I. Entity Name
VLRONU
II. Description
It is the count of subscribers belonging to other networks in the VLR.
9-89

Two measurement points are involved in the flow of location updating. See point A and
z At point A, the VLR inserts an unallocated record after it obtains the IMSI
information from a subscriber. At this moment, the VLR checks that the country
code and network number in the IMSI belong to another network and updates the
count of subscribers belonging to other networks in itself.
that the country code and network number in the IMSI belong to another network
and updates the count of subscribers belonging to other networks in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-90
data in itself. At this moment, the VLR checks that the country code and network
number in the IMSI belong to another network and updates the count of
subscribers belonging to other networks in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
subscriber data and notifies the HLR. Then the VLR checks that the country code
and network number in the IMSI belong to another network and updates the count
of subscribers belonging to other networks in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.30 Subscribers with Data Service
I. Entity Name
RDSU
9-91
II. Description
It is the count of subscribers with data services in the VLR.

that a data service is in the basic service subscription information of subscriber
data and updates the count of subscribers with data services in itself.
HLR, the VLR checks that the subscriber newly subscribes to a data service, and
updates the count of subscribers with data services in itself.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
9-92
data in itself. At this moment, the VLR checks that a data service is in the basic
service subscription information of subscriber data and updates the count of
subscribers with data services in itself.
VLR HLR OMC

MAP-CANCEL-LOCTION
A
z At point B, when the subscriber basic service subscription data is modified in the
HLR, the message MAP-INSERT-SUB-DATA or the message
subscriber is located. After receiving the message, the VLR updates the basic
service subscription data of the subscriber. At this moment, the VLR checks that it
is the first time for the subscriber to subscribe to a data service in the basic service
with data services in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
9-93
newly subscribes to a data service, and updates the count of subscribers with data
services in itself.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.31 Subscribers with Hot Billing
I. Entity Name
HPU
II. Description
It is the count of subscribers with the hot billing service in the VLR.

that the hot billing service is in the subscription information of subscriber data and
updates the count of subscribers with the hot billing service in itself.
HLR, the VLR checks that the subscriber newly subscribes to the hot billing
service, and updates the count of subscribers with the hot billing service in itself.
9-94
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the hot billing service is in the
with the hot billing service in itself.
9-95
VLR HLR OMC

MAP-CANCEL-LOCTION
A
z At point B, when the subscription data is modified in the HLR, the message
MAP-INSERT-SUB-DATA or the message MAP-DELETE-SUB-DATA needs to
be sent from the HLR to the VLR where the subscriber is located. After receiving
the message, the VLR updates the subscription data of the subscriber. At this
moment, the VLR checks that the hot billing service is in the subscription
information of subscriber data and updates the count of subscribers with the hot
billing service in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the hot billing service, and updates the count of subscribers
with the hot billing service in itself.
9-96
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.32 Subscribers with LCS
I. Entity Name
LCS
II. Description
It is the count of subscribers with the location service (LCS) in the VLR.

that the LCS service is in the subscription information of subscriber data and
updates the count of subscribers with LCS in itself.
HLR, the VLR checks that the subscriber newly subscribes to the LCS service,
and updates the count of subscribers with LCS in itself.
9-97
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the LCS service is in the
with LCS in itself.
9-98
VLR HLR OMC

MAP-CANCEL-LOCTION
A
z At point B, when the LCS subscription data is modified in the HLR, the message
moment, the VLR checks that the LCS service is in the subscription information of
subscriber data and updates the count of subscribers with LCS in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the LCS service, and updates the count of subscribers with
LCS in itself.
9-99
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.33 Subscribers with PPS Triggered by Number Segment
I. Entity Name
PPS
II. Description
It is the count of subscribers with the prepaid service (PPS) triggered by number
segment in the VLR.

that the PPS service is in the subscription information of subscriber data and
updates the count of subscribers with PPS in itself.
HLR, the VLR checks that the subscriber newly subscribes to the PPS service,
and updates the count of subscribers with PPS in itself.
9-100
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCTION
B
C
AREA-ACK
data in itself. At this moment, the VLR checks that the PPS service is in the
with PPS in itself.
9-101
VLR HLR OMC

MAP-CANCEL-LOCTION
A
z At point B, when the subscription data is modified in the HLR, the message
moment, the VLR checks that the PPS service is in the subscription information of
subscriber data and updates the count of subscribers with PPS in itself.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
newly subscribes to the PPS service, and updates the count of subscribers with
PPS in itself.
9-102
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.34 MO CAMEL Subscribers
I. Entity Name
OCSI
II. Description
It is the count of the O_CSI intelligent subscribers in the VLR of the local office.

Two measurement points are involved in the flow of location update. See point B and
z At point B, when the location is updated, the message CANCEL_LOCATION
needs to be sent from the HLR to the PVLR where the subscriber was located.
After receiving the message, the PVLR deletes the data of the subscriber that has
roamed to another VLR. At this moment, the PVLR checks whether the subscriber
subscribes to the O_CSI intelligent service according to the CAMEL subscription
data. If so, the PVLR measures and updates the count of the O_CSI intelligent
subscribers in the PVLR.
z At point C, after receiving the message INSERT_SUBSCRIBER_DATA from the
HLR, the VLR checks whether the CAMEL type of the subscriber is the O_CSI
intelligent service. If so, the VLR updates the count of the O_CSI intelligent
subscribers in the VLR.
9-103
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
MAP-CANCEL-LOCATION-ACK
MAP-VDB-INSERT-SUBSCRIBER-DATA
C
MAP-VDB-INSERT-SUBSCRIBER-DATA-ACK
AREA-ACK
Two measurement points are involved in the flow of operating HLR subscriber data.
See point A and point B in the following figure.
z At point A, when subscriber data is deleted from the HLR, it needs to send the
message CANCEL_LOCATION to the VLR where the subscriber is located. The
VLR deletes the subscriber data after receiving the message
CANCEL_LOCATION. At this moment, the VLR checks whether the subscriber
data. If so, the VLR measures and updates the count of the O_CSI intelligent
9-104
VLR HLR OMC

MAP-CANCEL-LOCATION
A
MAP-CANCEL-LOCATION-ACK Subscriber data is
deleted
z At point B, when the CAMEL service subscription data of a subscriber is modified

in the HLR, the message MAP-INSERT-SUB-DATA or MAP-DELETE-SUB-DATA
needs to be sent from the HLR to the VLR where the subscriber is located. After
receiving the message, the VLR updates the CAMEL service subscription data of
the subscriber in the VLR. At this moment, the VLR checks whether the subscriber
data. If so, the VLR measures and updates the count of the O_CSI intelligent
VLR HLR OMC
Modifiy subscriber data

MAP-DELETE-SUB-DATA
B
MAP-INSERT-SUB-DATA-ACK or Subscriber data is
It is measured inside the VLR. One measurement point is involved in the periodical
deletion of subscriber data. See point B in the following figure.
subscriber data and notifies the HLR. Then the VLR checks whether the
subscriber subscribes to the O_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the O_CSI
intelligent subscribers in the VLR.
9-105
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.35 CAMEL Subscribers with Dialing Service
I. Entity Name
DCSI
II. Description
It is the count of the D_CSI intelligent subscribers in the VLR of the local office.

subscribes to the D_CSI intelligent service according to the CAMEL subscription
data. If so, the PVLR measures and updates the count of the D_CSI intelligent
HLR, the VLR checks whether the CAMEL type of the subscriber is the D_CSI
intelligent service. If so, the VLR updates the count of the D_CSI intelligent
9-106
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
CANCEL_LOCATION needs to be sent from the HLR to the VLR where the
subscriber is located. The VLR deletes the subscriber data after receiving the
message. At this moment, the VLR checks whether the subscriber subscribes to
the D_CSI intelligent service according to the CAMEL subscription data. If so, the
VLR measures and updates the count of the D_CSI intelligent subscribers in the
VLR.
9-107
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
z At point B, when the CAMEL service subscription data of a subscriber is deleted in

the HLR, the message MAP-INSERT-SUB-DATA or MAP-DELETE-SUB-DATA
subscribes to the D_CSI intelligent service according to the CAMEL subscription
data. If so, the VLR measures and updates the count of the D_CSI intelligent
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
subscriber subscribes to the D_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the D_CSI
9-108
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.36 MT CAMEL Subscribers in VMSC
I. Entity Name
VTCSI
II. Description
It is the count of the VT_CSI intelligent subscribers in the VLR of the local office.

subscribes to the VT_CSI intelligent service according to the CAMEL subscription
data. If so, the PVLR measures and updates the count of the VT_CSI intelligent
HLR, the VLR checks whether the CAMEL type of the subscriber is the VT_CSI
intelligent service. If so, the VLR updates the count of the VT_CSI intelligent
9-109
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
message CANCEL_LOCATION. At this moment, the VLR checks whether the
subscriber subscribes to the VT_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the VT_CSI
9-110
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted

subscribes to the VT_CSI intelligent service according to the CAMEL subscription
data. If so, the VLR measures and updates the count of the VT_CSI intelligent
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
during a period specified in the VLR configuration table, the VLR deletes the data
of the subscriber and notifies the HLR. Then the VLR checks whether the
subscriber subscribes to the VT_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the VT_CSI
9-111
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.37 CAMEL Subscribers Invoked by Supplementary Service
I. Entity Name
SSCSI
II. Description
It is the count of the SS_CSI intelligent subscribers in the VLR of the local office.

subscribes to the SS_CSI intelligent service according to the CAMEL subscription
data. If so, the PVLR measures and updates the count of the SS_CSI intelligent
HLR, the VLR checks whether the CAMEL type of the subscriber is the SS_CSI
intelligent service. If so, the VLR updates the count of the SS_CSI intelligent
9-112
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
the SS_CSI intelligent service according to the CAMEL subscription data. If so, the
VLR measures and updates the count of the SS_CSI intelligent subscribers in the
VLR.
9-113
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
z At point B, when the HLR modifies the CAMEL service subscription data of a
subscriber, it needs to send the message MAP-INSERT-SUB-DATA or
MAP-DELETE-SUB-DATA to the VLR where the subscriber is located. After
the subscriber in the VLR. At this moment, the VLR checks whether the CAMEL
type of the subscriber is the D_CSI intelligent service. If so, the VLR updates the
count of the D_CSI intelligent subscribers in the VLR.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
during a period specified in the VLR configuration table, the VLR deletes
subscriber subscribes to the SS_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the SS_CSI
9-114
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.38 SMS CAMEL Subscribers
I. Entity Name
SMSCSI
II. Description
It is the count of the SMS_CSI intelligent subscribers in the VLR of the local office.

subscribes to the SMS_CSI intelligent service according to the CAMEL
subscription data. If so, the PVLR measures and updates the count of the
SMS_CSI intelligent subscribers in the PVLR.
HLR, the VLR checks whether the CAMEL type of the subscriber is the SMS_CSI
intelligent service. If so, the VLR updates the count of the SMS_CSI intelligent
9-115
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
the SMS_CSI intelligent service according to the CAMEL subscription data. If so,
the VLR measures and updates the count of the SMS_CSI intelligent subscribers
in the VLR.
9-116
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted

subscribes to the SMS_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the SMS_CSI
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
subscriber subscribes to the SMS_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the SMS_CSI
9-117
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.39 CAMEL Subscribers with Mobile Management
I. Entity Name
MCSI
II. Description
It is the count of the M_CSI intelligent subscribers in the VLR of the local office.

subscribes to the M_CSI intelligent service according to the CAMEL subscription
data. If so, the PVLR measures and updates the count of the M_CSI intelligent
HLR, the VLR checks whether the CAMEL type of the subscriber is the M_CSI
intelligent service. If so, the VLR updates the count of the M_CSI intelligent
9-118
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
the M_CSI intelligent service according to the CAMEL subscription data. If so, the
VLR measures and updates the count of the M_CSI intelligent subscribers in the
VLR.
9-119
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted

subscribes to the M_CSI intelligent service according to the CAMEL subscription
data. If so, the VLR measures and updates the count of the M_CSI intelligent
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
subscriber subscribes to the M_CSI intelligent service according to the CAMEL
subscription data. If so, the VLR measures and updates the count of the M_CSI
9-120
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.40 ALS Subscribers
I. Entity Name
ALS
II. Description
It is the count of the ALS subscribers in the VLR of the local office.

subscribes to the ALS service. If so, the VLR updates the count of the ALS
HLR, the VLR checks the subscriber subscribes to the ALS service. Then the VLR
updates the count of the ALS subscribers in the VLR.
9-121
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
the ALS service. If so, the VLR updates the count of the ALS subscribers in the
VLR.
9-122
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
z At point B, when the basic service data of a subscriber is modified in the HLR, the
message MAP-INSERT-SUB-DATA or MAP-DELETE-SUB-DATA needs to be
sent from the HLR to the VLR where the subscriber is located. After receiving the
message, the VLR updates the basic service subscription data in the VLR. At this
moment, the VLR checks whether the subscriber subscribes to the ALS service. If
so, the VLR updates the count of the ALS subscribers in the VLR.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
subscriber subscribes to the ALS service. If so, the VLR updates the count of the
ALS subscribers in the VLR.
9-123
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.3.41 Subscribers with VP Dual Number
I. Entity Name
VPD
II. Description
It is the count of VPD subscribers in the VLR of the local office.

subscribes to the VPD service according to the basic service subscription data. If
so, the PVLR updates the count of the PVD subscribers in the PVLR.
HLR, the VLR checks the subscriber subscribes to the VPD service according to
the basic service subscription data. Then the VLR updates the count of the VPD
9-124
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
the VPD service according to the basic service subscription data. If so, the VLR
updates the count of the VPD subscribers in the VLR.
9-125
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
z At point B, when the basic service data of a subscriber is modified in the HLR, the
message MAP-INSERT-SUB-DATA or MAP-DELETE-SUB-DATA needs to be
sent from the HLR to the VLR where the subscriber is located. After receiving the
message, the VLR updates the basic service subscription data in the VLR. At this
moment, the VLR checks whether the subscriber subscribes to the VPD service
according to the basic service subscription data. If so, the VLR updates the count
of the VPD subscribers in the VLR.
VLR HLR OMC

MAP-DELETE-SUB-DATA
B
subscriber subscribes to the VPD service according to the basic service
subscription data. If so, the VLR updates the count of the VPD subscribers in the
VLR.
9-126
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.4 Location Area Traffic Distribution

9.4.1 Overview of MS_LAI_STAT
Name Description
LLUN Count of local subscribers
LRUN Count of roaming subscribers
LSOUN Count of switch-off subscribers
LULREQN Count of requesting location update
LRRULU Count of failed location update due to roaming restriction
LULREJN Count of rejected location update
LIAN Count of IMSI attach
LIDN Count of IMSI detach
LMOTCN Count of MO call attempts
LMOUERN Count of MO subscriber release before connection
LMOAUERN Count of MO subscriber release before pickup
LMOAN MO call_count of absent callee
LMOBN MO call_count of busy callee
LMOCN MO call_count of call completion
LMORN MO call_count of call answer
LMOCT MO call_traffic of call completion
LMORT MO call_traffic of call answer
9-127
Name Description
LLAIPN Count of paging
LPRN Count of paging response
LMTUERN MT call_count of release before ringing
LMTAUERN MT call_count of release during ringing
LMTCN MT call_count of call completion
LMTRN MT call_count of call answer
LMTCT MT call_traffic of call completion
LMTRT MT call_traffic of call answer
LOLAIHN Count of move-out of location area
LOLAIHSN Count of successful move-out of location area
LILAIHN Count of move-in to location area
LILAIHSN Count of successful move-in to location area
LMODCN Count of call drop by mobile caller
LMTDCN Count of call drop by mobile callee
9.4.2 Count of Local Subscribers
I. Entity Name
LLUN
II. Description
It is the count of local subscribers within the location area.

It is measured inside the VLR. Three measurement points are involved in the flow of
location update. See point A, point B and point D in the following figure.
z At point A, the VLR internally sets the subscriber type and inserts a blank record
after receiving the IMSI of a subscriber. At the moment, the VLR checks whether
the subscriber is a local one. If so, it measures and updates the count of the local
subscribers using the LAI in the VLR.
After receiving the message, the PVLR deletes the subscriber that has roamed to
another office. At the moment, the PVLR internally checks whether the subscriber
9-128
is a local one. If so, it measures and updates the count of the local subscribers
using the LAI in the PVLR.
z At point D, the VLR internally updates the subscriber type through UpdateMMInfo
after receiving the message UPDATE_LOCATION_ACK from the HLR. Then the
VLR checks whether the subscriber is a local one. If so, it measures and updates
the count of the local subscribers using the LAI in the VLR.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
One measurement point is involved in the flow of operating HLR subscriber data. See
z At point A, when a subscriber is deleted from the HLR, the message
message. At the moment, the VLR internally checks the roaming type of the
subscriber. If the subscriber is a local one, the VLR updates the count of the local
9-129
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
management of the subscribers in the VLR. See point B in the following figure.
subscriber is a local one. If so, it measures and updates the count of the local
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.4.3 Count of Roaming Subscribers
I. Entity Name
LRUN
II. Description
It is the count of roaming subscribers within the local location area.
9-130
It is measured inside the VLR. For the count of roaming subscribers and that of local
subscribers, both of whose measurement objects are subscriber type, so the
measurement points are the same, too. Three measurement points are involved in the
flow of location update. See point A, point B and point D in the following figure.
the subscriber is a roaming one. If so, it measures and updates the count of the
roaming subscribers using the LAI in the VLR.
another VLR. At the moment, the PVLR internally checks whether the subscriber
is a roaming one. If so, it measures and updates the count of the roaming
subscribers using the LAI in the PVLR.
VLR checks whether the subscriber is a roaming one. If so, it measures and
updates the count of the roaming subscribers using the LAI in the VLR.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
9-131

message. At the moment, the VLR internally checks whether the subscriber is a
roaming one. If so, it updates the count of the roaming subscribers using the LAI in
the VLR.
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
subscriber is a roaming one. If so, it measures and updates the count of the
roaming subscribers using the LAI in the VLR.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9-132
9.4.4 Count of Switch-off Subscribers
I. Entity Name
LSOUN
II. Description
It is the count of the switch-off subscribers in the local location area.

Three measurement points are involved in the flow of location update. See point A,
after receiving the IMSI of a subscriber. At the moment, the VLR measures and
updates the count of the switch-off subscribers using the LAI in the VLR.
another office. At the moment, the PVLR measures and updates the count of the
switch-off subscribers using the LAI in the PVLR.
z At point D, the VLR internally updates the subscriber status with the operation
IMSI Attached status after receiving the message UPDATE_LOCATION_ACK
from the HLR. Then the VLR measures and updates the count of the switch-off
9-133
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
message. At the moment, the VLR updates the count of the switch-off subscribers
using the LAI in the VLR.
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
Two measurement points are involved in the flow of switch-off initiated by handsets.
9-134
z At point A, when a handset sends a switch-off request through the Iu interface in

the CS domain, the MAP sets the subscriber status to IMSI Detached. At this
moment, the VLR measures the count of the switch-off subscribers using the LAI
in the VLR.
Iu-CS
MS RNS MSC VLR
IMSI-DETACH-IND
MAP-SET-IMSI-DETACH
A
MAP-SET-IMSI-DETACH-
ACK
z At point B, when the switch-off is requested from a handset through the Gs

interface in the PS domain, the MAP sends the message
BSSAP-IMSI-DETACH-IND to the VLR and sets the subscriber status to IMSI
Detached. At this moment, the VLR measures the count of the switch-off
Iu-PS
IMSI-DETACH-IND
It is measured inside the VLR. Two measurement points are involved in the periodical
management of the subscribers in the VLR. See point A and point B in the following
figure.
during a period specified in the VLR configuration table, the VLR sends the
message IMPLICIT-IMSI-DETACH to the MSC and sets the subscriber status to
9-135
IMSI Detached. In addition, it updates the count of the switch-off subscribers using
the LAI in the VLR.
VLR MSC
NOTIFY-GSMSCF
A

subscriber data and notifies the HLR. Then the VLR updates the count of the
switch-off subscribers using the LAI in the VLR.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.4.5 Count of Requesting Location Update
I. Entity Name
LULREQN
II. Description
It is the count of the location update requests in the local location area, including
periodical location update and location update due to moving into a new location area.
It is measured at point A when the MSC receives the message Location Update
Request.
9-136
RNC MSC Server
IV. Formula
None
9.4.6 Count of Failed Location Update due to Roaming Restriction
I. Entity Name
LRRULU
II. Description
It is the count of failed location update due to roaming restriction when the function of
roaming restriction is enabled.
At point B, it is measured according to the failure causes when the MSC delivers the
message Location Update Reject.
9-137
RNC MSC Server
Cause:Roaming Not Allowed in B

This Location Area
IV. Formula
None
9.4.7 Count of Rejected Location Update
I. Entity Name
LULREJN
II. Description
It is the count of rejected location update for a certain cause (for example,
authentication failed) when there is location update in the local location area.
It is measured at point B when the MSC sends the message Location Update Reject.
9-138
RNC MSC Server
IV. Formula
None
9.4.8 Count of IMSI Attach
I. Entity Name
LIAN
II. Description
It is the count of IMSI attach in the local location area.
It is measured at point A when the MSC receives the message IMSI attach.
9-139
RNC MSC Server
(Location Update Type:IMSI Attach)

A
IV. Formula
None
9.4.9 Count of IMSI Detach
I. Entity Name
LIDN
II. Description
It is the count of IMSI detach in the local location area.
It is measured at point A when the MSC receives the message IMSI detach.
9-140
RNC MSC Server
IMSI_DETACH_INDICATION
IV. Formula
None
I. Entity Name
LMOTCN
II. Description
It is the count of mobile originated calls and emergency calls in the local location area.
It is measured at point A when the MSC receives the message CM Service Request.
9-141
RNC MSC Server
CM_SERVICE_REQUEST
Service Type:MO Call,Emergency

Call A
IV. Formula
None
9.4.11 Count of MO Subscriber Release Before Connection
I. Entity Name
LMOUERN
II. Description
It is the count of calls started by MO subscribers in the local location area and released
before callees pick up the calls.
It is measured when the caller releases the call before receiving the ALERTING
message.
IV. Formula
None
9.4.12 Count of MO Subscriber Release Before Pickup
I. Entity Name
LMOAUERN
9-142
II. Description
It is the count of the calls MO subscriber releases before pickup during a call initiated in
the local location area.
It is measured when the caller releases the call after receiving the ALERTING message
and before receiving the CONNECT message.
IV. Formula
None
9.4.13 MO Call_Count of Absent Callee
I. Entity Name
LMOAN
II. Description
because the callee’s phone sets are switched off.
It is measured when the MSC receives the message MAP Absence Subscriber.
IV. Formula
None
9.4.14 MO Call_Count of Busy Callee
I. Entity Name
LMOBN
II. Description
because callees are busy.
It is measured when the internal release message is received from the MSC and the
cause value is Busy Callee.
IV. Formula
None
9-143
9.4.15 MO Call_Count of Call Completion
I. Entity Name
LMOCN
II. Description
It is the count of connected calls that are started by MSs of the local location area.
It is measured when the ALERTING message is received from the callee.
IV. Formula
None
9.4.16 MO Call_Count of Call Answer
I. Entity Name
LMORN
II. Description
It is the count of answered calls that are started by MSs of the local location area.
It is measured when the CONNECT message is received if it is an intra-office call and

the ANM message is received if it is an inter-office call.
IV. Formula
None
9.4.17 MO Call_Traffic of Call Completion
I. Entity Name
LMOCT
II. Description
It is the traffic produced by a call of an MS of the local location area from the call setup
to release.
It is measured from when the MSC sends the message DTAP Alerting to the MO and
the CM status is transferred to CM_CALL_DELIVERED until the call is released and
the CM status becomes idle. The unit is Erlang.
9-144
IV. Formula
None
9.4.18 MO Call_Traffic of Call Answer
I. Entity Name
LMORT
II. Description
It is the traffic produced by a call of an MS of the local location area from the call answer
to release.
It is measured from when the MSC sends the message DTAP Connect to the MO and
the CM status is transferred to CM_CALL_CONNECT_INDICATION until the call is
released and the CM status becomes idle. The unit is Erlang.
IV. Formula
None
9.4.19 Count of Paging
I. Entity Name
LLAIPN
II. Description
It is the count of the pagings initiated in the local location area. Multiple pagings of a call
are counted once only.
It is measured at point A when the MSC sends the PAGING message.
9-145
RNC MSC Server
PAGING
……
A
PAGING
PAGING_RESPONSE
IV. Formula
None
9.4.20 Count of Paging Response
I. Entity Name
LPRN
II. Description
It is the count of the responses of the pagings initiated in the local location area.
It is measured at point A when the MSC receives the message Paging Response.
9-146
RNC MSC Server
PAGING
……
PAGING
IV. Formula
None
9.4.21 MT Call_Count of Release Before Ringing
I. Entity Name
LMTUERN
II. Description
It is the count of the calls to subscribers in the local location area that are released by
callers before ringing.
It is measured when the release message is received from the caller before the MSC
sends the Alerting (or ACM) message to the caller.
IV. Formula
None
9.4.22 MT Call_Count of Release During Ringing
I. Entity Name
LMTAUERN
II. Description
It is the count of calls to subscribers in the local location area that are released by
callers during ringing.
9-147
It is measured when the release message is received from the caller after the Alerting
(or ACM) message has been sent to the caller and before the Connect message is
received.
IV. Formula
None
9.4.23 MT Call_Count of Call Completion
I. Entity Name
LMTCN
II. Description
It is the count of call completion when the MS of the local location area is the callee.
It is measured when the MSC sends the Alerting (or ACM) message to the caller after
receiving the Alerting message from the MS.
IV. Formula
None
9.4.24 MT Call_Count of Call Answer
I. Entity Name
LMTRN
II. Description
It is the count of calls to MSs of the local location area that are answered.
It is measured when the CONNECT/ANM message is sent to the caller after the
CONNECT message is received from the MS.
IV. Formula
None
9.4.25 MT Call_Traffic of Call Completion
I. Entity Name
LMTCT
9-148
II. Description
It is the traffic produced by calls to MSs of the local location area from the call setup to
release (including normal release and abnormal release).
It is measured from when the MSC sends the Alerting (or ACM) message to the caller
until the call is released. The unit is Erlang.
IV. Formula
None
9.4.26 MT Call_Traffic of Call Answer
I. Entity Name
LMTRT
II. Description
It is the traffic produced by calls to MSs of the local location area from the call answer to
release (including normal release and abnormal release).
It is measured from when the CONNECT message is received and the CONNECT,
ANC and ANM messages are sent to the originating office until the call is released. The
unit is Erlang.
IV. Formula
None
9.4.27 Count of Move-out of Location Area
I. Entity Name
LOLAIHN
II. Description
It is the count of handovers when MSs of the local location area are on the phone.
1) Inside the MSC: The MSC receives the message HANDOVER_REQUIRED from
the BSS_A.
2) Between MSCs:
9-149
z Basic handover: The MSC_A sends the message MAP/E

MAP_Prep_Handover_Req to the MSC_B (the measurement entity is in the
MSC_A).
z Subsequent move back to the MSC_A: The MSC_B sends the message MAP/E
MAP_Prep_Handover_Req to the MSC_A (the measurement entity is in the
MSC_B).
z Subsequent move in to the MSC_C (the third party): The MSC_B sends the
message MAP/E MAP_Prep_Sub_Handover_Req to the MSC_A (the
measurement entity is in the MSC_B).
IV. Formula
None
9.4.28 Count of Successful Move-out of Location Area
I. Entity Name
LOLAIHSN
II. Description
It is the count of successful handover to another location area when MSs of the local
location area are on the phone.
1) Inside the MSC: The MSC sends the message CLEAR_COMMAND to the
BSS_A.
2) Between MSCs:
z Basic handover: The MSC_A receives the message MAP/E MAP/E
MAP_Send_End_Signal req from the MSC_B (the MSC_B sends the message
HO_COMPLETE to the MSC_A transparently).
z Subsequent move back to the MSC_A and move into the MSC_C (the third party):
The MSC_B receives the message MAP/E MAP_Send_End_Signal Resp from
the MSC_A (the message HO_COMPLETE is sent transparently) (the cell and the
measurement entity are in the MSC_B).
IV. Formula
None
9.4.29 Count of Move-in to Location Area
I. Entity Name
LILAIHN
9-150
II. Description
It is the count of handover attempts to the local location area when MSs are under calls
in another location area.
1) Move between MSCs:

z The MSC sends the message HANDOVER_REQUEST to the BSC_B (the cell to
be observed is in the BSC_B).
z The MSC receives the message HO PERFORMED from the BSS after the
successful move in the BSC.
z Basic handover: The MSC_B receives the message MAP/E MAP_Prep_Handover
req from the MSC_A (the count entity is in the MSC_B).
z Subsequent move back to the MSC_A: The MSC_A receives the message MAP/E
MAP_Prep_Sub_Handover Req from the MSC_B (the message HO_COMPLETE
is sent transparently) (the measurement entity is in the MSC_A).
z Subsequent move into the MSC_C (the third party): The MSC_C receives the
message MAP/E MAP_Prep_Handover Req from the MSC_A (the MSC_A
forwards the message MAP/E MAP_Prep_Sub_Handover Req to the MSC_C
after receiving the message from the MSC_B) (the measurement entity is in the
MSC_C).
IV. Formula
None
9.4.30 Count of Successful Move-in to Location Area
I. Entity Name
LILAIHSN
II. Description
It is the count of successful handover to the local location area when MSs of the local
location area are on the phone in another location area.
1) Inside the MSC:

z The MSC receives the message HANDOVER_COMPLETE from the BSS_B.
2) Between MSCs:
9-151
z Basic handover: The MSC_B sends the response of the message MAP/E
MAP_Send_End_Signal req to the MSC_A (the message HO_COMPLETE is sent
transparently).
z Subsequent move back to the MSC_A: The MSC_A sends the message MAP/E
MAP_Send_End_Signal resp to the MSC_B (the message HO_COMPLETE is
sent transparently) (the measurement entity is in the MSC_A).
z Subsequent move back to the MSC_C (the third party): The MSC_C sends the
response of the message MAP/E MAP/E MAP_Send_End_Signal req to the
MSC_A (the message A_HO_COMPLETE is sent transparently) (the
measurement entity is in the MSC_C).
IV. Formula
None
9.4.31 Count of Call Drop by Mobile Caller
I. Entity Name
LMODCN
II. Description
It is the count of call drops due to causes of mobile callers when subscribers of the local
location area are the caller.
It is measured at point A when the MSC receives the message Iu RELEASE REQUEST
from the RNC or the message CLEAR REQUEST from the BSC.
9-152
RNC MSC Server
RELEASE_REQUEST
IV. Formula
None
9.4.32 Count of Call Drop by Mobile Callee
I. Entity Name
LMTDCN
II. Description
It is the count of call drops due to causes of mobile callees when subscribers of the
local location area are the callee.
9-153
RNC MSC Server
RELEASE_REQUEST
IV. Formula
None
9.5 Cell Traffic Distribution

9.5.1 Overview of MS_GCI_STAT
Name Description
GLUN Count of local subscribers
GRUN Count of roaming subscribers
LSOUN Count of switch-off subscribers
GULREQN Count of requesting location update
GULREJN Count of rejected location update
GIAN Count of IMSI attach
GIDN Count of IMSI detach
GMOTCN Count of MO call attempts
GMOUERN Count of MO subscriber release before connection
GMOAUERN Count of MO subscriber release before pickup
GMOAN MO call_count of absent callee
GMOBN MO call_count of busy callee
GMOCN MO call_count of call completion
9-154
Name Description
GMORN MO call_count of call answer
GMOCT MO call_traffic of call completion
GMORT MO call_traffic of call answer
GMTUERN MT call_count of release before ringing
GMTAUERN MT call_count of release during ringing
GMTCN MT call_count of call completion
GMTRN MT call_count of call answer
GMTCT MT call_traffic of call completion
GMTRT MT call_traffic of call answer
GOLAIHN Count of move-out of cell
GOLAIHSN Count of successful move-out of cell
GILAIHN Count of move-in to cell
GILAIHSN Count of successful move-in to cell
GMODCN Count of call drop by mobile caller

GMTDCN Count of call drop by mobile callee
9.5.2 Count of Local Subscribers
I. Entity Name
GLUN
II. Description
It is the count of local subscribers within the cell.

It is measured inside the VLR. Three measurement points are involved in the flow of
location update. See point A, point B and point D in the following figure.
the subscriber is a local one. If so, it measures and updates the count of the local
subscribers using the GCI in the VLR.
9-155
another office. At the moment, the PVLR internally checks whether the subscriber
is a local one. If so, it measures and updates the count of the local subscribers
using the GCI in the PVLR.
VLR checks whether the subscriber is a local one. If so, it measures and updates
the count of the local subscribers using the GCI in the VLR.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
message. At the moment, the VLR internally checks the roaming type of the
subscriber. If the subscriber is a local one, the VLR updates the count of the local
9-156
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
management of the subscribers in the VLR. See point B in the following figure.
subscriber is a local one. If so, it measures and updates the count of the local
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.5.3 Count of Roaming Subscribers
I. Entity Name
GRUN
II. Description
It is the count of roaming subscribers within the local cell.
9-157
It is measured inside the VLR. For the count of roaming subscribers and that of local
subscribers, both of whose measurement objects are subscriber type, so the
measurement points are the same, too. Three measurement points are involved in the
flow of location update. See point A, point B and point D in the following figure.
the subscriber is a roaming one. If so, it measures and updates the count of the
roaming subscribers using the GCI in the VLR.
another VLR. At the moment, the PVLR internally checks whether the subscriber
is a roaming one. If so, it measures and updates the count of the roaming
subscribers using the GCI in the PVLR.
VLR checks whether the subscriber is a roaming one. If so, it measures and
updates the count of the roaming subscribers using the GCI in the VLR.
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
9-158

message. At the moment, the VLR internally checks whether the subscriber is a
roaming one. If so, it updates the count of the roaming subscribers using the GCI
in the VLR.
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
subscriber is a roaming one. If so, it measures and updates the count of the
roaming subscribers using the GCI in the VLR.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9-159
9.5.4 Count of Switch-off Subscribers
I. Entity Name
LSOUN
II. Description
It is the count of the switch-off subscribers in the local cell.

Three measurement points are involved in the flow of location update. See point A,
after receiving the IMSI of a subscriber. At the moment, the VLR measures and
updates the count of the switch-off subscribers using the LAI in the VLR.
another office. At the moment, the PVLR measures and updates the count of the
switch-off subscribers using LAI in the PVLR.
z At point D, the VLR internally updates the subscriber status with the operation
IMSI Attached status after receiving the message UPDATE_LOCATION_ACK
from the HLR. Then the VLR measures and updates the count of the switch-off
subscribers using LAI in the VLR.
9-160
MSC VLR PVLR HLR
AREA
MAP-PROVIDE-IMSI
A
MAP-UPDATE-LOCATION
MAP-CANCEL-LOCATION
B
C
AREA-ACK
message. At the moment, the VLR updates the count of the switch-off subscribers
using LAI in the VLR.
VLR HLR OMC

MAP-CANCEL-LOCATION
A
deleted
Two measurement points are involved in the flow of switch-off initiated by handsets.
9-161
z At point A, when a handset sends a switch-off request through the Iu interface in

the CS domain, the MAP sets the subscriber status to IMSI Detached. At this
moment, the VLR measures the count of the switch-off subscribers using LAI in
the VLR.
Iu-CS
MS RNS MSC VLR
IMSI-DETACH-IND
MAP-SET-IMSI-DETACH
A
MAP-SET-IMSI-DETACH-
ACK
z At point B, when the switch-off is requested from a handset through the Gs

interface in the PS domain, the MAP sends the message
BSSAP-IMSI-DETACH-IND to the VLR and sets the subscriber status to IMSI
Detached. At this moment, the VLR measures the count of the switch-off
subscribers using LAI in the VLR.
Iu-PS
IMSI-DETACH-IND
It is measured inside the VLR. Two measurement points are involved in the periodical
management of the subscribers in the VLR. See point A and point B in the following
figure.
during a period specified in the VLR configuration table, the VLR sends the
message IMPLICIT-IMSI-DETACH to the MSC and sets the subscriber status to
IMSI Detached. In addition, it updates the count of the switch-off subscribers using
LAI in the VLR.
9-162
VLR MSC
NOTIFY-GSMSCF
A

subscriber data and notifies the HLR. Then the VLR updates the count of the
switch-off subscribers using LAI in the VLR.
VLR MSC HLR
MAP-PURGY-MS
MAP-PURGY-MS
B
MAP-PURGY-MS-ACK
MAP-PURGY-MS-ACK
IV. Formula
None
9.5.5 Count of Requesting Location Update
I. Entity Name
GULREQN
II. Description
It is the count of the location update requests in the local cell, including periodical
location update and location update due to move into a new cell.
It is measured at point A when the MSC receives the message Location Update
Request.
9-163
RNC MSC Server
IV. Formula
None
9.5.6 Count of Rejected Location Update
I. Entity Name
GULREJN
II. Description
It is the count of rejected location update for a certain cause (for example,
authentication failed) when there is location update in the local cell.
It is measured at point B when the MSC sends the message Location Update Reject.
9-164
RNC MSC Server
IV. Formula
None
9.5.7 Count of IMSI Attach
I. Entity Name
GIAN
II. Description
It is the count of IMSI attach in the local cell.
It is measured at point A when the MSC receives the message IMSI attach.
9-165
RNC MSC Server
(Location Update Type:IMSI Attach)

A
IV. Formula
None
9.5.8 Count of IMSI Detach
I. Entity Name
GIDN
II. Description
It is the count of IMSI detach in the local cell.
It is measured at point A when the MSC receives the message IMSI detach.
9-166
RNC MSC Server
IMSI_DETACH_INDICATION
IV. Formula
None
I. Entity Name
GMOTCN
II. Description
It is the count of mobile originated calls and emergency calls in the local cell.
It is measured at point A when the MSC receives the message CM Service Request.
9-167
RNC MSC Server
CM_SERVICE_REQUEST
Service Type:MO Call,Emergency

Call A
IV. Formula
None
9.5.10 Count of MO Subscriber Release Before Connection
I. Entity Name
GMOUERN
II. Description
It is the count of calls started by MO subscribers in the local cell and released before the
MSC receives the ALERTING message.
It is measured when the release message is received from the MO subscriber before
the MSC receives the ALERTING message,
IV. Formula
None
9.5.11 Count of MO Subscriber Release Before Pickup
I. Entity Name
GMOAUERN
9-168
II. Description
It is the count of calls started by MO subscribers in the local cell and released after the
MSC receives the ALERTING message.
It is measured when the release message is received from the MO subscriber after the
ALERTING message is received.
IV. Formula
None
9.5.12 MO Call_Count of Absent Callee
I. Entity Name
GMOAN
II. Description
It is the count of calls started by MO subscribers in the local cell and released because
the callees' phone sets are switched off.
It is measured when the MSC receives the message MAP Absence Subscriber.
IV. Formula
None
9.5.13 MO Call_Count of Busy Callee
I. Entity Name
GMOBN
II. Description
It is the count of calls started by MO subscribers in the local cell and released because
the callees are busy.
It is measured when the MO receives the release message and and the cause value is
Busy Callee.
IV. Formula
None
9-169
9.5.14 MO Call_Count of Call Completion
I. Entity Name
GMOCN
II. Description
It is the count of connected calls that are started by MSs of the local cell.
It is measured when the MSC receives the ALERTING message.
IV. Formula
None
9.5.15 MO Call_Count of Call Answer
I. Entity Name
GMORN
II. Description
It is the count of answered calls that are started by MSs of the local cell.
It is measured when the caller receives the CONNECT message.
IV. Formula
None
9.5.16 MO Call_Traffic of Call Completion
I. Entity Name
GMOCT
II. Description
It is the traffic produced by a call of an MS of the local cell from the call setup to release.
It is measured from when the caller receives the Alerting message until the call is
released.
IV. Formula
None
9-170
9.5.17 MO Call_Traffic of Call Answer
I. Entity Name
GMORT
II. Description
It is the traffic produced by a call of an MS of the local cell from the call answer to
release.
It is measured from when the CONNECT message is received until the call is released.
IV. Formula
None
9.5.18 MT Call_Count of Release Before Ringing
I. Entity Name
GMTUERN
II. Description
It is the count of calls to subscribers in the local cell that are released by callers before
ringing.
It is measured when the MlSC receives the release message from the caller before
sending the Alerting (or TUP ACM) message to the caller.
IV. Formula
None
9.5.19 MT Call_Count of Release During Ringing
I. Entity Name
GMTAUERN
II. Description
It is the count of calls to subscribers in the local cell that are released by callers during
ringing.
9-171
It is measured when the release message is received from the caller after the Alerting
(or ACM) message has been sent to the caller and before the Connect message is
received (the ANC message and ANM message are sent to the originating office).
IV. Formula
None
9.5.20 MT Call_Count of Call Completion
I. Entity Name
GMTCN
II. Description
It is the count of call completion when the MS of the local cell is the callee.
It is measured when the MSC sends the Alerting (ACM) message to the caller.
IV. Formula
None
9.5.21 MT Call_Count of Call Answer
I. Entity Name
GMTRN
II. Description
It is the count of calls to MSs of the local cell that are answered.
It is measured when the Connect message is received (the ANC message and the
ANM message are sent to the originating office).
IV. Formula
None
9.5.22 MT Call_Traffic of Call Completion
I. Entity Name
GMTCT
9-172
II. Description
It is the traffic produced by calls to MSs of the local cell from the call setup to release
(including normal release and abnormal release).
It is measured from when the MSC sends the Alerting (or ACM) message to the caller
until the call is released. The unit is Erlang.
IV. Formula
None
9.5.23 MT Call_Traffic of Call Answer
I. Entity Name
GMTRT
II. Description
It is the traffic produced by calls to MSs of the local cell from the call answer to release
(including normal release and abnormal release).
It is measured from when the CONNECT message is received (or the ANC and ANM
messages are sent to the originating office) until the call is released. The unit is Erlang.
IV. Formula
None
9.5.24 Count of Move-out of Cell
I. Entity Name
GOLAIHN
II. Description
It is the count of handovers when MSs of the local cell are on the phone. The index is
effective for the GSM cell only.
1) Inside the MSC: The MSC receives the message HANDOVER_REQUIRED from
the BSS_A.
2) Between MSCs:
9-173
z Basic handover: The MSC_A sends the message MAP/E

MAP_Prep_Handover_Req to the MSC_B (the measurement entity is in the
MSC_A).
z Subsequent move back to the MSC_A: The MSC_B sends the message MAP/E
MAP_Prep_Handover_Req to the MSC_A (the measurement entity is in the
MSC_B).
z Subsequent move in to the MSC_C (the third party): The MSC_B sends the
message MAP/E MAP_Prep_Sub_Handover_Req to the MSC_A (the
measurement entity is in the MSC_B).
IV. Formula
None
9.5.25 Count of Successful Move-out of Cell
I. Entity Name
GOLAIHSN
II. Description
It is the count of successful handovers to another cell when MSs of the local cell are on
the phone. The index is effective for the GSM cell only.
1) Inside the MSC: The MSC sends the message CLEAR_COMMAND to the
BSS_A.
2) Between MSCs:
z Basic handover: The MSC_A receives the message MAP/E MAP/E
MAP_Send_End_Signal req from the MSC_B (the MSC_B sends the message
A_HO_COMPLETE to the MSC_A transparently).
z Subsequent move back to the MSC_A and move into the MSC_C (the third party):
The MSC_B receives the message MAP/E MAP_Send_End_Signal Resp from
the MSC_A (the message HO_COMPLETE is sent transparently) (the cell and the
measurement entity are in the MSC_B).
IV. Formula
None
9.5.26 Count of Move-in to Cell
I. Entity Name
GILAIHN
9-174
II. Description
It is the count of handover attempts to the local cell when MSs are under calls in
another cell. The index is effective for the GSM cell only.

z The MSC sends the message HANDOVER_REQUEST to the BSC_B (the cell to
be observed is in the BSC_B).
z Basic handover: The MSC_B receives the message MAP/E MAP_Prep_Handover
req from the MSC_A (the count entity is in the MSC_B).
z Subsequent move back to the MSC_A: The MSC_A receives the message MAP/E
MAP_Prep_Sub_Handover Req from the MSC_B (the message HO_COMPLETE
is sent transparently) (the measurement entity is in the MSC_A).
IV. Formula
None
9.5.27 Count of Successful Move-in to Cell
I. Entity Name
GILAIHSN
II. Description
It is the count of successful move-in to the local cell when MSs of the local cell are on
the phone in another cell. The index is effective for the GSM cell only.
1) Inside the MSC:

z The MSC receives the message HANDOVER_COMPLETE from the BSS_B.
2) Between MSCs:
z Basic handover: The MSC_B sends the response of the message MAP/E
MAP_Send_End_Signal req to the MSC_A (the message A_HO_COMPLETE is
sent transparently).
z Subsequent move back to the MSC_A: The MSC_A sends the message MAP/E
MAP_Send_End_Signal resp to the MSC_B (the message HO_COMPLETE is
sent transparently) (the measurement entity is in the MSC_C).
9-175
IV. Formula
None
9.5.28 Count of Call Drop by Mobile Caller
I. Entity Name
GMODCN
II. Description
It is the count of call drops due to causes of mobile callers when subscribers of the local
cell are the caller.
RNC MSC Server
RELEASE_REQUEST
IV. Formula
None
9.5.29 Count of Call Drop by Mobile Callee
I. Entity Name
GMTDCN
9-176
II. Description
It is the count of call drops due to causes of mobile callees when subscribers of the
local cell are the callee.
RNC MSC Server
RELEASE_REQUEST
IV. Formula
None
9.6 Count of MVNO Subscribers

9.6.1 Overview of MS_VDB_MVNO_SUB
The name and meanings of the measurement entity are listed in the following table.
Name Description
MVNO Count of MVNO subscribers
9.6.2 Count of MVNO Subscribers
I. Entity Name
MVNO
9-177
II. Description
It is the count of MVNO subscribers in the local office. You can measure number of all
MVNO subscribers or number of specific subscribers according to entered MVNO
serial numbers.
After the MVNO function is enabled and the MVNO limit mode table is configured with
the MVNO total number limit mode or single MVNO limit mode, the VDB measures
number of MVNO subscribers whose locations are updated to the local office.
IV. Formula
None
9-178
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 10 Signaling and Interfaces
Chapter 10 Signaling and Interfaces

This measurement set is used to effectively manage, evaluate and utilize signaling
network resources.
Name Description
MS_TYPE_A_PROTOCOL_ERR A-interface signaling procedure error
MS_BICCMSG BICC SCTP link
MS_BICC_NODE_CAPABILITY BICC node capability
MS_TYPE_BSC Base station controller

MS_TYPE_GPRS_TIMEOUT GPRS timeout
MS_TYPE_GS_OPER Gs-interface operation
MS_TYPE_GS_ERR Gs-interface error cause
MS_H248_MGW_TRAFIC H.248 MGW
MS_H248_SCTPLNK_TRAFIC H.248 SCTP link
MS_IFM_IPFLOW_TRAF IP port traffic
MS_ISUP_TKGRP_PERFORM_TRAF ISUP circuit group
MS_ISUP_NODE_PERFORM_TRAF ISUP node
MS_ISUP_NET_PERFORM_TRAF ISUP network
MS_ISUP_MSG_USING_TRAF ISUP message usage
MS_ISUP_TOTAL_MSU_TRAF Count of ISUP messages
MS_ISUP_UNUSUAL_TRAF ISUP abnormality
MS_IUA_LS_TRAF IUA link set
MS_IUA_LINK_TRAF IUA signaling link
MS_M2UA_LS_TRAF M2UA link set

MS_M2UA_LINK_TRAF M2UA link
MS_M3UA_DEST_ENTITY_TRAF M3UA destination entity
MS_M3UA_LINK_TRAF M3UA signaling link

MS_M3UA_LS_TRAF M3UA signaling link set
MS_TYPE_MAP_PUBLIC_SERVICE MAP public service procedure error
10-1
Name Description
MS_TYPE_MAP_OPERATION MAP operation
MS_MTP3B_LINK_TRAF MTP3B signaling link
MS_MTP3B_LINKSET_TRAF MTP3B signaling link set
MS_MTP3B_DSP_TRAF MTP3B destination signaling point
MS_MTP_DSP_TRAF MTP destination signaling point
MS_MTP_LINK_TRAF MTP signaling link
MS_MTP_LINKSET_TRAF MTP signaling link set
MS_SAAL_LINK_TRAF SAAL signaling link
MS_SCCP_AVAILABILITY SCCP availability
MS_SCCP_UTILIZATION SCCP usage
MS_SCCP_FLUX_TRAFFIC SCCP traffic
MS_SCCP_PERFORMANCE SCCP performance
MS_TCAP_CSL_PERFORMANCE TCAP CSL
MS_TCAP_TSL_PERFORMANCE TCAP transport sublayer

MS_TCAP_AVAILABILITY TCAP availability
MS_TCAP_MSG_UTILIZATION Count of TCAP messages
MS_TCAP_CMP_UTILIZATION TCAP component utilization

MS_TUP_TKGRP_PERFORM_TRAF TUP circuit group
MS_TUP_NODE_PERFORM_TRAF TUP node
MS_TUP_NET_PERFORM_TRAF TUP network
MS_TUP_MSG_USING_TRAF TUP message application
MS_TUP_TOTAL_MSU_TRAF Count of TUP messages
MS_TUP_UNUSUAL_TRAF TUP abnormity
MS_TYPE_UNION_LOC_UP Union location update rejected cause
10-2
10.2 A-Interface Signaling Procedure Error

10.2.1 Overview of MS_TYPE_A_PROTOCOL_ERR
Name Description
Count of received messages with cause of radio interface message
UMFU48
failure
Count of sent messages with cause of radio interface message

UMFD48
failure
UFU48 Count of received messages with cause of radio interface failure
UFD48 Count of sent messages with cause of radio interface failure
IMCU48 Count of received messages with cause of invalid message content

IMCD48 Count of sent messages with cause of invalid message content
Count of received messages with cause of information element or
IMFMU48
field missing
Count of sent messages with cause of information element or field
IMFMD48
missing
EVU48 Count of received messages with cause of incorrect value
EVD48 Count of sent messages with cause of incorrect value
UMTU48 Count of received messages with cause of unknown message type
UMTD48 Count of sent messages with cause of unknown message type
Count of received messages with cause of unknown information
UIU48
element
Count of sent messages with cause of unknown information

UID48
element
PEU48 Count of received messages with cause of protocol error

PED48 Count of sent messages with cause of protocol error
Count of received messages with cause of terrestrial circuit already
TCAU48
allocated
Count of sent messages with cause of terrestrial circuit already
TCAD48
allocated
10-3
10.2.2 Count of Received Messages with Cause of Radio Interface Message

Failure
I. Entity Name
UMFU48
II. Description
This cause value indicates that the BSC fails to wait for the response from the radio
interface due to timeout, for example, no response from the assigned radio interface.
It is measured when the MSC finds out that the cause value is "Radio Interface
Message Failure" after receiving the message Assignment Failure, Handover Failure,
or Clear Request from the BSC.
BSC MSC Server
ASSIGNMENT REQUEST
ASSIGNMENT FAILURE A
HANDOVER REQUEST
HANDOVER FAILURE A
CLEAR REQUEST A
IV. Formula
None
10.2.3 Count of Sent Messages with Cause of Radio Interface Message

Failure
I. Entity Name
UMFD48
10-4
II. Description
The MSC sends the message Clear Command to the BSC with the cause of “Radio
Interface Message Failure”. (Refer to the previous entity.) The MSC does not use this
cause value on initiative.
It is measured when the MSC sends the message Clear Command to the BSC. See
IV. Formula
None
10.2.4 Count of Received Messages with Cause of Radio Interface Failure
I. Entity Name
UFU48
II. Description
Faults, except radio interface message failure and direct retry, occur during procedures
like control and assignment.
It is measured when the MSC finds out that the cause value is "Radio Interface Failure"
after receiving the message Assignment Failure, Handover Failure, Clear Request,
Confusion, or SAPI “n” Reject from the BSC.
10-5
BSC MSC Server
ASSIGNMENT REQUEST
HANDOVER REQUEST
HANDOVER FAILURE A
IV. Formula
None
10.2.5 Count of Sent Messages with Cause of Radio Interface Failure
I. Entity Name
UFD48
II. Description
The MSC sends the message Clear Command to the BSC with the cause of “Radio
Interface Failure”. (Refer to the previous entity.) The MSC does not use this cause
value on initiative.
It is measured when the MSC sends the message Clear Command that contains the
cause value “Radio Interface Failure” to the BSC.
10-6
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10.2.6 Count of Received Messages with Cause of Invalid Message Content
I. Entity Name
IMCU48
II. Description
The BSC cannot recognize the content of the messages from the MSC.
It is measured when the MSC finds out that the cause value is "Invalid Message
Contents" after receiving the message Assignment Failure, Handover Failure, Clear
Request, Confusion, or SAPI “n” Reject from the BSC.
10-7
BSC MSC Server
ASSIGNMENT REQUEST
HANDOVER REQUEST
HANDOVER FAILURE A
CONFUSION A
IV. Formula
None
10.2.7 Count of Sent Messages with Cause of Invalid Message Content
I. Entity Name
IMCD48
II. Description
The MSC cannot recognize the content of the messages from the BSC.
cause value “Invalid Message Contents” to the BSC.
10-8
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10.2.8 Count of Received Messages with Cause of Information Element or

Field Missing
I. Entity Name
IMFMU48
II. Description
When analyzing a message from the MSC, the BSC finds that the mandatory IE is lost.
It is measured when the MSC finds out that the cause value is "Information Element or
Field Missing" after receiving the message Confusion from the BSC.
BSC MSC Server
CONFUSION A
IV. Formula
None
10-9
10.2.9 Count of Sent Messages with Cause of Information Element or Field

Missing
I. Entity Name
IMFMD48
II. Description
When analyzing a message from the BSC, the MSC finds that the mandatory IE is lost.
cause value “Information Element or Field Missing” to the BSC.
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10.2.10 Count of Received Messages with Cause of Incorrect Value
I. Entity Name
EVU48
II. Description
When analyzing a message from the MSC, the BSC finds that the IE value is wrong.
It is measured when the MSC finds out that the cause value is "Incorrect Value" after
receiving the message Confusion from the BSC.
10-10
BSC MSC Server
CONFUSION A
IV. Formula
None
10.2.11 Count of Sent Messages with Cause of Incorrect Value
I. Entity Name
EVD48
II. Description
When analyzing a message from the BSC, the MSC finds that the IE value is wrong.
cause value “Incorrect Value” to the BSC.
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10-11
10.2.12 Count of Received Messages with Cause of Unknown Message Type
I. Entity Name
UMTU48
II. Description
The BSC cannot recognize the type of a message from the MSC.
It is measured when the MSC finds out that the cause value is "Unknown Message
type" after receiving the message Confusion from the BSC.
BSC MSC Server
CONFUSION A
IV. Formula
None
10.2.13 Count of Sent Messages with Cause of Unknown Message Type
I. Entity Name
UMTD48
II. Description
The MSC cannot recognize the type of a message from the BSC.
cause value “Unknown Message type” to the BSC.
10-12
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10.2.14 Count of Received Messages with Cause of Unknown Information

Element
I. Entity Name
UIU48
II. Description
The BSC cannot recognize the IE of a message from the MSC.
It is measured when the MSC finds out that the cause value is "Unknown Information
Element" after receiving the message Confusion from the BSC.
BSC MSC Server
CONFUSION A
IV. Formula
None
10-13
10.2.15 Count of Sent Messages with Cause of Unknown Information

Element
I. Entity Name
UID48
II. Description
The MSC cannot recognize the IE of a message from the BSC.
cause value “Unknown Information Element” to the BSC.
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10.2.16 Count of Received Messages with Cause of Protocol Error
I. Entity Name
PEU48
II. Description
A message received by the BSC is not consistent with the state of the signaling
connection or sent in the wrong direction, or the wrong SCCP service primitive is used.
It is measured when the MSC finds out that the cause value is "Protocol Error between
BSS and MSC" after receiving the message Clear Request or Confusion from the BSC.
10-14
BSC MSC Server
CONFUSION A
CLEAR REQUEST A
IV. Formula
None
10.2.17 Count of Sent Messages with Cause of Protocol Error
I. Entity Name
PED48
II. Description
A message received by the MSC is not consistent with the state of the signaling
connection or sent in the wrong direction, or the wrong SCCP service primitive is used.
cause value “Protocol Error between BSS and MSC” to the BSC.
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10-15
10.2.18 Count of Received Messages with Cause of Terrestrial Circuit

Already Allocated
I. Entity Name
TCAU48
II. Description
The circuit resource allocated by the MSC is occupied at the BSC. This occurs when
the circuit states on the two sides of the A-interface are inconsistent.
It is measured when the MSC finds out that the cause value is "Terrestrial Circuit
Already Allocated" after receiving the message Assignment Failure from the BSC.
BSC MSC Server
ASSIGNMENT REQUEST
IV. Formula
None
10.2.19 Count of Sent Messages with Cause of Terrestrial Circuit Already

Allocated
I. Entity Name
TCAD48
II. Description
The MSC sends the message Clear Command to the BSC with the cause of “Terrestrial
Circuit Already Allocated”. (Refer to the previous entity.) The MSC does not use this
cause value on initiative.
10-16
cause value “Terrestrial Circuit Already Allocated” to the BSC.
BSC MSC Server
CLEAR COMMAND
IV. Formula
None
10.3 BICC SCTP Link

10.3.1 Overview of MS_BICCMSG
Name Description
DISCNT Count of link disconnections
DISDUR Duration of link disconnections
CONGCNT Count of link congestion
CONGDUR Duration of link congestion
SNDMSG Count of messages sent
SNDBYTE Count of bytes in messages sent
RCVMSG Count of messages received
RCVBYTE Count of bytes in messages received
SNDRATE Count of messages sent per second

RCVRATE Count of messages received per second
SNDBITR Count of bits sent per second
RCVBITR Count of bits received per second
10-17
10.3.2 Count of Link Disconnections
I. Entity Name
DISCNT
II. Description
It is the count of disconnections of the BICC SCTP link.
It is measured when the BICC SCTP link is disconnected.
IV. Formula
None
10.3.3 Duration of Link Disconnections
I. Entity Name
DISDUR
II. Description
It is the duration of disconnections of the BICC SCTP link.
It is measured when the BICC SCTP link is disconnected. The duration is accumulated.
IV. Formula
None
10.3.4 Count of Link Congestion
I. Entity Name
CONGCNT
II. Description
It is the count of congestion on the BICC SCTP link.
It is measured when the BICC SCTP link is congested.
IV. Formula
None
10-18
10.3.5 Duration of Link Congestion
I. Entity Name
CONGDUR
II. Description
It is the duration of congestion on the BICC SCTP link.
It is measured when the BICC SCTP link is disconnected. The duration is accumulated.
IV. Formula
None
10.3.6 Count of Messages Sent
I. Entity Name
SNDMSG
II. Description
It is the count of messages sent through the BICC SCTP link.
It is measured when BICC sends messages through the SCTP link.
IV. Formula
None
10.3.7 Count of Bytes in Messages Sent
I. Entity Name
SNDBYTE
II. Description
It is the count of bytes in messages sent through the BICC SCTP link.
IV. Formula
None
10-19
10.3.8 Count of Messages Received
I. Entity Name
RCVMSG
II. Description
It is the count of messages received through the BICC SCTP link.
It is measured when BICC receives messages through the SCTP link.
IV. Formula
None
10.3.9 Count of Bytes in Messages Received
I. Entity Name
RCVBYTE
II. Description
It is the count of bytes in messages received through the BICC SCTP link.
IV. Formula
None
10.3.10 Count of Messages Sent per Second
I. Entity Name
SNDRATE
II. Description
It is the count of messages sent through the BICC SCTP link every second.
IV. Formula
None
10-20
10.3.11 Count of Messages Received per Second
I. Entity Name
RCVRATE
II. Description
It is the count of messages received through the BICC SCTP link every second.
IV. Formula
None
10.3.12 Count of Bits Sent per Second
I. Entity Name
SNDBITR
II. Description
It is the count of bits sent through the BICC SCTP link every second.
IV. Formula
None
10.3.13 Count of Bits Received per Second
I. Entity Name
RCVBITR
II. Description
It is the count of bits received through the BICC SCTP link every second.
IV. Formula
None
10-21
10.4 BICC Node Capability

10.4.1 Overview of MS_BICC_NODE_CAPABILITY
Name Description
IPEGS Count of incoming call attempts
SEC Count of call failures due to switching equipment congestion
CGC Count of call failures due to no valid circuit
ADI Count of call failures due to address incomplete

TMPFL Count of call failures due to temporary failure
UNN Count of call failures due to unallocated number
SB Count of call failures due to callee busy

DPCFL Count of call failures due to destination fault
OTHFL Count of call failures due to other causes
10.4.2 Count of Incoming Call Attempts
I. Entity Name
IPEGS
II. Description
It is the count of BICC incoming call attempts.
It is measured when the MSC receives the IAM.

10-22
IAM
IV. Formula
None
10.4.3 Count of Call Failures Due to Switching Equipment Congestion
I. Entity Name
SEC
II. Description
It is the count of BICC call failures due to equipment congestion.
It is measured when BICC sends the REL message with the cause of “switching
equipment congestion (0101010)”.
10-23
IAM
REL
A
IV. Formula
None
10.4.4 Count of Call Failures Due to No Valid Circuit
I. Entity Name
CGC
II. Description
It is the count of BICC call failures due to no idle CIC.
It is measured when BICC sends the REL message with the cause of “no valid circuit
(0100010)”.
10-24
IAM
REL
IV. Formula
None
10.4.5 Count of Call Failures Due to Address Incomplete
I. Entity Name
ADI
II. Description
It is the count of BICC call failures due to address incomplete.
It is measured when BICC sends the REL message with the cause of “address
incomplete (0011100)”.
10-25
IAM
REL
IV. Formula
None
10.4.6 Count of Call Failures Due to Temporary Failure
I. Entity Name
TMPFL
II. Description
It is the count of BICC call failures due to temporary failure.
It is measured when BICC sends the REL message with the cause of “temporary failure
(0101001)”.
10-26
IAM
REL
IV. Formula
None
10.4.7 Count of Call Failures Due to Unallocated Number
I. Entity Name
UNN
II. Description
It is the count of BICC call failures due to the called number unallocated.
It is measured when BICC sends the REL message with the cause of “unallocated
number (0000001)”.
10-27
IAM
REL
IV. Formula
None
10.4.8 Count of Call Failures Due to Callee Busy
I. Entity Name
SB
II. Description
It is the count of BICC call failures due to callee busy.
It is measured when BICC sends the REL message with the cause of “subscriber busy
(0010001)”.
10-28
IAM
REL
IV. Formula
None
10.4.9 Count of Call Failures Due to Destination Fault
I. Entity Name
DPCFL
II. Description
It is the count of BICC call failures due to destination entity unreachable.
It is measured when BICC sends the REL message with the cause of “destination
unreachable (0011011)” or “destination incompatible (1011000)”.
10-29
IAM
REL
IV. Formula
None
10.4.10 Count of Call Failures Due to Other Causes
I. Entity Name
OTHFL
II. Description
It is the count of BICC call failures due to other causes.
It is measured when BICC sends the REL message with the cause not listed above.
10-30
IAM
REL
IV. Formula
None
10.5 Base Station Controller

10.5.1 Overview of MS_TYPE_BSC
Name Description
TRAB31 Count of reset messages from BSC
TRAM31 Count of circuit reset messages from MSC
TRCAB31 Count of circuit reset messages from BSC
TBCAB31 Count of circuit blocking messages from BSC
TUCAB31 Count of circuit unblocking messages from BSC
TBCGAB31 Count of circuit group blocking messages from BSC
TUCGAB31 Count of circuit group unblocking messages from BSC
TOAB31 Count of overload messages from BSC

TUCAM31 Count of unequipped circuit messages from MSC
TUCABS31 Count of unequipped circuit messages from BSC
TSMR31 Count of SAPI “N” rejection messages

TCMB31 Count of confusion messages from BSC
TCMM31 Count of confusion messages from MSC
10-31
10.5.2 Count of Reset Messages from BSC
I. Entity Name
TRAB31
II. Description
The BSC fails and sends the RESET message to the MSC to release all connections.
It is measured when the MSC receives the RESET message from the BSC.
BSC MSC Server
RESET
IV. Formula
None
10.5.3 Count of Circuit Reset Messages from MSC
I. Entity Name
TRAM31
II. Description
The MSC sends the RESET CIRCUIT message to the BSC to release a circuit due to
manual intervention or equipment failure.
It is measured when the MSC sends the message RESET CIRCUIT to the BSC.
10-32
BSC MSC Server
RESET CIRCUIT
IV. Formula
None
10.5.4 Count of Circuit Reset Messages from BSC
I. Entity Name
TRCAB31
II. Description
The BSC sends the RESET CIRCUIT message to the MSC to release a circuit due to
manual intervention or equipment failure.
It is measured when the MSC receives the message RESET CIRCUIT from the BSC.
BSC MSC Server
RESET CIRCUIT
IV. Formula
None
10.5.5 Count of Circuit Blocking Messages from BSC
I. Entity Name
TBCAB31
10-33
II. Description
The MSC receives the BLOCK message.
It is measured when the MSC receives the BLOCK message from the BSC.
BSC MSC Server
BLOCK
IV. Formula
None
10.5.6 Count of Circuit Unblocking Messages from BSC
I. Entity Name
TUCAB31
II. Description
The BSC sends the UNBLOCK message to the MSC to enable a circuit.
It is measured when the MSC receives the UNBLOCK message from the BSC.
10-34
BSC MSC Server
UNBLOCK
IV. Formula
None
10.5.7 Count of Circuit Group Blocking Messages from BSC
I. Entity Name
TBCGAB31
II. Description
The BSC sends the message CIRCUIT GROUP BLOCK to the MSC to disable a group
of circuits.
It is measured when the MSC receives the message CIRCUIT GROUP BLOCK from
the BSC.
BSC MSC Server
CIRCUIT GROUP BLOCK
IV. Formula
None
10-35
10.5.8 Count of Circuit Group Unblocking Messages from BSC
I. Entity Name
TUCGAB31
II. Description
The BSC sends the message CIRCUIT GROUP UNBLOCK to the MSC to enable a
group of circuits.
It is measured when the MSC receives the message CIRCUIT GROUP UNBLOCK
from the BSC.
BSC MSC Server
CIRCUIT GROUP UNBLOCK
IV. Formula
None
10.5.9 Count of Overload Messages from BSC
I. Entity Name
TOAB31
II. Description
The BSC sends the OVERLOAD message to the MSC when the CPU or CCCH is
overloaded.
It is measured when the MSC receives the OVERLOAD message from the BSC.
10-36
BSC MSC Server
OVERLOAD
IV. Formula
None
10.5.10 Count of Unequipped Circuit Messages from MSC
I. Entity Name
TUCAM31
II. Description
The MSC sends the message UNEQUIPPED CIRCUIT to the BSC when the circuit is
not configured at the MSC.
It is measured when the MSC sends the message UNEQUIPPED CIRCUIT to the BSC.
BSC MSC Server
UNEQUIPPED CIRCUIT
IV. Formula
None
10.5.11 Count of Unequipped Circuit Messages from BSC
I. Entity Name
TUCABS31
10-37
II. Description
The BSC sends the message UNEQUIPPED CIRCUIT to the MSC when the circuit is
not configured at the BSC.
It is measured when the MSC receives the message UNEQUIPPED CIRCUIT from the
BSC.
BSC MSC Server
UNEQUIPPED CIRCUIT
IV. Formula
None
10.5.12 Count of SAPI “N” Rejection Messages
I. Entity Name
TSMR31
II. Description
The BSC rejects a message with DLCI not equal to 0 from the MSC.
It is measured when the MSC receives the message SAPI "n" REJECT from the BSC.
10-38
BSC MSC Server
SAPI "n" REJECT
IV. Formula
None
10.5.13 Count of Confusion Messages from BSC
I. Entity Name
TCMB31
II. Description
The BSC regards that a message from the MSC is wrong and sends the CONFUSION
message to the MSC.
It is measured when the MSC receives the CONFUSION message from the BSC.
BSC MSC Server
CONFUSION
IV. Formula
None
10.5.14 Count of Confusion Messages from MSC
I. Entity Name
TCMM31
10-39
II. Description
The MSC regards that a message from the BSC is wrong and sends the CONFUSION
message to the BSC.
It is measured when the MSC sends the CONFUSION message to the BSC.
BSC MSC Server
CONFUSION
IV. Formula
None
10.6 GPRS Timeout

10.6.1 Overview of MS_TYPE_GPRS_TIMEOUT
Name Description
NGSTOTO78 Count of timeout requests for non-GPRS service indications
FUIOTO78 Count of timeout requests for getting subscriber information
10.6.2 Count of Timeouts for Non-GPRS Service Indications
I. Entity Name
NGSTOTO78
II. Description
It is the count of timeouts during which no response is received after ALERT-REQUEST

is sent through the Gs-interface.
10-40
It is measured when the timer times out because no response is received a within valid
duration after ALERT-REQUEST is sent through the Gs-interface.
SGSN MSC Server
BSSAP+-ALERT-REQUEST
IV. Formula
None
10.6.3 Count of Timeouts for Getting Subscriber Information
I. Entity Name
FUIOTO78
II. Description
It is the count of timeouts during which no response is received after

MS-INFORMATION-REQUEST is sent through the Gs-interface.
It is measured when the timer times out because no response is received within a valid
duration after MS-INFORMATION-REQUEST is sent through the Gs-interface.
10-41
SGSN MSC Server
BSSAP+-MS-INFORMATION-REQUEST
IV. Formula
None
10.7 Gs-Interface Operation

10.7.1 Overview of MS_TYPE_GS_OPER
Name Description
GSICM75 Count of paging messages on Gs-interface
GIRCM75 Count of paging rejection messages on Gs-interface
MSNR75 Count of MS unreachable messages from SGSN
POSC75 Count of messages of location update request
POSCA75 Count of messages of location update acceptance
POSCR75 Count of messages of location update rejection
TMSIRA75 Count of messages of TMSI reallocation
NGPRST75 Count of messages of non-GPRS indication request

NGSTR75 Count of messages of non-GPRS indication rejection
Count of messages of non-GPRS indication
NGSTA75
acknowledgement
MSMTN75 Count of messages of MS activity indication
GPRSDN75 Count of messages of GPRS detachment indication

GDACKN75 Count of messages of GPRS detachment acknowledgement
10-42
Name Description
IMSID75 Count of messages of IMSI detachment indication
IDACKN75 Count of messages of IMSI detachment acknowledgement
VRSIN75 Count of messages of VLR reset indication
VRSIAN75 Count of messages of VLR reset acknowledgement
SRSIN75 Count of messages of SGSN reset indication
SRSIAN75 Count of messages of SGSN reset acknowledgement
MSIRN75 Count of messages of MS information request
MSIAN75 Count of messages of MS information response
Count of messages of mobile management information
MMINN75
request
RUSAI75 Count of MS status abnormal messages received

SUSANI75 Count of MS status abnormal messages sent
10.7.2 Count of Paging Messages on Gs-Interface
I. Entity Name
GSICM75
II. Description
It is the count of GS_PAGING_REQ messages from the local MSC or VLR to the SGSN,
measured on the observed Gs-interface.
It is measured when the MSC or VLR sends the message GS_PAGING_REQ to the
SGSN.
10-43
SGSN MSC/VLR
GS_PAGING_REQ
GS_PAGING_REJ
IV. Formula
None
10.7.3 Count of Paging Rejection Messages on Gs-Interface
I. Entity Name
GIRCM75
II. Description
It is the count of GS_PAGING_REJ messages from the SGSN to the local MSC or VLR,
It is measured when the MSC or VLR receives the message GS_PAGING_REJ from
the SGSN.
10-44
SGSN MSC/VLR
GS_PAGING_REQ
GS_PAGING_REJ
IV. Formula
None
10.7.4 Count of MS Unreachable Messages from SGSN
I. Entity Name
MSNR75
II. Description
It is the count of GS_MS_UNREACHABLE messages from the SGSN to the local MSC
or VLR, measured on the observed Gs-interface.
It is measured when the SGSN sends the GS_MS_UNREACHABLE message to the

MSC.
10-45
SGSN MSC/VLR
GS_MS_UNREACHABLE
IV. Formula
None
10.7.5 Count of Messages of Location Update Request
I. Entity Name
POSC75
II. Description
It is the count of GS_LOC_UPD_REQ messages from the SGSN to the local MSC or
VLR, measured on the observed Gs-interface.
It is measured when the MSC or VLR receives the message GS_LOC_UPD_REQ from
the SGSN.
10-46
SGSN MSC/VLR
GS_LOC_UPD_REQ
GS_LOC_UPD_ACCEPT
IV. Formula
None
10.7.6 Count of Messages of Location Update Acceptance
I. Entity Name
POSCA75
II. Description
It is the count of GS_LOC_UPD_ACCEPT messages from the local MSC or VLR to the
specified SGSN, measured on the observed Gs-interface.
It is measured when the MSC or VLR sends the message GS_LOC_UPD_ACCEPT to

the SGSN.
10-47
SGSN MSC/VLR
GS_LOC_UPD_REQ
GS_LOC_UPD_ACCEPT
IV. Formula
None
10.7.7 Count of Messages of Location Update Rejection
I. Entity Name
POSCR75
II. Description
It is the count of GS_LOC_UPD_REJ messages from the local MSC or VLR to the
SGSN, measured on the observed Gs-interface.
It is measured when the MSC or VLR sends the message GS_LOC_UPD_REJ to the
SGSN.
10-48
SGSN MSC/VLR
GS_LOC_UPD_REQ
GS_LOC_UPD_REJ
IV. Formula
None
10.7.8 Count of Messages of TMSI Reallocation
I. Entity Name
TMSIRA75
II. Description
It is the count of GS_TMSI_RELOCATE_COMP messages from the SGSN to the local

MSC or VLR, measured on the observed Gs-interface.
It is measured when the MSC or VLR receives the message

GS_TMSI_RELOCATE_COMP from the SGSN.
10-49
SGSN MSC/VLR
GS_TMSI_RELOCATE_COMP
IV. Formula
None
10.7.9 Count of Messages of Non-GPRS Indication Request
I. Entity Name
NGPRST75
II. Description
It is the count of GS_ALERT_REQ messages from the local MSC or VLR to the
It is measured when the MSC or VLR sends the message GS_ALERT_REQ to the
SGSN.
10-50
SGSN MSC/VLR
GS_ALERT_REQ
GS_ALERT_ACK
IV. Formula
None
10.7.10 Count of Messages of Non-GPRS Indication Rejection
I. Entity Name
NGSTR75
II. Description
It is the count of GS_ALERT_REJ messages from the SGSN to the local MSC or VLR,
It is measured when the MSC or VLR receives the message GS_ALERT_REJ from the
SGSN.
10-51
SGSN MSC/VLR
GS_ALERT_REQ
GS_ALERT_REJ
IV. Formula
None
10.7.11 Count of Messages of Non-GPRS Indication Acknowledgement
I. Entity Name
NGSTA75
II. Description
It is the count of GS_ALERT_ACK messages from the SGSN to the local MSC or VLR,
It is measured when the MSC or VLR receives the message GS_ALERT_ACK from the
SGSN.
10-52
SGSN MSC/VLR
GS_ALERT_REQ
GS_ALERT_ACK
IV. Formula
None
10.7.12 Count of Messages of MS Activity Indication
I. Entity Name
MSMTN75
II. Description
It is the count of GS_MS_ACTIVITY_IND messages from the SGSN to the local MSC
It is measured when the SGSN sends the message of GS_MS_ACTIVITY_IND to the

local MSC or VLR.
10-53
SGSN MSC/VLR
GS_MS_ACTIVITY_IND
IV. Formula
None
10.7.13 Count of Messages of GPRS Detachment Indication
I. Entity Name
GPRSDN75
II. Description
It is the count of GS_GPRS_DETACH_IND messages from the SGSN to the local MSC
It is measured when the MSC or VLR receives the message GS_GPRS_DETACH_IND

from the SGSN.
10-54
SGSN MSC/VLR
GS_GPRS_DETACH_IND
A
GS_GPRS_DETACH_ACK
IV. Formula
None
10.7.14 Count of Messages of GPRS Detachment Acknowledgement
I. Entity Name
GDACKN75
II. Description
It is the count of GS_GPRS_DETACH_ACK messages from the local MSC or VLR to

the specified SGSN, measured on the observed Gs-interface.
It is measured when the MSC or VLR sends the message GS_GPRS_DETACH_ACK

to the SGSN.
10-55
SGSN MSC/VLR
GS_GPRS_DETACH_IND
A
GS_GPRS_DETACH_ACK
IV. Formula
None
10.7.15 Count of Messages of IMSI Detachment Indication
I. Entity Name
IMSID75
II. Description
It is the count of GS_IMSI_DETACH_IND messages from the specified SGSN to the

local MSC or VLR, measured on the observed Gs-interface.
It is measured when the MSC or VLR receives the message GS_IMSI_DETACH_IND

from the SGSN.
10-56
SGSN MSC/VLR
GS_IMSI_DETACH_IND
A
GS_IMSI_DETACH_ACK
IV. Formula
None
10.7.16 Count of Messages of IMSI Detachment Acknowledgement
I. Entity Name
IDACKN75
II. Description
It is the count of GS_IMSI_DETACH_ACK messages from the local MSC or VLR to the
It is measured when the MSC or VLR sends the message GS_IMSI_DETACH_ACK to

the SGSN.
10-57
SGSN MSC/VLR
GS_IMSI_DETACH_IND
A
GS_IMSI_DETACH_ACK
IV. Formula
None
10.7.17 Count of Messages of VLR Reset Indication
I. Entity Name
VRSIN75
II. Description
It is the count of GS_RESET_IND messages from the local MSC or VLR to the
It is measured when the MSC or VLR sends the message GS_RESET_IND to the
SGSN.
10-58
SGSN MSC/VLR
GS_RESET_IND
A
GS_RESET_ACK
IV. Formula
None
10.7.18 Count of Messages of VLR Reset Acknowledgement
I. Entity Name
VRSIAN75
II. Description
It is the count of GS_RESET_ACK messages from the SGSN to the local MSC or VLR,
It is measured when the MSC or VLR receives the message GS_RESET_ACK from the
SGSN.
10-59
SGSN MSC/VLR
GS_RESET_IND
A
GS_RESET_ACK
IV. Formula
None
10.7.19 Count of Messages of SGSN Reset Indication
I. Entity Name
SRSIN75
II. Description
It is the count of GS_RESET_IND messages from the SGSN to the local MSC or VLR,
It is measured when the MSC or VLR receives the message GS_RESET_IND from the
SGSN.
10-60
SGSN MSC/VLR
GS_RESET_IND
A
GS_RESET_ACK
IV. Formula
None
10.7.20 Count of Messages of SGSN Reset Acknowledgement
I. Entity Name
SRSIAN75
II. Description
It is the count of GS_RESET_ACK messages from the local MSC or VLR to the
It is measured when the MSC or VLR sends the message GS_RESET_ACK to the
SGSN.
10-61
SGSN MSC/VLR
GS_RESET_IND
A
GS_RESET_ACK
IV. Formula
None
10.7.21 Count of Messages of MS Information Request
I. Entity Name
MSIRN75
II. Description
It is the count of GS_MS_INFO_REQ messages from the local MSC or VLR to the
It is measured when the MSC or VLR sends the message GS_MS_INFO_REQ to the
SGSN.
10-62
SGSN MSC/VLR
GS_MS_INFO_REQ
A
GS_MS_INFO_RSP
IV. Formula
None
10.7.22 Count of Messages of MS Information Response
I. Entity Name
MSIAN75
II. Description
It is the count of GS_MS_INFO_RSP messages from the SGSN to the local MSC or
It is measured when the MSC or VLR receives the message GS_MS_INFO_RSP from
the SGSN.
10-63
SGSN MSC/VLR
GS_MS_INFO_REQ
A
GS_MS_INFO_RSP
IV. Formula
None
10.7.23 Count of Messages of Mobile Management Information Request
I. Entity Name
MMINN75
II. Description
It is the count of GS_MM_INFO_REQ messages from the local MSC or VLR to the
It is measured when the MSC or VLR sends the message GS_MM_INFO_REQ to the
SGSN.
10-64
SGSN MSC/VLR
GS_MM_INFO_REQ
IV. Formula
None
10.7.24 Count of MS Status Abnormal Messages Received
I. Entity Name
RUSAI75
II. Description
It is the count of GS_MOBILE_STATUS messages from the SGSN to the local MSC or
It is measured when the MSC or VLR receives the message GS_MOBILE_STATUS

from the SGSN.
10-65
SGSN MSC/VLR
GS_MOBILE_STATUS
IV. Formula
None
10.7.25 Count of MS Status Abnormal Messages Sent
I. Entity Name
SUSANI75
II. Description
It is the count of GS_MOBILE_STATUS messages from the local MSC or VLR to the
SGSN, measured on the observed Gs-interface.
It is measured when the MSC or VLR sends the message GS_MOBILE_STATUS to the
SGSN.
10-66
SGSN MSC/VLR
GS_MOBILE_STATUS
IV. Formula
None
10.8 Gs-Interface Error Cause

10.8.1 Overview of MS_TYPE_GS_ERR
Name Description
Count of messages with cause of IMSI detached for GPRS
GSID76
service
Count of messages with cause of IMSI detached for GPRS
GANGSD76
and non-GPRS services
UKIMSI76 Count of messages with cause of IMSI unknown
Count of messages with cause of IMSI explicitly detached for
ENGSID76
non-GPRS services
Count of messages with cause of IMSI implicitly detached for

INGSID76
non-GPRS services
MSUR76 Count of messages with cause of MS unreachable

Count of messages with cause of message not compatible
PSDM76
with protocol state
Count of messages with cause of missing mandatory

MCIU76
information element
Count of messages with cause of invalid mandatory

ICMU76
information
COMUF76 Count of messages with cause of conditional IE error
10-67
Name Description
Count of messages with cause of semantically incorrect
MSF76
message
UNKM76 Count of messages with cause of message unknown
ADDRF76 Count of messages with cause of address error
10.8.2 Count of Messages with Cause of IMSI Detached for GPRS Service
I. Entity Name
GSID76
II. Description
It is the count of messages with the cause of “IMSI detached for GPRS service”
between the local MSC or VLR and the specified SGSN, measured on the observed
Gs-interface.
It is measured when the MSC receives the message from the SGSN.
SGSN MSC Server
IMSI detached for GPRS services
IV. Formula
None
10-68
10.8.3 Count of Messages with Cause of IMSI Detached for GPRS and
Non-GPRS Services
I. Entity Name
GANGSD76
II. Description
It is the count of messages with the cause of “IMSI detached for GPRS and non-GPRS
services” between the local MSC or VLR and the specified SGSN, measured on the
observed Gs-interface.
SGSN MSC Server
IMSI detached for GPRS and non-GPRS

services
IV. Formula
None
10.8.4 Count of Messages with Cause of IMSI Unknown
I. Entity Name
UKIMSI76
II. Description
It is the count of messages with the cause of “IMSI unknown” between the local MSC or
VLR and the specified SGSN, measured on the observed Gs-interface.
10-69
SGSN MSC Server
IMSI unknown
IV. Formula
None
10.8.5 Count of Messages with Cause of IMSI Explicitly Detached for

Non-GPRS Services
I. Entity Name
ENGSID76
II. Description
It is the count of messages with the cause of “IMSI detached for non-GPRS services”
Gs-interface.
10-70
SGSN MSC Server
IMSI detached for non-GPRS services
IV. Formula
None
10.8.6 Count of Messages with Cause of IMSI Implicitly Detached for

Non-GPRS Services
I. Entity Name
INGSID76
II. Description
It is the count of messages with the cause of “IMSI implicitly detached for non-GPRS
services” between the local MSC or VLR and the specified SGSN, measured on the
10-71
SGSN MSC Server
IMSI implicitly detached for non-GPRS

services
IV. Formula
None
10.8.7 Count of Messages with Cause of MS Unreachable
I. Entity Name
MSUR76
II. Description
It is the count of messages with the cause of “MS unreachable” between the local MSC
or VLR and the specified SGSN, measured on the observed Gs-interface.
10-72
SGSN MSC Server
MS unreachable
IV. Formula
None
10.8.8 Count of Messages with Cause of Message Not Compatible with

Protocol State
I. Entity Name
PSDM76
II. Description
It is the count of messages with the cause of “Message not compatible with the protocol
state” between the local MSC or VLR and the specified SGSN, measured on the
10-73
SGSN MSC Server
Message not compatible with the protocol

state
IV. Formula
None
10.8.9 Count of Messages with Cause of Missing Mandatory Information

Element
I. Entity Name
MCIU76
II. Description
It is the count of messages with the cause of “Missing mandatory information element”
Gs-interface.
10-74
SGSN MSC Server
Missing mandatory information element
IV. Formula
None
10.8.10 Count of Messages with Cause of Invalid Mandatory Information
I. Entity Name
ICMU76
II. Description
It is the count of messages with the cause of “Invalid mandatory information” between
the local MSC or VLR and the specified SGSN, measured on the observed
Gs-interface.
10-75
SGSN MSC Server
Invalid mandatory information
IV. Formula
None
10.8.11 Count of Messages with Cause of Conditional IE Error
I. Entity Name
COMUF76
II. Description
It is the count of messages with the cause of “Conditional IE error” between the local
MSC or VLR and the specified SGSN, measured on the observed Gs-interface.
10-76
SGSN MSC Server
Conditional IE error
IV. Formula
None
10.8.12 Count of Messages with Cause of Semantically Incorrect Message
I. Entity Name
MSF76
II. Description
It is the count of messages with the cause of “Semantically incorrect message”

Gs-interface.
10-77
SGSN MSC Server
Semantically incorrect message
IV. Formula
None
10.8.13 Count of Messages with Cause of Message Unknown
I. Entity Name
UNKM76
II. Description
It is the count of messages with the cause of “Message unknown” between the local
MSC or VLR and the specified SGSN, measured on the observed Gs-interface.
10-78
SGSN MSC Server
Message unknown
IV. Formula
None
10.8.14 Count of Messages with Cause of Address Error
I. Entity Name
ADDRF76
II. Description
It is the count of messages with the cause of “Address error” between the local MSC or
VLR and the specified SGSN, measured on the observed Gs-interface.
10-79
SGSN MSC Server
Address error
IV. Formula
None
10.9 H.248 MGW

10.9.1 Overview of MS_H.248_MGW_TRAFIC
Name Description
MGWUAT Count of unavailable states
MGWUAD Duration of unavailable state
SSNDMSG Count of messages sent
SSNDBYT Count of bytes in messages sent
SRCVMSG Count of messages received
SRCVBYT Count of bytes in messages received
FSNDMSG Count of messages unsuccessfully sent
FRCVMSG Count of messages unsuccessfully received

SBINEN Count of binary encoded messages
SBINDE Count of binary decoded messages
STXTEN Count of text encoded messages

STXTDE Count of text decoded messages
FAPPSE Count of messages failed in security information application
FVERSE Count of messages failed in security information verification
10-80
Name Description
FEN Count of messages with error in encoding
FDE Count of messages with error in decoding
AVSNDMSG Count of messages sent per second
AVRCVMSG Count of messages received per second
AVSNDBIT Count of bits sent per second
AVRCVBIT Count of bits received per second
10.9.2 Count of Unavailable States
I. Entity Name
MGWUAT
II. Description
It is the count of states that the MGW is unavailable.
It is measured when the MGW fails.
IV. Formula
None
10.9.3 Duration of Unavailable State
I. Entity Name
MGWUAD
II. Description
It is the duration when the MGW is unavailable.
It is measured from the MGW failure to recovery.
IV. Formula
None
10-81
I. Entity Name
SSNDMSG
II. Description
It is the count of messages that H.248 successfully sends to the MGW.
It is measured when H.248 successfully sends messages to the MGW.
IV. Formula
None
I. Entity Name
SSNDBYT
II. Description
It is the count of bytes in messages that H.248 sends to the MGW.
IV. Formula
None
I. Entity Name
SRCVMSG
II. Description
It is the count of messages that H.248 successfully receives from the MGW.
It is measured when H.248 successfully receives messages from the MGW.
IV. Formula
None
10-82
I. Entity Name
SRCVBYT
II. Description
It is the count of bytes in messages that H.248 receives from the MGW.
IV. Formula
None
10.9.8 Count of Messages Unsuccessfully Sent
I. Entity Name
FSNDMSG
II. Description
It is the count of messages that H.248 fails to send to the MGW.
It is measured when H.248 fails to send messages to the MGW.
IV. Formula
None
10.9.9 Count of Messages Unsuccessfully Received
I. Entity Name
FRCVMSG
II. Description
It is the count of messages that H.248 fails to receive from the MGW.
It is measured when H.248 fails to receive messages from the MGW.
IV. Formula
None
10-83
10.9.10 Count of Binary Encoded Messages
I. Entity Name
SBINEN
II. Description
It is the count of binary messages successfully encoded by H.248.
It is measured when H.248 successfully encodes binary messages.
IV. Formula
None
10.9.11 Count of Binary Decoded Messages
I. Entity Name
SBINDE
II. Description
It is the count of binary messages successfully decoded by H.248.
It is measured when H.248 successfully decodes binary messages.
IV. Formula
None
10.9.12 Count of Text Encoded Messages
I. Entity Name
STXTEN
II. Description
It is the count of text messages successfully encoded by H.248.
It is measured when H.248 successfully encodes text messages.
IV. Formula
None
10-84
10.9.13 Count of Text Decoded Messages
I. Entity Name
STXTDE
II. Description
It is the count of text messages successfully decoded by H.248.
It is measured when H.248 successfully decodes text messages.
IV. Formula
None
10.9.14 Count of Messages Failed in Security Information Application
I. Entity Name
FAPPSE
II. Description
It is the count of messages that H.248 fails to apply security information on.
It is measured when H.248 fails to apply security information on messages.
IV. Formula
None
10.9.15 Count of Messages Failed in Security Information Verification
I. Entity Name
FVERSE
II. Description
It is the count of messages that fail H.248 security verification.
It is measured when H.248 fails to verify security information on messages.
IV. Formula
None
10-85
10.9.16 Count of Messages Failed in Encoding
I. Entity Name
FEN
II. Description
It is the count of messages that fail to be encoded.
It is measured when H.248 messages fail to be encoded.
IV. Formula
None
10.9.17 Count of Messages with Error in Decoding
I. Entity Name
FDE
II. Description
It is the count of messages that fail to be decoded.
It is measured when H.248 fails to decode messages.
IV. Formula
None
I. Entity Name
AVSNDMSG
II. Description
It is the count of messages that H.248 sends to the MGW every second.
IV. Formula
None
10-86
I. Entity Name
AVRCVMSG
II. Description
It is the count of messages that H.248 receives from the MGW every second.
IV. Formula
None
I. Entity Name
AVSNDBIT
II. Description
It is the count of bits in messages that H.248 sends to the MGW every second.
IV. Formula
None
I. Entity Name
AVRCVBIT
II. Description
It is the count of bits in messages that H.248 receives from the MGW every second.
IV. Formula
None
10-87
10.10 H.248 SCTP Link

10.10.1 Overview of MS_H.248_SCTPLNK_TRAFIC
Name Description
LNKUAT Count of unavailable states
LNKUAD Duration of unavailable state
LNKCGT Count of link congestion
LNKCGD Duration of link congestion

SNDMSG Count of messages sent
LSNDBYT Count of bytes in messages sent
RCVMSG Count of messages received

LRCVBYT Count of bytes in messages received
LAVSNDMSG Count of messages sent per second
LAVRCVMSG Count of messages received per second
LAVSNDBIT Count of bits sent per second
LAVRCVBIT Count of bits received per second
I. Entity Name
LNKUAT
II. Description
It is the count of states that the Mc SCTP link is unavailable.
It is measured when the Mc SCTP link fails.
IV. Formula
None
I. Entity Name
LNKUAD
10-88
II. Description
It is the duration when the Mc SCTP link is unavailable.
It is measured from the Mc SCTP link failure to recovery.
IV. Formula
None
10.10.4 Count of Link Congestion
I. Entity Name
LNKCGT
II. Description
It is the count of congestion on the Mc SCTP link.
It is measured when the Mc SCTP link is congested.
IV. Formula
None
10.10.5 Duration of Link Congestion
I. Entity Name
LNKCGD
II. Description
It is the duration of congestion of the Mc SCTP link.
It is measured from the Mc SCTP link congestion to recovery.
IV. Formula
None
I. Entity Name
SNDMSG
10-89
II. Description
It is the count of messages sent through the Mc SCTP link.
It is measured when H.248 messages are successfully sent through the specified
SCTP link.
IV. Formula
None
I. Entity Name
LSNDBYT
II. Description
It is the count of bytes in messages sent through the Mc SCTP link.
It is measured when H.248 messages are successfully sent through the specified
SCTP link.
IV. Formula
None
I. Entity Name
RCVMSG
II. Description
It is the count of messages received through the Mc SCTP link.
It is measured when H.248 messages are successfully received through the specified
SCTP link.
IV. Formula
None
10-90
I. Entity Name
LRCVBYT
II. Description
It is the count of bytes in messages received through the Mc SCTP link.
SCTP link.
IV. Formula
None
I. Entity Name
LAVSNDMSG
II. Description
It is the count of messages sent through the Mc SCTP link every second.
It is measured when messages are successfully sent through the specified SCTP link.
IV. Formula
None
I. Entity Name
LAVRCVMSG
II. Description
It is the count of messages received through the Mc SCTP link every second.
SCTP link.
10-91
IV. Formula
None
I. Entity Name
LAVSNDBIT
II. Description
It is the count of bits in messages sent through the Mc SCTP link every second.
It is measured when messages are successfully sent through the specified SCTP link.
IV. Formula
None
I. Entity Name
LAVRCVBIT
II. Description
It is the count of bits in messages received through the Mc SCTP link every second.
SCTP link.
IV. Formula
None
10.11 IP Port Traffic

10.11.1 Overview of MS_IFM_IPFLOW_TRAF
Name Description
PAKOS Count of packets sent
PAKOR Count of packets received
BYTOS Count of bytes sent
10-92
Name Description
BYTOR Count of bytes received
SPDOS Speed of sending packet
SPDOR Speed of receiving packet
BITOS Bit rate of sending packet
BITOR Bit rate of receiving packet
RATOS Bandwidth utilization of IP port when sending packet
RATOR Bandwidth utilization of IP port when receiving packet
DRPAK Count of discarded packets received
INVIP Count of packets with invalid IP address
ACCDY Count of rejected packets for access
LIMICMP Count of restricted ICMP packets
UNKIP Count of unknown IP packets
FORFAIL Count of packets that IFM fails to transfer
SNDFAIL Count of packets that IFM fails to send
10.11.2 Count of Packets Sent
I. Entity Name
PAKOS
II. Description
It is the count of packets sent by the IFM.
It is measured when the IFM sends packets.
IV. Formula
None
10.11.3 Count of Packets Received
I. Entity Name
PAKOR
II. Description
It is the count of packets received by the IFM.
10-93
It is measured when the IFM receives packets.
IV. Formula
None
10.11.4 Count of Bytes Sent
I. Entity Name
BYTOS
II. Description
It is the count of bytes in the packets sent by the IFM.
IV. Formula
None
10.11.5 Count of Bytes Received
I. Entity Name
BYTOR
II. Description
It is the count of bytes in the packets received by the IFM.
IV. Formula
None
10.11.6 Speed of Sending Packet
I. Entity Name
SPDOS
II. Description
It is the speed of sending packets by the IFM.
10-94
IV. Formula
None
10.11.7 Speed of Receiving Packet
I. Entity Name
SPDOR
II. Description
It is the speed of receiving packets by the IFM.
IV. Formula
None
10.11.8 Bit Rate of Sending Packet
I. Entity Name
BITOS
II. Description
It is the bit rate of sending packets by the IFM.
IV. Formula
None
10.11.9 Bit Rate of Receiving Packet
I. Entity Name
BITOR
II. Description
It is the bit rate of receiving packets by the IFM.
10-95
IV. Formula
None
10.11.10 Bandwidth Utilization of IP Port When Sending Packet
I. Entity Name
RATOS
II. Description
It is the bandwidth utilization of an IP port when sending packets by the IFM.
IV. Formula
None
10.11.11 Bandwidth Utilization of IP Port When Receiving Packet
I. Entity Name
RATOR
II. Description
It is the utilization of bandwidth of an IP port when receiving packets by the IFM.
IV. Formula
None
10.11.12 Count of Discarded Packets Received
I. Entity Name
DRPAK
II. Description
It is the count of packets discarded after being received by the IFM.
10-96
It is measured when the packets are discarded invalidly after being received by the
IFM.
IV. Formula
None
10.11.13 Count of Packets with Invalid IP Address
I. Entity Name
INVIP
II. Description
It is the count of packets with invalid IP address.
It is measured when the IFM receives the packets with invalid IP address.
IV. Formula
None
10.11.14 Count of Rejected Packets for Access
I. Entity Name
ACCDY
II. Description
It is the count of rejected packets for access.
It is measured when the IFM receives the rejected packets with the source IP
addresses.
IV. Formula
None
10.11.15 Count of Restricted ICMP Packets
I. Entity Name
LIMICMP
10-97
II. Description
It is the count of restricted ICMP packets.
It is measured from when the count of ICMP packets reaches the upper limit.
IV. Formula
None
10.11.16 Count of Unknown IP Packets
I. Entity Name
UNKIP
II. Description
It is the count of unknown IP packets.
It is measured when the IFM receives unknown packets.
IV. Formula
None
10.11.17 Count of Packets That IFM Fails to Transfer
I. Entity Name
FORFAIL
II. Description
It is the count of packets that the IFM fails to transfer.
It is measured when the IFM fails to transfer packets.
IV. Formula
None
10.11.18 Count of Packets That IFM Fails to Send
I. Entity Name
SNDFAIL
10-98
II. Description
It is the count of packets that the IFM fails to send.
It is measured when the IFM fails to send packets.
IV. Formula
None
10.12 ISUP Circuit Group

10.12.1 Overview of MS_ISUP_TKGRP_PERFORM_TRAF
Name Description
Count of REL messages sent with cause of switching

SEC
equipment congestion
CGC Count of messages of circuit group congestion
Count of REL messages sent with cause of address
ADI
incomplete
TMPFL Count of REL messages sent with cause of temporary failure
Count of REL messages sent with cause of unallocated

UNN
number
SB Count of REL messages sent with cause of subscriber busy
DPCFL Count of REL messages sent with cause of destination fault
OTHFL Count of REL messages sent with other causes
OPEGS Count of outgoing call attempts
Count of REL messages received with cause of switching
RSEC
equipment congestion
RCGC Count of REL messages received with cause of no valid circuit

Count of REL messages received with cause of address
RADI
incomplete
Count of REL messages received with cause of temporary
RTMPFL
failure
Count of REL messages received with cause of unallocated
RUNN
number
10-99
Name Description
Count of REL messages received with cause of no route to
RNRU
destination
Count of REL messages received with cause of subscriber
RSB
busy
Count of REL messages received with cause of destination
RDPCFL
fault
ROTH Count of REL messages received with other causes
ANN Count of answers without charging
MGB Count of maintenance-oriented CGB messages
HGB Count of hardware-oriented CGB messages
GRS Count of circuit group reset messages
CIRRST Count of circuit reset messages
ANS Count of answers
MSUR Count of messages received

MSUS Count of messages sent
MSURS Count of messages both received and sent
MSURL length of messages received

MSUSL length of messages sent
MSURSL length of messages both received and sent
IOPEGS Count of calls

MSULPC length of messages per call
MSUAVL average message length
I. Entity Name
IPEGS
II. Description
It is the count of IAMs received by the MSC.
It is measured when the MSC receives the ISUP IAM.

10-100
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
10.12.3 Count of REL Messages Sent with Cause of Switching Equipment

Congestion
I. Entity Name
SEC
II. Description
Switching equipment congestion occurs due to resource allocation failure, for example,
no Highway resource is allocated.
It is measured when the local MSC sends the REL message to the originating office,
with the cause of "switching equipment congestion (0101010)".
1) Count of switching equipment congestion (case 1)
The cause value for Release is CV_EXCHANGE_FACILITY_SURGE.
10-101
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

The cause value for Release is CV_EXCHANGE_FACILITY_SURGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A

The cause is that the system capability is exceeded and more than 10,000 calls are
simultaneously made on a module.
10-102
IAM
A
REL
IV. Formula
None
10.12.4 Count of Messages of Circuit Group Congestion
I. Entity Name
CGC
II. Description
It is the count of messages received with the cause of no route available.
It is measured when the outgoing trunk receives the REL message with the cause of
CV_NO_ROUTE_AVAILABLE.
1) Count of circuit group congestion (case 1)
The cause value for Release is CV_NO_ROUTE_AVAILABLE
10-103
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A
2) Count of circuit group congestion (case 2)

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-104
I. Entity Name
CG
II. Description
It is the count of congestion on the ISUP circuit group.
It is not measured.
IV. Formula
None
10.12.6 Count of REL Messages Sent with Cause of Address Incomplete
I. Entity Name
ADI
II. Description
It is the count of REL messages that the MSC sends to the originating office, with the
cause of “address incomplete”.
It is measured when the MSC sends the REL message to the originating office, with the
cause of “address incomplete (0011100)”.
1) Count of REL messages sent with cause of address incomplete (case 1)
The cause value for Release is
CV_INVALID_FORMAT_OR_ADDRESS_NOT_ENOUGH
10-105
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-106
10.12.7 Count of REL Messages Sent with Cause of Temporary Failure
I. Entity Name
TMPFL
II. Description
It is the count of REL messages sent by the MSC with the cause of “temporary failure”.
It is measured when the MSC sends the REL message with the cause of “temporary
failure (0101001)”.
1) Count of REL messages sent with cause of temporary failure (case 1)
The cause value for Release is CV_ERROR_FOR_THE_TIME_BEING
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

10-107
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.12.8 Count of REL Messages Sent with Cause of Unallocated Number
I. Entity Name
UNN
II. Description
cause of “unallocated number”.
cause of “unallocated number (0000001)”.
1) Count of REL messages sent with cause of unallocated number (case 1)
The cause value for Release is CV_UNALOC_CODE
10-108
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-109
10.12.9 Count of REL Messages Sent with Cause of Subscriber Busy
I. Entity Name
SB
II. Description
cause of “subscriber busy”.
cause of “subscriber busy (0010001)”.
1) Count of REL messages sent with cause of subscriber busy (case 1)
The cause value for Release is CV_BUSY
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

10-110
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.12.10 Count of REL Messages Sent with Cause of Destination Fault
I. Entity Name
DPCFL
II. Description
cause of “destination fault” like timeout after off-hook.
cause of “destination unreachable (0011011)" or "destination incompatible (1011000)”.
1) Count of REL messages sent with cause of destination fault (case 1)
The cause value for Release is one of the following:
z CV_TERMINAL_ERROR
z CV_TERMINAL_UNCOMPATABLE
10-111
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

z CV_TERMINAL_ERROR
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-112
10.12.11 Count of REL Messages Sent with Other Causes
I. Entity Name
OTHFL
II. Description
It is the count of REL messages sent by the MSC with a cause other than the above
listed.
It is measured when the MSC sends the REL message.

1) Count of REL messages sent with other causes (case 1)
The cause value for Release is none of the following:
z CV_TERMINAL_ERROR
z CV_NO_ROUTE_TO_SPECIFIED_INTERNETWORK
z CV_BUSY
z CV_UNALOC_CODE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

z CV_TERMINAL_ERROR
10-113
z CV_BUSY
z CV_UNALOC_CODE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.12.12 Count of Outgoing Call Attempts
I. Entity Name
OPEGS
II. Description
It is the count of IAI and IAM messages sent by the MSC.
It is measured when the MSC sends the ISUP IAI or IAM message.
10-114
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None

Equipment Congestion
I. Entity Name
RSEC
II. Description
It is the count of REL messages received by the MSC with the cause of “switching
equipment congestion”.
It is measured when the MSC receives the ISUP REL message from the peer office,
with the cause of “switching equipment congestion (0101010)”.
1) Count of REL messages received with cause of switching equipment congestion
(case 1)
10-115
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

(case 2)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-116
10.12.14 Count of REL Messages Received with Cause of No Valid Circuit
I. Entity Name
RCGC
II. Description
It is the count of REL messages received by the MSC with the cause of “no valid
circuit”.
with the cause of “no valid circuit (0100010)”.
1) Count of REL messages received with cause of no valid circuit (case 1)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

10-117
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None

Incomplete
I. Entity Name
RADI
II. Description
It is the count of invalid call attempts due to dialed number incomplete.
It is measured when the MSC receives the REL message from the peer office, with the
1) Count of REL messages received with cause of address incomplete (case 1)
10-118
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-119
10.12.16 Count of REL Messages Received with Cause of Temporary Failure
I. Entity Name
RTMPFL
II. Description
It is the count of REL messages that the MSC receives from the peer office, with the
cause of “temporary failure”.
cause of “temporary failure (0101001)”.
1) Count of REL messages received with cause of temporary failure (case 1)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

10-120
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.12.17 Count of REL Messages Received with Cause of Unallocated

Number
I. Entity Name
RUNN
II. Description
It is the count of REL messages received by the MSC with the cause of “unallocated
number”.
1) Count of REL messages received with cause of unallocated number (case 1)
10-121
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-122
10.12.18 Count of REL Messages Received with Cause of No Route to

Destination
I. Entity Name
RNRU
II. Description
It is the count of REL messages received by the MSC with the cause of "no route to
specified transit network".
It is measured when the MSC receives the REL message with the cause of "no route to
specified transit network (0000010)" or "no route to destination (0000011)".
1) Count of REL messages received with cause of no route to destination (case 1)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

10-123
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.12.19 Count of REL Messages Received with Cause of Subscriber Busy
I. Entity Name
RSB
II. Description
It is the count of REL messages received by the MSC with the cause of “subscriber
busy”.
1) Count of REL messages received with cause of subscriber busy (case 1)
10-124
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-125
10.12.20 Count of REL Messages Received with Cause of Destination Fault
I. Entity Name
RDPCFL
II. Description
cause of “destination unreachable” or “destination incompatible”.
1) Count of REL messages received with cause of destination fault (case 1)
z CV_TERMINAL_ERROR
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

z CV_TERMINAL_ERROR
10-126
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.12.21 Count of REL Messages Received with Other Causes
I. Entity Name
ROTH
II. Description
It is the count of REL messages received by the MSC with a cause other than the above
listed.
It is measured when the MSC receives the REL message.

1) Count of REL messages received with other causes (case 1)
z CV_TERMINAL_ERROR
z CV_BUSY
z CV_UNALOC_CODE
10-127
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

z CV_TERMINAL_ERROR
z CV_BUSY
z CV_UNALOC_CODE
10-128
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.12.22 Count of Answers Without Charging
I. Entity Name
ANN
II. Description
It is the count of answers without charging according to the indication signal.
It is measured when the ANM or CON message indicates not charging the call.
1) Count of answers without charging (case 1)
Here, the charging flag in the ANM or Connect message is set to NO.
See points A (for outgoing calls) and B (for incoming calls) in the following figure.
10-129
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM ANM
A
Connect
Connect
B
ANM
2) Count of answers without charging (case 2)

Here, the charging flag in the ANM or Connect message is set to NO.
See points A (for outgoing calls) and B (for incoming calls) in the following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
CON
A
Connect
Connect
B
CON
IV. Formula
None
10-130
10.12.23 Count of Maintenance-Oriented CGB Messages
I. Entity Name
MGB
II. Description
It is the count of maintenance-oriented CGB messages received or sent by the MSC.
It is measured when the MSC receives or sends the maintenance-oriented ISUP CGB
message.
The message is maintenance oriented and the measurement value is the sum of
counts of incoming and outgoing messages, that is, A + B.
MTP ISUP(inc) ISUP(out) MTP
CGB CGB
A B
CGBA CGBA
IV. Formula
None
10.12.24 Count of Hardware-Oriented CGB Messages
I. Entity Name
HGB
II. Description
It is the count of hardware-oriented CGB messages received or sent by the MSC.
10-131
It is measured when the MSC receives or sends the hardware-oriented ISUP CGB
message.
The message is hardware oriented and the measurement value is the sum of counts of
incoming and outgoing messages, that is, A + B.
CGB CGB
A B
CGBA CGBA
IV. Formula
None
10.12.25 Count of Circuit Group Reset Messages
I. Entity Name
GRS
II. Description
It is the count of GRS messages received or sent by the MSC.
It is measured when the MSC receives or sends the ISUP GRS message. The
measurement value is the sum of counts of outgoing and incoming messages, that is, A
+ B.
10-132
GRS GRS
A B
GRA GRA
IV. Formula
None
10.12.26 Count of Circuit Reset Messages
I. Entity Name
CIRRST
II. Description
It is the count of RSC messages received or sent by the MSC.
It is measured when the MSC receives or sends the ISUP RSC message. The
+ B.
10-133
GRS GRS
A B
GRA GRA
IV. Formula
None
10.12.27 Count of Answers
I. Entity Name
ANS
II. Description
It is the count of call answers.
It is measured when the MSC receives or sends the ISUP ANM. (ITU Q.762)
1) Count of answers (case 1)
See points A (for outgoing calls) and B (for incoming calls) in the following figure. The
+ B.
10-134
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM ANM
A
Connect
Connect
B
ANM
2) Count of answers (case 2)

See points A (for outgoing calls) and B (for incoming calls) in the following figure. The
+ B.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
CON
A
Connect
Connect
B
CON
IV. Formula
None
10-135
I. Entity Name
MSUR
II. Description
It is the count of ISUP messages received.
It is measured when the MSC receives the message TRANSFER IND from MTP3. The
total count or length of messages received is that of valid ISUP messages of NI, DPC,
OPC or CIC.
XXX XXX
A B
IV. Formula
None
I. Entity Name
MSUS
II. Description
It is the count of ISUP messages sent.
10-136
It is measured when the MSC sends the message TRANSFER REQ to MTP3. The total
count or length of messages sent is that of valid messages that ISUP sends to MTP.
XXX XXX
A B
IV. Formula
None
10.12.30 Count of Messages Both Received and Sent
I. Entity Name
MSURS
II. Description
It is the count of ISUP messages both received and sent.
Count of messages received + Count of messages sent.
IV. Formula
None
10-137
10.12.31 Length of Messages Received
I. Entity Name
MSURL
II. Description
It is the total length of ISUP messages received.
It is measured when the MSC receives the message TRANSFER IND from MTP3.
XXX XXX
A B
IV. Formula
None
10.12.32 Length of Messages Sent
I. Entity Name
MSUSL
II. Description
It is the total length of ISUP messages sent.
It is measured when the MSC sends the message TRANSFER REQ to MTP3.
10-138
XXX XXX
A B
IV. Formula
None
10.12.33 Length of Messages Both Received and Sent
I. Entity Name
MSURSL
II. Description
It is the total length of ISUP messages both received and sent.
Total length of messages received + Total length of messages sent.
IV. Formula
None
10.12.34 Count of Calls
I. Entity Name
IOPEGS
II. Description
It is the count of incoming and outgoing call attempts.
10-139
Count of incoming call attempts + Count of outgoing call attempts.
IV. Formula
None
10.12.35 Length of Messages per Call
I. Entity Name
MSULPC
II. Description
It is the count of bytes in messages needed for each call.
Length of messages both received and sent/Count of calls.
IV. Formula
None
10.12.36 Average Message Length
I. Entity Name
MSUAVL
II. Description
It is the average length of each ISUP message.
Length of messages both received and sent/Count of messages.
IV. Formula
None
10-140
10.13 ISUP Node

10.13.1 Overview of MS_ISUP_NODE_PERFORM_TRAF
Name Description
Count of REL messages sent with cause of switching equipment
SEC
congestion
CGC Count of REL messages sent with cause of no valid circuit
ADI Count of REL messages sent with cause of address incomplete

TMPFL Count of REL messages sent with cause of temporary failure
UNN Count of REL messages sent with cause of unallocated number
SB Count of REL messages sent with cause of subscriber busy

DPCFL Count of REL messages sent with cause of destination fault
OTHFL Count of REL messages sent with other causes
I. Entity Name
IPEGS
II. Description
It is the count of IAMs received by the MSC.
It is measured when the MSC receives the ISUP IAM.

10-141
IAM
A
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
10.13.3 Count of REL Messages Sent with Cause of Switching Equipment

Congestion
I. Entity Name
SEC
II. Description
failure to allocate resources like IPATH, CR, CCB and HW.
It is measured when the local MSC sends the REL message to originating office, with
the cause of "switching equipment congestion (0101010)".
1) Count of REL messages sent with cause of switching equipment congestion (case
1)
10-142
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A
2)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
3)
The cause is that the system capability is exceeded and more than 10,000 calls are
simultaneously made on a module.
10-143
IAM
A
REL
IV. Formula
None
10.13.4 Count of REL Messages Sent with Cause of No Valid Circuit
I. Entity Name
CGC
II. Description
It is the count of failures that the outgoing trunk cannot find the circuit.
cause of “no valid circuit (0100010)”.
1) Count of REL messages sent with cause of no valid circuit (case 1)
10-144
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A
2) Count of REL messages sent with cause of no valid circuit (case 2)

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-145
10.13.5 Count of REL Messages Sent with Cause of Address Incomplete
I. Entity Name
ADI
II. Description
cause of address incomplete.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

10-146
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.13.6 Count of REL Messages Sent with Cause of Temporary Failure
I. Entity Name
TMPFL
II. Description
It is the count of REL messages sent by the MSC with the cause of “temporary failure”.
It is measured when the MSC sends the REL message with the cause of “temporary
failure (0101001)”.
10-147
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-148
10.13.7 Count of REL Messages Sent with Cause of Unallocated Number
I. Entity Name
UNN
II. Description
cause of “unallocated number”.
1) Count of REL messages sent with cause of unallocated number (case 1)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

10-149
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.13.8 Count of REL Messages Sent with Cause of Subscriber Busy
I. Entity Name
SB
II. Description
cause of “subscriber busy”.
10-150
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10-151
10.13.9 Count of REL Messages Sent with Cause of Destination Fault
I. Entity Name
DPCFL
II. Description
cause of “destination fault” like timeout after off-hook.
z CV_TERMINAL_ERROR
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

z CV_TERMINAL_ERROR
10-152
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.13.10 Count of REL Messages Sent with Other Causes
I. Entity Name
OTHFL
II. Description
It is the count of REL messages sent by the MSC with a cause other than the above
listed.
It is measured when the MSC sends the REL message.

z CV_TERMINAL_ERROR
z CV_BUSY
z CV_UNALOC_CODE
10-153
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Release
Release
REL A

z CV_TERMINAL_ERROR
z CV_BUSY
z CV_UNALOC_CODE
10-154
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
Release
Release
REL A
IV. Formula
None
10.14 ISUP Network

10.14.1 Overview of MS_ISUP_NET_PERFORM_TRAF
Name Description
Count of REL messages received with cause of switching equipment

RSEC
congestion
RCGC Count of REL messages received with cause of no valid circuit
RADI Count of REL messages received with cause of address incomplete
RTMPFL Count of REL messages received with cause of temporary failure
RUNN Count of REL messages received with cause of unallocated number

Count of REL messages received with cause of no route to
RNRU
destination
RSB Count of REL messages received with cause of subscriber busy

RDPCFL Count of REL messages received with cause of destination fault
ROTH Count of REL messages received with other causes
10-155
I. Entity Name
OPEGS
II. Description
It is the count of IAMs sent by the MSC.
It is measured when the MSC sends the ISUP IAM.

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None

Equipment Congestion
I. Entity Name
RSEC
II. Description
It is the count of REL messages received by the MSC with the cause of “switching
equipment congestion”.
10-156
with the cause of “switching equipment congestion (0101010)”.
(case 1)
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

(case 2)
10-157
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.14.4 Count of REL Messages Received with Cause of No Valid Circuit
I. Entity Name
RCGC
II. Description
It is the count of REL messages received by the MSC with the cause of “no valid
circuit”.
with the cause of “no valid circuit (0100010)”.
10-158
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-159
10.14.5 Count of REL Messages Received with Cause of Address Incomplete
I. Entity Name
RADI
II. Description
It is the count of invalid call attempts due to dialed number incomplete.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

10-160
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.14.6 Count of REL Messages Received with Cause of Temporary Failure
I. Entity Name
RTMPFL
II. Description
cause of “temporary failure”.
cause of “temporary failure (0101001)”.
10-161
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-162
10.14.7 Count of REL Messages Received with Cause of Unallocated

Number
I. Entity Name
RUNN
II. Description
It is the count of REL messages received by the MSC with the cause of “unallocated
number”.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

10-163
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.14.8 Count of REL Messages Received with Cause of No Route to

Destination
I. Entity Name
RNRU
II. Description
It is the count of REL messages received by the MSC with the cause of "no route to
specified transit network".
It is measured when the MSC receives the REL message with the cause of "no route to
specified transit network (0000010)" or "no route to destination (0000011)".
10-164
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-165
10.14.9 Count of REL Messages Received with Cause of Subscriber Busy
I. Entity Name
RSB
II. Description
It is the count of REL messages received by the MSC with the cause of “subscriber
busy”.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

10-166
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.14.10 Count of REL Messages Received with Cause of Destination Fault
I. Entity Name
RDPCFL
II. Description
cause of “destination unreachable” or “destination incompatible”.
z CV_TERMINAL_ERROR
10-167
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

z CV_TERMINAL_ERROR
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10-168
10.14.11 Count of REL Messages Received with Other Causes
I. Entity Name
ROTH
II. Description
It is the count of REL messages received by the MSC with a cause other than the above
listed.
It is measured when the MSC receives the REL message.

z CV_TERMINAL_ERROR
z CV_BUSY
z CV_UNALOC_CODE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

z CV_TERMINAL_ERROR
10-169
z CV_BUSY
z CV_UNALOC_CODE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
10.15 ISUP Message Usage

10.15.1 Overview of MS_ISUP_MSG_USING_TRAF
Name Description
SMSG Count of certain messages sent
RMSG Count of certain messages received
10.15.2 Count of Certain Messages Sent
I. Entity Name
SMSG
10-170
II. Description
It is the count of a type of ISUP messages sent through a group of circuits.
It is measured when the MSC sends the ISUP message.
XXX XXX
A B
IV. Formula
None
10.15.3 Count of Certain Messages Received
I. Entity Name
RMSG
II. Description
It is the count of a type of ISUP messages received through a group of circuits.
It is measured when the MSC receives the ISUP message.
10-171
XXX XXX
A B
IV. Formula
None
10.16 Count of ISUP Messages

10.16.1 Overview of MS_ISUP_TOTAL_MSU_TRAF
Name Description
SMSU Count of messages sent
RMSU Count of messages received
I. Entity Name
SMSU
II. Description
It is the count of messages sent by ISUP of the MSC or a module.
It is measured when the MSC sends the ISUP message.
10-172
XXX XXX
A B
IV. Formula
None
I. Entity Name
RMSU
II. Description
It is the count of messages received by ISUP of the MSC or a module from MTP.
It is measured when the MSC receives the ISUP message.
10-173
XXX XXX
A B
IV. Formula
None
10.17 ISUP Abnormality

10.17.1 Overview of MS_ISUP_UNUSUAL_TRAF
Name Description
T17 Count of responses to RSC not received by T17
T23 Count of GRAS not received by T23
T5 Count of RLCS not received by T5
BLCIR Count of circuit remote blocking messages
NCGBA Count of failures to assign CGBA on some circuits
NCGUA Count of failures to assign CGUA on some circuits
TUCGBA Count of assignments of too many CGBAs on some circuits
TUCGUA Count of assignments of too many CGUAs on some circuits
RUEXCGBA Count of unexpected CGBAs received
RUEXCGUA Count of unexpected CGUAs received
RUEXBLA Count of unexpected BLAs received
RUEXUBA Count of unexpected UBAs received
10-174
Name Description
T13 Count of BLAs not received by T13
T15 Count of UBAs not received by T15
T19 Count of CGBAs not received by T19
T21 Count of CGUAs not received by T21
MSGER Count of CGUAs not received by T21
RUEXMSG Count of unexpected messages received
RUKNWMSG Count of unknown messages received
10.17.2 Count of Responses to RSC Not Received by T17
I. Entity Name
T17
II. Description
It is measured on each circuit. If ISUP receives no response (such as the RLC message)
after sending the RSC message to a certain circuit, it sends the RSC message every 30
seconds until receiving the response. If ISUP receives no response after sending the
message for 20 times, the T17 timer is started and ISUP sends the RSC message
every 10 minutes until receiving the response.
This entity is used to measure the event that no response is received from the circuit
within T17 duration after the RSC message is sent in delay (relative to every 30
seconds). Because the RSC message is sent under abnormal situations only (for
example, the memory of the MSC fails and information of circuit status is lost), it is
equal to the handshake message with circuit status of the peer office.
It is measured when T17 times out.
10-175
ISUP MTP
RSC
IV. Formula
None
10.17.3 Count of GRAs Not Received by T23
I. Entity Name
T23
II. Description
It is measured on a circuit group. The same as the previous entity, it is the count of
responses not received within T23 duration after a circuit group sends the GRS
message. The index reflects the instability of the circuits in a group.
ISUP MTP
GRS
IV. Formula
None
10-176
10.17.4 Count of RLCs Not Received by T5
I. Entity Name
T5
II. Description
It is measured on each circuit group. If no RLC message is received in 10 minutes after

the REL message is sent, the REL message is resent every 10 minutes for 20 times
and then the RSC message is sent instead and T17 is started. No RLC message is
received after the REL message is sent maybe because the peer office may wrongly
process messages or data. The measurement helps locate problems and severity
ISUP MTP
REL
IV. Formula
None
10.17.5 Count of Circuit Remote Blocking Messages
I. Entity Name
BLCIR
II. Description
It is the count of messages for circuit blocking.
It is measured when the MSC receives the valid blocking message or group blocking
10-177
ISUP MTP
BLO/CGB
IV. Formula
None
10.17.6 Count of Failures to Assign CGBA on Some Circuits
I. Entity Name
NCGBA
II. Description
It is the count of failures to assign CGBA messages on some circuits.
It is measured when the received circuit range indicated by the CGBA message is
incomplete.
ISUP MTP
CGB
CGBA
IV. Formula
None
10-178
10.17.7 Count of Failures to Assign CGUA on Some Circuits
I. Entity Name
NCGUA
II. Description
It is the count of failures to assign CGUA messages on some circuits.
It is measured when the received circuit range indicated by the CGUA message is
incomplete.
ISUP MTP
CGU
CGUA
IV. Formula
None
10.17.8 Count of Assignments of Too Many CGBAs on Some Circuits
I. Entity Name
TUCGBA
II. Description
It is the count of assignments of too many CGBA messages on some circuits.
It is measured when the received circuit range indicated by the CGBA message
exceeds the range indicated by the CGBA message sent by the local office.
10-179
ISUP MTP
CGB
CGBA
IV. Formula
None
10.17.9 Count of Assignments of Too Many CGUAs on Some Circuits
I. Entity Name
TUCGUA
II. Description
It is the count of assignments of too many CGUA messages on some circuits.
It is measured when the received circuit range indicated by the CGUA message
exceeds the range indicated by the CGUA message sent by the local office.
ISUP MTP
CGU
CGUA
IV. Formula
None
10-180
10.17.10 Count of Unexpected CGBAs Received
I. Entity Name
RUEXCGBA
II. Description
It is the count of unexpected CGBA messages received.
It is measured when the CGBA message is received but the local office does not send
the CGB message.
ISUP MTP
CGBA
IV. Formula
None
10.17.11 Count of Unexpected CGUAs Received
I. Entity Name
RUEXCGUA
II. Description
It is the count of unexpected CGUA messages received.
It is measured when the CGUA message is received but the local office does not send
the CGU message.
10-181
ISUP MTP
CGUA
IV. Formula
None
10.17.12 Count of Unexpected BLAs Received
I. Entity Name
RUEXBLA
II. Description
It is the count of unexpected BLA messages received.
It is measured when the BLA message is received but the local office does not send the
BLO message.
ISUP MTP
BLA
IV. Formula
None
10-182
10.17.13 Count of Unexpected UBAs Received
I. Entity Name
RUEXUBA
II. Description
It is the count of unexpected UBA messages received.
It is measured when the UBA message is received but the local office does not send the
UBL message.
ISUP MTP
UBA
IV. Formula
None
10.17.14 Count of BLAs Not Received by T13
I. Entity Name
T13
II. Description
It is measured on each circuit. The local office sends the BLO message but does not
receive the BLA message within T13 duration. This may be because circuit data of the
two offices are different, or one office processes messages wrongly.
It is measured when T13 times out after the BLO message is sent.
10-183
ISUP MTP
BLO
IV. Formula
None
10.17.15 Count of UBAs Not Received by T15
I. Entity Name
T15
II. Description
It is measured on each circuit. The local office sends the UBL message but does not
receive the UBA message within T15 duration. This may be because circuit data of the
two offices are different, or one office processes messages wrongly.
It is measured when T15 times out after the UBL message is sent.
ISUP MTP
UBL
IV. Formula
None
10-184
10.17.16 Count of CGBAs Not Received by T19
I. Entity Name
T19
II. Description
It is measured on each circuit group. The local office sends the CGB message but does
not receive the CGBA message within T19 duration.
ISUP MTP
CGB
IV. Formula
None
10.17.17 Count of CGUAs Not Received by T21
I. Entity Name
T21
II. Description
It is measured on each circuit group. The local office sends the CGU message but does
not receive the CGUA message within T21 duration.
10-185
ISUP MTP
CGU
IV. Formula
None
10.17.18 Count of Messages with Error Format
I. Entity Name
MSGER
II. Description
It is measured on each circuit group. If the format of a message received is wrong, the
message may be discarded.
It is measured when the message is received and processed.
IV. Formula
None
10.17.19 Count of Unexpected Messages Received
I. Entity Name
RUEXMSG
II. Description
It is measured on each circuit group. The unexpected message is a valid message that
can be recognized. It is received during the wrong period of the call. If too many
unexpected messages are received within a period, it indicates that the two offices
have problems in signaling negotiation.
10-186
ISUP MTP
IAM
BLO
IV. Formula
None
10.17.20 Count of Unknown Messages Received
I. Entity Name
RUKNWMSG
II. Description
It is measured on each circuit group. If too many unknown messages are received
within a period, it indicates that the two offices have problems in signaling negotiation.
IV. Formula
None
10.18 IUA Link Set

10.18.1 Overview of MS_IUA_LS_TRAF
Name Description
TUNUSE Count of unavailable states
DUNUSE Duration of unavailable state
CTRLS Count of control messages sent
CTRLR Count of control messages received
QPTMS Count of QPTM messages sent
10-187
Name Description
QPTMR Count of QPTM messages received
ERRR Count of ERROR messages received
CSBYTE Count of bytes in control messages sent
CRBYTE Count of bytes in control messages received
QSBYTE Count of bytes in QPTM messages sent
QRBYTE Count of bytes in QPTM messages received
SPPS Count of messages sent per second
RPPS Count of messages received per second
SBPS Count of bits sent per second
RBPS Count of bits received per second
I. Entity Name
TUNUSE
II. Description
It is the count of states that the IUA link set is unavailable.
It is measured when the link set is unavailable.
IV. Formula
None
I. Entity Name
DUNUSE
II. Description
It is the duration when the IUA link set is unavailable.
It is measured from the link set failure to recovery.
10-188
IV. Formula
None
10.18.4 Count of Control Messages Sent
I. Entity Name
CTRLS
II. Description
It is the count of control messages like ASPM, SSNM, and MGMT sent through the IUA
link set.
It is measured when the control message like ASPM, SSNM, and MGMT is sent
through the IUA link set.
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Linkset
A
IV. Formula
None
10.18.5 Count of Control Messages Received
I. Entity Name
CTRLR
II. Description
It is the count of control messages like ASPM, SSNM, and MGMT received through the
IUA link set.
10-189
It is measured when the control message like ASPM, SSNM, and MGMT is received
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Linkset
A
IV. Formula
None
10.18.6 Count of QPTM Messages Sent
I. Entity Name
QPTMS
II. Description
It is the count of QPTM data messages sent through the IUA link set, and helps find out
the count of messages used to transmit services.
It is measured when the QPTM data message is sent through the IUA link set.
10-190
AMG\
UMG\SG MSC Server
QPTM
IUA Linkset
A
IV. Formula
None
10.18.7 Count of QPTM Messages Received
I. Entity Name
QPTMR
II. Description
It is the count of QPTM data messages received through the IUA link set, and helps find
out the count of messages used to transmit services.
It is measured when the QPTM data message is received through the IUA link set.
AMG\
UMG\SG MSC Server
QPTM
IUA Linkset
A
IV. Formula
None
10-191
10.18.8 Count of ERROR Messages Received
I. Entity Name
ERRR
II. Description
It is the count of ERROR messages received through the IUA link set.
It is measured when the ERROR message like illegal parameter is received through the
IUA link set.
AMG\
UMG\SG MSC Server
ERROR Message
IUA Linkset
A
IV. Formula
None
10.18.9 Count of Bytes in Control Messages Sent
I. Entity Name
CSBYTE
II. Description
It is the count of bytes in control messages like ASPM, SSNM, and MGMT sent through
the IUA link set.
It is measured when the control message like ASPM, SSNM or MGMT is sent through
the IUA link set.
10-192
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Linkset A
IV. Formula
None
10.18.10 Count of Bytes in Control Messages Received
I. Entity Name
CRBYTE
II. Description
It is the count of bytes in control messages like ASPM, SSNM, and MGMT received
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Linkset
A
IV. Formula
None
10-193
10.18.11 Count of Bytes in QPTM Messages Sent
I. Entity Name
QSBYTE
II. Description
It is the count of bytes in QPTM data messages sent through the IUA link set, and helps
find out the count of bytes in messages used to transmit services.
It is measured when the QPTM data message is sent through the IUA link set.
AMG\
UMG\SG MSC Server
QPTM
IUA Linkset
A
IV. Formula
None
10.18.12 Count of Bytes in QPTM Messages Received
I. Entity Name
QRBYTE
II. Description
It is the count of bytes in QPTM data messages received through the IUA link set, and
helps find out the count of bytes in messages used to transmit services.
It is measured when the QPTM data message is received through the IUA link set.
10-194
AMG\
UMG\SG MSC Server
QPTM
IUA Linkset
A
IV. Formula
None
I. Entity Name
SPPS
II. Description
It is the count of messages sent through the IUA link set every second.
IV. Formula
None
I. Entity Name
RPPS
II. Description
It is the count of messages received through the IUA link set every second.
IV. Formula
None
10-195
I. Entity Name
SBPS
II. Description
It is the count of bits sent through the IUA link set every second.
IV. Formula
None
I. Entity Name
RBPS
II. Description
It is the count of bits received through the IUA link set every second.
IV. Formula
None
10.19 IUA Signaling Link

10.19.1 Overview of MS_IUA_LINK_TRAF
Name Description
OSTIMES Count of unavailable states
OSTIME Duration of unavailable state

CTIMES Count of congestion
CTIME Duration of congestion
10-196
Name Description
QPTMS Count of QPTM messages sent
QPTMR Count of QPTM messages received
ERRR Count of ERROR messages received
QSBYTE Count of bytes in QPTM messages sent
QRBYTE Count of bytes in QPTM messages received
I. Entity Name
OSTIMES
II. Description
It is the count of states that the IUA link is unavailable.
It is measured when the link is unavailable.
IV. Formula
None
I. Entity Name
OSTIME
II. Description
It is the duration when the IUA link is unavailable.
It is measured from the link failure to recovery.
10-197
IV. Formula
None
I. Entity Name
CTIMES
II. Description
It is the count of congestion on the IUA link.
It is measured when the link is congested.
IV. Formula
None
10.19.5 Duration of Congestion
I. Entity Name
CTIME
II. Description
It is the duration of congestion on the IUA link.
It is measured from the link congestion to recovery.
IV. Formula
None
I. Entity Name
CTRLS
II. Description
It is the count of control messages like ASPM, SSNM, and MGMT sent through the IUA
link.
10-198
through the IUA link.
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Link
A
IV. Formula
None
I. Entity Name
CTRLR
II. Description
IUA link.
10-199
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Link
A
IV. Formula
None
10.19.8 Count of QPTM Messages Sent
I. Entity Name
QPTMS
II. Description
It is the count of QPTM data messages sent through the IUA link, and helps find out the
count of messages used to transmit services.
It is measured when the QPTM data message is sent through the IUA link.
AMG\
UMG\SG MSC Server
QPTM
IUA Link
A
IV. Formula
None
10-200
10.19.9 Count of QPTM Messages Received
I. Entity Name
QPTMR
II. Description
It is the count of QPTM data messages received through the IUA link, and helps find out
It is measured when the QPTM data message is received through the IUA link.
AMG\
UMG\SG MSC Server
QPTM
IUA Link
A
IV. Formula
None
I. Entity Name
ERRR
II. Description
It is the count of ERROR messages received through the IUA link.
IUA link.
10-201
AMG\
UMG\SG MSC Server
ERROR Message
IUA Link
A
IV. Formula
None
I. Entity Name
CSBYTE
II. Description
the IUA link.
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Link
A
IV. Formula
None
10-202
I. Entity Name
CRBYTE
II. Description
AMG\
UMG\SG MSC Server
ASPM,SSNM,MGMT
IUA Link
A
IV. Formula
None
10.19.13 Count of Bytes in QPTM Messages Sent
I. Entity Name
QSBYTE
II. Description
It is the count of bytes in QPTM data messages sent through the IUA link, and helps find
out the count of bytes in messages used to transmit services.
It is measured when the QPTM data message is sent through the IUA link.
10-203
AMG\
UMG\SG MSC Server
QPTM
IUA Link
A
IV. Formula
None
10.19.14 Count of Bytes in QPTM Messages Received
I. Entity Name
QRBYTE
II. Description
It is the count of bytes in QPTM data messages received through the IUA link, and
It is measured when the QPTM data message is received through the IUA link.
AMG\
UMG\SG MSC Server
QPTM
IUA Link
A
IV. Formula
None
10-204
I. Entity Name
SPPS
II. Description
It is the count of messages sent through the IUA link every second.
IV. Formula
None
I. Entity Name
RPPS
II. Description
It is the count of messages received through the IUA link every second.
IV. Formula
None
I. Entity Name
SBPS
II. Description
It is the count of bits sent through the IUA link every second.
IV. Formula
None
10-205
I. Entity Name
RBPS
II. Description
It is the count of bits received through the IUA link every second.
IV. Formula
None
10.20 M2UA Link Set

10.20.1 Overview of MS_M2UA_LS_TRAF
Name Description
MAUPS Count of MAUP messages sent
MAUPR Count of MAUP messages received
ERROR Count of ERROR messages received

MSBYTE Count of bytes in MAUP messages sent
MRBYTE Count of bytes in MAUP messages received
10-206
I. Entity Name
CTRLS
II. Description
It is the count of control messages like ASPM, SSNM, and MGMT sent through the
M2UA link set.
through the M2UA link set.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Linkset
A
IV. Formula
None
I. Entity Name
CTRLR
II. Description
M2UA link set.
10-207
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Linkset A
IV. Formula
None
10.20.4 Count of MAUP Messages Sent
I. Entity Name
MAUPS
II. Description
It is the count of MAUP data messages sent through the M2UA link set, and helps find
It is measured when the MAUP data message is sent through the M2UA link set.
UMG\SG MSC Server
MAUP
M2UA Linkset A
IV. Formula
None
10.20.5 Count of MAUP Messages Received
I. Entity Name
MAUPR
10-208
II. Description
It is the count of MAUP data messages received through the M2UA link set, and helps
find out the count of messages used to transmit services.
It is measured when the MAUP data message is received through the M2UA link set.
UMG\SG MSC Server
MAUP
M2UA Linkset A
IV. Formula
None
I. Entity Name
ERROR
II. Description
It is the count of ERROR messages received through the M2UA link set.
It is measured when the ERROR message like wrong parameter is received through
the M2UA link set.
10-209
UMG\SG MSC Server
ERROR Message
M2UA Linkset A
IV. Formula
None
I. Entity Name
CSBYTE
II. Description
the M2UA link set.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Linkset A
IV. Formula
None
10-210
I. Entity Name
CRBYTE
II. Description
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Linkset A
IV. Formula
None
10.20.9 Count of Bytes in MAUP Messages Sent
I. Entity Name
MSBYTE
II. Description
It is the count of bytes in MAUP data messages sent through the M2UA link set, and
It is measured when the MAUP data message is sent through the M2UA link set.
10-211
UMG\SG MSC Server
MAUP
M2UA Linkset A
IV. Formula
None
10.20.10 Count of Bytes in MAUP Messages Received
I. Entity Name
MRBYTE
II. Description
It is the count of bytes in MAUP data messages received through the M2UA link set,
and helps find out the count of bytes in messages used to transmit services.
It is measured when the MAUP data message is received through the M2UA link set.
UMG\SG MSC Server
MAUP
M2UA Linkset A
IV. Formula
None
I. Entity Name
SPPS
10-212
II. Description
It is the count of messages sent through the M2UA link set every second.
IV. Formula
None
I. Entity Name
RPPS
II. Description
It is the count of messages received through the M2UA link set every second.
IV. Formula
None
I. Entity Name
SBPS
II. Description
It is the count of bits sent through the M2UA link set every second.
IV. Formula
None
I. Entity Name
RBPS
10-213
II. Description
It is the count of bits received through the M2UA link set every second.
IV. Formula
None
10.21 M2UA Link

10.21.1 Overview of MS_M2UA_LINK_TRAF
Name Description
TUNAVA Count of unavailable states
DUNAVA Duration of unavailable state
OSTIMES Count of congestion
OSTIME Duration of congestion
MAUPS Count of MAUP messages sent
MAUPR Count of MAUP messages received
ERROR Count of ERROR messages received
MSBYTE Count of bytes in MAUP messages sent
MRBYTE Count of bytes in MAUP messages received

10-214
I. Entity Name
TUNAVA
II. Description
It is the count of states that the M2UA link is unavailable.
IV. Formula
None
I. Entity Name
DUNAVA
II. Description
It is the duration when the M2UA link is unavailable.
IV. Formula
None
I. Entity Name
OSTIMES
II. Description
It is the count of congestion on the M2UA link.
IV. Formula
None
10-215
I. Entity Name
OSTIME
II. Description
It is the duration of congestion on the M2UA link.
IV. Formula
None
I. Entity Name
CTRLS
II. Description
M2UA link.
through the M2UA link.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Link A
IV. Formula
None
10-216
I. Entity Name
CTRLR
II. Description
M2UA link.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Link A
IV. Formula
None
10.21.8 Count of MAUP Messages Sent
I. Entity Name
MAUPS
II. Description
It is the count of MAUP data messages sent through the M2UA link, and helps find out
It is measured when the MAUP data message is sent through the M2UA link.
10-217
UMG\SG MSC Server
MAUP
M2UA Link A
IV. Formula
None
10.21.9 Count of MAUP Messages Received
I. Entity Name
MAUPR
II. Description
It is the count of MAUP data messages received through the M2UA link, and helps find
It is measured when the MAUP data message is received through the M2UA link.
UMG\SG MSC Server
MAUP
M2UA Link A
IV. Formula
None
I. Entity Name
ERROR
10-218
II. Description
It is the count of ERROR messages received through the M2UA link.
M2UA link.
UMG\SG MSC Server
ERROR Message
M2UA Link A
IV. Formula
None
I. Entity Name
CSBYTE
II. Description
the M2UA link.
10-219
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Link A
IV. Formula
None
I. Entity Name
CRBYTE
II. Description
UMG\SG MSC Server
ASPM,SSNM,MGMT
M2UA Link A
IV. Formula
None
10-220
10.21.13 Count of Bytes in MAUP Messages Sent
I. Entity Name
MSBYTE
II. Description
It is the count of bytes in MAUP data messages sent through the M2UA link, and helps
It is measured when the MAUP data message is sent through the M2UA link.
UMG\SG MSC Server
MAUP
M2UA Link A
IV. Formula
None
10.21.14 Count of Bytes in MAUP Messages Received
I. Entity Name
MRBYTE
II. Description
It is the count of bytes in MAUP data messages received through the M2UA link, and
It is measured when the MAUP data message is received through the M2UA link.
10-221
UMG\SG MSC Server
MAUP
M2UA Link A
IV. Formula
None
I. Entity Name
SPPS
II. Description
It is the count of messages sent through the M2UA link every second.
IV. Formula
None
I. Entity Name
RPPS
II. Description
It is the count of messages received through the M2UA link every second.
IV. Formula
None
10-222
I. Entity Name
SBPS
II. Description
It is the count of bits sent through the M2UA link every second.
IV. Formula
None
I. Entity Name
RBPS
II. Description
It is the count of bits received through the M2UA link every second.
IV. Formula
None
10.22 M3UA Destination Entity

10.22.1 Overview of MS_M3UA_DEST_ENTITY_TRAF
Name Description
TINACSBL Count of failed accesses
DINACSBL Duration of failed access
10-223
10.22.2 Count of Failed Accesses
I. Entity Name
TINACSBL
II. Description
It is the count of failures to access the M3UA destination entity.
It is measured when the M3UA destination entity is inaccessible.
IV. Formula
None
10.22.3 Duration of Failed Access
I. Entity Name
DINACSBL
II. Description
It is the duration of failure to access the M3UA destination entity.
It is measured from failure to success in accessing the M3UA destination entity.
IV. Formula
None
10.23 M3UA Signaling Link

10.23.1 Overview of MS_M3UA_LINK_TRAF
Name Description
TCONN Count of unavailable states

TSCON Count of congestion
DSCON Duration of congestion
NAMSGT Count of control messages sent
NAMSGR Count of control messages received
10-224
Name Description
BAMSGT Count of bytes in control messages sent
BAMSGR Count of bytes in control messages received
NDMSGT Count of data messages sent
NDMSGR Count of data messages received
BDMSGT Count of bytes in data messages sent
BDMSGR Count of bytes in data messages received
SSCCPMSU Count of SCCP messages sent
RSCCPMSU Count of SCCP messages received
SSCCPOCT Count of bytes in SCCP messages sent
RSCCPOCT Count of bytes in SCCP messages received
STUPMSU Count of TUP messages sent
RTUPMSU Count of TUP messages received
STUPOCT Count of bytes in TUP messages sent
RTUPOCT Count of bytes in TUP messages received

SISUPMSU Count of ISUP messages sent
RISUPMSU Count of ISUP messages received
SISUPOCT Count of bytes in ISUP messages sent

RISUPOCT Count of bytes in ISUP messages received
NMSGT Count of messages sent
NMSGR Count of messages received
BMSGT Count of bytes in messages sent
BMSGR Count of bytes in messages received
I. Entity Name
TCONN
10-225
II. Description
It is the count of states that the M3UA link is unavailable.
IV. Formula
None
I. Entity Name
DUNUSE
II. Description
It is the duration when the M3UA link is unavailable.
IV. Formula
None
I. Entity Name
TSCON
II. Description
It is the count of congestion on the M3UA link.
IV. Formula
None
I. Entity Name
DSCON
10-226
II. Description
It is the duration of congestion on the M3UA link.
IV. Formula
None
I. Entity Name
NAMSGT
II. Description
M3UA link.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Link A
IV. Formula
None
I. Entity Name
NAMSGR
10-227
II. Description
M3UA link.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Link A
IV. Formula
None
I. Entity Name
BAMSGT
II. Description
the M3UA link.
10-228
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Link A
IV. Formula
None
I. Entity Name
BAMSGR
II. Description
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Link A
IV. Formula
None
10-229
10.23.10 Count of Data Messages Sent
I. Entity Name
NDMSGT
II. Description
It is the count of data messages sent through the M3UA link, and helps find out the
It is measured when the data message is sent through the M3UA link.
UMG\SG MSC Server
DATA(ISUP,SCCP,BICC...)
M3UA Link A
IV. Formula
None
10.23.11 Count of Data Messages Received
I. Entity Name
NDMSGR
II. Description
It is the count of data messages received through the M3UA link, and helps find out the
It is measured when the data message is received through the M3UA link.
10-230
UMG\SG MSC Server
M3UA Link A
IV. Formula
None
10.23.12 Count of Bytes in Data Messages Sent
I. Entity Name
BDMSGT
II. Description
It is the count of bytes in data messages sent through the M3UA link, and helps find out
the count of bytes in messages used to transmit services.
It is measured when the data message is sent through the M3UA link.
UMG\SG MSC Server
M3UA Link A
IV. Formula
None
10.23.13 Count of Bytes in Data Messages Received
I. Entity Name
BDMSGR
10-231
II. Description
It is the count of bytes in data messages received through the M3UA link, and helps find
It is measured when the data message is received through the M3UA link.
UMG\SG MSC Server
M3UA Link A
IV. Formula
None
10.23.14 Count of SCCP Messages Sent
I. Entity Name
SSCCPMSU
II. Description
It is the count of SCCP messages sent through the M3UA link.
It is measured when the SCCP message is sent through the M3UA link.
10-232
UMG\SG MSC Server
DATA(SCCP)
M3UA Link A
IV. Formula
None
10.23.15 Count of SCCP Messages Received
I. Entity Name
RSCCPMSU
II. Description
It is the count of SCCP messages received through the M3UA link.
It is measured when the SCCP message is received through the M3UA link.
UMG\SG MSC Server
DATA(SCCP)
M3UA Link A
IV. Formula
None
10.23.16 Count of Bytes in SCCP Messages Sent
I. Entity Name
SSCCPOCT
10-233
II. Description
It is the count of bytes in SCCP messages sent through the M3UA link.
It is measured when the SCCP message is sent through the M3UA link.
UMG\SG MSC Server
DATA(SCCP)
M3UA Link A
IV. Formula
None
10.23.17 Count of Bytes in SCCP Messages Received
I. Entity Name
RSCCPOCT
II. Description
It is the count of bytes in SCCP messages received through the M3UA link.
It is measured when the SCCP message is received through the M3UA link.
10-234
UMG\SG MSC Server
DATA(SCCP)
M3UA Link A
IV. Formula
None
10.23.18 Count of TUP Messages Sent
I. Entity Name
STUPMSU
II. Description
It is the count of TUP messages sent through the M3UA link.
It is measured when the TUP message is sent through the M3UA link.
UMG\SG MSC Server
DATA(TUP)
M3UA Link A
IV. Formula
None
10.23.19 Count of TUP Messages Received
I. Entity Name
RTUPMSU
10-235
II. Description
It is the count of TUP messages received through the M3UA link.
It is measured when the TUP message is received through the M3UA link.
UMG\SG MSC Server
DATA(TUP)
M3UA Link A
IV. Formula
None
10.23.20 Count of Bytes in TUP Messages Sent
I. Entity Name
STUPOCT
II. Description
It is the count of bytes in TUP messages sent through the M3UA link.
It is measured when the TUP message is sent through the M3UA link.
10-236
UMG\SG MSC Server
DATA(TUP)
M3UA Link A
IV. Formula
None
10.23.21 Count of Bytes in TUP Messages Received
I. Entity Name
RTUPOCT
II. Description
It is the count of bytes in TUP messages received through the M3UA link.
It is measured when the TUP message is received through the M3UA link.
UMG\SG MSC Server
DATA(TUP)
M3UA Link A
IV. Formula
None
10.23.22 Count of ISUP Messages Sent
I. Entity Name
SISUPMSU
10-237
II. Description
It is the count of ISUP messages sent through the M3UA link.
It is measured when the ISUP message is sent through the M3UA link.
UMG\SG MSC Server
DATA(ISUP)
M3UA Link A
IV. Formula
None
10.23.23 Count of ISUP Messages Received
I. Entity Name
RISUPMSU
II. Description
It is the count of ISUP messages received through the M3UA link.
It is measured when the ISUP message is received through the M3UA link.
10-238
UMG\SG MSC Server
DATA(ISUP)
M3UA Link A
IV. Formula
None
10.23.24 Count of Bytes in ISUP Messages Sent
I. Entity Name
SISUPOCT
II. Description
It is the count of bytes in ISUP messages sent through the M3UA link.
It is measured when the ISUP message is sent through the M3UA link.
UMG\SG MSC Server
DATA(ISUP)
M3UA Link A
IV. Formula
None
10.23.25 Count of Bytes in ISUP Messages Received
I. Entity Name
RISUPOCT
10-239
II. Description
It is the count of bytes in ISUP messages received through the M3UA link.
It is measured when the ISUP message is received through the M3UA link.
UMG\SG MSC Server
DATA(ISUP)
M3UA Link A
IV. Formula
None
I. Entity Name
NMSGT
II. Description
It is the count of total messages sent through the M3UA link, and helps find out the
traffic through the M3UA link.
It is measured when a message is sent through the M3UA link.

10-240
UMG\SG MSC Server
M3UA Message
M3UA Link A
IV. Formula
None
I. Entity Name
NMSGR
II. Description
It is the count of total messages received through the M3UA link, and helps find out the
traffic through the M3UA link.
It is measured when a message is received through the M3UA link.

UMG\SG MSC Server
M3UA Message
M3UA Link A
IV. Formula
None
I. Entity Name
BMSGT
10-241
II. Description
It is the count of total bytes in messages sent through the M3UA link.
It is measured when a message is sent through the M3UA link.

UMG\SG MSC Server
M3UA Message
M3UA Link A
IV. Formula
None
I. Entity Name
BMSGR
II. Description
It is the count of total bytes in messages received through the M3UA link.
It is measured when a message is received through the M3UA link.

10-242
UMG\SG MSC Server
M3UA Message
M3UA Link A
IV. Formula
None
I. Entity Name
SPPS
II. Description
It is the count of messages sent through the M3UA link every second.
IV. Formula
None
I. Entity Name
RPPS
II. Description
It is the count of messages received through the M3UA link every second.
IV. Formula
None
10-243
I. Entity Name
SBPS
II. Description
It is the count of bits sent through the M3UA link every second.
IV. Formula
None
I. Entity Name
RBPS
II. Description
It is the count of bits received through the M3UA link every second.
IV. Formula
None
10.24 M3UA Signaling Link Set

10.24.1 Overview of MS_M3UA_LS_TRAF
Name Description
TUNUSE Count of unavailable states

NAMSGT Count of control messages sent
NAMSGR Count of control messages received
BAMSGT Count of bytes in control messages sent
BAMSGR Count of bytes in control messages received
10-244
Name Description
NDMSGT Count of data messages sent
NDMSGR Count of data messages received
BDMSGT Count of bytes in data messages sent
BDMSGR Count of bytes in data messages received
STUPMSG Count of SCCP messages sent
RTUPMSG Count of SCCP messages received
STUPBYTE Count of bytes in SCCP messages sent
RTUPBYTE Count of bytes in SCCP messages received
SISUPMSG Count of TUP messages sent
RISUPMSG Count of TUP messages received
SISUPBYTE Count of bytes in TUP messages sent
RISUPBYTE Count of bytes in TUP messages received

NMSGT Count of messages sent

NMSGR Count of messages received
BMSGT Count of bytes in messages sent
BMSGR Count of bytes in messages received
I. Entity Name
TUNUSE
II. Description
It is the count of states that the M3UA link set is unavailable.
10-245
It is measured when the link set is unavailable.
IV. Formula
None
I. Entity Name
DUNUSE
II. Description
It is the duration when the M3UA link set is unavailable.
IV. Formula
None
I. Entity Name
NAMSGT
II. Description
M3UA link set.
10-246
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Linkset A
IV. Formula
None
I. Entity Name
NAMSGR
II. Description
M3UA link set.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Linkset A
IV. Formula
None
10-247
I. Entity Name
BAMSGT
II. Description
the M3UA link set.
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Linkset A
IV. Formula
None
I. Entity Name
BAMSGR
II. Description
10-248
UMG\SG MSC Server
ASPM,SSNM,MGMT
M3UA Linkset A
IV. Formula
None
10.24.8 Count of Data Messages Sent
I. Entity Name
NDMSGT
II. Description
It is the count of data messages sent through the M3UA link set, and helps find out the
It is measured when the data message is sent through the M3UA link set.
UMG\SG MSC Server
M3UA Linkset A
IV. Formula
None
10.24.9 Count of Data Messages Received
I. Entity Name
NDMSGR
10-249
II. Description
It is the count of data messages received through the M3UA link set, and helps find out
It is measured when the data message is received through the M3UA link set.
UMG\SG MSC Server
M3UA Linkset A
IV. Formula
None
10.24.10 Count of Bytes in Data Messages Sent
I. Entity Name
BDMSGT
II. Description
It is the count of bytes in data messages sent through the M3UA link set, and helps find
It is measured when the data message is sent through the M3UA link set.
10-250
UMG\SG MSC Server
M3UA Linkset A
IV. Formula
None
10.24.11 Count of Bytes in Data Messages Received
I. Entity Name
BDMSGR
II. Description
It is the count of bytes in data messages received through the M3UA link set, and helps
It is measured when the data message is received through the M3UA link set.
UMG\SG MSC Server
M3UA Linkset A
IV. Formula
None
I. Entity Name
STUPMSG
10-251
II. Description
It is the count of SCCP messages sent through the M3UA link set.
It is measured when the SCCP message is sent through the M3UA link set.
UMG\SG MSC Server
DATA(SCCP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
RTUPMSG
II. Description
It is the count of SCCP messages received through the M3UA link set.
It is measured when the SCCP message is received through the M3UA link set.
10-252
UMG\SG MSC Server
DATA(SCCP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
STUPBYTE
II. Description
It is the count of bytes in SCCP messages sent through the M3UA link set.
It is measured when the SCCP message is sent through the M3UA link set.
UMG\SG MSC Server
DATA(SCCP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
RTUPBYTE
10-253
II. Description
It is the count of bytes in SCCP messages received through the M3UA link set.
It is measured when the SCCP message is received through the M3UA link set.
UMG\SG MSC Server
DATA(SCCP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
SISUPMSG
II. Description
It is the count of TUP messages sent through the M3UA link set.
It is measured when the TUP message is sent through the M3UA link set.
10-254
UMG\SG MSC Server
DATA(TUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
RISUPMSG
II. Description
It is the count of TUP messages received through the M3UA link set.
It is measured when the TUP message is received through the M3UA link set.
UMG\SG MSC Server
DATA(TUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
SISUPBYTE
10-255
II. Description
It is the count of bytes in TUP messages sent through the M3UA link set.
It is measured when the TUP message is sent through the M3UA link set.
UMG\SG MSC Server
DATA(TUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
RISUPBYTE
II. Description
It is the count of bytes in TUP messages received through the M3UA link set.
It is measured when the TUP message is received through the M3UA link set.
10-256
UMG\SG MSC Server
DATA(TUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
SISUPMSU
II. Description
It is the count of ISUP messages sent through the M3UA link set.
It is measured when the ISUP message is sent through the M3UA link set.
UMG\SG MSC Server
DATA(ISUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
RISUPMSU
10-257
II. Description
It is the count of ISUP messages received through the M3UA link set.
It is measured when the ISUP message is received through the M3UA link set.
UMG\SG MSC Server
DATA(ISUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
SISUPOCT
II. Description
It is the count of bytes in ISUP messages sent through the M3UA link set.
It is measured when the ISUP message is sent through the M3UA link set.
10-258
UMG\SG MSC Server
DATA(ISUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
RISUPOCT
II. Description
It is the count of bytes in ISUP messages received through the M3UA link set.
It is measured when the ISUP message is received through the M3UA link set.
UMG\SG MSC Server
DATA(ISUP)
M3UA Linkset A
IV. Formula
None
I. Entity Name
NMSGT
10-259
II. Description
It is the count of total messages sent through the M3UA link set.
It is measured when a message is sent through the M3UA link set.

UMG\SG MSC Server
M3UA Message
M3UA Linkset A
IV. Formula
None
I. Entity Name
NMSGR
II. Description
It is the count of total messages received through the M3UA link set.
It is measured when a message is received through the M3UA link set.

10-260
UMG\SG MSC Server
M3UA Message
M3UA Linkset A
IV. Formula
None
I. Entity Name
BMSGT
II. Description
It is the count of total bytes in messages sent through the M3UA link set.
It is measured when a message is sent through the M3UA link set.

UMG\SG MSC Server
M3UA Message
M3UA Linkset A
IV. Formula
None
I. Entity Name
BMSGR
10-261
II. Description
It is the count of total bytes in messages received through the M3UA link set.
It is measured when a message is received through the M3UA link set.

UMG\SG MSC Server
M3UA Message
M3UA Linkset A
IV. Formula
None
I. Entity Name
SPPS
II. Description
It is the count of messages sent through the M3UA link set every second.
IV. Formula
None
I. Entity Name
RPPS
II. Description
It is the count of messages received through the M3UA link set every second.
10-262
IV. Formula
None
I. Entity Name
SBPS
II. Description
It is the count of bits sent through the M3UA link set every second.
IV. Formula
None
I. Entity Name
RBPS
II. Description
It is the count of bits received through the M3UA link set every second.
IV. Formula
None
10-263
10.25 MAP Public Service Procedure Error

10.25.1 Overview of MS_TYPE_MAP_PUBLIC_SERVICE
Name Description
SORDL49 Count of session rejections at local MAP (OPEN_RSP)
RODRR49 Count of session rejections at remote MAP (OPEN_CNF)
NUSL49 Count of session aborts at local MAP (U_ABORT_REQ)

NURR49 Count of session aborts at remote MAP (U_ABORT_IND)
NPP49 Count of provider aborts (P_ABORT)
NN49 Count of notice indications (NOTICE)

Count of MAP_OPEN_RSP session rejections due to other
SORDNRG49
causes
Count of MAP_OPEN_RSP session rejections due to invalid
SORDIDR49
destination reference
Count of MAP_OPEN_RSP session rejections due to invalid

SORDIOR49
origination reference
Count of MAP_OPEN_RSP session rejections due to

SORDACNS49
application context not supported
Count of MAP_OPEN_RSP session rejections due to potential

SORDPVI49
version incompatibility
Count of MAP_OPEN_CNF Session Rejections Due to Other

RODRNRG49
Causes
Count of MAP_OPEN_CNF session rejections due to invalid
RODRIDR49
destination reference
Count of MAP_OPEN_CNF session rejections due to invalid

RODRIOR49
origination reference
Count of MAP_OPEN_CNF session rejections due to

RODRACNS49
application context not supported
Count of MAP_OPEN_CNF session rejections due to potential

RODRPVI49
Count of MAP_U_ABORT_REQ messages due to application

RUSPE49
program error
Count of MAP_U_ABORT_REQ messages due to subscriber

RUSRL49
resource limited
Count of MAP_U_ABORT_REQ messages due to resource

RUSRU49
unavailable
10-264
Name Description
Count of MAP_U_ABORT_REQ messages due to application
AUSAPC49
program cancelled
Count of MAP_U_ABORT_IND messages due to application
RURPE49
program error
Count of MAP_U_ABORT_IND messages due to subscriber
RURRL49
resource limited
Count of MAP_U_ABORT_IND messages due to resource
RURRU49
unavailable
Count of MAP_U_ABORT_IND messages due to application
RUAPC49
program cancelled
Count of MAP_P_ABORT_IND messages due to provider
RMRPM49
failure
Count of MAP_P_ABORT_IND messages due to supported
RMRSDXR49
session released
Count of MAP_P_ABORT_IND messages due to provider
RMRRL49
resource limited
RMRMA49 Count of MAP_P_ABORT_IND messages due to maintenance
Count of MAP_P_ABORT_IND messages due to potential
RMRVI49
Count of MAP_P_ABORT_IND messages due to abnormal

RMRAMD49
session
Count of MAP_NOTICE_IND messages due to abnormal event

RMRAEDP49
detected by remote MAP
Count of MAP_NOTICE_IND messages due to response
RMRRRP49
rejected by remote MAP
Count of MAP_NOTICE_IND messages due to abnormal event

RMRAERP49
received from remote MAP
10.25.2 Count of Session Rejections at Local MAP (OPEN_RSP)
I. Entity Name
SORDL49
II. Description
The local MAP rejects a session initiated by the remote MAP due to any cause.
10-265
It is measured when the local MAP service layer receives the message
MAP_OPEN_REQ and then sends the message MAP_OPEN_RSP to the MAPPM to
reject the session.
HLR MSC/VLR
MAP_OPEN_REQ
A
MAP_OPEN_RSP
IV. Formula
None
10.25.3 Count of Session Rejections at Remote MAP (OPEN_CNF)
I. Entity Name
RODRR49
II. Description
The remote MAP rejects a session initiated by the local MAP due to any cause.
It is measured when the MAPPM receives an abnormal acknowledgement like

U_ABORT or P_ABORT or a normal acknowledgement containing session rejection
information, after the local MAP initiates a session. The MAPPM sends the message
MAP_OPEN_CNF to the local MAP to reject the session.
10-266
HLR MSC/VLR
MAP_U_ABORT / MAP_P_ABORT
A
MAP_OPEN_CNF
IV. Formula
None
10.25.4 Count of Session Aborts at Local MAP (U_ABORT_REQ)
I. Entity Name
NUSL49
II. Description
The local MAP detects that the session is abnormal and aborts it due to any cause.
It is measured when the local MAP detects that the session is abnormal and then sends
the MAP_U_ABORT_REQ message to the MAPPM to abort the session.
10-267
HLR MSC/VLR
MAP_U_ABORT_REQ
IV. Formula
None
10.25.5 Count of Session Aborts at Remote MAP (U_ABORT_IND)
I. Entity Name
NURR49
II. Description
The remote MAP detects that the session is abnormal and aborts it due to any cause.
It is measured when the local MAPPM receives MAP_U_ABORT_IND from the remote
MAPPM and informs the local MAP of it, after the session is set up.
10-268
HLR MSC/VLR
MAP_U_ABORT_IND
IV. Formula
None
10.25.6 Count of Provider Aborts (P_ABORT)
I. Entity Name
NPP49
II. Description
The local or remote MAP bottom layer detects that the session is abnormal due to any
cause.
It is measured when the local or remote MAP bottom layer detects that the session is
abnormal, and the session cannot continue and must be terminated.
10-269
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.7 Count of Notice Indications (NOTICE)
I. Entity Name
NN49
II. Description
The MAPPM notifies the MAP that an error occurs at the local or remote bottom layer,
and then the MAP decides to abort or continue the session due to any cause.
It is measured when the local or remote MAPPM detects an error that does not affect
the session and informs the MAP, and then the MAP decides the subsequent procedure
of the session.
10-270
HLR MSC/VLR
MAP_NOTICE_IND
IV. Formula
None
10.25.8 Count of MAP_OPEN_RSP Session Rejections Due to Other Causes
I. Entity Name
SORDNRG49
II. Description
The local MAP rejects the session initiated by the remote MAP without giving any
reason.
It is measured when the MAP receives a session initiation request and then sends the
message MAP_OPEN_RSP to the MAPPM to reject the session, without any reason
given or the reason “no reason”.
10-271
HLR MSC/VLR
MAP_OPEN_RSP
IV. Formula
None
10.25.9 Count of MAP_OPEN_RSP Session Rejections Due to Invalid

Destination Reference
I. Entity Name
SORDIDR49
II. Description
The supplementary services related session initiated by the remote MAP contains no
destination reference (IMSI).
If the session is related to supplementary services, the message MAP_OPEN_IND

must contain the valid destination reference; otherwise, the session is rejected with the
cause of “invalid destination reference”.
10-272
HLR MSC/VLR
MAP_OPEN_RSP
IV. Formula
None
10.25.10 Count of MAP_OPEN_RSP Session Rejections Due to Invalid

Origination Reference
I. Entity Name
SORDIOR49
II. Description
The supplementary services related session initiated by the remote MAP contains no
origination reference (VLR_NO).
If the session is related to supplementary services, the message MAP_OPEN_IND

must contain the valid origination reference. Otherwise, the session is rejected with the
cause of “invalid origination reference”.
10-273
HLR MSC/VLR
MAP_OPEN_RSP
IV. Formula
None
10.25.11 Count of MAP_OPEN_RSP Session Rejections Due to Application

Context Not Supported
I. Entity Name
SORDACNS49
II. Description
The local MAP does not support the application context of the session.
It is measured when the MAP receives the session initiation request and then sends the
message MAP_OPEN_RSP to the MAPPM to reject the session, with the cause of
“application context not supported”. This may be because the version of the local MAP
is earlier than that of the remote MAP.
10-274
HLR MSC/VLR
MAP_OPEN_RSP
IV. Formula
None
10.25.12 Count of MAP_OPEN_RSP Session Rejections Due to Potential

Version Incompatibility
I. Entity Name
SORDPVI49
II. Description
The version of the local MAP is incompatible with that of the remote MAP.
It is measured when the MAP receives the session initiation request and then sends the
message MAP_OPEN_RSP to the MAPPM to reject the session, with the cause of
“potential version incompatibility”. This may be because the MAP detects an error
caused by version incompatibility.
10-275
HLR MSC/VLR
MAP_OPEN_RSP
IV. Formula
None
10.25.13 Count of MAP_OPEN_CNF Session Rejections Due to Other Causes
I. Entity Name
RODRNRG49
II. Description
The session initiated by the local MAP is rejected or detected with errors by the remote
MAP, but no specific reason is given.
The local MAPPM is in the “session to be established” status and finds that the session
is rejected or aborted by the remote MAPPM without any reason. It then sends the
primitive MAP_OPEN_CNF to the MAP to reject the session, with the cause of “other
causes”.
10-276
HLR MSC/VLR
MAP_OPEN_CNF
IV. Formula
None
10.25.14 Count of MAP_OPEN_CNF Session Rejections Due to Invalid

Destination Reference
I. Entity Name
RODRIDR49
II. Description
MAP, with the cause of “invalid destination reference".
is aborted by the remote MAPPM, with the cause of “invalid destination reference”. It
then sends the primitive MAP_OPEN_CNF to the MAP to reject the session, with the
cause of “invalid destination reference”. For example, the destination reference is
mandatory for a supplementary services related session; however, if the destination
reference is invalid or nonexistent, the session is rejected.
10-277
HLR MSC/VLR
MAP_OPEN_CNF
IV. Formula
None
10.25.15 Count of MAP_OPEN_CNF Session Rejections Due to Invalid

Origination Reference
I. Entity Name
RODRIOR49
II. Description
MAP, with the cause of “invalid origination reference".
is aborted by the remote MAPPM, with the cause of “invalid origination reference”. It
cause of “invalid origination reference”. For example, the origination reference is
mandatory for a supplementary services related session; however, if the origination
reference is invalid or nonexistent, the session is rejected.
10-278
HLR MSC/VLR
MAP_OPEN_CNF
IV. Formula
None
10.25.16 Count of MAP_OPEN_CNF Session Rejections Due to Application

Context Not Supported
I. Entity Name
RODRACNS49
II. Description
MAP, with the cause of “application context not supported.
is aborted by the remote MAPPM, with the cause of “application context not supported”.
It then sends the primitive MAP_OPEN_CNF to the MAP to reject the session, with the
cause of “application context not supported”. This may be because the version of the
remote MAP is not high enough.
10-279
HLR MSC/VLR
MAP_OPEN_CNF
IV. Formula
None
10.25.17 Count of MAP_OPEN_CNF Session Rejections Due to Potential

Version Incompatibility
I. Entity Name
RODRPVI49
II. Description
MAP, with the cause of “potential version incompatibility".
is aborted by the remote MAPPM, with the cause of “potential version incompatibility”. It
cause of “potential version incompatibility”.
10-280
HLR MSC/VLR
MAP_OPEN_CNF
IV. Formula
None
10.25.18 Count of MAP_U_ABORT_REQ Messages Due to Application

Program Error
I. Entity Name
RUSPE49
II. Description
An error occurs to the application program of the local MAP.
It is measured when the local MAP detects an error due to which the session must be
aborted, and then sends the primitive MAP_OPEN_REQ to the MAPPM to abort the
session, with the cause of “application program error”.
10-281
HLR MSC/VLR
MAP_OPEN_REQ
IV. Formula
None
10.25.19 Count of MAP_U_ABORT_REQ Messages Due to Subscriber

Resource Limited
I. Entity Name
RUSRL49
II. Description
The session processing resources of the local MAP run out.
It is measured when the session resources of the MAP or the resources of the related
programs are used up, and the MAP sends the primitive MAP_OPEN_REQ to the
MAPPM to abort the session, with the cause of “subscriber resource limited”. Usually,
this case occurs under high traffic only.
10-282
HLR MSC/VLR
MAP_OPEN_REQ
IV. Formula
None
10.25.20 Count of MAP_U_ABORT_REQ Messages Due to Resource

Unavailable
I. Entity Name
RUSRU49
II. Description
All resources of the local MAP are temporarily unavailable.
It is measured when resources of the MAP are temporarily unavailable due to

maintenance or other reasons, and the MAP sends the primitive MAP_OPEN_REQ to
the MAPPM to abort the session, with the cause of “resource unavailable”.
10-283
HLR MSC/VLR
MAP_OPEN_REQ
IV. Formula
None
10.25.21 Count of MAP_U_ABORT_REQ Messages Due to Application

Program Cancelled
I. Entity Name
AUSAPC49
II. Description
The MAP has to cancel the session due to some cause.
It is measured when the MAP has to cancel the session due to some cause and sends
the primitive MAP_OPEN_REQ to the MAPPM to abort the session, with the cause of
“application program cancelled”.
10-284
HLR MSC/VLR
MAP_OPEN_REQ
IV. Formula
None
10.25.22 Count of MAP_U_ABORT_IND Messages Due to Application

Program Error
I. Entity Name
RURPE49
II. Description
The session is aborted by the remote MAP after being established, because an error
occurs to the application program of the remote MAP.
It is measured when the session is aborted due to remote MAP application error after
being established, and the MAPPM sends the message MAP_U_ABORT_IND to the
MAP, with the cause of “application program error”.
10-285
HLR MSC/VLR
MAP_U_ABORT_IND
IV. Formula
None
10.25.23 Count of MAP_U_ABORT_IND Messages Due to Subscriber

Resource Limited
I. Entity Name
RURRL49
II. Description
The session is aborted by the remote MAP after being established, because resources
of the remote MAP are not enough and the session cannot continue.
It is measured when the session is aborted due to remote MAP resources insufficient
after being established, and the MAPPM sends the message MAP_U_ABORT_IND to
the MAP, with the cause of “subscriber resource limited”.
10-286
HLR MSC/VLR
MAP_U_ABORT_IND
IV. Formula
None
10.25.24 Count of MAP_U_ABORT_IND Messages Due to Resource

Unavailable
I. Entity Name
RURRU49
II. Description
The session is aborted by the remote MAP after being established, because resources
of the remote MAP are unavailable.
It is measured when the session is aborted due to remote MAP resources unavailable
after being established, and the MAPPM sends the message MAP_U_ABORT_IND to
the MAP, with the cause of “resource unavailable”.
10-287
HLR MSC/VLR
MAP_U_ABORT_IND
IV. Formula
None
10.25.25 Count of MAP_U_ABORT_IND Messages Due to Application

Program Cancelled
I. Entity Name
RUAPC49
II. Description
Due to some reason, the session is aborted by the remote MAP after being established.
It is measured when the session is cancelled due to some reason after being
established, and the MAPPM sends the message MAP_U_ABORT_IND to the MAP,
with the cause of “application program cancelled”.
10-288
HLR MSC/VLR
MAP_U_ABORT_IND
IV. Formula
None
10.25.26 Count of MAP_P_ABORT_IND Messages Due to Provider Failure
I. Entity Name
RMRPM49
II. Description
The TCAP layer of the local or remote MAP fails and cannot provide services.
It is measured when the TCAP layer fails and cannot support session services.
10-289
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.27 Count of MAP_P_ABORT_IND Messages Due to Supported Call

Released
I. Entity Name
RMRSDXR49
II. Description
The support part on the TCAP bottom layer has been released while the MAP session
is going on.
It is measured when the TCAP releases its session resources while the session on the
service layer is going on, without notifying the MAP layer.
10-290
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.28 Count of MAP_P_ABORT_IND Messages Due to Provider Resource

Limited
I. Entity Name
RMRRL49
II. Description
TCAP resources of the local or remote MAP are limited.
It is measured when resources of the TCAP layer are limited.
10-291
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.29 Count of MAP_P_ABORT_IND Messages Due to Maintenance
I. Entity Name
RMRMA49
II. Description
The session is aborted due to maintenance of the TCAP.
It is measured when the session is aborted due to TCAP maintenance.
10-292
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.30 Count of MAP_P_ABORT_IND Messages Due to Potential Version

Incompatibility
I. Entity Name
RMRVI49
II. Description
The TCAP or MAPPM detects errors due to version incompatibility.
It is measured when the TCAP detects errors and the session must be aborted, with the
possible cause of “version incompatibility”.
10-293
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.31 Count of MAP_P_ABORT_IND Messages Due to Abnormal Call
I. Entity Name
RMRAMD49
II. Description
The TCAP or MAPPM detects an error indicating the session is abnormal.
It is measured when the TCAP or MAPPM detects an error indicating the session is
abnormal and then aborts the session.
10-294
HLR MSC/VLR
MAP_P_ABORT_IND
IV. Formula
None
10.25.32 Count of MAP_NOTICE_IND Messages Due to Abnormal Event

Detected by Remote MAP
I. Entity Name
RMRAEDP49
II. Description
The bottom layer of the remote MAP detects errors in the session and then informs the
local MAP of it.
It is measured when the bottom layer of the remote MAP detects errors in the session
and then informs the local MAP of it.
10-295
HLR MSC/VLR
MAP_NOTICE_IND
IV. Formula
None
10.25.33 Count of MAP_NOTICE_IND Messages Due to Response Rejected

by Remote MAP
I. Entity Name
RMRRRP49
II. Description
The remote MAP rejects the response possibly because the response contains errors.
It is measured when the remote MAP rejects the response with the possible cause of
errors in the response.
10-296
HLR MSC/VLR
MAP_NOTICE_IND
IV. Formula
None
10.25.34 Count of MAP_NOTICE_IND Messages Due to Abnormal Event

Received from Remote MAP
I. Entity Name
RMRAERP49
II. Description
The local MAP receives a message from the remote MAP and detects abnormality.
It is measured when the local MAP receives a message from the remote MAP and
detects abnormality.
10-297
HLR MSC/VLR
MAP_NOTICE_IND
IV. Formula
None
10.26 MAP Operation

10.26.1 Overview of MS_TYPE_MAP_OPERATION
Name Description
UNKSUB Count of messages indicating subscriber unknown
UNKBSS Count of messages indicating base station unknown
UNKMSC Count of messages indicating MSC unknown
UNIDSUB Count of messages indicating subscriber unidentified
ABSSUBSM Count of messages indicating SMS subscriber absent
UNKEQP Count of messages indicating equipment unknown
ROMNOALLOW Count of messages indicating roaming not allowed
ISUB Count of messages indicating subscriber illegal

BEARNOSUP Count of messages indicating bearer services not supported
TELSRNOSUP Count of messages indicating teleservices not supported
IEQUIP Count of messages indicating equipment illegal

CALLBARR Count of messages indicating call restricted
FORWVIOL Count of messages indicating forwarding violation
CUGREJ Count of messages indicating CUG rejection
10-298
Name Description
Count of messages indicating operation on supplementary
ERRSSOP
services illegal
Count of messages indicating status error of supplementary
SSERRSTUS
services
Count of messages indicating supplementary services
SSNOAVIL
unavailable
Count of messages indicating subscription violation of
SSSUBVIOL
supplementary services
Count of messages indicating supplementary services
SSINCOMP
incompatible
FUNNOSUP Count of messages indicating function not supported
INVALIDTAG Count of messages indicating target base station invalid
NORADIORES Count of messages indicating radio resource unavailable
NOHONUM Count of messages indicating handover number unavailable
SUBHOFAIL Count of messages indicating subsequent handover failure

ABSSUB Count of messages indicating subscriber absent
INCMPTERM Count of messages indicating terminal incompatible
SHORTDEN Count of messages indicating short term rejection

LONGDEN Count of messages indicating long term rejection
SUBBUSYSMS Count of messages indicating MT SMS subscriber busy
SMSNDFAIL Count of messages indicating short message delivery failure

MSGWTFULL Count of messages indicating message waiting queue full
SYSFAIL Count of messages indicating system error
DATAMIS Count of messages indicating data loss

UNEXPDATA Count of messages indicating data unexpected
PWREGFAIL Count of messages indicating password registration failure
PWCHKERR Count of messages indicating password check failure
NOROMNUM Count of messages indicating MSRN unavailable
TRBUFFULL Count of Messages indicating trace buffer full
Count of messages indicating target cell outside group call
CELLOUT
area
PWVOIL Count of messages indicating password attempt violation

NUMCHG Count of messages indicating number changed
BUSYSUB Count of messages indicating subscriber busy
10-299
Name Description
NOSUBREP Count of messages indicating no answer
FORWFAIL Count of messages indicating forwarding failure
ORFAIL Count of messages indicating optimized routing not allowed
NOGRPNUM Count of messages indicating group call number unavailable
RESLIM Count of messages indicating resource limitation
Count of messages indicating requested network
UNAUTHNET
unauthorized
UNAUTHLCS Count of messages indicating LCS client unauthorized

POSFAIL Count of messages indicating location method failure
Count of messages indicating LCS client unknown or

UNKCLS
unreachable
Count of messages indicating mobility management event not

MMNOSUP
supported
UNKALP Count of messages indicating character set unknown
USSDBUSY Count of messages indicating USSD subscriber busy
OPREQ Count of messages indicating operation request
OPRSP Count of messages indicating normal response to operation

Count of messages indicating operation termination not due
OPABORT
to timeout
OPTIMEOUT Count of messages indicating operation timeout
OPTIME1 Duration of operation
10.26.2 Count of Messages Indicating Subscriber Unknown
I. Entity Name
UNKSUB
II. Description
The HLR returns the message when the subscriber ID does not exist in the HLR
database.
It is measured when an error is contained in the MAP operation response received or

sent.
10-300
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.3 Count of Messages Indicating Base Station Unknown
I. Entity Name
UNKBSS
II. Description
The destination base station is unknown during handover.

sent.
10-301
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.4 Count of Messages Indicating MSC Unknown
I. Entity Name
UNKMSC
II. Description
The destination MSC of the subsequent handover is unknown.

sent.
10-302
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.5 Count of Messages Indicating Subscriber Unidentified
I. Entity Name
UNIDSUB
II. Description
The subscriber ID does not exist in the VLR database.

sent.
10-303
HLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.6 Count of Messages Indicating SMS Subscriber Absent
I. Entity Name
ABSSUBSM
II. Description
The VLR returns the message when the short message center (SMC) delivers short
messages to a subscriber, but the MS is powered off.

sent.
10-304
HLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.7 Count of Messages Indicating Equipment Unknown
I. Entity Name
UNKEQP
II. Description
The EIR returns the message when the IMEI check equipment cannot be identified.

sent.
10-305
EIR MSC/VLR
MAP_SERVICE_IND
IV. Formula
None
10.26.8 Count of Messages Indicating Roaming Not Allowed
I. Entity Name
ROMNOALLOW
II. Description
The HLR or VLR prevents subscribers from roaming during location update.

sent.
10-306
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.9 Count of Messages Indicating Subscriber Illegal
I. Entity Name
ISUB
II. Description
Authentication fails during service request or location update.

sent.
10-307
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.10 Count of Messages Indicating Bearer Services Not Supported
I. Entity Name
BEARNOSUP
II. Description
The HLR returns the message when the requested bearer services are not subscribed
to.

sent.
10-308
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.11 Count of Messages Indicating Teleservices Not Supported
I. Entity Name
TELSRNOSUP
II. Description
The HLR returns the message when the requested teleservices are not subscribed to.

sent.
10-309
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.12 Count of Messages Indicating Equipment Illegal
I. Entity Name
IEQUIP
II. Description
The VLR returns the message when the terminal equipment is checked to be illegal in
the MT service.

sent.
10-310
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.13 Count of Messages Indicating Call Restricted
I. Entity Name
CALLBARR
II. Description
The HLR returns the message when the subscriber who registers the incoming call
barring service acts as the callee.

sent.
10-311
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.14 Count of Messages Indicating Forwarding Violation
I. Entity Name
FORWVIOL
II. Description
The HLR returns the message when the times that a call is forwarded exceeds the
maximum number allowed while route information is fetched.

sent.
10-312
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.15 Count of Messages Indicating CUG Rejection
I. Entity Name
CUGREJ
II. Description
The CUG check fails or the VLR fails to check the CUG authority of the subscriber,
when route information is fetched.

sent.
10-313
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.16 Count of Messages Indicating Operation on Supplementary

Services Illegal
I. Entity Name
ERRSSOP
II. Description
The HLR returns the message when requested supplementary services do not match
basic services.

sent.
10-314
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.17 Count of Messages Indicating Status Error of Supplementary

Services
I. Entity Name
SSERRSTUS
II. Description
The HLR returns the message when the current status of supplementary services fails
to meet that required for the operation on supplementary services.

sent.
10-315
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.18 Count of Messages Indicating Supplementary Services Unavailable
I. Entity Name
SSNOAVIL
II. Description
The HLR returns the message when supplementary services required for the
supplementary service operation is not subscribed to.

sent.
10-316
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.19 Count of Messages Indicating Subscription Violation of

Supplementary Services
I. Entity Name
SSSUBVIOL
II. Description
The HLR returns the message when the subscriber is not authorized for operations on
requested supplementary services.

sent.
10-317
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None

Incompatible
I. Entity Name
SSINCOMP
II. Description
The HLR returns the message when a supplementary service operation conflicts with
other supplementary service status.

sent.
10-318
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.21 Count of Messages Indicating Function Not Supported
I. Entity Name
FUNNOSUP
II. Description
The message is returned when the requested function is not supported.

sent.
10-319
MS MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.22 Count of Messages Indicating Target Base Station Invalid
I. Entity Name
INVALIDTAG
II. Description
The destination base station of the handover is unavailable.

sent.
10-320
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.23 Count of Messages Indicating Radio Resource Unavailable
I. Entity Name
NORADIORES
II. Description
The message is returned when the radio resources are congested.

sent.
10-321
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.24 Count of Messages Indicating Handover Number Unavailable
I. Entity Name
NOHONUM
II. Description
The message is returned when the VLR has no available handover number for a
handover request.

sent.
10-322
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.25 Count of Messages Indicating Subsequent Handover Failure
I. Entity Name
SUBHOFAIL
II. Description
The subsequent handover fails due to abnormal causes.

sent.
10-323
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.26 Count of Messages Indicating Subscriber Absent
I. Entity Name
ABSSUB
II. Description
The VLR returns the message when the subscriber powers off the MS; the HLR returns
the message when the VLR clears relative subscriber data.

sent.
10-324
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.27 Count of Messages Indicating Terminal Incompatible
I. Entity Name
INCMPTERM
II. Description
The terminal does not support the requested function.

sent in the MAP_REMOTE_USER_FREE session.
10-325
MS MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.28 Count of Messages Indicating Short Term Rejection
I. Entity Name
SHORTDEN
II. Description
The registration of supplementary services is rejected for a short term.

sent.
10-326
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.29 Count of Messages Indicating Long Term Rejection
I. Entity Name
LONGDEN
II. Description
The registration of supplementary services is rejected for a long term.

sent.
10-327
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.30 Count of Messages Indicating MT SMS Subscriber Busy
I. Entity Name
SUBBUSYSMS
II. Description
The VLR returns the message when the SMC delivers short messages to a subscriber,
but the MS is busy.

sent.
10-328
GMSC MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.31 Count of Messages Indicating Short Message Delivery Failure
I. Entity Name
SMSNDFAIL
II. Description
The corresponding entity returns the message when a short message fails to be sent or
received, always with the specific cause.

sent.
10-329
SMS Interworking MSC MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.32 Count of Messages Indicating Message Waiting Queue Full
I. Entity Name
MSGWTFULL
II. Description
The HLR returns the message when the short message waiting queue in the HLR
database is too full to store new SMC addresses.

sent.
10-330
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.33 Count of Messages Indicating System Error
I. Entity Name
SYSFAIL
II. Description
The HLR or VLR returns the message when the system fails.

sent.
10-331
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.34 Count of Messages Indicating Data Loss
I. Entity Name
DATAMIS
II. Description
The protocol checks that mandatory parameters are missing in received signaling.

sent.
10-332
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.35 Count of Messages Indicating Data Unexpected
I. Entity Name
UNEXPDATA
II. Description
The protocol checks that data of the received signaling is beyond the specified.

sent.
10-333
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.36 Count of Messages Indicating Registration Failure Due to Password

Invalid
I. Entity Name
PWREGFAIL
II. Description
The HLR returns the message when registration of restricted supplementary services
fails because the password is wrong.

sent.
10-334
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.37 Count of Messages Indicating Password Check Failure
I. Entity Name
PWCHKERR
II. Description
The HLR returns the message when the password for registering call baring services or
activating/deactivating restricted supplementary services is wrong.

sent.
10-335
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.38 Count of Messages Indicating MSRN Unavailable
I. Entity Name
NOROMNUM
II. Description
The message is returned when the HLR fetches MSRNs from the VLR but the VLR has
no MSRNs to allocate.

sent.
10-336
HLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.39 Count of Messages Indicating Trace Buffer Full
I. Entity Name
TRBUFFULL
II. Description
The trace buffer of the VLR is full.

sent.
10-337
HLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.40 Count of Messages Indicating Target Cell Outside Group Call Area
I. Entity Name
CELLOUT
II. Description
The target cell in the prepare handover is outside the group call area.

sent.
10-338
MSC/VLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.41 Count of Messages Indicating Password Attempt Violation
I. Entity Name
PWVOIL
II. Description
The HLR returns the message if the number of password attempts exceeds the limit
when the subscriber uses supplementary services or registers a new password for
supplementary services.

sent.
10-339
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.42 Count of Messages Indicating Number Changed
I. Entity Name
NUMCHG
II. Description
The HLR returns the message if the MSISDN of the subscriber is changed when route
information is fetched.

sent.
10-340
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.43 Count of Messages Indicating Subscriber Busy
I. Entity Name
BUSYSUB
II. Description
The message is returned when the IN service subscriber is considered busy.

sent.
10-341
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.44 Count of Messages Indicating No Answer
I. Entity Name
NOSUBREP
II. Description
The message is returned when no response is given to the paging of the IN service
subscriber.

sent.
10-342
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.45 Count of Messages Indicating Forwarding Failure
I. Entity Name
FORWFAIL
II. Description
The HLR returns the failure message when the GMSC needs forwarding information.

sent.
10-343
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.46 Count of Messages Indicating Optimized Routing Not Allowed
I. Entity Name
ORFAIL
II. Description
The HLR does not accept optimized routing query from the GMSC, or not allow calls to
the specified subscriber to be optimally routed.

sent.
10-344
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.47 Count of Messages Indicating Group Call Number Unavailable
I. Entity Name
NOGRPNUM
II. Description
No group call number is available when a group call is to be made.

sent.
10-345
Anchor_MSC/VLR Relay_MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.48 Count of Messages Indicating Resource Limitation
I. Entity Name
RESLIM
II. Description
The service provider (HLR) returns an error message because of resources limitation.

sent.
10-346
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.49 Count of Messages Indicating Requested Network Unauthorized
I. Entity Name
UNAUTHNET
II. Description
The requested network is not authorized.

sent.
10-347
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.50 Count of Messages Indicating LCS Client Unauthorized
I. Entity Name
UNAUTHLCS
II. Description
The requested LCS client is not authorized.
It is measured when the MSC receives the response containing the unauthorized LCS
client cell from the VLR or the subscriber.
10-348
GMLC MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.51 Count of Messages Indicating Location Method Failure
I. Entity Name
POSFAIL
II. Description
The location method is not supported.
It is measured when the MSC receives the message containing unsupported location
method from other NEs in MTLR or MOLR.
10-349
GMLC MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.52 Count of Messages Indicating LCS Client Unknown or Unreachable
I. Entity Name
UNKCLS
II. Description
The LCS client is unreachable or unknown.
It is measured when the MSC receives the location response containing the information
that the LCS subscriber is unreachable or unknown from the GMLC.
10-350
GMLC MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.53 Count of Messages Indicating Mobility Management Event Not

Supported
I. Entity Name
MMNOSUP
II. Description
The mobility management event is not supported.
It is measured when the MSC receives message indicating mobility management is not
supported from other NEs.
10-351
gsmSCF MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.54 Count of Messages Indicating Character Set Unknown
I. Entity Name
UNKALP
II. Description
The VLR or HLR returns the message when the coding scheme of the USSD string is
unknown.

sent.
10-352
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.55 Count of Messages Indicating USSD Subscriber Busy
I. Entity Name
USSDBUSY
II. Description
The message is returned when the network originates a USSD request but the callee is
busy.

sent.
10-353
HLR MSC/VLR
MAP_SERVICE_RSP
IV. Formula
None
10.26.56 Count of Messages Indicating Operation Request
I. Entity Name
OPREQ
II. Description
It is the count of messages indicating operation requests.
It is measured when the MAP operation request is received or sent.
10-354
HLR MSC/VLR
MAP_SERVICE_REQ
IV. Formula
None
10.26.57 Count of Messages Indicating Normal Response to Operation
I. Entity Name
OPRSP
II. Description
The response is returned normally to the operation.
It is measured when no error is contained in the MAP operation response received or

sent.
10-355
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.58 Count of Messages Indicating Operation Termination Not Due to

Timeout
I. Entity Name
OPABORT
II. Description
The operation is terminated not due to timeout.
It is measured when the Abort, Close or Notice message not caused by timeout is
received or sent.
10-356
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.59 Count of Messages Indicating Operation Timeout
I. Entity Name
OPTIMEOUT
II. Description
The operation times out.
It is measured when the local operation times out.
10-357
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.26.60 Duration of Operation
I. Entity Name
OPTIME1
II. Description
It is the duration of the operation.
It is measured from the time that the operation request is sent or received to the time
that the operation is normally or abnormally terminated.
10-358
HLR MSC/VLR
MAP_SERVICE_CNF
IV. Formula
None
10.27 MTP3B Signaling Link

10.27.1 Overview of MS_MTP3B_LINK_TRAF
Name Description
SLWRKD Duration of signaling link in in-service state
SLFLDT Count of signaling link failures (all causes)
SLFLDD Duration of signaling link failure
SLLIhbT Count of local management inhibition operations
SLLIhbD Duration of local management inhibition operation
SLRIhbT Count of remote management inhibition operations
SLRIhbD Duration of remote management inhibition operation
SLChOT Count of local automatic switchovers

SLSndMSUs Count of messages sent
SLSndMSUs Count of messages received
SLRcvMSUs Count of octets of SIF and SIO sent

SLSndOcts Count of octets of SIF and SIO received
SLRcvOcts Count of signaling link congestion
SLCgstT Duration of signaling link congestion
10-359
Name Description
Percentage of signaling link bandwidth used for sending
SLSndRate
signaling information
Percentage of signaling link bandwidth used for receiving
SLRcvRate
10.27.2 Duration of Signaling Link in In-Service State
I. Entity Name
SLWRKD
II. Description
It is the duration when the measurement link is in service.
It is measured from the link recovery to failure.
IV. Formula
None
10.27.3 Count of Signaling Link Failures (All Causes)
I. Entity Name
SLFLDT
II. Description
It is the count of signaling link failures, that is, the link is out of service.
It is measured when the link fails, for example, the SLT fails, or the link is out of service
or switched over.
IV. Formula
None
10.27.4 Duration of Signaling Link Failure
I. Entity Name
SLFLDD
10-360
II. Description
It is the duration when the signaling link is faulty.
IV. Formula
None
10.27.5 Count of Local Management Inhibition Operations
I. Entity Name
SLLIhbT
II. Description
It is the count of successes of local management inhibition on the signaling link.
It is measured when the OM originates the LIN message and then receives the LIA
message from the peer end.
UMG\SG\MSC MSC Server
LIN
LIA
MTP3B Link A
IV. Formula
None
10.27.6 Duration of Local Management Inhibition Operation
I. Entity Name
SLLIhbD
II. Description
It is the duration of successful local management inhibition on the signaling link.
10-361
It is measured since the OM originates the LIN message and receives the LIA from the
peer end, and until it removes the uninhibition (normally or forcedly) and receives the
LUA message.
IV. Formula
None
10.27.7 Count of Remote Management Inhibition Operations
I. Entity Name
SLRIhbT
II. Description
It is the count of successes of remote management inhibition on the signaling link.
It is measured when the OM receives the LIN message from peer end and returns the
LIA message.
LIN
LIA
MTP3B Link
A
IV. Formula
None
10.27.8 Duration of Remote Management Inhibition Operation
I. Entity Name
SLRIhbD
II. Description
It is the duration of successful remote management inhibition on the signaling link.
10-362
It is measured since the OM receives the LIN message from the peer end and returns
the LIA message, and until it receives the LUN or LFU message.
IV. Formula
None
10.27.9 Count of Local Automatic Switchovers
I. Entity Name
SLChOT
II. Description
It is the count of signaling link switchovers as the link fails to transmit services.
It is measured when the signaling link sends the XCO message and then receives the
COA or XCA message from the peer end, or the time controlled switchover completes.
XCO
COA\XCA
MTP3B Link
A
IV. Formula
None
I. Entity Name
SLSndMSUs
II. Description
It is the count of messages sent through the signaling link.
It is measured when a message is sent through the signaling link.
10-363
MSU
MTP3B Link
A
IV. Formula
None
I. Entity Name
SLRcvMSUs
II. Description
It is the count of messages that MTP3B receives through the signaling link.
It is measured when a message is received through the link.
MSU
MTP3B Link
A
IV. Formula
None
10.27.12 Count of Octets of SIF and SIO Sent
I. Entity Name
SLSndOcts
10-364
II. Description
It is the count of octets of signaling information field (SIF) and service information octets
(SIO) sent through the signaling link.
It is measured when a message is sent through the link.
MSU
MTP3B Link
A
IV. Formula
None
10.27.13 Count of Octets of SIF and SIO Received
I. Entity Name
SLRcvOcts
II. Description
It is the count of octets of SIF and SIO received through the signaling link.
It is measured when a message is received through the link.
MSU
MTP3B Link
A
IV. Formula
None
10-365
10.27.14 Count of Signaling Link Congestion
I. Entity Name
SLCgstT
II. Description
It is the count of congestion on the signaling link.
It is measured when the link receives the message LINK CONGESTED from the SAAL.
IV. Formula
None
10.27.15 Duration of Signaling Link Congestion
I. Entity Name
SLCgstD
II. Description
It is the duration of congestion of the signaling link.
It is measured when the link receives the message LINK CONGESTED from the SAAL.
IV. Formula
None

Signaling Information
I. Entity Name
SLSndRate
II. Description
It is the percentage of signaling link bandwidth used for sending signaling information.
IV. Formula
None
10-366
10.27.17 Percentage of Signaling Link Bandwidth Used for Receiving

I. Entity Name
SLRcvRate
II. Description
It is the percentage of signaling link bandwidth used for receiving signaling information.
IV. Formula
None
10.28 MTP3B Signaling Link Set

10.28.1 Overview of MS_MTP3B_LINKSET_TRAF
Name Description
SLSUabT Count of unavailable states
SLSUabD Duration of unavailable state
I. Entity Name
SLSUabT
II. Description
It is the count of states that the signaling link set is unavailable, that is, all links in the
signaling link set are unavailable.
It is measured when all links in the signaling link set are faulty. The failure may be SLT
failure, out of service, or switchover.
IV. Formula
None
10-367
I. Entity Name
SLSUabD
II. Description
It is the duration when the signaling link set is unavailable.
It is measured since all links in the signaling link set are faulty and until one link is
available.
IV. Formula
None
10.29 MTP3B Destination Signaling Point

10.29.1 Overview of MS_MTP3B_DSP_TRAF
Name Description
DSPIabT Count of failed accesses
DSPIabD Duration of failed access
DSPRcvTFPT Count of transfer prohibited signals received
I. Entity Name
DSPIabT
II. Description
It is the count of failures to access the DSP.
It is measured when the DSP turns inaccessible.
IV. Formula
None
10-368
I. Entity Name
DSPIabD
II. Description
It is the duration when the DSP is inaccessible.
It is measured since the DSP is inaccessible and until it is accessible again.
IV. Formula
None
10.29.4 Count of Transfer Prohibited Messages Received
I. Entity Name
DSPRcvTFPT
II. Description
It is the count of route transfer prohibited (TFP) messages received.
It is measured when the TFP message is received through the link.
TFP
MTP3B DSP
A
IV. Formula
None
10-369
10.30 MTP Destination Signaling Point

10.30.1 Overview of MS_MTP_DSP_TRAF
Name Description
INA Count of failed accesses
INAT Duration of failed access
I. Entity Name
INA
II. Description
It is the count of failures to access the DSP.
It is measured when the DSP is inaccessible.
IV. Formula
None
I. Entity Name
INAT
II. Description
It is the duration when the DSP is inaccessible.
It is measured since the DSP is inaccessible and until it is accessible again.
IV. Formula
None
10-370
10.31 MTP Signaling Link

10.31.1 Overview of MS_MTP_LINK_TRAF
Name Description
UAVT Duration of unavailable state
FL Count of failures
FLT Duration of failure
CGT Duration of congestion
CGMSUDIS Count of messages discarded due to congestion
RTFP Count of transfer prohibited signals received

LCO Count of local automatic switchovers
LLIN Count of local management inhibition operations
LLINT Duration of local management inhibition operations
RLIN Count of remote management inhibition operations
RLINT Duration of remote management inhibition operations
RPER Count of remote processor failures
RPERT Duration of remote processor failure



10-371
Name Description
SOCT Count of bytes in messages sent
ROCT Count of bytes in messages received
Percentage of signaling link bandwidth used for sending
SSEIZR
Percentage of signaling link bandwidth used for receiving

RSEIZR
I. Entity Name
UAVT
II. Description
It is the duration when the signaling link is unavailable due to any cause.
IV. Formula
None
10.31.3 Count of Failures
I. Entity Name
FL
II. Description
It is the count of faults of the signaling link.
It is measured when the link fails.
IV. Formula
None
10.31.4 Duration of Failure
I. Entity Name
FLT
10-372
II. Description
It is the duration when the signaling link is faulty.
IV. Formula
None
I. Entity Name
CG
II. Description
It is the count of congestion on the signaling link.
It is measured when the signaling link is congested.
IV. Formula
None
I. Entity Name
CGT
II. Description
It is the duration when the signaling link is congested.
IV. Formula
None
10.31.7 Count of Messages Discarded Due to Congestion
I. Entity Name
CGMSUDIS
10-373
II. Description
It is the count of messages discarded due to signaling link congestion.
It is measured when a message is discarded due to signaling link congestion.
IV. Formula
None
10.31.8 Count of Transfer Prohibited Signals Received
I. Entity Name
RTFP
II. Description
It is the count of TFP signals received.
It is measured when a TFP signal is received.
UMG\SG MSC Server
TFP
MTP3 Link A
IV. Formula
None
10.31.9 Count of Local Automatic Switchovers
I. Entity Name
LCO
II. Description
It is the count of signaling link switchovers as the link fails to transmit services.
10-374
It is measured when the local automatic switchover occurs.
IV. Formula
None
10.31.10 Count of Local Management Inhibition Operations
I. Entity Name
LLIN
II. Description
It is the count of successes of local management inhibition on the signaling link.
It is measured when the local end sends the LIN message and then receives the LIA
message from the peer end.
UMG\SG MSC Server
LIN
LIA
MTP3 Link A
IV. Formula
None
10.31.11 Duration of Local Management Inhibition Operations
I. Entity Name
LLINT
II. Description
It is the duration of successful local management inhibition on the signaling link.
10-375
It is measured when the local end receives the LIN message and then sends the LIA
message.
UMG\SG MSC Server
LIN
LIA
MTP3 Link A
IV. Formula
None
10.31.12 Count of Remote Management Inhibition Operations
I. Entity Name
RLIN
II. Description
It is the count of successes of remote management inhibition on the signaling link.
It is measured when the remote management inhibition is operated on the link.
IV. Formula
None
10.31.13 Duration of Remote Management Inhibition Operations
I. Entity Name
RLINT
II. Description
It is the duration of successful remote management inhibition on the signaling link.
10-376
It is measured since the remote management inhibition begins and until the inhibition is
removed.
IV. Formula
None
10.31.14 Count of Remote Processor Failures
I. Entity Name
RPER
II. Description
It is the count of failures of the remote processor.
It is measured when the remote processor fails.
IV. Formula
None
10.31.15 Duration of Remote Processor Failure
I. Entity Name
RPERT
II. Description
It is the duration when the signaling link is unavailable because the link receives the
indication for remote processor failure.
It is measured from the remote processor failure to recovery.
IV. Formula
None
I. Entity Name
SSCCPMSU
10-377
II. Description
It is the count of SCCP messages sent through the signaling link.
It is measured when the SCCP message is sent through the MTP3 signaling link.
UMG\SG MSC Server
MSU(SCCP)
MTP3 Link A
IV. Formula
None
I. Entity Name
RSCCPMSU
II. Description
It is the count of SCCP messages received through the signaling link.
It is measured when the SCCP message is received through the signaling link.
UMG\SG MSC Server
MSU(SCCP)
MTP3 Link A
IV. Formula
None
10-378
I. Entity Name
SSCCPOCT
II. Description
It is the count of bytes in SCCP messages sent through the signaling link.
It is measured when the SCCP message is sent through the signaling link.
UMG\SG MSC Server
MSU(SCCP)
MTP3 Link A
IV. Formula
None
I. Entity Name
RSCCPOCT
II. Description
It is the count of bytes in SCCP messages received through the signaling link.
It is measured when the SCCP message is received through the signaling link.
10-379
UMG\SG MSC Server
MSU(SCCP)
MTP3 Link A
IV. Formula
None
I. Entity Name
STUPMSU
II. Description
It is the count of TUP messages sent through the signaling link.
It is measured when the TUP message is sent through the signaling link.
UMG\SG MSC Server
MSU(TUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
RTUPMSU
10-380
II. Description
It is the count of TUP messages received through the signaling link.
It is measured when the TUP message is received through the signaling link.
UMG\SG MSC Server
MSU(TUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
STUPOCT
II. Description
It is the count of bytes in TUP messages sent through the signaling link.
It is measured when the TUP message is sent through the signaling link.
UMG\SG MSC Server
MSU(TUP)
MTP3 Link A
IV. Formula
None
10-381
I. Entity Name
RTUPOCT
II. Description
It is the count of bytes in TUP messages received through the signaling link.
It is measured when the TUP message is received through the signaling link.
UMG\SG MSC Server
MSU(TUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
SISUPMSU
II. Description
It is the count of ISUP messages sent through the signaling link.
It is measured when the ISUP message is sent through the signaling link.
10-382
UMG\SG MSC Server
MSU(TUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
RISUPMSU
II. Description
It is the count of ISUP messages received through the signaling link.
It is measured when the ISUP message is received through the signaling link.
UMG\SG MSC Server
MSU(TUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
SISUPOCT
10-383
II. Description
It is the count of bytes in ISUP messages sent through the signaling link.
It is measured when the ISUP message is sent through the signaling link.
UMG\SG MSC Server
MSU(ISUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
RISUPOCT
II. Description
It is the count of bytes in ISUP messages received through the signaling link.
It is measured when the ISUP message is received through the signaling link.
UMG\SG MSC Server
MSU(ISUP)
MTP3 Link A
IV. Formula
None
10-384
I. Entity Name
SMSU
II. Description
It is the count of messages sent through the signaling link.
UMG\SG MSC Server
MSU(ISUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
RMSU
II. Description
It is the count of messages received through the signaling link.
It is measured when a message is received through the signaling link.
10-385
UMG\SG MSC Server
MSU(ISUP)
MTP3 Link A
IV. Formula
None
I. Entity Name
SOCT
II. Description
It is the count of bytes in messages sent through the signaling link.
UMG\SG MSC Server
MSU(ISUP,SCCP,BICC...)
MTP3 Link A
IV. Formula
None
I. Entity Name
ROCT
10-386
II. Description
It is the count of bytes in messages received through the signaling link.
It is measured when a message is received through the signaling link.
UMG\SG MSC Server
MTP3 Link A
IV. Formula
None

I. Entity Name
SSEIZR
II. Description
It is the percentage of signaling link bandwidth used for sending signaling information.
IV. Formula
None
10.31.33 Percentage of Signaling Link Bandwidth Used for Receiving

I. Entity Name
RSEIZR
II. Description
It is the percentage of signaling link bandwidth used for receiving signaling information.
10-387
IV. Formula
None
10.32 MTP Signaling Link Set
10.32.1 Overview of MS_MTP_LINKSET_TRAF
Name Description
UAV Count of unavailability
UAVT Duration of unavailability




TMSU Count of messages received
SOCT Count of bytes in messages sent
ROCT Count of bytes in messages received
10.32.2 Count of Unavailability
I. Entity Name
UAV
10-388
II. Description
It is the count of states that all links in the signaling link set are unavailable.
It is measured when the signaling link set is unavailable.
IV. Formula
None
10.32.3 Duration of Unavailability
I. Entity Name
UAVT
II. Description
It is the duration when all links in the signaling link set are unavailable.
IV. Formula
None
I. Entity Name
SSCCPMSU
II. Description
It is the count of SCCP messages sent through the link set.
It is measured when the MTP sends the SCCP message.
10-389
UMG\SG MSC Server
MSU(SCCP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
RSCCPMSU
II. Description
It is the count of SCCP messages received through the link set.
It is measured when the MTP receives the SCCP message.
UMG\SG MSC Server
MSU(SCCP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
SSCCPOCT
10-390
II. Description
It is the count of bytes in SCCP messages sent through the link set.
It is measured when the MTP sends the SCCP message.
UMG\SG MSC Server
MSU(SCCP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
RSCCPOCT
II. Description
It is the count of bytes in SCCP messages received through the link set.
It is measured when the MTP receives the SCCP message.
UMG\SG MSC Server
MSU(SCCP)
MTP3 Linkset A
IV. Formula
None
10-391
I. Entity Name
STUPMSU
II. Description
It is the count of TUP messages sent through the link set.
It is measured when the MTP sends the TUP message.
UMG\SG MSC Server
MSU(TUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
RTUPMSU
II. Description
It is the count of TUP messages received through the link set.
It is measured when the MTP receives the TUP message.
10-392
UMG\SG MSC Server
MSU(TUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
STUPOCT
II. Description
It is the count of bytes in TUP messages sent through the link set.
It is measured when the MTP sends the TUP message.
UMG\SG MSC Server
MSU(TUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
RTUPOCT
10-393
II. Description
It is the count of bytes in TUP messages received through the link set.
It is measured when the MTP receives the TUP message.
UMG\SG MSC Server
MSU(TUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
SISUPMSU
II. Description
It is the count of ISUP messages sent through the link set.
It is measured when the MTP sends the ISUP message.
UMG\SG MSC Server
MSU(ISUP)
MTP3 Linkset A
IV. Formula
None
10-394
I. Entity Name
RISUPMSU
II. Description
It is the count of ISUP messages received through the link set.
It is measured when the MTP receives the ISUP message.
UMG\SG MSC Server
MSU(ISUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
SISUPOCT
II. Description
It is the count of bytes in ISUP messages sent through the link set.
It is measured when the MTP sends the ISUP message.
10-395
UMG\SG MSC Server
MSU(ISUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
RISUPOCT
II. Description
It is the count of bytes in ISUP messages received through the link set.
It is measured when the MTP receives the ISUP message.
UMG\SG MSC Server
MSU(ISUP)
MTP3 Linkset A
IV. Formula
None
I. Entity Name
SMSU
10-396
II. Description
It is the count of messages sent through the link set.
It is measured when a message is sent through the MTP link.
UMG\SG MSC Server
MTP3 Linkset A
IV. Formula
None
I. Entity Name
TMSU
II. Description
It is the count of messages received through the link set.
It is measured when a message is received through the MTP link.
UMG\SG MSC Server
MTP3 Linkset A
IV. Formula
None
10-397
I. Entity Name
SOCT
II. Description
It is the count of bytes in messages sent through the link set.
It is measured when a message is sent through the MTP link.
UMG\SG MSC Server
MTP3 Linkset A
IV. Formula
None
I. Entity Name
ROCT
II. Description
It is the count of bytes in messages received through the link set.
It is measured when a message is received through the MTP link.
10-398
UMG\SG MSC Server
MTP3 Linkset A
IV. Formula
None
10.33 SAAL Signaling Link
10.33.1 Overview of MS_SAAL_LINK_TRAF
Name Description
ISTIME Duration of SAAL signaling link in service
FAR Count of SAAL signaling link failures due to other causes
Count of SAAL signaling link failures due to no response timer
FNRE
timeout
FEER Count of SAAL signaling link failures due to too high bit error rate
FEDC Count of SAAL signaling link failures due to congestion timeout
FALN Count of location failures of SAAL signaling link
SDLOSS Count of MAA-ERROR indications due to lost SD
MAAUP Count of unexpected packet received
MAAOR Count of SSCOP sending error report to LM due to other causes
URET Count of failed retransmission
10.33.2 Duration of SAAL Signaling Link in Service
I. Entity Name
ISTIME
II. Description
It is the duration when the SSAL link is in service.
10-399
It is measured from the time when the SAAL link recovers from fault to the time when it
fails again.
IV. Formula
None
10.33.3 Count of SAAL Signaling Link Failures Due to Other Causes
I. Entity Name
FAR
II. Description
It is the count of SAAL link failures due to other causes.
It is measured when the SAAL link fails due to other causes.
IV. Formula
None
10.33.4 Count of SAAL Signaling Link Failures Due to Timeout of No

Response Timer
I. Entity Name
FNRE
II. Description
It is the count of SAAL link failures due to timeout of “No Response Timer”.
It is measured when the SAAL link fails due to timeout of “No Response Timer”.
IV. Formula
None
10.33.5 Count of SAAL Signaling Link Failures Due to Too High Bit Error
Rate
I. Entity Name
FEER
10-400
II. Description
It is the count of SAAL link failures due to too high bit error rate.
It is measured when the SAAL link fails due to too high bit error rate.
IV. Formula
None
10.33.6 Count of SAAL Signaling Link Failures Due to Congestion Timeout
I. Entity Name
FEDC
II. Description
It is the count of SAAL link failures due to long time congestion.
It is measured when the SAAL link fails due to long time congestion.
IV. Formula
None
10.33.7 Count of Location Failures of SAAL Signaling Link
I. Entity Name
FALN
II. Description
It is the count of location failures of the SAAL link within the time specified by protocols.
It is measured when the location of the SAAL link fails within the time specified by
protocols.
IV. Formula
None
10.33.8 Count of MAA-ERROR Indications Due to SD Loss
I. Entity Name
SDLOSS
10-401
II. Description
It is the count of MAA-ERROR indications due to SD loss.
It is measured when the indication MAA-ERROR is received due to SD loss.
IV. Formula
None
10.33.9 Count of Unexpected Packets Received
I. Entity Name
MAAUP
II. Description
It is the count of unexpected packets (including control packets and data packets)
received by SSCOP.
It is measured when SSCOP receives the unexpected packet.
IV. Formula
None
10.33.10 Count of SSCOP Sending Error Report to LM Due to Other Causes
I. Entity Name
MAAOR
II. Description
It is the count of successes that SSCOP sends the error report to the LM due to other
causes.
It is measured when SSCOP sends the error report to the LM due to other causes.
IV. Formula
None
10-402
10.33.11 Count of Failed Retransmission
I. Entity Name
URET
II. Description
It is the count of retransmission failures.
It is measured when retransmission fails.
IV. Formula
None
10.34 SCCP Availability
10.34.1 Overview of MS_SCCP_AVAILABILITY
Name Description
UAFL Count of local SCCP failures due to fault
UAMT Count of local SCCP failures due to maintenance

UACG Count of local SCCP failures due to congestion
UADUR Duration of unavailability of local SCCP due to all causes
UASTP Count of local SCCP back to available due to all causes
10.34.2 Count of Local SCCP Failures Due to Fault
I. Entity Name
UAFL
II. Description
It is the count of local SCCP failures due to fault.
It is measured when the local SCCP is unavailable due to node fault.
IV. Formula
None
10-403
10.34.3 Count of Local SCCP Failures Due to Maintenance
I. Entity Name
UAMT
II. Description
It is the count of local SCCP failures due to maintenance.
It is measured when the local SCCP is unavailable due to maintenance.
IV. Formula
None
10.34.4 Count of Local SCCP Failures Due to Congestion
I. Entity Name
UACG
II. Description
It is the count of local SCCP failures due to congestion.
It is measured when the local SCCP is unavailable due to congestion.
IV. Formula
None
10.34.5 Duration of Unavailability of Local SCCP Due to All Causes
I. Entity Name
UADUR
II. Description
It is the duration when the local SCCP is unavailable.
It is measured since the local SCCP is unavailable due to fault, congestion or

maintenance, and until it is available again.
IV. Formula
None
10-404
10.34.6 Count of Local SCCP Recovery Due to All Causes
I. Entity Name
UASTP
II. Description
It is the count that the local SCCP is available again.
It is measured when the local SCCP is available due to fault recovery, congestion
removal, or maintenance completion.
IV. Formula
None
10.35 SCCP Usage
10.35.1 Overview of MS_SCCP_UTILIZATION
Name Description
SNTUDTS Count of UDTS messages sent
RCVUDTS Count of UDTS messages received

Count of processed messages (from local or remote
ALLMSG
subsystem)
SSNMSG Count of messages used by local subsystem
GTMSG Count of messages needing GT translation
SNTCLM Count of connectionless messages sent

RCVCLM Count of connectionless messages received
RSSMSG Count of messages sent to a standby subsystem
10.35.2 Count of UDTS Messages Sent
I. Entity Name
SNTUDTS
10-405
II. Description
It is the count of sent messages returned because the SCCP routing function cannot
support transferring UDTS messages.
It is measured when the local SCCP receives a UDTS message, and performs the
routing function to check if the UDTS address information includes incompletely
translated information, or if the subsystem or signaling point is accessible. If the
optional field in the UDTS message is set to error return, SCCP sends the message
back to the originating SCCP.
MSC\HLR.. MSC Server
UDTS
SCCP A
IV. Formula
None
10.35.3 Count of UDTS Messages Received
I. Entity Name
RCVUDTS
II. Description
It is the count of UDTS messages send by SCCP but failed to reach the DSP.
It is measured when the SCCP entry receives the UDTS message.
10-406
UDTS
SCCP A
IV. Formula
None
10.35.4 Count of Processed Messages (from Local or Remote Subsystem)
I. Entity Name
ALLMSG
II. Description
It is the count of messages processed by SCCP.
It is measured when SCCP receives the SCCP message from MTP, or receives the
SCCP user message.
SCCP USER
SCCP Message
SCCP
A
IV. Formula
None
10.35.5 Count of Messages Used by Local Subsystem
I. Entity Name
SSNMSG
10-407
II. Description
It is the count of messages destined to the local SCCP subsystem.
It is measured when the DPC in either the SCCP message or the SCCP user message
received by SCCP is the local signaling point, and the subsystem specified in the
message is available.
SCCP USER
SCCP Message
SCCP
A
IV. Formula
None
10.35.6 Count of Messages Needing GT Translation
I. Entity Name
GTMSG
II. Description
It is the count of messages that require the SCCP GT translation function.
It is measured when SCCP receives the GT routing indication for a called address in
the MTP message, or receives a connectionless message or a connection request that
does not contain the DPC.
10-408
SCCP USER
SCCP Message
SCCP
A
IV. Formula
None
10.35.7 Count of Connectionless Messages Sent
I. Entity Name
SNTCLM
II. Description
It is the count of connectionless service (including class 0 and 1) messages sent by

SCCP.
It is measured when the local SCCP sends the connectionless message.
UDT
SCCP A
IV. Formula
None
10.35.8 Count of Connectionless Messages Received
I. Entity Name
RCVCLM
10-409
II. Description
It is the count of connectionless messages received by SCCP.
It is measured when the local SCCP entry receives the connectionless message.
UDT
SCCP A
IV. Formula
None
10.35.9 Count of Messages Sent to a Standby Subsystem
I. Entity Name
RSSMSG
II. Description
It is the count of messages that SCCP sends to a standby subsystem.
It is measured when the decoding flag is set to decode to standby subsystem.
SCCP Message
SCCP A
IV. Formula
None
10-410
10.36 SCCP Traffic
10.36.1 Overview of MS_SCCP_FLUX_TRAFFIC
Name Description
SNDMSGS Count of messages sent to a DSP
RCVMSGS Count of messages received from a DSP
SNDOCTS Count of bytes sent to a DSP
RCVOCTS Count of bytes received from a DSP
10.36.2 Count of Messages Sent to a DSP
I. Entity Name
SNDMSGS
II. Description
It is the count of messages sent to a DSP.
It is measured when SCCP sends a message to the DSP.
Message
SCCP A
IV. Formula
None
10.36.3 Count of Messages Received from a DSP
I. Entity Name
RCVMSGS
10-411
II. Description
It is the count of messages received from a DSP.
It is measured when SCCP receives a message from the DSP.
Message
SCCP A
IV. Formula
None
10.36.4 Count of Bytes Sent to a DSP
I. Entity Name
SNDOCTS
II. Description
It is the count of bytes in messages sent to a DSP.
It is measured when SCCP sends a message to the DSP.
Message
SCCP A
IV. Formula
None
10-412
10.36.5 Count of Bytes Received from a DSP
I. Entity Name
RCVOCTS
II. Description
It is the count of bytes in messages received from a DSP.
It is measured when SCCP receives a message from the DSP.
Message
SCCP A
IV. Formula
None
10.37 SCCP Performance
10.37.1 Overview of MS_SCCP_PERFORMANCE
Name Description
RFNAI Count of route failures due to invalid addressing information
RFNSA Count of route failures due to translation failure of valid address
RFPCU Count of route failures due to unavailable signaling point
RFNC Count of route failures due to network congestion
RFSSF Count of route failures due to subsystem failure
RFSSC Count of route failures due to subsystem congestion
RFSSU Count of route failures due to subsystem not installed
RFUR Count of route failures due to unknown reason
RFSER Count of route failures due to syntax error
10-413
10.37.2 Count of Route Failures Due to Invalid Addressing Information
I. Entity Name
RFNAI
II. Description
It is the count of SCCP route failures due to invalid addressing information.
It is measured when the SCCP route fails because SCCP receives a message which
contains invalid addressing information.
IV. Formula
None
10.37.3 Count of Route Failures Due to Translation Failure of Valid Address
I. Entity Name
RFNSA
II. Description
It is the count of SCCP route failures due to translation failure of valid addresses.
It is measured when the SCCP route fails because SCCP cannot find the translation
result of a specific address.
IV. Formula
None
10.37.4 Count of Route Failures Due to Unavailable Signaling Point
I. Entity Name
RFPCU
II. Description
It is the count of SCCP route failures due to signaling point unavailable.
It is measured when the SCCP route fails because the DSP is unavailable while SCCP
sends a message.
10-414
IV. Formula
None
10.37.5 Count of Route Failures Due to Network Congestion
I. Entity Name
RFNC
II. Description
It is the count of SCCP route failures due to network congestion.
It is measured when the SCCP route fails because the DSP is congested while SCCP
sends a message.
IV. Formula
None
10.37.6 Count of Route Failures Due to Subsystem Failure
I. Entity Name
RFSSF
II. Description
It is the count of SCCP route failures due to subsystem failure.
It is measured when the SCCP route fails because the subsystem is faulty while SCCP
receives or sends a message.
IV. Formula
None
10.37.7 Count of Route Failures Due to Subsystem Congestion
I. Entity Name
RFSSC
II. Description
It is the count of SCCP route failures due to subsystem congestion.
10-415
It is measured when the SCCP route fails because the subsystem is congested while
SCCP receives or sends a message.
IV. Formula
None
10.37.8 Count of Route Failures Due to Subsystem Not Installed
I. Entity Name
RFSSU
II. Description
It is the count of SCCP route failures due to subsystem not installed.
It is measured when the SCCP route fails because the subsystem is not installed while
SCCP receives or sends a message.
IV. Formula
None
10.37.9 Count of Route Failures Due to Unknown Reason
I. Entity Name
RFUR
II. Description
It is the count of SCCP route failures due to unknown reasons.
It is measured when the SCCP route fails due to unknown reasons.
IV. Formula
None
10.37.10 Count of Route Failures Due to Syntax Error
I. Entity Name
RFSER
10-416
II. Description
It is the count of SCCP route failures due to syntax error in the addressing information.
It is measured when the SCCP route fails because SCCP detects a syntax error in the
addressing information.
IV. Formula
None
10.38 TCAP CSL
10.38.1 Overview of MS_TCAP_CSL_PERFORMANCE
Name Description
UKCMP Count of unrecognized components
CMPTERR Count of components of wrong type
CMPSERR Count of wrong component structures
UKLID Count of unrecognized link IDs

RRUEXP Count of unexpected results
UKIIDRR Count of unrecognized operation IDs in results
REUEXP Count of unexpected errors

UKIIDRE Count of unrecognized operation IDs in errors
10.38.2 Count of Unrecognized Components
I. Entity Name
UKCMP
II. Description
It is the count of unrecognized components.
It is measured when TCAP receives unrecognized components.
10-417
IV. Formula
None
10.38.3 Count of Components of Wrong Type
I. Entity Name
CMPTERR
II. Description
It is the count of components of wrong types.
It is measured when TCAP sends or receives components of wrong types.
IV. Formula
None
10.38.4 Count of Wrong Component Structures
I. Entity Name
CMPSERR
II. Description
It is the count of wrong component structures.
It is measured when the component received by TCAP contains wrong component

structures.
IV. Formula
None
10.38.5 Count of Unrecognized Link IDs
I. Entity Name
UKLID
II. Description
It is the count of unrecognized link IDs.
It is measured when the component received by TCAP contains unrecognized link IDs.
10-418
IV. Formula
None
10.38.6 Count of Unexpected Results
I. Entity Name
RRUEXP
II. Description
It is the count of unexpected results returned.
It is measured when TCAP receives returned results which are unexpected.
IV. Formula
None
10.38.7 Count of Unrecognized Operation IDs in Results
I. Entity Name
UKIIDRR
II. Description
It is the count of unrecognized operation IDs in returned results.
It is measured when TCAP receives unrecognized operation IDs in the returned results.
IV. Formula
None
10.38.8 Count of Unexpected Errors
I. Entity Name
REUEXP
II. Description
It is the count of unexpected errors returned.
It is measured when TCAP receives returned errors which are unexpected.
10-419
IV. Formula
None
10.38.9 Count of Unrecognized Operation IDs in Errors
I. Entity Name
UKIIDRE
II. Description
It is the count of unrecognized operation IDs in returned errors.
It is measured when TCAP receives unrecognized operation IDs in the returned errors.
IV. Formula
None
10.39 TCAP Transport Sublayer
10.39.1 Overview of MS_TCAP_TSL_PERFORMANCE
Name Description
Count of P_ABORT messages with cause of unrecognized
UKMSG
message type
Count of P_ABORT messages with cause of wrong
TRPERR
transaction portion
Count of P_ABORT messages with cause of wrong format

TRPFERR
of transaction portion
Count of P_ABORT messages with cause of unrecognized

UKTID
transaction ID
Count of P_ABORT messages with cause of resource

TRRSCLMT
limitation on transaction sublayer
10.39.2 Count of P_ABORT Messages with Cause of Unrecognized Message

Type
I. Entity Name
UKMSG
10-420
II. Description
It is the count of P_ABORT messages (with the cause of unrecognized message type)
generated when syntax check fails after a message is received from the peer end.
It is measured when error occurs in the syntax check with the cause of unrecognized
message type, after TCAP receives a message.
TCAP MSC Server
message type unknown
TCAP A
IV. Formula
None
10.39.3 Count of P_ABORT Messages with Cause of Wrong Transaction

Portion
I. Entity Name
TRPERR
II. Description
It is the count of P_ABORT messages (with the cause of wrong transaction portion)
It is measured when error occurs in the syntax check with the cause of wrong
transaction portion, after TCAP receives a message.
10-421
TCAP MSC Server
incorrect transaction
portion
TCAP A
IV. Formula
None
10.39.4 Count of P_ABORT Messages with Cause of Wrong Format of

Transaction Portion
I. Entity Name
TRPFERR
II. Description
It is the count of P_ABORT messages (with the cause of wrong transaction portion
format) generated when syntax check fails after a message is received from the peer
end.
It is measured when error occurs in the syntax check with the cause of wrong
transaction portion format, after TCAP receives a message.
TCAP MSC Server
badly transaction portion
TCAP A
IV. Formula
None
10-422

Transaction ID
I. Entity Name
UKTID
II. Description
It is the count of P_ABORT messages (with the cause of unrecognized transaction ID)
It is measured when error occurs in the syntax check with the cause of unrecognized
transaction ID, after TCAP receives a message.
TCAP MSC Server
unrecognized TID
TCAP A
IV. Formula
None
10.39.6 Count of P_ABORT Messages with Cause of Resource Limitation on

Transaction Sublayer
I. Entity Name
TRRSCLMT
II. Description
It is the count of P_ABORT messages (with the cause of resource limitation on

transaction sublayer) generated because no resource is available after a message is
received from the peer end.
It is measured when TCAP receives a message and prepares to set up a call, but finds
no available resource.
10-423
TCAP MSC Server
resource limitation
TCAP A
IV. Formula
None
10.40 TCAP Availability
10.40.1 Overview of MS_TCAP_AVAILABILITY
Name Description
UAFL Count of local TCAP failures due to fault
UAMT Count of local TCAP failures due to maintenance
UACG Count of local TCAP failures due to congestion
UADUR Duration of unavailability of local TCAP due to all causes
10.40.2 Count of Local TCAP Failures Due to Fault
I. Entity Name
UAFL
II. Description
It is the count of local TCAP failures due to fault.
It is measured when the local TCAP fails due to fault.
IV. Formula
None
10-424
10.40.3 Count of Local TCAP Failures Due to Maintenance
I. Entity Name
UAMT
II. Description
It is the count of local TCAP failures due to maintenance.
It is measured when the local TCAP fails due to maintenance.
IV. Formula
None
10.40.4 Count of Local TCAP Failures Due to Congestion
I. Entity Name
UACG
II. Description
It is the count of local TCAP failures due to congestion.
It is measured when the local TCAP fails due to congestion.
IV. Formula
None
10.40.5 Duration of Unavailability of Local TCAP Due to All Causes
I. Entity Name
UADUR
II. Description
It is the duration of the local TCAP failure due to any cause.
It is measured since the local TCAP fails due to maintenance and until it is recovered.
IV. Formula
None
10-425
10.41 Count of TCAP Messages
10.41.1 Overview of MS_TCAP_MSG_UTILIZATION
Name Description
SNTIVKMSGS Count of invoke messages sent
SNTIVKMSGR Count of invoke messages received
SNTLRMSGS Count of last result messages sent (returned result)
SNTLRMSGR Count of last result messages received (returned result)
SNTNLRMSGS Count of not last result messages sent (returned result)
SNTNLRMSGR Count of not last result messages received (returned result)
SNTREMSGS Count of returned error messages sent
SNTREMSGR Count of returned error messages received
SNTRJMSGS Count of reject messages sent

SNTRJMSGR Count of reject messages received
10.41.2 Count of Invoke Messages Sent
I. Entity Name
SNTIVKMSGS
II. Description
It is the count of invoke messages sent by this node.
It is measured when TCAP sends the invoke message.
10-426
TCAP MSC Server
invoke message
TCAP A
IV. Formula
None
10.41.3 Count of Invoke Messages Received
I. Entity Name
SNTIVKMSGR
II. Description
It is the count of invoke messages received by this node.
It is measured when TCAP receives the invoke message.
TCAP MSC Server
invoke message
TCAP A
IV. Formula
None
10.41.4 Count of Last Result Messages Sent (Returned Result)
I. Entity Name
SNTLRMSGS
10-427
II. Description
It is the count of last result messages (returned results) from this node.
It is measured when TCAP sends the last result message (returned result).
TCAP MSC Server
last result message
TCAP A
IV. Formula
None
10.41.5 Count of Last Result Messages Received (Returned Result)
I. Entity Name
SNTLRMSGR
II. Description
It is the count of last result messages (returned results) to this node.
It is measured when TCAP receives the last result message (returned result).
TCAP MSC Server
result message
TCAP A
IV. Formula
None
10-428
10.41.6 Count of Not Last Result Messages Sent (Returned Result)
I. Entity Name
SNTNLRMSGS
II. Description
It is the count of not last result messages (returned results) from this node.
It is measured when TCAP sends the not last result message (returned result).
TCAP MSC Server
not last result message
TCAP A
IV. Formula
None
10.41.7 Count of Not Last Result Messages Received (Returned Result)
I. Entity Name
SNTNLRMSGR
II. Description
It is the count of not last result messages (returned results) to this node.
It is measured when TCAP receives the not last result message (returned result).
10-429
TCAP MSC Server
not last result message
TCAP A
IV. Formula
None
10.41.8 Count of Returned Error Messages Sent
I. Entity Name
SNTREMSGS
II. Description
It is the count of returned error messages sent by this node.
It is measured when TCAP sends the returned error message.
TCAP MSC Server
return error message
TCAP A
IV. Formula
None
10.41.9 Count of Returned Error Messages Received
I. Entity Name
SNTREMSGR
10-430
II. Description
It is the count of returned error messages received by this node.
It is measured when TCAP receives the returned error message.
TCAP MSC Server
return error message
TCAP A
IV. Formula
None
10.41.10 Count of Reject Messages Sent
I. Entity Name
SNTRJMSGS
II. Description
It is the count of reject messages sent by this node.
It is measured when TCAP sends the reject message.
TCAP MSC Server
reject message
TCAP A
IV. Formula
None
10-431
10.41.11 Count of Reject Messages Received
I. Entity Name
SNTRJMSGR
II. Description
It is the count of reject messages received by this node.
It is measured when TCAP receives the reject message.
TCAP MSC Server
reject message
TCAP A
IV. Formula
None
10.42 TCAP Component Utilization

10.42.1 Overview of MS_TCAP_CMP_UTILIZATION
Name Description
SNTIVKS Count of invoke components sent
SNTIVKR Count of invoke components received
SNTLRS Count of last result components sent (returned result)
SNTLRR Count of last result components received (returned result)
SNTNLRS Count of not last result components sent (returned result)
SNTNLRR Count of not last result components received (returned result)
SNTRES Count of return error components sent
SNTRER Count of return error components received
SNTRJS Count of reject components sent
SNTRJR Count of reject components received
10-432
10.42.2 Count of Invoke Components Sent
I. Entity Name
SNTIVKS
II. Description
It is the count of invoke components sent by this node.
It is measured when TCAP sends the invoke component.
TCAP MSC Server
invoke component
TCAP A
IV. Formula
None
10.42.3 Count of Invoke Components Received
I. Entity Name
SNTIVKR
II. Description
It is the count of invoke components received by this node.
It is measured when TCAP receives the invoke component.
10-433
TCAP MSC Server
invoke component
TCAP A
IV. Formula
None
10.42.4 Count of Last Result Components Sent (Returned Result)
I. Entity Name
SNTLRS
II. Description
It is the count of last result components (returned results) from this node.
It is measured when TCAP sends the last result component (returned result).
TCAP MSC Server
last result component
TCAP A
IV. Formula
None
10.42.5 Count of Last Result Components Received (Returned Result)
I. Entity Name
SNTLRR
10-434
II. Description
It is the count of last result components (returned results) to this node.
It is measured when TCAP receives the last result component (returned result).
TCAP MSC Server
last result component
TCAP A
IV. Formula
None
10.42.6 Count of Not Last Result Components Sent (Returned Result)
I. Entity Name
SNTNLRS
II. Description
It is the count of not last result components (returned results) from this node.
It is measured when TCAP sends the not last result component (returned result).
TCAP MSC Server
not last result component
TCAP A
IV. Formula
None
10-435
10.42.7 Count of Not Last Result Components Received (Returned Result)
I. Entity Name
SNTNLRR
II. Description
It is the count of not last result components (returned results) to this node.
It is measured when TCAP receives the not last result component (returned result).
TCAP MSC Server
not last result component
TCAP A
IV. Formula
None
10.42.8 Count of Return Error Components Sent
I. Entity Name
SNTRES
II. Description
It is the count of returned error components sent by this node.
It is measured when TCAP sends the returned error component.
10-436
TCAP MSC Server
return error component
TCAP A
IV. Formula
None
10.42.9 Count of Return Error Components Received
I. Entity Name
SNTRER
II. Description
It is the count of returned error components received by this node.
It is measured when TCAP receives the returned error component.
TCAP MSC Server
TCAP A
IV. Formula
None
10.42.10 Count of Reject Components Sent
I. Entity Name
SNTRJS
10-437
II. Description
It is the count of reject components sent by this node.
It is measured when TCAP sends the reject component.
TCAP MSC Server
TCAP A
IV. Formula
None
10.42.11 Count of Reject Components Received
I. Entity Name
SNTRJR
II. Description
It is the count of reject components received by this node.
It is measured when TCAP receives the reject component.
TCAP MSC Server
TCAP A
IV. Formula
None
10-438
10.43 TUP Circuit Group
10.43.1 Overview of MS_TUP_TKGRP_PERFORM_TRAF
Name Description
SEC Count of messages with cause of switch congestion
CGC Count of messages with cause of circuit group congestion
NNC Count of messages with cause of national network congestion
ADI Count of messages with cause of incomplete address
CLFL Count of messages with cause of call failure
BSY Count of messages with cause of callee busy
UNN Count of messages with cause of unallocated number

LOS Count of messages with cause of line out of service
SST Count of messages with cause of sending special signal tone
ACB Count of messages with cause of rejected access

DPN Count of messages with cause of digital path not provided
WGTKPFX Count of messages with cause of dial trunk prefix wrongly dialed

RSEC Count of SEC messages received
RCGC Count of CGC messages received
RNNC Count of NNC messages received
RADI Count of ADI messages received
RCFL Count of CFL messages received
RSB Count of messages received with cause of callee busy
RUNN Count of UNN messages received
RLOS Count of LOS messages received
RSST Count of SST messages received
RACB Count of ACB messages received
RDPN Count of DPN messages received
Count of messages received with cause of trunk prefix wrongly

RWGTKPFX
dialed
10-439
Name Description
ANN Count of answers without charging
MGB Count of maintenance-oriented CGB messages
HGB Count of hardware-oriented CGB messages
GRS Count of circuit group reset messages
CIRRST Count of circuit reset messages
ANS Count of answers
MSUR Count of messages received
MSUS Count of messages sent
MSURS Count of messages both received and sent
MSURL Length of messages received
MSUSL Length of messages sent
MSURSL Length of messages both received and sent
IOPEGS Count of calls
MSULPC Length of messages per call

MSUAVL Average message length
I. Entity Name
IPEGS
II. Description
It is the count of IAM or IAI messages received by the MSC.
It is measured when the MSC receives the TUP IAM or TUP IAI message. See point A
10-440
IAM/IAI
IV. Formula
None
10.43.3 Count of Messages with Cause of Switching Equipment Congestion
I. Entity Name
SEC
II. Description
no resource like IPATH, CR, CCB and HW is allocated.
It is measured when the local TUP sends the SEC message. See point A in the
following figure.
SEC
10-441
IV. Formula
None
10.43.4 Count of Messages with Cause of Circuit Group Congestion
I. Entity Name
CGC
II. Description
The circuit group in the peer office is congested.
It is measured when the local office receives the CGC message. See point A in the
following figure.
CGC
IV. Formula
None
10.43.5 Count of Messages with Cause of National Network Congestion
I. Entity Name
NNC
II. Description
It is the count of NNC messages received.
10-442
It is not measured.
IV. Formula
None
I. Entity Name
CG
II. Description
It is the count of total congestion.
It is not measured.
IV. Formula
None
10.43.7 Count of Messages with Cause of Incomplete Address
I. Entity Name
ADI
II. Description
It is the count of messages with the cause of incomplete called number for an incoming
call.
It is measured when the local office finds out that the called number for an incoming call
is incomplete and then sends the ADI message. See point A in the following figure.
10-443
ADI
IV. Formula
None
10.43.8 Count of Messages with Cause of Call Failure
I. Entity Name
CLFL
II. Description
It is the count of messages with the cause of callee busy.
It is measured when the local office sends the CFL message. See point A in the
following figure.
10-444
CFL
IV. Formula
None
10.43.9 Count of Messages with Cause of Callee Busy
I. Entity Name
BSY
II. Description
It is measured when the SLB or STB message is received. See point A in the following
figure.
10-445
SLB/STB
IV. Formula
None
10.43.10 Count of Messages with Cause of Unallocated Number
I. Entity Name
UNN
II. Description
It is the count of messages with the cause of incoming number unallocated.
It is measured when the local office sends the UNN message. See point A in the
following figure.
10-446
UNN
IV. Formula
None
10.43.11 Count of Messages with Cause of Line out of Service
I. Entity Name
LOS
II. Description
It is the count of messages with the cause of line out of service.
It is measured when the terminal fails and the local office sends the LOS message. See
10-447
LOS
IV. Formula
None
10.43.12 Count of Messages with Cause of Sending Special Signal Tone
I. Entity Name
SST
II. Description
It is the count of messages with the cause of notifying the former office that the local
office sends the special signal tone.
It is measured when the local office sends the SST message. See point A in the
following figure.
10-448
SST
IV. Formula
None
10.43.13 Count of Messages with Cause of Rejected Access
I. Entity Name
ACB
II. Description
It is the count of messages with the cause of rejected accesses due to bearer capability
not laid out or terminal incompatible.
It is measured when the local office sends the ACB message. See point A in the
following figure.
10-449
ACB
IV. Formula
None
10.43.14 Count of Messages with Cause of Digital Path Not Provided
I. Entity Name
DPN
II. Description
It is the count of messages with the cause of digital path not provided.
It is measured when the local office sends the DPN message. See point A in the
following figure.
10-450
DPN
IV. Formula
None
10.43.15 Count of Messages with Cause of Trunk Prefix Wrongly Dialed
I. Entity Name
WGTKPFX
II. Description
It is the count of messages with the cause of trunk prefix wrongly dialed.
It is not measured.
IV. Formula
None
I. Entity Name
OPEGS
II. Description
10-451
It is measured when the MSC sends the TUP IAM or TUP IAI message. See point A in
IAM/IAI
IV. Formula
None
10.43.17 Count of SEC Messages Received
I. Entity Name
RSEC
II. Description
It is the count of SEC messages received.
It is measured when the local office receives the SEC message. See point A in the
following figure.
10-452
SEC
IV. Formula
None
10.43.18 Count of CGC Messages Received
I. Entity Name
RCGC
II. Description
It is the count of CGC messages received.
following figure.
10-453
CGC
IV. Formula
None
10.43.19 Count of NNC Messages Received
I. Entity Name
RNNC
II. Description
It is measured when the local office receives the NNC message. See point A in the
following figure.
10-454
NNC
IV. Formula
None
10.43.20 Count of ADI Messages Received
I. Entity Name
RADI
II. Description
It is the count of ADI messages received.
It is measured when the local office receives the ADI message. See point A in the
following figure.
10-455
ADI
IV. Formula
None
10.43.21 Count of CFL Messages Received
I. Entity Name
RCFL
II. Description
It is the count of CFL messages received.
It is measured when the local office receives the CFL message. See point A in the
following figure.
10-456
CFL
IV. Formula
None
10.43.22 Count of Messages Received with Cause of Callee Busy
I. Entity Name
RSB
II. Description
It is the count of messages received with the cause of callee busy.
It is measured when the local office receives the SLB or STB message. See point A in
10-457
SLB/STB
IV. Formula
None
10.43.23 Count of UNN Messages Received
I. Entity Name
RUNN
II. Description
It is the count of UNN messages received.
It is measured when the local office receives the UNN message. See point A in the
following figure.
10-458
UNN
IV. Formula
None
10.43.24 Count of LOS Messages Received
I. Entity Name
RLOS
II. Description
It is the count of LOS messages received.
It is measured when the local office receives the LOS message. See point A in the
following figure.
10-459
LOS
IV. Formula
None
10.43.25 Count of SST Messages Received
I. Entity Name
RSST
II. Description
It is the count of SST messages received.
It is measured when the local office receives the SST message. See point A in the
following figure.
10-460
SST
IV. Formula
None
10.43.26 Count of ACB Messages Received
I. Entity Name
RACB
II. Description
It is the count of ACB messages received.
It is measured when the local office receives the ACB message. See point A in the
following figure.
10-461
ACB
IV. Formula
None
10.43.27 Count of DPN Messages Received
I. Entity Name
RDPN
II. Description
It is the count of DPN messages received.
It is measured when the local office receives the DPN message. See point A in the
following figure.
10-462
DPN
IV. Formula
None
10.43.28 Count of Messages Received with Cause of Trunk Prefix Wrongly

Dialed
I. Entity Name
RWGTKPFX
II. Description
It is the count of messages received with the cause of trunk prefix wrongly dialed.
It is not measured.
IV. Formula
None
10.43.29 Count of Answers Without Charging
I. Entity Name
ANN
II. Description
It is the count of answers without charging.
10-463
It is measured when the local office receives or sends the ANN message. See point A in
ANN
IV. Formula
None
10.43.30 Count of Maintenance-Oriented CGB Messages
I. Entity Name
MGB
II. Description
It is the count of maintenance-oriented CGB messages received.
It is measured when the local office receives or sends the MGB message. See point A
10-464
MGB
MGB
IV. Formula
None
10.43.31 Count of Hardware-Oriented CGB Messages
I. Entity Name
HGB
II. Description
It is the count of hardware-oriented CGB messages received.
10-465
It is measured when the local office receives or sends the HGB message. See point A in
HGB
HGB
IV. Formula
None
10.43.32 Count of Circuit Group Reset Messages
I. Entity Name
GRS
II. Description
It is the count of circuit group reset messages received.
10-466
It is measured when the local office receives or sends the GRS message. See point A in
GRS
GRS
IV. Formula
None
10.43.33 Count of Circuit Reset Messages
I. Entity Name
CIRRST
II. Description
It is the count of circuit reset messages received.
10-467
It is measured when the local office receives or sends the RSC message. See point A in
RSC
RSC
IV. Formula
None
10.43.34 Count of Answers
I. Entity Name
ANS
II. Description
It is the count of call answers.
10-468
It is measured when the local office receives or sends the ANC message. See point A in
ANC
ANC
IV. Formula
None
I. Entity Name
MSUR
II. Description
It is the count of TUP messages received by the local office.
10-469
It is measured when the local office receives the TUP message.
IV. Formula
None
I. Entity Name
MSUS
II. Description
It is the count of TUP messages sent by the local office.
It is measured when the local office sends the TUP message.
IV. Formula
None
10.43.37 Count of Messages Both Received and Sent
I. Entity Name
MSURS
II. Description
It is the count of TUP messages both received and sent by the local office.
IV. Formula
None
10.43.38 Length of Messages Received
I. Entity Name
MSURL
II. Description
It is the total length of TUP messages received by the local office.
10-470
It is measured when the local office receives the TUP message.
IV. Formula
None
10.43.39 Length of Messages Sent
I. Entity Name
MSUSL
II. Description
It is the total length of TUP messages sent by the local office.
It is measured when the local office sends the TUP message.
IV. Formula
None
10.43.40 Length of Messages Both Received and Sent
I. Entity Name
MSURSL
II. Description
It is the total length of TUP messages both received and sent by the local office.
IV. Formula
None
10.43.41 Count of Calls
I. Entity Name
IOPEGS
II. Description
It is the count of total calls.
10-471
It is not measured.
IV. Formula
None
10.43.42 Length of Messages per Call
I. Entity Name
MSULPC
II. Description
It is the count of bytes in messages needed for each call.
Length of messages both received and sent/Count of calls.
IV. Formula
None
10.43.43 Average Message Length
I. Entity Name
MSUAVL
II. Description
It is the average length of each TUP message.
Length of messages both received and sent/Count of messages.
IV. Formula
None
10-472
10.44 TUP Node
10.44.1 Overview of MS_TUP_NODE_PERFORM_TRAF
Name Description
SEC Count of messages with cause of switch congestion
CGC Count of messages with cause of circuit group congestion
NNC Count of messages with cause of national network congestion
ADI Count of messages with cause of incomplete address
CLFL Count of messages with call failure
SB Count of messages with cause of callee busy
UNN Count of messages with cause of unallocated number

LOS Count of messages with cause of line out of service
SST Count of messages with cause of sending special tone
ACB Count of messages with cause of rejected access

DPN Count of messages with cause of digital path not provided
WGTKPFX Count of messages with cause of trunk prefix wrongly dialed
I. Entity Name
IPEGS
II. Description
It is the count of IAM or IAI messages received by the MSC.
It is measured when the MSC receives the TUP IAM or TUP IAI message. See point A
10-473
IAM/IAI
IV. Formula
None
10.44.3 Count of Messages with Cause of Switch Congestion
I. Entity Name
SEC
II. Description
no resource like IPATH, CR, CCB and HW is allocated.
It is measured when the local TUP sends the SEC message. See point A in the
following figure.
10-474
SEC
IV. Formula
None
10.44.4 Count of Messages with Cause of Circuit Group Congestion
I. Entity Name
CGC
II. Description
The circuit group in the peer office is congested.
The local office receives the CGC message. See point A in the following figure.
CGC
10-475
IV. Formula
None
10.44.5 Count of Messages with Cause of National Network Congestion
I. Entity Name
NNC
II. Description
The NNC message is received.
It is not measured.
IV. Formula
None
10.44.6 Count of Messages with Cause of Incomplete Address
I. Entity Name
ADI
II. Description
It is the count of messages with the cause of incomplete called number for an incoming
call.
It is measured when the local office finds out that the called number for an incoming call
is incomplete and then sends the ADI message. See point A in the following figure.
10-476
ADI
IV. Formula
None
10.44.7 Count of Messages with Cause of Call Failure
I. Entity Name
CLFL
II. Description
It is the count of incoming call failures.
It is measured when the local office sends the CFL message. See point A in the
following figure.
10-477
CFL
IV. Formula
None
10.44.8 Count of Messages with Cause of Callee Busy
I. Entity Name
SB
II. Description
It is measured when the local office sends the SLB or STB message. See point A in the
following figure.
10-478
SLB/STB
IV. Formula
None
10.44.9 Count of Messages with Cause of Unallocated Number
I. Entity Name
UNN
II. Description
It is the count of messages with the cause of incoming number unallocated.
It is measured when the local office sends the UNN message. See point A in the
following figure.
10-479
UNN
IV. Formula
None
10.44.10 Count of Messages with Cause of Line out of Service
I. Entity Name
LOS
II. Description
It is the count of messages with the cause of line out of service.
It is measured when the terminal fails and the local office sends the LOS message. See
10-480
LOS
IV. Formula
None
10.44.11 Count of Messages with Cause of Sending Special Tone
I. Entity Name
SST
II. Description
It is the count of messages with the cause of notifying the former office that the local
office sends the special signal tone.
It is measured when the local office sends the SST message. See point A in the
following figure.
10-481
SST
IV. Formula
None
10.44.12 Count of Messages with Cause of Rejected Access
I. Entity Name
ACB
II. Description
It is the count of messages with the cause of rejected accesses due to bearer capability
not laid out or terminal incompatible.
It is measured when the local office sends the ACB message. See point A in the
following figure.
10-482
ACB
IV. Formula
None
10.44.13 Count of Messages with Cause of Digital Path Not Provided
I. Entity Name
DPN
II. Description
It is the count of messages with the cause of digital path not provided.
It is measured when the local office sends the DPN message. See point A in the
following figure.
10-483
DPN
IV. Formula
None
10.44.14 Count of Messages with Cause of Trunk Prefix Wrongly Dialed
I. Entity Name
WGTKPFX
II. Description
It is the count of messages with the cause of trunk prefix wrongly dialed.
It is not measured.
IV. Formula
None
10-484
10.45 TUP Network
10.45.1 Overview of MS_TUP_NET_PERFORM_TRAF
Name Description
RSEC Count of SEC messages received
RCGC Count of CGC messages received
RNNC Count of NNC messages received
RADI Count of ADI messages received
RCFL Count of CFL messages received
RSB Count of messages received with cause of callee busy
RUNN Count of UNN messages received

RLOS Count of LOS messages received
RSST Count of SST messages received
RACB Count of ACB messages received

RDPN Count of DPN messages received
Count of messages received with cause of trunk prefix wrongly
RWGTKPFX
dialed
I. Entity Name
OPEGS
II. Description
It is measured when the MSC sends the TUP IAM or TUP IAI message. See point A in
10-485
IAM/IAI
IV. Formula
None
10.45.3 Count of SEC Messages Received
I. Entity Name
RSEC
II. Description
It is the count of SEC messages received.
It is measured when the local office receives the SEC message. See point A in the
following figure.
10-486
SEC
IV. Formula
None
10.45.4 Count of CGC Messages Received
I. Entity Name
RCGC
II. Description
It is the count of CGC messages received.
following figure.
10-487
CGC
IV. Formula
None
10.45.5 Count of NNC Messages Received
I. Entity Name
RNNC
II. Description
It is measured when the local office receives the NNC message. See point A in the
following figure.
10-488
NNC
IV. Formula
None
10.45.6 Count of ADI Messages Received
I. Entity Name
RADI
II. Description
It is the count of ADI messages received.
It is measured when the local office receives the ADI message. See point A in the
following figure.
10-489
ADI
IV. Formula
None
10.45.7 Count of CFL Messages Received
I. Entity Name
RCFL
II. Description
It is the count of CFL messages received.
It is measured when the local office receives the CFL message. See point A in the
following figure.
10-490
CFL
IV. Formula
None
10.45.8 Count of Messages Received with Cause of Callee Busy
I. Entity Name
RSB
II. Description
It is the count of messages received with the cause of callee busy.
It is measured when the local office receives the SLB or STB message. See point A in
10-491
SLB/STB
IV. Formula
None
10.45.9 Count of UNN Messages Received
I. Entity Name
RUNN
II. Description
It is the count of UNN messages received.
It is measured when the local office receives the UNN message. See point A in the
following figure.
10-492
UNN
IV. Formula
None
10.45.10 Count of LOS Messages Received
I. Entity Name
RLOS
II. Description
It is the count of LOS messages received.
It is measured when the local office receives the LOS message. See point A in the
following figure.
10-493
LOS
IV. Formula
None
10.45.11 Count of SST Messages Received
I. Entity Name
RSST
II. Description
It is the count of SST messages received.
It is measured when the local office receives the SST message. See point A in the
following figure.
10-494
SST
IV. Formula
None
10.45.12 Count of ACB Messages Received
I. Entity Name
RACB
II. Description
It is the count of ACB messages received.
It is measured when the local office receives the ACB message. See point A in the
following figure.
10-495
ACB
IV. Formula
None
10.45.13 Count of DPN Messages Received
I. Entity Name
RDPN
II. Description
It is the count of DPN messages received.
It is measured when the local office receives the DPN message. See point A in the
following figure.
10-496
DPN
IV. Formula
None
10.45.14 Count of Messages Received with Cause of Trunk Prefix Wrongly

Dialed
I. Entity Name
RWGTKPFX
II. Description
It is the count of messages received with the cause of trunk prefix wrongly dialed.
It is not measured.
IV. Formula
None
10-497
10.46 TUP Message Application
10.46.1 Overview of MS_TUP_MSG_USING_TRAF
The names and meanings of the measurement entities are listed in the following figure.
Name Description
SMSG Count of certain messages sent
RMSG Count of certain messages received
10.46.2 Count of Certain Messages Sent
I. Entity Name
SMSG
II. Description
It is the count of a type of TUP messages sent through a group of circuits.
It is measured when the MSC sends the TUP message.
IV. Formula
None
10.46.3 Count of Certain Messages Received
I. Entity Name
RMSG
II. Description
It is the count of a type of TUP messages received through a group of circuits.
It is measured when the MSC receives the TUP message.
IV. Formula
None
10-498
10.47 Count of TUP Messages
10.47.1 Overview of MS_TUP_TOTAL_MSU_TRAF
Name Description
I. Entity Name
SMSU
II. Description
It is the count of a type of TUP messages sent through a group of circuits.
It is measured when the MSC sends the TUP message.
IV. Formula
None
I. Entity Name
RMSU
II. Description
It is the count of a type of TUP messages received through a group of circuits.
It is measured when the MSC receives the TUP message.
IV. Formula
None
10-499
10.48 TUP Abnormity
10.48.1 Overview of MS_TUP_UNUSUAL_TRAF
Name Description
T19 Count of responses to RSC not received by T19
T22 Count of RGAs not received by T22
T5 Count of CLFs not received by T5
T7 Count of RLGs not received by T7
UNSRLS Count of abnormal release messages
BLCIR Count of circuit blocking messages
NMHBA Count of failures to assign MHBA on some circuits
NMHUA Count of failures to assign MHUA on some circuits
TUMHBA Count of assignments of too many MHBAs on some circuits

TUMHUA Count of assignments of too many MHUAs on some circuits
RUEXMHBA Count of unexpected MHBAs received
RUEXMHUA Count of unexpected MHUAs received

RUEXBLA Count of unexpected BLAs received
RUEXUBA Count of unexpected UBAs received
T13 Count of BLAs not received by T13

T16 Count of UBAs not received by T16
T25 Count of second group messages not received by T25
T27 Count of MBAs not received by T27
T29 Count of MUAs not received by T29
T33 Count of HBAs not received by T33
T35 Count of HUAs not received by T35
MSGER Count of wrong format messages
RUEXMSG Count of unexpected messages received
RUKNWMSG Count of unknown messages received
10-500
10.48.2 Count of Responses to RSC Not Received by T19
I. Entity Name
T19
II. Description
It is the count of responses to the RSC message, which are not received by T19.
IV. Formula
None
10.48.3 Count of GRAs Not Received by T22
I. Entity Name
T22
II. Description
It is the count of GRA messages not received by T22.
IV. Formula
None
10.48.4 Count CLFs Not Received by T5
I. Entity Name
T5
II. Description
It is the count of CLF messages not received by T5.
IV. Formula
None
10-501
10.48.5 Count of RLGs Not Received by T7
I. Entity Name
T7
II. Description
It is the count of RLG messages not received by T7.
IV. Formula
None
10.48.6 Count of Abnormal Release Messages
I. Entity Name
UNSRLS
II. Description
It is the count of messages for abnormal release.
It is measured when the abnormal release message for circuit reset or hardware
blocking is received during a call.
IV. Formula
None
10.48.7 Count of Circuit Blocking Messages
I. Entity Name
BLCIR
II. Description
It is the count of messages for circuit blocking.
It is measured when the valid blocking message or group blocking message is received
from the peer office.
10-502
IV. Formula
None
10.48.8 Count of Failures to Assign MHBA on Some Circuits
I. Entity Name
NMHBA
II. Description
It is the count of failures to assign MHBA messages on some circuits.
It is not measured.
IV. Formula
None
10.48.9 Count of Failures to Assign MHUA on Some Circuits
I. Entity Name
NMHUA
II. Description
It is the count of failures to assign MHUA messages on some circuits.
It is not measured.
IV. Formula
None
10.48.10 Count of Assignments of Too Many MHBAs on Some Circuits
I. Entity Name
TUMHBA
II. Description
It is the count of assignments of too many MHBA messages on some circuits.
It is not measured.
10-503
IV. Formula
None
10.48.11 Count of Assignments of Too Many MHUAs on Some Circuits
I. Entity Name
TUMHUA
II. Description
It is the count of assignments of too many MHUA messages on some circuits.
It is not measured.
IV. Formula
None
10.48.12 Count of Unexpected MHBAs Received
I. Entity Name
RUEXMHBA
II. Description
It is the count of unexpected MHBA messages received.
It is not measured.
IV. Formula
None
10.48.13 Count of Unexpected MHUAs Received
I. Entity Name
RUEXMHUA
II. Description
It is the count of unexpected MHUA messages received.
It is not measured.
10-504
IV. Formula
None
10.48.14 Count of Unexpected BLAs Received
I. Entity Name
RUEXBLA
II. Description
It is the count of unexpected BLA messages received.
It is measured when the BLA message is received before the BLO message is sent.
IV. Formula
None
10.48.15 Count of Unexpected UBAs Received
I. Entity Name
RUEXUBA
II. Description
It is the count of unexpected UBA messages received.
It is measured when the UBA message is received before the UBL message is sent.
IV. Formula
None
10.48.16 Count of BLAs Not Received by T13
I. Entity Name
T13
II. Description
It is the count of BLA messages not received by T13.
10-505
IV. Formula
None
10.48.17 Count of UBAs Not Received by T16
I. Entity Name
T16
II. Description
It is the count of UBA messages not received by T16.
IV. Formula
None
10.48.18 Count of Second Group Messages Not Received by T25
I. Entity Name
T25
II. Description
It is the count of second group messages not received by T25.
It is measured when TR_TUP_T23, TR_TUP_T24, TR_TUP_T30, or TR_TUP_T31

times out.
IV. Formula
None
10.48.19 Count of MBAs Not Received by T27
I. Entity Name
T27
II. Description
It is the count of MBA messages not received by T27.
10-506
IV. Formula
None
10.48.20 Count of MUAs Not Received by T29
I. Entity Name
T29
II. Description
It is the count of MUA messages not received by T29.
IV. Formula
None
10.48.21 Count of HBAs Not Received by T33
I. Entity Name
T33
II. Description
It is the count of HBA messages not received by T33.
IV. Formula
None
10.48.22 Count of HUAs Not Received by T35
I. Entity Name
T35
II. Description
It is the count of HUA messages not received by T35.
10-507
IV. Formula
None
10.48.23 Count of Wrong Format Messages
I. Entity Name
MSGER
II. Description
It is the count of messages of a wrong format.
It is not measured.
IV. Formula
None
10.48.24 Count of Unexpected Messages Received
I. Entity Name
RUEXMSG
II. Description
It is the count of unexpected messages received.
It is measured when the unexpected message is received.
IV. Formula
None
10.48.25 Count of Unknown Messages Received
I. Entity Name
RUKNWMSG
II. Description
It is the count of unknown messages received.
It is measured when the unknown message is received.
10-508
IV. Formula
None
10.49 Union Location Update Rejected Cause
10.49.1 Overview of MS_TYPE_UNION_LOC_UP
Name Description
UNKU77 Count of messages indicating unknown subscriber
RNA77 Count of messages indicating roaming not allowed

PRNA77 Count of messages indicating PLMN roaming not allowed
SYSE77 Count of messages indicating system failure
LSDT77 Count of messages indicating data lost
10.49.2 Count of Messages Indicating Unknown Subscriber
I. Entity Name
UNKU77
II. Description
It is the count of reject messages for union location update, with the cause of "unknown
subscriber".
It is measured when LOCATION-UPDATE-REJECT is sent to the Gs-interface, with the

cause of “unknown subscriber”.
10-509
SGSN MSC Server
BSSAP+-LOCATION-UPDATE-REQUEST
A
BSSAP+-LOCATION-UPDATE-REJECT
IV. Formula
None
10.49.3 Count of Messages Indicating Roaming Not Allowed
I. Entity Name
RNA77
II. Description
It is the count of reject messages for union location update, with the cause of "roaming
not allowed".

cause of “roaming not allowed”.
10-510
SGSN MSC Server
A
IV. Formula
None
10.49.4 Count of Messages Indicating PLMN Roaming Not Allowed
I. Entity Name
PRNA77
II. Description
It is the count of reject messages for union location update, with the cause of "PLMN
roaming not allowed".

cause of “PLMN roaming not allowed”.
10-511
SGSN MSC Server
A
IV. Formula
None
10.49.5 Count of Messages Indicating System Failure
I. Entity Name
SYSE77
II. Description
It is the count of reject messages for union location update, with the cause of "system
failure”.

cause of “system failure”.
10-512
SGSN MSC Server
A
IV. Formula
None
10.49.6 Count of Messages Indicating Data Lost
I. Entity Name
LSDT77
II. Description
It is the count of reject messages for union location update, with the cause of "data
lost".

cause of “data lost”.
10-513
SGSN MSC Server
A
IV. Formula
None
10-514
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 11 IN Services
Chapter 11 IN Services

The measurement set is used to measure the traffic of IN calls. The measurement units
are listed in the following table.
Measurement unit name Description

MS_TYPE_CAP_OPER CAP operations
MS_IN_ICA Initial call attempts
MS_TYPE_MAP_IN_SERVICE MAP IN Services

MS_TYPE_SSF_CALL_TRAF SSF calls
MS_TYPE_IN_INC_TRAF Fixed subscriber calling IN subscriber
MS_TYPE_IN_MT_INT_TRAF Mobile subscriber calling IN subscriber
MS_TYPE_IN_COMPOMENT IN components
MS_IN_DIALOGUE_TRAF IN dialogue
MS_TYPE_IN_OPERATOR_TRAF IN calls of all subscribers calling operator
MS_IN_FAILURE_TRAF IN failures
MS_TYPE_IN_EVENT_TRAF IN events
MS_TYPE_IN_ORGOUT_TRAF IN subscriber calling fixed subscriber
MS_TYPE_IN_MO_INT_TRAF IN subscriber calling mobile subscriber
MS_TYPE_IN_BOTH_TRAF IN subscriber calling IN subscriber
11.2 CAP Operations

11.2.1 Overview of MS_TYPE_CAP_OPER
Name Description
TRAT73 Count of received Activity Test messages
TSAT73 Count of sent Activity Test messages
TSAC73 Count of received Apply Charging messages
TSACR73 Count of sent Apply Charging Report messages
TSARI73 Count of sent Assist Request Instructions messages
11-1
Name Description
TRC73 Count of received Call Gap messages
TSCR73 Count of sent Call Information Report messages
TRCR73 Count of received Call Information Request messages
TRCL73 Count of received Cancel messages
TRCT73 Count of received Connect messages
TRCTR73 Count of received Connect To Resource messages
TRCN73 Count of Continue messages
TRDFC73 Count of Disconnect Forward Connection messages
TRETC73 Count of Establish Temporary Connection messages
TSERB73 Count of Event Report BCSM messages
TRFCI73 Count of Received Furnish Charging Information messages
TSIDP73 Count of Initial DP messages
TRPA73 Count of Play Announcement messages
TRPCUI73 Count of Prompt And Collect User Information messages

TSPCUI73 Count of Prompt and Collect User Information Results
TRRC73 Count of Release Call messages
TRRB73 Count of Request Report BCSM Event messages

TRRT73 Count of Reset Timer messages
TRSCI73 Count of Send Charging Information messages
TSSRR73 Count of Specialized Resource Report messages
TRNT73 Count of received NULL messages
TSN73 Count of sent NULL messages
TRE73 Count of received Error messages
TSE73 Count of sent Error messages
TSTA73 Count of sent TC_ABORT messages
TRTA73 Count of received TC_ABORT messages
CON73 Count of Continue With Argument messages
SMSC73 Count of Connect SMS messages
SMST73 Count of Continue SMS messages
SMSE73 Count of Event Report SMS messages
SMSB73 Count of Furnish Charging Information SMS messages
SMSDP73 Count of Initial DP SMS messages
11-2
Name Description
SMSRE73 Count of Release SMS messages
RPSMS73 Count of Request Report SMS Event messages
SMSRS73 Count of Reset Timer SMS messages
ICA73 Count of ICA messages
RPDN73 Count of Provide Avail DN messages (received)
SPDN73 Count of Provide Avail DN messages (sent)
RCOP73 Count of Port Connected messages (received)
SCOP73 Count of Port Connected messages (sent)
RBP73 Count of Bridge Ports messages (received)
SBP73 Count of Bridge Ports messages (sent)
11.2.2 Count of Received Activity Test Messages
I. Entity Name
TRAT73
II. Description
It is the count of received Activity Test messages.
It is measured when the MSC Server/SSP receives the Activity Test message from the
SCP. See point A in the following figure.
11-3
SCP MSC Server/SSP
ActivityTest
A
ActivityTest(RESUTLT)
IV. Formula
None
11.2.3 Count of Sent Activity Test Messages
I. Entity Name
TSAT73
II. Description
It is the count of sent Activity Test (RESULT) messages.
It is measured when the MSC Server/SSP sends the Activity Test (RESULT) message
upon receiving it, on condition that Session-ID is activated, and the SSP is using the
session. See point B in the following figure.
11-4
SCP MSC Server/SSP
ActivityTest
A
ActivityTest(RESUTLT)
IV. Formula
None
11.2.4 Count of Apply Charging Messages
I. Entity Name
TSAC73
II. Description
It is the count of received Apply Charging messages.
It is measured when the MSC Server/SSP receives the message Apply Charging from
the SCP. See point A in the following figure.
11-5
SCP MSC Server/SSP
ApplyCharging
A
ApplyChargingReport
IV. Formula
None
11.2.5 Count of Apply Charging Report Messages
I. Entity Name
TSACR73
II. Description
It is the count of sent Apply Charging Report messages.
It is measured when the SSP reports the message Apply Charging Report upon
detecting the Call release event, or when the duration in the parameter max Call Period
Duration in AC expires. See point B in the following figure.
11-6
SCP MSC Server/SSP
ApplyCharging
A
ApplyChargingReport
IV. Formula
None
11.2.6 Count of Assist Request Instructions Messages
I. Entity Name
TSARI73
II. Description
It is the count of sent Assist Request Instructions messages.
It is measured when the auxiliary SSP sends the message Assist Request Instructions
after receiving the IAM from the initial SSP. See point A in the following figure.
11-7
SCP MSCServer/AssistSSP MSCServer/InitialSSP
IAM
AssistRequestInstructions
IV. Formula
None
11.2.7 Count of Call Gap Messages
I. Entity Name
TRC73
II. Description
It is the count of received Call Gap messages.
It is measured when the MSC Server/SSP receives the message Call Gap from the
SCP after initiating a session through the IDP message. See point A in the following
figure.
11-8
SCP MSC Server/SSP
IDP
CallGap
IV. Formula
None
11.2.8 Count of Call Information Report Messages
I. Entity Name
TSCR73
II. Description
It is the count of sent Call Information Report messages.
It is measured when the MSC Server/SSP sends the message Call Information Report
if an idle Call Information Request exists on the following occasions:
z Caller releases the call
z Caller gives up the call
z Callee releases the call
z Callee is busy
z SCP sends the Call Release message
11-9
SCP MSC Server/SSP
CallInformationRequest
A
CallInformationReport
IV. Formula
None
11.2.9 Count of Call Information Request Messages
I. Entity Name
TRCR73
II. Description
It is the count of received Call Information Request messages.
It is measured when the MSC Server/SSP receives the message Call Information
Request from the SCP. See point A in the following figure.
11-10
SCP MSC Server/SSP
CallInformationRequest
A
CallInformationReport
IV. Formula
None
11.2.10 Count of Cancel Messages
I. Entity Name
TRCL73
II. Description
It is the count of received Cancel messages.
It is measured when the MSC Server/SSP receives the Cancel message from the SCP.
11-11
SCP MSC Server/SSP
IDP
ConnectToResource
PlayAnnouncement
Cancel
IV. Formula
None
11.2.11 Count of Connect Messages
I. Entity Name
TRCT73
II. Description
It is the count of received Connect messages.
It is measured when the MSC Server/SSP receives the Connect message from the
11-12
SCP MSC Server/SSP
IDP
Connect
IV. Formula
None
11.2.12 Count of Connect To Resource Messages
I. Entity Name
TRCTR73
II. Description
It is the count of received Connect To Resource messages.
It is measured when the MSC Server/SSP receives the message Connect To Resource.
11-13
SCP MSC Server/SSP
IDP
ConnectToResource
A
PlayAnnouncement
IV. Formula
None
11.2.13 Count of Continue Messages
I. Entity Name
TRCN73
II. Description
It is the count of received Continue messages.
It is measured when the MSC Server/SSP receives the Continue message. See point A
11-14
SCP MSC Server/SSP
IDP
RequestReportBCSMEvent
ApplyCharging
FurnishChargingInformation
Contiune A
IV. Formula
None
11.2.14 Count of Disconnect Forward Connection Messages
I. Entity Name
TRDFC73
II. Description
It is the count of received Disconnect Forward Connection messages.
It is measured when the MSC Server/initial SSP receives the message Disconnect
Forward Connection. See point B in the following figure.
11-15
SCP MSC Server/AssistSSP MSC Server/initialSSP
IDP
EstablishTemporary Connect
A
IAM
ConnectToResourse
PlayAnnouncement
ACM
ANM
DisconnectForwardConnection
B
SCP MSC Server/SSP
InitialDP(TDP2)
ConnectToResourse
PlayAnnouncement
SpecializedResourceReport
IV. Formula
None
11.2.15 Count of Establish Temporary Connection Messages
I. Entity Name
TRETC73
II. Description
It is the count of received Establish Temporary Connection messages.
It is measured when the MSC Server/initial SSP receives the message Establish
Temporary Connection. See point B in the following figure.
11-16
SCP MSC Server/AssistSSP MSC Server/initialSSP
IDP
EstablishTemporary Connect
A
IAM
ConnectToResourse
PlayAnnouncement
ACM
ANM
B
IV. Formula
None
11.2.16 Count of Event Report BCSM Messages
I. Entity Name
TSERB73
II. Description
It is the count of sent Event Report BCSM messages.
It is measured when the MSC Server/SSP sends the message Event Report BCSM.
11-17
SCP MSC Server/SSP
IDP
A
EventReprotBCSM
IV. Formula
None
11.2.17 Count of Received Furnish Charging Information
I. Entity Name
TRFCI73
II. Description
It is the count of received Furnish Charging Information messages.
It is measured when the MSC Server/SSP receives the message Furnish Charging
Information. See point A in the following figure.
11-18
SCP MSC Server/SSP
IDP
ApplyCharging
Contiune A
IV. Formula
None
11.2.18 Count of Initial DP Messages
I. Entity Name
TSIDP73
II. Description
It is the count of sent Initial DP messages.
It is measured when the MSC Server/SSP sends the message Initial DP. See point A in
11-19
SCP MSC Server/SSP
IDP
IV. Formula
None
11.2.19 Count of Play Announcement Messages
I. Entity Name
TRPA73
II. Description
It is the count of received Play Announcement messages.
It is measured when the MSC Server/SSP receives the message Play Announcement.
11-20
SCP MSC Server/SSP
IDP
ConnectToResource
PlayAnnouncement
PromptAndCollectUser A
Information
PromptAndCollectUser
Information(RESULT) B
IV. Formula
None
11.2.20 Count of Prompt And Collect User Information Messages
I. Entity Name
TRPCUI73
II. Description
It is the count of received Prompt And Collect User Information messages.
It is measured when the MSC Server/SSP receives the message Prompt And Collect
User Information. See point B in the following figure.
11-21
SCP MSC Server/SSP
IDP
ConnectToResource
PlayAnnouncement
Information
IV. Formula
None
11.2.21 Count of Prompt and Collect User Information Results
I. Entity Name
TSPCUI73
II. Description
It is the count of sent Prompt And Collect User Information (RESULT) messages.
It is measured when the MSC Server/SSP sends the message Prompt And Collect
User Information (RESULT). See point C in the following figure.
11-22
SCP MSC Server/SSP
IDP
ConnectToResource
PlayAnnouncement
Information
IV. Formula
None
11.2.22 Count of Release Call Messages
I. Entity Name
TRRC73
II. Description
It is the count of received Release Call messages.
It is measured when the MSC Server/SSP receives the Release Call message. See
11-23
SCP MSC Server/SSP
IDP
ReleaseCall
IV. Formula
None
11.2.23 Count of Request Report BCSM Event Messages
I. Entity Name
TRRB73
II. Description
It is the count of received Request Report BCSM Event messages.
It is measured when the MSC Server/SSP receives the message Request Report
BCSM Event. See point A in the following figure.
11-24
SCP MSC Server/SSP
IDP
A
EventReprotBCSM
IV. Formula
None
11.2.24 Count of Reset Timer Messages
I. Entity Name
TRRT73
II. Description
It is the count of received Reset Timer messages.
It is measured when the MSC Server/SSP receives the message Reset Timer. See
11-25
SCP MSC Server/SSP
IDP
ResetTimer
IV. Formula
None
11.2.25 Count of Send Charging Information Messages
I. Entity Name
TRSCI73
II. Description
It is the count of received Send Charging Information messages.
It is measured when the MSC Server/SSP receives the message Send Charging
Information. See point A in the following figure.
11-26
SCP MSC Server/SSP
IDP
SendChargingInformation
IV. Formula
None
11.2.26 Count of Specialized Resource Report Messages
I. Entity Name
TSSRR73
II. Description
It is the count of sent Specialized Resource Report messages.
It is measured when the MSC Server/SSP returns the message Specialized Resource
Report due to the announcement end indication set in the PA message. See point A in
11-27
SCP MSC Server/SSP
IDP
ConnectToResourse
PlayAnnouncement
SpecializedResourceReport
IV. Formula
None
11.2.27 Count of Received NULL Messages
I. Entity Name
TRNT73
II. Description
It is the count of received TC_END INVOKE (NULL) messages.
It is measured when the MSC Server/SSP receives the message TC_END INVOKE
(NULL). See point A in the following figure.
11-28
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-END
INVOKE(NULL)
IV. Formula
None
11.2.28 Count of Sent NULL Messages
I. Entity Name
TSN73
II. Description
It is the count of sent TC-END_REQ (NULL) messages.
It is measured when the MSC Server/SSP sends the message TC-END_REQ (NULL).
11-29
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-CONTINUE
INVOKE(RequestReportBC
SMEvent)
TC-CONTINUE
INVOKE(Connect)
TC-END_REQ
(NULL)
IV. Formula
None
11.2.29 Count of Received Error Messages
I. Entity Name
TRE73
II. Description
It is the count of received Continue_Error or End_Error messages.
It is measured when the MSC Server/SSP receives the message TC-CONTINUE

RETURN ERROR. See point A in the following figure.
11-30
SCP MSC Server/SSP

TC-BEGIN
IDP
TC-CONTINUE
RETURN ERROR
IV. Formula
None
11.2.30 Count of Sent Error Messages
I. Entity Name
TSE73
II. Description
It is the count of sent Error messages.
It is measured when the SSP sends the Error message after receiving Connect To
Resource in idle state. See point A in the following figure.
11-31
SCP MSC Server/SSP
ConnectToResourse
Return ERROR
IV. Formula
None
11.2.31 Count of Sent TC_ABORT Messages
I. Entity Name
TSTA73
II. Description
It is the count of sent TC-U-Abort messages.
It is measured when the MSC Server/SSP sends the message TC-U-Abort. See point A
in the following figure. The MSC Server/SSP waits for the SCP command after
reporting the IDP message, and sends the message TC-U-Abort due to timeout in
waiting for the command that is not sent from the SCP.
11-32
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-U-Abort
IV. Formula
None
11.2.32 Count of Received TC_ABORT Messages
I. Entity Name
TRTA73
II. Description
It is the count of received TC_Abort messages.
It is measured when the MSC Server/SSP receives the message TC_Abort. See point
11-33
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-Abort
IV. Formula
None
11.2.33 Count of Continue With Argument Messages
I. Entity Name
CON73
II. Description
It is the count of received Continue With Argument messages.
It is measured when the MSC Server/SSP receives the message Continue With
Argument. See point A in the following figure.
11-34
SCP MSC Server/SSP
IDP
ContinueWithArgument
IV. Formula
None
11.2.34 Count of Connect SMS Messages
I. Entity Name
SMSC73
II. Description
It is the count of received Connect SMS messages.
It is measured when the MSC Server/SSP receives the message Connect SMS. See
11-35
SCP MSC Server/SSP
InitialDPSMS
ConnectSMS
IV. Formula
None
11.2.35 Count of Continue SMS Messages
I. Entity Name
SMST73
II. Description
It is the count of received Continue SMS messages.
It is measured when the MSC Server/SSP receives the message Continue SMS. See
point D in the following figure.
11-36
SCP MSC Server/SSP
InitialDPSMS
A
RequestReportSMSEvent
FurnishChargingInformation B
SMS
C
ContinueSMS
D
EventReportSMS
E
ReleaseSMS
F
IV. Formula
None
11.2.36 Count of Event Report SMS Messages
I. Entity Name
SMSE73
II. Description
It is the count of sent Event Report SMS messages.
It is measured when the MSC Server/SSP receives the message Event Report SMS.
See point E in the following figure.
11-37
SCP MSC Server/SSP
InitialDPSMS
A
SMS
C
ContinueSMS
D
EventReportSMS
E
ReleaseSMS
F
IV. Formula
None
11.2.37 Count of Furnish Charging Information SMS Messages
I. Entity Name
SMSB73
II. Description
It is the count of received Furnish Charging Information SMS messages.
It is measured when the MSC Server/SSP receives the message Furnish Charging
Information SMS. See point C in the following figure.
11-38
SCP MSC Server/SSP
InitialDPSMS
A
SMS
C
ContinueSMS
D
EventReportSMS
E
ReleaseSMS
F
IV. Formula
None
11.2.38 Count of Initial DP SMS Messages
I. Entity Name
SMSDP73
II. Description
It is the count of sent Initial DP SMS messages.
It is measured when the MSC Server/SSP sends the message Initial DP SMS. See
11-39
SCP MSC Server/SSP
InitialDPSMS
A
SMS
C
ContinueSMS
D
EventReportSMS
E
ReleaseSMS
F
IV. Formula
None
11.2.39 Count of Release SMS Messages
I. Entity Name
SMSRE73
II. Description
It is the count of received Release SMS messages.
It is measured when the MSC Server/SSP receives the message Release SMS. See
point F in the following figure
11-40
SCP MSC Server/SSP
InitialDPSMS
A
SMS
C
ContinueSMS
D
EventReportSMS
E
ReleaseSMS
F
IV. Formula
None
11.2.40 Count of Request Report SMS Event Messages
I. Entity Name
RPSMS73
II. Description
It is the count of received Request Report SMS Event messages.
It is measured when the MSC Server/SSP receives the message Request Report SMS
Event. See point B in the following figure.
11-41
SCP MSC Server/SSP
InitialDPSMS
A
SMS
C
ContinueSMS
D
ReleaseSMS
EventReportSMS E
IV. Formula
None
11.2.41 Count of Reset Timer SMS Messages
I. Entity Name
SMSRS73
II. Description
It is the count of received Reset Timer SMS messages.
It is measured when the MSC Server/SSP receives the message Reset Timer SMS.
11-42
SCP MSC Server/SSP
InitialDPSMS
ResetTimerSMS
IV. Formula
None
11.2.42 Count of ICA Messages
I. Entity Name
ICA73
II. Description
It is the count of received ICA messages.
It is measured when the MSC Server/SSP receives the ICA message. See point A in
11-43
SCP MSC/SSP
ICA
IV. Formula
None
11.2.43 Count of Provide Avail DN Messages (Received)
I. Entity Name
RPDN73
II. Description
It is the count of received Provide Avail DN messages.
It is measured when the MSC Server/SSP receives the message Provide Avail DN.
11-44
SCP MSC/SSP
ProvideAvailDN
IV. Formula
None
11.2.44 Count of Provide Avail DN Messages (Sent)
I. Entity Name
SPDN73
II. Description
It is the count of sent Provide Avail DN messages.
It is measured when the MSC Server/SSP sends the message Provide Avail DN. See
11-45
SCP MSC/SSP
ProvideAvailDN
IV. Formula
None
11.2.45 Count of Port Connected Messages (Received)
I. Entity Name
RCOP73
II. Description
It is the count of received Port Connected messages.
It is measured when the MSC Server/SSP receives the message Port Connected. See
11-46
SCP MSC/SSP
PortConnected
IV. Formula
None
11.2.46 Count of Port Connected Messages (Sent)
I. Entity Name
SCOP73
II. Description
It is the count of sent Port Connected messages.
It is measured when the MSC Server/SSP sends the message Port Connected. See
11-47
SCP MSC/SSP
PortConnected
IV. Formula
None
11.2.47 Count of Bridge Ports Messages (Received)
I. Entity Name
RBP73
II. Description
It is the count of received Bridge Ports messages.
It is measured when the MSC Server/SSP receives the message Bridge Ports. See
11-48
SCP MSC/SSP
BridgePorts
IV. Formula
None
11.2.48 Count of Bridge Ports Messages
I. Entity Name
SBP73
II. Description
It is the count of sent Bridge Ports messages.
It is measured when the MSC Server/SSP sends the message Bridge Ports. See point
11-49
SCP MSC/SSP
BridgePorts
IV. Formula
None
11.3 Initial Call Attempts

11.3.1 Overview of MS_IN_ICA
Name Description
ICAAT Count of ICA call attempts
ICAALT Count of ICA call alertings
ICAANT Count of ICA call answers
ICASETR ICA call seizure traffic
ICAALTR ICA call alerting traffic
ICAANTR ICA call answer traffic
ICAALR ICA call alerting rate
ICAANR ICA call answer rate

ICADNT Count of ICA DNs
ICADNFT Count of ICA DN failures
ICABRT Count of received Bridge Ports

ICABRFT Count of SSP Bridge Port failures
11-50
11.3.2 Count of ICA Call Attempts
I. Entity Name
ICAAT
II. Description
It is the count of ICA call attempts.
It is measured when the MSC receives the ICA message from the SCP. See point A in
SCP MSC Server/SSP HLR MSC Server
USSD Req
USSD Res
ICA
RRBE(DP7_R) A
Contiune
Contiune
SRI
PRN
PRN ACK PRN ACK
IAM
ACM
B ANM
C
IV. Formula
None
11.3.3 Count of ICA Call Alertings
I. Entity Name
ICAALT
II. Description
It is the count of ICA call alertings.
z If the callee is in another office, it is measured when the MSC receives the ACM
from the callee.
z If the callee is a local MS, it is measured when the MSC receives the message MT
DTAP Alerting from the callee. See point B in the following figure.
11-51
USSD Req
USSD Res
ICA
RRBE(DP7_R) A
Contiune
Contiune
SRI
PRN
PRN ACK PRN ACK
IAM
ACM
B ANM
C
IV. Formula
None
11.3.4 Count of ICA Call Answers
I. Entity Name
ICAANT
II. Description
It is the count of answers to ICA calls.
from the callee.
z If the callee is a local MS, it is measured when the MSC receives the message
DTAP connect from the callee.
11-52
USSD Req
USSD Res
ICA
RRBE(DP7_R) A
Contiune
Contiune
SRI
PRN
PRN ACK PRN ACK
IAM
ACM
B ANM
C
IV. Formula
None
11.3.5 ICA Call Seizure Traffic
I. Entity Name
ICASETR
II. Description
It is the traffic beginning from ICA call attempts to the end of the calls.
It is measured from the time when the MSC receives the ICA message from the SCP to
the time when the MSC sends the REL message.
IV. Formula
None
11.3.6 ICA Call Alerting Traffic
I. Entity Name
ICAALTR
II. Description
It is the traffic from the time when ICA calls are connected to the end of the calls.
z For outgoing calls, it is measured from the time when the MSC receives the ACM
to the time when the MSC sends the REL message
11-53
z For incoming calls, it is measured from the time when the MSC receives the
message MT DTAP Alerting to the time when the MSC sends the REL message.
IV. Formula
None
11.3.7 ICA Call Answer Traffic
I. Entity Name
ICAANTR
II. Description
It is the traffic from the time when callees answer ICA calls to the end of the calls.
z For outgoing calls, it is measured from the time when the MSC receives the ANM
to the time when the MSC sends the REL message.
z For incoming calls, it is measured from the time when the MSC receives the
message MT DTAP connect to the time when the MSC sends the REL message.
IV. Formula
None
11.3.8 ICA Call Alerting Rate
I. Entity Name
ICAALR
II. Description
It is the rate between ICA call alertings and ICA call attempts.
Count of call alertings/Call attempts
IV. Formula
ICAALR = ICAALT/ICAAT
11.3.9 ICA Call Answer Rate
I. Entity Name
ICAANR
11-54
II. Description
It is the rate between ICA call answers and ICA call attempts.
Count of answers/Count of call attempts
IV. Formula
ICAANR = ICAANT/ICAAT
11.3.10 Count of ICA DNs
I. Entity Name
ICADNT
II. Description
It is the count of DNs allocated by the SSP during UCB call.
It is measured when the MSC Server/SSP sends the message Avail DN Provided to the

USSD Req
USSD Req
USSD Res
ICA USSD Res
RRBE(DP7_R)
SRI
PRN
PRN ACK PRN ACK
IAM
ACM
ProvideAvailDN ANM
AvailDNProvided
A
IV. Formula
None
11.3.11 Count of ICA DN Failures
I. Entity Name
ICADNFT
11-55
II. Description
It is the count of DNs that fail to be allocated by the SSP during UCB calls.
It is measured when the SSP successfully allocates DNs during the UCB calls.
IV. Formula
None
11.3.12 Count of Received Bridge Ports
I. Entity Name
ICABRT
II. Description
It is the count of received Bridge Ports messages.
It is measured when the MSC Server/SSP sends the message Port Bridged to the SCP.
SCP MSC Server/SSP MS
ERB(DP7) Connect
ProvideAvailDN
AvailDNProvided
BridgePorts
PortsBridged
IV. Formula
None
11-56
11.3.13 Count of SSP Bridge Ports Failures
I. Entity Name
ICABRFT
II. Description
It is the count of Error messages returned by the SSP after it receives the Bridge Ports
messages.
It is measured when the MSC Server/SSP receives the Bridge Ports message from the
SCP and returns the Error message. See point A in the following figure.
ERB(DP7) Connect
ProvideAvailDN
AvailDNProvided
BridgePorts
Return ERROR
IV. Formula
None
11.4 MAP IN Services

11.4.1 Overview of MS_TYPE_MAP_IN_SERVICE
Name Description
TRBSI74 Count of providing CAMEL subscriber information
TSPSI74 Success count of providing CAMEL subscriber information
TRCRI74 Count of sending routing information for CAMEL subscriber
11-57
11.4.2 Count of Providing CAMEL Subscriber Information
I. Entity Name
TRBSI74
II. Description
It is the count of PROVIDE_SUBSCRIBER_INFO_REQ messages sent by the HLR to

the MSC/VLR.
It is measured when the MSC/VLR receives the message

PROVIDE_SUBSCRIBER_INFO_REQ from the HLR. See point A in the following
figure.
HLR MSC Server
PROVIDE_SUBSCRIBER_INFO_REQ
PROVIDE_SUBSCRIBER_INFO_RSP
IV. Formula
None
11.4.3 Success Count of Providing CAMEL Subscriber Information
I. Entity Name
TSPSI74
II. Description
It is the count of PROVIDE_SUBSCRIBER_INFO_RSP messages sent by the

MSC/VLR to the HLR.
11-58
It is measured when the MSC/VLR sends the message

PROVIDE_SUBSCRIBER_INFO _RSP to the HLR. See point B in the following figure.
HLR MSC Server
PROVIDE_SUBSCRIBER_INFO_REQ
PROVIDE_SUBSCRIBER_INFO_RSP
IV. Formula
None
11.4.4 Count of Sending Routing Information for CAMEL Subscriber
I. Entity Name
TRCRI74
II. Description
It is the count of SEND_ROUTING_INFORMATION_REQ messages sent by the

MSC/VLR for CAMEL subscribers.
It is measured when the MSC/VLR receives the message

SEND_ROUTING_INFORMATION_RSP that contains camelRoutingInfo. See point B
11-59
HLR MSC Server
IV. Formula
None
11.5 SSF Calls

11.5.1 Overview of MS_TYPE_SSF_CALL_TRAF
Name Description
OSIC84 Count of SSF call outs
ISIC84 Count of SSF call ins
11.5.2 Count of SSF Call Outs
I. Entity Name
OSIC84
II. Description
It is the count of IN calls sent from the SSF to all SCFs.
It is measured when the SSP sends the message Initial DP (DP2) to the SCP. See point
11-60
SCP MSC Server/SSP
InitialDP(DP2)
IV. Formula
None
11.5.3 Count of SSF Call Ins
I. Entity Name
ISIC84
II. Description
It is the count of IN calls received by the SSF in a data collection period.
It is measured when the SSP receives the ICA message from the SCP. See point A in
11-61
SCP MSC Server/SSP HLR
USSD Req
USSD Res
ICA
IV. Formula
None
11.6 Fixed Subscriber Calling IN Subscriber

11.6.1 Overview of MS_TYPE_IN_INC_TRAF
Name Description
LCNAN65 Attempt count of fixed subscriber calling IN subscriber
LIACN66 Connect count of fixed subscriber calling IN subscriber
LICCN66 Answer count of fixed subscriber calling IN subscriber
Abandon before alerting count of fixed subscriber calling IN
LIACKN66
subscriber
Abandon after alerting count of fixed subscriber calling IN
LIUERN66
subscriber
LILCNA66 Callee busy count of fixed subscriber calling IN subscriber
LIRERN66 No answer count of fixed subscriber calling IN subscriber

Callee Determined Busy count of fixed subscriber calling IN
LIMCRBN66
subscriber
LISTRF66 Seizure traffic of fixed subscriber calling IN subscriber
LICCT66 Connected traffic of fixed subscriber calling IN subscriber
LIACKT66 Answer traffic of fixed subscriber calling IN subscriber
11-62
11.6.2 Attempt Count of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LCNAN65
II. Description
It is the count of incoming call attempts initiated by fixed subscribers to CAMEL

subscribers. A call attempt is generated if the callee is judged as the local CAMEL
subscriber.
It is measured after the MSC analyzes a callee number.

z If the callee is in another office, see point A in the following figure.
z If the callee is a local mobile subscriber, see point D in the following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM/ANC C
IAM
D
DTAP SETUP
DTAP ALERTING
ACM E
DTAP CONNECT
ANM/ANC F
IV. Formula
None
11.6.3 Connect Count of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LIACN66
11-63
II. Description
It is the count of Alerting messages when fixed subscribers call local CAMEL
subscribers.
It is measured when the MSC receives the message DTAP Alerting from a CAMEL
subscriber and returns the ACM to the originating office.
z If the callee is in another office, see point B in the following figure.
z If the callee is a local mobile subscriber, see point E in the following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM/ANC C
IAM
D
DTAP SETUP
DTAP ALERTING
ACM E
DTAP CONNECT
ANM/ANC F
IV. Formula
None
11.6.4 Answer Count of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LICCN66
II. Description
It is the count of calls answered by local CAMEL subscribers when the callers are fixed
subscribers
11-64
It is measured when the MSC receives the message DTAP Connect from a CAMEL
subscriber and returns message ANC or ANM to the originating office.
z If the callee is in another office, see point C in the following figure.
z If the callee is a local mobile subscriber, see point F in the following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM/ANC C
IAM
D
DTAP SETUP
DTAP ALERTING
ACM E
DTAP CONNECT
ANM/ANC F
IV. Formula
None
11.6.5 Abandon Before Alerting Count of Fixed Subscriber Calling IN

Subscriber
I. Entity Name
LIACKN66
II. Description
It is the count of messages indicating abandon before alerting when fixed subscribers
call local CAMEL subscribers.
11-65
It is measured when the MSC receives the REL message from the originating office
before a call is connected.
z If the callee is a local mobile subscriber, see point B in the following figure.

IAM
REL
A
ACM
RNC/BSC
IAM
REL
B
DTAP ALERTING
IV. Formula
None
11.6.6 Abandon After Alerting Count of Fixed Subscriber Calling IN

Subscriber
I. Entity Name
LIUERN66
II. Description
It is the count of messages indicating abandon after alerting when fixed subscribers call
local CAMEL subscribers.
11-66
It is measured when the MSC sends the ring-back tone to a fixed caller after receiving
the DTAP Alerting message from a CAMEL subscriber, and receives the REL message
from the originating office before receiving the message DTAP Connect from the
CAMEL subscriber.
IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
REL
B
DTAP CONNECT
IV. Formula
None
11.6.7 Callee Busy Count of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LILCNA66
II. Description
It is the count of messages indicating the callee is busy when fixed subscribers call
local CAMEL subscribers.
11-67
It is measured when the MSC receives an MSRN from the HLR and sends the
message Send info for i/o call setup to the VLR, which returns the message indicating
the callee (without registering CF service) is busy. Or it is measured when the MSC
receives the message CV_ST_BUSY/CV_SL_BUSY/CV_BUSY after sending the IAM
to the peer office.

IAM
IAM
A
ACM RNC/BSC
IAM
DTAP PAGING
B
DTAP ALERTING
IV. Formula
None
11.6.8 No Answer Count of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LIRERN66
II. Description
It is the count of calls released due to timeout and made by fixed subscribers to local
CAMEL subscribers, who do not pick up the ringing phone.
11-68

IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.6.9 Callee Determined Busy Count of Fixed Subscriber Calling IN

Subscriber
I. Entity Name
LIMCRBN66
II. Description
It is the count of calls rejected by callees after hearing the ringing tone when fixed
subscribers call local CAMEL subscribers.
11-69
It is measured when the MSC receives the message DTAP DISCONNECT from a
mobile terminating subscriber before the callee picks up the ringing phone. The cause
values are user busy and all rejected.
IAM
IAM
ACM
ACM
RNC/BSC
A
ANM/ANC
IAM
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
ACM
B
DTAP CONNECT
IV. Formula
None
11.6.10 Seizure Traffic of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LISTRF66
II. Description
For calls made by fixed subscribers to local CAMEL subscribers, it is the traffic from the
time when the MSC confirms that the calls are incoming calls and callees are CAMEL
subscribers to the time when the calls are released.
11-70
It is measured when the MSC connects a call internally and confirms the call attributes.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM/ANC C
IAM
D
DTAP SETUP
DTAP ALERTING
ACM E
DTAP CONNECT
ANM/ANC F
IV. Formula
None
11.6.11 Connected Traffic of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LICCT66
II. Description
time when calls are connected to the time when the calls are released.
It is measured when the MSC sends the ACM to the peer office.
11-71

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM/ANC C
IAM
D
DTAP SETUP
DTAP ALERTING
ACM E
DTAP CONNECT
ANM/ANC F
IV. Formula
None
11.6.12 Answer Traffic of Fixed Subscriber Calling IN Subscriber
I. Entity Name
LIACKT66
II. Description
time when callees answer the calls to the time when calls are released.
It is measured when the MSC receives the message DTAP Connect from a CAMEL
subscriber and returns the message ANC or ANM to the originating office.
11-72

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM/ANC C
IAM
D
DTAP SETUP
DTAP ALERTING
ACM E
DTAP CONNECT
ANM/ANC F
IV. Formula
None
11.7 Mobile Subscriber Calling IN Subscriber

11.7.1 Overview of MS_TYPE_IN_MT_INT_TRAF
Name Description
MIATC68 Attempt count of mobile subscriber calling IN subscriber
MICCN68 Connect count of mobile subscriber calling IN subscriber
MIACKN68 Answer count of mobile subscriber calling IN subscriber
Abandon before alerting count of mobile subscriber calling IN
MIUER68
subscriber
Abandon after alerting count of mobile subscriber calling IN
MIRER68
subscriber
MICB68 Callee busy count of mobile subscriber calling IN subscriber
MILCNA68 No answer count of mobile subscriber calling IN subscriber
Callee determined busy count of mobile subscriber calling IN
MIMCRBN67
subscriber
11-73
Name Description
MISTRF68 Seizure traffic of mobile subscriber calling IN subscriber
MICCT68 Connected traffic of mobile subscriber calling IN subscriber
MIACKT68 Answer traffic of mobile subscriber calling IN subscriber
11.7.2 Attempt Count of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MIATC68
II. Description
It is the count of intra-office call attempts initiated by mobile subscribers. A call attempt
is generated if the callee is judged as a local CAMEL subscriber.
It is measured after the MSC analyzes a callee number.

11-74

DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
RNC/BSC
DTAP CONNECT C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.7.3 Connect Count of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MICCN68
II. Description
It is the count of Alerting messages when mobile subscribers call local CAMEL
subscribers.
It is measured when the MSC receives the message DTAP Alerting from a CAMEL
subscriber and sends the message DTAP Alerting to a mobile caller.
11-75

DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
RNC/BSC
DTAP CONNECT C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.7.4 Answer Count of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MIACKN68
II. Description
It is the count of answered calls when mobile subscribers call local CAMEL subscribers.
It is measured when the MSC sends the message DTAP Connect to a mobile caller
after receiving it from a CAMEL subscriber, and receives the message DTAP Connect
Ack from the mobile caller.
11-76

DTAP SETUP
A
IAM
ACM
DTAP ALERTING B
ANM/ANC
RNC/BSC
DTAP CONNECT C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.7.5 Abandon Before Alerting Count of Mobile Subscriber Calling IN

Subscriber
I. Entity Name
MIUER68
II. Description
It is the count of messages indicating abandon before alerting when mobile subscribers
It is measured when the MSC receives the message DTAP Disconnect from the mobile
caller before a call is connected.
11-77

DTAP SETUP
DTAP DISCONNECT
A
RNC/BSC
ACM
DTAP SETUP
DTAP DISCONNECT
B
DTAP ALERTING
IV. Formula
None
11.7.6 Abandon After Alerting Count of Mobile Subscriber Calling IN

Subscriber
I. Entity Name
MIRER68
II. Description
It is the count of messages indicating abandon after alerting when mobile subscribers
It is measured when the MSC sends the ring-back tone to a mobile caller after receiving
the DTAP Alerting message from a CAMEL subscriber, and receives the message
DTAP Disconnect from the mobile caller before receiving the message DTAP Connect
from the CAMEL subscriber.
11-78
DTAP SETUP
IAM
ACM
DTAP ALERTING
DTAP DISCONNECT
RNC/BSC
A
ANM/ANC
DTAP SETUP
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.7.7 Callee Busy Count of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MICB68
II. Description
It is the count of messages indicating that the callee is busy when mobile subscribers
It is measured when the MSC obtains an MSRN from the HLR and sends the message
Send info for i/o call setup to the VLR, which returns a message indicating that the
callee (no CF service) is busy.
11-79

DTAP SETUP
IAM
A
ACM RNC/BSC
DTAP SETUP
DTAP PAGING
DTAP ALERTING
IV. Formula
None
11.7.8 No Answer Count of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MILCNA68
II. Description
It is the count of calls released due to timeout and made by fixed subscribers to local
CAMEL subscribers, who do not pick up the ringing phone.
It is measured when the MSC processes a call due to ringing timeout.

11-80
DTAP SETUP
IAM
ACM
DTAP ALERTING
REL
RNC/BSC
A
ANM/ANC
DTAP SETUP
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.7.9 Callee Determined Busy Count of Mobile Subscriber Calling IN

Subscriber
I. Entity Name
MIMCRBN67
II. Description
It is the count of calls rejected by callees after hearing the ringing tone when mobile
subscribers call local CAMEL subscribers.
mobile terminating subscriber before the callee picks up the ringing phone. The cause
values are user busy and all rejected.
11-81
DTAP SETUP
IAM
ACM
DTAP ALERTING
RNC/BSC
A
ANM/ANC
DTAP SETUP
DTAP PAGING_RSP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
B
DTAP CONNECT
IV. Formula
None
11.7.10 Seizure Traffic of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MISTRF68
II. Description
If mobile subscribers call local CAMEL subscribers, it is the traffic from the time when
the MSC confirms that the callees are local CAMEL subscribers to the time when the
calls are released.
IV. Formula
None
11-82
11.7.11 Connected Traffic of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MICCT68
II. Description
calls are connected to the time when the calls are released.
It is measured when the MSC sends the message DTAP Alerting to a mobile caller.
IV. Formula
None
11.7.12 Answer Traffic of Mobile Subscriber Calling IN Subscriber
I. Entity Name
MIACKT68
II. Description
callees answer calls to the time when the calls are released.
It is measured when the MSC sends the message DTAP Connect to a mobile caller,
and receives DTAP Connect Ack.
IV. Formula
None
11.8 IN Components
11.8.1 Overview of MS_TYPE_IN_COMPOMENT
Name Description
TGSTO69 Sent INVOKE
TGSRO69 Received INVOKE

TGSTRNO69 Count of RESULTs that cannot be coded
TGSRRNO69 Count of RESULTs that cannot be decoded
11-83
Name Description
TGSTRO69 Count of sent TC_REJECT messages
TGSMR69 Count of received TC_REJECT messages
11.8.2 Sent INVOKE
I. Entity Name
TGSTO69
II. Description
It is the count of INVOKE messages sent from the SSP to the SCP.
It is measured when the SSP sends the message containing TC_INVOKE to the SCP,
such as Initialdp, EventReportBCSM or ApplychargeReport. The messages with
TC_RESULT are not included, like PCResult. See points A, D and E in the following
figure.
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-CONTINUE A
SMEvent)
TC-CONTINUE B
INVOKE(ApplyCharging)
INVOKE(EventReportBCSM) C
TC-CONTINUE
INVOKE(ApplyChargingReport)
TC-CONTINUE D
IV. Formula
None
11.8.3 Received INVOKE
I. Entity Name
TGSRO69
11-84
II. Description
It is the count of INVOKE messages received by the SSP from the SCP.
It is measured when the SCP sends to the SSP the message ConnectToResource, PA,
PC, RequestReportBCSMEvent, Connect, Applycharging or ReleaseCall. See points B
and C in the following figure.
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-CONTINUE A
SMEvent)
TC-CONTINUE B
INVOKE(EventReportBCSM) C
TC-CONTINUE
TC-CONTINUE D
IV. Formula
None
11.8.4 Count of RESULTs that Cannot be Coded
I. Entity Name
TGSTRNO69
II. Description
It is the count of failures in sending messages from the SSP to the SCP, that is, the
count of Error messages when the SSP sends the results (including results of
messages PC and ActiveTest currently).
It is measured when:
z The PCResult sent from the SSF (SRM) to the FEAM is abnormal in length.
z Or dlgid of PCResult is larger than MAXDIALOG
z Or callinstance of dlg in the FEAM is different from the one stored in the PCResult.
11-85
InitialDP
RequestReportBCSM
Event
ConnectToResource
Information
START_DTMF
RETURN ERROR
A
IV. Formula
None
11.8.5 Count of RESULTs that Cannot be Decoded
I. Entity Name
TGSRRNO69
II. Description
It is the count of RESULT messages when the SSP receives incorrect messages from
the SCP.
It is measured when the SSP returns the Error message after receiving the RESULT
message. As there is no RESULT message from the SCP to the SSP in the current
service, the measurement result of this entity is 0, that is, no result is measured.
IV. Formula
None
11.8.6 Count of Sent TC_REJECT Messages
I. Entity Name
TGSTRO69
II. Description
It is the count of TC_REJECT messages sent by the SSP to the SCP.
11-86
The CAP message sent from the SCP to the SSP includes:
z establishTemporaryConnection
z disconnectForwardConnection
z connectToResource
z connect
z releaseCall
z requestReportBCSMEvent
z collectInformation
z continue
z continueWithArgument
For example, it is measured when the SSP rejects the second AC from the SCP before
the SSP responds to the first AC with the ACR. See point A in the following figure.
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-CONTINUE
SMEvent)
TC-CONTINUE
TC-CONTINUE
INVOKE(Reject)
TC-CONTINUE
IV. Formula
None
11.8.7 Count of Received TC_REJECT Messages
I. Entity Name
TGSMR69
II. Description
It is the count of TC_REJECT messages received by the SSP from the SCP.
11-87
It is measured when the SSP receives the message TC_U_REJECT, TC_R_REJECT

or TC_L_REJECT. For example, it is measured when the SCP returns the message
TC-END INVOKE (reject) after receiving the incorrect IDP message from the SSP. See
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-END
INVOKE(reject)
IV. Formula
None
11.9 IN Dialogue
11.9.1 Overview of MS_IN_DIALOGUE_TRAF
Name Description
SDLG Count of sessions sent by SSF
RDLG Count of sessions received by SSF
SABDLG Count of sessions U-Abort sent by SSP
RABDLG Count of sessions P-Abort and U-Abort sent by SSP
TLDLGT Call duration between received TC-BEGIN and TC-END

TLDLG Total count of sessions
AVDLGT Count of sessions sent by SSP and SCP
11-88
11.9.2 Count of Sessions Sent by SSF
I. Entity Name
SDLG
II. Description
It is the count of sessions originated from the SSP.
It is measured when the SSP sends the message TC_BEGIN to the SCP. See point A in
SCP MSC Server/SSP

INVOKE(InitialDP)
TC-BEGIN
TC-CONTINUE A
SMEvent)
TC-CONTINUE
INVOKE(EventReportBCSM)
TC-CONTINUE
TC-CONTINUE
IV. Formula
None
11.9.3 Count of Sessions Received by SSF
I. Entity Name
RDLG
II. Description
It is the count of sessions originated from the SCP.
It is measured when the MSC Server/SSP receives the message TC_BEGIN. See point
11-89
SCP MSC Server/SSP
TC-BEGIN-IND
A
TC-CONTINUE-REQ
INVOKE(InitiateCallAttempt)
IV. Formula
None
11.9.4 Count of Sessions U-Abort Sent by SSP
I. Entity Name
SABDLG
II. Description
It is the count of aborted sessions after the SSP sends the message TC-U-ABORT.
It is measured when the SSP sends the message TC-U-ABORT. See point A in the
following figure. After the MSC Server/SSP sends the IDP message, the SCP does not
respond, and the SSP sends the message TC-U-ABORT to the SCP due to timeout.
11-90
SCP MSC Server/SSP
IDP
TC-U-ABORT
IV. Formula
None
11.9.5 Count of Sessions P-Abort and U-Abort Sent by SSP
I. Entity Name
RABDLG
II. Description
It is the count of TC-P-ABORT and TC-U-ABORT messages sent by the SCP to the
SSP.
It is measured when the SSP receives from the SCP the messages TC-P-ABORT and
TC-U-ABORT. See point A in the following figure.
11-91
SCP MSC Server/SSP
IDP
TC-P-ABORT
IV. Formula
None
11.9.6 Call Duration Between Received TC-BEGIN and TC-END
I. Entity Name
TLDLGT
II. Description
It is the duration from the time when the FEAM receives the message TC-BEGIN to the
time when the FEAM receives the message TC-END or TC-U-ABORT during a call.
It is measured from the time when the SSP receives the message TC_BEGIN to the
end of the session.
IV. Formula
None
11.9.7 Total Count of Sessions
I. Entity Name
TLDLG
II. Description
It is the total count of sessions originated from the SSP and received by the SSP.
11-92
Count of sessions originated from the SSP + Count of sessions received by the SSP
IV. Formula
None
11.9.8 Average Duration of Sessions
I. Entity Name
AVDLGT
II. Description
It is the average duration of sessions.
Duration of all sessions / Total count of sessions
IV. Formula
None
11.10 IN Calls of All Subscribers Calling Operator

11.10.1 Overview of MS_TYPE_IN_OPERATOR_TRAF
Name Description
ACN81 Attempt count of IN subscriber calling operator
CTN81 Connect count of IN subscriber calling operator
ACKN81 Answer count of IN subscriber calling operator
UERN81 Abandon before alerting count of IN subscriber calling operator
RERN81 Abandon after alerting count of IN subscriber calling operator
CBN81 Callee busy count of IN subscriber calling operator

LCNAN81 No answer count of IN subscriber calling operator
MCRBN81 Callee determined busy count of IN subscriber calling operator
STRF81 Seizure traffic of IN subscriber calling operator
PTTRF81 Connect traffic of IN subscriber calling operator
ACKTRF81 Answer traffic of IN subscriber calling operator
11-93
11.10.2 Attempt Count of IN Subscriber Calling Operator
I. Entity Name
ACN81
II. Description
It is the count of call attempts made by CAMEL subscribers.
It is measured after the MSC triggers the IN service for a caller and completes number
analysis.
z If the callee is in another office, see points A and D in the following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
z If the callee is a local mobile subscriber, see points A and D in the following figure.
11-94

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.10.3 Connect Count of IN Subscriber Calling Operator
I. Entity Name
CTN81
II. Description
It is the count of Alerting messages when CAMEL subscribers make calls.
from the callee. See points B and E in the following figure.
11-95

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
z If the callee is in the local office, it is measured when the MSC receives the
message DTAP Alerting from the callee. See points B and E in the following figure.
11-96

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.10.4 Answer Count of IN Subscriber Calling Operator
I. Entity Name
ACKN81
II. Description
It is the count of answers to calls made by CAMEL subscribers.
z If the callee is in another office, it is measured when the MSC receives the ANM
from the callee. See points C and F in the following figure.
11-97

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
message DTAP Connect from the callee. See points C and F in the following
figure.
11-98

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.10.5 Abandon Before Alerting Count of IN Subscriber Calling Operator
I. Entity Name
UERN81
II. Description
It is the count of messages indicating abandon before alerting sent by CAMEL callers
after success in routing.
It is measured when the MSC receives the message DTAP Disconnect from the caller
before a call is connected.
In the case that the callee is in another office:
z If the caller makes an incoming call, see point A in the following figure.
z If the caller is a mobile subscriber, see point B in the following figure.
11-99

IAM
REL
A
RNC/BSC
ACM
DTAP SETUP
DTAP DISCONNECT
B
ACM
In the case that the callee is in a terminating office:

11-100

IAM
REL
A
RNC/BSC DTAP ALERTING
DTAP SETUP
DTAP DISCONNECT
B
DTAP ALERTING
IV. Formula
None
11.10.6 Abandon After Alerting Count of IN Subscriber Calling Operator
I. Entity Name
RERN81
II. Description
It is the count of messages indicating abandon after alerting sent from CAMEL
subscribers.
It is measured when the MSC receives the message DTAP Disconnect from a caller
before the callee answers the connected call.
In the case that the callee is in another office:
11-101
IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
DTAP DISCONNECT
B
ANM/ANC
In the case that the callee is in a terminating office:

11-102
IAM
DTAP SETUP
DTAP ALERTING
ACM
ANM/ANC
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.10.7 Callee Busy Count of IN Subscriber Calling Operator
I. Entity Name
CBN81
II. Description
It is the count of messages indicating that the callee is busy when CAMEL subscribers
call the callees.
z If the callee is in another office, it is measured when the MSC receives the
message STB or SLB from the peer TUP, or the REL message from the ISUP due
to Callee busy. See points A and B in the following figure.
11-103

IAM
IAM
A
RNC/BSC ACM
DTAP SETUP
IAM
ACM
z If the callee is a local mobile subscriber, it is measured when the MSC receives the
MSRN from the HLR and sends the message Send info for i/o call setup to the
VLR, which returns a message indicating that the callee (no CF service) is busy.
See points A and B in the following figure.
11-104

IAM
DTAP SETUP
A
DTAP SETUP
DTAP SETUP
DTAP ALERTING
IV. Formula
None
11.10.8 No Answer Count of IN Subscriber Calling Operator
I. Entity Name
LCNAN81
II. Description
It is the count of messages indicating calls are not answered when CAMEL subscribers
make calls.
z It is measured when the MSC releases a call due to timeout in waiting for the
Answer message from the callee after receiving the ACM (DTAP Connect).It is
measured when the MSC receives the REL message from the callee after
receiving the ACM (DTAP Connect), and the cause value is 146
(CV_NO_RESPOND) or 147 (CV_NO_ACKNOWLEGE).
IV. Formula
None
11-105
11.10.9 Callee Determined Busy Count of IN Subscriber Calling Operator
I. Entity Name
MCRBN81
II. Description
It is the count of messages indicating callees determine to be busy when CAMEL

subscribers make calls.
mobile terminating subscriber due to callee determined busy before the callee picks up
the ringing phone.
z If the callee is in another office, see points A and B in the following figure.
DTAP SETUP
IAM
ACM
DTAP ALERTING
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
B
ANM/ANC
z If the callee is a local mobile subscriber, see points A and B in the following figure.
11-106
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
B
DTAP CONNECT
IV. Formula
None
11.10.10 Seizure Traffic of IN Subscriber Calling Operator
I. Entity Name
STRF81
II. Description
It is the traffic of call attempts made by CAMEL subscribers.
It is measured after the MSC triggers the IN service for a caller and completes number
analysis.
IV. Formula
None
11-107
11.10.11 Connect Traffic of IN Subscriber Calling Operator
I. Entity Name
PTTRF81
II. Description
It is the traffic generated when calls made by CAMEL subscribers are connected.
from the callee;
message DTAP Alerting from the callee.
IV. Formula
None
11.10.12 Answer Traffic of IN Subscriber Calling Operator
I. Entity Name
ACKTRF81
II. Description
It is the traffic generated when the calls made by CAMEL subscribers are answered.
z If the callee is in another office, it is measured when the MSC receives the ANM
from the callee
message DTAP Connect from the callee.
IV. Formula
None
11-108
11.11 IN Failures
11.11.1 Overview of MS_IN_FAILURE_TRAF
Name Description
OVLDREJ Count of overload rejected calls
FBINI Count of call failures before initialization
FAINI Count of call failures after initialization

SSFRREJ Count of sessions reject received by SSF
11.11.2 Count of Overload Rejected Calls
I. Entity Name
OVLDREJ
II. Description
It is the count of rejected calls due to overload.
It is measured when the IDP request message is rejected due to CALLGAP.
IV. Formula
None
11.11.3 Count of Call Failures Before Initialization
I. Entity Name
FBINI
II. Description
It is the count of call failures before the SSP sends the Initial DP message.
It is measured when the Dialogue ID messages fail to be allocated before the SSP
sends the Initial DP message.
IV. Formula
None
11-109
11.11.4 Count of Call Failures After Initialization
I. Entity Name
FAINI
II. Description
It is the count of call failures after the SSP sends the Initial DP message.
It is measured when errors occur to the IN module after the FEAM sends messages to
the SSF, that is, ssf_ssn is larger than MAX_SSF_SSN and dlgid equals
NULL_DIALOGUE, the message is empty or the message type is wrong (the message
is not the type between the FEAM and SSF).
IV. Formula
None
11.11.5 Count of Sessions Reject Received by SSF
I. Entity Name
SSFRREJ
II. Description
It is the count of received Reject messages.
It is measured when the SSF receives the Reject message. See point A in the following
figure.
11-110
SCP MSC Server/SSP
InitialDP(TDP2)
Reject
IV. Formula
None
11.12 IN Events
Name Description
SICS83 Originating IN call initiates (DP2)
SRCF83 Originating route selection fails (EDP4)
SCB83 Originating callee busy (DP5)
SCNACK83 Originating callee does not answer (DP6)
SCACK83 Originating callee answers (DP7)
SDLE83 Originating release event (DP9)
SMCA83 Originating caller abandons (DP10)
TICS83 Terminating IN call initiates (DP12)

TCB83 Terminating callee busy (EDP13)
TCNACK83 Terminating callee does not answer (EDP14)
TCACK83 Terminating callee answers (DP15)

TDLE83 Terminating releases (DP17)
TMCA83 Terminating caller abandons (DP18)
OAINFO83 Terminating analyzes information (DP3)
11-111
Name Description
ORCFT83 Terminating route selection fails (TDP4)
TBT83 Terminating callee busy (TDP13)
TNAT83 Terminating callee does not answer (TDP14)
SMS83 Terminating IN SMS initiates
SMSF83 Terminating SMS fails
SMSR83 Terminating SMS submits
11.12.2 Originating IN Call Initiates (DP2)
I. Entity Name
SICS83
II. Description
It is the count of messages containing TDP2 triggered by IN calls.
It is measured when an IN call triggers the message with TDP2. See point A in the
following figure.
SCP MSC Server/SSP
InitialDP(DP2)
A
EventReportBCSM(EDP4)
IV. Formula
None
11-112
11.12.3 Originating Route Selection Fails (EDP4)
I. Entity Name
SRCF83
II. Description
It is the count of messages containing EDP4 triggered by IN calls.
It is measured when an IN call triggers the message with EDP4. See point B in the
following figure.
SCP MSC Server/SSP
InitialDP(TDP2)
A
IV. Formula
None
11.12.4 Originating Callee Busy (DP5)
I. Entity Name
SCB83
II. Description
It is the count of messages containing DP5 triggered by IN calls.
It is measured when an IN call triggers the message with DP5 because the MO callee is
busy. See point A in the following figure.
11-113
SCP MSC Server/SSP
InitialDP(TDP2)
IV. Formula
None
11.12.5 Originating Callee Does Not Answer (DP6)
I. Entity Name
SCNACK83
II. Description
It is measured when an IN call triggers the message with DP6 because the originating
callee does not answer the call. See point A in the following figure.
11-114
SCP MSC Server/SSP
InitialDP(TDP2)
IV. Formula
None
11.12.6 Originating Callee Answers (DP7)
I. Entity Name
SCACK83
II. Description
callee answers the call.
11-115

Setup
InitialDP(TDP2)
RequestReportBCSM
Event
ApplyCharging
EventReportBCSM(EDP7) Connect
IV. Formula
None
11.12.7 Originating Release Event (DP9)
I. Entity Name
SDLE83
II. Description
It is measured when an IN call triggers the message with EDP9 because the originating
caller releases the call. See point A in the following figure.
11-116

Setup
InitialDP(TDP2)
RequestReportBCSM
Event
ApplyCharging
Disconnect
IV. Formula
None
11.12.8 Originating Caller Abandons (DP10)
I. Entity Name
SMCA83
II. Description
caller releases the call. See point A in the following figure.
11-117

Setup
InitialDP(TDP2)
EventReportBCSM(EDP10) Disconnect
IV. Formula
None
11.12.9 Terminating IN Call Initiates (DP12)
I. Entity Name
TICS83
II. Description
following figure.
11-118
SCP MSC Server/SSP
InitialDP(TDP12)
A
IV. Formula
None
11.12.10 Terminating Callee Busy (EDP13)
I. Entity Name
TCB83
II. Description
It is measured when an IN call triggers the message with DP13. See point A in the
following figure.
11-119
SCP MSC Server/SSP
InitialDP(TDP12)
A
IV. Formula
None
11.12.11 Terminating Callee Does Not Answer (EDP14)
I. Entity Name
TCNACK83
II. Description
following figure.
11-120
SCP MSC Server/SSP
InitialDP(TDP12)
IV. Formula
None
11.12.12 Terminating Callee Answers (DP15)
I. Entity Name
TCACK83
II. Description
following figure.
11-121
InitialDP(TDP12)
RequestReportBCSM
Event
ApplyCharging
EventReportBCSM(EDP15) Connect
IV. Formula
None
11.12.13 Terminating Releases (DP17)
I. Entity Name
TDLE83
II. Description
following figure.
11-122
InitialDP(TDP12)
RequestReportBCSM
Event
ApplyCharging
IV. Formula
None
11.12.14 Terminating Caller Abandons (DP18)
I. Entity Name
TMCA83
II. Description
It is measured when a mobile terminating subscriber triggers the message with DP18
upon receiving the Release message from the caller during the call connection. See
11-123
SCP MSCServer /SSP MS (caller)
InitialDP(TDP12)
RequestReportBCSM
Event
ApplyCharging
IV. Formula
None
11.12.15 Terminating Analyzes Information (DP3)
I. Entity Name
OAINFO83
II. Description
It is measured when an IN call triggers the message with EDP4. See point B in the
following figure.
11-124

Setup
InitialDP(TDP3)
A
ConnectToResourse
PlayAnnouncement
IV. Formula
None
11.12.16 Originating Route Selection Fails (TDP4)
I. Entity Name
ORCFT83
II. Description
following figure.
11-125

Setup
InitialDP(TDP4)
IV. Formula
None
11.12.17 Terminating Callee Busy (TDP13)
I. Entity Name
TBT83
II. Description
following figure.
11-126
SCP MSCServer /SSP MS
Setup
InitialDP(TDP13)
IV. Formula
None
11.12.18 Terminating Callee Does Not Answer (TDP14)
I. Entity Name
TNAT83
II. Description
following figure.
11-127
SCP MSCServer /SSP MS(callee)
Setup
Alerting
InitialDP(TDP14)
IV. Formula
None
11.12.19 Originating IN SMS Initiates
I. Entity Name
SMS83
II. Description
It is the count of messages containing SMS-DP1 triggered by IN calls.
It is measured when an IN call triggers the message with SMS-DP1. See point A in the
following figure.
11-128
SCP MSC Server/SSP

TC-BEGIN
INVOKE(IDP-SMS-DP1)
A
TC-END
INVOKE(ContinueSMS)
IV. Formula
None
11.12.20 Originating SMS Fails
I. Entity Name
SMSF83
II. Description
It is measured when an IN call triggers the message with SMS-DP2 See point A in the
following figure.
11-129
SCP MSC Server/SSP
InitialDPSMS
SMS
EventReportSMS(EDP2)
IV. Formula
None
11.12.21 Originating SMS Submits
I. Entity Name
SMSR83
II. Description
It is measured when an IN call triggers the message with SMS-DP3. See point A in the
following figure.
11-130
SCP MSC Server/SSP
InitialDPSMS
SMS
EventReportSMS(EDP3)
IV. Formula
None
11.13 IN Subscriber Calling Fixed Subscriber

11.13.1 Overview of MS_TYPE_IN_ORGOUT_TRAF
Name Description
ILACN65 Attempt count of IN subscriber calling fixed subscriber
ILCCN65 Connect count of IN subscriber calling fixed subscriber
ILCCK65 Answer count of IN subscriber calling fixed subscriber
Abandon before alerting count of IN subscriber calling fixed
ILUERN65
subscriber
Abandon after alerting count of IN subscriber calling fixed
ILRERN65
subscriber
ILCBN65 Callee busy count of IN subscriber calling fixed subscriber
ILLCNAN65 No answer count of IN subscriber calling fixed subscriber

ILSTRF65 Seizure traffic of IN subscriber calling fixed subscriber
ILCCTRF65 Connected traffic of IN subscriber calling fixed subscriber
ILACKT65 Answer traffic of IN subscriber calling fixed subscriber
11-131
11.13.2 Attempt Count of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILACN65
II. Description
It is the count of outgoing calls made by CAMEL subscribers.
It is measured after the MSC analyzes the callee number. See points A and D in the
following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.13.3 Connect Count of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILCCN65
II. Description
It is the count of Alerting messages when CAMEL subscribers make outgoing calls.
11-132
It is measured when the MSC receives the ACM from the peer office. See points B and
E in the following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.13.4 Answer Count of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILCCK65
II. Description
It is the count of answered calls when CAMEL subscribers make outgoing calls.
It is measured when the MSC receives the message ANC, ANN, or ANM from the peer
office. See points C and F in the following figure.
11-133

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.13.5 Abandon Before Alerting Count of IN Subscriber Calling Fixed

Subscriber
I. Entity Name
ILUERN65
II. Description
It is the count of messages indicating abandon before alerting when CAMEL

subscribers make outgoing calls to fixed subscribers (PSTN subscribers, mobile
subscribers in other regions or local mobile subscribers) after success in routing.
It is measured when the MSC receives the message DTAP Disconnect from the
CAMEL subscriber before a call is connected.
11-134

IAM
REL
A
RNC/BSC
ACM
DTAP SETUP
DTAP DISCONNECT
B
ACM
IV. Formula
None
11.13.6 Abandon After Alerting Count of IN Subscriber Calling Fixed

Subscriber
I. Entity Name
ILRERN65
II. Description
It is the count of messages indicating abandon after alerting from CAMEL subscribers
in outgoing calls to fixed subscribers (PSTN subscriber or MS in other regions).
It is measured when the MSC receives the message DTAP Disconnect from a mobile
caller before the callee answers the ringing call.
11-135
IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
DTAP DISCONNECT
B
ANM/ANC
IV. Formula
None
11.13.7 Callee Busy Count of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILCBN65
II. Description
It is the count of messages indicating the callee is busy when CAMEL subscribers
make outgoing calls to fixed subscribers.
It is measured when the MSC receives the message STB or SLB from the peer TUP, or
the REL message from the ISUP due to callee busy. See points A and B in the following
figure.
11-136

IAM
IAM
A
RNC/BSC ACM
DTAP SETUP
IAM
ACM
IV. Formula
None
11.13.8 No Answer Count of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILLCNAN65
II. Description
It is the count of messages indicating calls are not answered when CAMEL subscribers
make outgoing calls to fixed subscribers.
It is measured when the MSC releases a call due to ringing timeout. See points A and B
11-137
IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
REL
B
ANM/ANC
IV. Formula
None
11.13.9 Seizure Traffic of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILSTRF65
II. Description
It is the traffic from the time when the MSC analyzes and finds that calls made by
CAMEL subscribers are outgoing calls to the time when the calls are released.
See points A and D in the following figure.
11-138

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.13.10 Connected Traffic of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILCCTRF65
II. Description
It is the traffic from the time when the outgoing calls made by CAMEL subscribers to
fixed subscribers are connected to the time when the calls are released.
It is measured when the MSC sends the message DTAP Alerting to a CAMEL
subscriber after receiving the ACM. See points B and E in the following figure.
11-139

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.13.11 Answer Traffic of IN Subscriber Calling Fixed Subscriber
I. Entity Name
ILACKT65
II. Description
It is the traffic from the time when fixed subscribers answer the outgoing calls made by
CAMEL subscribers to the time when the calls are released.
It is measured when the MSC receives the ANM and sends the message DTAP
Connect to a CAMEL subscriber. See points C and F in the following figure.
11-140

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.14 IN Subscriber Calling Mobile Subscriber

11.14.1 Overview of MS_TYPE_IN_MO_INT_TRAF
Name Description
IMATCN67 Attempt count of IN subscriber calling mobile subscriber
IMCCN67 Connect count of IN subscriber calling mobile subscriber
IMACKN67 Answer count of IN subscriber calling mobile subscriber
Abandon before alerting count of IN subscriber calling mobile
IMUER67
subscriber
Abandon after alerting count of IN subscriber calling mobile
IMRER67
subscriber
IMCBN67 Callee busy count of IN subscriber calling mobile subscriber
IMLCNAN67 No answer count of IN subscriber calling mobile subscriber
Callee determined busy count of IN subscriber calling mobile
IMMCRBN67
subscriber
11-141
Name Description
IMSTRF67 Seizure traffic of IN subscriber calling mobile subscriber
IMCTRF67 Connected traffic of IN subscriber calling mobile subscriber
IMACKT67 Answer traffic of IN subscriber calling mobile subscriber
11.14.2 Attempt Count of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMATCN67
II. Description
It is the count of call attempts made by CAMEL subscribers to local mobile subscribers.
A call attempt is generated after the caller dials the number with the minimum length set
in the called analysis table.
It is measured after the MSC analyzes the callee number. See points A and D in the
following figure.
11-142

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.14.3 Connect Count of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMCCN67
II. Description
It is the count of Alerting messages when CAMEL subscribers call local mobile
subscribers.
It is measured when the MSC receives the message DTAP Alerting from a mobile
terminating subscriber and forwards the message to a CAMEL caller. See points B and
E in the following figure.
11-143

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.14.4 Answer Count of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMACKN67
II. Description
It is the count of answered calls when CAMEL subscribers call local mobile subscribers.
It is measured when the MSC receives the message DTAP Connect Ack from a CAMEL
caller after receiving the message DTAP Connect from a mobile terminating subscriber
and forwards it to the CAMEL caller. See points C and F in the following figure.
11-144

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.14.5 Abandon Before Alerting Count of IN Subscriber Calling Mobile

Subscriber
I. Entity Name
IMUER67
II. Description
It is the count of messages indicating abandon before alerting when CAMEL

subscribers call local mobile subscribers.
It is measured when the MSC receives the message DTAP Disconnect from a CAMEL
subscriber before a call is connected.
11-145

IAM
REL
A
DTAP SETUP
DTAP DISCONNECT
B
DTAP ALERTING
IV. Formula
None
11.14.6 Abandon After Alerting Count of IN Subscriber Calling Mobile

Subscriber
I. Entity Name
IMRER67
II. Description
It is the count of messages indicating abandon after alerting when CAMEL subscribers
call local mobile subscribers.
It is measured when the MSC sends the ring-back tone to a CAMEL caller after
receiving the DTAP Alerting message from a mobile terminating subscriber, and
receives the message DTAP Disconnect from the CAMEL caller before receiving the
message DTAP Connect from the mobile terminating subscriber.
11-146
IAM
DTAP SETUP
DTAP ALERTING
ACM
ANM/ANC
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.14.7 Callee Busy Count of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMCBN67
II. Description
It is the count of messages indicating the callee is busy when CAMEL subscribers call
local mobile subscribers.
It is measured when the MSC obtains the MSRN from the HLR and sends the message
Send info for i/o call setup to the VLR, which returns a message indicating that the
callee (no CF service) is busy. See points A and B in the following figure.
11-147

IAM
DTAP SETUP
A
DTAP SETUP
DTAP SETUP
DTAP ALERTING
IV. Formula
None
11.14.8 No Answer Count of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMLCNAN67
II. Description
It is the count of calls released due to timeout and made by CAMEL subscribers to local
mobile subscribers, who do not answer the connected call.
It is measured when the MSC releases a call due to ringing timeout. See points A and B
11-148
IAM
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.14.9 Callee Determined Busy Count of IN Subscriber Calling Mobile

Subscriber
I. Entity Name
IMMCRBN67
II. Description
It is the count of messages indicating callees determine to be busy when CAMEL

subscribers call local mobile subscribers.
mobile terminating subscriber before a callee answers the ringing call. The cause
values are #17 user busy and #21 all rejected. See points A and B in the following
figure.
11-149
IAM
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.14.10 Seizure Traffic of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMSTRF67
II. Description
It is the traffic from the time when the MSC analyzes and finds the calls made by
CAMEL subscribers to local mobile subscribers are intra-office calls to the time when
the calls are released.
See points A and D in the following figure.
11-150

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.14.11 Connected Traffic of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMCTRF67
II. Description
It is the traffic from the time when calls made by CAMEL subscribers to local mobile
subscribers are connected to the time when the calls are released.
It is measured when the MSC sends the message DTAP Alerting to a CAMEL
subscriber. See points B and E in the following figure.
11-151

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.14.12 Answer Traffic of IN Subscriber Calling Mobile Subscriber
I. Entity Name
IMACKT67
II. Description
It is the traffic from the time when local mobile subscribers answer the calls made by
CAMEL subscribers to the time when the calls are released.
It is measured when the MSC receives the message DTAP Connect Ack after sending
the message DTAP Connect to a CAMEL caller. See points C and F in the following
figure.
11-152

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.15 IN Subscriber Calling IN Subscriber

Name Description
CTC82 Count of caller attempts
CC82 Count of caller connections
CA82 Count of caller answers
CUER82 Count of caller abandons before ringing
CRER82 Count of caller abandons after ringing
CCNA82 Count of caller no answers
CDB82 Count of callee busy
CDDB82 Count of callee determined busy
COQ82 Caller seizure traffic
11-153
Name Description
CCQ82 Caller connected traffic
CAQ82 Caller answer traffic
CDTO82 Count of callee attempts
CDC82 Count of callee connections
CDA82 Count of callee answers
CDOQ82 Callee seizure traffic
CDCQ82 Callee connected traffic
CDAQ82 Callee answer traffic
11.15.2 Count of Caller Attempts
I. Entity Name
CTC82
II. Description
It is the count of call attempts when callers and callees are both CAMEL subscribers.
It is measured after the MSC triggers the IN service for the caller and callee and
completes the number analysis.
z If the callee is in another office, see points A and D in the following figure.
11-154

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
z If the callee is a local mobile subscriber, see points A and D in the following figure.
11-155

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.15.3 Count of Caller Connections
I. Entity Name
CC82
II. Description
It is the count of connected calls when callers and callees are both CAMEL subscribers.
z If the caller is in the local office, it is measured when the MSC sends the message
DTAP Alerting to the caller.
z If the caller is a fixed subscriber, it is measured when the MSC returns the ACM to
the originating office.
z If the callee is in another office, see points B and E in the following figure.
11-156

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
z If the callee is a local mobile subscriber, see points B and E in the following figure.
11-157

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.15.4 Count of Caller Answers
I. Entity Name
CA82
II. Description
It is the count of answered calls when the callers and callees are both CAMEL
subscribers.
z If the caller is in the local office, it is measured when the MSC receives the
message DTAP Connect Ack after sending DTAP Connect to the caller.
z If the caller is a fixed subscriber, it is measured when the MSC sends the message
ANC, ANN or ANM to the originating office.
z If the callee is in another office, see points C and F in the following figure.
11-158

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
z If the callee is a local mobile subscriber, see points C and F in the following figure.
11-159

IAM
A
DTAP SETUP
DTAP ALERTING
ACM B
DTAP CONNECT
RNC/BSC
ANM C
DTAP SETUP
D DTAP SETUP
DTAP ALERTING
DTAP ALERTING E
DTAP CONNECT
DTAP CONNECT F
IV. Formula
None
11.15.5 Count of Caller Abandons Before Ringing
I. Entity Name
CUER82
II. Description
It is the count of messages indicating abandon before ringing when the callers and
callees are both CAMEL subscribers.
z If the caller is in the local office, it is measured when the MSC receives the
message DTAP Disconnect from the caller before a call is connected.
z If the caller is a fixed subscriber, it is measured when the MSC receives the REL
message from the originating office before a call is connected.
The callee is in another office:
11-160

IAM
REL
A
RNC/BSC
ACM
DTAP SETUP
DTAP DISCONNECT
B
ACM
The callee is in a terminating office:

11-161

IAM
REL
A
DTAP SETUP
DTAP DISCONNECT
B
DTAP ALERTING
IV. Formula
None
11.15.6 Count of Caller Abandons After Ringing
I. Entity Name
CRER82
II. Description
It is the count of messages indicating abandon after ringing when the callers and
z If the caller is in the local office, it is measured when the MSC returns the ring-back
tone after receiving the message DTAP Alerting from the caller, and receives the
message DTAP Disconnect before receiving DTAP Connect from the caller.
z If the caller is a fixed subscriber, it is measured when the MSC sends the ACM to
the originating office, and receives the REL message before sending the ANM.
The callee is in another office:
11-162
IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
DTAP DISCONNECT
B
ANM/ANC
The callee is in a terminating office:

11-163
IAM
DTAP SETUP
DTAP ALERTING
ACM
ANM/ANC
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
11.15.7 Count of No Answers
I. Entity Name
CCNA82
II. Description
It is the count of messages indicating calls are not answered when the callers and
It is measured when a call is released due to timeout in waiting for the Answer message
after the MSC receives the ACM (DTAP Connect) from the callee. It is measured when
the MSC receives the REL message after receiving the ACM (DTAP Connect) from the
callee, and the cause value is 146 (CV_NO_RESPOND) or 147
(CV_NO_ACKNOWLEGE).
11-164
IAM
IAM
ACM
ACM
REL
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
REL
B
ANM/ANC
11-165
IAM
DTAP SETUP
DTAP ALERTING
ACM
DTAP DISCONNECT
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
DTAP DISCONNECT
B
DTAP CONNECT
IV. Formula
None
I. Entity Name
CDB82
II. Description
It is the count of messages indicating the callee is busy when the callers and callees
are both CAMEL subscribers.
z If the caller is in the local office, it is measured when the MSC receives a MSRN
from the HLR, and sends the message Send info for i/o call setup to the VLR,
which returns a message indicating that the callee (no CF service) is busy.
z If the caller is a fixed subscriber, it is measured when the MSC requests the data
about the callee from the VLR, which returns a message indicating that the callee
(no CF service) is busy.
11-166

IAM
IAM
A
RNC/BSC ACM
DTAP SETUP
IAM
ACM
11-167

IAM
DTAP SETUP
A
DTAP SETUP
DTAP SETUP
DTAP ALERTING
IV. Formula
None
I. Entity Name
CDDB82
II. Description
It is the count of messages indicating callees determine to be busy when the callers
and callees are both CAMEL subscribers
mobile terminating subscriber before the callee answers the ringing call. The cause
values are #17 user busy and #21 all rejected.
11-168
DTAP SETUP
IAM
ACM
DTAP ALERTING
RNC/BSC
A
ANM/ANC
DTAP SETUP
IAM
ACM
DTAP ALERTING
B
ANM/ANC
11-169
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
RNC/BSC
A
DTAP CONNECT
DTAP SETUP
DTAP SETUP
DTAP ALERTING
DTAP ALERTING
B
DTAP CONNECT
IV. Formula
None
11.15.10 Caller Seizure Traffic
I. Entity Name
COQ82
II. Description
It is the traffic from the time when the MSC triggers the IN service for CAMEL callers
and callees to the time when the calls are released.
IV. Formula
None
11-170
11.15.11 Caller Connected Traffic
I. Entity Name
CCQ82
II. Description
It is the traffic from the time when calls from CAMEL callers to CAMEL callees are
connected to the time when the calls are released.
z If the caller is fixed subscriber, it is measured when the MSC returns the ACM to
IV. Formula
None
11.15.12 Caller Answer Traffic
I. Entity Name
CAQ82
II. Description
It is the traffic from the time when local CAMEL callees answer the calls made by
mobile subscribers to the time when the calls are released.
z If the caller is fixed subscriber, it is measured when the MSC returns the ACM to
IV. Formula
None
11.15.13 Count of Callee Attempts
I. Entity Name
CDTO82
11-171
II. Description
It is the count of call attempts when the callers and callees are both CAMEL
subscribers.
It is measured when the MSC triggers the IN service for the caller and callee. See
points A and D in the following figure.

IAM
A
IAM
ACM
ACM B
ANM/ANC
RNC/BSC
ANM C
DTAP SETUP
D IAM
ACM
DTAP ALERTING E
ANM/ACM
DTAP CONNECT F
IV. Formula
None
11.15.14 Count of Callee Connections
I. Entity Name
CDC82
II. Description
It is the count of Alerting messages when the callers and callees are both CAMEL
subscribers.
11-172
IV. Formula
None
11.15.15 Count of Callee Answers
I. Entity Name
CDA82
II. Description
It is the count of answered calls when the callers and callees are both CAMEL
subscribers.
DTAP Connect to the caller, and receives DTAP Connect Ack.
z If the caller is a fixed subscriber, it is measured when the MSC sends the message
ANC, ANN or ANM to the originating office.
IV. Formula
None
11.15.16 Callee Seizure Traffic
I. Entity Name
CDOQ82
II. Description
It is the traffic from the time when the MSC triggers the IN service for callees to the time
when the calls are released. The callers and callees are both CAMEL subscribers.
It is measured when the MSC connects a call internally and triggers the IN service for a
callee.
IV. Formula
None
11-173
11.15.17 Callee Connected Traffic
I. Entity Name
CDCQ82
II. Description
It is the traffic from the time when the calls by the CAMEL callers to the CAMEL callees
are connected to the time when the calls are released.
IV. Formula
None
11.15.18 Callee Answer Traffic
I. Entity Name
CDAQ82
II. Description
It is the traffic from the time when local CAMEL callees answer the calls made by
mobile subscribers to the time when the calls are released.
DTAP Connect to the caller, and receives DTAP Connect Ack.
z If the caller is a fixed subscriber, it is measured when the MSC returns the
message ANC, ANN or ANM to the originating office.
IV. Formula
None
11-174
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 12 Lawful Interception
Chapter 12 Lawful Interception

The measurement set is used to measure the traffic of the lawful interception office
direction.
Name Description
MS_OFFICE_OUT_TRAF_LICI Monitored outgoing traffic
MS_OFFICEDIR_OUT_TRAF_LICI Monitored office direction outgoing traffic
MS_TKGRP_OUT_TRAF_LICI Monitored trunk group outgoing traffic
12.2 Monitored Outgoing Traffic

12.2.1 Overview of MS_OFFICE_OUT_TRAF_LICI
Name Description

NANS Count of no answer
BRGABN Count of abandon before alerting

ALBLCL Count of lost calls due to overload control
FWCTLCL Count of lost calls due to NMS control
CTB Count of callee toll busy
CLB Count of callee local busy
MNTCIR Count of circuits in maintenance state
12-1
Name Description
ANSR Answer rate
CATS Count of call attempts
CRFS
application failure
PCFS Count of failed call attempts due to peer office congestion
ATTR Traffic of connected calls
I. Measurement Entity
BID
II. Description
It is the count of attempts to seize the outgoing trunks in monitored calls (the caller
attribute is not taken into account).
It is measured when the MSC attempts to seize the outgoing trunk or BICC CIC, The
measurement starts when the ISUP receives the Setup message. See point A in the
following figure.
12-2
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
SEIZ
II. Description
It is the count of seizures of the outgoing trunk in monitored calls.
It is measured after the outgoing trunk or BICC CIC is successfully seized,

12-3
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
CNT
II. Description
It is the count of alertings to outgoing calls. The callees can be PSTN subscribers, local
subscribers or GSM subscribers in other regions.
It is measured when the MSC receives the Address Complete Message (ITU-T Rec.
Q.722) from the peer office.
The measurement starts when the ISUP receives the ACM. See point A in the following
figure.
12-4
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
ANS
II. Description
It is the count of answered calls monitored by the lawful interception center (LIC).
It is measured when the ISUP receives the ANM. See point A in the following figure.
12-5
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
12.2.6 Count of No Answer
NANS
II. Description
It is the count of calls that are not answered due to the reason that the callee does not
respond for a long time or the caller gives up the call, or other reasons (as the callee is
in another office, the conditions of callees cannot be distinguished with the signaling, so
the above reasons are classified as one type).
Count of No answer = Count of connected calls – Count of answered calls.
It is measured after the MSC receives the ACM.

1) Count of no answer (case 1)
The cause value of the Release message is one of the following:
z CV_NO_ACKNOWLEGE
12-6
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
2) Count of no answer (case 2)

The cause value of the Release message is one of the following:
z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL
IV. Formula
None
12-7
12.2.7 Count of Abandon Before Alerting
BRGABN
II. Description
It is the count of messages indicating that the monitored calls are abandoned before
alerting.
It is measured when the outgoing trunk receives the REL message from the local CCB
while waiting for the ACM. See point A in the following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL Release Release
A
REL
IV. Formula
None
12.2.8 Count of Lost Calls Due to Overload Control
ALBLCL
II. Description
It is the count of lost calls due to overload control.
12-8
It is measured when a call is released due to overload control.

1) Call loss due to overload control (case 1)
The cause value is CV_CPU_OVERLAP in the Release message.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release
A
REL

12-9
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release
A
REL

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Connect ANM
Connect
ANM Release
A
REL
IV. Formula
None
12-10
12.2.9 Count of Lost Calls Due to NMS Control
FWCTLCL
II. Description
It is the count of lost calls due to control of the network management system (NMS).
It is measured when a call is released due to control of the NMS.

1) Call loss due to NMS control (case 1)
The cause value is CV_NET_MANAGE_BARRING in the Release message.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Release
A
REL

12-11
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Release
A
REL
3) Call loss due to NMS control (case 3)

IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
Connect ANM
Connect
ANM Release
A
REL
IV. Formula
None
12-12
LRUOFL
II. Description
It is the count of attempts made by the MSC to seize the outgoing trunk or BICC CIC for
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.
MSCServer MSCServer
Last-choice route overflow
A
IAM
IV. Formula
None
CBSY
II. Description
It is the count of call failures due to the reason that the callees are busy.
It is measured when the cause value is CV_BUSY in the REL message sent from the
peer office in outgoing calls.
12-13

The cause value is CV_BUSY in the Release message.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

The cause value is CV_BUSY in the Release message.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
12-14
CTB
II. Description
It is the count of messages indicating that the callees are busy because they are
making toll calls.
It is measured when the TUP receives the STB message from the peer office in
outgoing calls.
IV. Formula
None
CLB
II. Description
It is the count of messages indicating that the callees are busy because they are
making local calls.
It is measured when the TUP receives the SLB message from the peer office in
outgoing calls.
IV. Formula
None
SERL
II. Description
It is the traffic generated by outgoing call attempts.
12-15
It is measured from the time when the MSC receives the IAM or IAI to the time when the
MSC receives the message REL, CLF or CBK in a measurement period. The final
result is indicated in Erlang (ITU-T Rec. Q.722).
IAM
REL
IV. Formula
None
RERL
II. Description
It is the traffic generated when the outgoing calls are answered.
It is measured from the time when the MSC receives the Answer signal to the time
when the MSC sends the message REL, CLF or CBK in a measurement period. The
final result is indicated in Erlang (ITU-T Rec. Q.722).
12-16
IAM
ANM
REL
A
REL
IV. Formula
None
12.2.16 Count of Circuits in Maintenance State
MNTCIR
II. Description
trunk.
It is measured when one or multiple circuits change to maintenance state.
IV. Formula
None
CNTR
II. Description
Call completion rate (OEX) = Count of connected calls (OEX)/Count of call attempts
(OEX)
12-17
IV. Formula
CNTR=CNT/CATS
12.2.18 Answer Rate
ANSR
II. Description
Answer rate (OEX) = Count of answered calls (OEX)/Count of call attempts (OEX)
IV. Formula
ANSR=ANS/CATS
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
that the call is an outgoing one, the MSC begins the measurement.
12-18
A
IAM
IV. Formula
None

Failure
CRFS
II. Description
It is the count of call failures caused by unavailability of common resources on the MSC,
including the IWF, DTR, bill pool, and control table.
12-19
IAM
ACM
REL
RLC
IV. Formula
None
PCFS
II. Description
situation.
It is measured in one of the following cases:

z Long time no reply
z Called line faulty
z Call connection failure
z Peer office circuit group congestion
z Send special signal tone
z Peer office congestion
12-20

The cause value of the REL message may be one of the following:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
12-21
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
12.2.22 Traffic of Completed Calls
ATTR
II. Description
It is the traffic generated when outgoing calls are connected.
It is measured from the time when the ACM is received from the destination MSC to the
time when 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.
12-22
IAM
ACM
A
REL
C
REL
IV. Formula
None
12.3 Monitored Office Direction Outgoing Traffic

12.3.1 Overview of MS_OFFICEDIR_OUT_TRAF_LICI
Name Description
NODIRECT Count of calls through indirect subroute
NOOFC Count of no command for nested calling


12-23
Name Description
SEIZR Seizure rate
ANSR Answer rate
BLKR Block rate


BID
II. Description
It is the count of attempts to seize the outgoing trunk in monitored calls.
12-24
It is measured when the trunk receives the SETUP message from the CCB. See point A
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
SEIZ
II. Description
It is the count of seizures of the outgoing trunk in monitored calls.
It is measured when the MSC at the trunk side receives the SETUP message from the
CCB. See point A in the following figure.
12-25
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
CNT
II. Description
It is the count of alertings.
It is measured when the MSC at the trunk side receives the ACM from the peer office.
12-26
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
ANS
II. Description
It is the count of answered calls monitored by the LIC.
It is measured when the MSC at the trunk side receives the ANM from the peer office.
12-27
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
OFL
II. Description
trunk.
It is measured when the MSC fails to select a trunk circuit.
IV. Formula
None
12.3.7 Count of Calls Through Indirect Sub-Routes
NODIRECT
12-28
II. Description
It is the count of outgoing calls through indirect subroutes between offices of the same
level.
It is measured when outgoing calls are made through indirect subroutes between
offices of the same level.
IV. Formula
None
12.3.8 Count of No Command for Nested Calling
NOOFC
II. Description
It is the count of messages indicating no command for nested calling between offices of
the same level.
It is measured when there is no command for nested calling between offices of the
same level.
IV. Formula
None
DSEIZ
II. Description
It is the count of messages indicating dual seizures on bidirectional circuits or BICC

CICs.
It is measured when dual seizure occurs on a bidirectional circuit or a BICC CIC. There
is a gap between circuit selection and the time when the local office sends an IAM. If the
local office receives an IAM from the peer office in the gap, dual seizure occurs.
12-29
The measurement starts when the local office receives an IAM on a same circuit from
the peer office after the ISUP receives the Setup message from the CCB. See point A in
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
RETRY
II. Description
trunk circuits or BICC CICs.
It is measured during call retry after the MSC fails to occupy an outgoing trunk circuit or
a BICC CIC.
There are all types of reasons for trunk retry. For example, if there is a gap between
circuit selection and the time when the local office sends an IAM, the message sending
fails due to the status change of the circuit. Another case is as shown in the following
figure: After the local office sends an IAM, the peer office responds by sending the BLO
message.The measurement starts when the ISUP receives the BLO from the peer
office after sending the IAM. See point A in the following figure.
12-30
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
BLO
IV. Formula
None
POFCCG
II. Description
It is measured when the MSC receives the REL message from the peer office.
The measurement starts when the cause value in the REL message is one of the
following:
12-31
Case 1:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
Case 2
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
12-32
IV. Formula
None
CBSY
II. Description
It is the count of messages indicating call loss in outgoing monitored calls for the
reason that resources are occupied in the LIC.
It is measured when the MSC at the trunk side receives the REL message with the
cause value CV_BUSY from the peer office.
office. See point A in the following two figures.
Case 1:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL
12-33
Case 2:
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
ARGABN
II. Description
in outgoing calls.
After the MSC receives the ACM/ALERTING message from the terminating office, the
caller hears the ringing. The entity is measured when the caller hooks on before the
MSC receives the ACK message sent by the terminating office. See point A in the
following figure.
12-34
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
IV. Formula
None
LTNANS
II. Description
It is the count of messages indicating timeout release of the MSC because non-local
callees do not answer the phones although the phones ring. For the BSC/RNC side, it
is the count of messages indicating call loss due to timeout release when callees on the
radio network controller (RNC) or base station controller (BSC) do not answer after
receiving the ALERTING message.

There are two cases as follows: local office timeout release and peer office timeout
release.
1) Local office timeout release
following:
12-35
z CV_NO_ACKNOWLEGE
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
2) Peer office timeout release

receives the REL message from the peer office and the cause value is one of the
following:
z CV_NO_ACKNOWLEGE
12-36
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
INSBICIR
II. Description
measurement period.
IV. Formula
None
AVABICIR
12-37
II. Description
bidirectional circuits in the office direction in a measurement period.
IV. Formula
None
BLKBICIR
II. Description
It is the count of blocked bidirectional trunk circuits in the office direction in a

measurement period.
IV. Formula
None
12.3.18 Availability of Outgoing Trunks
OTKAVAR
II. Description
Availability of outgoing trunks = Count of available circuits/Count of installed circuits

(Circuits on all modules are calculated on the BAM).
IV. Formula
OTKAVAR=E28/E27
12-38
SEIZR
II. Description
Seizure rate = Count of seizures/Count of call attempts (Circuits on all modules are
calculated on the BAM.)
IV. Formula
SEIZR=E1/E0
CNTR
II. Description
IV. Formula
CNTR=E2/E0
12.3.21 Answer Rate
ANSR
II. Description
IV. Formula
ANSR=E3/E0
12-39
12.3.22 Block Rate
BLKR
II. Description
Block rate = Count of blocked circuits/Count of installed circuits
IV. Formula
None
BLKBIR
II. Description
Rate of blocked bidirectional circuits = Count of blocked bidirectional circuits/Count of

installed bidirectional circuits
IV. Formula
BLKBIR=E29/E27
BISERL
II. Description
It is the traffic generated from the time when outgoing calls occupy bidirectional trunks
to the time when calls are released.
12-40
IV. Formula
None
SERL
II. Description
It is the traffic generated from the time when outgoing calls attempt to seize the trunk to
The measurement starts when the MSC at the trunk receives the SETUP message,
and stops when the call is released and the status of the ISUP circuits changes to idle in
a measurement period. The final result is indicated in Erlang.
IV. Formula
None
CERL
II. Description
It is the traffic generated from ringing to call release in intra-office calls.
The measurement starts when the local office receives the ACM, and stops when the
call is released. The final result is indicated in Erlang.
IV. Formula
None
RERL
12-41
II. Description
It is the traffic generated from the time when the LIC receives calls to the time when
calls are released in intra-office calls.
The measurement starts when the local MSC receives the ANM, and stops when the
call is released. The final result is indicated in Erlang.
IV. Formula
None
AST
II. Description
Average seizure duration (It is the intersection of the average duration from the time
when the call occupies the outgoing trunk to release of the outgoing trunk in a
measurement period) = Seizure traffic/Count of seizures; Formula on the BAM:
Average seizure duration = Seizure traffic/Count of seizures; Formula on the host:
Average seizure duration = Seizure traffic/100 × Measurement period (second)/100
IV. Formula
AST=E44/(E0*100)
OFLFIRST
II. Description
the office direction because all outgoing (bidirectional) trunks of the sub-route are busy.
12-42
IV. Formula
None
OFLSECND
II. Description
the office direction because all outgoing (bidirectional) trunks of the second sub-route
are busy.
IV. Formula
None
OFLTHIRD
II. Description
the office direction because all outgoing (bidirectional) trunks of the third sub-route are
busy.
IV. Formula
None
OFLFOURTH
12-43
II. Description
the office direction because all outgoing (bidirectional) trunks of the fourth sub-route are
busy.
IV. Formula
None
OFLFIFTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the fifth sub-route are
busy.
IV. Formula
None
OFLSIXTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the sixth sub-route are
busy.
IV. Formula
None
12-44
OFLSEVENTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the seventh sub-route
are busy.
IV. Formula
None
OFLEIGHTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the eighth sub-route
are busy.
IV. Formula
None
OFLNINTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the ninth sub-route are
busy.
12-45
IV. Formula
None
OFLTENTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the tenth sub-route are
busy.
IV. Formula
None
OFLELEVENTH
II. Description
the office direction because all outgoing (bidirectional) trunks of the eleventh sub-route
are busy.
IV. Formula
None
OFLTWELFTH
12-46
II. Description
the office direction because all outgoing (bidirectional) trunks of the twelfth sub-route
are busy.
IV. Formula
None
12.4 Monitored Trunk Group Outgoing Traffic

12.4.1 Overview of MS_TKGRP_OUT_TRAF_LICI
Name Description
DNMA Count of trunk circuit type mismatch
CNMA Count of bearer capability and mode mismatch
DSEIZ Count of dual seizure
NETADM Count of effects caused by NMS control
CTB Count of callee toll busy

CLB Count of callee local busy

12-47
Name Description
SEIZR Seizure rate
ANSR Answer rate
BLKR Block rate

BID
II. Description
It is the count of attempts to seize the trunk circuits to the monitored office in outgoing
calls to the office.
It is measured when the MSC fails to select the circuits in outgoing calls.
12-48
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
SEIZ
II. Description
It is the count of seizures of the trunk circuits to the monitored office in outgoing calls to
the office.
It is measured when the IAM (ITU-T Rec.Q.722) is sent.

12-49
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
CNT
II. Description
It is the count of alertings when calls are set up in the whole network.
It is measured when the ACM (ITU-T Rec.Q.722) is received from the peer office.
The measurement starts when the ISUP receives the ACM. See point B in the following
figure.
12-50
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
ANS
II. Description
It is the count of answered outgoing calls.
It is measured when the Answer Signal (ITU-T Rec.Q.722) is sent.

The measurement starts when the ISUP receives the ANM. See point C in the following
figure.
12-51
IAM
Setup
Setup
Setup Ack A
Setup Ack
IAM
Alerting ACM
Alerting
B
ANM
ACM Connect
Connect
Connect Ack
ANM C
Connect Ack
IV. Formula
None
OFL
II. Description
It is the count of messages indicating failure of circuit occupation in the office direction
because all outgoing (bidirectional) trunks in the office direction are busy.
It is measured when the circuits fail to be selected in the MSC.
IV. Formula
None
V. Count of Trunk Circuit Type Mismatch
VI. Measurement Entity
DNMA
VII. Description
It is the count of messages indicating that the type of trunk circuits is wrong.
12-52
VIII. Measurement Point
It is measured when a wrong type of trunk circuit is found.
IX. Formula
None
12.4.7 Count of Bearer Capability and Mode Mismatch
CNMA
II. Description
It is the count of messages indicating call failure because there is a mismatch between
the bearer capability and the bear mode.
It is measured when the call fails because there is a mismatch between the bearer
capability and the bear mode.
IV. Formula
None
DSEIZ
II. Description
It is the count of messages indicating dual seizures on bidirectional circuits.
It is measured when a dual seizure occurs on bidirectional circuits.

There is a gap between the circuit selection and the time when the local office sends an
IAM. If the local office receives an IAM from the peer office during the gap, dual seizure
occurs.
The measurement starts when the ISUP receives the IAM message. See point A in the
following figure.
12-53
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
IV. Formula
None
RETRY
II. Description
trunk circuits.
It is measured during call retry after the MSC fails to occupy an outgoing trunk circuit.
There are all types of reasons for call retry. For example, if there is a gap from the circuit
selection to the time when the local office sends an IAM, the message sending fails due
to the change of circuit status.
The following figure shows a case of call retry. After the local office sends the IAM, the
peer office responds with the BLO message, which causes call retry.
The measurement starts when the ISUP receives the BLO message. See point A in the
following figure.
12-54
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
BLO
IV. Formula
None
POFCCG
II. Description
It is measured when the MSC receives the TUP SEC and ISUP REL (switch congestion)
messages from the peer office.
12-55
following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

following figure.
12-56
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
CGT
II. Description
IV. Formula
None
12.4.12 Count of Effects Caused by NMS Control
NETADM
12-57
II. Description
Count of effects caused by NMS control = Call loss due to direct route limitation + Call
loss due to directional circuits + Call loss due to temporary suspension of circuits +
Count of cancellations of alternative routes + Count of switches to other circuits + Count
of temporary alternative routings
IV. Formula
E13+E14+E15+E16+E17+E18
CBSY
II. Description
It is the count of messages indicating call failure because callees are busy.
It is measured when the ISUP receives the REL message with the cause value
CV_BUSY (17 + 128) from the peer office. It is also measured by the TUP. When
queried, the ISUP/TUP shows the sum of three parameters: callee busy, callee toll busy,
and callee local busy.
following figure.
12-58
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
REL

following figure.
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
12-59
CTB
II. Description
toll calls
It is measured when the TUP outgoing trunk receives the STB message.
STB
IV. Formula
None
CLB
II. Description
local calls.
It is measured when the TUP outgoing trunk receives the SLB message.
12-60
SLB
IV. Formula
None
ARGABN
II. Description
It is the count of messages indicating callers release before offhook of non-local

fixed-line callees in outgoing calls.
message sent by the terminating office.
z CV_NORMAL
12-61
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL
IV. Formula
None
LTNANS
II. Description
It is the count of messages indicating that the MSC releases calls due to timeout in
waiting for offhook of non-local fixed-line callees.

z CV_NO_ACKNOWLEGE
12-62
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM
REL Release Release
A
REL

z CV_NO_ACKNOWLEGE
following figure.
12-63
IAM
Setup
Setup
Setup Ack
Setup Ack
IAM
Alerting ACM
Alerting
ACM REL
IV. Formula
None
INSCIR
II. Description
It is the count of installed outgoing trunk circuits (including bidirectional trunks) in the
IV. Formula
None
AVACIR
12-64
II. Description
It is the average count (an integer) of available outgoing trunk circuits including
IV. Formula
None
BLKCIR
II. Description
It is the count of blocked outgoing trunk circuits including bidirectional trunks in the
office direction in a measurement period.
IV. Formula
None
INSBICIR
II. Description
measurement period.
IV. Formula
None
12-65
AVABICIR
II. Description
IV. Formula
None
BLKBICIR
II. Description
It is the count of blocked bidirectional trunk circuits in the office direction in a

measurement period.
IV. Formula
None
12.4.24 Availability of Outgoing Trunks
OTKAVAR
II. Description
Availability of outgoing trunks = Count of available circuits/Count of installed circuits

(Circuits on all modules are calculated on the BAM)
12-66
IV. Formula
OTKAVAR=E25/E24.
SEIZR
II. Description
Seizure rate = Count of seizures/Count of call attempts (Circuits on all modules are
calculated on the BAM)
IV. Formula
SEIZR=E1/E0
CNTR
II. Description
IV. Formula
CNTR=E2/E0
12.4.27 Answer Rate
ANSR
II. Description
12-67
IV. Formula
ANSR=E3/E0.
12.4.28 Block Rate
BLKR
II. Description
Block rate = Count of blocked circuits/Count of installed circuits
IV. Formula
BLKR=E26/E24
BLKBIR
II. Description
Rate of blocked bidirectional circuits = Count of blocked bidirectional circuits/Count of

installed bidirectional circuits
IV. Formula
BLKBIR=E29/E27
BISERL
II. Description
12-68
IV. Formula
None
SERL
II. Description
It is measured from the time when outgoing calls in the office direction occupy outgoing
abnormally.
It is measured from the time when the MSC sends the IAM to the time when it sends or
receives the UBM, Clear Forward, Clear Backward, or REL message in a measurement
IV. Formula
None
CERL
II. Description
It is measured from the time when outgoing calls in an office direction are connected to
It is measured from the time when the MSC receives the ACM to the time when it sends
or receives the Clear Forward, Clear Backward, or REL message in a measurement
IV. Formula
None
12-69
RERL
II. Description
It is measured from the time when incoming calls in an office direction are answered to
It is measured from the time when the MSC receives the Answer Signal to the time
when it sends the Clear Forward, Clear Backward, or REL message in a measurement
IV. Formula
None
AST
II. Description
It is the average seizure duration of outgoing calls in an office direction. It is calculated

by using seizure traffic of outgoing calls, seizure count of outgoing calls, and sampling
cycle.
IV. Formula
E44/E0.
12-70
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index
Index
DTAP, 6-2
Numerics
3G VP Subscriber Originated Traffic, 8-63 F
3G VP Subscriber Terminated Traffic, 8-68 Failure Causes of the Office, 8-202
Fixed Subscriber Calling IN Subscriber, 11-62
A Forwarded Subscriber Count, 8-198
A-Interface Signaling Procedure Error, 10-3
Answer Rate, 6-23 G
ARD, 2-75 GPRS Timeout, 10-40
authentication, 2-48 Gs-Interface Error Cause, 10-67
Gs-Interface Operation, 10-42
B GSM Assignmen, 3-9
Base Station Controller, 10-31 GSM Call Drop Rate, 6-1
bearer Service, 4-9 GSM Cell Handover, 3-79
BICC Node Capability, 10-22
BICC SCTP Link, 10-17 H
H.248 MGW, 10-80
C H.248 SCTP Link, 10-88
Call Forwarding Traffic, 8-192 handover Between Two PLMN, 3-1
call processing, 6-1
Call Setup Rate, 6-14 I
CAP Operation, 11-1 IN Calls of All Subscribers Calling Operato, 11-93
Cell Traffic Distribution, 9-154 IN Component, 11-83
Ciphering Mode Setting, 3-179 IN Dialogue, 11-88
combined condition, 7-1 IN Event, 11-111
Combined Object Conditions Traffic, 7-1 IN Failure, 11-109
Connection Type, 8-158 IN Subscriber Calling Fixed Subscriber, 11-131
Count of ISUP Message, 10-172 IN Subscriber Calling IN Subscriber, 11-153
Count of MVNO Subscriber, 9-177 IN Subscriber Calling Mobile Subscriber, 11-141
Count of TCAP Message, 10-426 Incoming Traffic, 8-254
Count of TUP Message, 10-499 Initial Call Attempt, 11-50
Count of VLR Subscriber, 9-5 intra-Office Path Across MG, 5-12
CPU Seizure Rate, 9-1 Intra-Office Traffic, 8-174
IP Port Traffic, 10-92
D ISUP Abnormality, 10-174
Destination Code Traffic, 5-57 ISUP Circuit Group, 10-99
Destination Traffic Distribution, 5-68 ISUP Message Usage, 10-170
i-1
ISUP Network, 10-155 MTP3B Destination Signaling Point, 10-368

ISUP Node, 10-141 MTP3B Signaling Link, 10-359
IUA Link Set, 10-187 MTP3B Signaling Link Set, 10-367
IUA Signaling Link, 10-196
N
L NI_LR Location, 4-18
lawful interception, 12-1
Location Area Traffic Distribution, 9-127 O
location management, 2-1 Office Direction Incoming Traffic, 5-41
location Service, 4-1 Office Direction Outgoing Traffic, 5-15
location Update, 2-59 Outgoing Traffic, 8-135
M P
M2UA Link, 10-214 paging, 3-185
M2UA Link Set, 10-206 performance measurement, 1-1
M3UA Destination Entity, 10-223
M3UA Signaling Link, 10-224 R
M3UA Signaling Link Set, 10-244
relationship Between Measurement Object and
MAP IN Service, 11-57
Measurement Unit, 1-2
MAP Operation, 10-298
MAP Public Service Procedure Error, 10-264 S
measurement Entity, 1-2
SAAL Signaling Link, 10-399
measurement Set, 1-1
SCCP Availability, 10-403
measurement Unit, 1-1
SCCP Performance, 10-413
Mobile Subscriber Calling IN Subscriber, 11-73
SCCP Traffic, 10-411
mobile-Originated Location Service, 4-26
SCCP Usage, 10-405
mobile-Terminated Location Service, 4-43
Short Message Service, 3-58
Monitored Office Direction Outgoing Traffic, 12-23
SOR, 2-38
Monitored Outgoing Traffic, 12-1
Source TMG Destination Route Traffic, 8-270
Monitored Trunk Group Outgoing Traffic, 12-47
special service, 4-1
MSC basic service, 3-1
SSF Call, 11-60
MSC Basic Table, 2-1
Supplementary Service Traffic, 5-76
MSC Handover, 3-21
MSC mobility management, 2-1
T
MS-Originated Outgoing Traffic, 8-2
TCAP Availability, 10-424
MS-Originated Traffic, 8-18
TCAP Component Utilization, 10-432
MS-Terminated Incoming Traffic, 8-29
TCAP CSL, 10-417
MS-Terminated Traffic, 8-47
TCAP Transport Sublayer, 10-420
MTC Success Rate, 6-5
TMSI Reallocation, 3-34
MTP Destination Signaling Point, 10-370
total traffic of the office, 8-1
MTP Signaling Link, 10-371
traffic Between BICC MG, 5-2
MTP Signaling Link Set, 10-388
Traffic Distribution and Duration, 7-54
i-2
traffic of all office direction, 5-1 UE-Terminated Incoming Traffic, 8-102

traffic of IN call, 11-1 UE-Terminated Traffic, 8-119
Transit Traffic, 8-297 Union Location Update Rejected Cause, 10-509
Trunk Group Incoming Traffic, 5-147
Trunk Group Outgoing Traffic, 5-122 V
Trunk Office Direction Incoming Traffic, 5-104 VP Destination Traffic, 5-182
Trunk Office Direction Outgoing Traffic, 5-76 VP Office Direction Incoming Traffic, 5-161
TUP Abnormity, 10-500 VP Office Direction Outgoing Traffic, 5-171
TUP Circuit Group, 10-439 VP Trunk Office Direction Incoming Traffic, 5-193
TUP Message Application, 10-498 VP Trunk Office Direction Outgoing Traffic, 5-203
TUP Network, 10-485
TUP Node, 10-473 W
WCDMA Assignment, 3-40
U
WCDMA Call Drop Rate, 6-9
UE-Originated Outgoing Traffic, 8-74 WCDMA RNC Handover, 3-116
UE-Originated Traffic, 8-92
i.
i-3

MSOFTX3000 Technical Manual-Performance Measurement Entities

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MSOFTX3000 Technical Manual-Performance Measurement Entities

Uploaded by

Copyright:

Available Formats

Chapter 1 Overview .........................................................................................

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Huawei Technologies Proprietary

Volume Performance Measurement Entities

Manual Version T2-030249-20051031-C-3.03

Product Version V100R003

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Huawei Technologies Proprietary

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

Huawei Technologies Proprietary

This manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R003.

The manual provides an overall introduction to HUAWEI MSOFTX3000 Mobile

There are twelve chapters in the manual.

Huawei Technologies Proprietary

The manual is intended for the following readers:

The manual uses the following conventions:

Boldface Headings are in Boldface.

II. GUI conventions

Button names are inside angle brackets. For example, click

III. Keyboard operation

Huawei Technologies Proprietary

IV. Mouse operation

Press the left button or right button quickly (left button by

Caution Means reader be extremely careful during the operation.

Note: Means a complementary description.

Huawei Technologies Proprietary

Chapter 1 Overview ....................................................................................................................... 1-1

Chapter 2 MSC Basic Functions .................................................................................................. 2-1

Huawei Technologies Proprietary

2.3 Authentication .................................................................................................................. 2-48

Huawei Technologies Proprietary

Chapter 3 MSC Basic Services .................................................................................................... 3-1

Huawei Technologies Proprietary

3.4.8 Count of Successful Basic Outgoing Handovers .................................................. 3-26

Huawei Technologies Proprietary

3.6.25 Count of Assignment Failures Due to Directed Retry ......................................... 3-56

Huawei Technologies Proprietary

Huawei Technologies Proprietary

Huawei Technologies Proprietary

Chapter 4 MSC Special Services ................................................................................................. 4-1

Huawei Technologies Proprietary

4.3.3 Traffic of Asynchronous Digital Service BS2X ...................................................... 4-10

Huawei Technologies Proprietary

4.5.16 Count of MO Location Failures Due to Unknown/Unreachable LCS Client at GMLC

Chapter 5 Bearer Traffic ............................................................................................................... 5-1

Huawei Technologies Proprietary

5.3.6 Count of Path Seizures Across One MG .............................................................. 5-13

Huawei Technologies Proprietary

Huawei Technologies Proprietary

5.6.8 Seizure Traffic ....................................................................................................... 5-61

Huawei Technologies Proprietary

5.9.10 Count of Non–Main Control Circuit Contention................................................... 5-83

Huawei Technologies Proprietary

5.10.5 Call Completion Rate ........................................................................................ 5-108

Huawei Technologies Proprietary

5.11.17 Count of No Reply........................................................................................... 5-135

Huawei Technologies Proprietary

5.12.20 Rate of Blocked Bidirectional Circuits ............................................................. 5-158

Huawei Technologies Proprietary