alcatel performance data measurement

3BL76533FAAADSZZA Edition 07 1/128

COVER SHEET

Title Performance Data Measurements

Classification A5020 ATRIUM Wireless Call Server (WCS)

GSM/UMA CS CORE NETWORK SYSTEM DOCUMENTATION TECHNICAL REQUIREMENT SPECIFICATION

Edition 07 Date 2008-05-02 Change Note Appraisal Authority

Company Alcatel Function Name

Originator Company Alcatel Function SE Name Harinder Lakhian


Originator(s) Harinder Lakhian

Approval(s)

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 Creation 02 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

03 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

04 Added all DSP pool types in DSP usage group, added cause codes to SYSGRP

05 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

06 New counters added in CALLPERF group by Rel 3 SP9 are highlighted in Red bold color and shaded in grey.

07 New UMARJ11URRPERF performance group added in Rel 3 SP9


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

SYSTEM DOCUMENTATION TECHNICAL REQUIREMENT SPECIFICATION

Performance Data Measurements GSM/UMA


Table of contents

1 OVERVIEW ...................................................................................................................................... 7 1.1 Compatibility ..................................................................................................................... 7 1.2 Definitions & Abbreviations............................................................................................. 7

2 NMS INTERFACE – A BRIEF SUMMARY.................................................................................... 10 2.1 Data Storage .................................................................................................................... 10 2.2 Data Collection and Retention....................................................................................... 10

2.2.1 Data Transfer..................................................................................................... 11 3 ATRIUM® MSC PERFORMANCE DATA ..................................................................................... 12

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

4 SYSTEM PERFORMANCE DATA ................................................................................................ 14 4.1 WSS System Performance Information (SUMMARYPERF) ........................................ 14 4.2 WSS Overload Control Information (MOOVLDPERF).................................................. 19 4.3 ISUP Network Overload Control Information (ISUPOVLDPERF)................................ 20 4.4 Media Gateway Control (MEGACO) Information (CALLEGCPPERF)......................... 22 4.5 WMG CPU Usage Information (MSFCPULOAD)........................................................... 23 4.6 WSS Performance Information (WSSPERF)................................................................. 25 4.7 WSS Disk Performance Information (WSSDISKPERF) ............................................... 26

5 SIGNALING PERFORMANCE DATA ........................................................................................... 27 5.1 MTP2 Link Information (SYSMTP2LINKPERF) ............................................................. 27 5.2 MTP3 Link Information (SYSMTP3LINKPERF) ............................................................. 28 5.3 MTP3 Linkset Information (SYSMTP3LINKSETPERF)................................................. 30 5.4 MTP3 Route Information (SYSMTP3ROUTEPERF)...................................................... 31 5.5 ISUP DPC Information (SYSISUPDPCPERF) ................................................................ 33 5.6 BICC DPC Information (SYSBICCDPCPERF) ............................................................... 36 5.7 SCCP Information (SYSSCCPPERF) ............................................................................. 39 5.8 CAP (CAMEL Application Part) Information (CAPMSGPERF).................................... 41 5.9 INAP Information (INAPMSGPERF)............................................................................... 44 5.10 IS-41 Information (IS41MSGPERF) ................................................................................ 47 5.11 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

6 CALL-RELATED & GSM / MOBILITY PERFORMANCE DATA .................................................. 60 6.1 Call Control & Features Information (CALLPERF)....................................................... 60 6.2 MAP Information – Gateway MSC (MAP1PERF) .......................................................... 64 6.3 MAP Information – Visited/Serving MSC (MAPPERF) ................................................. 65 6.4 BSSAP (A-Interface) and Mobile Call Information (BSSAPPERF).............................. 68 6.5 IS41 Information (IS41PERF).......................................................................................... 71


6.6 SMS Information – A-Interface Related (BSSAPSMSPERF) ....................................... 72 6.7 Call Independent Supplementary Services Information (CISSPERF)........................ 73 6.8 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

7 IN RELATED INFORMATION ....................................................................................................... 79 7.1 INAP Information (INAPGWYPERF) .............................................................................. 79 7.2 CAMEL Information (CAPPERF).................................................................................... 80

8 REGULATORY SERVICES INFORMATION ................................................................................ 81 8.1 Wireless Priority Service (WPS) Information (PRIORITYCALLPERF) ....................... 81 8.2 Emergency Call (E911) Information (EMERGENCYCALLPERF) ................................ 83 8.3 Emergency Routing Key (ESRK) Information (ESRKPOOLPERF)............................. 84

9 FACILITIES PERFORMANCE DATA............................................................................................ 85 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

10 CONFIGURATION DATA .............................................................................................................. 99 10.1 Trunk Group Information ( TRKGP_WMG_RELATIONSHIP) ...................................... 99 10.2 WMG Information( WMG_ID_NAME_RELATIONSHIP) .............................................. 100 10.3 Interconnect Information( ICON_WMG_RELATIONSHIP) ......................................... 101 10.4 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


[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


1 OVERVIEW 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.

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)

1.2 Definitions & Abbreviations AP Access Point BCSM Basic Call State Model BICC Bearer Independent Call Control BSSMAP BSS Management Application Part CAMEL Customized Application for Mobile Network Enhanced Logic CAP CAMEL Application Part CCM Call Control Module CCS7 Common Channel Signaling System #7 CF Call Forwarding CIC Circuit Identification Code CISS Call Independent Supplementary Service CPU Central Processing Unit CS Circuit Switch CTM Cellular TTY Modem DDM Data Distribution Module DER Discrete Event Registration DMSC Distributed (Visited/Serving) MSC DN Directory Number DP Detection Point DPC Destination Point Code EMS Element Management System ETC Establish Temporary Connection ESRK Emergency Routing Key FCI Forward Call Indicator GEDI Gestion Electronique de Documents Intranet


HLR Home Location Register ICON Interconnect IMEI International Mobile subscriber Equipment Identity IMSI International Mobile Subscriber Identity INAP IN Application Part IS-41 Interim Standard 41 ISDN Integrated Services Digital Network IWF Interworking Function GMSC Gateway MSC GMT Greenwich Mean Time (see UTC) GSM Global System for Mobile Communication GUI Graphical User Interface LAC Location Area Code LNP Local Number Portability LRN Location Number Routing MAP Mobile Application Part MM Mobility Management MO Mobile Originated MT Mobile Terminated MS Mobile Station MSC Mobile Services Switching Center MSRN Mobile Subscriber Routing Number NE Network Element NMS Network Management System NPDB Number Portability Database OAM Operation, Administration and Maintenance QoS Quality of Service Ph2 Phase-2 PS Packet Switch PSTN Public Switched Telephone Network PVLR Previous VLR SAM System Administration Module SAPI Service Access Point Identifier SCP Service Control Point SI Status Inspection SIM Signaling Interface Module SMS Short Message Service SNMP Simple Network Management Protocol SS Supplementary Service T-CSI Terminating CAMEL Service Information TCP/IP Transmission Control Protocol/Internet Protocol TDD Telecommunications Device for the Deaf (Please refer to CTM) TDM Time Domain Multiplexing (tradition circuit-switch trunk facilities) TMN Telecommunications Management Network TMSI Temporary Mobile Subscriber Identity TRS Technical Requirement Specification TTY Text Telephony (Please refer to CTM) UMA Unlicensed Mobile Access UMAN Unlicensed Mobile Access Network UMTS Universal Mobile Telecommunication System UNC UMA Network Controller URLC UMA Radio Link Controller URR UMA Radio Resource USS Unstructured Supplementary Service UTC Universal Coordinated Time


VLR Visitor Location Register VMSC Visited MSC WEM Wireless Element Manager WMG Wireless Media Gateway WSS Wireless SoftSwitch


2 NMS INTERFACE – A BRIEF SUMMARY 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 All WSS history files are saved to dual disks for redundancy. These files are written to sub-directories, 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 day’s data is overwritten.


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.


3 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.


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. Alcatel’s 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.


4 SYSTEM PERFORMANCE DATA

4.1 WSS System Performance Information (SUMMARYPERF) Performance Group Name: SUMMARYPERF File Naming Convention: SUMMARYPERF.YYMMDD-HHMM Number of records: 1

Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 MAXSIMCPU Highest value of maximum CPU occupancy across all configured SIM

cards (%), derived from WSSPERF. 4 MAXDDMCPU Highest value of maximum CPU occupancy across all configured DDM

cards (%), derived from WSSPERF. 5 MAXCCMCPU Highest value of maximum CPU occupancy across all configured CCM

cards (%), derived from WSSPERF. 6 MAXSAMCPU Highest value of maximum CPU occupancy across all configured SAM

cards (%), derived from WSSPERF. 7 MAXIPMCPU Highest value of maximum CPU occupancy reached across all

configured IPM cards (%),derived from WSSPERF. 8 MEANSIMCPU Mean CPU occupancy reached across all SIM cards (%),derived from

WSSPERF as an average of the reported mean for all SIM cards. 9 MEANDDMCPU Mean CPU occupancy reached across all DDM cards (%),derived from

WSSPERF as an average of the reported mean for all DDM cards... 10 MEANCCMCPU

Mean CPU occupancy reached across all CCM cards (%), derived from WSSPERF as an average of the reported mean for all active CCM cards.

11 MEANSAMCPU Mean CPU occupancy reached across all active SAM cards (%), derived from WSSPERF as an average of the reported mean for all SAM cards.

12 MEANIPMCPU Mean CPU occupancy reached across all IPM cards (%), derived from WSSPERF as an average of the reported mean for all IPM cards.

13 ROOTDISKOCCACTSAM Disk occupancy percentage (/root partition) on Primary SAM (%)1 derived form WSSDISKPERF

14 VARDISKOCCACTSAM Disk occupancy percentage (/var partition) on Primary SAM (%) derived form WSSDISKPERF

15 SPACEDISKOCCACTSAM Disk occupancy percentage (/space partition) on Primary SAM (%) derived form WSSDISKPERF

16 ROOTDISKOCCSTBSAM Disk occupancy percentage (/root partition) on Secondary SAM (%) derived form WSSDISKPERF

17 VARDISKOCCSTBSAM Disk occupancy percentage (/var partition) on Secondary SAM (%) derived form WSSDISKPERF

18 SPACEDISKOCCSTBSAM Disk occupancy percentage (/space partition) on Secondary SAM (%) derived form WSSDISKPERF

19 AVAILSIMMEMORY Minimum memory available on any SIM card (%), derived from WSSPERF.

20 AVAILDDMMEMORY Minimum memory available on any DDM card (%), derived from WSSPERF.

21 AVAILCCMMEMORY Minimum memory available on any CCM card (%) from all configured active CCM cards, derived from WSSPERF.

22 AVAILSAMMEMORY Minimum memory available on any SAM card (%), derived from WSSPERF.

23 AVAILIPMMEMORY Minimum memory available on any IPM card (%), derived from WSSPERF.

24 TOTALCALLATT Total number of call attempts per hour (normalized) –all types. This is 1 Fields 13 through 18 are measured at the end of the performance interval.


Position Field Name Description derived from BSSAPPERF, UMAPERF, SYSISUPDPCPERF, SYSBICCDPCPERF, and MOOVLDPERF by adding MSORIGCMSRVCREQ + MSEMRGNCYCMSRVCREQ + ISUPPFMIAMRX + BICCPFMIAMRX + OVRLDRJCTMOVCALL

25 TOTALACTSUBS Total number of subscribers in VLR2. This is a snapshot of VLR database, total active and inactive subs.

26 MMCALLATT Total number of Mobile-to-Mobile call attempts per hour (normalized), derived from CALLPERF by adding CALLATTMSTOMSVCCAL+ CALLATTUMATO2GVCCAL+ CALLATTUMATOUMAVCCAL+ CALLATT2GTOUMAVCCAL for all CCM cards.

27 MLCALLATT Total number of Mobile-to-Land call attempts per hour (normalized), derived from CALLPERF by adding CALLATTMSTOPSTNVCCAL + CALLATTUMATOPSTNVCCAL for all CCM cards.

28 LMCALLATT Total number of Land-to-Mobile call attempts per hour (normalized), derived from CALLPERF by adding CALLATTPSTNTOMSVCCAL + CALLATTPSTNTOUMAVCCAL for all CCM cards.

29 LLCALLATT Total number of Land-to-Land call attempts per hour (normalized), derived from CALLPERF by adding CALLATTLANDTOLANDVCCAL for all CCM cards.

30 INTERVLRLUPCALLATT Total number of Inter-VLR Location Update attempts per hour (normalized), derived from BSSAPPERF and UMAPERF by adding ATTINTERVLRLOCUPD for all CCM cards.

31 INTRAVLRLUPCALLATT Total number of Intra-VLR Location Update attempts per hour (normalized), derived from BSSAPPERF and UMAPPERF by adding ATTINTRAVLRLOCUPD for all CCM cards.

32 AUTHENTICATIONCALLATT Total number of Mobile Authentication Requests per hour (normalized), derived from BSSAPPERF and UMAPPERF by adding ATTAUTH for all CCM cards.

33 SMSCALLATT Total SMS (MO plus MT) Attempts per hour (normalized), derived from BSSAPSMSPERF by adding CALLATTMSORGSMS and CALLATTMSTERMSMS for all CCM cards.

34 SSINVOCATIONCALLATT

Total Number of Supplementary Service invocations per hour (normalized), derived from CALLPERF by adding of INVOKECFUSS, INVOKECFBSS, INVOKECFNRYSS, INVOKECFNRCSS, INVOKECALLWAITSS, INVOKEECTSS, INVOKEMULTIPTYSS for all CCM cards.

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 cards.

36 SUCCINTRAMSCHO 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.

37 UNSCCEXTHDORECNCTPERMSC 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 CCM cards.

38 UNSCEXTHDOLOSCNCTPERMSC 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.

39 ATTINTERMSCHOHI Total number of attempted Inter MSC Handovers (Incoming) per hour (normalized). Derived from MAPPERF by adding (ATTININTERMSCHDO + ATTSUBSQNTINTERMSCHDOMSCA + ATTSUBSQNTINTERMSCHDOMSCC) for all CCM cards.

40 SUCCINTERMSCHOHI Total number of successful Inter MSC Handovers (Incoming) per hour (normalized). Derived from MAPPERF by adding

2 As measured at the end of the performance interval.


Position Field Name Description (SUCCININTERMSCHDO + SUCCSUBSQNTINTERMSCHDOMSCA + SUCCSUBSQNTINTERMSCHDOMSCC) for all CCM cards.

41 ATTINTERMSCHOHO Total number of attempted Inter MSC Handovers (Outgoing) per hour (normalized). Derived from MAPPERF by adding (OUTINTERMSCHDO + ATTOUTSUBINTERMSCHOMSCA + ATTOUTSUBINTERMSCHOMSCC) for all CCM cards.

42 SUCCINTERMSCHOHO Total number of successful Inter MSC Handovers (Outgoing) per hour (normalized). Derived from MAPPERF by adding (SUCCOUTINTERMSCHDO + SUCCOUTSUBINTERMSCHOMSCA + SUCCOUTSUBINTERMSCHOMSCC) for all CCM cards.

43 MNPDBQUERIES Total number of queries sent to NPDB per hour (normalized). Derived from CALLPERF by adding LNPDIPTOTAL for all CCM cards.

44 MNPDBNEGRESP Total number of unsuccessful NPDB queries per hour (normalized). Derived from CALLPERF as: LNPDIPTOTAL - LNPDIPRESULTLRN – LNPDIPNONPORTED for all CCM cards

45 MEANHOLDTIMEMOBILETOMOBILE

Mean Mobile-to-Mobile Call Holding Time3, 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.

46 MEANHOLDTIMEMOBILETOLAND 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.

47 MEANHOLDTIMELANDTOMOBILE 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.

48 MEANHOLDTIMELANDTOLAND 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.

49 MMCALLFAILURERATE Mobile-to-Mobile Call Failure Rate (%)4, derived from CALLPERF: {1- (CALLSUCCMSTOMSVCCAL+ CALLSUCCUMATO2GVCCAL + CALLSUCCUMATOUMAVCCAL+ CALLSUCC2GTOUMAVCCAL) /(CALLATTMSTOMSVCCAL+ CALLATTUMATO2GVCCAL + CALLATTUMATOUMAVCCAL+ CALLATT2GTOUMAVCCAL))}*100

50 MLCALLFAILURERATE Mobile-to-Land Call Failure Rate (%), derived from CALLPERF: {1- (CALLSUCCMSTOPSTNVCCAL+ CALLSUCCUMATOPSTNVCCAL) /(CALLATTMSTOPSTNVCCAL+ CALLATTUMATOPSTNVCCAL)}*100

51 LMCALLFAILURERATE Land-to-Mobile Call Failure Rate (%), derived from CALLPERF: {1- (CALLSUCCPSTNTOMSVCCAL+ CALLSUCCPSTNTOUMAVCCAL) /(CALLATTPSTNTOMSVCCAL+ CALLATTPSTNTOUMAVCCAL)}*100

52 LLCALLFAILURERATE Land-to-Land Call Failure Rate (%), derived from CALLPERF: {1- (CALLSUCCLANDTOLANDVCCAL /CALLATTLANDTOLANDVCCAL)}*100

53 LUPFAILURERATE Location Update Failure Rate (%), derived from BSSAPPERF and UMAPPERF as: {1- ((SUCCINTRAVLRLOCUPD + SUCCINTERVLRLOCUPD) / (ATTINTRAVLRLOCUPD + ATTINTERVLRLOCUPD))}*100

3 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.


Position Field Name Description

54 SMSFAILURERATE SMS Failure Rate – Including MO and MT (%) derived from BSSAPSMSPERF as: {1 - (CALLSUCCMSORGSMS + CALLSUCCMSTERMSMS) /( CALLATTMSORGSMS + CALLATTMSTERMSMS )}*100

55 AUTHFAILURERATE Authentication Failure Rate (%) derived from BSSAPPERF and UMAPPERF as: {1 - (SUCCAUTH / ATTAUTH)}*100

56 TOTALCALLFAILURERATE

Calls failing during setup – all call types (%) derived from BSSAPPERF, UMAPPERF SYSISUPDPCPERF, and SYSBICCDPCPERF as: {1- (SUCCMSORIGCALLS+ SUCCMSEMRGCYCALLS + ISUPPFMACMTX+ BICCPFMACMTX ) /( ATTMSORIGCALLS+ ATTMSEMRGCYCALLS + ISUPPFMIAMRX+BICCPFMIAMRX)}*100

57 MAXTXLINKOCC Maximum transmit link occupancy5 reached - across all SS7 links (%) 58 MAXRXLINKOCC Maximum receive link occupancy6 reached - across all SS7 links (%) 59 MAXTXLINKOCCPERLS Maximum transmit link occupancy reached – across all links in the

specified linkset (% - special format see below) 60 MAXRXLINKOCCPERLS Maximum receive link occupancy reached – across all links in the

specified linkset (% - special format see below) 61 MEANTXLINKOCCPERLS Average (mean) transmit link occupancy across all links in the specified

linkset (% - special format see below) 62 MEANRXLINKOCCPERLS Average (mean) receive link occupancy across all links in the specified

linkset (% - special format see below) 63 MAXTRUNKGROUPOCC Maximum trunk group occupancy reached (across all groups) (%) 64 MAXTRUNKOCCPERTG Maximum trunk group occupancy reached – in the specified trunk group

(% - special format see below) 65 MEANTRUNKOCCPERTG Average (mean) trunk group occupancy – in the specified trunk group (%

- special format see below) 66 Reserved1 Reserved field 1 for future use 67 Reserved2 Reserved field 2 for future use 68 Reserved3 Reserved field 3 for future use 69 Reserved4 Reserved field 4 for future use 70 Reserved5 Reserved field 5 for future use 71 Reserved6 Reserved field 6 for future use 72 Reserved7 Reserved field 7 for future use 73 Reserved8 Reserved field 8 for future use 74 Reserved9 Reserved field 9 for future use 75 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:

5 The formula used for this counters is derived from SYSMTP3LINKPERF group as follow:

( )

