dids in sts

DESCRIPTION 1 (220)Uppgjord − Prepared

XCS/UZ/TI XRESPOTGodkänd − Approved Kontr − Checked

TEI/XYX/B (Antonio Montone)

omnifilter R5A

Datum − Date Rev Dokumentnr − Document no

2010−09−01 A 6/1551−CSA 121 01/3Tillhor / referens − File / Reference

DIDs in STS

1 Revision Information

2 Application2.1 Scope2.2 Purpose

3 Description

4 Abbreviations4.1 DIDs in Alphabetical Order

5 DID−descriptions5.1 BTROUTECNT5.2 LOSSROUTECNT5.3 LOASCNT5.4 TRTYPECNT15.5 EOSEVERYCNT5.6 EOSLASTCNT5.7 LOSTCLCNT5.8 LOSTRECNT5.9 DIPSTCNTDATA5.10 SNTCNTDATA5.11 NSCNTDATA5.12 ROUTEACCCNT5.13 DISSDCNTDATA5.14 FAUSCNTDATA5.15 QUASCNTDATA5.16 SETSCNTDATA5.17 CPCNTDATA5.18 RPCNTDATA5.19 EMRPCNTDATA5.20 EMCNTDATA5.21 EMGCNTDATA5.22 BTROUTELVLCNT5.23 ROUTETRANTAB5.24 SLDESTAB5.25 MTPBASMES5.26 SCCPBASMES5.27 SLMES5.28 EMGTRANTAB5.29 SLMES25.30 SLMES35.31 SS7PG15.32 SS7PG25.33 MTPBASMES25.34 STPTIMERS5.35 LSDESTAB5.36 LSMES

DESCRIPTION 2 (220)Datum − Date Rev Dokumentnr − Document no


5.37 CAMABTCNT15.38 CAMABTCNT25.39 EMGSTATCNT5.40 BNTAB5.41 GTWYONET5.42 GTWYONETTT5.43 GTWYLNKSET5.44 GTWYLSONET5.45 GTWYLSDNET5.46 SS7TTCNT5.47 C7MESSDATA5.48 CHANASSIGNCNT5.49 HANDOVERCNT5.50 LOCUPDACNT5.51 PAGINGCNT5.52 MTSMAPCNT5.53 SECURITYCNT5.54 SSCNT5.55 BSCCNT5.56 MTSMAPTAB5.57 SSTAB5.58 BSCTAB5.59 C7SCPERFCNT5.60 C7SCQOSCNT5.61 C7SCSSNUSECNT5.62 C7SCUSECNT5.63 C7SCSIGPCNT5.64 C7SCSPTAB5.65 C7TCMSGCNT5.66 C7TCCMPCNT5.67 C7TCTOTAL5.68 C7TCABOCNT5.69 C7TCREJCNT5.70 C7TCMSGTAB5.71 C7TCCMPTAB5.72 C7TCABOTAB5.73 C7TCREJTAB5.74 C7SL1CNT5.75 C7SL2CNT5.76 C7SLTAB5.77 C7SLSETCNT5.78 C7SLSETTAB5.79 C7RTSETCNT5.80 C7SPTAB5.81 C7ADJSLPCNT5.82 C7OPCCNT5.83 C7OPCTAB5.84 C7DPCCNT5.85 C7DPCTAB5.86 C7SIOCNT5.87 C7OPCSIOCNT5.88 C7OPCSIOTAB5.89 C7DPCSIOCNT5.90 C7DPCSIOTAB



5.91 C7ODSCNT5.92 C7ODSTAB5.93 C7RTTOTALCNT5.94 SESSSFCNT5.95 DIPQCNT15.96 DIPQCNT25.97 DIPTAB5.98 CELLTAB5.99 CELLCNT5.100 EIRCNT5.101 HLRTAB5.102 LACNT5.103 LATAB5.104 MOBSUBHLRCNT5.105 MSCTAB5.106 NBRCELLCNT5.107 NBRMSCLCNT5.108 SMSCNT5.109 C7TCDIACNT5.110 C7TCDIATAB5.111 GSMSCCNT5.112 IWSMSCCNT5.113 MTSFBCNT5.114 MTSFBTAB5.115 ODBCNT5.116 SAECNT5.117 TPLATMES5.118 STPTIMERS25.119 C7ODCNT5.120 C7ODTAB5.121 C7LSSICNT5.122 C7LSSITAB5.123 C7OPCDSCNT5.124 C7OPCDSTAB5.125 MTPFORMTAB5.126 C7MRVTOTCNT5.127 C7MRVFAILCNT5.128 C7MRVFAILTAB5.129 C7ODS24CNT5.130 DIPQCNT35.131 SS7SCSSNUSECNT5.132 LATACNT5.133 COPRVLRCNT5.134 COPRVLRTAB5.135 LATATAB5.136 LATAMISCNT5.137 SS7SCQOSCNT5.138 SERVICESWCNT5.139 NBRMSCPROCCNT5.140 TRDCNT15.141 REGSERVCNT5.142 SS7SCUSECNT5.143 EQLACCCNT5.144 C7OPCDS24CNT



5.145 DISCCALLCNT5.146 DIPPRM1CNT5.147 DIPPRM2CNT5.148 IRNEGCNT5.149 CODERASGNCNT5.150 TRAPEVENTCNT5.151 TPTRANTAB5.152 SCCPFORMTAB5.153 CVTR01CNT5.154 CVTR02CNT5.155 CVTR01TAB5.156 SHISTCNT5.157 SHSCFCNT5.158 SHAMCNT5.159 SHAMCALLCNT5.160 LNPGTT1CNT5.161 DATACNT5.162 DATATAB5.163 SERVFEATCNT5.164 SERVFEATTAB5.165 LNPMAINTCNT5.166 SDIPMSCNT5.167 SDIPTAB5.168 SDIPLEVTAB5.169 SDIPHPCNT5.170 SDIPLPCNT5.171 NMROUTECNT5.172 GPRSGSCNT5.173 BSC2CNT5.174 HS7SL1CNT5.175 LCSCNT5.176 DIGSCNT5.177 LOASMISC1CNT5.178 LOASMISC2CNT5.179 LOASINCOCNT5.180 RNCSTATCNT5.181 RNCTAB5.182 LSCCCNT5.183 RELOCCNT5.184 NMSCUGHOCNT5.185 UGHNDOVERCNT5.186 DID 591 "NOT USED"5.187 UMTSSECCNT5.188 OPTFEATCNT5.189 APPLATCNT5.190 APDISKCNT5.191 APDISKTAB5.192 GUHNDOVERCNT5.193 DTAPLCSCNT5.194 MTSFB3CNT5.195 NBRMSCGUHCNT5.196 MNPMAINTCNT5.197 CAMEL3CNT5.198 CAMELSMSCNT



5.199 UMTSPOSCNT5.200 APPLATTAB5.201 L3CCMSGCNT5.202 SS7HSLTRACNT5.203 SS7HSLMT1CNT5.204 SS7HSLMT2CNT5.205 SS7HSLMT3CNT5.206 SS7HSLS1CNT5.207 SS7HSLS2CNT5.208 SS7HSLPG1CNT5.209 SS7HSLPG2CNT5.210 M3DATACNT5.211 M3SSNMCNT5.212 M3ASPSMCNT5.213 M3ASPTMCNT5.214 M3MGMTCNT5.215 M3ASSOCCNT5.216 M3DEST1CNT5.217 M3DEST2CNT5.218 M3PERFCNT5.219 M3ASSOCTAB5.220 M3DEST1TAB5.221 M3DEST2TAB5.222 SUCORCLCNT5.223 MSCOOBTCCNT5.224 NSEPCALLCNT5.225 TQROUTECNT5.226 PRBTCALLCNT5.227 NMSCSRNSCNT5.228 PMROUTECNT5.229 NRTCFASERCNT5.230 NRTCAPCNT5.231 TRTYPECNT35.232 GANDIREPACNT5.233 GANRPLOADCNT5.234 DEFMGWCNT5.235 LOCUPDA2CNT5.236 NBRMSCL3CNT5.237 SUBSVLRCNT5.238 INTTRAFCNT5.239 MGNAMETAB5.240 RNCCODERSTATCNT5.241 MIBIPV4GCNT5.242 MIBIPSSTCNT5.243 MIBICMPSTCNT5.244 MIBICMPMSGSTCNT5.245 MIBUDPBASECNT5.246 MIBIFTABLECNT5.247 MIBIFXTABLECNT5.248 MIBVMIPSTSTAB5.249 LA2CNT5.250 MIBIPLCGCNT5.251 MIBIPV4ITCNT5.252 MIBIPSST2CNT



5.253 MIBIPIFSTCNT5.254 MIBIPIFST2CNT5.255 MIBIFTABLE2CNT5.256 MIBSCTPSTGCNT5.257 MIBSCTPST2CNT5.258 MIBSCTPLGCNT5.259 SUAQOSCNT5.260 SUAASSTCNT5.261 SUAIBSTCNT5.262 SUAASCONGCNT5.263 SUAIBCONGCNT5.264 SUAASDATACNT5.265 SUAIBDATACNT5.266 SUAASPTMCNT5.267 SUASSNMCNT5.268 SUAASPSMMCNT5.269 SUAPERFCNT5.270 SUAIBPERFCNT5.271 SUAUTILCNT5.272 SUAASTAB5.273 SUAIBTAB5.274 SUASPTAB

6 References6.1 LOCUPDA2CNT6.2 NBRMSCL3CNT6.3 SUBSVLRCNT6.4 INTTRAFCNT6.5 VOIPROUTCNT6.6 SIPROUTCNT6.7 SIPCODECCNT6.8 MGNAMETAB6.9 SIPNODECNT6.10 RNCCODERSTATCNT6.11 MIBIPV4GCNT6.12 MIBIPSSTCNT6.13 MIBICMPSTCNT6.14 MIBICMPMSGSTCNT6.15 MIBTCPBASECNT6.16 MIBUDPBASECNT6.17 MIBIFTABLECNT6.18 MIBIFXTABLECNT6.19 MIBDNSRCONFIGCNT6.20 MIBDNSRCCNT6.21 MIBDRCBOCNT6.22 MIBDRCBRCNT6.23 MIBDNSRCCACHECNT6.24 MIBDNSRNCACNT6.25 MIBDNSROCACNT6.26 MIBVMIPSTSTAB6.27 LA2CNT6.28 MIBIPLCGCNT6.29 MIBIPV4ITCNT6.30 MIBIPSST2CNT



6.31 MIBIPIFSTCNT6.32 MIBIPIFST2CNT6.33 MIBIFTABLE2CNT6.34 MIBSCTPSTGCNT6.35 MIBSCTPST2CNT6.36 MIBSCTPLGCNT6.37 SUAQOSCNT6.38 SUAASSTCNT6.39 SUAIBSTCNT6.40 SUAASCONGCNT6.41 SUAIBCONGCNT6.42 SUAASDATACNT6.43 SUAIBDATACNT6.44 SUAASPTMCNT6.45 SUASSNMCNT6.46 SUAASPSMMCNT6.47 SUAPERFCNT6.48 SUAIBPERFCNT6.49 SUAUTILCNT6.50 SUAASTAB6.51 SUAIBTAB6.52 SUASPTAB6.53 LOCUPAINTCNT

7 References



1 Revision Information

Revision A is based on Revision E.

Changes:

Updated DIDs:

SIPCODECCNT

2 Application

2.1 Scope

This Document should be used by all Designers that wish to use theStatistics and Traffic Measurement Subsystem (STS) as the method ofcollecting, manipulating and outputing their counters.

2.2 Purpose

This document should be used as a reference to show what counters STScan already handle, and also whether any NEW ’counters’ can be handledin a similar way to ’counters’ already handled by STS.

This will make it possible for already existing Data Interface Descriptions(DID) to be reused by similar functions.

An exception to this are DIDs marked as which are defined in this documentbut not supported.

3 Description

The Data Interface Descriptions (DID) describes the data interface betweenapplications in CP, SP and STS.

The contents of a DID specifies which data (that is variables) are possibleto output to applications in the SP.

Every DID has a name which should be declared as a Global NumberSymbol, the value is shown as the DID−number.

Every DID item position correspond to DS−stored Variable (NOT temporaryvariables, numeric values, NSYMB etc.). The variable can be included in arecord (that is file of records) or in Common data (mixing is not allowed).

The file of records may contain several individuals.

The counter names within brackets (for example CALLCNT) are proposedCP variable names according to the design rule "Counters in APT 210" orby convention.



The Data Interface description is interpreted as follows −

DID−name The Name of the DID

DID−numberThe number of the DID as reported to LAVS.

Function The purpose of the DID.

Application Where the DID is used.

Position The position within the DID.

Contents What that DID position means.

Description A description of the internal CP structure of the data andrelations with other DIDs.

4 Abbreviations

AP Adjunct Processor

CP Central Processor

DID Data Interface Description

FF Function Framework

FS Function Specification

IP Implemenatation Proposal

SP Support Processor

STS Statistics and Traffic Measurement Subsystem.



4.1 DIDs in Alphabetical Order

DID name DID number−−−−−−−− −−−−−−−−−−APDISKCNT 606APDISKTAB 607APPLATCNT 605APPLATTAB 638BNTAB 94BSC2CNT 561BSCCNT 133BSCTAB 136BTROUTECNT 1BTROUTELVLCNT 38C7ADJSLPCNT 159C7DPCCNT 162C7DPCSIOCNT 167C7DPCSIOTAB 168C7DPCTAB 163C7LSSICNT 303C7LSSITAB 304C7MESSDATA 118C7MRVFAILCNT 313C7MRVFAILTAB 314C7MRVTOTCNT 312C7ODCNT 301C7ODS24CNT 315C7ODSCNT 169C7ODSTAB 170C7ODTAB 302C7OPCCNT 160C7OPCDS24CNT 369C7OPCDSCNT 305C7OPCDSTAB 306C7OPCSIOCNT 165C7OPCSIOTAB 166C7OPCTAB 161C7RTSETCNT 157C7RTTOTALCNT 171C7SCPERFCNT 137C7SCQOSCNT 138C7SCSIGPCNT 141C7SCSPTAB 142C7SCSSNUSECNT 139C7SCUSECNT 140C7SIOCNT 164C7SL1CNT 152C7SL2CNT 153C7SLSETCNT 155C7SLSETTAB 156C7SLTAB 154C7SPTAB 158C7TCABOCNT 146C7TCABOTAB 150C7TCCMPCNT 144C7TCCMPTAB 149C7TCDIACNT 257C7TCDIATAB 258C7TCMSGCNT 143C7TCMSGTAB 148C7TCREJCNT 147C7TCREJTAB 151C7TCTOTAL 145CAMABTCNT1 78



CAMABTCNT2 79CAMEL3CNT 617CAMELSMSCNT 618CELLCNT 192CELLTAB 191CHANASSIGNCNT 126CODERASGNCNT 391COPRVLRCNT 340COPRVLRTAB 341CPCNTDATA 33CVTR01CNT 466CVTR01TAB 468CVTR02CNT 467DATACNT 518DATATAB 519DEFMGWCNT 770DIGSCNT 574DIPPRM1CNT 379DIPPRM2CNT 380DIPQCNT1 175DIPQCNT2 176DIPQCNT3 325DIPSTCNTDATA 20DIPTAB 177DISCCALLCNT 378DISSDCNTDATA 29DTAPLCSCNT 609EIRCNT 193EMCNTDATA 36EMGCNTDATA 37EMGSTATCNT 82EMGTRANTAB 64EMRPCNTDATA 35EOSEVERYCNT 13EOSLASTCNT 14EQLACCCNT 363FAUSCNTDATA 30GPRSGSCNT 555GSMSCCNT 261GTWYLNKSET 98GTWYLSDNET 100GTWYLSONET 99GTWYONET 96GTWYONETTT 97GUHNDOVERCNT 608HANDOVERCNT 127HLRTAB 194HS7SL1CNT 564INTTRAFCNT 805IRNEGCNT 389IWSMSCCNT 263L3CCMSGCNT 642LA2CNT 853LACNT 195LATAB 196LATACNT 339LATAMISCNT 345LATATAB 344LCSCNT 567LNPGTT1CNT 517LNPMAINTCNT 532LOASCNT 11LOASINCOCNT 577LOASMISC1CNT 575LOASMISC2CNT 576LOCUPAINTCNT 891LOCUPDA2CNT 777



LOCUPDACNT 128LOSSROUTECNT 3LOSTCLCNT 15LOSTRECNT 16LSCCCNT 580LSDESTAB 73LSMES 74M3ASPSMCNT 660M3ASPTMCNT 661M3ASSOCCNT 663M3ASSOCTAB 668M3DATACNT 658M3DEST1CNT 665M3DEST1TAB 670M3DEST2CNT 666M3DEST2TAB 671M3MGMTCNT 662M3SSNMCNT 659M3PERFCNT 667MGNAMETAB 811MIBICMPMSGSTCNT 840MIBICMPSTCNT 839MIBDNSRCCACHECNT 849MIBDNSRCCNT 846MIBDNSRCONFIGCNT 845 MIBDNSRNCACNT 850MIBDNSROCACNT 851MIBDRCBOCNT 847MIBDRCBRCNT 848MIBIFTABLE2CNT 859MIBIFTABLECNT 843MIBIFXTABLECNT 844MIBIPIFST2CNT 858MIBIPIFSTCNT 857MIBIPLCGCNT 854MIBIPSST2CNT 856 MIBIPSSTCNT 838MIBIPV4GCNT 837MIBIPV4ITCNT 855MIBSCTPLGCNT 862MIBSCTPST2CNT 861 MIBSCTPSTGCNT 860 MIBTCPBASECNT 841MIBUDPBASECNT 842MIBVMIPSTSTAB 852 MNPMAINTCNT 615MOBSUBHLRCNT 197MSCOOBTCCNT 704MSCTAB 198MTPBASMES 54MTPBASMES2 71MTPFORMTAB 311MTSFBCNT 264MTSFB3CNT 611MTSFBTAB 265MTSMAPCNT 130MTSMAPTAB 134NBRCELLCNT 199NBRMSCGUHCNT 612NBRMSCL3CNT 798NBRMSCLCNT 200NBRMSCPROCCNT 348NMROUTECNT 541NMSCSRNSCNT 745NMSCUGHOCNT 588NRTCAPCNT 749NRTCFASERCNT 748



NSCNTDATA 23NSEPCALLCNT 719ODBCNT 266OPTFEATCNT 604PAGINGCNT 129PMROUTECNT 747PRBTCALLCNT 722QUASCNTDATA 31REGSERVCNT 350RELOCCNT 587RNCCODERSTATCNT 819RNCSTATCNT 578RNCTAB 579ROUTEACCCNT 26ROUTETRANTAB 46RPCNTDATA 34SAECNT 287SCCPBASMES 55SCCPFORMTAB 453SDIPHPCNT 536SDIPLEVTAB 535SDIPLPCNT 537SDIPMSCNT 533SDIPTAB 534SECURITYCNT 131SERVFEATCNT 520SERVFEATTAB 521SERVICESWCNT 347SESSSFCNT 174SETSCNTDATA 32SHAMCALLCNT 474SHAMCNT 471SHISTCNT 469SHSCFCNT 470SIPCODECCNT 809SIPNODECNT 814 SIPROUTCNT 807 SLDESTAB 53SLMES 56SLMES2 67SLMES3 68SMSCNT 201SNTCNTDATA 22SS7HSLMT1CNT 645SS7HSLMT2CNT 646SS7HSLMT3CNT 647SS7HSLPG1CNT 650SS7HSLPG2CNT 651SS7HSLS1CNT 648SS7HSLS2CNT 649SS7HSLTRACNT 644SS7PG1 69SS7PG2 70SS7SCQOSCNT 346SS7SCSSNUSECNT 335SS7SCUSECNT 362SS7TTCNT 101SSCNT 132SSTAB 135STPTIMERS 72STPTIMERS2 299SUAASCONGCNT 866 SUAASDATACNT 868 SUAASPSMMCNT 872 SUAASPTMCNT 870 SUAASSTCNT 864 SUAASTAB 876



SUAIBCONGCNT 867 SUAIBDATACNT 869 SUAIBPERFCNT 874 SUAIBSTCNT 865 SUAIBTAB 877SUAPERFCNT 873 SUAQOSCNT 863 SUASPTAB 878SUASSNMCNT 871 SUAUTILCNT 875 SUBSVLRCNT 799SUCORCLCNT 692TPLATMES 289TPTRANTAB 451TQROUTECNT 720TRAPEVENTCNT 450TRDCNT1 349TRTYPECNT1 12TRTYPECNT3 752UGHNDOVERCNT 589UMTSPOSCNT 635UMTSSECCNT 592VOIPROUTCNT 806



5 DID−descriptions

5.1 BTROUTECNT

−VALID FOR IOG/APG

DID−name: BTROUTECNTDID−number: 1

Function: Route−counters for Bothway Trunks

Position Contents 1 Global route number 2 Number of individuals in service 3 Number of blocked 4 Number of occupied 5 Number of call 6 Number of call with cong 7 Number of B−answer 8 Number of restricted calls 9 Number of devices out of service10 BT−route type11 Number of semipermanent connections12 Number of simultaneous calls13 Number of manually blocked14 Number of other blocked15 Number of automatically A−blocked16 Number of outgoing seizures17 Number of dual seizures18 Number of ATP received on ISUP routes19 Number of restricted devices20 Number of successful end of selections21 Number of congestions on the last available route22 Number of congestions due to route software individuals not available23 Number of Congestions due to MGW individuals not available in Bearer Terminator24 Number of Congestions due no transmission resource available in BEACC

Description: Counters for the bi−directional or one−way Trunk Routes.

A BT−route consists of two individuals(route records).One for icoming traffic (even internal route number)and one for outgoing traffic (odd internal route number).The incoming route record, in a pair of routes, is locatedbefore the outgoing route in the file.

If the BT−route is used for bothway traffic (a real BT−route) thenare both the individuals defined.( Position 1 and 2 <> 0)If only one of the individuals are defined then theBT−route is used for one−way traffic (false BT−route), forincoming or for outgoing traffic.The internal route number is identical with the record number(that is record pointer or individual).Individual number 0 and 1 are not in use.Individual number 2 and 3 are reserved for test route.The BT−route type (item 10) indicates the type of the route:1 = incoming route2 = outgoing route



3 = bothway route

All other values (that is 0 and > 3) will be interpreted asundefined routes (that is measurement will not take place).(In most of the BT−blocks the existing variable "FNC",that is function code, can be used).

All variables (which are pointed out by the DID item positions)are stored in a record, the number of records = number ofroutes in the block.

Size of the variables.Position Size of variable1 16 bits2−3 16 bits4 16 bits5−7 16 bits5−7 32 bits8− 9 16 bits10 16 bits8 32 bits11 − 15 16 bits16 − 18 32 bits19 − 20 16 bits20 − 21 32 bits22 16 bits23 16 bits24 16 bits

5.2 LOSSROUTECNT


DID−name: LOSSROUTECNTDID−number: 3

Function: Route−counters for loss−system routes (call attempt rejected when no device idle)

Position Contents 1 Global route number 2 Number of individuals (devices on route) 3 Number of blocked individuals. 4 Number of occupied individuals. (traffic level counter) 5 Number of calls (call level counter) 6 Number of call with congestion. (conjestion level counter) 7 Number of automatically B−blocked 8 Number of B−Answers 9 Number of manually blocked10 Number of other blocked11 Number of automatically A−blocked

Description:One record per route in the block.All the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = number of routes in the block.LOSS routes with hardware have the following restriction:Individual number 0 is not in use.Individual number 1 is reserved for test route.



The DID position 1 is stored in all the blocks mentionedabove.

The global routes are identified by a number.The translation table (DID 46: ROUTETRANTAB) is used totranslate the global route number to the symbolic routename.

NOTE. The counter "Number of B−answers" is only valid for CFC routes (Measurement on Business Groups). The size of the variables.DID position Block Size1 ADJI,ADJO,TRACO,DROP,IA 16 bit2 ADJI,ADJO 16 bit34 ADJI,ADJO,TRACO,DROP,IA 16 bit5 ADJI,ADJO,TRACO,DROP,IA 32 bit6 ADJI,ADJO 16 bit7−11

5.3 LOASCNT


DID−name: LOASCNTDID−number: 11

Function: Traffic and load counters

Position Contents 1 Accumulated processor load 2 Number of accumulations 3 Number of offered originating call attempts 4 Number of offered incoming call attempts and number of offered setup of VGCS channel attempts. 5 Number of fetched originating call attempts. 6 Number of fetched incoming call attempts. 7 Miscellaneous tasks: Number of low−priority requests for capacity in the load supervision function 8 Miscellaneous tasks: Number of high−priority requests for capacity in the load supervision function 9 Miscellaneous tasks: Number of low−priority requests for capacity accepted by the load supervision function10 Miscellaneous tasks: Number of high−priority requests for capacity accepted by the load supervision function11 Number of processor capacity requests sent by HLR12 Number of not accepted processor capacity requests sent by HLR13 Number of priority originating calls offered to the Processor Load Control function14 Number of non−priority originating calls offered to the Processor Load



Control function15 Number of priority originating calls fetched from the Processor Load Control function16 Number of non−priority originating calls fetched from the Processor Load Control function17 Number of processor capacity requests for low priority TCAP messages offered to the Processor Load Control function18 Number of accepted processor capacity requests for low priority TCAP messages

Description:One record.All the Variables (which are pointed out by theDID item positions) are stored in one record or ascommon variables.

5.4 TRTYPECNT1


DID−name: TRTYPECNT1DID−number: 12

Function: Traffic type counters

Position Contents 1 Number of calls (was Number of calls recognised by RE) 2 Number of unsuccessful calls 3 Traffic Level, Number of ongoing through connected calls 4 Number of calls rejected due to internal congestion 5 Number of calls rejected due to external congestion 6 Number of successful end of selections 7 Number of calls with B−answer 8 Number of calls disconnected due to release (A−replacement or Clear Forward) before dialling 9 Number of calls disconnected due to release (A−replacement or Clear Forward) during dialling 10 Number of calls disconnected due to release (A−replacement or Clear Forward) after dialling, but before through connection 11 Number of calls disconnected due to time out (no digits dialled) before dialling 12 Number of calls disconnected due to time out (all digits not received) during dialling 13 Number of calls rejected due to busy B−subscriber 14 Number of calls rejected due to Non−existent B−number 15 Number of calls rejected due to inaccessible number 16 Number of calls rejected due to Network Management action 17 Number of calls released due to lack of "proceed to send" signal, or dual seizure 18 Number of calls released due to reception of a congestion signal 19 Number of calls released due to a signalling time out (except lack of "proceed to send" signal) 20 Number of calls released due to



A−replacement, while waiting for the end of selection signal 21 Number of calls released due to faulty signalling 22 Number of ISDN calls (was Number of ISDN calls recognised by the register (RE) function (RE seizures). Recall of the register function is considered a new call) 23 Number of calls rejected by "Circuit reservation" 24 Number of calls rejected by Mass Calling Control

Description:One set of counter per basic traffic type.A basic traffic type is determined by origin anddestination. There are 16 origins and destinations,respectively. That makes a total of 16 X 16=256 basictraffic types.All the Variables (which are pointed out by theDID item positions) are stored in an indexed record, the numberof records = 16 and the number of indices = 16.

5.5 EOSEVERYCNT


DID−name: EOSEVERYCNTDID−number: 13Function: Counters per EOS−code, every attempt

Position Contents

1 Number of attempts

Description:One counter per EOS−code. The counter is stepped every timethe EOS−code is analysed.The Variable (which is pointed out by theDID item position) is stored in a record, the numberof records = round 1200.

5.6 EOSLASTCNT


DID−name: EOSLASTCNTDID−number: 14Function: Counters per EOS−code, last attempt

Position Contents 1 Number of calls

Description:One counter per EOS−code. The counter is stepped the EOS−code is analysed the last time in a call.The Variable (which is pointed out by theDID item position) is stored in a record, the numberof records = round 1200.

5.7 LOSTCLCNT




DID−name: LOSTCLCNTDID−number: 15Function: Counter for number of lost call due to restart in speech position.

Position Contents 1 Number of lost calls

Description:The counter shows the number of calls lost in speechposition due to restart. The number of lost call isalways added to the counter, that is the counter willcontain number of lost calls from all the restarts.The Variable (which is pointed out by theDID item position) is stored in one record or ina common variable.

5.8 LOSTRECNT


DID−name: LOSTRECNTDID−number: 16Function: Counter for number of lost calls due to restart in register position.

Position Contents 1 Number of lost calls

Description:The counter shows the number of calls lost in registerposition due to restart. The number of lost call isalways added to the counter, that is the counter willcontain number of lost calls from all the restarts.The Variable (which is pointed out by theDID item position) is stored in one record or ina common variable.

5.9 DIPSTCNTDATA


DID−name: DIPSTCNTDATADID−number: 20

Function: Digital paths counter data

Position Contents

1 Block number 2 Number of connected digital paths. 3 Number of blockings made by the Digital Path supervision. 4 Number of times threshold 1 is exceeded due to bitfault. 5 Number of times threshold 2 is exceeded due to bitfault. 6 Number of times threshold is exceeded due to slipfrequence.



7 Number of times threshold is exceeded due to disturbances. 8 Number of times when the bitfault super− vision function isn’t working. 9 Number of connected synchronous digital paths. 10 Number of connected multiplex sections. 11 Number of connected higher order path objects. 12 Number of connected lower order path objects. 13 Number of blockings made by the Synchronous Digital Path supervision. 14 Number of blockings made by the multiplex section supervision. 15 Number of blockings made by the higher order path supervision. 16 Number of blockings made by the lower order path supervision 17 Number of performed network protection switches

Description:One record per DIPST−block.The Variables (which are pointed out by theDID item position) are stored in one record or incommon variables.The translation table BNTAB is used to translate the block numberto the Block Name.

5.10 SNTCNTDATA


DID−name: SNTCNTDATADID−number: 22

Function: SNT counter data

Position Contents

1 Block number 2 Number of connected SNT’s 3 Number of blocked SNT’s

Description:One record per block.The Variables (which are pointed out by theDID item position) will be stored in common variables.

The translation table BNTAB is used to translate the block numberto the Block Name.

DID position Block Size1 − 3 ECP, ECP5, ECP6 16 bits

5.11 NSCNTDATA


DID−name: NSCNTDATADID−number: 23

Function: Neywork synchronization counter data



Position Contents

1 Number of clock references type CCM 2 Number of clock references type RCM 3 Number of clock references type EXT 4 Number of reference groups with clock reference of type DIP 5 Number of blocked references type CCM 6 Number of blocked references type RCM 7 Number of blocked references type EXT 8 Number of reference groups with all references of type DIP blocked 9 Number of switches of EX−reference from one reference group to another.

Description:One recordThe Variables (which are pointed out by theDID item position) are stored in one record or incommon variables.

5.12 ROUTEACCCNT


DID−name: ROUTEACCCNTDID−number: 26

Function: Accumulated route level counters for device types with short holding time, that is CR, CS, KR, RE, ASAM and the subscriber service features (SUS and BGS).

Position Contents

1 Global route number 2 Accumulated traffic level counter 3 Accumulated blocking level counter 4 Accumulated queue traffic level counter 5 Scanning counter (number of accumulations) 6 Accumulated manual blocking level counter 7 Accumulated other blocking level counter 8 Accumulated automatic type−A blocking level counter

Description:One record per global route number.Global route number indicates if position 2−5 isloaded (<>0) or not.Position 4 is only valid for queue system routes (CR,CSand KR).

5.13 DISSDCNTDATA


DID−name: DISSDCNTDATADID−number: 29

Function: Counters for Disturbance Supervision on trunks



Position Contents 1 Number of disturbances 2 Number of blockings

Description:One record per trunk type, that is per IT, OT and BT.IT − 1st recordOT − 2nd recordBT − 3rd recordAll the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = 3.

5.14 FAUSCNTDATA


DID−name: FAUSCNTDATADID−number: 30

Function: Counters for Fault Supervision on trunks

Position Contents 1 Number of signalling faults.

Description:One record per trunk type, that is per IT, OT and BTIT − 1st recordOT − 2nd recordBT − 3rd recordAll the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = 3.

5.15 QUASCNTDATA


DID−name: QUASCNTDATADID−number: 31

Function: Counters for Quality supervision

Position Contents

1 Number of indications 2 Number of blockings

Description:One record per type, that is per IT,OT,BT,RT,JT,AJ and BJIT − 1st recordOT − 2nd recordBT − 3rd recordRT − 4th recordJT − 5th recordAJ − 6th recordBJ − 7th recordAll the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = 7.



5.16 SETSCNTDATA


DID−name: SETSCNTDATADID−number: 32

Function: Counters for Seizure supervision on trunks

Position Contents

1 Number of not seized trunks

Description:One record per trunk type, that is per IT, OT and BTIT − 1st recordOT − 2nd recordBT − 3rd recordAll the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = 3.

5.17 CPCNTDATA


DID−name: CPCNTDATADID−number: 33

Function: Counters for the Central Processor

Position Contents 1 Number of large restarts with reload, manually initiated. 2 Number of large restarts with reload, automatically initiated. 3 Number of large restarts without reload, manually initiated. 4 Number of large restarts without reload, automatically initiated. 5 Number of small restarts manually initiated. 6 Number of small restarts automatically initiated. 7 Accumulated system blocking time, in seconds. 8 Number of permanent bitfaults 9 Number of temporary bitfaults10 Number of permanent CP−faults11 Number of temporary CP−faults12 Number of MAU/AMU faults13 Accumulated time of blocked CP−unit, manually blocked, in seconds.14 Accumulated time of blocked CP−unit, autamatically blocked, in seconds.15 Accumulated time of blocked MAU/AMU, manually blocked, in seconds.16 Accumulated time of blocked MAU/AMU autamatically blocked, in seconds.17 Memory size of program store/main store18 Memory size of data store19 Memory size of reference store



20 Number of forlopps aborted by APZ.21 Number of forlopps aborted by APT.22 Number of forlopps aborted manually.23 Number of prog executions terminated.

Description:One record.The Variables (which are pointed out by theDID item position) are stored in one record or incommon variables.

5.18 RPCNTDATA


DID−name: RPCNTDATADID−number: 34

Function: Counters for the RP’s

Position Contents 1 Number of RP’s 2 Number of RP’s in blocking state, man. blocked. 3 Number of RP’s in blocking state, aut. blocked. 4 Number of pair of RP’s in blocking state,man. blocked. 5 Number of pair of RP’s in blocking state,aut. blocked. 6 Number of RP’s, in an RP−pair, in blocking state,man blocked. 7 Number of RP’s, in an RP−pair, in blocking state,aut blocked. 8 Number of temporary faults in RP 9 Number of permanent faults in RP


5.19 EMRPCNTDATA


DID−name: EMRPCNTDATADID−number: 35

Function: Counters for the EMRPs

Position Contents

1 Number of EMRP’s 2 Number of blocked EMRP’s

Description:One record.The Variables (which are pointed out by theDID item position) are stored in one record or in



common variables.

5.20 EMCNTDATA


DID−name: EMCNTDATADID−number: 36

Function: Counters for the EMs

Position Contents

1 Number of EM’s 2 Number of blocked EM’s


5.21 EMGCNTDATA


DID−name: EMGCNTDATADID−number: 37

Function: Counters for the EMGs

Position Contents 1 Number of EMG’s 2 Number of permanent faults in EMG


5.22 BTROUTELVLCNT


DID−name: BTROUTELVLCNTDID−number: 38

Function: Accumulated Route level counters for devices of type BT−route with short holding time

Position Contents 1 Global route number 2 Number of blocked 3 Number of occupied 4 Number of devices out of service 5 BT−route type 6 Number of manually blocked



7 Number of other blocked 8 Number of automatically A−blocked 9 Through−connection Traffic level, number of ongoing through−connected calls10 B−answer Traffic level, number of ongoing B−answered callsDescription:The BT−route type (item 5) indicates the type of the route:1 = incoming route2 = outgoing route3 = bothway routeAll other values (that is 0 and > 3 ) will be interpreted asundefined routes (that is measurement will not take place).(In most of the BT−blocks the existing variable "FNC",that is function code, can be used).All the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = number of routes in the block.

The size of the variables:Position Block Size1 MALT, C7BTC 16 bits9 MALT, C7BTC 32 bits10 MALT, C7BTC 32 bits

5.23 ROUTETRANTAB


DID−name: ROUTETRANTABDID−number: 46

Function: Route translation table.

Position Contents 1 Symbolic route name 2 Trunk Group Number

Description:One record per global route number.The records are addressed by the global route number.The size of the variables:DID position Size1 7 characters string2 32 bits

5.24 SLDESTAB


DID−name: SLDESTABDID−number: 53Function: Signalling link designation translation table

Position Contents 1 Network code 2 Cluster code 3 Member code 4 Signalling link code 5 State (undefined/defined) 6 Link set name



Description:Translation table data for translating from SLP(Signalling link pointer) to signalling link designationand/or name.Signalling links designated according to following:Network−Cluster−Member−signalling link code and/orLink set name−signalling link code

Examples: 1−2−1−1,105−111−255−15,1−12−55−3 1−12−55−3 and/or AB000112−3DID positions 1−3 contains each the 8 bit binaryrepresentation ofNetwork code,Cluster code and Member code.Position 4 contains the 4 bit binary representation of asignalling link code.Position 5 is the record state telling if the recordis idle or used. 0=idle record, <> 0=used record.Position 6 contains the link set name (8 characters)stored in a 15 character string variable (128 bits).One record per signalling link.Items 1−6 are stored in S7LS.

5.25 MTPBASMES


DID−name: MTPBASMESDID−number: 54

Function: CCS traffic related total counts

Position Contents 1 Number of incoming MSU’s 2 Number of incoming SIF octets 3 Number of terminating management MSU’s 4 Number of terminating management SIF octets 5 Number of terminating SCCP/UP MSU’s 6 Number of terminating SCCP/UP SIF octets 7 Number of discarded MSU’s 8 Number of discarded MSU’s octets 9 Number of originating management MSU’s10 Number of originating management MSU octets11 Number of originating SCCP/UP MSU’s12 Number of originating SCCP/UP MSU octets13 Number of MSUs not requiring GTT, sampled for CP handling time.14 Accumulated total of CP handling time for sampled non−translated MSUs in ms.15 Number of sampled non−translated MSUs failing normal−load 95% test for CP handling time.16 Number of MSUs discarded due to invalid destination point code17 Number of MSUs discarded due to invalid Service Indicator Octet18 Number of octets retransmitted

Description:MTP traffic measurement total counters.

Counters 1−2 and 18 are stored in S7SL (previously in S7ST).Counters 3−17 are stored in S7DR.



5.26 SCCPBASMES


DID−name: SCCPBASMESDID−number: 55

Function: SCCP global title translation counts

Position Contents 1 Number of MSUs requiring GTT, sampled for CP handling time 2 Accumulated total of CP handling time for sampled GTT MSUs in ms 3 Number of sampled translated MSUs failing normal−load 95% test for CP handling time

Description:

5.27 SLMES


DID−name: SLMESDID−number: 56

Function: Signalling link measurements

Position Contents

1 State 2 Number of MSU’s transmitted, (retransmission not included) 3 Number of MSU’s received 4 Number of SIF and SIO octets received 5 Number of SIF and SIO octets transmitted 6 Number of SIF, SIO, LI, FSN, and BSN octets retransmitted 7 Number of MSUs retransmitted 8 Value of hourly link maintenance threshold for MSUs received in error 9 Number of MSUs received in error10 Value of hourly link maintenance threshold for negative acknowledgement received11 Number of negative acknowledgments received12 Number of errored seconds13 Number of priority 0 MSUs discarded due to SL congestion14 Number of priority 1 MSUs discarded due to SL congestion15 Number of priority 2 MSUs discarded due to SL congestion16 Indication of Link Declared Failure State 0 = ’XER’ 1 = ’Z01’ 2 = ’ABN’ 3 = ’ABN’ 4 = ’Z04’ 5 = ’XDC’ 6 = ’XDA’ 7 = ’XER’ 8 = ’APF’ 9 = ’APF’ 10 = ’APF’ 11 = ’N’ 12 = ’HWP’ 13 = ’HWP’ 14 = ’HWP’ 15 = ’HWP’ 16 = ’HWP’ 17 = ’HWP’ 18 = ’HWP’ 19 = ’HWP’ 20 = ’Z20’ 21 = ’Z21’ 22 = ’Z22’ 23 = ’APF’ 25 = ’LPO’ 26 = ’Z26’ 255 = ’N’ Change failure states in STS R12, refer to the FS 6/15517−ANTU 218 05/1 Uen



for valid failure states17 Indication of Link Management−Inhibit Status 0 = ’N’ 1 = ’Y’18 Current Link Transmit Congestion Level 0 = ’0’ 1 = ’0’ (semi−congestion) 2 = ’1’ 3 = ’2’ 4 = ’3’19 Current Link Transmit Congestion State 0 = ’N’ 1 = ’O’ 2 = ’D’20 Maintenance state (same as ’signalling link service status’) 0 = ’UNAV’ 1 = ’OOS’ 2 = ’ACT’21 Indication of processor outage status units being received 0 = ’N’ 1 = ’Y’22 Number of priority 3 MSUs discarded due to SL congestion

Description:One record per signalling link in the blocks.STATE indicates if the record is used (=1) or not (=0).

Variables for DID positions 1−19 and 21−22 are stored inS7SLVariables for DID positions 1 and 20 are stored in S7LS.

5.28 EMGTRANTAB


DID−name: EMGTRANTABDID−number: 64

Function: EMG translation table.

Position Contents 1 Symbolic EMG name 2 State (undefined/defined)

Description:Translation from EMG−number to symbolic EMG−name.One record per EMG. The records are addressed by EMG−number.State indicates whether the EMG is undefined (=0)or defined.

5.29 SLMES2


DID−name: SLMES2DID−number: 67


Position Contents 1 State (undefined/defined) 2 Accumulated total of link transmission buffer occupancy in octets 3 Accumulated total of link transmission buffer occupancy in MSUs 4 Accumulated total of link transmission



buffer occupancy in priority 0 MSUs 5 Accumulated total of link transmission buffer occupancy in priority 1 MSUs 6 Accumulated total of link transmission buffer occupancy in priority 2 MSUs 7 Accumulated total of link transmission buffer occupancy in priority 3 MSUs 8 Number of samples from signalling terminal 9 Link maintenance usage in 10 sec. units.10 MSUs received requiring GTT.11 MSU octets received for messages requiring GTT12 Number of times SL enters level 1 congestion state13 Number of times SL enters level 2 congestion state14 Number of times SL enters level 3 congestion state15 Total duration of level 1 congestion state in 10 sec. units16 Total duration of level 2 congestion state in 10 sec. units17 Total duration of level 3 congestion state in 10 sec. units18 Duration of link busy status declared by near−end signaling terminal in 50 ms. units19 Duration of busy−link status unit received from far−end in 50 ms. units20 Duration of far−end processor outage in 10 sec. units21 Signalling link active time in 10 sec. units22 Number of ten second scannings23 Link Set Pointer.24 Indication of processor outage status units being transmitted.

Description:One record per signalling link in the blocks.Item 1 is the record state telling if the record is idle orused. 0 = idle record, 0 <> used record.

5.30 SLMES3


DID−name: SLMES3DID−number: 68


Position Contents 1 State (undefined/defined) 2 Duration of SL declared failures, − All types in 10 sec. units 3 Number of SL declared failures,− All types 4 Duration of SL declared failures due to abnormal FIBR/BNSR in 10 sec. units 5 Number of SL declared failures due to abnormal FIBR/BNSR 6 Duration of SL declared failures due to excessive delay of acknowledgement in 10 sec. units 7 Number of SL declared failures due to excessive delay of acknowledgement 8 Duration of SL declared failures due to



excessive error rate in10 sec. units 9 Number of SL declared failures due to excessive error rate10 Duration of SL declared failures due to excessive duration of congestion in 10 sec. units11 Number of SL declared failures due to due to excessive duration of congestion12 Duration of SL declared failures due to due to hardware problems in 10 sec. units13 Number of SL declared failures due to hardware problems14 Duration of SL failures (declared and undeclared) in 10 sec. units.15 Duration of near−end processor outage in 10 sec. units16 Number of near−end manual changeovers17 Value of hourly link maintenance threshold for automatic changeovers18 Number of automatic changeovers19 Number of near−end management inhibits20 Number of far−end management inhibits21 Duration of signalling link management inhibits in 10 sec. units22 Parameter group number for signalling link23 Number of 10 second scans in S7SL.24 Number of 10 second scans in S7LS.

Description:One record per signaling link. Item 1 is the record statetelling if the record is idle or used. 0 = idle record,0 <> used record.

5.31 SS7PG1


DID−name: SS7PG1DID−number: 69

Function: Parameter group measurements

Position Contents 1 Q.703 T1 Timer,"aligned/ready" in 50 ms units 2 Q.703 T2 Timer, "not aligned" in 50 ms. units 3 Q.703 T3 Timer, "aligned" in 50 ms. units 4 Q.703 T4 Timer, normal proving period timer in 50 ms. units 5 Q.703 T4 Timer, emergency proving period timer in 50 ms. units 6 Q.703 T5 Timer, "sending SIB" in 50 ms. units 7 Q.703 T6 Timer, "remote congestion" in 50 ms. units 8 Q.703 T7 Timer, "excessive delay of acknowledgement" in 50 ms. units 9 Q.704 T17 Timer, "delay to avoid oscillation of initial alignment failure and link restart" in ms.10 Q.707 T1 Timer, "signalling link test message acknowledgement supervision" in seconds11 SL test procedure period in seconds12 SUERM parameter T13 SUERM parameter D in signal units divided by four



Description:One record per parameter group in the block. There are 8parameter groups. The parameter groups are identified bya number from 0 to 7. The parameter group number is the sameas the record number (pointer) in the parameter group file.

5.32 SS7PG2


DID−name: SS7PG2DID−number: 70

Function: Parameter group measurements

Position Contents 1 AERM parameter Tin 2 AERM parameter Tie 3 AERM parameter M 4 AERM parameter N in octets 5 Type of error correction method 6 (Number of octets in TB/RTB before forced retransmissionis ordered / 64) − 1 ; valid only when type of error correction is equal to 2 7 Value of congestion onset for level 1, CNCONTH1 = (number of octets in TB/RTB buffer when level 1 is reached / 64) − 1 8 Value of congestion onset for level 2, CNCONTH1 = (number of octets in TR/RTB buffer when level 2 is reached / 64) −1 9 Value of congestion onset for level3, CNCONTH1 = (number of octets in TR/RTB buffer when level 3 is reached / 64) −110 Value of congestion discard for level 1, CNCONTH1 = (number of octets in TR/RTB buffer when level 1 is reached / 64) −111 Value of congestion discard for level 2, CNCONTH1 = (number of octets in TR/RTB buffer when level 2 is reached / 64) −112 Value of congestion discard for level 3, CNCONTH1 = (number of octets in TR/RTB buffer when level 3 is reached / 64) −113 Value of congestion abatement for level 1, CNCONTH1 = (number of octets in TR/RTB buffer when level 1 is reached / 64) −114 Value of congestion abatement for level 2, CNCONTH1 = (number of octets in TR/RTB buffer when level 2 is reached / 64) −115 Value of congestion abatement for level 3, CNCONTH1 = (number of octets in TR/RTB buffer when level 3 is reached / 64) −1

Description:One record per parameter group in the block. There are 8parameter groups. The parameter groups are identified bya number from 0 to 7. The parameter group number is the sameas the record number (pointer) in the parameter group file.

5.33 MTPBASMES2




DID−name: MTPBASMES2DID−number: 71

Function: CCS Traffic related total counts

Position Contents 1 Number of assigned link sets 2 Total number of assigned signalling links 3 Number of in−service buffers (TB & RTB) 4 30−minutes usage verification count 5 Link transmission buffer size in octets 6 Link receiving message buffer size in MSUs 7 Number of MTP restarts Initiated 8 HSL transmission buffer size in octets.

Description:MTP total counters.These counters are common stored and are system totals..

5.34 STPTIMERS


DID−name: STPTIMERSDID−number: 72

Function: STP timers

Position Contents 1 Q.704 T1 Timer in seconds or 100 millisecond units 2 Q.704 T2 Timer in seconds or 100 millisecond units 3 Q.704 T3 Timer in seconds or 100 millisecond units 4 Q.704 T4 Timer in seconds or 100 millisecond units 5 Q.704 T5 Timer in seconds or 100 millisecond units 6 Q.704 T6 Timer in seconds or 100 millisecond units 7 Q.704 T8 Timer in seconds or 100 millisecond units 8 Q.704 T10 Timer in seconds 9 Q.704 T11 Timer in seconds10 Q.704 T12 Timer in seconds or 100 millisecond units11 Q.704 T13 Timer in seconds or 100 millisecond units12 Q.704 T14 Timer in seconds13 Q.704 T15 Timer in seconds14 Q.704 T16 Timer in seconds or 100 millisecond units15 Q.704 T20 Timer in seconds16 Q.704 T21 Timer in seconds17 Q.704 T19 Timer in seconds18 Q.704 Z31 Timer in seconds19 Q.704 Z32 Timer in seconds20 T1.111.4 T22 Timer in seconds21 T1.111.4 T23 Timer in seconds22 T1.111.4 T24 Timer in seconds23 T1.111.4 T25 Timer in seconds24 T1.111.4 T26 Timer in seconds

Description:MTP traffic measurement total counters.These counters are common stored and are system totals.

5.35 LSDESTAB




DID−name: LSDESTABDID−number: 73

Function: Link set designation and name translation table

Position Contents 1 Network code 2 Cluster code 3 Member code 4 State (undefined/defined) 5 Link set name

Description:Translation table data for translating from LSP(Link set pointer) to link set designation and/or name.Link set designated according to following:Network−Cluster−Member and/orLink set name

Examples: 1−2−1 and/or AA000321 105−111−255 and/or AB000123DID positions 1−3 are a representation ofNetwork code, Cluster code and Member code.Position 4 is the record state telling if the recordis idle or used. 0=idle record, 0 <> used record.Position 5 contains the Link set name (8 characters).One record per link set.

5.36 LSMES


DID−name: LSMESDID−number: 74

Function: Link set measurements

Position Contents 1 State (undefined/defined) 2 Number of MSU’s transmitted, (retransmission not included) 3 Number of MSU’s received 4 Number of SIF and SIO octets received 5 Number of SIF and SIO octets transmitted 6 Number of SIF, SIO, LI, FSN, and BSN octets retransmitted 7 Number of MSU’s retransmitted 8 Number of assigned SLs 9 Total duration of LS inactivity due to no links in LS are active in 10 sec. units10 Number of links in the Out−of−Service (OSS) Maintenance State11 Number of links in the Unavailable maintenance state12 Number of 10 sec. scans13 Maintenance state (same as ’link set service status’). 0 = ’UNAV’ 1 = ’OOS’ 2 = ’ACT’14 Number of currently available links

Description:One record per Link Set in the blocks.



Item 1 is the record state telling if the recordis idle or used. 0=idle record,0<>used record.

5.37 CAMABTCNT1


DID−name: CAMABTCNT1DID−number: 78

Function: CAMA counters per BT block.

Position Contents 1 Number of CAMA seizures.

Description:One counter per BT block.

The variable (which is pointed out by the DIDitem positions) is stored in one record or in acommon variable.

5.38 CAMABTCNT2


DID−name: CAMABTCNT2DID−number: 79

Function: CAMA counters per BT block.

Position Contents 1 Number of ONI calls or not accepted CAMA seizures

2 Number of CAMA seizures for which ANI failure digits are received

Description:Two counters per block.

The variables (which is pointed out by the DIDitem positions) are stored in one record or incommon variables.

5.39 EMGSTATCNT


DID−name: EMGSTATCNTDID−number: 82

Function: EMG performance statistic data per EMG.

Position Contents

1 Number of occurrences, all control paths to EMG are unavailable.



2 Time counter in seconds, all control paths to EMG are unavailable. 3 Number of occurrences, A−side control path to EMG is unavailable due to fault in control system (STC or STR). 4 Number of occurrences, B−side control path to EMG is unavailable due to fault in control system (STC or STR). 5 Number of occurrences, A−side control path to EMG is unavailable due to fault in signalling link. 6 Number of occurrences, B−side control path to EMG is unavailable due to fault in signalling link. 7 Time counter in seconds, one control path to EMG is unavailable

Description:One set of counters per EMG.The EMG is identified by the record number in the file,that is the pointer.All the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = max number of EMGs.

5.40 BNTAB


DID−name: BNTABDID−number: 94

Function: Translation table for block number to block name

Position Contents 1 Block Number 2 Symbolic Block Name

Description:One record per block.Translation of block number to block name.Variables are stored as common data.

Size of the variables.Position Block Size1 MUHOC, MUHIC, MUAMCO MUAMH, MHOCOIP, TRACO,TRACOB,DROP 16 bits2 MUHOC, MUHIC,MUAMCO MUAMH, MHOCOIP, MUSCCO,TRACO,TRACOB, DROP String 7 characters

5.41 GTWYONET


DID−name: GTWYONETDID−number: 96

Function: STP gateway administration measurements



per originating network.

Position Contentspostition 1 State 2 Originating Network 3 Originating Cluster 4 Number of global title translations performed, result is a DPC of an inter− connecting network. 5 Number of global title translations that were unable to be performed on messages received from an inter−connecting network, due to no translation table for the translation type.

Description:Counter 1 is a 2 bit variable (0=record not used, 1=usedwith network only, 2=used with network and cluster, 3=notvalid).

5.42 GTWYONETTT


DID−name: GTWYONETTTDID−number: 97

Function: STP gateway administration measurements per originating network and translation type.

Position Contents 1 State 2 Originating Network 3 Originating Cluster 4 Translation Type 5 Number of global title translations performed on messages received from an inter−connecting network. 6 Number of global title translations that were unable to be performed on messages received from an inter−connecting network, due to no translation for this address.

Description:Counter 1 (0=record not used, 1=usedwith network only, 2=used with network and cluster, 3=notvalid).

5.43 GTWYLNKSET


DID−name: GTWYLNKSETDID−number: 98

Function: STP gateway administration measurements per gateway link set

Position Contents 1 State 2 Internal LS Pointer



3 Number of Transfer−Prohibited (TFP) Message Signalling Units (MSUs) transmitted 4 Number of TFP MSUs received 5 Number of Transfer−Restricted (TFR) MSUs transmitted 6 Number of TFR MSUs received 7 Number of Transfer−Allowed (TFA) MSUs transmitted 8 Number of TFA MSUs received 9 Number of Signalling−Route−Set−Test (SRST) MSUs transmitted10 Number of SRST MSUs received11 Number of Transfer−Controlled (TFC) MSUs transmitted, originated by gateway STP12 Number of Signalling−Route−Set−Congestion− Test (SRSCT) MSUs transmitted13 Number of SRSCT MSUs received14 Number of Testing and Maintenance (T&M) MSUs received15 Number of Subsystem−Prohibited (SSP) MSUs transmitted16 Number of SSP MSUs received17 Number of Subsystem−Allowed (SSA) MSUs transmitted18 Number of SSA MSUs received19 Number of Subsystem−Status−Test (SST) MSUs transmitted20 Number of SST MSUs received21 Number of Signalling Link Tests received

Description:

5.44 GTWYLSONET


DID−name: GTWYLSONETDID−number: 99

Function: STP gateway administration measurements per gateway link set and originating network.

Position Contents 1 State 2 Internal LS Pointer 3 Network Identifier 4 Number of Testing and Maintenance (T&M) MSUs rejected due to screening, disallowed address (not gateway STP) 5 Number of MSUs rejected due to screening, disallowed Originating Point Code (OPC) 6 Number of MSUs rejected due to screening, disallowed Destination Point Code (DPC) 7 Number of MSUs rejected due to screening disallowed Service Indicator (SI) 8 Number of SCCP MSUs rejected due to screening, disallowed Calling Party Address 9 Number of Subsystem−Prohibited (SSP) and Subsystem−Allowed (SSA) MSUs rejected due to screening, disallowed Affected Point Code10 Number of Subsystem−Status−Test (SST) MSUs rejected due to screening, disallowed Affected Point Code and SSN



11 Number of MSUs rejected due to screening, disallowed Message Priority12 Number of MTP−NM MSUs rejected due to screening, disallowed Destination Field13 Number of SCCP MSUs rejected due to screening, disallowed Translation Type14 Number of SCCP MSUs rejected due to screening, disallowed DPC/SSN15 Number of messages rejected due to screening for other reasons (used for calculations)16 Number of Transfer−Controlled (TFC) MSUs received, addressed to gateway STP

Description:Counter 1 (0=not used, 1=used).

5.45 GTWYLSDNET


DID−name: GTWYLSDNETDID−number: 100

Function: STP gateway administration measurements per gateway link set and destination network.

Position Contents 1 State 2 Internal LS Pointer 3 Network Identifier 4 Number of Message Signalling Units (MSUs) received from another network, not addressed to the BCC Network. 5 Number of MSU Octets received from another network, not addressed to the BCC Network. 6 Number of MSUs transmitted, addressed to a network other than the adjacent receiving network. 7 Number of MSU octets transmitted, addressed to a network other than the adjacent receiving network.


5.46 SS7TTCNT


DID−name: SS7TTCNTDID−number: 101

Function: STP measurements per translation type.

Position Contents 1 State 2 Translation Type 3 Number of Global title Translations (GTTs) performed.



4 Number of GTTs that were unable to be performed due to no translation for address of such nature (Diagnostic 0). 5 Number of GTTs that were unable to be performed due to no translation for this specific address (Diagnostic 1).


5.47 C7MESSDATA


DID−name: C7MESSDATADID−number: 118

Function: Number of abmornal messages received on Level 3 and Level 4.

Position Contents 1 Number of abnormal messages received on Level 4 2 Number of abmormal messages received on Level 3 3 Number of abnormal messages received on Level 4 for ISUP

Description:All the Variables (which are pointed out by the DIDitem positions) are stored as common−stored variables.

5.48 CHANASSIGNCNT


DID−name: CHANASSIGNCNTDID−number: 126

Function: Counters for channel assignment

Position Contents 1 Number of channel assignments for call from mobile subscriber 2 Number of successful channel assignments for call from mobile subscriber 3 Number of channel assignments for call to mobile subscriber 4 Number of successful channel assignments for call to mobile subscriber 5 Number of assignment attempts for SMS on traffic channel 6 Number of successful assignments for SMS on traffic channel 7 Number of successful RAB assignments for call from mobile subscriber 8 Number of successful RAB assignments for call to mobile subscriber 9 Total number of RAB assignments for call from mobile subscriber10 Total number of RAB assignments for call to mobile subscriber11 Number of initial channel assignments on



remote A−interface when "CTM text telephony" is supported by the MS12 Number of initial channel assignments on remote A−interface when "CTM text telephony" is supported by the MS and the assignment of a CTM function in C−MGW is successful13 Number of initial channel assignments on remote A−interface when "CTM Text Telephony" is supported by the MS, CTM function in C−MGW is not available, but the assignment for speech device is successful14 Number of initial channel assignments on Iu−interface when "CTM text telephony" is supported by the MS15 Number of initial channel assignments on Iu−interface when "CTM text telephony" is supported by the MS and the assignment of a CTM function in C−MGW is successful16 Number of initial channel assignments on Iu−interface when "CTM Text Telephony" is supported by the MS, CTM function in C−MGW is not available, but the assignment for speech device is successful

Description:The counters belong to the Object Type CHASSIGNT andcounters shall be increased when the message "RABAssignment request" is sent to RNC and "RAB Assignmentresponse" is received from a RNC.

All the variables are stored as common data.

The size of the variables:Position Size1−6 16 bits7−16 32 bits

5.49 HANDOVERCNT


DID−name: HANDOVERCNTDID−number: 127

Function: Counters for handover, MSC level

Position Contents 1 Number of external intra−BSS handover attempts 2 Number of received handover required (excluding those received during guard time) 3 Number of sent handover requests to the target BSC 4 Number of successful handover requests to the target BSC 5 Number of sent handover commands 6 Number of successful internal intra BSS handovers (handover performed) 7 Number of successful external intra BSS handovers 8 Number of successful inter BSS handovers 9 Number of GS−operations triggered by timer THNDGSOP10 Number of GS−operations triggered by handover detect



11 Number of GS−operations triggered by handover complete12 Number of handover attempts causing the MS to switch back to old traffic channel13 Number of handover faults causing the MSC to release the call14 Number of inter−BSS handover attempts15 Number of external intra BSS handover attempts on SDCCH16 Number of successful external intra BSS handovers on SDCCH17 Number of inter BSS handover attempts on SDCCH18 Number of successful inter BSS handovers on SDCCH19 Number of external intra BSS handover attempts from SDCCH to TCH20 Number of successful external intra BSS handovers from SDCCH to TCH21 Number of inter BSS handover attempts from SDCCH to TCH22 Number of successful inter BSS handovers from SDCCH to TCH23 Number of own handovers with synchronisation error

Description:All the variables are stored as common data.

5.50 LOCUPDACNT


DID−name: LOCUPDACNTDID−number: 128

Function: Counters for location updating

Position Contents 1 Number of location updating attempts from non−registered subscribers (IMSI attach, normal location updating or periodic location updating) 2 Number of failed location updating attempts due to unknown IMSI number series 3 Number of location updating attempts for already registered subscribers 4 Number of periodic location updating attempts for already registered subscribers 5 Spare 6 Number of IMSI attach messages received (from already registered subscribers) 7 Number of IMSI detach messages received 8 Number of successful location updatings for non registered subscribers 9 Number of implicit detach events in MSC/VLR 10 Number of national roaming implicit detach events in MSC/VLR 11 Number of successful location updatings for already registered subscribers 12 Number of rejected location updating attempts due to Regional Subscription. 13 Number of failed location updating attempts due to unknown IMSI number series (2nd block). 14 Number of successful location updatings



for non registered subscribers (2nd block). 15 Number of successful location updatings for already registered subscribers (2nd block). 16 Number of IMSI detach messages received (2nd block). 17 Number of location updating attempts from non−registered subscribers (2nd block). 18 Number of location updating attempts for already registered subscribers (2nd block). 19 Number of IMSI attach messages received (from already registered subscribers) (2nd block). 20 Number of location updating attempts over Gs interface 21 Number of successful location updatings over Gs interface 22 Number of successful location updating indications sent to mobile subscribers, resulting from failure of operations ’update location’ to HLR due to network congestion 23 Number of periodic location updating requests for non−registered subscribers 24 Number of periodic location updating requests when capacity not granted for non−registered subscribers 25 Number of periodic location updating requests when capacity not granted for already registered subscribers


DID item positions 1−25 are peg counters.

5.51 PAGINGCNT


DID−name: PAGINGCNTDID−number: 129

Function: Paging counter

Position Contents 1 Number of first local page attempts

2 Number of first global page attempts

3 Number of repeated local page attempts

4 Number of repeated global page attempts

5 Number of page responses to first page

6 Number of page responses to repeated page

7 Number of unsuccessful page responses (includes unexpected page responses)

8 Number of first page attempts over Gs interface

9 Number of repeated page attempts over Gs interface



10 Number of page responses to first page over Gs interface 11 Number of page responses to repeated page over Gs interface 12 Number of paging failures over Gs interface

13 Number of MS Unreachable messages received as a response to a Paging Request message

14 Number of paging attempts for SMS

15 Number of successful paging responses for SMS

16 Number of first local page attempts over Iu interface 17 Number of first global page attempts over Iu interface 18 Number of repeated local page attempts over Iu interface 19 Number of repeated global page attempts over Iu interface 20 Number of page responses to first page over Iu interface 21 Number of page responses to repeated page over Iu interface 22 Number of unsuccessful page responses (includes unexpected page responses) over Iu interface MMMCS Iu−interface. PAGECONF/ACK 23 Number of page responses via A−interface when paging is done via IU−interface in MUPAG. 24 Number of page responses via IU−interface when paging is done via A−interface in MBPAG.


5.52 MTSMAPCNT


DID−name: MTSMAPCNTDID−number: 130Function: Counters for MAP operations

Position Contents 1 MAP operation identity (code) 2 Number of total requests of SubscriberLocationReport 3 Number of successful operations SubscriberLocationReport(first block) 4 Number of unsuccessful SubscriberLocationReport due to local TCAP resource problem 5 Number of total requests of a MAP operation (second block) 6 Number of successful MAP operations (second block) 7 Number of unsuccessful MAP operations due to local TCAP resource problems (second block) 8 Number of total requests of a MAP operation (status counter)



9 Number of total requests of a MAP operation (third block)10 Number of successful MAP operations (third block)11 Number of unsuccessful MAP operations due to local TCAP resource problems (third block)12 Number TC transferred MAP operations between Blades(first block)

Description:One record per MAP operation and MAP version.All the variables which are pointed out by theDID item positions are stored in a record,the number of records = number of MAP operations inthe block.The variables are stored as common data if the blockcontains only one MAP operation.The MAP operations are identified by a code.See DID MTSMAPTAB.All counters are not relevant for all of the MAPoperations.Positions 5−7 and 9−11 are used for the same MAPoperation but in different blocks.For the MAP operations ’Reset’ and ’Reset2’the status counter is independent of the MAP version.Therefore, the status counter for ’Reset’ is incrementedand decremented irrespective of the MAP version, while thestatus counter for ’Reset2’ will always remain zero.Blocks MPELAP, MPSLAP and MSLRAP belong to thesubsystem LSS.Blocks GSCTAP, GSMOSAP, GSMS, IWASCAP, IWMOAP, IWSCAP,IWSMS, MSMOAP, MSMPAP, MSMTAP belong to the subsystemSHS.Blocks GAP, GAP3, GRCHAP, MRCHAP, MSSNOAP and MTISTAPbelong to the subsystem MSS.Blocks MECAP, MHOAAP, MHOAAP2, MHOAAP3, MHONAP, MHONAP2and MHONAP3 belong to the subsystem MMS.Blocks MADAP, MDPAP, MFDAP, MHPNAP, MLCAP, MLUAP,MNMMAP,MPROIAP,MPSIAP, MRESTAP, MRNAP, MSECAP3, MSDAP, MSECAP, MSPUAP,MSRAP, MSSPAP, MTRAP, MUSSPAP,MRESIAP and MSMTIAP(handle onlycluster internal MAP messages) belong to the subsystemMDS.Position 12 is applicable only in Blade Cluster Environment.

Size of the variables.Position Size1 8 bits2−7,9−11 32 bits8 16 bits12 32 bits

5.53 SECURITYCNT


DID−name: SECURITYCNTDID−number: 131

Function: Counters for security handling

Position Contents 1 Number of request attempts for authentication parameters from HLR 2 Number of successful requests for



authentication parameters from HLR 3 Number of sent authentication requests 4 Number of successful authentications including check of SRES 5 Number of failed authentications due to invalid SRES 6 Number of authentication requests using used triplets 7 Number of ciphering mode setting attempts 8 Number of successful ciphering mode settings 9 Number of sent authentication requests with TMSI10 Number of failed authentications with TMSI due to invalid SRES11 Number of successful authentications with IMSI after failed TMSI authentication12 Number of TMSI reallocation attempts13 Number of unsuccessful TMSI reallocations14 Number of authentication request messages to PP15 Number of authentication reject messages received from PP16 Number of authentication reply messages received from PP17 Number of MM Cipher−Request message towards PP18 Number of MM cipher reject messages received as answer to the message MM cipher request19 Number of failed authentications due to invalid MAC20 Number of failed authentications due to resynchronisation

Description:All the variables are stored as common data.The size of the variables.Position Size1−6 R−declared7,8 16 bits9−13 R−declared14−18 16 bits19−20 R−declared

5.54 SSCNT


DID−name: SSCNTDID−number: 132

Function: Counters for supplementary services

Position Contents 1 SS identity 2 Number of SS−interrogations handled by VLR without MAP operation to HLR excluding operator1 and operator2 3 Number of SS−invocations excluding operator1 and operator2 4 Number of SS−interrogations made by subscribers from operator1 in MSC/VLR 5 Number of SS−interrogations made by subscribers from operator2 in MSC/VLR 6 Number of SS−invocations for subscribers from operator1 in MSC/VLR or in GMSC 7 Number of SS−invocations for subscribers from operator2 in MSC/VLR or in GMSC



8 Number of retrievals of held call excluding operator1 and operator2 in MSC/VLR 9 Number of retrievals of held call for subscribers from operator1 in MSC/VLR 10 Number of retrievals of held call for subscribers from operator2 in MSC/VLR 11 Number of successful SS−invocations excluding operator1 and operator2 12 Number of successful SS−invocations for subscribers from operator1 in MSC/VLR or in GMSC 13 Number of successful SS−invocations for subscribers from operator2 in MSC/VLR or in GMSC

Description:One record per supplementary service.All the variables (which are pointed out by theDID item positions) are stored in a record,the number of records = number of supplementaryservices in the block.The variables are stored as common data if the blockcontains counters for only one service.The supplementary services are identified by a codewhich will be translated to a slogan according toDID SSTAB.All counters are not relevant for all services.None of the counters are in more than one block.

Size of the variables.Position Size1 8 bits2 16 bits2−4 R−declared3 R−declared4−5 16 bits6−7 R−declared8−10 16 bits11−13 16 bits

5.55 BSCCNT


DID−name: BSCCNTDID−number: 133

Function: Counters for BSC statistics

Position Contents 1 Number handover required messages received 2 Number handover requests messages sent to the target BSC 3 Number of successful incoming handovers to the BSC 4 Number of successful outgoing handovers from the BSC 5 Number of successful internal intra BSS handovers (handover performed) 6 Number of received reset messages.

7 Number of A−interface circuit pool number mismatch per BSC at channel assignment completion or handover completion 8 Number of channel assignment failure or handover failure per BSC due to A−interface circuit pool mismatch reason 9 Number of channel assignment failure or handover failure per BSC due to A−interface



switch circuit pool reason10 Number of external intra BSS handover attempted per BSC for A−interface circuit pool handling reasons

11 Number of initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to FR.12 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to FR.13 Number of initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to HR.14 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to HR.15 Number of initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual FR.16 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual FR and FR assigned.17 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual FR and HR assigned.18 Number of initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual HR.19 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual HR and FR assigned.20 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual HR and HR assigned.21 Number of initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual.22 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual and FR assigned.23 Number of successful initial channel assignments per BSC with Channel Rate and Type in ASSIGNMENT REQUEST equal to Dual and HR assigned.24 Number of initial channel assignments with channel rate and type in ASSIGNMENT REQUEST indicating a multi−slot configuration25 Number of successful initial channel assignments with channel rate and type in ASSIGNMENT REQUEST indicating a multi−slot configuration

Description:One record per BSC in the blocks.The BSC file is size alterable (SAE 255). In practice it isnormal to have 50 records in the BSC file.The pointer for a BSC is the same in all blocks.This DID is associated to the translation DID BSCTAB whichis implemented in the subsystem MDS.

DIDINFO for positions 7 to 10 is associated with circuit pools forA−interface in MSC/VLR and is turned on by exchange dependantparameter.

DIDINFO for positions 11 to 20 is associated with Half Ratefunctionality which is turned on by exchange dependant parameter.



DIDINFO for positions 21 to 23 is associated with Speech Codersfunctionality which is turned on by exchange dependant parameter.

5.56 MTSMAPTAB

MTSMAPTAB −VALID FOR IOG/APG

DID−name: MTSMAPTABDID−number: 134

Function: MAP translation table for MTS

Position Contents 1 MAP operation identity (code) 2 Symbolic name of the MAP operation (slogan)

Description:This existing DID is now used for the translation from the MAP operation codes to the new MAP operation slogans as well. This translation is used for MAP operation statistics (DID: MTSMAPCNT).

The following table lists the new relations between codes, slogans, MAPoperations and blocks

Code Slogan MAP operations Blocksxxx RESETB1 ResetToBlade in sending entity MRESIAPxxx RESETB2 ResetToBlade in receiving entity MRESTAPxxx FWDSMB1 FwdSMtoBlade in sending entity MSMTIAPxxx FWDSMB2 FwdSMtoBlade in receiving entity MSMTAPxxx MTFSMB1 mt−FwdSMtoBlade in sending entity MSMTIAPxxx MTFSMB2 mt−FwdSMtoBlade in receiving entity MSMTAP

The codes will be assigned by the design of the IWD ’Data Interface Descriptions for Mobile Specific Traffic and Event Measurements in MSC/VLR, GMSC, SMS−GMSC and SMS−IWMSC’.Only the new blocks are listed in ’Application’.

The size of the variables.DID item position: 1 = 8 bitsDID item position: 2 =string 15 characters

5.57 SSTAB


DID−name: SSTABDID−number: 135

Function: Subscriber service translation table

Position Contents 1 SS identity (code) 2 Symbolic name of supplementary service (slogan)

Description:Translation from Supplementary Service code to SS−slogan.This translation is used for Supplementary Servicecounters (DID: SSCNT).



The relation between codes and operations is defined in andcontrolled by the document 6/155 19−1/APT 210 15/6 which waslast approved by PC−STS at revision PA3.

Size of the variables.Position Size1 8 bits2 String 7 characters

5.58 BSCTAB


DID−name: BSCTABDID−number: 136

Function: BSC translation table

Position Contents 1 State (undefined/defined) 2 Symbolic BSC name

Description:Translation from BSC pointer to symbolic name.State indicates whether the BSC is undefined (=0)or defined (=1).One record per BSC.DID position Size1 1 bit2 7 characters string

5.59 C7SCPERFCNT


DID−name: C7SCPERFCNTDID−number: 137

Function: Counters for SCCP Performance.

Position Contents 1 Routing Failure, No translation for address of such nature. 2 Routing Failure, No translation for this specific address. 3 Routing Failure, Subsystem failure. 4 Routing Failure, Unequipped user. 5 Routing Failure, Network Failure. 6 Routing Failure, Network Congestion. 7 Routing Failure, Unqualified. 8 Syntax error detected. 9 Total number of policed messages by the SCCP policing function.10 Number of not allowed messages by the SCCP policing function.

Description:All the variables are common stored data.

5.60 C7SCQOSCNT




DID−name: C7SCQOSCNTDID−number: 138

Function: Counters for SCCP Quality of service.

Position Contents 1 UDT messages sent to MTP. 2 UDTS messages sent to MTP. 3 UDT messages received from MTP. 4 UDTS messages received from MTP. 5 CR messages sent to MTP. 6 CREF messages sent to MTP. 7 CR messages received from MTP. 8 CREF messages received from MTP. 9 ERR messages sent to MTP.10 ERR messages received from MTP.11 XUDT messages sent to MTP12 XUDTS messages sent to MTP13 XUDT messages received from MTP14 XUDTS messages received from MTP15 LUDT messages sent to MTP16 LUDTS messages sent to MTP17 LUDT messages received from MTP18 LUDTS messages received from MTP


5.61 C7SCSSNUSECNT


DID−name: C7SCSSNUSECNTDID−number: 139

Function: Counters for SCCP Subsystem utilization.

Position Contents 1 State. 2 DT1 terminating per local SSN. 3 UDT/XUDT/LUDT terminating class 0 per local SSN. 4 UDT/XUDT/LUDT terminating class 1 per local SSN. 5 UDT/XUDT/LUDT originating class 0 per local SSN. 6 UDT/XUDT/LUDT originating class 1 per local SSN. 7 UDT originating class 1 per local SSN. 8 Total connection oriented messages originating per destination SSN. 9 Total connectionless messages originating per destination SSN. 10 Total incoming intermediate node connection oriented messages per destination SSN. 11 Total intermediate node connectionless messages per destination SSN. 12 Total outgoing intermediate node connection oriented messages per destination SSN.



13 Total connection oriented messages terminating per local SSN. 14 Total connectionless messages terminating per local SSN.

Description:Item position 1 is a state value to indicate if the recordinformation is valid (=1) or not (=0). That means if the SSNis defined or not.

5.62 C7SCUSECNT


DID−name: C7SCUSECNTDID−number: 140

Function: Counters for SCCP Utilization.

Position Contents 1 Total messages handled from local or remote subsystem. 2 Messages requiring global title translation. 3 Total messages sent for connectionless class 0. 4 Total messages sent for connectionless class 1. 5 Total messages received for connectionless class 0. 6 Total messages received for connectionless class 1. 7 Total number of simultaneous connection sections. 8 Total number of simultaneous buffers of 256 octets 9 Total number of simultaneous buffers of 512 octets10 Total number of simultaneous buffers of 1024 octets11 Total number of simultaneous buffers of 2048 octets


5.63 C7SCSIGPCNT


DID−name: C7SCSIGPCNTDID−number: 141

Function: Counter for messages sent to a backup node.

Position Contents 1 State 2 Messages sent a backup node.

Description:This DID is associated with the translation table



C7SCSPTAB.

DID position 1 indicates whether the individual isactive or inactive for ITU−T, China or JapanSCCP. Values are:

0 Invalid for ITU−T, China and Japan SCCP1 Defined for ITU−T or China SCCP2 Defined for Japan SCCP

5.64 C7SCSPTAB


DID−name: C7SCSPTABDID−number: 142

Function: Translation table for 14/16 or 24 bit signalling point.

Position Contents 1 Network Indicator 2 Signalling Point Code 3 Address string (NI−SPC) or (NI−MSA−SSA−CSP)

Description:Translation from signalling point pointer to networkaddress. Network address is designated as follow: NI−SPC

Example: 2−40

The Translation table SCCPFORMTAB will indicate whether aparticular switch will use the old format of adress string orthe new format using DID position 3 which contains up to16 BCD characters.The external address should be presented as:

NI−SPC or NI−MSA−SSA−CSP

The variables are stored in the record per signallingpoint in the block C7SM.

This translation table is associated to the DID C7SCSIGPCNT.The variables are specified in binary code.

5.65 C7TCMSGCNT


DID−name: C7TCMSGCNTDID−number: 143

Function: Counters for TCAP messages

Position Contents

1 Number of messages sent 2 Number of messages received

Description:One record per message type.All the variables (which are pointed out by the



DID item positions) are stored in record,the number of records = number of TCAP message typesThe TCAP message types are identified by the pointer.

This counter DID is associated to the translation tableC7TCMSGTAB.

5.66 C7TCCMPCNT


DID−name: C7TCCMPCNTDID−number: 144

Function: Counters for components

Position Contents

1 Number of components sent 2 Number of components received

Description:One record per component typeAll the variables (which are pointed out by theDID item positions) are stored in record,the number of records = number of component typesThe component types are identified by the pointer.

This counter DID is associated to the translation tableC7TCCMPTAB.

5.67 C7TCTOTAL


DID−name: C7TCTOTALDID−number: 145

Function: TCAP Utilization Measurements

Position Contents 1 Total number of simultaneous TCAP dialogue individuals 2 Total number of simultaneous TCAP operations 3 Total number of simultaneous TCAP buffers


5.68 C7TCABOCNT


DID−name: C7TCABOCNTDID−number: 146

Function: Counters for protocol errors in transaction portion



Position Contents 1 Number of P−Abort messages sent 2 Number of P−Abort messages received 3 Number of protocol error situations not resulting in abort sending

Description:One record per P−Abort causeAll the variables (which are pointed out by theDID item positions) are stored in record,the number of records = number of P−Abort causesThe P−Abort causes are identified by the pointer.

This counter DID is associated to the translation tableC7TCABOTAB.

The size of the variablesPosition Size 1−3 32−bit

5.69 C7TCREJCNT


DID−name: C7TCREJCNTDID−number: 147

Function: Counters for protocol errors in component portion

Position Contents 1 Number of situations when protocol error is detected by TCAP 2 Number of rejects sent by TC−user 3 Number of rejects received by TC−user

Description:One record per problem code.All the variables (which are pointed out by theDID item positions) are stored in record,the number of records = number of problem codesThe problem codes are identified by the pointer.

This counter DID is associated to the translation tableC7TCREJTAB.

The size of the variablesPosition Size 1−3 32−bit

5.70 C7TCMSGTAB


DID−name: C7TCMSGTABDID−number: 148

Function: Translation table for message types,

Position Contents 1 Symbolic name of the message type (slogan)



Description:This translation table is associated to the DID, C7TCMSGCNT.

Relation between slogans and message types:

Slogan Message type

1 BEGINM Begin message2 CONTINM Continue message3 ENDM End message4 UABORTM U−abort message5 PABORTM P−abort message6 UNIM Uni message7 MRETURN Message Return

5.71 C7TCCMPTAB


DID−name: C7TCCMPTABDID−number: 149

Function: Translation table for component types,

Position Contents 1 Symbolic name of the component type (slogan)

This translation table is associated to the DID, C7TCCMPCNT.

Relation between slogans and component types:

Slogan Component type

1 INVOKE Invoke2 RESULT Result3 REJECT Reject4 ERROR Error

5.72 C7TCABOTAB


DID−name: C7TCABOTABDID−number: 150

Function: Translation table for P−Abort causes,

Position Contents 1 Symbolic name of the P−Abort cause (slogan)

This translation table is associated to the DID, C7TCABOCNT.

Relation between slogans and P−Abort causes:

Slogan P−Abort cause

1 URECMST Unrecognized message type2 INCORTP Incorrect TP3 BFORMTP Badly formatted TP4 URECTID Unrecognized TID



5 RESLIM Resource limitation

5.73 C7TCREJTAB


DID−name: C7TCREJTABDID−number: 151

Function: Translation table for problem codes

Position Contents 1 Symbolic name of the problem code (slogan)

This translation table is associated to the DID, C7TCREJCNT.

Relation between slogans and problem codes:

Slogan Problem code

1 UNRECC Unrecognized component 2 MISTC Mistyped component 3 BSTRUCC Badly structured component 4 URECLI Unrecognized linked ID 5 URECII Unrecognized invoked ID 6 RRUNEXP Return result (RR) unexpected 7 REURECI Unrecognized invoked ID (RE) 8 REUNEXP Return error (RE) unexpected 9 URECREJ Unrecognised invoked ID (Reject Problem)10 DUPLII Duplicate invoke ID11 URECOP Unrecognized operation12 MISTP Mistyped parameter13 RESLIM Resource limitation14 INITREL Initiating release15 LREUEXP Linked response unexpected16 UEXPLOP Unexpected linked operation17 URECE Unrecognized error18 UEXPE Unexpected error19 MISTPRR Mistyped parameter, return result20 MISTPRE Mistyped parameter, return error

Slogans 1−8 belong to TCAP problem codes.Slogans 9−19 belong to TC−user problem codes.

5.74 C7SL1CNT


DID−name: C7SL1CNTDID−number: 152

Function: Counters on the signalling link level

Position Contents 1 State 2 Duration of link in In−Service state in seconds 3 Number of occurances of SL Alignment or Proving failure 4 Number of signal units in error or



Number of normalised signal units in error 5 Number of negative acks. received 6 Number of occurances of local automatic changeover 7 Duration of SL unavailability (all reasons) in seconds 8 Duration of SL inhibition due to local mgt. action in seconds 9 Duration of SL inhibition due to remote mgt. action in seconds10 Duration of SL unavailability due to link failure in seconds11 Duration of SL unavailability due to remote P.O. in seconds12 Number of occurances of Local Mgt. Inhibit13 Number of occurances of Local Mgt. Uninhibit14 Duration of local busy in 100 ms units15 Number of SIF and SIO octets transmitted16 Number of occurances of octets retransmitted17 Number of MSU’s transmitted18 Number of SIF and SIO octets received19 Number of MSU’s received

Description:To identify these counters the DID C7SLTAB is required.One record per signalling link (1−1022).Records are identified by signalling link pointer (SLP).DID position 1 indicates whether the individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTP.

5.75 C7SL2CNT


DID−name: C7SL2CNTDID−number: 153

Function: Counters on the signalling link level.

Position Contents 1 State 2 Number of SL congestion indications level 1 3 Number of SL congestion indications level 2 4 Number of SL congestion indications level 3 5 Cumulative duration



of SL congestion level 1 in seconds 6 Cumulative duration of SL congestion level 2 in seconds 7 Cumulative duration of SL congestion level 3 in seconds 8 Number of MSU’s discarded due to SL congestion level 1 9 Number of MSU’s discarded due to SL congestion level 2 10 Number of MSU’s discarded due to SL congestion level 3 11 Number of congestion events resulting in loss of MSU’s level 1 12 Number of congestion events resulting in loss of MSU’s level 2 13 Number of congestion events resulting in loss of MSU’s level 3 14 Number of indications of stop of SL congestion level 1 15 Number of indications of stop of SL congestion level 2 16 Number of indications of stop of SL congestion level 3

Description:To identify these counters DID C7SLTAB is required.One record per signalling link (1−1022).Records are identified by signalling link pointer (SLP).

DID position 1 indicates whether the individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTPDID item positions 8, 9, 10, 11, 12 and 13 are not valid forHSL neither for ATM.

5.76 C7SLTAB


DID−name: C7SLTABDID−number: 154

Function: Translation table between signalling link pointers and network addresses

Position Contents

1 Network Indicator 2 Signalling Point Code 3 Signalling Link Code 4 Address string

Description:One record per signalling link (1−1022).Records are identified by signalling link pointer (SLP).NI has the range 0 upto 3.



SPC has the range 0 up to 16383 when Type of MTP is C7MTP,and the range 0 up to 65535 when Type of MTP is J7MTP.SLC has the range 0 up to 15.

The output will look as follows:NI−SPC−SLC1−75−4DID position 4 will have a value of ’1A75A4FFFFFFFFFF’for the above network address.

5.77 C7SLSETCNT


DID−name: C7SLSETCNTDID−number: 155

Function: Counters on the signalling linkset level

Application: CDMA, GSM, WCDMA Block: C7LS2, J7LS

DID item Contentsposition 1 State 2 Duration of unavailability of signalling linkset in seconds 3 Number of links in the link set not available for traffic 4 Level of links in the link set not available for traffic

Description:To identify these counters DID C7SLSETTAB is required.One record per linkset (1−1022).Records are identified by signalling linkset pointer (LSP).

Position 1 indicates whether the individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTP

The size of the variables:

Positions Block Size1 C7LS2, J7LS 2 bits2 C7LS2, J7LS 16 bits3 C7LS2 16 bits4 C7LS2 16 bits

5.78 C7SLSETTAB


DID−name: C7SLSETTABDID−number: 156

Function: Translation table between signalling linkset pointers and network addresses

Position Contents 1 Network Indicator



2 Signalling Point Code 3 Address string

Description:One record per linkset (1−1022).Records are identified by signalling linkset pointer (LSP).NI has the range 0 upto 3.SPC has the range 0 upto 16383 when Type of MTP is C7MTP,and the range 0 upto 65535 when Type of MTP is J7MTP.

The output will look as follows:NI−SPC1−75DID position 3 will have a value of ’1A75FFFFFFFFFFFF’for the above network address.

5.79 C7RTSETCNT


DID−name: C7RTSETCNTDID−number: 157

Function: Counters on the signalling routeset level

Position Contents 1 State 2 Number of occurances of unavailability of route set to a given destination or set of destinations 3 Duration of unavailability of routeset to a given destination or set of destinations in seconds.

Description:To identify these counters the DID C7SPTAB is required.One record per signalling point (16−4095,a total of 4080records including record 16).Records 0−15 will not be the used since they are definedfor OWNSP.No counters will be stored in these records.Records are identified by signalling point pointer (SPP).Individuals are identified by signalling network address.DID position 1 indicates whether individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTP

5.80 C7SPTAB


DID−name: C7SPTABDID−number: 158

Function: Translation table between signalling point pointers and network addresses

Position Contents 1 Network Indicator 2 Signalling Point Code



3 Address string

Description:One record per signalling point (16−4095,a total of 4080records including record 16).Records 0−15 will not be the used since they are definedfor OWNSP.Individuals are identified by signalling network address.Records are identified by signalling point pointer (SPP).NI has the range 0 upto 3.SPC has the range 0 upto 16383 when Type of MTP is C7MTP,and the range 0 upto 65535 when Type of MTP is J7MTP.

The output will look as follows:NI−SPC1−75DID position 3 will have a value of ’1A75FFFFFFFFFFFF’for the above network address.

5.81 C7ADJSLPCNT


DID−name: C7ADJSLPCNTDID−number: 159

Function: Counters for an adjacent signalling point

Position Contents 1 State 2 Number of times that adjacent SP becomes inaccessible 3 Duration of adjacent SP inaccessible in seconds

Description:One record per linkset (1−1022).Records are identified by linkset pointer (LSP).Individuals are identified by signalling network address.DID position 1 is a 1 bit variable.DID positions 2 and 3 are 16 bit variables.DID position 1 indicates whether the individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTP

The linkset pointer is used to access the translationtable C7SLSETTAB.

5.82 C7OPCCNT


DID−name: C7OPCCNTDID−number: 160

Function: Counters for a given OPC

Position Contents 1 State 2 Number of SIF and SIO octets received with



given OPC

Description:To identify these counters DID C7OPCTAB is required.Records are identified by counter record pointer (CPTR1)Individuals are identified by signalling network address.There are 128 records (each counter type can be definedup to 128 times).The record pointer is translatedinto the counter addresses which are in C7OPCTAB.

DID position 1 indicates whether the individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTP

5.83 C7OPCTAB


DID−name: C7OPCTABDID−number: 161

Function: Translation table between record pointers of DID position 2 in DID "C7OPCCNT" and network addresses

Position Contents 1 Network Indicator 2 Originating Point Code 3 Address string

Description:Records are identified by counter record pointer (CPTR1).Individuals are identified by signalling network address.NI has the range 0 upto 3.OPC has the range 0 upto 16383 when Type of MTP is C7MTP,and a range 0 upto 65535 when Type of MTP is J7MTP.

The output will look as follows:NI−OPC1−75DID position 3 will have a value of ’1A75FFFFFFFFFFFF’for the above network address.

5.84 C7DPCCNT


DID−name: C7DPCCNTDID−number: 162

Function: Counters for a given DPC

Position Contents

1 State 2 Number of SIF and SIO octets transmitted with given DPC

Description:To identify these counters DID C7DPCTAB is required.



Records are identified by counter record pointer (CPTR2).Individuals are identified by signalling network address.There are 128 records (each counter type can be definedupto 128 times).The record pointer is translatedinto the counter addresses which are in C7DPCTAB.


5.85 C7DPCTAB


DID−name: C7DPCTABDID−number: 163

Function: Translation table between record pointers of DID position 2 in DID "C7DPCCNT" and network addresses

Position Contents 1 Network Indicator 2 Destination Point Code 3 Address string

Description:Records are identified by counter record pointer (CPTR2).Individuals are identified by signalling network address.NI has the range 0 upto 3.DPC has the range 0 upto 16383 when Type of MTP is C7MTPand a range 0 upto 65535 when Type of MTP is J7MTP.

The output will look as follows:NI−DPC1−75DID position 3 will have a value of ’1A75FFFFFFFFFFFF’ forthe above network address.

5.86 C7SIOCNT


DID−name: C7SIOCNTDID−number: 164

Function: Counters for given SI

Position Contents 1 State 2 Number of SIF and SIO octets handled (received and transmitted) with given SI.

Description:There are 32 records.ITU−T and China use 16 of the recordsand Japan the remaining 16.Records are identified by counter record pointer (SIOPTR).Individuals are identified by SI and MTP variant.

DID position 1 indicates whether the individual is active orinactive for ITU−T, China or Japan MTP. Values are:



0 Invalid for both ITU−T, China and Japan MTP1 Defined for ITU−T or China MTP2 Defined for Japan MTP

5.87 C7OPCSIOCNT


DID−name: C7OPCSIOCNTDID−number: 165

Function: Counters for given OPC+SIO

Position Contents 1 State 2 Number of SIF and SIO octets received with given OPC+SIO

Description:To identify these counters DID C7OPCSIOTAB is required.Records are identified by counter record pointer (CPTR4).Individuals are identified by signalling network address.There are 128 records (each counter type can be definedupto 128 times).The record pointer is translatedinto the counter addresses which are in C7OPCSIOTAB.


5.88 C7OPCSIOTAB


DID−name: C7OPCSIOTABDID−number: 166

Function: Translation table between record pointers of DID position 2 in DID "C7OPCSIOCNT" and network addresses

Position Contents 1 Network Indicator 2 Originating Point Code 3 Service Indicator 4 Address string

Description:Records are identified by counter record pointer (CPTR4).Individuals are identified by signalling network address.NI has the range 0 upto 3.OPC has the range 0 upto 16383 when Type of MTP is C7MTPand range 0 upto 65535 when Type of MTP is J7MTP.SI has the range 0 upto 15.

The output will look as follows:NI OPC SI1−75−5DID position 4 will have a value of ’1A75A5FFFFFFFFFF’for the above network address.



5.89 C7DPCSIOCNT


DID−name: C7DPCSIOCNTDID−number: 167

Function: Counters for given DPC+SIO

Position Contents 1 State 2 Number of SIF and SIO octets transmitted with given DPC and SIO

Description:To identify these counters DID C7DPCSIOTAB is required.Records are identified by counter record pointer (CPTR5).Individuals are identified by signalling network address.There are 128 records (each counter type can be definedupto 128 times).The record pointer is translatedinto the counter addresses which are in C7DPCSIOTAB.DID position 1 indicates whether the individual is active orinactive for C7MTP or J7MTP, values are:0 Invalid for C7MTP or J7MTP1 Defined for C7MTP2 Defined for J7MTP

5.90 C7DPCSIOTAB


DID−name: C7DPCSIOTABDID−number: 168

Function: Translation table between record pointers in DID position 2 in DID "C7DPCSIOCNT" and network addresses

Position Contents

1 Network Indicator 2 Destination Point Code 3 Service Indicator 4 Address string

Description:Records are identified by counter record pointer (CPTR5).Individuals are identified by signalling network address.NI has the range 0 upto 3.DPC has the range 0 upto 16383 when Type of MTP is C7MTPand range 0 upto 65535 when Type of MTP is J7MTP.SI has the range 0 upto 15.

The output will look as follows:NI−DPC−SI1−75−5DID position 4 will have a value of ’1A75A5FFFFFFFFFF’ forthe above network address.



5.91 C7ODSCNT


DID−name: C7ODSCNTDID−number: 169

Function: Counters for given OPC+DPC+SIO

Position Contents

1 State 2 LS/NI (network indicator of linkset) 3 LS/SPC (signalling point code of linkset) 4 Number of SIF and SIO Octets handled with given OPC+DPC+SIO (with the option to specify an incoming LS).

Description:To identify these counters DID C7ODSTAB is required.Records are identified bu counter record pointer (CPTR6).Individuals are identified by signalling network address.There are 128 records (each counter type can be definedupto 128 times).The record pointer is translatedinto the counter addresses which are in C7ODSTAB.LS/NI has the range 0 upto 3.LS/SPC has the range 0 upto 16383.


5.92 C7ODSTAB


DID−name: C7ODSTABDID−number: 170

Function: Translation table between record pointers in DID position 2 in DID "C7ODSCNT" and network addresses

Position Contents 1 Network Indictor 2 Originating Point Code 3 Destination Point Code 4 Service Indicator 5 Address string

Description:Records are identified by counter record pointer (CPTR6).Individuals are identified by signalling network address.NI has the range 0 upto 3.OPC has the range 0 upto 16383 when Type of MTP is C7MTP,and range 0 upto 65535 when Type of MTP is J7MTP.DPC has the range 0 upto 16383 when Type of MTP is C7MTP,and range 0 upto 65535 when Type of MTP is J7MTP.SI has the range 0 upto 15.

The output will look as follows:



NI−OPC−DPC−SI LS/NI LS/SPC Counter name0−16383−16383−15 1 16383 123DID position 5 will have a value of ’0A16383A16383A15’ forthe above network address.

5.93 C7RTTOTALCNT


DID−name: C7RTTOTALCNTDID−number: 171

Function: This is a system total counter for counting of routing error.

Position Contents 1 Number of occurances of MSU discarded due to a routing error.

Description:This is a system total of C7 and J7 where applicable.

5.94 SESSSFCNT


DID−name: SESSSFCNTDID−number: 174

Function: Counters indicating the performance of the of the TCAP−Interface to/from the Service Switching Point (SSP) in the Intelligent Network.

DID−item Contents 1 Number of Dialogues in progress 2 Number of Dialogue Initiation Attempts 3 Number of Dialogue Initiation Attempts with congestion 4 Total number of Dialogues processed 5 Number of unsuccessful Dialogues, Message not accepted by TCAP 6 Number of unsuccessful Dialogues, Aborted by SCF or remote TCAP 7 Number of unsuccessful Dialogues, Aborted locally by SSF 8 Number of unsuccessful Dialouges, Timeout on response 9 Number of unsuccessful Dialogues, Activity Test failed10 Number of unsuccessful Dialouges, Error or Reject messages received from SCP11 Number of Error or Reject messages sent by SSP12 Number of message sending requests rejected by Protocol Adaption

Description:All counters are stored as common data.

5.95 DIPQCNT1




DID−name: DIPQCNT1DID−number: 175

Function: Digital paths quality counters.

Position Contents

1 CNTSTATE 2 Global DIP−number 3 Bitfaults Frequency 4 Number of Slips 5 Number of Disturbances

Description:Item pos 1 CNTSTATE, gives information whether DIPQCNT1 isrelevant (1=relevant, DIP is connected and has noCRC−supervision).One record per chosen DIP in STS.All the variables (which are pointed out by the DID itempositions) are stored in a record. Record individuals 0−2687can be used.This DID is associated to the translation DID, DIPTAB.

5.96 DIPQCNT2



Function: Digital paths quality CRC counters.

Position Contents

1 CNT1STATE 2 Global DIP−number 3 Number of Errored Seconds 4 Number of Severly Erroed Seconds 5 Number of Degraded Minutes 6 Number of Unavailable Seconds 7 Number of Errored Seconds Remote end 8 Number of Severly Errored Seconds Remote end 9 Number of Degraded Minutes Remote end 10 Number of Unavailable Seconds Remote end 11 Number of Unavailability Events 12 Number of Unavailable Seconds bi−directional, Unavailable Time 13 Number of suspect−marked 15−minute intervals 14 Number of slips 15 Number of unavailable events at local end 16 Number of unavailable events from remote end

Description:Item pos 1 CNT1STATE, gives information whether DIPQCNT2 isrelevant (1=relevant, DIP is connected and hasCRC−supervision).One record per chosen DIP in STS.All the variables (which are pointed out by the DID itempositions) are stored in a record. Record individuals 0−2687



can be used.This DID is associated to the translation DID, DIPTAB.

DID item position 2 is a pointer to the translation table(DID DIPTAB)

NOTE. Counter DID position 5 is not supported by US local mobility PCS application

5.97 DIPTAB


DID−name: DIPTABDID−number: 177

Function: Digital paths symbolic DIP−name.

Position Contents1 Symbolic DIP−name.

Description:Translation from DIP global number to DIP symbolic number.

One record per DIP. Pointer equals to global DIP number.

All the variables (which are pointed out by the DID itempositions) are stored in a record. Record individuals 0−2687can be used.

5.98 CELLTAB


DID−name: CELLTABDID−number: 191

Function: Cell translation table

Position Contents

1 State 2 Symbolic cell name 3 Cell Type

Description:Translation from cell pointer to symbolic name.Item position 1 is a state value indicating: − cell not defined (=0) − cell defined, own cell (=1)Item position 2 can be either the identity of the targetcell or of the serving cell.Item position 3 indicates whether the cell is an owncell (=0) or an outer cell (=1).A cell has always the same name regardless if it is aserving or a target cell.One record per cell.

5.99 CELLCNT




DID−name: CELLCNTDID−number: 192

Function: Counters for cell level statistics.

Position Contents 1 State 2 Target cell identity 3 Number of handover attempts to the target cell from unknown serving cells 4 Number of successful handovers to the target cell from unknown serving cells 5 Number of handover attempts to the target cell from unspecified neighbouring serving cells 6 Number of successful handovers to the target cell from unspecified neighbouring serving cells 7 Not used 8 Not used 9 Not used10 Not used

Description:The cell statistics files in block MHO has alimited size, with a maximum number of 1000 records.Each cell with statistics defined has one record in thecell statistics file of block MHO.

DID item position 1 is a state value indicating: − Counter has not been stepped, not valid for statistics − Counter has been used, valid for statisticsDID item position 2 refers to a pointer located in the cellstatistics records. This variable is used to indicate thesuitable record in the cell conversion file in MTRAN.Translation from cell pointer to symbolic cell name isdefined in the DID CELLTAB.

Item positions 3 and 4 include the number of (GSM to GSM)handovers from a serving cell not known by the MSC/VLR.Item positions 5 and 6 include the number of (GSM to GSM)handovers from a serving cell known by the MSC/VLR, butwhich could not be included in the neighbouring cellstatistics file of MHO.

Item positions 7, 8, 9, 10 are not used anymore.

The size of the variables.DID position Block Size1 MHO 1 bit2 MHO 32 bits3 MHO 32 bits4 MHO 32 bits5 MHO 32 bits6 MHO 32 bits7 not used8 not used9 not used10 not used

5.100 EIRCNT




DID−name: EIRCNTDID−number: 193

Function: Counters for equipment identity control

Position Contents

1 Number of IMEI fetch attempts towards MS’s 2 Number of successful IMEI fetches from MS’s 3 Number of IMEI check attempts towards EIR 4 Number of IMEI check results from EIR where ’white listed’ indicated 5 Number of IMEI check results from EIR where ’black listed’ indicated 6 Number of IMEI check results from EIR where ’grey listed’ indicated 7 Number of IMEI check results from EIR where ’unknown’ indicated


5.101 HLRTAB


DID−name: HLRTABDID−number: 194

Function: HLR translation table

Position Contents

1 State (undefined/defined) 2 HLR nature of address indicator 3 HLR address 1 4 HLR address 2 5 HLR address 3 6 HLR address 4

Description:Translation from HLR pointer to HLR address.This translation is used for counters on HLRlevel (DID: MOBSUBHLRCNT)State indicates whether the HLR is undefined (=0)or defined (=1).One record per HLR. In practice, it is conceivable tohave 80 records in the HLR address file.Item position 2 contains the nature of HLR address:3 = national or 4 = international.Items position 3−6 include a unique address (15 digits).Example:

The number 356 will be delivered as Did item position 2 3 3 FF65 4 FFFF 5 FFFF 6 FFFF

The number 48769054 will be delivered as Did item position 2 4



3 9678 4 F450 5 FFFF 6 FFFF

5.102 LACNT


DID−name: LACNTDID−number: 195

Function: Counters for location area statistics

DID item Contentsposition 1 Number of first page attempts to an LA 2 Number of repeated page attempts to an LA 3 Number of page responses to first page to an LA 4 Number of page responses to repeated page to an LA 5 Number of unsuccessful page responses to an LA 6 Number of location updating rejections due to the CSS restriction 7 Total number of location updating attempts 8 Number of successful location updatings 9 Number of location updating rejections due to Partial Roaming.10 Number of normal location updating attempts for already registered subscribers over A and Iu−interface11 Number of successful normal location updatings for already registered subscribers over A and Iu−interface12 Number of normal location updatings for non−registered subscribers over A and Iuinterface13 Number of successful normal location updatings for non−registered subscribers over A and Iu−interface14 Number of IMSI attached location updatings for already registered subscribers over A and Iu−interface15 Number of successful IMSI attached location updatings for already registered subscribers over A and Iu−interface16 Number of periodic location updatings over A and Iu−interface17 Number of successful periodic location updatings over A and Iu−interface18 Number of normal location updatings for already registered subscribers over Gsinterface19 Number of successful normal location updatings for already registered subscribers over Gs−interface20 Number of IMSI attached location updatings for already registered subscribers over Gs−interface21 Number of successful IMSI attached location updatings for already registered subscribers over Gs−interface22 Total number of location updating attempts on intermediate MSC−blade after failed authentication with TMSI23 Number of normal location updating



attempts for already registered subscribers over A and IU−interface on intermediate MSC−blade after failed authentication with TMSI24 Number of normal location updatings for non−registered subscribers over A and Iu−interface on intermediate MSC−blade after failed authentication with TMSI25 Number of IMSI attached location updatings for already registered subscriber over A and Iu−interface on intermediate MSC−blade after failed authentication with TMSI

Description:One record per location area in the blocks.The size of the LA file depends on the number oflocation areas in one MSC. In practice, it is conceivableto have 50 LAs handled by a MSC.The record pointer of the LA file is the same in allblocks (MPAG, MMMCS, MMMLR, MGPRO and MVLRP) and correspondswith the pointer in the MBSSD translation table (DID: LATAB).

The size of the variables.DID position Block Size1−4 MPAG 32 bits5 MMMCS 32 bits6 MVLRP 32 bits7−9 MMMLR 32 bits10 MVLRP 32 bits11 MMMLR 32 bits12 MVLRP 32 bits13 MMMLR 32 bits14 MVLRP 32 bits15−17 MMMLR 32 bits18−21 MGPRO 32 bits22 MMMLR 32 bits23−25 MVLRP 32 bits

5.103 LATAB


DID−name: LATABDID−number: 196

Function: LA translation table

Position Contents

1 State (undefined/defined) 2 LAI 1 3 LAI 2 4 LAI 3 5 LAI 4

Description:Translation from LA pointer to LAI.This translation is used for statistics on locationarea level (DID: LACNT).State indicates whether the LA is undefined (=0)or defined (=1).One record per LA. It is conceivable to have 50 recordsin the LA file.



Items position 2−4 include a unique LAI (max 9 digits).Item position 2 refers to the MCC: Mobile Country Code.Item position 3 refers to the MNC: Mobile Network Code.Item positions 4 and 5 refer to the LAC: Location Area Code.

Example:The number 4631956223 will be delivered as follows: DID item position 2 F364 3 91 4 2265 5 FFF3

5.104 MOBSUBHLRCNT


DID−name: MOBSUBHLRCNTDID−number: 197

Function: Counters for registered mobile subscribers on HLR level.

Position Contents 1 State 2 Number of registered mobile subscribers per HLR 3 Number of registered attached subscribers per HLR 4* Number of registered mobile subscribers per HLR, with GSM as last access type stored in VLR 5* Number of registered attached subscribers per HLR, with GSM as last access type stored in VLR 6* Number of registered mobile subscribers per HLR, with WCDMA as last access type stored in VLR 7* Number of registered attached subscribers per HLR, with WCDMA as last access type stored in VLR

POSITIONS MARKED * NOT IMPLEMENTED ON IOG

Description:One record per HLR in MTV. The size of the HLR file depends on the number of HLRs, a conceivable number is 80 records for this file. State indicates whether statistics are defined for the HLR (=1)or not.State is set to ’1’ when one of the counters is stepped the first time. It is never reset except at large restart. The record pointer used for the HLR file is the same as the pointer of the HLR translation table in MHLRAD. The difference between the total registered mobile subscribers per HLR and the sum of registered mobile subscribers per HLR with GSM and WCDMA last access type stored in VLR reflects the number of mobile subscribers per HLR with no valid access type yet stored in VLR (e.g the case of subscriber registration in VLR due to PRN but with no radio contact established yet). The same applies for the registered attached subscribers per HLR.The block MTV belongs to the subsystem MDS.

The size of the variables:DID position Block Size1 MTV 1 bit2 MTV 32 bits3 MTV 32 bits



4 MTV 32 bits5 MTV 32 bits6 MTV 32 bits7 MTV 32 bits

5.105 MSCTAB


DID−name: MSCTABDID−number: 198

Function: MSC translation table

Position Contents 1 State (undefined/defined) 2 Symbolic MSC name

Description:Translation from MSC pointer to symbolic name.This translation is required for statistics onneighbouring MSC level (DID: NBRMSCLCNT, NBRMSCPROCCNT,NBRMSCSRNSCNT, NBRMSCGUHCNT, NMSCUGHOCNT, NBRMSCL3CNT).State indicates whether the MSC is undefined (=0)or defined (=1).One record per MSC.The size of the variables:DID position Block Size1 MTRAN 1 bit2 MTRAN String 7 characters

5.106 NBRCELLCNT


DID−name: NBRCELLCNT (MSC)DID−number: 199

Function: Counters for neighbouring cell level statistics.

DID item Contentsposition 1 State 2 Serving cell identity 3 Target cell identity 4 Number of handover attempts to the target cell from this serving cell 5 Number of successful handovers to the target cell from this serving cell 6 Not used 7 Not used

Description:The neighbouring cell statistics file has a limited size.Each cell with statistics defined has a max. number ofneighbouring cells defined by command.This number is a multiple of 8.The sum of these values for all cells will correspondto the number of records in the neighbouring cellstatistics file. The maximum number of records in this fileis 8000.DID item position 1 is a state value indicating:



− counter has not been stepped, not valid for statistics (=0) − counter has been used, valid for statistics (=1)DID item positions 2 and 3 are two pointers used to indicatethe suitable record in the cell conversion file in MTRAN.(DID: CELLTAB)

The size of the variables.DID position Block Size1 MHO 1 bit2 MHO 32 bits3 MHO 32 bits4 MHO 32 bits5 MHO 32 bits6 Not used7 Not used

5.107 NBRMSCLCNT


DID−name: NBRMSCLCNTDID−number: 200

Function: Counters for UMTS to GSM inter−MSC handover on neighbouring MSC level

Position Contents

1 Number of basic handover attempts to neighbouring MSC 2 Number of successful basic handovers per MSC to neighbouring MSC 3 Number of subsequent handover attempts from neighbouring MSC back to anchor MSC 4 Number of successful subsequent handovers from neighbouring MSC back to anchor MSC per serving MSC 5 Number of subsequent handover attempts from neighbouring MSC to third MSC The target MSC is the measurement object. 6 Number of successful subsequent handovers from neighbouring MSC to third MSC. The target MSC is the measurement object. 7 Number of incoming handover attempts from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neigh− bouring MSC) 8 Number of successful incoming hando− vers from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neigh− bouring MSC) 9 Number of subsequent handover attempts to neighbouring MSC (back to anchor or to third MSC)10 Number of successful subsequent handovers to neighbouring MSC (back to anchor or to third MSC per target MSC)11 Number of basic handover attempts from SDCCH to TCH12 Number of successful basic handovers from SDCCH to TCH



13 Number of basic handover attempts on TCH before through connection14 Number of successful basic handovers on TCH before through connection15 Number of basic handover attempts on signalling channels to neighbouring MSC16 Number of successful basic handovers on signalling channels to neighbouring MSC17 Number of subsequent handover attempts on signalling channels, from neighbouring MSC back to anchor MSC, per serving MSC18 Number of successful subsequent handovers on signalling channels, from neighbouring MSC back to anchor MSC, per serving MSC19 Number of subsequent handover attempts on signalling channels, from neighbouring MSC to third MSC. The target MSC is the measurement object.20 Number of successful subsequent handovers on signalling channels, from neighbouring MSC to third MSC. The target MSC is the measurement object.21 Number of incoming handover attempts on signalling channels from neighbouring MSC. (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC)22 Number of successful incoming handovers on signalling channels from neighbouring MSC. (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC)23 Number of subsequent handover attempts on signalling channels to neighbouring MSC. (back to anchor or to third MSC)24 Number of successful subsequent handovers on signalling channels to neighbouring MSC. (back to anchor or to third MSC)25 Number of neighbouring Handovers with Synchronous errors.

Description:One record per neighbouring MSC in the blocks. Inpractice, it is conceivable for one particular MSC tohave 5 neighbours.The pointer for MSC is the same in all blocks.

5.108 SMSCNT


DID−name: SMSCNTDID−number: 201

Function: Counters for short message service

Position Contents 1 Number of requests for short message delivery towards MSs 2 Number of successful short message deliveries towards MSs 3 Number of sent short messages towards MSs 4 Number of successful short message transfers towards MSs 5 Number of requests for short message delivery from MSs



6 Number of successful short message deliveries from MSs 7 Number of received short messages from MSs 8 Number of successful short message transfers from MSs 9 Number of requests for short message memory available from MSs received in MSC/VLR10 Number of not accepted MAP V2 operation ReadyForSM to HLR with alert reason memory available.11 Number of Broadcastmessage attempted successfully from Message Centre12 Number of Unsuccessful Broadcast processed13 Number of not accepted MAP V3 operation ReadyForSM to HLR with alert reason memory available14* Number of requests for originating short message deliveries from an MS. The counter is incremented when MSC receives CM Service Request sent by BS of idle subscribers indicating it is a SMS MO service message, or MSC receives ADDS Transfer message that BS sends SMS over access channel indicating it is an MS originating SMS.15 Number of MO−SMS redirections to a new SC Address due to destination based routing.



Size of variables:DID position Block Size1 − 4 MSMT 32 bits5 − 9 MSMO 32 bits10 MSMPAP 32 bits11 − 12 MSSMS 16 bits13 MSMPAP 32 bits14 MRRM 16 bits15 MSMO 32 bits

5.109 C7TCDIACNT


DID−name: C7TCDIACNTDID−number: 257

Function: Counters for Dialogue Portions

Position Contents

1 Number of Dialogue Portions sent 2 Number of Dialogue Portions received

Description:One record per Dialogue Portion type.All the variables (which are pointed out by theDID item positions) are stored in a record,the number of records = number of Dialogue Portion typesThe Dialogue Portion types are identified by the pointer.

This counter DID is associated to the translation table



C7TCDIATAB.

5.110 C7TCDIATAB


DID−name: C7TCDIATABDID−number: 258

Function: Translation table for Dialogue Portion types.

Position Contents

1 Symbolic name of the Dialogue Portion type (slogan)

This translation table is associated to the DID, C7TCDIACNT.

Relation between slogans and Dialogue Portion types:

Slogan Dialogue Portion type

1 AARQ AARQ APDU2 AARE AARE APDU3 ABRT ABRT APDU4 AUDT AUDT APDU5 USRINF User Information

5.111 GSMSCCNT


DID−name: GSMSCCNTDID−number: 261

Function: Counters for short messages in SMS−GMSC.

Position Contents

1 Total number of mobile terminated short messages in SMS−GMSC 2 Number of successful mobile terminated short messages in SMS−GMSC 3 Unsuccessful use of MAP version 2 for SM transfer pipeline


5.112 IWSMSCCNT


DID−name: IWSMSCCNTDID−number: 263

Function: Counters for short messages in SMS−IWMSC.



Position Contents

1 Total number of mobile originated short messages in SMS−IWMSC 2 Number of successful mobile originated short messages in SMS−IWMSC


5.113 MTSFBCNT


DID−name: MTSFBCNTDID−number: 264

Function: Counters for MTS MAP V2 operation Fall Back statistics for Application Contexts (AC).

Position Contents

1 AC Identity (code) 2 Number of fall backs for an Application Context

Description:One record per Application Context(the number of records = number of Application Contexts inthe block).The variables are stored as common data if the blockcontains only one Application Context.The Application Contexts are identified by a code.(DID: MTSFBTAB).

Size of the variables.Position Size1 8 bits2 R−declared

5.114 MTSFBTAB


DID−name: MTSFBTABDID−number: 265

Function: MTS Fall Backs per AC translation table

Position Contents

1 AC identity (code) 2 Symbolic name of Application Context (slogan)

Description:Translation from Application Context identity/code to ACsymbolic name (slogan).This translation is used for:’MTS Fall Back from MAP version 2 back to MAP version 1’statistics on AC level and MO SMS application context’shortMsgMO−RelayContext−v3’ with slogan ’FBSMMO3’



(DID: MTSFBCNT).

The relations between codes,slogans and Application Contexts isdefined in document 87/155 16−ANT 219 07, Rev B.

Size of the variables.Position Size1 8 bits2 String 7 characters

5.115 ODBCNT


DID−name: ODBCNTDID−number: 266

Function: Counters for Operator Determined Barring statistics.

Position Contents

1 Number of outgoing calls barred due to ODB in MSC/VLR 2 Number of outgoing short messages barred due to ODB in MSC/VLR 3 Number of call independent supplementary services subscriber procedures barred due to ODB in MSC/VLR 4 Number of call related supplementary services subscriber procedures barred due to ODB in MSC/VLR (first block) 5 Number of call related supplementary services subscriber procedures barred due to ODB in MSC/VLR (second block) 6 Number of ECT invocations barred due to ODB in MSC/VLR


Size of the variables.Position Size1−6 16 bits

5.116 SAECNT


DID−name: SAECNTDID−number: 287

Function: Counters for size alterable files in which individuals are seized dynamically during traffic handling and report 16 bit or 32 bit. Note that both types (16 bit or 32 bit) can be reported via a 32 bit DID interface. Application: Blocks in subsystem FNS, which own traffic size alterable files: FSRFSC,BEACC, FMAPTC, FRRGAP, FRDOP, HGDAP, HGLRAD, HLEAP, HLRAP, FANSITC,



HMAPTC, HRSSAP, HRTGMAP, HSDAP, HSDH, HSDPAP, HSSAP, HSSPH, MRCC, MRHOS, FARRAP, MRASS, MRSCH,HCLOP, HGLRADI, HICOP, HLOP, HRON, HSDHI, HSOP, HTSSOP, IWTSS, MADAP, MCI, MICOP, MISJAP, MLOP, MMMMH, HUSDAP, MOSJAP, MSDHI, MSOP, MTCOP,GMWI, MIWUC MUSDAP, IUCID, GRICOP, MCITOP, MCODOP, MGENL, MGSDHV, MGVIOP, MGVOOP, MSECAP3, MUJAP, MVIOP, MVOOP, SSFDJI, SSFDJO, SHCM, SHMM, SHCC, SHEC,SHPM, SHTCU1, SHTCU2, SHTCU3, SHOPSRF, SHINSRF, SHTD1, SHTD2, SHTD3, SHTD4, SHTD5, SHTD6, SHTD7, SHTD8, HASCAP, HDSDAP2, HINAPTC, HISDAP HISDAP2, HLCAP, HLUAP, HLUAP2, HMAPTC HMSPAP2, HNMSPAP, HQUERAP, HREDAP2, HRETAP, HRRGAP, HRRGAP2, HRRVAP, HRRVAP2 HRSMAP,HSACAP2,HSBEAP2,HSD,HSDH,HSAIAP3,HSDH2, HSDPAP, HSMWDAP, HSPWAP2, HSREAP2, HSSACAP, HSSBEAP, HSSD, HSSINAP, HSSPWAP, HSSREAP, HSSUDAP, HSUDAP2, HUDEXAP, HUEXAP2. HRMAPTC, HRUIDAP, HRUODAP, HGDOP, HLETOP, HLRPOP, HRSSOP, HRDOP, HSSOP, HUSDOP, MGDOP, MINOP, MLETOP, MLRROP, MSSOP, MUSDOP, MAPTCI, MISIAP, MOSIAP, MIDJAP, MIDIAP, MODJAP, MODIAP, MUIAP,SHRDO, SHMCS, SHSF, SHCG and SHCL, SHTRI,SHTDM UPMHR, UPMHS, UPPC,DTMFSC,HCI, HCITOP, HMAPMC, MAUTHPD,MMWIS,CHOPA, CATA, DJAMI, CHVIEW HGLUAP, HGSDH, HRFSAP3, HCAD, HANOP, HAROP, MPSLAP, MLSC, MPELAP, MSSNOAP, HSTRAP2, HSTRAP3, MTRAP, SH2LEG, SH2DM, SH2TD2, SH2TD4, SH2TD5, SH2TD6, SH2TD7, SH2TD8, SH2CPM, SH2PM, SH2TCU1, SH2SRF, SH2LEGO, SH2CSAO, SH2CSO, SH2MCS, SH2SF, SH2CG, SH2CL, MSLRAP, MLSPCH, HRRLAP3, MHO, MEC, MECAP, MHONAP, MHOAAP, MAUTH, MFDAP, MHPNAP, MLCAP, MRESTAP, MSDAP, MSECAP, MSECAP3, MSPUAP, MSSPAP, MVIPH, MZONE, MUATAI, MTB, MRR, MUSSH, DQMNT, MAMH, MCAL, MDAVI, MOSMS, MPPP, MREDGV, MRI, MRNB, MRR, MSCHC, MSREG, MSSH, MSSMS, MTA, MTB, MTCINT, MTSUP, MVRP, MVU, MWSH, MCMMM, MHBSMAP, MMMCS, MMMLR, MPAG, MRRM, MSCCL, MSCCO, HRSMAP3 and HSMRAP3

Position Counter Contents

1 − Block (number) 2 SAE Number SAE 500 3 NCALLS Number of seizure attempts 4 NTRAL Number of occupied individuals 5 NOVERFLOW Number of seizure attempts with congestion 6 NIND Number of individuals received during successful size alteration.

Description:All the variables (which are pointed out by the DID itempositions) are stored as common data. However, if there is morethan one set of counters (more than one size alterable filerecorded) in a function block, all the variables are stored ina record. There is one record per SAE event.

The blocks are identified by the block number. The translationtable (DID 94: BNTAB) is used to translate the block number tothe block name.The size of the variables: DID item positions: 1−6 = 32 or 16bits (depending on APZ).



Size of the variables.Position Block Size1−2 MUHOC, MUHIC, MUAMCO MUAMH, MHOCOIP,MUSCCO,TRACO,TRACOB, DROP 16 bits3−6 MUHOC, MUHIC, MUAMCO MUAMH, MHOCOIP,MUSCCO,TRACO,TRACOB, DROP 32 bits Note: The list of blocks reporting the DID positions is not complete.

5.117 TPLATMES


DID−name: TPLATMESDID−number: 289

Function: Counters in TCAP platform in SSP or SCP

Position Contents 1 State 2 Subsystem number 3 Number of messages successfully delivered to specific application 4 Number of messages originated from a specific application

Description:Counters are defined per application (Subsystem). The subsystemnumber, the object identifier, can have the value of 0−255.This will give 256 objects. No translation table is needed sincethe object name is the same as the subsystem number.

Item position 1 is a state value to indicate if the recordinformation is valid (=1) or not (0).

5.118 STPTIMERS2


DID−name: STPTIMERS2DID−number: 299

Function: STP timers

Position Contents1 T1.111.4 T27 Timer in seconds2 T1.111.4 T28 Timer in seconds3 T1.111.4 T29 Timer in seconds4 T1.111.4 T30 Timer in seconds

Description:MTP traffic measurement total counters.These counters are common stored and are system totals.

5.119 C7ODCNT




DID−name: C7ODCNTDID−number: 301

Function: Counters for given OPC + DPC

Position Contents 1 State 2 Number of SIF & SI Octets handled with given OPC + DPC

Description:To identify these counters DID C7ODTAB is required.Records are identified by counter record pointer (C8PTR).The signalling network address is used as an identifier.There are upto 1024 records.

DID position 1 indicates whether the individual is activeor inactive for ITU−T or Japan MTP.Values are:

0 Invalid for both ITU−T and Japan MTP1 Defined for ITU−T MTP2 Defined for Japan MTP

5.120 C7ODTAB


DID−name: C7ODTABDID−number: 302

Function: Translation table for translating record pointer (C8PTR) to a network address

Position Contents 1 Network Indicator 2 Originating Point Code 3 Destination Point Code 4 Address string

Description:Records are identified by counter record pointer (C8PTR).The signalling network address is used as an identifier.The Address string contains upto 16 BCD characters.The output object identifier will look like :−NI−OPC−DPC0−16383−16383DID position 4 will have a value of ’0A16383A16383FFF’for the above network address.

5.121 C7LSSICNT


DID−name: C7LSSICNTDID−number: 303

Function: Counters for given LS + SIO

Position Contents



1 State 2 Number of SIF & SI Octets handled with given LS + SIO

Description:To identify these counters DID C7LSSITAB is required.Records are identified by counter record pointer (C9PTR).The signalling network address is used as an identifier.There are upto 128 records.The record pointer is translated into signaling networkaddress using C7LSSITAB.

DID position 1 indicates whether the individual is activeor inactive for ITU−T, China or Japan MTP.Values are:


5.122 C7LSSITAB


DID−name: C7LSSITABDID−number: 304


Position Contents 1 Link Set Network Indicator 2 Link Set Signaling Point Code 3 Service Indicator 4 Address string

Description:Records are identified by counter record pointer (C9PTR).The signalling network address is used as an identifier.The Address string contains upto 16 BCD characters.The output object identifier will look like :−LSNI−LSSPC−SI2−1500−15DID position 4 will have a value of ’2A1500A15FFFFF’for the above network address.

5.123 C7OPCDSCNT


DID−name: C7OPCDSCNTDID−number: 305

Function: Counters for given OPC+DPC+SIO

Position Contents 1 State 2 Link Set Network Indicator 3 Link Set Signaling Point Code 4 Number of MSU’s handled with given OPC+DPC+SIO



Description:To identify these counters DID C7OPCDSTAB is required.Records are identified by counter record pointer (C7PTR).The signalling network address is used as an identifier.There are upto 128 records.The record pointer is translated into signaling networkaddress using C7OPCDSTAB.

DID position 1 indicates whether the individual is activeor inactive for ITU−T, China or Japan MTP.Values are:


5.124 C7OPCDSTAB


DID−name: C7OPCDSTABDID−number: 306


Position Contents 1 Network Indicator 2 Originating Point Code 3 Destination Point Code 4 service indicator 5 Address string

Description:Records are identified by counter record pointer (C7PTR).The signalling network address is used as an identifier.The Address string contains upto 16 BCD characters.The output object identifier will look like :−NI−OPC−DPC−SI LSNI LSSPC0−16383−15383−15 1 14383DID position 5 will have a value of ’0A2A1500A15FFFFF’for the above network address.

5.125 MTPFORMTAB


DID−name: MTPFORMTABDID−number: 311

Function: Used to indicate whether BCD strings or old format of MTP translation DID’s are to be used.

Position Contents 1 MTP format to be used

Description:DID position 1 is an indicator whether the old translationtable format for MTP DID’s or the new BCD string should beused (value = 1).



5.126 C7MRVTOTCNT


DID−name: C7MRVTOTCNTDID−number: 312

Function: MRV System totals, no failure messages included

Position Contents

1 Total number of MRVT messages sent by the node 2 Total number of MRVA messages sent by the node 3 Total number of MRVR messages sent by the node 4 Total number of MRVA partial success messages sent by the node 5 Total number of MRVT messages received by the node 6 Total number of MRVA success messages received by the node 7 Total number of MRVR success messages received by the node 8 Total number of MRVA partial success messages received by the node 9 Total number of unexpected MRVR messages received by the node10 Total number of MRV tests initiated by the node11 Total number of MRV tests simultaneously active in the node

Description:All counters are common stored data.

5.127 C7MRVFAILCNT


DID−name: C7MRVFAILCNTDID−number: 313

Function: MRV failure message counters

Position Contents

1 Total number of MRVA failure types sent by the node 2 Total number of MRVA failure types received by the node 3 Total number of MRVR failure messages sent by the node 4 Total number of MRVR failure messages received by the node

Description:There is one record per failure type.



All DID positions are stored in records, the number ofrecords is equal to the number of failure types.The failure types are indentified by translating the recordpointer, using C7MRVFAILTAB translation table, into afailure slogan.

5.128 C7MRVFAILTAB


DID−name: C7MRVFAILTABDID−number: 314Function: Translation table for MRV failure types

Position Contents 1 Symbolic name of failure type

Description:The translation table is used to translate recordpointers from C7MRVPM into failure slogans, forthe various failure types.This translation table is associated with C7MRVFAILCNTDID.

Relationship between slogans and failure types.

Record ptr Slogan Failure Type0 LOOP Detected Loop1 EROUTEL Excessive route length2 UNOBJIN Unknown object instance3 ROUTEIN Route inaccessible4 PROFAIL Processing failure5 UNINSP Unknown initiating SP6 TIMEXP timer expired7 SPNOSTP SP not an STP

5.129 C7ODS24CNT


DID−name: C7ODS24CNTDID−number: 315

Function: Counters for 24−bit OPC+DPC+SIO

Position Contents 1 State 2 DPC/MSA 3 DPC/SSA 4 DPC/CSP 5 SI 6 Number of SIF and SIO Octets handled with given 24 bit OPC+DPC+SIO

Description:’State’ indicates whether individual is active (=1)or inactive (=0).The DID C7ODSTAB is used as a translation table for thisDID.Records are identified by the counter record pointer(C6PTR).Individuals are identified by signalling network address.There are 128 records (each counter type can be defined



upto 128 times).The record pointer is translatedinto the counter addresses which are in C7ODSTAB.DPC/MSA has the range 0−255.DPC/SSA has the range 0−255.DPC/CSP has the range 0−255.SI has the range 0−15.

5.130 DIPQCNT3



Function: Digital paths quality sectionalized maintenance counters.

Position Contents 1 CNT2STATE 2 Global DIP−number 3 Number of Errored Seconds, section 1 4 Number of Severely Errored Seconds, section 1 5 Number of Degraded Minutes, section 1 6 Number of Errored Seconds Remote end, section 1 7 Number of Severely Errored Seconds Remote end, section 1 8 Number of Degraded Minutes Remote end, section 1 9 Number of Errored Seconds, section 2 10 Number of Severely Errored Seconds, section 2 11 Number of Degraded Minutes,section 2 12 Number of Errored Seconds Remote end,section 2 13 Number of Severely Errored Seconds Remote end, section 2 14 Number of Degraded Minutes Remote end, section 2

Description:Item pos 1 CNT2STATE, gives information whether DIPQCNT3 isrelevant (1=relevant, DIP is connected and has sectionalizedmaintenance).One record per chosen DIP in STS.All the variables (which are pointed out by the DID itempositions) are stored in a record. Record individuals 0−2687can be used.This DID is associated to the translation DID, DIPTAB.

5.131 SS7SCSSNUSECNT


DID−name: SS7SCSSNUSECNTDID−number: 335

Function: Counters for SCCP Subsystem utilization.

Position Contents 1 State. 2 DT1 terminating per local SSN. 3 DT1 originating per local SSN. 4 Total connection oriented messages originating per destination SSN. 5 Total incoming intermediate node connection oriented messages per



destination SSN. 6 Total outgoing intermediate node connection oriented messages per destination SSN. 7 Total connection oriented messages terminating per local SSN.

Description:One record per SSN, which pointer is equal to SSN,in the block SCCOC.

Item position 1 is a state value to indicate if the recordinformation is valid (=1) or not (=0). That means if the SSNis defined or not.

5.132 LATACNT


DID−name: LATACNTDID−number: 339

Function: Counters for LATA Level Statistics

Position Contents 1 Number of first location area page attempts for a LATA 2 Number of repeated location area page attempts for a LATA 3 Number of page responses to first location area page for a LATA 4 Number of page responses to repeated location area page for a LATA 5 Number of LATA wide page attempts for a LATA 6 Number of page responses to LATA wide paging

Description:Provides paging counters to STS.

The maximum number of LATA existing will be 256.The LATA file will be size alterable.

5.133 COPRVLRCNT


DID−name: COPRVLRCNTDID−number: 340

Function: Counters for fetching security data on co−operating VLR level.

DID item Content

1 Number of total requests for security data from VLR2 Number of successful requests for security data from VLR3 Number of received authentication vectors from VLR4 Number of received current security context



data from VLR

Description:One record per co−operating VLR in block MCVLRD.The pointer in MCVLRD for co−operating VLR addresses iscommon with the translation table in block MTRAN.The translation table COPRVLRTAB is used to translate thepointer to a symbolic VLR name.

5.134 COPRVLRTAB


DID−name: COPRVLRTABDID−number: 341

Function: Counters for fetching security data on co−operating VLR level.

DID item Content

1 State (defined / undefined)2 Symbolic VLR name

Description:Translation table used to translate VLR pointer in SymbolicVLR name.Used inconjuction with DID COPRVLRCNT.The State indicates if the co−operating VLR is defined ornot. (defined = 1, undefined = 0).One record per co−operating VLR.

5.135 LATATAB


DID−name: LATATABDID−number: 344

Function: LATA names for LATA Level Statistics

Position Contents 1 State for LATA (undefined/defined) 2 LATA identity

Description:Translation table used to identify LATAs

5.136 LATAMISCNT


DID−name: LATAMISCNTDID−number: 345

Function: Counter for rejections due to LATA mismatch

Position Contents



1 Number of calls rejected due to LATA mismatch Description:Pprovides LATA Mismatch Statistical Counters to STS.

5.137 SS7SCQOSCNT


DID−name: SS7SCQOSCNTDID−number: 346

Function: Counters for SCCP quality of service

Position Contents

1 CR messages sent to MTP. 2 CREF messages sent to MTP 3 CR messages received from MTP. 4 CREF messages received from MTP. 5 Originating messages requiring segmentation 6 Terminating messages requiring reassembly 7 XUDT messages sent to MTP 8 XUDT messages received from MTP 9 XUDTS messages sent to MTP 10 XUDTS messages received from MTP 11 UDT messages sent to MTP 12 UDT messages received from MTP 13 UDTS messages sent to MTP 14 UDTS messages received from MTP Description:All the variables are common stored data.

5.138 SERVICESWCNT


DID−name: SERVICESWCNTDID−number: 347

Function: Counters for service switching for alternate speech/fax.

Position Contents 1 Number of attempts to switch from one mode to alternate mode. (first block) 2 Number of attempts to switch from one mode to alternate mode. (second block) 3 Number of successful switch from one mode to alternate mode. (first block) 4 Number of successful switch from one mode to alternate mode. (second block)

Description:



The variables (which are pointed out by the DIDitem posiiton) are stored in common variables.The counters specified in DID positions 1 and 3are stored in block MTA and positions 2 and 4 arestored in block MTB.

5.139 NBRMSCPROCCNT


DID−Name: NBRMSCPROCCNTDID−Number: 348

Function: Counters related to the BSSAP procedures applied on the E−Interface, on Neighbouring MSC Level.

Position Contents1 Number of subsequent channel assignment attempts usinga circuit connection to neighbouring MSC. The counter will be stepped when the request for the handover number is sent.2 Number of successful subsequent channel assignments using a circuit connection to neighbouring MSC. The counter will be stepped after both the BSSMAP−ASSIGNMENTCOMPLETE message is received on the E−Interface and the B−Answer is received on the PSTN/ISDN.3 Number of subsequent channel assignment attempts using a circuit connection to neighbouring MSC. The counter will be stepped when the request for the handover number is received.4 Number of successful subsequent channel assignments using a circuit connection to neighbouring MSC. The counter will be stepped after both the BSSMAP−ASSIGNMENTCOMPLETE message is sent on the E−Interface and the B−Answer on the PSTN/ISDN.5 Number of subsequent channel assignment attempts using a circuit connection to neighbouring MSC after GSM to UMTS handover. The counter will be stepped when the request for the handover Number is received.6 Number of successful subsequent channel assignments using a circuit connection to neighbouring MSC after GSM to UMTS handover. The counter will be stepped after both the BSSMAP−ASSIGNMENT COMPLETE message is sent on the E−Interface and the B−Answer on the PSTN/ISDN.7 A subsequent channel assignment attempt should be counted in anchor MSC, when the request for the handover number is sent8 A successful subsequent channel assignment should be counted in anchor MSC, if BSSMAP ASSIGNMENT COMPLETE message is received on the E−interface and if the B−answer is received on the PSTN/ISDN9 A subsequent channel assignment attempt should be counted in nonanchor MSC, when the request for the handover number is received10 A successful channel assignment should be counted



in non−anchor MSC, if BSSMAP ASSIGNMENT COMPLETE message is sent on the E−interface and if the B−answer is sent on the PSTN/ISDN11 Number of subsequent traffic channel assignment attempts using a circuit connection to neigbouring MSC12 A successful subsequent channel assignment should be counted in anchor MSC, if BSSMAP ASSIGNMENT COMPLETE message is received on the E−interface and if the B−answer is received on the PSTN/ISDN

Description:One record per neighbouring MSC in the blocks. Inpractice, it is conceivable for one particular MSC tohave 5 neighbours.The pointer for MSC is the same in all blocks. It is thesame as the pointer in the MSC translation table in blockMTRAN (DID: MSCTAB). Pointer 0 is used in case of"unknown MSC".

The size of the variables.DID position Block Size3−6,9−10 MHIC 16 BITS1−2,7−8,11−12 MHOC 16 BITS

5.140 TRDCNT1


DID−name: TRDCNT1DID−number: 349

Function: Counters for traffic destination codes

Position Contents 1 State (valid/not valid) 2 Number of bids/call 3 Number of unsuccessful call 4 Number of occupied 5 Number of b−answers 6 Number of dest. blockings 7 Number of calls seizing an outgoing circuit 8 Number of successful end of selections 9 All calls reaching the B−subscriber 10 Number of calls rejected by Mass Calling Control

Description:One record per traffic destination code.The traffic destination codes are identified by a number.The number is identical with the record number in thefile, that is the pointer.All the Variables (which are pointed out by theDID item positions) are stored in a record, the numberof records = max number of traffic destination codes (4096).Size alteration event = SAE 5NREJMCCCNT will be declared as a RELOAD variable.

5.141 REGSERVCNT


DID−name: REGSERVCNT



DID−number: 350

Function: Counters for regional services

DID−item Contents

1 Number of originating call attempts within local subscription area 2 Number of terminating call attempts within local subscription area 3 Number of originating call attempts rejected due to local subscription 4 Number of terminating call attempts rejected due to local subscription 5 Number of originating call attempts for subscription with tariff areas 6 Number of terminating call attempts for subscription with tariff areas 7 Number of mobile initiated interrogations for a tariff area applied to a call for subscription with tariff areas 8 Number of mobile initiated interrogations for a tariff area related to the current location for subscription with tariff areas

Description:All the variables are stored as common data.The counters indicate the number of originating andterminating call attempts for the different regionalservices.

5.142 SS7SCUSECNT


DID−name: SS7SCUSECNTDID−number: 362

Function: Counters for SCCP Utilization.

Position Contents Counter name 1 Total number of simultaneous connection sections.

2 Number of segmentation/assembly errors

Description:The variables are common stored data.

5.143 EQLACCCNT


DID−name: EQLACCCNTDID−number: 363

Function: Counters for Equal Access statistics

Position Contents1 Number of originating IXC call attempts using 10XXX or 101XXXX access.



2 Number of originating IXC call attempts using 950−WXXX or 950−XXXX access.3 Number of originating IXC call attempts with pre−subscribed Inter−LATA IXC.4 Number of originating call attempts using Service Access Code (SAC).5 Number of failed originating call set−ups due to dialled carrier unavailable.

Description:All the variables are stored as common stored variables in the newblock CANA and pare resented as system total counters(i.e. defined per office).

Originating IXC call attempts include originating call attemptsboth direct and through an access tandem to the carrier.

5.144 C7OPCDS24CNT


DID−name: C7OPCDS24CNTDID−number: 369

Function: Counters for given 24−bit OPC+DPC+SIO

Position Contents Counter names

1 State 2 DPC/MSA 3 DPC/SSA 4 DPC/CSP 5 SI 6 Number of SIF and SIO Octets handled with given 24−bit OPC+DPC+SIO

Description:To identify these counters DID C7OPCDSTAB is required.Records are identified by counter record pointer (C7PTR).Individuals are identified by signalling network address.There are 128 records (each counter type can be definedupto 128 times).The record pointer is translatedinto the counter addresses which are in C7OPCDSTAB.

’State’ indicates whether individual is active (=1)or inactive (=0).

DPC/MSA has the range 0−255.DPC/SSA has the range 0−255.DPC/CSP has the range 0−255.SI has the range 0−15.

5.145 DISCCALLCNT


DID−name: DISCCALLCNTDID−number: 378

Function: Number of disconnected calls

Position Contents



1 Number of automatically disconnected calls due to long duration call 2 Number of calls that have a duration longer than the predefined limit 3 Number of manually disconnected long duration calls 4 number of calls disconnected as a result of command initiated CTD 5 Number of calls disconnected as a result of CTD due to reception of the Location Cancellation message from the HLR 6 Number of calls disconnected due to wrong exchange data configuration (incompatible MGW types on incoming and outgoing access) 7 Number of terminated call activities due to reception of MAP IST Alert Response operation in MSC 8 Number of terminated call activities due to reception of MAP IST Alert Response operation in GMSC 9 Number of terminated call activities due to reception of MAP IST Command operation in MSC and GMSC

Description:This is a system total.The Variable (which is pointed out by the DID item position)is stored in a common stored variable.

Size of the variables.Position Size1 16 bits2−3 16 bits4−5 16 bits6 32 bits7−9 32 bits

5.146 DIPPRM1CNT


DID−name: DIPPRM1CNTDID−number: 379

Function: Digital path Performance Report Message (PRM) counters local end (transmitted messages)

Position Contents 1 CNT2STATE 2 Global DIP−number 3 Number of CRC error events of type G1 4 Number of CRC error events of type G2 5 Number of CRC error events of type G3 6 Number of CRC error events of type G4 7 Number of CRC error events of type G5 8 Number of CRC error events of type G6 9 Number of severely errored framing events 10 Number of frame synchronization bit error events 11 Number of line code violation events 12 Number of seconds with controlled slips

Description:Item pos 1 CNT2STATE, gives information whether DIPPRM1CNT is



relevant (1=relevant, DIP is connected and supports transmissionof Performance Report Messages (PRM) in the 4 kbit/s Facility datalink (FDL)of the Extended superframe format for 24 channelPCM (24 frames/multiframe)).One record per chosen DIP in STS.All the variables (which are pointed out by the DID itempositions) are stored in a record. Record individuals 0−2687can be used.This DID is associated to the translation DID, DIPTAB.

5.147 DIPPRM2CNT


DID−name: DIPPRM2CNTDID−number: 380

Function: Digital path Performance Report Message (PRM) counters remote end (received messages)

Position Contents 1 CNT3STATE 2 Global DIP−number 3 Number of CRC error events of type G1 4 Number of CRC error events of type G2 5 Number of CRC error events of type G3 6 Number of CRC error events of type G4 7 Number of CRC error events of type G5 8 Number of CRC error events of type G6 9 Number of severely errored framing events 10 Number of frame synchronization bit error events 11 Number of line code violation events 12 Number of seconds with controlled slips

Description:Item pos 1 CNT3STATE, gives information whether DIPPRM2CNT isrelevant (1=relevant, DIP is connected and supports receptionof Performance Report Messages (PRM) in the 4 kbit/s Facilitydata link (FDL) of the Extended superframe format (ESF) for24 channel PCM (24 frames/multiframe)).One record per chosen DIP in STS.All the variables (which are pointed out by the DID itempositions) are stored in a record. Record individuals 0−2687can be used.This DID is associated to the translation DID, DIPTAB.

5.148 IRNEGCNT


DID−name: IRNEGCNTDID−number: 389

Function: Counters for Intermediate Rate negotiation for non−transparent services on full rate channel.

DID item Content

1 Number of 6 kb/s non−transparent full rate services requests in mobile originated calls (implemented in MABC).2 Number of accepted 6 kb/s non−transparent full rate



services requests in mobile originated calls The counter is stepped at first assignment with 6kb/s radio interface data rate on FR channel during the call (implemented in MTA).3 Number of 6 kb/s non−transparent full rate services proposal in mobile terminated calls (implemented in MABC). The counter is stepped after reception of the CALL CONFIRMED message, when 6 kb/s radio interface data rate on FR channel was offered to the MS and is stepped when 6 kb/s radio interface data rate on FR channel is received from the MS, but no intermediate rate negotiation information was sent to the MS in the SETUP message.4 Number of accepted 6 kb/s non−transparent full rate services offers in mobile terminated calls. The counter is stepped after first assignment with 6 kb/s radio interface data rate on FR channel during the call (implemented in MTB).

Description:The variables are common stored.The DIDINFO signal is reported/not reported at restart based onthe value of a commercial parameter.

5.149 CODERASGNCNT


DID−name: CODERASGNCNTDID−number: 391

Function : Counters for speech coder assignment on BSC level

DID item Content Counter name

1 Number of initial channel assignments NBSFRV1PTOT with speech coder FRV1 preferred2 Number of initial channel assignments NBSFRV2PTOT with speech coder FRV2 preferred3 Number of initial channel assignments NBSFRV3PTOT with speech coder FRV3 preferred4 Number of initial channel assignments NBSHRV1PTOT with speech coder HRV1 preferred5 Number of initial channel assignments NBSHRV2PTOT with speech coder HRV2 preferred6 Number of initial channel assignments NBSHRV3PTOT with speech coder HRV3 preferred7 Number of successful initial channel NBSFRV1ATOT assignments with speech coder FRV1 assigned8 Number of successful initial channel NBSFRV2ATOT assignments with speech coder FRV2 assigned9 Number of successful initial channel NBSFRV3ATOT assignments with speech coder FRV3 assigned10 Number of successful initial channel NBSHRV1ATOT assignments with speech coder HRV1 assigned11 Number of successful initial channel NBSHRV2ATOT assignments with speech coder HRV2 assigned12 Number of successful initial channel NBSHRV3ATOT assignments with speech coder HRV3 assigned13 Number of successful initial channel NBSFRV1ANPTOT assignments with other speech coder



than FRV1 preferred and FRV1 assigned14 Number of successful initial channel NBSFRV2ANPTOT assignments with other speech coder than FRV2 preferred and FRV2 assigned15 Number of successful initial channel NBSFRV3ANPTOT assignments with other speech coder than FRV3 preferred and FRV3 assigned16 Number of successful initial channel NBSHRV1ANPTOT assignments with other speech coder than HRV1 preferred and HRV1 assigned17 Number of successful initial channel NBSHRV2ANPTOT assignments with other speech coder than HRV2 preferred and HRV2 assigned18 Number of successful initial channel NBSHRV3ANPTOT assignments with other speech coder than HRV3 preferred and HRV3 assigned19 Number of initial channel assignments NBSDFR5PRE with speech coder FRV5 preferred20 Number of successful intial channel NBSDFRV5SUCC assignments with speech coder FRV5 assigned21 Number of successful intial channel NBNOFR5PFR5ASG assignments with other speech coder than FRV5 preferred and FRV5 assigned

Description:One record per BSC in the blocks. The pointer for a BSC is the same in allblocks and corresponds with the pointer in the BSC translation table (DID:BSCTAB).The counters specified in DID positions 1−21 are stored in block MRRMASG.Block MRRMASG belong to subsystem MMS.The size of the variables:DID item positions: 1− 21 = 32 bits

The size of the variables:DID position Block Size1−21 MRRMASG 32 Bits

5.150 TRAPEVENTCNT


DID−name: TRAPEVENTCNTDID−number: 450

Function: Transcoder resource registrations per pool.

Position Contents 1 Global transcoder pool pointer. 2 Number of accumulations. 3 Active Transcoder Resources. 4 Available Transcoder Resources. 5 Idle Transcoder Resources. 6 Transcoder Resource Allocation Attempts. 7 Transcoder Resource Congestion. 8 Transcoder Resource Congestion Time. 9 V.110 Synchronization Failure for pooled transcoder devices. 10 Number of TFO re−establishment attempts. 11 Number of successful TFO re−establishment. 12 Number of seconds all TFO capable devices have been used in a speech call.



13 Number of seconds all TFO capable devices (TPTFOTIMEOPE) have been in TFO operation mode.

Description:The counters are defined per transcoder pool.DID item positions 1 − 13 are stored in the transcoder pool file in block RTTPH.

DID item position 1 is a pointer, the pointer value can be translated toa transcoder pool name in the transcoder pool translation table(TPTRANTAB).

The number of records in the file is 32. No size alteration.DID item positions: 1 − 13 = R declared.

The size of the variables:DID position Block Size1 − 13 RTTPH 32 bits

5.151 TPTRANTAB


DID−name: TPTRANTABDID−number: 451

Function: Transcoder pool translation table.

Position Contents 1 Transcoder pool name

Description:Translation from transcoder pool pointer to transcoderpool name. The transcoder pool pointer is identicalwith the record number in the file.

The number of records in the transcoder pool file is 32.No size alteration.

5.152 SCCPFORMTAB


DID−name: SCCPFORMTABDID−number: 453

Function: Indicates whether 14/16 or 24 bit SPC is to be used in a switch.

Position Contents 1 SCCP format to be used (0/1)

Description:DID position 1 is an indicator whether the oldtranslation table format for SCCP (value = 0)or the new BCD string should be used (value = 1).It applies to translation table C7SCSPTAB DID number 142.

Example of BCD string and the output string in STS. CBCDSPR(0) = 2; CBCDSPR(1) = 10; ! HYPHEN IS REPRESENTED BY H’A ! CBCDSPR(2) = 1;



CBCDSPR(3) = 2; CBCDSPR(4) = 3; CBCDSPR(5) = 10; ! HYPHEN IS REPRESENTED BY H’A ! CBCDSPR(6) = 1; CBCDSPR(7) = 5; CBCDSPR(8) = 6; CBCDSPR(9) = 10; ! HYPHEN IS REPRESENTED BY H’A ! CBCDSPR(10) = 7; CBCDSPR(11) = 8; CBCDSPR(12) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! CBCDSPR(13) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! CBCDSPR(14) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! CBCDSPR(15) = 15; ! EMPTY SPACE REPRESENTED BY H’F !

The output by STS should be presented as:

2−123−156−78

5.153 CVTR01CNT


DID−name: CVTR01CNTDID−number: 466

Function: Converter counters per SCCP Overhead Address.

Position Contents1 State (record undefined/defined)2 Number of successful address conversions

Description:There is one record for each SCCP overhead address in OCVTR. Thesecounters pertain to the state and number of conversions relating toeach record. Objects are identified by using CVTR01TAB (DID 468).

5.154 CVTR02CNT


DID−name: CVTR02CNTDID−number: 467

Function: Total SCCP Overhead conversions.

Position Contents1 Total number of failed address conversions2 Total number of successful address conversions

Description:System Total for SCCP Overhead conversions.

5.155 CVTR01TAB


DID−name: CVTR01TABDID−number: 468

Function: SCCP Overhead Record Identity.



Position Contents1 Conversion record name

Description:There is one record for each SCCP overhead address in OCVTR. Thisaddress is uniquely identified by the record name and this isrepresented in this DID. The record name is defined by theparameter "ID" in the S7ODI command.

5.156 SHISTCNT


DID−name: SHISTCNTDID−number: 469

Function: Triggering and SCF Invocation, Dialogue Level.

Position Contents 1 State of IST (allocated/not allocated) 2 Number of Tssf timeouts due to subsequent operations 3 Number of IDP/ARI operations sent 4 Number of aborts for sent IDP/ARI operations 5 Number of rejects and ReturnErrors for sent IDP/ARIs 6 Number of sent operations 7 Number of aborts for subsequent operations 8 Number of rejects and ReturnErrors for subsequent operations 9 Number of received operations10 Number of errors for received operations11 Number of IST Selection12 Number of failed IST selections due to data error in the IST data.13 Number of Tssf timeouts due to IDP/ARI

Description:One set of counter is defined for each row in SHIST table.DID item position 1 is a state value indicating if the IST field in SHIST table row is used or not, (0 = not used).DID item positions 1 − 13 are stored in the SHIST table row in SHTD4 block. The size alteration event 925 is used to alter the file size. The maximum number of records in the file is 65535.

The size of the variables.DID position Size 1 1 bit 2 R bits 3 R bits 4 R bits 5 R bits 6 R bits 7 R bits 8 R bits 9 R bits10 R bits11 R bits12 R bits13 R bits

5.157 SHSCFCNT




DID−name: SHSCFCNTDID−number: 470

Function: Operation Handling and Dialogue Control, Traffic Level.

Position Contents 1 Number of SCF invocation attempts per DPC+SSN 2 Number of SCF invocation attempts per GLT 3 Number of SCF invocation attempts per GLT+SSN

Description:One record per destination in the SSF. All the variables (which arepointed out by DID item positions) are stored in a record.

This file is size alterable by SAE 937.The maximum number of records is 32766.

5.158 SHAMCNT


DID−name: SHAMCNTDID−number: 471

Function: Counters for the Dialogue Files held in the Protocol Handling Function in the SSF−AM.

Position Contents1 Number of SRF seizure attempts2 Number of SRF seizure attempts with congestion3 Number of unsuccessful SRF control connections

4 Number of occupied SRF individuals5 Number of ETC seizure attempts6 Number of ETC seizure attempts with congestion7 Number of unsuccessful ETC control connections

8 Number of occupied ETC individuals9 Number of service requests for Call Gapping.10 Number of service requests for Call Limiting.11 Number of service requests for Service Filtering.12 Number of unsuccessful dialogues ActivityTest failure13 Number of message sending requests rejected by Protocol Manager14 Dialogue initiation attempts15 Dialogue initiation attempts with congestion

16 Number of unsuccessful dialogues aborted by SSF17 Dialogues in progress.18 Number of processed dialogues.19 Number of unsuccessful dialogues, message not accepted by TCAP.20 Number of unsuccessful dialogues, aborted by SCF or remote TCAP.21 Number of Error or Reject components received



from SCF.22 Number of Error or Reject components sent by SSF.23 Number of dialogue seizure attempts24 Number of dialogue seizure attempts that meet congestion25 Number of dialogues individuals in use

Description:All the variables are stored as common data and the countersare presented as system total.

Note that multiple SHPM blocks can be present in the SSF−AM.Note that only one SHTCUx block is active on the SSF−AM dump.

5.159 SHAMCALLCNT


DID−name: SHAMCALLCNTDID−number: 474

Function: Counters for the Call File held in the function block SHCM in the SSF−AM.

Position Contents1 Number of call seizure attempts2 Number of occupied call individuals3 Number of call seizure attempts with congestion


5.160 LNPGTT1CNT


DID−name: LNPGTT1CNTDID−number: 517

Function: Total SCCP LNP Global Title Translation

DID item Contentsposition

1 Total number of LNP Global Title translations attempted

2 Number of successful LNP Global Title translations for ported subscribers3 Number of successful LNP Global Title translations for non−ported subscribers

Description:Three common store variables.

5.161 DATACNT




DID−name: DATACNTDID−number: 518

Function: Counter for data services

Position Contents1 Data Service Code2 Number of requests for data services, identified via called party number prefix analysis, at call from mobile subscriber.

Description:The variables pointed out by the DID item positionsare stored as common data.

The data services are identified by a code. See DIDDATATAB.

DID item position 1 is a pointer to the translation table(DID DATATAB)

5.162 DATATAB


DID−name: DATATABDID−number: 519

Function: Data services translation table

Position Contents 1 Data Service Code 2 Data Service Slogan

Description:The variables pointed out by the DID item positionsare stored in a record.

Relation between code, slogan and data service:

Code Slogan Data service

1 A−S HDLC Asynchronous to synchronous HDLC

5.163 SERVFEATCNT


DID−name: SERVFEATCNT



DID−number: 520

Function: Counter for feature

Position Contents1 Feature Code2 Subscribers having a feature Active.3 Number of successful invocations.

Description:Variables are stored in common data.One record per CAMEL−feature. All the variables (whichare pointed out by the DID item positions) are stored in arecord, the number of records = number of CAMEL servicesin block MIN.

The CAMEL features are identified by a code which will be translated to a slogan according to DID SERVFEATTAB.However, if there more than one set of counters inthe block, the variables are stored in record data ofa fixed, non size alterable, file.

Block MIN belongs to the subsystem MSS.

Size of the variables.Position Block Size1 HDPD,HCSID,HSTED,HSTRD,HRRGAP3,HSD,HCSID2 8 bits2 HDPD,HCSID,HSTED,HSTRD,HSD,HCSID2 32 bits3 HRRGAP3,HSD,HCSID2 32 bits

5.164 SERVFEATTAB


DID−name: SERVFEATTABDID−number: 521

Function: Translation table for features in HLR

Position Contents1 Feature Code2 Feature Slogan

Description:Translation from feature code to a slogan.This translation isused for feature counters (DID: SERVFEATCNT). Variables arestored in common data. However, if there is more than one setof counters in the block, the variables are stored in recorddata of a fixed, non size alterable, file. One record perfeature.The existing DID SERVFEATTAB (object type SERVFEAT) will beused as translation table for features in HLR.One new slogan OBCC will be introduced in DID SERVFEATTAB.

Size of the variables.DID position Block Size1 HSD 8 bits2 HSD 15 characters (ASCII string)

Relation between feature codes, featureslogans and features.

Featurecode Slogan Feature



1 OCAMEL Originating CAMEL2 TCAMEL Terminating CAMEL3 OCAMEL HLR Originating CAMEL in HLR4 Reserved for other subsystems, not applicable in HLR5 Reserved for other subsystems, not applicable in HLR6 Reserved for other subsystems, not applicable in HLR7 TCAMEL HLR Terminating CAMEL in HLR8 Reserved for other subsystems, not applicable in HLR9 E−OCAMELINC HLR Extended Originating CAMEL with IN Capability Indicator in HLR10 Reserved for other subsystems, not applicable in HLR11 Reserved for other subsystems, not applicable in HLR12 Reserved for other subsystems, not applicable in HLR13 E−TCAMELINC HLR Extended Terminating CAMEL with IN Capability Indicator in HLR14 Reserved for other subsystems15 E−CAMELOICK HLR Extended Originating CAMEL with OICK in HLR16 Reserved for other subsystems, not applicable in HLR17 Reserved for other subsystems, not applicable in HLR18 Reserved for other subsystems, not applicable in HLR19 E−CAMELTICK HLR Extended Terminating CAMEL with TICK in HLR20 Reserved for other subsystems, not applicable in HLR21 MMINT Mobility Management IN Triggering22 SUBTRAC Subscriber Tracing23 GPRSCSI GPRS CAMEL Subscription Information24 CRIT−TCSI12 HLR Criteria for TCTDP 12 in HLR25 CRIT−OCSI2 HLR Criteria for OCTDP 2 in HLR26 MO−SMS−CSI Originating SMS CAMEL Subscription Information27 MCSI Mobility Management CAMEL Subscription Information28 VTCSI Visitor MSC Terminating CAMEL Subscription Information29 ORHPLMN Optimal Routing Interrogations from Home PLMN30 ORTOT Optimal Routing Interrogations31 TCAMEL MSC Terminating CAMEL in MSC/VLR 32 IST Immediate Service Termination33 MTSMSCSI Terminating SMS CAMEL Subscription Information.34 STE Spatial Triggers.35 DCSI Dialled Services CAMEL Subscription Information36 PRBT Personalized Ring Back Tone37 SPAMSMS Spam control for Mobile Terminating SMS38 OBCC Operator Determined Barring of CCDA Calls39 GERAN ARD GERAN Access Restriction 40 UTRAN ARD UTRAN Access Restriction



5.165 LNPMAINTCNT


DID−name: LNPMAINTCNTDID−number: 532

Function: Counters for LNP maintenance

Position Contents1 Number of failed LNP−SCP queries2 Number of LNP−SCP responses with LRN3 Total number of LNP−SCP queries

Description:Three common store variables

5.166 SDIPMSCNT


DID−name: SDIPMSCNTDID−number: 533

Function: Synchronous Digital paths multiplex section counter data

Position Contents 1 MSCNTSTATE 2 Global SDIP number 3 Level numeric code 4 Local MS index 5 Number of near end errored seconds MSNES 6 Number of far end errored seconds MSFES 7 Number of near end severely errored seconds MSNSES 8 Number of far end severely errored seconds MSFSES 9 Number of near end unavailable seconds MSNUAS10 Number of far end unavailable seconds MSFUAS11 Number of near end unavailable events MSNUAV12 Number of far end unavailable events MSFUAV13 Number of suspect marked 15 minute intervals SMI14 Number of base block errors near end MSNBBE15 Number of base block errors far end MSFBBE

Description:The MSCNTSTATE in pos.1 indicates whetherSDIPMSCNT is defined or not. The level numeric code in DIDpos.3 is used to point to translation table SDIPLEVTAB.The index number in DID pos.4 and translation tableSDIPLEVTAB is used to identify the MS object ex. "MS−0".

The counters are presented as a total for each MS. Onerecord per connected MS object.The counter file is size alterable, SAE 515 in SDIP.SDIP number and MS index must survive restart, all others areclear marked.



Minor processor load for CP to SP data transfer.DID item position 1 is a state bitDID item position 2 is a pointer to the translation table(DID SDIPTAB)DID item position 3 is a pointer to the translation table(DID SDIPLEVTAB)

5.167 SDIPTAB


DID−name: SDIPTABDID−number: 534

Function: Synchronous Digital paths symbolic SDIP−name

Position Contents 1 Symbolic SDIP−name

Description:Translation from SDIP global number to SDIP symbolic numberOne record per SDIP. Pointer equals to global SDIP numberAll the variables which are pointed out by the DID itempositions are stored in a record.Record individuals 0−255 can be used.

5.168 SDIPLEVTAB


DID−name: SDIPLEVTABDID−number: 535

Function: Synchronous Digital paths level names

Position Contents 1 Level numeric code 2 Level Name

Description:Translation from level numeric code to a symbolic MS, HP or LP name

All codes can be sent from a record structureand STS will put the "−" in the Object Identifier.

Code to name relationship1 MS2 VC43 VC12

5.169 SDIPHPCNT


DID−name: SDIPHPCNTDID−number: 536



Function: Synchronous Digital paths higher order path counter data

Position Contents 1 HPCNTSTATE 0=undefined, 1=defined 2 Global SDIP number 3 Level numeric code 4 Local HP index 5 Number of near end errored seconds HPNES 6 Number of far end errored seconds HPFES 7 Number of near end severely errored seconds HPNSES 8 Number of far end severely errored seconds HPFSES 9 Number of near end unavailable seconds HPNUAS 10 Number of far end unavailable seconds HPFUAS 11 Number of near end unavailable events HPNUAV 12 Number of far end unavailable events HPFUAV 13 Number of suspect marked 15 minute intervals SMI 14 Number of base block errors near end HPNBBE 15 Number of base block errors far end HPFBBE

Description:DID item position 1 is a state bit

DID item position 2 is a pointer to the translation table (DID SDIPTAB)

DID item position 3 is a pointer to the translation table(DID SDIPLEVTAB)

The index number in DID pos.4 and translation table SDIPLEVTABis used to identify the HP object ex. "VC4−0"

The counters are presented as a total for each HP.One record per connected HP object.The counter file is size alterable, SAE 515 in SDIP.SDIP number and HP index must survive restart, all others areclear marked.Minor processor load for CP to SP data transfer.

5.170 SDIPLPCNT


DID−name: SDIPLPCNTDID−number: 537

Function: Synchronous Digital paths lower order path counter data

Position Contents 1 LPCNTSTATE 2 Global SDIP number 3 Level numeric code 4 Local LP index 5 Number of near end errored seconds LPNES



6 Number of far end errored seconds LPFES 7 Number of near end severely errored seconds LPNSES 8 Number of far end severely errored seconds LPFSES 9 Number of near end unavailable seconds LPNUAS10 Number of far end unavailable seconds LPFUAS11 Number of near end unavailable events LPNUAV12 Number of far end unavailable events LPFUAV13 Number of suspect marked 15 minute intervals SMI14 Number of base block errors near end LPNBBE15 Number of base block errors far end LPFBBE

Description:The LPCNTSTATE in DID pos 1 indicates whetherSDIPLPCNT is defined or not. The level numeric code in DIDpos.3 is used to point to translation table SDIPLEVTAB. Theindex number in DID pos.4 and translation table SDIPLEVTABis used to identify the LP object ex. "VC12−0".

The counters are presented as a total for each LP.One record per connected LP object.The counter file is size alterable, SAE 515.SDIP number and LP index must survive restart, all others areclear marked.

DID item position 1 is a state bitDID item position 2 is a pointer to the translation table(DID SDIPTAB)DID item position 3 is a pointer to the translation table(DID SDIPLEVTAB)

5.171 NMROUTECNT


DID−name: NMROUTECNTDID−number: 541

Function: Number of calls rejected due to NMS functions

Position Contents 1 Number of calls affected by TAR 2 Number of unsuccessful calls affected by TAR 3 Number of calls affected by CANT 4 Number of calls affected by CANF 5 Number of calls affected by SKIP 6 Number of calls affected by CRO 7 Number of calls affected by ACC 8 Number of unsuccesful route seizure affected by SCR 9 Number of calls affected by ROSA10 Number of unsuccessful calls affected by ROSA11 State12 Number of calls considered by ACC



Description:One record per global route number.The global route number is identical with the record numberin the file, that is the pointer.The global routes are identified by a number.The translation table (DID 46: ROUTETRANTAB) is used totranslate the global route number to the symbolic routename.All the Variables (which are pointed out by the DID itempositions) are stored as record−stored variables

5.172 GPRSGSCNT


DID−name: GPRSGSCNTDID−number: 555

Function: Additional GPRS Gs interface counters

DID−item: Contentsposition 1 Number of received GPRS detach messages 2 Number of sent Reset messages 3 Number of received Reset messages 4 Number of sent Alert Request messages 5 Number of received MS Activity Indication messages 6 Number of sent MS Information Request messages 7 Number of received MS Information Response messages

Description:All the variables are stored as common data.DID item position 1−7 are peg counters.

5.173 BSC2CNT


DID−name: BSC2CNTDID−number: 561

Function: Counters for BSC statistics

Position Contents1 Number of MSC Invoke Trace messages sent to the target BSC.2 Number of CONNECTION ORIENTED INFORMATION messages sent to the target BSC.3 Number of successful CONNECTION ORIENTED INFORMATION messages received from the target BSC with valid TA value.4 Number of handover request messages sent to the target BSC during UMTS to GSM handover5 Number of successful incoming handovers to the BSC during UMTS to GSM handover



6 Number of total PERFORM LOCATION REQUEST messages sent to the target BSC7 Number of successful PERFORM LOCATION RESPONSE messages received from the target BSC including Location Estimate8 Number of handover required messages received9 Number of successful outgoing handover from the BSC.10 Number of sent OVERLOAD messages to the target BSC11 Number of initial channel assignments when "CTM text telephony" is supported by the MS12 Number of initial channel assignments when "CTM text telephony" is supported by the MS, a circuit is selected from a CTM circuit pool, and the assignment is successful13 Number of initial channel assignments when "CTM text telephony" is supported by the MS, a circuit is selected from a non−CTM circuit pool, and the assignment is successful14 Number of initial channel assignments when "CTM text telephony" is NOT supported by the MS, a circuit is selected from a CTM circuit pool, and the assignment is successful

Description:Each record is identified by the BSC number (pointer).The DID item positions for BSC2CNT is to be record stored.

The size of the variables:Position Size1 −10 16 bits11−14 32 bits

5.174 HS7SL1CNT


DID−name: HS7SL1CNTDID−number: 564

Function: High Speed Signalling Link group 1

Position Contents 1 Status Indicator 2 Total time in local RB congestion. Coded as HSLTTLRBC x 50ms. 3 Number of messages transmitted (not including retransmission of messages). 4 Number of messages received in error (incoming message error rate). 5 Number of negative acknowledgements received to messages sent. That is the number of MAA−ERROR indications with error type SD loss (outgoing message error rate). 6 Number of messages received. 7 Number of messages discarded due to SL congestion on level 1. 8 Number of messages discarded due to SL congestion on level 2. 9 Number of messages discarded due to SL congestion on level 3. 10 Number of occurences of congestion events resulting in loss of messages on level 1.



11 Number of occurences of congestion events resulting in loss of messages on level 2. 12 Number of occurences of congestion events resulting in loss of messages on level 3. 13 Number of cells discarded due to Header Error Control (HEC) violations. 14 Number of Out of Cell Delineation (OCD) violations.

15 Number of cells discarded due to protocol (Asynchronous Transfer Mode (ATM) Layer Header) errors. 16 Number of incoming Network Data Collection (NDC) valid (occupied) ATM cells. 17 Number of outgoing Network Data Collection (NDC) valid ATM cells.

Description:The counters are defined per signalling link. Individuals areidentified by signalling link number.

To identify these counters the DID C7SLTAB(154) is required.One record per signalling link (1−1022).Records are identified by signalling link pointer (SLP).

DID position 1 is a state value and indicates whether theindividual is active or inactive for ITU, MTP or TTC, values are:0 − DID inactive1 − DID active for ITU and MTP signalling links2 − DID active for TTC signalling links.DID item positions 13, 14, 15, 16, and 17 are not valid forfor ATM.

5.175 LCSCNT


DID−name: LCSCNTDID−number: 567

Function: Counters for Location Services

Position Contents 1 Total number of initiated Location Acquisition procedure. 2 Number of successful initiated Location Acquisition procedure. 3 Total number of initiated Perform loation messages 4 Number of successful messages 5 Number of successful messages for which Location Estimate was generated by E−OTD method. 6 Number of successful messages for which Location Estimate was generated by AGPS method. 7 Number successful messages for which Location Estimate was generated by Time−Advance method. 8 Number of successful messages for which Location Estimate was generated by U−TDOA method.

Description:All the variables are stored as common data.The size of the variables:



DID position Block Size1 − 2 MLSC 1−32 bits3 − 8 MLSC 1−32 bits

5.176 DIGSCNT


DID−name: DIGSCNTDID−number: 574

Function: Counters for measurement data base for GSS set of parts, GSTS

Position Contents 1 Block (number) 2 Number of connected DIGS units 3 Number of blocked DIGS units in plane A 4 Number of blocked DIGS units in plane B 5 Number of blocked DIGS units

Description:All the variables are stored as common data.The blocks are identified by a number.The translation table (DID 94: BNTAB) is used totranslate the block number to the block name.DID item position 1 is a pointer to the translation table(DID BNTAB)

5.177 LOASMISC1CNT


DID−name: LOASMISC1CNTDID−number: 575

Function: Counters for offered Miscellaneous Tasks

Position Contents 1 Number of miscellaneous tasks with priority level 0 offered to the Processor Load Control function 2 Number of miscellaneous tasks with priority level 1 offered to the Processor Load Control function 3 Number of miscellaneous tasks with priority level 2 offered to the Processor Load Control function 4 Number of miscellaneous tasks with priority level 3 offered to the Processor Load Control function 5 Number of miscellaneous tasks with priority level 4 offered to the Processor Load Control function 6 Number of miscellaneous tasks with priority level 5 offered to the Processor Load Control function 7 Number of miscellaneous tasks with priority level 6 offered to the Processor Load Control function 8 Number of miscellaneous tasks with priority level 7 offered to the Processor Load Control function



9 Number of miscellaneous tasks with priority level 8 offered to the Processor Load Control function10 Number of miscellaneous tasks with priority level 9 offered to the Processor Load Control function11 Number of miscellaneous tasks with priority level 10 offered to the Processor Load Control function12 Number of miscellaneous tasks with priority level 12 offered to the Processor Load Control function13 Number of miscellaneous tasks with priority level 13 offered to the Processor Load Control function14 Number of miscellaneous tasks with priority level 14 offered to the Processor Load Control function15 Number of miscellaneous tasks with priority level 15 offered to the Processor Load Control function

Description:One record.All the Variables (which are pointed out by theDID item positions) are stored in one record oras common stored variables.

5.178 LOASMISC2CNT


DID−name: LOASMISC2CNTDID−number: 576

Function: Counters for fetched Miscellaneous Tasks

Position Contents 1 Number of miscellaneous tasks with priority level 0 fetched from the Processor Load Control function 2 Number of miscellaneous tasks with priority level 1 fetched from the Processor Load Control function 3 Number of miscellaneous tasks with priority level 2 fetched from the Processor Load Control function 4 Number of miscellaneous tasks with priority level 3 fetched from the Processor Load Control function 5 Number of miscellaneous tasks with priority level 4 fetched from the Processor Load Control function 6 Number of miscellaneous tasks with priority level 5 fetched from the Processor Load Control function 7 Number of miscellaneous tasks with priority level 6 fetched from the Processor Load Control function 8 Number of miscellaneous tasks with priority level 7 fetched from the Processor Load Control function 9 Number of miscellaneous tasks with priority level 8 fetched from the Processor Load Control function



10 Number of miscellaneous tasks with priority level 9 fetched from the Processor Load Control function11 Number of miscellaneous tasks with priority level 10 fetched from the Processor Load Control function12 Number of miscellaneous tasks with priority level 12 fetched from the Processor Load Control function13 Number of miscellaneous tasks with priority level 13 fetched from the Processor Load Control function14 Number of miscellaneous tasks with priority level 14 fetched from the Processor Load Control function15 Number of miscellaneous tasks with priority level 15 fetched from the Processor Load Control function

Description :One record.All the Variables (which are pointed out by theDID item positions) are stored in one record oras common stored variables.

5.179 LOASINCOCNT


DID−name: LOASINCOCNTDID−number: 577

Function: Counters for Incoming Calls

Position Contents 1 Number of incoming calls with priority level 0 offered to the Processor Load Control function 2 Number of incoming calls with priority level 0 fetched from the Processor Load Control function 3 Number of incoming calls with priority level 1 offered to the Processor Load Control function 4 Number of incoming calls with priority level 1 fetched from the Processor Load Control function 5 Number of incoming calls with priority level 2 offered to the Processor Load Control function 6 Number of incoming calls with priority level 2 fetched from the Processor Load Control function 7 Number of incoming calls with priority level 3 offered to the Processor Load Control function 8 Number of incoming calls with priority level 3 fetched from the Processor Load Control function 9 Number of incoming calls with priority level 4 offered to the Processor Load Control function10 Number of incoming calls with priority level 4 fetched from the Processor Load Control function



11 Number of incoming calls with priority level 5 offered to the Processor Load Control function12 Number of incoming calls with priority level 5 fetched from the Processor Load Control function13 Number of incoming calls with priority level 6 offered to the Processor Load Control function14 Number of incoming calls with priority level 6 fetched from the Processor Load Control function15 Number of incoming calls with priority level 7 offered to the Processor Load Control function16 Number of incoming calls with priority level 7 fetched from the Processor Load Control function17 Number of incoming calls with priority level 8 offered to the Processor Load Control function18 Number of incoming calls with priority level 8 fetched from the Processor Load Control function19 Number of incoming calls with priority level 9 offered to the Processor Load Control function20 Number of incoming calls with priority level 9 fetched from the Processor Load Control function21 Number of incoming calls with priority level 10 offered to the Processor Load Control function22 Number of incoming calls with priority level 10 fetched from the Processor Load Control function23 Number of incoming calls with priority level 15 offered to the Processor Load Control function24 Number of incoming calls with priority level 15 fetched from the Processor Load Control function

Description :One record.All the Variables (which are pointed out by theDID item positions) are stored in one record oras common stored variables.

5.180 RNCSTATCNT


DID−name: RNCSTATCNTDID−number: 578

Function: RNC record counter.


1 Number of received reset messages 2 Number of relocation required



messages received 3 Number of relocation request messages sent to the target RNC 4 Number of successful incoming relocation to the RNC 5 Number of successful outgoing relocation to the RNC 6 Number of relocation required messages received for UMTS to GSM handover 7 Number of successful outgoing UMTS to GSM handover from the RNC 8 Number of successful RAB assign. for call from mobile subscriber. 9 Number of successful RAB assign. for call to mobile subscriber.10 Total number of RAB assignments for call from mobile subscriber.11 Total number of RAB assignments for call to mobile subscriber.12 Number of received Reset Resource messages.13 Number of sent Reset Resource messages.14 Number of relocation request messages sent to the target RNC.15 Number of successful incoming relocation to the RNC.16 Number of Location Reporting Control messages sent.17 Number of Location Report messages containing Geographical Co−ordinates received.18 Number of received relocation cancel messages per source RNC19 Number of Location Related Data Request messages sent.20 Number of Location Related Data Response messages or Location Related Data Failure messages received.

Description:All the variables are stored as record stored data.The counters are stepped per RNC.

The translation table RNCTAB will be used to translate fromthe internal record number to the symbolic RNC name.


DID position Block Size1 MUAMCL 32 bits2 − 3 MURELP 32 bits4 − 5 MUREL 32 bits6 MURELP 32 bits7 MUREL 32 bits8 − 11 MURABP 32 bits12 − 13 MUAMCL 32 bits14 MURELP 32 bits15 MHO 32 bits16 − 17 MUIP 16 bits18 MURELP 32 bits19 − 20 MUIP 16 bits

5.181 RNCTAB




DID−name: RNCTABDID−number: 579

Function: RNC name translation table

Position Contents 1 State (undefined/defined) 2 Symbolic RNC name

Description:Translation from RNC pointer to symbolic name.This translation is required for statistics(DID RNCSTATCNT).State indicates whether the RNC is undefined (=0)or defined (=1).One record per RNC.DID position Size1 1 bit2 7 characters string

5.182 LSCCCNT


DID−name: LSCCCNTDID−number: 580

Function: Simultaneously established and rejection calls counters

Position Contents 1 Simultaneously established calls counter 2 Rejection counter

Description:All the variables (which are pointed out by the DID itempositions) are stored as common stored variables.

5.183 RELOCCNT


DID−name: RELOCCNTDID−number: 587

Function: Counters for relocation, MSC level

Position Contents 1 Number of inter−RNC relocation attempts. 2 Number of received relocation required (excluding those received during guard time). 3 Number of sent relocation requests to the target RNC. 4 Number of successful relocation requests to the target RNC. 5 Number of sent relocation commands. 6 Number of successful inter−RNC



relocation attempts. 7 Number of switch orders to the MGW triggered by relocation detect. 8 Number of switch orders to the MGW triggered by relocation complete. 9 Number of relocation attempts causing the UE to switch back to the old RNC.10 Number of relocation faults causing the MSC server to release the call.11 Number of inter−RNC relocation attempts on signalling channel.12 Number of successful inter−RNC relocation on signalling channel.


5.184 NMSCUGHOCNT


DID−name: NMSCUGHOCNTDID−number: 588

Function: Counters for WCDMA to GSM inter−MSC handover on neighbouring MSC level


1 Number of basic UMTS to GSM handover attempts to neighbouring MSC/VLR server or MSC/VLR 2 Number of successful basic UMTS to GSM handovers to neighbouring MSC/VLR server or MSC/VLR 3 Number of basic UMTS to GSM handover attempts on signalling channels to neighbouring MSC/VLR server or MSC/VLR 4 Number of successful basic UMTS to GSM handovers on signalling channels to neighbouring MSC/VLR server or MSC/VLR 5 Number of subsequent UMTS to GSM handover attempts to neighbouring MSC (back to anchor or to third MSC) 6 Number of successful subsequent UMTS to GSM handovers to neighbouring MSC (back to anchor or to third MSC) 7 Number of subsequent UMTS to GSM handover attempts on signalling channel to neighbouring MSC (back to anchor or to third MSC) 8 Number of successful subsequent UMTS to GSM handovers on signalling channel to neighbouring MSC (back to anchor or to third MSC) 9 Number of basic handover attempts from signalling channel to traffic channel to neighbouring MSC/VLR Server or MSC/VLR



10 Number of successful basic handovers from signalling channel to traffic channel to neighbouring MSC/VLR Server or MSC/VLR 11 Number of incoming handover attempts from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC),in case the call type is traffic to traffic and the HO is WCDMA to GSM. 12 Number of successful incoming handover attempts from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC), in case the call type is traffic to traffic and the HO is WCDMA to GSM. 13 Number of incoming handover attempts from signalling to signalling channel from neighbouring MSC (incoming handovers include basic relocations and subsequent relocations from neighbouring MSC), in case the call type is signalling to signalling and the HO is WCDMA to GSM. 14 Number of successful incoming handovers from signalling to signalling channel from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC), in case the call type is signalling to signalling and the HO is WCDMA to GSM. 15 Number of incoming WCDMA to GSM handover rejections from neighbouring MSC due to MSC Pool redistribution activities (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC).Description:One record per neighbouring MSC in the blocks. Inpractice, it is conceivable for one particular MSC tohave 5 neighbours.The pointer for MSC is the same in all blocks. It isthe same as the pointer in the MSC translation table in block MTRAN (DID: MSCTAB). Pointer 0 is used in case of ’unknown MSC’.

The size of the variables.DID position Block Size1 − 4 MUREL 32 BITS5 − 8 MHIC 16 BITS9 − 10 MUREL 32 BITS11 − 15 MHIC 16 BITS

5.185 UGHNDOVERCNT


DID−name: UGHNDOVERCNTDID−number: 589

Function: Counters for UMTS to GSM handover, MSC level.


1 Number of received relocation required (excluding those received during guard time) for UTMS to GSM handover 2 Number of sent UTMS to GSM handover



requests to the target BSC 3 Number of successful UTMS to GSM handover requests to the target BSC 4 Number of sent relocation commands sent during UTMS to GSM handover 5 Number of GS−operations triggered by handover detect during UTMS to GSM handover 6 Number of GS−operations triggered by handover complete during UTMS to GSM handover 7 Number of UTMS to GSM handover attempts causing the MS to switch back to the old serving RNC 8 Number of UTMS to GSM handover faults causing the MSC to release the call 9 Number of handover attempts from RNC to BSC 10 Number of successful handovers from RNC to BSC 11 Number of handover attempts from RNC to BSC on SDCCH 12 Number of successful handovers from RNC to BSC on SDCCH 13 Number of handover attempts from signalling channel to traffic channel 14 Number of successful handovers from signalling channel to traffic channel


5.186 DID 591 "NOT USED"

5.187 UMTSSECCNT


DID−name: UMTSSECCNTDID−number: 592

Function: Security handling counter for UMTS

DID itemposition Contents

1 Number of successfully received Security Mode Complete messages. (signal SENDCIPHR)2 Total Number of sent Security Mode Command messages. (signal SENDCIPH)

Description:The counters are stored in common data

5.188 OPTFEATCNT


DID−name: OPTFEATCNT



DID−number: 604

Function: Counters for Optional Feature statistic


1 Total number of call attempts requiring "Bypassing of the local IWF for Internet calls" 2 Total number of successful call attempts requiring "Bypassing of the local IWF for Internet calls" 3 Number of service requests for multi−media over 3.1 kHz audio 4 Number of accepted service requests for multi−media over 3.1 kHz audio 5 Number of service requests for multi−media over UDI or RDI 6 Number of accepted service requests for multi−media over UDI or RDI. 7 Total number of invoked WPS calls

Description:All the variables are stored as common variablesThe counters specified in DID positions 1 and 2 are storedin block MTA.The counters specified in DID positions 3 and 4 are storedin block MABC.The counters specified in DID positions 5 and 6 are storedin block MUABC.The counter specified in DID positions 7 is storedin block MTA.

Blocks MABC, MTA and MUABC belong to thesubsystem MSS.

NOTE: Counters 8−12 was introduced in SCAPE P6 increment 1 and removed in SCAPE P6 increment 2. Removal was performed accordingly to CR−STS−8, 58/109 18−FCG 101 07 Uen Rev PA1.

The size of the variables:Position Size1−7 32 bits

5.189 APPLATCNT

−VALID FOR APG

DID−name: APPLATCNTDID−number: 605

Function: Counters for the Adjunct Processor.

Position Contents

1 Current CPU usage (percent) 2 Current Priviledged CPU usage (percent) 3 Current User CPU usage (percent) 4 Context switching rate (switches per second) 5 Registry quota in use (percentage) 6 Available free memory (bytes) 7 Page fault rate (number per second) 8 Cache fault rate (number per second) 9 Network Interface, bytes received (per second)



10 Network Interface, bytes sent (per second)11 External Interface, bytes received (per second)12 External Interface, bytes sent (per second)

Description:One record per AP platform. The record number can be usedto translated to the AP name in the translation table(DID APPLATTAB).Size of variables:DID position: 1−12 = 32 bits

5.190 APDISKCNT

−VALID FOR APG

DID−name: APDISKCNTDID−number: 606

Function: Counters for the Adjunct Processor disks

Position Contents

1 State 2 Disk read time (percentage of period spent reading) 3 Disk write time (percentage of period spent writing) 4 Average disk read Queue length 5 Average disk write Queue length

Description:One record per disk. State position indicates if theindividual is valid or not (0=invalid). The disksare identified using the translation table APDISKTAB.The individual for the table corresponds to theindividual in the counter DID.

5.191 APDISKTAB

−VALID FOR APG

DID−name: APDISKTABDID−number: 607

Function: Translation table for disk name on Adjunct Processor.

Position Contents 1 Disk Name

Description:One record per disk per AP platform. Translation from recordpointer to DISK name The Disk identifier is made up to theAP platform identifier and the disk name as shown.AP1DAP2E

The size of the variables.Position Size 1 STRING 31 Characters



5.192 GUHNDOVERCNT


DID−name: GUHNDOVERCNTDID−number: 608

Function: Counters for Intra−MSC GSM to UMTS handover


1 Number of received handover required 2 Number of sent relocation requests to the target RNC. 3 Number of successful GSM TO UMTS relocation requests to the target RNC. 4 Number of handover commands send during GSM to UMTS handover. 5 Number of switch orders to the MGW triggered by relocation detect during GSM to UMTS handover. 6 Number of switch orders to the MGW triggered by relocation complete during GSM to UMTS handover. 7 Number of handover attempts causing the UE to switch back to the old BSC. 8 Number of handover faults causing the MSC server to release the call. 9 Number of handover attempts from BSC to RNC. 10 Number of successful handovers from BSC to RNC. 11 Number of handover attempts from BSC to RNC on signalling channel. 12 Number of successful handovers from BSC to RNC on signalling channel. 13 Number of handover attempts from BSC to RNC from signalling to traffic channel. 14 Number of successful handovers from BSC to RNC from signalling to traffic channel.


5.193 DTAPLCSCNT


DID−name: DTAPLCSCNTDID−number: 609

Function: Counters for DTAP messages for Location Services




1 Total number of initiated DTAP messages for Location Services. 2 Total number of accepted messages requesting that Location Estimate is sent to the MS. 3 Total number of accepted messages requesting that Location Estimate is sent to a specific LCS client. 4 Number of accepted messages requesting deciphering keys or assistance data for E−OTD. 5 Number of accepted messages requesting deciphering keys or assistance data for A−GPS. 6 Total number of successful messages.

Description:The counters will be stored in common variables.The variables will be clear marked.

5.194 MTSFB3CNT


DID−name: MTSFB3CNTDID−number: 611

Function: Counters for MTS MAP V3 operation Fall Back statistics for Application Contexts (AC).

DID item Contentsposition 1 AC Identity (code) 2 Number of fall backs for an Application Context MAP V3 to MAP V2 3 Number of fall backs for an Application Context MAP V3 to MAP V1

Description:One record per Application Context(the number of records = number of Application Contexts inthe block).The variables are stored as common data if the blockcontains only one Application Context.The Application Contexts are identified by a code.(DID: MTSFBTAB).Note that the description of the DID MTSFBTAB shouldbe rephrased in order to include also fallbacksfrom MAP V3.

5.195 NBRMSCGUHCNT


DID−name: NBRMSCGUHCNTDID−number: 612

Function: Counters Neightbouring MSC Level Statistics for



GSM to WCDMA Handover

DID item Contentsposition 1 Number of basic GSM to WCDMA handover attempts to neighbouring MSC/VLR server 2 Number of successful basic GSM to WCDMA handover attempts to neighbouring MSC/VLR server 3 Number of subsequent GSM to WCDMA handover attempts from neighbouring MSC back to anchor MSC/VLR server per serving MSC 4 Number of successful subsequent GSM to WCDMA handover from neighbouring MSC back to anchor MSC/VLR server per serving MSC 5 Number of subsequent GSM to WCDMA handover attempts from neighbouring MSC to third MSC/VLR server. The target MSC/VLR server shall be the measurement object. 6 Number of successful subsequent GSM to WCDMA handovers from neighbouring MSC to third MSC/VLR server. The target MSC/VLR server shall be the measurement object. 7 Number of incoming GSM to WCDMA handover attempts from neighbouring MSC (incoming handovers shall include basic handovers and subsequent handover from neighbouring MSC) 8 Number of successful incoming GSM to WCDMA handovers from neighbouring MSC (incoming handovers shall include basic handovers and subsequent handover from neighbouring MSC) 9 Number of basic GSM to WCDMA handovers attempts from signalling to traffic channel10 Number of successful basic GSM to WCDMA handovers from signalling to traffic channel11 Number of basic GSM to WCDMA handovers attempts from signalling to signalling channel to neighbouring MSC/VLR server12 Number of successful basic GSM to WCDMA handovers from signalling to signalling channel to neighbouring MSC/VLR server13 Number of subsequent GSM to WCDMA handover attempts on signalling channel from neighbouring MSC back to anchor MSC/VLR server, per serving MSC14 Number of successful subsequent GSM to WCDMA handovers on signalling channel from neighbouring MSC back to anchor MSC/VLR server, per serving MSC15 Number of subsequent GSM to WCDMA handover attempts from signalling to signalling channel from neighbouring MSC to third MSC/VLR server. The target MSC/VLR server shall be the measurement object.16 Number of successful subsequent GSM to WCDMA handover from signalling to signalling channel from neighbouring MSC to third MSC/VLR server. The target MSC/VLR server



shall be the measurement object.17 Number of Subsequent GSM to WCDMA handover attempts from signalling to signalling channel from neighbouring MSC to third MSC/VLR server. The target MSC/VLR server shall be the measurement object.18 Number of successful incoming GSM to WCDMA handovers on signalling channel from neighbouring MSC (incoming handovers shall include basic handovers and subsequent handover from neighbouring MSC)19 Number of incoming GSM to WCDMA handover rejections from neighbouring MSC due to MSC Pool redistribution activities (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC)

Description:One record per neighbouring MSC in the blocks. Inpractice, it is conceivable for one particular MSC tohave 5 neighbours.The pointer for MSC is the same in all blocks. It isthe same as the pointer in the MSC translation table in block MTRAN (DID: MSCTAB). Pointer 0 is used in case of ’unknown MSC’.

The size of the variables.DID position Block Size1 − 6 MHO 16 BITS7 − 8 MHIC 16 BITS9 − 16 MHO 16 BITS17 − 19 MHIC 16 BITS

5.196 MNPMAINTCNT


DID−name: MNPMAINTCNTDID−number: 615

Function: Counters for MNP maintenance

Position Contents1 Number of unsuccessful MNP database queries due to signalling failure towards MNP database.2 Nunber of ReleaseCall operations received from the MNP database.

Description:Common store variables.

5.197 CAMEL3CNT


DID−name: CAMEL3CNTDID−number: 617



Function: Counters for Camel phase 3 data statistics

Position Contents1 Number of Camel phase 3 data received but not supported.

Description:Variable is stored in common data and the counter ispresented as system total.

5.198 CAMELSMSCNT


DID−name: CAMELSMSCNTDID−number: 618

Function: Counter for Camel MO−SMS and MT−SMS

Position Contents1 Number of invocations of access CAMEL service for MO SMS2 Number of MO SMS failures due to rejection from the CAMEL feature3 Number of invocations of access CAMEL service for MT−SMS4 Number of MT−SMS failures due to rejection from the CAMEL feature

Description:All the variables are stored as common data and the counters arepresented as system total.

The size of the variables:DID position Size 1 32 bits 2 32 bits 3 32 bits 4 32 bits

5.199 UMTSPOSCNT


DID−name: UMTSPOSCNTDID−number: 635

Function: Counters for UMTS positioning.

Position Contents1 Number of Location Reporting Control messages sent.2 Number of Location Report messages containing Geographical Co−ordinates received.3 Number or Location Related Data Request messages sent.4 Number of Location Related Data Response received.

Description:All the variables are stored as common stored data.

DID item positions Block Size



1 − 4 MUIP 16 bits

5.200 APPLATTAB

−VALID FOR APG

DID−name: APPLATTABDID−number: 638

Function: Platform names for the Adjunct Processor.Application: Statistics Gatherer (AP)

Position Contents 1 Platform Name

Description:One record per platform.

Size of variables:DID Position 1 = String 16 characters A−Z a−z 0−9 .,/

The Gatherer is responsible for the DID APPLATTAB. It shall fillthe DID with the names Of the AP platforms from which is hasrequested data. The names can be retrieved from the statisticsprofile.

5.201 L3CCMSGCNT


DID−name: L3CCMSGCNTDID−number: 642

Function: Layer 3 Call Control counters per MSC/VLR server

Position Contents1 Number of sent Layer 3 Call Control CALL PROCEEDING messages

2 Number of received Layer 3 Call Control CALL CONFIRMED valid messages

Description: Data stored as common stored 32 bit variables

DID item position 1−2 are peg counters.

5.202 SS7HSLTRACNT


DID−name: SS7HSLTRACNTDID−number: 644

Function: SAAL Signalling Link Traffic Measurements

Position Contents1 State



2 Number of MTP3 messages transmitted3 Number of MTP3 messages received4 Number of SIF and SIO octets transmitted5 Number of SIF and SIO octets received6 Number of MTP3 messages received requiring Global Title Translation(GTT)7 Number of MTP3 message octets associated with MTP3 messages received that required GTT8 Number of incoming (received) NDC−valid ATM cells9 Number of outgoing(transmitted) NDC−valid ATM cells10 Number of incoming(received) ATM user− information (UI) cells11 Number of outgoing(transmitted) ATM user− information (UI) cells12 Number of errored seconds for SAAL,ATM and physical layers13 Number of SSCOP PDUs of all types transmitted14 Number of SSCOP PDUs of all types received15 Number of octets associated with SSCOP PDUs of all types transmitted including retransmissions16 Number of octets associated with SSCOP PDUs of all types received17 Number of SSCOP Sequence Data (SD) PDUs transmitted , including retransmissions18 Number of SSCOP SD PDUs retransmitted19 Number of octets associated with SSCOP SD PDUs traqnsmitted including retransmissions20 Number of octets associated with SSCOP SD PDUs retransmitted21 Number of SSCOP SD PDUs received22 Number of octets associated with SSCOP SD PDUs received23 Number of SSCOP SD PDUs transmitted requiring retransmission because they were not acknowledged by the far−end’s SSCOP peer

Description:One record per signalling link in the blocks.The objects are identified by their record pointersSTATE indicates if the record is used for a high speedlink (=1) or not (=0).The record pointer is translated ( translation DID SLDESTAB)to its signalling link designation in the form of N−C−M−SLC(Network−Cluster−Member−Signalling Link code)The record number of the file being reported is used toidentify the measurement objects.Max file size is 1025,(SAE 52)

5.203 SS7HSLMT1CNT

−VALID FOR IOG/APG DID−name: SS7HSLMT1CNTDID−number: 645

Function: SAAL Signalling Link Maintenance and Traffic Measurements

Position Contents1 State



2 Accumulated total of link transmission buffer occupancy in octets3 Accumulated total of link transmission buffer occupancy in MTP3 messages4 Accumulated total of link transmission buffer occupancy in priority 0 MTP3 messages5 Accumulated total of link transmission buffer occupancy in priority 1 MTP3 messages6 Accumulated total of link transmission buffer occupancy in priority 2 MTP3 messages7 Accumulated total of link transmission buffer occupancy in priority 3 MTP3 messages8 Number of samples from signaLling terminal9 Number of priority 0 MTP3 messages discarded due to signalling congestion10 Number of priority 1 MTP3 messages discarded due to signalling congestion11 Number of priority 2 MTP3 messages discarded due to signalling congestion12 Number of priority 3 MTP3 messages discarded due to signalling congestion13 Number of times a signalling link enters level 1 congestion state14 Number of times a signalling link enters level 2 congestion state15 Number of times a signalling link enters level 3 congestion state )16 Total duration of level 1 congestion state in 10 second units17 Total duration of level 2 congestion state in 10 second units18 Total duration of level 3 congestion state in 10 second units19 Link maintenance usage in 10 second units20 Signalling link active time in 10 second units21 Number of 10 second scans22 Maintenance state (same as signalling link service status) 0="UNAV", 1="OOS",2="ACT"23 Number of MPT3 messages discarded due to message length longer than 272 octets24 Duration of Far−end Processor Outage in 10 seconds

Description:One record per signalling link in the blocks.The objects are identified by their record pointersSTATE indicates if the record is used for a high speed link (=1) or not (=0).The record pointer is translated ( translation DID SLDESTAB)to its signalling link designation in the form of N−C−M−SLC( Network−Cluster−Member−Signalling Link code)The record number of the file being reported is used toidentify the measurement objects.Max file size is 1025,(SAE 52).

5.204 SS7HSLMT2CNT


DID−name: SS7HSLMT2CNTDID−number: 646

Function: SAAL Signalling Link Maintenance and



Traffic Measurements

Position Contents1 State2 Duration of signalling link declared failures, all types, in 10 second units3 Number of signalling link declared failures all types.4 Duration of signalling link declared failures due to excessive delay of acknowledgement in 10 second units.5 Number of signalling link declared failures due to excessive delay of acknowledgement6 Duration of signalling link declared failures due to excessive error rate in 10 second units7 Number of signalling link declared failures due to excessive error rate8 Duration of signalling link declared failures due to excessive duration of congestion in 10 second units9 Duration of signalling link declared failures due to excessive duration of congestion10 Duration of signalling link declared failures due to hardware problems in 10 second units11 Number of signalling link declared failures due to hardware problems12 Number of near−end manual changeovers13 Number of automatic changeovers14 Number of near−end management inhibits15 Number of far−end management inhibits (successfully inhibited from the far−end)16 Duration of signalling link management inhibits in 10 second units17 Parameter group number for signalling link18 Indication of link declared failure state19 Indication of link management−inhibit status ( 0=N, 1=Y)20 Current link transmit congestion level is 0,1,2 or 321 Current link transmit congestion state 0=’N’, 1=’O’,2=’D’22 Duration of link busy status declared by near−end signalling terminal in 50 ms units23 Duration of near−end processor outage in 10 second units24 Signalling link alignment failures

Description:One record per signalling link .The objects are identified by their record pointersSTATE indicates if the record is used for a high speed link (=1) or not (=0).The record pointer is translated (translation DID SLDESTAB) to its signalling link designation in the form of N−C−M−SLC ( Network−Cluster−Member−Signalling Link code)The record number of the file being reported is used toidentify the measurement objects.Max file size is 1025,(SAE 52)

5.205 SS7HSLMT3CNT




DID−name: SS7HSLMT3CNTDID−number: 647

Function: SAAL Signalling Link Maintenance Measurements

Position Contents1 State2 Number of incoming ATM cells discarded due to Header Error Control (HEC) violations3 Number of time Out of Cell Delineation (OCD) anomalies4 Total time in seconds that the link is regarded in service(at level 2) by SAAL5 Number of incoming ATM cells discarded due to protocol ( ATM−layer Header) errors6 Number of abnormal occurrences of SSCOP Connection Disconnect7 Number of SSCOP Connection Initiation Failures8 Number of SSCOP Connection Restablishment/ Resynchronisations9 A SCSCOP Connection sum of errors counter i.e the sum of CSPRM−54 and CSPRM −5510 Number of unexpected SSCOP PDUs received11 Number of invalid SSCOP PDUs received12 Number of SSCOP PDUs with List Element Errors13 A SSCOP Errored PDUs sum of errors counter i.e a sum of CSPRM−58 ,59 and 6014 Number of times that SSCOP had PDUs to send to its peer but could not do because it was not given credit by the far end.15 Cumulative duration of time in seconds during which SSCOP had PDUs to send to its peer but could not do so because it was not given credit by the far−end, summed over Lack−of−Credit events occurring during the measurement interval16 Number of 10 second scans in S7SL17 Number of 10 second scans in S7LS18 Number of messages discarded due to SL congestion on level 119 Number of messages discarded due to SL congestion on level 220 Number of messages discarded due to SL congestion on level 3

Description:One record per signalling link. The objects are identified by their record pointers. STATE indicates if the record is used (=1) or not (=0). The record pointer is translated (translation DID SLDESTAB) to its signalling link designation in the form of N−C−M−SLC (Network−Cluster−Member−Signalling Link code) The record number of the file being reported is used to identify the measurement objects. Max file size is 1024, controllable by SAE 52. All the DID positions are delivered to STS by S7SL block. The size of the variables:

DID position Block Size1 S7SL 1 bit2,3,5−15,18−20 S7SL 32 bits4,16,17 S7SL 16 bits18 − 20 S7SL 32 bits

5.206 SS7HSLS1CNT




DID−name: SS7HSLS1CNTDID−number: 648

Function: SAAL Signalling Link Set Measurements

Position Contents1 State2 Number of MTP3 messages transmitted, including those for which retransmissions of SSCOP SD PDUs3 Number of MTP3 messages received4 Number of octets for MTP3 messages transmitted5 Number of octets for MTP3 messages received6 Number of assigned signalling links7 Total duration of link set inactivity due to no links in link set that are active in 10 second units8 Number of links in the Out−of−Service maintenance state .9 Number of links in the Unavailable maintenance state.10 Number of 10 second scans.11 Maintenance state(same as link set service status) 0="UNAV", 1="OOS",2="ACT".12 Number of Currently Available Links ( ACT).

Description:One record per link set in the blocks.The objects are identified by their record pointersSTATE indicates if link set contains high speed links (=1) or not (=0).The record pointer is translated ( translation DID LSDESTAB) to its signalling link designation in the form of N−C−M( Network−Cluster−Member). The record number of the file being reported is used to identify the measurement objects.Max file size is 1025,(SAE 207)Variables for DID positions 1, 2−5 are stored inS7DR

5.207 SS7HSLS2CNT


DID−name: SS7HSLS2CNTDID−number: 649

Function: SAAL Signalling Link Set Measurements

Position Contents1 State2 Total number of incoming (received) NDC−valid ATM cells3 Total number of outgoing(transmitted) NDC−valid ATM cells4 Total number of incoming (received) ATM user information (UI) cells5 Total number of outgoing(transmitted) ATM user information (UI) cells6 Total number of SSCOP PDUs transmitted7 Total number of SSCOP PDUs received



8 Total number of SSCOP PDU octets transmitted9 Total number of SSCOP PDU octets received10 Number of SSCOP SD PDUs transmitted11 Number of SSCOP SD PDUs retransmitted12 Number of SSCOP SD PDU octets transmitted13 Number of SSCOP SD PDU octets retransmitted14 Number of SSCOP SD PDUs received15 Number of SSCOP SD PDU octets received

Description:One record per link set in the blocks.The objects are identified by their record pointersSTATE indicates if link set contains high speed links(=1) or not (=0).The record pointer is translated (translation DID LSDESTAB)to its signalling link designation in the form of N−C−M( Network−Cluster−Member) .The record number of the file being reported is used to identify the measurement objects.Max file size is 1025,(SAE 207)

5.208 SS7HSLPG1CNT


DID−name: SS7HSLPG1CNTDID−number: 650

Function: High speed Signalling Link parameter group Measurements

Position Contents1 TimercCC, time between transmission of unacknowledged BGN, END,ER, or RS PDUs.2 TimerKEEP−ALIVE, "keep alive" for 3622 cells/sec signalling rate3 TimerNO−RESPONSE, maximum time interval during which at least one STAT PDU must be received4 TimerPOLL, "Poll" for 3622cels/sec signalling rate5 TimerIDLE, maximum time of the idle phase of an SSCOP connection6 TimerT1, time between link release and re−establishment during alignment7 TimerT2, time SSCF will attempt alignment8 TimerT3, time between proving PDUs in 1 ms9 TimerREPEAT−SREC, minimum interval between reports of an SSCOP recovery10 TimerN0−CREDIT, maximum interval without credit11 Tsup, superblock size12 Tloss, stat loss limit13 T(tau), error monitoring interval14 TimerFORCE−PROVING,force proving15 A (alpha), exponential smoothing factor16 N, Monitoring intervals after 400ms error event17 MaxCC, maximum number of unacknowledged BGN, END,ER, or RS PDUs.18 MaxPD, maximum number of SD PDUs sent between POLL PDUs19 MaxSTAT, maximum number of list elements in a STAT PDU20 N1, PDUs sent during normal proving



21 MaxNRP, maximum number of retransmitted SCCOP PDUs permissible for link proving22 Thres,threshold for comparing the running Quality of Service23 Nblk, monitoring intervals per block

Description:One record per parameter group for HSL in the block.The objects are identified by their record pointers.There are 8 parameter groups and each is identified by itsname and a number from 8 to 15The parameter group number is obtained by adding 8 tothe record pointer in the HSL parameter group file

5.209 SS7HSLPG2CNT


DID−name: SS7HSLPG2CNTDID−number: 651

Function: High speed Signalling Link parameter group Measurements

Position Contents1 Value of congestion onset for level 1. CNGONTH1 = (number of octets in TR/RTB when level 1 is reached/1000)2 Value of congestion onset for level 2. CNGONTH2 =(number of octets in TR/RTB when level 2 is reached/1000) 3 Value of congestion onset for level 3. CNGONTH3 =(number of octets in TR/RTB when level 3 is reached/1000)4 Value of congestion discard for level 1. CNGDITH1 =(number of octets in TR/RTB when level 1 is reached/1000)5 Value of congestion discard for level 2. CNGDITH2 = (number of octets in TR/RTB when level 2 is reached/1000)6 Value of congestion discard for level 3. CNGDITH3 = (number of octets in TR/RTB when level 3 is reached/1000)7 Value of congestion abatement for level 1. CNGABTH1 =(number of octets in TR/RTB when level 1 is reached/1000)8 Value of congestion abatement for level 2. CNGABTH2 =(number of octets in TR/RTB when level 2 is reached/1000)9 Value of congestion abatement for level 3. CNGABTH3 =(number of octets in TR/RTB when level 3 is reached/1000)Description:One record per parameter group for HSL in the block.The objects are identified by their record pointers.There are 8 parameter groups and each is identified by itsname and a number from 8 to 15The parameter group number is obtained by adding 8 tothe record pointer in the HSL parameter group file

5.210 M3DATACNT




DID−name: M3DATACNTDID−number: 658

Function: Counters for number of M3UA Transfer messages

Position Contents 1 State 2 Number of DATA messages sent 3 Number of DATA messages recieved 4 Number of DATA messages discarded

Description:The record pointer is used to enable translation to symbolicAssociation name using M3ASSOCTAB translation tableOne record per Association (1−1024).DID position 1 indicates if the record is used (=1)for an Association or not (=0).Size of variables:DID item position 1 = 1 bit.DID item positions 2−4 = 32 bits.

5.211 M3SSNMCNT


DID−name: M3SSNMCNTDID−number: 659

Function: Counters for number of M3UA SSNM messages

Position Contents 1 State 2 Number of DUNA messages sent 3 Number of DUNA messages received 4 Number of DAVA messages sent 5 Number of DAVA messages received 6 Number of DAUD messages sent 7 Number of DAUD messages received 8 Number of SCON messages sent 9 Number of SCON messages received 10 Number of DUPU messages sent 11 Number of DUPU messages received


5.212 M3ASPSMCNT


DID−name: M3ASPSMCNTDID−number: 660



Function: Counters for number of M3UA ASPSM messages

Position Contents 1 State 2 Number of ASPUp messages sent 3 Number of ASPUp messages received 4 Number of ASPUpAck messages sent 5 Number of ASPUpAck messages received 6 Number of ASPDown messages sent 7 Number of ASPDown messages received 8 Number of ASPDownAck messages sent 9 Number of ASPDownAck messages received


5.213 M3ASPTMCNT


DID−name: M3ASPTMCNTDID−number: 661

Function: Counters for number of M3UA ASPTM messages

Position Contents 1 State 2 Number of ASPActive messages sent 3 Number of ASPActive messages received 4 Number of ASPActiveAck messages sent 5 Number of ASPActiveAck messages received 6 Number of ASPInactive messages sent 7 Number of ASPInactive messages received 8 Number of ASPInactiveAck messages sent 9 Number of ASPInactiveAck messages received


5.214 M3MGMTCNT


DID−name: M3MGMTCNTDID−number: 662

Function: Counters for number of M3UA Management messages



Position Contents 1 State 2 Number of ERROR messages sent 3 Number of ERROR messages received 4 Number of NOTIFY messages received 5 Number of NOTIFY messages sent

Description:The record pointer is used to enable translation to symbolicAssociation name using M3ASSOCTAB translation table.

One record per Association (1−1024).

DID position 1 indicates if the record is used (=1)for an Association or not (=0).


DID Position Block Size1 M3UADR 1 bit 2−5 M3UADR 32 bits

5.215 M3ASSOCCNT


DID−name: M3ASSOCCNTDID−number: 663

Function: Counters for Association measurements

Position Contents 1 State 2 Number of times an Association becomes unavailable for traffic 3 Duration of unavailability of Association for traffic (number of seconds)

Description:The record pointer is used to enable translation to symbolicAssociation name using M3ASSOCTAB translation tableOne record per Association (1−1024).DID position 1 indicates if the record is used (=1)for an Association or not (=0).Size of variables:DID item position 1 = 1 bit.DID item position 2−3 = 16 bits.

5.216 M3DEST1CNT


DID−name: M3DEST1CNTDID−number: 665

Function: Counters for ITU−T and MPT destinations in M3UA

Position Contents 1 State 2 Number of times a destination becomes unreachable (route set unavailable)



3 Duration of inaccessibility of destination (number of seconds)

Description:The record pointer is used to enable translation to symbolicAssociation name using M3DEST1TAB translation table.One record per ITU−T and MPT destination (1−4079). The number ofrecords of this file is controlled by means of the SizeAlteration Event number 165.DID position 1 indicates if the record is used (=1)for an Association or not (=0).Size of variables:DID item position 1 = 1 bit.DID item position 2−3 = 16 bits.

5.217 M3DEST2CNT


DID−name: M3DEST2CNTDID−number: 666

Function: Counters for ANSI destinations in M3UA

Position Contents 1 State 2 Number of times a destination becomes unreachable (route set unavailable) 3 Duration of inaccessibility of destination (number of seconds)

Description:The record pointer is used to enable translation to symbolicAssociation name using M3DEST2TAB translation table.One record per ANSI destination (1−7537).The number of recordsof this file is controlled by means of the Size AlterationEvent number 19.DID position 1 indicates if the record is used (=1)for an Association or not (=0).Size of variables:DID item position 1 = 1 bit.DID item position 2−3 = 16 bits.

5.218 M3PERFCNT


DID−name: M3PERFCNTDID−number: 667

Function: Counters for M3UA performance

Position Contents 1 Routing, discrimination or distribution error

Description:The counter is presented as system total in a commonstored variable.Size of variable = 16 bits.



5.219 M3ASSOCTAB


DID−name: M3ASSOCTABDID−number: 668

Function: Translation table between Association pointer and Association identity

Position Contents 1 Symbolic name of Association (SAID)

Description:One record per Association (1−1024).Translation from Association pointer to symbolic Associationname.The output will look as follows (example):ASSOCIATIONMSCHLR1 (parameter string provided by operator as SAID)Size of variables:DID item position: 1 = string 7 characters

5.220 M3DEST1TAB


DID−name: M3DEST1TABDID−number: 670

Function: Translation table from Signalling Point pointer to network address (ITU)

Position Contents 1 BCD Address representation of a SP

Description:One record per destination (1−4079).Translation from destination pointer to symbolicdestination identifier.The external address should be presented as:NI−SPC, NI−MSA−SSA−CSP

Example of BCD string and the output string in STS. BCDSPR(0) = 2; BCDSPR(1) = 10; ! HYPHEN IS REPRESENTED BY H’A ! BCDSPR(2) = 1; BCDSPR(3) = 2; BCDSPR(4) = 3; BCDSPR(5) = 10; ! HYPHEN IS REPRESENTED BY H’A ! BCDSPR(6) = 1; BCDSPR(7) = 5; BCDSPR(8) = 6; BCDSPR(9) = 10; ! HYPHEN IS REPRESENTED BY H’A ! BCDSPR(10) = 7; BCDSPR(11) = 8; BCDSPR(12) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! BCDSPR(13) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! BCDSPR(14) = 15; ! EMPTY SPACE REPRESENTED BY H’F !



BCDSPR(15) = 15; ! EMPTY SPACE REPRESENTED BY H’F !

The output by STS should be presented as:DESTINATION2−123−156−78Size of variable = string 16 BCD characters

5.221 M3DEST2TAB


DID−name: M3DEST2TABDID−number: 671

Function: Translation table from Signalling Point pointer to network address (ANSI)

Position Contents 1 BCD Address representation of a SP

Description:One record per destination (1−7537).Translation from destination pointer to symbolicdestination identifier.The external address should be presented as:NETWORK−CLUSTER−MEMBER

Example of BCD string and the output string in STS. BCDSPR(0) = 2; BCDSPR(1) = 10; ! HYPHEN IS REPRESENTED BY H’A ! BCDSPR(2) = 1; BCDSPR(3) = 2; BCDSPR(4) = 3; BCDSPR(5) = 10; ! HYPHEN IS REPRESENTED BY H’A ! BCDSPR(6) = 1; BCDSPR(7) = 5; BCDSPR(8) = 6; BCDSPR(9) = 10; ! HYPHEN IS REPRESENTED BY H’A ! BCDSPR(10) = 7; BCDSPR(11) = 8; BCDSPR(12) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! BCDSPR(13) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! BCDSPR(14) = 15; ! EMPTY SPACE REPRESENTED BY H’F ! BCDSPR(15) = 15; ! EMPTY SPACE REPRESENTED BY H’F !

The output by STS should be presented as:DESTINATION123−156−78Size of variable = string 16 BCD characters

5.222 SUCORCLCNT


DID−name: SUCORCLCNTDID−number: 692

Function: Counters for number of successful optimally routed calls

Position Contents



1 Number of successful optimally routed calls in MSC/VLR 2 Number of successful optimally routed calls in GMSC server

Description:The counters are stored as common stored variables.

Size of the variables.Position Size1 16 bits2 16 bits

5.223 MSCOOBTCCNT


DID−name: MSCOOBTCCNTDID−number: 704

Function: Counters for OOBTC statistics in node. (MSC/GMSC/TSC)

Position Contents 1 Number of calls where OoBTC is successfully performed and speech compression using Narrow−Band Codecs is applied on incoming Nb side 2 Number of calls where OoBTC is successfully performed and speech compression using Narrow−Band Codecs is applied on outgoing Nb side 3 Number of calls where OoBTC is successfully performed and speech compression is not applied on incoming Nb side 4 Number of calls where OoBTC is successfully performed and speech compression is not applied on outgoing Nb side 5* Number of calls where OoBTC is successfully performed and speech compression using AMR−WB codecs is applied on incoming Nb side 6* Number of calls where OoBTC is successfully performed and speech compression using AMR−WB codecs is applied on outgoing Nb side


Description:Counters are used for OOBTC statistics on node (MSC/GMSC/TSC) level.This DID is system total, that is only one instance.All the variables (DID item positions 1−6) are stored as common variables in block BIPHT and BIPHTI.

The size of the variables:Position Block Size1 BIPHT, BIPHTI 32 bits 2 BIPHT, BIPHTI 32 bits 3 BIPHT, BIPHTI 32 bits 4 BIPHT, BIPHTI 32 bits 5 BIPHT, BIPHTI 32 bits 6 BIPHT, BIPHTI 32 bits

5.224 NSEPCALLCNT




DID−name: NSEPCALLCNTDID−number: 719

Function: Node counters for Wireless Priority Service statistics.

Position Contents 1 Number of MO WPS call requests. 2 Number of successful MO WPS calls after successful TCH assignment. 3 Number of MO GETS call requests. 4 Number of MT NS/EP calls. 5 Number of MT NS/EP calls after successful TCH. 6 Number of unsuccessful NS/EP calls, not possible to be routed out of the exchange on an o/g trunk. 7 Number of NS/EP calls received from incoming trunks. 8 Number of NS/EP calls received from incoming trunks, without the Precedence parameter. 9 Number of NS/EP calls with an established signalling link to the succeeding exchange. 10 Total number of times that NS/EP calls fail to queue because the maximum queue length has been reached. 11 Total number of times that NS/EP calls are removed from a trunk queue due to queue timer expiry. 12 Number of queued NS/EP calls released due to a forward release. 13 Number of NS/EP calls that have been queued. 14 Number of outgoing NS/EP calls that require a trunk. 15 Number of NS/EP call received on incoming trunks whose destination is an MS served by this MSC. 16 Number of NS/EP calls with an established signalling link to the succeeding IXC exchange. 17 Number of unsuccessful NS/EP calls to an IXC, not possible to be routed out of the exchange on an o/g trunk. 18 Number of mobile terminating NS/EP calls for which polling for a MGW is done. 19 Number of mobile terminating NS/EP calls for which attempts to select a MGW have been abandoned due to a forward release indication during polling. 20 Number of NS/EP calls for which polling for a MGW is done. 21 Number of NS/EP calls for which attempts to select a MGW have been abandoned due to a forward release indication during polling. 22 Number of times the polling timer has expired for NE/EP calls.

Description:The functionality of the counters 1 − 5 is described in [MP1].Counter 6 is implemented in TRAM and is described in detail in [MP30].Counters for NS/EP call on the incoming routes with and without precedence parameter (positions 7 and 8) are implemented in TSS. In order to get the total number of NS/EP calls on the incoming routes, STS needs to add the counter values reported by the blocks in TSS, where those counters are implemented and represent the total value on the node basis. For details on the implementationof the counters, see [MP30]. Positions 9, 10, 11, 12 and 16 are implemented in TSS. In order to get the total value on node basis,



STS needs to add the counter values reported by the blocks in TSS where those counters are implemented and represent the value on the node basis. For details on the implementation of the counters, see this document. Positions 13, 14 and 17 are implemented in TRAM and is described in detail in this document.Position 15 is implemented in MAGAM and is described in detailin this document.

For the new polling counters in DID item positions 20 and 21, theshared counter implementation concept will be used. This means that DID position can be counted in different blocks and arereported to the same counter object. STS then adds up the valuesfrom the different jobs and presents one value to the operator.

The size of the variables.DID position Block Size1 − 3 MTACC 32 bits4 − 5 MTB 32 bits6 − 8 TRARE 32 bits9 BT4,UPD24,BIPHT 32 bits10 − 12 BT4,UPD24 32 bits13 − 14 TRARE 32 bits15 MTB 32 bits16 BT4,UPD24,BIPHT 32 bits17 TRARE 32 bits18 − 19 MTB 32 bits20 − 21 MTB,BIPHT 32 bits22 BIPHT 32 bits

5.225 TQROUTECNT


DID−name: TQROUTECNTDID−number: 720

Function: Route counters for Trunk Queuing capable routes

Position Contents 1 Global Route Number. 2 Number of seizure attempts (bids) for the NS/EP calls. 3 Number of times that NS/EP calls are inserted in a trunk queue. 4 Number of queued NS/EP calls released due to a forward release. 5 Number of NS/EP calls with a established signalling link to the succeeding exchange. 6 Number of times that NS/EP calls fail to queue because the maximum queue length has been reached. 7 Number of times that NS/EP calls are removed from a trunk queue due to queue timer expiry.

Description:DID item position one is global route pointer which needs to be translated to symbolic route name, using the existing translationtable DID ROUTETRANTAB, DID number 46. The functionality of other counters is described in [MP30]. (DID ROUTETRANTAB).

The size of the variables:Position Size



1−7 32 bits

5.226 PRBTCALLCNT


DID−name: PRBTCALLCNTDID−number: 722

Function: Counters for Personalized Ring Back Tone statistics.

Position Contents 1 Total number of Personalized Ring Back Tone invocations. 2 Number of successful Personalized Ring Back Tone invocations.

Description:Counters for number of total and number of successful PRBT invocationsThis new DID is used by block GORC. All variables are stored as Common data.

The size of the variables:Position Size1 − 2 32 bits

5.227 NMSCSRNSCNT


DID−name: NMSCSRNSCNTDID−number: 745

Function: Neighbouring MSC Level Statistics for Inter−MSC SRNS RELOCATION.

DID item Contentsposition1 Number of basic RELOCATION traffic to traffic attemtps to neighboring MSC2 Number of basic RELOCATION signalling to signalling attemtps to neighboring MSC3 Number of subsequent relocation traffic to traffic attempts from neighbouring MSC back to anchor MSC for each neighbouring MSC.4 Number of subsequent relocation signalling to signalling attempts from neighbouring MSC back to anchor MSC for each neighbouring MSC.5 Number of subsequent relocation traffic to traffic attempts from neighbouring MSC to third MSC for each neighbouring MSC6 Number of subsequent relocation signalling to signalling attempts from neighbouring MSC to third MSC for each neighbouring MSC7 Number of successful basic relocation traffic to traffic to neighbouting MSC. 8 Number of successful basic relocation signalling to signalling to neighbouting MSC9 Number of successful subsequent relocation traffic to traffic from neighbouring MSC back to anchor MSC for each neighbouring MSC.10 Number of successful subsequent relocation signalling to signalling from neighbouring MSC back to anchor MSC



for each neighbouring MSC.11 Number of successful subsequent relocation traffic to traffic from neighbouring MSC to third MSC for each neighbouring MSC.12 Number of successful subsequent relocation signalling to signalling from neighbouring MSC to third MSC for each neighbouring MSC.13 Number of incoming relocation traffic to traffic attempts from neighbouring MSC (incoming handovers include basic relocations and subsequent relocations from neighbouring MSC)14 Number of incoming relocation signalling ro signalling attempts from neighbouring MSC (incoming handovers include basic relocations and subsequent relocations from neighbouring MSC.15 Number of successful incoming relocations traffic to traffic from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC)16 Number of successful incoming relocations signalling to signalling from neighbouring MSC (incoming handovers include basic handovers and subsequent handovers from neighbouring MSC).17 Number of subsequent relocation traffic to traffic attempts to neighbouring MSC (back to anchor or to third MSC).18 Number of subsequent relocation signalling to signalling attempts to neighbouring MSC (back to anchor or to third MSC).19 Number of successful subsequent relocations traffic to traffic to neighbouring MSC (back to anchor or to third MSC).20 Number of successful subsequent relocations signalling to signalling to neighbouring MSC (back to anchor or to third MSC).21 A subsequent channel assignment attempt should be counted in anchor MSC, when the request for the handover number is sent.22 A subsequent channel assignment attempt should be counted in anchor MSC, when the request for the handover number is sent.23 In a subsequent channel assignment attempt should be counted in nonanchor MSC, when the request for the handover number is received.24 A successful channel assignment should be counted in non−anchor MSC, if RANAP RAB ASSIGNMENT COMPLETE message is sent on the E−interface and if the B−answer is sent on the PSTN/ISDN.25 Number of incoming relocation rejections from neighbouring MSC due to MSC Pool redistribution activities (incoming relocations include basic relocations and subsequent relocation from neighbouring MSC)

Description: One record per neighbouring MSC in the blocks. Inpractice, it is conceivable for one particular MSC tohave 5 neighbours.The pointer for MSC is the same in all blocks. It isthe same as the pointer in the MSC translation table in block MTRAN (DID: MSCTAB). Pointer 0 is used in case of ’unknown MSC’.The counters specified in DID positions 1−12 are stored inblock MUREL.The counters specified in DID positions 21−22 are stored inblock MUHOC.The counters specified in DID positions 13−20 and 23−25 are stored



in block MUHIC.

The size of the variables.DID position Block Size1 − 12 MUREL 32 BITS13 − 20 MUHIC 32 BITS21 − 22 MUHOC 16 BITS23 − 25 MUHIC 32 BITS

5.228 PMROUTECNT


DID−name: PMROUTECNTDID−number: 747

Function: Route counters for polling capable routes.

DID item Contentsposition1 Global Route Number.2 Number of seizure attempts (bids) for the NS/EP calls.3 Number of times polling for a Media Gateway is done.4 Number of times attempts to select a Media Gateway has been abandoned due to a forwards release indication received during polling.5 Number of NS/EP calls for which an outgoing route is successfully set up to a succeeding switch.6 Number of times the maximum time span (polling time) for selecting a Media Gateway has been expired.

Description: DID item position one is global route pointer which needs to be translated to symbolic route name, using the existing translation table DID ROUTETRANTAB, DID number 46.

The size of the variables:DIDposition Block Size1 BID,BIPHT 16 bits2 BID 32 bits3 − 6 BIPHT 32 bits

5.229 NRTCFASERCNT


DID−name: NRTCFASERCNTDID−number: 748

Function: Node level counters for RTCfA for end−user services.

DID item position Contents1 Total Number of RTCfA requests for calls.2 Number of successfully real−time charged calls.3 Total Number of RTCfA requests for SMStransactions.



4 Number of successfully real−time charged SMS transactions.

Description:All the variables are stored as record stored data.The record number of the file being reported is used to identifythe measurement objects.

The size of the variables and the reporting block:DID position Block Size1 − 4 RTCSC 32 bits

5.230 NRTCAPCNT


DID−name: NRTCAPCNTDID−number: 749

Function: Counters for RTCAP usage.

DID item position Contents1 Number of successfully answered RTCAP Credit Control Operations.2 Number of failed RTCAP Credit Control operations. Description:All the variables are stored as record stored data.The record number of the file being reported is used to identify the measurement objects.

The size of the variables and the reporting block:DID position Block Size1 − 2 RTCMH 32 bits

5.231 TRTYPECNT3


DID−name: TRTYPECNT3DID−number: 752

Function: Additional Traffic Type Counters

Position Contents1 Traffic level, number of ongoing through−connected calls2 B−answer Traffic level, number of ongoing B−answered calls3 Number of Data Calls4 Number of Unsuccessful Calls5 Traffic Level, number of ongoing through connected Data calls6 B−Answer Traffic Level, Number of ongoing B−Answered Data Calls7 Number of Data Calls rejected due to internal congestion8 Number of Data Calls rejected due to external congestion9 Number of Data Calls that reached End−of−selection stage successf10 Number of Answered Data Calls

Description:This DID includes additional counters for Basic Traffic Types.



One set of counters is provided for each basic traffic type.A basic traffic type is a combination of an originating code and adestination type (see FS Traffic Measurement on Traffic Types, 1/155 17−CNT 216 2531). There are 16 originating codes and 16 destination types,resulting in a total of 256 basic traffic types (DID instances).

DID item positions 1 and 2 are stored each in an indexed record variablein block TRARE. The file has a fixed size of 16 records corresponding tothe originating code and each indexed record variable has 16 indexescorresponding to the destination type.

The size of the variables:Position Block Size1 TRARE 32 bits2 TRARE 32 bits3 TRARE 32 bits4 TRARE 32 bits5 TRARE 32 bits6 TRARE 32 bits7 TRARE 32 bits8 TRARE 32 bits9 TRARE 32 bits10 TRARE 32 bits

5.232 GANDIREPACNT

−VALID FOR APG

DID−name: GANDIREPACNTDID−number: 757

Function: Statistics related to discovery, registration and pagings.

Application: Block: HURR, HPAG, HUMSGH

DID Item ContentsPosition1 Discover requests received2 Discover requests rejected3 Registration attempts4 Registration rejects, congestion5 Registration rejects, Loc. not allowed6 Registration rejects, invalid GANC7 Registration rejects, Geo loc not known8 Registration redirections external9 Registration redirections internal10 GARC Status message received11 Pagings CS from MSC received12 Pagings CS from MSC MS not registered13 Pagings CS from SGSN received14 Pagings CS from SGSN MS not registered15 Pagings CS answered16 Pagings PS received17 Pagings PS MS not registered Description:This DID contains counters related to discovery, registration andpagings.DID item positions 1−10 are stored in HURR block as common storedvariables.DID item positions 11−14 and 16−17 are stored in HPAG block as commonstored variables.DID item position 15 is stored in HUMSGH block as common stored variable.



This DID is a system total with only one instance.

The size of the variables.DID position Block Size1 − 10 HURR 3211 − 14 HPAG 3215 HUMSGH 3216 − 17 HPAG 32

5.233 GANRPLOADCNT

−VALID FOR APG

DID−name: GANRPLOADCNTDID−number: 758

Function: Statistics related to load in regional functions.

DID item Contentsposition1 STIP RP load 0−39%2 STIP RP load 40−59%3 STIP RP load 60−79%4 STIP RP load 80−89%5 STIP RP load 90−100%6 IGW RP load 0−39%7 IGW RP load 40−59%8 IGW RP load 60−79%9 IGW RP load 80−89%10 IGW RP load 90−100%11 PCU RP load 0−39%12 PCU RP load 40−59%13 PCU RP load 60−79%14 PCU RP load 80−89%15 PCU RP load 90−100%

Description:This DID contains counters related to processor load in regionalfunctions.DID item positions 1−5 are stored in HURR block as common storedvariables.DID item positions 6−10 are stored in HIGW block as common storedvariables.DID item positions 11−15 are stored in HRLC block as common storedvariables.This DID is a system total with only one instance.The size of the variables.DID position Block Size1 − 5 HURR 326 − 10 HIGW 3211 − 15 HRLC 32

5.234 DEFMGWCNT

−VALID FOR APG

DID−name: DEFMGWCNTDID−number: 770Function: Counters per defined MGW

DID item Contentsposition1 Status



2 Number of Ephemeral Terminations with pending release3 Number of Add and Move commands that request seizure of a new context4 Number of successful Add and Move commands that requested seizure of a new context5 Number of sent GCP messages6 Number of received GCP messages7 Number of sent GCP octets8 Number of received GCP octets9 Number of sent GCP transaction retransmissions10 Number of received GCP transaction pending messages11 Number of transactions, containing an Add, Move or Modify command, and/or a Topology Descriptor, that fail due to no transaction reply being received12 Number of transactions, containing an Audit Value, Subtract or Service Change command, that fail due to no transaction reply being received13 Number of transactions, where the maximum number of GCP transaction pending messages has been received14 Number of seconds the MGW is not reachable for the MSC server15 Number of seconds the MGW is not reachable for the MSC server due to signalling outage 16 Number of times the MGW becomes not reachable for the MSC server due to signalling outage17 Number of received notifications, including the ’MGW Congestion’ Event, for which the ’Reduction’ parameter indicates an allowed load increase18 Number of received notifications, including the ’MGW Congestion’ Event, for which the ’Reduction’ parameter indicates a required load decrease, MGW Traffic Reduction Percentage indicates a value higher than 0 but lower than, or equal to, 25%19 Number of received notifications, including the ’MGW Congestion’ Event, for which the ’Reduction’ parameter indicates a required load decrease, MGW Traffic Reduction Percentage indicates a value higher than 25% but lower than, or equal to, 50%20 Number of received notifications, including the ’MGW Congestion’ Event, for which the ’Reduction’ parameter indicates a required load decrease, MGW Traffic Reduction Percentage indicates a value higher than 50% Description:This DID describes counters per defined MGW.DID item position 1 should be used as indicator whether the individual is used and should be printed in the STS report or whether it is not used and should not be printed in the STSreport0 − not used, should not be printed1 − used, should be printedThis DID uses Translation table DID MGNAMETAB.The counters are stored as a record data either in block GAMGW or in block GCPH or in block NRM.One record per MGW exists.



The identification of the records shall be the MGW name provided by new translation DID MGNAMETAB.The maximum number of records reported is 65535.To alter the file size the size alteration event number 1134 is to be used.

The size of the variables.DID position Block Size1 GAMGW 1 bit2 GAMGW 32 bits3 GAMGW 32 bits4 GAMGW 32 bits5 GCPH 32 bits6 GCPH 32 bits7 GCPH 32 bits8 GCPH 32 bits9 GCPH 32 bits10 GCPH 32 bits11 GCPH 32 bits12 GCPH 32 bits13 GAMGW 32 bits14 NRM 32 bits15 NRM 32 bits16 NRM 32 bits17 NRM 32 bits18 NRM 32 bits19 NRM 32 bits20 NRM 32 bits

5.235 LOCUPDA2CNT


DID−name: LOCUPDA2CNTDID−number: 777Function: Counters for location updating

DID item Contentsposition1 Number of normal location updating attempts for already registered subscribers over A and Iu−interface2 Number of successful normal location updatings for already registered subscribers over A and Iu−interface3 Number of successful IMSI attached location updatings for already registered subscribers over A and Iu−interface4 Number of successful periodic location updatings over A and Iu−interface5 Number of successful IMSI attached location updatings for already registered subscribers over Gs interface6 Number of location updating attempts from non−registered subscribers (IMSI attach, normal location updating or periodic location updating) on intermediate MSC−blade after failed authentication with TMSI7 Number of location updating attempts for already registered subscribers on intermediate MSC−blade after failed authentication with TMSI8 Number of periodic location updating attempts for already registered subscribers on intermediate MSC−blade after failed



authentication with TMSI9 Number of periodic location updating requests for non−registered on intermediate MSC−blade after failed authentication with TMSI10 Number of normal location updating attempts for already registered subscribers over A and Iu−interface on intermediate MSC−blade after failed authentication with TMSI

Description:All the variables are stored as common data.DID item positions 1−10 are peg counters.Counter specified in DID positions 1, 6−8, 10 are stored in blockMVLRP.Counters specified in DID positions 2−4, 9 are stored in blockMMMLR.Counter specified in DID position 5 is stored in block MGPRO.Blocks MMMLR, MGPRO and MVLRP belong to the subsystem MMS.

The size of the variables.DID position Block Size1 MVLRP 32 bits2−4 MMMLR 32 bits5 MGPRO 32 bits6−8 MVLRP 32 bits9 MMMLR 32 bits10 MVLRP 32 bits

5.236 NBRMSCL3CNT


DID−name: NBRMSCL3CNTDID−number: 798Function: Counters for inter−MSC handover on neighboring MSC level

DID item Contents Counter nameposition1 Number of incoming hadnover rejections from NNREDREJ neighbouring MSC due to MSC Pool redistribution activities (incoming handovers include basic handovers and subequent handovers from neighbouring MSC)


The size of the variables:DID position Block Size1 MHIC 16 bits

5.237 SUBSVLRCNT




DID−name: SUBSVLRCNTDID−number: 799Function: Counters VLR subscribers.

DID item Contents Counter nameposition1 Number of registered VLR subscribers. TNSVLR2 Number of registered subscribers that are in TNSPEND status "Pending Redistribution".3 Number of registered subscribers in Location TNSEXTP Areas external to the pool not being Gs attached.4 Number of registered subscribers via the TNSATGS Gs interface.5 Number of registered subscribers with primary TNSPRSEXOUTD subscription including ones with incomplete data (subscribers known only with IMSI) and excluding the outdated ones.6 Total number of primary active subscriptions CODCNT1PACT per blade7 Total number of primary passive subscriptions CODCNTPPASS per blade8 Total number of buddy active subscriptions CODCNT2BACT per blade9 Total number of buddy passive subscriptions CODCNTBPASS per blade

Description:

All the variables are stored as common data.DID item positions: 1−9 = 32 bits

The counters specified in DID positions 1−9 are stored inblock MTV.

Block MTV belongs to the subsystem MDS


DID position Block Size1 MTV 32 bits2 MTV 32 bits3 MTV 32 bits4 MTV 32 bits5 MTV 32 bits6 MTV 32 bits7 MTV 32 bits8 MTV 32 bits9 MTV 32 bits

5.238 INTTRAFCNT

−VALID FOR APG

DID−name: INTTRAFCNTDID−number: 805Function: Counters for Internal Traffic in MSC−S BC environment

DID item ContentsPosition



1 State2 Number of calls to destination Blade (CALLDBLD)3 Number of B−Answers received from destination (BANSWDBLD) Blade4 Number of unsuccessful calls to destination (UNSUCCFULDBLD) blade5 Number of seizure attempts for mobile (MTERMCNT) terminating traffic to destination Blade6 Traffic Level per blade (TRALBLD)7 Number of seizure attempts per blade (NCALLSBLD)

Description:One set of counters is defined for each ’destination blade’.DID item 1 is a state value indicating if the respective blade is available at all or not (0 = not available).DID items 2 − 7 are stored in a ’blade counter’ file in the block INTRO. This file has the fixed size 64.The following sizes of the variables are used:DID Position Block Size 1 INTRO 1 Bit 2 INTRO 32 Bit 3 INTRO 32 Bit 4 INTRO 32 Bit 5 INTRO 32 Bit 6 INTRO 32 Bit 7 INTRO 32 Bit

5.239 MGNAMETAB

−VALID FOR APG

DID−name: MGNAMETABDID−number: 811Function: MGW Translation Table

DID item Contents position1 MGW Name Description:This DID translates from the position in the file to the MGW Name. According to command NRGWI up to 7 characters can be used for a MGW Name.One record per MGW exists in block NRM.The maximum number of records is 65535.To alter the file size the size alteration event number 1134 is to be used.

DID position Block Size1 NRM string 7 characters

5.240 RNCCODERSTATCNT


DID−name: RNCCODERSTATCNTDID−number: 819Function: Counters for speech coder in RAB assignment per RNC.

DID item Contents Counter nameposition1 Number of RAB assignments NRFRMAMR



from mobile subscriber with UMTSAMR as codec type2 Number of RAB assignments NRFRM2AMR from mobile subscriber with UMTSAMR2 as codec type3 Number of RAB assignments from NRFRMWBAMR mobile subscriber with UMTSAMR−WB as codec type 4 Number of RAB assignments NRTOAMR to mobile subscriber with UMTSAMR as codec type5 Number of RAB assignments NRTO2AMR to mobile subscriber with UMTSAMR2 as codec type6 Number of RAB assignments NRTOWBAMR to mobile subscriber with UMTSAMR−WB as codec type

Description:All the variables are stored in record related data.The translation table RNCTAB will be used to translate from the internalrecord number to the symbolic RNC name.The counters are stepped per RNC.The counters specified in DID positions 1−6 are stored in block MURABP.Block MURABP belong to subsystem MMS.The size of the variables:DID item positions: 1−6 = 32 bits

The size of the variables:DID position Block Size1−6 MURABP 32 bits

5.241 MIBIPV4GCNT

−VALID FOR APG

DID−name: MIBIPV4GCNTDID−number: 837Function: IETF RFC 4293 IPv4 counters.

DID item Contents position1 Indicates if this entity acts as an IPv4 router or not (IPv4 routers forwards datagrams, IPv4 hosts do not).2 Default value for IPv4 TTL header field.3 Maximum number of seconds received fragments are held while awaiting reassembly.Description:This system total DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the ipv4GeneralGroup OBJECT−GROUP.See RFC 4293 for more detailed documentation about the individual counters.DID item positions 1−3 are status counters.

The size of the variables:DID position Block Size1−3 VMIPSTS 32 bits

5.242 MIBIPSSTCNT



−VALID FOR APG

DID−name: MIBIPSSTCNTDID−number: 838Function: IETF RFC 4293 IP related counters per IP protocolversion.

DID item Contents position1 IP protocol version2 Total number of received IP datagrams.3 Number of discarded IP datagrams due to IP header errors.4 Number of discarded IP datagrams due to unknown or unsupported protocol.5 Number of received IP fragments needing reassembly.6 Number of successfully reassembled IP datagrams.7 Number of failures detected during reassembly.8 Number of discarded IP datagrams due to lack of resources.9 Number of successfully delivered IP datagrams.10 Total number of non−forward IP datagram delivery requests.11 Number of discarded IP datagrams due to no route to destination.12 Number of discarded IP datagrams due to lack of resources.13 Number of successfully fragmented IP datagrams.14 Number of discarded IP datagrams due to that they could not be fragmented.15 Number of fragmented IP datagrams.16 Total number of received IP datagrams. High 32 bits.17 Number of octets received in input IP datagrams, including those received in error. Low 32 bits.18 Number of octets received in input IP datagrams, including those received in error. High 32 bits.19 Number of input IP datagrams discarded because of invalid address in the IP header’s destination field.20 Number of input IP datagrams discarded because the datagram frame didn’t carry enough data.21 Number of successfully delivered IP datagrams. High 32 bits.22 Total number of non−forward IP datagram delivery requests. High 32 bits.23 Number of outgoing IP datagrams requiring fragmentation.24 Value of sysUpTime on the latest occasion at which any counter suffered a discontinuity.Description:This DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the ipSystemStatsTable OBJECT−TYPE (one ipSystemStatsEntry per IP protocol version).See RFC 4293 for more detailed documentation about the individual counters.DID item position 1 is translated to IP protocol version name in position 2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).The size of the variables:DID position Block Size1 VMIPSTS 8 bits2−24 VMIPSTS 32 bits

5.243 MIBICMPSTCNT

−VALID FOR APG

DID−name: MIBICMPSTCNTDID−number: 839



Function: IETF RFC 4293 ICMP related counters per IP protocolversion.

DID item Contents position1 IP protocol version.2 Total number of received ICMP messages.3 Number of received faulty ICMP messages.4 Total number of sent ICMP messages.5 Number of not sent ICMP messages due to problems in ICMP.Description:This DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the icmpStatsTable OBJECT−TYPE (one icmpStatsEntry per IP protocol version).See RFC 4293 for more detailed documentation about the individual counters.DID item position 1 is translated to IP protocol version name in position 2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).The size of the variables:DID position Block Size1 VMIPSTS 8 bits2−5 VMIPSTS 32 bits

5.244 MIBICMPMSGSTCNT

−VALID FOR APG

DID−name: MIBICMPMSGSTCNTDID−number: 840Function: IETF RFC 4293 ICMP related counters per IP protocolversion.

DID item Contents position1 State2 IP protocol version.3 ICMP type field.4 Number of input packets for this address family and type.5 Number of output packets for this address family and type.Description:This DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the icmpMsgStatsTable OBJECT−TYPE (one icmpStatsEntry per IP protocol version and ICMP type value).See RFC 4293 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).The symbolic name for each valid object (or individual) is created from concatenating two strings and separating them with a ’−’ (hyphen) character. The first string is obtained by translating DID item position 2 to IP protocol version name in position 2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB). The second string is obtained by translating DID item position 3 to ICMP type field name in position 3 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).For instance if DID item position 2 contains the value ’1’ (one) and DID item position 3 contains the value ’3’, then this would result in the strings "and "DESTUNREACH" being translated (IETF RFC 4001, section 3 (page 6), maps the value ’1’ (one) to IPv4, and IETF RFC 792 maps the value ’3’ to "Destination Unreachable").These two strings, "V4" and "DESTUNREACH", are concatenated and separated using a ’−’ (hyphen), in order to form the string "V4−DESTUNREACH".The size of the variables:DID position Block Size1 VMIPSTS 1 bit2 VMIPSTS 8 bits3−5 VMIPSTS 32 bits



5.245 MIBUDPBASECNT

−VALID FOR APG

DID−name: MIBUDPBASECNTDID−number: 842Function: IETF RFC 4113 UDP related counters.

DID item Contents position1 Total number of delivered datagrams to UDP users.2 Total number of received datagrams with no application at destination port.3 Number of undelivered datagrams due to other reasons than no application at destination port.4 Total number of sent datagrams.Description:This system total DID contains the counters defined in IETF RFC 4113, "Management Information Base for the User Datagram Protocol (UDP)", udpBaseGroup OBJECT−GROUP.See RFC 4113 for more detailed documentation about the individual counters.The size of the variables:DID position Block Size1−4 VMIPSTS 32 bits

5.246 MIBIFTABLECNT

−VALID FOR APG

DID−name: MIBIFTABLECNTDID−number: 843Function: IETF RFC 2863 interface related counters.

DID item Contents position1 State2 Interface pointer3 Interface number4 Total number of received octets on the interface, including framing characters.5 Number of wraparounds for total number of received octets on the interface, including framing characters.6 Number of packets delivered to a unicast address.7 Number of wraparounds for packets delivered to a unicast address.8 Number of packets discarded before delivery.9 Number of wraparounds for packets discarded before delivery.10 Number of faulty packets preventing them to be delivered to a higher−layer protocol. 11 Number of wraparounds for faulty packets preventing them to be delivered to a higher−layer protocol.12 Number of discarded packets due to unknown or unsupported protocol.13 Number of wraparounds for discarded packets due to unknown or unsupported protocol.14 Total number of sent octets on the interface, including framing characters.15 Number of wraparounds for total number of sent octets on the interface, including framing characters.16 Number of sent packets to a unicast address.17 Number of wraparounds for sent packets to a unicast



address.18 Number of packets discarded before being sent.19 Number of wraparounds for packets discarded before being sent.20 Number of packets that could not be transmitted due to errors.21 Number of wraparounds for packets that could not be transmitted due to errors.Description:This DID contains a subset of the counters defined in IETF RFC 2863, "The Interfaces Group MIB", ifTable OBJECT−TYPE (one ifEntry per interface). It also contains a number of non−standard counters that tracks the number of wraparounds that has occurred for the respective counters.See RFC 2863 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).DID item position 2 is a pointer, the pointer value can be translated to an interface name in position 1 of the MIBVMIPSTSTAB translation table (DID MIBVM IDID item position 3 is the interface number which is used when naming the corresponding Objects/instances/individuals, see documentation for the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.The size of the variables:DID position Block Size1 VMIPSTS 1 bit2−21 VMIPSTS 32 bits

5.247 MIBIFXTABLECNT

−VALID FOR APG

DID−name: MIBIFXTABLECNTDID−number: 844Function: IETF RFC 2863 interface related counters.

DID item Contents position1 State2 Interface pointer3 Interface number4 Number of packets delivered to a multicast address.5 Number of wraparounds for packets delivered to a multicast address.6 Number of packets delivered to a broadcast address.7 Number of wraparounds for packets delivered to a broadcast address.8 Number of sent packets to a multicast address.9 Number of wraparounds for sent packets to a multicast address.10 Number of sent packets to a broadcast address.11 Number of wraparounds for sent packets to a broadcast address.12 Value of sysUpTime on the latest occasion at which any counter suffered a discontinuity.

Description:This DID contains a subset of the counters defined in IETF RFC 2863, "The Interfaces Group MIB", ifXTable OBJECT−TYPE (one ifXEntry per interface). It also contains a number of non−standard counters that tracks the number of wraparounds that has occurred for the respective counters.See RFC 2863 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).DID item position 2 is a pointer, the pointer value can be translated to an interface name in position 1 of the MIBVMIPSTSTAB translation table (DID MIBVM IDID item position 3 is the interface number which is used when naming the



corresponding Objects/instances/individuals, see documentation for the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.

The size of the variables:DID position Block Size1 VMIPSTS 1 bit2−12 VMIPSTS 32 bits

5.248 MIBVMIPSTSTAB

−VALID FOR APG

DID−name: MIBVMIPSTSTABDID−number: 852Function: Translation Table for IETF RFC 2863 and 4293 relatedcounters.

DID item Contents position1 IETF RFC 2863 symbolic interface names2 IETF RFC 4293 symbolic IP version names3 IETF RFC 792 and IETF RFC 950 symbolic ICMP type names4 IETF RFC 1612 opcode name5 IETF RFC 1612 response code name

Description:Position 1 is used when translating from symbolic interface number tosymbolic interface name. This Translation Table DID position contains aprefix for the interface name (e.g. "ETHA" or "ETHB") which should beconcatenated with ’−’ (hyphen or minus) and followed with the "Interfacenumber" stored in position 3 of the corresponding DID (e.g. forming aninterface name looking like "ETHA−22"). The interface pointer is used forlooking up the prefix name in the Translation Table DID. This correspondsto the string in the object ifName in RFC 2863 "IF−MIB". However, stringsare only included in this Translation DID.Position 2 translates from symbolic IP version number to symbolic IPversion name, where the symbolic IP version number is identical to the IPprotocol version ID counter.If both position 1 and 2 are used, the result of the translation fromposition 2 is concatenated with ’−’ (hyphen or minus) and followed withthe translation as described in the first paragraph above.Position 3 translates from symbolic ICMP type code to symbolic ICMP typename, where the symbolic ICMP type code is identical to the ICMP typecode ID counter.Position 4 translates from opcode number to symbolic opcode name, wherethe opcode number is identical to the opcode.Position 5 translates from response code number to symbolic response codename, where the response code number is identical to the response code.

The complete table of symbolic interface names looks like this

InterfaceNumber Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−1 ETHA Ethernet interface for physical A−plane in CP2 ETHB Ethernet interface for physical B−plane in CP

The complete table of IP version names (according to IETF RFC 4293) looks Like this (with AXE specific slogan added)

IP VersionNumber Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−1 V4 IPv42 V6 IPv6



The complete table of ICMP type codes (IETF RFC 792 and IETF RFC 950 combined, IETF RFC 950 adds two ICMP type codes for "Address Mask Request" and "Address Mask Reply") looks like this (with AXE specific slogan added)

ICMP TypeCode AXE Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−0 ECHOREPLY Echo Reply3 DESTUNREACH Destination Unreachable4 SOURCEQUENCH Source Quench5 REDIRECT Redirect8 ECHO Echo11 TIMEEXCEEDED Time Exceeded12 PARAMPROBLEM Parameter Problem13 TMESTAMP Timestamp14 TMESTAMPRPLY Timestamp Reply15 INFOREQUEST Information Request16 INFOREPLY Information Reply17 ADDRMASKREQ Address Mask Request (AM1)18 ADDRMASKRPLY Address Mask Reply (AM2)

All gaps in the sequence above are filled with empty strings.

The complete table of DNS opcodes (according to IETF RFC 1612) looks like this (with AXE specific slogan added)

DNS Opcode AXE Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−0 QUERY A standard query (QUERY)1 INVERSEQUERY An inverse query (IQUERY)2 STATUSREQUEST A server status request (STATUS)3−15 Reserved for future use

The complete table of DNS response codes (according to IETF RFC 1612) looks like this (with AXE specific slogan added)

DNS ResponseCode AXE Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−0 NOERROR No error condition1 FORMATERROR Format Error2 SERVERFAILURE Server Failure3 NAMEERROR Name Error4 NOTIMPLEMENTED Not Implemented5 REFUSED Refused6−15 Reserved for future use.

The size of the variables:DID position Block Size1 VMIPSTS Up to 4 character long strings2 VMIPSTS Up to 3 character long strings3 VMIPSTS Up to 12 character long strings4 VMIPSTS Up to 16 character long strings5 VMIPSTS Up to 16 character long strings

5.249 LA2CNT

−VALID FOR APG

DID−name: LA2CNTDID−number: 853Function: Counters for location area statistics

DID item Contents



position1 Number of periodic location updatings over A and Iu−interface on intermediate MSC−blade after failed authentication with TMSI

Description:One record per location area in this blocks (referring tothis DID and DID: LACNT).The size of the LA file depends on the number oflocation areas in one MSC. In practice, it is conceivableto have 50 LAs handled by a MSC.The record pointer of the LA file is the same in allblocks (MPAG, MMMCS, MMMLR, MGPRO and MVLRP) and correspondswith the pointer in the MBSSD translation table (DID: LATAB).

The size of the variables:DID position Block Size1 MMMLR 32 bits

5.250 MIBIPLCGCNT

−VALID FOR APG

DID−name: MIBIPLCGCNTDID−number: 854Function: IETF RFC 4293 IP related counters.

DID item Contents position1 SysUpTime value for the most recent modification of the ipv4InterfaceTable structure, ipv4InterfaceReasmMaxSize or ipv4InterfaceEnableStatus object.2 SysUpTime value for the most recent addition or deletion of a row in the ipIfStatsTable.

Description:This system total DID contains a subset of the counters defined in IETFRFC 4293, "Management Information Base for the Internet Protocol (IP)", within the ipLastChangeGroup OBJECT−GROUP.

See RFC 4293 for more detailed documentation about the individual counters.


5.251 MIBIPV4ITCNT

−VALID FOR APG

DID−name: MIBIPV4ITCNTDID−number: 855Function: IETF RFC 4293 IPV4 counters.

DID item Contents position1 State2 Interface pointer3 Interface number4 Interface index that also relates to the IF−MIB’s ifIndex.5 The size of the largest IPv4 datagram that this entity can assemble on this interface.6 The indication whether IPv4 is enabled (up) or disabled



(down) on this interface.7 The time between retransmissions of ARP requests to a neighbor during address resolving or reachability probing.

Description:

This system total DID contains a subset of the counters defined in IETFRFC 4293, "Management Information Base for the Internet Protocol (IP)",within the ipv4InterfaceTable OBJECT−TYPE (one ipv4InterfaceEntry perinterface).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).DID item position 2 is a pointer, the pointer value can be translated toan interface name in position 1 of the MIBVMIPSTSTAB translation table(DID MIBVMIPSTSTAB).DID item position 3 is the interface number which is used when naming thecorresponding Objects/instances/individuals, see documentation for theMIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.DID item positions 5−7 are status counters.

The size of the variables.DID position Block Size1 VMIPSTS 1 bit2−7 VMIPSTS 32 bits

5.252 MIBIPSST2CNT

−VALID FOR APG

DID−name: MIBIPSST2CNTDID−number: 856Function: IETF RFC 4293 IP related counters per IP protocol version.

DID item Contents position 1 Number of IP datagrams transmitted. Low 32 bits. 2 Number of IP datagrams transmitted. High 32 bits. 3 Number of octets transmitted in IP datagram. Low 32 bits. 4 Number of octets transmitted in IP datagram. High 32 bits. 5 Number of IP multicast datagrams received. Low 32 bits. 6 Number of IP multicast datagrams received. High 32 bits. 7 Number of octets received in IP multicast datagrams. Low 32 bits. 8 Number of octets received in IP multicast datagrams. High 32 bits. 9 Number of IP multicast datagrams transmitted. Low 32 bits.10 Number of IP multicast datagrams transmitted. High 32 bits.11 Number of octets transmitted in IP multicast datagrams. Low 32 bits.12 Number of octets transmitted in IP multicast datagrams. High 32 bits.13 Number of IP broadcast datagrams received. Low 32 bits.14 Number of IP broadcast datagrams received. High 32 bits.15 Number of IP broadcast datagrams transmitted. Low 32 bits.16 Number of IP broadcast datagrams transmitted. High 32 bits.

Description:

This DID contains a subset of the counters defined in IETF RFC 4293,"Management Information Base for the Internet Protocol (IP)", within theipSystemStatsTable OBJECT−TYPE (one ipSystemStatsEntry per IP protocol



version).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is translated to IP protocol version name in position2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).

The size of the variables.DID position Block Size1−16 VMIPSTS 32 bits

5.253 MIBIPIFSTCNT

−VALID FOR APG

DID−name: MIBIPIFSTCNTDID−number: 857Function: IETF RFC 4293 IP related counters per IP protocol version.

DID item Contents position 1 State 2 Interface pointer 3 Interface number 4 IP protocol version 5 Interface index. Same as the IF−MIB’s ifIndex. 6 Number of input IP datagrams received, including those received in error. Low 32 bits. 7 Number of input IP datagrams received, including those received in error. High 32 bits. 8 Number of octets received in input IP datagrams, including those received in error. Low 32 bits. 9 Number of octets received in input IP datagrams, including those received in error. High 32 bits.10 Number of input IP datagrams discarded due to errors in their IP headers.11 Number of input IP datagrams discarded because of invalid address in the IP header’s destination field.12 Number of locally−addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol.13 Number of input IP datagrams discarded because the datagram frame didn’t carry enough data.14 Number of IP fragments received that needed to be reassembled.15 Number of IP datagrams successfully reassembled.16 The number of failures detected by the IP re−assembly algorithm.17 Number of input IP datagrams with no IP−related problems that still were discarded (e.g., for lack of buffer space).18 Number of datagrams successfully delivered to IP user− protocols. Low 32 bits.19 Number of datagrams successfully delivered to IP user− protocols. High 32 bits.20 Number of IP datagrams that local IP user−protocols supplied to IP in requests for transmission. Low 32 bits.21 Number of IP datagrams that local IP user−protocols supplied to IP in requests for transmission. High 32 bits.22 Number of output IP datagrams with no IP−related problems that still were discarded (e.g., for lack of buffer space). 23 Number of outgoing IP datagrams requiring fragmentation.24 Number of IP datagrams that have been successfully fragmented.25 Value of sysUpTime on the latest occasion at which any



counter suffered a discontinuity.Description:

This DID contains a subset of the counters defined in IETF RFC 4293,"Management Information Base for the Internet Protocol (IP)", within theipIfStatsTable OBJECT−TYPE (one IpIfStatsEntry per IP interface andprotocol version).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).DID item position 2 is a pointer, the pointer value can be translated toan interface name in position 1 of the MIBVMIPSTSTAB translation table(DID MIBVMIPSTSTAB).DID item position 3 is the interface number which is used when naming thecorresponding Objects/instances/individuals, see documentation for theMIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.DID item position 4 is translated to IP protocol version name in position2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).

The size of the variables:DID position Block Size1 VMIPSTS 1 bit2−3 VMIPSTS 32 bits4 VMIPSTS 8 bits5 VMIPSTS 16 bits6−25 VMIPSTS 32 bits

5.254 MIBIPIFST2CNT

−VALID FOR APG

DID−name: MIBIPIFST2CNTDID−number: 858Function: IETF RFC 4293 IP related counters per IP protocol version.

DID item Contents position 1 State 2 Number of IP datagrams discarded because they needed to be fragmented but could not be. 3 Number of output datagram fragments generated due to IP fragmentation. 4 Number of IP datagrams transmitted. Low 32 bits. 5 Number of IP datagrams transmitted. High 32 bits. 6 Number of octets transmitted in IP datagram. Low 32 bits. 7 Number of octets transmitted in IP datagram. High 32 bits. 8 Number of IP multicast datagrams received. Low 32 bits. 9 Number of IP multicast datagrams received. High 32 bits.10 Number of octets received in IP multicast datagrams. Low 32 bits.11 Number of octets received in IP multicast datagrams. High 32 bits.12 Number of IP multicast datagrams transmitted. Low 32 bits.13 Number of IP multicast datagrams transmitted. High 32 bits.14 Number of octets transmitted in IP multicast datagrams. Low 32 bits.15 Number of octets transmitted in IP multicast datagrams. High 32 bits.16 Number of IP broadcast datagrams received. Low 32 bits.17 Number of IP broadcast datagrams received. High 32 bits.18 Number of IP broadcast datagrams transmitted. Low 32 bits.19 Number of IP broadcast datagrams transmitted. High 32



bits.

Description:

This DID contains a subset of the counters defined in IETF RFC 4293,"Management Information Base for the Internet Protocol (IP)", within theipIfStatsTable OBJECT−TYPE (one IpIfStatsEntry per IP interface andprotocol version).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).


5.255 MIBIFTABLE2CNT

−VALID FOR APG

DID−name: MIBIFTABLE2CNTDID−number: 859Function: IETF RFC 2863 interface related counters.

DID item Contents position 1 State 2 A unique value, greater than zero, for each interface. 3 The type of interface. 4 The size of the largest packet which can be sent/received on the interface. 5 The interface’s address at its protocol sub−layer. Low 32 bits. 6 The interface’s address at its protocol sub−layer. High 32 bits. 7 The current operational state of the interface. 8 The value of sysUpTime when the interface entered its current operational state.

Description:

This DID contains a subset of the counters defined in IETF RFC 2863, "TheInterfaces Group MIB", ifTable OBJECT−TYPE (one ifEntry per interface).See RFC 2863 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).DID item positions 3−7 are status counters.

The size of the variables.DID position Block Size 1 VMIPSTS 1 bit 2−8 VMIPSTS 32 bits

5.256 MIBSCTPSTGCNT

−VALID FOR APG

DID−name: MIBSCTPSTGCNTDID−number: 860



Function: IETF RFC 3873 SCTP related counters.

DID item Contents position1 Number of associations for which the current state is either ESTABLISHED, SHUTDOWN−RECEIVED or SHUTDOWN−PENDING.2 Number of direct transitions from the COOKIE−ECHOED state to the ESTABLISHED state by associations initiated by the upper layer.3 Number of direct transitions from the CLOSED state to the ESTABLISHED state by associations initiated by the remote endpoint.4 Number of direct transitions from any state using the primitive ’ABORT’ to the CLOSED state (ungraceful termination).5 Number of direct transition from either the SHUTDOWN−SENT state or the SHUTDOWN−ACK−SENT state to the CLOSED state by associations (graceful termination).6 Number of out−of−the−blue packets, i.e., correctly formed SCTP packets with no appropriate association.7 Number of SCTP packets received with an invalid checksum.8 Number of SCTP control (non−data) chunks sent (retransmissions are not included). Low 32 bits.9 Number of SCTP control (non−data) chunks sent (retransmissions are not included). High 32 bits.10 Number of SCTP ordered data chunks sent (retransmissions are not included). Low 32 bits.11 Number of SCTP ordered data chunks sent (retransmissions are not included). High 32 bits.12 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included). Low 32 bits.13 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included). High 32 bits.14 Number of SCTP control (non−data) chunks received (no duplicate chunks included). Low 32 bits.15 Number of SCTP control (non−data) chunks received (no duplicate chunks included). High 32 bits.16 Number of SCTP ordered data chunks received (no duplicate chunks included). Low 32 bits.17 Number of SCTP ordered data chunks received (no duplicate chunks included). High 32 bits.18 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included). Low 32 bits.19 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included). High 32 bits.20 Number of user messages that have to be fragmented because of the MTU. Low 32 bits.21 Number of user messages that have to be fragmented because of the MTU. High 32 bits.22 Number of user messages reassembled, after conversion into DATA chunks. Low 32 bits.23 Number of user messages reassembled, after conversion into DATA chunks. High 32 bits.

Description:

This system total DID contains a subset of the counters defined in IETF RFC 3873, "Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)", sctpStatsGroup OBJECT−GROUP.




DID item position 1 is a status counter.


5.257 MIBSCTPST2CNT

−VALID FOR APG

DID−name: MIBSCTPST2CNTDID−number: 861Function: IETF RFC 3873 SCTP related counters.

DID item Contents position1 Number of SCTP packets sent. Retransmitted DATA chunks are included. Low 32 bits.2 Number of SCTP packets sent. Retransmitted DATA chunks are included. High 32 bits.3 Number of SCTP packets received. Duplicates are included. Low 32 bits.4 Number of SCTP packets received. Duplicates are included. High 32 bits.5 Value of sysUpTime on the latest occasion at which any counter above suffered a discontinuity.6 Number of times the T1 timer has expired.7 Number of times the T2 timer has expired.8 Number of DATA chunks in SCTP packets that has triggered the T3−rtx timer.9 Number of SCTP packet DATA chunks retransmissions to this specific IP address.

Description:




5.258 MIBSCTPLGCNT

−VALID FOR APG

DID−name: MIBSCTPLGCNTDID−number: 862Function: IETF RFC 3873 SCTP related counters.

DID item Contents position1 The algorithm used to determine the timeout value (T3−rtx) used for re−transmitting unacknowledged chunks.2 The minimum value for the retransmission timeout (milliseconds). Zero means immediate retransmission.3 The maximum value for the retransmission timeout (milliseconds). Zero means immediate retransmission.



4 The initial value for the retransmission timer. Zero means immediate retransmission.5 The upper limit on supported associations. "−1" means dynamic number of associations.6 Valid cookie life in the 4−way start−up handshake procedure (milliseconds).7 The maximum number of retransmissions at the start−up phase (INIT and COOKIE ECHO chunks).

Description:This system total DID contains a subset of the counters defined in IETF RFC 3873, "Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)", sctpLayerParamsGroup OBJECT−GROUP.


DID item positions 1−7 are status counters.


5.259 SUAQOSCNT

−VALID FOR APG

DID−name: SUAQOSCNTDID−number: 863Function: Counters for number of SUA messages processed, delivered successfully or not delievered ones per Signalling Process (ASP or SGP).

DID item Contents position1 State2 Number of CLDT messages sent. (SASCLDATA)3 Number of CLDT messages (RASCLDATA) received.4 Number of CLDR messages sent. (SASCLDATA)5 Number of CLDR messages (RASCLDATA) received.6 Number of CORE messages sent. (SASCODATA)7 Number of CORE messages (RASCODATA) received.8 Number of COREF messages sent. (SASCODATA)9 Number of COREF messages (RASCODATA)10 Number of ERROR messages sent. (SASCODATA)11 Number of ERROR messages (RASCODATA) received.

Description:The record pointer is used to enable translation to symbolic SPname using SUASPTAB translation table.DID position 1 indicates if the record is used (=1) for an SPor not (=0).One record per SP (1−1024)

The size of the variables:DID position Block Size1 SUADR 1 bit2−11 SUADR 32 bits



5.260 SUAASSTCNT

−VALID FOR APG

DID−name: SUAASSTCNTDID−number: 864Function: Counters for AS state changes (duration and number of occurences) when AS state is not in ACTIVE state but ACTIVE state is required.

DID item Contents position1 State2 Duration of non AS−ACTIVE state (TASINAC) (number of seconds).3 Number of occurences, (NASINAC) AS non ACTIVE

Description:The record pointer is used to enable translation to symbolic ASname using SUAASTAB translation table.DID position 1 indicates if the record is used (=1) for an ASor not (=0).One record per AS (1−16384)

The size of the variables:DID position Block Size1 SUADR 1 bit2 SUADR 32 bits3 SUADR 32 bits

5.261 SUAIBSTCNT

−VALID FOR APG

DID−name: SUAIBSTCNTDID−number: 865Function: Counters for IB state changes (duration and number of occurences) when IB state is in DOWN state but UP state is required.

DID item Contents position1 State2 Duration of IB−DOWN state (TIBDOWN) (number of seconds).3 Number of occurences, (NIBDOWN) IB−DOWN state

Description:The record pointer is used to enable translation to symbolicremote Blade name using SUAIBTAB translation table.DID position 1 indicates if the record is used (=1) for an IBor not (=0).One record per Blade (SP) (1−1024)




5.262 SUAASCONGCNT

−VALID FOR APG

DID−name: SUAASCONGCNTDID−number: 866Function: Counters for AS congestion state duration and number of occurences.

DID item Contents position1 State2 Duration of AS congestion state (TASCONG) (number of seconds).3 Number of occurences, (NASCONG) AS congestedDescription:The record pointer is used to enable translation to symbolic ASname using SUAASTAB translation table.DID position 1 indicates if the record is used (=1) for an ASor not (=0).One record per AS (1−16384)


5.263 SUAIBCONGCNT

−VALID FOR APG

DID−name: SUAIBCONGCNTDID−number: 867Function: Counters for IB congestion state duration and number of occurences.DID item Contents position1 State2 Duration of AS congestion state (TIBCONG) (number of seconds).3 Number of occurences, (NIBCONG) AS congested



5.264 SUAASDATACNT

−VALID FOR APG



DID−name: SUAASDATACNTDID−number: 868Function: Counters for number of SUA CL and CO DATA messages and DATA octets per AS

DID item Contents position1 State2 Number of CL DATA messages sent. (SASCLDATA)3 Number of CL DATA messages (RASCLDATA) received.4 Number of CO DATA messages sent. (SASCODATA)5 Number of CO DATA messages (RASCODATA) received.6 Number of DATA octets sent. (SASOCT)7 Number of DATA octets (RASOCT) received.



5.265 SUAIBDATACNT

−VALID FOR APG

DID−name: SUAIBDATACNTDID−number: 869Function: Counters for number of SUA CL and CO DATA messages and DATA octets per remote Blade at inter−Blade communication.

DID item Contents position1 State2 Number of CL DATA messages sent. (SIBCLDATA)3 Number of CL DATA messages (RIBCLDATA) received.4 Number of CO DATA messages sent. (SIBCODATA)5 Number of CO DATA messages (RIBCODATA) received.6 Number of DATA octets sent. (SIBOCT)7 Number of DATA octets (RIBOCT) received.





5.266 SUAASPTMCNT

−VALID FOR APG

DID−name: SUAASPTMCNTDID−number: 870Function: Counters for number of ASP TM messages per SP

DID item Contents position1 State2 Number of ASPInactive (SASPIA) messages sent.3 Number of ASPInactive (RASPIA) messages received.4 Number of ASPInactiveAck (SIAACK) messages sent.5 Number of ASPInactiveAck (RIAACK) messages received.6 Number of ASPActive (SASPAC) messages sent.7 Number of ASPActive (RASPAC) messages received.8 Number of ASPActiveAck (SACACK) messages sent.9 Number of ASPActiveAck (RACACK) messages received.



5.267 SUASSNMCNT

−VALID FOR APG

DID−name: SUASSNMCNTDID−number: 871Function: Counters for number of SSNM messages per SP

DID item Contents position1 State2 Number of DUNA (SDUNA) messages sent.3 Number of DUNA (RDUNA) messages received.4 Number of DAVA (SDAVA) messages sent.5 Number of DAVA (RDAVA) messages received.6 Number of SCON (SSCON) messages sent.7 Number of SCON (RSCON)



messages received.8 Number of DUPU (SDUPU) messages sent.9 Number of DUPU (RDUPU) messages received.10 Number of DAUD (SDAUD) messages sent.11 Number of DAUD (RDAUD) messages received.



5.268 SUAASPSMMCNT

−VALID FOR APG

DID−name: SUAASPSMMCNTDID−number: 872Function: Counters for number of ASP SM and Management (Error) messages sent and received per SP

DID item Contents position1 State2 Number of ASPUp (SASPUP) messages sent.3 Number of ASPUp (RASPUP) messages received.4 Number of ASPUpAck (SUPACK) messages sent.5 Number of ASPUpAck (RUPACK) messages received.6 Number of ASPDown (SASPDWN) messages sent.7 Number of ASPDown (RASPDWN) messages received.8 Number of ASPDownAck (SDWNACK) messages sent.9 Number of ASPDownAck (RDWNACK) messages received10 Number of ERROR (SERR) messages sent.11 Number of ERROR (RERR) messages received.


The size of the variables:DID position Block Size1 SUADR 1 bit



2−11 SUADR 32 bits

5.269 SUAPERFCNT

−VALID FOR APG

DID−name: SUAPERFCNTDID−number: 873Function: Performance counters for SUA.

DID item Contents position1 State2 Number of occurences, (RFSUADR) Routing failure, No translation for address of such nature.3 Number of occurences, (RFSPADR) Routing failure, No translation for this specific address.4 Number of occurences, (RFSSNFL) Routing failure, Subsystem failure.5 Number of occurences, (RFUNEQP) Routing failure, Unequipped user.6 Number of occurences, (RFNTWFL) Routing failure, Network failure.7 Number of occurences, (RFNTWCG) Routing failure, Network congestion.8 Number of occurences, (RFUNQAL) Routing failure, Reason unqualified.9 Number of occurences, (SYNTXER) Syntax Error in SUA message.



5.270 SUAIBPERFCNT

−VALID FOR APG

DID−name: SUAIBPERFCNTDID−number: 874Function: Performance counters for SUA Iner Blade communication.

DID item Contents position1 State2 Number of occurences, (RFIBSSNFL) Routing failure, Subsystem failure.3 Number of occurences, (RFIBUNEQP) Routing failure, Unequipped user.4 Number of occurences, (RFIBNTWFL) Routing failure, Network failure.5 Number of occurences, (RFIBNTWCG)



Routing failure, Network congestion.6 Number of occurences, (RFIBUNQAL) Routing failure, Reason unqualified.7 Number of occurences, (IBSYNTXER) Syntax Error in SUA message.

Description:The record pointer is used to enable translation to symbolic SPname using SUAIBTAB translation table.DID position 1 indicates if the record is used (=1) for an SPor not (=0).One record per SP (1−1024)


5.271 SUAUTILCNT

−VALID FOR APG

DID−name: SUAUTILCNTDID−number: 875Function: SUA utilization counter.

DID item Contents position1 State2 Number of messages requiring (MSGREQGT) Global Title translation.3 Total number of simultaneous (CSECUTIL) connection sections.

Description:The counters are presented as system total in common storedvariables.


5.272 SUAASTAB

−VALID FOR APG

DID−name: SUAASTABDID−number: 876Function: Translation table between AS pointer and AS identity.

DID item Contents position1 Symbolic name of AS.

Description:It translates AS pointer to symbolic AS name.

The size of the variables:DID position Block Size1 SUADR string 16 characters



5.273 SUAIBTAB

−VALID FOR APG

DID−name: SUAIBTABDID−number: 877Function: Translation table between SP pointer and remote Blade identity.

DID item Contents position1 Symbolic name of remote Blade.

Description:It translates SP pointer to symbolic remote Blade name.


5.274 SUASPTAB

−VALID FOR APG

DID−name: SUASPTABDID−number: 878Function: Translation table between SP pointer and SP identity.

DID item Contents position1 Symbolic name of SP.



6 References

(1) 1/1551 − ANZ 230 03/1, Object Types in STS.

6.1 LOCUPDA2CNT


DID−name: LOCUPDA2CNTDID−number: 777Function: Counters for location updating

DID item Contentsposition1 Number of normal location updating attempts for already registered subscribers



over A and Iu−interface2 Number of successful normal location updatings for already registered subscribers over A and Iu−interface3 Number of successful IMSI attached location updatings for already registered subscribers over A and Iu−interface4 Number of successful periodic location updatings over A and Iu−interface5 Number of successful IMSI attached location updatings for already registered subscribers over Gs interface6 Number of location updating attempts from non−registered subscribers (IMSI attach, normal location updating or periodic location updating) on intermediate MSC−blade after failed authentication with TMSI7 Number of location updating attempts for already registered subscribers on intermediate MSC−blade after failed authentication with TMSI8 Number of periodic location updating attempts for already registered subscribers on intermediate MSC−blade after failed authentication with TMSI9 Number of periodic location updating requests for non−registered on intermediate MSC−blade after failed authentication with TMSI10 Number of normal location updating attempts for already registered subscribers over A and Iu−interface on intermediate MSC−blade after failed authentication with TMSI

Description:All the variables are stored as common data.DID item positions 1−10 are peg counters.Counter specified in DID positions 1, 6−8, 10 are stored in blockMVLRP.Counters specified in DID positions 2−4, 9 are stored in blockMMMLR.Counter specified in DID position 5 is stored in block MGPRO.Blocks MMMLR, MGPRO and MVLRP belong to the subsystem MMS.

The size of the variables.DID position Block Size1 MVLRP 32 bits2−4 MMMLR 32 bits5 MGPRO 32 bits6−8 MVLRP 32 bits9 MMMLR 32 bits10 MVLRP 32 bits

6.2 NBRMSCL3CNT


DID−name: NBRMSCL3CNTDID−number: 798Function: Counters for inter−MSC handover on neighboring MSC level

DID item Contents Counter nameposition



1 Number of incoming hadnover rejections from NNREDREJ neighbouring MSC due to MSC Pool redistribution activities (incoming handovers include basic handovers and subequent handovers from neighbouring MSC)


The size of the variables:DID position Block Size1 MHIC 16 bits

6.3 SUBSVLRCNT


DID−name: SUBSVLRCNTDID−number: 799Function: Counters VLR subscribers.

DID item Contents Counter nameposition1 Number of registered VLR subscribers. TNSVLR2 Number of registered subscribers that are in TNSPEND status "Pending Redistribution".3 Number of registered subscribers in Location TNSEXTP Areas external to the pool not being Gs attached.4 Number of registered subscribers via the TNSATGS Gs interface.5 Number of registered subscribers with primary TNSPRSEXOUTD subscription including ones with incomplete data (subscribers known only with IMSI) and excluding the outdated ones.

Description:All the variables are stored as common data.The counters specified in DID positions 1−5 are stored inblock MTV.Block MTV belongs to the subsystem MDSThe size of the variables:DID item positions: 1−5 = 32 bits

The size of the variables:DID position Block Size1 MTV 32 bits2 MTV 32 bits3 MTV 32 bits4 MTV 32 bits5 MTV 32 bits

6.4 INTTRAFCNT

−VALID FOR APG



DID−name: INTTRAFCNTDID−number: 805Function: Counters for Internal Traffic in MSC−S BC environment

DID item ContentsPosition

1 State2 Number of calls to destination Blade (CALLDBLD)3 Number of B−Answers received from destination (BANSWDBLD) Blade4 Number of unsuccessful calls to destination (UNSUCCFULDBLD) blade5 Number of seizure attempts for mobile (MTERMCNT) terminating traffic to destination Blade6 Traffic Level per blade (TRALBLD)7 Number of seizure attempts per blade (NCALLSBLD)

Description:One set of counters is defined for each ’destination blade’.DID item 1 is a state value indicating if the respective blade is available at all or not (0 = not available).DID items 2 − 7 are stored in a ’blade counter’ file in the block INTRO. This file has the fixed size 64.The following sizes of the variables are used:DID Position Block Size 1 INTRO 1 Bit 2 INTRO 32 Bit 3 INTRO 32 Bit 4 INTRO 32 Bit 5 INTRO 32 Bit 6 INTRO 32 Bit 7 INTRO 32 Bit

6.5 VOIPROUTCNT

−VALID FOR APG

DID−name: VOIPROUTCNTDID−number: 806Function: Route counters for VoIP routes.

DID item Contents position1 Global Route Number (GLRTENO)2 VoIP route type3 Number of occupied4 Number of calls5 Number of calls with congestion6 Number of B−answers7 Number of outgoing seizures8 Number of congestions due to route software individuals not available9 Number of ATP received on ISUP routes10 Number of Congestions due no transmission resource available in BEACC11 Number of successful end of selections12 Number of congestions on the last available route13 Number of (traffic) individuals in service

Description:Counters for the bothway Voice over IP (VoIP) routes.DID item position one is global route pointer which needs to be translated



to symbolic route name, using the existing translation table DIDROUTETRANTAB, DID number 46.

A VoIP route consists of two individuals (route records): one for incomingtraffic (even internal route number) and one for outgoing traffic (oddinternal route number). The incoming route record, in a pair of routes, islocated before the outgoing route in the file.For the VoIP route both the individuals are defined. The internal routenumber is identical with the record number (that is record pointer orindividual).Individual number 0 and 1 are not in use.Individual number 2 and 3 are reserved for test route.The VoIP route type (item 2) indicates the type of the route:3 = bothway traffic route7 = main routeAll other values (that is <>3 and <> 7) will be interpreted as undefinedroutes (that is measurement will not take place).DID item positions 1 − 13 are stored in the route file in block SIPCO.The size alteration event 504 is used to alter the file size.The maximum number of records in the file is 65534.

The size of the variables:DID position Block Size1 SIPCO 16 bits2 SIPCO 16 bits3−13 SIPCO 32 bits

6.6 SIPROUTCNT

−VALID FOR APG

DID−name: SIPROUTCNTDID−number: 807Function: Route counters for SIP or SIP with encapsulatedISUP protocols.

DID item Contents Counter nameposition1 Global Route Number GLRTENO2 Route type3 SIP protocol type SIP or SIP−I4 Number of initial INVITE requests SIPSES5 Number of successfully created initial INVITE requests SUCSES6 Number of cancelled initial INVITE requests TRMINV7 Number of rejected initial INVITE requests due to server INTERR internal error 8 Number of rejected initial INVITE requests due to URI416 unsupported URI scheme in Request−URI 9 Number of rejected initial INVITE requests due to user INV480 unavailability 10 Number of rejected initial INVITE requests due to addressINV484 incomplete 11 Number of rejected initial INVITE requests due to busy BUSYBN user 12 Number of initial INVITE requests rejected with 3xx final NV3XX response 13 Number of initial INVITE requests rejected with 4xx final INV4XX response 14 Number of initial INVITE requests rejected with 5xx final INV5XX response 15 Number of initial INVITE requests rejected with 6xx final INV6XX response 16 Number of rejected requests due to unacceptable SDP offer ERRSDP



17 Number of rejected initial INVITE requests due to ERISUP incorrect encapsulated ISUP information 18 Number of sent initial INVITE requests without received INVNOFR final response

Description:Counters for the SIP and SIP with encapsulated ISUP protocols.DID item position one is global route pointer which needs to be translatedto symbolic route name, using the existing translation table DIDROUTETRANTAB, DID number 46.A SIP route consists of two individuals (route records): one for incomingtraffic (even internal route number) and one for outgoing traffic (oddinternal route number). The incoming route record, in a pair of routes, islocated before the outgoing route in the file.For the SIP route both the individuals are defined. The internal routenumber is identical with the record number (that is record pointer orindividual).Individual number 0 and 1 are not in use.Individual number 2 and 3 are reserved for test route.The route type (item 2) indicates the type of the route:3 = bothway traffic routeAll other values (that is <3 and >3) will be interpreted as undefinedroutes (that is measurement will not take place).The SIP protocol type (item 3) indicates the type of protocol used on theSIP route:1 = SIP2 = SIP with encapsulated ISUPAll other values (that is 0 and >2) will be interpreted as undefinedroutes (that is measurement will not take place).DID item positions 1 − 18 are stored in the route file in block SIPD.The size alteration event 504 is used to alter the file size.The maximum number of records in the file is 65534.

Size of the variables.DID Position Block Size of variable1 SIPHIT, SIPHOT 16 bits2 SIPHIT, SIPHOT 16 bits3 SIPHIT, SIPHOT 16 bits4−6 SIPHIT, SIPHOT 32 bits7−8 SIPHIT 32 bits9−11 SIPHIT, SIPHOT 32 bits12 SIPHIT, SIPHOT 32 bits13−18 SIPHIT, SIPHOT 32 bits

6.7 SIPCODECCNT

−VALID FOR APG

DID−name: SIPCODECCNTDID−number: 809Function: Counters for SIP/SIP−I codec negotiation on per route.

DID item Contents position1 The global route number (GLRTENO) 2 Route type3 SIP protocol type (SIP or SIP−I)4 Number of calls where 3GPP Narrow Band Compressed payload type is applied on SIP/SIP−I route5 Number of calls where PCM payload type is applied on SIP/SIP−I route 6 Number of calls where G729 payload type is applied on SIP/SIP−I route7 Number of incoming/outgoing calls where Clear Channel



(CLEARMODE codec) is applied on SIP/SIP−I route Description:DID item position one is global route pointer which needs to be translatedto symbolic route name, using the existing translation table DIDROUTETRANTAB, DID number 46.A SIP or SIP−I route consists of two individuals (route records): one forincoming traffic (even internal route number) and one for outgoing traffic(odd internal route number). The incoming route record, in a pair ofroutes, is located before the outgoing route in the file.For the SIP or SIP−I route, both the individuals are defined. The internalroute number is identical with the record number (that is record pointeror individual).Individual number 0 and 1 are not in use.Individual number 2 and 3 are reserved for test route.The route type (item 2) indicates the type of the route:3 = bothway traffic routeAll other values (that is <3 and >3) will be interpreted as undefinedroutes (that is measurement will not take place).The SIP protocol type (item 3) indicates the type of protocol used on theSIP route:1 = SIP2 = SIP with encapsulated ISUPAll other values (that is 0 and >2) will be interpreted as undefinedroutes (that is measurement will not take place).DID item positions 1 − 7 are stored in the route file in block SIPBC.The size alteration event 504 is used to alter the file size.The maximum number of records in the file is 65534.

Size of the variablesDID position Block Size1 − 3 SIPBC 16 bits4 − 5 SIPBC 32 bits6 − 7 SIPBC 32 bits

6.8 MGNAMETAB

−VALID FOR APG

DID−name: MGNAMETABDID−number: 811Function: MGW Translation Table

DID item Contents position1 MGW Name Description:This DID translates from the position in the file to the MGW Name. According to command NRGWI up to 7 characters can be used for a MGW Name.One record per MGW exists in block NRM.The maximum number of records is 65535.To alter the file size the size alteration event number 1134 is to be used.

DID position Block Size1 NRM string 7 characters

6.9 SIPNODECNT

−VALID FOR APG



DID−name: SIPNODECNTDID−number: 814Function: Node counters for SIP protocol

DID item Contents position1 Number of session establishment request failures due to invalid address 2 Number of received INVITE requests 3 Number of session establishment request failures due to server capability mismatches 4 Number of unsuccessful INVITE attempts received 5 Number of active SIP transactions 6 Number of faulty received SIP messages with syntax or size errors 7 Number of received SIP request messages 8 Number of sent SIP request messages 9 Number of received SIP response messages 10 Number of sent SIP response messages 11 Number of unresolved addresses due to failed DNS lookup attempts 12 Number of DNS queries for SIP 13 Number of DNS queries that have resulted in time−out 14 Number of sent SIP requests without final response 15 Number of TCP connections used by SIP

Description:Node counters for SIP protocol.DID item positions 1 − 15 are stored in the record (file) in block TPC.File is not size alterable.

The size of the variables:DID position Block Size1−15 TPC 32 bit

6.10 RNCCODERSTATCNT


DID−name: RNCCODERSTATCNTDID−number: 819Function: Counters for speech coder in RAB assignment per RNC.

DID item Contents Counter nameposition1 Number of RAB assignments NRFRMAMR from mobile subscriber with UMTSAMR as codec type2 Number of RAB assignments NRFRM2AMR from mobile subscriber with UMTSAMR2 as codec type3 Number of RAB assignments from NRFRMWBAMR mobile subscriber with UMTSAMR−WB as codec type 4 Number of RAB assignments NRTOAMR to mobile subscriber with UMTSAMR as codec type5 Number of RAB assignments NRTO2AMR to mobile subscriber with UMTSAMR2 as codec type6 Number of RAB assignments NRTOWBAMR to mobile subscriber with UMTSAMR−WB as codec type

Description:



All the variables are stored in record related data.The translation table RNCTAB will be used to translate from the internalrecord number to the symbolic RNC name.The counters are stepped per RNC.The counters specified in DID positions 1−6 are stored in block MURABP.Block MURABP belong to subsystem MMS.The size of the variables:DID item positions: 1−6 = 32 bits

The size of the variables:DID position Block Size1−6 MURABP 32 bits

6.11 MIBIPV4GCNT

−VALID FOR APG

DID−name: MIBIPV4GCNTDID−number: 837Function: IETF RFC 4293 IPv4 counters.

DID item Contents position1 Indicates if this entity acts as an IPv4 router or not (IPv4 routers forwards datagrams, IPv4 hosts do not).2 Default value for IPv4 TTL header field.3 Maximum number of seconds received fragments are held while awaiting reassembly.Description:This system total DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the ipv4GeneralGroup OBJECT−GROUP.See RFC 4293 for more detailed documentation about the individual counters.DID item positions 1−3 are status counters.


6.12 MIBIPSSTCNT

−VALID FOR APG

DID−name: MIBIPSSTCNTDID−number: 838Function: IETF RFC 4293 IP related counters per IP protocolversion.

DID item Contents position1 IP protocol version2 Total number of received IP datagrams.3 Number of discarded IP datagrams due to IP header errors.4 Number of discarded IP datagrams due to unknown or unsupported protocol.5 Number of received IP fragments needing reassembly.6 Number of successfully reassembled IP datagrams.7 Number of failures detected during reassembly.



8 Number of discarded IP datagrams due to lack of resources.9 Number of successfully delivered IP datagrams.10 Total number of non−forward IP datagram delivery requests.11 Number of discarded IP datagrams due to no route to destination.12 Number of discarded IP datagrams due to lack of resources.13 Number of successfully fragmented IP datagrams.14 Number of discarded IP datagrams due to that they could not be fragmented.15 Number of fragmented IP datagrams.16 Total number of received IP datagrams. High 32 bits.17 Number of octets received in input IP datagrams, including those received in error. Low 32 bits.18 Number of octets received in input IP datagrams, including those received in error. High 32 bits.19 Number of input IP datagrams discarded because of invalid address in the IP header’s destination field.20 Number of input IP datagrams discarded because the datagram frame didn’t carry enough data.21 Number of successfully delivered IP datagrams. High 32 bits.22 Total number of non−forward IP datagram delivery requests. High 32 bits.23 Number of outgoing IP datagrams requiring fragmentation.24 Value of sysUpTime on the latest occasion at which any counter suffered a discontinuity.Description:This DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the ipSystemStatsTable OBJECT−TYPE (one ipSystemStatsEntry per IP protocol version).See RFC 4293 for more detailed documentation about the individual counters.DID item position 1 is translated to IP protocol version name in position 2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).The size of the variables:DID position Block Size1 VMIPSTS 8 bits2−24 VMIPSTS 32 bits

6.13 MIBICMPSTCNT

−VALID FOR APG

DID−name: MIBICMPSTCNTDID−number: 839Function: IETF RFC 4293 ICMP related counters per IP protocolversion.

DID item Contents position1 IP protocol version.2 Total number of received ICMP messages.3 Number of received faulty ICMP messages.4 Total number of sent ICMP messages.5 Number of not sent ICMP messages due to problems in ICMP.Description:This DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the icmpStatsTable OBJECT−TYPE (one icmpStatsEntry per IP protocol version).See RFC 4293 for more detailed documentation about the individual counters.DID item position 1 is translated to IP protocol version name in position 2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).The size of the variables:DID position Block Size



1 VMIPSTS 8 bits2−5 VMIPSTS 32 bits

6.14 MIBICMPMSGSTCNT

−VALID FOR APG

DID−name: MIBICMPMSGSTCNTDID−number: 840Function: IETF RFC 4293 ICMP related counters per IP protocolversion.

DID item Contents position1 State2 IP protocol version.3 ICMP type field.4 Number of input packets for this address family and type.5 Number of output packets for this address family and type.Description:This DID contains a subset of the counters defined in IETF RFC 4293, "Management Information Base for the Internet Protocol (IP)", within the icmpMsgStatsTable OBJECT−TYPE (one icmpStatsEntry per IP protocol version and ICMP type value).See RFC 4293 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).The symbolic name for each valid object (or individual) is created from concatenating two strings and separating them with a ’−’ (hyphen) character. The first string is obtained by translating DID item position 2 to IP protocol version name in position 2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB). The second string is obtained by translating DID item position 3 to ICMP type field name in position 3 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).For instance if DID item position 2 contains the value ’1’ (one) and DID item position 3 contains the value ’3’, then this would result in the strings "and "DESTUNREACH" being translated (IETF RFC 4001, section 3 (page 6), maps the value ’1’ (one) to IPv4, and IETF RFC 792 maps the value ’3’ to "Destination Unreachable").These two strings, "V4" and "DESTUNREACH", are concatenated and separated using a ’−’ (hyphen), in order to form the string "V4−DESTUNREACH".The size of the variables:DID position Block Size1 VMIPSTS 1 bit2 VMIPSTS 8 bits3−5 VMIPSTS 32 bits

6.15 MIBTCPBASECNT

−VALID FOR APG

DID−name: MIBTCPBASECNTDID−number: 841Function: IETF RFC 4022 TCP related counters.

DID item Contents position1 Algorithm used to determine timeout value used for retransmitting unacknowledged octets.2 Minimum retransmission timeout value, measured in milliseconds.3 Maximum retransmission timeout value, measured in milliseconds.



4 Limit on total number of simultanous TCP connections supported.5 Number of direct transitions to SYN−SENT state from CLOSED state.6 Number of direct transitions to SYN−RCVD state from LISTEN state.7 Sum of direct transitions to CLOSED state from either SYN− SENT or SYN−RCVD states and direct transitions to LISTEN state from SYN−RCVD state.8 Number of direct transitions to CLOSED state from either ESTABLISHED or CLOSE−WAIT states.9 Number of connections where state is ESTABLISHED or CLOSE−WAIT.10 Total number of received segments.11 Total number of sent segments (excluding those containing only retransmitted octets).12 Total number of retransmitted segments.13 Total number of faulty segments received.14 Number of segments containing RST flag.15 Total number of received segments. High 32 bits.16 Total number of sent segments (excluding those containing only retransmitted octets). High 32 bits.Description:This system total DID contains a subset of the counters defined in IETF RFC 4022, "Management Information Base for the Transmission Control Protocol (TCP)", tcpBaseGroup OBJECT−GROUP.See RFC 4022 for more detailed documentation about the individual counters.DID item positions 1−4 and 9 are status counters.The size of the variables:DID position Block Size1−16 VMIPSTS 32 bits

6.16 MIBUDPBASECNT

−VALID FOR APG

DID−name: MIBUDPBASECNTDID−number: 842Function: IETF RFC 4113 UDP related counters.

DID item Contents position1 Total number of delivered datagrams to UDP users.2 Total number of received datagrams with no application at destination port.3 Number of undelivered datagrams due to other reasons than no application at destination port.4 Total number of sent datagrams.Description:This system total DID contains the counters defined in IETF RFC 4113, "Management Information Base for the User Datagram Protocol (UDP)", udpBaseGroup OBJECT−GROUP.See RFC 4113 for more detailed documentation about the individual counters.The size of the variables:DID position Block Size1−4 VMIPSTS 32 bits

6.17 MIBIFTABLECNT

−VALID FOR APG

DID−name: MIBIFTABLECNTDID−number: 843



Function: IETF RFC 2863 interface related counters.

DID item Contents position1 State2 Interface pointer3 Interface number4 Total number of received octets on the interface, including framing characters.5 Number of wraparounds for total number of received octets on the interface, including framing characters.6 Number of packets delivered to a unicast address.7 Number of wraparounds for packets delivered to a unicast address.8 Number of packets discarded before delivery.9 Number of wraparounds for packets discarded before delivery.10 Number of faulty packets preventing them to be delivered to a higher−layer protocol. 11 Number of wraparounds for faulty packets preventing them to be delivered to a higher−layer protocol.12 Number of discarded packets due to unknown or unsupported protocol.13 Number of wraparounds for discarded packets due to unknown or unsupported protocol.14 Total number of sent octets on the interface, including framing characters.15 Number of wraparounds for total number of sent octets on the interface, including framing characters.16 Number of sent packets to a unicast address.17 Number of wraparounds for sent packets to a unicast address.18 Number of packets discarded before being sent.19 Number of wraparounds for packets discarded before being sent.20 Number of packets that could not be transmitted due to errors.21 Number of wraparounds for packets that could not be transmitted due to errors.Description:This DID contains a subset of the counters defined in IETF RFC 2863, "The Interfaces Group MIB", ifTable OBJECT−TYPE (one ifEntry per interface). It also contains a number of non−standard counters that tracks the number of wraparounds that has occurred for the respective counters.See RFC 2863 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).DID item position 2 is a pointer, the pointer value can be translated to an interface name in position 1 of the MIBVMIPSTSTAB translation table (DID MIBVM IDID item position 3 is the interface number which is used when naming the corresponding Objects/instances/individuals, see documentation for the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.The size of the variables:DID position Block Size1 VMIPSTS 1 bit2−21 VMIPSTS 32 bits

6.18 MIBIFXTABLECNT

−VALID FOR APG

DID−name: MIBIFXTABLECNTDID−number: 844Function: IETF RFC 2863 interface related counters.



DID item Contents position1 State2 Interface pointer3 Interface number4 Number of packets delivered to a multicast address.5 Number of wraparounds for packets delivered to a multicast address.6 Number of packets delivered to a broadcast address.7 Number of wraparounds for packets delivered to a broadcast address.8 Number of sent packets to a multicast address.9 Number of wraparounds for sent packets to a multicast address.10 Number of sent packets to a broadcast address.11 Number of wraparounds for sent packets to a broadcast address.12 Value of sysUpTime on the latest occasion at which any counter suffered a discontinuity.

Description:This DID contains a subset of the counters defined in IETF RFC 2863, "The Interfaces Group MIB", ifXTable OBJECT−TYPE (one ifXEntry per interface). It also contains a number of non−standard counters that tracks the number of wraparounds that has occurred for the respective counters.See RFC 2863 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).DID item position 2 is a pointer, the pointer value can be translated to an interface name in position 1 of the MIBVMIPSTSTAB translation table (DID MIBVM IDID item position 3 is the interface number which is used when naming the corresponding Objects/instances/individuals, see documentation for the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.


6.19 MIBDNSRCONFIGCNT

−VALID FOR APG

DID−name: MIBDNSRCONFIGCNTDID−number: 845Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 Kind of DNS resolution service provided

Description:This system total DID contains a subset of the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResConfigGroup OBJECT−GROUP.See RFC 1612 for more detailed documentation about the individual counters.DID item position 1 is a status counter.The size of the variables:DID position Block Size1 VMIPSTS 32 bits

6.20 MIBDNSRCCNT

−VALID FOR APG



DID−name: MIBDNSRCCNTDID−number: 846Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 Number of resolver requests with non−authoritative (cached) answer.2 Number of resolver requests with non−authoritative (cached) ’no such data’ answer (empty answer).3 Number of responses from servers the resolver does not think it asked.4 Number of responses received to all queries.5 Number of times the resolver had to fall back to its seat belt information.

Description:This system total DID contains a subset of the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResCounterGrup OBJECT−GROUP.See RFC 1612 for more detailed documentation about the individual counters.The size of the variables:DID position Block Size1−5 VMIPSTS 32 bits

6.21 MIBDRCBOCNT

−VALID FOR APG

DID−name: MIBDRCBOCNTDID−number: 847Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 State2 Index to opcode table found in RFC−1035 section 4.1.1.3 Total number of queries sent by the resolver for this opcode.4 Total number of responses received by the resolver for this opcode.

Description:This DID contains the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResCounterByOpcodeTable OBJECT−TYPE (one dnsResCounterByOpcodeEntry per opcode).See RFC 1612 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).DID item position 2 is translated to an opcode name in position 4 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).The size of the variables:DID position Block Size1 VMIPSTS 1 bit2 VMIPSTS 8 bits3−4 VMIPSTS 32 bits

6.22 MIBDRCBRCNT

−VALID FOR APG

DID−name: MIBDRCBRCNTDID−number: 848



Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 State2 Index to response code table found in RFC−1035 section 4.1.1.3 Number of responses received by the resolver for this response code.Description:This DID contains the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResCounterByRcodeTable OBJECT−TYPE (one dnsResCounterByRcodeEntry per response ccode).See RFC 1612 for more detailed documentation about the individual counters.DID item position 1 is a state value indicating if the individual is used or n o(0 = not used).DID item position 2 is translated to a response code name in position 5 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).The size of the variables:DID position Block Size1 VMIPSTS 1 bit2 VMIPSTS 8 bits3 VMIPSTS 32 bits

6.23 MIBDNSRCCACHECNT

−VALID FOR APG

DID−name: MIBDNSRCCACHECNTDID−number: 849Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 Status for the resolvers cache.2 Number of RRs the resolver has cached successfully.3 Number of RRs the resolver has refused to cache.Description:This is a system total DID contains a subset of the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResCacheGroup OBJECT−GROUP.See RFC 1612 for more detailed documentation about the individual counters.DID item position 1 is a status counter.The size of the variables:DID position Block Size1 VMIPSTS 8 bits2−3 VMIPSTS 32 bits

6.24 MIBDNSRNCACNT

−VALID FOR APG

DID−name: MIBDNSRNCACNTDID−number: 850Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 Number of authoritative errors the resolver has cached successfully.Description:This is a system total DID contains a subset of the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResNCacheGroup OBJECT−GROUP.See RFC 1612 for more detailed documentation about the individual counters.



The size of the variables:DID position Block Size1 VMIPSTS 32 bits

6.25 MIBDNSROCACNT

−VALID FOR APG

DID−name: MIBDNSROCACNTDID−number: 851Function: IETF RFC 1612 DNS related counters.

DID item Contents position1 Number of retransmitted requests for all reasons.2 Number of retransmitted requests due to no response.3 Number of resolver generated requests.4 Number of resolver generated requests that timed out.Description:This is a system total DID contains the counters defined in IETF RFC 1612, "DNS Resolver MIB Extensions", dnsResOptCounterGroup OBJECT−GROUP.See RFC 1612 for more detailed documentation about the individual counters.The size of the variables:DID position Block Size1−4 VMIPSTS 32 bits

6.26 MIBVMIPSTSTAB

−VALID FOR APG

DID−name: MIBVMIPSTSTABDID−number: 852Function: Translation Table for IETF RFC 2863 and 4293 relatedcounters.

DID item Contents position1 IETF RFC 2863 symbolic interface names2 IETF RFC 4293 symbolic IP version names3 IETF RFC 792 and IETF RFC 950 symbolic ICMP type names4 IETF RFC 1612 opcode name5 IETF RFC 1612 response code name

Description:Position 1 is used when translating from symbolic interface number tosymbolic interface name. This Translation Table DID position contains aprefix for the interface name (e.g. "ETHA" or "ETHB") which should beconcatenated with ’−’ (hyphen or minus) and followed with the "Interfacenumber" stored in position 3 of the corresponding DID (e.g. forming aninterface name looking like "ETHA−22"). The interface pointer is used forlooking up the prefix name in the Translation Table DID. This correspondsto the string in the object ifName in RFC 2863 "IF−MIB". However, stringsare only included in this Translation DID.Position 2 translates from symbolic IP version number to symbolic IPversion name, where the symbolic IP version number is identical to the IPprotocol version ID counter.If both position 1 and 2 are used, the result of the translation fromposition 2 is concatenated with ’−’ (hyphen or minus) and followed withthe translation as described in the first paragraph above.Position 3 translates from symbolic ICMP type code to symbolic ICMP typename, where the symbolic ICMP type code is identical to the ICMP typecode ID counter.Position 4 translates from opcode number to symbolic opcode name, where



the opcode number is identical to the opcode.Position 5 translates from response code number to symbolic response codename, where the response code number is identical to the response code.

The complete table of symbolic interface names looks like this

InterfaceNumber Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−1 ETHA Ethernet interface for physical A−plane in CP2 ETHB Ethernet interface for physical B−plane in CP

The complete table of IP version names (according to IETF RFC 4293) looks Like this (with AXE specific slogan added)

IP VersionNumber Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−1 V4 IPv42 V6 IPv6

The complete table of ICMP type codes (IETF RFC 792 and IETF RFC 950 combined, IETF RFC 950 adds two ICMP type codes for "Address Mask Request" and "Address Mask Reply") looks like this (with AXE specific slogan added)

ICMP TypeCode AXE Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−0 ECHOREPLY Echo Reply3 DESTUNREACH Destination Unreachable4 SOURCEQUENCH Source Quench5 REDIRECT Redirect8 ECHO Echo11 TIMEEXCEEDED Time Exceeded12 PARAMPROBLEM Parameter Problem13 TMESTAMP Timestamp14 TMESTAMPRPLY Timestamp Reply15 INFOREQUEST Information Request16 INFOREPLY Information Reply17 ADDRMASKREQ Address Mask Request (AM1)18 ADDRMASKRPLY Address Mask Reply (AM2)

All gaps in the sequence above are filled with empty strings.

The complete table of DNS opcodes (according to IETF RFC 1612) looks like this (with AXE specific slogan added)

DNS Opcode AXE Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−0 QUERY A standard query (QUERY)1 INVERSEQUERY An inverse query (IQUERY)2 STATUSREQUEST A server status request (STATUS)3−15 Reserved for future use

The complete table of DNS response codes (according to IETF RFC 1612) looks like this (with AXE specific slogan added)

DNS ResponseCode AXE Slogan Description−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−−0 NOERROR No error condition1 FORMATERROR Format Error2 SERVERFAILURE Server Failure3 NAMEERROR Name Error4 NOTIMPLEMENTED Not Implemented5 REFUSED Refused



6−15 Reserved for future use.

The size of the variables:DID position Block Size1 VMIPSTS Up to 4 character long strings2 VMIPSTS Up to 3 character long strings3 VMIPSTS Up to 12 character long strings4 VMIPSTS Up to 16 character long strings5 VMIPSTS Up to 16 character long strings

6.27 LA2CNT

−VALID FOR APG

DID−name: LA2CNTDID−number: 853Function: Counters for location area statistics

DID item Contents position1 Number of periodic location updatings over A and Iu−interface on intermediate MSC−blade after failed authentication with TMSI

Description:One record per location area in this blocks (referring tothis DID and DID: LACNT).The size of the LA file depends on the number oflocation areas in one MSC. In practice, it is conceivableto have 50 LAs handled by a MSC.The record pointer of the LA file is the same in allblocks (MPAG, MMMCS, MMMLR, MGPRO and MVLRP) and correspondswith the pointer in the MBSSD translation table (DID: LATAB).

The size of the variables:DID position Block Size1 MMMLR 32 bits

6.28 MIBIPLCGCNT

−VALID FOR APG

DID−name: MIBIPLCGCNTDID−number: 854Function: IETF RFC 4293 IP related counters.

DID item Contents position1 SysUpTime value for the most recent modification of the ipv4InterfaceTable structure, ipv4InterfaceReasmMaxSize or ipv4InterfaceEnableStatus object.2 SysUpTime value for the most recent addition or deletion of a row in the ipIfStatsTable.

Description:This system total DID contains a subset of the counters defined in IETFRFC 4293, "Management Information Base for the Internet Protocol (IP)", within the ipLastChangeGroup OBJECT−GROUP.


The size of the variables:DID position Block Size



1−2 VMIPSTS 32 bits

6.29 MIBIPV4ITCNT

−VALID FOR APG

DID−name: MIBIPV4ITCNTDID−number: 855Function: IETF RFC 4293 IPV4 counters.

DID item Contents position1 State2 Interface pointer3 Interface number4 Interface index that also relates to the IF−MIB’s ifIndex.5 The size of the largest IPv4 datagram that this entity can assemble on this interface.6 The indication whether IPv4 is enabled (up) or disabled (down) on this interface.7 The time between retransmissions of ARP requests to a neighbor during address resolving or reachability probing.

Description:

This system total DID contains a subset of the counters defined in IETFRFC 4293, "Management Information Base for the Internet Protocol (IP)",within the ipv4InterfaceTable OBJECT−TYPE (one ipv4InterfaceEntry perinterface).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).DID item position 2 is a pointer, the pointer value can be translated toan interface name in position 1 of the MIBVMIPSTSTAB translation table(DID MIBVMIPSTSTAB).DID item position 3 is the interface number which is used when naming thecorresponding Objects/instances/individuals, see documentation for theMIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.DID item positions 5−7 are status counters.

The size of the variables.DID position Block Size1 VMIPSTS 1 bit2−7 VMIPSTS 32 bits

6.30 MIBIPSST2CNT

−VALID FOR APG

DID−name: MIBIPSST2CNTDID−number: 856Function: IETF RFC 4293 IP related counters per IP protocol version.

DID item Contents position 1 Number of IP datagrams transmitted. Low 32 bits. 2 Number of IP datagrams transmitted. High 32 bits. 3 Number of octets transmitted in IP datagram. Low 32 bits. 4 Number of octets transmitted in IP datagram. High 32 bits. 5 Number of IP multicast datagrams received. Low 32 bits. 6 Number of IP multicast datagrams received. High 32 bits. 7 Number of octets received in IP multicast datagrams. Low



32 bits. 8 Number of octets received in IP multicast datagrams. High 32 bits. 9 Number of IP multicast datagrams transmitted. Low 32 bits.10 Number of IP multicast datagrams transmitted. High 32 bits.11 Number of octets transmitted in IP multicast datagrams. Low 32 bits.12 Number of octets transmitted in IP multicast datagrams. High 32 bits.13 Number of IP broadcast datagrams received. Low 32 bits.14 Number of IP broadcast datagrams received. High 32 bits.15 Number of IP broadcast datagrams transmitted. Low 32 bits.16 Number of IP broadcast datagrams transmitted. High 32 bits.

Description:

This DID contains a subset of the counters defined in IETF RFC 4293,"Management Information Base for the Internet Protocol (IP)", within theipSystemStatsTable OBJECT−TYPE (one ipSystemStatsEntry per IP protocolversion).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is translated to IP protocol version name in position2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).


6.31 MIBIPIFSTCNT

−VALID FOR APG

DID−name: MIBIPIFSTCNTDID−number: 857Function: IETF RFC 4293 IP related counters per IP protocol version.

DID item Contents position 1 State 2 Interface pointer 3 Interface number 4 IP protocol version 5 Interface index. Same as the IF−MIB’s ifIndex. 6 Number of input IP datagrams received, including those received in error. Low 32 bits. 7 Number of input IP datagrams received, including those received in error. High 32 bits. 8 Number of octets received in input IP datagrams, including those received in error. Low 32 bits. 9 Number of octets received in input IP datagrams, including those received in error. High 32 bits.10 Number of input IP datagrams discarded due to errors in their IP headers.11 Number of input IP datagrams discarded because of invalid address in the IP header’s destination field.12 Number of locally−addressed IP datagrams received successfully but discarded because of an unknown or unsupported protocol.13 Number of input IP datagrams discarded because the datagram frame didn’t carry enough data.14 Number of IP fragments received that needed to be reassembled.



15 Number of IP datagrams successfully reassembled.16 The number of failures detected by the IP re−assembly algorithm.17 Number of input IP datagrams with no IP−related problems that still were discarded (e.g., for lack of buffer space).18 Number of datagrams successfully delivered to IP user− protocols. Low 32 bits.19 Number of datagrams successfully delivered to IP user− protocols. High 32 bits.20 Number of IP datagrams that local IP user−protocols supplied to IP in requests for transmission. Low 32 bits.21 Number of IP datagrams that local IP user−protocols supplied to IP in requests for transmission. High 32 bits.22 Number of output IP datagrams with no IP−related problems that still were discarded (e.g., for lack of buffer space). 23 Number of outgoing IP datagrams requiring fragmentation.24 Number of IP datagrams that have been successfully fragmented.25 Value of sysUpTime on the latest occasion at which any counter suffered a discontinuity.Description:

This DID contains a subset of the counters defined in IETF RFC 4293,"Management Information Base for the Internet Protocol (IP)", within theipIfStatsTable OBJECT−TYPE (one IpIfStatsEntry per IP interface andprotocol version).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).DID item position 2 is a pointer, the pointer value can be translated toan interface name in position 1 of the MIBVMIPSTSTAB translation table(DID MIBVMIPSTSTAB).DID item position 3 is the interface number which is used when naming thecorresponding Objects/instances/individuals, see documentation for theMIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB) for more information.DID item position 4 is translated to IP protocol version name in position2 of the MIBVMIPSTSTAB translation table (DID MIBVMIPSTSTAB).

The size of the variables:DID position Block Size1 VMIPSTS 1 bit2−3 VMIPSTS 32 bits4 VMIPSTS 8 bits5 VMIPSTS 16 bits6−25 VMIPSTS 32 bits

6.32 MIBIPIFST2CNT

−VALID FOR APG

DID−name: MIBIPIFST2CNTDID−number: 858Function: IETF RFC 4293 IP related counters per IP protocol version.

DID item Contents position 1 State 2 Number of IP datagrams discarded because they needed to be fragmented but could not be. 3 Number of output datagram fragments generated due to IP fragmentation.



4 Number of IP datagrams transmitted. Low 32 bits. 5 Number of IP datagrams transmitted. High 32 bits. 6 Number of octets transmitted in IP datagram. Low 32 bits. 7 Number of octets transmitted in IP datagram. High 32 bits. 8 Number of IP multicast datagrams received. Low 32 bits. 9 Number of IP multicast datagrams received. High 32 bits.10 Number of octets received in IP multicast datagrams. Low 32 bits.11 Number of octets received in IP multicast datagrams. High 32 bits.12 Number of IP multicast datagrams transmitted. Low 32 bits.13 Number of IP multicast datagrams transmitted. High 32 bits.14 Number of octets transmitted in IP multicast datagrams. Low 32 bits.15 Number of octets transmitted in IP multicast datagrams. High 32 bits.16 Number of IP broadcast datagrams received. Low 32 bits.17 Number of IP broadcast datagrams received. High 32 bits.18 Number of IP broadcast datagrams transmitted. Low 32 bits.19 Number of IP broadcast datagrams transmitted. High 32 bits.

Description:

This DID contains a subset of the counters defined in IETF RFC 4293,"Management Information Base for the Internet Protocol (IP)", within theipIfStatsTable OBJECT−TYPE (one IpIfStatsEntry per IP interface andprotocol version).See RFC 4293 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).


6.33 MIBIFTABLE2CNT

−VALID FOR APG

DID−name: MIBIFTABLE2CNTDID−number: 859Function: IETF RFC 2863 interface related counters.

DID item Contents position 1 State 2 A unique value, greater than zero, for each interface. 3 The type of interface. 4 The size of the largest packet which can be sent/received on the interface. 5 The interface’s address at its protocol sub−layer. Low 32 bits. 6 The interface’s address at its protocol sub−layer. High 32 bits. 7 The current operational state of the interface. 8 The value of sysUpTime when the interface entered its current operational state.

Description:

This DID contains a subset of the counters defined in IETF RFC 2863, "The



Interfaces Group MIB", ifTable OBJECT−TYPE (one ifEntry per interface).See RFC 2863 for more detailed documentation about the individualcounters.DID item position 1 is a state value indicating if the individual is usedor not, (0 = not used).DID item positions 3−7 are status counters.

The size of the variables.DID position Block Size 1 VMIPSTS 1 bit 2−8 VMIPSTS 32 bits

6.34 MIBSCTPSTGCNT

−VALID FOR APG

DID−name: MIBSCTPSTGCNTDID−number: 860Function: IETF RFC 3873 SCTP related counters.

DID item Contents position1 Number of associations for which the current state is either ESTABLISHED, SHUTDOWN−RECEIVED or SHUTDOWN−PENDING.2 Number of direct transitions from the COOKIE−ECHOED state to the ESTABLISHED state by associations initiated by the upper layer.3 Number of direct transitions from the CLOSED state to the ESTABLISHED state by associations initiated by the remote endpoint.4 Number of direct transitions from any state using the primitive ’ABORT’ to the CLOSED state (ungraceful termination).5 Number of direct transition from either the SHUTDOWN−SENT state or the SHUTDOWN−ACK−SENT state to the CLOSED state by associations (graceful termination).6 Number of out−of−the−blue packets, i.e., correctly formed SCTP packets with no appropriate association.7 Number of SCTP packets received with an invalid checksum.8 Number of SCTP control (non−data) chunks sent (retransmissions are not included). Low 32 bits.9 Number of SCTP control (non−data) chunks sent (retransmissions are not included). High 32 bits.10 Number of SCTP ordered data chunks sent (retransmissions are not included). Low 32 bits.11 Number of SCTP ordered data chunks sent (retransmissions are not included). High 32 bits.12 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included). Low 32 bits.13 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included). High 32 bits.14 Number of SCTP control (non−data) chunks received (no duplicate chunks included). Low 32 bits.15 Number of SCTP control (non−data) chunks received (no duplicate chunks included). High 32 bits.16 Number of SCTP ordered data chunks received (no duplicate chunks included). Low 32 bits.17 Number of SCTP ordered data chunks received (no duplicate chunks included). High 32 bits.18 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included). Low 32 bits.



19 Number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included). High 32 bits.20 Number of user messages that have to be fragmented because of the MTU. Low 32 bits.21 Number of user messages that have to be fragmented because of the MTU. High 32 bits.22 Number of user messages reassembled, after conversion into DATA chunks. Low 32 bits.23 Number of user messages reassembled, after conversion into DATA chunks. High 32 bits.

Description:



DID item position 1 is a status counter.


6.35 MIBSCTPST2CNT

−VALID FOR APG

DID−name: MIBSCTPST2CNTDID−number: 861Function: IETF RFC 3873 SCTP related counters.

DID item Contents position1 Number of SCTP packets sent. Retransmitted DATA chunks are included. Low 32 bits.2 Number of SCTP packets sent. Retransmitted DATA chunks are included. High 32 bits.3 Number of SCTP packets received. Duplicates are included. Low 32 bits.4 Number of SCTP packets received. Duplicates are included. High 32 bits.5 Value of sysUpTime on the latest occasion at which any counter above suffered a discontinuity.6 Number of times the T1 timer has expired.7 Number of times the T2 timer has expired.8 Number of DATA chunks in SCTP packets that has triggered the T3−rtx timer.9 Number of SCTP packet DATA chunks retransmissions to this specific IP address.

Description:



The size of the variables.



DID position Block Size1−9 VMIPSTS 32 bits

6.36 MIBSCTPLGCNT

−VALID FOR APG

DID−name: MIBSCTPLGCNTDID−number: 862Function: IETF RFC 3873 SCTP related counters.

DID item Contents position1 The algorithm used to determine the timeout value (T3−rtx) used for re−transmitting unacknowledged chunks.2 The minimum value for the retransmission timeout (milliseconds). Zero means immediate retransmission.3 The maximum value for the retransmission timeout (milliseconds). Zero means immediate retransmission.4 The initial value for the retransmission timer. Zero means immediate retransmission.5 The upper limit on supported associations. "−1" means dynamic number of associations.6 Valid cookie life in the 4−way start−up handshake procedure (milliseconds).7 The maximum number of retransmissions at the start−up phase (INIT and COOKIE ECHO chunks).

Description:This system total DID contains a subset of the counters defined in IETF RFC 3873, "Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)", sctpLayerParamsGroup OBJECT−GROUP.


DID item positions 1−7 are status counters.


6.37 SUAQOSCNT

−VALID FOR APG

DID−name: SUAQOSCNTDID−number: 863Function: Counters for number of SUA messages processed, delivered successfully or not delievered ones per Signalling Process (ASP or SGP).

DID item Contents position1 State2 Number of CLDT messages sent. (SASCLDATA)3 Number of CLDT messages (RASCLDATA) received.4 Number of CLDR messages sent. (SASCLDATA)5 Number of CLDR messages (RASCLDATA) received.6 Number of CORE messages sent. (SASCODATA)



7 Number of CORE messages (RASCODATA) received.8 Number of COREF messages sent. (SASCODATA)9 Number of COREF messages (RASCODATA)10 Number of ERROR messages sent. (SASCODATA)11 Number of ERROR messages (RASCODATA) received.



6.38 SUAASSTCNT

−VALID FOR APG

DID−name: SUAASSTCNTDID−number: 864Function: Counters for AS state changes (duration and number of occurences) when AS state is not in ACTIVE state but ACTIVE state is required.

DID item Contents position1 State2 Duration of non AS−ACTIVE state (TASINAC) (number of seconds).3 Number of occurences, (NASINAC) AS non ACTIVE



6.39 SUAIBSTCNT

−VALID FOR APG

DID−name: SUAIBSTCNTDID−number: 865Function: Counters for IB state changes (duration and number of occurences) when IB state is in DOWN state but UP state is required.

DID item Contents position



1 State2 Duration of IB−DOWN state (TIBDOWN) (number of seconds).3 Number of occurences, (NIBDOWN) IB−DOWN state



6.40 SUAASCONGCNT

−VALID FOR APG

DID−name: SUAASCONGCNTDID−number: 866Function: Counters for AS congestion state duration and number of occurences.

DID item Contents position1 State2 Duration of AS congestion state (TASCONG) (number of seconds).3 Number of occurences, (NASCONG) AS congestedDescription:The record pointer is used to enable translation to symbolic ASname using SUAASTAB translation table.DID position 1 indicates if the record is used (=1) for an ASor not (=0).One record per AS (1−16384)


6.41 SUAIBCONGCNT

−VALID FOR APG

DID−name: SUAIBCONGCNTDID−number: 867Function: Counters for IB congestion state duration and number of occurences.DID item Contents position1 State2 Duration of AS congestion state (TIBCONG) (number of seconds).3 Number of occurences, (NIBCONG) AS congested





6.42 SUAASDATACNT

−VALID FOR APG

DID−name: SUAASDATACNTDID−number: 868Function: Counters for number of SUA CL and CO DATA messages and DATA octets per AS

DID item Contents position1 State2 Number of CL DATA messages sent. (SASCLDATA)3 Number of CL DATA messages (RASCLDATA) received.4 Number of CO DATA messages sent. (SASCODATA)5 Number of CO DATA messages (RASCODATA) received.6 Number of DATA octets sent. (SASOCT)7 Number of DATA octets (RASOCT) received.



6.43 SUAIBDATACNT

−VALID FOR APG

DID−name: SUAIBDATACNTDID−number: 869Function: Counters for number of SUA CL and CO DATA messages and DATA octets per remote Blade at inter−Blade communication.

DID item Contents position1 State2 Number of CL DATA messages sent. (SIBCLDATA)3 Number of CL DATA messages (RIBCLDATA) received.



4 Number of CO DATA messages sent. (SIBCODATA)5 Number of CO DATA messages (RIBCODATA) received.6 Number of DATA octets sent. (SIBOCT)7 Number of DATA octets (RIBOCT) received.



6.44 SUAASPTMCNT

−VALID FOR APG

DID−name: SUAASPTMCNTDID−number: 870Function: Counters for number of ASP TM messages per SP

DID item Contents position1 State2 Number of ASPInactive (SASPIA) messages sent.3 Number of ASPInactive (RASPIA) messages received.4 Number of ASPInactiveAck (SIAACK) messages sent.5 Number of ASPInactiveAck (RIAACK) messages received.6 Number of ASPActive (SASPAC) messages sent.7 Number of ASPActive (RASPAC) messages received.8 Number of ASPActiveAck (SACACK) messages sent.9 Number of ASPActiveAck (RACACK) messages received.



6.45 SUASSNMCNT

−VALID FOR APG



DID−name: SUASSNMCNTDID−number: 871Function: Counters for number of SSNM messages per SP

DID item Contents position1 State2 Number of DUNA (SDUNA) messages sent.3 Number of DUNA (RDUNA) messages received.4 Number of DAVA (SDAVA) messages sent.5 Number of DAVA (RDAVA) messages received.6 Number of SCON (SSCON) messages sent.7 Number of SCON (RSCON) messages received.8 Number of DUPU (SDUPU) messages sent.9 Number of DUPU (RDUPU) messages received.10 Number of DAUD (SDAUD) messages sent.11 Number of DAUD (RDAUD) messages received.



6.46 SUAASPSMMCNT

−VALID FOR APG

DID−name: SUAASPSMMCNTDID−number: 872Function: Counters for number of ASP SM and Management (Error) messages sent and received per SP

DID item Contents position1 State2 Number of ASPUp (SASPUP) messages sent.3 Number of ASPUp (RASPUP) messages received.4 Number of ASPUpAck (SUPACK) messages sent.5 Number of ASPUpAck (RUPACK) messages received.6 Number of ASPDown (SASPDWN) messages sent.7 Number of ASPDown (RASPDWN) messages received.8 Number of ASPDownAck (SDWNACK)



messages sent.9 Number of ASPDownAck (RDWNACK) messages received10 Number of ERROR (SERR) messages sent.11 Number of ERROR (RERR) messages received.



6.47 SUAPERFCNT

−VALID FOR APG

DID−name: SUAPERFCNTDID−number: 873Function: Performance counters for SUA.

DID item Contents position1 State2 Number of occurences, (RFSUADR) Routing failure, No translation for address of such nature.3 Number of occurences, (RFSPADR) Routing failure, No translation for this specific address.4 Number of occurences, (RFSSNFL) Routing failure, Subsystem failure.5 Number of occurences, (RFUNEQP) Routing failure, Unequipped user.6 Number of occurences, (RFNTWFL) Routing failure, Network failure.7 Number of occurences, (RFNTWCG) Routing failure, Network congestion.8 Number of occurences, (RFUNQAL) Routing failure, Reason unqualified.9 Number of occurences, (SYNTXER) Syntax Error in SUA message.



6.48 SUAIBPERFCNT



−VALID FOR APG

DID−name: SUAIBPERFCNTDID−number: 874Function: Performance counters for SUA Iner Blade communication.

DID item Contents position1 State2 Number of occurences, (RFIBSSNFL) Routing failure, Subsystem failure.3 Number of occurences, (RFIBUNEQP) Routing failure, Unequipped user.4 Number of occurences, (RFIBNTWFL) Routing failure, Network failure.5 Number of occurences, (RFIBNTWCG) Routing failure, Network congestion.6 Number of occurences, (RFIBUNQAL) Routing failure, Reason unqualified.7 Number of occurences, (IBSYNTXER) Syntax Error in SUA message.

Description:The record pointer is used to enable translation to symbolic SPname using SUAIBTAB translation table.DID position 1 indicates if the record is used (=1) for an SPor not (=0).One record per SP (1−1024)


6.49 SUAUTILCNT

−VALID FOR APG

DID−name: SUAUTILCNTDID−number: 875Function: SUA utilization counter.

DID item Contents position1 State2 Number of messages requiring (MSGREQGT) Global Title translation.3 Total number of simultaneous (CSECUTIL) connection sections.



6.50 SUAASTAB



−VALID FOR APG

DID−name: SUAASTABDID−number: 876Function: Translation table between AS pointer and AS identity.

DID item Contents position1 Symbolic name of AS.

Description:It translates AS pointer to symbolic AS name.


6.51 SUAIBTAB

−VALID FOR APG

DID−name: SUAIBTABDID−number: 877Function: Translation table between SP pointer and remote Blade identity.

DID item Contents position1 Symbolic name of remote Blade.

Description:It translates SP pointer to symbolic remote Blade name.


6.52 SUASPTAB

−VALID FOR APG

DID−name: SUASPTABDID−number: 878Function: Translation table between SP pointer and SP identity.

DID item Contents position1 Symbolic name of SP.



6.53 LOCUPAINTCNT



−VALID FOR APG

DID−name: LOCUPAINTCNTDID−number: 891Function: Counters for Location Updating from A−interface and for Implicit detach per access type.

DID item Contents position1 Number of location updating attempts from non−registered subscribers (IMSI attach, normal location updating, or periodic updating) over A−interface2 Number of failed location updating attempts due to unknown IMSI number series over A−interface3 Number of location updating attempts for already registered subscribers over A−interface4 Number of periodic location updating attempts for already registered subscribers over A−interface5 Number of IMSI attach messages received (from already registered subscribers) over A−interface6 Number of IMSI detach messages received over A−interface7 Number of successful location updatings for non−registered subscribers over A−interface8 Number of implicit detach events for subscribers in MSC/VLR server, with GSM as last access type stored in VLR9 Number of implicit detach events for subscribers in MSC/VLR server, with WCDMA as last access type stored in VLR10 Number of national roaming restriction events in MSC/VLR server over A−interface11 Number of successful location updatings for already registered subscribers over A−interface12 Number of rejected location updating attempts due to regional subscription over A−interface13 Number of successful location updating indications sent to mobile subscribers, resulting from failure of operations ’update location’ to HLR due to network congestion over Ainterface14 Number of periodic location updating requests for non−registered subscribers over A−interface15 Number of periodic location updating requests when capacity not granted for non−registered subscribers over Ainterface16 Number of periodic location updating requests when capacity not granted for already registered subscribers over Ainterface17 Number of normal location updating attempts for already registered subscribers over A−interface18 Number of successful normal location updating attempts for already registered subscribers over A−interface19 Number of successful IMSI attached location updatings for already



registered subscribers over A−interface20 Number of successful periodic location updatings over A−interface21 Number of location updating attempts from non−registered subscribers (IMSI attach, normal location updating or periodic location updating) on intermediate MSC blade after failed authentication with TMSI over A−interface22 Number of location updating attempts for already registered subscribers on intermediate MSC blade after failed authentication with TMSI over A−interface23 Number of periodic location updating attempts for already registered subscribers on intermediate MSC blade after failed authentication with TMSI over A−interface24 Number of periodic location updating requests for non−registered subscribers on intermediate MSC blade after location update with unknown TMSI over A−interface25 Number of normal location updating attempts for already registered subscribers on intermediate MSC blade after failed authentication with TMSI over A−interface

Description:

All the variables are stored as common data.The difference between the total number of implicit detach events in MSC/VLR (DID: LOCUPDACNT) and the sum of number of implicit detach events for subscribers with GSM and WCDMA access in this DID, reflects the number of implicit detach events for subscribers with no valid access type yet stored in VLR (e.g in the case of subscriber registration in VLR due to PRN but with no radio contact established.The counters specified in DID positions 1, 3−5, 10, 17, 21−23 and 25 are stored in block MVLRP.The counters specified in DID position 8, 9 are stored in block MTV.The counters specified in DID positions 2, 6, 7, 11−16, 18−20 and 24 are stored in block MMMLR.Blocks MMMLR and MVLRP belong to subsystem MMS.The block MTV belongs to the subsystem MDS.


DID position Block Size1 MVLRP 32 bits2 MMMLR 32 bits3 MVLRP 32 bits4 MVLRP 32 bits5 MVLRP 32 bits6 MMMLR 32 bits7 MMMLR 32 bits8 MTV 32 bits9 MTV 32 bits10 MVLRP 32 bits11 MMMLR 32 bits12 MMMLR 32 bits13 MMMLR 32 bits14 MMMLR 16 bits15 MMMLR 16 bits16 MMMLR 16 bits17 MVLRP 32 bits18 MMMLR 32 bits19 MMMLR 32 bits20 MMMLR 32 bits21 MVLRP 32 bits22 MVLRP 32 bits



23 MVLRP 32 bits24 MMMLR 32 bits25 MVLRP 32 bits

7 References

(1) 1/1551 − ANZ 230 03/1, Object Types in STS.

Documents

dids in sts