Alcatel Performance Data Measurement

COVER SHEET
Title
Performance Data Measurements
Classification
A5020 ATRIUM Wireless Call Server (WCS) GSM/UMA CS CORE NETWORK SYSTEM DOCUMENTATION TECHNICAL REQUIREMENT SPECIFICATION
Edition Date Change Note
07
2008-05-02
Appraisal Authority
Company
Function Name
Alcatel
Originator
Company
Function Name
Alcatel SE Harinder Lakhian
3BL76533FAAADSZZA Edition 07
1/128
Originator(s) Approval(s)
Harinder Lakhian
ABSTRACT
This document identifies the performance parameters and data measurements for the Alcatel Atrium Distributed MSC product. It identifies the key performance statistics expected to be required for the DMSC/GMSC projects.
01 02
Creation
03
04 05
06 07
Added all DSP pool types in DSP usage group, added cause codes to SYSGRP Removed G from GMSC in section 3 New counters added in the following groups by Rel 3 SP9 are highlighted in Red bold color and shaded in grey. - Added new counters to UMAURRPERF and UMABSSMAPPERF New counters added in CALLPERF group by Rel 3 SP9 are highlighted in Red bold color and shaded in grey. New UMARJ11URRPERF performance group added in Rel 3 SP9
Updated with latest counter description, formulae in SUMMARYPERF, and added UMA groups for Rel 3 SP6 combined GSM/UMA load. Added UMA call type counters in CALLPERF Added card status and card type in WSSPERF and WSSDISKPERF New counters added in the following groups by Rel 3 SP7 are highlighted in yellow color Added new counters (26-27) to UMAUNCPSPERF Added two new counters (counters 14-15) to UMALCSUNCPERF Added new counters (counters 16-60) to UMAPERF
2/128
A5020 ATRIUM Wireless Call Server (WCS) GSM/UMA CS CORE NETWORK

SYSTEM DOCUMENTATION
TECHNICAL REQUIREMENT SPECIFICATION
Performance Data Measurements GSM/UMA
3/128
Table of contents
1 OVERVIEW ...................................................................................................................................... 7 1.1 1.2 Compatibility ..................................................................................................................... 7 Definitions & Abbreviations ............................................................................................. 7
NMS INTERFACE A BRIEF SUMMARY.................................................................................... 10 2.1 2.2
Data Storage .................................................................................................................... 10 Data Collection and Retention....................................................................................... 10 2.2.1 Data Transfer..................................................................................................... 11 MSC PERFORMANCE DATA ..................................................................................... 12
ATRIUM 3.1 3.2
SYSTEM PERFORMANCE DATA ................................................................................................ 14 4.1 4.2 4.3 4.4 4.5 4.6 4.7 WSS System Performance Information (SUMMARYPERF) ........................................ 14 WSS Overload Control Information (MOOVLDPERF).................................................. 19 ISUP Network Overload Control Information (ISUPOVLDPERF)................................ 20 Media Gateway Control (MEGACO) Information (CALLEGCPPERF)......................... 22 WMG CPU Usage Information (MSFCPULOAD)........................................................... 23 WSS Performance Information (WSSPERF)................................................................. 25 WSS Disk Performance Information (WSSDISKPERF) ............................................... 26
General File Format ........................................................................................................ 12 Reserve Fields ................................................................................................................. 13
SIGNALING PERFORMANCE DATA ........................................................................................... 27 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11
CALL-RELATED & GSM / MOBILITY PERFORMANCE DATA .................................................. 60 6.1 6.2 6.3 6.4 6.5
MTP2 Link Information (SYSMTP2LINKPERF) ............................................................. 27 MTP3 Link Information (SYSMTP3LINKPERF) ............................................................. 28 MTP3 Linkset Information (SYSMTP3LINKSETPERF)................................................. 30 MTP3 Route Information (SYSMTP3ROUTEPERF) ...................................................... 31 ISUP DPC Information (SYSISUPDPCPERF) ................................................................ 33 BICC DPC Information (SYSBICCDPCPERF) ............................................................... 36 SCCP Information (SYSSCCPPERF) ............................................................................. 39 CAP (CAMEL Application Part) Information (CAPMSGPERF).................................... 41 INAP Information (INAPMSGPERF)............................................................................... 44 IS-41 Information (IS41MSGPERF) ................................................................................ 47 MAP Information ............................................................................................................. 48 5.11.1 Mobility Management Related MAP Message (MAPMMMSGPERF) ............... 48 5.11.2 Subscriber Information Related MAP Messaging (MAPSPMMSGPERF)......... 51 5.11.3 SMS Related MAP Messaging (MAPSMSMSGPERF) ..................................... 52 5.11.4 CISS Related MAP Messaging (MAPCISSMSGPERF) .................................... 53 5.11.5 Location Services Related MAP Messaging (MAPLCSMSGPERF) ................. 55 5.12 BSSAP (A-Interface from BSS) Information ................................................................. 56 5.12.1 Call and Mobility Related BSSAP Information (BSSAPMMMSGPERF) .......... 56 5.12.2 Circuit and System Maintenance Related BSSAP Information (BSSAPMNTMSGPERF) 58 Call Control & Features Information (CALLPERF)....................................................... 60 MAP Information Gateway MSC (MAP1PERF) .......................................................... 64 MAP Information Visited/Serving MSC (MAPPERF) ................................................. 65 BSSAP (A-Interface) and Mobile Call Information (BSSAPPERF).............................. 68 IS41 Information (IS41PERF).......................................................................................... 71 4/128
IN RELATED INFORMATION ....................................................................................................... 79 7.1 7.2
SMS Information A-Interface Related (BSSAPSMSPERF) ....................................... 72 Call Independent Supplementary Services Information (CISSPERF)........................ 73 Circuit Switched Data and Data Interworking Function.............................................. 74 6.8.1 IWF Group Information (MSFIWFGRPPERF) ................................................... 74 6.8.2 IWF Signaling Information (SYSIWFSMIMPERF) ............................................. 75 6.9 Call Disposition Information (ENDOFCALLPERF)....................................................... 77 6.10 Call Total Time Performance Information (CALLTOTALTIMEPERF) ......................... 78 INAP Information (INAPGWYPERF) .............................................................................. 79 CAMEL Information (CAPPERF) .................................................................................... 80
6.6 6.7 6.8
REGULATORY SERVICES INFORMATION ................................................................................ 81 8.1 8.2 8.3 Wireless Priority Service (WPS) Information (PRIORITYCALLPERF) ....................... 81 Emergency Call (E911) Information (EMERGENCYCALLPERF) ................................ 83 Emergency Routing Key (ESRK) Information (ESRKPOOLPERF)............................. 84
FACILITIES PERFORMANCE DATA............................................................................................ 85
10 CONFIGURATION DATA .............................................................................................................. 99 10.1 10.2 10.3 10.4
9.1 System Route Information (SYSROUTEPERF) ............................................................ 85 9.2 System Group Information (SYSGRPPERF)................................................................. 86 9.3 TDM Echo Cancellation DSP usage ( DSPUSAGEPERF)............................................ 90 9.4 TDM Interconnect Information (ICONCARDPERF) ...................................................... 92 9.5 TRUNKGROUP and WMG Interconnect Information (TRKGRPWMGICONPERF) .... 93 Error! Objects cannot be created from editing field codes. ......................................................... 95 9.6 Port Capacity Performance Group ( PORTCAPACITYPERF) ..................................... 96 9.7 Summary of CDR statistics ( CDRSUMMARYPERF) ................................................... 98 Trunk Group Information ( TRKGP_WMG_RELATIONSHIP) ...................................... 99 WMG Information( WMG_ID_NAME_RELATIONSHIP) .............................................. 100 Interconnect Information( ICON_WMG_RELATIONSHIP) ......................................... 101 Link and Linkset Relationship (LINK_LINKSET_RELATIONSHIP)........................... 102
11 UMA PERFORMANCE DATA INFORMATION .......................................................................... 103
11.1 UMA Performance Data Information in UNC .............................................................. 103 11.1.1 URR Discovery, Registration and TCP Connection Information (UMAURRPERF) 103 11.1.2 URR RJ11 Discovery, Registration and TCP Connection Information (UMAURRPERF) 105 11.1.3 URR Connection, Channel, Call, Handover and Miscellaneous Information (UMAURRCONNCALLPERF)......................................................................................... 108 11.1.4 Call and Mobility Related BSSMAP Information (UMABSSMAPPERF) ......... 109 11.1.5 UMA LDAP Interface Information (UMALDAPPERF)...................................... 111 11.1.6 RR Cause Received Information (UMARRCSRXPERF)................................. 112 11.1.7 RR Cause Sent Information (UMARRCSTXPERF)......................................... 113 11.1.8 BSSMAP Cause Received Information (UMABSSMAPCSRXPERF) ............. 114 11.1.9 BSSMAP Cause Sent Information (UMABSSMAPCSTXPERF) ..................... 116 11.1.10 UNC Security Gateway Message Information (UMASGWPERF) ................ 118 11.1.11 UNC-PS Message Information (UMAUNCPSPERF) ...................................... 119 11.1.12 Location Services UNC SMLC Interface Information (UMALCSUNCPERF) 121 11.1.13 Location Services UMADB UNC Message Information (UMADBUNCPERF). 122 11.1.14 GMLC Message Information (UMAGMLCUNCPERF) .................................... 123 11.1.15 Location Services SMLC Information (UMALCSSMLCPERF) ........................ 124 11.2 UMA Performance Data Information in Call Server ................................................... 125 11.2.1 Call and Handover Information (UMAPERF)................................................... 125
5/128
[1] WEM Performance Management Wireless Customer Document 700-0027-004 [2] A5020 ATRIUM Wireless Call Server (WCS) GSM/UMTS CS Core Network System Documentation Technical Requirements Specification Key Performance Indicators 3BL76534AAAADSZZA [3] A5020 ATRIUM Wireless Call Server (WCS) UMA CS Core Network System Documentation Technical Requirements Specification Key Performance Indicators for UMA 3BL76532AAAADSZZA [4] A5020 ATRIUM Wireless Call Server (WCS) GSM/UMA/UMTS CS Core Network System Documentation Technical Requirements Specification External Cause /Internal Code Mapping 3BL76757AAAADSZZA
6/128
This document identifies the performance parameters and data measurements for the Alcatel Atrium Distributed MSC product. It identifies the key performance statistics expected to be required for the R3.0 GSM/UMA DMSC/GMSC projects. This document reflects the Rel 3.0 SP9 release for the GSM/UMA combined load. The items highlighted in yellow color represents delta between Rel 3 SP7 and pre-SP7 Rel 3. The items highlighted in grey in UMAURRPERF group and UMABSSMAPPERF groups are new items introduced for Rel 3 SP9 load. The items highlighted in green indicate UMARJ11URRPERF group are new items introduced for Rel 3 SP9 load.
OVERVIEW
1.1 Compatibility
This document describes the performance and data measurements for:
Atrium Release 3.0 (DMSC (Visited MSC) Application, plus continued support of GMSC/Tandem Application) AP BCSM BICC BSSMAP CAMEL CAP CCM CCS7 CF CIC CISS CPU CS CTM DDM DER DMSC DN DP DPC EMS ETC ESRK FCI GEDI Access Point Basic Call State Model Bearer Independent Call Control BSS Management Application Part Customized Application for Mobile Network Enhanced Logic CAMEL Application Part Call Control Module Common Channel Signaling System #7 Call Forwarding Circuit Identification Code Call Independent Supplementary Service Central Processing Unit Circuit Switch Cellular TTY Modem Data Distribution Module Discrete Event Registration Distributed (Visited/Serving) MSC Directory Number Detection Point Destination Point Code Element Management System Establish Temporary Connection Emergency Routing Key Forward Call Indicator Gestion Electronique de Documents Intranet 7/128
1.2 Definitions & Abbreviations
HLR ICON IMEI IMSI INAP IS-41 ISDN IWF GMSC GMT GSM GUI LAC LNP LRN MAP MM MO MT MS MSC MSRN NE NMS NPDB OAM QoS Ph2 PS PSTN PVLR SAM SAPI SCP SI SIM SMS SNMP SS T-CSI TCP/IP TDD TDM TMN TMSI TRS TTY UMA UMAN UMTS UNC URLC URR USS UTC 3BL76533FAAADSZZA Edition 07
Home Location Register Interconnect International Mobile subscriber Equipment Identity International Mobile Subscriber Identity IN Application Part Interim Standard 41 Integrated Services Digital Network Interworking Function Gateway MSC Greenwich Mean Time (see UTC) Global System for Mobile Communication Graphical User Interface Location Area Code Local Number Portability Location Number Routing Mobile Application Part Mobility Management Mobile Originated Mobile Terminated Mobile Station Mobile Services Switching Center Mobile Subscriber Routing Number Network Element Network Management System Number Portability Database Operation, Administration and Maintenance Quality of Service Phase-2 Packet Switch Public Switched Telephone Network Previous VLR System Administration Module Service Access Point Identifier Service Control Point Status Inspection Signaling Interface Module Short Message Service Simple Network Management Protocol Supplementary Service Terminating CAMEL Service Information Transmission Control Protocol/Internet Protocol Telecommunications Device for the Deaf (Please refer to CTM) Time Domain Multiplexing (tradition circuit-switch trunk facilities) Telecommunications Management Network Temporary Mobile Subscriber Identity Technical Requirement Specification Text Telephony (Please refer to CTM) Unlicensed Mobile Access Unlicensed Mobile Access Network Universal Mobile Telecommunication System UMA Network Controller UMA Radio Link Controller UMA Radio Resource Unstructured Supplementary Service Universal Coordinated Time 8/128
VLR VMSC WEM WMG WSS
Visitor Location Register Visited MSC Wireless Element Manager Wireless Media Gateway Wireless SoftSwitch
9/128
Performance history data is collected on the Disk space mounted on Wireless Call Server (WCS) System Administration Module (SAM). A Wireless Element Manager (WEM) client provides remote Java GUI to view both history and current performance data. Remote or local Users through the WEM client on a PC or Workstation can view performance data as well as configure the collection and distribution management for performance. WSS OAM also provides an SNMP interface to TMN Network Element Layer functionality of the WSSNE Performance Control Tables. WEM Server and WSS OAM share Performance Management configuration database and communicates through SNMP v2. Please refer to [1] for detailed information on the WEM Performance management 2.1 Data Storage
NMS INTERFACE A BRIEF SUMMARY
All WSS history files are saved to dual disks for redundancy. These files are written to subdirectories, usually named after the Performance Group Names under the main directory /space/stats on each disk connected to the SAM. Please login to the Atrium system to get the actual name of the sub-directories. The /space/stats directory is also soft linked as /stats. In case of active SAM failure data can still be accessed from the newly active SAM. A performance history file is created in a sub-directory under /stats directory whenever specified time interval expires. The general file name format is <prefix>.YYMMDD-HHMM.NodeNumber where

<prefix> is the performance Group Name see the sections describing each performance data file. An example of a prefix is SYSISUPCICPERF YYMMDD is the date and HHMM is the end time of the performance collection interval. The time used is the local time on the System Administration Module (SAM). Node Number is the number of either the WSS Node or the WMG Node that is collecting the performance data. It is not present for all performance groups. See the detailed description of each group for confirmation of the file name format for that group.
2.2 Data Collection and Retention
Performance collection can be enabled or disabled on a performance group basis. Collection for all of the groups highlighted herein should be activated. Default for collection is generally disabled for most groups. Collection intervals for most performance groups can be configured to any of the following values: 15 minutes, 30 minutes, 60 minutes, and 24 hours (except for the SYSGRPPERF (see 9.2) performance group, which can also be set to a 5-minute collection interval; and certain WMG groups which allow only 15 minute intervals). Default interval is 15 minutes. The number of days performance data is retained can be configured to any value between 1 and 7 days. The default value for retention is 3 days. On the day after the retention period, the oldest days data is overwritten.
3BL76533FAAADSZZA Edition 07 10/128
Please see product documentation [1] for full information on enabling and disabling collection for a given performance group. In general, this will be done by operations personnel via the WEM client.
2.2.1 Data Transfer
Retained Performance data can be transferred through (S/T) FTP to a remote host (push). This data can also be fetched (pulled) by external systems such as Watchmark or RAMSES by using FTP mechanisms with proper UNIX level access privileges configured to the SAM module. Please see product documentation [1] for full information on configuring the data transfer.
11/128
ATRIUM MSC PERFORMANCE DATA
3.1 General File Format
The historical data for each of the performance groups described herein is stored in a text file. This text file contains one or more records whether this is the case for a specific performance group will be explained in detail with each group. Where more than one record is present, a key field exists identifying each record as an instance of the performance data. For example, the key field might be an MTP link, an ISUP destination point code, etc. Records are separated by the new line character (ASCII LF). Fields in the records are separated by an ASCII character comma character (,). An example record format is shown below. 2002-08-15 17:15:00,2002-08-15 17:20:00,4,1,1,0,0,0,0,0,0,0,0,0,0,0,1440,0,0,1440, 0,0,1440,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<LF> As can be noted above, all fields except the first two are integer fields, represented by a string of ASCII digit characters (0 9). Most of these integer fields are simple accumulative registers. Where they represent something else, an explanatory note is provided in the description of each performance group. The first two fields in every record are a Start Time Stamp and a Stop Time Stamp, encompassing the time interval covered by the file. Each of these is represented in the following format: YYYY-MM-DD<Space>HH:MM:SS Where YYYY=year, MM=month, DD=day, HH=hour (in 24-hour format), MM=minutes, SS=seconds. Each of these is an ASCII digit character (0 9). The Start Time Stamp and Stop Time Stamps for records within a file may not exactly match the end time in the file name, because of the internal mechanism by which statistics are collected in the Atrium. The start and stop times within the file are the precise interval to which the statistics apply, while the stop time in the file name is the nominal end-point. One or more performance data files are generated for each performance group or sub-group based on the configured time interval, provided that collection is enabled for that group. Each file is produced on the interval. For example, if the interval is set to 60 minutes, then files will be produced every hour, on the hour. If the interval is set to 15 minutes, then files will be produced on the hour and 15, 30, and 45 minutes past the hour. All legitimate records are generated, even if all of the field values are zero, in order to provide continuity in downstream processing systems.
12/128
High-priority performance data files for the Atrium GMSC or DMSC (Visited MSC) are provided in the next sections. Each section refers to a particular performance data file. In these sections, a table is used to describe one record. For each table, the first column represents the position of the field in the record. The second column is the name code used on the WEM GUIs, for cross-reference. The third column provides a brief description of the counter. The section also includes file naming convention and the description of any fields that are not simply accumulative registers. Finally, any fields that are used as key fields to describe the entity to which a given record applies are specifically identified (in blue) and described (beneath the table). Please note that wherever a field appears in gray, the field is present but is either for future use or is slated for removal in the future and is not being maintained as accurate. In either case, for now any value present in the field should not be counted on as accurate. 3.2 Reserve Fields
Reserve Fields were introduced in Release 2.3C to minimize the impact in the future software patches related to the addition of new performance pegs. Reserve fields will be continued in future releases. Reserve fields are added only to certain performance peg groups that were identified for potential future growth. Depending on the need, some of the reserve fields will be used in a software patch. The mapping of such reserve fields if any will be communicated to the customer and to information processing partners through the Release Notes. Alcatels customers can in turn communicate these mappings to their down stream software companies for proper processing. If the reserve fields are exhausted in a deployed release due to greater number of new peg requests, Alcatel will follow the previous method of over-writing the existing but least used peg in consultation with the customer. The new fields that are mapped to the reserve fields in a patch release will be added as new fields and the reserved fields will be freed up in the next main software release provided the requests come in before the freeze date of the next main release. However, the sequence/order of the mapped fields in a performance group will be retained in the main release in order to prevent changes to the down stream software should customer upgrade to next release.
13/128
SYSTEM PERFORMANCE DATA
4.1 WSS System Performance Information (SUMMARYPERF)