++= kbpsinBandwidthLinkXLNKPFMMSUTMTPCTTXLNKPFMSIOOMTPCTTXLNKPFMSIFOMTPOccMeanTxLink ___

)6*333(*8*100 6 The formula used for this counters is derived from SYSMTP3PERF group as follow:

( )

++= kbpsinBandwidthLinkXLNKPFMMSURMTPCTRXLNKPFMSIOOMTPCTRXLNKPFMSIFOMTPOccMeanRxLink ___

)6*333(*8*100


• 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:

,“\nAA aaa:##\nBB bbb:##\nCC ccc:##”, Where the entire field is a character string of variable length, containing in turn the following information:

• • \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 Field format for this group is different from all other groups.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (DDM Card) to which this record applies 4 OVRLDRJCTMOVCALL Number of Mobile Originated Calls rejected as a result of overload

controls being active. 5 OVRLDRJCTLUP Number of Location Updates rejected as a result of overload controls

being active. 6 OVRLDRJCTMOSMSCALL Number of Mobile Originated SMS transactions rejected as a result of

overload controls being active. 7 OVRLDRJCTMOCISSCALL Number of Mobile Originated CISS transactions rejected as a result of

overload controls being active. 8 RESERVED1 Reserved field 1 for future use 9 RESERVED2 Reserved field 2 for future use 10 RESERVED3 Reserved field 3 for future use 11 RESERVED4 Reserved field 4 for future use

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.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 DPC Destination Point Code. 5 IBCALLRJTATRLVL1 Number of Inbound ISUP calls rejected per DPC during Atrium®

System Overload level 1. 6 IBCALLRJTATRLVL2 Number of Inbound ISUP calls rejected per DPC during Atrium®

System Overload level 2. 7 IBCALLRJTATRLVL3 Number of Inbound ISUP calls rejected per DPC during Atrium®

System Overload level 3. 8 OBCALLRJTLCLLVL1 Number of Outbound ISUP calls rejected per DPC during local DPC

congestion level 17. 9 OBCALLRJTLCLLVL2 Number of Outbound ISUP calls rejected per DPC during local DPC

congestion level 2. 10 OBCALLRJTLCLLVL3 Number of Outbound ISUP calls rejected per DPC during local DPC

congestion level 3. 11 OBCALLRJTRMTLVL1 Number of Outbound ISUP calls rejected per DPC during Remote DPC

ACC congestion level 1. 12 OBCALLRJTRMTLVL2 Number of Outbound ISUP calls rejected per DPC during Remote DPC

ACC congestion level 2. 13 OBCALLRJTRMTLVL3 Number of Outbound ISUP calls rejected per DPC during Remote DPC

ACC congestion level 3. 14 OBCALLRJTUSRUNAVAIL Number of Outbound ISUP calls rejected per DPC during user part

unavailable condition. 15 OBMSGDRPLCLLVL1 Number of Outbound ISUP messages dropped per DPC due to local

DPC congestion level 1. 16 OBMSGDRPLCLLVL2 Number of Outbound ISUP messages dropped per DPC due to local

DPC congestion level 2. 17 OBMSGDRPLCLLVL3 Number of Outbound ISUP messages dropped per DPC due to local

DPC congestion level 3. 18 OBMSGDRPUSRUNAVAIL Number of Outbound ISUP messages dropped per DPC during user

part unavailable condition. 19 RESERVED1 Reserved field 1 for future use 20 RESERVED2 Reserved field 2 for future use 21 RESERVED3 Reserved field 3 for future use 22 RESERVED4 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

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


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.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 WMGNODENUM WMG Node (Media Gateway) to which this record applies 5 CALLATTMGCADD Number of MEGACO Add messages that were attempted. Pegged at

attempt to send "MEGACO_ADD" message to MGW 6 CALLSUCCMGCADD Number of MEGACO Add messages that were successful - number

of "MEGACO_ACK" (ADD) messages received from MGW 7 CALLATTMGCMODIFY Number of MEGACO Modify messages that were attempted. Pegged

at attempt to send "MEGACO_MODIFY" message to MGW 8 CALLSUCCMGCMODIFY Number of MEGACO Modify messages that were Successful -

number of "MEGACO_ACK" (MODIFY) messages received from MGW

9 CALLATTMGCMOVE Number of MEGACO Move messages that were attempted. Pegged at attempt to send "MEGACO_MOVE" message to MGW

10 CALLSUCCMGCMOVE Number of MEGACO Move messages that were successful - number of "MEGACO_ACK" (MOVE) messages received from MGW

11 CALLATTMGCSUBTRACT Number of MEGACO Subtract messages that were attempted. Pegged at attempt to send "MEGACO_SUBTRACT" message to MGW

12 CALLSUCCMGCSUBTRACT Number of MEGACO Subtract messaged that were successful - number of "MEGACO_ACK" (SUBTRACT) messages received from MGW

13 RESERVED1 Reserved field 1 for future use 14 RESERVED2 Reserved field 2 for future use 15 RESERVED3 Reserved field 3 for future use 16 RESERVED4 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.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 MSFNODEID WMG (media gateway) Node Number to which this record applies. 4 MSFSLOTID WMG card slot to which this record applies ( range 1 to 40) 5 MSFCPUID CPU (on the card) to which this record applies 6 MSFCPULOAD1SEC Mean occupancy (percentage) across last 1 second in the

performance interval 7 MSFCPULOAD5SEC Mean occupancy (percentage) across last 5 seconds in the



performance interval 10 MSFCPULOAD1MIN Mean occupancy (percentage) across last 1 minute in the

performance interval 11 MSFCPULOAD5MIN Mean occupancy (percentage) across last 5 minutes in the

performance interval 12 MSFCPULOAD15MIN Mean occupancy (percentage) across the entire 15-minute

performance interval. 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:


4.6 WSS Performance Information (WSSPERF) Performance Group Name: WSSPERF File Naming Convention: WSSPERF.YYMMDD-HHMM Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node to which this record applies 4 MAXWSSCPU Max CPU occupancy (percentage) 5 MEANWSSCPU Mean CPU occupancy 6 MEANWSSMEM Mean available memory 7 CARDTYPE Type of WSS card (CCM, DDM, SAM, SIM, IPM)8 8 CARDSTATUS Status of WSSNODENUM (i.e. ACTIVE or INACTIVE/STANDBY)9

WSSNODENUM is the key field, and identifies the WSS node (card) to which this record applies. Card type:

02 DDM card 04 CCM card 08 SAM card 16 SIM card 32 ERM card 64 IPM card

Card Status: 00 Loadshare 01 Active 02 Inactive/Standby

8 Added by PR 10889 9 Added by PR 10889


4.7 WSS Disk Performance Information (WSSDISKPERF) Performance Group Name: WSSDISKPERF File Naming Convention: WSSDISKPERF.YYMMDD-HHMM Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node to which this record applies 4 DISKOCCPARROOT Disk occupancy 5 DISKOCCPARAR Disk occupancy 6 DISKOCCPARSPACE Disk occupancy 7 CARDTYPE Card type of WSS node number to which the record apply10 8 CARDSTATUS Status of WSSNODENUM (i.e. ACTIVE or INACTIVE/STANDBY)11

WSSNODENUM is the key field, and identifies the WSS Node (card) to which this record applies. Card type:

02 DDM card 04 CCM card 08 SAM card 16 SIM card 32 ERM card 64 IPM card

Card Status: 00 Loadshare 01 Active 02 Inactive/Standby

10 Added by PR 10889 11 Added by PR 10889


5 SIGNALING PERFORMANCE DATA

5.1 MTP2 Link Information (SYSMTP2LINKPERF) Performance Group Name: SYSMTP2LINKPERF File Naming Convention: SYSMTP2LINKPERF.YYMMDD-HHMM.###

• ### 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

Number of records: Equals the number of CCS7 links provisioned on the system Position Field Name Description

1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 GATEWAYNO Gateway – Will always have a value of ‘1’ 4 LNKID CCS7 Link. 5 MTP2LNKPFMLINKINSVCTIME Time since the signaling link was last aligned (in seconds)12. 6 MTP2LNKPFMLINKFAILTOTAL Total number of signaling link failures due to all reasons. 7 MTP2LNKPFMLINKLCLBUSY Total time (during this collection period – in seconds) during

which the link remained locally congested. 8 MTP2LNKPFMLINKFAILABNFIBBSNR Number of signaling link failures due to abnormal

FIBR/BSNR (Forward Indicator Bit Received/Backward Sequence Number Received)

9 MTP2LNKPFMLINKFAILT7EXP Number of signaling link failures due to T7 Expiry13. 10 MTP2LNKPFMLINKFAILCONG Number of signaling link failures due to excessive

congestion. 11 MTP2LNKPFMLINKFAILSUERM Number of signaling link failures due to signal unit error rate. 12 MTP2LNKPFMALIGNFAIL Number of signaling link alignment/proving failures. 13 MTP2LNKPFMSUERRS Number of received Signaling Units (SU) in error. 14 MTP2LNKPFMNACKRX Number of Negative acknowledgements received. 15 MTP2LNKPFMMSUOCTETRETX Number of MSU (Message Signal Unit) octets retransmitted. 16 MTP2LNKPFMMSUTX Number of MSUs (Message Signal Units) transmitted. 17 MTP2LNKPFMMSURX Number of MSUs (Message Signal Units) 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. 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.

12 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


5.2 MTP3 Link Information (SYSMTP3LINKPERF) Performance Group Name: SYSMTP3LINKPERF File Naming Convention: SYSMTP3LINKPERF.YYMMDD-HHMM.###

• ### 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

Number of records: Equals the number of CCS7 links provisioned on the system Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (SIM Card) to which this record applies 4 GATEWAYNO Gateway – Will always have a value of ‘1’ 5 LNKID CCS7 Link. 6 MTP3LNKPFMCOOTX Number of changeover order messages transmitted 7 MTP3LNKPFMCOORX Number of changeover order messages received 8 MTP3LNKPFMCOATX Number of changeover acknowledgement messages transmitted. 9 MTP3LNKPFMCOARX Number of changeover acknowledgement messages received. 10 MTP3LNKPFMCBDTX Number of changeback declaration messages transmitted 11 MTP3LNKPFMCBDRX Number of changeback declaration messages received 12 MTP3LNKPFMCBATX Number of changeback acknowledgement transmitted. 13 MTP3LNKPFMCBARX Number of changeback acknowledgement messages received. 14 MTP3LNKPFMECOTX Number of emergency changeover order messages transmitted. 15 MTP3LNKPFMECORX Number of emergency changeover order messages received. 16 MTP3LNKPFMECATX Number of emergency changeover ACK transmitted. 17 MTP3LNKPFMECARX Number of emergency changeover ACK received. 18 MTP3LNKPFMLINTX Number of link inhibit messages transmitted. 19 MTP3LNKPFMLINRX Number of link inhibits messages received. 20 MTP3LNKPFMLUNTX Number of link uninhibit messages transmitted. 21 MTP3LNKPFMLUNRX Number of link uninhibit messages received. 22 MTP3LNKPFMLIATX Number of link inhibit acknowledgement messages transmitted. 23 MTP3LNKPFMLIARX Number of link inhibit acknowledgement messages received. 24 MTP3LNKPFMLUATX Number of link uninhibit acknowledgement messages transmitted. 25 MTP3LNKPFMLUARX Number of link uninhibit acknowledgement messages received. 26 MTP3LNKPFMLIDTX Number of link inhibit denied messages transmitted. 27 MTP3LNKPFMLIDRX Number of link inhibit denied messages received. 28 MTP3LNKPFMLFUTX Number of force link uninhibit messages transmitted. 29 MTP3LNKPFMLFURX Number of force link uninhibit messages received. 30 MTP3LNKPFMLLITX Number of local link inhibit test messages transmitted. 31 MTP3LNKPFMLLIRX Number of local link inhibit test messages received. 32 MTP3LNKPFMLRITX Number of remote link inhibit test messages transmitted. 33 MTP3LNKPFMLRIRX Number of remote link inhibit test messages received. 34 MTP3LNKPFMCONNORDTX Number of link connection order messages transmitted. 35 MTP3LNKPFMCONNORDRX Number of link connection order messages received. 36 MTP3LNKPFMCONNACKTX Number of link connection acknowledgement messages transmitted. 37 MTP3LNKPFMCONNACKRX Number of link connection acknowledgement messages received. 38 MTP3LNKPFMLNKTSTRX Number of link test messages received. 39 MTP3LNKPFMLNKTSTTX Number of link test messages transmitted.


Position Field Name Description 40 MTP3LNKPFMLNKTSTACKRX Number of link test acknowledgement messages received. 41 MTP3LNKPFMLNKTSTACKTX Number of link test acknowledgement messages transmitted. 42 MTP3LNKPFMTXDROP Number of transmitted messages dropped. 43 MTP3LNKPFMTXCONGDROP Number of MSUs (Message Signal Units) dropped due to link

congestion. 44 MTP3LNKPFMSIFOCTTX Number of SIF octet transmitted. 45 MTP3LNKPFMSIFOCTRX Number of SIF octet received. 46 MTP3LNKPFMSIOOCTTX Number of SIO octet transmitted. 47 MTP3LNKPFMSIOOCTRX Number of SIO octet received. 48 MTP3LNKPFMMSUTX Number of MSU transmitted. 49 MTP3LNKPFMMSURX Number of MSU received. 50 MTP3LNKPFMUNAVDUR The duration of any current link unavailability during this collection

period14. (100 millisecond units) 51 MTP3LNKPFMDURLNKCONG The duration of any current link congestion during this collection

period15. (100 millisecond units) 52 MTP3LNKPFMERRPDURX 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.

14 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).


5.3 MTP3 Linkset Information (SYSMTP3LINKSETPERF) Performance Group Name: SYSMTP3LINKSETPERF File Naming Convention: SYSMTP3LINKSETPERF.YYMMDD-HHMM.###

• ### 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

Number of records: Equals the number of CCS7 linksets provisioned on the system. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (DDM Card) to which this record applies 4 GATEWAYNO Gateway – Will always have a value of ‘1’ 5 LNKSETID CCS7 Link Set 6 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).

16 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).


5.4 MTP3 Route Information (SYSMTP3ROUTEPERF) Performance Group Name: SYSMTP3ROUTEPERF File Naming Convention: SYSMTP3ROUTEPERF.YYMMDD-HHMM.###

• ### 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

Number of records: Equals the number of Destination Point Codes provisioned Position Field Name Description

1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (DDM Card) to which this record applies 4 GATEWAYNO Gateway – Will always have a value of ‘1’ 5 DPC Destination Point Code. 6 MTP3ROUTEPFMRSMTX Number of route set test messages transmitted. 7 MTP3ROUTEPFMRSMRX Number of route set test messages received. 8 MTP3ROUTEPFMRCTTX Number of route set congestion test messages transmitted. 9 MTP3ROUTEPFMRCTRX Number of route set congestion test messages received. 10 MTP3ROUTEPFMTFPTX Number of transfer prohibited messages transmitted. 11 MTP3ROUTEPFMTFPRX Number of transfer prohibited messages received. 12 MTP3ROUTEPFMTFRTX Number of transfer restrict messages transmitted. 13 MTP3ROUTEPFMTFRRX Number of transfer restricted messages received. 14 MTP3ROUTEPFMTFATX Number of transfer allowed messages transmitted. 15 MTP3ROUTEPFMTFARX Number of transfer allowed messages received. 16 MTP3ROUTEPFMTFCTX Number of transfer controlled messages transmitted. 17 MTP3ROUTEPFMTFCRX Number of transfer controlled messages received. 18 MTP3ROUTEPFMRTEUNAV Number of times route was unavailable. 19 MTP3ROUTEPFMSIFTX Number of SIF octet messages transmitted. 20 MTP3ROUTEPFMSIOTX Number of SIO octet messages transmitted. 21 MTP3ROUTEPFMUNAVDUR 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 17 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).


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).


5.5 ISUP DPC Information (SYSISUPDPCPERF) Performance Group Name: SYSISUPDPCPERF File Naming Convention: SYSISUPDPCPERF.YYMMDD-HHMM.###

• ### 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

Number of records: Equals the number of destination point codes (to which ISUP trunks have been assigned) provisioned in the system. Position Field Name Description

1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 DPC Destination Point Code. 5 GATEWAYNO Gateway Number – will always have a value of ‘1’. 6 ISUPPFMACMTX Number of address complete messages transmitted. 7 ISUPPFMANMTX Number of answer messages transmitted. 8 ISUPPFMBLATX Number of blocking acknowledgement messages transmitted. 9 ISUPPFMBLOTX Number of blocking messages transmitted. 10 ISUPPFMCCRTX Number of continuity check request messages transmitted. 11 ISUPPFMCFNTX Number of confusion messages transmitted. 12 ISUPPFMCGBTX Number of circuit group blocking messages transmitted. 13 ISUPPFMCGBATX Number of circuit group blocking acknowledgement messages transmitted. 14 ISUPPFMCGUTX Number of circuit group unblocking messages transmitted. 15 ISUPPFMCGUATX Number of circuit group unblocking acknowledgement messages

transmitted. 16 ISUPPFMCONTX Number of connect messages transmitted. 17 ISUPPFMCOTTX Number of continuity messages transmitted. 18 ISUPPFMCPGTX Number of call progress messages transmitted. 19 ISUPPFMCQMTX Number of circuit query messages transmitted. 20 ISUPPFMCQRTX Number of circuit query acknowledgement messages transmitted. 21 ISUPPFMCRGTX Number of charging messages transmitted. 22 ISUPPFMFAATX Number of facility accepted messages transmitted. 23 ISUPPFMFACTX Number of facility messages transmitted. 24 ISUPPFMFARTX Number of facility request messages transmitted. 25 ISUPPFMFOTTX Number of forward transfer messages transmitted. 26 ISUPPFMFRJTX Number of facility rejected messages transmitted. 27 ISUPPFMGRATX Number of circuit group reset acknowledgement messages transmitted. 28 ISUPPFMGRSTX Number of circuit group reset messages transmitted. 29 ISUPPFMIAMTX Number of initial address messages transmitted. 30 ISUPPFMIDRTX Number of identification request messages transmitted. 31 ISUPPFMINFTX Number of information messages transmitted. 32 ISUPPFMINRTX Number of information request messages transmitted. 33 ISUPPFMIRSTX Number of identification response messages transmitted. 34 ISUPPFMLOPTX Number of loop prevention messages transmitted. 35 ISUPPFMLPATX Number of loopback acknowledgement messages transmitted. 36 ISUPPFMNRMTX Number of network resource management messages transmitted. 37 ISUPPFMOLMTX Number of overload messages transmitted. 38 ISUPPFMPAMTX Number of pass-along messages transmitted. 39 ISUPPFMRELTX Number of release messages transmitted.


Position Field Name Description 40 ISUPPFMRESTX Number of resume messages transmitted. 41 ISUPPFMRLCTX Number of release complete messages transmitted. 42 ISUPPFMRSCTX Number of reset messages transmitted. 43 ISUPPFMSAMTX Number of subsequent address messages transmitted. 44 ISUPPFMSGMTX Number of segmentation messages transmitted. 45 ISUPPFMSUSTX Number of suspend messages transmitted. 46 ISUPPFMUBATX Number of unblocking acknowledgement messages transmitted. 47 ISUPPFMUBLTX Number of unblocking messages transmitted. 48 ISUPPFMUCICTX Number of unequipped CIC messages transmitted. 49 ISUPPFMUPATX Number of user part available messages transmitted. 50 ISUPPFMUPTTX Number of user part test messages transmitted. 51 ISUPPFMUSRTX Number of user to user messages transmitted. 52 ISUPPFMCRATX Number of circuit reservation acknowledgement messages transmitted. 53 ISUPPFMCRMTX Number of circuit reservation messages transmitted. 54 ISUPPFMCVRTX Number of circuit validation response messages transmitted. 55 ISUPPFMCVTTX Number of circuit validation messages transmitted. 56 ISUPPFMEXMTX Number of exit messages transmitted. 57 ISUPPFMACMRX Number of address complete messages received. 58 ISUPPFMANMRX Number of answer messages received. 59 ISUPPFMBLARX Number of blocking acknowledgement messages received. 60 ISUPPFMBLORX Number of blocking messages received. 61 ISUPPFMCCRRX Number of continuity check request messages received. 62 ISUPPFMCFNRX Number of confusion messages received. 63 ISUPPFMCGBRX Number of circuit group blocking messages received. 64 ISUPPFMCGBARX Number of circuit group blocking acknowledgement messages received. 65 ISUPPFMCGURX Number of circuit group unblocking messages received. 66 ISUPPFMCGUARX Number of circuit group unblocking acknowledgement messages received. 67 ISUPPFMCONRX Number of connect messages received. 68 ISUPPFMCOTRX Number of continuity messages received. 69 ISUPPFMCPGRX Number of call progress messages received. 70 ISUPPFMCQMRX Number of circuit query messages received. 71 ISUPPFMCQRRX Number of circuit query acknowledgement messages received. 72 ISUPPFMCRGRX Number of charging messages received. 73 ISUPPFMFAARX Number of facility accepted messages received. 74 ISUPPFMFACRX Number of facility messages received. 75 ISUPPFMFARRX Number of facility request messages received. 76 ISUPPFMFOTRX Number of forward transfer messages received. 77 ISUPPFMFRJRX Number of facility rejected messages received. 78 ISUPPFMGRARX Number of circuit group reset acknowledgement messages received. 79 ISUPPFMGRSRX Number of circuit group reset messages received. 80 ISUPPFMIAMRX Number of initial address messages received. 81 ISUPPFMIDRRX Number of identification request messages received. 82 ISUPPFMINFRX Number of information messages received. 83 ISUPPFMINRRX Number of information request messages received. 84 ISUPPFMIRSRX Number of identification response messages received. 85 ISUPPFMLOPRX Number of loop prevention messages received. 86 ISUPPFMLPARX Number of loopback acknowledgement messages received.


Position Field Name Description 87 ISUPPFMNRMRX Number of network resource management messages received. 88 ISUPPFMOLMRX Number of overload messages received. 89 ISUPPFMPAMRX Number of pass-along messages received. 90 ISUPPFMRELRX Number of release messages received. 91 ISUPPFMRESRX Number of resume messages received. 92 ISUPPFMRLCRX Number of release complete messages received. 93 ISUPPFMRSCRX Number of reset messages received. 94 ISUPPFMSAMRX Number of subsequent address messages received. 95 ISUPPFMSGMRX Number of segmentation messages received. 96 ISUPPFMSUSRX Number of suspend messages received. 97 ISUPPFMUBARX Number of unblocking acknowledgement messages received. 98 ISUPPFMUBLRX Number of unblocking messages received. 99 ISUPPFMUCICRX Number of unequipped CIC messages received. 100 ISUPPFMUPARX Number of user part available messages received. 101 ISUPPFMUPTRX Number of user part test messages received. 102 ISUPPFMUSRRX Number of user-to-user messages received. 103 ISUPPFMCRARX Number of circuit reservation acknowledgement messages received. 104 ISUPPFMCRMRX Number of circuit reservation messages received. 105 ISUPPFMCVRRX Number of circuit validation response messages received. 106 ISUPPFMCVTRX Number of circuit validation messages received. 107 ISUPPFMEXMRX Number of exit messages received.


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 aggregated across the files in order to formulate a system wide view.


5.6 BICC DPC Information (SYSBICCDPCPERF) Performance Group Name: SYSBICCDPCPERF File Naming Convention: SYSBICCDPCPERF.YYMMDD-HHMM.###


Number of records: Equals the number of destination point codes provisioned in the system. Position Field Name Description

1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. Will

always equal node number in the file name. 4 DPC Destination Point Code. 5 GATEWAYNO Gateway Number – will always have a value of ‘1’. 6 BICCPFMACMTX Number of Address Complete messages transmitted. 7 BICCPFMANMTX Number of Answer messages transmitted. 8 BICCPFMBLATX Number of Blocking Acknowledgement messages transmitted. 9 BICCPFMBLOTX Number of Blocking messages transmitted. 10 BICCPFMCCRTX Number of Continuity Check Request messages transmitted. 11 BICCPFMCFNTX Number of Confusion messages transmitted. 12 BICCPFMCGBTX Number of Circuit Group Blocking messages transmitted. 13 BICCPFMCGBATX Number of Circuit Group Blocking Acknowledgement messages

transmitted. 14 BICCPFMCGUTX Number of Circuit Group Unblocking messages transmitted. 15 BICCPFMCGUATX Number of Circuit Group Unblocking Acknowledgement

messages transmitted. 16 BICCPFMCONTX Number of Connect messages transmitted. 17 BICCPFMCOTTX Number of Continuity messages transmitted. 18 BICCPFMCPGTX Number of Call Progress messages transmitted. 19 BICCPFMCQMTX Number of Circuit Query messages transmitted. 20 BICCPFMCQRTX Number of Circuit Query Acknowledgement messages

transmitted. 21 BICCPFMCRGTX Number of Charging messages transmitted. 22 BICCPFMFAATX Number of Facility Accepted messages transmitted. 23 BICCPFMFACTX Number of Facility messages transmitted. 24 BICCPFMFARTX Number of Facility request messages transmitted. 25 BICCPFMFOTTX Number of Forward Transfer messages transmitted. 26 BICCPFMFRJTX Number of Facility Rejected messages transmitted. 27 BICCPFMGRATX Number of Circuit Group Reset Acknowledgement messages

transmitted. 28 BICCPFMGRSTX Number of Circuit Group Reset messages transmitted. 29 BICCPFMIAMTX Number of Initial Address messages transmitted. 30 BICCPFMIDRTX Number of Identification Request messages transmitted. 31 BICCPFMINFTX Number of Information messages transmitted. 32 BICCPFMINRTX Number of Information request messages transmitted. 33 BICCPFMIRSTX Number of Identification Response messages transmitted. 34 BICCPFMLOPTX Number of Loop Prevention messages transmitted. 35 BICCPFMLPATX Number of Loopback Acknowledgement messages transmitted. 36 BICCPFMNRMTX Number of network Resource Management messages

transmitted. 37 BICCPFMOLMTX Number of Overload messages transmitted.


Position Field Name Description 38 BICCPFMPAMTX Number of Pass-Along messages transmitted. 39 BICCPFMRELTX Number of Release messages transmitted. 40 BICCPFMRESTX Number of Resume messages transmitted. 41 BICCPFMRLCTX Number of Release Complete messages transmitted. 42 BICCPFMRSCTX Number of Reset messages transmitted. 43 BICCPFMSAMTX Number of Subsequent Address messages transmitted. 44 BICCPFMSGMTX Number of Segmentation messages transmitted. 45 BICCPFMSUSTX Number of Suspend messages transmitted. 46 BICCPFMUBATX Number of Unblocking Acknowledgement messages

transmitted. 47 BICCPFMUBLTX Number of Unblocking messages transmitted. 48 BICCPFMUCICTX Number of Unequipped CIC messages transmitted. 49 BICCPFMUPATX Number of User Parts Available messages transmitted. 50 BICCPFMUPTTX Number of User Part Test messages transmitted. 51 BICCPFMUSRTX Number of User-To-User messages transmitted. 52 BICCPFMCRATX Number of Circuit Reservation Acknowledgement messages

transmitted. 53 BICCPFMCRMTX Number of Circuit Reservation messages transmitted. 54 BICCPFMCVRTX Number of Circuit Validation Response messages transmitted. 55 BICCPFMCVTTX Number of Circuit Validation messages transmitted. 56 BICCPFMEXMTX Number of Exit messages transmitted. 57 BICCPFMAPMTX Number of Application Transport Mechanism (APM) messages

transmitted. 58 BICCPFMACMRX Number of Address Complete messages received. 59 BICCPFMANMRX Number of Answer messages received. 60 BICCPFMBLARX Number of Blocking Acknowledgement messages received. 61 BICCPFMBLORX Number of Blocking messages received. 62 BICCPFMCCRRX Number of Continuity Check Request messages received. 63 BICCPFMCFNRX Number of Confusion messages received. 64 BICCPFMCGBRX Number of Circuit Group Blocking messages received. 65 BICCPFMCGBARX Number of Circuit Group Blocking Acknowledgement messages

received. 66 BICCPFMCGURX Number of Circuit Group Unblocking messages received. 67 BICCPFMCGUARX Number of Circuit Group Unblocking Acknowledgement

messages received. 68 BICCPFMCONRX Number of Connect messages received. 69 BICCPFMCOTRX Number of Continuity messages received. 70 BICCPFMCPGRX Number of Call Progress messages received. 71 BICCPFMCQMRX Number of Circuit Query messages received. 72 BICCPFMCQRRX Number of Circuit Query Acknowledgement messages

received. 73 BICCPFMCRGRX Number of Charging messages received. 74 BICCPFMFAARX Number of Facility Accepted messages received. 75 BICCPFMFACRX Number of Facility messages received. 76 BICCPFMFARRX Number of Facility Request messages received. 77 BICCPFMFOTRX Number of Forward Transfer messages received. 78 BICCPFMFRJRX Number of Facility Rejected messages received. 79 BICCPFMGRARX Number of Circuit Group Reset Acknowledgement messages

received. 80 BICCPFMGRSRX Number of Circuit Group Reset messages received.


Position Field Name Description 81 BICCPFMIAMRX Number of Initial Address messages received. 82 BICCPFMIDRRX Number of Identification Request messages received. 83 BICCPFMINFRX Number of Information messages received. 84 BICCPFMINRRX Number of Information Request messages received. 85 BICCPFMIRSRX Number of Identification Response messages received. 86 BICCPFMLOPRX Number of Loop Prevention messages received. 87 BICCPFMLPARX Number of Loopback Acknowledgement messages received. 88 BICCPFMNRMRX Number of network Resource Management messages received. 89 BICCPFMOLMRX Number of Overload messages received. 90 BICCPFMPAMRX Number of Pass-Along messages received. 91 BICCPFMRELRX Number of Release messages received. 92 BICCPFMRESRX Number of Resume messages received. 93 BICCPFMRLCRX Number of Release Complete messages received. 94 BICCPFMRSCRX Number of Reset messages received. 95 BICCPFMSAMRX Number of Subsequent address messages received. 96 BICCPFMSGMRX Number of Segmentation messages received. 97 BICCPFMSUSRX Number of Suspend messages received. 98 BICCPFMUBARX Number of Unblocking Acknowledgement messages received. 99 BICCPFMUBLRX Number of Unblocking messages received. 100 BICCPFMUCICRX Number of Unequipped CIC received. 101 BICCPFMUPARX Number of User Parts Available messages received. 102 BICCPFMUPTRX Number of User Part Test messages received. 103 BICCPFMUSRRX Number of User-To-User messages received. 104 BICCPFMCRARX Number of Circuit Reservation Acknowledgement messages

received. 105 BICCPFMCRMRX Number of Circuit Reservation messages received. 106 BICCPFMCVRRX Number of Circuit Validation Response messages received. 107 BICCPFMCVTRX Number of Circuit Validation messages received. 108 BICCPFMEXMRX Number of Exit messages received. 109 BICCPFMAPMRX Number of Application Transport Mechanism (APM) 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 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.

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) Performance Group Name: SYSSCCPPERF File Naming Convention: SYSSCCPPERF.YYMMDD-HHMM.###

• ### 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

Number of records: One per file. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (SIM Card) to which this record applies. Will

always equal node number in the file name 4 GATEWAYNO Gateway Number – will always have a value of ‘1’. 5 SCCPGENPFMRFNTASN Number of routing failures due to no translation for address of

such nature. 6 SCCPGENPFMRFNTSA Number of routing failures due to no translation for this

specific address. 7 SCCPGENPFMRFNETFAIL Number of routing failure due to network failure (point code

unavailable). 8 SCCPGENPFMRFNETCONG Number of routing failures due to network congestion. 9 SCCPGENPFMRFSSNFAIL Number of routing failures due to sub-system failure. 10 SCCPGENPFMRFSSNCONG Number of routing failures due to sub-system congestion. 11 SCCPGENPFMRFUNEQUIP Number of routing failures due to unequipped user. 12 SCCPGENPFMRFHOPVIOLATE Number of routing failures due to hop counter violation. 13 SCCPGENPFMSYNERROR Number of routing failures due to syntax error. 14 SCCPGENPFMRFUNKNOWN Number of routing failures due to unknown reason. 15 SCCPGENPFMUDTTX Number of unit data message transmitted. 16 SCCPGENPFMUDTSTX Number of unit data service messages transmitted. 17 SCCPGENPFMUDTRX Number of unit data messages received. 18 SCCPGENPFMUDTSRX Number of unit data service messages received. 19 SCCPGENPFMXUDTTX Number of extended unit data messages transmitted. 20 SCCPGENPFMXUDTSTX Number of extended unit data service messages transmitted. 21 SCCPGENPFMXUDTRX Number of extended unit data messages received. 22 SCCPGENPFMXUDTSRX Number of extended unit data service messages received. 23 SCCPGENPFMTOTALMSG Number of messages handled (total inbound). 24 SCCPGENPFMMSGLOC Number of inbound messages intended for local sub-system. 25 SCCPGENPFMGTTRANREQ Number of messages requiring Global Title Translation

(GTT). 26 SCCPGENPFMMSGTXC0 Number of class 0 messages transmitted. 27 SCCPGENPFMMSGTXC1 Number of class 1 messages transmitted. 28 SCCPGENPFMMSGRXC0 Number of class 0 messages received. 29 SCCPGENPFMMSGRXC1 Number of class 1 messages received. 30 SCCPGENPFMIUDTTX Number of ITU96 unit data messages transmitted. 31 SCCPGENPFMIUDTSTX Number of ITU96 unit data service messages transmitted. 32 SCCPGENPFMIUDTRX Number of ITU96 unit data messages received. 33 SCCPGENPFMIUDTSRX Number of ITU96 unit data messages service received. 34 SCCPGENPFMTIMEREXP Number of times the SCCP connection inactivity timer

expired. 35 SCCPGENPFMPRVINITRESET Number of times the SCCP layer initiated resets. 36 SCCPGENPFMPRVINITREL Number of times the SCCP layer initiated releases. 37 SCCPGENPFMSSCONGRX Number of times the SS Congest messages received


Position Field Name Description 38 SCCPGENPFMSSPROHRX Number of times the SS Prohibit messages received 39 SCCPGENPFMSEGERR Number of times the Segment message too large 40 SCCPGENPFMSEGERRFAIL Number of times the Segment message fail 41 SCCPGENPFMREASSEMERR Number of times the Reassembly out of sequence error 42 SCCPGENPFMERRTIMEXP Number of times the Reassembly time expired error 43 SCCPGENPFMERRNOSPC Number of times the Reassembly no space error 44 SCCPGENPFMCRTX Number of times the CR messages sent 45 SCCPGENPFMCRRX Number of times the CR messages received 46 SCCPGENPFMCREFTX Number of times the CREF messages sent 47 SCCPGENPFMCREFRX Number of times the CREF messages received 48 SCCPGENPFMRSRTX Number of times the RSR messages sent 49 SCCPGENPFMRSRRX Number of times the RSR messages received 50 SCCPGENPFMERRTX Number of times the ERR messages sent 51 SCCPGENPFMERRRX Number of times the ERR messages received 52 SCCPGENPFMRLSCMPFAIL Number of times the Release Complete fail

To provide a system-wide view of the information in this performance group, the values must be accumulated across all SIM cards.


5.8 CAP (CAMEL Application Part) Information (CAPMSGPERF) Performance Group Name: CAPMSGPERF File Naming Convention: CAPMSGPERF.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 Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. Will always

equal node number in the file name 4 INITDPINVTX Number of Initial Detection Point (IDP): Invoke messages

transmitted. 5 ESTTMPCONRETX Number of Establish Temporary Connection (ETC): Return Error

messages transmitted. 6 DISCFWDCONRETX Number of Disconnect Forward Connection: Return Error

messages transmitted. 7 CONTORESRETX Number of Connect to Resource: Return Error messages

transmitted. 8 CONRETX Number of Connect: Return Error messages transmitted. 9 REQRPTBCSMRETX Number of Request Report BCSM Event: Return Error

messages transmitted. 10 EVTRPTBCSMINVTX Number of Event Report BCSM: Invoke messages transmitted. 11 RSTTMRRETX Number of Reset Timer: Return Error messages transmitted. 12 APPCHRGRETX Number of Apply Charging: Return Error messages transmitted. 13 APPCHRGRPTINVTX Number of Apply Charging Report: Invoke messages

transmitted. 14 CALLINFORPTINVTX Number of Call Information Report: Invoke messages

transmitted. 15 CALLINFOREQRETX Number of Call Information Request: Return Error messages

transmitted. 16 SNDCHRGINFORETX Number of Send Charging Info: Return Error messages

transmitted. 17 CNCLRETX Number of Cancel: Return Error messages transmitted. 18 ACTVTSTRRTX Number of Activity Test: Return Result messages transmitted. 19 CONTWITHARGRETX Number of Continue with Argument: Return Error messages

transmitted. 20 INITDPSMSINVTX Number of Initial Detection Point (DP) SMS: Invoke messages

transmitted. 21 FURCHRGINFOSMSRETX Number of Furnish Charging Information SMS: Return Error

messages transmitted. 22 CONSMSRETX Number of Connect SMS: Return Error messages transmitted. 23 REQRPTSMSRETX Number of Request Report SMS Event: Return Error messages

transmitted. 24 EVTRPTSMSINVTX Number of Event Report SMS: Invoke messages transmitted. 25 RSTTMRSMSRETX Number of Reset Timer SMS: Return Error messages

transmitted. 26 INITDPPH2INVTX Number of Initial Detection Point (IDP) Phase-2: Invoke

messages transmitted. 27 ESTTMPCONPH2RETX Number of Establish Temporary Connection Ph2: Return Error

messages transmitted. 28 DISCFWDCONPH2RETX Number of Disconnect Forward Connection Ph2: Return Error

messages transmitted. 29 CONTORESPH2RETX Number of Connect to Resource Ph2: Return Error messages

transmitted.


Position Field Name Description 30 CONPH2RETX Number of Connect Ph2: Return Error messages transmitted. 31 REQRPTBCSMPH2RETX Number of Request Report BCSM Event Ph2: Return Error

messages transmitted. 32 EVTRPTBCSMPH2INVTX Number of Event Report BCSM Ph2: Invoke messages

transmitted. 33 RSTTMRPH2RETX Number of Reset timer Ph2: Return Error messages transmitted. 34 FURCHRGINFOPH2RETX Number of Furnish Charging Information Ph2: Return Error

messages transmitted. 35 APPCHRGPH2RETX Number of Apply Charging Ph2: Return Error messages

transmitted. 36 APPCHRGRPTPH2INVTX Number of Apply Charging report Ph2: Invoke messages

transmitted. 37 CALLGAPPH2INVTX Number of Call Gap Ph2: Invoke messages transmitted. 38 CALLINFORPTPH2INVTX Number of Call Information Report Ph2: Invoke messages

transmitted. 39 SNDCHRGINFOPH2RETX Number of Send Charging Info Ph2: Return Error messages

transmitted. 40 CNCLPH2RETX Number of Cancel Ph2: Return Error messages transmitted. 41 ACTVTSTPH2RRTX Number of Activity Test Ph2: Return Result messages

transmitted. 42 INITDPRERX Number of Initial DP (IDP): Return Error messages received. 43 ESTTMPCONINVRX Number of Establish Temporary Connection (ETC): Invoke

messages received. 44 DISCFWDCONINVRX Number of Disconnect Forward Connection: Invoke messages

received. 45 CONTORESINVRX Number of Connect To Resource: Invoke messages received. 46 CONINVRX Number of Connect: Invoke messages received. 47 RELCALLINVRX Number of Release Call: Invoke messages received. 48 REQRPTBCSMINVRX Number of Request Report BCSM Event: Invoke messages

received. 49 CONTINVRX Number of Continue: Invoke messages received. 50 FURCHRGINFOINVRX Number of Furnish Charging Information: Invoke messages

received. 51 APPCHRGINVRX Number of Apply Charging: Invoke messages received. 52 APPCHRGRPTRERX Number of Apply Charging Report: Return Error messages

received. 53 CALLGAPINVRX Number of Call Gap: Invoke messages received. 54 CALLINFOREQINVRX Number of Call Information Request: Invoke messages received. 55 SNDCHRGINFOINVRX Number of Send Charging Info: Invoke messages received. 56 CNCLINVRX Number of Cancel: Invoke messages received. 57 ACTVTSTINVRX Number of Activity Test: Invoke messages received. 58 CONTWITHARGINVRX Number of Continue with Argument: Invoke messages received. 59 INITDPSMSRERX Number of Initial DP SMS: Return Error messages received. 60 FURCHRGINFOSMSINVRX Number of Furnish Charging Information SMS: Invoke messages

received. 61 CONSMSINVRX Number of Connect SMS: Invoke messages received. 62 REQRPTSMSINVRX Number of Request Report SMS Event: Invoke messages

received. 63 CONTSMSINVRX Number of Continue SMS: Invoke messages received. 64 RELSMSINVRX Number of Release SMS: Invoke messages received. 65 RSTTMRSMSINVRX Number of Reset Timer SMS: Invoke messages received. 66 INITDPPH2RERX Number of Initial DP Ph2: Return Error messages received. 67 ESTTMPCONPH2INVRX Number of Establish Temporary Connection Ph2: Invoke

messages received. 68 DISCFWDCONPH2INVRX Number of Disconnect Forward Connection Ph2: Invoke

messages received.


Position Field Name Description 69 CONTORESPH2INVRX Number of Connect to Resource Ph2: Invoke messages

received. 70 CONPH2INVRX Number of Connect Ph2: Invoke messages received. 71 RELCALLPH2INVRX Number of Release Call Ph2: Invoke messages received. 72 REQRPTBCSMPH2INVRX Number of Request Report BCSM Event Ph2: Invoke messages

received. 73 CONTPH2INVRX Number of Continue Ph2: Invoke messages received. 74 RSTTMRPH2INVRX Number of Reset Timer Ph2: Invoke messages received. 75 FURCHRGINFOPH2INVRX Number of Furnish Charging Information Ph2: Invoke messages

received. 76 APPCHRGPH2INVRX Number of Apply Charging Ph2: Invoke messages received. 77 APPCHRGRPTPH2RERX Number of Apply Charging Report Ph2: Return Error messages

received. 78 CALLINFOREQPH2INVRX Number of Call Information Request Ph2: Invoke messages

received. 79 CALLINFOREQPH2RERX Number of Call Information Request Ph2: Return Error

messages received. 80 SNDCHRGINFOPH2INVRX Number of Send Charging Info Ph2: Invoke messages received. 81 CNCLPH2INVRX Number of Cancel Ph2: Invoke messages received. 82 ACTVTSTPH2INVRX Number of Activity Test Ph2: Invoke 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 an Establish Temporary Connection: Invoke).


5.9 INAP Information (INAPMSGPERF) Performance Group Name: INAPMSGPERF File Naming Convention: INAPMSGPERF.YYMMDD-HHMM


Number of records: One per file. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. Will

always equal node number in the file name 4 INITDPRETX Number of Initial DP: Return Error messages transmitted. 5 OATTAUTHINVTX Number of Origination Attempt Authorized: Invoke messages

transmitted. 6 CTEDINFOINVTX Number of Collected Information: Invoke messages transmitted. 7 ASEDINFOINVTX Number of Analyzed Information: Invoke messages transmitted. 8 ROUTSELFAILINVTX Number of Route Select Failure: Invoke messages transmitted. 9 OCDPTYBUSYINVTX Number of Origination Called Party Busy: Invoke messages

transmitted. 10 ONOANSWERINVTX Number of Origination No Answer: Invoke messages

transmitted. 11 OANSWERINVTX Number of Origination Answer: Invoke messages transmitted. 12 ODISCINVTX Number of Origination Disconnect: Invoke messages

transmitted. 13 TATTAUTHINVTX Number of Termination Attempt Authorized: Invoke messages

transmitted. 14 TCDPTYBUSYINVTX Number of Termination Called Party Busy: Invoke messages

transmitted. 15 TNOANSWERINVTX Number of Termination No Answer: Invoke messages

transmitted. 16 TANSWERINVTX Number of Termination Answer: Invoke messages transmitted. 17 TDISCINVTX Number of Termination Disconnect: Invoke messages

transmitted. 18 OMIDCALLINVTX Number of Origination Mid Call: Invoke messages transmitted. 19 TMIDCALLINVTX Number of Termination Mid Call: Invoke messages transmitted. 20 ASTREQINSTRINVTX Number of Assist Request Instructions: Invoke messages

transmitted. 21 ESTTMPCONRETX Number of Establish Temporary Connection: Return Error

messages transmitted. 22 DISCFWDCONRETX Number of Disconnect Forward Connection: Return Error

messages transmitted. 23 CONTORESRETX Number of Connect To Resource: Return Error messages

transmitted. 24 CONRETX Number of Connect: Return Error messages transmitted. 25 HOLDCALLNETRETX Number of Hold Call In Network: Return Error messages

transmitted. 26 REQRPTBCSMRETX Number of Request Report BCSM Event Return Error

messages transmitted. 27 EVTRPTBCSMINVTX Number of Event Report BCSM: Invoke messages transmitted. 28 REQNOTCHGRETX Number of Request Notification Charging Event: Return Error

messages transmitted. 29 EVTNOTCHGINVTX Number of Event Notification Charging: Invoke messages

transmitted. 30 CLCTINFORETX Number of Collect Information: Return Error messages

transmitted.


Position Field Name Description 31 ASEINFORETX Number of Analyze Information: Return Error messages

transmitted. 32 SELROUTRETX Number of Select Route: Return Error messages transmitted. 33 SELFACRETX Number of Select Facility: Return Error messages transmitted. 34 INITCALLATTRETX Number of Initiate Call Attempt: Return Error messages

transmitted. 35 RSTTMRRETX Number of Reset Timer: Return Error messages transmitted. 36 FURCHGINFORETX Number of Furnish Charging Information: Return Error

messages transmitted. 37 APPCHGRETX Number of Apply Charging: Return Error messages transmitted. 38 APPCHGRPTINVTX Number of Apply Charging Report: Invoke messages

transmitted. 39 REQCRNTSTATRRTX Number of Request Current Status Report: Return Result

messages transmitted. 40 REQCRNTSTATRETX Number of Request Current Status Report: Return Error

messages transmitted. 41 REQEVERYSTATRETX Number of Request Every Status Report: Return Error

messages transmitted. 42 REQFIRSTSTATRETX Number of Request First Status Match Report: Return Error

messages transmitted. 43 ACTVSVCFTDRETX Number of Activate Service Filtering: Return Error messages

transmitted. 44 SVCFTDRSPINVTX Number of Service Filtering Response: Invoke messages

transmitted. 45 CALLINFORPTINVTX Number of Call Information Report: Invoke messages

transmitted. 46 CALLINFOREQRETX Number of Call Information Request: Return Error messages

transmitted. 47 SNDCHGINFORETX Number of Send Charging Info: Return Error messages

transmitted. 48 CNCLRETX Number of Cancel: Return Error messages transmitted. 49 CNCLSTATREQRETX Number of Cancel Status Report: Request Return Error

messages transmitted. 50 INITDPINVRX Number of Initial DP: Invoke messages received. 51 OATTAUTHRERX Number of Origination Attempt Authorized: Return Error

messages received. 52 CTEDINFORERX Number of Collected Information: Return Error messages

received. 53 ASEDINFORERX Number of Analyzed Information; Return Error messages

received. 54 ROUTSELFAILRERX Number of Route Select Failure: Return Error messages

received. 55 OCDPTYBUSYRERX Number of Origination Called Party Busy: Return Error

messages received. 56 ONOANSWERRERX Number of Origination No Answer: Return Error messages

received. 57 OANSWERRERX Number of Origination Answer: Return Error messages

received. 58 ODISCRERX Number of Origination Disconnect: Return Error messages

received. 59 TATTAUTHRERX Number of Termination Attempt Authorized: Return Error

messages received. 60 TCDPTYBUSYRERX Number of Termination Called Party Busy: Return Error

messages received. 61 TNOANSWERRERX Number of Termination No Answer: Return Error messages

received. 62 TANSWERRERX Number of Termination Answer: Return Error messages

received.


Position Field Name Description 63 TDISCRERX Number of Termination Disconnect; Return Error messages

received. 64 OMIDCALLRERX Number of Origination Mid Call: Return Error messages

received. 65 TMIDCALLRERX Number of Termination Mid Call: Return Error messages

received. 66 ASTREQINSTRRERX Number of Assist Request Instructions: Return Error messages

received. 67 ESTTMPCONINVRX Number of Establish Temporary Connection: Invoke messages

received. 68 DISCFWDCONINVRX Number of Disconnect Forward Connection: Invoke messages

received. 69 CONTORESINVRX Number of Connect To Resource: Invoke messages received. 70 CONINVRX Number of Connect: Invoke messages received. 71 HOLDCALLNETINVRX Number of Hold Call In Network: Invoke messages received. 72 RELCALLINVRX Number of Release Call: Invoke messages received. 73 REQRPTBCSMINVRX Number of Request Report BCSM Event: Invoke messages

received. 74 REQNOTCHGINVRX Number of Request Notification Charging Event: Invoke

messages received. 75 CLCTINFOINVRX Number of Collect Information: Invoke messages received. 76 ASEINFOINVRX Number of Analyze Information: Invoke messages received. 77 SELROUTINVRX Number of Select Route: Invoke messages received. 78 SELFACINVRX Number of Select Facility: Invoke messages received. 79 CONTINVRX Number of Continue: Invoke messages received. 80 INITCALLATTINVRX Number of Initiate Call Attempt: Invoke messages received. 81 RSTTMRINVRX Number of Reset Timer: Invoke messages received. 82 FURCHGINFOINVRX Number of Furnish Charging Information: Invoke messages

received. 83 APPCHGINVRX Number of Apply Charging: Invoke messages received. 84 APPCHGRPTRERX Number of Apply Charging Report: Return Error messages