Performance Group Name: SUMMARYPERF File Naming Convention: SUMMARYPERF.YYMMDD-HHMM Number of records: 1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
1
Position
STARTTIMESTAMP STOPTIMESTAMP MAXSIMCPU MAXDDMCPU MAXCCMCPU MAXSAMCPU MAXIPMCPU MEANSIMCPU MEANDDMCPU MEANCCMCPU MEANSAMCPU MEANIPMCPU
Field Name
ROOTDISKOCCACTSAM VARDISKOCCACTSAM SPACEDISKOCCACTSAM ROOTDISKOCCSTBSAM VARDISKOCCSTBSAM SPACEDISKOCCSTBSAM AVAILSIMMEMORY AVAILDDMMEMORY AVAILCCMMEMORY AVAILSAMMEMORY AVAILIPMMEMORY TOTALCALLATT
Beginning time of the performance interval Ending time of the performance interval Highest value of maximum CPU occupancy across all configured SIM cards (%), derived from WSSPERF. Highest value of maximum CPU occupancy across all configured DDM cards (%), derived from WSSPERF. Highest value of maximum CPU occupancy across all configured CCM cards (%), derived from WSSPERF. Highest value of maximum CPU occupancy across all configured SAM cards (%), derived from WSSPERF. Highest value of maximum CPU occupancy reached across all configured IPM cards (%),derived from WSSPERF. Mean CPU occupancy reached across all SIM cards (%),derived from WSSPERF as an average of the reported mean for all SIM cards. Mean CPU occupancy reached across all DDM cards (%),derived from WSSPERF as an average of the reported mean for all DDM cards... Mean CPU occupancy reached across all CCM cards (%), derived from WSSPERF as an average of the reported mean for all active CCM cards. Mean CPU occupancy reached across all active SAM cards (%), derived from WSSPERF as an average of the reported mean for all SAM cards. Mean CPU occupancy reached across all IPM cards (%), derived from WSSPERF as an average of the reported mean for all IPM cards. 1 Disk occupancy percentage (/root partition) on Primary SAM (%) derived form WSSDISKPERF Disk occupancy percentage (/var partition) on Primary SAM (%) derived form WSSDISKPERF Disk occupancy percentage (/space partition) on Primary SAM (%) derived form WSSDISKPERF Disk occupancy percentage (/root partition) on Secondary SAM (%) derived form WSSDISKPERF Disk occupancy percentage (/var partition) on Secondary SAM (%) derived form WSSDISKPERF Disk occupancy percentage (/space partition) on Secondary SAM (%) derived form WSSDISKPERF Minimum memory available on any SIM card (%), derived from WSSPERF. Minimum memory available on any DDM card (%), derived from WSSPERF. Minimum memory available on any CCM card (%) from all configured active CCM cards, derived from WSSPERF. Minimum memory available on any SAM card (%), derived from WSSPERF. Minimum memory available on any IPM card (%), derived from WSSPERF. Total number of call attempts per hour (normalized) all types. This is
Description
Fields 13 through 18 are measured at the end of the performance interval. 14/128
Position
Field Name
25 26 27 28 29 30 31 32 33
TOTALACTSUBS MMCALLATT MLCALLATT LMCALLATT LLCALLATT INTERVLRLUPCALLATT INTRAVLRLUPCALLATT AUTHENTICATIONCALLATT SMSCALLATT
derived from BSSAPPERF, UMAPERF, SYSISUPDPCPERF, SYSBICCDPCPERF, and MOOVLDPERF by adding MSORIGCMSRVCREQ + MSEMRGNCYCMSRVCREQ + ISUPPFMIAMRX + BICCPFMIAMRX + OVRLDRJCTMOVCALL 2 Total number of subscribers in VLR . This is a snapshot of VLR database, total active and inactive subs. Total number of Mobile-to-Mobile call attempts per hour (normalized), derived from CALLPERF by adding CALLATTMSTOMSVCCAL+ CALLATTUMATO2GVCCAL+ CALLATTUMATOUMAVCCAL+ CALLATT2GTOUMAVCCAL for all CCM cards. Total number of Mobile-to-Land call attempts per hour (normalized), derived from CALLPERF by adding CALLATTMSTOPSTNVCCAL + CALLATTUMATOPSTNVCCAL for all CCM cards. Total number of Land-to-Mobile call attempts per hour (normalized), derived from CALLPERF by adding CALLATTPSTNTOMSVCCAL + CALLATTPSTNTOUMAVCCAL for all CCM cards. Total number of Land-to-Land call attempts per hour (normalized), derived from CALLPERF by adding CALLATTLANDTOLANDVCCAL for all CCM cards. Total number of Inter-VLR Location Update attempts per hour (normalized), derived from BSSAPPERF and UMAPERF by adding Total number of Intra-VLR Location Update attempts per hour (normalized), derived from BSSAPPERF and UMAPPERF by adding Total number of Mobile Authentication Requests per hour (normalized), derived from BSSAPPERF and UMAPPERF by adding ATTAUTH for Total SMS (MO plus MT) Attempts per hour (normalized), derived from Total Number of Supplementary Service invocations per hour (normalized), derived from CALLPERF by adding of INVOKECFUSS,
Description
ATTINTERVLRLOCUPD for all CCM cards.
ATTINTRAVLRLOCUPD for all CCM cards. all CCM cards.
BSSAPSMSPERF by adding CALLATTMSORGSMS and CALLATTMSTERMSMS for all CCM cards.
34
SSINVOCATIONCALLATT
35
ATTINTRAMSCHO
Total Number of attempted Intra MSC Handovers per hour (normalized), derived by adding ATTINEXTINTRAMSCHDO from BSSAPPERF and HOATTUMATO2G + HOATT2GTOUMA from UMAPERF for all CCM
INVOKECFBSS, INVOKECFNRYSS, INVOKECFNRCSS, INVOKECALLWAITSS, INVOKEECTSS, INVOKEMULTIPTYSS for all CCM cards.
36
SUCCINTRAMSCHO
37 38 39 40
2
UNSCCEXTHDORECNCTPERMSC UNSCEXTHDOLOSCNCTPERMSC ATTINTERMSCHOHI SUCCINTERMSCHOHI
Total Number of Successful Intra MSC Handovers per hour (normalized). Derived by adding SUCCINEXTINTRAMSCHDO from BSSAPPERF and HOSUCCUMATO2G + HOSUCC2GTOUMA from UMAPERF for all CCM cards. Total number of unsuccessful external handovers with reconnect to the old channels per hour (normalized). Derived from BSSAPPERF and UMAPPERF by adding UNSCCEXTHDORECNCTPERMSC for all Total number of unsuccessful external handovers with loss of connection per hour (normalized). Derived from BSSAPPERF and UMAPPERF by adding UNSCEXTHDOLOSSCNCTPERMSC for all CCM cards. Total number of attempted Inter MSC Handovers (Incoming) per hour (normalized). Derived from MAPPERF by adding (ATTININTERMSCHDO + ATTSUBSQNTINTERMSCHDOMSCA + ATTSUBSQNTINTERMSCHDOMSCC) for all CCM cards. Total number of successful Inter MSC Handovers (Incoming) per hour (normalized). Derived from MAPPERF by adding
cards.
CCM cards.
As measured at the end of the performance interval. 15/128
Position
Field Name
41
ATTINTERMSCHOHO
42 43 44
SUCCINTERMSCHOHO MNPDBQUERIES MNPDBNEGRESP
45
MEANHOLDTIMEMOBILETOMOBILE
46
MEANHOLDTIMEMOBILETOLAND
47
MEANHOLDTIMELANDTOMOBILE
48
MEANHOLDTIMELANDTOLAND
49
MMCALLFAILURERATE
50 51 52 53
MLCALLFAILURERATE LMCALLFAILURERATE LLCALLFAILURERATE LUPFAILURERATE
(SUCCININTERMSCHDO + SUCCSUBSQNTINTERMSCHDOMSCA + SUCCSUBSQNTINTERMSCHDOMSCC) for all CCM cards. Total number of attempted Inter MSC Handovers (Outgoing) per hour (normalized). Derived from MAPPERF by adding (OUTINTERMSCHDO + ATTOUTSUBINTERMSCHOMSCA + ATTOUTSUBINTERMSCHOMSCC) for all CCM cards. Total number of successful Inter MSC Handovers (Outgoing) per hour (normalized). Derived from MAPPERF by adding (SUCCOUTINTERMSCHDO + SUCCOUTSUBINTERMSCHOMSCA + SUCCOUTSUBINTERMSCHOMSCC) for all CCM cards. Total number of queries sent to NPDB per hour (normalized). Derived from CALLPERF by adding LNPDIPTOTAL for all CCM cards. Total number of unsuccessful NPDB queries per hour (normalized). Derived from CALLPERF as: LNPDIPTOTAL - LNPDIPRESULTLRN LNPDIPNONPORTED for all CCM cards 3 Mean Mobile-to-Mobile Call Holding Time , derived by dividing TOTALCALLTIMEMOBILETOMOBILE from CALLTOTALTIMEPERF group by (CALLANSMSTOMSVCCAL + CALLANSUMATO2GVCCAL+ CALLANSUMATOUMAVCCAL+ CALLANS2GTOUMAVCCAL) from CALLPERF. This really represents mean call conversation time since it starts from answer. Mean Mobile-to-Land Call Holding Time derived by dividing TOTALCALLTIMEMOBILETOLAND from CALLTOTALTIMEPERF group by (CALLANSMSTOPSTNVCCAL+ CALLANSUMATOPSTNVCCAL) from CALLPERF. This really represents mean call conversation time since it starts from answer. Mean Land-to-Mobile Call Holding Time derived by dividing TOTALCALLTIMELANDTOMOBILE from CALLTOTALTIMEPERF group by (CALLANSPSTNTOMSVCCAL+ CALLANSPSTNTOUMAVCCAL) from CALLPERF. This really represents mean call conversation time since it starts from answer. Mean Land-to-Land Call Holding Time derived by dividing TOTALCALLTIMELANDTOLAND from CALLTOTALTIMEPERF group by CALLANSLANDTOLANDVCCAL from CALLPERF. This really represents mean call conversation time since it starts from answer. 4 Mobile-to-Mobile Call Failure Rate (%) , derived from CALLPERF: {1(CALLSUCCMSTOMSVCCAL+ CALLSUCCUMATO2GVCCAL + CALLSUCCUMATOUMAVCCAL+ CALLSUCC2GTOUMAVCCAL) /(CALLATTMSTOMSVCCAL+ CALLATTUMATO2GVCCAL + CALLATTUMATOUMAVCCAL+ CALLATT2GTOUMAVCCAL))}*100 Mobile-to-Land Call Failure Rate (%), derived from CALLPERF: {1(CALLSUCCMSTOPSTNVCCAL+ CALLSUCCUMATOPSTNVCCAL) /(CALLATTMSTOPSTNVCCAL+ CALLATTUMATOPSTNVCCAL)}*100 Land-to-Mobile Call Failure Rate (%), derived from CALLPERF: {1(CALLSUCCPSTNTOMSVCCAL+ CALLSUCCPSTNTOUMAVCCAL) /(CALLATTPSTNTOMSVCCAL+ CALLATTPSTNTOUMAVCCAL)}*100 Land-to-Land Call Failure Rate (%), derived from CALLPERF: {1(CALLSUCCLANDTOLANDVCCAL /CALLATTLANDTOLANDVCCAL)}*100 Location Update Failure Rate (%), derived from BSSAPPERF and UMAPPERF as: {1- ((SUCCINTRAVLRLOCUPD +
Description
SUCCINTERVLRLOCUPD) / (ATTINTRAVLRLOCUPD + ATTINTERVLRLOCUPD))}*100
Please note that the fields highlighted in yellow background have changed their positions. This is done to group them logically. The previous order was MMCALLFAILURERATE, MEANHOLDTIMELANDTOLAND, MEANHOLDTIMEMOBILETOLAND, MEANHOLDTIMELANDTOMOBILE and MEANHOLDTIMEMOBILETOMOBILE. 4 This counter does not include calls that failed due to terminating leg establishment failure during the call attempt process. This footnote applies to this and subsequent Call Failure Rate (%) fields.
3
16/128
Position
Field Name
54 55
SMSFAILURERATE AUTHFAILURERATE
SMS Failure Rate Including MO and MT (%) derived from BSSAPSMSPERF as: {1 - (CALLSUCCMSORGSMS +
Description
Authentication Failure Rate (%) derived from BSSAPPERF and UMAPPERF as: {1 - (SUCCAUTH / ATTAUTH)}*100 Calls failing during setup all call types (%) derived from BSSAPPERF, UMAPPERF SYSISUPDPCPERF, and SYSBICCDPCPERF as: {1-
CALLSUCCMSTERMSMS) /( CALLATTMSORGSMS + CALLATTMSTERMSMS )}*100
56
TOTALCALLFAILURERATE
57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75
MAXTXLINKOCC
MAXRXLINKOCC
MAXTXLINKOCCPERLS MAXRXLINKOCCPERLS MEANTXLINKOCCPERLS MEANRXLINKOCCPERLS MAXTRUNKGROUPOCC MAXTRUNKOCCPERTG MEANTRUNKOCCPERTG Reserved1 Reserved2 Reserved3 Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved9
Maximum receive link occupancy reached - across all SS7 links (%) Maximum transmit link occupancy reached across all links in the specified linkset (% - special format see below) Maximum receive link occupancy reached across all links in the specified linkset (% - special format see below) Average (mean) transmit link occupancy across all links in the specified linkset (% - special format see below) Average (mean) receive link occupancy across all links in the specified linkset (% - special format see below) Maximum trunk group occupancy reached (across all groups) (%) Maximum trunk group occupancy reached in the specified trunk group (% - special format see below) Average (mean) trunk group occupancy in the specified trunk group (% - special format see below) Reserved field 1 for future use
6
Maximum transmit link occupancy reached - across all SS7 links (%)
5
(SUCCMSORIGCALLS+ SUCCMSEMRGCYCALLS + ISUPPFMACMTX+ BICCPFMACMTX ) /( ATTMSORIGCALLS+ ATTMSEMRGCYCALLS + ISUPPFMIAMRX+BICCPFMIAMRX)}*100
Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use
Reserved10
Reserved field 10 for future use
Since some SUMMARYPERF information is calculated based on the value of other performance group pegs, when the SUMMARYPERF collection interval is set, it will set the interval of certain other groups to match. A warning is generated on the WEM GUI prior to this being done. SUMMARYPERF is a special group presenting key system-wide data. It pulls information from eleven other performance groups. These groups are:
The formula used for this counters is derived from SYSMTP3PERF group as follow: 8 * (( MTP3LNKPFMSIFO CTRX + MTP3LNKPFMSIOO CTRX + MTP3LNKPFMMSUR X * 6)) MeanRxLinkOcc = 100 * Link _ Bandwidth _ in _ kbps 17/128
The formula used for this counters is derived from SYSMTP3LINKPERF group as follow: 8 * ((MTP3LNKPFMSIFOCTTX + MTP3LNKPFMSIOOCTTX + MTP3LNKPFMMSUTX * 6)) MeanTxLinkOcc = 100 * Link _ Bandwidth _ in _ kbps
BSSAPERF UMAPERF BSSAPSMSPERF CALLPERF CALLTOTALTIMEPERF MAPPERF MOOVLDPERF ISUPOVLDPERF SYSGRPPERF SYSISUPDPCPERF SYSMTP3LINKPERF WSSDISKPERF WSSPERF
Please note the units carefully in SUMMARYPERF, they are often either percentage values or special character fields representing multiple system entities the special format identified above. Please also note that fields #24 and #26 through #44 are presented on an hourly rate. If statistics are being gathered in intervals less than one hour, then the fields #24 and #26 through #44 will be adjusted or normalized to an hourly rate. As an example, to get the absolutely event count for a 15 minute interval, the numbers in these fields must be divided by four (4). The details of this special format are as specified below:
Where the entire field is a character string of variable length, containing in turn the following information:
,\nAA aaa:##\nBB bbb:##\nCC ccc:##,
Field format for this group is different from all other groups.
\n as a subfield delimiter between different trunk groups (fields #64 and #65) or linksets (fields #59, #60, #61, and #62) AA<space>aaa is a variable length field containing the trunk group or linkset number, a space, and then the trunk group or linkset name. A trunk group number can range from 2-4 digits in length, and a trunk Group Name from 1-64 characters in length. A linkset number can range from 1-3 digits in length, and a linkset name from 1-16 characters in length. There will be as many trunk groups or linksets within each record as are equipped on the switch in question (represented above by AA aaa, BB bbb, CC ccc, etc.). : indicates the separation of the linkset/trunk group number and name from the % value captured for that trunk group ## is the value of the field for that trunk group or linkset
18/128
4.2 WSS Overload Control Information (MOOVLDPERF)
Performance Group Name: MOOVLDPERF File Naming Convention: MOOVLDPERF.YYMMDD-HHMM Number of records: Equals the number of DDM cards active in the system.
Position
1 2 3 4 5 6 7
WSSNODENUM OVRLDRJCTMOVCALL OVRLDRJCTLUP OVRLDRJCTMOSMSCALL OVRLDRJCTMOCISSCALL RESERVED2 RESERVED3 RESERVED4 RESERVED1
STARTTIMESTAMP STOPTIMESTAMP
Field Name
9 10 11
WSS Node (DDM Card) to which this record applies Number of Mobile Originated Calls rejected as a result of overload controls being active. Number of Location Updates rejected as a result of overload controls being active. Number of Mobile Originated SMS transactions rejected as a result of overload controls being active. Number of Mobile Originated CISS transactions rejected as a result of overload controls being active. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
Beginning time of the performance interval Ending time of the performance interval
Description
WSSNODENUM is the key field, and identifies the DDM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all DDM cards.
19/128
4.3 ISUP Network Overload Control Information (ISUPOVLDPERF)
Performance Group Name: ISUPOVLDPERF File Naming Convention: ISUPOVLDPERF.YYMMDD-HHMM Number of records: Equals the number of CCM cards active in the system, multiplied by the number of Destination Point Codes.
Position
1 2 3 4 5 6 7 8 9
WSSNODENUM DPC
Field Name
IBCALLRJTATRLVL1 IBCALLRJTATRLVL2 IBCALLRJTATRLVL3 OBCALLRJTLCLLVL1 OBCALLRJTLCLLVL2
Number of Inbound ISUP calls rejected per DPC during Atrium System Overload level 1. Number of Inbound ISUP calls rejected per DPC during Atrium System Overload level 2.
WSS Node (CCM Card) to which this record applies Destination Point Code.
Description
10 11 12 13 14 15 16 17 18 19 20 21 22
OBCALLRJTLCLLVL3 OBCALLRJTRMTLVL1 OBCALLRJTRMTLVL2 OBCALLRJTRMTLVL3 OBCALLRJTUSRUNAVAIL OBMSGDRPLCLLVL1 OBMSGDRPLCLLVL2 OBMSGDRPLCLLVL3 OBMSGDRPUSRUNAVAIL RESERVED1 RESERVED2 RESERVED3 RESERVED4
Number of Inbound ISUP calls rejected per DPC during Atrium System Overload level 3. Number of Outbound ISUP calls rejected per DPC during local DPC congestion level 17. Number of Outbound ISUP calls rejected per DPC during local DPC congestion level 2. Number of Outbound ISUP calls rejected per DPC during local DPC congestion level 3. Number of Outbound ISUP calls rejected per DPC during Remote DPC ACC congestion level 1. Number of Outbound ISUP calls rejected per DPC during Remote DPC ACC congestion level 2. Number of Outbound ISUP calls rejected per DPC during Remote DPC ACC congestion level 3. Number of Outbound ISUP calls rejected per DPC during user part unavailable condition. Number of Outbound ISUP messages dropped per DPC due to local DPC congestion level 1. Number of Outbound ISUP messages dropped per DPC due to local DPC congestion level 2. Number of Outbound ISUP messages dropped per DPC due to local DPC congestion level 3. Number of Outbound ISUP messages dropped per DPC during user part unavailable condition. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
WSSNODENUM and DPC are the key fields (dual key).WSSNODENUM identifies the CCM Node (card) to which this record applies. DPC identifies the destination point code about which this record applies. It is in the format of a single integer that can be converted to traditional <network><cluster><member> format as follows: 1. Convert the integer value to a 6-numeral hexadecimal value
Please note that it is considered to be rejection of a call (as opposed to a message) when it is the Initial Address Message (IAM) that is dropped.
7
20/128
To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards.
2. The two most significant hexadecimal Numerals represent the <network>, the middle two Numerals represent the <cluster>, and the least two significant numerals represent the <member>. They can, of course, be converted individually back to decimal notation as required.
21/128
4.4 Media Gateway Control (MEGACO) Information (CALLEGCPPERF)
Performance Group Name: CALLEGCPPERF File Naming Convention: CALLEGCPPERF.YYMMDD-HHMM Number of records: Equals the number of CCM cards active in the system multiplied by the number of media gateways subtending the WSS.
Position
1 2 3 4 5 6 7 8 9
WSSNODENUM WMGNODENUM
Field Name
CALLATTMGCADD CALLSUCCMGCADD CALLATTMGCMODIFY CALLSUCCMGCMODIFY CALLATTMGCMOVE
WSS Node (CCM Card) to which this record applies WMG Node (Media Gateway) to which this record applies
Description
10 11 12 13 14 15 16
CALLSUCCMGCMOVE CALLATTMGCSUBTRACT CALLSUCCMGCSUBTRACT RESERVED1 RESERVED2 RESERVED3 RESERVED4
Number of MEGACO Add messages that were attempted. Pegged at attempt to send "MEGACO_ADD" message to MGW Number of MEGACO Add messages that were successful - number of "MEGACO_ACK" (ADD) messages received from MGW Number of MEGACO Modify messages that were attempted. Pegged at attempt to send "MEGACO_MODIFY" message to MGW Number of MEGACO Modify messages that were Successful number of "MEGACO_ACK" (MODIFY) messages received from MGW Number of MEGACO Move messages that were attempted. Pegged at attempt to send "MEGACO_MOVE" message to MGW Number of MEGACO Move messages that were successful - number of "MEGACO_ACK" (MOVE) messages received from MGW Number of MEGACO Subtract messages that were attempted. Pegged at attempt to send "MEGACO_SUBTRACT" message to MGW Number of MEGACO Subtract messaged that were successful number of "MEGACO_ACK" (SUBTRACT) messages received from MGW Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
WSSNODENUM and WMGNODENUM together comprise key fields (2-part key) that uniquely identify the control pair to which this record applies. To provide a system-wide view of the information towards a specific media gateway, the values for that WMGNODENUM must be accumulated across all CCM cards. To find a system-wide total for all media gateways, then all records across all CCM cards should be accumulated.
22/128
4.5 WMG CPU Usage Information (MSFCPULOAD)
Performance Group Name: MSFCPULOAD File Naming Convention: MSFCPULOAD.YYMMDD-HHMM Number of records: Equal to the number of processors on all cards on all WMG Nodes.
Position
1 2 3 4 5 6 7 8 9
STARTTIMESTAMP STOPTIMESTAMP MSFNODEID MSFSLOTID
Field Name
MSFCPUID MSFCPULOAD1SEC MSFCPULOAD5SEC MSFCPULOAD15SEC MSFCPULOAD30SEC MSFCPULOAD1MIN MSFCPULOAD5MIN MSFCPULOAD15MIN
WMG (media gateway) Node Number to which this record applies. WMG card slot to which this record applies ( range 1 to 40) CPU (on the card) to which this record applies Mean occupancy (percentage) across last 1 second in the performance interval Mean occupancy (percentage) across last 5 seconds in the performance interval Mean occupancy (percentage) across last 15 seconds in the performance interval Mean occupancy (percentage) across last 30 seconds in the performance interval Mean occupancy (percentage) across last 1 minute in the performance interval Mean occupancy (percentage) across last 5 minutes in the performance interval Mean occupancy (percentage) across the entire 15-minute performance interval.
Description
10 11 12
Because of the unique nature of the information in this file (i.e. each field relates to a specific performance interval), the STARTTIMESTAMP is present but is not used. It is set to equal the STOPTIMESTAMP. The actual start time of the measurement interval will depend upon which field is being analyzed. For example, for Field 13 (recommended as a high-priority field), the start time implied will be 15 minutes prior to the STOPTIMESTAMP. MSFNODEID, SLOT, and CPUID together comprise key fields (3-part key) that uniquely identify the CPU to which this record applies. Each SLOTID may report MSFCPUIDs (1-7) depending on the type of card equipped in the slot. For example, CM1 and CM2 cards will report the following MSFCPUID: CPU 0 is CMM CPU (OAM & etc) CPU 1 is CMF CPU (Facility etc) CPU 2 is CMC CPU (CRM) CPU 3 is CMT CPU (Narrow band signaling, PRI, GR303 etc) CPU 4 is CMU CPU (ATM signaling) CPU 5 is CMP CPU (HDLC expansion) CPU 6 is CMI CPU (IP etc) - supported for CM2 only
For VSM card, the following MSFCPUIDs will be reported: CPU 0 is the master CPU (manages cards and connections) CPU 1 are the two slave CPUs (SAR drivers) CPU 2 are the two slave CPUs (SAR drivers)
For ES, ESM4, VSM2, Q-OC3/STM1, GbE, PM, VSM8 cards, MSFCPUID CPU 0 will be reported:
24/128
4.6 WSS Performance Information (WSSPERF)

Performance Group Name: WSSPERF File Naming Convention: WSSPERF.YYMMDD-HHMM
Position Field Name Description
1 2 3 4 5 6 7 8
WSSNODENUM MAXWSSCPU
CARDTYPE CARDSTATUS
MEANWSSCPU MEANWSSMEM
WSS Node to which this record applies Max CPU occupancy (percentage) Mean CPU occupancy Mean available memory
Type of WSS card (CCM, DDM, SAM, SIM, IPM) 9 Status of WSSNODENUM (i.e. ACTIVE or INACTIVE/STANDBY)
8
WSSNODENUM is the key field, and identifies the WSS node (card) to which this record applies.
Card type: 02 04 08 16 32 64 Card Status: 00 01 02 DDM card CCM card SAM card SIM card ERM card IPM card Loadshare Active Inactive/Standby
8 9
Added by PR 10889 Added by PR 10889 25/128
4.7 WSS Disk Performance Information (WSSDISKPERF)

Performance Group Name: WSSDISKPERF File Naming Convention: WSSDISKPERF.YYMMDD-HHMM
Position Field Name Description
1 2 3 4 5 6 7 8
WSSNODENUM DISKOCCPARROOT
CARDTYPE CARDSTATUS
DISKOCCPARAR DISKOCCPARSPACE
WSS Node to which this record applies Disk occupancy Disk occupancy Disk occupancy
Card type of WSS node number to which the record apply 11 Status of WSSNODENUM (i.e. ACTIVE or INACTIVE/STANDBY)
10
WSSNODENUM is the key field, and identifies the WSS Node (card) to which this record applies.
Card type: 02 04 08 16 32 64 Card Status: 00 01 02 DDM card CCM card SAM card SIM card ERM card IPM card Loadshare Active Inactive/Standby
10 11
Added by PR 10889 Added by PR 10889 26/128
SIGNALING PERFORMANCE DATA
5.1 MTP2 Link Information (SYSMTP2LINKPERF)
Performance Group Name: SYSMTP2LINKPERF File Naming Convention: SYSMTP2LINKPERF.YYMMDD-HHMM.###
Number of records: Equals the number of CCS7 links provisioned on the system
Position
### is the Node Number of the SIM card for which the statistics apply it will range over the SIM cards actually provisioned on the system
Field Name Description
1 2 3 4 5 6 7 8 9
STARTTIMESTAMP STOPTIMESTAMP GATEWAYNO
LNKID MTP2LNKPFMLINKINSVCTIME MTP2LNKPFMLINKFAILTOTAL MTP2LNKPFMLINKLCLBUSY
MTP2LNKPFMLINKFAILABNFIBBSNR MTP2LNKPFMLINKFAILT7EXP MTP2LNKPFMLINKFAILCONG MTP2LNKPFMALIGNFAIL MTP2LNKPFMSUERRS MTP2LNKPFMLINKFAILSUERM
10 11 12 13 14 15 16 17
Time since the signaling link was last aligned (in seconds) . Total number of signaling link failures due to all reasons. Total time (during this collection period in seconds) during which the link remained locally congested. Number of signaling link failures due to abnormal FIBR/BSNR (Forward Indicator Bit Received/Backward Sequence Number Received) 13 Number of signaling link failures due to T7 Expiry . Number of signaling link failures due to excessive congestion. Number of signaling link failures due to signal unit error rate. Number of signaling link alignment/proving failures. Number of received Signaling Units (SU) in error.
CCS7 Link.
Date and time performance interval stopped. Gateway Will always have a value of 1
12
Date and time performance interval started.
MTP2LNKPFMNACKRX MTP2LNKPFMMSUOCTETRETX MTP2LNKPFMMSUTX MTP2LNKPFMMSURX
Number of MSUs (Message Signal Units) transmitted. Number of MSUs (Message Signal Units) received.
Number of Negative acknowledgements received. Number of MSU (Message Signal Unit) octets retransmitted.
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. LNKID is the key field, and identifies the CCS7 link number to which this record applies. Since MTP2 is handled entirely within a given SIM card, LNKIDs will not be duplicated across different files in the same collection interval.
Please note that this field, unlike MTP3 duration fields, is in units of seconds (not milliseconds). This field will have a value of zero (0) if the link is not aligned at the end of the collection interval. If the link is aligned at the end of the collection interval, this time will reflect either the total time of the collection interval (if the link was aligned for the entire interval) or the time since the link was last aligned (if the link came into alignment during the collection interval). 13 T7 is the Excessive Delay of Acknowledgment Timer
12
27/128
5.2 MTP3 Link Information (SYSMTP3LINKPERF)
Performance Group Name: SYSMTP3LINKPERF File Naming Convention: SYSMTP3LINKPERF.YYMMDD-HHMM.###
Number of records: Equals the number of CCS7 links provisioned on the system
Position
### is the Node Number of the SIM card for which the statistics apply it will range over the SIM cards actually provisioned on the system
1 2 3 4 5 6 7 8 9
STOPTIMESTAMP WSSNODENUM GATEWAYNO LNKID
STARTTIMESTAMP
Date and time performance interval stopped. WSS Node (SIM Card) to which this record applies Gateway Will always have a value of 1 CCS7 Link.
MTP3LNKPFMCOOTX MTP3LNKPFMCOORX MTP3LNKPFMCOATX MTP3LNKPFMCOARX
Number of changeover order messages transmitted Number of changeover order messages received
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
MTP3LNKPFMCBDTX MTP3LNKPFMCBDRX MTP3LNKPFMCBATX MTP3LNKPFMCBARX
Number of changeover acknowledgement messages transmitted. Number of changeover acknowledgement messages received. Number of changeback declaration messages transmitted Number of changeback declaration messages received
MTP3LNKPFMECOTX MTP3LNKPFMECORX MTP3LNKPFMECATX MTP3LNKPFMECARX MTP3LNKPFMLINTX MTP3LNKPFMLINRX
Number of emergency changeover order messages transmitted. Number of emergency changeover order messages received. Number of emergency changeover ACK transmitted. Number of emergency changeover ACK received.
Number of changeback acknowledgement transmitted. Number of changeback acknowledgement messages received.
MTP3LNKPFMLUNTX MTP3LNKPFMLUNRX MTP3LNKPFMLIATX MTP3LNKPFMLIARX
Number of link uninhibit messages transmitted. Number of link uninhibit messages received.
Number of link inhibit messages transmitted. Number of link inhibits messages received.
MTP3LNKPFMLUATX MTP3LNKPFMLUARX MTP3LNKPFMLIDTX MTP3LNKPFMLIDRX
MTP3LNKPFMLFUTX MTP3LNKPFMLFURX MTP3LNKPFMLLITX MTP3LNKPFMLLIRX
Number of force link uninhibit messages transmitted. Number of force link uninhibit messages received.
Number of link inhibit denied messages transmitted. Number of link inhibit denied messages received.
Number of link uninhibit acknowledgement messages transmitted. Number of link uninhibit acknowledgement messages received.
Number of link inhibit acknowledgement messages transmitted. Number of link inhibit acknowledgement messages received.
MTP3LNKPFMLRITX MTP3LNKPFMLRIRX
MTP3LNKPFMCONNORDTX MTP3LNKPFMCONNORDRX MTP3LNKPFMCONNACKTX MTP3LNKPFMCONNACKRX MTP3LNKPFMLNKTSTRX MTP3LNKPFMLNKTSTTX
Number of link connection order messages transmitted. Number of link connection order messages received.
Number of remote link inhibit test messages transmitted. Number of remote link inhibit test messages received.
Number of local link inhibit test messages transmitted. Number of local link inhibit test messages received.
Number of link connection acknowledgement messages transmitted. Number of link connection acknowledgement messages received. Number of link test messages received. Number of link test messages transmitted.
28/128
Position
40 41 42 43 44 45 46 47 48 49 50 51 52
MTP3LNKPFMLNKTSTACKRX MTP3LNKPFMLNKTSTACKTX MTP3LNKPFMTXDROP MTP3LNKPFMTXCONGDROP MTP3LNKPFMSIFOCTTX MTP3LNKPFMSIFOCTRX MTP3LNKPFMSIOOCTTX
Field Name
Number of transmitted messages dropped. Number of MSUs (Message Signal Units) dropped due to link congestion. Number of SIF octet transmitted. Number of SIF octet received. Number of SIO octet transmitted.
Number of link test acknowledgement messages received. Number of link test acknowledgement messages transmitted.
Description
MTP3LNKPFMSIOOCTRX MTP3LNKPFMMSUTX MTP3LNKPFMMSURX MTP3LNKPFMUNAVDUR
Number of SIO octet received. Number of MSU transmitted.
MTP3LNKPFMDURLNKCONG MTP3LNKPFMERRPDURX
Number of MSU received. The duration of any current link unavailability during this collection 14 period . (100 millisecond units) The duration of any current link congestion during this collection 15 period . (100 millisecond units) Number of error messages received.
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. Records for the same LNKID can (but are not guaranteed) to be in each instance of this file (i.e. across multiple SIM cards) for a given performance interval. If a specific LNKID record is found in multiple files, the fields should be accumulated across the files in order to formulate a system wide view except that duration fields (50, 51) should assume the highest value found in any record for that LNKID (e.g. if a specific link has a value of 900 for field 50 in one file, but 0 in another file, the 900 value should be used). LNKID is the key field, and identifies the CCS7 link number to which this record applies.
Applicable only if the link is unavailable at the end of the collection interval. Includes the time since the link became unavailable (if this occurred during the current collection interval) or the entire time of the collection interval (if the link was unavailable throughout the collection interval). 15 Applicable only if the link is congested at the end of the collection interval. Includes the time since the link first became congested (if this occurred during the current collection interval) or the entire time of the collection interval (if the link was congested throughout the collection interval).
14
29/128
5.3 MTP3 Linkset Information (SYSMTP3LINKSETPERF)

Position
Performance Group Name: SYSMTP3LINKSETPERF File Naming Convention: SYSMTP3LINKSETPERF.YYMMDD-HHMM.###
Number of records: Equals the number of CCS7 linksets provisioned on the system.
1 2 3 4 5 6 STOPTIMESTAMP WSSNODENUM GATEWAYNO LNKSETID STARTTIMESTAMP
### is the Node Number of the DDM card for which the statistics are gathered it will range over the DDM cards actually provisioned on the system
Date and time performance interval stopped. WSS Node (DDM Card) to which this record applies Gateway Will always have a value of 1 CCS7 Link Set
MTP3LNKSETPFMUNAVAILDUR
Time duration (during this collection interval) of any current linkset unavailability in 100 millisecond units16
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. LNKSETID is the key field, and identifies the CCS7 linkset number to which this record applies. Records for this performance group generally will be generated only on one SIM card, but in some cases it is possible that non-zero-length files will be generated across multiple SIM cards. In this case, the same LNKSETID may (but is not guaranteed) be in each instance of this file. If a specific LNKSETID record is found in multiple files, the fields should assume the highest value found in any record for that LNKSETID (e.g. if a specific link has a value of 8500 for field 8 in one file, but 0 in another file, the 8500 value should be used).
Applicable only if the linkset is unavailable at the end of the collection interval. Includes the time since the linkset became unavailable (if this occurred during the current collection interval) or the entire time of the collection interval (if the linkset was unavailable throughout the collection interval).
16
30/128
5.4 MTP3 Route Information (SYSMTP3ROUTEPERF)

Position
Performance Group Name: SYSMTP3ROUTEPERF File Naming Convention: SYSMTP3ROUTEPERF.YYMMDD-HHMM.###
Number of records: Equals the number of Destination Point Codes provisioned

1 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM GATEWAYNO DPC STARTTIMESTAMP
### is the Node Number of the DDM card for which the statistics are gathered it will range over the DDM cards actually provisioned on the system
MTP3ROUTEPFMRSMTX MTP3ROUTEPFMRSMRX MTP3ROUTEPFMRCTTX MTP3ROUTEPFMRCTRX
10 MTP3ROUTEPFMTFPTX 11 MTP3ROUTEPFMTFPRX
Number of route set congestion test messages transmitted. Number of route set congestion test messages received. Number of transfer prohibited messages transmitted. Number of transfer prohibited messages received.
Number of route set test messages transmitted. Number of route set test messages received.
Gateway Will always have a value of 1 Destination Point Code.
Date and time performance interval stopped. WSS Node (DDM Card) to which this record applies
12 MTP3ROUTEPFMTFRTX 13 MTP3ROUTEPFMTFRRX 14 MTP3ROUTEPFMTFATX 15 MTP3ROUTEPFMTFARX
Number of transfer restrict messages transmitted. Number of transfer restricted messages received.
16 MTP3ROUTEPFMTFCTX 17 MTP3ROUTEPFMTFCRX
18 MTP3ROUTEPFMRTEUNAV 19 MTP3ROUTEPFMSIFTX
Number of transfer controlled messages transmitted. Number of transfer controlled messages received. Number of times route was unavailable. Number of SIF octet messages transmitted.
Number of transfer allowed messages transmitted. Number of transfer allowed messages received.
20 MTP3ROUTEPFMSIOTX 21 MTP3ROUTEPFMUNAVDUR
Number of SIO octet messages transmitted.
Duration of route unavailability (100 millisecond units)17
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. DPC is the key field, and identifies the destination point code about which this record applies. It is in the format of a single integer that can be converted to traditional <network><cluster><member> format as follows: 1. Convert the integer value to a 6-numeral hexadecimal value 2. The two most significant hexadecimal numerals represent the <network>, the middle two numerals represent the <cluster>, and the least two significant numerals represent the <member>. They can, of course, be converted individually back to decimal notation as required.
For a given performance interval, records for the same DPC can (but are not guaranteed to) be in each instance of this file (i.e. across multiple SIM cards). If a specific DPC record is found in multiple files, the fields should be accumulated across the files in order to formulate a system wide
Applicable only if the route (DPC) is unavailable at the end of the collection interval. Includes the time since the route became unavailable (if this occurred during the current collection interval) or the entire time of the collection interval (if the route was unavailable throughout the collection interval).
17
31/128
view except that fields 18 and 21 should assume the highest value found in any record for that DPC (e.g. if a specific link has a value of 900 for field 21 in one file, but 0 in another file, the 900 value should be used).
32/128
5.5 ISUP DPC Information (SYSISUPDPCPERF)
Performance Group Name: SYSISUPDPCPERF File Naming Convention: SYSISUPDPCPERF.YYMMDD-HHMM.###
Number of records: Equals the number of destination point codes (to which ISUP trunks have been assigned) provisioned in the system.
Position
### is the Node Number of the CCM card for which the statistics are gathered it will range over the active CCM cards actually provisioned on the system
1 2 3 4 5 6 7 8 9
STOPTIMESTAMP WSSNODENUM DPC GATEWAYNO
STARTTIMESTAMP
ISUPPFMACMTX ISUPPFMANMTX ISUPPFMBLATX ISUPPFMBLOTX
Destination Point Code. Gateway Number will always have a value of 1.
Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies
Number of address complete messages transmitted. Number of answer messages transmitted.
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
ISUPPFMCCRTX ISUPPFMCFNTX
ISUPPFMCGBTX ISUPPFMCGBATX
Number of continuity check request messages transmitted. Number of confusion messages transmitted.
Number of blocking acknowledgement messages transmitted. Number of blocking messages transmitted.
ISUPPFMCGUTX ISUPPFMCGUATX ISUPPFMCONTX ISUPPFMCOTTX
ISUPPFMCPGTX ISUPPFMCQMTX ISUPPFMCQRTX ISUPPFMCRGTX ISUPPFMFAATX ISUPPFMFACTX ISUPPFMFARTX ISUPPFMFOTTX
Number of call progress messages transmitted. Number of circuit query messages transmitted.
Number of circuit group unblocking messages transmitted. Number of circuit group unblocking acknowledgement messages transmitted. Number of connect messages transmitted. Number of continuity messages transmitted.
Number of circuit group blocking messages transmitted. Number of circuit group blocking acknowledgement messages transmitted.
Number of circuit query acknowledgement messages transmitted. Number of charging messages transmitted. Number of facility accepted messages transmitted. Number of facility messages transmitted.
ISUPPFMFRJTX ISUPPFMGRATX ISUPPFMGRSTX ISUPPFMIAMTX ISUPPFMIDRTX ISUPPFMINFTX ISUPPFMINRTX ISUPPFMIRSTX
Number of facility request messages transmitted. Number of forward transfer messages transmitted.
Number of circuit group reset messages transmitted. Number of initial address messages transmitted.
Number of facility rejected messages transmitted. Number of circuit group reset acknowledgement messages transmitted.
Number of identification request messages transmitted. Number of information messages transmitted.
ISUPPFMLOPTX ISUPPFMLPATX
Number of information request messages transmitted. Number of identification response messages transmitted.
ISUPPFMNRMTX ISUPPFMOLMTX ISUPPFMPAMTX ISUPPFMRELTX
Number of network resource management messages transmitted. Number of overload messages transmitted. Number of pass-along messages transmitted. Number of release messages transmitted.
Number of loop prevention messages transmitted. Number of loopback acknowledgement messages transmitted.
33/128
Position
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86
ISUPPFMRESTX ISUPPFMRLCTX
Field Name
ISUPPFMRSCTX ISUPPFMSAMTX
Number of resume messages transmitted. Number of release complete messages transmitted.
Description
ISUPPFMSGMTX ISUPPFMSUSTX ISUPPFMUBATX ISUPPFMUBLTX
Number of segmentation messages transmitted. Number of suspend messages transmitted.
Number of reset messages transmitted. Number of subsequent address messages transmitted.
ISUPPFMUCICTX ISUPPFMUPATX ISUPPFMUPTTX ISUPPFMUSRTX
Number of unequipped CIC messages transmitted. Number of user part available messages transmitted. Number of user part test messages transmitted. Number of user to user messages transmitted.
Number of unblocking acknowledgement messages transmitted. Number of unblocking messages transmitted.
ISUPPFMCRATX ISUPPFMCRMTX ISUPPFMCVRTX ISUPPFMCVTTX
Number of circuit reservation acknowledgement messages transmitted. Number of circuit reservation messages transmitted. Number of circuit validation response messages transmitted. Number of circuit validation messages transmitted.
ISUPPFMEXMTX ISUPPFMACMRX ISUPPFMANMRX ISUPPFMBLARX ISUPPFMBLORX ISUPPFMCCRRX
Number of exit messages transmitted. Number of address complete messages received.
ISUPPFMCFNRX ISUPPFMCGBRX
ISUPPFMCGBARX ISUPPFMCGURX
ISUPPFMCGUARX ISUPPFMCONRX ISUPPFMCOTRX ISUPPFMCPGRX
Number of circuit group blocking acknowledgement messages received. Number of circuit group unblocking messages received.
Number of confusion messages received. Number of circuit group blocking messages received.
Number of blocking messages received. Number of continuity check request messages received.
Number of answer messages received. Number of blocking acknowledgement messages received.
Number of circuit group unblocking acknowledgement messages received. Number of connect messages received. Number of continuity messages received. Number of call progress messages received.
ISUPPFMCQMRX ISUPPFMCQRRX ISUPPFMCRGRX ISUPPFMFAARX ISUPPFMFACRX ISUPPFMFARRX ISUPPFMFOTRX ISUPPFMFRJRX
Number of circuit query messages received. Number of circuit query acknowledgement messages received. Number of charging messages received. Number of facility accepted messages received. Number of facility messages received. Number of facility request messages received.
ISUPPFMGRARX ISUPPFMGRSRX ISUPPFMIAMRX ISUPPFMIDRRX ISUPPFMINFRX ISUPPFMINRRX
Number of forward transfer messages received. Number of facility rejected messages received.
ISUPPFMIRSRX ISUPPFMLOPRX ISUPPFMLPARX
Number of information messages received. Number of information request messages received.
Number of initial address messages received. Number of identification request messages received.
Number of circuit group reset acknowledgement messages received. Number of circuit group reset messages received.
Number of identification response messages received. Number of loop prevention messages received.
Number of loopback acknowledgement messages received.
34/128
Position
87 88 89 90 91 92 93 94 95 96 97 98
ISUPPFMNRMRX ISUPPFMOLMRX ISUPPFMPAMRX ISUPPFMRELRX ISUPPFMRESRX ISUPPFMRLCRX
Field Name
Number of network resource management messages received. Number of overload messages received. Number of pass-along messages received. Number of release messages received.
Description
ISUPPFMRSCRX ISUPPFMSAMRX
Number of resume messages received. Number of release complete messages received.
ISUPPFMSGMRX ISUPPFMSUSRX ISUPPFMUBARX ISUPPFMUBLRX
Number of segmentation messages received. Number of suspend messages received.
Number of reset messages received. Number of subsequent address messages received.
99 ISUPPFMUCICRX 100 ISUPPFMUPARX 101 ISUPPFMUPTRX 102 ISUPPFMUSRRX
Number of unequipped CIC messages received. Number of user part available messages received. Number of user part test messages received. Number of user-to-user messages received.
Number of unblocking acknowledgement messages received. Number of unblocking messages received.
103 ISUPPFMCRARX 104 ISUPPFMCRMRX 105 ISUPPFMCVRRX 106 ISUPPFMCVTRX
Number of circuit reservation acknowledgement messages received. Number of circuit reservation messages received. Number of circuit validation response messages received. Number of circuit validation messages received.
107 ISUPPFMEXMRX
Number of exit messages received.
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. DPC is the key field, and identifies the destination point code about which this record applies. It is in the format of a single integer that can be converted to traditional <network><cluster><member> format as follows:
For a given performance interval, records for the same DPC can (but are not guaranteed to) be in each instance of this file (i.e. across multiple SIM cards). If a specific DPC record is found in multiple files, the fields should be aggregated across the files in order to formulate a system wide view.
1. Convert the integer value to a 6-numeral hexadecimal value 2. The two most significant hexadecimal numerals represent the <network>, the middle two numerals represent the <cluster>, and the least two significant numerals represent the <member>. They can, of course, be converted individually back to decimal notation as required.
35/128
5.6 BICC DPC Information (SYSBICCDPCPERF)

Performance Group Name: File Naming Convention:
Position
Number of records: Equals the number of destination point codes provisioned in the system.
1 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM DPC GATEWAYNO Field Name STARTTIMESTAMP Date and time performance interval started.
Description
SYSBICCDPCPERF SYSBICCDPCPERF.YYMMDD-HHMM.###
BICCPFMACMTX BICCPFMANMTX BICCPFMBLATX BICCPFMBLOTX
Number of Address Complete messages transmitted. Number of Answer messages transmitted.
Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name. Destination Point Code. Gateway Number will always have a value of 1.
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
BICCPFMCCRTX BICCPFMCFNTX
BICCPFMCGBTX BICCPFMCGBATX BICCPFMCGUTX BICCPFMCONTX BICCPFMCOTTX BICCPFMCPGTX BICCPFMCGUATX
Number of Circuit Group Blocking messages transmitted. Number of Circuit Group Blocking Acknowledgement messages transmitted. Number of Circuit Group Unblocking messages transmitted. Number of Circuit Group Unblocking Acknowledgement messages transmitted. Number of Connect messages transmitted. Number of Continuity messages transmitted. Number of Call Progress messages transmitted.
Number of Continuity Check Request messages transmitted. Number of Confusion messages transmitted.
Number of Blocking Acknowledgement messages transmitted. Number of Blocking messages transmitted.
BICCPFMCQMTX BICCPFMCQRTX BICCPFMCRGTX BICCPFMFAATX BICCPFMFACTX BICCPFMFARTX BICCPFMFOTTX
Number of Circuit Query messages transmitted. Number of Circuit Query Acknowledgement messages transmitted. Number of Charging messages transmitted. Number of Facility Accepted messages transmitted. Number of Facility messages transmitted.
BICCPFMFRJTX BICCPFMGRATX BICCPFMGRSTX BICCPFMIAMTX BICCPFMIDRTX BICCPFMINFTX BICCPFMINRTX BICCPFMIRSTX
Number of Facility request messages transmitted. Number of Forward Transfer messages transmitted.
Number of Facility Rejected messages transmitted. Number of Circuit Group Reset Acknowledgement messages transmitted. Number of Circuit Group Reset messages transmitted. Number of Initial Address messages transmitted. Number of Identification Request messages transmitted. Number of Information messages transmitted.
BICCPFMLOPTX BICCPFMLPATX
Number of Information request messages transmitted. Number of Identification Response messages transmitted.
BICCPFMNRMTX BICCPFMOLMTX
Number of network Resource Management messages transmitted. Number of Overload messages transmitted.
Number of Loop Prevention messages transmitted. Number of Loopback Acknowledgement messages transmitted.
36/128
Position
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80
Field Name BICCPFMPAMTX BICCPFMRELTX BICCPFMRESTX BICCPFMRLCTX
BICCPFMRSCTX BICCPFMSAMTX
Number of Resume messages transmitted. Number of Release Complete messages transmitted.
Number of Pass-Along messages transmitted. Number of Release messages transmitted.
Description
BICCPFMSGMTX BICCPFMSUSTX BICCPFMUBATX BICCPFMUBLTX BICCPFMUCICTX BICCPFMUPATX BICCPFMUPTTX
Number of Unblocking Acknowledgement messages transmitted. Number of Unblocking messages transmitted. Number of Unequipped CIC messages transmitted.
Number of Segmentation messages transmitted. Number of Suspend messages transmitted.
Number of Reset messages transmitted. Number of Subsequent Address messages transmitted.
BICCPFMUSRTX BICCPFMCRATX BICCPFMCRMTX BICCPFMCVRTX BICCPFMCVTTX BICCPFMEXMTX
Number of User-To-User messages transmitted. Number of Circuit Reservation Acknowledgement messages transmitted. Number of Circuit Reservation messages transmitted. Number of Circuit Validation Response messages transmitted. Number of Circuit Validation messages transmitted. Number of Exit messages transmitted.
Number of User Parts Available messages transmitted. Number of User Part Test messages transmitted.
BICCPFMAPMTX BICCPFMACMRX BICCPFMANMRX BICCPFMBLARX BICCPFMBLORX
Number of Application Transport Mechanism (APM) messages transmitted. Number of Address Complete messages received. Number of Answer messages received. Number of Blocking Acknowledgement messages received. Number of Blocking messages received.
BICCPFMCCRRX BICCPFMCFNRX
BICCPFMCGBRX BICCPFMCGBARX BICCPFMCGURX BICCPFMCGUARX BICCPFMCONRX BICCPFMCOTRX BICCPFMCPGRX
Number of Circuit Group Blocking messages received. Number of Circuit Group Blocking Acknowledgement messages received. Number of Circuit Group Unblocking messages received. Number of Circuit Group Unblocking Acknowledgement messages received. Number of Connect messages received. Number of Continuity messages received. Number of Call Progress messages received.
Number of Continuity Check Request messages received. Number of Confusion messages received.
BICCPFMCQMRX BICCPFMCQRRX BICCPFMCRGRX BICCPFMFAARX BICCPFMFACRX BICCPFMFARRX BICCPFMFOTRX BICCPFMFRJRX
Number of Circuit Query messages received. Number of Circuit Query Acknowledgement messages received. Number of Charging messages received. Number of Facility Accepted messages received. Number of Facility messages received. Number of Facility Request messages received.
BICCPFMGRARX BICCPFMGRSRX
Number of Forward Transfer messages received. Number of Facility Rejected messages received.
Number of Circuit Group Reset Acknowledgement messages received. Number of Circuit Group Reset messages received.
37/128
Position
81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98
Field Name BICCPFMIAMRX BICCPFMIDRRX BICCPFMINFRX BICCPFMINRRX
BICCPFMIRSRX BICCPFMLOPRX
Number of Information messages received. Number of Information Request messages received.
Number of Initial Address messages received. Number of Identification Request messages received.
Description
BICCPFMLPARX BICCPFMNRMRX BICCPFMOLMRX BICCPFMPAMRX BICCPFMRELRX BICCPFMRESRX
Number of Overload messages received. Number of Pass-Along messages received. Number of Release messages received. Number of Resume messages received.
Number of Loopback Acknowledgement messages received. Number of network Resource Management messages received.
Number of Identification Response messages received. Number of Loop Prevention messages received.
BICCPFMRLCRX BICCPFMRSCRX
BICCPFMSAMRX BICCPFMSGMRX BICCPFMSUSRX BICCPFMUBARX
Number of Release Complete messages received. Number of Reset messages received.
Number of Subsequent address messages received. Number of Segmentation messages received.
99 BICCPFMUBLRX 100 BICCPFMUCICRX 101 BICCPFMUPARX 102 BICCPFMUPTRX
Number of Unblocking messages received. Number of Unequipped CIC received.
Number of Suspend messages received. Number of Unblocking Acknowledgement messages received.
103 BICCPFMUSRRX 104 BICCPFMCRARX 105 BICCPFMCRMRX 106 BICCPFMCVRRX 107 BICCPFMCVTRX
Number of User-To-User messages received. Number of Circuit Reservation Acknowledgement messages received. Number of Circuit Reservation messages received. Number of Circuit Validation Response messages received. Number of Circuit Validation messages received.
Number of User Parts Available messages received. Number of User Part Test messages received.
108 BICCPFMEXMRX 109 BICCPFMAPMRX
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. DPC is the key field, and identifies the destination point code for which this record applies. It is in the format of a single integer that can be converted to traditional <network><cluster><member> format as follows: 1. Convert the integer value to a 6-numeral hexadecimal value 2. The two most significant hexadecimal numerals represent the <network>, the middle two numerals represent the <cluster>, and the least two significant numerals represent the <member>. They can, of course, be converted individually back to decimal notation as required.
Number of Exit messages received. Number of Application Transport Mechanism (APM) messages received.
For a given performance interval, records for the same DPC can (but are not guaranteed to) be in each instance of this file (i.e. across multiple SIM cards). If a specific DPC record is found in multiple files, the fields should be aggregated across the files in order to formulate a system wide view.
5.7 SCCP Information (SYSSCCPPERF)

Position
Performance Group Name: SYSSCCPPERF File Naming Convention: SYSSCCPPERF.YYMMDD-HHMM.### Number of records: One per file.
1 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM STARTTIMESTAMP
Field Name
### is the Node Number of the SIM card for which the statistics are gathered it will range over the active SIM cards actually provisioned on the system
Description
GATEWAYNO SCCPGENPFMRFNTASN SCCPGENPFMRFNTSA SCCPGENPFMRFNETFAIL SCCPGENPFMRFNETCONG SCCPGENPFMRFSSNFAIL
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
SCCPGENPFMRFSSNCONG SCCPGENPFMRFUNEQUIP
Date and time performance interval stopped. WSS Node (SIM Card) to which this record applies. Will always equal node number in the file name Gateway Number will always have a value of 1. Number of routing failures due to no translation for address of such nature. Number of routing failures due to no translation for this specific address. Number of routing failure due to network failure (point code unavailable). Number of routing failures due to network congestion. Number of routing failures due to sub-system failure. Number of routing failures due to sub-system congestion. Number of routing failures due to unequipped user. Number of routing failures due to hop counter violation. Number of routing failures due to syntax error.
SCCPGENPFMRFHOPVIOLATE SCCPGENPFMSYNERROR SCCPGENPFMRFUNKNOWN SCCPGENPFMUDTTX SCCPGENPFMUDTSTX SCCPGENPFMUDTRX
Number of routing failures due to unknown reason. Number of unit data message transmitted.
SCCPGENPFMUDTSRX SCCPGENPFMXUDTTX
SCCPGENPFMXUDTSTX SCCPGENPFMXUDTRX
SCCPGENPFMXUDTSRX SCCPGENPFMTOTALMSG
Number of extended unit data service messages transmitted. Number of extended unit data messages received. Number of extended unit data service messages received. Number of messages handled (total inbound).
Number of unit data service messages received. Number of extended unit data messages transmitted.
Number of unit data service messages transmitted. Number of unit data messages received.
SCCPGENPFMMSGLOC SCCPGENPFMGTTRANREQ SCCPGENPFMMSGTXC0 SCCPGENPFMMSGTXC1
SCCPGENPFMMSGRXC0 SCCPGENPFMMSGRXC1 SCCPGENPFMIUDTTX SCCPGENPFMIUDTSTX
Number of class 0 messages received. Number of class 1 messages received.
Number of inbound messages intended for local sub-system. Number of messages requiring Global Title Translation (GTT). Number of class 0 messages transmitted. Number of class 1 messages transmitted.
SCCPGENPFMIUDTRX SCCPGENPFMIUDTSRX
SCCPGENPFMTIMEREXP SCCPGENPFMPRVINITRESET SCCPGENPFMPRVINITREL SCCPGENPFMSSCONGRX
Number of times the SCCP connection inactivity timer expired. Number of times the SCCP layer initiated resets. Number of times the SCCP layer initiated releases. Number of times the SS Congest messages received
Number of ITU96 unit data messages received. Number of ITU96 unit data messages service received.
Number of ITU96 unit data messages transmitted. Number of ITU96 unit data service messages transmitted.
39/128
Position
To provide a system-wide view of the information in this performance group, the values must be accumulated across all SIM cards.
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
SCCPGENPFMSSPROHRX SCCPGENPFMSEGERR SCCPGENPFMSEGERRFAIL SCCPGENPFMREASSEMERR SCCPGENPFMERRTIMEXP SCCPGENPFMERRNOSPC SCCPGENPFMCRTX SCCPGENPFMCRRX SCCPGENPFMCREFTX SCCPGENPFMCREFRX SCCPGENPFMRSRTX SCCPGENPFMRSRRX SCCPGENPFMERRTX SCCPGENPFMERRRX SCCPGENPFMRLSCMPFAIL
Field Name
Number of times the SS Prohibit messages received Number of times the Segment message too large Number of times the Segment message fail Number of times the Reassembly out of sequence error Number of times the Reassembly time expired error Number of times the Reassembly no space error Number of times the CR messages sent Number of times the CR messages received Number of times the CREF messages sent Number of times the CREF messages received Number of times the RSR messages sent Number of times the RSR messages received Number of times the ERR messages sent Number of times the ERR messages received Number of times the Release Complete fail
Description
40/128
5.8 CAP (CAMEL Application Part) Information (CAPMSGPERF)

Position
Number of records: One per file.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 STOPTIMESTAMP WSSNODENUM INITDPINVTX ESTTMPCONRETX DISCFWDCONRETX CONTORESRETX CONRETX REQRPTBCSMRETX EVTRPTBCSMINVTX RSTTMRRETX APPCHRGRETX STARTTIMESTAMP
Field Name
### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system
Description
CAPMSGPERF CAPMSGPERF.YYMMDD-HHMM.###
Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Initial Detection Point (IDP): Invoke messages transmitted. Number of Establish Temporary Connection (ETC): Return Error messages transmitted. Number of Disconnect Forward Connection: Return Error messages transmitted. Number of Connect to Resource: Return Error messages transmitted. Number of Connect: Return Error messages transmitted. Number of Request Report BCSM Event: Return Error messages transmitted. Number of Event Report BCSM: Invoke messages transmitted. Number of Reset Timer: Return Error messages transmitted. Number of Apply Charging: Return Error messages transmitted.
APPCHRGRPTINVTX CALLINFORPTINVTX CALLINFOREQRETX SNDCHRGINFORETX CNCLRETX ACTVTSTRRTX
CONTWITHARGRETX INITDPSMSINVTX FURCHRGINFOSMSRETX CONSMSRETX REQRPTSMSRETX EVTRPTSMSINVTX RSTTMRSMSRETX INITDPPH2INVTX ESTTMPCONPH2RETX DISCFWDCONPH2RETX CONTORESPH2RETX
Number of Continue with Argument: Return Error messages transmitted. Number of Initial Detection Point (DP) SMS: Invoke messages transmitted. Number of Furnish Charging Information SMS: Return Error messages transmitted. Number of Connect SMS: Return Error messages transmitted. Number of Request Report SMS Event: Return Error messages transmitted. Number of Event Report SMS: Invoke messages transmitted. Number of Reset Timer SMS: Return Error messages transmitted. Number of Initial Detection Point (IDP) Phase-2: Invoke messages transmitted. Number of Establish Temporary Connection Ph2: Return Error messages transmitted. Number of Disconnect Forward Connection Ph2: Return Error messages transmitted. Number of Connect to Resource Ph2: Return Error messages transmitted.
Number of Apply Charging Report: Invoke messages transmitted. Number of Call Information Report: Invoke messages transmitted. Number of Call Information Request: Return Error messages transmitted. Number of Send Charging Info: Return Error messages transmitted. Number of Cancel: Return Error messages transmitted. Number of Activity Test: Return Result messages transmitted.
41/128
Position
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68
CONPH2RETX REQRPTBCSMPH2RETX EVTRPTBCSMPH2INVTX RSTTMRPH2RETX FURCHRGINFOPH2RETX APPCHRGPH2RETX APPCHRGRPTPH2INVTX CALLGAPPH2INVTX CALLINFORPTPH2INVTX SNDCHRGINFOPH2RETX CNCLPH2RETX ACTVTSTPH2RRTX INITDPRERX ESTTMPCONINVRX DISCFWDCONINVRX CONTORESINVRX CONINVRX
Field Name
RELCALLINVRX REQRPTBCSMINVRX CONTINVRX FURCHRGINFOINVRX APPCHRGINVRX CALLGAPINVRX APPCHRGRPTRERX CALLINFOREQINVRX SNDCHRGINFOINVRX CNCLINVRX ACTVTSTINVRX
Number of Connect Ph2: Return Error messages transmitted. Number of Request Report BCSM Event Ph2: Return Error messages transmitted. Number of Event Report BCSM Ph2: Invoke messages transmitted. Number of Reset timer Ph2: Return Error messages transmitted. Number of Furnish Charging Information Ph2: Return Error messages transmitted. Number of Apply Charging Ph2: Return Error messages transmitted. Number of Apply Charging report Ph2: Invoke messages transmitted. Number of Call Gap Ph2: Invoke messages transmitted. Number of Call Information Report Ph2: Invoke messages transmitted. Number of Send Charging Info Ph2: Return Error messages transmitted. Number of Cancel Ph2: Return Error messages transmitted. Number of Activity Test Ph2: Return Result messages transmitted. Number of Initial DP (IDP): Return Error messages received. Number of Establish Temporary Connection (ETC): Invoke messages received. Number of Disconnect Forward Connection: Invoke messages received. Number of Connect To Resource: Invoke messages received. Number of Connect: Invoke messages received. Number of Release Call: Invoke messages received. Number of Request Report BCSM Event: Invoke messages received. Number of Continue: Invoke messages received.
Description
Number of Furnish Charging Information: Invoke messages received. Number of Apply Charging: Invoke messages received. Number of Apply Charging Report: Return Error messages received. Number of Call Gap: Invoke messages received.
Number of Call Information Request: Invoke messages received. Number of Send Charging Info: Invoke messages received. Number of Cancel: Invoke messages received. Number of Activity Test: Invoke messages received.
CONTWITHARGINVRX INITDPSMSRERX FURCHRGINFOSMSINVRX CONSMSINVRX REQRPTSMSINVRX CONTSMSINVRX RELSMSINVRX RSTTMRSMSINVRX INITDPPH2RERX ESTTMPCONPH2INVRX DISCFWDCONPH2INVRX
Number of Continue with Argument: Invoke messages received. Number of Initial DP SMS: Return Error messages received. Number of Furnish Charging Information SMS: Invoke messages received. Number of Connect SMS: Invoke messages received. Number of Request Report SMS Event: Invoke messages received. Number of Continue SMS: Invoke messages received. Number of Release SMS: Invoke messages received. Number of Reset Timer SMS: Invoke messages received. Number of Initial DP Ph2: Return Error messages received. Number of Establish Temporary Connection Ph2: Invoke messages received. Number of Disconnect Forward Connection Ph2: Invoke messages received.
42/128
Position
69 70 71 72 73 74 75 76 77 78 79 80 81 82
CONTORESPH2INVRX CONPH2INVRX RELCALLPH2INVRX REQRPTBCSMPH2INVRX CONTPH2INVRX RSTTMRPH2INVRX FURCHRGINFOPH2INVRX APPCHRGPH2INVRX APPCHRGRPTPH2RERX CALLINFOREQPH2INVRX CALLINFOREQPH2RERX SNDCHRGINFOPH2INVRX CNCLPH2INVRX ACTVTSTPH2INVRX
Field Name
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send an Establish Temporary Connection: Invoke).
Number of Connect to Resource Ph2: Invoke messages received. Number of Connect Ph2: Invoke messages received. Number of Release Call Ph2: Invoke messages received. Number of Request Report BCSM Event Ph2: Invoke messages received. Number of Continue Ph2: Invoke messages received. Number of Reset Timer Ph2: Invoke messages received. Number of Furnish Charging Information Ph2: Invoke messages received. Number of Apply Charging Ph2: Invoke messages received. Number of Apply Charging Report Ph2: Return Error messages received. Number of Call Information Request Ph2: Invoke messages received. Number of Call Information Request Ph2: Return Error messages received. Number of Send Charging Info Ph2: Invoke messages received. Number of Cancel Ph2: Invoke messages received. Number of Activity Test Ph2: Invoke messages received.
Description
43/128
5.9 INAP Information (INAPMSGPERF)
Performance Group Name: INAPMSGPERF File Naming Convention: INAPMSGPERF.YYMMDD-HHMM ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file.
Position
1 2 3 4 5 6 7 8 9
STOPTIMESTAMP WSSNODENUM INITDPRETX OATTAUTHINVTX CTEDINFOINVTX ASEDINFOINVTX
STARTTIMESTAMP
Field Name
ROUTSELFAILINVTX OCDPTYBUSYINVTX ONOANSWERINVTX OANSWERINVTX ODISCINVTX TATTAUTHINVTX TCDPTYBUSYINVTX TNOANSWERINVTX TANSWERINVTX TDISCINVTX OMIDCALLINVTX TMIDCALLINVTX
Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Initial DP: Return Error messages transmitted. Number of Origination Attempt Authorized: Invoke messages transmitted. Number of Collected Information: Invoke messages transmitted. Number of Analyzed Information: Invoke messages transmitted. Number of Route Select Failure: Invoke messages transmitted. Number of Origination Called Party Busy: Invoke messages transmitted. Number of Origination No Answer: Invoke messages transmitted. Number of Origination Answer: Invoke messages transmitted. Number of Origination Disconnect: Invoke messages transmitted. Number of Termination Attempt Authorized: Invoke messages transmitted. Number of Termination Called Party Busy: Invoke messages transmitted. Number of Termination No Answer: Invoke messages transmitted. Number of Termination Answer: Invoke messages transmitted.
Description
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
ASTREQINSTRINVTX ESTTMPCONRETX DISCFWDCONRETX CONTORESRETX CONRETX HOLDCALLNETRETX REQRPTBCSMRETX EVTRPTBCSMINVTX REQNOTCHGRETX EVTNOTCHGINVTX CLCTINFORETX
Number of Assist Request Instructions: Invoke messages transmitted. Number of Establish Temporary Connection: Return Error messages transmitted. Number of Disconnect Forward Connection: Return Error messages transmitted. Number of Connect To Resource: Return Error messages transmitted. Number of Connect: Return Error messages transmitted. Number of Hold Call In Network: Return Error messages transmitted. Number of Request Report BCSM Event Return Error messages transmitted. Number of Event Report BCSM: Invoke messages transmitted. Number of Request Notification Charging Event: Return Error messages transmitted. Number of Event Notification Charging: Invoke messages transmitted. Number of Collect Information: Return Error messages transmitted.
Number of Termination Disconnect: Invoke messages transmitted. Number of Origination Mid Call: Invoke messages transmitted. Number of Termination Mid Call: Invoke messages transmitted.
44/128
Position
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62
ASEINFORETX
Field Name
SELROUTRETX SELFACRETX RSTTMRRETX
INITCALLATTRETX FURCHGINFORETX APPCHGRETX APPCHGRPTINVTX REQCRNTSTATRRTX REQCRNTSTATRETX REQEVERYSTATRETX REQFIRSTSTATRETX ACTVSVCFTDRETX SVCFTDRSPINVTX CALLINFORPTINVTX CALLINFOREQRETX SNDCHGINFORETX CNCLRETX CNCLSTATREQRETX INITDPINVRX OATTAUTHRERX CTEDINFORERX ASEDINFORERX ROUTSELFAILRERX OCDPTYBUSYRERX ONOANSWERRERX OANSWERRERX ODISCRERX TATTAUTHRERX TCDPTYBUSYRERX TNOANSWERRERX TANSWERRERX
Number of Furnish Charging Information: Return Error messages transmitted. Number of Apply Charging: Return Error messages transmitted. Number of Apply Charging Report: Invoke messages transmitted. Number of Request Current Status Report: Return Result messages transmitted. Number of Request Current Status Report: Return Error messages transmitted. Number of Request Every Status Report: Return Error messages transmitted. Number of Request First Status Match Report: Return Error messages transmitted. Number of Activate Service Filtering: Return Error messages transmitted. Number of Service Filtering Response: Invoke messages transmitted. Number of Call Information Report: Invoke messages transmitted. Number of Call Information Request: Return Error messages transmitted. Number of Send Charging Info: Return Error messages transmitted. Number of Cancel: Return Error messages transmitted. Number of Cancel Status Report: Request Return Error messages transmitted. Number of Initial DP: Invoke messages received. Number of Origination Attempt Authorized: Return Error messages received. Number of Collected Information: Return Error messages received. Number of Analyzed Information; Return Error messages received. Number of Route Select Failure: Return Error messages received. Number of Origination Called Party Busy: Return Error messages received. Number of Origination No Answer: Return Error messages received. Number of Origination Answer: Return Error messages received. Number of Origination Disconnect: Return Error messages received. Number of Termination Attempt Authorized: Return Error messages received. Number of Termination Called Party Busy: Return Error messages received. Number of Termination No Answer: Return Error messages received. Number of Termination Answer: Return Error messages received.
Number of Initiate Call Attempt: Return Error messages transmitted. Number of Reset Timer: Return Error messages transmitted.
Number of Analyze Information: Return Error messages transmitted. Number of Select Route: Return Error messages transmitted. Number of Select Facility: Return Error messages transmitted.
Description
45/128
Position
63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
TDISCRERX
Field Name
OMIDCALLRERX TMIDCALLRERX ASTREQINSTRRERX ESTTMPCONINVRX DISCFWDCONINVRX CONTORESINVRX CONINVRX HOLDCALLNETINVRX RELCALLINVRX REQRPTBCSMINVRX REQNOTCHGINVRX CLCTINFOINVRX ASEINFOINVRX SELROUTINVRX SELFACINVRX CONTINVRX INITCALLATTINVRX RSTTMRINVRX FURCHGINFOINVRX APPCHGINVRX APPCHGRPTRERX REQCRNTSTATINVRX REQEVERYSTATINVRX REQFIRSTSTATINVRX STATRPTINVRX CALLGAPINVRX ACTVSVCFTDINVRX CALLINFOREQINVRX SNDCHGINFOINVRX CNCLINVRX CNCLSTATREQINVRX ACTVTSTINVRX
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send an Establish Temporary Connection: Invoke).
Number of Termination Disconnect; Return Error messages received. Number of Origination Mid Call: Return Error messages received. Number of Termination Mid Call: Return Error messages received. Number of Assist Request Instructions: Return Error messages received. Number of Establish Temporary Connection: Invoke messages received. Number of Disconnect Forward Connection: Invoke messages received. Number of Connect To Resource: Invoke messages received. Number of Connect: Invoke messages received. Number of Hold Call In Network: Invoke messages received. Number of Release Call: Invoke messages received. Number of Request Report BCSM Event: Invoke messages received. Number of Request Notification Charging Event: Invoke messages received. Number of Collect Information: Invoke messages received. Number of Analyze Information: Invoke messages received. Number of Select Route: Invoke messages received. Number of Select Facility: Invoke messages received. Number of Continue: Invoke messages received. Number of Initiate Call Attempt: Invoke messages received. Number of Reset Timer: Invoke messages received. Number of Furnish Charging Information: Invoke messages received. Number of Apply Charging: Invoke messages received. Number of Apply Charging Report: Return Error messages received. Number of Request Current Status Report: Invoke messages received. Number of Request Every Status Report: Invoke messages received. Number of Request First Status Match Report: Invoke messages received. Number of Status Report: Invoke messages received. Number of Call Gap: Invoke messages received. Number of Activate Service Filtering: Invoke messages received. Number of Call Information Request: Invoke messages received. Number of Send Charging Info Send Charging Info: Invoke messages received. Number of Cancel: Invoke messages received. Number of Cancel Status Report Request: Invoke messages received. Number of Activity Test: Invoke messages received.
Description
5.10 IS-41 Information (IS41MSGPERF)
Performance Group Name: IS41MSGPERF File Naming Convention: IS41MSGPERF.YYMMDD-HHMM.### ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file. NOTE: This performance group is for GMSC-Applicable Messages only and is not applicable to GSM DMSC application
Position
1 2 3 4 5
WSSNODENUM
Field Name
REDIRREQRRTX REDIRREQRETX XFERTONMBINVTX REDIRREQINVRX LOCREQRRRX LOCREQRERX XFERTONMBRRRX XFERTONMBRERX LOCREQINVTX
7
8 9 10 11 12
WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Redirection Request: Return Result messages transmitted. Number of Redirection Request: Return Error messages transmitted. Number of Location Request: Invoke messages transmitted.
Date and time performance interval started. Date and time performance interval stopped.
Description
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an ANSI 41GMSC are included.
Number of Location Request: Return Result messages received. Number of Location Request: Return Error messages received. Number of Transfer To Number Request: Return Result messages received Number of Transfer To Number Request: Return Error messages received.
Number of Transfer To Number Request: Invoke messages transmitted. Number of Redirection Request: Invoke messages received.
47/128
5.11 MAP Information
Five different software modules in WSS capture performance pegs for all the MAP messages. These pegs are therefore split across five performance groups, applying to functions as follows: 1. 2. 3. 4. 5. Mobility Management Related MAP messaging (DMSC) Subscriber Information Related MAP Messaging (GMSC / DMSC) SMS Related MAP Messaging (DMSC) CISS Related MAP Messaging (DMSC) Location-Services Related MAP Messaging (DMSC)
The following sub sections list each software modules performance pegs.
5.11.1 Mobility Management Related MAP Message (MAPMMMSGPERF) Performance Group Name: MAPMMMSGPERF File Naming Convention: MAPMMMSGPERF.YYMMDD-HHMM.### ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file.
Position Field Name 1 STARTTIMESTAMP 2 STOPTIMESTAMP 3 4 5 6 7 8 9 WSSNODENUM CHKIMEIREQTX CANLOCRSPTX Description Date and time performance interval started. Date and time performance interval stopped.
CANLOCRETX PURGMSREQTX AUTHINFREQTX INSSUBRSPTX
10 11
13
14 15 16 17 18 19 20 21 22 23 24 25 26
12
DELSUBRETX ACTVTRRSPTX
INSSUBRETX DELSUBRSPTX
Number of Authentication Info: Request messages transmitted Number of Insert Subscriber Data: Response messages transmitted
Number of Cancel Location: Return messages transmitted Number of Mobile Station Purge: Request messages transmitted
WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Check IMEI: Request messages transmitted Number of Cancel Location: Response messages transmitted
ACTVTRRETX DACTVTRRSPTX
DACTVTRRETX AUTHFAILRPTREQTX UPLOCREQTX RESTOREREQTX
SNDIMSIREQTX PROVROAMNMBRSPTX PROVROAMNMBRETX NOTMMEVREQTX SNDIDREQTX SNDIDRSPTX SNDIDRETX
Number of Update Location: Request messages transmitted Number of Restore: Request messages transmitted
Number of Deactivate Trace: Return messages transmitted Number of Authentication Fail Report: Request messages transmitted
Number of Activate Trace: Return messages transmitted Number of Deactivate Trace: Response messages transmitted
Number of Delete Subscriber Data: Return Error messages transmitted Number of Activate Trace: Response messages transmitted
Number of Insert Subscriber Data: Return Error messages transmitted Number of Delete Subscriber Data: Response messages transmitted
Number of Provide Roaming Number: Return Error messages transmitted Number of MAP Notify MM: Event messages transmitted
Number of Send IMSI: Request messages transmitted Number of Provide Roaming Number: Response messages transmitted
Number of Send Identification: Request messages transmitted Number of Send Identification: Response messages transmitted
Number of Send Identification: Return Error messages transmitted
48/128
Position Field Name 27 PREHOREQTX 28 PREHORSPTX 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 PREHORETX PRESUBHOREQTX PRESUBHORSPTX PRESUBHORETX SNDENDSIGREQTX SNDENDSIGRSPTX PROCACCSIGREQTX FWDACCSIGREQTX PROVSUBSINFORSPTX PROVSUBSINFORETX FWDCHKSSINDREQRX CHKIMEIRSPRX CHKIMEIRERX CANLOCREQRX PURGMSRSPRX PURGMSRERX AUTHINFRSPRX AUTHINFRERX INSSUBREQRX DELSUBREQRX RESETREQRX ACTVTRREQRX DACTVTRREQRX AUTHFAILRPTRSPRX AUTHFAILRPTRERX UPLOCRSPRX UPLOCRERX RESTORERSPRX RESTORERERX SNDIMSIRSPRX SNDIMSIRERX PROVROAMNMBREQRX NOTMMEVRSPRX NOTMMEVRERX SNDIDREQRX SNDIDRSPRX SNDIDRERX PREHOREQRX PREHORSPRX PREHORERX PRESUBHOREQRX PRESUBHORSPRX PRESUBHORERX SNDENDSIGREQRX SNDENDSIGRSPRX PROCACCSIGREQRX FWDACCSIGREQRX PROVSUBSINFOREQRX
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies.
Number of Prepare Handover: Return Error messages transmitted Number of Prepare Subsequent Handover: Request messages transmitted Number of Prepare Subsequent Handover: Response messages transmitted Number of Prepare Subsequent Handover: Return Error messages transmitted Number of Send End Signal: Request messages transmitted Number of Send End Signal: Response messages transmitted Number of Process Access Signaling: Request messages transmitted Number of Forward Access Signaling: Request messages transmitted Number of Provide Subscriber Info: Response messages transmitted Number of Provide Subscriber Info: Return Error messages transmitted Number of Forward Check SS Indication: Request messages received Number of Check IMEI: Response messages received Number of Check IMEI: Return Error messages received Number of Cancel Location: Request messages received Number of Purge MS: Response messages received Number of Purge MS: Return messages received Number of Authentication Info: Response messages received Number of Authentication Info: Return Error messages received Number of Insert Subscriber Data: Request messages received Number of Delete Subscriber Data: Request messages received Number of Reset: Request messages received Number of Activate Trace: Request messages received Number of Deactivate Trace: Request messages received Number of Authentication Fail Report: Response messages received Number of Authentication Fail Report: Return Error messages received Number of Update Location: Response messages received Number of Update Location: Return Error messages received Number of Restore SS: Response messages received Number of Restore SS: Return Error messages received Number of Send IMSI: Response messages received Number of Send IMSI: Return Error messages received Number of Provide Roaming Number: Request messages received Number of MAP Notify MM Event: Response messages received. Number of MAP Notify MM Event: Return Error messages received. Number of Send Identification: Request messages received Number of Send Identification: Response messages received Number of Send Identification: Return Error messages received Number of Prepare Handover: Request messages received Number of Prepare Handover: Response messages received Number of Prepare Handover: Return Error messages received Number of Prepare Subsequent Handover: Request messages received Number of Prepare Subsequent Handover: Response messages received Number of Prepare Subsequent Handover: Return Error message received Number of Send End Signal: Request messages received Number of Send End Signal: Response messages received Number of Process Access Signaling: Request messages received Number of Forward Access Signaling: Request messages received Number of Provide Subscriber Info: Request messages received
Description Number of Prepare Handover: Request messages transmitted Number of Prepare Handover: Response messages transmitted
To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send a Provide Roaming Number Request).
50/128
5.11.2 Subscriber Information Related MAP Messaging (MAPSPMMSGPERF) Performance Group Name: MAPSPMMSGPERF File Naming Convention: MAPSPMMSGPERF.YYMMDD-HHMM.### ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file.
Position Field Name 1 STARTTIMESTAMP 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Send Route Info: Request messages transmitted Number of Resume Call Handling: Request messages transmitted Number of Resume Call Handling: Response messages transmitted Number of Resume Call Handling: Return Error messages transmitted Description Date and time performance interval started.
ROUTINFOREQTX RESCALLHANDLREQTX RESCALLHANDLRSPTX RESCALLHANDLRETX ROUTINFORSPRX ROUTINFORERX
10 11 12
RESCALLHANDLREQRX RESCALLHANDLRSPRX RESCALLHANDLRERX
Number of Send Route Info: Response messages received Number of Send Route Info: Return Error messages received
Number of Resume Call Handling: Request messages received Number of Resume Call Handling: Response messages received
Number of Resume Call Handling: Return Error messages received
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send a Send Route Info Response).
51/128
5.11.3 SMS Related MAP Messaging (MAPSMSMSGPERF) Performance Group Name: MAPSMSMSGPERF File Naming Convention: MAPSMSMSGPERF.YYMMDD-HHMM.### ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file.
Position Field Name 1 STARTTIMESTAMP 2 3 4 5 6 7 8 9 10 11 12 13 14 STOPTIMESTAMP WSSNODENUM Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Short Message Ready: Request messages transmitted Number of Notify Subscriber Present: Request messages transmitted Number of Forward Short Message: Request messages transmitted Number of Mobile Terminated Forward Short Message: Response messages transmitted Number of Mobile Terminated Forward Short Message: Return Error messages transmitted Number of Short Message Ready: Response messages received Number of Short Message Ready: Return messages received Number of Notify Subscriber Present: Request messages received Number of Forward Short Message: Response messages received Description Date and time performance interval started.
SMRDYREQTX NOTSUBPRESREQTX FWDSMREQTX MTFWDSMRSPTX MTFWDSMRETX SMRDYRSPRX SMRDYRERX
NOTSUBPRESREQRX FWDSMRSPRX FWDSMRERX MTFWDSMREQRX
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send a Forward Short Message Response).
Number of Forward Short Message: Return Error messages received Number of Mobile Terminated Forward Short Message: Request messages received
52/128
5.11.4 CISS Related MAP Messaging (MAPCISSMSGPERF) Performance Group Name: MAPCISSMSGPERF File Naming Convention: MAPCISSMSGPERF.YYMMDD-HHMM.### ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file.
Position Field Name 1 STARTTIMESTAMP 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM REGSSREQTX ERASESSREQTX ACTVSSREQTX DACTVSSREQTX Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Register SS: Request messages transmitted Number of Erase SS: Request messages transmitted Number of Activate SS: Request messages transmitted Number of Deactivate SS: Request messages transmitted Description Date and time performance interval started.
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
GETPASSWDRSPTX GETPASSWDRETX
INTERSSREQTX REGPASSWDREQTX
Number of Interrogate SS: Request messages transmitted Number of Register Password: Request messages transmitted Number of Get Password: Response messages transmitted Number of Get Password: Return Error messages transmitted
PROCUSSDATREQTX PROCUSSDATRSPTX PROCUSSDATRETX PROCUSSREQTX PROCUSSRSPTX PROCUSSRETX USSREQTX USSRSPTX
Number of Process USS Data: Return Error messages transmitted Number of Process USS: Request messages transmitted Number of Process USS: Response messages transmitted Number of Process USS: Return Error messages transmitted
Number of Process USS Data: Request messages transmitted Number of Process USS Data: Response messages transmitted
USSRETX USSNOTRETX
BGNSUBACTVREQTX REGSSRSPRX REGSSRERX ERASESSRSPRX ERASESSRERX ACTVSSRSPRX
Number of USS: Return error messages transmitted Number of USS Notify: Return Error messages transmitted
Number of USS: Request messages transmitted Number of USS: Response messages transmitted
Number of Register SS: Return Error messages received Number of Erase SS: Response messages received Number of Erase SS: Return Error messages received Number of Activate SS: Response messages received
Number of Begin Subscriber Activity: Request messages transmitted Number of Register SS: Response messages received
ACTVSSRERX DACTVSSRSPRX DACTVSSRERX INTERSSRSPRX
INTERSSRERX REGPASSWDRSPRX REGPASSWDRERX GETPASSWDREQRX
Number of Interrogate SS: Return Error messages received Number of Register Password: Response messages received
Number of Deactivate SS: Return Error messages received Number of Interrogate SS: Response messages received
Number of Activate SS: Return Error messages received Number of Deactivate SS: Response messages received
PROCUSSDATREQRX PROCUSSDATRSPRX PROCUSSDATRERX PROCUSSREQRX PROCUSSRSPRX
Number of Process USS DATA: Return Error messages received Number of Process USS: Request messages received Number of Process USS: Response messages received
Number of Process USS DATA: Request messages received Number of Process USS DATA: Response messages received
Number of Register Password: Return Error messages received Number of Get Password: Request messages received
53/128
Position Field Name 41 PROCUSSRERX 42 USSREQRX 43 44 45 USSRSPRX USSRERX
Description Number of Process USS: Return Error messages received Number of USS: Request messages received Number of USS: Response messages received Number of USS: Return Error messages received
USSNOTREQRX
Number of USS Notify: Request messages received
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send a Register SS Response message).
54/128
5.11.5 Location Services Related MAP Messaging (MAPLCSMSGPERF) Performance Group Name: MAPLCSMSGPERF File Naming Convention: MAPLCSMSGPERF.YYMMDD-HHMM.### ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system Number of records: One per file.
Position Field Name 1 STARTTIMESTAMP 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Number of Provide Subscriber Location: Response messages transmitted Number of Provide Subscriber Location: Return Error messages transmitted Number of Subscriber Location: Request messages transmitted Number of Provide Subscriber Location: Request messages received Number of Subscriber Location: Response messages received Number of Subscriber Location: Return Error messages received. Description Date and time performance interval started.
PROVSUBSLOCRSPTX PROVSUBSLOCRETX SUBSLOCREQTX PROVSUBSLOCREQRX SUBSLOCRSPRX SUBSLOCRERX
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never send a Provide Subscriber Location Request message).
55/128
5.12 BSSAP (A-Interface from BSS) Information
Two different software modules in WSS capture performance pegs for all the BSSAP (A-Interface from BSS) messages. These pegs are therefore split across two performance groups, applying to functions as follows 1. Call and Mobility-Related BSSAP Messages 2. Circuit and System Maintenance Related BSSAP Messages
The following sub sections list each software modules performance pegs.
5.12.1 Call and Mobility Related BSSAP Information (BSSAPMMMSGPERF) Performance Group Name: BSSAPMMMSGPERF File Naming Convention: BSSAPMMMSGPERF.YYMMDD-HHMM.###
Number of records: Equals the number of BSS destination point codes provisioned in the system.
Position Field Name 1 STARTTIMESTAMP 2 3 4 5 6 7 8 9 STOPTIMESTAMP WSSNODENUM Description Date and time performance interval started.
DPC ASSIGNMENTREQTX
CLRCOMMANDTX HOCANDIDATEENQUIRETX HOREQUESTTX HOREQUIREDREJTX HOCOMMANDTX HOSUCCEEDEDTX
Number of Clear Command messages transmitted. Number of Handover Candidate Enquire messages transmitted. Number of Handover Request messages transmitted. Number of Handover Required Reject messages transmitted.
Date and time performance interval stopped. WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Destination Point Code. Number of Assignment Request messages transmitted.
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
RESOURCEREQTX PAGINGTX
Number of Handover Command messages transmitted. Number of Handover Succeeded messages transmitted. Number of Resource Request messages transmitted. Number of Paging messages transmitted.
OVERLOADTX MSCINVOKETRACETX
BSSINVOKETRACETX CLASSMARKREQUESTTX
Number of Overload messages transmitted. Number of MSC Invoke Trace messages transmitted.
CIPHERMODECOMMANDTX LOADINDTX CHANGECIRCUITTX COMMONIDTX
LSAINFOTX PERFORMLOCREQTX
Number of Change Circuit messages transmitted. Number of Common ID messages transmitted.
Number of Cipher Mode Command messages transmitted. Number of Load Indication messages transmitted.
Number of BSS Invoke Trace messages transmitted. Number of Classmark Request messages transmitted.
CONNECTIONLESSINFOTX ASSIGNMENTCOMPLETERX ASSIGNMENTFAILURERX CLRCOMPLETERX CLRREQRX HOCANDIDATERSPRX
Number of LSA Information messages transmitted. Number of Perform Location Request messages transmitted.
Number of Connectionless Information messages transmitted. Number of Assignment Complete messages received. Number of Assignment Failure messages received. Number of Clear Complete messages received.
Number of Clear Request messages received. Number of Handover Candidate Response messages received.
56/128
Position Field Name 30 HOREQUIREDRX 31 HOREQUESTACKRX
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis. DPC is the key field, and identifies the destination point code about which this record applies. It is in the format of a single integer that can be converted to traditional <network><cluster><member> format as follows: 1. Convert the integer value to a 6-numeral hexadecimal value 2. The two most significant hexadecimal numerals represent the <network>, the middle two numerals represent the <cluster>, and the least two significant numerals represent the <member>. They can, of course, be converted individually back to decimal notation as required.
32 HOCOMPLETERX 33 HOSUCCEEDEDRX 34 HOFAILURERX 35 HOPERFORMEDRX 36 HODETECTRX 37 RESOURCEINDRX 38 OVERLOADRX 39 BSSINVOKETRACERX 40 CLASSMARKUPDATERX 41 CIPHERMODECOMPLETERX 42 CIPHERMODEREJECTRX 43 COMPLETELAYER3INFORX 44 QUEUINGINDICATIONRX 45 SAPINREJECTRX 46 LOADINDRX 47 SUSPENDRX 48 RESUMERX 49 CHANGECIRCUITACKRX 50 PERFORMLOCRESPRX 51 PERFORMLOCABORTRX 52 CONNECTIONLESSINFORX
Number of Handover Complete messages received. Number of Handover Succeeded messages received. Number of Handover Failure messages received. Number of Handover Performed messages received. Number of Handover Detect messages received. Number of Resource Indication messages received. Number of Overload messages received. Number of BSS Invoke Trace messages received. Number of Classmark Update messages received. Number of Cipher Mode Complete messages received. Number of Cipher Mode Reject messages received. Number of Complete Layer 3 Information messages received. Number of Queuing Indication messages received. Number of SAPI "N" Reject messages received. Number of Load Indication messages received. Number of Suspend messages received. Number of Resume messages received. Number of Change Circuit Acknowledge messages received. Number of Perform Location Response messages received. Number of Perform Location Abort messages received. Number of Connectionless Information messages received.
Description Number of Handover Required messages received. Number of Handover Request Acknowledge messages received.
To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note that, for this group, only those message types legitimate to the purposes of an MSC are captured (e.g. an MSC will never receive a Paging message).
57/128
5.12.2
Circuit and System Maintenance Related BSSAP Information (BSSAPMNTMSGPERF) ### is the Node Number of the CCM card for which the statistics are gathered it will range over the CCM cards actually provisioned on the system
Description Date and time performance interval started. Date and time performance interval stopped.
BSSAPMNTMSGPERF BSSAPMNTMSGPERF.YYMMDD-HHMM.###
Number of records: Equals the number of BSS destination point codes provisioned in the system.
Position Field Name 1 STARTTIMESTAMP 2 STOPTIMESTAMP 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 WSSNODENUM DPC BLOCKTX
Number of Blocking Acknowledgment messages transmitted. BLOCKINGACKNOWLEDGETX CKTGRPBLCKTX Number of Circuit Group Block messages transmitted. CKTGRPBLCKINGACKTX CKTGRPUNBLOCKTX CKTGRPUNBLCKINGACKTX UNBLOCKTX UNBLOCKINGACKTX RESETTX RESETACKTX
WSS Node (CCM Card) to which this record applies. Will always equal node number in the file name Destination Point Code. Number of Block messages transmitted.
Number of Circuit Group Blocking Acknowledgment messages transmitted. Number of Circuit Group Unblock messages transmitted. Number of Circuit Group Unblocking Acknowledgment messages transmitted. Number of Unblock messages transmitted. Number of Unblocking Acknowledgment messages transmitted. Number of Reset messages transmitted. Number of Reset Acknowledgment messages transmitted.
RESETCIRCUITTX RESETCIRCUITACKTX CONFUSIONTX UNEQUIPPEDCKTTX BLOCKRX
Number of Confusion messages transmitted. Number of Unequipped Circuit messages transmitted.
Number of Reset Circuit messages transmitted. Number of Reset Circuit Acknowledgment messages transmitted.
CKTGRPBLCKRX CKTGRPBLCKINGACKRX CKTGRPUNBLOCKRX UNBLOCKRX
BLOCKINGACKNOWLEDGERX
CKTGRPUNBLCKINGACKRX UNBLOCKINGACKRX RESETRX RESETACKRX RESETCIRCUITRX
Number of Circuit Group Unblocking Acknowledgment messages received. Number of Unblock messages received. Number of Unblocking Acknowledgment messages received. Number of Reset messages received. Number of Reset Acknowledgment messages received. Number of Reset Circuit messages received.
Number of Circuit Group Block messages received. Number of Circuit Group Blocking Acknowledgment messages received. Number of Circuit Group Unblock messages received.
Number of Block messages received. Number of Blocking Acknowledgment messages received.
RESETCIRCUITACKRX CONFUSIONRX UNEQUIPPEDCKTRX
Number of Reset Circuit Acknowledgment messages received. Number of Confusion messages received. Number of Unequipped Circuit messages received.
Please note that for this performance group, the Node Number is not a key field because the files themselves are split on a per-node basis.
DPC is the key field, and identifies the destination point code about which this record applies. It is in the format of a single integer that can be converted to traditional <network><cluster><member> format as follows: 1. Convert the integer value to a 6-numeral hexadecimal value 2. The two most significant hexadecimal numerals represent the <network>, the middle two numerals represent the <cluster>, and the least two significant numerals represent the <member>. They can, of course, be converted individually back to decimal notation as required.
To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards.
59/128
CALL-RELATED & GSM / MOBILITY PERFORMANCE DATA
6.1 Call Control & Features Information (CALLPERF)
Performance Group Name: CALLPERF File Naming Convention: CALLPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Position 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. STARTTIMESTAMP STOPTIMESTAMP Field Name Beginning time of the performance interval Ending time of the performance interval Description
WSSNODENUM
CALLATTMSTOMSVCCAL CALLSUCCMSTOMSVCCAL CALLANSMSTOMSVCCAL CALLATTMSTOPSTNVCCAL CALLSUCCMSTOPSTNVCCAL CALLANSMSTOPSTNVCCAL CALLATTPSTNTOMSVCCAL CALLSUCCPSTNTOMSVCCAL CALLANSPSTNTOMSVCCAL CALLATTLANDTOLANDCAL CALLSUCCLANDTOLANDCAL CALLANSLANDTOLANDCAL SUCCMSORIGCTMCALLS SUCCMSTERCTMCALLS ATTMSORIGCTMCALLS ATTMSTERCTMCALLS ORINTERROGATION
WSS Node (CCM Card) to which this record applies. Number of attempted mobile-to-mobile calls pegged when setup message is sent to the terminating MS. Number of successful mobile-to-mobile calls pegged when assignment complete message is received from the terminating MS. Number of answered mobile-to-mobile calls pegged when connect message received from terminating MS. Number of attempted mobile to PSTN call pegged when IAM is sent to the terminating switch. A call forward to voice mail for a busy and not reachable sub, and intersystem handoff will also peg this counter. Number of successful mobile to PSTN calls pegged when ACM received from terminating switch. Number of answered mobile to PSTN calls pegged when ANM received from terminating switch. Number of attempted PSTN to mobile call pegged when setup message is sent to the terminating MS. Number of successful PSTN to mobile calls pegged when assignment complete message is received from the terminating MS. Number of answered PSTN to mobile calls pegged when connect message received from terminating MS. Number of attempted Land-to-Land call pegged when IAM is sent to the terminating switch. Number of successful Land-to-Land call pegged when ACM received from terminating switch. Number of answered Land to Land call pegged when ANM received from terminating switch. Number of successful CTM calls for 2G and UMA mobile originating traffic Number of successful CTM calls for 2G and UMA mobile terminating traffic Number of attempted CTM calls for 2G and UMA mobile originating traffic Number of attempted CTM calls for 2G and UMA mobile terminating traffic Number of OR Interrogation. Number of Inter-PLMN Calls Allowed Number of Inter-PLMN Calls Not Allowed Number of OR Early CF Allowed. Number of OR GMSC Late CF Allowed. Pegged when the RCH message received with call forwarding allowed.
ORINTERPLMNCALLALLOWED
ORINTERPLMNCALLNOTALLOWED
OREARLYCFALLOWED ORGMSCLATCFALLOWED
60/128
Position
Field Name
Description Number of OR GMSC Late CF Not Allowed. Pegged when the RCH message is received with no redirect number or call forwarding not allowed. RCH message received with redirect allowed, however, services are not allowed (PLMN not allowed CAMEL not supported) after interrogation to HLR if required. Number of OR GMSC Late CF Failed. Pegged when RCH is received but failed to call forward, or timed-out on HLR interrogation when forwarding interrogation to HLR is required. Number of OR VMSC Late CF Request. Pegged when RCH message is sent. Number of OR VMSC Late CF Allowed. Pegged when RCH response with status OK is received from other MSC. Number of OR VMSC Late CF Not Allowed. Pegged when RCH response with status not allowed received. Number of OR VMSC Late CF Failed. Pegged when RCH response with status Failed or timeout received. Number of OR VMSC Late CF Timeout. Number of Call Forwarding Unconditional. Number of Call Forwarding Busy. Number of Call Forwarding No Reply.
25.
ORGMSCLATCFNOTALLOWED
26.
ORGMSCLATECFFAILED
27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52.
ORVMSCLATCFREQUEST ORVMSCLATECFALLOWED ORVMSCLATECFNOTALLOWED ORVMSCLATECFFAILED ORVMSCLATECFREQTIMEOUT INVOKECFUSS INVOKECFBSS INVOKECFNRYSS
INVOKEECTSS INVOKEMULTIPARTYSS
INVOKECFNRCSS INVOKECALLWAITSS
Number of Call Forwarding Not Reachable Number of Call Waiting. Number of Explicit Call Transfers Number of Multi-party calls.
ADDDNTOGSMEXCPTION DELDNFROMGSMEXCPTION
LNPDIPTOTAL LNPDIPRESULTLRN
ADDDNTOANSI41EXCPTION DELDNFROMANSI41EXCPTION
Add DN to GSM Exception. Delete DN from GSM Exception.
LNPDIPNONPORTED LNPOWNLRNUNALLOC LNPMISROUTE SEVENDIGITDIALATT
SEVENDIGITDIALSUCC LONGCALLDISCONNECT CALLATT3GTO2GVCCAL CALLSUCC3GTO2GVCCAL
Total number of LNP NPDB dips. Number of LNP NPDB dips resulting in LRN being returned. Number of LNP NPDB dips resulting in dialed number being returned (non-ported case). Number of instances of an LRN being returned which is the operators (own) LRN, but for which the related HLR query result is unsuccessful Number of instances of an IAM arriving with LRN (and FCI Mbit set to number translated), where LRN is the operators (own) LRN, but for which the related HLR query result is unsuccessful Number of 7-digit dialing attempts. Number of calls that are allowed to go through with user dials 7 digits. Number of calls disconnected by the long call disconnect function. Number of attempted 3G to 2G mobile calls pegged when setup message is sent to the terminating MS. Number of successful 3G to 2G mobile calls pegged when
Add DN to ANSI-41 Exception. Delete DN from ANSI-41 Exception.
61/128
Position 53. 54. 55. 56. 57. 58. 59. 60. 61. 62.
Field Name CALLANS3GTO2GVCCAL CALLATT3GTOLANDVCCAL CALLSUCC3GTOLANDVCCAL CALLANS3GTOLANDVCCAL CALLATTM2GTO3G CALLSUCC2GTO3G CALLANS2GTO3G CALLATTMLANDTO3G CALLSUCCLANDTO3G CALLANSLANDTO3G
63. CALLATTUMATO2GVCCAL 64. CALLSUCCUMATO2GVCCAL