received. 85 REQCRNTSTATINVRX Number of Request Current Status Report: Invoke messages

received. 86 REQEVERYSTATINVRX Number of Request Every Status Report: Invoke messages

received. 87 REQFIRSTSTATINVRX Number of Request First Status Match Report: Invoke

messages received. 88 STATRPTINVRX Number of Status Report: Invoke messages received. 89 CALLGAPINVRX Number of Call Gap: Invoke messages received. 90 ACTVSVCFTDINVRX Number of Activate Service Filtering: Invoke messages

received. 91 CALLINFOREQINVRX Number of Call Information Request: Invoke messages

received. 92 SNDCHGINFOINVRX Number of Send Charging Info Send Charging Info: Invoke

messages received. 93 CNCLINVRX Number of Cancel: Invoke messages received. 94 CNCLSTATREQINVRX Number of Cancel Status Report Request: Invoke messages

received. 95 ACTVTSTINVRX Number of Activity Test: Invoke 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 an Establish Temporary Connection: Invoke).


5.10 IS-41 Information (IS41MSGPERF) Performance Group Name: IS41MSGPERF File Naming Convention: IS41MSGPERF.YYMMDD-HHMM.###


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 Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. Will

always equal node number in the file name 4 REDIRREQRRTX Number of Redirection Request: Return Result messages

transmitted. 5 REDIRREQRETX Number of Redirection Request: Return Error messages

transmitted. 6 LOCREQINVTX Number of Location Request: Invoke messages transmitted. 7 XFERTONMBINVTX Number of Transfer To Number Request: Invoke messages

transmitted. 8 REDIRREQINVRX Number of Redirection Request: Invoke messages received. 9 LOCREQRRRX Number of Location Request: Return Result messages

received. 10 LOCREQRERX Number of Location Request: Return Error messages received. 11 XFERTONMBRRRX Number of Transfer To Number Request: Return Result

messages received 12 XFERTONMBRERX Number of Transfer To Number Request: 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 ANSI 41GMSC are included.


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. Mobility Management Related MAP messaging (DMSC) 2. Subscriber Information Related MAP Messaging (GMSC / DMSC) 3. SMS Related MAP Messaging (DMSC) 4. CISS Related MAP Messaging (DMSC) 5. Location-Services Related MAP Messaging (DMSC)

The following sub sections list each software module’s performance pegs.

5.11.1 Mobility Management Related MAP Message (MAPMMMSGPERF) Performance Group Name: MAPMMMSGPERF File Naming Convention: MAPMMMSGPERF.YYMMDD-HHMM.###


Number of records: One per file. Position Field Name Description

1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. Will always equal

node number in the file name 4 CHKIMEIREQTX Number of Check IMEI: Request messages transmitted 5 CANLOCRSPTX Number of Cancel Location: Response messages transmitted 6 CANLOCRETX Number of Cancel Location: Return messages transmitted 7 PURGMSREQTX Number of Mobile Station Purge: Request messages transmitted 8 AUTHINFREQTX Number of Authentication Info: Request messages transmitted 9 INSSUBRSPTX Number of Insert Subscriber Data: Response messages transmitted 10 INSSUBRETX Number of Insert Subscriber Data: Return Error messages transmitted 11 DELSUBRSPTX Number of Delete Subscriber Data: Response messages transmitted 12 DELSUBRETX Number of Delete Subscriber Data: Return Error messages transmitted 13 ACTVTRRSPTX Number of Activate Trace: Response messages transmitted 14 ACTVTRRETX Number of Activate Trace: Return messages transmitted 15 DACTVTRRSPTX Number of Deactivate Trace: Response messages transmitted 16 DACTVTRRETX Number of Deactivate Trace: Return messages transmitted 17 AUTHFAILRPTREQTX Number of Authentication Fail Report: Request messages transmitted 18 UPLOCREQTX Number of Update Location: Request messages transmitted 19 RESTOREREQTX Number of Restore: Request messages transmitted 20 SNDIMSIREQTX Number of Send IMSI: Request messages transmitted 21 PROVROAMNMBRSPTX Number of Provide Roaming Number: Response messages transmitted 22 PROVROAMNMBRETX Number of Provide Roaming Number: Return Error messages

transmitted 23 NOTMMEVREQTX Number of MAP Notify MM: Event messages transmitted 24 SNDIDREQTX Number of Send Identification: Request messages transmitted 25 SNDIDRSPTX Number of Send Identification: Response messages transmitted 26 SNDIDRETX Number of Send Identification: Return Error messages transmitted


Position Field Name Description 27 PREHOREQTX Number of Prepare Handover: Request messages transmitted 28 PREHORSPTX Number of Prepare Handover: Response messages transmitted 29 PREHORETX Number of Prepare Handover: Return Error messages transmitted 30 PRESUBHOREQTX Number of Prepare Subsequent Handover: Request messages

transmitted 31 PRESUBHORSPTX Number of Prepare Subsequent Handover: Response messages

transmitted 32 PRESUBHORETX Number of Prepare Subsequent Handover: Return Error messages

transmitted 33 SNDENDSIGREQTX Number of Send End Signal: Request messages transmitted 34 SNDENDSIGRSPTX Number of Send End Signal: Response messages transmitted 35 PROCACCSIGREQTX Number of Process Access Signaling: Request messages transmitted 36 FWDACCSIGREQTX Number of Forward Access Signaling: Request messages transmitted 37 PROVSUBSINFORSPTX Number of Provide Subscriber Info: Response messages transmitted 38 PROVSUBSINFORETX Number of Provide Subscriber Info: Return Error messages transmitted 39 FWDCHKSSINDREQRX Number of Forward Check SS Indication: Request messages received 40 CHKIMEIRSPRX Number of Check IMEI: Response messages received 41 CHKIMEIRERX Number of Check IMEI: Return Error messages received 42 CANLOCREQRX Number of Cancel Location: Request messages received 43 PURGMSRSPRX Number of Purge MS: Response messages received 44 PURGMSRERX Number of Purge MS: Return messages received 45 AUTHINFRSPRX Number of Authentication Info: Response messages received 46 AUTHINFRERX Number of Authentication Info: Return Error messages received 47 INSSUBREQRX Number of Insert Subscriber Data: Request messages received 48 DELSUBREQRX Number of Delete Subscriber Data: Request messages received 49 RESETREQRX Number of Reset: Request messages received 50 ACTVTRREQRX Number of Activate Trace: Request messages received 51 DACTVTRREQRX Number of Deactivate Trace: Request messages received 52 AUTHFAILRPTRSPRX Number of Authentication Fail Report: Response messages received 53 AUTHFAILRPTRERX Number of Authentication Fail Report: Return Error messages received 54 UPLOCRSPRX Number of Update Location: Response messages received 55 UPLOCRERX Number of Update Location: Return Error messages received 56 RESTORERSPRX Number of Restore SS: Response messages received 57 RESTORERERX Number of Restore SS: Return Error messages received 58 SNDIMSIRSPRX Number of Send IMSI: Response messages received 59 SNDIMSIRERX Number of Send IMSI: Return Error messages received 60 PROVROAMNMBREQRX Number of Provide Roaming Number: Request messages received 61 NOTMMEVRSPRX Number of MAP Notify MM Event: Response messages received. 62 NOTMMEVRERX Number of MAP Notify MM Event: Return Error messages received. 63 SNDIDREQRX Number of Send Identification: Request messages received 64 SNDIDRSPRX Number of Send Identification: Response messages received 65 SNDIDRERX Number of Send Identification: Return Error messages received 66 PREHOREQRX Number of Prepare Handover: Request messages received 67 PREHORSPRX Number of Prepare Handover: Response messages received 68 PREHORERX Number of Prepare Handover: Return Error messages received 69 PRESUBHOREQRX Number of Prepare Subsequent Handover: Request messages

received 70 PRESUBHORSPRX Number of Prepare Subsequent Handover: Response messages

received 71 PRESUBHORERX Number of Prepare Subsequent Handover: Return Error message

received 72 SNDENDSIGREQRX Number of Send End Signal: Request messages received 73 SNDENDSIGRSPRX Number of Send End Signal: Response messages received 74 PROCACCSIGREQRX Number of Process Access Signaling: Request messages received 75 FWDACCSIGREQRX Number of Forward Access Signaling: Request messages received 76 PROVSUBSINFOREQRX Number of Provide Subscriber Info: 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 Provide Roaming Number Request).


5.11.2 Subscriber Information Related MAP Messaging (MAPSPMMSGPERF) Performance Group Name: MAPSPMMSGPERF File Naming Convention: MAPSPMMSGPERF.YYMMDD-HHMM.###




node number in the file name 4 ROUTINFOREQTX Number of Send Route Info: Request messages transmitted 5 RESCALLHANDLREQTX Number of Resume Call Handling: Request messages transmitted 6 RESCALLHANDLRSPTX Number of Resume Call Handling: Response messages transmitted 7 RESCALLHANDLRETX Number of Resume Call Handling: Return Error messages transmitted 8 ROUTINFORSPRX Number of Send Route Info: Response messages received 9 ROUTINFORERX Number of Send Route Info: Return Error messages received 10 RESCALLHANDLREQRX Number of Resume Call Handling: Request messages received 11 RESCALLHANDLRSPRX Number of Resume Call Handling: Response messages received 12 RESCALLHANDLRERX 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).


5.11.3 SMS Related MAP Messaging (MAPSMSMSGPERF) Performance Group Name: MAPSMSMSGPERF File Naming Convention: MAPSMSMSGPERF.YYMMDD-HHMM.###



1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. Will always

equal node number in the file name 4 SMRDYREQTX Number of Short Message Ready: Request messages transmitted 5 NOTSUBPRESREQTX Number of Notify Subscriber Present: Request messages

transmitted 6 FWDSMREQTX Number of Forward Short Message: Request messages transmitted 7 MTFWDSMRSPTX Number of Mobile Terminated Forward Short Message: Response

messages transmitted 8 MTFWDSMRETX Number of Mobile Terminated Forward Short Message: Return Error

messages transmitted 9 SMRDYRSPRX Number of Short Message Ready: Response messages received 10 SMRDYRERX Number of Short Message Ready: Return messages received 11 NOTSUBPRESREQRX Number of Notify Subscriber Present: Request messages received 12 FWDSMRSPRX Number of Forward Short Message: Response messages received 13 FWDSMRERX Number of Forward Short Message: Return Error messages

received 14 MTFWDSMREQRX Number of Mobile Terminated Forward Short Message: 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 Forward Short Message Response).


5.11.4 CISS Related MAP Messaging (MAPCISSMSGPERF) Performance Group Name: MAPCISSMSGPERF File Naming Convention: MAPCISSMSGPERF.YYMMDD-HHMM.###




equal node number in the file name 4 REGSSREQTX Number of Register SS: Request messages transmitted 5 ERASESSREQTX Number of Erase SS: Request messages transmitted 6 ACTVSSREQTX Number of Activate SS: Request messages transmitted 7 DACTVSSREQTX Number of Deactivate SS: Request messages transmitted 8 INTERSSREQTX Number of Interrogate SS: Request messages transmitted 9 REGPASSWDREQTX Number of Register Password: Request messages transmitted 10 GETPASSWDRSPTX Number of Get Password: Response messages transmitted 11 GETPASSWDRETX Number of Get Password: Return Error messages transmitted 12 PROCUSSDATREQTX Number of Process USS Data: Request messages transmitted 13 PROCUSSDATRSPTX Number of Process USS Data: Response messages transmitted 14 PROCUSSDATRETX Number of Process USS Data: Return Error messages transmitted 15 PROCUSSREQTX Number of Process USS: Request messages transmitted 16 PROCUSSRSPTX Number of Process USS: Response messages transmitted 17 PROCUSSRETX Number of Process USS: Return Error messages transmitted 18 USSREQTX Number of USS: Request messages transmitted 19 USSRSPTX Number of USS: Response messages transmitted 20 USSRETX Number of USS: Return error messages transmitted 21 USSNOTRETX Number of USS Notify: Return Error messages transmitted 22 BGNSUBACTVREQTX Number of Begin Subscriber Activity: Request messages transmitted 23 REGSSRSPRX Number of Register SS: Response messages received 24 REGSSRERX Number of Register SS: Return Error messages received 25 ERASESSRSPRX Number of Erase SS: Response messages received 26 ERASESSRERX Number of Erase SS: Return Error messages received 27 ACTVSSRSPRX Number of Activate SS: Response messages received 28 ACTVSSRERX Number of Activate SS: Return Error messages received 29 DACTVSSRSPRX Number of Deactivate SS: Response messages received 30 DACTVSSRERX Number of Deactivate SS: Return Error messages received 31 INTERSSRSPRX Number of Interrogate SS: Response messages received 32 INTERSSRERX Number of Interrogate SS: Return Error messages received 33 REGPASSWDRSPRX Number of Register Password: Response messages received 34 REGPASSWDRERX Number of Register Password: Return Error messages received 35 GETPASSWDREQRX Number of Get Password: Request messages received 36 PROCUSSDATREQRX Number of Process USS DATA: Request messages received 37 PROCUSSDATRSPRX Number of Process USS DATA: Response messages received 38 PROCUSSDATRERX Number of Process USS DATA: Return Error messages received 39 PROCUSSREQRX Number of Process USS: Request messages received 40 PROCUSSRSPRX Number of Process USS: Response messages received


Position Field Name Description 41 PROCUSSRERX Number of Process USS: Return Error messages received 42 USSREQRX Number of USS: Request messages received 43 USSRSPRX Number of USS: Response messages received 44 USSRERX Number of USS: Return Error messages received 45 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).


5.11.5 Location Services Related MAP Messaging (MAPLCSMSGPERF) Performance Group Name: MAPLCSMSGPERF File Naming Convention: MAPLCSMSGPERF.YYMMDD-HHMM.###




node number in the file name 4 PROVSUBSLOCRSPTX Number of Provide Subscriber Location: Response messages

transmitted 5 PROVSUBSLOCRETX Number of Provide Subscriber Location: Return Error messages

transmitted 6 SUBSLOCREQTX Number of Subscriber Location: Request messages transmitted 7 PROVSUBSLOCREQRX Number of Provide Subscriber Location: Request messages received 8 SUBSLOCRSPRX Number of Subscriber Location: Response messages received 9 SUBSLOCRERX Number of Subscriber Location: 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 Provide Subscriber Location Request message).


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 module’s 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 Description


equal node number in the file name 4 DPC Destination Point Code. 5 ASSIGNMENTREQTX Number of Assignment Request messages transmitted. 6 CLRCOMMANDTX Number of Clear Command messages transmitted. 7 HOCANDIDATEENQUIRETX Number of Handover Candidate Enquire messages transmitted. 8 HOREQUESTTX Number of Handover Request messages transmitted. 9 HOREQUIREDREJTX Number of Handover Required Reject messages transmitted. 10 HOCOMMANDTX Number of Handover Command messages transmitted. 11 HOSUCCEEDEDTX Number of Handover Succeeded messages transmitted. 12 RESOURCEREQTX Number of Resource Request messages transmitted. 13 PAGINGTX Number of Paging messages transmitted. 14 OVERLOADTX Number of Overload messages transmitted. 15 MSCINVOKETRACETX Number of MSC Invoke Trace messages transmitted. 16 BSSINVOKETRACETX Number of BSS Invoke Trace messages transmitted. 17 CLASSMARKREQUESTTX Number of Classmark Request messages transmitted. 18 CIPHERMODECOMMANDTX Number of Cipher Mode Command messages transmitted. 19 LOADINDTX Number of Load Indication messages transmitted. 20 CHANGECIRCUITTX Number of Change Circuit messages transmitted. 21 COMMONIDTX Number of Common ID messages transmitted. 22 LSAINFOTX Number of LSA Information messages transmitted. 23 PERFORMLOCREQTX Number of Perform Location Request messages transmitted. 24 CONNECTIONLESSINFOTX Number of Connectionless Information messages transmitted. 25 ASSIGNMENTCOMPLETERX Number of Assignment Complete messages received. 26 ASSIGNMENTFAILURERX Number of Assignment Failure messages received. 27 CLRCOMPLETERX Number of Clear Complete messages received. 28 CLRREQRX Number of Clear Request messages received. 29 HOCANDIDATERSPRX Number of Handover Candidate Response messages received.


Position Field Name Description 30 HOREQUIREDRX Number of Handover Required messages received. 31 HOREQUESTACKRX Number of Handover Request Acknowledge messages received. 32 HOCOMPLETERX Number of Handover Complete messages received. 33 HOSUCCEEDEDRX Number of Handover Succeeded messages received. 34 HOFAILURERX Number of Handover Failure messages received. 35 HOPERFORMEDRX Number of Handover Performed messages received. 36 HODETECTRX Number of Handover Detect messages received. 37 RESOURCEINDRX Number of Resource Indication messages received. 38 OVERLOADRX Number of Overload messages received. 39 BSSINVOKETRACERX Number of BSS Invoke Trace messages received. 40 CLASSMARKUPDATERX Number of Classmark Update messages received. 41 CIPHERMODECOMPLETERX Number of Cipher Mode Complete messages received. 42 CIPHERMODEREJECTRX Number of Cipher Mode Reject messages received. 43 COMPLETELAYER3INFORX Number of Complete Layer 3 Information messages received. 44 QUEUINGINDICATIONRX Number of Queuing Indication messages received. 45 SAPINREJECTRX Number of SAPI "N" Reject messages received. 46 LOADINDRX Number of Load Indication messages received. 47 SUSPENDRX Number of Suspend messages received. 48 RESUMERX Number of Resume messages received. 49 CHANGECIRCUITACKRX Number of Change Circuit Acknowledge messages received. 50 PERFORMLOCRESPRX Number of Perform Location Response messages received. 51 PERFORMLOCABORTRX Number of Perform Location Abort messages received. 52 CONNECTIONLESSINFORX Number of Connectionless Information 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).


5.12.2 Circuit and System Maintenance Related BSSAP Information (BSSAPMNTMSGPERF)

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


Number of records: Equals the number of BSS destination point codes provisioned in the system. Position Field Name Description


equal node number in the file name 4 DPC Destination Point Code. 5 BLOCKTX Number of Block messages transmitted. 6

BLOCKINGACKNOWLEDGETX Number of Blocking Acknowledgment messages transmitted.

7 CKTGRPBLCKTX Number of Circuit Group Block messages transmitted. 8 CKTGRPBLCKINGACKTX Number of Circuit Group Blocking Acknowledgment messages

transmitted. 9 CKTGRPUNBLOCKTX Number of Circuit Group Unblock messages transmitted. 10 CKTGRPUNBLCKINGACKTX Number of Circuit Group Unblocking Acknowledgment messages

transmitted. 11 UNBLOCKTX Number of Unblock messages transmitted. 12 UNBLOCKINGACKTX Number of Unblocking Acknowledgment messages transmitted. 13 RESETTX Number of Reset messages transmitted. 14 RESETACKTX Number of Reset Acknowledgment messages transmitted. 15 RESETCIRCUITTX Number of Reset Circuit messages transmitted. 16 RESETCIRCUITACKTX Number of Reset Circuit Acknowledgment messages transmitted. 17 CONFUSIONTX Number of Confusion messages transmitted. 18 UNEQUIPPEDCKTTX Number of Unequipped Circuit messages transmitted. 19 BLOCKRX Number of Block messages received. 20 BLOCKINGACKNOWLEDGERX Number of Blocking Acknowledgment messages received. 21 CKTGRPBLCKRX Number of Circuit Group Block messages received. 22 CKTGRPBLCKINGACKRX Number of Circuit Group Blocking Acknowledgment messages

received. 23 CKTGRPUNBLOCKRX Number of Circuit Group Unblock messages received. 24 CKTGRPUNBLCKINGACKRX Number of Circuit Group Unblocking Acknowledgment messages

received. 25 UNBLOCKRX Number of Unblock messages received. 26 UNBLOCKINGACKRX Number of Unblocking Acknowledgment messages received. 27 RESETRX Number of Reset messages received. 28 RESETACKRX Number of Reset Acknowledgment messages received. 29 RESETCIRCUITRX Number of Reset Circuit messages received. 30 RESETCIRCUITACKRX Number of Reset Circuit Acknowledgment messages received. 31 CONFUSIONRX Number of Confusion messages received. 32 UNEQUIPPEDCKTRX 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:



To provide a system-wide view of the information in this performance group, the values must be accumulated across all CCM cards.


6 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 Field Name Description

1. STARTTIMESTAMP Beginning time of the performance interval 2. STOPTIMESTAMP Ending time of the performance interval 3. WSSNODENUM WSS Node (CCM Card) to which this record applies. 4. CALLATTMSTOMSVCCAL Number of attempted mobile-to-mobile calls pegged when

setup message is sent to the terminating MS. 5. CALLSUCCMSTOMSVCCAL

Number of successful mobile-to-mobile calls pegged when assignment complete message is received from the terminating MS.

6. CALLANSMSTOMSVCCAL Number of answered mobile-to-mobile calls pegged when connect message received from terminating MS.

7. CALLATTMSTOPSTNVCCAL 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.

8. CALLSUCCMSTOPSTNVCCAL Number of successful mobile to PSTN calls pegged when ACM received from terminating switch.

9. CALLANSMSTOPSTNVCCAL Number of answered mobile to PSTN calls pegged when ANM received from terminating switch.

10. CALLATTPSTNTOMSVCCAL Number of attempted PSTN to mobile call pegged when setup message is sent to the terminating MS.

11. CALLSUCCPSTNTOMSVCCAL Number of successful PSTN to mobile calls pegged when assignment complete message is received from the terminating MS.

12. CALLANSPSTNTOMSVCCAL Number of answered PSTN to mobile calls pegged when connect message received from terminating MS.

13. CALLATTLANDTOLANDCAL Number of attempted Land-to-Land call pegged when IAM is sent to the terminating switch.

14. CALLSUCCLANDTOLANDCAL Number of successful Land-to-Land call pegged when ACM received from terminating switch.

15. CALLANSLANDTOLANDCAL Number of answered Land to Land call pegged when ANM received from terminating switch.

16. SUCCMSORIGCTMCALLS Number of successful CTM calls for 2G and UMA mobile originating traffic

17. SUCCMSTERCTMCALLS Number of successful CTM calls for 2G and UMA mobile terminating traffic

18. ATTMSORIGCTMCALLS Number of attempted CTM calls for 2G and UMA mobile originating traffic

19. ATTMSTERCTMCALLS Number of attempted CTM calls for 2G and UMA mobile terminating traffic

20. ORINTERROGATION Number of OR Interrogation.

21. ORINTERPLMNCALLALLOWED Number of Inter-PLMN Calls Allowed

22. ORINTERPLMNCALLNOTALLOWED Number of Inter-PLMN Calls Not Allowed

23. OREARLYCFALLOWED Number of OR Early CF Allowed.

24. ORGMSCLATCFALLOWED Number of OR GMSC Late CF Allowed. Pegged when the RCH message received with call forwarding allowed.


Position Field Name Description

25. ORGMSCLATCFNOTALLOWED

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.

26. ORGMSCLATECFFAILED 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.

27. ORVMSCLATCFREQUEST

Number of OR VMSC Late CF Request. Pegged when RCH message is sent.

28. ORVMSCLATECFALLOWED

Number of OR VMSC Late CF Allowed. Pegged when RCH response with status “OK” is received from other MSC.

29.

ORVMSCLATECFNOTALLOWED Number of OR VMSC Late CF Not Allowed. Pegged when

RCH response with status “not allowed” received.

30. ORVMSCLATECFFAILED Number of OR VMSC Late CF Failed. Pegged when RCH

response with status “Failed or timeout” received.

31. ORVMSCLATECFREQTIMEOUT Number of OR VMSC Late CF Timeout. 32. INVOKECFUSS Number of Call Forwarding Unconditional. 33. INVOKECFBSS Number of Call Forwarding Busy. 34. INVOKECFNRYSS Number of Call Forwarding No Reply. 35. INVOKECFNRCSS Number of Call Forwarding Not Reachable 36. INVOKECALLWAITSS Number of Call Waiting. 37. INVOKEECTSS Number of Explicit Call Transfers 38. INVOKEMULTIPARTYSS Number of Multi-party calls. 39. ADDDNTOGSMEXCPTION Add DN to GSM Exception. 40. DELDNFROMGSMEXCPTION Delete DN from GSM Exception. 41. ADDDNTOANSI41EXCPTION Add DN to ANSI-41 Exception. 42. DELDNFROMANSI41EXCPTION Delete DN from ANSI-41 Exception. 43. LNPDIPTOTAL Total number of LNP NPDB dips. 44. LNPDIPRESULTLRN Number of LNP NPDB dips resulting in LRN being returned. 45. LNPDIPNONPORTED Number of LNP NPDB dips resulting in dialed number being

returned (non-ported case). 46. LNPOWNLRNUNALLOC

Number of instances of an LRN being returned which is the operator’s (own) LRN, but for which the related HLR query result is unsuccessful

47. LNPMISROUTE Number of instances of an IAM arriving with LRN (and FCI M-

bit set to “number translated”), where LRN is the operator’s (own) LRN, but for which the related HLR query result is unsuccessful

48. SEVENDIGITDIALATT Number of 7-digit dialing attempts. 49. SEVENDIGITDIALSUCC Number of calls that are allowed to go through with user dials

7 digits. 50. LONGCALLDISCONNECT Number of calls disconnected by the long call disconnect

function. 51. CALLATT3GTO2GVCCAL Number of attempted 3G to 2G mobile calls pegged when

setup message is sent to the terminating MS. 52. CALLSUCC3GTO2GVCCAL Number of successful 3G to 2G mobile calls pegged when


Position Field Name Description assignment complete received from the terminating MS.

53. CALLANS3GTO2GVCCAL Number of answered 3G to 2G mobile calls pegged when connect message received from the terminating MS.

54. CALLATT3GTOLANDVCCAL Number of attempted 3G mobile to land calls pegged when IAM message is sent to the terminating switch.

55. CALLSUCC3GTOLANDVCCAL Number of successful 3G mobile to land calls pegged when ACM message received from the terminating switch.

56. CALLANS3GTOLANDVCCAL Number of answered 3G mobile to land calls pegged when ANM message received from the terminating switch.

57. CALLATTM2GTO3G Number of attempted 2G to 3G mobile calls pegged when setup message is sent to the terminating MS.

58. CALLSUCC2GTO3G Number successful 2G to 3G mobile calls pegged when RAB assignment complete received from the terminating MS.

59. CALLANS2GTO3G Number of answered 2G to 3G mobile calls pegged when connect message received from the terminating MS.

60. CALLATTMLANDTO3G Number of attempted land to 3G mobile calls pegged when setup message is sent to the terminating MS.

61. CALLSUCCLANDTO3G Number of successful land to 3G mobile calls pegged when RAB assignment complete received from the terminating MS.

62. CALLANSLANDTO3G Number of answered land to 3G mobile calls pegged when connect message received from the terminating MS.

63. CALLATTUMATO2GVCCAL Number of attempted UMA to 2G calls pegged when setup message is sent to the terminating MS.

64. CALLSUCCUMATO2GVCCAL Number of successful UMA to 2G calls pegged when assignment complete received from the terminating MS.

65. CALLANSUMATO2GVCCAL Number of answered UMA to 2G calls pegged when connect message received from the terminating MS.

66. CALLATTUMATOUMAVCCAL Number of attempted UMA to UMA calls pegged when setup message is sent to the terminating MS.

67. CALLSUCCUMATOUMAVCCAL Number of successful UMA to UMA calls pegged when assignment complete received from the terminating MS.

68. CALLANSUMATOUMAVCCAL Number of answered UMA to UMA calls pegged when connect message received from the terminating MS.

69. CALLATT2GTOUMAVCCAL Number of attempted 2G to UMA calls pegged when setup message is sent to the terminating MS.

70. CALLSUCC2GTOUMAVCCAL Number of successful 2G to UMA calls pegged when assignment complete received from the terminating MS.

71. CALLANS2GTOUMAVCCAL Number of answered 2G to UMA calls pegged when connect message received from the terminating MS.

72. CALLATTPSTNTOUMAVCCAL Number of attempted PSTN to UMA calls pegged when setup message is sent to the terminating MS.

73. CALLSUCCPSTNTOUMAVCCAL Number of successful PSTN to UMA calls pegged when assignment complete received from the terminating MS.

74. CALLANSPSTNTOUMAVCCAL Number of answered PSTN to UMA calls pegged when connect message received from the terminating MS.

75. CALLATTUMATOPSTNVCCAL Number of attempted UMA to PSTN calls pegged when IAM message is sent to the terminating switch.

76. CALLSUCCUMATOPSTNVCCAL Number of successful UMA to PSTN calls pegged when ACM or ANM message is received from the terminating switch.

77. CALLANSUMATOPSTNVCCAL Number of answered UMA to PSTN calls pegged when ANM message is received from the terminating switch.

78. CNAMQUERYATT 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.

79. CNAMQUERYSUCC 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.

80. CNAMQUERYTIMEOUT This counter is pegged when Call processing timeout on CNAP query to the SPM process that wait for CNAP query


Position Field Name Description response from LIDB.

81. Reserved4 Reserved field 4 for future use 82. Reserved5 Reserved field 5 for future use 83. Reserved6 Reserved field 6 for future use 84. Reserved7 Reserved field 7 for future use 85. Reserved8 Reserved field 8 for future use 86. Reserved9 Reserved field 9 for future use 87. Reserved10 Reserved field 10 for future use

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.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 ATTINTERROHLRFORROUTING Number of HLR queries by the GMSC function for the purpose of

routing incoming calls 5 SUCCINTERROHLRMSRN Number of successful HLR interrogations where MSRN is obtained 6 SUCCINTERROHLRCALFRWD Number of successful HLR interrogations where forwarded to

number obtained 7 SUCCINTERROHLRCAMEL Number of successful HLR interrogations where T-CSI is returned 8 RESERVED1 Reserved field 1 for future use 9 RESERVED2 Reserved field 2 for future use 10 RESERVED3 Reserved field 3 for future use 11 RESERVED4 Reserved field 4 for future use



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 Description

1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies.

4 ATTININTERMSCHDO Number of attempted incoming inter-MSC handovers18 pegged when the serving MSC receives MAP-Prep-Handover-Req message from the anchor MSC.

5 SUCCININTERMSCHDO Number of successful incoming inter-MSC handovers pegged when the serving MSC sends MAP-Send-End-Signal-Req to the anchor MSC.

6 OUTINTERMSCHDO Number of attempted outgoing inter-MSC handovers pegged when the anchor MSC sends MAP-Prep-Handover-Req message to the serving MSC.

7 SUCCOUTINTERMSCHDO Number of successful outgoing inter-MSC handovers pegged when the anchor MSC receives MAP-Send-End-Signal-Req from the serving MSC.

8 ATTSUBSQNTINTERMSCHDOMSCA Number of attempted subsequent inter-MSC handbacks (to MSC-A)19 pegged when the anchor MSC-A receives MAP-Prep-Sub-Handover-Req from the serving MSC-B.

9 SUCCSUBSQNTINTERMSCHDOMSCA

Number of successful subsequent inter-MSC handbacks (to MSC-A) pegged when the anchor MSC-A sends back MAP-Send-End-Signal-Resp to the serving MSC-B.

10 ATTSUBSQNTINTERMSCHDOMSCC Number of attempted subsequent inter-MSC handovers (to MSC-C) pegged when the anchor MSC-A receives MAP-Prep-Sub-Handover-Req and attempts to send MAP-Prep-Handover-Req to the target MSC-C.

11 SUCCSUBSQNTINTERMSCHDOMSCC

Number of successful subsequent inter-MSC handovers (to MSC-C) pegged when anchor MSC-A receives MAP-Send-End-Signal-Req from target MSC-C and attempts to send MAP-Send-End-Signal-Resp to serving MSC-B.

12 ATTIDRQSTTOPVLR Number of identification information requests to the previous VLR for subscribers registering afresh in this VLR

13 SUCCIDRQSTTOPVLR Number of successful identification requests to the previous VLR for subscriber registering afresh in this VLR

14 ATTAUTHSETSRQSTTOHLR Number of requests to the HLR by the VLR for Authentication triplets 15 SUCCAUTHSETSFROMHLR Number of successful responses (including Authentication triplet

vector) received by the VLR in response to requests for Authentication information.

16 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.)

17 TOTALTRIPLETAUTHSETSFROMHLR Total Number of successful actual triplets. It includes triplets from previous VLR in inter-VLR location updates

18 ATTLOCUPDTHLR Attempted location updates to HLR from VLR 19 SUCCLOCUPDTHLR Success location updates to HLR from VLR 20 ATTREQFORMSRN Requests for MSRN received by VLR 21 SUCCREQFORMSRN Successful Request for MSRN (MSRN available, response sent)

18 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)


Position Field Name Description 22 CANCELLOCREQFROMHLR Cancel Location Request From HLR 23 INSSUBSCRIBERFROMHLR Number of successful Insert Subscriber Data transactions received

from HLR 24 DELSUBSCRIBERFROMHLR Number of Delete Subscriber received from HLR

25 USOUTINTERMSCHORB Number of unsuccessful Inter MSC handovers out of serving MSC-A with reconnect back to MSC-A. Pegged when MSC-A receives an A-HO-FAILURE from its BSS-A and MSC-A attempts to send MAP Process Access Signaling Req to target MSC-B. This was previously mapped to RESERVED120

26 USSUBINTERMSCHOMSCARB 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 A-HO-FAILURE from serving MSC-B. This was previously mapped to RESERVE221.

27 USSUBINTERMSCHOMSCCRB Number of unsuccessful subsequent Inter MSC handovers out of Serving MSC-B to target MSC-C with reconnect back to Serving MSC-B22. Pegged when anchor MSC-A receives MAP-Process-Access-Signaling req with HO failure from serving MSC-B.

28 ATTOUTSUBINTERMSCHOMSCA 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 previously mapped to RESERVE323

29 ATTOUTSUBINTERMSCHOMSCC Number of subsequent Inter MSC handover attempts out of serving MSC-B to MSC-C24, pegged when MSC-B sends MAP-Prep-Sub-Handover-Req to MSC-A (anchor) for target cell belonging to MSC-C. (Not supported as a separate counter, currently pegged as part of 28)

30 SUCCOUTSUBINTERMSCHOMSCA 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 mapped to RESERVE425

31 SUCCOUTSUBINTERMSCHOMSCC 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-End-Sig Resp from MSC-A .26 (currently not supported)

32 USOUTSUBINTERMSCHOMSCARB

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 HO-Failure 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 # 16) in the Patch 2.3.1727

33 USOUTSUBINTERMSCHOMSCCRB Number of unsuccessful subsequent Inter MSC handovers out of Serving MSC-B to target MSC-C with reconnect back to MSC-B28. 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..

34 RESERVED1 Reserved field 1 for future use 35 RESERVED2 Reserved field 2 for future use

20 Added by FR-0453 21 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


Position Field Name Description 36 RESERVED3 Reserved field 3 for future use 37 RESERVED4 Reserved field 4 for future use 38 RESERVED5 Reserved field 5 for future use 39 RESERVED6 Reserved field 6 for future use 40 RESERVED7 Reserved field 7 for future use 41 RESERVED8 Reserved field 8 for future use 42 RESERVED9 Reserved field 9 for future use 43 RESERVED10 Reserved field 10 for future use



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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 NBRCLSMRKUPDT Number of Classmark Updates 5 ATTMSORIGCALLS Number of call attempts for mobile originating traffic

Pegged when a SETUP message is received from the originating mobile.

6 MSORIGCMSRVCREQ CM Service Request from originating MS – number of all CM_SERVIC_REQUEST messages (voice, data, SMS) received.

7 SUCCMSORIGCALLS Number of successful calls for mobile originating traffic Pegged when an “Assignment Complete” message is sent to the originating mobile

8 ANSMSORIGCALLS Number of answered calls for mobile originating traffic Pegged when a connect ack message is received from the originating MS.

9 ATTMSTERCALLS Number of call attempts for mobile terminating traffic Pegged when an attempt is made to send a SETUP message to the terminating mobile

10 SUCCMSTERCALLS Number of successful calls for mobile terminating traffic Pegged when an “Assignment Complete” message is received from the terminating side.

11 ANSMSTERCALLS Number of answered calls for mobile terminating traffic Pegged when a Connect Ack message is sent to the terminating mobile.

12 ATTMSEMRGNCYCALLS Number of emergency call attempts Pegged when a “Setup or Emergency Setup” message is received from the originating mobile

13 MSEMRGNCYCMSRVCREQ Number of Emergency CM Service Requests – number of CM_SERVICE_REQUEST” (Emergency Call) messages received

14 SUCCMSEMRGNCYCALLS Number of successful emergency calls pegged when an “Assignment complete” message is sent to the originating side.

15 ANSMSEMRGNCYCALLS Number of answered emergency calls pegged when an answer message is sent to the originating side.

16 ATTCIPHRMDCTRPROCS Number of ciphering mode control procedures transmitted Pegged on attempt to send “Cipher Request” to mobile

17 SUCCCIPHRMDCTRPROCS Number of successful ciphering mode control procedures Pegged on “Cipher Response” received by the WSS

18 TRANSSUBIDWTMSI Number of transactions where mobile subscriber was identified with his TMSI

19 TRANSSUBIDWIMSI Number of transactions where mobile subscriber was identified with his IMSI

20 ATTTMSIREALOC Number of TMSI re-allocation attempts 21 SUCCTMSIREALOC Number of successfully performed TMSI re-allocations 22 IMSIDETACHPROCS Number of IMSI Detach procedures – number of “Location

Update Request” (Detach) messages received 23 IMSIATTACHPROCS Number of IMSI Attach procedures – number of Location Update

Request (Attach) messages received


Position Field Name Description 24 IMPLICITDETACH Total Number of subscribers implicitly detached (i.e. by VLR

audit) 25 ATTINEXTINTRAMSCHDO Number of intra-MSC target cell handover procedures initiated

(pegged at dispatch of BSSMAP:Handover Request)29 26 SUCCINEXTINTRAMSCHDO

Number of intra-MSC target cell handover procedures successfully completed (pegged at receipt of BSSMAP:Handover Complete)

27 SUCCOUTEXTINTRAMSCHDO Number of intra-MSC serving cell handover procedures