65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. CALLANSUMATO2GVCCAL CALLATTUMATOUMAVCCAL CALLSUCCUMATOUMAVCCAL CALLANSUMATOUMAVCCAL CALLATT2GTOUMAVCCAL CALLSUCC2GTOUMAVCCAL CALLANS2GTOUMAVCCAL CALLATTPSTNTOUMAVCCAL CALLSUCCPSTNTOUMAVCCAL CALLANSPSTNTOUMAVCCAL CALLATTUMATOPSTNVCCAL CALLSUCCUMATOPSTNVCCAL CALLANSUMATOPSTNVCCAL CNAMQUERYATT CNAMQUERYSUCC CNAMQUERYTIMEOUT
Description assignment complete received from the terminating MS. Number of answered 3G to 2G mobile calls pegged when connect message received from the terminating MS. Number of attempted 3G mobile to land calls pegged when IAM message is sent to the terminating switch. Number of successful 3G mobile to land calls pegged when ACM message received from the terminating switch. Number of answered 3G mobile to land calls pegged when ANM message received from the terminating switch. Number of attempted 2G to 3G mobile calls pegged when setup message is sent to the terminating MS. Number successful 2G to 3G mobile calls pegged when RAB assignment complete received from the terminating MS. Number of answered 2G to 3G mobile calls pegged when connect message received from the terminating MS. Number of attempted land to 3G mobile calls pegged when setup message is sent to the terminating MS. Number of successful land to 3G mobile calls pegged when RAB assignment complete received from the terminating MS. Number of answered land to 3G mobile calls pegged when connect message received from the terminating MS. Number of attempted UMA to 2G calls pegged when setup message is sent to the terminating MS. Number of successful UMA to 2G calls pegged when assignment complete received from the terminating MS. Number of answered UMA to 2G calls pegged when connect message received from the terminating MS. Number of attempted UMA to UMA calls pegged when setup message is sent to the terminating MS. Number of successful UMA to UMA calls pegged when assignment complete received from the terminating MS. Number of answered UMA to UMA calls pegged when connect message received from the terminating MS. Number of attempted 2G to UMA calls pegged when setup message is sent to the terminating MS. Number of successful 2G to UMA calls pegged when assignment complete received from the terminating MS. Number of answered 2G to UMA calls pegged when connect message received from the terminating MS. Number of attempted PSTN to UMA calls pegged when setup message is sent to the terminating MS. Number of successful PSTN to UMA calls pegged when assignment complete received from the terminating MS. Number of answered PSTN to UMA calls pegged when connect message received from the terminating MS. Number of attempted UMA to PSTN calls pegged when IAM message is sent to the terminating switch. Number of successful UMA to PSTN calls pegged when ACM or ANM message is received from the terminating switch. Number of answered UMA to PSTN calls pegged when ANM message is received from the terminating switch. This counter is pegged when Call processing sends a CNAP query message to the SPM which in turn sends a TCAP query to external LIDB database. This counter is pegged when Call processing receives a CNAP query response from the SPM which in turn would have received a response from external LIDB database. This counter is pegged when Call processing timeout on CNAP query to the SPM process that wait for CNAP query
62/128
Position 81. 82. 83. 84. 85. 86. 87. Reserved4 Reserved5 Reserved6 Reserved7 Reserved8
Field Name
response from LIDB.
Description
Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use
Reserved9 Reserved10
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards.
Reserved field 9 for future use Reserved field 10 for future use
63/128
6.2 MAP Information Gateway MSC (MAP1PERF)
Performance Group Name: MAP1PERF File Naming Convention: MAP1PERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Position
1 2 3 4 5 6 7 8 9
WSSNODENUM ATTINTERROHLRFORROUTING SUCCINTERROHLRMSRN SUCCINTERROHLRCALFRWD SUCCINTERROHLRCAMEL RESERVED1 RESERVED2
Field Name
WSS Node (CCM Card) to which this record applies. Number of HLR queries by the GMSC function for the purpose of routing incoming calls Number of successful HLR interrogations where MSRN is obtained Number of successful HLR interrogations where forwarded to number obtained Number of successful HLR interrogations where T-CSI is returned Reserved field 1 for future use Reserved field 2 for future use
Description
10 11
RESERVED3 RESERVED4
64/128
6.3 MAP Information Visited/Serving MSC (MAPPERF)
Performance Group Name: MAPPERF File Naming Convention: MAPPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system. NOTE: This performance group will not be applicable to pure GMSC system application
Position Field Name 1 STARTTIMESTAMP 2 STOPTIMESTAMP 3 4 5 6 7 8 9 10 WSSNODENUM Description Beginning time of the performance interval Ending time of the performance interval
11 12 13 14 15 16
17 18 19 20 21
18
WSS Node (CCM Card) to which this record applies. 18 Number of attempted incoming inter-MSC handovers pegged when ATTININTERMSCHDO the serving MSC receives MAP-Prep-Handover-Req message from the anchor MSC. Number of successful incoming inter-MSC handovers pegged when the SUCCININTERMSCHDO serving MSC sends MAP-Send-End-Signal-Req to the anchor MSC. Number of attempted outgoing inter-MSC handovers pegged when the OUTINTERMSCHDO anchor MSC sends MAP-Prep-Handover-Req message to the serving MSC. Number of successful outgoing inter-MSC handovers pegged when the SUCCOUTINTERMSCHDO anchor MSC receives MAP-Send-End-Signal-Req from the serving MSC. 19 Number of attempted subsequent inter-MSC handbacks (to MSC-A) ATTSUBSQNTINTERMSCHDOMSCA pegged when the anchor MSC-A receives MAP-Prep-Sub-HandoverReq from the serving MSC-B. Number of successful subsequent inter-MSC handbacks (to MSC-A) pegged when the anchor MSC-A sends back MAP-Send-End-SignalSUCCSUBSQNTINTERMSCHDOMSCA Resp to the serving MSC-B. Number of attempted subsequent inter-MSC handovers (to MSC-C) pegged when the anchor MSC-A receives MAP-Prep-Sub-HandoverATTSUBSQNTINTERMSCHDOMSCC Req and attempts to send MAP-Prep-Handover-Req to the target MSC-C. Number of successful subsequent inter-MSC handovers (to MSC-C) pegged when anchor MSC-A receives MAP-Send-End-Signal-Req SUCCSUBSQNTINTERMSCHDOMSCC from target MSC-C and attempts to send MAP-Send-End-SignalResp to serving MSC-B. ATTIDRQSTTOPVLR Number of identification information requests to the previous VLR for subscribers registering afresh in this VLR SUCCIDRQSTTOPVLR Number of successful identification requests to the previous VLR for subscriber registering afresh in this VLR ATTAUTHSETSRQSTTOHLR Number of requests to the HLR by the VLR for Authentication triplets SUCCAUTHSETSFROMHLR Number of successful responses (including Authentication triplet vector) received by the VLR in response to requests for Authentication information. EMPTYRESPAUTHFROMHLR Number of empty responses received by the VLR in response to requests for Authentication information. (Previously this field was over-written by another field USOUTSUBINTERMSCHOMSCARB in patch2.3.17.Now it is freed.) TOTALTRIPLETAUTHSETSFROMHLR Total Number of successful actual triplets. It includes triplets from previous VLR in inter-VLR location updates ATTLOCUPDTHLR Attempted location updates to HLR from VLR SUCCLOCUPDTHLR ATTREQFORMSRN Success location updates to HLR from VLR Requests for MSRN received by VLR
SUCCREQFORMSRN
Successful Request for MSRN (MSRN available, response sent)
This field and field #5 (SUCCININTERMSCHDO) measure from the perspective of the target MSC (MSC-B in the case of initial inter-MSC handover, MSC-C in the case of subsequent handover). 19 These four fields (#8 through #11) are all measured on the anchor MSC (MSC-A) 3BL76533FAAADSZZA Edition 07 65/128
Position Field Name 22 CANCELLOCREQFROMHLR 23 INSSUBSCRIBERFROMHLR 24 25 DELSUBSCRIBERFROMHLR USOUTINTERMSCHORB
26
USSUBINTERMSCHOMSCARB
27
USSUBINTERMSCHOMSCCRB
28
ATTOUTSUBINTERMSCHOMSCA
29
ATTOUTSUBINTERMSCHOMSCC
30
SUCCOUTSUBINTERMSCHOMSCA
31
SUCCOUTSUBINTERMSCHOMSCC
32
USOUTSUBINTERMSCHOMSCARB
33 34 35
20 21
USOUTSUBINTERMSCHOMSCCRB RESERVED1 RESERVED2
Description Cancel Location Request From HLR Number of successful Insert Subscriber Data transactions received from HLR Number of Delete Subscriber received from HLR Number of unsuccessful Inter MSC handovers out of serving MSC-A with reconnect back to MSC-A. Pegged when MSC-A receives an AHO-FAILURE from its BSS-A and MSC-A attempts to send MAP Process Access Signaling Req to target MSC-B. This was previously 20 mapped to RESERVED1 Number of unsuccessful subsequent Inter MSC handovers into MSC-A with reconnect back to serving MSC-B. Pegged when anchor MSC-A receives MAP-PROCESS-ACCESS-SIGNALING req containing AHO-FAILURE from serving MSC-B. This was previously mapped to 21 RESERVE2 . Number of unsuccessful subsequent Inter MSC handovers out of Serving MSC-B to target MSC-C with reconnect back to Serving 22 MSC-B . Pegged when anchor MSC-A receives MAP-ProcessAccess-Signaling req with HO failure from serving MSC-B. Number of subsequent Inter MSC handover attempts out of Serving MSC-B to Anchor MSC-A or target MSC-C via MSC-A, pegged when serving MSC-B sends MAP-Prep-Sub-Handover-Req to MSC-A and the target cell belongs to anchor MSC-A or MSC-C. This was 23 previously mapped to RESERVE3 Number of subsequent Inter MSC handover attempts out of serving 24 MSC-B to MSC-C , pegged when MSC-B sends MAP-Prep-SubHandover-Req to MSC-A (anchor) for target cell belonging to MSC-C. (Not supported as a separate counter, currently pegged as part of 28) Number of subsequent Inter MSC handover successes for the attempts out of Serving MSC-B to anchor MSC-A when the target call belongs to MSC-A or MSC-C, it is pegged when MSC-B receives successful MAP-Send-End-Sig resp from MSC-A. This was previously 25 mapped to RESERVE4 Number of subsequent Inter MSC handover successes for the attempts out of MSC-B to MSC-C when the target cell belongs to MSC-C, pegged when MSC-B receives successful MAP-Send-End26 Sig Resp from MSC-A . (currently not supported) Number of unsuccessful subsequent Inter MSC handovers out of Serving MSC-B to Anchor MSC-A or target MSC-C with reconnect back to Serving MSC-B. Pegged when serving MSC-B received HOFailure from its BSC-B and it sends HO failure to anchor MSC-A or target MSC-C via MAP Process access signaling Req to MSC-A. This field was overwritten on EMPTYRESPAUTHFROMHLR field (field 27 # 16) in the Patch 2.3.17 Number of unsuccessful subsequent Inter MSC handovers out of 28 Serving MSC-B to target MSC-C with reconnect back to MSC-B . Pegged when MSC-B received HO-Failure from its BSC-B and it sends HO failure to anchor MSC-A via MAP Process access signaling Req.. Reserved field 1 for future use Reserved field 2 for future use
Added by FR-0453 Added by FR-0453 22 Added by FR-0453 23 Added by FR-0453 24 Added by FR-0453 25 Added by FR-0453 26 Added by FR-0453 27 Added by FR-0453 28 Added by FR-0453 3BL76533FAAADSZZA Edition 07 66/128
Position 36 37 38 39 40 41 42 43
Field Name RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 RESERVED9 RESERVED10
Description Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use Reserved field 10 for future use
67/128
6.4 BSSAP (A-Interface) and Mobile Call Information (BSSAPPERF)
Performance Group Name: BSSAPPERF File Naming Convention: BSSAPPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system. NOTE: This performance group will not be applicable to pure GMSC system application
Position
1 2 3 4 5 6 7 8 9
WSSNODENUM NBRCLSMRKUPDT
Field Name
ATTMSORIGCALLS MSORIGCMSRVCREQ SUCCMSORIGCALLS ANSMSORIGCALLS ATTMSTERCALLS
10 11 12 13 14 15 16 17 18 19 20 21 22 23
SUCCMSTERCALLS ANSMSTERCALLS ATTMSEMRGNCYCALLS MSEMRGNCYCMSRVCREQ SUCCMSEMRGNCYCALLS ANSMSEMRGNCYCALLS ATTCIPHRMDCTRPROCS SUCCCIPHRMDCTRPROCS TRANSSUBIDWTMSI TRANSSUBIDWIMSI ATTTMSIREALOC SUCCTMSIREALOC
IMSIDETACHPROCS IMSIATTACHPROCS
Number of call attempts for mobile originating traffic Pegged when a SETUP message is received from the originating mobile. CM Service Request from originating MS number of all CM_SERVIC_REQUEST messages (voice, data, SMS) received. Number of successful calls for mobile originating traffic Pegged when an Assignment Complete message is sent to the originating mobile Number of answered calls for mobile originating traffic Pegged when a connect ack message is received from the originating MS. Number of call attempts for mobile terminating traffic Pegged when an attempt is made to send a SETUP message to the terminating mobile Number of successful calls for mobile terminating traffic Pegged when an Assignment Complete message is received from the terminating side. Number of answered calls for mobile terminating traffic Pegged when a Connect Ack message is sent to the terminating mobile. Number of emergency call attempts Pegged when a Setup or Emergency Setup message is received from the originating mobile Number of Emergency CM Service Requests number of CM_SERVICE_REQUEST (Emergency Call) messages received Number of successful emergency calls pegged when an Assignment complete message is sent to the originating side. Number of answered emergency calls pegged when an answer message is sent to the originating side. Number of ciphering mode control procedures transmitted Pegged on attempt to send Cipher Request to mobile Number of successful ciphering mode control procedures Pegged on Cipher Response received by the WSS Number of transactions where mobile subscriber was identified with his TMSI Number of transactions where mobile subscriber was identified with his IMSI Number of TMSI re-allocation attempts Number of successfully performed TMSI re-allocations
WSS Node (CCM Card) to which this record applies. Number of Classmark Updates
Description
Number of IMSI Detach procedures number of Location Update Request (Detach) messages received Number of IMSI Attach procedures number of Location Update Request (Attach) messages received
68/128
Position
24 25
IMPLICITDETACH
Field Name
ATTINEXTINTRAMSCHDO SUCCINEXTINTRAMSCHDO SUCCOUTEXTINTRAMSCHDO EXTHDO UNSCCEXTHDORECNCTPERMSC
26 27 28 29 30 31 32 33 34 35 36 37 38 39
UNSCEXTHDOLOSSCNCTPERMSC SUCCINTRAHOCTMCALLS SUCCINTEROUTHOCTMCALLS SUCCINTERINHOCTMCALLS ATTINTRAHOCTMCALLS
Total Number of subscribers implicitly detached (i.e. by VLR audit) Number of intra-MSC target cell handover procedures initiated (pegged at dispatch of BSSMAP:Handover Request)29 Number of intra-MSC target cell handover procedures successfully completed (pegged at receipt of BSSMAP:Handover Complete) Number of intra-MSC serving cell handover procedures successfully completed (pegged at receipt of BSSMAP:Clear Complete from serving BSS Number of handovers initiated (pegged at receipt of BSSMAP:Handover Required) Number of unsuccessful Handovers with reconnect to the original channels pegged when HO failure received from the serving BSS. Number of unsuccessful Handovers with loss of the call pegged when Clear Request message is received from the serving BSS. Number of successful Intra MSC HO for CTM Calls Number of successful Outgoing Inter-MSC HO for CTM Calls Number of successful Incoming Inter-MSC HO for CTM Calls Number of attempted Intra MSC HO CTM Calls Number of attempted Outgoing Inter-MSC HO for CTM Calls Number of attempted Incoming Inter-MSC HO for CTM Calls
Description
ATTINTEROUTHOCTMCALLS ATTINTERINHOCTMCALLS ATTINTERVLRLOCUPD
SUCCINTERVLRLOCUPD ATTINTRAVLRLOCUPD
40 ATTPERIINTRAVLRLOCUPD 41 SUCCINTRAVLRLOCUPD 42 SUCCPERIINTRAVLRLOCUPD 43 44 45 46 ATTAUTH SUCCAUTH TOTALACTIVESUB INTRABSCHANDOVER
Number of attempted (incoming) inter VLR location update pegged when MAP Update Location Req is received by VLR with no subscriber record in VLR. Number of successful (incoming) inter VLR location update pegged when MAP Update Location Resp is sent from VLR to the MSC after VLR retrieves subscriber record. Number of attempted intra VLR location update (all types) pegged when MAP Update Location Req is received by VLR with subscriber record already in VLR. Number of attempted periodic intra VLR location update Number of successful intra VLR location update (all types) pegged when MAP Update Location Resp is sent from VLR to the MSC after VLR subscriber record is updated. Number of successful periodic intra VLR location update Number of attempted Authentication procedures Attempt to send authentication request to mobile Number of successful Authentication procedures An authentication response received by the WSS 30 Number of total subscribers in the VLR, it provides a snap shot of total subscribers in the VLR database. Number of Intra BSC Handover pegged when Handover performed message is received from the BSS. Number of roamers registered in the VLR31 Number of Paging Attempts (within LAC) with TMSI. Pegged at attempt to send first Paging Request with TMSI message. Number of Successful Paging (within LAC) with TMSI
47 CALLVLRRGSTRDSUBFROMOTHERPLMN 48 ATTPAGEMSTMSI 49 SUCCPAGEMSTMSI
Some handover fields (#24, #25, and #27) are applicable but higher order fields within this group and the SUMMARYPERF group are more appropriate for overall handover performance tracking. These fields may be removed in a future release. 30 Measured at the end of the performance stat interval. 31 Measured at the end of the performance stat interval.
29
69/128
Position
50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67
ATTPAGEMSIMSI
Field Name
SUCCPAGEMSIMSI ATTSEARCHMSIMSI SUCCSEARCHMSIMSI REJLUPPLMNNOTALLOWED REJLUPLACNOTALLOWED REJLUPROAMNOTALLOWED ATTOUTEXTINTRAMSCHO RESERVED1 RESERVED2 RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 RESERVED9 RESERVED10
Number of Paging Attempts (within LAC) with IMSI. Pegged on attempt to send first paging request with IMSI message Number of Successful Paging (within LAC) with IMSI Number of Global Search Attempts with IMSI nd Pegged on attempt to send Paging Retry message (2 ) or first Paging Request when the LAC is invalid Number of Successful Global Searches with IMSI number of nd st Paging_response (2 ) or 1 Paging when invalid LAC messages Number of Location Updates rejected due to visitors PLMN not 32 allowed. LUP Rejection Cause value is 11. Pegged when unable to derive or find HLR from IMSI. Number of Location Updates rejected due to invalid CGI (Cell 33 Global Id). LUP Rejection Cause value is 12. Number of Location Updates rejected due to roaming not allowed in this location area (LAC or PLMN in restrictions list). 34 LUP Rejection Cause value is 13. 35 Number of intra-MSC but inter-BSC Handover attempts pegged when HO required is received from serving BSS and attempt is being made to send HO request to the target BSS. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use Reserved field 10 for future use
Description
Added by FR-0454 Added by FR-0454 34 Added by FR-0454 35 Added by FR-0453

32 33
70/128
6.5 IS41 Information (IS41PERF)
Performance Group Name: IS41PERF File Naming Convention: IS41PERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system. NOTE: This group will not be applicable to GSM DMSC application
Position Field Name 1 STARTTIMESTAMP 2 STOPTIMESTAMP 3 4 5 6 7 8 9 WSSNODENUM LOCREQREQSENT
LOCREQRSPWROUTNUMRECVD LOCREQRSPWCFRECVD REDIRREQREQRECVD REDIRREQRSPSENT TRANSNUMREQSENT
Number of Location Request response with Routing Number received from HLR Number of Location Request response with Call Forwarding received from HLR Number of Redirection request received from HLR Number of Redirection response sent to HLR Number of transfer to number sent to HLR
WSS Node (CCM Card) to which this record applies. Number of Location Request sent to HLR
Description Beginning time of the performance interval Ending time of the performance interval
10 11 12 13 14
TRANSNUMRSPRECVD RESERVED1 RESERVED2 RESERVED3 RESERVED4
Number of transfer to number response received from HLR Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
71/128
6.6 SMS Information A-Interface Related (BSSAPSMSPERF)
Performance Group Name: BSSAPSMSPERF File Naming Convention: BSSAPSMSPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system. NOTE: This performance group will not be applicable to pure GMSC system application
Position
1 2 3 4 5 6 7 8 9
WSSNODENUM CALLATTMSORGSMS CALLSUCCMSORGSMS CALLATTMSTERMSMS CALLSUCCMSTERMSMS RESERVED1 RESERVED2
Field Name
10 11
RESERVED3 RESERVED4
WSS Node (CCM Card) to which this record applies. Number of attempted SMS transactions for mobile originating traffic pegged when RP Data is received from MS. Number of successful SMS transactions for mobile originating traffic36 pegged when attempt is made to send RP_ACK to MS. Number of attempted SMS transactions for mobile terminating traffic pegged when attempt is made to send RP Data to the MS. Number of successful SMS transactions for mobile terminating traffic pegged when RP_ACK is received from the MS. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
Description
36
Successful transaction implies confirmation of end-to-end delivery of the short message. 72/128
6.7 Call Independent Supplementary Services Information (CISSPERF)
Performance Group Name: CISSPERF File Naming Convention: CISSPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system. NOTE: This performance group will not be applicable to pure GMSC system application
Position
1 2 3 4 5 6 7 8
WSSNODENUM ACTIVATIONATTEMPT
Field Name
ACTIVATIONSUCCESS DEACTIVATIONATTEMPT
WSS Node (CCM Card) to which this record applies. Number of SS feature activation attempts. Number of SS feature activation succeeded. Number of SS feature de-activation attempts.37 Number of SS feature de-activation succeeded. Number of SS feature Registration attempts. Number of SS feature Registration succeeded. Number of SS feature de-registration attempts.38 Number of SS feature de-registration succeeded. Number of Mobile Initiated USSD attempts. Number of Mobile USSD succeeded. Number of network Initiated USSD attempts. Number of network Initiated USSD succeeded. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
Description
9 10 11 12 13 14 15 16 17 18 19
REGISTRSUCCESS DEREGISTRATTEMPT DEREGISTRSUCCESS MIUSSDATTEMPT MIUSSDSUCCESS NIUSSDATTEMPT NIUSSDSUCCESS RESERVED1 RESERVED2 RESERVED3 RESERVED4
DEACTIVATIONSUCCESS REGISTRATTEMPT
37 38
This field name has been changed to DEACTIVATIONATTEMPT from DEACTIVATION This field name has been changed to DEREGISTRATIONATTEMPT from DEREGISTRATION 73/128
6.8 Circuit Switched Data and Data Interworking Function

6.8.1 IWF Group Information (MSFIWFGRPPERF) Performance Group Name: MSFIWFGRPPERF File Naming Convention: MSFIWFGRPPERF.YYMMDD-HHMM Number of records: Equals the number of bearer groups provisioned to the attached data Inter-Working Function (IWF) NOTE: This performance group will not be applicable to pure GMSC system application
Position 39
1. 2. 3. 4. 5. 6. 7. 8.
STARTTIMESTAMP STOPTIMESTAMP MSFIWFGRPID
Field Name
MOBILEORIGATTEMPTS MOBILETERMATTEMPTS TOTALUSAGESEC OVERFLOW MINRESOURCEAVAIL
9. MINRESOURCEAVAILVALID 10. MAXRESOURCEAVAIL 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. RESERVED1 RESERVED2
Mobile originated attempts pegged when two circuits to IWF are allocated on IWF trunk. Note: the trunk allocation occurs at the begining of the call before ACM/Alerting. Mobile terminated attempts pegged when two circuits to IWF are allocated on IWF trunk. Total time in seconds that there are active calls (during this collection interval)40 Number of calls that are denied because of circuit unavailability Minimum number of idle circuits available during this collection interval Whether the value in field MINRESOURCEAVAIL is a valid value or not41 Maximum number of idle circuits available during this collection interval Reserved field 1 for future use Reserved field 2 for future use
Ending time of the performance interval Facility group (to IWF) to which this record applies.
Beginning time of the performance interval
Description
RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 RESERVED9 RESERVE10
Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use
Reserved field 9 for future use Rerserved field 10 for future use
MSFIWFGRPID is the key field and identifies the facility group to the IWF to which this record applies.
Previously Added Performance Group This is the accumulation of all calls made on all trunks in the group during this collection interval. As a result, this number can significantly exceed the number of seconds in the collection interval. 41 If this value is 1, then the value in field #8 is legitimately for this collection interval. If this value is 0, then the value in field #8 should be ignored for this collection interval.
39 40
74/128
6.8.2 IWF Signaling Information (SYSIWFSMIMPERF) Performance Group Name: SYSIWFSMIMPERF File Naming Convention: SYSIWFSMIMPERF.YYMMDD-HHMM Number of records: Equals the number of SMIM defined in the Inter-Working Function (IWF) Rack/Node This performance group provides statistics for communication messages between SMIM and Call server. These statistics are pegged on the call server side. Since this group covers Cicrcuit Switched Data (CSD) calls message to SMIM, the IWF trunks related statistics for CSD call are provided in MSFIWFGRPPERF. NOTE: This performance group will not be applicable to pure GMSC system application
Position
1 2 3 4 5 6 7 8 9
STOPTIMESTAMP NODEID
STARTTIMESTAMP
Field Name
SMIMID MOMODEMCALLS MTMODEMCALLS MODIGITALCALLS MTDIGITALCALLS MOFAXCALLS MTFAXCALLS XCONNREQTX CONNRELTX CONNACKRX CONNFCDRELRX FCDRESTTX IWERRACKTX IWCONNERRRX IWERRORRX READALARMSTATUSTX ALARMREPORTRX ALARMREPORTACKTX IWASRQTX IWASRSPRX RESETOBCCALCTX RESETOBCMIWXTX SENDRJATX CHGOCCSTATETX
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
SMIM to which this record applies. Number of Mobile Originated Modem Calls. Pegged when XCONNREQTX is sent to the SMIM. Number of Mobile Terminated Modem Calls. Pegged when XCONNREQTX is sent to the SMIM. Number of Mobile Originated Digital Calls. Pegged when XCONNREQTX is sent to the SMIM. Number of Mobile Terminated Digital Calls. Pegged when XCONNREQTX is sent to the SMIM. Number of Mobile Originated Fax Calls. Pegged when XCONNREQTX is sent to the SMIM. Number of Mobile Terminated Fax Calls. Pegged when XCONNREQTX is sent to the SMIM. Number of Data Connection Request messages transmitted from WSS to SMIM. Note: XCONNREQ is sent after the call has been answered from the terminating party. Number of Connection Release messages transmitted from WSS to SMIM Number of Connection Acknowledgement messages or Connection Release Acknowledgement messages received by WSS from SMIM Number of Forced Connection Release messages received by WSS from SMIM Number of Forced Restart messages transmitted from WSS to SMIM Number of Acknowledgement messages for IWF Error appearance and disappearance transmitted by WSS to SMIM Number of IWF Connection Error messages received by WSS from SMIM Number of IWF Error appearance and disappearance messages received by WSS from SMIM Number of Read Alarm Status messages transmitted by WSS to SMIM Number of Alarm Report messages received by WSS from SMIM Number of Alarm Report Acknowledgement messages transmitted by WSS to SMIM Number of All IWF Alarm States request (after the restart of WSS) messages transmitted by WSS to SMIM Number of All IWF Alarm States Response messages received by WSS from SMIM Number of Clock and Alarm On-Board-Controller Reset messages transmitted by WSS to SMIM Number of Mobile Interworking Unit Version X (MIWX) On-BoardController Reset messages transmitted by WSS to SMIM Number of block and unblock messages to SMIM to prevent seizure from the switch. Number of Change OBC Channel Controller (OCC) State messages transmitted by WSS to SMIM
Ending time of the performance interval IWF Node/Rack ID to which this record applies.
Description
75/128
Position
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
XSYSPARMTX LOADBIDRX
Field Name
OCCSTRSPRX RESTARTINDRX CMMREQRX CMMCONFTX UPDNOTCHTX RESERVED1 RESERVED2 RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 RESERVED9
Number of System Parameter/Configuration messages transmitted by WSS to SMIM Number of Fast Test on MIWX (Load Bid) messages received by WSS from SMIM. This is just an information for WSS Number of OBC Channel Controller (OCC) State Change Response messages received by WSS from SMIM Number of Autonomous Restart on MIWX Indication messages received by WSS from SMIM Number of Change of Channel Coding due to negotiation of end-to-end connection messages received by WSS from SMIM Number of Acknowledgment to Change of Channel Coding due to negotiation of end-to-end connection messages transmitted by WSS to SMIM Number of Update of the number of real Traffic Channels used messages transmitted by WSS to SMIM Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use
Description
Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use
RESERVED10
NODEID and SMIMID are the key fields and identify the IWF Node and SMIM cards in the IWF to which this record applies. To provide a system-wide view of the information in this performance group, the values must be accumulated across all SMIM cards.
SUGGESTED FORMULA:
Success Rate of CSD calls = XCONNREQTX/( MOBILEORIGATTEMPTS + MOBILETERMATTEMPTS)

assuming that Mobile to Mobile CSD calls on the same switch are negligible.
Success Rate of IWF CSD calls = (CONNACKRX - CONNRELTX ) / (XCONNREQTX) Note this is an
approximation until CONNACKRX only counts +ve ACKS for XCONNREQTX.
Failure Rate of IWF CSD calls = 1 - Success Rate of CSD calls
76/128
6.9 Call Disposition Information (ENDOFCALLPERF)
Performance Group Name: ENDOFCALLPERF File Naming Convention: ENDOFCALLPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Position
1 2 3 4 5 6
WSSNODENUM ENDOFCALLCAUSEVALUE ENDOFCALLCATEGORY ENDOFCALLCOUNTER
Field Name
WSS Node (CCM Card) to which this record applies. Internal Call Disposition Code or Cause Code to end a call
Description
Not used Number of occurrences of a particular Call Disposition Code
WSSNODENUM and ENDOFCAUSEVALUE are the key fields. WSSNODENUM identifies the CCM Node (card) to which this record applies; ENDOFCALLCAUSEVALUE identifies the call disposition code. The end of call cause values or cause codes range from 000 to 999. The values will be grouped or categorized as given in the following table. A complete description of all of the meanings of each cause code and category names are under development, and will be provided as an addition to this document in a future update.
Cause Code Range
129 ~ 134 135 ~ 139 200 ~ 249 250 ~ 299 300 ~ 328 329 ~ 340 341 ~ 349 350 ~ 399 400 ~ 449 450 ~ 499 500 ~ 569 750 ~ 770 800 ~ 824 825 ~ 859 861 ~ 989 990 ~ 999
To be provided in a future update To be provided in a future update
To be provided in a future update
Category Description
To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update
To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update To be provided in a future update
Detailed reference for each cuase, refer to Technical Requirements Specification External Cuase /Internal Code Mapping, 3BL76757AAAADSZZA
77/128
6.10 Call Total Time Performance Information (CALLTOTALTIMEPERF)

Performance Group Name:
Position 1. 2. 3. 4.
CALLTOTALTIMEPERF
File Naming Convention: CALLTOTALTIMEPERF.YYMMDD-HHMM

Field name STARTTIMESTAMP STOPTIMESTAMP WSSNODENUM TOTALCALLTIMELANDTOLAND
Description
Beginning time of the performance interval Ending time of the performance interval WSS Node (CCM Card) to which this record applies. Used for mean hold time for Land to Land call. This time is a commulative time in seconds for all land to land answered calls. The timer starts from ANSWER message and stops with call termination. Used for mean hold time for 2G Mobile to Land call. This time is a commulative time in seconds for all 2G mobile to land answered calls. The timer starts from ANSWER message and stops with call termination. Used for mean hold time for Land to 2G Mobile call. This time is a commulative time in seconds for all land to 2G answered calls. The timer starts from ANSWER message and stops with call termination. Used for mean hold time for Mobile to Mobile call. This time is a commulative time in seconds for all mobile to mobile answered calls. The timer starts from ANSWER message and stops with call termination.
5.
TOTALCALLTIMEMOBILETOLAND
6.
TOTALCALLTIMELANDTOMOBILE
7.
TOTALCALLTIMEMOBILETOMOBILE
WSSNODENUM IS the key fields.
78/128
7 7.1
IN RELATED INFORMATION INAP Information (INAPGWYPERF)
Performance Group Name: INAPGWYPERF File Naming Convention: INAPGWYPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Position
1 2 3 4 5 6 7 8
WSSNODENUM SERVICEKEY
Field Name
DEFAULTHANDLINGCALLS INITDP2 INITDP3 INITDP12
WSS Node (CCM Card) to which this record applies. The service key
Description
Number of calls for which default handling was applied Number of InitialDP2 attempts Number of IntialDP3 attempts Number of IntialDP12 attempts Reserved field 1 for future use Reserved field 2 for future use
9 10 11 12
RESERVED1 RESERVED2
RESERVED3 RESERVED4
WSSNODENUM and SERVICEKEY are the key fields. WSSNODENUM identifies the CCM Node (card) to which this record applies; SERVICEKEY identifies the service key. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. SERVICE KEYS are numbers that range from 0 to 2,147,483,647. There will typically be very few distinct service keys (say 4 or 5) within this range. Services would be provisioned (and hence a number is assigned) in Atrium (MSC/VLR) in business agreement with SCP provider. The service keys are stored in Spatial'sN_CSI_DP_Criteria_Data table and will be included in the service request to the SCP.
79/128
7.2
Performance Group Name: CAPPERF File Naming Convention: CAPPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Position
CAMEL Information (CAPPERF)
1 2 3 4 5 6 7 8 9
WSSNODENUM SERVICEKEY
Field Name
CAPSUCCINITDPREQ CAPNUMETCMSGRX CAPNUMDFLTCAMELHNDLINVKD INITDP2 INITDP3
WSS Node (CCM Card) to which this record applies. The service key
Description
Number of successful Initial DP requests (when Continue, ContinueWithArg, Connect, or ETC is received from SCP in response to Initial DP) Number of ETC messages received Number of calls for which default handling was applied Number of Initial DP2 request Number of Initial DP3 request
10 11 12 13 14
INITDP12 INITDPSMS
CAPSUCCINITDPSMSREQ RESERVED1 RESERVED2
Number of Initial DP12 request Number of Initial DP SMS request
Number of successful INIT DP SMS Requests Reserved field 1 for future use Reserved field 2 for future use
WSSNODENUM and SERVICEKEY are the key fields. WSSNODENUM identifies the CCM Node (card) to which this record applies; SERVICEKEY identifies the service key. To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. SERVICEKEYS are numbers that range from 0 to 2,147,483,647. Services such as voice-mail, prepaid etc. would be dynamically (meaning no pre-defined assignment of a particular number to a particular service) assigned a number. Atrium (MSC/VLR) downloads CSI data - including these service keys (one per CSI) in response to SRI or in the Insert Subscriber Data (ISD) from the HLR.
80/128
8 8.1
REGULATORY SERVICES INFORMATION Wireless Priority Service (WPS) Information (PRIORITYCALLPERF)
Required / Referenced by WPS FOC
Performance Group Name: PRIORITYCALLPERF File Naming Convention: PRIORITYCALLPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Position
1 2 3 4 5 6 7 8
WSSNODENUM WPSATTMOCALLS
Field Name
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
WPSRADSUCCMOCALLS [O-18] Total Number of WPS call attempts with a radio traffic channel assigned GETSATTMOCALLS [R-159] Total Number of GETS call attempts PCATTLTOMSCALLS [R-160] Total Number of NS/EP calls received on inc trunks w/ MSCs MSRN PCATTNOPRECCALLS [R-160] Total Number of incoming NS/EP calls received w/o the precedence PCATTINCLCALLS [R-168] Total Number of NS/EP calls received on incoming trunks PCATTTOMSCALLS [R-160] Total Number of NS/EP calls terminated in this MSC PCRADSUCCMTCALLS PCATTLTOLCALL PCSUCCTOLCALL PCATTNOCKT PCSUCCIXCCALLS PCNOIXCCKTCALLS PCATTLQDCALLS
WSS Node (CCM Card) to which this record applies. [R-158] Total Number of WPS call attempts
Description
WPSATTTOLCALL
[O-21] Total Number of incoming NS/EP calls received with a radio traffic channel assigned [R-161] Total Number of WPS calls that require an outgoing trunk [R-168] Total Number of NS/EP calls that require an outgoing trunk [R-161] Total Number of NS/EP calls with successful trunk set up
[R-169] Total Number of NS/EP calls failed to queue for an outgoing trunk PCATTLQDOFLOWCALLS PCATTLQTOUTCALLS [R-169] Total Number of NS/EP calls removed from a queue due to timeout PCATTLQABANCALLS [R-169] Total Number of NS/EP calls removed from a queue due to user abandon RESERVED1 Reserved field 1 for future use RESERVED2 Reserved field 2 for future use RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use
[R-161] Total Number of NS/EP calls with no outgoing trunk circuit available [R-161] Total Number of NS/EP calls with successful trunk set up to an IXC [R-161] Total Number of NS/EP calls with no outgoing trunk circuit available to an IXC [R-169] Total Number of NS/EP calls queued for a outgoing trunk
RESERVED9 RESERVED10
81/128
WSSNODENUM is the key field, and identifies the CCM Node (card) to which this record applies.
To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards. Please note for this group, the bracketed reference number refers to the requirement or optional requirements outlined in the WPS FOC (Full Operating Capability) requirements document to which the field cross-references.
82/128
8.2
Performance Group Name: EMERGENCYCALLPERF File Naming Convention: EMERGENCYCALLPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system.
Positi on Field Name Description
Emergency Call (E911) Information (EMERGENCYCALLPERF)
1 2 3 4 5 6 7 8
WSSNODENUM PHASE0ATTEMPTS PHASE0FALLBACK PHASE1ATTEMPTS PHASE1FALLBACK PHASE2ATTEMPTS
WSS Node (CCM Card) to which this record applies Number of Emergency Call Attempts using Phase 0 Number of Fallbacks to Phase 0 Number of Emergency Call Attempts using Phase 1 Number of Fallbacks to Phase 0 from Phase 1 Number of Emergency Call Attempts using Phase 2
9 10 11 12 13 14 15 17 18 19 20 21 22 23 24
PHASE2FALLBACK ATTINAPQUERY
SUCCINAPQWCONTINUE SUCCINAPQWCONNECTWESRK INAPESRKNOTIFICATIONS SUCCINAPQWCONNECTWOESRK RESERVED1
16
RESERVED2 RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 RESERVED9
Number of successful INAP queries with CONTINUE to obtain ESRK. Note that by default this does not return 42 ESRK. Number of successful INAP queries with CONNECT to obtain ESRK. This is the count where CONNECT contains 43 ESRK. Number of INAP queries to inform GMLC what ESRK was used Number of successful INAP queries with connect to obtain ESRK. This is the count where CONNECT does NOT 44 contain ESRK Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use
Number of Fallbacks to Phase 0 from Phase 2 Number of INAP queries attempted to obtain ESRK
RESERVED10
42 43 44
in parser
The name has been changed from SUCCINAPQUERIESWCONTINUE to SUCCINAPQWCONTINUE due to ling name error The name has been changed from SUCCINAPQUERIESWCONNECT to SUCCINAPQWCONNECTWESRK due to ling This field replaces the Reserved1 field. 83/128
name error in parser
8.3
Position Field Name 1 STARTTIMESTAMP 2 STOPTIMESTAMP 3 4 5 6 7 9 10 11 12 13 14 15 16 17 18 19 20 8 ESZID ESRKPOOL1IDLE ESRKPOOL2IDLE ESRKPOOL3IDLE
Performance Group Name: ESRKPOOLPERF File Naming Convention: ESRKPOOLPERF.YYMMDD-HHMM Number of records: Equals the number of emergency zones.
Emergency Routing Key (ESRK) Information (ESRKPOOLPERF)
ESRKPOOL1ALLOCATED ESRKPOOL2ALLOCATED ESRKPOOL3ALLOCATED ESRKALLOCFAILURE RESERVED1 RESERVED2 RESERVED3 RESERVED4 RESERVED5 RESERVED6 RESERVED7 RESERVED8 RESERVED9 RESERVED10
Number of ESRK Numbers that are available in 1 ESRK pool. Number of ESRK Numbers that are available in 2 Number of ESRK Numbers that are available in 3
nd rd st
Emergency Services Zone ID
Description Date and time performance interval started. Date and time performance interval stopped.
st
Number of ESRK Numbers that are allocated from 1 ESRK pool. Number of ESRK Numbers that are allocated from 2 ESRK pool.
nd rd
ESZID is the key field. Emergency zones are configured on the EMS.
Number of ESRK Numbers that are allocated from 3 ESRK pool. Number of times system failed to allocate ESRK Number. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use Reserved field 10 for future use
ESRK pool.
ESRK pool.
84/128
9 9.1
FACILITIES PERFORMANCE DATA System Route Information (SYSROUTEPERF)
Performance Group Name: SYSROUTEPERF File Naming Convention: SYSROUTEPERF.YYMMDD-HHMM Number of records: Equals the number of route indexes provisioned in the system.
Position
1 2 3 4 5 6 7 8 9
STARTTIMESTAMP STOPTIMESTAMP ROUTEINDEX CALLSROUTED NOCIRCUITAVAIL CALLSQUEUED
Field Name
CALLSQUEUEDABANDON CALLSQUEUEDSUCCESS PRIORCALLATT PRIORCALLATTQTOUT PRIORCALLATTQOFLOW
10 11
Route index. Number of calls attempted for routing. This also includes priority call attempts. Number of calls encountering no circuits available pegged when no circuit is available in case of regular calls or when there was a queue overflow in case of priority calls. This does not include calls queued abandoned. [R-169] Total number of NS/EP calls queued for a outgoing trunk. Since only priority calls are queued, this is a subset of PRIORCALLATT. [R-169] Total number of NS/EP calls removed from a queue. This may be due to queue timeout, user abandon etc. This is a superset of PRIORCALLATTQTOUT. [R-169] Total number of NS/EP calls successful after being queued for a outgoing trunk pegged when circuit becomes available for a queued call. [R-168] Total number of NS/EP calls that require an outgoing trunk. It is a subset of CALLROUTED. [R-169] Total number of NS/EP calls removed from a queue due to queue timeout. This is a subset of CALLSQUEUEDABANDON. [R-169] Total number of NS/EP calls failed to queue for an OG trunk as the maximum queue size was reached. It is a subset of NOCIRCUITAVAIL.
Description
ROUTEINDEX is the key field, and identifies the route index to which this record applies. Please note for this group, the bracketed reference number refers to the requirement or optional requirements outlined in the WPS FOC (Full Operating Capability) requirements document to which the field crossreferences. The following represent relationship between counters.
SUCCESSFULLYROUTED = CALLSROUTED NOCIRCUITAVAIL CALLSQUEUEDABANDON PRIORCALLATT = CALLSQUEUEDSUCCESS + CALLSQUEUEDABANDON + PRIORCALLATTQOFLOW
85/128
9.2
Performance Group Name: SYSGRPPERF File Naming Convention: SYSGRPPERF.YYMMDD-HHMM Number of records: Equals the number of facilities (trunk groups) provisioned in the system.
Position
System Group Information (SYSGRPPERF)
1 2 3 4 5 6 7
SYSGRPNUM WMGNODENUM
Field Name
NUMBEROFRESOURCES GROUPDIRECTION INCOMINGATTEMPTS
TRANSLATIONERRORS
9 10
INCOMINGBLOCKED INCOMINGCONGESTION
11
ROUTINGFAILURE
System group number. 45 The node number of WMG serving the trunk group (SYSGRPNUM) Number of circuits defined (or provisioned) including Out-of-Service in the trunk group at the end of the recording interval Indication of whether the trunk group is incoming only, outgoing only or both ways. Total number of incoming call attempts on this trunk group (access as well as IMT trunks). It is pegged when facility manager allocates circuit in response to either setup or IAM message. 46 Number of calls dropped due to number translation errors occurred on both access and IMT trunks. This includes cause code 1 (unallocated number), and internal cause codes: 350 - digits not found in Prefix or normalization translation tree, 351 - digits not found in National translation tree, 352 - route selection failure based on carrier ID code, 354 - encounter IE error during translation, 356 digits not found in Country Code translation tree, 357 - received invalid carrier ID code to translate, 362 - routing info not found in Orig routing table, 368 - call screening failure, 375 - routing info not found in NOA routing table, 379 - seven digits dialing from roamer, and 412 - problem in ported data Number of calls blocked due to calls coming in (the wrong direction) on 47 a trunk that is designated for outgoing only . Applicable to both IMT and access trunks, however, the value should be nil for access trunks since they are bidirectional. Number of incoming calls dropped due to internal (local) system 48 congestion occurred on either access or IMT trunks. Number of incoming calls that has successfully passed translation but 49 dropped due to routing errors , applicable to both access and IMT trunks. Pegged when no circuit to destination, invalid route index, fail on continuity test, LNP misrouted ported number due to unknown number in coming message. In addition, it will also peg cause code 2 (no route to specified network), 3 (no route to destination), 4 (send special information tone), 5 (misdialed trunk prefix), 6 (channel unacceptable), 25 (Exchange routing error), 26 (nonselected user clearing), 27 (destination out of order), 34 (no circuit/channel available), and 44 (requested channel/circuit not available).
Description
A new field introduced by CR1161. In the event of a trunk group that spans multiple WMGs, the WMG of the first circuit of the trunk group will be listed. 46 A new field introduced by CR024. TRANSLATIONERRORS tracks the number of incoming calls for which the dialed numbers could not be translated to a proper destination. The translation errors include unallocated number, service not available or implemented, fail in prefix, and service not allowed. These calls will be dropped. 47 A new field introduced by CR024. When an incoming call lands on a trunk group that is designated for outgoing calls only, then the call will be dropped and the INCOMINGBLOCKED counter will be pegged 48 A new field introduced by CR024. In the event of an internal (local) congestion due to unexpected processing or resources limits, the incoming new calls will be dropped so that the existing calls can be served with the available processing resources. When the internal congestion abates, the new calls will be accepted. 49 A new field introduced by CR024. In the event of a successful Number of Translation but invalid routes or routes not available to the destination, the calls will be dropped and the routing errors will be pegged.
45
86/128
12
SYSTEMERRORSINCOMING
13 14 15 16
PROTOCOLERRORSINCOMING INCOMINGCOMPLETION OUTGOINGATTEMPTS SIGFAILURES
17 18 19 20 21 22 23 24
OVERFLOWS OVERFLOWSEC MINRESOURCEAVAIL MINRESOURCEAVAILVALID MAXRESOURCEAVAIL OOSSEC OUTGOINGGLARE OUTGOINGCONGESTION
25
SYSTEMERRORSOUTGOING
Number of incoming calls dropped due to system errors on the 50 incoming side , applicable to access and IMT trunks. Pegged when assignment failure occurs, prepaid timer expires, unexpected message recvd from term side, invalid internal response from message etc. It will also peg locally generated temporary failure, cause code 41. Number of calls dropped due to unspecified protocol errors on the 51 incoming side , applicable to both access and IMT trunks. Pegged when incoming message has unsupported bearer, invalid mandatory info, or mandatory IE missing. 52 Total number of valid incoming call attempts derived counter as explained in footnote. This counter was previously called as INCOMINGVALIDATTEMPTS Total number of outgoing call attempts pegged when facility manager received a request to idle the circuit that was used for outgoing (termination) party id. Either setup or IAM message was sent. Number of call attempts that had signaling failures. Pegged when ACM timeout, timeout on failed to connect bearer, timeout on setup message response, ring timeout, timeout on info message etc. Number of call attempts that were denied due to all resources (circuits) being busy on either access or IMT trunks (including PSTN trunks). For IMT trunks overflow get pegged for outgoing calls only. For access trunks it gets pegged whenever there is no circuit available for either outgoing or incoming call on that access trunk. Number of seconds that the group had all resources (circuit) busy Minimum number of resources available during the measurement interval. This represents the heaviest traffic point in the measurement interval. This field indicates whether the minimum number of resources available field is valid or default 0. Maximum number of circuits available during the measurement interval. This represents lowest traffic point in the measurement interval. Total number of seconds all the resources spent in the out of service state. Number of outgoing call attempts that encountered glare, applicable to IMT trunks only. There should not be any glare on trunks to/from access network. 53 Number of calls failed due to outgoing congestion , applicable to both access and IMT trunks 54 Number of calls dropped due to system errors on the outgoing side . Pegged when error during outgoing setup message, timeout on the response to terminate attempt message, received unexpected CCP release when waiting for call proceeding from ISUP, COT Test result, ACM etc. It will also peg locally generated temporary failure, cause code 41.
A new field introduced by CR024. Whenever an incoming call is dropped before being attempted out of the Atrium due to internal system or software overloads/errors, the SYSTEMERRORSINCOMING counter will be pegged. 51 A new field introduced by CR024. In the event of an unspecified protocol error while decoding the signaling messages for an incoming call. The call will be dropped and the PROTOCOLERRORSINCOMING counter will be pegged. 52 A new field introduced by CR024. Not all the incoming call attempts that come to a switch are valid attempts. All the incoming calls need to be validated before they are attempted out of the switch. INCOMINGCOMPLETION is equal to INCOMINGATTEMPTS (TRANSLATIONERRORS + INCOMINGBLOCKED + INCOMINGCONGESTION + ROUTINGFAILURE + SYSTEMERRORSINCOMING + PROTOCOLERRORSINCOMING + INCOMINGABANDONED). 53 A new field introduced by CR024. In the event of congestion in a far end switch due to unexpected processing limits, the outgoing new calls will be dropped at the request of the far-end switch. When the far-end switchs congestion abates, the outgoing new calls will be attempted. 54 A new field introduced by CR024. Whenever an outgoing call is dropped due to internal system or software overloads/errors, the SYSTEMERRORSOUTGOING counter will be pegged.
50
87/128
26
PROTOCOLERRORSOUTGOING
27
OUTGOINGNOTANSWERED
28 29 30 31 32 33 34 35 36
OUTGOINGANSWERED INCOMINGABANDONED INCOMINGANSWERED INCOMINGTERMSS7 INCOMINGTERMBSS INCOMINGTERMCASTRK PRIORITYCALLATT MAXRESOURCEOCCUPIED INCOMINGUSAGESEC
37
OUTGOINGUSAGESEC
38
ORIGMSHANDOVER
39
40
TERMMSHANDOVER INSERVICERESOURCES
Number of incoming call attempts that terminated on a local CAS trunk. [R-168] Total number of NS/EP calls that require an outgoing trunk. 57 Maximum number of channels with active calls during the measurement interval. This should be equal to (INSERVICERESOURCES MINRESOURCEAVAIL). The accumulated number of seconds of incoming resource usage for that period. If a long duration call is spans two or more measurement intervals, the usage seconds will only reflect the duration for which the circuit was busy in respective intervals. The accumulated number of seconds of outgoing resource usage usage for that period. If a long duration call is spans two or more measurement intervals, the usage seconds will only reflect the duration for which the circuit was busy in respective intervals. Previous Reserved field 1 was used: Total number of circuits used due 58 to originating MS got handed over . This counter also gets pegged for inter-MSC handout from achor MSC, in addition to outgoing attempts. For access trunks, no outgoing attempts are pgged for intra or interMSC handover. Previous Reserved field 2 was used: Total number of circuits used due 59 to terminating MS got handed over . This counter also gets pegged for inter-MSC handout from achor MSC, in addition to outgoing attempts. For access trunks, no outgoing attempts are pgged for intra or interMSC handover. Previous Reserved field 3 was used: Total number of resources/circuits in service.
Number of calls dropped due to unspecified protocol errors on the 55 outgoing side Number of outgoing call attempts that ended due to no answer or ring timeout. In addition, if a release message was received from the far end office before ANM with any release cause codes, it will be pegged as outgoing not answered. It will also peg a release with cause code 22 (Number changed) and 28 (invalid number format). It will also peg cause code 41 (Temporary failure) received from the far end. Number of outgoing call attempts that were answered. This counter was previously called as OUTGOINGCOMPLETION Number of incoming call attempts that were abandoned. It is pegged, If an originating side release the call before ANM was received. If an originating call connected to the announcement (based on a release cause code received from the terminating office) releases the call before the announcement is completed. Number of Incoming call attempts that were completed. This counter was previously called as INCOMINGCOMPLETION 56 Number of incoming call attempts that terminated on a local ISUP trunk. Number of incoming call attempts that terminated on a local BSS trunk.
A new field introduced by CR024. In the event of an unspecified protocol error while decoding the signaling messages for an outgoing call. The call will be dropped and the PROTOCOLERRORSOUTGOING counter will be pegged. 56 INCOMINGATTEMPTS >= INCOMINGTERMSS7 + INCOMINGTERMBSS + INCOMINGTERMCASTRK. 57 This field is used primarily for calculations for the SUMMARYPERF group. 58 In the event of an originating MS gets handed over, OUTGOINGATTEMPTS is pegged and hence the OUTGOINGATTEMPTS will be greater than the INCOMINGATTEMPTS. This ORIGMSHANDOVER counter which tracks how many times trunk is allocated due to originating MS gets handed over needs to be subtracted from the
55
OUTGOINGATTEMPTS in order to get the original Outgoing Attempts. 59 In the event of a terminating MS gets handed over, OUTGOINGATTEMPTS is pegged and hence the OUTGOINGATTEMPTS will be greater than the INCOMINGATTEMPTS. This TERMMSHANDOVER counter which tracks
how many times trunk is allocated due to terminating MS gets handed over needs to be subtracted from the
OUTGOINGATTEMPTS in order to get the original Outgoing attempts.
88/128
41
INCOMINGREJECTED
42
OUTGOINGREJECTED
43
INCOMINGNOTANSWERED
44
OUTGOINGABANDONED
45
OUTGOINGCOMPLETION
46 47 48 49 50 51 52 53 54 55 56 57 58 59
INCOMINGORLATECFW Reserved1 Reserved2 Reserved3 Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved9 Reserved10 GROUPNAME WMGNODENAME OUTGOINGORLATECFW
Number of incoming call-attempts that were rejected due to call barring or other service restrictions. It also includes cause code 20 (subscriber absent), 21 (call rejected), 29 (Facility rejected), 46 (precedence call blocked), 47 (Resources unavailable), 57(Bearer capability not authorized), and 58(Bearer capability not available). Number of outgoing call-attempts that were rejected by the call terminating switch due to call barring or other service restrictions. It also includes cause code 20 (subscriber absent), 21 (call rejected), 29 (Facility rejected), 46 (precedence call blocked), and 47 (Resources unavailable), 57(Bearer capability not authorized), and 58(Bearer capability not available) from far end. Number of incoming call-attempts that did not get answered due to reasons other than call rejection, translation error, protocol error, routing failure, system error, and call abandon. In addition, it will also peg a release with cause code 22 (Number changed) and 28 (invalid number format) from the far. It will also peg cause code 41 (Temporary failure) received from the far end. Number of Outgoing call-attempts that were abandoned by the call originator before the reception of ANM message. Note, the sum of OUTGOINGABANDONED across all trunk groups should be less than or equal to sum of INCOMINGABANDONED across all trunk groups in a call server. Total number of outgoing call attempts that were completed but not necessarily answered. It shall be equal to OUTGOINGATTEMPTS (SIGFAILURES + OUTGOINGCONGESTION + OUTGOINGABANDONED + SYSTEMERRORSOUTGOING + PROTOCOLERRORSOUTGOING + OUTGOINGNOANS + OUTGOINGGLARE ) Number of incoming Optimal Routing Late Call Forward allowed in GMSC. Number of outgoing Optimal Routing Late Call Forward allowed in VMSC. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use Reserved field 9 for future use Reserved field 10 for future use 60 The name for this system group 61 The node name of WMG serving the trunk group (SYSGRPNUM)
SysGrpNum is the key field, and identifies the trunk group to which this record applies.
GROUPNAME is not a new field but its position will be towards the end of this SYSGRPPERF Performance Group. This is a text field with double quotes. It might contain spaces if the group name entered by operator contains spaces. 61 A new field introduced by CR1432. In the event of a trunk group that spans multiple WMGs, the WMG of the first circuit of the trunk group will be listed. This is a text field with double quotes. It might contain spaces if the WMG node name entered by operator contains spaces.
60
89/128
9.3
Performance Group Name: DSPUSAGEPERF File Naming Convention: DSPUSAGEPERF.YYMMDD-HHMM Number of records: Equal to the number of processors on all cards on all WMG Nodes.
Position
TDM Echo Cancellation DSP usage ( DSPUSAGEPERF)
1 2 3 4 5 6 7 8 9
MSFNODEID
Field Name
10
WMGNODEID and DSPPOOLTYPE are the key fields, and identify the Node ID of the media gateway and the type of the DSP pool respectively, to which this record applies. TDM Echo Cancellation: DSPPOOLTYPE = 2 - EchoDSP Pool uses DSP on SM card. DSPPOOLTYPE = 11 - EsEcho DSP Pool, uses DSP on ES card. DSPPOOLTYPE = 12 - VeEcho DSP Pool, uses DSP on VE card. So, the record that contains DSPPOOLTYPE = 11 should only be considered for ESEcho cancellation on ES card. Tone Detection: DSPPOOLTYPE = 3 MF Detection DSP pool type. DSPPOOLTYPE = 4 - DTMF Detection DSP pool type. DSPPOOLTYPE = 9 Network Tone Detector DSP pool type. Conference Bridge: DSPPOOLTYPE = 1 identifies Conference Bridge DSP. So, the record that contains DSPPOOLTYPE = 1 should only be considered for Conference Bridge.
Please note that this counter indicates the maximum DSP allocation since the start of system and NOT for the measurement period in minutes.
62
Number of DSP channels in this DSP Pool (including outof-service channels.) MSFTDMSYSDSPALLOCCHANNELS Number of allocated DSP channels in this DSP Pool. MSFTDMSYSDSPFREECHANNELS Number of available (and in-service) DSP channels in this DSP Pool MSFTDMSYSDSPMAXALLOCCHANNELS Maximum number of DSP channels allocated in this DSP Pool since this counter was last reset.62 MSFTDMSYSDSPSUCCALLOCREQUESTS The number of DSP channel allocation requests that were successful. MSFTDMSYSDSPUNSUCCALLOCREQS The number of DSP channel allocation requests that were unsuccessful (as there were no available DSP channels).
DSPPOOLTYPE
MSFTDMSYSDSPCHANNELS
WMG (media gateway) Node Number to which this record applies. DSP Pool Type to which this record applies.
Description
90/128
Others: DSPPOOLTYPE = 7 - Announcement DSP pool type. DSPPOOLTYPE = 8 Tone sequence DSP pool type. To provide a system-wide view of the information in this performance group, the values must be accumulated across all WMGs but for the particular DSP pool type
91/128
9.4
Performance Group Name: ICONCARDPERF File Naming Convention: ICONCARDPERF.YYMMDD-HHMM Number of records: Equals the number of Interconnect IDs provisioned in the system.
Position
TDM Interconnect Information (ICONCARDPERF)
1 2 3 4 5 6 7 8
ICONID GATEWAYNODE1ATTEMPTS GATEWAYNODE2ATTEMPTS TOTALUSAGESEC OVERFLOW OVERFLOWSEC MINRESOURCEAVAILVALID MAXRESOURCEAVAIL INSERVICERESOURCES WMGNODE1ID WMGNODE2ID RESERVED1 RESERVED2 RESERVED3 RESERVED4 MINRESOURCEAVAIL
Field Name
Number of Call attempts coming from Gateway Node - 1. Number of Call attempts coming from Gateway Node -2. Total time in seconds that there are active calls
Interconnect ID on the WMG to which this record applies.
Description
63
64
10 11 12 13 14 15 16 17 18
Number of calls that are turned away when there are no circuits available Total time in seconds when all trunks are busy and no circuit is available to allocate Minimum number of resources available This a flag that indicates whether the value in the above field MINRESOURCEAVAIL is a valid value or not Maximum number of idle circuits available observed
Total Number of resources/circuits in service. The Node ID of the first WMG having lowest WMG ID.
The Node ID of the second WMG having highest WMG ID. Reserved field 1 for future use Reserved field 2 for future use Reserved field 3 for future use Reserved field 4 for future use
ICONID is the key field that identifies the Interconnect ID, to which this record applies. An Interconnect connects two media gateways (WMGs) controlled by the same WSS. There can be multiple Interconnects (and hence multiple Interconnect IDs) between two WMGs. The lowest node ID in an interconnect is considered as the GATWAYNODE-1. The highest node ID in an interconnect is considered as the GATWAYNODE-2. For example, if 131 is the interconnect ID for a set of trunks connecting WMG-1 (whose node ID is 100) and WMG-3 (whose node ID is 300), then GatewayNode-1 is WMG-1 because its node is 100 which is less than the node ID of GatewayNode-2, WMG-3, which is 300. Please note that there can be many interconnect IDs between WMG-1 and WMG-3 and also many interconnects going out of WMG-1 and WMG-3 to other WMGs. To provide a system-wide view of the information in this performance group, the values must be accumulated across all Interconnect group IDs.
63 64
A GATEWAYNODE-1 is the node that has the lowest node ID in that Interconnect. A GATEWAYNODE-2 is the node that has the highest node ID in that Interconnect. 92/128
9.5
Performance Group Name: TRKGRPWMGICONPERF File Naming Convention: TRKGRPWMGICONPERF.YYMMDD-HHMM Number of records: Equals the number of Trunk Groups and WMG combinations in a local WMG cluster controlled by a single MSC.
Position
TRUNKGROUP and WMG Interconnect Information (TRKGRPWMGICONPERF)
1 2 3 4 5 6 7 8 9
WMGID
STARTTIMESTAMP STOPTIMESTAMP SYSGRPNUM
Field Name
INCOMINGATTEMPTS OUTGOINGATTEMPTSTOOTHERTRKGS OUTGOINGATTEMPTSTOICONS INCOMINGATTEMPTSUSAGESEC OUTATTTOOTHERTRKGSUSAGESEC OUTATTTOICONSUSAGESEC
10
11
INDROPNORESAVAILONOUTTRKGS
12 13 14 15 16 17 18 19 20 21 22
INDROPNORESAVAILONOUTICONS OUTGOINGATTEMPTS INCOMINGATTFROMOTHERTRKGS INCOMINGATTEMPTSFROMICONS OUTATTUSAGESEC INATTFROMOTHERTRKGSUSAGESEC INATTFROMICONSUSAGESEC OUTDROPNORESOURCEAVAILONIN WMGIDONE WMGIDONEOUTGOINGATTEMPTSICON WMGIDONEINCOMINGATTEMPTSICON
Date and time performance interval started. Date and time performance interval stopped. System group number or Trunk Group ID. The node number of WMG serving this Trunk Group ID (SYSGRPNUM) Number of Call attempts coming towards this WMG ID (key field in this record) from this Trunk Group ID (key field in this record) Number of Call attempts coming from this trunk group on this WMG and going out to other Trunk Groups on this WMG. (This does not include attempts going out through the same trunk group on this WMG) Total number of Call attempts coming from this trunk group on this WMG and going out to Interconnects from this WMG ID to other WMGs served by the this WSS. Incoming Usage seconds for the call attempts towards this WMG ID (key field in this record) from this Trunk Group ID (key field in this record) Usage seconds for Call attempts coming from this trunk group on this WMG and going out to other Trunk Groups on this WMG. (This does not include attempts going out through the same trunk group on this WMG) Usage seconds for call attempts coming from this trunk group on this WMG and going out to Interconnects from this WMG ID to other WMGs served by the this WSS. Number of calls coming from this trunk group on this WMG dropped (not overflows) due to no resources available on the outgoing Trunk Groups of this WMG and this trunk group (this is the case where call came in this trunk group and it attempted to go out on the same trunk). Number of calls coming from this trunk group on this WMG dropped (not overflows) due to no resources available on the Interconnects from this WMG ID to other WMGs served by the WSS. Number of Call attempts going out through this trunk group of this WMG ID. Number of Call attempts going to this Trunk Group ID from other Trunk Groups through this WMG ID Total number of Call attempts going to this Trunk Group ID from all Interconnects through this WMG ID Outgoing usage seconds for call attempts going out of this WMG ID to this Trunk Group Usage seconds for call attempts going this Trunk Group ID from all other Trunk Groups through this WMG ID Usage seconds for call attempts going to this Trunk Group ID from all Interconnects through this WMG ID Number of calls dropped (not overflows to other trunk groups) due to no resources available on this Trunk Group The ID of the WMG for which the next two fields are applicable Number of calls going from WMGID (key field in this record) to the WMGIDONE Number of calls coming from WMGIDONE to WMGID (key field in this record)
Description
93/128
23
24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
WMGIDTWO
The ID of the WMG for which the next two fields are applicable Number of calls going from WMGID (key field in this record) to WMGIDTWOOUTGOINGATTEMPTSICON the WMGIDTWO Number of calls coming from WMGIDTWO to WMGID (key field WMGIDTWOINCOMINGATTEMPTSICON in this record) WMGIDTHREE The ID of the WMG for which the next two fields are applicable Number of calls going from this WMGID (key field in this record) WMGIDTHREEOUTGOINGATTEMPTSICON to the WMGIDTHREE Number of calls coming from WMGIDTHREE to this WMGID WMGIDTHREEINCOMINGATTEMPTSICON (key field in this record) WMGIDFOUR The ID of the WMG for which the next two fields are applicable Number of calls going from this WMGID (key field in this record) WMGIDFOUROUTGOINGATTEMPTSICON to the WMGIDFOUR Number of calls coming from WMGIDFOUR to WMGID (key WMGIDFOURINCOMINGATTEMPTSICON field in this record) Formerly Reserved Field 1. The number of calls that came in OUTATTFROMSAMETRKGRP on this trunk and left out on the same trunk. Reserved Field 2 Usage seconds for calls that came in on this OUTATTFROMSAMETRKGRPUSAGESEC trunk and left out on the same trunk. Reserved3 Reserved Field 3 for future use Reserved4 Reserved5 Reserved6 Reserved7 Reserved Field 4 for future use Reserved Field 5 for future use Reserved Field 6 for future use Reserved Field 7 for future use
Reserved8 Reserved9
Reserved10
Reserved Field 10 for future use
Reserved Field 8 for future use Reserved Field 9 for future use
SYSGRPNUM and WMGID are the key fields that identify the Trunk Group ID and WMG ID to which this record applies. There will be as many records as the combination of Trunk Group ID and WMG ID are possible. For example, if there is one Trunk Group and four WMGs then there will be four records. If there are two Trunk Groups and 4 WMGs then, there will be eight records. In case of one trunk group and four WMGs in a cluster, the incoming calls on WMG-1 will be routed to the destination directly from the WMG-1. So, there will be equal number of INCOMINGATTEMPTS and OUTGOINGATTEMPTS on WMG-1 (exception, Inter-MSC HO may skew the distribution as BSS trunk is selected before the PSTN trunk per standard). Similarly, if the Trunks are distributed to all the WMGs fairly equally (at least at the DS-1 level if not DS-0 level), then INCOMINGATTEMPTS and OUTGOINGATTEMPTS on each WMG shall be fairly equal. Please note that if the distribution is at DS-0 level, then the distribution of calls on the WMGs will be equal (but can differ by few calls). Please note that if the distribution is at DS-1 level, then the distribution of calls on the WMGs would differ by at least 24 calls. If the WMG-1 has exhausted all the direct trunks to the destination(s), then the WMG-1 will try to route calls to the Interconnects to WMGIDTWO, WMGIDTHREE or WMGIDFOUR. (Note Since WMG-1 to WMGIDONE are the same, the associated counters will be zero. This is provided to keep programming and Metrica Database Schema simple and easy). It is expected that the outgoing attempts from WMG-1 to other WMGs shall be equal. Similarly the incoming attempts to WMG-1 from other WMGs shall also be equal.
94/128
Balancing Incoming Attempts of a Trunk Group on a WMG

9 6 5
Other Trunk Groups
WMG 1
30
24 27
WMG 2
Trunk Group # 76
33
32
WMG 4
WMG 3
7 5 8
= = =
24 6 9
+ + +
27 7 10
+ + +
30 11 33
12
32
Usage seconds
Note: The numbers in the circle corresponds to entry (column) number in the table
Figure 1
Balancing Outgoing Attempts of a Trunk Group on a WMG

17 14
Other Trunk Groups
16
Trunk Group # 76
13
32
WMG 1
31
25 28
WMG 2
33
WMG 4
WMG 3
15 13 16
= = =
25 14 17
+ + +
28 15 18
+ + +
31 32 33
Usage seconds
Note: The numbers in the circle corresponds to entry (column) number in the table
Figure 2.
95/128
9.6
Performance Group Name: PORTCAPACITYPERF File Naming Convention: PORTCAPACITYPERF.YYMMDD-HHMM Number of records: Equals the number of cards on all WMG Nodes.
Position
Port Capacity Performance Group ( PORTCAPACITYPERF)
2 B 4 5 6 7 8 9
STOPTIMESTAMP WMGNODEID SLOTID CARDID
STARTTIMESTAMP
Field Name
Ending time of the performance interval WMG (media gateway) Node Number to which this record applies. WMG Slot ID to which this record applies WMG Card ID to which this record applies
Description
CARDTYPE PORTCAPACITY CARDSTATUS RESERVED1
10 11 12
RESERVED2 RESERVED3 RESERVED4
WMG Card Type ((TDM Channelized Interface T1, T3, OC-3, or ATM) Number of ports (DS0) available in the slot or card i.e. Port capacity of the card The status of the card whether locked or unlocked Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use
WMGNODEID, SLOTID and DAUGHTERPORTID are the key fields, and identify the node ID of the wireless media gateway, the slot ID and daughter port ID respectively, to which this record applies To provide a slotwide view of the information in this performance group, the values must be aggregated across all records for the given SLOTID with CARDSTATUS equal to UNLOCKED.
To provide a WMG-wide view of the information in this performance group, the values must be accumulated across all the records with CARDSTATUS equal to UNLOCKED in this statistics file. Cards with a status of LOCKED will not be available for traffic. Card status: 1 Locked 2- unlocked
To provide a system-wide (WSS) view of the information in this performance group, the values must be accumulated across all WMGs connected to the WSS. Given below are the port capacities of the different card types # of daughter ports 1 4 2 # of port per card or slot 1 4 2 Capacity per daughter port (DS0s) 24192 2016 2016
Card Type
Capacity per Card or slot (DS0) 24192 8064 4032 96/128
OC12_CHAN_INTERFACE = 16,
4 port OC3_CHAN_INTERFACE = 56, 2 port OC3_CHAN_INTERFACE = 15,

E3_CHAN_INTERFACE = 14, T3_CHAN_INTERFACE = 13, E1_CHAN_INTERFACE = 12,
1 2 1 1 1 1
** 60 60 6
1920 1440
2016
268
2688 4032 1920 1440 32256 8064
T1_CHAN_INTERFACE = 11, STM4_CHAN_INTERFACE = 22, [OC12]
4 4
STM1_CHAN_INTERFACE = 21, [OC-3]
8064 2016
97/128
9.7
DEFFERED IMPLEMENTATION TO REL 4
Summary of CDR statistics ( CDRSUMMARYPERF)
Performance Group Name: CDRSUMMARYPERF File Naming Convention: CDRSUMMARYPERF.YYMMDD-HHMM Number of records: Equals the number of Cause for Termination of a call.
Position
1 2 3 4 5 6 7 8
CAUSEFORTERMINATION COUNT RESERVED1 RESERVED2 RESERVED3 RESERVED4
Field Name
Cause for Termination of a call to which this record applies. The number of occurrences of cause for termination. Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use
Description
CAUSEFORTERMINATION is the key field and identifies the Cause for Termination of a call to which this record applies. This information is provided on a system-wide basis and is generated from the CDR collection process in the WSS. To obtain total number of calls made system-wide, the COUNT field of all the records shall be added.
is an 3 2 0 0 0 0 0 1 0 1 1 0 1 0 1 1 1 1 0 0 0 0 1 1 8-bit field that can assume the following values: 1 Cause for Termination 0 Normal Release 1 Partial Record 0 RESERVED FOR FUTURE USE 1 Unsuccessful Call Attempt 0 Stable Call, Abnormal Termination 1 CAMEL Initiated Call Release 0 RESERVED FOR FUTURE USE RESERVED FOR FUTURE USE 1 RESERVED FOR FUTURE USE 0 Call Release Initiated by Long-Duration Call Timer 1 RESERVED FOR FUTURE USE RESERVED FOR FUTURE USE 1 RESERVED FOR FUTURE USE
Cause For Termination 8 7 6 5 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 thru 0 0 0 0 1 0 0 0 1 0 0 0 0 1 0 thru 1 1 1 1 1
98/128
10 CONFIGURATION DATA 10.1

Performance Group Name: TRKGP_WMG_RELATIONSHIP File Naming Convention: TRKGRP_WMG_RELATIONSHIP.YYMMDD-HHMM Number of records: Equals the number of route indexes provisioned in the system.
Position
Trunk Group Information ( TRKGP_WMG_RELATIONSHIP)
1 2 3
SYSGRPNUM WMGID
Field Name
SYSGRPNAME
Trunk Group ID. The ID of the WMG associated with Trunk Group. The name of the Trunk Group
Description
SYSGRPNUM and WMGID are the key fields, and identify the Trunk Group and WMG index to which this record applies. The SYSGROUPNUM and WMG ID show that the Trunk Group is terminated on that WMG, which is the relationship between them. This info also serves as SYSGRPNUM to SYSGRPNAME conversion.
99/128
Performance Group Name: WMG_ID_NAME_RELATIONSHIP File Naming Convention: WMG_ID_NAME_RELATIONSHIP.YYMMDD-HHMM Number of records: Equals the number of route indexes provisioned in the system.
Position
10.2
WMG Information65( WMG_ID_NAME_RELATIONSHIP)
1 2
WMGID WMGNAME
Field Name
The ID of the WMG associated with Trunk Group. The name of the WMG.
Description
WMGID is the key field, and identifies the WMG index to which this record applies. This info serves as WMGID to WMGNAME conversion. Please note that when a trunk group is not terminated on any WMG, then we should show so and hence an entry of WMGID = 0, and WMGNAME= Not Terminated will be provided.
65
Added by FR-0469 100/128
Performance Group Name: ICON_WMG_RELATIONSHIP File Naming Convention: ICON_WMG_RELATIONSHIP.YYMMDD-HHMM Number of records: Equals the number of route indexes provisioned in the system.
Position
10.3
Interconnect Information66( ICON_WMG_RELATIONSHIP)
1 2 3 4
ICONID WMG1ID
Field Name
WMG2ID ICONNAME
The ID of the WMG associated with Trunk Group. The ID of the WMG-1 associated with the Interconnect. The ID of the WMG-2 associated with the Interconnect. The name of the Interconnect.
Description
ICONID, WMG1ID and WMG2ID are the key fields, and identify the WMG index to which this record applies. This info provides a relationship between Interconnect ID and the two WMGs that it connects. This info also serves as ICONID to ICONNAME conversion.
66
Added by FR-0469 101/128
10.4 Link and Linkset Relationship (LINK_LINKSET_RELATIONSHIP)67

Performance Group Name: LINK_LINKSET_RELATIONSHIP File Naming Convention: LINK_LINKSET_RELATIONSHIP.YYMMDD-HHMM Number of records: Equals the number of SS7 links provisioned in the system.
Position
1 2 3 4
DPC DPCNAME
LINKID LINKSETID
Field Name
The DPC number The assigned string name for DPC
The SS7 Link id The Linkset id to which the link belongs.
Description
LINKID is the key fields, and DPCNAME is the string name for DPC. This info provides a relationship between LINK ID, LINKSET ID, DPC and DPCNAME. Customer can derive the name that appears on LINKSET GUI by concatenating the DPC number followed by DPC NAME i.e. 123-456-789 HLR.
67
Added by FCR 1024 102/128
11 UMA PERFORMANCE DATA INFORMATION
The UMA performance groups are pegged at Call server and UNC. The following sections describes performance groups supported on UNC and Call servers 11.1 UMA Performance Data Information in UNC
Some of the UNC based pegged, UMAURRPERF, may be pegged on an Access Point basis as well as a node (card) basis. These APs must be defined in a configured set. The performance records for this configured set of APs are accessed by specifying the Access Point Id (MAC Address) along with the node ID. For APs not specified in the configured set, the measurements are collected on a node basis. The performance records for these APs are accessed using the special Access Point Id value 000000000000 and node ID. The node basis measurements are the sum of the measurements for each AP being monitored and the corresponding measurement for the special AP ID.
11.1.1 URR Discovery, Registration and TCP Connection Information (UMAURRPERF) These pegs are captured on a node basis as well as on a per Access Point (AP) basis. These pegs are captured by URR-CM. Performance Group Name: UMAURRPERF File Naming Convention: UMAURRPERF.YYMMDD-HHMM Number of records: Equals the number of IPM card pairs in the system, multiplied by the number of Access Points for which measurements are being taken plus one. Currently, a maximum of 100 access point can be configured that need to be monitored.
Position 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. STOPTIMESTAMP WSSNODENUM ACCESSPOINT0 ACCESSPOINT1 DISREQUESTRX DISACCEPTTX DISREJECTINATX DISREJECTUNSPECTX REGREQUESTRX REGACCEPTTX DISREJECTNCTX STARTTIMESTAMP Field Name Date and time performance interval stopped WSS Node (IPM card) to which this record applies Access Point to which the record applies (MSB 2 bytes bytes in binary format right to left) Access Point to which the record applies (LSB 4 bytes in binary format right to left) Number of URR Discovery requests received Number of URR Discovery Accept sent Number of URR Discovery Reject sent (IMSI not allowed) Number of URR Discovery Reject sent (Network congestion) Number of URR Discovery Reject sent (Unspecified) Number of URR Registration requests received Number of URR Registration Accept messages sent Date and time performance interval started Description
REGREJECTANATX REGREJECTNCTX REGREJECTINATX REGREJECTLNATX
Number of URR Registration Reject sent (AP not allowed) Number of URR Registration Reject sent (Network congestion) Number of URR Registration Reject sent (IMSI not allowed) Number of URR Registration Reject sent (Location not allowed)
103/128
Position 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32.
REGREJECTIUTX
Field Name
REGREJECTGLNKTX REGREJECTUNSPECTX REGREDIRECTTX DEREGTX DEREGRX REGUPDULRX REGUPDDLTX KEEPALIVERX
Number of URR Registration Reject sent (Invalid UNC) Number of URR Registration Reject sent (Geo location not known) Number of URR Registration Reject sent (Unspecified) Number of URR Registration Redirect sent Number of URR Deregister sent
Description
CURRTCPCONN PEAKTCPCONN TCPCONNREJ OTHERTX OTHERRX CURRUSERS CURRACCPTS
33. * CONNREJECTOVLD 34. * UMAMOREJCMOVLD 35. * UMAMOREJDDFOVLD 36. * UMALUPREJCMOVLD 37. * UMALUPREJDDFOVLD 38. 39. 40. 41. RESERVE1 RESERVE2 RESERVE3 RESERVE4
Number of URR Register Update Downlink messages sent Number of URR Keep Alive received Current TCP connections. This is the number of connections at the end of the poll interval Peak number of TCP connections Number of TCP connections rejected because max allowable number reached. Number of times any other URR message sent Number of times any other URR message received Current number of users per node. This does not include RJ-11 subscribers. Current number of Access Points per node. This does not include RJ-11 router that has at least one RJ-11 subscriber. Total connections rejected due to overload UMA Mobile Origination calls rejected by URRCM due to IPM overload. UMA Mobile Origination calls rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs. UMA Location update rejected by URRCM due to IPM overload. UMA Location update rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs. Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use
Number of URR Deregister received Number of URR Register Update Uplink received
WSSNODENUM and ACCESSPOINT are both used as the key to access a record. CURRUSERS and CURRACCPTS are counted on a node-basis only. added in Rel 3 SP9
104/128
11.1.2 URR RJ11 Discovery, Registration and TCP Connection Information (UMAURRPERF) These pegs are captured on a node basis as well as on a per RJ11 Access Point (AP) basis. These pegs are captured by URR-CM. Performance Group Name: UMARJ11URRPERF File Naming Convention: UMARJ11URRPERF.YYMMDD-HHMM.LOADNAME Number of records: Equals the number of IPM card pairs in the system.
Position 1 2 3 4 5 6 7 STARTTIMESTAMP STOPTIMESTAMP ACCESSPOINT0 ACCESSPOINT1 CURRRJ11USERSNATIONAL CURRRJ11USERSINTERNATIONAL Field Name Date and time performance interval started Date and time performance interval stopped Description
WSSNODENUM
WSS Node (IPM card) to which this record applies Access Point to which the record applies (MSB 2 bytes bytes in binary format left to right) Access Point to which the record applies (LSB 4 bytes in binary format left to right) Current number of RJ-11 national subscribers registered with the UNC. This statistics is per node. Current number of RJ-11 international subscribers registered with the UNC. This statistics is per node. To be implemented in
CURRRJ11ACCPTSNATIONAL
CURRRJ11ACCPTSINTERNATIONAL
10 11 12 13 14 15 16 17 18 19 20 21 22 23
DISREQUESTRX DISACCEPTTX DISREJECTINATX DISREJECTNCTX DISREJECTUNSPECTX REGREQUESTRX REGACCEPTTX REGREJECTANATX REGREJECTNCTX REGREJECTINATX REGREJECTLNATX REGREJECTIUTX REGREJECTGLNKTX REGREJECTUNSPECTX
Number of URR Discovery requests messages received from RJ11 sub Number of URR Discovery Reject messages sent (IMSI not allowed) to RJ11 sub Number of URR Discovery Reject messages sent (Network congestion) to RJ11 sub Number of URR Discovery Accept messages sent to RJ11 sub
future release (RDS10610). Currently, it will show zero value. Current number of national RJ-11 access points (routers) connected to the UNC. Note, these AP's could be serving both RJ-11 users as well as non-RJ-11 users. These statistics are per node. Current number of RJ-11 international access points (routers) connected to the UNC. Note, these AP's could be serving both RJ-11 users as well as non-RJ-11 users. This statistics is per node. To be implemented in future release (RDS10610). Currently, it will show zero value.
Number of URR Discovery Reject messages sent (Unspecified) to RJ11 sub Number of URR Registration Requests messages received for RJ11 user Number of URR Registration Accept messages sent for RJ11 user Number of URR Registration Reject messages sent (AP not allowed) for RJ11 user Number of URR Registration Reject messages sent (Network congestion) for RJ11 user Number of URR Registration Reject messages sent (IMSI not allowed) for RJ11 user Number of URR Registration Reject messages sent (Location not allowed) for RJ11 user Number of URR Registration Reject messages sent (Invalid UNC) for RJ11 user Number of URR Registration Reject messages sent (Geo location not known) for RJ11 user Number of URR Registration Reject messages sent (Unspecified)
105/128
Position 24 25 26
Field Name REGREDIRECTTX DEREGTX DEREGRX REGUPDULRX REGUPDDLTX KEEPALIVERX OTHERTX OTHERRX UMAMOREJCMOVLD UMALUPREJCMOVLD UMAMOREJDDFOVLD UMALUPREJDDFOVLD
27 28 29 30 31 32 33 34 35 36
Number of URR Register Update Downlink messages sent for RJ11 user Number of URR Keep Alive messages received from MS for RJ11 user. Number of times any other URR message sent to RJ11 user
Description for RJ11 user Number of URR Registration Redirect messages sent in response to URR Reg request for RJ11 user Number of URR Deregister messages sent because of network initiated de-registration for RJ11 user. Number of URR Deregister messages received for RJ11 user. Number of URR Register Update Uplink messages received for RJ11 user
Number of times any other URR message received to RJ11 user
UMA Mobile Origination calls rejected by URRCM due to IPM overload. UMA Location update rejected by URRCM due to IPM overload. UMA Mobile Origination calls rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs. UMA Location update rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs.
REGUPDREDIRECTTX
37
REGUPDREJECTANATX
38
REGUPDREJECTNCTX
39
REGUPDREJECTINATX
40
REGUPDREJECTLNATX
41 42
REGUPDREJECTUNSPECTX REGUPDREJECTGLNKTX
Number of URR Register Redirect sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "AP not allowed" sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "Network Congestion" sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "IMSI not allowed" sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "Location not allowed" sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "Unspecified" sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "Geo
106/128
Position
Field Name
43
REGUPDREJECTIUTX
44 45 46
ORIGCALLATT ORIGCALLSUCC ORIGEMERGNCYCALLATT
Description Location not known" sent by UNC in response to URR Register Update Uplink for RJ11 user. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of URR Deregister messages with reject cause of "Invalid UNC" sent by UNC in response to URR Register Update Uplink. Because the current UNC implementation does not send URR Deregister in responding to URR Register Update Uplink for RJ11, it will have zero value. Number of RJ11 originating call attempts. Pegged when UNC receives a URR Request message from RJ11 user with establishment cause code of mobile originating call. Number of RJ11 originating call successes. Pegged when Activate Channel message is sent to the RJ11 user. Number of RJ11 originating emergency call attempts. Pegged when UNC receives a Request message from RJ11 user with establishment cause code of emergency call Number of RJ11 originating emergency call successes. Pegged when UNC sends an Activate Channel message to RJ11 user for emergency call. Number of location update attempts received from RJ11 user. Pegged when UNC receives a Request message for Location update from RJ11 user. Number of RJ11 paging attempts. Pegged when UNC sends a Paging Request message to RJ11. Number of paging response messages received from RJ11 device. Pegged when UNC receives a Request message for paging response. Note: RJ11 is not a mobile device, therefore it shall always respond to paging message unless something is wrong with the device itself. Number of RJ11 terminating call successes. Pegged when Activate Channel message is sent to the RJ11 user. Note, there is no corresponding terminating call attempt counter. However, if paging request is sent only for terminating call attempts (no SMS), then PAGINGATT could be used for terminating call attempt counters.
47 48 49
ORIGEMERGNCYCALLSUCC LOCUPDATT PAGINGATT
50
PAGINGSUCC
51 52 53 54 55 56
TERMCALLSUCC RESERVED1 RESERVED2 RESERVED3 RESERVED4 RESERVED5
107/128
11.1.3 URR Connection, Channel, Call, Handover and Miscellaneous Information (UMAURRCONNCALLPERF) These pegs are captured on a node basis only by URR-P. Performance Group Name: UMAURRCONNCALLPERF File Naming Convention: UMAURRCONNCALLPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 Position STARTTIMESTAMP STOPTIMESTAMP Field Name Date and time performance interval started Date and time performance interval stopped Description
WSSNODENUM REQUESTRX
REQUESTACCEPTTX REQUESTREJECTTX CIPHMODECMDTX CIPHMODECOMPRX
WSS Node (CCM card) to which this record applies Number of URR Request messages received Number of URR Request Accept sent Number of URR Request Reject sent
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
ACTIVATECHTX ACTIVATECHACKRX
Number of URR Ciphering Mode Command sent Number of URR Ciphering Mode Complete received Number of URR Activate Channel sent Number of URR Activate Channel Ack received
ACTIVATECHFAILRX ACTIVATECHCOMPTX
CHMODEMODIFYTX CHMODEMODIFYACKRX RELEASETX RELEASECOMPRX
Number of URR Channel Mode Modify sent Number of URR Channel Mode Modify Acknowledge received Number of URR Release sent Number of URR Release Complete received
Number of URR Activate Channel Failure received Number of URR Activate Channel Complete sent
CLEARREQRX HOACCESSRX
HOCOMPRX HOREQUIREDRX HOCOMMANDTX HOFAILURERX PAGINGREQTX PAGINGRESPRX UPQUALINDTX UPDIRXFERRX
Number of URR Handover Command sent Number of URR Handover Failure received
Number of URR Handover Complete received Number of URR Handover Required received
Number of URR Clear Request received Number of URR Handover Access received
DOWNDIRXFERTX CLASSMARKENQTX CLASSMARKCHRX STATUSRX SYNCINFORX CURRCHANNELS PEAKCHANNELS OTHERTX OTHERRX
Number of URR Downlink Direct Transfer sent Number of URR Classmark Enquiry sent Number of URR Classmark Change received Number of URR Status received
Number of URR Uplink Quality Indication sent Number of URR Uplink Direct Transfer received
Number of URR Paging Request sent Number of URR Paging Response received
Number of URR Synchronization received Current number of channels assigned at the end of the poll interval Peak number of channels assigned Number of times any other URR message sent Number of times any other URR messaged received Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use
RESERVE1 RESERVE2 RESERVE3 RESERVE4
108/128
WSSNODENUM is key field and identifies the node (card) to which this record applies.
11.1.4 Call and Mobility Related BSSMAP Information (UMABSSMAPPERF) These pegs are captured on a node basis only by URR-P. Performance Group Name: UMABSSMAPPERF File Naming Convention: UMABSSMAPPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 Position STOPTIMESTAMP WSSNODENUM COMPL3INFOTX ASSIGNREQRX STARTTIMESTAMP Field Name Date and time performance interval stopped WSS Node (CCM card) to which this record applies Number of Complete Layer 3 Information sent Number of BSSMAP Assignment Request received Number of BSSMAP Assignment Failure sent Number of BSSMAP Assignment Complete sent Date and time performance interval started Description
ASSIGNFAILTX ASSIGNCOMPTX CLEARCMDRX CLEARCOMPTX
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
CLEARREQTX HOREQUESTRX HOREQACKTX HODETECTTX
Number of BSSMAP Clear Command received Number of BSSMAP Clear Complete sent
HOCOMPTX HOCOMMANDRX HOREQDTX HOREQDREJRX HOFAILTX HOSUCCRX
Number of BSSMAP Handover Complete sent Number of BSSMAP Handover Command received
Number of BSSMAP Handover Request Acknowledge sent Number of BSSMAP Handover Detect sent
Number of BSSMAP Clear Request sent Number of BSSMAP Handover Request received
Number of BSSMAP Handover Required sent Number of BSSMAP Handover Required Reject received Number of BSSMAP Handover Failure sent Number of BSSMAP Handover Succeeded received
HOREQTIMEREXP RESETRX RESETTX
HOPERFORMEDTX
RESETACKTX RESETACKRX
Number of BSSMAP Handover Performed sent Number of times Handover Request Timer (HOReqTimer) expired Number of BSSMAP Reset received Number of BSSMAP Reset sent Number of BSSMAP Reset Acknowledge sent Number of BSSMAP Reset Acknowledge received
CIPHERMODECMDRX CIPHERMODECOMPTX CIPHERMODEREJTX DTAPINDTX DTAPREQRX PAGINGRX
Number of BSSMAP Cipher Mode Command received Number of BSSMAP Cipher Mode Complete sent Number of BSSMAP Cipher Mode Reject sent Number of DTAP Indication sent Number of DTAP request received Number of BSSMAP Paging received
MSCINVTRACERX BSSINVTRACETX BSSINVTRACERX CMUPDTX CMUPDRX CMREQRX
Number of BSSMAP MSC Invoke Trace received Number of BSSMAP BSS Invoke Trace sent Number of BSSMAP BSS Invoke Trace received Number of BSSMAP Classmark Update sent
PERFLOCREQRX PERFLOCRSPTX
Number of BSSMAP Classmark Update received Number of BSSMAP Classmark Request received
Number of BSSMAP Perform Location Request received Number of BSSMAP Perform Location Response sent
109/128
40 41 42 43 44 46 47 48 49
Position
PERFLOCABTRX CNLSINFOTX CNLSINFORX OTHERTX OTHERRX
Field Name
Number of BSSMAP Perform Location Abort received Number of BSSMAP Connectionless Information sent
Description
Number of BSSMAP Connectionless Information received Number of times any other BSSMAP message sent Paging requests rejected due to overload Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use Number of times any other BSSMAP messaged received
45 *
PAGINGREJECTOVLD
WSSNODENUM is the key field, and identifies the node (card) to which this record applies. * added in Rel 3 SP9
110/128
11.1.5 UMA LDAP Interface Information (UMALDAPPERF) These pegs are captured on a node basis only by URR-CM. Performance Group Name: UMALDAPPERF File Naming Convention: UMALDAPPERF.YYMMDD-HHMM Number of records: Equals the number of IPM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 Position STARTTIMESTAMP WSSNODENUM SERCONEST STOPTIMESTAMP Field Name
WSS Node (IPM Card) to which this record applies Number of Subscriber DB queries attempted
Ending time of the performance interval
Description
SUBDBQUERIES APDBQUERIES STDBQUERIES QUERIESSENT ZDBQUERIES CGIDBQUERIES
Number of times connection with LDAP Server established. Number of Access Point DB queries attempted
Number of Service Type DB queries attempted Number of Zone DB queries attempted Number of queries successfully sent to LDAP Server
Number of CGI DB queries attempted
QUERIESFAILIE QUERIESFAILCB POLLTIMEDOUT DBENTRY NODBENTRY CONNBROKEN MIDBQUERIES RESERVE1 QUERIESTIMEDOUT RESERVE2 RESERVE3 RESERVE4
Number of queries not sent due to Internal Error Number of queries not sent because connection to LDAP Server was broken Number of times LDAP Interface returned a timeout (i.e. no response from LDAP server was received). This does not indicate an error. If this count is too high then the LDAP Poll Timer parameter value should be increased Number of times LDAP Interface returned a database entry Number of times LDAP Interface returned with no match in the DB for requested search key Number of times the LDAP Interface retuned a Connection broken indication Number of MapInfo DB queries attempted Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use Total number of queries to the UMA DBs that timed out
WSSNODENUM is the key field, and identifies the node (card) to which this record applies.
111/128
11.1.6 RR Cause Received Information (UMARRCSRXPERF) These pegs are captured on a node basis only by URR-P and count the number of times that the cause is received from the MS. Performance Group Name: UMARRCSRXPERF File Naming Convention: UMARRCSRXPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Position STARTTIMESTAMP WSSNODENUM STOPTIMESTAMP ABRELUNSPEC ABRELTIMEXP ABRELNOACT PREEMPTREL HOIMPTOR CHMODEUNACC FREQNOTIMP OTLGCA LLFAIL CALLAC Field Name Ending time of the performance interval Beginning time of the performance interval Description
WSS Node (CCM Card) to which this record applies Number of Abnormal Release, Channel Unacceptable Number of Abnormal Release, No Activity On Radio Path Number of Abnormal Release, Timer Expired Number of Abnormal Release, Unspecified
ABRELCHUNACC
UTRANCFGUN
Number of Preemptive Release
Number of UTRAN Configuration Unknown Number of Handover Impossible, Timing Advance Out Of Range Number of Channel Mode Unacceptable Number of Frequency Not Implemented Number of Lower Layer Failure
Number of Originator Or Talker Leaving Group Call Area Number of Call Already Cleared
SEMINCMSG MTNEORNI MTNCWIPS CONDIEERR NOCELLALL RESERVE1
INVMANINFO
Number of Semantically Incorrect Message
Number of Invalid Mandatory Information Number of Message Type Non-Existent Or Not Implemented Number of Message Type Nor compatible With Protocol State Number of Conditional IE Error Number of No Cell Allocation Available Number of Protocol Error Unspecified Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 4 for future use
PROTERRUNSPEC RESERVE2 RESERVE3 RESERVE4
112/128
11.1.7 RR Cause Sent Information (UMARRCSTXPERF) These pegs are captured on a node basis only by URR-P and count the number of times that the cause is sent to the MS. Performance Group Name: UMARRCSTXPERF File Naming Convention: UMARRCSTXPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Position STARTTIMESTAMP WSSNODENUM STOPTIMESTAMP ABRELUNSPEC ABRELTIMEXP ABRELNOACT PREEMPTREL HOIMPTOR CHMODEUNACC FREQNOTIMP OTLGCA LLFAIL CALLAC Field Name Ending time of the performance interval Beginning time of the performance interval Description
WSS Node (CCM Card) to which this record applies Number of Abnormal Release, Channel Unacceptable Number of Abnormal Release, No Activity On Radio Path Number of Abnormal Release, Timer Expired Number of Abnormal Release, Unspecified
ABRELCHUNACC
UTRANCFGUN
Number of Preemptive Release
Number of UTRAN Configuration Unknown Number of Handover Impossible, Timing Advance Out Of Range Number of Channel Mode Unacceptable Number of Frequency Not Implemented Number of Lower Layer Failure
Number of Originator Or Talker Leaving Group Call Area Number of Call Already Cleared
SEMINCMSG MTNEORNI
INVMANINFO MTNCWIPS CONDIEERR NOCELLALL RESERVE1 PROTERRUNSPEC RESERVE2 RESERVE3 RESERVE4
Number of Semantically Incorrect Message Number of Invalid Mandatory Information Number of Message Type Non-Existent Or Not Implemented Number of Message Type Nor compatible With Protocol State Number of Conditional IE Error Number of No Cell Allocation Available Number of Protocol Error Unspecified Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use
113/128
11.1.8 BSSMAP Cause Received Information (UMABSSMAPCSRXPERF) These pegs are captured on a node basis only by URR-P and count the number of times the particular cause is received from the Core Network (CN). Performance Group Name: UMABSSMAPCSRXPERF File Naming Convention: UMABSSMAPCSRXPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 Position STARTTIMESTAMP WSSNODENUM RADNFFAIL UPLKQUAL UPLKSTGH DWLKQUAL DWLKSTGH DISTANCE OMINT RSPMSCINV CALLCNTL RIFAILREV HOSUCC BETTERCELL DIRRETRY JOINGCC TRAFFIC REDLDINSC TLTCHISC RELTRIG EQUIPFAIL STOPTIMESTAMP RADINFMSGFAIL Field Name Ending time of the performance interval Beginning time of the performance interval Description
WSS Node (CCM Card) to which this record applies Number of Radio interface failure Number of Uplink Quality (this cause is received in a Handover Request) Number of Uplink Strength (this cause is received in a Handover Request) Number of Downlink Quality (this cause is received in a Handover Request) Number of Downlink Strength (this cause is received in a Handover Request) Number of Distance (this cause is received in a Handover Request) Number of O And M Intervention (this cause is received in a Handover Request) Number of Response To MSC Invocation (this cause is received in a Handover Request) Number of Call Control Number of Radio Interface Failure, Reversion To Old Channel Number of Radio interface message failure
Number of Handover Successful Number of Better Cell (this cause is received in a Handover Request) Number of Directed Retry (this cause is received in a Handover Request) Number of Joined Group Call Channel Number of Traffic Number of Reduce Load In Serving Cell (this cause is received in a Handover Request) Number of Traffic Load In Target Cell Higher Than In Source Cell Number of Relocation Triggered Number of Equipment Failure
NORADRESAVL RTRESUNAVL CCHOVL PROCOVL
Number of CCH Overload
Number of Requested Terrestrial Resource Unavailable
Number Of No Radio Resource Available
BSSNOTEQP MSNOTEQP INVCELL TRAFFICLOAD PREEMPTION
Number of Processor Overload Number of BSS Not Equipped Number of MS Not Equipped Number of Invalid Cell (this cause is received in a Handover Request) Number of Traffic Load (this cause is received in a Handover Request) Number of Preemption
114/128
Position 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
Field Name RETRRAUVL CPMISMATCH SCPOOL RSPVERUVL LSANOTALL CIPALNS
Number Of Requested Transcoding/Rate Adaptation Unavailable
Description
Number Of Circuit Pool Mismatch Number of Switched Circuit Pool (this cause is received in a Handover Request) Number Of Requested Speech Version Unavailable Number of LSA Not Allowed Number of Ciphering Algorithm Not Allowed Number of GERAN Lu-mode failure Number of Terrestrial Circuit Already Allocated Number of Invalid Message Contents Number Of Incorrect Value Number Of Information Element Or Field Missing Number Of Unknown Message Type
GELUMOFAIL TCALALLOC IEMISS INMSGCONT INCVAL UNIE
UNMSGTYPE PEBSSMSC VVCNE OTHER
Number Of Unknown Information Element Number Of VGCC/VBS Call Non Existent Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use Reserved Field 4 for future use
Number of Protocol Error Between BSS And MSC Number of times any other BSSMAP Cause value received
RESERVE2 RESERVE3 RESERVE4
RESERVE1
115/128
11.1.9 BSSMAP Cause Sent Information (UMABSSMAPCSTXPERF) These pegs are captured on a node basis only. These pegs are captured by URR-P and count the times the particular cause is sent to the Core Network (CN). Performance Group Name: UMABSSMAPCSTXPERF File Naming Convention: UMABSSMAPCSTXPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 Position STARTTIMESTAMP WSSNODENUM RADNFFAIL UPLKQUAL UPLKSTGH DWLKQUAL DWLKSTGH DISTANCE OMINT RSPMSCINV CALLCNTL HOSUCC RIFAILREV BETTERCELL DIRRETRY JOINGCC TRAFFIC REDLDINSC TLTCHISC RELTRIG EQUIPFAIL STOPTIMESTAMP RADINFMSGFAIL Field Name Ending time of the performance interval Beginning time of the performance interval Description
WSS Node (CCM Card) to which this record applies Number of Radio interface message failure Number of Radio interface failure
Number of Uplink Quality (this cause is sent in a Handover Required) Number of Uplink Strength (this cause is sent in a Handover Required) Number of Downlink Quality (this cause is sent in a Handover Required) Number of Downlink Strength (this cause is sent in a Handover Required) Number of Distance (this cause is sent in a Handover Required) Number of O And M Intervention (this cause is sent in a Handover Required) Number of Response To MSC Invocation (this cause is sent in a Handover Required) Number of Call Control Number of Radio Interface Failure, Reversion To Old Channel Number of Handover Successful Number of Better Cell (this cause is sent in a Handover Required) Number of Directed Retry (this cause is sent in a Handover Required) Number of Joined Group Call Channel Number of Traffic Number of Reduce Load In Serving Cell (this cause is sent in a Handover Required) Number of Relocation Triggered Number of Equipment Failure
Number of Traffic Load In Target Cell Higher Than In Source Cell
NORADRESAVL RTRESUNAVL CCHOVL PROCOVL
Number of CCH Overload
Number of Requested Terrestrial Resource Unavailable
Number Of No Radio Resource Available
BSSNOTEQP INVCELL MSNOTEQP
Number of Processor Overload Number of BSS Not Equipped Number of MS Not Equipped Number of Invalid Cell
TRAFFICLOAD PREEMPTION RETRRAUVL SCPOOL
Number of Traffic Load (this cause is sent in a Handover Required) Number of Preemption (this cause is sent in a Handover Required) Number Of Requested Transcoding/Rate Adaptation Unavailable Number Of Circuit Pool Mismatch Number of Switched Circuit Pool (this cause is sent in a Handover Required)
CPMISMATCH
116/128
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52
Position
RSPVERUVL LSANOTALL CIPALNS
Field Name
Number Of Requested Speech Version Unavailable Number of LSA Not Allowed Number of Ciphering Algorithm Not Allowed Number of GERAN Lu-mode failure Number of Terrestrial Circuit Already Allocated Number of Invalid Message Contents Number Of Incorrect Value Number Of Information Element Or Field Missing Number Of Unknown Message Type
Description
GELUMOFAIL TCALALLOC IEMISS INMSGCONT INCVAL UNIE
UNMSGTYPE PEBSSMSC VVCNE OTHER
Number Of Unknown Information Element Number Of VGCC/VBS Call Non Existent Reserved Field 1 for future use Reserved Field 3 for future use Reserved Field 4 for future use
Number of Protocol Error Between BSS And MSC Number of times any other BSSMAP Cause value sent Reserved Field 2 for future use
RESERVE2 RESERVE3 RESERVE4
RESERVE1
117/128
11.1.10 UNC Security Gateway Message Information (UMASGWPERF) These pegs are captured on a node basis only by URR-CM and are associated with the SA-IMSI Interface to the SGW. Performance Group Name: UMASGWPERF File Naming Convention: UMASGWPERF.YYMMDD-HHMM Number of records: Equals the number of IPM card pairs in the system, multiplied by the number of SGWs.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Position STOPTIMESTAMP WSSNODENUM SGWIP RANGESETRX CONFIGTX TUNQUERYTX TUNINFORX STARTTIMESTAMP Field Name Date and time performance interval stopped WSS Node (IPM card) to which this record applies Date and time performance interval started Description
TUNOUTOFRANGERX TUNRELEASETX TCPCONNREQ TCPCONNRELTO TCPCONNREL RESERVE1 RESERVE2 RESERVE3 RESERVE4
Number of Tunnel-Info messages received from SGW Number of Tunnel-Out-of-Range messages received from SGW Number of Tunnel-Release messages sent to SGW Number of times TCP connection requested by SGW Number of times TCP connection was released by UNC due to heartbeat timer expiration Number of times TCP connection release encountered at UNC (other than TCPCONNRELTO) Reserve Field 1 for future use Reserve Field 2 for future use Reserve Field 3 for future use Reserve Field 4 for future use
Number of Configuration messages sent to SGW Number of Tunnel-Query messages sent to SGW
The IP Address of the SGW to which this record applies Number of Range-Set messages received from SGW
WSSNODENUM and SGWIP are used as the key.
118/128
11.1.11 UNC-PS Message Information (UMAUNCPSPERF) These pegs are captured on a node basis. These pegs are captured by URR-CM. Performance Group Name: UMAUNCPSPERF File Naming Convention: UMAUNCPSPERF.YYMMDD-HHMM Number of records: Equals the number of IPM card pairs, multiplied by the total number of logical UNC-PS (Service Nodes) plus the number of GPRS gateways.
1 2 3 4 5 6 7 8 Position STOPTIMESTAMP WSSNODENUM GGWID SVCNODEID CONFIGINFREQTX CONFIGINFRESRX CONFIGINFUPDRX STARTTIMESTAMP Field Name Date and time performance interval stopped WSS Node (IPM card) to which this record applies Identifies the GPRS Gateway to which this record applies Identifies the UNC-PS within the GPRS Gateway to which this record applies. Number of Config Info Request sent to the GPRS Gateway Management Number of Config Info Result received from UNC-PS Number of Config Info Update received from UNC-PS Date and time performance interval started Description
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
SYSINFREQTX SYSINFRESRX
SYSINFUPDRX REGREQTX
REGUPDUPLTX DEREGTX DEREGRX GPRSSUSPTX GPRSRESTX GPRSRESRSLTRX PAGEREQRX SYNCINFOTX URLCMSGTX URLCMSGRX OTHERTX OTHERRX TCPCONNEST MSINITIATEDTCACT
Number of System Info Update received from UNC-PS Number of UPPS Register Request sent to UNC-PS Number of UPPS Update Uplink sent to UNC-PS Number of UPPS Deregister sent to UNC-PS
Number of System Info Req sent to UNC-PS Number of System Info Result received from UNC-PS
Number of URLC messages received from UNC-PS Number of any other messages sent
Number of UPPS Deregister received from UNC-PS Number of UPPS GPRS Suspension Request sent to UNC-PS Number of UPPS GPRS Resume Request sent to UNC-PS Number of UPPS GPRS Resume Result received from UNC-PS Number of UPPS Paging Request CS received from UNC-PS Number of UPPS Synchronization Information sent to UNC-PS Number of URLC messages sent to UNC-PS
27 26 27 28
NETWORKINITIATEDTCACT RESERVE1 RESERVE2 RESERVE3
Number of requested MS initiated URLC Transport Channel activations incremented when URLC-ACTIVATE-UTC-REQ is received from MS Number of requested Network Initiated URLC Transport Channel activations incremented when URLC-ACTIVATE-_UTC_REQ is sent to MS
Reserved Field 1 for future use Reserved Field 2 for future use Reserved Field 3 for future use
Number of any other messages received Number of times TCP connection was established with Service Node
119/128
29
Position
RESERVE4
Field Name
WSSNODENUM, GGWID and SVCNODEID are used as the key. The pegs CONFIGINFREQTX, CONFIGINFRESTX and CONFIGINFUPDRX are only counted on a GPRS Gateway basis. The special SVCNODEID value 256 is used with pegs that are only counted on a GPRS Gateway basis.
Description
120/128
11.1.12 Location Services UNC SMLC Interface Information These pegs are captured on a node basis only by URR-P Performance Group Name: UMALCSUNCPERF File Naming Convention: UMALCSUNCPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 14 15 16 17 Position STOPTIMESTAMP WSSNODENUM PERFLOCREQTX STARTTIMESTAMP Field Name
(UMALCSUNCPERF)
Date and time performance interval stopped WSS Node (CCM card) to which this record applies
Date and time performance interval started
Description
PERFLOCRESPSUCCRX PERFLOCRESPRX UMAPOSREQRX UMAPOSRESPTX UMAPOSRESPSUCCTX UMAPOSRESPMACRX UMAPOSRESPCGIRX UMAPOSRESPIPRX UMAPOSRESPIMSIRX UMAABORTTX UMAREJECTTX RESERVE1 RESERVE2 RESERVE3 RESERVE4
Number of Perform Location Request sent to SMLC Number of Perform Location Response with location estimate received from SMLC Total number of Perform Location Response received from SMLC Number of UMA Position Request received from SMLC Total number of UMA Position Response sent to SMLC Number of UMA Position Response with location sent to SMLC Number of AP MAC locations received in Perform Location Response from SMLC Number of AP CGI locations received in Perform Location Response from SMLC Number of AP IP locations received in Perform Location Response from SMLC Number of Subscriber locations received in Perform Location Response from SMLC Number of UMA Abort sent to SMLC Number of UMA Reject sent to SMLC Reserve Field 1 for future use Reserve Field 2 for future use
Reserve Field 3 for future use Reserve Field 4 for future use
121/128
11.1.13 Location Services UMADB UNC Message Information These pegs are captured on a node basis only by URR-CM. Performance Group Name: UMADBUNCPERF File Naming Convention: UMADBUNCPERF.YYMMDD-HHMM Number of records: Equals the number of IPM card pairs in the system.
1 2 3 4 5 6 7 8 9 Position STOPTIMESTAMP WSSNODENUM STARTTIMESTAMP Field Name Description
(UMADBUNCPERF)
UMADBLOCREQTX UMADBLOCRESPRX RESERVE1 RESERVE2 RESERVE3 RESERVE4
Date and time performance interval stopped WSS Node (IPM card) to which this record applies Number of UMA DB Location Request sent to UMA DB Number of UMA DB Location Response with location, received from UMA DB Reserve Field 1 for future use Reserve Field 2 for future use Reserve Field 3 for future use Reserve Field 4 for future use
WSSNODENUM is key field and identifies the node (card) to which this record applies
122/128
11.1.14 GMLC Message Information (UMAGMLCUNCPERF) These pegs are captured on a node basis only by URR-P. Performance Group Name: UMAGMLCUNCPERF File Naming Convention: UMAGMLCUNCPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
1 2 3 4 5 6 7 8 9 Position STOPTIMESTAMP WSSNODENUM STARTTIMESTAMP Field Name
GEOPOSREQINITRX GEOPOSRETRESINITTX GEOPOSREQUPDRX GEOPOSRETRESUPDTX RESERVE1 RESERVE2
10 11 12 13
Date and time performance interval stopped WSS Node (CCM card) to which this record applies Number of Geo Position Request (Initial) received from GMLC Number of Geo Position Return Result (Initial) sent to GMLC Number of Geo Position Request (Updated) received from GMLC Number of Geo Position Return Result (Updated) sent to GMLC Reserve Field 1 for future use Reserve Field 2 for future use Reserve Field 3 for future use Reserve Field 4 for future use
Description
Reserve Field 5 for future use Reserve Field 6 for future use
123/128
11.1.15 Location
This performance group is not currently implemented and will be implemented in future releases. These pegs are captured on a node basis only by SMLC. Performance Group Name: UMALCSSMLCPERF File Naming Convention: UMALCSSMLCPERF.YYMMDD-HHMM Number of records: Equals the number of IPM card pairs in the system.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Position STARTTIMESTAMP STOPTIMESTAMP PERFLOCREQRX PERFLOCRESPSUCCTX PERFLOCRESPTX UMAPOSREQTX UMAPOSRESPRX UMAPOSRESPSUCCRX UMAPOSRESPMACTX UMAPOSRESPCGITX UMAPOSRESPIPTX UMAPOSRESPIMSITX RESERVE1 RESERVE2 RESERVE3 RESERVE4 Field Name Date and time performance interval started Date and time performance interval stopped Description
FUTURE IMPLEMENTATION This performance group is not implemented in the Drop 3.0 (UMA2.1) UMA software release.
Services SMLC Information (UMALCSSMLCPERF)
WSSNODENUM
WSS Node (CCM card) to which this record applies Number of Perform Location Request received from UNC Number of Perform Location Response with location estimate sent to UNC Total number of Perform Location Response sent to UNC Number of UMA Position Request sent to UNC Total number of UMA Position Response received from UNC Number of UMA Position Response with location received from UNC Number of AP MAC locations sent in Perform Location Response to UNC Number of AP CGI locations sent in Perform Location Response to UNC Number of AP IP locations sent in Perform Location Response to UNC Number of Subscriber locations sent in Perform Location Response to UNC Reserve Field 1 for future use Reserve Field 2 for future use Reserve Field 3 for future use Reserve Field 4 for future use
124/128
11.2 UMA Performance Data Information in Call Server

11.2.1 Call and Handover Information (UMAPERF) These pegs are captured by Mobility Management at WSS on its interface to UNC. These pegs are on a per node basis. Performance Group Name: UMAPERF File Naming Convention: UMAPERF.YYMMDD-HHMM Number of records: Equals the number of CCM card pairs in the system.
Position 1 2 3 4 5 6 7 8 9 10 11 12 STARTTIMESTAMP STOPTIMESTAMP MOCALLATTEMPT MOCALLSUCC MTCALLATTEMPT MTCALLSUCC HOATT2GTOUMA HOSUCC2GTOUMA HOATTUMATO2G HOSUCCUMATO2G HOATTUMATOUMA Field Name Beginning time of the performance interval Ending time of the performance interval Description
WSSNODENUM
13 14 15 16 17
HOSUCCUMATOUMA MOESCALLATTEMPT MOESCALLSUCC NBRCLSMRKUPDT MSORIGCMSRVCREQ
WSS Node (CCM Card) to which this record applies. Number of attempted UMA mobile-originated calls (WSS receives DTAP Setup message from the MS). Number of successful UMA mobile-originated calls (WSS receives Assignment Complete from the UNC). Number of attempted UMA mobile-terminated calls (WSS sends DTAP Setup message to the MS). Number of successful UMA mobile-terminated calls (WSS receives Assignment Complete from the UNC). Number of Intra-MSC 2G to UMA Handovers attempted (WSS receives Handover Required from the serving BSS and the target cell belongs to UMA). Number of Intra-MSC 2G to UMA Handovers successfully completed (WSS receives Handover Complete from the target UNC and the MS was attached to a GSM BSS previously). Number of Intra-MSC UMA to 2G Handovers attempted (WSS receives Handover Required from the serving UNC and the target cell belongs to GSM). Number of Intra-MSC UMA to 2G Handovers successfully completed (WSS receives Handover Complete from the target BSS and the MS was attached to UNC previously). Number of Intra-MSC UMA to UMA Handovers attempted (WSS receives Handover Required from a serving UNC and the target cell belongs to UMA). Currently not supported, for future use. Number of Intra-MSC UMA to UMA Handovers successfully completed (WSS receives Handover Complete from the target UNC and the MS was attached to UNC previously). Currently not supported, for future use. Number of attempted UMA mobile-originated emergency calls (WSS receives DTAP Emergency Setup message from the MS). Number of successful UMA-mobile originated emergency calls (WSS receives Assignment Complete from the UNC for an emergency call). Number of Classmark Updates pegged when Class mark update message received. CM Service Request from originating MS pegged when CM service request message received from originating UMA
125/128
Position 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
Field Name ANSMSORIGCALLS ANSMSTERCALLS MSEMRGNCYCMSRVCREQ ANSMSEMRGNCYCALLS ATTCIPHRMDCTRPROCS SUCCCIPHRMDCTRPROCS TRANSSUBIDWTMSI TRANSSUBIDWIMSI ATTTMSIREALOC SUCCTMSIREALOC IMSIDETACHPROCS IMSIATTACHPROCS IMPLICITDETACH
Description MS. Number of answered calls for mobile originating traffic pegged when connect ack message is received from UMA MS. Number of answered calls for mobile terminating traffic pegged when connect ack message is sent to UMA MS. Number of Emergency CM Service Requests is received from originating UMA MS. Number of answered emergency calls when connect ack is received from originating UMA MS. Number of ciphering mode control procedures transmitted to UMA MS. Number of successful ciphering mode control procedures Number of transactions where mobile subscriber was identified with his TMSI Number of transactions where mobile subscriber was identified with his IMSI Number of TMSI re-allocation attempts Number of successfully performed TMSI re-allocations Number of IMSI Detach procedures
ATTINEXTINTRAMSCHDO SUCCOUTEXTINTRAMSCHDO UNSCCEXTHDORECNCTPER MSC UNSCEXTHDOLOSSCNCTPE RMSC SUCCINTRAHOCTMCALLS SUCCINTERINHOCTMCALLS ATTINTRAHOCTMCALLS ATTINTERINHOCTMCALLS ATTINTERVLRLOCUPD SUCCINTERVLRLOCUPD
Number of IMSI Attach procedures received from UMA MS. Total number of subscribers implicitly detached (i.e. by VLR audit) Number of intra-MSC target cell 2G to UMA handover procedures initiated pegged on dispatch of BSSMAP:Handover Request to target UNC Number of intra-MSC serving cell 2G to UMA handover procedures successfully completed pegged on receipt of BSSMAP:Handover complete from target UNC. Number of unsuccessful 2G to UMA Handovers with reconnect to the original channels pegged when HO failure received from the serving BSS. Number of unsuccessful 2G to UMA Handovers with loss of the call pegged when Clear Request message is received from the serving BSS. Number of successful Intra-MSC UMA HO for CTM Calls. These counters will be zero since they are not supported in this release. Number of successful Incoming Inter-MSC HO for CTM Calls. These counters will be zero since they are not supported in this release Number of attempted Intra MSC HO CTM Calls. These counters will be zero since they are not supported in this release Number of attempted Incoming Inter-MSC HO for CTM Calls. These counters will be zero since they are not supported in this release Number of attempted (incoming) inter VLR location update Number of successful (incoming) inter VLR location update Number of attempted intra VLR location update (all types) Number of attempted periodic intra VLR location update
ATTINTRAVLRLOCUPD ATTPERIINTRAVLRLOCUPD SUCCINTRAVLRLOCUPD
Number of successful intra VLR location update (all types)
SUCCPERIINTRAVLRLOCUPD Number of successful periodic intra VLR location update ATTAUTH Number of attempted Authentication procedures SUCCAUTH ATTPAGEMSTMSI
Number of successful Authentication procedures Number of Paging Attempts (within LAC) with TMSI pegged
126/128
Position
Field Name SUCCPAGEMSTMSI ATTPAGEMSIMSI SUCCPAGEMSIMSI
48
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70
Number of Successful Paging (within LAC) with IMSI Number of Search Attempts with IMSI, after the first Page to ATTSEARCHMSIMSI UMA fails Number of Successful Searches with IMSI, after the first SUCCSEARCHMSIMSI Page to UMA fails Number of Location Updates rejected due to visitors PLMN REJLUPPLMNNOTALLOWED 68 not allowed. LUP Rejection Cause value is 11. Number of Location Updates rejected due to Location Area REJLUPLACNOTALLOWED 69 not allowed. LUP Rejection Cause value is 12. Number of Location Updates rejected due to roaming not REJLUPROAMNOTALLOWED allowed in this location area. LUP Rejection Cause value is 70 13. REJLUPIMSIUNKINHLR Location Update failed, cause = IMSI unknown in HLR REJLUPILLEGALMS Location Update rejected, cause = Illegal MS REJLUPILLEGALME Location Update rejected, cause = Illegal ME REJLUPNOSUITCELLINAREA Location Update rejected, cause = No Suitable cell in area REJLUPNETWORKFAIL Location Update rejected, cause = Network failure Reserved1 Reserved field 1 for future use Reserved2 Reserved field 2 for future use Reserved3 Reserved4 Reserved5 Reserved6 Reserved7 Reserved8 Reserved field 3 for future use Reserved field 4 for future use Reserved field 5 for future use Reserved field 6 for future use Reserved field 7 for future use Reserved field 8 for future use
Number of Successful Paging (within LAC) with TMSI Number of Paging Attempts (within LAC) with IMSI pegged when paging message is sent with IMSI.
Description when paging message is sent with TMSI and IMSI.
Reserved9 Reserved10
127/128
END OF DOCUMENT
128/128

Alcatel Performance Data Measurement

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Alcatel Performance Data Measurement

Загружено:

Авторское право:

Доступные форматы

COVER SHEET

Performance Data Measurements

Edition Date Change Note

Alcatel SE Harinder Lakhian

A5020 ATRIUM Wireless Call Server (WCS) GSM/UMA CS CORE NETWORK

TECHNICAL REQUIREMENT SPECIFICATION

Performance Data Measurements GSM/UMA

NMS INTERFACE A BRIEF SUMMARY.................................................................................... 10 2.1 2.2

ATRIUM 3.1 3.2

General File Format ........................................................................................................ 12 Reserve Fields ................................................................................................................. 13

IN RELATED INFORMATION ....................................................................................................... 79 7.1 7.2

6.6 6.7 6.8

FACILITIES PERFORMANCE DATA............................................................................................ 85

10 CONFIGURATION DATA .............................................................................................................. 99 10.1 10.2 10.3 10.4

11 UMA PERFORMANCE DATA INFORMATION .......................................................................... 103

This document describes the performance and data measurements for:

1.2 Definitions & Abbreviations

VLR VMSC WEM WMG WSS

NMS INTERFACE A BRIEF SUMMARY

2.2 Data Collection and Retention

ATRIUM MSC PERFORMANCE DATA

3.1 General File Format

SYSTEM PERFORMANCE DATA

4.1 WSS System Performance Information (SUMMARYPERF)

TOTALACTSUBS MMCALLATT MLCALLATT LMCALLATT LLCALLATT INTERVLRLUPCALLATT INTRAVLRLUPCALLATT AUTHENTICATIONCALLATT SMSCALLATT

ATTINTERVLRLOCUPD for all CCM cards.

ATTINTRAVLRLOCUPD for all CCM cards. all CCM cards.

BSSAPSMSPERF by adding CALLATTMSORGSMS and CALLATTMSTERMSMS for all CCM cards.

UNSCCEXTHDORECNCTPERMSC UNSCEXTHDOLOSCNCTPERMSC ATTINTERMSCHOHI SUCCINTERMSCHOHI

As measured at the end of the performance interval. 15/128

SUCCINTERMSCHOHO MNPDBQUERIES MNPDBNEGRESP

MLCALLFAILURERATE LMCALLFAILURERATE LLCALLFAILURERATE LUPFAILURERATE

SUCCINTERVLRLOCUPD) / (ATTINTRAVLRLOCUPD + ATTINTERVLRLOCUPD))}*100

CALLSUCCMSTERMSMS) /( CALLATTMSORGSMS + CALLATTMSTERMSMS )}*100