successfully completed (pegged at receipt of BSSMAP:Clear Complete from serving BSS

28 EXTHDO Number of handovers initiated (pegged at receipt of BSSMAP:Handover Required)

29 UNSCCEXTHDORECNCTPERMSC Number of unsuccessful Handovers with reconnect to the original

channels pegged when HO failure received from the serving BSS.

30 UNSCEXTHDOLOSSCNCTPERMSC

Number of unsuccessful Handovers with loss of the call pegged when Clear Request message is received from the serving BSS.

31 SUCCINTRAHOCTMCALLS Number of successful Intra MSC HO for CTM Calls 32 SUCCINTEROUTHOCTMCALLS Number of successful Outgoing Inter-MSC HO for CTM Calls 33 SUCCINTERINHOCTMCALLS Number of successful Incoming Inter-MSC HO for CTM Calls 34 ATTINTRAHOCTMCALLS Number of attempted Intra MSC HO CTM Calls 35 ATTINTEROUTHOCTMCALLS Number of attempted Outgoing Inter-MSC HO for CTM Calls 36 ATTINTERINHOCTMCALLS Number of attempted Incoming Inter-MSC HO for CTM Calls 37 ATTINTERVLRLOCUPD Number of attempted (incoming) inter VLR location update

pegged when MAP Update Location Req is received by VLR with no subscriber record in VLR.

38 SUCCINTERVLRLOCUPD 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.

39 ATTINTRAVLRLOCUPD 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.

40 ATTPERIINTRAVLRLOCUPD Number of attempted periodic intra VLR location update 41 SUCCINTRAVLRLOCUPD 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.

42 SUCCPERIINTRAVLRLOCUPD Number of successful periodic intra VLR location update 43 ATTAUTH Number of attempted Authentication procedures

Attempt to send “authentication request to mobile 44 SUCCAUTH Number of successful Authentication procedures An

“authentication response” received by the WSS 45 TOTALACTIVESUB Number of total subscribers30 in the VLR, it provides a snap shot

of total subscribers in the VLR database. 46 INTRABSCHANDOVER Number of Intra BSC Handover pegged when “Handover

performed” message is received from the BSS. 47 CALLVLRRGSTRDSUBFROMOTHERPLMN Number of roamers registered in the VLR31 48 ATTPAGEMSTMSI Number of Paging Attempts (within LAC) with TMSI. Pegged at

attempt to send first Paging Request with TMSI message. 49 SUCCPAGEMSTMSI Number of Successful Paging (within LAC) with TMSI

29 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.


Position Field Name Description 50 ATTPAGEMSIMSI Number of Paging Attempts (within LAC) with IMSI. Pegged on

attempt to send first paging request with IMSI message 51 SUCCPAGEMSIMSI Number of Successful Paging (within LAC) with IMSI 52 ATTSEARCHMSIMSI Number of Global Search Attempts with IMSI

Pegged on attempt to send Paging Retry message (2nd) or first Paging Request when the LAC is invalid

53 SUCCSEARCHMSIMSI Number of Successful Global Searches with IMSI – number of Paging_response (2nd) or 1st Paging when invalid LAC messages

54 REJLUPPLMNNOTALLOWED Number of Location Updates rejected due to visitor’s PLMN not allowed. LUP Rejection Cause value is 11.32 Pegged when unable to derive or find HLR from IMSI.

55 REJLUPLACNOTALLOWED Number of Location Updates rejected due to invalid CGI (Cell Global Id). LUP Rejection Cause value is 12.33

56 REJLUPROAMNOTALLOWED Number of Location Updates rejected due to roaming not allowed in this location area (LAC or PLMN in restrictions list). LUP Rejection Cause value is 13.34

57 ATTOUTEXTINTRAMSCHO Number of intra-MSC but inter-BSC Handover attempts35 pegged when HO required is received from serving BSS and attempt is being made to send HO request to the target BSS.

58 RESERVED1 Reserved field 1 for future use 59 RESERVED2 Reserved field 2 for future use 60 RESERVED3 Reserved field 3 for future use 61 RESERVED4 Reserved field 4 for future use 62 RESERVED5 Reserved field 5 for future use 63 RESERVED6 Reserved field 6 for future use 64 RESERVED7 Reserved field 7 for future use 65 RESERVED8 Reserved field 8 for future use 66 RESERVED9 Reserved field 9 for future use 67 RESERVED10 Reserved field 10 for future use


32 Added by FR-0454 33 Added by FR-0454 34 Added by FR-0454 35 Added by FR-0453


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 Description

1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 LOCREQREQSENT Number of Location Request sent to HLR 5 LOCREQRSPWROUTNUMRECVD Number of Location Request response with Routing Number

received from HLR 6 LOCREQRSPWCFRECVD Number of Location Request response with Call Forwarding

received from HLR 7 REDIRREQREQRECVD Number of Redirection request received from HLR 8 REDIRREQRSPSENT Number of Redirection response sent to HLR 9 TRANSNUMREQSENT Number of transfer to number sent to HLR 10 TRANSNUMRSPRECVD Number of transfer to number response received from HLR 11 RESERVED1 Reserved field 1 for future use 12 RESERVED2 Reserved field 2 for future use 13 RESERVED3 Reserved field 3 for future use 14 RESERVED4 Reserved field 4 for future use



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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 CALLATTMSORGSMS Number of attempted SMS transactions for mobile originating traffic

pegged when “RP Data” is received from MS. 5 CALLSUCCMSORGSMS Number of successful SMS transactions for mobile originating traffic36

pegged when attempt is made to send “RP_ACK” to MS. 6 CALLATTMSTERMSMS Number of attempted SMS transactions for mobile terminating traffic

pegged when attempt is made to send “RP Data” to the MS. 7 CALLSUCCMSTERMSMS Number of successful SMS transactions for mobile terminating traffic

pegged when RP_ACK is received from the MS. 8 RESERVED1 Reserved field 1 for future use 9 RESERVED2 Reserved field 2 for future use 10 RESERVED3 Reserved field 3 for future use 11 RESERVED4 Reserved field 4 for future use


36 Successful transaction implies confirmation of end-to-end delivery of the short message.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 ACTIVATIONATTEMPT Number of SS feature activation attempts. 5 ACTIVATIONSUCCESS Number of SS feature activation succeeded. 6 DEACTIVATIONATTEMPT Number of SS feature de-activation attempts.37 7 DEACTIVATIONSUCCESS Number of SS feature de-activation succeeded. 8 REGISTRATTEMPT Number of SS feature Registration attempts. 9 REGISTRSUCCESS Number of SS feature Registration succeeded. 10 DEREGISTRATTEMPT Number of SS feature de-registration attempts.38 11 DEREGISTRSUCCESS Number of SS feature de-registration succeeded. 12 MIUSSDATTEMPT Number of Mobile Initiated USSD attempts. 13 MIUSSDSUCCESS Number of Mobile USSD succeeded. 14 NIUSSDATTEMPT Number of network Initiated USSD attempts. 15 NIUSSDSUCCESS Number of network Initiated USSD succeeded. 16 RESERVED1 Reserved field 1 for future use 17 RESERVED2 Reserved field 2 for future use 18 RESERVED3 Reserved field 3 for future use 19 RESERVED4 Reserved field 4 for future use


37 This field name has been changed to DEACTIVATIONATTEMPT from DEACTIVATION 38 This field name has been changed to DEREGISTRATIONATTEMPT from DEREGISTRATION


6.8 Circuit Switched Data and Data Interworking Function

6.8.1 IWF Group Information39 (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 Field Name Description

1. STARTTIMESTAMP Beginning time of the performance interval 2. STOPTIMESTAMP Ending time of the performance interval 3. MSFIWFGRPID Facility group (to IWF) to which this record applies. 4. MOBILEORIGATTEMPTS 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.

5. MOBILETERMATTEMPTS Mobile terminated attempts pegged when two circuits to IWF are allocated on IWF trunk.

6. TOTALUSAGESEC Total time in seconds that there are active calls (during this collection interval)40

7. OVERFLOW Number of calls that are denied because of circuit unavailability 8. MINRESOURCEAVAIL Minimum number of idle circuits available during this collection interval 9. MINRESOURCEAVAILVALID Whether the value in field MINRESOURCEAVAIL is a valid value or not41 10. MAXRESOURCEAVAIL Maximum number of idle circuits available during this collection interval 11. RESERVED1 Reserved field 1 for future use 12. RESERVED2 Reserved field 2 for future use 13. RESERVED3 Reserved field 3 for future use 14. RESERVED4 Reserved field 4 for future use 15. RESERVED5 Reserved field 5 for future use 16. RESERVED6 Reserved field 6 for future use 17. RESERVED7 Reserved field 7 for future use 18. RESERVED8 Reserved field 8 for future use 19. RESERVED9 Reserved field 9 for future use 20. RESERVE10 Rerserved field 10 for future use

MSFIWFGRPID is the key field and identifies the facility group to the IWF to which this record applies.

39 Previously Added Performance Group 40 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.


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 NODEID IWF Node/Rack ID to which this record applies. 4 SMIMID SMIM to which this record applies. 5 MOMODEMCALLS Number of Mobile Originated Modem Calls. Pegged when

XCONNREQTX is sent to the SMIM. 6 MTMODEMCALLS Number of Mobile Terminated Modem Calls. Pegged when

XCONNREQTX is sent to the SMIM. 7 MODIGITALCALLS Number of Mobile Originated Digital Calls. Pegged when XCONNREQTX

is sent to the SMIM. 8 MTDIGITALCALLS Number of Mobile Terminated Digital Calls. Pegged when XCONNREQTX

is sent to the SMIM. 9 MOFAXCALLS Number of Mobile Originated Fax Calls. Pegged when XCONNREQTX is

sent to the SMIM. 10 MTFAXCALLS Number of Mobile Terminated Fax Calls. Pegged when XCONNREQTX is

sent to the SMIM. 11 XCONNREQTX 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.

12 CONNRELTX Number of Connection Release messages transmitted from WSS to SMIM

13 CONNACKRX Number of Connection Acknowledgement messages or Connection Release Acknowledgement messages received by WSS from SMIM

14 CONNFCDRELRX Number of Forced Connection Release messages received by WSS from SMIM

15 FCDRESTTX Number of Forced Restart messages transmitted from WSS to SMIM 16 IWERRACKTX Number of Acknowledgement messages for IWF Error appearance and

disappearance transmitted by WSS to SMIM 17 IWCONNERRRX Number of IWF Connection Error messages received by WSS from SMIM 18 IWERRORRX Number of IWF Error appearance and disappearance messages received

by WSS from SMIM 19 READALARMSTATUSTX Number of Read Alarm Status messages transmitted by WSS to SMIM 20 ALARMREPORTRX Number of Alarm Report messages received by WSS from SMIM 21 ALARMREPORTACKTX Number of Alarm Report Acknowledgement messages transmitted by

WSS to SMIM 22 IWASRQTX Number of All IWF Alarm States request (after the restart of WSS)

messages transmitted by WSS to SMIM 23 IWASRSPRX Number of All IWF Alarm States Response messages received by WSS

from SMIM 24 RESETOBCCALCTX Number of Clock and Alarm On-Board-Controller Reset messages

transmitted by WSS to SMIM 25 RESETOBCMIWXTX Number of Mobile Interworking Unit Version X (MIWX) On-Board-

Controller Reset messages transmitted by WSS to SMIM 26 SENDRJATX Number of block and unblock messages to SMIM to prevent seizure from

the switch. 27 CHGOCCSTATETX Number of Change OBC Channel Controller (OCC) State messages

transmitted by WSS to SMIM


Position Field Name Description 28 XSYSPARMTX Number of System Parameter/Configuration messages transmitted by

WSS to SMIM 29 LOADBIDRX Number of Fast Test on MIWX (Load Bid) messages received by WSS

from SMIM. This is just an information for WSS 30 OCCSTRSPRX Number of OBC Channel Controller (OCC) State Change Response

messages received by WSS from SMIM 31 RESTARTINDRX Number of Autonomous Restart on MIWX Indication messages received

by WSS from SMIM 32 CMMREQRX Number of Change of Channel Coding due to negotiation of end-to-end

connection messages received by WSS from SMIM 33 CMMCONFTX Number of Acknowledgment to Change of Channel Coding due to

negotiation of end-to-end connection messages transmitted by WSS to SMIM

34 UPDNOTCHTX Number of Update of the number of real Traffic Channels used messages transmitted by WSS to SMIM


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


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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 ENDOFCALLCAUSEVALUE Internal Call Disposition Code or Cause Code to end a call 5 ENDOFCALLCATEGORY Not used 6 ENDOFCALLCOUNTER 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 Category Description 129 ~ 134 To be provided in a future update 135 ~ 139 To be provided in a future update 200 ~ 249 To be provided in a future update 250 ~ 299 To be provided in a future update 300 ~ 328 To be provided in a future update 329 ~ 340 To be provided in a future update 341 ~ 349 To be provided in a future update 350 ~ 399 To be provided in a future update 400 ~ 449 To be provided in a future update 450 ~ 499 To be provided in a future update 500 ~ 569 To be provided in a future update 750 ~ 770 To be provided in a future update 800 ~ 824 To be provided in a future update 825 ~ 859 To be provided in a future update 861 ~ 989 To be provided in a future update 990 ~ 999 To be provided in a future update

Detailed reference for each cuase, refer to Technical Requirements Specification – External Cuase /Internal Code Mapping, 3BL76757AAAADSZZA


6.10 Call Total Time Performance Information (CALLTOTALTIMEPERF) Performance Group Name: CALLTOTALTIMEPERF File Naming Convention: CALLTOTALTIMEPERF.YYMMDD-HHMM

Position Field name Description 1. STARTTIMESTAMP Beginning time of the performance interval 2. STOPTIMESTAMP Ending time of the performance interval 3. WSSNODENUM WSS Node (CCM Card) to which this record applies.

4. TOTALCALLTIMELANDTOLAND 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.

5. TOTALCALLTIMEMOBILETOLAND 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.

6. TOTALCALLTIMELANDTOMOBILE 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.

7. TOTALCALLTIMEMOBILETOMOBILE 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.

WSSNODENUM IS the key fields.


7 IN RELATED INFORMATION

7.1 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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 SERVICEKEY The service key 5 DEFAULTHANDLINGCALLS Number of calls for which default handling was applied 6 INITDP2 Number of InitialDP2 attempts 7 INITDP3 Number of IntialDP3 attempts 8 INITDP12 Number of IntialDP12 attempts 9 RESERVED1 Reserved field 1 for future use 10 RESERVED2 Reserved field 2 for future use 11 RESERVED3 Reserved field 3 for future use 12 RESERVED4 Reserved field 4 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. 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.


7.2 CAMEL Information (CAPPERF) 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 Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 SERVICEKEY The service key 5 CAPSUCCINITDPREQ Number of successful Initial DP requests (when Continue,

ContinueWithArg, Connect, or ETC is received from SCP in response to Initial DP)

6 CAPNUMETCMSGRX Number of ETC messages received 7 CAPNUMDFLTCAMELHNDLINVKD Number of calls for which default handling was applied 8 INITDP2 Number of Initial DP2 request 9 INITDP3 Number of Initial DP3 request 10 INITDP12 Number of Initial DP12 request 11 INITDPSMS Number of Initial DP SMS request 12 CAPSUCCINITDPSMSREQ Number of successful INIT DP SMS Requests 13 RESERVED1 Reserved field 1 for future use 14 RESERVED2 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.


8 REGULATORY SERVICES INFORMATION

8.1 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 Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 WPSATTMOCALLS [R-158] Total Number of WPS call attempts 5 WPSRADSUCCMOCALLS [O-18] Total Number of WPS call attempts with a radio traffic channel

assigned 6 GETSATTMOCALLS [R-159] Total Number of GETS call attempts 7 PCATTLTOMSCALLS [R-160] Total Number of NS/EP calls received on inc trunks w/ MSC’s

MSRN 8 PCATTNOPRECCALLS [R-160] Total Number of incoming NS/EP calls received w/o the

precedence 9 PCATTINCLCALLS [R-168] Total Number of NS/EP calls received on incoming trunks 10 PCATTTOMSCALLS [R-160] Total Number of NS/EP calls terminated in this MSC 11 PCRADSUCCMTCALLS [O-21] Total Number of incoming NS/EP calls received with a radio traffic

channel assigned 12 WPSATTTOLCALL [R-161] Total Number of WPS calls that require an outgoing trunk 13 PCATTLTOLCALL [R-168] Total Number of NS/EP calls that require an outgoing trunk 14 PCSUCCTOLCALL [R-161] Total Number of NS/EP calls with successful trunk set up 15 PCATTNOCKT [R-161] Total Number of NS/EP calls with no outgoing trunk circuit

available 16 PCSUCCIXCCALLS [R-161] Total Number of NS/EP calls with successful trunk set up to an

IXC 17 PCNOIXCCKTCALLS [R-161] Total Number of NS/EP calls with no outgoing trunk circuit

available to an IXC 18 PCATTLQDCALLS [R-169] Total Number of NS/EP calls queued for a outgoing trunk 19

PCATTLQDOFLOWCALLS [R-169] Total Number of NS/EP calls failed to queue for an outgoing trunk

20 PCATTLQTOUTCALLS [R-169] Total Number of NS/EP calls removed from a queue due to timeout

21 PCATTLQABANCALLS [R-169] Total Number of NS/EP calls removed from a queue due to user abandon



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.


8.2 Emergency Call (E911) Information (EMERGENCYCALLPERF) Performance Group Name: EMERGENCYCALLPERF File Naming Convention: EMERGENCYCALLPERF.YYMMDD-HHMM Number of records: Equals the number of active CCM cards provisioned in the system. Position

Field Name Description

1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 PHASE0ATTEMPTS Number of Emergency Call Attempts using Phase 0 5 PHASE0FALLBACK Number of Fallbacks to Phase 0 6 PHASE1ATTEMPTS Number of Emergency Call Attempts using Phase 1 7 PHASE1FALLBACK Number of Fallbacks to Phase 0 from Phase 1 8 PHASE2ATTEMPTS Number of Emergency Call Attempts using Phase 2 9 PHASE2FALLBACK Number of Fallbacks to Phase 0 from Phase 2 10 ATTINAPQUERY Number of INAP queries attempted to obtain ESRK 11 SUCCINAPQWCONTINUE Number of successful INAP queries with CONTINUE to

obtain ESRK. Note that by default this does not return ESRK.42

12 SUCCINAPQWCONNECTWESRK Number of successful INAP queries with CONNECT to obtain ESRK. This is the count where CONNECT contains ESRK.43

13 INAPESRKNOTIFICATIONS Number of INAP queries to inform GMLC what ESRK was used

14 SUCCINAPQWCONNECTWOESRK Number of successful INAP queries with connect to obtain ESRK. This is the count where CONNECT does NOT contain ESRK44



42 The name has been changed from SUCCINAPQUERIESWCONTINUE to SUCCINAPQWCONTINUE due to ling name error in parser 43 The name has been changed from SUCCINAPQUERIESWCONNECT to SUCCINAPQWCONNECTWESRK due to ling name error in parser 44 This field replaces the Reserved1 field.


8.3 Emergency Routing Key (ESRK) Information (ESRKPOOLPERF) Performance Group Name: ESRKPOOLPERF File Naming Convention: ESRKPOOLPERF.YYMMDD-HHMM Number of records: Equals the number of emergency zones. Position Field Name Description

1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 ESZID Emergency Services Zone ID 4 ESRKPOOL1IDLE Number of ESRK Numbers that are available in 1st ESRK pool. 5 ESRKPOOL1ALLOCATED Number of ESRK Numbers that are allocated from 1st ESRK pool. 6 ESRKPOOL2IDLE Number of ESRK Numbers that are available in 2nd ESRK pool. 7 ESRKPOOL2ALLOCATED Number of ESRK Numbers that are allocated from 2nd ESRK pool. 8 ESRKPOOL3IDLE Number of ESRK Numbers that are available in 3rd ESRK pool. 9 ESRKPOOL3ALLOCATED Number of ESRK Numbers that are allocated from 3rd ESRK pool. 10 ESRKALLOCFAILURE Number of times system failed to allocate ESRK Number. 11 RESERVED1 Reserved field 1 for future use 12 RESERVED2 Reserved field 2 for future use 13 RESERVED3 Reserved field 3 for future use 14 RESERVED4 Reserved field 4 for future use 15 RESERVED5 Reserved field 5 for future use 16 RESERVED6 Reserved field 6 for future use 17 RESERVED7 Reserved field 7 for future use 18 RESERVED8 Reserved field 8 for future use 19 RESERVED9 Reserved field 9 for future use 20 RESERVED10 Reserved field 10 for future use

ESZID is the key field. Emergency zones are configured on the EMS.


9 FACILITIES PERFORMANCE DATA

9.1 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 Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 ROUTEINDEX Route index. 4 CALLSROUTED Number of calls attempted for routing. This also includes priority call

attempts.

5 NOCIRCUITAVAIL 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.

6 CALLSQUEUED [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.

7 CALLSQUEUEDABANDON [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.

8 CALLSQUEUEDSUCCESS [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.

9 PRIORCALLATT [R-168] Total number of NS/EP calls that require an outgoing trunk. It is a subset of CALLROUTED.

10 PRIORCALLATTQTOUT [R-169] Total number of NS/EP calls removed from a queue due to queue timeout. This is a subset of CALLSQUEUEDABANDON.

11 PRIORCALLATTQOFLOW [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.

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 cross-references. The following represent relationship between counters. SUCCESSFULLYROUTED = CALLSROUTED – NOCIRCUITAVAIL – CALLSQUEUEDABANDON PRIORCALLATT = CALLSQUEUEDSUCCESS + CALLSQUEUEDABANDON + PRIORCALLATTQOFLOW


9.2 System Group Information (SYSGRPPERF) 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 Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 SYSGRPNUM System group number. 4 WMGNODENUM The node number of WMG serving the trunk group (SYSGRPNUM)45 5 NUMBEROFRESOURCES Number of circuits defined (or provisioned) including Out-of-Service in

the trunk group at the end of the recording interval 6 GROUPDIRECTION Indication of whether the trunk group is incoming only, outgoing only or

both ways. 7 INCOMINGATTEMPTS

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.

8 TRANSLATIONERRORS

Number of calls dropped due to number translation errors46 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

9 INCOMINGBLOCKED Number of calls blocked due to calls coming in (the wrong direction) on

a trunk that is designated for outgoing only47. Applicable to both IMT and access trunks, however, the value should be nil for access trunks since they are bidirectional.

10 INCOMINGCONGESTION Number of incoming calls dropped due to internal (local) system congestion48 occurred on either access or IMT trunks.

11 ROUTINGFAILURE

Number of incoming calls that has successfully passed translation but dropped due to routing errors49, 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 (non–selected user clearing), 27 (destination out of order), 34 (no circuit/channel available), and 44 (requested channel/circuit not available).

45 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.


12 SYSTEMERRORSINCOMING

Number of incoming calls dropped due to system errors on the incoming side50, applicable to access and IMT trunks. Pegged when assignment failure occurs, prepaid timer expires, unexpected message recv’d from term side, invalid internal response from message etc. It will also peg locally generated temporary failure, cause code 41.

13 PROTOCOLERRORSINCOMING Number of calls dropped due to unspecified protocol errors on the

incoming side51, applicable to both access and IMT trunks. Pegged when incoming message has unsupported bearer, invalid mandatory info, or mandatory IE missing.

14 INCOMINGCOMPLETION Total number of valid incoming call attempts52 derived counter as explained in footnote. This counter was previously called as INCOMINGVALIDATTEMPTS

15 OUTGOINGATTEMPTS 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.

16 SIGFAILURES 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.

17 OVERFLOWS 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.

18 OVERFLOWSEC Number of seconds that the group had all resources (circuit) busy 19 MINRESOURCEAVAIL

Minimum number of resources available during the measurement interval. This represents the heaviest traffic point in the measurement interval.

20 MINRESOURCEAVAILVALID This field indicates whether the minimum number of resources available field is valid or default 0.

21 MAXRESOURCEAVAIL Maximum number of circuits available during the measurement interval. This represents lowest traffic point in the measurement interval.

22 OOSSEC Total number of seconds all the resources spent in the out of service state.

23 OUTGOINGGLARE 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.

24 OUTGOINGCONGESTION Number of calls failed due to outgoing congestion53, applicable to both access and IMT trunks

25 SYSTEMERRORSOUTGOING

Number of calls dropped due to system errors on the outgoing side54. 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.

50 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 switch’s 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.


26 PROTOCOLERRORSOUTGOING Number of calls dropped due to unspecified protocol errors on the outgoing side55

27 OUTGOINGNOTANSWERED

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.

28 OUTGOINGANSWERED Number of outgoing call attempts that were answered. This counter was previously called as OUTGOINGCOMPLETION

29 INCOMINGABANDONED 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.

30 INCOMINGANSWERED Number of Incoming call attempts that were completed. This counter was previously called as INCOMINGCOMPLETION

31 INCOMINGTERMSS7 Number of incoming call attempts56 that terminated on a local ISUP trunk.

32 INCOMINGTERMBSS Number of incoming call attempts that terminated on a local BSS trunk. 33 INCOMINGTERMCASTRK Number of incoming call attempts that terminated on a local CAS trunk. 34 PRIORITYCALLATT [R-168] Total number of NS/EP calls that require an outgoing trunk.

35 MAXRESOURCEOCCUPIED Maximum number of channels with active calls57 during the

measurement interval. This should be equal to (INSERVICERESOURCES – MINRESOURCEAVAIL).

36 INCOMINGUSAGESEC 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.

37 OUTGOINGUSAGESEC 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.

38 ORIGMSHANDOVER Previous Reserved field 1 was used: Total number of circuits used due to originating MS got handed over 58. 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 inter-MSC handover.

39 TERMMSHANDOVER Previous Reserved field 2 was used: Total number of circuits used due to terminating MS got handed over59. 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 inter-MSC handover.

40 INSERVICERESOURCES Previous Reserved field 3 was used: Total number of resources/circuits in service.

55 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 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.


41 INCOMINGREJECTED 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).

42 OUTGOINGREJECTED

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.

43 INCOMINGNOTANSWERED

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.

44 OUTGOINGABANDONED 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.

45 OUTGOINGCOMPLETION

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 )

46 INCOMINGORLATECFW Number of incoming Optimal Routing Late Call Forward allowed in GMSC.

47 OUTGOINGORLATECFW Number of outgoing Optimal Routing Late Call Forward allowed in VMSC.

48 Reserved1 Reserved field 1 for future use 49 Reserved2 Reserved field 2 for future use 50 Reserved3 Reserved field 3 for future use 51 Reserved4 Reserved field 4 for future use 52 Reserved5 Reserved field 5 for future use 53 Reserved6 Reserved field 6 for future use 54 Reserved7 Reserved field 7 for future use 55 Reserved8 Reserved field 8 for future use 56 Reserved9 Reserved field 9 for future use 57 Reserved10 Reserved field 10 for future use 58 GROUPNAME The name for this system group60 59 WMGNODENAME The node name of WMG serving the trunk group (SYSGRPNUM)61

SysGrpNum is the key field, and identifies the trunk group to which this record applies.

60 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.


9.3 TDM Echo Cancellation DSP usage ( DSPUSAGEPERF) 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 Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 MSFNODEID WMG (media gateway) Node Number to which this record

applies. 4 DSPPOOLTYPE DSP Pool Type to which this record applies. 5 MSFTDMSYSDSPCHANNELS Number of DSP channels in this DSP Pool (including out-

of-service channels.) 6 MSFTDMSYSDSPALLOCCHANNELS Number of allocated DSP channels in this DSP Pool. 7 MSFTDMSYSDSPFREECHANNELS Number of available (and in-service) DSP channels in this

DSP Pool 8 MSFTDMSYSDSPMAXALLOCCHANNELS Maximum number of DSP channels allocated in this DSP

Pool since this counter was last reset.62 9 MSFTDMSYSDSPSUCCALLOCREQUESTS The number of DSP channel allocation requests that were

successful. 10 MSFTDMSYSDSPUNSUCCALLOCREQS The number of DSP channel allocation requests that were

unsuccessful (as there were no available DSP channels).

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. 62 Please note that this counter indicates the maximum DSP allocation since the start of system and NOT for the measurement period in minutes.


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


9.4 TDM Interconnect Information (ICONCARDPERF) Performance Group Name: ICONCARDPERF File Naming Convention: ICONCARDPERF.YYMMDD-HHMM Number of records: Equals the number of Interconnect IDs provisioned in the system.

Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 ICONID Interconnect ID on the WMG to which this record applies. 4 GATEWAYNODE1ATTEMPTS Number of Call attempts coming from Gateway Node - 1.63 5 GATEWAYNODE2ATTEMPTS Number of Call attempts coming from Gateway Node -2.64 6 TOTALUSAGESEC Total time in seconds that there are active calls 7 OVERFLOW Number of calls that are turned away when there are no circuits

available 8 OVERFLOWSEC Total time in seconds when all trunks are busy and no circuit is

available to allocate 9 MINRESOURCEAVAIL Minimum number of resources available 10 MINRESOURCEAVAILVALID This a flag that indicates whether the value in the above field

MINRESOURCEAVAIL is a valid value or not 11 MAXRESOURCEAVAIL Maximum number of idle circuits available observed 12 INSERVICERESOURCES Total Number of resources/circuits in service. 13 WMGNODE1ID The Node ID of the first WMG having lowest WMG ID. 14 WMGNODE2ID The Node ID of the second WMG having highest WMG ID. 15 RESERVED1 Reserved field 1 for future use 16 RESERVED2 Reserved field 2 for future use 17 RESERVED3 Reserved field 3 for future use 18 RESERVED4 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 A GATEWAYNODE-1 is the node that has the lowest node ID in that Interconnect. 64 A GATEWAYNODE-2 is the node that has the highest node ID in that Interconnect.


9.5 TRUNKGROUP and WMG Interconnect Information (TRKGRPWMGICONPERF) 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 Field Name Description 1 STARTTIMESTAMP Date and time performance interval started. 2 STOPTIMESTAMP Date and time performance interval stopped. 3 SYSGRPNUM System group number or Trunk Group ID. 4 WMGID The node number of WMG serving this Trunk Group ID

(SYSGRPNUM) 5 INCOMINGATTEMPTS Number of Call attempts coming towards this WMG ID (key field

in this record) from this Trunk Group ID (key field in this record)

6 OUTGOINGATTEMPTSTOOTHERTRKGS 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)

7 OUTGOINGATTEMPTSTOICONS 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.

8 INCOMINGATTEMPTSUSAGESEC 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)

9 OUTATTTOOTHERTRKGSUSAGESEC 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)

10 OUTATTTOICONSUSAGESEC 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.

11 INDROPNORESAVAILONOUTTRKGS 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).

12 INDROPNORESAVAILONOUTICONS 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.

13 OUTGOINGATTEMPTS Number of Call attempts going out through this trunk group of this WMG ID.

14 INCOMINGATTFROMOTHERTRKGS Number of Call attempts going to this Trunk Group ID from other Trunk Groups through this WMG ID

15 INCOMINGATTEMPTSFROMICONS Total number of Call attempts going to this Trunk Group ID from all Interconnects through this WMG ID

16 OUTATTUSAGESEC Outgoing usage seconds for call attempts going out of this WMG ID to this Trunk Group

17 INATTFROMOTHERTRKGSUSAGESEC Usage seconds for call attempts going this Trunk Group ID from all other Trunk Groups through this WMG ID

18 INATTFROMICONSUSAGESEC Usage seconds for call attempts going to this Trunk Group ID from all Interconnects through this WMG ID

19 OUTDROPNORESOURCEAVAILONIN Number of calls dropped (not overflows to other trunk groups) due to no resources available on this Trunk Group

20 WMGIDONE The ID of the WMG for which the next two fields are applicable 21 WMGIDONEOUTGOINGATTEMPTSICON Number of calls going from WMGID (key field in this record) to

the WMGIDONE 22 WMGIDONEINCOMINGATTEMPTSICON Number of calls coming from WMGIDONE to WMGID (key field

in this record)


23 WMGIDTWO The ID of the WMG for which the next two fields are applicable 24 WMGIDTWOOUTGOINGATTEMPTSICON Number of calls going from WMGID (key field in this record) to

the WMGIDTWO 25 WMGIDTWOINCOMINGATTEMPTSICON Number of calls coming from WMGIDTWO to WMGID (key field

in this record) 26 WMGIDTHREE The ID of the WMG for which the next two fields are applicable 27 WMGIDTHREEOUTGOINGATTEMPTSICON Number of calls going from this WMGID (key field in this record) to the WMGIDTHREE 28 WMGIDTHREEINCOMINGATTEMPTSICON Number of calls coming from WMGIDTHREE to this WMGID (key field in this record) 29 WMGIDFOUR The ID of the WMG for which the next two fields are applicable 30 WMGIDFOUROUTGOINGATTEMPTSICON Number of calls going from this WMGID (key field in this record) to the WMGIDFOUR 31 WMGIDFOURINCOMINGATTEMPTSICON Number of calls coming from WMGIDFOUR to WMGID (key

field in this record) 32 OUTATTFROMSAMETRKGRP Formerly Reserved Field – 1. The number of calls that came in

on this trunk and left out on the same trunk. 33 OUTATTFROMSAMETRKGRPUSAGESEC Reserved Field – 2 Usage seconds for calls that came in on this

trunk and left out on the same trunk. 34 Reserved3 Reserved Field – 3 for future use 35 Reserved4 Reserved Field – 4 for future use 36 Reserved5 Reserved Field – 5 for future use 37 Reserved6 Reserved Field – 6 for future use 38 Reserved7 Reserved Field – 7 for future use 39 Reserved8 Reserved Field – 8 for future use 40 Reserved9 Reserved Field – 9 for future use 41 Reserved10 Reserved Field – 10 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.


Balancing Incoming Attempts of a Trunk Group on a WMG

WMG 1 WMG 2

WMG 3WMG 4

Other TrunkGroups

6

24

30 27

Trunk Group # 76

5

7 24 27 30

6 75 11 12

8

9

9 108

===

+++

+++

+

32

+ 32

33

33 Usage seconds

Figure 1Note: The numbers in the circle corresponds to entry (column) number in the table

Balancing Outgoing Attempts of a Trunk Group on a WMG

WMG 1 WMG 2

WMG 3WMG 4

Other TrunkGroups

14

25

31 28Trunk Group # 76

13

15 25 28 31

1413

16

17

17 1816

===

+++

+++ Usage seconds

15 32

32

33

33

Figure 2.Note: The numbers in the circle corresponds to entry (column) number in the table


9.6 Port Capacity Performance Group ( PORTCAPACITYPERF) Performance Group Name: PORTCAPACITYPERF File Naming Convention: PORTCAPACITYPERF.YYMMDD-HHMM Number of records: Equals the number of cards on all WMG Nodes. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval B WMGNODEID WMG (media gateway) Node Number to which this record applies. 4 SLOTID WMG Slot ID to which this record applies 5 CARDID WMG Card ID to which this record applies 6 CARDTYPE WMG Card Type ((TDM Channelized Interface T1, T3, OC-3, or ATM) 7 PORTCAPACITY Number of ports (DS0) available in the slot or card i.e. Port capacity of the

card 8 CARDSTATUS The status of the card whether locked or unlocked 9 RESERVED1 Reserved Field – 1 for future use 10 RESERVED2 Reserved Field – 2 for future use 11 RESERVED3 Reserved Field – 3 for future use 12 RESERVED4 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 slot–wide 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

Card Type

# of daughter ports

# of port per card or slot

Capacity per daughter port

(DS0s) Capacity per Card or slot (DS0)

OC12_CHAN_INTERFACE = 16, 1

1

24192 24192

4 port OC3_CHAN_INTERFACE = 56, 4 4 2016 8064 2 port OC3_CHAN_INTERFACE = 15, 2 2 2016 4032


E3_CHAN_INTERFACE = 14, 1 ** 268 2688 T3_CHAN_INTERFACE = 13, 2 6 2016 4032 E1_CHAN_INTERFACE = 12, 1 60 1920 1920 T1_CHAN_INTERFACE = 11, 1 60 1440 1440 STM4_CHAN_INTERFACE = 22, [OC-12]

1 48064 32256

STM1_CHAN_INTERFACE = 21, [OC-3] 1 4 2016 8064


9.7 Summary of CDR statistics ( CDRSUMMARYPERF) DEFFERED IMPLEMENTATION TO REL 4 Performance Group Name: CDRSUMMARYPERF File Naming Convention: CDRSUMMARYPERF.YYMMDD-HHMM Number of records: Equals the number of Cause for Termination of a call. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 CAUSEFORTERMINATION Cause for Termination of a call to which this record applies. 4 COUNT The number of occurrences of cause for termination. 5 RESERVED1 Reserved Field – 1 for future use 6 RESERVED2 Reserved Field – 2 for future use 7 RESERVED3 Reserved Field – 3 for future use 8 RESERVED4 Reserved Field – 4 for future use

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. Cause For Termination is an 8-bit field that can assume the following values: 8 7 6 5 4 3 2 1 Cause for Termination 0 0 0 0 0 0 0 0 Normal Release 0 0 0 0 0 0 0 1 Partial Record 0 0 0 0 0 0 1 0 RESERVED FOR FUTURE USE 0 0 0 0 0 0 1 1 Unsuccessful Call Attempt 0 0 0 0 0 1 0 0 Stable Call, Abnormal Termination 0 0 0 0 0 1 0 1 CAMEL Initiated Call Release 0 0 0 0 0 1 1 0 RESERVED FOR FUTURE USE thru RESERVED FOR FUTURE USE 0 0 0 0 1 1 1 1 RESERVED FOR FUTURE USE 0 0 0 1 0 0 0 0 Call Release Initiated by Long-Duration Call Timer 0 0 0 1 0 0 0 1 RESERVED FOR FUTURE USE thru RESERVED FOR FUTURE USE 1 1 1 1 1 1 1 1 RESERVED FOR FUTURE USE


10 CONFIGURATION DATA

10.1 Trunk Group Information ( TRKGP_WMG_RELATIONSHIP) 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 Field Name Description 1 SYSGRPNUM Trunk Group ID. 2 WMGID The ID of the WMG associated with Trunk Group. 3 SYSGRPNAME The name of the Trunk Group

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.


10.2 WMG Information65( WMG_ID_NAME_RELATIONSHIP) 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 Field Name Description 1 WMGID The ID of the WMG associated with Trunk Group. 2 WMGNAME The name of the WMG.

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


10.3 Interconnect Information66( ICON_WMG_RELATIONSHIP) 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 Field Name Description 1 ICONID The ID of the WMG associated with Trunk Group. 2 WMG1ID The ID of the WMG-1 associated with the Interconnect. 3 WMG2ID The ID of the WMG-2 associated with the Interconnect. 4 ICONNAME The name of the Interconnect.

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


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 Field Name Description 1 LINKID The SS7 Link id 2 LINKSETID The Linkset id to which the link belongs. 3 DPC The DPC number 4 DPCNAME The assigned string name for DPC

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


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 Field Name Description

1. STARTTIMESTAMP Date and time performance interval started 2. STOPTIMESTAMP Date and time performance interval stopped 3. WSSNODENUM WSS Node (IPM card) to which this record applies 4. ACCESSPOINT0 Access Point to which the record applies (MSB – 2 bytes

bytes in binary format right to left) 5. ACCESSPOINT1 Access Point to which the record applies (LSB – 4 bytes in

binary format right to left) 6. DISREQUESTRX Number of URR Discovery requests received 7. DISACCEPTTX Number of URR Discovery Accept sent 8. DISREJECTINATX Number of URR Discovery Reject sent (IMSI not allowed) 9. DISREJECTNCTX Number of URR Discovery Reject sent (Network

congestion) 10. DISREJECTUNSPECTX Number of URR Discovery Reject sent (Unspecified) 11. REGREQUESTRX Number of URR Registration requests received 12. REGACCEPTTX Number of URR Registration Accept messages sent 13. REGREJECTANATX Number of URR Registration Reject sent (AP not allowed) 14. REGREJECTNCTX Number of URR Registration Reject sent (Network

congestion) 15. REGREJECTINATX Number of URR Registration Reject sent (IMSI not allowed) 16. REGREJECTLNATX Number of URR Registration Reject sent (Location not

allowed)


Position Field Name Description 17. REGREJECTIUTX Number of URR Registration Reject sent (Invalid UNC) 18. REGREJECTGLNKTX Number of URR Registration Reject sent (Geo location not

known) 19. REGREJECTUNSPECTX Number of URR Registration Reject sent (Unspecified) 20. REGREDIRECTTX Number of URR Registration Redirect sent 21. DEREGTX Number of URR Deregister sent 22. DEREGRX Number of URR Deregister received 23. REGUPDULRX Number of URR Register Update Uplink received 24. REGUPDDLTX Number of URR Register Update Downlink messages sent 25. KEEPALIVERX Number of URR Keep Alive received 26. CURRTCPCONN Current TCP connections. This is the number of

connections at the end of the poll interval 27. PEAKTCPCONN Peak number of TCP connections 28. TCPCONNREJ Number of TCP connections rejected because max

allowable number reached. 29. OTHERTX Number of times any other URR message sent 30. OTHERRX Number of times any other URR message received 31. CURRUSERS Current number of users per node. This does not include

RJ-11 subscribers. 32. CURRACCPTS

Current number of Access Points per node. This does not include RJ-11 router that has at least one RJ-11 subscriber.

33. * CONNREJECTOVLD Total connections rejected due to overload 34. * UMAMOREJCMOVLD UMA Mobile Origination calls rejected by URRCM due to

IPM overload. 35. * UMAMOREJDDFOVLD

UMA Mobile Origination calls rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs.

36. * UMALUPREJCMOVLD UMA Location update rejected by URRCM due to IPM overload.

37. * UMALUPREJDDFOVLD UMA Location update rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs.

38. RESERVE1 Reserved Field 1 for future use 39. RESERVE2 Reserved Field 2 for future use 40. RESERVE3 Reserved Field 3 for future use 41. RESERVE4 Reserved Field 4 for future use

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


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 Field Name Description

1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (IPM card) to which this record applies 4 ACCESSPOINT0 Access Point to which the record applies (MSB – 2 bytes bytes in

binary format left to right) 5 ACCESSPOINT1 Access Point to which the record applies (LSB – 4 bytes in binary

format left to right) 6 CURRRJ11USERSNATIONAL Current number of RJ-11 national subscribers registered with the

UNC. This statistics is per node.

7 CURRRJ11USERSINTERNATIONAL Current number of RJ-11 international subscribers registered with the UNC. This statistics is per node. To be implemented in future release (RDS10610). Currently, it will show zero value.

8 CURRRJ11ACCPTSNATIONAL 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.

9 CURRRJ11ACCPTSINTERNATIONAL

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.

10 DISREQUESTRX Number of URR Discovery requests messages received from RJ11 sub

11 DISACCEPTTX Number of URR Discovery Accept messages sent to RJ11 sub

12 DISREJECTINATX Number of URR Discovery Reject messages sent (IMSI not allowed) to RJ11 sub

13 DISREJECTNCTX Number of URR Discovery Reject messages sent (Network congestion) to RJ11 sub

14 DISREJECTUNSPECTX Number of URR Discovery Reject messages sent (Unspecified) to RJ11 sub

15 REGREQUESTRX Number of URR Registration Requests messages received for RJ11 user

16 REGACCEPTTX Number of URR Registration Accept messages sent for RJ11 user 17 REGREJECTANATX Number of URR Registration Reject messages sent (AP not

allowed) for RJ11 user 18 REGREJECTNCTX Number of URR Registration Reject messages sent (Network

congestion) for RJ11 user 19 REGREJECTINATX Number of URR Registration Reject messages sent (IMSI not

allowed) for RJ11 user 20 REGREJECTLNATX Number of URR Registration Reject messages sent (Location not

allowed) for RJ11 user 21 REGREJECTIUTX Number of URR Registration Reject messages sent (Invalid UNC)

for RJ11 user 22 REGREJECTGLNKTX Number of URR Registration Reject messages sent (Geo location

not known) for RJ11 user 23 REGREJECTUNSPECTX Number of URR Registration Reject messages sent (Unspecified)


Position Field Name Description for RJ11 user

24 REGREDIRECTTX Number of URR Registration Redirect messages sent in response to URR Reg request for RJ11 user

25 DEREGTX Number of URR Deregister messages sent because of network initiated de-registration for RJ11 user.

26 DEREGRX Number of URR Deregister messages received for RJ11 user. 27 REGUPDULRX Number of URR Register Update Uplink messages received for

RJ11 user

28 REGUPDDLTX Number of URR Register Update Downlink messages sent for RJ11 user

29 KEEPALIVERX Number of URR Keep Alive messages received from MS for RJ11 user.

30 OTHERTX Number of times any other URR message sent to RJ11 user 31 OTHERRX Number of times any other URR message received to RJ11 user

32 UMAMOREJCMOVLD UMA Mobile Origination calls rejected by URRCM due to IPM overload.

33 UMALUPREJCMOVLD UMA Location update rejected by URRCM due to IPM overload. 34 UMAMOREJDDFOVLD UMA Mobile Origination calls rejected due to system, DDM, CCM

overload. Note URRCM overload will not peg DDM overload pegs.

35 UMALUPREJDDFOVLD UMA Location update rejected due to system, DDM, CCM overload. Note URRCM overload will not peg DDM overload pegs.

36 REGUPDREDIRECTTX 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.

37 REGUPDREJECTANATX 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.

38 REGUPDREJECTNCTX

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.

39 REGUPDREJECTINATX

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.

40 REGUPDREJECTLNATX

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.

41 REGUPDREJECTUNSPECTX

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.

42 REGUPDREJECTGLNKTX Number of URR Deregister messages with reject cause of "Geo


Position Field Name 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.

43 REGUPDREJECTIUTX 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.

44 ORIGCALLATT 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.

45 ORIGCALLSUCC Number of RJ11 originating call successes. Pegged when “Activate Channel” message is sent to the RJ11 user.

46 ORIGEMERGNCYCALLATT Number of RJ11 originating emergency call attempts. Pegged when UNC receives a Request message from RJ11 user with establishment cause code of emergency call

47 ORIGEMERGNCYCALLSUCC Number of RJ11 originating emergency call successes. Pegged when UNC sends an “Activate Channel” message to RJ11 user for emergency call.

48 LOCUPDATT

Number of location update attempts received from RJ11 user. Pegged when UNC receives a Request message for Location update from RJ11 user.

49 PAGINGATT Number of RJ11 paging attempts. Pegged when UNC sends a Paging Request message to RJ11.

50 PAGINGSUCC

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.

51 TERMCALLSUCC

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.

52 RESERVED1 53 RESERVED2 54 RESERVED3 55 RESERVED4 56 RESERVED5


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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (CCM card) to which this record applies 4 REQUESTRX Number of URR Request messages received 5 REQUESTACCEPTTX Number of URR Request Accept sent 6 REQUESTREJECTTX Number of URR Request Reject sent 7 CIPHMODECMDTX Number of URR Ciphering Mode Command sent 8 CIPHMODECOMPRX Number of URR Ciphering Mode Complete received 9 ACTIVATECHTX Number of URR Activate Channel sent 10 ACTIVATECHACKRX Number of URR Activate Channel Ack received 11 ACTIVATECHFAILRX Number of URR Activate Channel Failure received 12 ACTIVATECHCOMPTX Number of URR Activate Channel Complete sent 13 CHMODEMODIFYTX Number of URR Channel Mode Modify sent 14 CHMODEMODIFYACKRX Number of URR Channel Mode Modify Acknowledge received 15 RELEASETX Number of URR Release sent 16 RELEASECOMPRX Number of URR Release Complete received 17 CLEARREQRX Number of URR Clear Request received 18 HOACCESSRX Number of URR Handover Access received 19 HOCOMPRX Number of URR Handover Complete received 20 HOREQUIREDRX Number of URR Handover Required received 21 HOCOMMANDTX Number of URR Handover Command sent 22 HOFAILURERX Number of URR Handover Failure received 23 PAGINGREQTX Number of URR Paging Request sent 24 PAGINGRESPRX Number of URR Paging Response received 25 UPQUALINDTX Number of URR Uplink Quality Indication sent 26 UPDIRXFERRX Number of URR Uplink Direct Transfer received 27 DOWNDIRXFERTX Number of URR Downlink Direct Transfer sent 28 CLASSMARKENQTX Number of URR Classmark Enquiry sent 29 CLASSMARKCHRX Number of URR Classmark Change received 30 STATUSRX Number of URR Status received 31 SYNCINFORX Number of URR Synchronization received 32 CURRCHANNELS Current number of channels assigned at the end of the poll

interval 33 PEAKCHANNELS Peak number of channels assigned 34 OTHERTX Number of times any other URR message sent 35 OTHERRX Number of times any other URR messaged received 36 RESERVE1 Reserved Field 1 for future use 37 RESERVE2 Reserved Field 2 for future use 38 RESERVE3 Reserved Field 3 for future use 39 RESERVE4 Reserved Field 4 for future use


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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (CCM card) to which this record applies 4 COMPL3INFOTX Number of Complete Layer 3 Information sent 5 ASSIGNREQRX Number of BSSMAP Assignment Request received 6 ASSIGNFAILTX Number of BSSMAP Assignment Failure sent 7 ASSIGNCOMPTX Number of BSSMAP Assignment Complete sent 8 CLEARCMDRX Number of BSSMAP Clear Command received 9 CLEARCOMPTX Number of BSSMAP Clear Complete sent 10 CLEARREQTX Number of BSSMAP Clear Request sent 11 HOREQUESTRX Number of BSSMAP Handover Request received 12 HOREQACKTX Number of BSSMAP Handover Request Acknowledge sent 13 HODETECTTX Number of BSSMAP Handover Detect sent 14 HOCOMPTX Number of BSSMAP Handover Complete sent 15 HOCOMMANDRX Number of BSSMAP Handover Command received 16 HOREQDTX Number of BSSMAP Handover Required sent 17 HOREQDREJRX Number of BSSMAP Handover Required Reject received 18 HOFAILTX Number of BSSMAP Handover Failure sent 19 HOSUCCRX Number of BSSMAP Handover Succeeded received 20 HOPERFORMEDTX Number of BSSMAP Handover Performed sent 21 HOREQTIMEREXP Number of times Handover Request Timer (HOReqTimer)

expired 22 RESETRX Number of BSSMAP Reset received 23 RESETTX Number of BSSMAP Reset sent 24 RESETACKTX Number of BSSMAP Reset Acknowledge sent 25 RESETACKRX Number of BSSMAP Reset Acknowledge received 26 CIPHERMODECMDRX Number of BSSMAP Cipher Mode Command received 27 CIPHERMODECOMPTX Number of BSSMAP Cipher Mode Complete sent 28 CIPHERMODEREJTX Number of BSSMAP Cipher Mode Reject sent 29 DTAPINDTX Number of DTAP Indication sent 30 DTAPREQRX Number of DTAP request received 31 PAGINGRX Number of BSSMAP Paging received 32 MSCINVTRACERX Number of BSSMAP MSC Invoke Trace received 33 BSSINVTRACETX Number of BSSMAP BSS Invoke Trace sent 34 BSSINVTRACERX Number of BSSMAP BSS Invoke Trace received 35 CMUPDTX Number of BSSMAP Classmark Update sent 36 CMUPDRX Number of BSSMAP Classmark Update received 37 CMREQRX Number of BSSMAP Classmark Request received 38 PERFLOCREQRX Number of BSSMAP Perform Location Request received 39 PERFLOCRSPTX Number of BSSMAP Perform Location Response sent


Position Field Name Description 40 PERFLOCABTRX Number of BSSMAP Perform Location Abort received 41 CNLSINFOTX Number of BSSMAP Connectionless Information sent 42 CNLSINFORX Number of BSSMAP Connectionless Information received 43 OTHERTX Number of times any other BSSMAP message sent 44 OTHERRX Number of times any other BSSMAP messaged received 45 * PAGINGREJECTOVLD Paging requests rejected due to overload 46 RESERVE1 Reserved Field 1 for future use 47 RESERVE2 Reserved Field 2 for future use 48 RESERVE3 Reserved Field 3 for future use 49 RESERVE4 Reserved Field 4 for future use WSSNODENUM is the key field, and identifies the node (card) to which this record applies. * added in Rel 3 SP9


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. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (IPM Card) to which this record applies 4 SERCONEST Number of times connection with LDAP Server established. 5 SUBDBQUERIES Number of Subscriber DB queries attempted 6 APDBQUERIES Number of Access Point DB queries attempted 7 CGIDBQUERIES Number of CGI DB queries attempted 8 STDBQUERIES Number of Service Type DB queries attempted 9 ZDBQUERIES Number of Zone DB queries attempted 10 QUERIESSENT Number of queries successfully sent to LDAP Server 11 QUERIESFAILIE Number of queries not sent due to Internal Error 12 QUERIESFAILCB Number of queries not sent because connection to LDAP

Server was broken

13 POLLTIMEDOUT 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

14 DBENTRY Number of times LDAP Interface returned a database entry 15 NODBENTRY Number of times LDAP Interface returned with no match in

the DB for requested search key 16 CONNBROKEN Number of times the LDAP Interface retuned a Connection

broken indication 17 MIDBQUERIES Number of MapInfo DB queries attempted 18 QUERIESTIMEDOUT Total number of queries to the UMA DBs that timed out 19 RESERVE1 Reserved Field 1 for future use 20 RESERVE2 Reserved Field 2 for future use 21 RESERVE3 Reserved Field 3 for future use 22 RESERVE4 Reserved Field 4 for future use WSSNODENUM is the key field, and identifies the node (card) to which this record applies.


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. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 ABRELUNSPEC Number of Abnormal Release, Unspecified 5 ABRELCHUNACC Number of Abnormal Release, Channel Unacceptable 6 ABRELTIMEXP Number of Abnormal Release, Timer Expired 7 ABRELNOACT Number of Abnormal Release, No Activity On Radio Path 8 PREEMPTREL Number of Preemptive Release 9 UTRANCFGUN Number of UTRAN Configuration Unknown 10 HOIMPTOR Number of Handover Impossible, Timing Advance Out Of

Range 11 CHMODEUNACC Number of Channel Mode Unacceptable 12 FREQNOTIMP Number of Frequency Not Implemented 13 OTLGCA Number of Originator Or Talker Leaving Group Call Area 14 LLFAIL Number of Lower Layer Failure 15 CALLAC Number of Call Already Cleared 16 SEMINCMSG Number of Semantically Incorrect Message 17 INVMANINFO Number of Invalid Mandatory Information 18 MTNEORNI Number of Message Type Non-Existent Or Not

Implemented 19 MTNCWIPS Number of Message Type Nor compatible With Protocol

State 20 CONDIEERR Number of Conditional IE Error 21 NOCELLALL Number of No Cell Allocation Available 22 PROTERRUNSPEC Number of Protocol Error Unspecified 23 RESERVE1 Reserved Field 1 for future use 24 RESERVE2 Reserved Field 2 for future use 25 RESERVE3 Reserved Field 3 for future use 26 RESERVE4 Reserved Field 4 for future use WSSNODENUM is the key field, and identifies the node (card) to which this record applies.


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. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 ABRELUNSPEC Number of Abnormal Release, Unspecified 5 ABRELCHUNACC Number of Abnormal Release, Channel Unacceptable 6 ABRELTIMEXP Number of Abnormal Release, Timer Expired 7 ABRELNOACT Number of Abnormal Release, No Activity On Radio Path 8 PREEMPTREL Number of Preemptive Release 9 UTRANCFGUN Number of UTRAN Configuration Unknown 10 HOIMPTOR Number of Handover Impossible, Timing Advance Out Of

Range 11 CHMODEUNACC Number of Channel Mode Unacceptable 12 FREQNOTIMP Number of Frequency Not Implemented 13 OTLGCA Number of Originator Or Talker Leaving Group Call Area 14 LLFAIL Number of Lower Layer Failure 15 CALLAC Number of Call Already Cleared 16 SEMINCMSG Number of Semantically Incorrect Message 17 INVMANINFO Number of Invalid Mandatory Information 18 MTNEORNI Number of Message Type Non-Existent Or Not Implemented 19 MTNCWIPS Number of Message Type Nor compatible With Protocol

State 20 CONDIEERR Number of Conditional IE Error 21 NOCELLALL Number of No Cell Allocation Available 22 PROTERRUNSPEC Number of Protocol Error Unspecified 23 RESERVE1 Reserved Field 1 for future use 24 RESERVE2 Reserved Field 2 for future use 25 RESERVE3 Reserved Field 3 for future use 26 RESERVE4 Reserved Field 4 for future use WSSNODENUM is the key field, and identifies the node (card) to which this record applies.


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. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 RADINFMSGFAIL Number of Radio interface message failure 5 RADNFFAIL Number of Radio interface failure 6 UPLKQUAL Number of Uplink Quality (this cause is received in a

Handover Request) 7 UPLKSTGH Number of Uplink Strength (this cause is received in a

Handover Request) 8 DWLKQUAL Number of Downlink Quality (this cause is received in a

Handover Request) 9 DWLKSTGH Number of Downlink Strength (this cause is received in a

Handover Request) 10 DISTANCE Number of Distance (this cause is received in a Handover

Request) 11 OMINT Number of O And M Intervention (this cause is received in a

Handover Request) 12 RSPMSCINV Number of Response To MSC Invocation (this cause is

received in a Handover Request) 13 CALLCNTL Number of Call Control 14 RIFAILREV Number of Radio Interface Failure, Reversion To Old

Channel 15 HOSUCC Number of Handover Successful 16 BETTERCELL Number of Better Cell (this cause is received in a Handover

Request) 17 DIRRETRY Number of Directed Retry (this cause is received in a

Handover Request) 18 JOINGCC Number of Joined Group Call Channel 19 TRAFFIC Number of Traffic 20 REDLDINSC Number of Reduce Load In Serving Cell (this cause is

received in a Handover Request) 21 TLTCHISC Number of Traffic Load In Target Cell Higher Than In Source

Cell 22 RELTRIG Number of Relocation Triggered 23 EQUIPFAIL Number of Equipment Failure 24 NORADRESAVL Number Of No Radio Resource Available 25 RTRESUNAVL Number of Requested Terrestrial Resource Unavailable 26 CCHOVL Number of CCH Overload 27 PROCOVL Number of Processor Overload 28 BSSNOTEQP Number of BSS Not Equipped 29 MSNOTEQP Number of MS Not Equipped 30 INVCELL Number of Invalid Cell (this cause is received in a Handover

Request) 31 TRAFFICLOAD Number of Traffic Load (this cause is received in a Handover

Request) 32 PREEMPTION Number of Preemption


Position Field Name Description 33 RETRRAUVL Number Of Requested Transcoding/Rate Adaptation

Unavailable 34 CPMISMATCH Number Of Circuit Pool Mismatch 35 SCPOOL Number of Switched Circuit Pool (this cause is received in a

Handover Request) 36 RSPVERUVL Number Of Requested Speech Version Unavailable 37 LSANOTALL Number of LSA Not Allowed 38 CIPALNS Number of Ciphering Algorithm Not Allowed 39 GELUMOFAIL Number of GERAN Lu-mode failure 40 TCALALLOC Number of Terrestrial Circuit Already Allocated 41 INMSGCONT Number of Invalid Message Contents 42 IEMISS Number Of Information Element Or Field Missing 43 INCVAL Number Of Incorrect Value 44 UNMSGTYPE Number Of Unknown Message Type 45 UNIE Number Of Unknown Information Element 46 PEBSSMSC Number of Protocol Error Between BSS And MSC 47 VVCNE Number Of VGCC/VBS Call Non Existent 48 OTHER Number of times any other BSSMAP Cause value received 49 RESERVE1 Reserved Field 1 for future use 50 RESERVE2 Reserved Field 2 for future use 51 RESERVE3 Reserved Field 3 for future use 52 RESERVE4 Reserved Field 4 for future use WSSNODENUM is the key field, and identifies the node (card) to which this record applies.


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. Position Field Name Description 1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies 4 RADINFMSGFAIL Number of Radio interface message failure 5 RADNFFAIL Number of Radio interface failure 6 UPLKQUAL Number of Uplink Quality (this cause is sent in a Handover Required) 7 UPLKSTGH Number of Uplink Strength (this cause is sent in a Handover

Required) 8 DWLKQUAL Number of Downlink Quality (this cause is sent in a Handover

Required) 9 DWLKSTGH Number of Downlink Strength (this cause is sent in a Handover

Required) 10 DISTANCE Number of Distance (this cause is sent in a Handover Required) 11 OMINT Number of O And M Intervention (this cause is sent in a Handover

Required) 12 RSPMSCINV Number of Response To MSC Invocation (this cause is sent in a

Handover Required) 13 CALLCNTL Number of Call Control 14 RIFAILREV Number of Radio Interface Failure, Reversion To Old Channel 15 HOSUCC Number of Handover Successful 16 BETTERCELL Number of Better Cell (this cause is sent in a Handover Required) 17 DIRRETRY Number of Directed Retry (this cause is sent in a Handover

Required) 18 JOINGCC Number of Joined Group Call Channel 19 TRAFFIC Number of Traffic 20 REDLDINSC Number of Reduce Load In Serving Cell (this cause is sent in a

Handover Required) 21 TLTCHISC Number of Traffic Load In Target Cell Higher Than In Source Cell 22 RELTRIG Number of Relocation Triggered 23 EQUIPFAIL Number of Equipment Failure 24 NORADRESAVL Number Of No Radio Resource Available 25 RTRESUNAVL Number of Requested Terrestrial Resource Unavailable 26 CCHOVL Number of CCH Overload 27 PROCOVL Number of Processor Overload 28 BSSNOTEQP Number of BSS Not Equipped 29 MSNOTEQP Number of MS Not Equipped 30 INVCELL Number of Invalid Cell 31 TRAFFICLOAD Number of Traffic Load (this cause is sent in a Handover Required) 32 PREEMPTION Number of Preemption (this cause is sent in a Handover Required) 33 RETRRAUVL Number Of Requested Transcoding/Rate Adaptation Unavailable 34 CPMISMATCH Number Of Circuit Pool Mismatch 35 SCPOOL Number of Switched Circuit Pool (this cause is sent in a Handover

Required)


Position Field Name Description 36 RSPVERUVL Number Of Requested Speech Version Unavailable 37 LSANOTALL Number of LSA Not Allowed 38 CIPALNS Number of Ciphering Algorithm Not Allowed 39 GELUMOFAIL Number of GERAN Lu-mode failure 40 TCALALLOC Number of Terrestrial Circuit Already Allocated 41 INMSGCONT Number of Invalid Message Contents 42 IEMISS Number Of Information Element Or Field Missing 43 INCVAL Number Of Incorrect Value 44 UNMSGTYPE Number Of Unknown Message Type 45 UNIE Number Of Unknown Information Element 46 PEBSSMSC Number of Protocol Error Between BSS And MSC 47 VVCNE Number Of VGCC/VBS Call Non Existent 48 OTHER Number of times any other BSSMAP Cause value sent 49 RESERVE1 Reserved Field 1 for future use 50 RESERVE2 Reserved Field 2 for future use 51 RESERVE3 Reserved Field 3 for future use 52 RESERVE4 Reserved Field 4 for future use WSSNODENUM is the key field, and identifies the node (card) to which this record applies.


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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (IPM card) to which this record applies 4 SGWIP The IP Address of the SGW to which this record applies 5 RANGESETRX Number of Range-Set messages received from SGW 6 CONFIGTX Number of Configuration messages sent to SGW 7 TUNQUERYTX Number of Tunnel-Query messages sent to SGW 8 TUNINFORX Number of Tunnel-Info messages received from SGW 9 TUNOUTOFRANGERX Number of Tunnel-Out-of-Range messages received from

SGW 10 TUNRELEASETX Number of Tunnel-Release messages sent to SGW 11 TCPCONNREQ Number of times TCP connection requested by SGW 12 TCPCONNRELTO Number of times TCP connection was released by UNC due

to heartbeat timer expiration 13 TCPCONNREL Number of times TCP connection release encountered at

UNC (other than TCPCONNRELTO) 14 RESERVE1 Reserve Field 1 for future use 15 RESERVE2 Reserve Field 2 for future use 16 RESERVE3 Reserve Field 3 for future use 17 RESERVE4 Reserve Field 4 for future use WSSNODENUM and SGWIP are used as the key.


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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (IPM card) to which this record applies 4 GGWID Identifies the GPRS Gateway to which this record

applies 5 SVCNODEID Identifies the UNC-PS within the GPRS Gateway to

which this record applies. 6 CONFIGINFREQTX Number of Config Info Request sent to the GPRS

Gateway Management 7 CONFIGINFRESRX Number of Config Info Result received from UNC-PS 8 CONFIGINFUPDRX Number of Config Info Update received from UNC-PS 9 SYSINFREQTX Number of System Info Req sent to UNC-PS 10 SYSINFRESRX Number of System Info Result received from UNC-PS 11 SYSINFUPDRX Number of System Info Update received from UNC-PS 12 REGREQTX Number of UPPS Register Request sent to UNC-PS 13 REGUPDUPLTX Number of UPPS Update Uplink sent to UNC-PS 14 DEREGTX Number of UPPS Deregister sent to UNC-PS 15 DEREGRX Number of UPPS Deregister received from UNC-PS 16 GPRSSUSPTX Number of UPPS GPRS Suspension Request sent to

UNC-PS 17 GPRSRESTX Number of UPPS GPRS Resume Request sent to

UNC-PS 18 GPRSRESRSLTRX Number of UPPS GPRS Resume Result received from

UNC-PS 19 PAGEREQRX Number of UPPS Paging Request CS received from

UNC-PS 20 SYNCINFOTX Number of UPPS Synchronization Information sent to

UNC-PS 21 URLCMSGTX Number of URLC messages sent to UNC-PS 22 URLCMSGRX Number of URLC messages received from UNC-PS 23 OTHERTX Number of any other messages sent 24 OTHERRX Number of any other messages received 25 TCPCONNEST Number of times TCP connection was established with

Service Node

26 MSINITIATEDTCACT Number of requested MS initiated URLC Transport Channel activations incremented when URLC-ACTIVATE-UTC-REQ is received from MS

27 NETWORKINITIATEDTCACT Number of requested Network Initiated URLC Transport Channel activations incremented when URLC-ACTIVATE-_UTC_REQ is sent to MS

26 RESERVE1 Reserved Field 1 for future use 27 RESERVE2 Reserved Field 2 for future use 28 RESERVE3 Reserved Field 3 for future use


Position Field Name Description 29 RESERVE4 Reserved Field 4 for future use 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.


11.1.12 Location Services UNC – SMLC Interface Information (UMALCSUNCPERF) 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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (CCM card) to which this record applies 4 PERFLOCREQTX Number of Perform Location Request sent to SMLC 5 PERFLOCRESPSUCCRX Number of Perform Location Response with location

estimate received from SMLC 6 PERFLOCRESPRX Total number of Perform Location Response received

from SMLC 7 UMAPOSREQRX Number of UMA Position Request received from SMLC 8 UMAPOSRESPTX Total number of UMA Position Response sent to

SMLC 9 UMAPOSRESPSUCCTX Number of UMA Position Response with location sent

to SMLC 10 UMAPOSRESPMACRX Number of AP MAC locations received in Perform

Location Response from SMLC 11 UMAPOSRESPCGIRX Number of AP CGI locations received in Perform

Location Response from SMLC 12 UMAPOSRESPIPRX Number of AP IP locations received in Perform

Location Response from SMLC 13 UMAPOSRESPIMSIRX Number of Subscriber locations received in Perform

Location Response from SMLC 14 UMAABORTTX Number of UMA Abort sent to SMLC 15 UMAREJECTTX Number of UMA Reject sent to SMLC 14 RESERVE1 Reserve Field 1 for future use 15 RESERVE2 Reserve Field 2 for future use 16 RESERVE3 Reserve Field 3 for future use 17 RESERVE4 Reserve Field 4 for future use



11.1.13 Location Services UMADB UNC Message Information (UMADBUNCPERF) 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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (IPM card) to which this record applies 4 UMADBLOCREQTX Number of UMA DB Location Request sent to UMA

DB 5 UMADBLOCRESPRX Number of UMA DB Location Response with

location, received from UMA DB 6 RESERVE1 Reserve Field 1 for future use 7 RESERVE2 Reserve Field 2 for future use 8 RESERVE3 Reserve Field 3 for future use 9 RESERVE4 Reserve Field 4 for future use

WSSNODENUM is key field and identifies the node (card) to which this record applies


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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (CCM card) to which this record applies 4 GEOPOSREQINITRX Number of Geo Position Request (Initial) received

from GMLC 5 GEOPOSRETRESINITTX Number of Geo Position Return Result (Initial) sent to

GMLC 6 GEOPOSREQUPDRX Number of Geo Position Request (Updated) received

from GMLC 7 GEOPOSRETRESUPDTX Number of Geo Position Return Result (Updated) sent

to GMLC 8 RESERVE1 Reserve Field 1 for future use 9 RESERVE2 Reserve Field 2 for future use 10 RESERVE3 Reserve Field 3 for future use 11 RESERVE4 Reserve Field 4 for future use 12 RESERVE5 Reserve Field 5 for future use 13 RESERVE6 Reserve Field 6 for future use



11.1.15 Location Services SMLC Information (UMALCSSMLCPERF) FUTURE IMPLEMENTATION – This performance group is not implemented in the Drop 3.0 (UMA2.1) UMA software release. 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. Position Field Name Description 1 STARTTIMESTAMP Date and time performance interval started 2 STOPTIMESTAMP Date and time performance interval stopped 3 WSSNODENUM WSS Node (CCM card) to which this record applies 4 PERFLOCREQRX Number of Perform Location Request received from

UNC 5 PERFLOCRESPSUCCTX Number of Perform Location Response with location

estimate sent to UNC 6 PERFLOCRESPTX Total number of Perform Location Response sent to

UNC 7 UMAPOSREQTX Number of UMA Position Request sent to UNC 8 UMAPOSRESPRX Total number of UMA Position Response received from

UNC 9 UMAPOSRESPSUCCRX Number of UMA Position Response with location

received from UNC 10 UMAPOSRESPMACTX Number of AP MAC locations sent in Perform Location

Response to UNC 11 UMAPOSRESPCGITX Number of AP CGI locations sent in Perform Location

Response to UNC 12 UMAPOSRESPIPTX Number of AP IP locations sent in Perform Location

Response to UNC 13 UMAPOSRESPIMSITX Number of Subscriber locations sent in Perform

Location Response to UNC 14 RESERVE1 Reserve Field 1 for future use 15 RESERVE2 Reserve Field 2 for future use 16 RESERVE3 Reserve Field 3 for future use 17 RESERVE4 Reserve Field 4 for future use



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 Field Name Description

1 STARTTIMESTAMP Beginning time of the performance interval 2 STOPTIMESTAMP Ending time of the performance interval 3 WSSNODENUM WSS Node (CCM Card) to which this record applies. 4 MOCALLATTEMPT Number of attempted UMA mobile-originated calls (WSS

receives DTAP Setup message from the MS). 5 MOCALLSUCC Number of successful UMA mobile-originated calls (WSS

receives Assignment Complete from the UNC). 6 MTCALLATTEMPT Number of attempted UMA mobile-terminated calls (WSS

sends DTAP Setup message to the MS). 7 MTCALLSUCC Number of successful UMA mobile-terminated calls (WSS

receives Assignment Complete from the UNC). 8 HOATT2GTOUMA

Number of Intra-MSC 2G to UMA Handovers attempted (WSS receives Handover Required from the serving BSS and the target cell belongs to UMA).

9 HOSUCC2GTOUMA 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).