(SUCCMSORIGCALLS+ SUCCMSEMRGCYCALLS + ISUPPFMACMTX+ BICCPFMACMTX ) /( ATTMSORIGCALLS+ ATTMSEMRGCYCALLS + ISUPPFMIAMRX+BICCPFMIAMRX)}*100

Reserved field 10 for future use

,\nAA aaa:##\nBB bbb:##\nCC ccc:##,

4.2 WSS Overload Control Information (MOOVLDPERF)

WSSNODENUM OVRLDRJCTMOVCALL OVRLDRJCTLUP OVRLDRJCTMOSMSCALL OVRLDRJCTMOCISSCALL RESERVED2 RESERVED3 RESERVED4 RESERVED1

4.3 ISUP Network Overload Control Information (ISUPOVLDPERF)

IBCALLRJTATRLVL1 IBCALLRJTATRLVL2 IBCALLRJTATRLVL3 OBCALLRJTLCLLVL1 OBCALLRJTLCLLVL2

4.4 Media Gateway Control (MEGACO) Information (CALLEGCPPERF)

CALLATTMGCADD CALLSUCCMGCADD CALLATTMGCMODIFY CALLSUCCMGCMODIFY CALLATTMGCMOVE

CALLSUCCMGCMOVE CALLATTMGCSUBTRACT CALLSUCCMGCSUBTRACT RESERVED1 RESERVED2 RESERVED3 RESERVED4

4.5 WMG CPU Usage Information (MSFCPULOAD)

STARTTIMESTAMP STOPTIMESTAMP MSFNODEID MSFSLOTID

MSFCPUID MSFCPULOAD1SEC MSFCPULOAD5SEC MSFCPULOAD15SEC MSFCPULOAD30SEC MSFCPULOAD1MIN MSFCPULOAD5MIN MSFCPULOAD15MIN

4.6 WSS Performance Information (WSSPERF)

Added by PR 10889 Added by PR 10889 25/128

4.7 WSS Disk Performance Information (WSSDISKPERF)

Added by PR 10889 Added by PR 10889 26/128

SIGNALING PERFORMANCE DATA

5.1 MTP2 Link Information (SYSMTP2LINKPERF)

Performance Group Name: SYSMTP2LINKPERF File Naming Convention: SYSMTP2LINKPERF.YYMMDD-HHMM.###

STARTTIMESTAMP STOPTIMESTAMP GATEWAYNO

LNKID MTP2LNKPFMLINKINSVCTIME MTP2LNKPFMLINKFAILTOTAL MTP2LNKPFMLINKLCLBUSY

MTP2LNKPFMLINKFAILABNFIBBSNR MTP2LNKPFMLINKFAILT7EXP MTP2LNKPFMLINKFAILCONG MTP2LNKPFMALIGNFAIL MTP2LNKPFMSUERRS MTP2LNKPFMLINKFAILSUERM

Date and time performance interval started.

MTP2LNKPFMNACKRX MTP2LNKPFMMSUOCTETRETX MTP2LNKPFMMSUTX MTP2LNKPFMMSURX

5.2 MTP3 Link Information (SYSMTP3LINKPERF)

Performance Group Name: SYSMTP3LINKPERF File Naming Convention: SYSMTP3LINKPERF.YYMMDD-HHMM.###

STOPTIMESTAMP WSSNODENUM GATEWAYNO LNKID

Date and time performance interval started.