10 HOATTUMATO2G Number of Intra-MSC UMA to 2G Handovers attempted

(WSS receives Handover Required from the serving UNC and the target cell belongs to GSM).

11 HOSUCCUMATO2G 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).

12 HOATTUMATOUMA 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.

13 HOSUCCUMATOUMA 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.

14 MOESCALLATTEMPT Number of attempted UMA mobile-originated emergency

calls (WSS receives DTAP Emergency Setup message from the MS).

15 MOESCALLSUCC Number of successful UMA-mobile originated emergency

calls (WSS receives Assignment Complete from the UNC for an emergency call).

16 NBRCLSMRKUPDT Number of Classmark Updates pegged when Class mark update message received.

17 MSORIGCMSRVCREQ CM Service Request from originating MS pegged when CM service request message received from originating UMA


Position Field Name Description MS.

18 ANSMSORIGCALLS Number of answered calls for mobile originating traffic pegged when connect ack message is received from UMA MS.

19 ANSMSTERCALLS Number of answered calls for mobile terminating traffic pegged when connect ack message is sent to UMA MS.

20 MSEMRGNCYCMSRVCREQ Number of Emergency CM Service Requests is received from originating UMA MS.

21 ANSMSEMRGNCYCALLS Number of answered emergency calls when connect ack is received from originating UMA MS.

22 ATTCIPHRMDCTRPROCS Number of ciphering mode control procedures transmitted to UMA MS.

23 SUCCCIPHRMDCTRPROCS Number of successful ciphering mode control procedures 24 TRANSSUBIDWTMSI Number of transactions where mobile subscriber was

identified with his TMSI 25 TRANSSUBIDWIMSI Number of transactions where mobile subscriber was

identified with his IMSI 26 ATTTMSIREALOC Number of TMSI re-allocation attempts 27 SUCCTMSIREALOC Number of successfully performed TMSI re-allocations 28 IMSIDETACHPROCS Number of IMSI Detach procedures 29 IMSIATTACHPROCS Number of IMSI Attach procedures received from UMA MS. 30 IMPLICITDETACH Total number of subscribers implicitly detached (i.e. by VLR

audit) 31 ATTINEXTINTRAMSCHDO

Number of intra-MSC target cell 2G to UMA handover procedures initiated pegged on dispatch of BSSMAP:Handover Request to target UNC

32 SUCCOUTEXTINTRAMSCHDO

Number of intra-MSC serving cell 2G to UMA handover procedures successfully completed pegged on receipt of BSSMAP:Handover complete from target UNC.

33 UNSCCEXTHDORECNCTPERMSC

Number of unsuccessful 2G to UMA Handovers with reconnect to the original channels pegged when HO failure received from the serving BSS.

34 UNSCEXTHDOLOSSCNCTPERMSC

Number of unsuccessful 2G to UMA Handovers with loss of the call pegged when Clear Request message is received from the serving BSS.

35 SUCCINTRAHOCTMCALLS

Number of successful Intra-MSC UMA HO for CTM Calls. These counters will be zero since they are not supported in this release.

36 SUCCINTERINHOCTMCALLS

Number of successful Incoming Inter-MSC HO for CTM Calls. These counters will be zero since they are not supported in this release

37 ATTINTRAHOCTMCALLS

Number of attempted Intra MSC HO CTM Calls. These counters will be zero since they are not supported in this release

38 ATTINTERINHOCTMCALLS Number of attempted Incoming Inter-MSC HO for CTM Calls.

These counters will be zero since they are not supported in this release

39 ATTINTERVLRLOCUPD Number of attempted (incoming) inter VLR location update 40 SUCCINTERVLRLOCUPD Number of successful (incoming) inter VLR location update 41 ATTINTRAVLRLOCUPD Number of attempted intra VLR location update (all types) 42 ATTPERIINTRAVLRLOCUPD Number of attempted periodic intra VLR location update 43 SUCCINTRAVLRLOCUPD Number of successful intra VLR location update (all types) 44

SUCCPERIINTRAVLRLOCUPD Number of successful periodic intra VLR location update 45 ATTAUTH Number of attempted Authentication procedures 46 SUCCAUTH Number of successful Authentication procedures 47 ATTPAGEMSTMSI Number of Paging Attempts (within LAC) with TMSI pegged


Position Field Name Description when paging message is sent with TMSI and IMSI.

48 SUCCPAGEMSTMSI Number of Successful Paging (within LAC) with TMSI 49 ATTPAGEMSIMSI

Number of Paging Attempts (within LAC) with IMSI pegged when paging message is sent with IMSI.

50 SUCCPAGEMSIMSI Number of Successful Paging (within LAC) with IMSI 51 ATTSEARCHMSIMSI

Number of Search Attempts with IMSI, after the first Page to UMA fails

52 SUCCSEARCHMSIMSI Number of Successful Searches with IMSI, after the first Page to UMA fails

53 REJLUPPLMNNOTALLOWED Number of Location Updates rejected due to visitor’s PLMN not allowed. LUP Rejection Cause value is 11.68 54 REJLUPLACNOTALLOWED Number of Location Updates rejected due to Location Area

not allowed. LUP Rejection Cause value is 12.69 55 REJLUPROAMNOTALLOWED

Number of Location Updates rejected due to roaming not allowed in this location area. LUP Rejection Cause value is 13.70

56 REJLUPIMSIUNKINHLR Location Update failed, cause = IMSI unknown in HLR 57 REJLUPILLEGALMS Location Update rejected, cause = Illegal MS 58 REJLUPILLEGALME Location Update rejected, cause = Illegal ME 59 REJLUPNOSUITCELLINAREA Location Update rejected, cause = No Suitable cell in area 60 REJLUPNETWORKFAIL Location Update rejected, cause = Network failure 61 Reserved1 Reserved field 1 for future use 62 Reserved2 Reserved field 2 for future use 63 Reserved3 Reserved field 3 for future use 64 Reserved4 Reserved field 4 for future use 65 Reserved5 Reserved field 5 for future use 66 Reserved6 Reserved field 6 for future use 67 Reserved7 Reserved field 7 for future use 68 Reserved8 Reserved field 8 for future use 69 Reserved9 Reserved field 9 for future use 70 Reserved10 Reserved field 10 for future use

WSSNODENUM is the key field, and identifies the node (card) to which this record applies.


END OF DOCUMENT

alcatel performance data measurement

Documents

new counters counters

system performance data

type counters

atrium msc performance

data collection

data storage

data transfer

sp9 3bl76533faaadszza